Alex Goodman 901d7bbab2 fix: don't infer archive nesting from paths in error text ...

`ProcessPathErrors` cut the `path="..."` it pulled out of an error at the first `!/` and built nested
coordinates from it, so a host file with `!/` in its name was reported as a file inside an archive.

- paths from error text are taken as plain real paths again, as on main
- the php extension reader already has the location in hand, so it records the unknown against that
  instead of re-parsing the error (this is the one caller that could see a nested path). It also
  no longer defers `Close` on a nil reader when the read fails

Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>

2026-10-21 11:28:53 -04:00

..

coordinate_error_test.go

fix: keep RealPath as top-level, use FullPath and utility functions FullNestedPath, LocalPath, Path

2026-10-19 15:44:37 -04:00

coordinate_error.go

fix: keep RealPath as top-level, use FullPath and utility functions FullNestedPath, LocalPath, Path

2026-10-19 15:44:37 -04:00

path_error_test.go

fix: don't infer archive nesting from paths in error text

2026-10-21 11:28:53 -04:00

path_error.go

fix: don't infer archive nesting from paths in error text

2026-10-21 11:28:53 -04:00