issues: 364247513
This data as json
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 364247513 | MDExOlB1bGxSZXF1ZXN0MjE4NDgxMjkz | 2442 | Use Hypothesis profile mechanism, not no-op mutation | 12229877 | closed | 0 | 2 | 2018-09-26T23:14:33Z | 2018-09-27T00:35:46Z | 2018-09-26T23:47:27Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2442 | Closes #2441 - Hypothesis 3.72.0 turned a common no-op into an explicit error. Apparently this was such a common misunderstanding that I had done it too :disappointed: Anyway: while it hasn't been using the deadline at all until now, I've still translated it into the correct form rather than deleting it in order to avoid flaky tests if the Travis VM is slow. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2442/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |