-
Notifications
You must be signed in to change notification settings - Fork 449
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix or workaround logical and cosmetic bugs with S3 impl
- Add locking for (initial call to) GetChildren and (all calls to) LoadMoreChildren Both of these append to the internal node cache Any combination of these calls can possibly be in progress concurrently The easiest (and probably most correct) behavior is to queue up calls behind a single write lock - Ignore attempts to load more children when one is already in progress for the node This can happen if the user double clicks the load more node The intent was most likely to load a single page Rather than queueing up 2 pages, it's better to drop the subsequent load command invocations - Remove leading period from file extension filter Per electron doc, the extension filter should not contain the leading period Without this, Windows was shown to duplicate the file extension - Tweak order of file extension filters Was shown on mac that the first item will be the one selected by default - Use hardcoded SVGs when the user has Seti file icon theme enabled Indentation of child nodes gets messed up when the parent node doesn't have an icon microsoft/vscode#85654 This is the case for the very common Seti file icon theme Switching to SVG works around the issue for Seti Other themes may also not have folder icons however there is no way to detect this currently and the thought is that this is quite uncommon The pros of using the native icon theme outweigh the cons here - Clear the AWS SDK S3 bucket region cache before invocations S3 maintains an internal cache of region to bucket name as an optimization however this cache does not contain the partition Bucket names are not unique across partitions This can cause the wrong region to be selected when the user switches between partitions that contain buckets with the same name - Workaround logging errors when Error.name is a number e.g. AWS SDK for JS can sometimes set the error name to the error code number (like 404) Node.inspect (used by the logger) has a bug where it expects the name to be a string and will actually throw an Error otherwise VSCode's ES5 type definitions and lodash also make this expectation The spec seems to make no mention of the string requirement Additionally, Node fixed the Error in v12.14.1 nodejs/node#30572 However, VSCode uses an older version of Node without the fix
- Loading branch information
Showing
22 changed files
with
274 additions
and
56 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.