issue_comments
4 rows where user = 2049051 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- brews · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue | 
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1057653294 | https://github.com/pydata/xarray/issues/6176#issuecomment-1057653294 | https://api.github.com/repos/pydata/xarray/issues/6176 | IC_kwDOAMm_X84_CoIu | brews 2049051 | 2022-03-03T04:24:14Z | 2022-03-03T04:24:14Z | CONTRIBUTOR | Using semver can be handy to signal breaking changes. Any thoughts on how xarray will handle breaking changes with calver? Any release can break, or during select periods, after a timeout, etc.? | {
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
} | Xarray versioning to switch to CalVer 1108564253 | |
| 223775868 | https://github.com/pydata/xarray/issues/869#issuecomment-223775868 | https://api.github.com/repos/pydata/xarray/issues/869 | MDEyOklzc3VlQ29tbWVudDIyMzc3NTg2OA== | brews 2049051 | 2016-06-04T20:13:14Z | 2016-06-04T20:13:32Z | CONTRIBUTOR | Wow. How did I not know about conda-forge? This solve all problems. They even have a windspharm for py3! I owe you a beer @fmaussion! Thanks again. | {
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
} | open netCDF gives 'time' dim with 1969 change in timezone 158518147 | |
| 223774592 | https://github.com/pydata/xarray/issues/869#issuecomment-223774592 | https://api.github.com/repos/pydata/xarray/issues/869 | MDEyOklzc3VlQ29tbWVudDIyMzc3NDU5Mg== | brews 2049051 | 2016-06-04T19:47:39Z | 2016-06-04T19:47:39Z | CONTRIBUTOR | @fmaussion Yes this solves the problem! Closed. Now the problem is that my Basemap and Cartopy 0.14 in conda currently depend on numpy 1.10*. This puts me in Dependency Hell. Does anyone happen to have a channel for these (or at least Cartopy 0.14) that will work with numpy 1.11*? | {
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
} | open netCDF gives 'time' dim with 1969 change in timezone 158518147 | |
| 219923130 | https://github.com/pydata/xarray/issues/789#issuecomment-219923130 | https://api.github.com/repos/pydata/xarray/issues/789 | MDEyOklzc3VlQ29tbWVudDIxOTkyMzEzMA== | brews 2049051 | 2016-05-18T04:37:03Z | 2016-05-18T04:37:03Z | CONTRIBUTOR | Just curious, has anyone tried to open an issue in pandas for this? | {
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
} | Time limitation (between years 1678 and 2262) restrictive to climate community 139956689 | 
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]);
issue 3