issues

Table actions

2 rows where type = "pull" and user = 1191149 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

type 1

  • pull · 2 ✖

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
517522619 MDExOlB1bGxSZXF1ZXN0MzM2NTc1NzYx 3485 uamiv test using only raw uamiv variables barronh 1191149 closed 0     2 2019-11-05T03:07:14Z 2019-11-05T15:42:36Z 2019-11-05T15:42:35Z CONTRIBUTOR   0 pydata/xarray/pulls/3485

Previous test relied on CF generated metadata, but this test is more robust.

  • [x] Addresses #3409 #3420 #3434
  • [x] Tests fixed

Development machine is missing python3.6 environment, using azure to check. This should help me get this fix in faster.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3485/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
296561316 MDExOlB1bGxSZXF1ZXN0MTY4NzE1OTQy 1905 Added PNC backend to xarray barronh 1191149 closed 0     34 2018-02-12T23:26:36Z 2018-06-01T11:40:58Z 2018-06-01T04:21:44Z CONTRIBUTOR   0 pydata/xarray/pulls/1905

PNC is used for GEOS-Chem, CAMx, CMAQ and other atmospheric data formats including NOAA arl packed bit and HYSPLIT related files. The goal is to provide access to many file types that have their own file formats and meta-data conventions. It can provide a CF compliant netCDF-like interface.

  • [x] Tests were run using example datasets, but datasets were not added to repository as they are large and diverse. Only files that provide CF compliant structures will successfully open. Confirmed by @bbakernoaa
  • [x] Tests added (for all bug fixes or enhancements)
  • [x] Tests passed (for all non-documentation changes)
  • [x] 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)
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1905/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

Advanced export

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

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);