Missing keys after upgrade to 0.3.0
See original GitHub issueThe new version of s3fs is not retrieving all bucket keys. E.g.:
In [16]: s3 = s3fs.S3FileSystem(anon=True, client_kwargs=dict(region_name='eu-west-2'))
In [17]: store = s3fs.S3Map(root='zarr-demo/store', s3=s3, check=False)
In [18]: list(store.keys())
Out[18]:
['.zattrs',
'.zgroup',
'foo/.zattrs',
'foo/.zgroup',
'foo/bar/.zattrs',
'foo/bar/.zgroup',
'spam/.zgroup',
'spam/eggs',
'spam/eggs/.zarray',
'spam/eggs/0.0',
'spam/eggs/0.1',
'spam/eggs/1.0',
'spam/eggs/1.1']
In [19]: 'foo/bar/baz/.zarray' in store
Out[19]: True
In [20]: 'foo/bar/baz/.zarray' in list(store.keys())
Out[20]: False
xref https://github.com/zarr-developers/zarr-python/pull/456
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Upgrade of Converted Releases Fails · Issue #147 · helm ...
Hello everyone,. I was facing exact same issue after updating the helm version from 2 to 3. I was able to resolve this...
Read more >1365451 – ovirt-imageio-proxy service failed to start after ...
Cause: PKI (key/cert) was not generated for ovirt-imageio-proxy by engine-setup during upgrade from earlier version.
Read more >After installing some npm module globally shows a long list ...
How to fix it? Packages I have installed : eslint; gatsby-cli; gulp; heroku; node-gyp; npm-install-peers; yarn.
Read more >Release Notes
gpg: By default new keys expire after 2 years. gpg: New command –quick-set-expire to conveniently change the expiration date of keys.
Read more >Upgrade Guides | Nomad
ClientStatus has reached a terminal state ( complete , failed , or lost ). ... Downgrading to a previous version of the client...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Released.
Closing as the new
fsspec
release has fixed the originally posted issue:Thanks all!