pull_requests
10 rows where user = 3698640
This data as json, CSV (advanced)
Suggested facets: base, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 160454420 | MDExOlB1bGxSZXF1ZXN0MTYwNDU0NDIw | 1802 | closed | 0 | Handle _FillValue in variable-length unicode string variables | delgadom 3698640 | - [x] Closes #1781 - [x] Tests added - [x] Tests passed - [x] Passes ``git diff upstream/master **/*py | flake8 --diff`` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API For testing - I could use some guidance. Not sure if it's worth creating a fixture set or something just for this issue. If so, would that go in test_backends? | 2017-12-28T23:13:54Z | 2018-01-11T23:56:57Z | 2018-01-11T23:56:57Z | a34cb49226d654ca1ce8f6bc628679dd158c0ae7 | 0 | 99873ca821c510a778eb92431e53205fc73abfa1 | 6eac8574f85623b18b59ba1ac9cf95e09c87980b | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/1802 | |||||
| 183232241 | MDExOlB1bGxSZXF1ZXN0MTgzMjMyMjQx | 2072 | closed | 0 | resolve #2071: 'bebroadcast' in ValueError msg | delgadom 3698640 | Simple spelling correction. Add space to end of line halfway through error message on line 682 to avoid 'bebroadcast' on string concatenation. - [x] Closes #2071 - ~~Tests added (for all bug fixes or enhancements)~~ - [ ] Tests passed (for all non-documentation changes) - ~~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)~~ | 2018-04-21T17:02:44Z | 2018-04-21T17:42:11Z | 2018-04-21T17:42:06Z | 2018-04-21T17:42:06Z | 99b457ce5859bd949cfea4671db5150c7297843a | 0 | 2557d2bf2b335f245b3746030cac5c0fdd575a2d | 093518207f4a3210ec692308da2b181a646115d6 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/2072 | ||||
| 791167521 | PR_kwDOAMm_X84vKEIh | 6034 | closed | 0 | fix grammatical typo in docs | delgadom 3698640 | very simple fix in the [broadcasting by dimension name](http://xarray.pydata.org/en/stable/user-guide/computation.html#broadcasting-by-dimension-name) docs: > ``DataArray`` objects ~~are~~ automatically align themselves [...] by dimension name instead of axis order. <!-- Feel free to remove check-list items aren't relevant to your change --> No workflow stages - this is a very minor docs fix. | 2021-11-29T23:48:10Z | 2021-11-30T00:33:07Z | 2021-11-30T00:33:07Z | 2021-11-30T00:33:07Z | f08672847abec18f46df75e2f620646d27fa41a2 | 0 | c68e191f41a4d67ab8f884f27e332773f270f1f9 | cc03589dadfef8d7ebcb95f7adc302895cf0fcbc | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6034 | ||||
| 799209108 | PR_kwDOAMm_X84vovaU | 6056 | closed | 0 | add set_options link to FAQ on metadata | delgadom 3698640 | If helpful - added a PR to adds a reference and link to `xr.set_options` in the section of the FAQ on "what is your approach to metadata?". I had to do a bit of digging to figure out what was meant by "there is a global flag" and thought others might find the direct ref useful. Relevant section: https://github.com/pydata/xarray/blob/main/doc/getting-started-guide/faq.rst#what-is-your-approach-to-metadata Current text: > An implication of this choice is that we do not propagate ``attrs`` through most operations unless explicitly flagged (some methods have a ``keep_attrs`` option, and there is a global flag for setting this to be always True or False) Proposed version: > An implication of this choice is that we do not propagate ``attrs`` through most operations unless explicitly flagged (some methods have a ``keep_attrs`` option, and there is a global flag, **accessible with [`xr.set_options`](http://xarray.pydata.org/en/stable/generated/xarray.set_options.html),** for setting this to be always True or False). Minor docs change only. No workflow steps needed. | 2021-12-09T21:04:21Z | 2021-12-15T06:21:18Z | 2021-12-09T21:39:45Z | 2021-12-09T21:39:45Z | 8073a7f84d57d06fd162840bbe827d9eab729156 | 0 | 599875b3db6f95e28e097a1e8086323e9e12fb67 | a9238339f55edac0f2efb4a231c8818c5539bd28 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6056 | ||||
| 811226240 | PR_kwDOAMm_X84wWlSA | 6122 | closed | 0 | assert ds errors in test_backends | delgadom 3698640 | Makes four changes to xarray/tests/test_backends.py::test_open_fsspec Previously, there were four inequality tests which will always pass regardless of whether the read was successful. `assert ds0 == ds2` will always evaluate to True if the datasets have at least one data variable. Instead, xr.testing.assert_equal should be used to test data variable equality. No workflow stages here - I just made the changes in the browser. Pretty simple patch that increases the effectiveness of existing tests - no changes to the xarray core code. | 2021-12-29T02:06:23Z | 2021-12-31T22:21:55Z | 2021-12-29T06:24:50Z | 2021-12-29T06:24:50Z | 92ac89f8a19368d1e6d18529997f68661e8e7784 | 0 | 12d508551beb7fbab636198577b2b142776e44f1 | 5d30f96e94de6922a01ad240dec65d2810e19ea0 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6122 | ||||
| 811230470 | PR_kwDOAMm_X84wWmUG | 6123 | closed | 0 | assert ds errors in test_dataset.py | delgadom 3698640 | a number of assert statements in test_dataset.py::test_clip make assertions which will never fail as long as there is at least one data_variable: ```python assert result.min(...) >= 0.5 ``` this evaluates to datasets with scalar True or False values in each data_variable; however, `ds.__bool__` returns true if `len(ds.data_vars) > 0`. related: https://github.com/pydata/xarray/pull/6122 No workflow stages here - I just made the changes in the browser. Pretty simple patch that increases the effectiveness of existing tests - no changes to the xarray core code. Let me know if you'd like me to implement any of the normal checks. | 2021-12-29T02:24:21Z | 2021-12-31T22:22:16Z | 2021-12-29T06:17:33Z | 2021-12-29T06:17:33Z | 6b11d6e80a2445f2e1e7c4d5895008f7c845c4d5 | 0 | 5f18b8803b905fa46c76f53c4b205eab8d3fdb13 | 5d30f96e94de6922a01ad240dec65d2810e19ea0 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6123 | ||||
| 811676415 | PR_kwDOAMm_X84wYTL_ | 6126 | closed | 0 | Deprecate bool(ds) | delgadom 3698640 | Issues a PendingDeprecationWarning on `Dataset.__bool__` - [x] Closes #6124 - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` <-- could definitely use a review | 2021-12-29T21:06:28Z | 2022-01-04T01:23:02Z | 2022-01-03T16:57:58Z | 2022-01-03T16:57:57Z | d6ee8caa84b27d4635ec3384b1a06ef4ddf2d998 | 0 | a9ba93b07f5ac68f443df61bc8087bb3a2fa8188 | f85ec665940291c9ac368f5e1b8a0711e2d9952d | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6126 | ||||
| 815158265 | PR_kwDOAMm_X84wllP5 | 6144 | closed | 0 | allow 1 non-null value in interpolate_na with method="nearest" | delgadom 3698640 | - [x] Closes #5994 - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` @Skealz's great issue (#5994) highlighted that DataArrays with a single non-null value raise an error if `DataArray.interpolate_na` is called with `method='nearest'`. Note that this does not occur for the default (`method='linear'`). In this PR: * Uses the "fast track" to quickly return *any* 1-D slices with a single non-null value in addition to the previous all-nan or no-nan fasttrack * Explicitly check this behavior for all 1-D interpolation methods using parametrized tests * consolidate other fast-track tests (`interpolate_allnans` and `interpolate_nonans`) into a single parameterized test For discussion: * This patch may break existing workflows if they rely on the current behavior, which errors for slices with only a single value | 2022-01-06T01:28:17Z | 2022-01-19T03:33:19Z | 2022-01-18T22:45:39Z | 2022-01-18T22:45:39Z | 8c0166cba410eb96c18efbc34d7d8af8e448df6e | 0 | 5a8736b8e0d7f06e839c3c09ef7fe9c5aadebd8c | 3666a6fb7226601002f408d56e81837ab69b8d4e | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6144 | ||||
| 905294187 | PR_kwDOAMm_X8419bFr | 6467 | closed | 0 | allow other and drop arguments in where (gh#6466) | delgadom 3698640 | - [x] Closes #6466 - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - not sure if this is warranted or if it should go in new features or bug fixes. happy to change/remove. | 2022-04-10T18:03:24Z | 2022-04-12T16:39:53Z | 2022-04-12T15:33:05Z | 2022-04-12T15:33:05Z | 1048df26386c5355469e08cecfed11696d30258f | 0 | ed6ea36ce057067a4bc802df2643fcfe4eac0591 | 0cd5285c56c5375da9f4d27836ec41eea4d069f3 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6467 | ||||
| 924320931 | PR_kwDOAMm_X843GASj | 6542 | closed | 0 | docs on specifying chunks in to_zarr encoding arg | delgadom 3698640 | The structure of the [`Dataset.to_zarr`](https://docs.xarray.dev/en/stable/generated/xarray.Dataset.to_zarr.html) encoding argument is particular to xarray (at least, it's not immediately obvious from the zarr docs how this argument gets parsed) and it took a bit of trial and error to figure out out the rules. Hoping this docs block is helpful to others! Documentation additions only (no workflow stages) | 2022-04-29T18:37:25Z | 2022-07-01T01:20:19Z | 2022-06-23T21:31:37Z | 2022-06-23T21:31:37Z | ec41d651a7fdc6190ce2823bf8f6067a40de612e | 0 | 31e4f175cb3b0c4a7059b44bbbfa6f1170b6a551 | abad670098a48ab8f876117c6b2cf3db8aff05dc | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/6542 |
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]);