-
Notifications
You must be signed in to change notification settings - Fork 437
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
async_commands: extended configuration proposal #914
async_commands: extended configuration proposal #914
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 at first glance. I've skimmed the code for obvious errors and it looks good to me. Will come back to it in the evening if time allows.
Hey @Steveb-p. Did you have any chance to look at it? The build is failing from 3rd party reason. I'd like to know if we can do some progress with it. Cheers, |
'command' => Commands::RUN_COMMAND, | ||
'queue' => Commands::RUN_COMMAND, | ||
'client' => $client['name'], | ||
'command' => $client['prefix'].Commands::RUN_COMMAND, |
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.
IMO prefix is misleading, what about to allow configure a whole command and queue names?
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.
The default value could be the one from Commands::RUN_COMMAND
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.
@makasim sounds like a great idea. I'm going to implement the fix
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey @makasim, please accept my apologies for this late reply. I submitted the change related to the command name. Could you take a look again? |
Looks good to me. There should be no BC breaks because of it so no migration documentation necessary - though docs related to async commands might need an update. Specifically: |
Hi guys, I use async_commands and I found out that it's missing a few things.
Firstly, we can't prefix
run_command
queue and because of that, on example: if we use one queue provider with many services it will provide problems as we will push everything to one queue.Same with many configurations, each of it can have a different prefix.
Then, the second issue: default Symfony process timeout is 60 seconds. after this, the message is requeued and processed again. We don't have any option to extend this time.
In this pull-request I provide a proposal for these two issues:
run_command
queue