issue_comments

Table actions

4 rows where issue = 1598266728 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 2

issue 1

  • broken documentation link · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1464106326 https://github.com/pydata/xarray/issues/7556#issuecomment-1464106326 https://api.github.com/repos/pydata/xarray/issues/7556 IC_kwDOAMm_X85XRH1W nashira26 32673772 2023-03-10T17:05:37Z 2023-03-10T17:05:37Z NONE

I am an Outreachy intern and I would love to contribute by updating this documentation.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   broken documentation link 1598266728
1459792052 https://github.com/pydata/xarray/issues/7556#issuecomment-1459792052 https://api.github.com/repos/pydata/xarray/issues/7556 IC_kwDOAMm_X85XAqi0 keewis 14808389 2023-03-08T09:01:53Z 2023-03-08T09:01:53Z MEMBER

Since the label exists and the spelling is correct, I think the only thing we need to do here is use the appropriate sphinx role. To figure out which one, we can either manually search the intersphinx registry using bash $ python -m sphinx.ext.intersphinx https://docs.xarray.dev/en/latest/objects.inv | less (which is a bit tedious because that particular section is pretty big, and we need to have sphinx installed)

or we can use sphobjinv: ```bash $ sphobjinv suggest -u https://docs.xarray.dev/en/latest/ datetime_component_indexing

Attempting https://docs.xarray.dev/en/latest ... ... no recognized inventory. Attempting "https://docs.xarray.dev/en/latest/objects.inv" ... ... inventory found.

The intersphinx_mapping for this docset is LIKELY:

(https://docs.xarray.dev/en/latest/, None)

Project: xarray Version: 2023.2.1.dev19

7468 objects in inventory.

1 result found at/above current threshold of 75.

:std:label:datetime_component_indexing `` which helpfully tells us the correct link (though I think we can use:label:instead of:std:label:`)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   broken documentation link 1598266728
1459595302 https://github.com/pydata/xarray/issues/7556#issuecomment-1459595302 https://api.github.com/repos/pydata/xarray/issues/7556 IC_kwDOAMm_X85W_6gm JoyNyuguto 87148605 2023-03-08T06:05:59Z 2023-03-08T06:05:59Z NONE

@TomNicholas I amJoy Nyuguto from Outreachy It appears that the link you provided is no longer available on the xarray documentation site. It's possible that the page has been removed or the URL has been updated.

I recommend checking the xarray documentation home page or using the search bar to locate the page you're looking for.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   broken documentation link 1598266728
1458901771 https://github.com/pydata/xarray/issues/7556#issuecomment-1458901771 https://api.github.com/repos/pydata/xarray/issues/7556 IC_kwDOAMm_X85W9RML TomNicholas 35968931 2023-03-07T21:31:16Z 2023-03-07T21:31:16Z MEMBER

Thanks for reporting @arfriedman .

The link is supposed to be referring to the section immediately following the Datetime Indexing subsection. I think the underscores in datetime_component_indexing might be what's breaking the link.

If anyone wants to make their first small contribution to xarray this would be a great start!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   broken documentation link 1598266728

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