Normally you shouldn’t have to run rad sync or restart the node. It should just magically sync in the background. If it doesn’t, something might be broken and we need to fix it.

The app doesn’t reload on new changes yet, so navigating around would show the new data, so would a restart or a manual reload.

Yes, so that’s what I’d expect. I mean I regularly need to restart/rad sync, maybe b/c my computer sleeps/wakes up multiple times between usages, I’m not sure. But no indication is a little misleading

Are you running the latest radicle stack? What’s your rad --version?

Not really related with debugging why it doesn’t sync, but I wrote a patch 6fca8ec458639ac22f48bb7c3e79fa1c5b2b9825 that would help to display to users that maybe there are new things out there for a repo and they should maybe try to sync.

Ok, so I just ran into this issue myself, so adding a +1 here. To me this seems to be a node/protocol issue, because things should just be in-sync automatically. If they are not, I’m not sure we’ll be able to detect it anyway.

The way it manifested on my end was that I was seeing @daniel’s issues in app.radicle.xyz on seed.radicle.xyz, but not locally in my desktop app. Only when I ran rad sync in the desktop repo the issues appeared. My node is always on and I’ve set Announce Changes to “Right Away”.

I think we should report this higher up in heartwood.

Now that I think of it, I should have run rad sync status first in the repo to see what’s the status. We should monitor and try to debug this.

Yeah I think this is definitely something we should bring up to the heartwood people. Also not so sure anymore if we want to have the added complexity of querying all repos for their status. Could work now but maybe the workload will be too high in the future.

Mentioned here in dogfood.