Repository navigation
Qualify activity deadline authority during Avro read load - #442
Conversation
|
Run 38494055609 attempt 1 is failed before any database execution. The unchanged locked published Rust SDK adapter build returned exit 101 in job 115625681074. Cargo stderr was redirected to rust-sdk-build.txt, but that failed job did not publish a diagnostic artifact. The available job log proves terminal failure and does not establish its cause. All native/shared actor inputs, source and declared 25-minute/2CPU/2GiB adapter limits are unchanged. I am making one identical-head, identical-limits retry of this terminal failed adapter job. The failed original remains failed. This is not an observation-timeout restart, source correction or qualification claim. Local #442 PHP/native load preparation proceeds independently; actual load/deadline acceptance is still pending. |
|
The first local committed-source ccd82d8 original is runner-blocked, not CPU/deadline-qualified. The genuine dense seed and separate activity were admitted; the original activity's late completion/failure returned409, heartbeat refused progress and canonical timeout/parent delivery survived. However all458 direct description requests returned400/missing_control_plane_version. The reader omitted the published control-plane2 header. Its CPU usage therefore cannot count as real Avro-read load, and the existing strict validator correctly refuses the record. The original run and deadlines are not restarted, repaired or rebudgeted. The correction adds the published header on every read and checks it against the installed SDK's Version constant, with a real HTTP counterfactual and regression control. Payload shape, eight readers, nine-second wave, service resources, original activity timeout and observer budgets stay unchanged. New qualification will use separate fresh originals; this is a runner fix, not a PHP/native defect or a lighter workload. The first native bootstrap command also refused an unsupported CLI spelling before data setup; the documented schema-bootstrap command is now being used. No native code change. The one identical-head/limits hosted adapter retry succeeds. Its original exit101 remains failed with no captured stderr/cause; downstream originals are now running. Future failed SDK setup will retain small diagnostics instead of losing the build error. No complete matrix, performance or release claim. |
|
Actual optimized native SQLite qualification passes the unchanged pending CPU/deadline profile. Producer/runner Original The original authored four-second schedule-to-close deadline is 29 controls derived from this actual record refuse altered actor/identity/typed values, original clocks/policy/prefix, stale outcome acceptance, failed/empty/late reads, missing or idle CPU evidence, changed allocation/swap and excessive memory. Original int64 bytes survive the profile writer. Seven focused streaming/timeout/status controls pass; the current shared Node suite passes 4,826 tests with one existing skip. No fixture builds a substitute producer or turns a failed original into a pass. Failed observations remain explicit:
Current source |
|
Current The earlier Remaining older attempt-2 jobs are intentionally cancelled because the corrected final head supersedes them. This is a source revision, not a retry that changes their failed/cancelled outcomes or proves a network cause. The new final head adds small setup-log retention on failure and keeps source/resource/request budgets unchanged. No old original is called passed by the new run. Native subtree f8 and frozen tuples remain unchanged. |
|
Immediate local audit and cleanup are complete. The published Apache original's WAL-aware read-only audit confirms exactly one Task containers, network, databases/WALs, compiler caches, dependencies, binaries, runtime images and full recordings/downloads are deleted. The readable outcome and regression/profile code remain. Final-head38498037842 and normal source checks are still running. No publication, matched performance or full #325 claim. |
rmcdaniel
left a comment
There was a problem hiding this comment.
Reviewed the declared workload, installed SDK identity/control-plane header, separate absolute-timeout read and health processes, original admission/handoff/observer budgets, late-outcome fencing, whole history/policy/typed-value checks, actual CPU/resource evidence, and lossless original JSON writer. The verified local optimized SQLite original and 29 corruption controls qualify this bounded case. Earlier missing-header, debug read-timeout and PHP OOM observations remain failed. All six final-head default-corpus jobs and applicable PHP/source/boundary checks pass; the conditional cancellation/prepared-local job is explicitly skipped. Complete candidate and CI merge trees both equal d22aac11b6680a22d4963faa33bc62677cb1d5cc. Native f8, dependencies, frozen actors and default corpus are unchanged. Broader CPU operations remain separately owned in draft443; no performance, published native, migration or full325 claim.
|
#442 merged at Fresh-main qualification remains pending: Shared Server fixtures 38502424493, PHP/source 38502424660, and boundary 38502424648. The local optimized SQLite activity-expiry proof and 29 guards keep their bounded scope. Broader CPU timer/renewal/cleanup is separate in draft #443, with other databases still pending. No publication, matched performance, migration, native capability, or full #325 claim. Draft #443 is retargeted to main after integrating this identical main tree. Its newer canonical-clock reader refuses one-microsecond early/excess lateness without changing raw timestamps. The original failed race/source/reference outcomes remain recorded. Merged #442's remote head returns 404, and its clean worktree/local branch are removed. Runtime, build, dependency, and raw data were already deleted. |
|
#442 is delivered at main Fresh main shared run This delivers the bounded activity-only Avro read/health/original global-deadline fixture, including its actual optimized native SQLite original and 29 corruption controls. Earlier missing-header/debug/native timeout and frozen PHP OOM/read-timeout originals remain failed. No current PHP cause, matched throughput/capacity, all-database CPU health, timer/renewal/cleanup CPU coverage, migration, release or full #325 completion is inferred from these ordinary six-database jobs. Those additional CPU families remain separate #443 qualification. Frozen actors/tuples, native subtree |
Qualify an original activity's global deadline while genuine Avro description reads saturate the native service. Independent load and health processes keep bounded counts/hashes/timings, and the installed SDK preserves exact input, original policy/identity/history, canonical timeout/parent delivery and late-outcome fences. The profile fixes eight readers, nine seconds, one CPU/512 MiB/no swap, two-second absolute reads, a four-second global timeout and the original 35-second observer budget before admission.
An optimized native SQLite original passes: 91/91 dense reads and 88/88 health/readiness reads, measured busy CPU around expiry, exact original prefix/deadlines, one activity attempt/timeout and zero repairs in a stopped read-only WAL-aware audit. Maximum read times are 926 ms and 27 ms. 29 corruption controls run against that actual original and retain lossless int64 bytes. Seven streaming/timeout/status controls and 4,826 shared Node tests pass with one existing skip. PHP syntax checks pass.
Failed missing-header/debug/native setup originals remain recorded. The frozen PHP 2.6.2 Apache original hits OOM/read timeouts under the same declared workload and retains one stored timeout/unclaimed unrepaired parent, but fails HTTP qualification. Actual outcome and limits. This is one bounded source qualification, not matched performance, embedded CPU behavior or full timer/lease-renewal/cancellation health on every database.
The default corpus, native source, dependencies, frozen actors and capabilities remain unchanged. Final-head ordinary matrix, review and promotion are pending. Refs #325 and its existing CPU/deadline scope.