-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
project.py: request users to stop IDEs before running west init
#703
project.py: request users to stop IDEs before running west init
#703
Conversation
There have been many users reports in zephyrproject-rtos#558 that `west init` fails on the Windows NTFS filesystem when some IDEs are running concurrently. There is no simple and reliable fix for this because: - The lack of concurrency is a core limitation in the NTFS design that will not change anytime soon, - IDEs have no reliable way to know when they should pause scanning the filesystem. - Placing temporary files outside the workspace would invite other, complex and nasty issues with cross-filesystem moves (zephyrproject-rtos#558) Short of a fix, explain why this happens very briefly in `west init -h` and request users to temporarily close their IDEs. It's the only simple and universal mitigation available. Mention the issue number in case someone needs more details, some evidence or smarter workarounds specific to certain IDEs. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
The whole installation process is very inconvenient. |
I don't remember BTW this particular NTFS design issue is not specific to west, it has been reproduced without west in #558. |
This is really off-topic but I heard that https://docs.platformio.org/en/latest/frameworks/zephyr.html is much more user-friendly than plain Zephyr. I never tried it myself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit of a drive-by review, but LGTM.
For VS Code, I believe temporarily disabling the git.autoRefresh
setting would be enough, actually, but it has a pretty extensive file watching system, so you never know.
filesystem. Find other, similar "Access is denied" examples in west | ||
issue #558. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
filesystem. Find other, similar "Access is denied" examples in west | |
issue #558. | |
filesystem. Find other, similar "Access is denied" examples in | |
https://github.com/zephyrproject-rtos/west/issues/558. |
Most terminals make links clickable these days, so this is worth spelling out, IMO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered this but I tried to minimize the length as much as possible. In fact I was a bit reluctant to add this at all because a help text should be really concise and not turn into a changelog or bug list. However this particular bug seems frequent, fatal and totally unfixable.
There have been many users reports in #558 that
west init
fails on the Windows NTFS filesystem when some IDEs are running concurrently.There is no simple and reliable fix for this because:
Short of a fix, explain why this happens very briefly in
west init -h
and request users to temporarily close their IDEs. It's the only simple and universal mitigation available.Mention the issue number in case someone needs more details, some evidence or smarter workarounds specific to certain IDEs.