issues
3 rows where milestone = 3008859 and type = "pull" sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: user, comments, created_at (date), updated_at (date), closed_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
281423161 | MDExOlB1bGxSZXF1ZXN0MTU3ODU2NTEx | 1776 | [WIP] Fix pydap array wrapper | fujiisoup 6815844 | closed | 0 | 0.10.3 3008859 | 6 | 2017-12-12T15:22:07Z | 2019-09-25T15:44:19Z | 2018-01-09T01:48:13Z | MEMBER | 0 | pydata/xarray/pulls/1776 |
I am trying to fix #1775, but tests are still failing. Any help would be appreciated. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1776/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | ||||
283388962 | MDExOlB1bGxSZXF1ZXN0MTU5Mjg2OTk0 | 1793 | fix distributed writes | jhamman 2443309 | closed | 0 | 0.10.3 3008859 | 35 | 2017-12-19T22:24:41Z | 2018-03-13T15:32:54Z | 2018-03-10T15:43:18Z | MEMBER | 0 | pydata/xarray/pulls/1793 |
Right now, I've just modified the dask distributed integration tests so we can all see the failing tests. I'm happy to push this further but I thought I'd see if either @shoyer or @mrocklin have an idea where to start? |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1793/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | ||||
284607311 | MDExOlB1bGxSZXF1ZXN0MTYwMTY1NjI3 | 1800 | WIP: Performance improvements for zarr backend | jhamman 2443309 | closed | 0 | 0.10.3 3008859 | 6 | 2017-12-26T20:37:45Z | 2018-01-24T14:56:57Z | 2018-01-24T14:55:52Z | MEMBER | 0 | pydata/xarray/pulls/1800 |
This is building on top of #1799. Based on the suggestion from @alimanfoo in https://github.com/pangeo-data/pangeo/issues/48#issuecomment-353807691, I have reworked the handling of attributes in the zarr backend. There is more to do here, particularly in the cc @rabernat, @mrocklin and @alimanfoo |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1800/reactions", "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);