Alex Burgel

This issue has been frustrating me too so I did some investigating. The cause is that there were two fields that were missed when updating the migrations for django 4.0...

@arnav13081994 @jleclanche any updates on 2.7? it's blocking a bunch of us from upgrading to django 4.0 i'm happy to help out with the release if it's needed 😄

@jleclanche I suggested some changes to that PR and tested locally. I'm concerned that it will take a while to get that PR into good shape, let alone all the...

> @aburgel `3.` is always an option as they could simply run `python manage.py djstripe_sync_models Payout` after the `schema` and `code` changes get deployed. @arnav13081994 Oh, that's useful! I think...

The issue I was seeing was that the commits from the second parent of the merge were not shown. You would only see the merge commit itself, not what it...

@mark2185 thanks for the tip on how to speed this up! is it possible to turn your patch into a config option? seems like it would be pretty useful for...

is there a reason this is closed and marked as completed? it's still broken for me on rails 7.1. (same with #566)

> The same problem occurs if you're not using `before_all` but regular transactional tests; so, it's more about ensuring that background tasks are executed before teardown. Sure, but it wouldn't...

I think the issue is that [hooks defined at the suite level run after hooks](https://www.rubydoc.info/gems/rspec-core/RSpec%2FCore%2FHooks:after) defined in each example or context. It looks like rspec mixes in a module that...

Try adding `config.rails_semantic_logger.semantic = false` to your `development.rb` and `test.rb` environment config files.