pull_requests
5 rows where user = 950575
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date), merged_at (date)
id ▼ | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
68785473 | MDExOlB1bGxSZXF1ZXN0Njg3ODU0NzM= | 842 | closed | 0 | Fix #665 decode_cf_timedelta 2D | ocefpaf 950575 | Long time listener first time caller :wink: I am not 100% about this PR though. I think that there are cases when we need the actual data rather than the `timedelta`. In [this](http://nbviewer.jupyter.org/gist/ocefpaf/6ed33fb35fe526f677e215b3fb304847) notebook we have wave period (`'mper'`) that should be _seconds_ ranging `0-30` and not those big numpy timedelta numbers. I know that I can get that behavior with `decode_times=True` when opening the dataset, but then the `time` coordinate get decoded as well. (Maybe I am way off and there is a way to do this.) | 2016-05-03T22:26:34Z | 2016-05-14T00:36:12Z | 2016-05-04T17:11:59Z | 2016-05-04T17:11:59Z | b25d145b092e1f0ae6555e9ac2103a7afb838592 | 0 | 888e6c25d462fdd89a397c127a409775a5cc0fcf | ecc442054f05c5b500f3b58d3c9dacce75a9de36 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/842 | ||||
68940102 | MDExOlB1bGxSZXF1ZXN0Njg5NDAxMDI= | 844 | closed | 0 | Add a filter_by_attrs method to Dataset | ocefpaf 950575 | This PR adds the `get_variables_by_attributes` method similar to the one in `netCDF4-python` and netcdf-java libraries. It is useful to filter a Dataset to known/expected attributes. @shoyer I don't really like the docs nor the change log entry I created. I will look at them again tomorrow with fresh eyes to see if I can improve them. Closes https://github.com/pydata/xarray/issues/567 xref: https://github.com/pydata/xarray/issues/567#issuecomment-216947679 | 2016-05-04T22:08:07Z | 2016-08-03T18:09:04Z | 2016-08-03T17:53:42Z | 2016-08-03T17:53:42Z | d5d3e1926f748f67dee7e38f549a332ec658126e | 0 | 270b6a6bce8002ba9771b5e9d781b348cd7a241a | 884b247742af2480e269bb54c9102f08c867fdaa | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/844 | ||||
80008855 | MDExOlB1bGxSZXF1ZXN0ODAwMDg4NTU= | 940 | closed | 0 | Don't convert time data to timedelta by default | ocefpaf 950575 | I don't really like this PR... Too much change for a simple thing. I may try again soon. Closes #843 | 2016-08-04T02:19:36Z | 2016-08-11T16:15:07Z | 2016-08-11T16:15:05Z | 90496985853162d4a54d95d0bf6350b60bf3aaf8 | 0 | 98ed32ec9d81036763ff498c8f1ab643150115b9 | 9d8bb1325b2d5992574622273bc379bb51fa663c | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/940 | |||||
80995741 | MDExOlB1bGxSZXF1ZXN0ODA5OTU3NDE= | 962 | closed | 0 | Two minor docs fixes | ocefpaf 950575 | ~~I am not sure how to build the docs locally (yet) to test these changes.~~ --- Edit: I found the env file in the `docs` and tested the docs locally. These changes looks fine in the HTML. | 2016-08-11T17:18:28Z | 2016-08-11T21:41:08Z | 2016-08-11T21:40:46Z | 2016-08-11T21:40:46Z | 4e2be70bc224a574cb6d4cf7f86c6411b7e18414 | 0 | 3dd00616fac866be4a2fc23a23729c92f4a9e8ac | 9fe2aff89494f0f268dc98bcb549246837d0ae89 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/962 | ||||
185989865 | MDExOlB1bGxSZXF1ZXN0MTg1OTg5ODY1 | 2105 | closed | 0 | Deprecate decode timedelta | ocefpaf 950575 | - [X] Closes #1621 (remove if there is no corresponding issue, which should only be the case for minor changes) - [X] Tests added (for all bug fixes or enhancements) - [X] Tests passed (for all non-documentation changes) - [X] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later) I'll add tests, docs, and the whats-new entry later if I'm on the right path here. xref.: #843, #940, and #2085 See http://nbviewer.jupyter.org/gist/ocefpaf/e736c07faf3d4c9361ecf546a692c2cd | 2018-05-04T13:50:33Z | 2019-05-17T13:48:30Z | 2019-05-17T13:48:30Z | 624a291d6360fc9cde3e1306129f2791a53af97b | 0 | 39eb727e0f220a28f51f26170e225804b26081e9 | bb87a9441d22b390e069d0fde58f297a054fd98a | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/2105 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [pull_requests] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [state] TEXT, [locked] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [body] TEXT, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [merged_at] TEXT, [merge_commit_sha] TEXT, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [draft] INTEGER, [head] TEXT, [base] TEXT, [author_association] TEXT, [auto_merge] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [url] TEXT, [merged_by] INTEGER REFERENCES [users]([id]) ); CREATE INDEX [idx_pull_requests_merged_by] ON [pull_requests] ([merged_by]); CREATE INDEX [idx_pull_requests_repo] ON [pull_requests] ([repo]); CREATE INDEX [idx_pull_requests_milestone] ON [pull_requests] ([milestone]); CREATE INDEX [idx_pull_requests_assignee] ON [pull_requests] ([assignee]); CREATE INDEX [idx_pull_requests_user] ON [pull_requests] ([user]);