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
Enhance the log for failures when reading or parsing the fee_estimates.dat file #3501
base: 1.15.0-dev
Are you sure you want to change the base?
Conversation
Use a try-catch block for error handling in the TxConfirmStats::Read function.
Update fees.cpp [try-catch]
What error didn't get caught? |
Although the check on fileDecay ensures the integrity of the data by confirming that it is between 0 (no decay) and 1 (full decay), there remains a potential issue with data corruption or a software bug. The try-catch block has the benefit of logging any potential errors. |
Neat. Seems like it would cut out uncertainties.Sent from my iPhoneOn Mar 28, 2024, at 10:27 PM, Skylar Loomis ***@***.***> wrote:
Although the check on fileDecay ensures the integrity of the data by confirming that it is between 0 (no decay) and 1 (full decay), there remains a potential issue with data corruption, modification, or a software bug.
The try-catch block ensures that the data integrity adheres to specific expectations regarding its values and structure. Additionally, it has the added benefit of logging out any potential errors.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Okay. An overall try-catch already is implemented in the calling code: Line 926 in 6c0095b
If you're looking to enrich the logged message (I'd support that), it should be done in that catch block instead. |
Use a try-catch block for error handling in the TxConfirmStats::Read function.