issues
11 rows where comments = 9, state = "closed" and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2110888925 | I_kwDOAMm_X8590Zvd | 8690 | Add `nbytes` to repr? | max-sixty 5635139 | closed | 0 | 9 | 2024-01-31T20:13:59Z | 2024-02-19T22:18:47Z | 2024-02-07T20:47:38Z | MEMBER | Is your feature request related to a problem?Would having the I frequently find myself logging this separately. For example:
Describe the solution you'd likeNo response Describe alternatives you've consideredStatus quo :) Additional contextNo response |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8690/reactions",
"total_count": 6,
"+1": 6,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | xarray 13221727 | issue | ||||||
| 1897096472 | PR_kwDOAMm_X85aXwKH | 8183 | Remove `setup.cfg` in favor of `pyproject.toml` | max-sixty 5635139 | closed | 0 | 9 | 2023-09-14T18:29:16Z | 2023-09-15T22:42:42Z | 2023-09-14T20:52:39Z | MEMBER | 0 | pydata/xarray/pulls/8183 | This is tested, but much of it was me tweaking from an LLM's attempt at the translation, so there may be small issues that aren't picked up in tests (but should be very easy to fix if these come up) |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8183/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 936123457 | MDExOlB1bGxSZXF1ZXN0NjgyOTI5NDA1 | 5569 | Consolidate TypeVars in a single place | max-sixty 5635139 | closed | 0 | 9 | 2021-07-03T00:01:09Z | 2021-08-22T00:04:54Z | 2021-08-21T23:38:14Z | MEMBER | 0 | pydata/xarray/pulls/5569 |
This consolidates the TypeVars into a single place, and merges I'm not 100% sure the interaction between the There's a note to rename |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5569/reactions",
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 860909006 | MDExOlB1bGxSZXF1ZXN0NjE3NjY2NzI0 | 5188 | Replace raises_regex with pytest.raises | max-sixty 5635139 | closed | 0 | 9 | 2021-04-19T05:26:23Z | 2021-04-19T23:10:06Z | 2021-04-19T23:10:03Z | MEMBER | 0 | pydata/xarray/pulls/5188 |
Is there a reason we have our own This is another regex special, so it misses multi-line statements. I can dust off the multi-line regex manual if this ends up working. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5188/reactions",
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 681528611 | MDExOlB1bGxSZXF1ZXN0NDY5OTA2MzQ3 | 4351 | Allow cov & corr to handle missing values | max-sixty 5635139 | closed | 0 | 9 | 2020-08-19T04:02:21Z | 2020-08-30T11:36:38Z | 2020-08-24T16:39:11Z | MEMBER | 0 | pydata/xarray/pulls/4351 |
I'm not that excited about how this is tested, very open to alternatives. And the mechanics could take another set of eyes too. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4351/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 509486175 | MDExOlB1bGxSZXF1ZXN0MzMwMDQxNjM2 | 3418 | change ALL_DIMS to equal ellipsis | max-sixty 5635139 | closed | 0 | 9 | 2019-10-19T17:46:55Z | 2019-10-25T17:16:33Z | 2019-10-25T15:15:47Z | MEMBER | 0 | pydata/xarray/pulls/3418 |
This is a more drastic version of the suggested change, making The only downside I can see is that printing |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3418/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 393710539 | MDU6SXNzdWUzOTM3MTA1Mzk= | 2627 | Is pep8speaks working well? | max-sixty 5635139 | closed | 0 | 9 | 2018-12-22T23:38:14Z | 2018-12-30T11:08:41Z | 2018-12-30T11:08:41Z | MEMBER | I returned to do some work on xarray, and looks like there are lots of linting errors. Maybe we shouldn't worry ourselves with this; though let's make a deliberate decision Is pep8speaks working well? One example is this PR: https://github.com/pydata/xarray/pull/2553, where it looks like pep8speaks initially complained, but doesn't have a test so was potentially lost in the discussion. Any thoughts? I'm happy to help see if there are alternatives / pep8speaks can be added as a test / add a test in travis / fix these. FWIW I've used
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2627/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | xarray 13221727 | issue | ||||||
| 309976469 | MDExOlB1bGxSZXF1ZXN0MTc4NDk0ODMw | 2031 | Isin | max-sixty 5635139 | closed | 0 | 9 | 2018-03-30T05:07:12Z | 2018-04-04T03:52:21Z | 2018-04-04T02:46:57Z | MEMBER | 0 | pydata/xarray/pulls/2031 |
This is an initial implementation of I've been away from these sorts features for too long: Is there a canonical place to put these? What's the canonical approach to extending to datasets? I can see a few approaches in the code. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2031/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 206632333 | MDU6SXNzdWUyMDY2MzIzMzM= | 1257 | PERF: Add benchmarking? | max-sixty 5635139 | closed | 0 | 9 | 2017-02-09T21:17:40Z | 2017-07-26T16:17:34Z | 2017-07-26T16:17:34Z | MEMBER | Because xarray is all python and generally not doing much compute itself (i.e. it marshals other libraries to do that), this hasn't been that important. IIRC most of the performance issues have arisen where xarray builds on (arguably) shaky foundations, like Though as we mature, is it worth adding some benchmarks? If so, what's a good way to do this? Pandas uses asv successfully. I don't have experience with https://github.com/ionelmc/pytest-benchmark but that could be a lower cost way of getting started. Any others? |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/1257/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | xarray 13221727 | issue | ||||||
| 192702101 | MDExOlB1bGxSZXF1ZXN0OTU5ODk3Mzc= | 1145 | Rolling count | max-sixty 5635139 | closed | 0 | 9 | 2016-11-30T22:44:50Z | 2017-06-26T18:43:06Z | 2017-06-26T18:43:06Z | MEMBER | 0 | pydata/xarray/pulls/1145 | {
"url": "https://api.github.com/repos/pydata/xarray/issues/1145/reactions",
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | ||||||
| 156072065 | MDExOlB1bGxSZXF1ZXN0NzA5MzI2Mzc= | 852 | BUG: Stringify DS attrs in dir | max-sixty 5635139 | closed | 0 | 9 | 2016-05-21T00:07:23Z | 2016-08-10T01:15:31Z | 2016-08-10T01:13:50Z | MEMBER | 0 | pydata/xarray/pulls/852 | Previously: ``` python In [21]: ds Out[21]: <xarray.Dataset> Dimensions: (abc: 3) Coordinates: * abc (abc) int64 0 1 2 Data variables: 0 (abc) float64 0.3168 0.1132 0.6664 1 (abc) float64 0.9799 0.9663 0.01084 2 (abc) float64 0.9171 0.6848 0.5028 In [22]: dir(ds)TypeError Traceback (most recent call last) <ipython-input-22-fd55ce5c03db> in <module>() ----> 1 dir(ds) /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/xarray/core/common.py in dir(self) 157 extra_attrs = [item for sublist in self._attr_sources 158 for item in sublist] --> 159 return sorted(set(dir(type(self)) + extra_attrs)) 160 161 TypeError: unorderable types: numpy.ndarray() > str() ``` |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/852/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
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]);