issue_comments
2 rows where issue = 1200356907 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- RTD concurrency limit · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1102144010 | https://github.com/pydata/xarray/issues/6473#issuecomment-1102144010 | https://api.github.com/repos/pydata/xarray/issues/6473 | IC_kwDOAMm_X85BsWIK | max-sixty 5635139 | 2022-04-19T06:29:24Z | 2022-04-19T06:29:24Z | MEMBER | This seems resolved now |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD concurrency limit 1200356907 | |
1095403839 | https://github.com/pydata/xarray/issues/6473#issuecomment-1095403839 | https://api.github.com/repos/pydata/xarray/issues/6473 | IC_kwDOAMm_X85BSok_ | max-sixty 5635139 | 2022-04-11T18:27:23Z | 2022-04-11T18:27:23Z | MEMBER | Looks like if we want to go to 6 concurrent builds, it's $250/ month: https://readthedocs.com/pricing/ This issue suggests others are having the same issue: https://github.com/readthedocs/readthedocs.org/issues/9014, but that it's not intentional. So maybe let's see if it corrects. The most important thing is that it doesn't keep retrying commits which are no longer the head of a branch — otherwise we could fall permanently behind. I know others have done some work to ensure GHA operates correctly here. Is anyone familiar with whether this happens in RTD? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD concurrency limit 1200356907 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1