home / github

Menu
  • GraphQL API
  • Search all tables

issues

Table actions
  • GraphQL API for issues

3 rows where user = 4687996 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: closed_at, created_at (date), updated_at (date), closed_at (date)

type 2

  • pull 2
  • issue 1

state 1

  • closed 3

repo 1

  • xarray 3
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
694876170 MDExOlB1bGxSZXF1ZXN0NDgxMTk1NTM3 4411 Fix incorrect legend labels for Dataset.plot.scatter phausamann 4687996 closed 0     0 2020-09-07T08:48:38Z 2020-09-10T18:48:12Z 2020-09-10T18:48:11Z CONTRIBUTOR   0 pydata/xarray/pulls/4411
  • [x] Closes #4126
  • [x] Tests added
  • [x] Passes isort . && black . && mypy . && flake8
  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4411/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 pull
381518663 MDExOlB1bGxSZXF1ZXN0MjMxNDY3Nzkw 2556 Add transpose_coords option to DataArray.transpose phausamann 4687996 closed 0     11 2018-11-16T09:36:13Z 2019-05-21T17:38:07Z 2019-05-21T17:37:55Z CONTRIBUTOR   0 pydata/xarray/pulls/2556
  • [x] Closes #1856
  • [x] Tests added (for all bug fixes or enhancements)
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

I've added the option transpose_coords to DataArray.transpose as described in #1856. It's False by default, as it breaks a couple of tests otherwise (TestConcatDataset.test_concat, test_apply_output_core_dimension and test_dot). I'm not sure whether fixing these tests to work with the new behavior should be part of the PR.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2556/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    xarray 13221727 pull
291485366 MDU6SXNzdWUyOTE0ODUzNjY= 1856 Option to make DataArray.transpose also transpose coords phausamann 4687996 closed 0     3 2018-01-25T08:20:11Z 2019-05-21T17:37:55Z 2019-05-21T17:37:55Z CONTRIBUTOR      

I've noticed that Dataset.transpose transposes the coordinates while DataArray.transpose does not.

Example:

import xarray as xr
import numpy as np

X_da = xr.DataArray(
    np.random.random((100, 10)),
    coords={'coord_1': (['sample', 'feature'], np.ones((100, 10)))},
    dims=('sample', 'feature')
)

In []: X_da.transpose().coord_1.dims
Out[]: ('sample', 'feature')

X_ds = xr.Dataset(
    {'var_1': (['sample', 'feature'], np.random.random((100, 10)))},
    coords={'coord_1': (['sample', 'feature'], np.ones((100, 10)))},
)

In []: X_ds.transpose().coord_1.dims
Out[]: ('feature', 'sample')

This behaviour is probably intentional, but there are cases where I'd like DataArray.transpose to also transpose the coordinates. As a workaround, I have to convert to a Dataset, transpose and convert back.

I was thinking that DataArray.transpose could accept a keyword argument transpose_coords which would be False by default. I could work on a PR implementing this behavior if it's desired.

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

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]);
Powered by Datasette · Queries took 20.826ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows