issue_comments

Table actions

3 rows where issue = 1603957501 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • Add optional min versions to conda-forge recipe (`run_constrained`) · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1498200620 https://github.com/pydata/xarray/issues/7573#issuecomment-1498200620 https://api.github.com/repos/pydata/xarray/issues/7573 IC_kwDOAMm_X85ZTLos ocefpaf 950575 2023-04-05T21:47:19Z 2023-04-05T21:47:19Z CONTRIBUTOR

With the current PR we would end up with two different build numbers with differing behaviour, which might confuse folks.

+1

But I'd rely on @ocefpaf's expertise.

The PR is a good idea and we, conda-forge, even though about making something like that for all packages. The problem is that optional packages metadata in Python-land is super unreliable. So, doing it on a package bases and with the original authors as part of it, it is super safe and recommended.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add optional min versions to conda-forge recipe (`run_constrained`) 1603957501
1497866542 https://github.com/pydata/xarray/issues/7573#issuecomment-1497866542 https://api.github.com/repos/pydata/xarray/issues/7573 IC_kwDOAMm_X85ZR6Eu kmuehlbauer 5821660 2023-04-05T17:31:05Z 2023-04-05T17:31:05Z MEMBER

If it helps to minimize interoperability issues I'm all in for the change. One thing I would maybe do is wait for the next version. With the current PR we would end up with two different build numbers with differing behaviour, which might confuse folks.

But I'd rely on @ocefpaf's expertise.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add optional min versions to conda-forge recipe (`run_constrained`) 1603957501
1497690966 https://github.com/pydata/xarray/issues/7573#issuecomment-1497690966 https://api.github.com/repos/pydata/xarray/issues/7573 IC_kwDOAMm_X85ZRPNW dcherian 2448579 2023-04-05T15:33:03Z 2023-04-05T15:33:03Z MEMBER

Does any one have any thoughts here? Shall we merge https://github.com/conda-forge/xarray-feedstock/pull/84/files and see if someone complains?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add optional min versions to conda-forge recipe (`run_constrained`) 1603957501

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,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);