issue_comments

Table actions

3 rows where author_association = "OWNER", issue = 717729056 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • simonw · 3 ✖

issue 1

  • Datasette should default to running Uvicorn with workers=1 · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
705872767 https://github.com/simonw/datasette/issues/999#issuecomment-705872767 https://api.github.com/repos/simonw/datasette/issues/999 MDEyOklzc3VlQ29tbWVudDcwNTg3Mjc2Nw== simonw 9599 2020-10-08T23:21:36Z 2020-10-08T23:21:36Z OWNER

I ran this to prove that it breaks:

datasette publish heroku fixtures.db -n datasette-issue-999

https://datasette-issue-999.herokuapp.com/ returned an error, as expected - here's the relevant logs:

$ heroku logs --tail -a datasette-issue-999 2020-10-08T23:19:01.065103+00:00 heroku[web.1]: Starting process with command `datasette serve --host 0.0.0.0 -i fixtures.db --cors --port 22329 --inspect-file inspect-data.json` 2020-10-08T23:19:05.381374+00:00 app[web.1]: WARNING: You must pass the application as an import string to enable 'reload' or 'workers'. 2020-10-08T23:19:05.617519+00:00 heroku[web.1]: Process exited with status 1 2020-10-08T23:19:05.690673+00:00 heroku[web.1]: State changed from starting to crashed Then I deployed again using:

datasette publish heroku fixtures.db -n datasette-issue-999 --branch=main

This time the deploy worked OK.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette should default to running Uvicorn with workers=1 717729056  
705871513 https://github.com/simonw/datasette/issues/999#issuecomment-705871513 https://api.github.com/repos/simonw/datasette/issues/999 MDEyOklzc3VlQ29tbWVudDcwNTg3MTUxMw== simonw 9599 2020-10-08T23:17:31Z 2020-10-08T23:17:31Z OWNER

This does mean that any deploys to Heroku will fail with an error until this code has been released in a non-alpha Datasette release (unless you use --branch=main) - so I should ship this as soon as possible.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette should default to running Uvicorn with workers=1 717729056  
705869129 https://github.com/simonw/datasette/issues/999#issuecomment-705869129 https://api.github.com/repos/simonw/datasette/issues/999 MDEyOklzc3VlQ29tbWVudDcwNTg2OTEyOQ== simonw 9599 2020-10-08T23:09:41Z 2020-10-08T23:09:41Z OWNER

I want to fix this now because then I don't need to document it in #997.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette should default to running Uvicorn with workers=1 717729056  

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,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);