You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using viewer to diagnose build issue(s) and trying to find ways to optimize my investigation. A few ideas came to mind that can help when comparing between two logs.
"Search in subtree" is helpful but sometimes the result can exists in a different node. Consider extending with a different option like, "Search in under this project". This change will also work well when comparing from a different different binlog.
$Target search should have an option to filter Skipped Targets.
$start and $end should show all results or compute all of them in order to show top/bottom. As it is, the results are sorted but is sometimes misleading because not all results are present.
For privacy, add a clear recent searches.
Add a "searching" icon or indicator that work is processing.
Add an option to ignore Evaluation.
Add an option to collapse all. (Also on the log side too)
Typing a "space" should not start a search.
Thank You.
The text was updated successfully, but these errors were encountered:
You can combine search in subtree for multiple projects under($1) under($2) $csc. Multiple under clauses act as a union (not intersection). There's also a project clause, so you can look under specific projects project(Foo.csproj) $csc. They also combine and you can have more than one.
OK
you can click the button to show all results (slow), then all results will be loaded and sorted
OK
OK
You can add a notunder(Evaluation) clause to filter out eval
I was using viewer to diagnose build issue(s) and trying to find ways to optimize my investigation. A few ideas came to mind that can help when comparing between two logs.
Thank You.
The text was updated successfully, but these errors were encountered: