Closed v-xinda closed 3 years ago
I've tried this scenario. The experiences aren't optimal.
Actual result: once the upload completed, readme.md did show up under the container "container1" node
Continue testing:
Actual result: You will see the new tab "container1 [Codespaces] - Visual Studio Code - Insiders - Codespaces" like this:
Clicking on the node "container1' shown as the last node in the above screenshot, you'll get the below error:
Remember that at this point, I already have the file "readme.md" uploaded into container "container1" as shown in the main Codespaces window:
BTW, this works as expected in normal VS Code with the storage extension. That is, the files are shown if i open in a new window.
Actual result: once the upload completed, readme.md did show up under the container "container1" node
@jinglouMSFT As of right now it's by design to not show a blob that has just been uploaded (unless the blob container is already expanded). When you uploaded "readme.md" was "container1" expanded?
Actual result: You will see the new tab "container1 [Codespaces] - Visual Studio Code - Insiders - Codespaces" like this:
Codespaces' behavior with opening in file explorer is funky right now. It looks like you ran into a similar issue CTI filed in https://github.com/microsoft/vscode-azurestorage/issues/874. A VS Code bug on this has been filed in https://github.com/microsoft/vscode/issues/110352.
As for the original reason for this issue, which was not being able to select files to upload in Codespaces, it has been resolved (VS Code bug: https://github.com/microsoft/vscode/issues/110265). So this issue can be closed once we tie up any loose ends based on this comment.
OK. my issue is different from what's originally in bug 877. Created a new issue #898 for my part of the issue.
OS: Win10 Build Version: Latest Release
Repro Steps:
Expect: The file shows in a dialog.
Actual: There is no file shows.