issue_comments
9 rows where "updated_at" is on date 2019-11-08 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 9 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
551361792 | https://github.com/simonw/datasette/issues/608#issuecomment-551361792 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM2MTc5Mg== | simonw 9599 | 2019-11-08T02:51:36Z | 2019-11-08T02:51:36Z | OWNER | A nice undocumented bonus feature of this change is that you can see a full list of your Cloud Run services by running |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551361489 | https://github.com/simonw/datasette/issues/608#issuecomment-551361489 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM2MTQ4OQ== | simonw 9599 | 2019-11-08T02:50:03Z | 2019-11-08T02:50:03Z | OWNER | Here's the new interface: ``` $ datasette publish cloudrun fixtures.db Please provide a service name for this deployment Using an existing service name will over-write it Your existing services: csvconf - created 2019-05-09T18:52:17.829Z - https://csvconf-j7hipcg4aq-uc.a.run.app fixtures - created 2019-11-08T02:22:14.048160Z - https://fixtures-j7hipcg4aq-uc.a.run.app Service name: ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551354256 | https://github.com/simonw/datasette/issues/608#issuecomment-551354256 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM1NDI1Ng== | simonw 9599 | 2019-11-08T02:17:50Z | 2019-11-08T02:17:50Z | OWNER | If the user specifies If they don't I'm going to ask them to enter a service manually (like happens at the moment) BUT I'm not going to give them a default and I'm going to show them the list of currently deployed services in the UI. I can get that by shelling out to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551353133 | https://github.com/simonw/datasette/issues/608#issuecomment-551353133 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM1MzEzMw== | simonw 9599 | 2019-11-08T02:13:10Z | 2019-11-08T02:13:10Z | OWNER | Right now you're not asked to select a service until AFTER the image has been compiled and pushed: ``` 7f41a4f30654: Pushed 60c95c8aac78: Pushed 5bad104547b2: Pushed latest: digest: sha256:7737f14d8490bbea49f29a750401fe2bf8a69f3da3bc2fd1ec5d1a031abf1b06 size: 2849 DONE ID CREATE_TIME DURATION SOURCE IMAGES STATUS 55b495e1-6862-464b-a99c-ee6eb1d8ac31 2019-11-08T02:08:14+00:00 35S gs://datasette-222320_cloudbuild/source/1573178893.56-8a2500be28d540e1baac7c6726c5c975.tgz gcr.io/datasette-222320/datasette (+1 more) SUCCESS ... Service name (datasette):
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551352256 | https://github.com/simonw/datasette/issues/608#issuecomment-551352256 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM1MjI1Ng== | simonw 9599 | 2019-11-08T02:09:43Z | 2019-11-08T02:09:43Z | OWNER | I'm going to improve the UI to make it less likely people will accidentally over-write an existing service instead. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551351754 | https://github.com/simonw/datasette/issues/608#issuecomment-551351754 | https://api.github.com/repos/simonw/datasette/issues/608 | MDEyOklzc3VlQ29tbWVudDU1MTM1MTc1NA== | simonw 9599 | 2019-11-08T02:07:40Z | 2019-11-08T02:07:40Z | OWNER | I'm nervous about how this will affect existing automation scripts that use this command. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improve UI of "datasette publish cloudrun" to reduce chances of accidentally over-writing a service 513008936 | |
551351578 | https://github.com/simonw/datasette/issues/616#issuecomment-551351578 | https://api.github.com/repos/simonw/datasette/issues/616 | MDEyOklzc3VlQ29tbWVudDU1MTM1MTU3OA== | simonw 9599 | 2019-11-08T02:06:56Z | 2019-11-08T02:06:56Z | OWNER | I think I know what's going on here. http://bases.vortex.media/-/versions says it's running http://teste-templates.herokuapp.com/-/versions (the one that works) is running I fixed a bug with FTS detection in 0.29.3 - https://datasette.readthedocs.io/en/stable/changelog.html#v0-29-3 fixed - #570 So upgrading to the latest release should fix this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Datasette FTS detection bug 518506242 | |
551349885 | https://github.com/simonw/datasette/issues/617#issuecomment-551349885 | https://api.github.com/repos/simonw/datasette/issues/617 | MDEyOklzc3VlQ29tbWVudDU1MTM0OTg4NQ== | simonw 9599 | 2019-11-08T01:59:43Z | 2019-11-08T02:00:52Z | OWNER | A clean starting point would be to refactor out the "take a table and a bunch of querystring parameters and turn them into a SQL query" portion. Added bonus to this: I've long wanted to be able to apply the various trimmings of the TableView (like faceting and foreign key expansion) to other arbitrary SQL queries. Splitting out the code that builds the SELECT query will go a long way to making that a reality. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Refactor TableView.data() method 519613116 | |
551349022 | https://github.com/simonw/datasette/issues/617#issuecomment-551349022 | https://api.github.com/repos/simonw/datasette/issues/617 | MDEyOklzc3VlQ29tbWVudDU1MTM0OTAyMg== | simonw 9599 | 2019-11-08T01:56:28Z | 2019-11-08T01:56:28Z | OWNER | Here's the current monstrosity: https://github.com/simonw/datasette/blob/f9c146b893856a48afa810ebcce1714f30d0d3a2/datasette/views/table.py#L210-L780 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Refactor TableView.data() method 519613116 |
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 3