issue_comments
8 rows where user = 1700203 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- blsqr · 8 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
781160118 | https://github.com/pydata/xarray/pull/2905#issuecomment-781160118 | https://api.github.com/repos/pydata/xarray/issues/2905 | MDEyOklzc3VlQ29tbWVudDc4MTE2MDExOA== | blsqr 1700203 | 2021-02-18T08:30:46Z | 2021-02-18T08:30:46Z | CONTRIBUTOR | @keewis Thanks for looking into this and updating the PR! :) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Use explicit type check in `as_compatible_data` instead of blanket access to `values` attribute 434502234 | |
631608640 | https://github.com/pydata/xarray/pull/4018#issuecomment-631608640 | https://api.github.com/repos/pydata/xarray/issues/4018 | MDEyOklzc3VlQ29tbWVudDYzMTYwODY0MA== | blsqr 1700203 | 2020-05-20T17:13:21Z | 2020-05-20T17:13:21Z | CONTRIBUTOR | Thanks, @dcherian! I'm happy to contribute 😊 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add NetCDF3 dtype coercion for unsigned integer types 610687463 | |
622965234 | https://github.com/pydata/xarray/pull/4018#issuecomment-622965234 | https://api.github.com/repos/pydata/xarray/issues/4018 | MDEyOklzc3VlQ29tbWVudDYyMjk2NTIzNA== | blsqr 1700203 | 2020-05-02T14:47:54Z | 2020-05-02T14:47:54Z | CONTRIBUTOR | Alright, I added the test. From my side, this would be ready. :) Let me know if further changes to the tests or What's New are necessary. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add NetCDF3 dtype coercion for unsigned integer types 610687463 | |
622389439 | https://github.com/pydata/xarray/pull/4018#issuecomment-622389439 | https://api.github.com/repos/pydata/xarray/issues/4018 | MDEyOklzc3VlQ29tbWVudDYyMjM4OTQzOQ== | blsqr 1700203 | 2020-05-01T13:32:02Z | 2020-05-01T13:32:02Z | CONTRIBUTOR | @dcherian I think this would be ready for review now. I'd appreciate some guidance on the implementation of the tests; see above. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add NetCDF3 dtype coercion for unsigned integer types 610687463 | |
622342323 | https://github.com/pydata/xarray/pull/4018#issuecomment-622342323 | https://api.github.com/repos/pydata/xarray/issues/4018 | MDEyOklzc3VlQ29tbWVudDYyMjM0MjMyMw== | blsqr 1700203 | 2020-05-01T10:51:20Z | 2020-05-01T10:51:20Z | CONTRIBUTOR | Currently, the error that is raised by A test could look something like this: ```python def test_dtype_coercion_error(self): for dtype in _nc3_dtype_coercions: if dtype == "bool": continue
``` ... but I'm not sure ...
* whether this would be desirable to test
* whether this PR should take care of this or not
* where in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add NetCDF3 dtype coercion for unsigned integer types 610687463 | |
621102297 | https://github.com/pydata/xarray/issues/4014#issuecomment-621102297 | https://api.github.com/repos/pydata/xarray/issues/4014 | MDEyOklzc3VlQ29tbWVudDYyMTEwMjI5Nw== | blsqr 1700203 | 2020-04-29T09:56:11Z | 2020-04-29T09:56:11Z | CONTRIBUTOR | I'd be happy to open a PR, if such a behaviour is desired. It seems like extending the Suggestion: Add all |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add NetCDF3 dtype coercion for unsigned integer types 608923222 | |
560126145 | https://github.com/pydata/xarray/pull/2905#issuecomment-560126145 | https://api.github.com/repos/pydata/xarray/issues/2905 | MDEyOklzc3VlQ29tbWVudDU2MDEyNjE0NQ== | blsqr 1700203 | 2019-12-01T16:13:22Z | 2019-12-01T16:13:49Z | CONTRIBUTOR | @dcherian The most recent pipeline now fails in the Could you give me a hint on how to continue? Or need this be fixed elsewhere (or is already fixed) and I need to update this topic branch? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Use explicit type check in `as_compatible_data` instead of blanket access to `values` attribute 434502234 | |
484255028 | https://github.com/pydata/xarray/issues/2097#issuecomment-484255028 | https://api.github.com/repos/pydata/xarray/issues/2097 | MDEyOklzc3VlQ29tbWVudDQ4NDI1NTAyOA== | blsqr 1700203 | 2019-04-17T20:46:55Z | 2019-04-17T20:46:55Z | CONTRIBUTOR | I was wondering if this is still up for consideration?
Same here. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Variable.__setitem__ coercing types on objects with a values property 319329850 |
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]);
issue 4