-
Notifications
You must be signed in to change notification settings - Fork 16
[$250] Cannot create Webook #423
Comments
@maxceem - What sort of access rights do you have to that repo? |
@jmgasper I'm admin there |
@afrisalyp - Any idea on this one? |
@afrisalyp - I think that we're running into one of the "brown outs" listed here: https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param We'll need to fix this ASAP, thanks! |
@jmgasper Okay, going to check it. |
@jmgasper Fixes provided to support the Github API changes. |
@afrisalyp - Thanks! @maxceem - This should start working again shortly, and we'll plan a production deploy for next week to apply the permanent fix. |
@jmgasper The fix addresses the Github API change. I am still investigating the problem Any idea? |
@afrisalyp - Sorry, I just assumed it was failing because of the incorrect token approach. I'll open up a separate ticket to keep investigating. |
Challenge https://www.topcoder.com/challenges/d33759f3-21e7-457c-a042-34bf812bb1d7 has been created for this ticket. |
Challenge https://www.topcoder.com/challenges/d33759f3-21e7-457c-a042-34bf812bb1d7 has been assigned to afrisalyp. |
@maxceem - Can you try again now please? I'm interested to see if this is still an issue now that the brownout is over in the Github API. |
Challenge https://www.topcoder.com/challenges/d33759f3-21e7-457c-a042-34bf812bb1d7 afrisalyp has been unassigned. |
@jmgasper yeah, it's still there, just checked: |
Challenge https://www.topcoder.com/challenges/d33759f3-21e7-457c-a042-34bf812bb1d7 has been assigned to afrisalyp. |
@maxceem - In Topcoder-X (x.topcoder.com) can you try going into settings, revoking your Github token, and then renewing it please? |
@jmgasper revoking GitHub token and setting it up again didn't help, see demo video https://monosnap.com/file/oOxHDY3nYchkZWNIu8rTsJ1qMh0rlv. It didn't redirect me anywhere during setting up a new token, not sure if this is expected or no. |
Can you please try to revoke the TCX apps in the Github Applications setting? Then please try to revoke and re-setup again on the TCX website. It will take us to the Github authorization page. Please make sure that you have been granted to the organisation. |
Thanks for details @afrisalyp this time I've managed to reauthorize the topcoder-x app, but it didn't help in general. After I removed the application from my settings, and click revoke/setup inside Topcoder-X settings, it did redirect me to the authorise app page, and I can see access to the organisations is there: Though when I'm trying to re-created webhooks I got the same error: Btw, I gave it a try with another repository from the same organisation and it did work: This is super weird as I'm admin in both repos. And in both repos TopcoderX worked for me before. |
Thanks @maxceem Btw, can you open the webhook setting like this? |
Sure @afrisalyp here is how the page looks like I've added some hook using After that I've tried again to use Topcoder X, but got error again |
That's weird :) Can you please help to check with this curl command. Let see if it works.
|
@afrisalyp yeah, super weird :) I've tried these commands and both worked good to me: |
Can you please help to check in the DB record? Please check records in the Project table with
Thanks. |
@afrisalyp - I've requested these details. |
Sure thanks. |
@afrisalyp / @maxceem - |
Thank you @jmgasper @afrisalyp it helped! Just for reference: |
Most TCX functionalities that need Github access such as auto commenting and labelling uses copilot access. Any idea on this? |
@afrisalyp - Yeah, I've been discussing with Topcoder. I think for now we'll just chalk this up as an edge case. |
Payment task has been updated: https://www.topcoder.com/challenges/d33759f3-21e7-457c-a042-34bf812bb1d7 |
Topcoder-X stopped working for one of my repo where it previously worked, it didn't react to assigning Topcoder-X labels. So I decided trying to re-create webhooks. First I removed existent webhook from the repo, and then I tried to create it again using Topcoder X UI, but got an error:
The text was updated successfully, but these errors were encountered: