home / github

Menu
  • Search all tables
  • GraphQL API

issues

Table actions
  • GraphQL API for issues

16 rows where milestone = 6346396 and type = "issue" sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, comments, author_association, created_at (date), updated_at (date), closed_at (date)

type 1

  • issue · 16 ✖

state 1

  • closed 16

repo 1

  • datasette 16
id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
781262510 MDU6SXNzdWU3ODEyNjI1MTA= 1181 Certain database names results in 404: "Database not found: None" jieter 1470389 closed 0   Datasette 0.54 6346396 4 2021-01-07T12:01:16Z 2021-12-21T18:25:15Z 2021-01-25T05:13:19Z NONE  

I have a file named test-database (1).sqlite. When requesting the home route /, I see datasette is able to read it correctly:

However, if I click any of the links, datasette replies with: Error 404 Database not found: None

It seems the hash is crucial, as renaming the file to database (1).sqlite makes the error go away.

This lines checks for a single dash: https://github.com/simonw/datasette/blob/97fb10c17dd007a275ab743742e93e932335ad67/datasette/views/base.py#L184

``` $ datasette test-database\ (1).sqlite INFO: Started server process [68314] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://127.0.0.1:8001 (Press CTRL+C to quit) INFO: 127.0.0.1:54043 - "GET /favicon.ico HTTP/1.1" 200 OK INFO: 127.0.0.1:54043 - "GET / HTTP/1.1" 200 OK ... INFO: 127.0.0.1:54044 - "GET /favicon.ico HTTP/1.1" 200 OK INFO: 127.0.0.1:54044 - "GET /test-database (1) HTTP/1.1" 404 Not Found

Version: $ datasette --version datasette, version 0.53 ```

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1181/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
770448622 MDU6SXNzdWU3NzA0NDg2MjI= 1151 Database class mechanism for cross-connection in-memory databases simonw 9599 closed 0   Datasette 0.54 6346396 11 2020-12-17T23:25:43Z 2021-01-26T19:07:44Z 2020-12-18T01:01:26Z OWNER  

Next challenge: figure out how to use the Database class from https://github.com/simonw/datasette/blob/0.53/datasette/database.py for an in-memory database which persists data for the duration of the lifetime of the server, and allows access to that in-memory database from multiple threads in a way that lets them see each other's changes.

Originally posted by @simonw in https://github.com/simonw/datasette/issues/1150#issuecomment-747768112

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1151/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
792904595 MDU6SXNzdWU3OTI5MDQ1OTU= 1201 Release notes for Datasette 0.54 simonw 9599 closed 0   Datasette 0.54 6346396 5 2021-01-24T21:22:28Z 2021-01-25T17:42:21Z 2021-01-25T17:42:21Z OWNER  

These will incorporate the release notes from the alpha, much expanded: https://github.com/simonw/datasette/releases/tag/0.54a0

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1201/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
788447787 MDU6SXNzdWU3ODg0NDc3ODc= 1194 ?_size= argument is not persisted by hidden form fields in the table filters simonw 9599 closed 0   Datasette 0.54 6346396 3 2021-01-18T17:41:52Z 2021-01-25T03:10:23Z 2021-01-25T03:10:23Z OWNER  

Click "Apply" on https://covid-19.datasettes.com/covid/ny_times_us_counties?_size=1000&county__exact=San+Francisco&state__exact=California&_sort_desc=date#g.mark=line&g.x_column=date&g.x_type=temporal&g.y_column=cases&g.y_type=quantitative and the ?_size=1000 parameter from the URL will no longer apply on the reloaded page.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1194/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
777145954 MDU6SXNzdWU3NzcxNDU5NTQ= 1167 Add Prettier to contributing documentation simonw 9599 closed 0   Datasette 0.54 6346396 3 2020-12-31T22:00:55Z 2021-01-25T02:01:19Z 2021-01-25T01:58:28Z OWNER  

