home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 772438273

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
772438273 MDU6SXNzdWU3NzI0MzgyNzM= 1157 Use time.perf_counter() instead of time.time() to measure performance 9599 closed 0   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.

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

Links from other tables

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