issue_comments

Table actions

4 rows where issue = 930925407 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • Faster transpose · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
869158990 https://github.com/pydata/xarray/pull/5541#issuecomment-869158990 https://api.github.com/repos/pydata/xarray/issues/5541 MDEyOklzc3VlQ29tbWVudDg2OTE1ODk5MA== github-actions[bot] 41898282 2021-06-27T13:08:06Z 2021-06-27T19:58:14Z CONTRIBUTOR

Unit Test Results

6 files  ±0           6 suites  ±0   54m 37s :stopwatch: ±0s 16 156 tests ±0  14 440 :heavy_check_mark: ±0  1 716 :zzz: ±0  0 :x: ±0  90 132 runs  ±0  81 991 :heavy_check_mark: ±0  8 141 :zzz: ±0  0 :x: ±0 

Results for commit 1a0ac999. ± Comparison against base commit 1a0ac999.

:recycle: This comment has been updated with latest results.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Faster transpose 930925407
869213523 https://github.com/pydata/xarray/pull/5541#issuecomment-869213523 https://api.github.com/repos/pydata/xarray/issues/5541 MDEyOklzc3VlQ29tbWVudDg2OTIxMzUyMw== max-sixty 5635139 2021-06-27T19:31:06Z 2021-06-27T19:31:06Z MEMBER

These failures seems unrelated? Just server issues perhaps?

It looks like they're on the flaky test. The binary pass / fail on GHA isn't ideal for those

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Faster transpose 930925407
869213401 https://github.com/pydata/xarray/pull/5541#issuecomment-869213401 https://api.github.com/repos/pydata/xarray/issues/5541 MDEyOklzc3VlQ29tbWVudDg2OTIxMzQwMQ== max-sixty 5635139 2021-06-27T19:29:48Z 2021-06-27T19:29:48Z MEMBER

This makes sense!

No strong view on the 1D copy — I guess it's a performance vs simplicity tradeoff.

I don't think there's an existing ASV but we could create one if we want to work more on this.

I'll merge this, thank you @Illviljan !

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Faster transpose 930925407
869190336 https://github.com/pydata/xarray/pull/5541#issuecomment-869190336 https://api.github.com/repos/pydata/xarray/issues/5541 MDEyOklzc3VlQ29tbWVudDg2OTE5MDMzNg== Illviljan 14371165 2021-06-27T16:31:08Z 2021-06-27T16:31:08Z MEMBER

python =========================== short test summary info ============================ FAILED xarray/tests/test_backends.py::TestPydapOnline::test_dask - webob.exc.... FAILED xarray/tests/test_backends.py::TestPydapOnline::test_cmp_local_file - ... FAILED xarray/tests/test_backends.py::TestPydapOnline::test_compatible_to_netcdf = 3 failed, 13646 passed, 1097 skipped, 209 xfailed, 67 xpassed, 214 warnings in 503.11s (0:08:23) =

These failures seems unrelated? Just server issues perhaps?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Faster transpose 930925407

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);