Fix handling of UVWASI_LOOKUP_SYMLINK_FOLLOW in uvwasi_path_filestat_get #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If uvwasi_path_filestat_get the pathname is resolved by
uvwasi__resolve_path which honors the UVWASI_LOOKUP_SYMLINK_FOLLOW
flag.
Later we were we unconditionally calling uv_fs_stat which always
follows symlinks. Instead we want to unconditionally call uv_fs_lstat
which never follows them (since the resolution was already handled
by the preceding call to uvwasi__resolve_path).