issue_comments
23 rows where author_association = "OWNER", "created_at" is on date 2022-08-14, "updated_at" is on date 2022-08-14 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, created_at (date), updated_at (date)
user 1
- simonw · 23 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1214420905 | https://github.com/simonw/datasette/issues/1782#issuecomment-1214420905 | https://api.github.com/repos/simonw/datasette/issues/1782 | IC_kwDOBm6k_c5IYpep | simonw 9599 | 2022-08-14T17:40:45Z | 2022-08-14T17:40:45Z | OWNER | Now live here: https://docs.datasette.io/en/latest/changelog.html#v0-62 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release notes for Datasette 0.62 1338278056 | |
1214420523 | https://github.com/simonw/datasette/issues/1782#issuecomment-1214420523 | https://api.github.com/repos/simonw/datasette/issues/1782 | IC_kwDOBm6k_c5IYpYr | simonw 9599 | 2022-08-14T17:37:39Z | 2022-08-14T17:37:39Z | OWNER | I'm not going to write annotated release notes for this one. I think the existing release notes are detailed enough, and the most exciting parts of this release relate to Datasette Lite which I have already written about extensively (and linked from the new release notes). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release notes for Datasette 0.62 1338278056 | |
1214416491 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214416491 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYoZr | simonw 9599 | 2022-08-14T17:07:34Z | 2022-08-14T17:07:34Z | OWNER | Tested that with:
|
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214414471 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214414471 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYn6H | simonw 9599 | 2022-08-14T16:55:40Z | 2022-08-14T16:55:40Z | OWNER | Here's the start of the man page for SYNOPSIS
gcloud run deploy [[SERVICE] --namespace=NAMESPACE] [--args=[ARG,...]]
[--async] [--command=[COMMAND,...]] [--concurrency=CONCURRENCY]
[--cpu=CPU] [--ingress=INGRESS; default="all"]
[--max-instances=MAX_INSTANCES] [--memory=MEMORY]
[--min-instances=MIN_INSTANCES]
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214414320 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214414320 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYn3w | simonw 9599 | 2022-08-14T16:54:32Z | 2022-08-14T16:54:32Z | OWNER | (I deleted my |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214414013 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214414013 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYny9 | simonw 9599 | 2022-08-14T16:52:14Z | 2022-08-14T16:52:14Z | OWNER | Just tried this instead, and it still worked and deployed OK:
@fgregg I'm not able to replicate your deployment failure I'm afraid. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214413750 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214413750 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnu2 | simonw 9599 | 2022-08-14T16:50:08Z | 2022-08-14T16:50:08Z | OWNER | Just spotted this in the failing Actions workflow:
I tried that locally too but the deploy still succeeds. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214413534 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214413534 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnre | simonw 9599 | 2022-08-14T16:48:28Z | 2022-08-14T16:48:28Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214413419 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214413419 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnpr | simonw 9599 | 2022-08-14T16:47:27Z | 2022-08-14T16:47:27Z | OWNER | Maybe I need to upgrade:
Your current Google Cloud CLI version is: 378.0.0 You will be upgraded to version: 397.0.0 ┌─────────────────────────────────────────────────────────────────────────────┐ │ These components will be updated. │ ├─────────────────────────────────────────────────────┬────────────┬──────────┤ │ Name │ Version │ Size │ ├─────────────────────────────────────────────────────┼────────────┼──────────┤ │ BigQuery Command Line Tool │ 2.0.75 │ 1.6 MiB │ │ BigQuery Command Line Tool (Platform Specific) │ 2.0.75 │ < 1 MiB │ │ Cloud Storage Command Line Tool │ 5.11 │ 15.5 MiB │ │ Cloud Storage Command Line Tool (Platform Specific) │ 5.11 │ < 1 MiB │ │ Google Cloud CLI Core Libraries │ 2022.08.05 │ 24.3 MiB │ │ Google Cloud CLI Core Libraries (Platform Specific) │ 2022.08.05 │ < 1 MiB │ │ anthoscli │ 0.2.28 │ 48.0 MiB │ │ gcloud Alpha Commands │ 2022.08.05 │ < 1 MiB │ │ gcloud cli dependencies │ 2022.07.29 │ 11.2 MiB │ └─────────────────────────────────────────────────────┴────────────┴──────────┘ A lot has changed since your last upgrade. For the latest full release notes,
please visit:
https://cloud.google.com/sdk/release_notes
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214413161 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214413161 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnlp | simonw 9599 | 2022-08-14T16:45:36Z | 2022-08-14T16:45:36Z | OWNER | Tried duplicating this error locally but the following command succeeded when I expected it to fail:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214412382 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214412382 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnZe | simonw 9599 | 2022-08-14T16:40:02Z | 2022-08-14T16:40:02Z | OWNER | Here's the relevant part of the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214412135 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214412135 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnVn | simonw 9599 | 2022-08-14T16:38:08Z | 2022-08-14T16:38:08Z | OWNER | Actually I disagree that Datasette isn't setup to make use of container scaling: part of the idea behind the Baked Data pattern is that you can scale to handle effectively unlimited traffic by running multiple copies of your application, each with their own duplicate copy of the database. So I'm going to default maxScale to 10 and still let people customize it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214411951 | https://github.com/simonw/datasette/issues/1779#issuecomment-1214411951 | https://api.github.com/repos/simonw/datasette/issues/1779 | IC_kwDOBm6k_c5IYnSv | simonw 9599 | 2022-08-14T16:36:55Z | 2022-08-14T16:36:55Z | OWNER | I'm going to default maxscale to 2 but provide an extra command line option for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
google cloudrun updated their limits on maxscale based on memory and cpu count 1334628400 | |
1214411623 | https://github.com/simonw/datasette/issues/1728#issuecomment-1214411623 | https://api.github.com/repos/simonw/datasette/issues/1728 | IC_kwDOBm6k_c5IYnNn | simonw 9599 | 2022-08-14T16:34:20Z | 2022-08-14T16:34:20Z | OWNER | Here's what it looks like: I put the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writable canned queries fail with useless non-error against immutable databases 1218133366 | |
1214408558 | https://github.com/simonw/datasette/issues/1728#issuecomment-1214408558 | https://api.github.com/repos/simonw/datasette/issues/1728 | IC_kwDOBm6k_c5IYmdu | simonw 9599 | 2022-08-14T16:14:36Z | 2022-08-14T16:14:36Z | OWNER | Decision: I'm going to implement this:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writable canned queries fail with useless non-error against immutable databases 1218133366 | |
1214408429 | https://github.com/simonw/datasette/issues/1738#issuecomment-1214408429 | https://api.github.com/repos/simonw/datasette/issues/1738 | IC_kwDOBm6k_c5IYmbt | simonw 9599 | 2022-08-14T16:13:55Z | 2022-08-14T16:13:55Z | OWNER | That fixed both bugs. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"Cannot use _sort and _sort_desc at the same time" 1223527226 | |
1214407462 | https://github.com/simonw/datasette/issues/1738#issuecomment-1214407462 | https://api.github.com/repos/simonw/datasette/issues/1738 | IC_kwDOBm6k_c5IYmMm | simonw 9599 | 2022-08-14T16:08:23Z | 2022-08-14T16:09:49Z | OWNER | This isn't just a mobile display issue. https://latest.datasette.io/fixtures/compound_three_primary_keys?_sort_desc=pk1 - click "Apply" and each time it adds another This doesn't happen for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"Cannot use _sort and _sort_desc at the same time" 1223527226 | |
1214407104 | https://github.com/simonw/datasette/issues/1773#issuecomment-1214407104 | https://api.github.com/repos/simonw/datasette/issues/1773 | IC_kwDOBm6k_c5IYmHA | simonw 9599 | 2022-08-14T16:06:25Z | 2022-08-14T16:06:25Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
500 error if sorted by a column not in the ?_col= list 1318907685 | ||
1214405023 | https://github.com/simonw/datasette/issues/1768#issuecomment-1214405023 | https://api.github.com/repos/simonw/datasette/issues/1768 | IC_kwDOBm6k_c5IYlmf | simonw 9599 | 2022-08-14T15:54:11Z | 2022-08-14T15:54:11Z | OWNER | Also trying this locally:
https://issue-1768-j7hipcg4aq-uc.a.run.app/-/versions |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Upgrade to 3.10.6-slim-bullseye Docker base image 1296222572 | |
1214404690 | https://github.com/simonw/datasette/issues/1768#issuecomment-1214404690 | https://api.github.com/repos/simonw/datasette/issues/1768 | IC_kwDOBm6k_c5IYlhS | simonw 9599 | 2022-08-14T15:52:02Z | 2022-08-14T15:52:02Z | OWNER | Tested locally with:
And then:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Upgrade to 3.10.6-slim-bullseye Docker base image 1296222572 | |
1214403875 | https://github.com/simonw/datasette/issues/1768#issuecomment-1214403875 | https://api.github.com/repos/simonw/datasette/issues/1768 | IC_kwDOBm6k_c5IYlUj | simonw 9599 | 2022-08-14T15:46:49Z | 2022-08-14T15:46:49Z | OWNER | https://hub.docker.com/layers/python/library/python/3.10.6-slim-bullseye/images/sha256-cf85cd32e60184a94d88a0103c289d09024abffaa77680d116d7cc837668ea15?context=explore is the most recent - |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Upgrade to 3.10.6-slim-bullseye Docker base image 1296222572 | |
1214400698 | https://github.com/simonw/datasette/issues/1770#issuecomment-1214400698 | https://api.github.com/repos/simonw/datasette/issues/1770 | IC_kwDOBm6k_c5IYki6 | simonw 9599 | 2022-08-14T15:25:51Z | 2022-08-14T15:25:51Z | OWNER | I've tested this with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`handle_exception` plugin hook for custom error handling 1306492437 | |
1214399749 | https://github.com/simonw/datasette/issues/1781#issuecomment-1214399749 | https://api.github.com/repos/simonw/datasette/issues/1781 | IC_kwDOBm6k_c5IYkUF | simonw 9599 | 2022-08-14T15:20:09Z | 2022-08-14T15:20:09Z | OWNER | I'm going to promote it here too: https://docs.datasette.io/en/latest/getting_started.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ensure Datasette Lite is promoted in docs and README 1338137350 |
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