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.

Sign up for GitHub

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

Jump to bottom

Introduce timeout between invocations #4

Open
EthanThatOneKid opened this issue Sep 27, 2023 · 1 comment
Open

Introduce timeout between invocations #4

EthanThatOneKid opened this issue Sep 27, 2023 · 1 comment
Assignees
@EthanThatOneKid

Comments

@EthanThatOneKid
Copy link
Contributor

Bug

Apparently, the bot currently faces an issue where it cannot handle multiple consecutive invocations effectively. In some cases, the most recent invocation tends to overwrite the previous ones.

Strategy

To address this problem, we propose implementing a "cool down" or timeout mechanism. This will allow the bot to work more smoothly by ensuring that it has sufficient time to create GitHub commits sequentially and maintain the desired behavior.
@EthanThatOneKid EthanThatOneKid self-assigned this Sep 27, 2023
@EthanThatOneKid
Copy link
Contributor Author

Note: A TTL duration is deemed invalid if it is shorter than the constant timeout.

@EthanThatOneKid EthanThatOneKid mentioned this issue Oct 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EthanThatOneKid EthanThatOneKid

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@EthanThatOneKid