home / github

Menu
  • Search all tables
  • GraphQL API

pull_requests

Table actions
  • GraphQL API for pull_requests

4 rows where user = 17169544

✎ View and edit SQL

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
273699653 MDExOlB1bGxSZXF1ZXN0MjczNjk5NjUz 2920 closed 0 [WIP] Custom fill value for reindex, align, and merge operations zdgriffith 17169544 This PR adds an optional `fill_value` parameter for the following functions/methods: ``` xarray.core.alignment.align() xarray.core.alignment.deep_align() xarray.core.dataset.reindex() xarray.core.dataset.reindex_like() xarray.core.dataset.merge() xarray.core.dataarray.DataArray.reindex() xarray.core.dataarray.DataArray.reindex_like() xarray.core.merge.merge_coords() xarray.core.merge.merge_core() xarray.core.merge.merge() xarray.core.merge.dataset_merge_method() ``` The value given to `fill_value` is used to fill missing values in the new object after the operation. By default `fill_value` is NaN. - [x] Closes #2876 - [x] Tests added - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API 2019-04-25T22:08:09Z 2019-05-05T20:31:58Z 2019-05-05T00:20:55Z 2019-05-05T00:20:55Z 5aaa6547cd14a713f89dfc7c22643d86fce87916     0 4fda518475297bc71c33c53e85e5a8972a40c99d 6d93a95d05bdbfc33fff24064f67d29dd891ab58 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/2920  
279156025 MDExOlB1bGxSZXF1ZXN0Mjc5MTU2MDI1 2964 closed 0 Add fill_value for concat and auto_combine zdgriffith 17169544 This PR adds the optional `fill_value` parameter to `concat()` and `auto_combine()` in `xarray.core.combine`, plus the associated underlying functions in the module. This builds on the previous PR #2920 in addressing issue #2876, and gives users the option to avoid type-changing to `float` for arrays with missing values when using these functions as discussed in issue #2870. - [x] Closes #2870 - [x] Tests added - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API 2019-05-15T15:40:48Z 2019-05-27T00:21:02Z 2019-05-27T00:20:55Z 2019-05-27T00:20:55Z 6dc8b60849fab48f24494859c15a42f078025be6     0 72875311626165d9ce68463da7edd1cc6bd9f655 4e778f0421a31f26b06e504271e122a9bd0ff1a3 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/2964  
297330107 MDExOlB1bGxSZXF1ZXN0Mjk3MzMwMTA3 3110 closed 0 Change name of testing conda environment zdgriffith 17169544 This PR changes the test environment name from `test_env` to `xarray-tests` for clarity and to be consistent with the documentation environment name (`xarray-docs`). - [x] Closes #3107 2019-07-13T16:41:09Z 2019-07-13T17:12:30Z 2019-07-13T17:11:52Z 2019-07-13T17:11:51Z b3ba4ba5f9508e4b601d9cf5dbcd9024993adf37     0 2723bdcecef3ee31a86e4b0428c05b30e6461867 6586c26af6e55279efe646188b39ee1caf86db23 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/3110  
297346763 MDExOlB1bGxSZXF1ZXN0Mjk3MzQ2NzYz 3113 closed 0 [DOC] Be more explicit about netCDF groups and xarray.Dataset relationship. zdgriffith 17169544 This PR is related to the discussion in #2916. In https://xarray.pydata.org/en/stable/io.html#netcdf there are statements like > netCDF files on disk directly correspond to Dataset objects. This is useful conceptually but can be confusing when working with netCDF groups which are not supported as part of the data model. I thought it would be clearer if the description of how to work with groups explicitly said this. 2019-07-13T20:48:58Z 2019-07-14T05:34:56Z 2019-07-14T05:34:56Z 2019-07-14T05:34:56Z 82fd8320b1be7a434effd247baf07004b66b802f     0 5827f710e39ebc67771bc4abb1f2213c0a1c0b12 b3ba4ba5f9508e4b601d9cf5dbcd9024993adf37 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/3113  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

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]);
Powered by Datasette · Queries took 20.517ms · About: xarray-datasette