-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Description
When a scope filter is applied in the Scope Navigation window, the Log Output window updates correctly, but the Duration field is not refreshed and continues to display stale data.
Environment
- Offline log files
- Scope navigation and log output views enabled
Steps to Reproduce
- Load an offline log file.
- In the Log Output window, double-click a log entry that contains scope information.
Result: The Duration field displays the execution time of the scoped method. This behavior is correct. - In the Scope Navigation window, locate the corresponding scope or its parent and apply a filter to hide scope messages.
Result:- The Log Output window no longer displays scope entries. This behavior is correct.
- The Duration field remains unchanged and still shows the previously calculated execution time. This behavior is incorrect.
Actual Behavior
The Duration field retains the last calculated value even when scoped log entries are filtered out and no longer visible in the Log Output window.
Expected Behavior
When scope entries are filtered out and no scopes are visible, the Duration field should be reset to N/A.
This should match the behavior observed when double-clicking a log entry that does not contain scope information.
Impact
This issue may mislead users during log analysis by displaying outdated execution timing data that no longer corresponds to the currently visible log entries.
Metadata
Metadata
Assignees
Labels
Projects
Status