issue_comments
2 rows where issue = 268725471 and user = 1956032 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Decoding time according to CF conventions raises error if a NaN is found · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 340008407 | https://github.com/pydata/xarray/issues/1662#issuecomment-340008407 | https://api.github.com/repos/pydata/xarray/issues/1662 | MDEyOklzc3VlQ29tbWVudDM0MDAwODQwNw== | gmaze 1956032 | 2017-10-27T15:44:11Z | 2017-10-27T15:44:11Z | CONTRIBUTOR | Note that if the xarray decode_cf is given a NaT, in a datetime64, it works: ```python attrs = {'units': 'days since 1950-01-01 00:00:00 UTC'} # Classic Argo data Julian Day reference jd = [24658.46875, 24658.46366898, 24658.47256944, np.NaN] # Sample def dirtyfixNaNjd(ref,day): td = pd.NaT if not np.isnan(day): td = pd.Timedelta(days=day) return pd.Timestamp(ref) + td jd = [dirtyfixNaNjd('1950-01-01',day) for day in jd]
print jd
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Decoding time according to CF conventions raises error if a NaN is found 268725471 | |
| 339991529 | https://github.com/pydata/xarray/issues/1662#issuecomment-339991529 | https://api.github.com/repos/pydata/xarray/issues/1662 | MDEyOklzc3VlQ29tbWVudDMzOTk5MTUyOQ== | gmaze 1956032 | 2017-10-27T14:42:56Z | 2017-10-27T14:42:56Z | CONTRIBUTOR | Hi Ryan, never been very far, following/promoting xarray around here, and congrats for Pangeo ! Ok, I get the datatype being wrong, but about the issue from pandas TimedeltaIndex: Does this means that a quick/dirty fix should be to decode value by value rather than on a vector ? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Decoding time according to CF conventions raises error if a NaN is found 268725471 |
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