issues

Table actions

3 rows where repo = 107914493 and user = 10352819 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

type 2

state 1

repo 1

  • datasette · 3 ✖
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
471292050 MDU6SXNzdWU0NzEyOTIwNTA= 563 incorrect json url for row-level data? rprimet 10352819 closed 0     0 2019-07-22T19:59:38Z 2019-10-21T02:03:09Z 2019-10-21T02:03:09Z CONTRIBUTOR  

While visiting this example page (linked from Datasette documentation), manually clicking on the link ("This data as .json") to the json data results in an error 500 data() got an unexpected keyword argument 'as_format'

The JSON page linked to from the documentation however is correct (the page address ends in .json rather than using a query string ?format=json)

This particular datasette demo page is now a few versions behind, but I was able to reproduce the issue using v0.29.2 and a downloaded copy of the demo database (and also with the current HEAD).

Here is a stack trace:

``` Traceback (most recent call last): File "/home/romain/miniconda3/envs/dsbug/lib/python3.7/site-packages/datasette/utils/asgi.py", line 101, in call return await view(new_scope, receive, send) File "/home/romain/miniconda3/envs/dsbug/lib/python3.7/site-packages/datasette/utils/asgi.py", line 173, in view request, scope["url_route"]["kwargs"] File "/home/romain/miniconda3/envs/dsbug/lib/python3.7/site-packages/datasette/views/base.py", line 267, in get request, database, hash, correct_hash_provided, kwargs File "/home/romain/miniconda3/envs/dsbug/lib/python3.7/site-packages/datasette/views/base.py", line 399, in view_get request, database, hash, **kwargs TypeError: data() got an unexpected keyword argument 'as_format'

```

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/563/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
434321685 MDExOlB1bGxSZXF1ZXN0MjcxMzM4NDA1 434 "datasette publish cloudrun" command to publish to Google Cloud Run rprimet 10352819 closed 0     8 2019-04-17T14:41:18Z 2019-05-03T21:50:44Z 2019-05-03T13:59:02Z CONTRIBUTOR simonw/datasette/pulls/434

This is a very rough draft to start a discussion on a possible datasette cloud run publish plugin (see issue #400).

The main change was to dynamically set the listening port in make_dockerfile to satisfy cloud run's requirements.

This was done by running datasette through sh to get environment variable substitution. Not sure if that's the right approach?

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/434/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
398559195 MDU6SXNzdWUzOTg1NTkxOTU= 400 datasette publish cloudrun plugin rprimet 10352819 closed 0     1 2019-01-12T14:35:11Z 2019-05-03T16:57:35Z 2019-05-03T16:57:35Z CONTRIBUTOR  

Google announced that they may launch a simple service for running Docker containers (previously serverless containers, now called "cloud run" -- link to alpha here). If/when this happens, it might be a good fit for publishing datasettes? (at least using the current version, manually publishing a datasette seems relatively painless).

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/400/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]);