issues

Table actions

3 rows where user = 24938400 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

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
748379763 MDExOlB1bGxSZXF1ZXN0NTI1Mzc4Mjg5 4600 plot tests: ensure all figures are closed yashsaboo 24938400 closed 0     16 2020-11-22T23:45:04Z 2020-11-27T12:03:15Z 2020-11-27T10:18:38Z CONTRIBUTOR   0 pydata/xarray/pulls/4600

Test testxyincrease_false_changes_axes is flaky in nature.

TestCase passes consistently in the actual order with command: pytest tests/test_plot.py

TestCase fails when one randomises the order in test_plot.py module by using the plugin pytest-random-order with command: pytest tests/test_plot.py --random-order-seed=802425 -v

The victim test_xyincrease_false_changes_axes fails in a failing test order because there is at least one test that runs before the victim and “pollute” the state (e.g., global state: here, it is matplotlib's plt) on which the victim depends. (Paper)

After investigation, we found the polluter test to be test_ylim_kwarg

Potential Fix: Adding a plt.clf or plt.cla at the end of the polluter test. Let us know your preference.

Please let us know if you require the pass and fail logs.

Also, if one runs test_plot.py in any random order, Teardown phase throws an error which is raised by test_all_figures_closed(). Should I raise a separate PR for the same?

Contributors: Yash Saboo Nirupam K N

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4600/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
751846954 MDExOlB1bGxSZXF1ZXN0NTI4MjgyMDA4 4614 Updated the forked repo code with original repo code yashsaboo 24938400 closed 0     0 2020-11-26T22:13:33Z 2020-11-26T22:14:26Z 2020-11-26T22:14:26Z CONTRIBUTOR   0 pydata/xarray/pulls/4614

To edit the whats new page, I had it update my local forked repo.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4614/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
750167997 MDExOlB1bGxSZXF1ZXN0NTI2ODcxNzU0 4609 Fixed test_plot_transposed_nondim_coord() and class TestDiscreteColorMap's polluter tests yashsaboo 24938400 closed 0     2 2020-11-25T00:03:38Z 2020-11-25T13:13:33Z 2020-11-25T08:41:45Z CONTRIBUTOR   0 pydata/xarray/pulls/4609

As suggested by @mathause here, we modified the test_plot_transposed_nondim_coord() and class TestDiscreteColorMap's polluter tests.

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