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

(PE-38293) Fix test for modified error message with new Bouncy Castle #2868

Conversation

nmburgan
Copy link
Contributor

No description provided.

@nmburgan nmburgan requested review from a team as code owners July 16, 2024 19:12
@nmburgan
Copy link
Contributor Author

Tested locally with new clj-parent and this fixes the test failure

@nmburgan nmburgan force-pushed the issue/main/pe-38293_fix_test_for_new_bouncycastle branch from 5297bfd to 1f5339b Compare July 16, 2024 20:19
@justinstoller
Copy link
Member

closing and re-opening to try and kick this against the recent clj-parent bump

@justinstoller
Copy link
Member

@nmburgan , looks like we need to make the final dashes in the exception message optional. Doesn't look like the FIPS jars have been updated with the improved error message yet.

Copy link
Member

@justinstoller justinstoller left a comment

Choose a reason for hiding this comment

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

Message change hasn't happened in FIPS yet, assertion needs to handle both, or do separate assertions for FIPS vs non-FIPS.

@nmburgan nmburgan force-pushed the issue/main/pe-38293_fix_test_for_new_bouncycastle branch from 1f5339b to 2e5af50 Compare July 16, 2024 21:45
@nmburgan
Copy link
Contributor Author

Updated

@justinstoller justinstoller merged commit b338e3a into puppetlabs:main Jul 16, 2024
11 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