Cause (Documented platform behavior): macOS FSEvents limit (not directly configurable).
Fix status: documented_behavior
Limitations:
- Doc-derived; not reproduced.
Other error fragments:
- Recrawled this watch 1 time, most recently because:
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/facebook/watchman/e8cbdc2e8137c61e3036bd2c4a3f6116e87ddb72/website/docs/troubleshooting.md (official_docs, unknown, documented_behavior): Recrawl section: kFSEventStreamEventFlagUserDropped indicates hitting macOS limits; increase fsevents_latency; warning persists until watch re-established or server restarted.
Search phrasings: kFSEventStreamEventFlagUserDropped recrawl; watchman Recrawled this watch warning jest; fsevents_latency watchmanconfig
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Warning in watchman responses (surfaced by Jest/Metro); expensive full recrawls mark files changed, triggering spurious rebuilds/test reruns.
- Context
- Product: Watchman Component: recrawl on FSEvents overflow Operation: Large repos with heavy churn (installs, builds, git checkouts) under watchman on macOS Affected versions: unknown Environment: macOS Packages: watchman current docs Trigger: Change rate exceeds FSEvents internal buffering; events dropped.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- kFSEventStreamEventFlagUserDropped
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Watchman on macOS] 'Recrawled this watch N times, most recently because: ... kFSEventStreamEventFlagUserDropped' — FSEvents queue overflow; clients see all files as changed
Recommended action: Increase fsevents_latency in .watchmanconfig (watchman >= 3.2); reduce churn inside watched roots; clear the sticky warning with `watchman shutdown-server`.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 9e2c8925-b147-425b-bccb-6a2cdca0c05a
- Proposed action
- Recommended action: Increase fsevents_latency in .watchmanconfig (watchman >= 3.2); reduce churn inside watched roots; clear the sticky warning with `watchman shutdown-server`.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.