pull down to refresh

0 sats \ 7 replies \ @WeAreAllSatoshi 30 Aug 2023 \ parent \ on: Weird SN bug I just found. meta
Could it be some kind of SSR caching issue? I don't see any graphql fetch calls with the temporary user profile data...
ETA: I do see the rogue user profile data in the HTML payload from the server, so that would seem likely ^ though idk why
write
preview
0 sats \ 4 replies \ @k00b 30 Aug 2023
This was a way, dare I say, cooler bug involving closures around getGetServerSideProps parameters.
I thought I was being efficient by reusing them for storage inside the closure, but I was "enclosing" the changes to the parameters. The next time the function was called, it was using the enclosed values and not the parameters.
reply
0 sats \ 3 replies \ @WeAreAllSatoshi 30 Aug 2023
That is very interesting. I'll keep an eye out for the commit that fixes it, I'd like to take a look!
reply
21 sats \ 2 replies \ @k00b 31 Aug 2023
Pushed
reply
2292 sats \ 1 reply \ @ryu OP 31 Aug 2023
This is proof anyone can contribute to FOSS projects without having to know a single line of code.
Bless.
reply
110 sats \ 0 replies \ @nemo 31 Aug 2023
deleted by author
reply
0 sats \ 1 reply \ @k00b 30 Aug 2023
It's probably cache related but it could also be query params getting sent as null or something because it's the same handful of wrong users.
reply
0 sats \ 0 replies \ @k00b 30 Aug 2023
We were all seeing the same stackers because we were all sharing the closure state.
reply