issue_comments
8,883 rows where user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: issue
user 1
- simonw · 2,678 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
643676314 | https://github.com/simonw/datasette/issues/843#issuecomment-643676314 | https://api.github.com/repos/simonw/datasette/issues/843 | MDEyOklzc3VlQ29tbWVudDY0MzY3NjMxNA== | simonw 9599 | 2020-06-13T20:47:37Z | 2020-06-13T20:47:37Z | OWNER | I can use this action: https://github.com/codecov/codecov-action |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Configure codecov.io 638229448 | |
643676069 | https://github.com/simonw/datasette/issues/843#issuecomment-643676069 | https://api.github.com/repos/simonw/datasette/issues/843 | MDEyOklzc3VlQ29tbWVudDY0MzY3NjA2OQ== | simonw 9599 | 2020-06-13T20:45:29Z | 2020-06-13T20:45:29Z | OWNER | I set up https://codecov.io/gh/simonw/datasette/settings and added a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Configure codecov.io 638229448 | |
643663005 | https://github.com/simonw/datasette/issues/842#issuecomment-643663005 | https://api.github.com/repos/simonw/datasette/issues/842 | MDEyOklzc3VlQ29tbWVudDY0MzY2MzAwNQ== | simonw 9599 | 2020-06-13T18:51:57Z | 2020-06-13T18:51:57Z | OWNER | Two potential designs:
I fee the first would be easier to implement. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Magic parameters for canned queries 638212085 | |
643661125 | https://github.com/simonw/datasette/issues/841#issuecomment-643661125 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY2MTEyNQ== | simonw 9599 | 2020-06-13T18:35:30Z | 2020-06-13T18:36:50Z | OWNER | I ran export CODECOV_TOKEN="f7935cad...", then ran this:
x> No CI provider detected. Testing inside Docker? http://docs.codecov.io/docs/testing-with-docker Testing with Tox? https://docs.codecov.io/docs/python#section-testing-with-tox project root: . --> token set from env Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml ==> Running gcov in . (disable via -X gcov) ==> Searching for coverage reports in: + . -> Found 1 reports ==> Detecting git/mercurial file structure ==> Reading reports + ./coverage.xml bytes=139174 ==> Appending adjustments https://docs.codecov.io/docs/fixing-reports -> No adjustments found ==> Gzipping contents ==> Uploading reports url: https://codecov.io query: branch=master&commit=0e49842e227a0f1f69d48108c87d17fe0379e548&build=&build_url=&name=&tag=&slug=simonw%2Fdatasette&service=&flags=&pr=&job= -> Pinging Codecov https://codecov.io/upload/v4?package=bash-20200602-f809a24&token=secret&branch=master&commit=0e49842e227a0f1f69d48108c87d17fe0379e548&build=&build_url=&name=&tag=&slug=simonw%2Fdatasette&service=&flags=&pr=&job= -> Uploading -> View reports at https://codecov.io/github/simonw/datasette/commit/0e49842e227a0f1f69d48108c87d17fe0379e548 ``` But https://codecov.io/github/simonw/datasette/commit/0e49842e227a0f1f69d48108c87d17fe0379e548 is a 404, so it doesn't seem to have worked? UPDATE: It works now, took about 30 seconds before the report showed up at that URL. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643660757 | https://github.com/simonw/datasette/issues/841#issuecomment-643660757 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY2MDc1Nw== | simonw 9599 | 2020-06-13T18:32:20Z | 2020-06-13T18:32:20Z | OWNER | Looking at options for publishing coverage reports: I'm going to try https://codecov.io/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643660427 | https://github.com/simonw/datasette/issues/841#issuecomment-643660427 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY2MDQyNw== | simonw 9599 | 2020-06-13T18:29:30Z | 2020-06-13T18:29:36Z | OWNER | This one looks easy enough to fix: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643658036 | https://github.com/simonw/datasette/issues/841#issuecomment-643658036 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY1ODAzNg== | simonw 9599 | 2020-06-13T18:08:13Z | 2020-06-13T18:08:13Z | OWNER | From digging through that report it looks like the majority stuff that isn't fully covered is corner-cases... which are the kind of things I really do want the tests to catch. I'm not entirely ready to commit to 100%, but I'm going to start digging through and seeing how close I can get. If I can get to 98% (I'm on 91% already) I may as well push all the way to 100. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643657287 | https://github.com/simonw/datasette/issues/841#issuecomment-643657287 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY1NzI4Nw== | simonw 9599 | 2020-06-13T18:01:39Z | 2020-06-13T18:01:39Z | OWNER | Added |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643656053 | https://github.com/simonw/datasette/issues/841#issuecomment-643656053 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY1NjA1Mw== | simonw 9599 | 2020-06-13T17:50:34Z | 2020-06-13T17:50:34Z | OWNER | Added a datasette/init.py 3 0 100% datasette/main.py 3 3 0% datasette/actor_auth_cookie.py 19 3 84% datasette/app.py 499 27 95% datasette/cli.py 157 45 71% datasette/database.py 233 17 93% datasette/default_permissions.py 39 0 100% datasette/facets.py 209 24 89% datasette/filters.py 122 7 94% datasette/hookspecs.py 19 0 100% datasette/inspect.py 37 23 38% datasette/plugins.py 34 6 82% datasette/publish/init.py 0 0 100% datasette/publish/cloudrun.py 55 2 96% datasette/publish/common.py 19 1 95% datasette/publish/heroku.py 95 13 86% datasette/renderer.py 63 4 94% datasette/sql_functions.py 4 0 100% datasette/tracer.py 85 16 81% datasette/utils/init.py 503 31 94% datasette/utils/asgi.py 253 25 90% datasette/version.py 4 0 100% datasette/views/init.py 0 0 100% datasette/views/base.py 288 19 93% datasette/views/database.py 120 2 98% datasette/views/index.py 57 2 96% datasette/views/special.py 72 16 78% datasette/views/table.py 418 18 96% TOTAL 3410 304 91% ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643655108 | https://github.com/simonw/datasette/issues/841#issuecomment-643655108 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzY1NTEwOA== | simonw 9599 | 2020-06-13T17:43:15Z | 2020-06-13T17:43:15Z | OWNER | Using https://pypi.org/project/pytest-cov/ and running datasette/init.py 3 0 100% datasette/main.py 3 3 0% datasette/_version.py 277 152 45% datasette/actor_auth_cookie.py 19 3 84% datasette/app.py 499 27 95% datasette/cli.py 157 45 71% datasette/database.py 233 17 93% datasette/default_permissions.py 39 0 100% datasette/facets.py 209 24 89% datasette/filters.py 122 7 94% datasette/hookspecs.py 19 0 100% datasette/inspect.py 37 23 38% datasette/plugins.py 34 6 82% datasette/publish/init.py 0 0 100% datasette/publish/cloudrun.py 55 2 96% datasette/publish/common.py 19 1 95% datasette/publish/heroku.py 95 13 86% datasette/renderer.py 63 4 94% datasette/sql_functions.py 4 0 100% datasette/tracer.py 85 16 81% datasette/utils/init.py 503 31 94% datasette/utils/asgi.py 253 25 90% datasette/utils/shutil_backport.py 44 40 9% datasette/version.py 4 0 100% datasette/views/init.py 0 0 100% datasette/views/base.py 288 19 93% datasette/views/database.py 120 2 98% datasette/views/index.py 57 2 96% datasette/views/special.py 72 16 78% datasette/views/table.py 418 18 96% TOTAL 3731 496 87% ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643648359 | https://github.com/simonw/datasette/issues/834#issuecomment-643648359 | https://api.github.com/repos/simonw/datasette/issues/834 | MDEyOklzc3VlQ29tbWVudDY0MzY0ODM1OQ== | simonw 9599 | 2020-06-13T16:47:29Z | 2020-06-13T16:47:29Z | OWNER | Implementing this is proving surprisingly tricky, because of the need to be able to optionally I could switch to using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
startup() plugin hook 637342551 | |
643576372 | https://github.com/simonw/datasette/issues/841#issuecomment-643576372 | https://api.github.com/repos/simonw/datasette/issues/841 | MDEyOklzc3VlQ29tbWVudDY0MzU3NjM3Mg== | simonw 9599 | 2020-06-13T06:08:34Z | 2020-06-13T06:08:34Z | OWNER | Starlette achieves this. https://github.com/encode/starlette |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Research feasibility of 100% test coverage 638104520 | |
643510240 | https://github.com/simonw/datasette/issues/834#issuecomment-643510240 | https://api.github.com/repos/simonw/datasette/issues/834 | MDEyOklzc3VlQ29tbWVudDY0MzUxMDI0MA== | simonw 9599 | 2020-06-12T22:40:26Z | 2020-06-12T22:40:26Z | OWNER | Another use-case: plugins that need their own database with the correct tables. They can write to the database on startup to create their tables. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
startup() plugin hook 637342551 | |
643509358 | https://github.com/simonw/datasette/issues/834#issuecomment-643509358 | https://api.github.com/repos/simonw/datasette/issues/834 | MDEyOklzc3VlQ29tbWVudDY0MzUwOTM1OA== | simonw 9599 | 2020-06-12T22:36:37Z | 2020-06-12T22:36:37Z | OWNER | This should be able to optionally return an async function which is then awaited. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
startup() plugin hook 637342551 | |
643501428 | https://github.com/simonw/datasette/issues/805#issuecomment-643501428 | https://api.github.com/repos/simonw/datasette/issues/805 | MDEyOklzc3VlQ29tbWVudDY0MzUwMTQyOA== | simonw 9599 | 2020-06-12T22:06:08Z | 2020-06-12T22:06:08Z | OWNER | This needs the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writable canned queries live demo on Glitch 632724154 | |
643501064 | https://github.com/simonw/datasette/issues/834#issuecomment-643501064 | https://api.github.com/repos/simonw/datasette/issues/834 | MDEyOklzc3VlQ29tbWVudDY0MzUwMTA2NA== | simonw 9599 | 2020-06-12T22:04:43Z | 2020-06-12T22:04:43Z | OWNER | Another use-case for this: I want to use the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
startup() plugin hook 637342551 | |
643454625 | https://github.com/simonw/datasette/issues/840#issuecomment-643454625 | https://api.github.com/repos/simonw/datasette/issues/840 | MDEyOklzc3VlQ29tbWVudDY0MzQ1NDYyNQ== | simonw 9599 | 2020-06-12T19:47:38Z | 2020-06-12T19:47:53Z | OWNER | Another problem: what to display in the "you are logged in as", since we don't dictate an actor design. I'm going to use a includes template for this that can easily be over-ridden by administrators or by plugins. The default will look for the first available of the following keys:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Log out mechanism for clearing ds_actor cookie 637966833 | |
643453128 | https://github.com/simonw/datasette/issues/840#issuecomment-643453128 | https://api.github.com/repos/simonw/datasette/issues/840 | MDEyOklzc3VlQ29tbWVudDY0MzQ1MzEyOA== | simonw 9599 | 2020-06-12T19:43:15Z | 2020-06-12T19:43:15Z | OWNER | I don't like how this often involves a logout link that can be maliciously activated. I'm going to use a CSRF protected form button styled to look like a link instead. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Log out mechanism for clearing ds_actor cookie 637966833 | |
643414646 | https://github.com/dogsheep/github-to-sqlite/issues/40#issuecomment-643414646 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/40 | MDEyOklzc3VlQ29tbWVudDY0MzQxNDY0Ng== | simonw 9599 | 2020-06-12T18:06:48Z | 2020-06-12T18:06:48Z | MEMBER | That fixed it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Demo deploy is broken 637899539 | |
643406939 | https://github.com/simonw/sqlite-utils/issues/115#issuecomment-643406939 | https://api.github.com/repos/simonw/sqlite-utils/issues/115 | MDEyOklzc3VlQ29tbWVudDY0MzQwNjkzOQ== | simonw 9599 | 2020-06-12T17:51:11Z | 2020-06-12T17:51:11Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to execute insert/update statements with the CLI 637889964 | ||
643393506 | https://github.com/dogsheep/github-to-sqlite/issues/40#issuecomment-643393506 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/40 | MDEyOklzc3VlQ29tbWVudDY0MzM5MzUwNg== | simonw 9599 | 2020-06-12T17:21:14Z | 2020-06-12T17:21:14Z | MEMBER | I only install SQLite for this: I'm going to remove the need to install sqlite3 by making this possible with sqlite-utils: https://github.com/simonw/sqlite-utils/issues/115 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Demo deploy is broken 637899539 | |
643010591 | https://github.com/simonw/datasette/issues/806#issuecomment-643010591 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MzAxMDU5MQ== | simonw 9599 | 2020-06-12T01:13:06Z | 2020-06-12T01:13:06Z | OWNER | Tests are passing again: https://github.com/simonw/datasette/commit/9ae0d483ead93c0832142e5dc85959ae3c8f73ea |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
643000948 | https://github.com/simonw/datasette/issues/806#issuecomment-643000948 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MzAwMDk0OA== | simonw 9599 | 2020-06-12T00:34:21Z | 2020-06-12T00:34:21Z | OWNER | I'm going to add https://github.com/simonw/datasette-auth-tokens and https://github.com/simonw/datasette-permissions-sql to the documentation and release notes in a few places. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
642998097 | https://github.com/simonw/datasette/issues/806#issuecomment-642998097 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0Mjk5ODA5Nw== | simonw 9599 | 2020-06-12T00:26:00Z | 2020-06-12T00:26:00Z | OWNER | OK, I'm ready to ship. Last check of the release notes, then I'll update the news section in the README and release 0.44! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
642993277 | https://github.com/simonw/datasette/issues/838#issuecomment-642993277 | https://api.github.com/repos/simonw/datasette/issues/838 | MDEyOklzc3VlQ29tbWVudDY0Mjk5MzI3Nw== | simonw 9599 | 2020-06-12T00:18:26Z | 2020-06-12T00:18:50Z | OWNER | Have you tried this without the This is the test I used to ensure this feature works - it scrapes all of the links on a bunch of different pages. Could it be missing something here? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Incorrect URLs when served behind a proxy with base_url set 637395097 | |
642991513 | https://github.com/simonw/datasette/issues/824#issuecomment-642991513 | https://api.github.com/repos/simonw/datasette/issues/824 | MDEyOklzc3VlQ29tbWVudDY0Mjk5MTUxMw== | simonw 9599 | 2020-06-12T00:11:50Z | 2020-06-12T00:11:50Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example authentication plugin 635108074 | ||
642958225 | https://github.com/simonw/datasette/issues/833#issuecomment-642958225 | https://api.github.com/repos/simonw/datasette/issues/833 | MDEyOklzc3VlQ29tbWVudDY0Mjk1ODIyNQ== | simonw 9599 | 2020-06-11T22:15:32Z | 2020-06-11T22:15:32Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
/-/metadata and so on should respect view-instance permission 637253789 | ||
642953605 | https://github.com/simonw/datasette/issues/824#issuecomment-642953605 | https://api.github.com/repos/simonw/datasette/issues/824 | MDEyOklzc3VlQ29tbWVudDY0Mjk1MzYwNQ== | simonw 9599 | 2020-06-11T22:02:32Z | 2020-06-11T22:02:32Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example authentication plugin 635108074 | |
642952962 | https://github.com/simonw/datasette/issues/824#issuecomment-642952962 | https://api.github.com/repos/simonw/datasette/issues/824 | MDEyOklzc3VlQ29tbWVudDY0Mjk1Mjk2Mg== | simonw 9599 | 2020-06-11T22:01:58Z | 2020-06-11T22:01:58Z | OWNER | Alternative idea: a plugin that handles Bearer token authentication. Uses |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example authentication plugin 635108074 | |
642951150 | https://github.com/simonw/datasette/issues/824#issuecomment-642951150 | https://api.github.com/repos/simonw/datasette/issues/824 | MDEyOklzc3VlQ29tbWVudDY0Mjk1MTE1MA== | simonw 9599 | 2020-06-11T22:00:17Z | 2020-06-11T22:00:17Z | OWNER | I got this working: https://github.com/simonw/datasette-auth-github/pull/64 Just one problem: it uses the existing It does use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example authentication plugin 635108074 | |
642944645 | https://github.com/simonw/datasette/issues/220#issuecomment-642944645 | https://api.github.com/repos/simonw/datasette/issues/220 | MDEyOklzc3VlQ29tbWVudDY0Mjk0NDY0NQ== | simonw 9599 | 2020-06-11T21:49:55Z | 2020-06-11T21:49:55Z | OWNER | I'm OK with not implementing this - I've got used to the existing mechanism, and it doesn't frustrate me enough to work on this more. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Investigate syntactic sugar for plugins 314847571 | |
642907021 | https://github.com/simonw/datasette/issues/832#issuecomment-642907021 | https://api.github.com/repos/simonw/datasette/issues/832 | MDEyOklzc3VlQ29tbWVudDY0MjkwNzAyMQ== | simonw 9599 | 2020-06-11T20:20:35Z | 2020-06-11T20:20:35Z | OWNER | I think the new |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Having view-table permission but NOT view-database should still grant access to /db/table 636722501 | |
642906681 | https://github.com/simonw/datasette/issues/832#issuecomment-642906681 | https://api.github.com/repos/simonw/datasette/issues/832 | MDEyOklzc3VlQ29tbWVudDY0MjkwNjY4MQ== | simonw 9599 | 2020-06-11T20:19:47Z | 2020-06-11T20:20:02Z | OWNER | So for the following:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Having view-table permission but NOT view-database should still grant access to /db/table 636722501 | |
642905424 | https://github.com/simonw/datasette/issues/833#issuecomment-642905424 | https://api.github.com/repos/simonw/datasette/issues/833 | MDEyOklzc3VlQ29tbWVudDY0MjkwNTQyNA== | simonw 9599 | 2020-06-11T20:16:41Z | 2020-06-11T20:16:41Z | OWNER | I'll add a new test in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
/-/metadata and so on should respect view-instance permission 637253789 | |
642902208 | https://github.com/simonw/datasette/issues/833#issuecomment-642902208 | https://api.github.com/repos/simonw/datasette/issues/833 | MDEyOklzc3VlQ29tbWVudDY0MjkwMjIwOA== | simonw 9599 | 2020-06-11T20:08:57Z | 2020-06-11T20:08:57Z | OWNER | I'm tempted to add a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
/-/metadata and so on should respect view-instance permission 637253789 | |
642874724 | https://github.com/simonw/datasette/issues/833#issuecomment-642874724 | https://api.github.com/repos/simonw/datasette/issues/833 | MDEyOklzc3VlQ29tbWVudDY0Mjg3NDcyNA== | simonw 9599 | 2020-06-11T19:07:49Z | 2020-06-11T19:07:49Z | OWNER | A live demo running the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
/-/metadata and so on should respect view-instance permission 637253789 | |
642870553 | https://github.com/simonw/datasette/issues/801#issuecomment-642870553 | https://api.github.com/repos/simonw/datasette/issues/801 | MDEyOklzc3VlQ29tbWVudDY0Mjg3MDU1Mw== | simonw 9599 | 2020-06-11T18:58:49Z | 2020-06-11T18:58:49Z | OWNER | I've implemented this in a plugin instead: https://github.com/simonw/datasette-permissions-sql |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
allow_by_query setting for configuring permissions with a SQL statement 631932926 | |
642795966 | https://github.com/simonw/datasette/issues/832#issuecomment-642795966 | https://api.github.com/repos/simonw/datasette/issues/832 | MDEyOklzc3VlQ29tbWVudDY0Mjc5NTk2Ng== | simonw 9599 | 2020-06-11T16:37:21Z | 2020-06-11T16:37:21Z | OWNER | How would I document this? Probably in another section on https://datasette.readthedocs.io/en/latest/authentication.html#permissions But I'd also need to add documentation to the individual views stating what permissions are checked and in what order. I could do that on this page: https://datasette.readthedocs.io/en/latest/pages.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Having view-table permission but NOT view-database should still grant access to /db/table 636722501 | |
642772344 | https://github.com/simonw/datasette/pull/809#issuecomment-642772344 | https://api.github.com/repos/simonw/datasette/issues/809 | MDEyOklzc3VlQ29tbWVudDY0Mjc3MjM0NA== | simonw 9599 | 2020-06-11T16:01:15Z | 2020-06-11T16:01:15Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Publish secrets 632919570 | |
642754589 | https://github.com/simonw/datasette/pull/809#issuecomment-642754589 | https://api.github.com/repos/simonw/datasette/issues/809 | MDEyOklzc3VlQ29tbWVudDY0Mjc1NDU4OQ== | simonw 9599 | 2020-06-11T15:45:25Z | 2020-06-11T15:45:25Z | OWNER |
https://datasette-publish-secret-j7hipcg4aq-uw.a.run.app/-/messages |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Publish secrets 632919570 | |
642750790 | https://github.com/simonw/datasette/pull/809#issuecomment-642750790 | https://api.github.com/repos/simonw/datasette/issues/809 | MDEyOklzc3VlQ29tbWVudDY0Mjc1MDc5MA== | simonw 9599 | 2020-06-11T15:42:23Z | 2020-06-11T15:42:23Z | OWNER |
https://datasette-publish-secret.herokuapp.com/-/messages - Heroku works. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Publish secrets 632919570 | |
642745518 | https://github.com/simonw/datasette/pull/809#issuecomment-642745518 | https://api.github.com/repos/simonw/datasette/issues/809 | MDEyOklzc3VlQ29tbWVudDY0Mjc0NTUxOA== | simonw 9599 | 2020-06-11T15:38:51Z | 2020-06-11T15:38:51Z | OWNER | The way to manually test this is to publish a database to each provider and then check that the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Publish secrets 632919570 | |
642741930 | https://github.com/simonw/datasette/issues/832#issuecomment-642741930 | https://api.github.com/repos/simonw/datasette/issues/832 | MDEyOklzc3VlQ29tbWVudDY0Mjc0MTkzMA== | simonw 9599 | 2020-06-11T15:35:53Z | 2020-06-11T15:36:05Z | OWNER | May the fix here is to implement a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Having view-table permission but NOT view-database should still grant access to /db/table 636722501 | |
642420375 | https://github.com/simonw/datasette/issues/818#issuecomment-642420375 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MjQyMDM3NQ== | simonw 9599 | 2020-06-11T05:40:07Z | 2020-06-11T05:40:07Z | OWNER | https://github.com/simonw/datasette-permissions-sql is now released as a 0.1a here: https://pypi.org/project/datasette-permissions-sql/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
642412017 | https://github.com/simonw/datasette/issues/832#issuecomment-642412017 | https://api.github.com/repos/simonw/datasette/issues/832 | MDEyOklzc3VlQ29tbWVudDY0MjQxMjAxNw== | simonw 9599 | 2020-06-11T05:13:59Z | 2020-06-11T05:13:59Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Having view-table permission but NOT view-database should still grant access to /db/table 636722501 | ||
642324847 | https://github.com/simonw/datasette/issues/831#issuecomment-642324847 | https://api.github.com/repos/simonw/datasette/issues/831 | MDEyOklzc3VlQ29tbWVudDY0MjMyNDg0Nw== | simonw 9599 | 2020-06-10T23:50:55Z | 2020-06-10T23:50:55Z | OWNER | Actually I'm not sure about this. If It could be So I think I'm going to stick with the current mechanism, which is that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
It would be more intuitive if "allow": none meant "no-one can do this" 636614868 | |
642231871 | https://github.com/simonw/datasette/issues/818#issuecomment-642231871 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MjIzMTg3MQ== | simonw 9599 | 2020-06-10T20:11:50Z | 2020-06-10T20:11:50Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
642230499 | https://github.com/simonw/datasette/issues/818#issuecomment-642230499 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MjIzMDQ5OQ== | simonw 9599 | 2020-06-10T20:08:46Z | 2020-06-10T20:09:26Z | OWNER | What's a simple but useful plugin I could release that exercises this hook? Ideally one which executes permission checks against the database somehow. I could do a simplest-possible implementation of the idea in #801 (allow-by-query). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
642229899 | https://github.com/simonw/datasette/issues/818#issuecomment-642229899 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MjIyOTg5OQ== | simonw 9599 | 2020-06-10T20:07:36Z | 2020-06-10T20:07:36Z | OWNER | New policy in 9f236c4 dictates that this should be in Milestone 0.44 after all:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
642217520 | https://github.com/simonw/datasette/issues/829#issuecomment-642217520 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjIxNzUyMA== | simonw 9599 | 2020-06-10T19:41:35Z | 2020-06-10T19:41:35Z | OWNER | I didn't bother with the alternative epoch - it only shaves off two or three bytes from the cookie. Documentation for the new |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
642178604 | https://github.com/simonw/datasette/issues/829#issuecomment-642178604 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjE3ODYwNA== | simonw 9599 | 2020-06-10T18:18:36Z | 2020-06-10T18:20:19Z | OWNER | Even shorter: encode an integer that is the difference between that expiry timestamp and a more recent epoch - June 1st 2020 will do. ```
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
642176180 | https://github.com/simonw/datasette/issues/829#issuecomment-642176180 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjE3NjE4MA== | simonw 9599 | 2020-06-10T18:14:02Z | 2020-06-10T18:14:15Z | OWNER | And the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
642175892 | https://github.com/simonw/datasette/issues/829#issuecomment-642175892 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjE3NTg5Mg== | simonw 9599 | 2020-06-10T18:13:26Z | 2020-06-10T18:13:26Z | OWNER | I'm going with
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
642174272 | https://github.com/simonw/datasette/issues/829#issuecomment-642174272 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjE3NDI3Mg== | simonw 9599 | 2020-06-10T18:10:13Z | 2020-06-10T18:10:13Z | OWNER | Some options:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
642161210 | https://github.com/simonw/datasette/issues/829#issuecomment-642161210 | https://api.github.com/repos/simonw/datasette/issues/829 | MDEyOklzc3VlQ29tbWVudDY0MjE2MTIxMA== | simonw 9599 | 2020-06-10T17:45:58Z | 2020-06-10T17:45:58Z | OWNER |
I currently only decode the If plugins want to be able to set their own policies on how long the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to set ds_actor cookie such that it expires 636426530 | |
641713087 | https://github.com/simonw/datasette/issues/828#issuecomment-641713087 | https://api.github.com/repos/simonw/datasette/issues/828 | MDEyOklzc3VlQ29tbWVudDY0MTcxMzA4Nw== | simonw 9599 | 2020-06-10T04:28:17Z | 2020-06-10T04:28:17Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Horizontal scrollbar on changelog page on mobile 635914822 | ||
641710745 | https://github.com/simonw/datasette/issues/828#issuecomment-641710745 | https://api.github.com/repos/simonw/datasette/issues/828 | MDEyOklzc3VlQ29tbWVudDY0MTcxMDc0NQ== | simonw 9599 | 2020-06-10T04:19:31Z | 2020-06-10T04:19:31Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Horizontal scrollbar on changelog page on mobile 635914822 | ||
641710670 | https://github.com/simonw/datasette/issues/828#issuecomment-641710670 | https://api.github.com/repos/simonw/datasette/issues/828 | MDEyOklzc3VlQ29tbWVudDY0MTcxMDY3MA== | simonw 9599 | 2020-06-10T04:19:17Z | 2020-06-10T04:19:17Z | OWNER | This CSS seems to fix it:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Horizontal scrollbar on changelog page on mobile 635914822 | |
641637696 | https://github.com/simonw/datasette/issues/806#issuecomment-641637696 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYzNzY5Ng== | simonw 9599 | 2020-06-09T23:46:00Z | 2020-06-09T23:46:00Z | OWNER | The issues that should be referenced from this release are: 395, #519, #576, #699, #706, #774, #777, #781, #784, #788, #790, #797, #798, #800, #802, #804, #819, #822 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641634749 | https://github.com/simonw/datasette/issues/806#issuecomment-641634749 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYzNDc0OQ== | simonw 9599 | 2020-06-09T23:34:52Z | 2020-06-09T23:34:52Z | OWNER | Preview of the release notes is now available here: https://datasette.readthedocs.io/en/latest/changelog.html#v0-44 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641616185 | https://github.com/simonw/datasette/issues/795#issuecomment-641616185 | https://api.github.com/repos/simonw/datasette/issues/795 | MDEyOklzc3VlQ29tbWVudDY0MTYxNjE4NQ== | simonw 9599 | 2020-06-09T22:33:33Z | 2020-06-09T22:33:33Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
response.set_cookie() method 629541395 | ||
641616060 | https://github.com/simonw/datasette/issues/826#issuecomment-641616060 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTYxNjA2MA== | simonw 9599 | 2020-06-09T22:33:12Z | 2020-06-09T22:33:12Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Document the ds_actor signed cookie 635519358 | ||
641604210 | https://github.com/simonw/datasette/issues/806#issuecomment-641604210 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwNDIxMA== | simonw 9599 | 2020-06-09T21:59:33Z | 2020-06-09T22:00:11Z | OWNER | AWS IAM uses action and resource terminology: https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_access-management.html - I think that's where I got that language:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641603457 | https://github.com/simonw/datasette/issues/806#issuecomment-641603457 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwMzQ1Nw== | simonw 9599 | 2020-06-09T21:57:32Z | 2020-06-09T21:57:32Z | OWNER | operation, procedure, process as alternative words for those menu items? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641602794 | https://github.com/simonw/datasette/issues/806#issuecomment-641602794 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwMjc5NA== | simonw 9599 | 2020-06-09T21:55:45Z | 2020-06-09T21:55:45Z | OWNER | Last-minute thought: Should I worry about calling permissions "actions", when I have an idea for a future plugin hook that allows plugins to add something I was going to call "actions" to database, table and row pages? Those actions would take the form of menu item commands that Do Something to the selected object. If I use "actions" to mean permission names, will I be able to find a good alternative name for these dynamic menu items? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641538982 | https://github.com/simonw/datasette/issues/804#issuecomment-641538982 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUzODk4Mg== | simonw 9599 | 2020-06-09T20:01:30Z | 2020-06-09T20:01:30Z | OWNER | Now fully documented here: https://datasette.readthedocs.io/en/latest/contributing.html#setting-up-a-development-environment |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
python tests/fixtures.py command has a bug 632673972 | |
641538799 | https://github.com/simonw/datasette/issues/804#issuecomment-641538799 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUzODc5OQ== | simonw 9599 | 2020-06-09T20:01:08Z | 2020-06-09T20:01:08Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
python tests/fixtures.py command has a bug 632673972 | |
641528737 | https://github.com/simonw/datasette/issues/804#issuecomment-641528737 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUyODczNw== | simonw 9599 | 2020-06-09T19:39:24Z | 2020-06-09T19:39:24Z | OWNER | Switched to 0.44 milestone because I don't like shipping releases with known bugs. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
python tests/fixtures.py command has a bug 632673972 | |
641528269 | https://github.com/simonw/datasette/issues/827#issuecomment-641528269 | https://api.github.com/repos/simonw/datasette/issues/827 | MDEyOklzc3VlQ29tbWVudDY0MTUyODI2OQ== | simonw 9599 | 2020-06-09T19:38:30Z | 2020-06-09T19:38:30Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Document CSRF protection (for plugins) 635696400 | ||
641406944 | https://github.com/simonw/datasette/issues/825#issuecomment-641406944 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQwNjk0NA== | simonw 9599 | 2020-06-09T16:12:02Z | 2020-06-09T17:19:19Z | OWNER | Alternative design: leave actor alone. Instead specify that allow blocks can look like this:
I like this: the above block is very self-documenting. The I'm going with this design. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | |
641452563 | https://github.com/simonw/datasette/issues/825#issuecomment-641452563 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQ1MjU2Mw== | simonw 9599 | 2020-06-09T17:08:00Z | 2020-06-09T17:08:00Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | ||
641449725 | https://github.com/simonw/datasette/issues/825#issuecomment-641449725 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQ0OTcyNQ== | simonw 9599 | 2020-06-09T17:02:31Z | 2020-06-09T17:02:31Z | OWNER | Documented at the bottom of this section: https://github.com/simonw/datasette/blob/7633b9ab249b2dce5ee0b4fcf9542c13a1703ef0/docs/authentication.rst#defining-permissions-with-allow-blocks |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | |
641412424 | https://github.com/simonw/datasette/issues/825#issuecomment-641412424 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQxMjQyNA== | simonw 9599 | 2020-06-09T16:22:07Z | 2020-06-09T16:22:07Z | OWNER | When I implement this I should also document default allow vs default deny as a concept, and specify that default next to every documented permission. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | |
641361311 | https://github.com/simonw/datasette/issues/795#issuecomment-641361311 | https://api.github.com/repos/simonw/datasette/issues/795 | MDEyOklzc3VlQ29tbWVudDY0MTM2MTMxMQ== | simonw 9599 | 2020-06-09T15:11:50Z | 2020-06-09T15:11:50Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
response.set_cookie() method 629541395 | ||
641360187 | https://github.com/simonw/datasette/issues/826#issuecomment-641360187 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTM2MDE4Nw== | simonw 9599 | 2020-06-09T15:10:00Z | 2020-06-09T15:11:24Z | OWNER | Also a good reminder that I need a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Document the ds_actor signed cookie 635519358 | |
641359103 | https://github.com/simonw/datasette/issues/826#issuecomment-641359103 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTM1OTEwMw== | simonw 9599 | 2020-06-09T15:08:07Z | 2020-06-09T15:10:33Z | OWNER | I should probably add a utility function for setting that cookie - right now the only code that does that is here: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Document the ds_actor signed cookie 635519358 | |
641353729 | https://github.com/simonw/datasette/issues/812#issuecomment-641353729 | https://api.github.com/repos/simonw/datasette/issues/812 | MDEyOklzc3VlQ29tbWVudDY0MTM1MzcyOQ== | simonw 9599 | 2020-06-09T14:59:25Z | 2020-06-09T14:59:25Z | OWNER | I'm going to figure this out by working with https://github.com/simonw/datasette-auth-github/issues/62 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to customize what happens when a view permission fails 634112607 | |
641353186 | https://github.com/simonw/datasette/issues/823#issuecomment-641353186 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTM1MzE4Ng== | simonw 9599 | 2020-06-09T14:58:36Z | 2020-06-09T14:58:36Z | OWNER | Docs now say:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation is inconsistent about "id" as required field on actor 635107393 | |
641320947 | https://github.com/simonw/datasette/issues/825#issuecomment-641320947 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTMyMDk0Nw== | simonw 9599 | 2020-06-09T14:06:46Z | 2020-06-09T14:06:46Z | OWNER | I'm torn between
I'm going with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | |
641062164 | https://github.com/simonw/datasette/issues/825#issuecomment-641062164 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTA2MjE2NA== | simonw 9599 | 2020-06-09T06:30:24Z | 2020-06-09T14:05:33Z | OWNER | Idea: the anonymous actor could be passed to
Then allow blocks like this could be used to allow them:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Way to enable a default=False permission for anonymous users 635147716 | |
641059221 | https://github.com/simonw/datasette/issues/823#issuecomment-641059221 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTA1OTIyMQ== | simonw 9599 | 2020-06-09T06:23:51Z | 2020-06-09T06:24:09Z | OWNER | I don't like the "id" requirement. I can think of plenty of situations where a unique ID might not be available:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation is inconsistent about "id" as required field on actor 635107393 | |
641026726 | https://github.com/simonw/datasette/issues/806#issuecomment-641026726 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTAyNjcyNg== | simonw 9599 | 2020-06-09T04:52:07Z | 2020-06-09T04:52:07Z | OWNER | Changelog for this is going to be huge - 96 commits since 0.43 already! https://github.com/simonw/datasette/compare/0.43...master |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 0.44 632753851 | |
641026230 | https://github.com/simonw/datasette/issues/818#issuecomment-641026230 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAyNjIzMA== | simonw 9599 | 2020-06-09T04:50:24Z | 2020-06-09T04:50:24Z | OWNER | I'm dropping this from the 0.44 milestone. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
641025760 | https://github.com/simonw/datasette/issues/823#issuecomment-641025760 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTAyNTc2MA== | simonw 9599 | 2020-06-09T04:48:40Z | 2020-06-09T04:48:40Z | OWNER | I should assert that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation is inconsistent about "id" as required field on actor 635107393 | |
641017851 | https://github.com/simonw/datasette/issues/805#issuecomment-641017851 | https://api.github.com/repos/simonw/datasette/issues/805 | MDEyOklzc3VlQ29tbWVudDY0MTAxNzg1MQ== | simonw 9599 | 2020-06-09T04:17:00Z | 2020-06-09T04:17:00Z | OWNER | I can't get Datasette working on Glitch installed from a URL - I'm going to try this on Glitch once I've shipped the 0.44 release in #806. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writable canned queries live demo on Glitch 632724154 | |
641017721 | https://github.com/simonw/datasette/issues/805#issuecomment-641017721 | https://api.github.com/repos/simonw/datasette/issues/805 | MDEyOklzc3VlQ29tbWVudDY0MTAxNzcyMQ== | simonw 9599 | 2020-06-09T04:16:28Z | 2020-06-09T04:16:28Z | OWNER | Create |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writable canned queries live demo on Glitch 632724154 | |
638301073 | https://github.com/simonw/datasette/issues/797#issuecomment-638301073 | https://api.github.com/repos/simonw/datasette/issues/797 | MDEyOklzc3VlQ29tbWVudDYzODMwMTA3Mw== | simonw 9599 | 2020-06-03T16:14:54Z | 2020-06-09T04:00:40Z | OWNER | I want a unit test that exercises this for both writable and regular canned queries. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation for new "params" setting for canned queries 630120235 | |
641013524 | https://github.com/simonw/datasette/issues/818#issuecomment-641013524 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAxMzUyNA== | simonw 9599 | 2020-06-09T03:57:38Z | 2020-06-09T04:00:24Z | OWNER | Problem with that is it's more of a The most interesting permissions plugin would be one that implements permissions against some kind of database schema, hence allowing admins to edit permissions through writable canned queries. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
641009744 | https://github.com/simonw/datasette/issues/818#issuecomment-641009744 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAwOTc0NA== | simonw 9599 | 2020-06-09T03:43:18Z | 2020-06-09T03:43:18Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
641009442 | https://github.com/simonw/datasette/issues/818#issuecomment-641009442 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAwOTQ0Mg== | simonw 9599 | 2020-06-09T03:41:55Z | 2020-06-09T03:41:55Z | OWNER | I want to build a plugin that does |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Example permissions plugin 634917088 | |
641003291 | https://github.com/simonw/datasette/issues/822#issuecomment-641003291 | https://api.github.com/repos/simonw/datasette/issues/822 | MDEyOklzc3VlQ29tbWVudDY0MTAwMzI5MQ== | simonw 9599 | 2020-06-09T03:17:43Z | 2020-06-09T03:17:43Z | OWNER | I'm leaning towards |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
request.url_vars helper property 635077656 | |
641003237 | https://github.com/simonw/datasette/issues/822#issuecomment-641003237 | https://api.github.com/repos/simonw/datasette/issues/822 | MDEyOklzc3VlQ29tbWVudDY0MTAwMzIzNw== | simonw 9599 | 2020-06-09T03:17:32Z | 2020-06-09T03:17:32Z | OWNER | Currently querystring parameters are accessed through |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
request.url_vars helper property 635077656 | |
641002504 | https://github.com/simonw/datasette/issues/215#issuecomment-641002504 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MTAwMjUwNA== | simonw 9599 | 2020-06-09T03:14:32Z | 2020-06-09T03:14:32Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow plugins to define additional URL routes and views 314506669 | ||
640982533 | https://github.com/simonw/datasette/issues/820#issuecomment-640982533 | https://api.github.com/repos/simonw/datasette/issues/820 | MDEyOklzc3VlQ29tbWVudDY0MDk4MjUzMw== | simonw 9599 | 2020-06-09T02:00:21Z | 2020-06-09T02:00:21Z | OWNER | In the case of registering API tokens it would be useful if the plugin could call a writable canned query which knows how to insert a randomly generated value. This could be achieved using a custom SQL function. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Idea: Plugin hook for registering canned queries 635049296 | |
640972952 | https://github.com/simonw/datasette/issues/215#issuecomment-640972952 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk3Mjk1Mg== | simonw 9599 | 2020-06-09T01:24:52Z | 2020-06-09T01:25:33Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow plugins to define additional URL routes and views 314506669 | ||
640971470 | https://github.com/simonw/datasette/issues/215#issuecomment-640971470 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk3MTQ3MA== | simonw 9599 | 2020-06-09T01:19:44Z | 2020-06-09T01:19:44Z | OWNER | I'll need to add documentation of the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow plugins to define additional URL routes and views 314506669 | |
640960667 | https://github.com/simonw/datasette/issues/215#issuecomment-640960667 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk2MDY2Nw== | simonw 9599 | 2020-06-09T00:41:35Z | 2020-06-09T00:41:35Z | OWNER | I'm going to implement this one documentation-first in a pull request. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow plugins to define additional URL routes and views 314506669 | |
640960553 | https://github.com/simonw/datasette/issues/215#issuecomment-640960553 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk2MDU1Mw== | simonw 9599 | 2020-06-09T00:41:09Z | 2020-06-09T00:41:09Z | OWNER | I'm going to imitate So I'll do this:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Allow plugins to define additional URL routes and views 314506669 | |
640957423 | https://github.com/simonw/datasette/issues/777#issuecomment-640957423 | https://api.github.com/repos/simonw/datasette/issues/777 | MDEyOklzc3VlQ29tbWVudDY0MDk1NzQyMw== | simonw 9599 | 2020-06-09T00:29:03Z | 2020-06-09T00:29:03Z | OWNER | Here's why: 404 errors are rendered by looking for a template from
That template extends |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error pages not correctly loading CSS 626171242 | |
640955788 | https://github.com/simonw/datasette/issues/777#issuecomment-640955788 | https://api.github.com/repos/simonw/datasette/issues/777 | MDEyOklzc3VlQ29tbWVudDY0MDk1NTc4OA== | simonw 9599 | 2020-06-09T00:23:26Z | 2020-06-09T00:23:57Z | OWNER | Clue: https://latest.datasette.io/404 displays correctly but https://latest.datasette.io/fixtures/404 does not. That's because |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error pages not correctly loading CSS 626171242 |
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]);
author_association 2