issues

Table actions

2 rows where comments = 2, type = "pull" and user = 226037 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
708766975 MDExOlB1bGxSZXF1ZXN0NDkyOTMxMzk3 4458 Autodetect the engine only when `engine=None` alexamici 226037 closed 0     2 2020-09-25T08:53:27Z 2020-12-10T10:30:56Z 2020-09-28T15:42:01Z MEMBER   0 pydata/xarray/pulls/4458

Always use the engine explicitly selected by the user and perform auto detection only when engine=None.

  • [x] Closes #4457
  • [x] Tests added
  • [x] Passes isort . && black . && mypy . && flake8
  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [x] No new functions/methods

The refactor complexity stems mostly from moving or duplicating some logic from _get_engine_from_magic_number to the backend stores. The current, rather ugly, code minimizes changes to the error conditions and messages.

Later in the backend refactor the plugins will provide the functionalities to identify the format from the file content and the duplication should be eliminated.

@jhamman do you think I need to acknowledge the CZI sponsorship in the changelog?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4458/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
372924734 MDExOlB1bGxSZXF1ZXN0MjI0OTgxMjc5 2502 Fix tests to new coordinate names in cfgrib>=0.9.2 alexamici 226037 closed 0     2 2018-10-23T10:24:05Z 2018-10-25T20:57:40Z 2018-10-23T18:28:48Z MEMBER   0 pydata/xarray/pulls/2502

Fix TestCfGrib broken by a user-visible backward-incompatible change in cfgrib>=0.9.2.

No other user visible coordinate name change is expected so the test can remain like it is.

Sorry for the inconvenience!

  • [x] Noted in the discussion of #2500
  • [x] Tests added
  • ~~Fully documented, including whats-new.rst for all changes and api.rst for new API~~
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2502/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]);