Nicholas Barone

I was very confused by the docs, and thought this was supported. > In the latter case AASM will try to use pluralized column name to access possible enum states....

There's a Rails update that should let you resolve the warnings: https://rubyonrails.org/2022/11/25/this-week-in-rails-disable-enum-methods-generation-a-concurrency-fix-and-more-5e5cc7ab

Update: Explicitly adding the PT update callback a second time, at the bottom of the model: ``` paper_trail.on_update end ``` causes there to be (1,3,5) versions (consistent with two update...

Update: I tried explicitly telling PT to record a version in an AASM callback: ``` ensure_on_all_events do self.paper_trail.save_with_version end ``` This causes the same behavior as my last comment -...

This is my most promising lead so far: https://blog.carbonfive.com/raking-and-testing-with-eventmachine/

@cronoklee I'm at the same place you are. ...Do we need to specify an *amount* in the `withdrawPayments` action?

OZ [docs ](https://docs.openzeppelin.com/contracts/2.x/api/payment#PullPayment-withdrawPaymentsWithGas-address-payable- )say it's just all funds, _but_ they also say `withdrawPayments` is deprecated in favor of `withdrawPaymentsWithGas`.

I saw that, and thanks! That meant that the contract address has funds, but my `withdraw` still doesn't seem to be able to move those funds (although it publishes a...

I needed this too! Thank you!

I recommend: 1) Consolidating all the mutations "in one place" - so, either the `Account::Syncer#sync` handles the `update!(status: "SYNCING")`, _or_, `Account#sync` does the `upsert_all` (and the syncer returns the `balances_to_upsert...