-
Notifications
You must be signed in to change notification settings - Fork 6
(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
(INF-2871) Fix COmanage API request back-off in scripts. #26
Conversation
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.
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.
See requested changes in-line. I don't think we need to explicitly set StandardOutput=journal
as that's the default
6747fd3
to
e51ac88
Compare
e51ac88
to
820d978
Compare
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.
A few changes
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.
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
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?