The Jtech Homepage logs this error to the console
forumapi-vvtyqkmgxa-uc.a.run.app/forum/leaderboard/6?period=monthly:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
The Jtech Homepage logs this error to the console
forumapi-vvtyqkmgxa-uc.a.run.app/forum/leaderboard/6?period=monthly:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Anyone knows the reason for this or how to fix?
@TripleU any idea?
@ars18 any idea?
I believe the error is caused by a error
That’s helpful, but I can’t see the server logs to find the error to suggest a fix
its google cloud run I think
What exactly is not working
Lemme check the source
@TripleU can’t test, don’t have env for firebase.
The reason it’s not working is because it’s using auth for leaderboard when you don’t need it, works fine without.
Make auth=false for proxy when it comes to leaderboard.
Was ANOTHER dumbcourse bug. fixed.
Fastest I’ve ever opened and closed a pr ![]()
We raced bro. I WON. FACE IT.
kidding didn’t know you were on it
I also tried doing it but you told me to test before opening a pr so I saw that you changed it before I was able to submit
#NoMoreYOLO
test passed
Haha I couldn’t fully test locally, so I wrote that in the pr.
Firebase env
I had claude create a test script and I ran it
Test script for what
Discourse leaderboard data is publicly accessible and does not require API-key authentication. Previously, every proxyJson call unconditionally attached the Discourse API key, which:
DISCOURSE_API_KEY environment variable was not configured — even though the leaderboard endpoint doesn’t need it.By making authentication opt-in per route, the leaderboard proxy works without a configured API key, while all other routes (/forum/latest, /forum/about, /forum/topic/:id) continue to authenticate as before.
passed,