Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ls on empty container throws FileNotFoundError #64

Closed
jamesmyatt opened this issue Jun 8, 2020 · 3 comments
Closed

ls on empty container throws FileNotFoundError #64

jamesmyatt opened this issue Jun 8, 2020 · 3 comments

Comments

@jamesmyatt
Copy link
Contributor

Working on reproducing #63, I've realised there's a more fundamental problem with ls, which is that it doesn't work with empty containers. It throws a FileNotFoundError rather than returning [].

See: 1b1cd42

Failure: https://dev.azure.com/dask-dev/dask/_build/results?buildId=1242&view=logs&j=d090b295-8b65-5b33-df45-4b0e4ec519f8&t=8e34badb-79ac-5acb-45f0-df0af76ba649&l=133
@jamesmyatt jamesmyatt changed the title ls on empty container give FileNotFoundError ls on empty container throws FileNotFoundError Jun 8, 2020
This was referenced Jun 8, 2020
Closed
Closed
@andersbogsnes
Copy link
Contributor

Could be related to my issue #59 - the root cause of that is also an ls issue

@jamesmyatt
Copy link
Contributor Author

jamesmyatt commented Jun 9, 2020 •
edited

@andersbogsnes , I agree they seem related. Especially this comment: #59 (comment)

@hayesgb
Copy link
Collaborator

hayesgb commented Aug 2, 2020

Fixed in 0.3.1.

@hayesgb hayesgb closed this as completed Aug 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jamesmyatt @hayesgb @andersbogsnes