-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix: Add Index out of bound exception handling for PropertiesFile.save() #96
Conversation
a39c0b4
to
9e630de
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.
This should workaround the issue. Were you able to locate the root cause? Is this from lack of file access, or Properties have become corrupted?
I'll ask if customer can give us some log info that Marvin previous added. It sounds like a random access issue that caused by multithreading |
Will the logs you and Marvin added provide more info about the root cause? It looks like we're logging the file path and the stack trace, but the problem appears to be with the values in the properties map. Do we blanket catch Exception normally in our SDKs? It's normally an anti-pattern since it can potentially hide serious problems that should actually escalate instead of leaving the app in an uncertain state. |
## [1.5.2](v1.5.1...v1.5.2) (2022-11-19) ### Bug Fixes * Add Index out of bound exception handling for PropertiesFile.save() ([#96](#96)) ([c6578bf](c6578bf))
🎉 This PR is included in version 1.5.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Summary
Expection catch and log for PropertiesFile.save()
Change more general Exception catch for PropertiesFile.load()
Unit test for added function
Checklist