Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ghactions.notifyHandler doesn't get called for requests to /api/checks/github-actions #4009

Closed
past opened this issue Sep 20, 2024 · 1 comment · Fixed by #4017
Closed

ghactions.notifyHandler doesn't get called for requests to /api/checks/github-actions #4009

past opened this issue Sep 20, 2024 · 1 comment · Fixed by #4017
Labels
back-end bug Something isn't working

Comments

@past
Copy link
Member

past commented Sep 20, 2024

See the discussion at web-platform-tests/wpt#48223. This run should have ended up at ghactions.notifyHandler, but instead was handled by checks.updateCheckHandler.

@past
Copy link
Member Author

past commented Sep 20, 2024

I believe #4010 and web-platform-tests/wpt#48293 will fix this.

gsnedders added a commit to gsnedders/wpt.fyi that referenced this issue Sep 24, 2024
Per the mux docs, "Routes are tested in the order they were added to
the router. If two routes match, the first one wins."

This means that `checks.RegisterRoutes()` needs to be called after
everything else defining a route in /api/checks/ as it otherwise
matches every path under /api/checks/.
past pushed a commit that referenced this issue Sep 25, 2024
Per the mux docs, "Routes are tested in the order they were added to
the router. If two routes match, the first one wins."

This means that `checks.RegisterRoutes()` needs to be called after
everything else defining a route in /api/checks/ as it otherwise
matches every path under /api/checks/.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end bug Something isn't working
Projects
None yet
1 participant