CI run 188 failed once on the SQLite job: a cross-engine test lost its
connection (EndOfStreamException) while creating its PostgreSQL database,
right after the service container started. The retry covered only
timeouts. It now covers every transient Npgsql error and picks a new
database name on each attempt, in case the lost answer had already
created the database. Test helper only; no product code changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On the CI runner twelve test workers open PostgreSQL connections at once
and some waited longer than the application's 5 seconds, failing two
collector tests with a connection timeout that has nothing to do with
the code under test. The connect timeout is now a DbSettings field that
keeps the 5-second default for the application, and the test databases
ask for 30 seconds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The skipped-minute test waited for the recovered bar, but the issue is
closed a moment after the bar is stored; on PostgreSQL in CI (run 181) it
read the issue in between and saw it still open. It now waits for the
issue's final state.
- Creating a PostgreSQL test database retries on a connection timeout: CI
run 179 on main failed because twelve workers created their databases at
once and one connection missed the application's 5-second timeout. The
application's timeout is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase 1 foundations in the Anubis library:
- Platform: startup configuration from environment variables (Docker) or
config.toml (desktop, in-house TOML subset), data folder layout, secret key
custody (ANUBIS_SECRET_KEY, DPAPI on Windows, restricted file elsewhere),
installation identity and database fingerprint.
- Db: ADO.NET with Npgsql and Microsoft.Data.Sqlite, money as NUMERIC(38,18)
or canonical text rounded to 18 decimals, UTC moments, UUIDv7 ids; numbered
SQL migrations with type tokens and a version table; engine-independent
export/import with count and accounting-total checks; backups keeping 14.
- Core: injectable clock, channel event bus, scheduler with fixed, interval
and market-relative times, settings with change log, AES-GCM secrets, log
redaction, Italian formats.
- Access: PBKDF2-SHA512 hashes, RFC 6238 TOTP, hashed session tokens,
sign-in attempt limit.
SQLitePCLRaw (Apache-2.0) arrives with Microsoft.Data.Sqlite and is declared
in DependencyPolicyTests and API-NOTES.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The independent review found that the policy tests could be bypassed:
Microsoft-named direct packages and GlobalPackageReference slipped past
the dependency check, the live-money scan missed the JSON, Dockerfile
and Unraid template forms, the secret scan missed short project
secrets but would have failed on the user's own ignored .env. The
scans now read only the files git would commit and cover those cases.
Also adds the fixed-seed generator for property tests, the REGISTRY
variables reserved for phase 9 in the CI, a git pre-commit hook in
place of the pre-commit tool (tasks hooks), the missing SPEC 4 facts
in API-NOTES (Fed/ECB/BLS times, USDC depth on OKX) and the full list
of today's indirect packages.
refs #3 refs #5 refs #6
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Empty but complete solution so every later phase starts from a working
toolchain: analyzers as errors, locked restore, format check, policy tests
that keep packages within ADR 0004 and keep live trading switched off,
a /health endpoint served from Docker, and a Gitea workflow with only
run steps. API facts of SPEC section 4 re-checked in docs/API-NOTES.md;
ADR 0006 records what changed (MSTest base packages, Ubuntu images,
OKX WebSocket on 443, Alpaca margin-only accounts).
refs #1 refs #2 refs #3 refs #4 refs #5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>