issue_comments

Table actions

7 rows where author_association = "CONTRIBUTOR" and user = 3383837 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • itcarroll · 7 ✖

author_association 1

  • CONTRIBUTOR · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1453707146 https://github.com/pydata/xarray/issues/7423#issuecomment-1453707146 https://api.github.com/repos/pydata/xarray/issues/7423 IC_kwDOAMm_X85Wpc-K itcarroll 3383837 2023-03-03T15:33:27Z 2023-03-03T15:33:27Z CONTRIBUTOR

Would you consider xarray itself to be "numpy-adjacent"? If XArray fully adopted (i don't know how!) the NetCDF4 _FillValue attribute, this and some other challenges, could be solved rigorously.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   unstacking an integer array yields a RuntimeWarning after upgrade to numpy 1.24.1 1521368478
1424713396 https://github.com/pydata/xarray/issues/6715#issuecomment-1424713396 https://api.github.com/repos/pydata/xarray/issues/6715 IC_kwDOAMm_X85U62a0 itcarroll 3383837 2023-02-09T19:38:17Z 2023-02-09T19:38:17Z CONTRIBUTOR

@ShengpeiWang Has the right preventative solution. What do you do when you mess this up in an interactive python session? I can find no way to unlock the file other than renaming it and then opening and closing. The lock even persists through restarting the python interpreter.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `xr.open_rasterio` fails to locate file after being ran 3 times 1280507371
1316282950 https://github.com/pydata/xarray/issues/6447#issuecomment-1316282950 https://api.github.com/repos/pydata/xarray/issues/6447 IC_kwDOAMm_X85OdOJG itcarroll 3383837 2022-11-16T03:46:56Z 2022-11-16T03:46:56Z CONTRIBUTOR

Rather than arbitrary, I'd like to see it make the choice match the "first" (or caller of update, in this example, but same error happens with xr.merge) input.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   allow merging datasets where a variable might be a coordinate variable only in a subset of datasets 1194945072
1302289476 https://github.com/pydata/xarray/issues/7250#issuecomment-1302289476 https://api.github.com/repos/pydata/xarray/issues/7250 IC_kwDOAMm_X85Nn1xE itcarroll 3383837 2022-11-03T15:31:52Z 2022-11-03T15:31:52Z CONTRIBUTOR

You're welcome! Please let me know if a PR (a first for me on xarray) would be welcome. A pointer to the relevant source would get me started.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   stack casts int32 dtype coordinate to int64 1433998942
1302248046 https://github.com/pydata/xarray/issues/7250#issuecomment-1302248046 https://api.github.com/repos/pydata/xarray/issues/7250 IC_kwDOAMm_X85Nnrpu itcarroll 3383837 2022-11-03T15:03:17Z 2022-11-03T15:04:10Z CONTRIBUTOR

Darn. Well, to help this be more transparent, I think it would be on XArray to sync the new dtype in the variable's attributes. Because I also currently get False for the following:

ds.stack(b=('a',))['a'].dtype == ds.stack(b=('a',))['a'].values.dtype

Thanks for looking into this issue!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   stack casts int32 dtype coordinate to int64 1433998942
1019306532 https://github.com/pydata/xarray/issues/6055#issuecomment-1019306532 https://api.github.com/repos/pydata/xarray/issues/6055 IC_kwDOAMm_X848wWIk itcarroll 3383837 2022-01-22T16:45:52Z 2022-01-22T16:45:52Z CONTRIBUTOR

For future searchers: @jp-dark just added a feature to the upcoming release of the tiledb backend introducing an argument encode_fill to set (or not) the _FillValue metadata in XArray. Then the XArray mask_and_scale works as documented.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unexpected type conversion in variables with _FillValue 1075765204
991042526 https://github.com/pydata/xarray/issues/6055#issuecomment-991042526 https://api.github.com/repos/pydata/xarray/issues/6055 IC_kwDOAMm_X847Ehve itcarroll 3383837 2021-12-10T14:59:29Z 2021-12-10T15:25:11Z CONTRIBUTOR

@dcherian Chiming in as the author of TileDB-Inc/TileDB-CF-py#117. To help ensure the tiledb backend matches the behavior of xr.open_dataset for netCDF files, can you help me understand why the promotion to float does NOT occur in the following case:

``` import netCDF4 import xarray as xr import numpy as np

filename = 'temp_file.nc' with netCDF4.Dataset(filename, mode="w") as group: group.createDimension("index", 4) var = group.createVariable("var", np.int16, ("index",)) var[0:3] = np.array([5, 6, 7], dtype=np.int16) dataset = xr.open_dataset(filename) dataset["var"].dtype ```

Note that netCDF.default_fillvalues['i2'] is the value found at dataset["var"][3], which was never explicitly written. Here XArray seems to ignore the fill value.

Update

Okay, I think I understand why. In createVariable whether I use the default fill_value=None or set fill_value=False, XArray does not include _FillValue in dataset["var"].encoding. That, I think, is a bug. If you print(var) with fill_value=None, you'll see that NetCDF is setting the _FIllValue attribute. I don't think XArray should ignore it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Unexpected type conversion in variables with _FillValue 1075765204

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]);