issue_comments

Table actions

3 rows where issue = 256557897 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 3

issue 1

  • When reporting errors, note what value was invalid and why · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
522436770 https://github.com/pydata/xarray/issues/1566#issuecomment-522436770 https://api.github.com/repos/pydata/xarray/issues/1566 MDEyOklzc3VlQ29tbWVudDUyMjQzNjc3MA== Zac-HD 12229877 2019-08-19T06:50:15Z 2019-08-19T06:50:15Z CONTRIBUTOR

It's at least out of date, and doesn't appear to be helpful, so I'm happy to close this issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   When reporting errors, note what value was invalid and why 256557897
522418287 https://github.com/pydata/xarray/issues/1566#issuecomment-522418287 https://api.github.com/repos/pydata/xarray/issues/1566 MDEyOklzc3VlQ29tbWVudDUyMjQxODI4Nw== stale[bot] 26384082 2019-08-19T05:31:01Z 2019-08-19T05:31:01Z 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 or remove the stale label; 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
}
   When reporting errors, note what value was invalid and why 256557897
328399848 https://github.com/pydata/xarray/issues/1566#issuecomment-328399848 https://api.github.com/repos/pydata/xarray/issues/1566 MDEyOklzc3VlQ29tbWVudDMyODM5OTg0OA== shoyer 1217238 2017-09-11T02:30:07Z 2017-09-11T02:30:07Z MEMBER

Thanks for raising this concern. I think we have been gradually improving the quality of our error messages, but I agree that we still have a large opportunity for improvement.

This also one area where someone inexperienced can have a big impact. Experienced developers are likely to gloss over confusing error messages (or not see them at all) because they already understand what's going on. Any GitHub issues you open when you encounter an error that was not as helpful as possible would be gratefully appreciated.

I've been trying to collect these under the error reporting tag: https://github.com/pydata/xarray/issues?q=is%3Aopen+is%3Aissue+label%3A%22error+reporting%22

Our contributing guidelines (see https://github.com/pydata/xarray/pull/1485) should make it clear that full code to reproduce is not required for such cases.

Potentially it would also make sense to audit some of our code line by line to check that error messages are as good as possible.

cc @jhamman 

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   When reporting errors, note what value was invalid and why 256557897

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