We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ubiquity/ts-template#61 (comment)
When trying to check for the current pull-requests, the bot fails with a 500 errors and retries until exhaustion:
https://dash.cloudflare.com/17b9dfa79e16b79dffcb11a66768539c/workers/services/view/ubiquity-os-command-start-stop-main/production/observability/logs?time=%7B%22from%22%3A1740770520000%2C%22to%22%3A1740770700000%2C%22type%22%3A%22absolute%22%7D
The fetching of the pull-requests kept failing with a 500 error, until Cloudflare worker was shut down.
Ideally, the pull-requests should have been handled without a 500. Worst case, an error should have been posted.
The text was updated successfully, but these errors were encountered:
Note
The following contributors may be suitable for this task:
79% Match ubiquity/devpool-directory-tasks#21
79% Match
79% Match ubiquity-os/ubiquity-os-kernel#227
77% Match ubiquity/cloudflare-deploy-action#19
77% Match
Sorry, something went wrong.
No branches or pull requests
ubiquity/ts-template#61 (comment)
When trying to check for the current pull-requests, the bot fails with a 500 errors and retries until exhaustion:
https://dash.cloudflare.com/17b9dfa79e16b79dffcb11a66768539c/workers/services/view/ubiquity-os-command-start-stop-main/production/observability/logs?time=%7B%22from%22%3A1740770520000%2C%22to%22%3A1740770700000%2C%22type%22%3A%22absolute%22%7D
What happened
The fetching of the pull-requests kept failing with a 500 error, until Cloudflare worker was shut down.
What was expected
Ideally, the pull-requests should have been handled without a 500. Worst case, an error should have been posted.
The text was updated successfully, but these errors were encountered: