issue_comments
16 rows where author_association = "MEMBER" and issue = 196278181 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix tests for upcoming matplotlib v2 · 16 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
270094486 | https://github.com/pydata/xarray/pull/1171#issuecomment-270094486 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI3MDA5NDQ4Ng== | fmaussion 10050469 | 2017-01-03T11:20:17Z | 2017-01-03T11:20:17Z | MEMBER | OK, so thanks to https://github.com/pydata/xarray/pull/1191 the required changes for the tests to pass in mpl v2 are minimal:
- deprecation of This is ready for review / merge |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269574812 | https://github.com/pydata/xarray/pull/1171#issuecomment-269574812 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU3NDgxMg== | jhamman 2443309 | 2016-12-29T02:55:56Z | 2016-12-29T02:55:56Z | MEMBER | I've never been completely satisfied with what we came up with for the vmin/vmax/levels logic. Its been the source of a few bugs and confusion (#1015). The feature set we were going for is mostly covered (discrete colorbar, flexibility in specification of levels, etc.) but we may want to revisit the approach. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269556898 | https://github.com/pydata/xarray/pull/1171#issuecomment-269556898 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU1Njg5OA== | fmaussion 10050469 | 2016-12-28T23:17:02Z | 2016-12-28T23:17:02Z | MEMBER | @shoyer
AFAIK, there is no logic for However, the default mpl behavior when no levels are set is to call the private method _autolev which has a logic based on Long story short: I'll start another PR to address this problem specifically and then go back to MPL2 later on. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269553953 | https://github.com/pydata/xarray/pull/1171#issuecomment-269553953 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU1Mzk1Mw== | fmaussion 10050469 | 2016-12-28T22:49:46Z | 2016-12-28T22:51:27Z | MEMBER | @efiring thanks for jumping in! I understand and I see that xarray is kind of misusing this tool, we'll change this in this PR. In the test above |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269551434 | https://github.com/pydata/xarray/pull/1171#issuecomment-269551434 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU1MTQzNA== | shoyer 1217238 | 2016-12-28T22:29:20Z | 2016-12-28T22:29:20Z | MEMBER | My feeling is that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269550777 | https://github.com/pydata/xarray/pull/1171#issuecomment-269550777 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU1MDc3Nw== | fmaussion 10050469 | 2016-12-28T22:23:30Z | 2016-12-28T22:23:30Z | MEMBER | @QuLogic : thanks, and sorry for the noise. @shoyer : should we use On a side note, I already encountered this problem with my students before: what most users will do in this case is to set |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269549955 | https://github.com/pydata/xarray/pull/1171#issuecomment-269549955 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU0OTk1NQ== | shoyer 1217238 | 2016-12-28T22:16:47Z | 2016-12-28T22:16:47Z | MEMBER | @fmaussion as you note, even if this is a matplotlib bug, it seems like this was not doing quite the desired thing in xarray even with matplotlib 1.5 -- we really should be using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269548744 | https://github.com/pydata/xarray/pull/1171#issuecomment-269548744 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU0ODc0NA== | shoyer 1217238 | 2016-12-28T22:07:01Z | 2016-12-28T22:07:01Z | MEMBER | The Matplotlib 2.0 release notes mention that the algorithm for the number of ticks in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269548536 | https://github.com/pydata/xarray/pull/1171#issuecomment-269548536 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU0ODUzNg== | fmaussion 10050469 | 2016-12-28T22:05:29Z | 2016-12-28T22:05:29Z | MEMBER | I've found this ticket, but it's not clear to me if the problem is solved or not. I'll have to test against mpl2 master I guess... @QuLogic do you maybe have a moment to have a look at my comment above? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269546930 | https://github.com/pydata/xarray/pull/1171#issuecomment-269546930 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTU0NjkzMA== | fmaussion 10050469 | 2016-12-28T21:52:38Z | 2016-12-28T21:52:38Z | MEMBER |
Yes, I should've looked into this in more detail. So the problem is here. Furthermore,
Which prints, depending on mpl version:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269369833 | https://github.com/pydata/xarray/pull/1171#issuecomment-269369833 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTM2OTgzMw== | shoyer 1217238 | 2016-12-27T19:15:47Z | 2016-12-27T19:15:47Z | MEMBER | @fmaussion I think this is a bug, either with xarray plotting or matplotlib 2. If you supply Also, shouldn't you get the requested number of levels? In matplotlib 2.0, I see 9 levels, not 7. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269312214 | https://github.com/pydata/xarray/pull/1171#issuecomment-269312214 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTMxMjIxNA== | fmaussion 10050469 | 2016-12-27T11:12:37Z | 2016-12-27T11:12:37Z | MEMBER | This fixes the failing tests on MPL2. Two of the tests were failing because of how mpl chooses to do things, which makes me think that the tests are not very robust. My fixes are also rather simple... For example the ```python import xarray as xr import matplotlib.pyplot as plt import numpy as np import matplotlib x = np.arange(start=0, stop=10, step=2) y = np.arange(start=9, stop=-7, step=-3) xy = np.dstack(np.meshgrid(x, y)) distance = np.linalg.norm(xy, axis=2) darray = xr.DataArray(distance, list(zip(('y', 'x'), (y, x)))) darray.plot(levels=7, vmin=4, vmax=8, extend='both') plt.title('mpl {}'.format(matplotlib.version)) ``` produces:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269094918 | https://github.com/pydata/xarray/pull/1171#issuecomment-269094918 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTA5NDkxOA== | jhamman 2443309 | 2016-12-24T18:17:30Z | 2016-12-24T18:17:30Z | MEMBER | @fmaussion Great. No rush. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269094708 | https://github.com/pydata/xarray/pull/1171#issuecomment-269094708 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTA5NDcwOA== | fmaussion 10050469 | 2016-12-24T18:11:09Z | 2016-12-24T18:11:09Z | MEMBER | @jhamman I planned to do so but I won't come to this in the next couple of days, so if its urgent and you want to do it go ahead! They should be easy fixes |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
269094437 | https://github.com/pydata/xarray/pull/1171#issuecomment-269094437 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2OTA5NDQzNw== | jhamman 2443309 | 2016-12-24T18:03:10Z | 2016-12-24T18:03:10Z | MEMBER | @fmaussion - do you want to take point on resolving these failing tests? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 | |
267824875 | https://github.com/pydata/xarray/pull/1171#issuecomment-267824875 | https://api.github.com/repos/pydata/xarray/issues/1171 | MDEyOklzc3VlQ29tbWVudDI2NzgyNDg3NQ== | fmaussion 10050469 | 2016-12-18T14:40:48Z | 2016-12-18T14:40:48Z | MEMBER | ... three failing tests. Not too bad! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix tests for upcoming matplotlib v2 196278181 |
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 3