Vladimir Dementyev

> do you remember any places in your code using it? Nope 🙂

Here is also Action Cable protocol description: https://docs.anycable.io/misc/action_cable_protocol

> The connection increment is happening in the Puma thread It also must happen in the test thread (before any browser interaction), since every test is wrapped into a transaction....

Hey, Could you please provide more details? Rails version, Isolator version, environment in which you observe this issue (development, test, production), database configuration (multi-db or not, etc.)

> Isolator 0.11 Let's upgrade Isolator first (the latest version is 1.0.1) and see if it helps. > Multi database with postgresql Is the model in question use the primary...

Thanks! Okay, the next step would be running a failing test with Active Record logs and try to figure out what's going on there. Here is a quick snippet to...

Hey @rwehresmann! Sorry for late response. Have no good clues for now, but we can try one more debugging technique (using the latest Isolator). We can define Isolator callbacks to...

Thanks for the report and the backtrace! Can you also share an exception itself? The backtrace doesn't have any traces of Isolator.

Thanks! This line is just calling `super`: https://github.com/palkan/isolator/blob/b3e918fb69bd887beece7f2a4df5cb1275a6724c/lib/isolator/railtie.rb#L38 The exception comes from the `file_fixture` helper: https://github.com/rails/rails/blob/274bc97d63f9e29129851a99c00fd2cefe97cfcf/activesupport/lib/active_support/testing/file_fixtures.rb#L27 It seems that the `file_fixture_path` is not configured.

> Perhaps isolator is making this call before ActiveStorage is loaded? Isolator doesn't call `#setup_fixtures`, it just extends it, so 🤷‍♂️As I understand, removing isolator fixes the problem, right? I...