docs: add troubleshooting steps for ENOTFOUND error
This commit is contained in:
parent
2166cdc91a
commit
efdc220554
29
README.md
29
README.md
|
@ -42,7 +42,34 @@ As "documentation" `flake.nix` shows the internals, and
|
||||||
command was used to generate it.
|
command was used to generate it.
|
||||||
|
|
||||||
### Troubleshooting
|
### Troubleshooting
|
||||||
An common error is:
|
|
||||||
|
When running `deno task serve`, if you see an error message like:
|
||||||
|
|
||||||
|
```
|
||||||
|
NotFound: No such file or directory (os error 2): stat '/home/<user>/.../git.pub.solar/pub-solar/pub.solar/.direnv/flake-inputs/5acdh8xyry0kdvp6xla2hw7wf3zkphkl-source/pkgs/test/nixpkgs-check-by-name/tests/symlink-invalid/pkgs/by-name/fo/foo/foo.nix'
|
||||||
|
at Object.statSync (ext:deno_fs/30_fs.js:362:7)
|
||||||
|
at FS.#walkLink (https://deno.land/x/lume@v2.0.1/core/fs.ts:143:23)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:117:23)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21)
|
||||||
|
at FS.#walkFs (https://deno.land/x/lume@v2.0.1/core/fs.ts:136:21) {
|
||||||
|
name: "NotFound",
|
||||||
|
code: "ENOENT"
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
try removing the .direnv directory:
|
||||||
|
|
||||||
|
```
|
||||||
|
rm -rf .direnv
|
||||||
|
deno task serve
|
||||||
|
```
|
||||||
|
|
||||||
|
Another common error message after updating dependencies is:
|
||||||
|
|
||||||
```
|
```
|
||||||
22.31 error: The source code is invalid, as it does not match the expected hash in the lock file.
|
22.31 error: The source code is invalid, as it does not match the expected hash in the lock file.
|
||||||
|
|
Loading…
Reference in a new issue