issues
3 rows where "created_at" is on date 2023-10-07, state = "closed" and user = 14371165 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: draft, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1931329996 | PR_kwDOAMm_X85cK3Or | 8281 | Add high level from_array function in namedarray | Illviljan 14371165 | closed | 0 | 1 | 2023-10-07T12:19:23Z | 2023-10-10T17:10:37Z | 2023-10-10T17:10:37Z | MEMBER | 1 | pydata/xarray/pulls/8281 | The Idea is to avoid as much normalization in the NamedArray class as possible. Different types are handled before initializing instead.
References: https://github.com/tomwhite/cubed/blob/ea885193dd37d27917a24878b51bb086aaef5fb1/cubed/core/ops.py#L34 https://stackoverflow.com/questions/74633074/how-to-type-hint-a-generic-numpy-array https://numpy.org/doc/stable/reference/arrays.scalars.html#scalars https://github.com/numpy/numpy/blob/040ed2dc9847265c581a342301dd87d2b518a3c2/numpy/init.pyi#L1423 https://github.com/numpy/numpy/blob/040ed2dc9847265c581a342301dd87d2b518a3c2/numpy/_typing/_array_like.py#L32 Mypy issues: https://github.com/python/typing/issues/548 |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8281/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1931220385 | PR_kwDOAMm_X85cKhhk | 8279 | Add pyright type checker | Illviljan 14371165 | closed | 0 | 5 | 2023-10-07T06:38:14Z | 2023-10-09T12:32:29Z | 2023-10-09T12:32:28Z | MEMBER | 0 | pydata/xarray/pulls/8279 | It can be helpful to get a second opinion from another typer checker than mypy. The CI activates when the |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8279/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
xarray 13221727 | pull | |||||
| 1931223548 | PR_kwDOAMm_X85cKiKo | 8280 | Remove if condition to trigger mypy | Illviljan 14371165 | closed | 0 | 0 | 2023-10-07T06:49:18Z | 2023-10-08T00:49:34Z | 2023-10-08T00:49:34Z | MEMBER | 0 | pydata/xarray/pulls/8280 | This seems to be fixed according to #6551. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8280/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]);