Tim Diggins

Thanks for response @tdeo it led me to the right answer, but it still feels like a workaround. `bundle exec rubocop` in the nexted project directory *doesn't* work on it's...

The only slightly unusual thing with Thredded is that the app uses threads to render some things in parallel (this is really a way of dealing with onebox). So maybe...

(Yes, this is going quite off topic now, but continuing the discussion here anyway) It sounds like your ActiveJobs / DelayedJobs were running in your tests but in the background....

draft PR @ https://github.com/plentz/lol_dba/pull/148 - but needs a spec writing for this case

I agree with this. However there could be an argument that this makes password reset enumeration attacks a tiny bit easier (because you only need a simple get to see...

FYI same issue with let and include_context, where the context includes the same let. so you might write ```ruby shared_context "projecty" do let(:project) { raise "define project in spec" }...

Thanks for noticing. https://github.com/thredded/thredded_create_app needs updating - it hasn't been updated in a while. In the meantime, you'd have to use a much earlier (out of date) version of ruby...

Fixed in #260 (but only one of the two links fixed in #280)

Actually I've just tested this out and my theory seems to be wrong. You need the `export BUNDLE_GEMFILE=Gemfile.next` in the calling shell (where you type `next rails c` or whatever)...

@kaspergrubbe I don't quite follow you / @pauldix, old gem's client requires username and password and doesn't seem to support tokens at all.