The I/O handling fix now logs an unreadable discovery entry, but index create still exits successfully with a zero-file index when the project root does not exist.
Reproduction:
$ rustytokens index create /path/that/does/not/exist
rustytokens: skipped unreadable entry: ... No such file or directory
{
"files": 0,
"imports": 0,
"symbols": 0
}
$ echo $?
0
A typo in the project path should fail explicitly rather than create a misleading empty database. Validate that the root exists and is a directory before walking it; keep the warning behavior for individual unreadable entries if desired.
The I/O handling fix now logs an unreadable discovery entry, but `index create` still exits successfully with a zero-file index when the project root does not exist.
Reproduction:
```text
$ rustytokens index create /path/that/does/not/exist
rustytokens: skipped unreadable entry: ... No such file or directory
{
"files": 0,
"imports": 0,
"symbols": 0
}
$ echo $?
0
```
A typo in the project path should fail explicitly rather than create a misleading empty database. Validate that the root exists and is a directory before walking it; keep the warning behavior for individual unreadable entries if desired.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The I/O handling fix now logs an unreadable discovery entry, but
index createstill exits successfully with a zero-file index when the project root does not exist.Reproduction:
A typo in the project path should fail explicitly rather than create a misleading empty database. Validate that the root exists and is a directory before walking it; keep the warning behavior for individual unreadable entries if desired.
Fixed in commit
a416a9f.