H
Residual spec coverage (auto-filed by the spec-coverage gate #9914) The workflow for #440 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 1/2 of the integration points named in the parent were addressed and 1/1 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped. Parent issue: #440 (closed) Landing workflow:…
H
Workflow 440-haf-system-suite-test-blocks-r-s5e0d19f2-v1 completed on session-haf-simple. Merged to staging branch. Implementation: a19b72b81bfeab50ab60abb7b5f609e19bda4cd6 Final branch HEAD: 842ae01c265e59c64837fc9a83075c17fc101b55 (after auto-format) Advisory Partial delivery (spec-coverage gate #8930). This change addresses 1/2 of the integration points declared in the issue. Unaddressed: .aidev/known_failures.txt. A follow-up may be needed to finish the scope. Observation criteria handed to…
H
Problem and intended result The haf_system suite of the full slot (#432 (closed)) produced three errors in #436 (closed)'s workflow (436-haf-s-hive-submodule-lacks-hiv-s5e0d19f2-v1, aidev test affected on 2026-11-04, steem-11 under heavy load). The suite ran in its pinned image registry.gitlab.syncad.com/hive/haf/aidev-system-tests@sha256:4e769773…, with hived from develop 46558ea2, independent of #436 (closed)'s change: test_blocks_reversible.py test_event_after_replay.py…
H
AIDEV Production Bot (842ae01c) at 04 Nov 06:36 Merge #440: Give the haf-system suite CI's 60 s test_tools live-mod...
H
AIDEV Production Bot (842ae01c) at 04 Nov 06:36 Merge #440: Give the haf-system suite CI's 60 s test_tools live-mod... ... and 1 more commit
H
AIDEV Production Bot (a19b72b8) at 04 Nov 06:29 Give the haf-system suite CI's 60 s test_tools live-mode timeout (#... ... and 10 more commits
H
AIDEV Production Bot (40db15ba) at 04 Nov 06:29 Give the haf-system suite CI's 60 s test_tools live-mode timeout (#... ... and 46 more commits
H
Problem and intended result The aidev/integration -> develop hand-off (!1030, pipeline 185407, aidev/integration a6303fda) fails all four image builds: haf_image_build, haf_image_build_testnet, haf_image_build_mirrornet, haf_image_build_pg17 (for example job 3388363): FAILED: tests/unit/sql_serializer/CMakeFiles/unit.sql_serializer.dir/data_processor_tests.cpp.o /home/hived/source/src/sql_serializer/include/hive/plugins/sql_serializer/data_processor.hpp:4:10: fatal error:…
H
AIDEV Production Bot (a6303fda) at 04 Nov 06:20 Land #437 (canary verdict reused) ... and 6 more commits
H
Workflow promote-session-velocity-identity-1793388310 completed on session-velocity-identity. Merged to staging branch. Merge commit: ee7eb92731526bc254429b2d868cf197ebc85ab0
H
Resolved by workflow promote-session-velocity-identity-1793388310 — original issue #6 (closed) completed successfully.
H
Failed workflow with recoverable code A workflow failed after producing code on its branch. The implementation may be worth retrying with fixes. Workflow ID: 6-ci-give-every-job-a-runner-tag-d-s07bc55ea-v1 Branch: ai/6-ci-give-every-job-a-runner-tag-d-s07bc55ea-v1 Original issue: #6 (closed) Error category: test Recovery hint: The candidate changed a lock file but left sandbox.runtime pinned to the image built from the old one, so the gate refused to run the suite. Rebuild the project's test…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Auto-promotion failed The workflow could not automatically promote this implementation to aidev/integration. Branch: session/velocity-identity (implementation was on session/velocity-identity) Original issue: N/A Landed-work issues: #6 (closed) Attempted head: 169d60311a8bf6c41d86d48e675c4d010e42c672 Reason: Promote candidate canary failed (before promotion; candidate not merged): pnpm-workspace.yaml changed against the approved base at /home/worker/target@11a63bda3d3f, but sandbox.runtime is…
H
Workflow promote-session-velocity-identity-1793388310 completed on session-velocity-identity. Merged to staging branch. Merge commit: ee7eb92731526bc254429b2d868cf197ebc85ab0
H
Problem Several CI jobs in .gitlab-ci.yml carry no tags:. Untagged jobs seen in pipelines since July: test, typecheck, lint. An untagged job can only run on a runner with run_untagged=true. The only such runner is hive-builder-11, and it is down (silent since 2026-10-29 22:01 UTC). Every other hive builder has run_untagged=false. So these jobs now fail with stuck_pending_no_matching_runners, and the pipeline cannot pass. Every job should carry a runner tag; this config was written before that…
H
Dan Notestein (ee7eb927) at 30 Oct 19:26 Merge #14: Run the suites in the shared node-test-tools-pg image wi... ... and 2 more commits
H
jthomasewsky (b3b53fc5) at 30 Oct 19:26 Add HF30 config constants to OpenAPI schema
H
Problem #1397 (closed)'s full fixture_e2e run (commit 34891988) failed in global teardown on a new fixture MISS: bridge.get_community in postEditCommunity.spec.ts. Its parent (6ed32f43) already includes #1396 (closed), whose known-misses.json has the intermittent entry for hash 50f0a6832c3ff911 (get_community {name: hive-137823, observer: guest4test}). Teardown matches spec, method and hash exactly (apps/blog/playwright/tests/support/fixture-misses/known-misses.ts), so this miss must have had a…
H
Follow-up to #1391 (closed)/#1397 (closed) (hb-auth worker locking on sign-out). The #1397 (closed) review (commit 34891988) found these remaining paths where an account can stay unlocked in an app's hb-auth worker after a sign-out, so a later page of that app could sign without a password prompt. All are traced from code, not reproduced. Blog (/blog) and wallet (/wallet) share one origin but each has its own SharedWorker. 1. The worker outlives its last tab hb-auth opens its SharedWorker with…
H
Problem apps/wallet/feature/transfers-page/pending-savings-withdrawals.tsx: one openCancelTransfer boolean drives every row's cancel . With two or more pending savings withdrawals, clicking Cancel on row 1 opens every row's dialog. The topmost is the last row's, so confirming broadcasts cancel_transfer_from_savings for the last withdrawal's request_id, not the clicked one. The dialog shows that last row's text, so an attentive user might notice, but the action doesn't match the click. This…
H
Workflow 14-run-the-suites-in-the-shared-cc-s07bc55ea-v1 completed on session-velocity-identity. Merged to staging branch. Implementation: 43ef5a8a7554ed518bba0a3efbd843743139026c Final branch HEAD: ee7eb92731526bc254429b2d868cf197ebc85ab0 (after auto-format) Advisory Spec coverage not evaluated (#11829). spec coverage not evaluated — the issue declares no integration points. Declare them in an ## Integration points block (aidev integration-points propose --issue N drafts one from the prose).
H
Switch this project to aidev's shared test image route (environment.kind: shared). Operator guide: aidev docs/operations/shared-test-images.md. The operator approved widening it on 2026-10-30, after velocity-js-sdk proved the route. Today .aidev/project.yaml runs every suite in registry.gitlab.syncad.com/hive/velocity-identity/aidev-tests@sha256:71f91fa96a80db336ede94df4510acf4c3b7ca0da0218f7e7dabd9a7a1f9ef32, built by .aidev/runtime/Dockerfile. This project's integration suite starts…
H
Dan Notestein (ee7eb927) at 30 Oct 19:24 Merge #14: Run the suites in the shared node-test-tools-pg image wi...
H
Dan Notestein (ee7eb927) at 30 Oct 19:24 Merge #14: Run the suites in the shared node-test-tools-pg image wi... ... and 1 more commit
H
Residual spec coverage (auto-filed by the spec-coverage gate #9914) The workflow for #420 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 1/1 of the integration points named in the parent were addressed and 1/3 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped. Parent issue: #420 (closed) Landing workflow:…