issue_comments

Table actions

4 rows where issue = 677272618 and user = 9599 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • simonw · 4 ✖

issue 1

  • Test failures caused by failed attempts to mock pip · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
672379897 https://github.com/simonw/datasette/issues/928#issuecomment-672379897 https://api.github.com/repos/simonw/datasette/issues/928 MDEyOklzc3VlQ29tbWVudDY3MjM3OTg5Nw== simonw 9599 2020-08-12T00:07:49Z 2022-02-23T16:19:47Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Test failures caused by failed attempts to mock pip 677272618  
672373061 https://github.com/simonw/datasette/issues/928#issuecomment-672373061 https://api.github.com/repos/simonw/datasette/issues/928 MDEyOklzc3VlQ29tbWVudDY3MjM3MzA2MQ== simonw 9599 2020-08-11T23:56:19Z 2020-08-11T23:56:19Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Test failures caused by failed attempts to mock pip 677272618  
672372465 https://github.com/simonw/datasette/issues/928#issuecomment-672372465 https://api.github.com/repos/simonw/datasette/issues/928 MDEyOklzc3VlQ29tbWVudDY3MjM3MjQ2NQ== simonw 9599 2020-08-11T23:54:28Z 2020-08-11T23:54:28Z OWNER

While debugging this I found a useful clue in https://github.com/pypa/pip/blob/e060970d51c5946beac8447eb95585d83019582d/src/pip/_internal/cli/main.py#L23-L47

```

Do not import and use main() directly! Using it directly is actively

discouraged by pip's maintainers. The name, location and behavior of

this function is subject to change, so calling it directly is not

portable across different pip versions.

In addition, running pip in-process is unsupported and unsafe. This is

elaborated in detail at

https://pip.pypa.io/en/stable/user_guide/#using-pip-from-your-program.

That document also provides suggestions that should work for nearly

all users that are considering importing and using main() directly.

However, we know that certain users will still want to invoke pip

in-process. If you understand and accept the implications of using pip

in an unsupported manner, the best approach is to use runpy to avoid

depending on the exact location of this entry point.

The following example shows how to use runpy to invoke pip in that

case:

sys.argv = ["pip", your, args, here]

runpy.run_module("pip", run_name="main")

Note that this will exit the process after running, unlike a direct

call to main. As it is not safe to do any processing after calling

main, this should not be an issue in practice.

```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Test failures caused by failed attempts to mock pip 677272618  
672372197 https://github.com/simonw/datasette/issues/928#issuecomment-672372197 https://api.github.com/repos/simonw/datasette/issues/928 MDEyOklzc3VlQ29tbWVudDY3MjM3MjE5Nw== simonw 9599 2020-08-11T23:53:38Z 2020-08-11T23:53:38Z OWNER

Caused by the tests for #925

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Test failures caused by failed attempts to mock pip 677272618  

Advanced export

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

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);