22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
# Points import repair: e637457001fdb64e74b833ec
|
|
|
|
The supplied first error points to tools/points-business-cases.mjs:151,
|
|
the missing-file rejection loop after successful PLY import and FCStd snapshots.
|
|
PointsRuntimeProbe.cpp called Points.insert without containing native C++
|
|
exceptions. The bridge now releases its Python references and returns the
|
|
existing points_import_failed record for native exceptions as well as Python
|
|
error returns. Actual file parsing remains in the existing Points.insert path.
|
|
|
|
The mounted workbench-shell.tsx already calls DesktopCommandDispatcher.execute
|
|
and displays facade errors. The dispatcher now converts Points record errors
|
|
into facade errors so a failed import cannot appear as command completion.
|
|
|
|
Build, sync, and business acceptance remain owned by the outer pipeline and
|
|
were not run during this edit batch. First verify the missing-file input and
|
|
subsequent document snapshot/recovery through the existing PLY business case.
|
|
The exception diagnosis and document preservation after the exception still
|
|
require runtime verification. No business IDs are marked accepted here.
|
|
Reuse the supplied evidence for unaffected selected records; browser file
|
|
staging, full point-cloud UI, and OPFS persistence are not established by this
|
|
repair.
|