-
-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Listing directory failure on folder within bucket with ~ in path #9611
Comments
What is the name of the folder that gives the error when attempting to browse? |
Hi -- It's 1404. 1403 works OK and is in the same enclosing folder, so I don't think the folder name . Would logs be helpful, and if so, where would I find them? |
Please post the transcript from the log drawer (⌘-L) from both the Browser and the Transfers window. |
Thank you! Here's the transcript from the browser -- it includes listing of a directory that does work (1403) and another that does not (1404). Bucket name and credentials have been changed. I'll send the transfer log as soon as the current transfer fails.
|
|
Thank you!! Just downloaded the latest snapshot build and everything seems to be working great. Much appreciated. |
I have tried repeatedly to upload about 2100 files to a particular folder within a bucket, both all at once and in smaller chunks. At some point (which seems to vary), the upload fails, and when I try to list the current contents of the folder, I get the dreaded error:
Note that this problem occurs on a folder within a bucket -- I can log in and see the contents of the bucket OK and can list other folder contents without a problem, so the issue is not my credentials. I can log in via the web interface or AWS cli (same credentials) and list the folder contents without a problem. I've had the issue on a few folders, while others have uploaded OK. The files in the folder have some "~" characters in them, but these don't seem to cause issues in the other folders. No equals or @ signs in the filenames, as reported in previous tickets with the same error. I have not run into this problem until yesterday (6/28/16), and tried with the latest snapshot build as well as the current release. Any help would be much appreciated!
The text was updated successfully, but these errors were encountered: