mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 08:18:15 +03:00
f7c66f9786
Summary: For non-UTF8 names, the PathComponent constructor would raise an exception, and since that exception wasn't caught by the handler itself, it would bubble up to the RPC server and a generic "server IO error" would be sent back to the client. Since non-UTF8 names aren't a server error, but an invalid argument, we should instead return a different error. Unfortunately, EILSEQ isn't an error that an NFS server can return, instead let's use EINVAL as the argument is clearly invalid. Reviewed By: chadaustin Differential Revision: D28482032 fbshipit-source-id: b59044f1a76f7eac79e2df07356a0aeafa22e3c5 |
||
---|---|---|
.. | ||
benchharness | ||
benchmarks | ||
cli | ||
cli_rs | ||
config | ||
docs | ||
fuse | ||
inodes | ||
journal | ||
model | ||
monitor | ||
nfs | ||
notifications | ||
prjfs | ||
py | ||
rocksdb | ||
scripts | ||
service | ||
sqlite | ||
store | ||
takeover | ||
telemetry | ||
testharness | ||
third-party | ||
utils | ||
CMakeLists.txt |