issue_comments
14 rows where "created_at" is on date 2020-10-08 sorted by issue
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue ▼ | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
705878827 | https://github.com/simonw/datasette/issues/514#issuecomment-705878827 | https://api.github.com/repos/simonw/datasette/issues/514 | MDEyOklzc3VlQ29tbWVudDcwNTg3ODgyNw== | simonw 9599 | 2020-10-08T23:33:05Z | 2020-10-08T23:33:05Z | OWNER | Documentation is now live at https://docs.datasette.io/en/latest/deploying.html#running-datasette-using-systemd |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation with recommendations on running Datasette in production without using Docker 459397625 | |
705799046 | https://github.com/simonw/datasette/issues/865#issuecomment-705799046 | https://api.github.com/repos/simonw/datasette/issues/865 | MDEyOklzc3VlQ29tbWVudDcwNTc5OTA0Ng== | simonw 9599 | 2020-10-08T20:15:26Z | 2020-10-08T20:15:26Z | OWNER | Can anyone give me some detailed steps to reproduce for this issue? I think I need to set up my own local nginx or Apache proxy so I can really dig into this and figure out what's going on. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
base_url doesn't seem to work when adding criteria and clicking "apply" 644582921 | |
705887638 | https://github.com/simonw/datasette/issues/943#issuecomment-705887638 | https://api.github.com/repos/simonw/datasette/issues/943 | MDEyOklzc3VlQ29tbWVudDcwNTg4NzYzOA== | simonw 9599 | 2020-10-08T23:53:13Z | 2020-10-08T23:53:13Z | OWNER | I want this in Datasette 0.50, so I can use it in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
await datasette.client.get(path) mechanism for executing internal requests 681375466 | |
705874317 | https://github.com/simonw/datasette/issues/969#issuecomment-705874317 | https://api.github.com/repos/simonw/datasette/issues/969 | MDEyOklzc3VlQ29tbWVudDcwNTg3NDMxNw== | simonw 9599 | 2020-10-08T23:27:00Z | 2020-10-08T23:27:00Z | OWNER | I'm working on this now. Just ran this test and it worked (no longer showed my the warning message).
But... I wonder if it should automatically do this if it detects that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add --tar option to "datasette publish heroku" 705057955 | |
705874457 | https://github.com/simonw/datasette/issues/969#issuecomment-705874457 | https://api.github.com/repos/simonw/datasette/issues/969 | MDEyOklzc3VlQ29tbWVudDcwNTg3NDQ1Nw== | simonw 9599 | 2020-10-08T23:27:30Z | 2020-10-08T23:27:30Z | OWNER | For the moment I'm going to ship this as the |
{ "total_count": 2, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 1, "eyes": 0 } |
Add --tar option to "datasette publish heroku" 705057955 | |
705306117 | https://github.com/simonw/datasette/issues/997#issuecomment-705306117 | https://api.github.com/repos/simonw/datasette/issues/997 | MDEyOklzc3VlQ29tbWVudDcwNTMwNjExNw== | simonw 9599 | 2020-10-08T03:22:16Z | 2020-10-08T03:22:16Z | OWNER | Note #633 - you need to set WEB_CONCURRENCY=1 on Heroku for this to work. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation covering buildpack deployment 716988478 | |
705466873 | https://github.com/simonw/datasette/issues/997#issuecomment-705466873 | https://api.github.com/repos/simonw/datasette/issues/997 | MDEyOklzc3VlQ29tbWVudDcwNTQ2Njg3Mw== | simonw 9599 | 2020-10-08T10:02:02Z | 2020-10-08T10:02:02Z | OWNER | I asked about other hosts for these on Twitter https://twitter.com/simonw/status/1314042631949676544 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation covering buildpack deployment 716988478 | |
705883053 | https://github.com/simonw/datasette/issues/997#issuecomment-705883053 | https://api.github.com/repos/simonw/datasette/issues/997 | MDEyOklzc3VlQ29tbWVudDcwNTg4MzA1Mw== | simonw 9599 | 2020-10-08T23:36:55Z | 2020-10-08T23:36:55Z | OWNER | Docs are now live here: https://docs.datasette.io/en/latest/deploying.html#deploying-using-buildpacks |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation covering buildpack deployment 716988478 | |
705851211 | https://github.com/simonw/datasette/issues/998#issuecomment-705851211 | https://api.github.com/repos/simonw/datasette/issues/998 | MDEyOklzc3VlQ29tbWVudDcwNTg1MTIxMQ== | simonw 9599 | 2020-10-08T22:14:00Z | 2020-10-08T22:14:00Z | OWNER | I tried this out and it did cause one problem with plugins: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Wide tables should scroll horizontally within the page 717699884 | |
705851405 | https://github.com/simonw/datasette/issues/998#issuecomment-705851405 | https://api.github.com/repos/simonw/datasette/issues/998 | MDEyOklzc3VlQ29tbWVudDcwNTg1MTQwNQ== | simonw 9599 | 2020-10-08T22:14:31Z | 2020-10-08T22:14:31Z | OWNER | So maybe this is blocked on #987 and adding a new hook in the HTML which plugins like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Wide tables should scroll horizontally within the page 717699884 | |
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 | |
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 |
{ "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 | |
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:
https://datasette-issue-999.herokuapp.com/ returned an error, as expected - here's the relevant logs:
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 | |
705889120 | https://github.com/simonw/datasette/pull/1000#issuecomment-705889120 | https://api.github.com/repos/simonw/datasette/issues/1000 | MDEyOklzc3VlQ29tbWVudDcwNTg4OTEyMA== | simonw 9599 | 2020-10-08T23:59:01Z | 2020-10-08T23:59:01Z | OWNER | Needs tests and documentation. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
datasette.client internal requests mechanism 717746043 |
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, [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]);
issue 8