Paolo Zaccagnini
Paolo Zaccagnini
I've got this issue, too, and I see that the consumers are registered when the `Hutch::Consumer` mixin is included and this doesn't seem to play well with the development environment's...
I guess so, or the consumers registration could happen differently - I'm not sure what would work best, though. After some study I've found a better workaround for a Rails...
Will do, and would be glad to have some zeitwerk expert to chime in if there are better ways to tackle this issue
Here it is, feel free to edit/improve/close: https://github.com/gocardless/hutch/pull/342
..or deadlocks 
Then we'd lose the purpose and benefit of the counter cache, but this was an example: the same happens when an after_save callback updates another parent object
Works for me if I clone the repo into ST3's Packages directory
Mac & Firefox 79: works if you move the `open_with_mac.py` script to `~/Public`.
This is the biggest problem I have with SM. GitX commit graph was/is far more efficient and easier on the eyes.
If you're on a mac you need to add that file to `~/Library/Application Support/Sublime Merge/Packages/User`. If you use the light theme the file name should be `Merge.sublime-theme`