issue_comments
11 rows where issue = 957439114 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Limit and format number of displayed dimensions in repr · 11 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1003205657 | https://github.com/pydata/xarray/pull/5662#issuecomment-1003205657 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X847y7QZ | Illviljan 14371165 | 2021-12-30T22:56:42Z | 2021-12-30T22:56:42Z | MEMBER | I'll merge this in a couple of days unless someone minds. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
890483420 | https://github.com/pydata/xarray/pull/5662#issuecomment-890483420 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X841E7Lc | github-actions[bot] 41898282 | 2021-08-01T09:20:21Z | 2021-10-31T23:05:56Z | CONTRIBUTOR | Unit Test Results6 files 6 suites 53m 34s :stopwatch: 16 291 tests 14 559 :heavy_check_mark: 1 732 :zzz: 0 :x: 90 942 runs 82 751 :heavy_check_mark: 8 191 :zzz: 0 :x: Results for commit e3af7c03. :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 } |
Limit and format number of displayed dimensions in repr 957439114 | |
894144580 | https://github.com/pydata/xarray/pull/5662#issuecomment-894144580 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X841S5BE | pep8speaks 24736507 | 2021-08-06T09:50:29Z | 2021-10-31T08:56:37Z | NONE | Hello @Illviljan! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: Comment last updated at 2021-10-31 08:56:37 UTC |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
904159594 | https://github.com/pydata/xarray/pull/5662#issuecomment-904159594 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X8415GFq | Illviljan 14371165 | 2021-08-23T21:54:35Z | 2021-08-23T21:54:35Z | MEMBER | The |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
904084591 | https://github.com/pydata/xarray/pull/5662#issuecomment-904084591 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X8414zxv | st-bender 28786187 | 2021-08-23T20:08:30Z | 2021-08-23T20:11:26Z | CONTRIBUTOR | @Illviljan Thanks for this comparison, I certainly prefer the second one, it looks better aligned to me and we get a little more information on one page. But then that's only me. ;) Edit: Not sure what you mean with the attributes, they all start in the 5th column, after 4 spaces like the officially recommended python indentation. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
904000203 | https://github.com/pydata/xarray/pull/5662#issuecomment-904000203 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X8414fLL | Illviljan 14371165 | 2021-08-23T18:13:54Z | 2021-08-23T18:13:54Z | MEMBER | It was easy enough to change so here's how it would look like with one of these extreme datasets: Original:
New line with some indent:
No new line but small indent:
I think I prefer the original one because of the alignment with the dims in coords and data variables. The second one is nice, familiar format as Coordinates and will likely never get in to the 1 long dimension per row issue like in one of the examples. But it looks a little too dense now maybe? This is also adds an extra row for all cases which might not be necessary with most real life datasets? Dimensions without coordinates will add 1 extra row as well. The 3rd one was an alternative to avoid a completely breaking change like the second one is. But I think it looks the worst of these alternatives, too messy. But it's similar to how it looks like right now if the console wraps the printed text. On another note I'm slightly annoyed that the attribute values aren't aligning the same way as coords and data variables and I cannot unsee it now. :/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
903520910 | https://github.com/pydata/xarray/pull/5662#issuecomment-903520910 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X8412qKO | st-bender 28786187 | 2021-08-23T07:40:06Z | 2021-08-23T07:40:06Z | CONTRIBUTOR |
Looks good, but in my opinion this wastes some screen space on the left side.
One could probably start a new line for the dimensions in a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
903354752 | https://github.com/pydata/xarray/pull/5662#issuecomment-903354752 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X8412BmA | max-sixty 5635139 | 2021-08-23T00:11:50Z | 2021-08-23T00:11:50Z | MEMBER | The tests look good! Any thoughts from anyone before we merge? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
895850899 | https://github.com/pydata/xarray/pull/5662#issuecomment-895850899 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X841ZZmT | Illviljan 14371165 | 2021-08-10T08:51:25Z | 2021-08-10T08:51:25Z | MEMBER |
https://github.com/pydata/xarray/blob/4bb9d9c6df77137f05e85c7cc6508fe7a93dc0e4/xarray/core/formatting_html.py#L255 Seems to be this line that caused the error. I don't understand what it does though, some backup of sorts? If it's only being used as backup when something fails I think this is ready. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
894158453 | https://github.com/pydata/xarray/pull/5662#issuecomment-894158453 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X841S8Z1 | Illviljan 14371165 | 2021-08-06T10:13:51Z | 2021-08-06T11:04:23Z | MEMBER | Seems the EDIT: This seems solvable using typeddict, https://stackoverflow.com/questions/48013561/how-to-use-static-type-checking-using-dict-with-different-value-types-in-python |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 | |
894175194 | https://github.com/pydata/xarray/pull/5662#issuecomment-894175194 | https://api.github.com/repos/pydata/xarray/issues/5662 | IC_kwDOAMm_X841TAfa | Illviljan 14371165 | 2021-08-06T10:47:04Z | 2021-08-06T10:47:04Z | MEMBER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Limit and format number of displayed dimensions in repr 957439114 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 5