Handle foreign-owned compile artifacts
This commit is contained in:
@@ -578,7 +578,14 @@ header free-functions are `inline`. The wasm backend exposes only declarations
|
||||
held unit and registry locks, silent nonzero and missing-output compiler
|
||||
results, compiler descendants, staged-output timeout, prior-generation
|
||||
hashes, same-worker recovery, configured-error-page boundedness, residue,
|
||||
and deadline-independent offline precompile.
|
||||
foreign-owned offline-precompile artifacts, and deadline-independent offline
|
||||
precompile. Normal rollback snapshots are hard links. If Linux ownership or
|
||||
link policy rejects that fast path, the compiler copies the prior artifact
|
||||
under the same unit lock and keeps the same all-or-nothing publication.
|
||||
Source-generation markers likewise publish through a same-directory rename,
|
||||
so a runtime user can replace a readable marker created by an administrator.
|
||||
Existing foreign-owned unit, registry, generation, and PCH lock files are
|
||||
opened read-only for `flock`; new locks are still created read-write.
|
||||
`scripts/test_cold_component_deadline.sh` separately compiles a deliberately
|
||||
cold component that exceeds the development epoch window and proves the
|
||||
parent request still renders it. The focused shell gates create temporary
|
||||
|
||||
Reference in New Issue
Block a user