• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In
Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?

Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.

Adjust setting

ingitdb / dalgo2ingitdb4github / 33022483860
85%
main: 85%

Build:
Build:
LAST BUILD BRANCH: chore/dalgo-v0.74.0
DEFAULT BRANCH: main
Ran 26 Aug 2026 11:14PM UTC
Jobs 1
Files 13
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

26 Aug 2026 11:11PM UTC coverage: 84.572%. Remained the same
33022483860

Pull #5

github

trakhimenok
fix: bump dalgo to v0.74.0, record to v0.1.3; close duplicate-insert conformance gap

dal.DB's sealing (the unexported dalgoDB() marker method) has not changed
shape since this adapter adopted it for v0.64.2; the interface is satisfied
unchanged at v0.74.0 with no adapter redesign required.

dal-go/record v0.1.3 added the cross-adapter ErrRecordExists / IsAlreadyExists
sentinel that dalgo's dalgotest.Checks() conformance suite now mandates
("rejects an Insert over an existing key with record.IsAlreadyExists").
Insert's existing-key error in tx_readwrite.go now wraps
record.ErrRecordExists in both the MapOfRecords and single-record branches,
so callers can distinguish "created" from "duplicate key" via
record.IsAlreadyExists(err) instead of string-matching an ad hoc message.

Fixture fix: newGitHubContentsServer's GET handler 404'd any path not present
in the server's static fixture set, even after that path had been written via
PUT during the test. That masked the new conformance check: a record written
by a seed Insert always read back as "not found" on the next Insert, so
duplicate-key detection looked broken. Directory listings still come from the
static fixtures; file content now comes from the live contents map for any
path, matching what the real GitHub Contents API does.

go.mod's `go` directive moved from 1.26.0+toolchain 1.27.0 to a plain 1.27.0
as a mechanical side effect of `go get`/`go mod tidy` against dalgo v0.74.0's
own go.mod floor.

go build ./... && go vet ./... && go test ./... all green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KFsyYhYi9h9Am1JbAMxuhv
Pull Request #5: fix: bump dalgo to v0.74.0, close duplicate-insert conformance gap

2 of 2 new or added lines in 1 file covered. (100.0%)

1195 of 1413 relevant lines covered (84.57%)

0.85 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33022483860.1 26 Aug 2026 11:14PM UTC 13
84.57
GitHub Action Run
Source Files on build 33022483860
  • Tree
  • List 13
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #5
  • PR Base - main (#32931923467)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc