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

Caught an issue if the props file can't be parsed #58

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

dpp
Copy link
Contributor

@dpp dpp commented Feb 7, 2025

💻 Description of Change(s) (w/ context)

If the Maven manifest file, can't be parsed, ignore the parse error

🧠 Rationale Behind Change(s)

The parse error was causing the whole JAR to fail

📝 Test Plan

Runs existing tests

📜 Documentation

What documentation did you add or update?
Was the documentation appropriate for the scope of this change?

💣 Quality Control

(All items must be checked before a PR is merged)
Did you…

  • Mention an issue number in the PR title?
  • Update the version # in the build file?
  • Create new and/or update relevant existing tests?
  • Create or update relevant documentation and/or diagrams?
  • Comment your code?
  • Fix any stray verbose logging (removing, or moving to debug / trace level)?

Before Merging…

  • Make sure the Quality Control boxes are all ticked
  • Make sure any open comments or conversations on the PR are resolved

@dpp dpp requested review from aredridel and earldouglas February 7, 2025 00:05
@@ -157,7 +157,10 @@ case class MavenState(
val manifestString =
Helpers.slurpInputToString(manifest.asStream())
val props = java.util.Properties()
props.load(manifest.asStream())
// if this causes an exception, welp...
Try {
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it be worth logging, or would there be nothing for the user to do anyway?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Maybe... do we have a plan in the Ingestion pipeline to review Error and other anomalies?

@dpp dpp merged commit 53e7e76 into main Feb 10, 2025
2 checks passed
@dpp dpp deleted the catch_some_format_exceptions branch February 12, 2025 13:18
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.

3 participants