Don't start file watcher before "initial sync" is complete, when joining
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 54
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 3
Description
Describe the bug
When I join, sometimes, teamtype detects a lot of conflicts, delete files, does some random stuff.
We have to stop it and retry.
We are on the same git commit, no local changes, that's really strange.
I did not have nvim launched at all.
Versions:
teamtype --version: teamtype 0.9.1-dev (fc6d8e728 2025-12-17)
The logs are HUGE logs.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the join flow, the initial sync, and when the file watcher is started; the issue does not name specific files or tests. Use the attached logs and reproduce a join with both peers on the same Git commit and no local changes. Done means the watcher does not act until initial sync completes, avoiding the reported conflicts and deletions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100