Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better exception #56

Open
apotonick opened this issue Oct 19, 2022 · 1 comment
Open

Better exception #56

apotonick opened this issue Oct 19, 2022 · 1 comment

Comments

@apotonick
Copy link
Member

I don't know how it could be done, yet, but the wiring error exception with anonymous classes is very hard to debug

Unrecognized Signal `#<Trailblazer::Activity::End semantic=:skip>` returned from #<Class:0x00005559038d3b30>. Registered signals are, 
#<Trailblazer::Activity::End semantic=:failure>
#<Trailblazer::Activity::End semantic=:success>
#<Trailblazer::Activity::End semantic=:key_not_found>

Maybe the activity could maintain a "name hint" and add this to the exception. Then it would be much more obvious this exception is coming from, say "song.deserialize.nested".

@apotonick
Copy link
Member Author

Actually, this exception could be prevented in 99% of the cases if we had a compile time check when adding a Subprocess that has unwired termini.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant