home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 1377811868

This data as json

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
1377811868 I_kwDOBm6k_c5SH72c 1813 missing next and next_url in JSON responses from an instance deployed on Fly 883348 closed 0     1 2022-09-19T11:32:34Z 2022-09-19T11:34:45Z 2022-09-19T11:34:45Z CONTRIBUTOR  

👋 thank you for an incredibly useful project!

I have noticed that my deployed instance on Fly does not include the next and next_url keys even for a truncated response :

This is publically accessible here: https://collectif-objets-datasette.fly.dev/collectif-objets.json?sql=select+*+from+mairies

However when I run the dataset server locally with the same data I get these next keys for the exact same query:

I am wondering if I've missed some config or something specific to deployments on Fly.io?

I am running datasette v0.62, without any specific config :

  • locally poetry run datasette data/collectif-objets.sqlite
  • for the deploy : poetry run datasette publish fly data/collectif-objets.sqlite

as visible in the Makefile. The very limited codebase is public but the sqlite db is not versioned yet because it is too large.

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

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 1 row from issue in issue_comments
Powered by Datasette · Queries took 1.003ms · About: github-to-sqlite