pull down to refresh

10.1k sats \ 9 replies \ @k00b 23 Jun \ parent \ on: Stacker Saloon
~lol I'll comment here when it's done
write
preview
1361 sats \ 0 replies \ @optimism 23 Jun
It worked. Thanks k00b!
reply
0 sats \ 7 replies \ @optimism 23 Jun
Minor follow-up issue: my /notifications now forwards to /404.
reply
0 sats \ 6 replies \ @k00b 23 Jun
What does it say in the browser console? nevermind .. if it's forwarding to 404 it's in the server logs.
reply
0 sats \ 5 replies \ @optimism 23 Jun
I've also turned on diagnostics for the time being, but nothing visible in console so I doubt it helps?
reply
0 sats \ 4 replies \ @k00b 23 Jun
yep, not going to be visible on your end. i'm combing the logs now. so sorry (but glad i waited to deploy until i had time to diagnose)
reply
100 sats \ 0 replies \ @optimism 23 Jun
These kind of edge cases are hard to test for too. Been there done that. No need to apologize. As long as no one else revives a territory I'm probably the only affected user and I can handle it, so it's a good way to debug it like this.
reply
100 sats \ 2 replies \ @k00b 23 Jun
I think I found it. I'll ship as soon as it's fixed.
It's a case sensitivity issue on an implicit join on the territory name.
https://github.com/prisma/prisma/issues/14935
reply
1000 sats \ 1 reply \ @k00b 23 Jun
should be fixed
view all 1 replies