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

Event Queue #30

Closed
whilefoo opened this issue Mar 10, 2024 · 1 comment
Closed

Event Queue #30

whilefoo opened this issue Mar 10, 2024 · 1 comment

Comments

@whilefoo
Copy link
Contributor

I think we should process events from one repository (or maybe from one issue) in a sequential order. For example if the maintainer adds labels and closes the issue, the second event might be executed before the first one because of the async nature of Github Actions which could cause potential bugs.
But there might be scenarios where sequential execution is unwanted for example there is a long running task triggered by a command - in this situation we still want to execute other events while the task is running.

@0x4007
Copy link
Member

0x4007 commented Mar 11, 2024

Makes sense.

Can you organize your research and any context you have and include it here? It will provide sufficient context so that somebody else, like @FernandVEYRIER can jump in and help if you want it to be worked on concurrently to your other work.

You should also provide a time estimate.

@0x4007 0x4007 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
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

2 participants