Following #1166 - the docs at https://docs.datasette.io/en/stable/contributing.html should include a section about JavaScript, and it should document how to run Prettier.

I run it in VS Code but it can be run on the command-line too:

npx prettier 'datasette/static/*[!.min].js' --write
datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1167/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
771208009 MDU6SXNzdWU3NzEyMDgwMDk= 1154 Documentation for new _internal database and tables simonw 9599 closed 0   Datasette 0.54 6346396 2 2020-12-18T22:34:52Z 2021-01-25T00:09:22Z 2021-01-25T00:08:41Z OWNER  

Needs documentation, but I can wait to write that until I've tested out the feature a bit more.

Originally posted by @simonw in https://github.com/simonw/datasette/issues/1150#issuecomment-748352106

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1154/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
792931244 MDU6SXNzdWU3OTI5MzEyNDQ= 1202 Documentation convention for marking unstable APIs. simonw 9599 closed 0   Datasette 0.54 6346396 2 2021-01-24T23:47:18Z 2021-01-25T00:01:02Z 2021-01-25T00:01:02Z OWNER  

I'm going to document this but mark it as unstable, using a new documentation convention for marking unstable APIs.

Originally posted by @simonw in https://github.com/simonw/datasette/issues/1154#issuecomment-766462197

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1202/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
785588942 MDU6SXNzdWU3ODU1ODg5NDI= 1187 extra_body_script() support for script type="module" simonw 9599 closed 0   Datasette 0.54 6346396 1 2021-01-14T02:01:47Z 2021-01-24T21:21:44Z 2021-01-14T02:14:39Z OWNER  

Follows #1186. The extra_body_script() plugin hook should provide a mechanism for specifying that the script should use <script type="module">.

Relevant docs: https://docs.datasette.io/en/stable/plugin_hooks.html#extra-body-script-template-database-table-columns-view-name-request-datasette

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1187/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
785573793 MDU6SXNzdWU3ODU1NzM3OTM= 1186 script type="module" support simonw 9599 closed 0   Datasette 0.54 6346396 1 2021-01-14T01:17:47Z 2021-01-24T21:21:41Z 2021-01-14T01:50:58Z OWNER  

Custom JavaScript can be loaded in metadata.json like this: json { "extra_js_urls": [ { "url": "https://code.jquery.com/jquery-3.2.1.slim.min.js", "sri": "sha256-k2WSCIexGzOj3Euiig+TlR8gA0EmPjuc79OEeY5L45g=" } ] } Add a "module": true option which causes the resulting script element to use <script type="module">

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1186/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
784628163 MDU6SXNzdWU3ODQ2MjgxNjM= 1185 "Statement may not contain PRAGMA" error is not strictly true simonw 9599 closed 0   Datasette 0.54 6346396 3 2021-01-12T22:07:10Z 2021-01-24T21:21:37Z 2021-01-12T22:26:26Z OWNER  

Consider https://latest.datasette.io/fixtures?sql=select+%27select%0D%0A%27+%7C%7C+group_concat%28%27++++case+when+%5B%27+%7C%7C+name+%7C%7C+%27%5D+is+not+null+then+%27+%7C%7C+quote%28name+%7C%7C+%27%2C+%27%29+%7C%7C+%27+else+%27%27%27%27+end%27%2C+%27+%7C%7C%0D%0A%27%29+%7C%7C+%27%0D%0A++as+columns%2C%0D%0A++count%28*%29+as+num_rows%0D%0Afrom%0D%0A++%5B%27+%7C%7C+%3Atable+%7C%7C+%27%5D%0D%0Agroup+by%0D%0A++columns%0D%0Aorder+by%0D%0A++num_rows+desc%27+as+query+from+pragma_ytable_info%28%3Atable%29&table=facetable

It says "Statement may not contain PRAGMA" - but that's not actually true. Datasette has an allow-list of PRAGMA that are OK - in this case there was a typo in pragma_ytable_info which caused the error, but pragma_table_info` would have been OK.

