-
Notifications
You must be signed in to change notification settings - Fork 9
Better error reporting #2585
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
base: main
Are you sure you want to change the base?
Better error reporting #2585
Conversation
a30e6fd to
31f83fc
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.
Pull request overview
This PR enhances error reporting capabilities in the MIES system by adding better runtime error detection, improving error messages, and including additional diagnostic information when assertions fail.
- Added
AssertOnAndClearRTError()calls before critical operations to prevent silent RTE suppression - Enhanced assertion output to include FIFO position and higher precision timestamps
- Improved analysis function error reporting to distinguish between runtime errors and V_AbortCode aborts
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Packages/MIES/MIES_Utilities_ProgramFlow.ipf | Added AssertOnAndClearRTError() in ASSERT/ASSERT_TS functions, added FIFO position tracking to assertion output, and increased timestamp precision to 3 fractional seconds |
| Packages/MIES/MIES_MiesUtilities_Logbook.ipf | Added AssertOnAndClearRTError() and AbortOnRTE to wave assignment operations, and added settingCol parameter to function call for optimization |
| Packages/MIES/MIES_ExperimentDocumentation.ipf | Added AssertOnAndClearRTError() and AbortOnRTE to wave assignment loops to catch runtime errors early |
| Packages/MIES/MIES_AnalysisFunctionManagement.ipf | Improved error reporting to distinguish between runtime errors and V_AbortCode, capturing error code in variable |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
MichaelHuth
left a comment
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.
LGTM
d7d1200 to
a4e2ad6
Compare
This comment was marked as outdated.
This comment was marked as outdated.
a4e2ad6 to
1fb5f1f
Compare
This should make finding the place of lingering RTEs easier.
This would have helped in debugging issue #2568.
This then takes the fast path as we don't need to determine it again.
…ch case And also tone down the message do the user.
Since 8be5388 (NewExperiment: Keep the cache waves across NewExperiment calls, 2025-10-02) we allow to keep the cache across experiments. For the labnotebook row and index cache keeping the cache across experiments is equivalent to deleting the logbook waves and then restarting over. But the upgrade path for both cases did not work as expected as we only did a full upgrade if the labnotebook was empty i.e. the GetLastSweepWithSetting call did not succeed. But if we added an entry for the first sweep, that would pass but then we would not overwrite entries from later sweeps from the previous labnotebook.
…nts again This reverts commit 3ecf2cd (MIES_IVSCC.ipf: Disable cache across new experiments [1], 2025-12-02). Fixed in the previous commit.
8ab1bcf to
c35bc6b
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.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Close #2568