issues
2 rows where state = "open" and user = 23738400 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1240234432 | I_kwDOAMm_X85J7HnA | 6620 | Using the html repr in the documentation | OriolAbril 23738400 | open | 0 | 1 | 2022-05-18T16:53:46Z | 2022-05-18T17:46:26Z | CONTRIBUTOR | What is your issue?most (if not all) of xarray documentation is written as rst files and using the ipython directive. Due to this, the html repr is not use in the documentation. I find the html repr to be much more informative and intuitive, especially for beginners and I think it would be great to use it in the documentation. There are multiple ways to do this (not necessarly incompatible between them):
afaik, nbsphinx can be changed with myst-nb without needing to do any changes to the documentation, then rst files could be progressively updated to ipynb, myst or any other format supported by jupytext, rst, markdown and notebook sources can all be used at the same time to generate the documentation and link from one to the other with sphinx roles and cross references. Is this something that sounds interesting? I could update the infrastructure at some point whenever I have time and update a page (to any or multiple of the options above) as an example and then let other people take over |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6620/reactions", "total_count": 3, "+1": 3, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue | ||||||||
457716471 | MDU6SXNzdWU0NTc3MTY0NzE= | 3032 | apply_ufunc should preemptively broadcast | OriolAbril 23738400 | open | 0 | 11 | 2019-06-18T22:02:36Z | 2019-06-19T22:27:27Z | CONTRIBUTOR | Code SampleI am having some troubles understanding ```python import xarray as xr import numpy as np a = xr.DataArray(data=np.random.normal(size=(7, 3)), dims=["dim1", "dim2"]) c = xr.DataArray(data=np.random.normal(size=(5, 6)), dims=["dim3", "dim4"]) def func(x,y): print(x.shape) print(y.shape) return ``` The function defined always raises an error when trying to call Problem description```python xr.apply_ufunc(func, a, c) Out(7, 3, 1, 1)(5, 6)``` Here, ```python print([ary.shape for ary in xr.broadcast(a,c)]) [(7, 3, 5, 6), (7, 3, 5, 6)]``` Using different input core dims does not get rid of the problem, instead I believe it shows some more issues: ```python xr.apply_ufunc(func, a, c, input_core_dims=[["dim1"],[]]) (3, 1, 1, 7), expected (3, 5, 6, 7)(5, 6), expected (3, 5, 6)xr.apply_ufunc(func, a, c, input_core_dims=[[],["dim3"]]) (7, 3, 1), expected (7, 3, 6)(6, 5), expected (7, 3, 6, 5)xr.apply_ufunc(func, a, c, input_core_dims=[["dim1"],["dim3"]]) (3, 1, 7), expected (3, 6, 7)(6, 5), expected (3, 6, 5)``` Is this current behaviour what should be expected? Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3032/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);