issue_comments
3 rows where issue = 722437965 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- encode_cf_datetime: reference_date can not be "2000-02-30" · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
754715890 | https://github.com/pydata/xarray/issues/4514#issuecomment-754715890 | https://api.github.com/repos/pydata/xarray/issues/4514 | MDEyOklzc3VlQ29tbWVudDc1NDcxNTg5MA== | mathause 10194086 | 2021-01-05T15:42:37Z | 2021-01-05T15:42:37Z | MEMBER | I can confirm that this works now. So I close this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
encode_cf_datetime: reference_date can not be "2000-02-30" 722437965 | |
709672708 | https://github.com/pydata/xarray/issues/4514#issuecomment-709672708 | https://api.github.com/repos/pydata/xarray/issues/4514 | MDEyOklzc3VlQ29tbWVudDcwOTY3MjcwOA== | spencerkclark 6628425 | 2020-10-16T01:18:38Z | 2020-10-16T01:18:56Z | MEMBER | Thanks @mathause -- interestingly I happened to try this example out with a branch that's soon to be merged in ``` In [1]: import xarray as xr In [2]: import cftime In [3]: import numpy as np In [4]: time = xr.cftime_range("2000-02-30", "2001-01-01", freq="3M", calendar="360_day") In [5]: dates = np.asarray(time) In [6]: reference_date = xr.coding.times.infer_datetime_units(dates) In [7]: xr.coding.times.encode_cf_datetime(time) Out[7]: (array([ 0, 90, 180, 270]), 'days since 2000-02-30 00:00:00.000000', '360_day') ``` As a general point I think we should strive to be able to handle reference dates that might not be valid in all calendars (they might occur in the wild). Would we be ok labeling this as an upstream issue? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
encode_cf_datetime: reference_date can not be "2000-02-30" 722437965 | |
709426866 | https://github.com/pydata/xarray/issues/4514#issuecomment-709426866 | https://api.github.com/repos/pydata/xarray/issues/4514 | MDEyOklzc3VlQ29tbWVudDcwOTQyNjg2Ng== | dcherian 2448579 | 2020-10-15T16:03:42Z | 2020-10-15T16:03:42Z | MEMBER | The fix looks nice, except we should not rely on |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
encode_cf_datetime: reference_date can not be "2000-02-30" 722437965 |
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 3