-
Notifications
You must be signed in to change notification settings - Fork 13
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
Detect already running execution for group_id #63
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a couple things then green light from me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A proposal on the name registration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick on error atom, but LGTM
happy when CI is
bbea5ee
to
a0ac8d0
Compare
a0ac8d0
to
01d82b7
Compare
All the requested changes have been addressesd
Detect if an execution with a specific group id is already being executed. Using the
:global
registry should make this distributed as well. Raise an error in this case by now.We can do different things with this error later on: stop current execution, requeue message...
Some refs on the name registration: https://hexdocs.pm/elixir/1.12/GenServer.html#module-name-registration
PD: Maybe there better solutions for this, but I had some fun learning the :global registry usage hehe