Repository navigation
Failing tests in release 0.0.52 #71
Description
Tests are failing on released version, looks like maybe a sorting mismatch. Looking through the Actions workflows, I don't immediately see any jobs which would exercise these tests.
--- FAIL: TestGetContextFromPaths (0.00s)
prompt_test.go:43:
Error Trace: /home/adam/git/opencode/internal/llm/prompt/prompt_test.go:43
Error: Not equal:
expected: "# From:/tmp/TestGetContextFromPaths737290226/001/file.txt\nfile.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_a.txt\ndirectory/file_a.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_b.txt\ndirectory/file_b.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_c.txt\ndirectory/file_c.txt: test content"
actual : "# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_a.txt\ndirectory/file_a.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_b.txt\ndirectory/file_b.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/file.txt\nfile.txt: test content\n# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_c.txt\ndirectory/file_c.txt: test content"
Diff:
--- Expected
+++ Actual
@@ -1,3 +1 @@
-# From:/tmp/TestGetContextFromPaths737290226/001/file.txt
-file.txt: test content
# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_a.txt
@@ -6,2 +4,4 @@
directory/file_b.txt: test content
+# From:/tmp/TestGetContextFromPaths737290226/001/file.txt
+file.txt: test content
# From:/tmp/TestGetContextFromPaths737290226/001/directory/file_c.txt
Test: TestGetContextFromPaths
Activity
[-]Failing tests in release 0.0.52[/-][+]Failing tests[/+][-]Failing tests[/-][+]Failing tests in release 0.0.52[/+]adamcstephens commentedon Jun 7, 2025
Actually looks like this may be resolved in
dev. I'll close then. Sorry for the noise.feat(#70): enhance research-specialist permissions for AWS diagnostics (
fix(ui): remove developer shield icon (anomalyco#71)
anthonykewl20 commentedon Aug 16, 2026
Starting implementation of tunable bounded provider retry policy. Scope: core provider retry config/service, runner retry integration and durable budget evidence/tests only. Branch: provider-retry-policy. Worktree: /tmp/opencode/wt-71.
anthonykewl20 commentedon Aug 16, 2026
Finding: existing retry_attempt/retry_next_attempt_at preserve only attempt and deadline; they cannot reconstruct elapsed-window or cumulative-sleep ceilings after restart. Added nullable retry_cumulative_delay_ms and retry_window_started_at with migration-safe defaults, and replay-compatible optional retry decision evidence.
anthonykewl20 commentedon Aug 16, 2026
Implementation complete on
provider-retry-policyin/tmp/opencode/wt-71(db246b7fa5).Validation:
cd packages/core && bun test-> 1265 pass, 1 skip, 0 fail (4374 expectations)cd packages/core && bun typecheck-> pass (tsgo --noEmit)cd packages/sdk/js && bun run build-> pass; regenerated compatible V2 event typescd packages/core && bun script/migration.ts-> pass; generated migration20260816064134_lowly_zemoNo push performed.
anthonykewl20 commentedon Aug 16, 2026
Addressed the independent review findings in 42e9fdf963: Retry-After is finally capped; real assistant/interruption state is passed to the retry policy with runner coverage; base-shaped Retried payload compatibility is regression-tested; projector no longer guesses legacy backoff; and the retry projection atomicity was verified against the EventV2 transaction path.