Kurt Werle

I'm guessing the problem is somewhere between ``` 124: safely_define_method klass, "#{name}!", ->(*args, &block) do 125: aasm(aasm_name).current_event = :"#{name}!" 126: aasm_fire_event(aasm_name, event, {:persist => true}, *args, &block) 127: end ```...

Ah - it looks like maybe this is fixed in https://github.com/aasm/aasm/tree/add_ruby_3.2_in_github_workflows Looks like that was only a partial fix.

I found that location by stepping into my code where it was failing. I certainly didn't dig into the AASM code to figure out the right fix. It seems likely...

> Can you create a failing spec? I'm on an M1 mac and do all my dev work in docker containers. I have not been able to get the aasm...

I'm starting to dig into this, and the first broken spot I see is we have: ``` event :submit do before { |some_variable:| self.foo = some_variable } transitions from: ......

Ah - instead it is being passes as a hash: `{:some_variable =>1234}`

For those following with interest - I think I've given enough detail to formulate a reasonable test in https://github.com/aasm/aasm/issues/834#issuecomment-1793154832 . I will not be pursuing this further - our workaround...

We're wandering way off topic - but today I plan on implementing a docker project for mounting remote filesystems. I've used fuse-sshfs on OSX and it was unstable. My intention...

I would also request that if/when this is implemented there be a remote_command portion. I specifically want to forward a port to a service that I want to launch as...

My strong recommendation is to side-grade to vs code. I'm happy to take PRs for atom stuff, but I'm not going to spend time on it.