{"html_url": "https://github.com/simonw/datasette/pull/2155#issuecomment-1737363182", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/2155", "id": 1737363182, "node_id": "IC_kwDOBm6k_c5njg7u", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2023-09-27T13:05:41Z", "updated_at": "2023-09-27T13:05:41Z", "author_association": "CONTRIBUTOR", "body": "I'm hitting the #2123 issue and I just patched my local version with this and it seems to work fine.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1865572575, "label": "Fix hupper.start_reloader entry point"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/1401#issuecomment-950150483", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1401", "id": 950150483, "node_id": "IC_kwDOBm6k_c44oiVT", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2021-10-23T13:09:10Z", "updated_at": "2021-10-23T13:09:10Z", "author_association": "CONTRIBUTOR", "body": "I think it's because of this in `app.css` \r\n\r\n```\r\nol,\r\nul {\r\n\tlist-style: none;\r\n}\r\n```\r\n\r\nhttps://github.com/simonw/datasette/blame/main/datasette/static/app.css#L35-L38\r\n\r\nYou could probably reinstate that by providing your own CSS.\r\nhttps://docs.datasette.io/en/0.24/custom_templates.html#custom-css-and-javascript", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 950664971, "label": "unordered list is not rendering bullet points in description_html on database page"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/pull/653#issuecomment-582106085", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/653", "id": 582106085, "node_id": "MDEyOklzc3VlQ29tbWVudDU4MjEwNjA4NQ==", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2020-02-04T20:43:43Z", "updated_at": "2020-02-04T20:43:43Z", "author_association": "CONTRIBUTOR", "body": "but this also doesn't have to land at all if it doesn't match your use case. ", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 541331755, "label": "allow leading comments in SQL input field"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/pull/653#issuecomment-582105810", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/653", "id": 582105810, "node_id": "MDEyOklzc3VlQ29tbWVudDU4MjEwNTgxMA==", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2020-02-04T20:43:01Z", "updated_at": "2020-02-04T20:43:01Z", "author_association": "CONTRIBUTOR", "body": "I *think* the existing code will be OK even if I strip the lines in the middle of a new line delimited string.\r\n\r\nIt's only used for the validation, SQLite handles the `--` just fine and the whole SQL textarea still gets sent once it passes validation.\r\n\r\nI can add your test case to my branch later this evening though.\r\n", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 541331755, "label": "allow leading comments in SQL input field"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/329#issuecomment-422915450", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/329", "id": 422915450, "node_id": "MDEyOklzc3VlQ29tbWVudDQyMjkxNTQ1MA==", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2018-09-19T18:45:02Z", "updated_at": "2018-09-20T10:50:50Z", "author_association": "CONTRIBUTOR", "body": "That works for me. Was able to pull the public image and no errors on my canned query. (~although a small rendering bug. I'll create an issue and if I have time today, a PR to fix~ this turned out to be my error.)\r\nThanks for the quick response!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 336465018, "label": "Travis should push tagged images to Docker Hub for each release"}, "performed_via_github_app": null} {"html_url": "https://github.com/simonw/datasette/issues/329#issuecomment-422821483", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/329", "id": 422821483, "node_id": "MDEyOklzc3VlQ29tbWVudDQyMjgyMTQ4Mw==", "user": {"value": 418191, "label": "jaywgraves"}, "created_at": "2018-09-19T14:17:42Z", "updated_at": "2018-09-19T14:17:42Z", "author_association": "CONTRIBUTOR", "body": "I'm using the docker image (0.23.2) and notice some differences/bugs between the docs and the published version with canned queries. (submitted a tiny doc fix also)\r\n\r\nI was able to build the docker container locally using `master` and I'm using that for now.\r\nWould it be possible to manually push 0.24 to DockerHub until the TravisCI stuff is fixed?\r\n\r\nI would like to run this in our Kubernetes cluster but don't want to publish a version in our internal registry if I don't have to.\r\nThanks!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 336465018, "label": "Travis should push tagged images to Docker Hub for each release"}, "performed_via_github_app": null}