pull_requests
12 rows where user = 3958036
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 349974653 | MDExOlB1bGxSZXF1ZXN0MzQ5OTc0NjUz | 3601 | closed | 0 | Fix contourf set under | johnomotani 3958036 | Copies the `cmap._rgba_bad`, `cmap._rgba_under`, and `cmap._rgba_over` values to `new_cmap`, in case they have been set to non-default values. Allows the user to customize plots more by using matplotlib methods on a `cmap` before passing as an argument to xarray's plotting methods. Previously these settings were overridden by defaults when creating the `cmap` actually used to make the plot. I'm not a fan of copying attributes one-by-one like this, but I guess this is an issue with matplotlib's API, unless there's a nicer way to convert a `cmap` to a discrete `cmap` than `mpl.colors.from_levels_and_colors()`. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #3590 - [x] Tests added - [x] Passes `black . && mypy . && flake8` | 2019-12-06T13:47:37Z | 2020-02-24T20:20:09Z | 2020-02-24T20:20:08Z | 2020-02-24T20:20:07Z | b14eea2f06bbcf1a02c4ae4cba9ed981aef69292 | 0 | 4fa6f8ecce70c427ca2c7c26fb3eb1c1d28a959b | f468a0676b2411a53e4bb94d67918092d06b50b8 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3601 | ||||
| 392111128 | MDExOlB1bGxSZXF1ZXN0MzkyMTExMTI4 | 3877 | closed | 0 | Control attrs of result in `merge()`, `concat()`, `combine_by_coords()` and `combine_nested()` | johnomotani 3958036 | `combine_attrs` argument for `merge()`, `concat()`, `combine_by_coords()` and `combine_nested()` controls what attributes the result is given. Defaults maintain the current behaviour. Possible values (named following `compat` arguments) are: - 'drop': empty attrs on returned Dataset. - 'identical': all attrs must be the same on every object. - 'no_conflicts': attrs from all objects are combined, any that have the same name must also have the same value. - 'override': skip comparing and copy attrs from the first dataset to the result. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #3865 - [x] Tests added - [x] Passes `isort -rc . && black . && mypy . && flake8` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2020-03-23T01:32:59Z | 2020-04-05T20:44:47Z | 2020-03-24T20:40:18Z | 2020-03-24T20:40:18Z | d8bb6204dc6a4bacdfca25b02ba62bb7f1bb5795 | 0 | e4158156e2b7800627652c951917f83b1deb58d4 | c707b337a0f75224ee3b3e3b65a08da792df2fa6 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3877 | ||||
| 393256581 | MDExOlB1bGxSZXF1ZXN0MzkzMjU2NTgx | 3887 | closed | 0 | Rename ordered_dict_intersection -> compat_dict_intersection | johnomotani 3958036 | `xarray` does not use `OrderedDicts` any more, so name did not make sense. As suggested here https://github.com/pydata/xarray/pull/3877#discussion_r396620551. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Test~~s~~ ~~added~~ updated - [x] Passes `isort -rc . && black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` | 2020-03-24T21:08:26Z | 2020-03-24T22:59:07Z | 2020-03-24T22:59:07Z | 2020-03-24T22:59:07Z | 009aa66620b3437cf0de675013fa7d1ff231963c | 0 | fe31e99dca793027f6ef045c31ce5a730416ccf8 | d8bb6204dc6a4bacdfca25b02ba62bb7f1bb5795 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3887 | ||||
| 396639636 | MDExOlB1bGxSZXF1ZXN0Mzk2NjM5NjM2 | 3923 | closed | 0 | Add missing_dims argument allowing isel() to ignore missing dimensions | johnomotani 3958036 | <!-- Feel free to remove check-list items aren't relevant to your change --> Note: only added to `DataArray.isel()` and `Variable.isel()`. A `Dataset` should include all dimensions, so presumably it should always be an error to pass a non-existent dimension when slicing a `Dataset`? - [x] Closes #3866 - [x] Tests added - [x] Passes `isort -rc . && black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2020-03-31T22:19:54Z | 2020-04-03T19:47:08Z | 2020-04-03T19:47:08Z | 2020-04-03T19:47:08Z | 9b5140e0711247c373987b56726282140b406d7f | 0 | f98bc1dd59d336454d15844a80d0d3bf3c6cf64f | b3bafeefbd6e6d70bce505ae1f0d9d5a2b015089 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3923 | ||||
| 399200887 | MDExOlB1bGxSZXF1ZXN0Mzk5MjAwODg3 | 3936 | closed | 0 | Support multiple dimensions in DataArray.argmin() and DataArray.argmax() methods | johnomotani 3958036 | These return dicts of the indices of the minimum or maximum of a DataArray over several dimensions. Inspired by @fujiisoup's work in #1469. With #3871, replaces #1469. Provides a simpler solution to #3160. Implemented so that ``` da.isel(da.argmin(list_of_dim)) == da.min(list_of_dim) da.isel(da.argmax(list_of_dim)) == da.max(list_of_dim) ``` <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #1469 - [x] Tests added - [x] Passes `isort -rc . && black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2020-04-05T18:52:52Z | 2020-06-29T20:22:49Z | 2020-06-29T19:36:26Z | 2020-06-29T19:36:25Z | bdcfab524ef1c852abe6dabcfabc7292f058fddc | 0 | 4aca9d9fcf5d2fbd4cecd951f5a99791ad5313ea | 65ca92a5c0a4143d00dd7a822bcb1d49738717f1 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/3936 | ||||
| 411421823 | MDExOlB1bGxSZXF1ZXN0NDExNDIxODIz | 4017 | closed | 0 | Combining attrs of member DataArrays of Datasets | johnomotani 3958036 | While looking at #4009, I noticed that the `combine_attrs` kwarg to `concat` or `merge` only affects the global attrs of the `Dataset`, not the attrs of `DataArray` or `Variable` members of the `Dataset`s being combined. I think this is a bug. So far this PR adds tests that reproduce the issue in #4009, and the issue described above. Fixing should be fairly simple: for #4009 pass `combine_attrs="drop"` to `combine_by_coords` and `combine_nested` in `open_mfdataset`; for this issue insert the `combine_attrs` handling in an appropriate place - possibly in `merge.unique_variable`. I'll update with fixes when I get a chance. - [ ] Closes #4009 - [x] Tests added - [ ] Passes `isort -rc . && black . && mypy . && flake8` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2020-04-30T12:23:10Z | 2021-05-05T16:37:25Z | 2021-05-05T16:37:25Z | 08dc29d52e8b2a205cf7f86a179c862027cdd313 | 0 | 9ae7d97b6f89e6449faf8e8e0d3957450bc19927 | 7bf9df9d75c40bcbf2dd28c47204529a76561a3f | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/4017 | |||||
| 439098573 | MDExOlB1bGxSZXF1ZXN0NDM5MDk4NTcz | 4173 | closed | 0 | Fix 4009 | johnomotani 3958036 | Don't know if/when I'll have time to finish #4017, so pulling out the fix for #4009 into a separate PR here that is ready to merge. - [x] Closes #4009 - [x] Tests added - [x] Passes `isort -rc . && black . && mypy . && flake8` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2020-06-24T09:59:28Z | 2020-06-24T18:22:20Z | 2020-06-24T18:22:19Z | 2020-06-24T18:22:19Z | 24d755d59421fd0eaf22ad109408275d2bfb8216 | 0 | 4faa2f9677f89ce80e73ec98f2e3f39d08947997 | 2a8cd3b0545851cff2773d493e30d5c84aa1c4db | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/4173 | ||||
| 461443771 | MDExOlB1bGxSZXF1ZXN0NDYxNDQzNzcx | 4298 | closed | 0 | Fix docstring for missing_dims argument to isel methods | johnomotani 3958036 | Incorrect value "exception" was given in the description of `missing_dims` argument - "exception" was renamed to "raise". - [x] Passes `isort . && black . && mypy . && flake8` | 2020-08-01T21:40:27Z | 2020-08-03T20:23:29Z | 2020-08-03T20:23:28Z | 2020-08-03T20:23:28Z | 8cea79823e729e19f79d629fc3ba7c7380bc9342 | 0 | b31a75d190a41bb359253595b3cc5f6c84c756bb | 9058114f70d07ef04654d1d60718442d0555b84b | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/4298 | ||||
| 585774268 | MDExOlB1bGxSZXF1ZXN0NTg1Nzc0MjY4 | 5003 | closed | 0 | Add Dataset.plot.streamplot() method | johnomotani 3958036 | Since @dcherian added Quiver plots in #4407, it's fairly simple to extend the functionality to `streamplot()`. For example (copying from @dcherian's unit test setup) ``` import xarray as xr from matplotlib import pyplot as plt das = [ xr.DataArray( np.random.randn(3, 3), dims=["x", "y"], coords=[range(k) for k in [3, 3]], ) for _ in [1, 2] ] ds = xr.Dataset({"u": das[0], "v": das[1]}) ds["mag"] = np.hypot(ds.u, ds.v) ds.plot.streamplot(x="x",y="y",u="u",v="v", hue="mag") plt.show() ```  - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] New functions/methods are listed in `api.rst` | 2021-03-05T17:41:49Z | 2021-03-30T16:41:08Z | 2021-03-30T16:41:07Z | 2021-03-30T16:41:07Z | ba47216ec1cd2f170fd85a10f232be7bf3ecc578 | 0 | e49fd0ec36aff8366a6970342a88a3175e769d8c | 2bbac154ddacd6d6ec989b040130cd9afb8dc0a1 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5003 | ||||
| 606230215 | MDExOlB1bGxSZXF1ZXN0NjA2MjMwMjE1 | 5099 | closed | 0 | Use broadcast_like for 2d plot coordinates | johnomotani 3958036 | Use broadcast_like if either `x` or `y` inputs are 2d to ensure that both have dimensions in the same order as the DataArray being plotted. Convert to numpy arrays after possibly using broadcast_like. Simplifies code, and fixes #5097 (bug when dimensions have the same size). @dcherian > IIRC the "resolving intervals" section later will break and is somewhat annoying to fix. This is why the current ugly code exists. This change seems to 'just work', and unit tests pass. Is there some extra check that needs doing to make sure "resolving intervals" is behaving correctly? I can't think of a unit test that would have caught #5097, since even when the bug happens, a plot is produced without errors or warnings. If anyone has an idea, suggestions/pushes welcome! <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #5097 - [ ] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2021-03-31T19:34:32Z | 2021-04-22T07:16:17Z | 2021-04-22T07:16:17Z | 2021-04-22T07:16:17Z | b2351cbe3f3e92f0e242312dae5791fc83a4467a | 0 | 8a331c39831085c7f93cef0e760b204dde384370 | ddc352faa6de91f266a1749773d08ae8d6f09683 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5099 | ||||
| 606502308 | MDExOlB1bGxSZXF1ZXN0NjA2NTAyMzA4 | 5101 | closed | 0 | Surface plots | johnomotani 3958036 | `.plot.surface()` method that wraps `matplotlib`'s `plot_surface()` method from the 3d toolkit. * works with facet grids * disables all the automatic color-map, etc. because it doesn't necessarily make sense for surface plots - the default (in matplotlib, and as implemented now) is not to color the surface. xarray's auto-selection stuff would interfere with `plot_surface()`'s kwargs. I'm not sure if there's somewhere good to note the new `surface()` method in the docs to make it more discoverable? Maybe in one of the examples? <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #5084 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] New functions/methods are listed in `api.rst` | 2021-03-31T22:58:20Z | 2021-05-03T13:05:59Z | 2021-05-03T13:05:02Z | 2021-05-03T13:05:02Z | 9f118624e7924c80fc305f351fa9621d2b58514c | 0 | cf9c49ab921b484acaf964db048ce496e84cc845 | 3391fec79da03361b13c9e113999740908152f86 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5101 | ||||
| 614809585 | MDExOlB1bGxSZXF1ZXN0NjE0ODA5NTg1 | 5153 | closed | 0 | cumulative_integrate() method | johnomotani 3958036 | Provides the functionality of `scipy.integrate.cumulative_trapezoid`. <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2021-04-13T22:53:58Z | 2021-05-02T10:34:23Z | 2021-05-01T20:01:31Z | 2021-05-01T20:01:31Z | 04acabb50bea9f48224464850ae5a918e57406e5 | 0 | 668c21cdb9eafea7af5472d163e1380301036d39 | 01b6cc76c6b7c77f2f93fc1766eb76f851529b5d | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5153 |
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]);