issues
3 rows where comments = 7, type = "issue" and user = 10194086 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 594669577 | MDU6SXNzdWU1OTQ2Njk1Nzc= | 3937 | compose weighted with groupby, coarsen, resample, rolling etc. | mathause 10194086 | open | 0 | 7 | 2020-04-05T22:00:40Z | 2023-07-27T18:10:10Z | MEMBER | It would be nice to make However, it is not entirely clear to me how that should be done. One way would be to do:
Or
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/3937/reactions",
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | issue | ||||||||
| 975385095 | MDU6SXNzdWU5NzUzODUwOTU= | 5721 | pandas deprecates Index.get_loc with method | mathause 10194086 | closed | 0 | 7 | 2021-08-20T08:24:16Z | 2022-01-27T21:06:40Z | 2022-01-27T21:06:40Z | MEMBER | pandas deprecates the
We should fix this before pandas releases because the warning will not be silent (
We use this here:
https://github.com/pydata/xarray/blob/4bb9d9c6df77137f05e85c7cc6508fe7a93dc0e4/xarray/core/indexes.py#L233-L235
Is this only ever called with one item? Then we might be able to use
```python
indexer = self.index.get_indexer(
[label_value], method=method, tolerance=tolerance
).item()
if indexer == -1:
raise KeyError(label_value)
```
---
https://github.com/pydata/xarray/blob/3956b73a7792f41e4410349f2c40b9a9a80decd2/xarray/core/missing.py#L571-L572
This one could be easy to fix (replace with `imin = index.get_indexer([minval], method="nearest").item()`)
---
It is also defined in `CFTimeIndex`, which complicates things:
https://github.com/pydata/xarray/blob/eea76733770be03e78a0834803291659136bca31/xarray/coding/cftimeindex.py#L461-L466
because `get_indexer` expects an iterable and thus the `if isinstance(key, str)` test no longer works.
@benbovy @spencerkclark |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5721/reactions",
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | xarray 13221727 | issue | ||||||
| 407864596 | MDU6SXNzdWU0MDc4NjQ1OTY= | 2754 | silence warning for decode_cf_datetime? | mathause 10194086 | closed | 0 | 7 | 2019-02-07T19:38:38Z | 2019-02-19T20:47:26Z | 2019-02-19T20:47:26Z | MEMBER | Code Sample, a copy-pastable example if possible```python import xarray as xr import numpy as np x = np.arange(100) * 365 x = xr.coding.times.decode_cf_datetime(x, 'days since 2400-01-01', calendar='proleptic_gregorian') ``` Problem descriptionxarray still throws an error when decoding out-of-bounds dates for proleptic_gregorian - should this be silenced? Output of
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2754/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | xarray 13221727 | issue |
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]);