issue_comments
4 rows where issue = 1718410975 and user = 35968931 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Unrecognized chunk manager dask - must be one of: [] · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1561504841 | https://github.com/pydata/xarray/issues/7856#issuecomment-1561504841 | https://api.github.com/repos/pydata/xarray/issues/7856 | IC_kwDOAMm_X85dEqxJ | TomNicholas 35968931 | 2023-05-24T16:16:41Z | 2023-05-24T16:26:15Z | MEMBER | Solution for those who just found this issue:Just re-install xarray. @Illviljan I brought this up in the xarray team call today and we decided that since this only affects people who have previously cloned the xarray repository, are using a development install, and then updated by pulling changes from main; this problem only affects maybe ~10-20 people worldwide, all of whom are developers who are equipped to quickly solve it. I'm going to add a note into the what's new entry for this version now - if you think we need to do more then let me know. EDIT: I added a note to whatsnew in https://github.com/pydata/xarray/commit/69445c62953958488a6b35fafd8b9cfd6c0374a5, and updated the release notes. |
{
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Unrecognized chunk manager dask - must be one of: [] 1718410975 | |
| 1556201913 | https://github.com/pydata/xarray/issues/7856#issuecomment-1556201913 | https://api.github.com/repos/pydata/xarray/issues/7856 | IC_kwDOAMm_X85cwcG5 | TomNicholas 35968931 | 2023-05-21T15:04:05Z | 2023-05-21T15:04:05Z | MEMBER | The only reason I didn't separate the chunkmanager entry points into local and other entry points was simplicity of code. I didn't realise that might make a difference when it came to whether or not you have to pip install - I assumed that adding a new type of entry point would require re-installing no matter how I implemented it. If that's not the case perhaps we should adjust it (and re-release). |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Unrecognized chunk manager dask - must be one of: [] 1718410975 | |
| 1556191719 | https://github.com/pydata/xarray/issues/7856#issuecomment-1556191719 | https://api.github.com/repos/pydata/xarray/issues/7856 | IC_kwDOAMm_X85cwZnn | TomNicholas 35968931 | 2023-05-21T14:19:27Z | 2023-05-21T14:35:22Z | MEMBER | Yes, but I'm wondering what functional difference is that making here? Have you tried doing the local pip install of the xarray dev version again? I.e. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Unrecognized chunk manager dask - must be one of: [] 1718410975 | |
| 1556182520 | https://github.com/pydata/xarray/issues/7856#issuecomment-1556182520 | https://api.github.com/repos/pydata/xarray/issues/7856 | IC_kwDOAMm_X85cwXX4 | TomNicholas 35968931 | 2023-05-21T13:36:22Z | 2023-05-21T13:36:22Z | MEMBER | Hmm, it's acting as if dask is not installed/importable. Any idea what's different about your setup vs the xarray CI? Yes daskmanager is also registered via a different entry point, but that should already be set up to happen by default. To see which chunk managers it can find you can call ```python from xarray.core.parallelcompat import list_chunkmanagers list_chunkmanagers() ``` I expect it will return an empty list in your case, but that's the code we should be trying to debug on your system. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Unrecognized chunk manager dask - must be one of: [] 1718410975 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] (
[html_url] TEXT,
[issue_url] TEXT,
[id] INTEGER PRIMARY KEY,
[node_id] TEXT,
[user] INTEGER REFERENCES [users]([id]),
[created_at] TEXT,
[updated_at] TEXT,
[author_association] TEXT,
[body] TEXT,
[reactions] TEXT,
[performed_via_github_app] TEXT,
[issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
ON [issue_comments] ([user]);
user 1