issues

Table actions

2 rows where repo = 13221727, state = "closed" and user = 141709 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 2

state 1

  • closed · 2 ✖

repo 1

  • xarray · 2 ✖
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
56817968 MDU6SXNzdWU1NjgxNzk2OA== 316 Not-quite-ISO timestamps sjpfenninger 141709 closed 0   0.4 799013 7 2015-02-06T14:30:11Z 2015-02-18T04:45:25Z 2015-02-18T04:45:25Z CONTRIBUTOR      

I have trouble reading NetCDF files obtained from MERRA. It turns out that their time unit is of the form "hours since 1982-1-10 0". Because there is only a single "0" for the hour, rather than "00", this is not an ISO compliant datetime string and pandas.Timestamp raises an error (see pydata/pandas#9434).

This makes it impossible to open such files unless passing decode_times=False to open_dataset().

I wonder if this is a rare edge case or if xray could attempt to intelligently handle it somewhere (maybe in conventions._unpack_netcdf_time_units). For now, I just used NCO to append an extra 0 to the time unit (luckily all files are the same, so I can just do this across the board): ncatted -O -a units,time,a,c,"0" file.nc

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/316/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
57198686 MDExOlB1bGxSZXF1ZXN0MjkwMjE2Mzg= 317 Fall back to netCDF4 if pandas can’t parse a date sjpfenninger 141709 closed 0   0.4 799013 1 2015-02-10T16:31:34Z 2015-02-10T18:37:35Z 2015-02-10T18:37:32Z CONTRIBUTOR   0 pydata/xarray/pulls/317

Addresses #316

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/317/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]);