issue_comments

Table actions

3 rows where issue = 157886730 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 3

issue 1

  • TypeError: invalid type promotion when reading multi-file dataset · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
457948951 https://github.com/pydata/xarray/issues/864#issuecomment-457948951 https://api.github.com/repos/pydata/xarray/issues/864 MDEyOklzc3VlQ29tbWVudDQ1Nzk0ODk1MQ== stale[bot] 26384082 2019-01-27T19:58:04Z 2019-01-27T19:58:04Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   TypeError: invalid type promotion when reading multi-file dataset 157886730
223160437 https://github.com/pydata/xarray/issues/864#issuecomment-223160437 https://api.github.com/repos/pydata/xarray/issues/864 MDEyOklzc3VlQ29tbWVudDIyMzE2MDQzNw== shoyer 1217238 2016-06-02T00:01:32Z 2016-06-02T00:01:32Z MEMBER

What are the types of the incompatible arrays? This certainly is not desirable for xarray -- we'd like to be able to stack these arrays together, into a lowest compatible dtype (even if that's only object). I think the main issue here is actually in dask.array, but it would be nice to be able to provide them with a minimal example.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   TypeError: invalid type promotion when reading multi-file dataset 157886730
222995827 https://github.com/pydata/xarray/issues/864#issuecomment-222995827 https://api.github.com/repos/pydata/xarray/issues/864 MDEyOklzc3VlQ29tbWVudDIyMjk5NTgyNw== mangecoeur 743508 2016-06-01T13:42:21Z 2016-06-01T13:42:59Z CONTRIBUTOR

On further investigation, it appears the problem is the dataset contains a mix of string and float data - the strings are redundant representations of the time stamp, therefore they don't appear in the index query. When I tried to convert to array, the numpy chokes on the mixed types. Explicitly selecting on the desired data variable solves this:

selection = cfsr_new.TMP_L103.sel(lon=lon_sel, lat=lat_sel, time=time_sel)

I think a clearer error message may be needed: when you do sel without indexing on certain dimensions, those are included in the resulting selection. It's possible for those to be of mixed incompatible types. Clearly to do to_array you need a numpy-friendly uniform type. The error should make this clearer.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   TypeError: invalid type promotion when reading multi-file dataset 157886730

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