So the error message is misleading.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1185/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
783714076 MDU6SXNzdWU3ODM3MTQwNzY= 1184 request.full_path property simonw 9599 closed 0   Datasette 0.54 6346396 0 2021-01-11T21:21:58Z 2021-01-24T21:21:16Z 2021-01-11T21:34:47Z OWNER  

I'll also add request.full_path for consistency with these: https://github.com/simonw/datasette/blob/97fb10c17dd007a275ab743742e93e932335ad67/datasette/utils/asgi.py#L77-L90

Originally posted by @simonw in https://github.com/simonw/datasette/issues/1179#issuecomment-755495387

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1184/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
782692159 MDU6SXNzdWU3ODI2OTIxNTk= 1182 Retire "Ecosystem" page in favour of datasette.io/plugins and /tools simonw 9599 closed 0   Datasette 0.54 6346396 3 2021-01-09T21:54:47Z 2021-01-24T21:21:09Z 2021-01-09T22:17:28Z OWNER  

https://docs.datasette.io/en/stable/ecosystem.html is no longer needed.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1182/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
780267857 MDU6SXNzdWU3ODAyNjc4NTc= 1178 Use force_https_urls on when deploying with Cloud Run simonw 9599 closed 0   Datasette 0.54 6346396 9 2021-01-06T08:20:55Z 2021-01-24T21:21:05Z 2021-01-06T18:24:47Z OWNER  

Original title: datasette.absolute_url() should return https:// not http:// on Cloud Run

https://latest-with-plugins.datasette.io/github/issue_comments.Notebook?_labels=on currently provides http:// links, which break in Observable since it won't load http:// content.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1178/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
772438273 MDU6SXNzdWU3NzI0MzgyNzM= 1157 Use time.perf_counter() instead of time.time() to measure performance simonw 9599 closed 0   Datasette 0.54 6346396 1 2020-12-21T20:21:41Z 2021-01-24T21:20:42Z 2020-12-21T21:49:20Z OWNER  

I do that in a bunch of places: https://ripgrep.datasette.io/-/ripgrep?pattern=time%28%29&literal=on&glob=datasette%2F%2A%2A

https://docs.python.org/3/library/time.html#time.perf_counter

time.``perf_counter() → float

Return the value (in fractional seconds) of a performance counter, i.e. a clock with the highest available resolution to measure a short duration. It does include time elapsed during sleep and is system-wide. The reference point of the returned value is undefined, so that only the difference between the results of consecutive calls is valid.

New in version 3.3.

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1157/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
772408750 MDU6SXNzdWU3NzI0MDg3NTA= 1156 Rename _schemas to _internal simonw 9599 closed 0   Datasette 0.54 6346396 1 2020-12-21T19:27:58Z 2021-01-24T21:20:39Z 2020-12-21T19:51:18Z OWNER  

I like _internal as the name for the in-memory Datasette schema database better.

Refs #1154 #1150 #1155

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1156/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed
742011049 MDU6SXNzdWU3NDIwMTEwNDk= 1091 .json and .csv exports fail to apply base_url simonw 9599 closed 0   Datasette 0.54 6346396 22 2020-11-12T23:45:16Z 2021-01-24T21:20:24Z 2021-01-09T22:19:29Z OWNER  

Just tested with the latest Docker image, and it works pretty much everywhere! THANK YOU!

I did notice that if I try to export json or csv, the base is not applied. Not sure if I should reopen this issue or open a new one.

To see this, go here: https://corpora.tika.apache.org/datasette/corpora-metadata/REF_PARSE_EXCEPTION_TYPES

Click/hover over json or CSV and you'll see that the 'datasette' base is not included.

Originally posted by @tballison in https://github.com/simonw/datasette/issues/865#issuecomment-726385422

datasette 107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/1091/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);
Powered by Datasette · Queries took 39.251ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows