Matthew Rayermann

Issue is with the * character it seems. Also, I noticed that files adjacent to the troublesome folder get uploaded.

For 1.27, get component ready to use.

`archiver` ultimately responded to the security issue in just 5 days. I think that's pretty good. https://github.com/archiverjs/node-archiver/issues/583 Moving this to future...

@jsuddsjr to be clear are you using blob containers? Because if you are instead using file shares, those can be mounted as drives over SMB. So something for you to...

Closing due to lack of response. If you are still encountering this problem, we recommend opening a support ticket via the Azure portal alternatively you can open a new issue...

@JasonYeMSFT do we want to dedicate this issue (or a separate one) to making sure we update our blob SDK in 1.26?

@FaronFaulk it can be difficult trying to decide the various places where we should do deep investigations into error messages during runtime. Can you share with us what you were...

Hi @FaronFaulk, if you'd like to use an image in your reply, you'll need to come to GitHub and reply there. Thanks.

Ok so during an explorer refresh, thank you!

We need to: - Have team discussion regarding error reporting in explorers (deficiencies with using the info bar) - Talk about checking SAS expiration in explorers - Investigate experimenting with...