issue_comments: 705872767
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/datasette/issues/999#issuecomment-705872767 | https://api.github.com/repos/simonw/datasette/issues/999 | 705872767 | MDEyOklzc3VlQ29tbWVudDcwNTg3Mjc2Nw== | 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} | 717729056 |