issue_comments
2 rows where issue = 327089588 and user = 6063709 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Adding resample functionality to CFTimeIndex · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 399320016 | https://github.com/pydata/xarray/issues/2191#issuecomment-399320016 | https://api.github.com/repos/pydata/xarray/issues/2191 | MDEyOklzc3VlQ29tbWVudDM5OTMyMDAxNg== | aidanheerdegen 6063709 | 2018-06-22T04:51:16Z | 2018-06-22T04:51:16Z | CONTRIBUTOR | Does this need it's own issue then, so it doesn't get lost? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding resample functionality to CFTimeIndex 327089588 | |
| 399315302 | https://github.com/pydata/xarray/issues/2191#issuecomment-399315302 | https://api.github.com/repos/pydata/xarray/issues/2191 | MDEyOklzc3VlQ29tbWVudDM5OTMxNTMwMg== | aidanheerdegen 6063709 | 2018-06-22T04:12:11Z | 2018-06-22T04:45:03Z | CONTRIBUTOR | I'm not sure if my issue belongs in here, but I didn't want to create a new Issue (there are already 455 open ones). I am experimenting with the new I am trying to ```python da.time.get_index('time').shift(1,'D') NotImplementedError Traceback (most recent call last) <ipython-input-71-db48b2fbb340> in <module>() ----> 1 da.time.get_index('time').shift(1,'D') /g/data3/hh5/public/apps/miniconda3/envs/analysis27-18.04/lib/python2.7/site-packages/pandas/core/indexes/base.pyc in shift(self, periods, freq) 2627 """ 2628 raise NotImplementedError("Not supported for type %s" % -> 2629 type(self).name) 2630 2631 def argsort(self, args, *kwargs): NotImplementedError: Not supported for type CFTimeIndex ``` Is this not implemented because it might require resampling? I ask because this works:
I guess I am asking, if I want to shift a time index is the best (only?) way currently is to loop over all the individual elements of the index and add a time offset to each? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding resample functionality to CFTimeIndex 327089588 |
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