pull_requests
5 rows where user = 23625371
This data as json, CSV (advanced)
Suggested facets: draft, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 501996625 | MDExOlB1bGxSZXF1ZXN0NTAxOTk2NjI1 | 4506 | closed | 0 | Decoding year 1 time | znicholls 23625371 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #4422 - [x] Tests added - [x] Passes `isort . && black . && mypy . && flake8` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] Decision on whether to raise a warning or not when padding is performed | 2020-10-13T05:38:58Z | 2020-10-26T10:15:13Z | 2020-10-26T09:50:18Z | 2020-10-26T09:50:18Z | adc55ac4d2883e0c6647f3983c3322ca2c690514 | 0 | 7ef15fe08837e4a21ab41fee14b33032bc28d27c | 1597e3a91eaf96626725987d23bbda2a80d2bae7 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/4506 | ||||
| 595205842 | MDExOlB1bGxSZXF1ZXN0NTk1MjA1ODQy | 5050 | closed | 0 | BUG: Future time decoding | znicholls 23625371 | - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` This identifies (and hopefully soon fixes) an issue with decoding times that are way into the future. Without re-introducing a change made in #4684, the test fails (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136824754). With the change put back in, the test passes (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136892412). @spencerkclark can I ask for your help on this one please? It seems that the removal in #4684 caused this case (which wasn't tested) to break in v0.17 and it's unclear to me where the fix should be (I'm guessing pandas from the discussions in #4684...). | 2021-03-18T04:31:31Z | 2021-03-18T14:04:09Z | 2021-03-18T14:03:59Z | 2021-03-18T14:03:59Z | fbd48d4307502f7dbe8afa37b84df59e74407820 | 0 | 5c75f66ae670c06131a2bc3763d5bf13453b156f | a6f51c680f4e4c3ed5101b9c1111f0b94d28a781 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5050 | ||||
| 631050680 | MDExOlB1bGxSZXF1ZXN0NjMxMDUwNjgw | 5264 | closed | 0 | Numpy string coding | znicholls 23625371 | Fixes handling of numpy string types in coding - [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-05-06T02:35:55Z | 2021-12-30T23:40:28Z | 2021-12-30T23:39:55Z | 2021-12-30T23:39:55Z | f75c3be583db377e1efe0fb90ece11e79bb4297e | 0 | e450cd2db0a9445d4a915fb0144ee6c5a234a65d | f85ec665940291c9ac368f5e1b8a0711e2d9952d | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5264 | ||||
| 727340089 | MDExOlB1bGxSZXF1ZXN0NzI3MzQwMDg5 | 5767 | closed | 0 | Open mfdataset with long time axis | znicholls 23625371 | When `open_mfdataset` is used on files which have a long time axis, sometimes one time axis is cast to `pd.Timestamp` whilst the other is cast to `cftime.datetime`. In such a case, xarray thinks the time co-ordinates are different and won't load and combine the files automatically. This PR identifies this issue. I've also put in a hack solution but there must be a better way to handle this edge case. - [x] Tests added - [ ] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` | 2021-09-05T05:18:14Z | 2021-09-08T01:06:31Z | 2021-09-08T01:06:31Z | a0709c341cecf324ff88b55c354945a54cb60d7e | 1 | 548644aad9bd289258d666a98e668b16a7e45cc6 | 6a29380008dcd790f9adfbc290affcb767c913b2 | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5767 | |||||
| 729093736 | MDExOlB1bGxSZXF1ZXN0NzI5MDkzNzM2 | 5776 | closed | 0 | Update combine error | znicholls 23625371 | The update points users in the direction of the `use_cftime` argument, which can solve issues where calendars are decoded into different time classes (see also the discussion in #5767) - [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-09-08T01:05:38Z | 2021-09-27T15:14:49Z | 2021-09-27T14:43:15Z | 2021-09-27T14:43:15Z | 19ab40ee401187e8a4b255d1082beb4f36b7ab24 | 0 | ec2657bfc1a426aa3559243b02ecf48de6673506 | ed94afbd5398e208762bce3341ab7fb0fbc1977d | CONTRIBUTOR | xarray 13221727 | https://github.com/pydata/xarray/pull/5776 |
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]);