Identity and meaning
СсылкаRuntime guard could not complete
- Семейство
- topaz
- Этап
- run
- Код
TPZ5099
Доступность
Включено по умолчанию · Не определено
The relevant runtime operation and std.lispex host boundary must be active.
The guard definition, product decoder, and selected producer branches are source reviewed. Installed-product exposure and default-distribution availability remain Pending.
Причина и условия
The reviewed std. boundary produces TPZ5099 for a host refusal that reaches its fallback, a response for the wrong operation, an out-of-range limit or artifact length, a completed settlement missing its result, or an unknown operational-fault code.
Действия
Retain the full message, operation, compiler version, target, and package context. For a host refusal, check the relevant std.lispex activation and operation contract. A wrong-operation response or missing required result warrants a runtime defect-candidate report if reproduced. There is no verified source rewrite that resolves every producer of this code.
TPZ5099 covers several runtime conditions. Use the accompanying message and operation to identify the cause; the code alone does not identify a particular unsupported language construct.
Producer conditions
СсылкаRuntime guard conditions
The reviewed std. boundary produces TPZ5099 for a host refusal that reaches its fallback, a response for the wrong operation, an out-of-range limit or artifact length, a completed settlement missing its result, or an unknown operational-fault code.
Причина
Host replies must match the requested operation and fit the expected value ranges. Guards prevent invalid replies from becoming successful API results.
Ordinary operational faults returned by Evaluate or EvaluateWithEvidence are handled separately as result values before the fallback. They do not all become TPZ5099. These source branches do not enumerate every producer or phase in the repository.
Canonical values do not require a factory handle
A valid canonical value conversion does not require an unrelated rule factory call.
The paired public 5.21.3 examples check host selection with the 5.21 conversion signature. Topaz 6.0 takes an admitted package, bytes, and host limits under Lispex values. The exact-value round trip specifies that conversion.
Причина
A rule factory selects a prepared program. Converting a value does not select or evaluate a program.
Response
СсылкаRetain the full message, operation, compiler version, target, and package context. For a host refusal, check the relevant std.lispex activation and operation contract. A wrong-operation response or missing required result warrants a runtime defect-candidate report if reproduced. There is no verified source rewrite that resolves every producer of this code.
Host selection and canonical conversion
СсылкаConvert canonical input without a factory call
Ссылкаimport std.ioimport std.testimport std.lispex { valueFromCanonical }let bytes = test.assertOk(Bytes.fromArray([0]))let value = test.assertOk(valueFromCanonical(bytes))io.writeLine("canonical-ok")
canonical-ok
Ожидаемый результат
Ожидаемый результат
Выполнение завершается. Код завершения 0.
canonical-ok
This public 5.21.3 example checks host selection with the 5.21 one-argument conversion. Use the maintained application package and unchanged lock.
Convert canonical input after an explicit factory call
Ссылкаimport std.ioimport std.testimport std.lispex { valueFromCanonical }import std.lispex.rules { approve }let rule = approve()let bytes = test.assertOk(Bytes.fromArray([0]))let value = test.assertOk(valueFromCanonical(bytes))io.writeLine("canonical-ok")
canonical-ok
Ожидаемый результат
Ожидаемый результат
Выполнение завершается. Код завершения 0.
canonical-ok
This public 5.21.3 example checks host selection with the 5.21 one-argument conversion. Use the maintained application package and unchanged lock.