The relevant part of the node path is displayed next to the tab's name when only one tab is open for a blob container or table

[v-xianya]

Storage Explorer Version: 1.36.0-dev (101) Build Number: 20240926.1 Branch: main Platform/OS: Windows11 Architecture: arm64 How Found: From running test cases Regression From: Not a regression

Steps to Reproduce

1. Expand one storage account -> Blob Containers.
2. Open one blob container.
3. Check whether no relevant part of the node path is displayed next to the tab's name.

Expected Experience

No relevant part of the node path is displayed next to the tab's name.

Actual Experience

The relevant part of the node path is displayed next to the tab's name.

Additional Context

1. For now, we only occurred this issue against blob containers and tables on Windows ARM64 and it is unstable.
2. This issue can't be reproduced consistently.
3. Here is the record:
4. Here is the log: 2024-09-27_055658 (2).zip 2024-09-27_055658.zip

[craxal]

@v-xianya Can you verify whether this only reproduces on Windows ARM64? Or does this also reproduce in Windows x64 or other platforms?

[craxal]

Unfortunately, the logs you attached don't contain much useful information. I'm going to add some extra verbose logging to help us narrow down the problem. If you can repro, please share any relevant verbose output from the renderer process (or just share the renderer process logs).

[v-xianya]

Got it, will share the logs once we reproduce this issue.

[v-xianya]

Hi @craxal We reproduced this issue on Linux(.tar) using build 20241008.1. here is the log: 2024-10-08_014006_renderer_5006.zip

[v-xianya]

Hi @craxal @richardMSFT Today we met this issue on MacOS ARM, Windows ARM64, Windows X64, Linux.

here are the steps that can reproduce this issue <Also apply to file shares/tables/queues>. I hope this helps.

Steps:

1. Ensure there are two blob containers with the same name but from different storage accounts.
2. Expand one storage account and temporarily open the blob container.
3. Expand the other storage account and temporarily open the blob container with the same name.

Here is the render log on Windows ARM64. 2024-10-09_074651_renderer_6888.log

Below is the record:

[v-xianya]

@richardMSFT Verified this issue on the rel build 20241011.2. It doesn't reproduce. However, I noticed that the relevant part of the node path briefly flashes after opening a secondary temporary tab. I'm not sure if this requires further attention. Here is the record.

[craxal]

The flash comes from the time between adding the new temporary tab to the collection of tabs (which causes path differentiations to be recalculated) and removing the old temporary tab. We can address this in 1.37.0.

[craxal]

Initial problem is resolved, but we won't worry about the "flash".