Update content hash item limit to prevent Watchman crawl failed errors#2629
Update content hash item limit to prevent Watchman crawl failed errors#2629chipsnyder merged 2 commits intodevelopfrom
Conversation
| @@ -1 +1,3 @@ | |||
| {} | |||
| { | |||
| "content_hash_max_items": 400000 | |||
There was a problem hiding this comment.
This number was obtained by running find . | wc -l from the gutenberg-mobile root
|
Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job! |
|
Hey @hypest Would I be able to get you to take a look at this PR as well? It's the same change as WordPress/gutenberg#25385 but handles it for the GB-mobile side. |
👋 Chip, sure! I still am not able to reproduce the issue, and this time I tried lowering the |
That seems odd to me that a clean and a reset isn't able to fix the issue for you. Do you happen to have a file in I would think lowering the number to |
To be clear, it's not that the fix doesn't work for me but rather, I don't see the original issue so can't verify that the fix actually works. The PR doesn't seem to break the build on my side anyway though so, I'm OK with merging since it fixes it for you. If the issue ends up not being fixed anyway we can revisit. How's that sound? |
I think that's a good plan :) It's an easy enough line to remove if it does cause trouble. |
hypest
left a comment
There was a problem hiding this comment.
LGTM!
Also, reminder to update to resolve the merge conflict.
Related-PRWordPress/gutenberg#25385Fixes:
While running the metro server locally we'll see the error:
This error will occur when our file size has outgrown the default cache size of metro (more info in this SO answer) This increases the content hash size limit to prevent the error.
To test:
npm run cleannpm start --reset-cacheExpect The Metro server to start without displaying the cache failure error
PR submission checklist: