home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

1 row where "closed_at" is on date 2021-01-07, comments = 2 and user = 10194086 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 1

state 1

  • closed 1

repo 1

  • xarray 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
780726453 MDExOlB1bGxSZXF1ZXN0NTUwNTczNjM4 4773 CI: ignore some warnings mathause 10194086 closed 0     2 2021-01-06T17:34:05Z 2021-01-07T21:00:31Z 2021-01-07T21:00:27Z MEMBER   0 pydata/xarray/pulls/4773
  • [x] Part of #3266
  • [x] Passes isort . && black . && mypy . && flake8

Supresses 3 warnings we get in the test suite. Two are trivial. The third is PytestUnraisableExceptionWarning: Exception ignored in: CachingFileManager.__del__:

  • The test triggers an error is in CachingFileManager.__init__:

https://github.com/pydata/xarray/blob/31d540f9d668fc5f8c1c92165f950c568778db01/xarray/tests/test_backends_file_manager.py#L205-L207

  • It then tries to run __del__ but there is an error because an attribute is not available (as __init__ failed)

https://github.com/pydata/xarray/blob/31d540f9d668fc5f8c1c92165f950c568778db01/xarray/backends/file_manager.py#L238

  • However, errors in __del__ are ignored, therefore we get a PytestUnraisableExceptionWarning

I decided to suppress the error and not fix CachingFileManager as I think that's nothing user-facing...

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4773/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]);
Powered by Datasette · Queries took 3440.953ms · About: xarray-datasette