Closed andreaseriksson closed 8 months ago
Thank you for the detailed report @andreaseriksson ~ I noticed something like this as well yesterday - especially after recompiles.
In the latest version I didn't make any changes in the supervision stuff but perhaps this could be the issue: https://github.com/cpursley/walex/blob/master/lib/walex/events.ex#L32
Could you try with the previous version? You won't be able to use the DSL but you can use process behavior (in README - def process(txn) do
etc). I won't be able to dig in until this weekend.
With 2.3.2 it works every time. Restarted server about 15 times 😃
My guess its the module load order: https://github.com/cpursley/walex/blob/master/lib/walex/events.ex#L37-L40
@andreaseriksson 3.0.2 release should resolve this issue:
https://github.com/cpursley/walex/blob/master/lib/walex/events.ex#L38
Modules are also now optional in the config if you follow this pattern: MyApp.Events.User, MyApp.Events.ToDo
✅
Actually, there's still some issues (around transactions). Working on getting those fixed.
I have an issue that it does not work on every server boot in my dev environment. When it works, it works 100% and vice versa. My guess, some sort of race condition. The processes seem to be alive and seems to be the same in both scenarios.
dev.exs
I run
Elixir 1.15.7 (compiled with Erlang/OTP 26)
I run Postgres 15 (postgres.app) and ran these and restarted the server: