issue_comments
9 rows where "created_at" is on date 2021-05-24 and "updated_at" is on date 2021-05-24 sorted by node_id
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions
id | html_url | issue_url | node_id ▼ | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
846659272 | https://github.com/simonw/datasette/issues/615#issuecomment-846659272 | https://api.github.com/repos/simonw/datasette/issues/615 | MDEyOklzc3VlQ29tbWVudDg0NjY1OTI3Mg== | simonw 9599 | 2021-05-24T00:44:47Z | 2021-05-24T00:44:47Z | OWNER | I can't think of any good reasons to support passing the same column twice `?col=airline&_col=airline` so I'm going to de-duplicate and silently ignore the second one. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ?_col= and ?_nocol= support for toggling columns on table view 517451234 | |
846660103 | https://github.com/simonw/datasette/issues/615#issuecomment-846660103 | https://api.github.com/repos/simonw/datasette/issues/615 | MDEyOklzc3VlQ29tbWVudDg0NjY2MDEwMw== | simonw 9599 | 2021-05-24T00:47:00Z | 2021-05-24T00:47:00Z | OWNER | > Here's a bug: removing the `rowid` column returns an error. Removing the `rowid` column should work. We can continue to show the `Link` column, ensuring users can still navigate to the row page for each row. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ?_col= and ?_nocol= support for toggling columns on table view 517451234 | |
846668419 | https://github.com/simonw/datasette/issues/615#issuecomment-846668419 | https://api.github.com/repos/simonw/datasette/issues/615 | MDEyOklzc3VlQ29tbWVudDg0NjY2ODQxOQ== | simonw 9599 | 2021-05-24T01:14:27Z | 2021-05-24T01:14:27Z | OWNER | I tried allowing the removal of `rowid` and got this exception: ``` File "/Users/simon/Dropbox/Development/datasette/datasette/views/table.py", line 831, in extra_template display_columns, display_rows = await self.display_columns_and_rows( File "/Users/simon/Dropbox/Development/datasette/datasette/views/table.py", line 163, in display_columns_and_rows pk_path = path_from_row_pks(row, pks, not pks, False) File "/Users/simon/Dropbox/Development/datasette/datasette/utils/__init__.py", line 82, in path_from_row_pks bits = [row["rowid"]] IndexError: No item with that key ``` I'm going to disable the removal of `rowid` - or indeed any of the primary keys, since they are needed to construct the row permalink. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ?_col= and ?_nocol= support for toggling columns on table view 517451234 | |
847240470 | https://github.com/simonw/datasette/issues/1327#issuecomment-847240470 | https://api.github.com/repos/simonw/datasette/issues/1327 | MDEyOklzc3VlQ29tbWVudDg0NzI0MDQ3MA== | simonw 9599 | 2021-05-24T18:21:44Z | 2021-05-24T18:21:44Z | OWNER | I'm having trouble replicating this - I tried the following `metadata.json` in my local environment and it displayed correctly: ```json { "title": "မြန်မာစာ (" } ``` What operating system are you using here? Is there a chance that your `metadata.json` file is saved in a text encoding other than utf-8? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support Unicode characters in metadata.json 892457208 | |
847271122 | https://github.com/simonw/datasette/issues/1327#issuecomment-847271122 | https://api.github.com/repos/simonw/datasette/issues/1327 | MDEyOklzc3VlQ29tbWVudDg0NzI3MTEyMg== | GmGniap 20846286 | 2021-05-24T19:10:21Z | 2021-05-24T19:10:21Z | NONE | wow, thanks a lot @simonw , problem is solved. I converted my current json file into utf-8 format with Python script. It's working now. I'm using with Window 10. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Support Unicode characters in metadata.json 892457208 | |
847223853 | https://github.com/simonw/datasette/issues/1320#issuecomment-847223853 | https://api.github.com/repos/simonw/datasette/issues/1320 | MDEyOklzc3VlQ29tbWVudDg0NzIyMzg1Mw== | simonw 9599 | 2021-05-24T17:51:12Z | 2021-05-24T17:51:12Z | OWNER | This is a good catch, thank you. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Can't use apt-get in Dockerfile when using datasetteproj/datasette as base 884952179 | |
847230866 | https://github.com/simonw/datasette/issues/1320#issuecomment-847230866 | https://api.github.com/repos/simonw/datasette/issues/1320 | MDEyOklzc3VlQ29tbWVudDg0NzIzMDg2Ng== | simonw 9599 | 2021-05-24T18:03:29Z | 2021-05-24T18:03:29Z | OWNER | ``` root@33c269900821:/# du -h /var/lib/dpkg 6.3M /var/lib/dpkg/info 24K /var/lib/dpkg/triggers 4.0K /var/lib/dpkg/updates 20K /var/lib/dpkg/alternatives 4.0K /var/lib/dpkg/parts 6.7M /var/lib/dpkg ``` So `/var/lib/dpkg/info` is most of the space, I'll try just deleting that. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Can't use apt-get in Dockerfile when using datasetteproj/datasette as base 884952179 | |
847232547 | https://github.com/simonw/datasette/issues/1320#issuecomment-847232547 | https://api.github.com/repos/simonw/datasette/issues/1320 | MDEyOklzc3VlQ29tbWVudDg0NzIzMjU0Nw== | simonw 9599 | 2021-05-24T18:06:32Z | 2021-05-24T18:06:32Z | OWNER | I'm testing tweaks to the Dockerfile by editing it and running: ``` docker build . -t datasette-057a0 --build-arg VERSION=0.57a0 ``` Then running this to inspect the new image: ``` docker run -it -p 8001:8001 datasette-057a0 bash ``` After changing that line to `rm -rf /var/lib/dpkg/info/*` I can run `apt-get` successfully from inside that bash prompt: ``` # apt-get update # apt-get install ripgrep # rg --version ripgrep 12.1.1 ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Can't use apt-get in Dockerfile when using datasetteproj/datasette as base 884952179 | |
847237524 | https://github.com/simonw/datasette/issues/1320#issuecomment-847237524 | https://api.github.com/repos/simonw/datasette/issues/1320 | MDEyOklzc3VlQ29tbWVudDg0NzIzNzUyNA== | simonw 9599 | 2021-05-24T18:15:56Z | 2021-05-24T18:15:56Z | OWNER | Added some new documentation about that here: https://github.com/simonw/datasette/blob/c0a748e5c3f498fa8c139b420d07dd3dea612379/docs/installation.rst#installing-plugins | {"total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Can't use apt-get in Dockerfile when using datasetteproj/datasette as base 884952179 |
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]);
updated_at (date) 1 ✖