issue_comments
15 rows where issue = 565064079 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- --dirs option for scanning directories for SQLite databases · 15 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
604667029 | https://github.com/simonw/datasette/pull/672#issuecomment-604667029 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDYwNDY2NzAyOQ== | simonw 9599 | 2020-03-26T20:26:46Z | 2020-03-26T20:26:46Z | OWNER | I think I can tell what the current file limit is like so: ``` In [1]: import resource In [2]: resource.getrlimit(resource.RLIMIT_NOFILE) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
604665229 | https://github.com/simonw/datasette/pull/672#issuecomment-604665229 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDYwNDY2NTIyOQ== | simonw 9599 | 2020-03-26T20:22:48Z | 2020-03-26T20:22:48Z | OWNER | I also eventually get this error:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
604569063 | https://github.com/simonw/datasette/pull/672#issuecomment-604569063 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDYwNDU2OTA2Mw== | simonw 9599 | 2020-03-26T17:32:06Z | 2020-03-26T17:32:06Z | OWNER | While running it against a nested directory with a TON of databases I kept seeing errors like this:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
604561639 | https://github.com/simonw/datasette/pull/672#issuecomment-604561639 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDYwNDU2MTYzOQ== | simonw 9599 | 2020-03-26T17:22:07Z | 2020-03-26T17:22:07Z | OWNER | Here's the new utility function I should be using to verify database files that I find: https://github.com/simonw/datasette/blob/6aa516d82dea9885cb4db8d56ec2ccfd4cd9b840/datasette/utils/init.py#L773-L787 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586441484 | https://github.com/simonw/datasette/pull/672#issuecomment-586441484 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjQ0MTQ4NA== | simonw 9599 | 2020-02-14T19:34:25Z | 2020-02-14T19:34:25Z | OWNER | I've figured out how to tell if a database is safe to open or not:
Run this against a SpatiaLite database and you get the following:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586112662 | https://github.com/simonw/datasette/pull/672#issuecomment-586112662 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjExMjY2Mg== | simonw 9599 | 2020-02-14T06:05:27Z | 2020-02-14T06:05:27Z | OWNER | It think the fix is to use an old-fashioned |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586111619 | https://github.com/simonw/datasette/pull/672#issuecomment-586111619 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjExMTYxOQ== | simonw 9599 | 2020-02-14T06:01:24Z | 2020-02-14T06:01:24Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | ||
586111102 | https://github.com/simonw/datasette/pull/672#issuecomment-586111102 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjExMTEwMg== | simonw 9599 | 2020-02-14T05:59:24Z | 2020-02-14T06:00:36Z | OWNER | Interesting new problem: hitting Ctrl+C no longer terminates the problem provided that https://stackoverflow.com/questions/49992329/the-workers-in-threadpoolexecutor-is-not-really-daemon has clues. The workers are only meant to exit when their worker queues are empty. But... I want to run the worker every 10 seconds. How do I do that without having it loop forever and hence never quit? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586109784 | https://github.com/simonw/datasette/pull/672#issuecomment-586109784 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjEwOTc4NA== | simonw 9599 | 2020-02-14T05:53:50Z | 2020-02-14T05:54:21Z | OWNER | ... cheating like this seems to work:
Seems to work in my testing. Wish I could prove it with a unit test though. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586109238 | https://github.com/simonw/datasette/pull/672#issuecomment-586109238 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjEwOTIzOA== | simonw 9599 | 2020-02-14T05:51:12Z | 2020-02-14T05:51:12Z | OWNER | ... or maybe I can cheat and wrap the access to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586109032 | https://github.com/simonw/datasette/pull/672#issuecomment-586109032 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjEwOTAzMg== | simonw 9599 | 2020-02-14T05:50:15Z | 2020-02-14T05:50:15Z | OWNER | So I need to ensure the Mainly I need to ensure that it is locked during iterations over it, then unlocked at the end. Trickiest part is probably ensuring there is a test that proves this is working - I feel like I got lucky encountering that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586107989 | https://github.com/simonw/datasette/pull/672#issuecomment-586107989 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjEwNzk4OQ== | simonw 9599 | 2020-02-14T05:45:12Z | 2020-02-14T05:45:12Z | OWNER | I tried running the Makes sense - I had a thread that added an item to that dictionary right while the homepage was attempting to run this code: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586069529 | https://github.com/simonw/datasette/pull/672#issuecomment-586069529 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjA2OTUyOQ== | simonw 9599 | 2020-02-14T02:37:17Z | 2020-02-14T02:37:17Z | OWNER | Another problem: if any of the found databases use SpatiaLite then Datasette will fail to start at all. It should skip them instead. The |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586068095 | https://github.com/simonw/datasette/pull/672#issuecomment-586068095 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjA2ODA5NQ== | simonw 9599 | 2020-02-14T02:30:37Z | 2020-02-14T02:30:46Z | OWNER | This can take a LONG time to run, and at the moment it's blocking and prevents Datasette from starting up. It would be much better if this ran in a thread, or an asyncio task. Probably have to be a thread because there's no easy |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 | |
586067794 | https://github.com/simonw/datasette/pull/672#issuecomment-586067794 | https://api.github.com/repos/simonw/datasette/issues/672 | MDEyOklzc3VlQ29tbWVudDU4NjA2Nzc5NA== | simonw 9599 | 2020-02-14T02:29:16Z | 2020-02-14T02:29:16Z | OWNER | One design issue: how to pick neat unique names for database files in a file hierarchy? Here's what I have so far: For these files:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
--dirs option for scanning directories for SQLite databases 565064079 |
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]);
user 1