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

Update release/3.30 to 3.30.1 #256

Merged
merged 2 commits into from
Aug 20, 2024
Merged

Update release/3.30 to 3.30.1 #256

merged 2 commits into from
Aug 20, 2024

Conversation

shivaprasad-metimath
Copy link
Contributor

@shivaprasad-metimath shivaprasad-metimath commented Aug 20, 2024

Summary and Scope

Merge main to release/3.30 to get a stable build of the latest 3.30.1.

This will be merged locally and pushed to get a true fastforward merge without a merge commit, which git does not allow through the pull request web UI, unfortunately.

Issues and Related PRs

Testing

Test description:

See PRs to main.

Risks and Mitigations

See PRs to main.

Pull Request Checklist

  • Version number(s) incremented, if applicable
  • Copyrights updated
  • License file intact
  • Target branch correct
  • CHANGELOG.md updated
  • Testing is appropriate and complete, if applicable
  • HPC Product Announcement prepared, if applicable

shivaprasad-metimath and others added 2 commits August 14, 2024 11:16
During the sat status execution if the user token is expired, there is a traceback which comes as the output. Hence graceful handling of the token expiry is added to inform the user.
…ful-handle

CRAYSAT-1392: Graceful handle of user token expiry
Reviewer:Ryan
@shivaprasad-metimath shivaprasad-metimath merged commit fe8ea55 into release/3.30 Aug 20, 2024
5 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