Vinh Pham

Not a real solution, but using `ActiveJob::Uniqueness.unlock!` is a quick fix in this situation.

I want to report this happens for the `after_all_transactions` and `after_all_transitions` as well. I don't think this should be the expected behavior. If a transition failed, it should not trigger...

In case anyone comes here with the same problem @danielbonnell has in the [comment above](https://github.com/Casecommons/pg_search/issues/224#issuecomment-254558457) The answer is that trigram search just simply does not work like that. Here is...

Bravo! This is a really well documented issue report. I am running into the same issue using this gem. The order clause won't work with an associated model. I tried...

Bump. I also think we should consider this a bug. It really doesn't play nice with `useExternalFiltering`. For me, I use underscore's `_.debounce()` to limit the amount of AJAX request...

> If you're already supporting multiple authentication strategies, then you can store some information regarding how the user logged in and use that in your application code to treat them...

Thanks for the tip. This worked for my Rails 4.1.5

@CMTegner Have you given additional thoughts to this problem? I am having a similar issue with my setup. I have a button in my autocompleter dropdown that hides the dropdown...

+1 for rails 2.3 support