pull_requests
2 rows where user = 5948670
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
341790366 | MDExOlB1bGxSZXF1ZXN0MzQxNzkwMzY2 | 3544 | open | 0 | Open dataset cf options conflict solving | MeraX 5948670 | It took some time*, but here is a suggestion to solve option conflicts in xarray.open_dataset(). If any of the options `mask_and_scale`, `decode_times`, `concat_characters`, or `decode_coords` is manually set and contradicts the manually set choice of `decode_cf` a `ValueError` will be raised. This commit requires to change some option default values of open_dataset() parameters from `True` to `None`. I hope this is acceptable. - [x] Closes #3020 - [x] Tests added - [x] Passes `black . && flake8` (`mypy`passes in principle, but backends/api.py:21 has an unrelated error) - [x] Fully documented, - [ ] including `whats-new.rst` for all changes and `api.rst` for new API What do you think? Do I have to add something to `whats-new.rst` and `api.rst`? PS: (*) This is my first PR of this kind and I wanted to build it in a proper testing environment, but I had to set this up first. | 2019-11-16T20:43:39Z | 2022-06-09T14:50:17Z | 6a671eb4f37fe06cc0cc1bf9dccb36fb7b28b1a5 | 0 | 04f926e40c62ea957a23946817d893dcf3ff52ce | d1e4164f3961d7bbb3eb79037e96cae14f7182f8 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3544 | ||||||
374335374 | MDExOlB1bGxSZXF1ZXN0Mzc0MzM1Mzc0 | 3766 | closed | 0 | Allow plotting bool data | MeraX 5948670 | as @dcherian said: > matplotlib can plot `bool` values so we should add that to the check in `_ensure_plottable`. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #3722 | 2020-02-12T14:22:11Z | 2020-04-03T23:19:23Z | 2020-04-03T23:19:23Z | 2020-04-03T23:19:23Z | 0181aa5741ce376a9dad45750754f3cf1ed41dde | 0 | 4be5a1541582c57ef14e00ca9fa95a69f496da2b | 1416d5ae475c0875e7a5d76fa4a8278838958162 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3766 |
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]);