fix: resolve 500s on nest-details endpoints under Docker deployment

NestReader opened .pep files with FileStream(path, FileMode.Open), which
defaults to FileAccess.ReadWrite. The forge deployment bind-mounts
/mnt/pep-nest read-only, so every read-only open was rejected with
"Read-only file system" (EROFS) even though the code never writes.
Pass FileAccess.Read/FileShare.Read explicitly, matching DrawingReader
and ZipHelper elsewhere in PepLib.Core.

Once that was fixed, a second pre-existing bug surfaced: GetNestDetailsAsync
matched DB rows by NestName AND a literal Path comparison built from the
container's local mount path. NestHeader.Path stores the original Windows
UNC share path (e.g. \REMCOSRV0\pep nest\) from when PepApi ran directly
against the network share, so the comparison can never match post-Docker.
Match by NestName alone (ordered by most recent), consistent with the
fallback lookup already used elsewhere in NestsController.

This commit is contained in:

2026-06-30 15:00:22 -04:00

parent 85f6a50f1a

commit 1d4f64726b

3 changed files with 37 additions and 3 deletions

									
										PepLib.Core/IO/NestReader.cs
									
		+1
		-1
	
												View File
												
				@@ -86,7 +86,7 @@ namespace PepLib.IO

				            try

				            {

				                stream = new FileStream(nestFile, FileMode.Open);

				                stream = new FileStream(nestFile, FileMode.Open, FileAccess.Read, FileShare.Read);

				                Read(stream);

				            }

				            finally