Skip to content

(INF-2871) Fix COmanage API request back-off in scripts. #26

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

Merged

Conversation

williamnswanson
Copy link
Collaborator

Fix exponential back-off to also apply to wait times between making requests, and not just timeouts on the requests themselves. Also improve error messages to include more information about how the request went / why it failed.

For the Stdout logs to make their way to the journal when scripts are being run as a systemd service, I believe we may need to add StandardOutput=journal to the service description?

Fix exponential backoff to also apply to wait times between making requests, and not just timeouts on the requests themselves. Also improve error messages to include more information about how the request went / why it failed.
@williamnswanson williamnswanson self-assigned this Mar 6, 2025
Copy link
Member

@brianhlin brianhlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See requested changes in-line. I don't think we need to explicitly set StandardOutput=journal as that's the default

Copy link
Member

@brianhlin brianhlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few changes

Copy link
Member

@brianhlin brianhlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pylint test failures are unrelated to these changes so I'll override to merge.

@williamnswanson in the future, I'd like to see more informative commit messages that adhere to https://osg-htc.org/technology/software/git-software-development/#put-logically-separate-changes-into-separate-commits. I would have liked to see a collection of different commits explaining the what / why of each change rather than blanket "address PR feedback" commits

@brianhlin brianhlin merged commit 5236b3e into opensciencegrid:master Mar 11, 2025
2 of 3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants