Liz Conlan

@nigeljonez > Alaveteli cannot rely on the fact that the "From:" component is a verified sender Yes, unfortunately by the time the message gets as far as the Rails application,...

> https://blog.socialcops.com/technology/engineering/camelot-python-library-pdf-data/ Had a quick play with that last night (used an older laptop so made the path to install harder for myself than it needed to be) and it...

Hmm, we are storing this properly and we generate a valid header in the form: ``` , > ``` From examining the logs, the Exim MTA appears to have hedged...

Not having much luck finding any references to this behaviour online, maybe it's acceptable? Could it be a stray rewriting rule?

Ok, so it looks like part of what's happening in the first case might be that it's searching on the notes field as well as the name so there are...

The fix might be as simple as: ```diff def select_authority … - @xapian_requests = typeahead_search(query, :model => PublicBody) + @xapian_requests = typeahead_search(query, + model: PublicBody, + prefix: 'name') ``` Which...

Ah, looks like we're building all the `PublicBody` model fields into a single Term List which explains why our results are off (we also have V for variety and U...

Ok, this seems to work (although `ActsAsXapian` doesn't implement weighting - although it does have access to it via the standard ruby bindings - so implementing this may not be...

to pick up where we left off (or at least close to it), something like... ``` rb start_id = ENV["START_ID"] || 0 InfoRequestEvent.where("id > #{start_id}").find_in_batches(:batch_size => 300) do |events| events.each(&:xapian_mark_needs_index)...

Would we have to do anything special to prevent something from automatically adding everything to the job queue on deploy?