issues

Table actions

11 rows where milestone = 4471010 and state = "closed" sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 2

state 1

  • closed · 11 ✖

repo 1

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
465001185 MDU6SXNzdWU0NjUwMDExODU= 549 Send pull request to the repo that the _table.html template will break simonw 9599 closed 0   Datasette 0.29 4471010 1 2019-07-07T22:45:17Z 2019-07-08T03:36:46Z 2019-07-08T03:36:45Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/549/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
464990184 MDU6SXNzdWU0NjQ5OTAxODQ= 547 Release notes for 0.29 simonw 9599 closed 0   Datasette 0.29 4471010 2 2019-07-07T20:30:28Z 2019-07-08T03:31:59Z 2019-07-08T03:31:59Z OWNER   datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/547/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
445868234 MDU6SXNzdWU0NDU4NjgyMzQ= 478 Make it so Docker build doesn't delay PyPI release simonw 9599 closed 0   Datasette 0.29 4471010 3 2019-05-19T21:52:10Z 2019-07-08T03:30:41Z 2019-07-07T20:03:20Z OWNER  

Datasette automated releases currently include building a Docker image that has a full custom-compiled version of SQLite and SpatiaLite. This takes ages!

I still want to publish this Docker image (to https://hub.docker.com/r/datasetteproject/datasette/tags ) but I'd like it if this wasn't a blocker on pushing the new package to PyPI. Ideally PyPI publish would happen first.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/478/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
464868844 MDU6SXNzdWU0NjQ4Njg4NDQ= 543 datasette publish option for setting plugin configuration secrets simonw 9599 closed 0   Datasette 0.29 4471010 3 2019-07-06T16:21:23Z 2019-07-08T02:06:34Z 2019-07-08T02:06:34Z OWNER  

Follow-on from #538 - the datasette publish command needs a way of passing secrets which will be made available to plugin configuration but will not be exposed in /-/metadata.json.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/543/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
464894812 MDExOlB1bGxSZXF1ZXN0Mjk1MDY1Nzk2 544 --plugin-secret option simonw 9599 closed 0   Datasette 0.29 4471010 1 2019-07-06T22:18:20Z 2019-07-08T02:06:31Z 2019-07-08T02:06:31Z OWNER simonw/datasette/pulls/544

Refs #543

  • [x] Zeit Now v1 support
  • [x] Solve escaping of ENV in Dockerfile
  • [x] Heroku support
  • [x] Unit tests
  • [x] Cloud Run support
  • [x] Documentation
 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/544/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
464994105 MDU6SXNzdWU0NjQ5OTQxMDU= 548 Add datasette-cors and datasette-auth-github plugins to Ecosystem page simonw 9599 closed 0   Datasette 0.29 4471010 0 2019-07-07T21:14:14Z 2019-07-08T02:02:36Z 2019-07-08T02:02:36Z OWNER  
datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/548/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
465002978 MDU6SXNzdWU0NjUwMDI5Nzg= 550 Pull m2m faceting out of master so we can ship a release without it simonw 9599 closed 0   Datasette 0.29 4471010 1 2019-07-07T23:10:48Z 2019-07-07T23:21:22Z 2019-07-07T23:21:22Z OWNER  

After spending some time with #495 I believe I need to make some pretty major changes to how m2m faceting works. I don't want it to block the release of ASGI Datasette so I'm going to revert it back out of master for the moment and merge it back in after the release has gone out.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/550/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
446433735 MDU6SXNzdWU0NDY0MzM3MzU= 482 Example of a custom facet plugin is incorrect simonw 9599 closed 0   Datasette 0.29 4471010 0 2019-05-21T06:12:47Z 2019-07-07T23:19:10Z 2019-07-07T23:19:10Z OWNER  

The function signatures are wrong on https://datasette.readthedocs.io/en/0.28/plugins.html#register-facet-classes

The new signatures are: async def suggest(self) and async def facet_results(self) - the sql and params are now passed to the class constructor.

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/482/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
453829910 MDU6SXNzdWU0NTM4Mjk5MTA= 505 Add white-space: pre-wrap to SQL create statement simonw 9599 closed 0 simonw 9599 Datasette 0.29 4471010 0 2019-06-08T19:59:56Z 2019-07-07T20:26:55Z 2019-07-07T20:26:55Z OWNER  

Right now a super-long CREATE TABLE statement causes the table page to be even wider than the table itself:

Adding white-space: pre-wrap to that <pre> element is an easy fix:

 datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/505/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
464905894 MDU6SXNzdWU0NjQ5MDU4OTQ= 545 Fix header on 404 page simonw 9599 closed 0   Datasette 0.29 4471010 1 2019-07-07T01:47:40Z 2019-07-07T20:26:55Z 2019-07-07T20:26:55Z OWNER  

datasette 107914493 issue     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/545/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
445875242 MDExOlB1bGxSZXF1ZXN0MjgwMjA1NTAy 480 Split pypi and docker travis tasks glasnt 813732 closed 0   Datasette 0.29 4471010 1 2019-05-19T23:14:37Z 2019-07-07T20:03:20Z 2019-07-07T20:03:20Z CONTRIBUTOR simonw/datasette/pulls/480

Resolves #478

This should work, but because this is a change that'll only really be testable on a) this repo, b) master branch, this might fail fast if I didn't get the configurations right.

Looking at #478 it should just be as simple as splitting out the docker and pypi processes into separate jobs, but it might end up being more complicated than that, depending on what pre-processes the pypi deployment needs, and how travisci treats deployment steps without scripts in general.

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

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]);