issues: 1517330438
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1517330438 | I_kwDOAMm_X85acKAG | 7408 | Question: Feature request: test isolation and storage engine cache | 193170 | open | 0 | 4 | 2023-01-03T12:32:40Z | 2023-01-03T19:24:15Z | NONE | Is your feature request related to a problem?We have several tests that write and/or read test datasets using a common name, using open_zarr and to_zarr. Run individually, they work. However, when (e.g.) writing twice, we have errors as the zarr storage is trying to check to see which variables we may have updated, when in fact it is a new dataset. Describe the solution you'd likeWe would like a method to ensure there is no cached state between tests. Describe alternatives you've consideredIf there is an undocumented way to clear cached state, would be grateful for a pointer (and suggest inclusion in the documentation). Additional contextNo response |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/7408/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | issue |