Skip to content

Odd meta label behavior #75

Description

@Fishrock123

in nodejs/node#8466 the bot somehow is adding meta a second time...

Activity

  1. mscdex commented on Sep 9, 2016

    @mscdex
    Contributor

    AFAIK I don't think it's a bug in github-bot, but a Github UI bug? The labels were all added at the same time it looks like, so maybe a race condition issue on Github's end?

  2. phillipj commented on Sep 12, 2016

    @phillipj
    Member

    As the bot fetches the existing labels on a PR via the github API, before adding new ones which haven't already been added, I'm also leaning towards some kind of race condition here..

    Have we seen this in other PRs?

  3. jbergstroem commented on Sep 12, 2016

    @jbergstroem
    Member

    So, we add some $time? We don't have to be 0sec.

  4. mscdex commented on Sep 12, 2016

    @mscdex
    Contributor

    Either way, maybe github support should be notified about this?

    Also AFAIK checking labels first shouldn't even be necessary since github only adds the complement of the intersection of the old label set and the new label set (it does not remove existing labels).

  5. jbergstroem commented on Sep 13, 2016

    @jbergstroem
    Member

    @mscdex you want to do the honors?

  6. mscdex commented on Sep 13, 2016

    @mscdex
    Contributor

    @jbergstroem I can try, but I don't have any contacts at Github.

  7. phillipj commented on Sep 13, 2016

    @phillipj
    Member

    As the bot fetches the existing labels on a PR via the github API, before adding new ones which haven't already been added ...

    I stand corrected -- just realised we don't check existing labels anymore, as of last week w/4b6f2b3. The newest version of node-github got a new API letting us add labels which POSTs to api.github.com/repos/nodejs/node/issues/X/labels

  8. jbergstroem commented on Sep 13, 2016

    @jbergstroem
    Member

    @mscdex I've had pretty good success with their public support (https://github.com/contact) -- just ref this issue.

  9. phillipj commented on Sep 16, 2016

    @phillipj
    Member

    @mscdex keep us updated. I've see this on several PRs lately, and if GH is too busy to have a look at this, it's trivial for us revert and only add labels which haven't already been added.

  10. mscdex commented on Sep 19, 2016

    @mscdex
    Contributor

    Just got a response from Github, they've now opened an issue internally to investigate this further. They can't promise an ETA but will keep me updated.

  11. phillipj commented on May 6, 2017

    @phillipj
    Member

    FYI I've just contacted GitHub support about this again.

  12. phillipj commented on May 14, 2017

    @phillipj
    Member

    Still no progress on this internally at GitHub, and no estimate on when it will be prioritised.

    In other words, we'll have to get a work around in place to avoid this happening in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions