CRAYSAT-1945: Fix traceback error of session checks in CFS v2 #306
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Testing output on starlord: https://gist.github.com/annapoorna-s-alt/3067f3aeec92b9a38a26e9329572ee65 |
annapoorna-s-alt
requested review from
haasken-hpe,
ethanholen-hpe and
vinanti-p
haasken-hpe
approved these changes
Dec 18, 2024
|
/backport release/3.33 |
|
Backporting into branch release/3.33 was successful. New PR: #307 |
This was referenced Dec 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary and Scope
Fixed the traceback error encountered during session checks in CFS v2 when using a smaller page size.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
List the environments in which these changes were tested.
Tested on:
Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?
Tested cfs v2 and cfs v3 session checks for both lower and higher page size
Risks and Mitigations
Low
Pull Request Checklist