Desktop shows “Repository not initialized” for a working self-hosted repo after restart
- Dominant language
- Rust
- Stars
- 32.7k
- Forks
- 4.3k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 253
Description
## Describe the bug
I ran into a Git repository that works normally until I quit and reopen Buzz Desktop.
The repository was created on a self-hosted Buzz relay. I could push a commit, open the README, and browse the repository without any trouble. After a full `Cmd+Q` and relaunch, though, Buzz reported:
> Repository not initialized
> The project announcement exists, but its git repository was not found on the Buzz relay.
Retrying or fetching from the UI did not recover it.
## Steps to reproduce
1. Connect Buzz Desktop to a self-hosted relay.
2. Create a project and Git repository.
3. Assign an access channel.
4. Push a commit and confirm the README and files load in Desktop.
5. Quit Buzz Desktop completely with `Cmd+Q`.
6. Relaunch it and open the same repository.
## Expected behavior
The repository should still be available after restarting the app.
## Actual behavior
Desktop shows the repository as `Local missing` and says it was not found on the relay.
The local checkout is still present, and its `origin` points to the correct relay URL.
## Environment
- Buzz Desktop 0.5.20
- macOS
- Git 2.50.1
- Self-hosted Buzz relay 0.2.1
## Additional context
I checked the relay before and after restarting Desktop:
- the latest repository announcement still has the correct access channel
- the repository owner is still an active member of that channel
- the relay accepted the Git push and published the derived manifest event
- both the repository pointer and manifest are present in object storage
- the same repository worked in the original Desktop process before it was restarted
This looks related to #5186, but the failure seems different. In this case the pointer and manifest already exist, and the repository is usable until Desktop restarts.
I have reproduced this on the latest release, but not yet on a build from `main`. I’d be happy to test a patch or a current main build if that would help narrow it down.
Note: I’m not a native English speaker. This issue was originally written in Korean and then translated into English.
Contributor guide
Assessment
This issue has not been assessed yet.