Pinned not updating until refresh

[filippocrocchini]

When I pin/unpin a card I have to refresh the page in order for it to actually show in or get removed from the pinned stack.
I can reproduce it in both Firefox and Chrome.

Not sure if this is a known issue since it's only happening if I run the docker container but not on https://app.fizzy.do.

[farfromexact]

The fact that it reproduces in Firefox and Chrome but only in the Docker deployment strongly suggests a client-side cache or asset-version difference, although the server mutation should still be verified.

I would check this sequence:

1. Pin a card, inspect the network response, and reload the page. Confirm that the server now returns the updated pinned state.
2. If the server is correct, inspect whether the Docker image has the same frontend commit and compiled JavaScript assets as app.fizzy.do.
3. Check the browser console and whether the pin action updates a Turbo frame or client-side store that is actually present in the self-hosted build.
4. Unpin the same card in a second tab to see whether the stale state is local to one page or shared by the server response.

A useful regression test would assert both the mutation and the rendered pinned stack without a full page refresh. If the mutation response is successful but the list is stale, invalidate or replace the relevant frame or cache entry after the action. Please include the Docker image tag, commit, browser console output, and the response body from the pin request; that will separate an old asset bundle from a server-side persistence problem.

[filippocrocchini]

I compared network traffic between docker and app.fizzy.do and I can't tell any difference, both in requests and responses.
I don't know how turbo not fizzy work and cannot debug this further, I hope you are able to reproduce the problem otherwise I don't know what else to do. I used the latest docker container available, I don't think there's a way for me to know what commit app.fizzy.do is using.