Skip to content

fix(db): repair main after the #103/#105 semantic merge conflict - #106

Merged
gustavobertoi merged 1 commit into
mainfrom
fix/reset-resolvetenant-signature
Jul 1, 2026
Merged

fix(db): repair main after the #103/#105 semantic merge conflict#106
gustavobertoi merged 1 commit into
mainfrom
fix/reset-resolvetenant-signature

Conversation

@gustavobertoi

Copy link
Copy Markdown
Contributor

main is red after #103 + #105 both merged — a semantic conflict git did not flag. #105 changed resolveTenant (now takes kind, returns 6 values) and replaced defaultPgDumper() with SelectDumper(d,kind); #103's reset.go + db pull still used the old forms. Both call sites fixed (pg kind). Build, vet, full go test ./internal/..., and make determinism all green locally.

#103 (db reset/pull) and #105 (redis/minio dumpers) each passed CI alone but
broke `main` when both merged — a semantic conflict git didn't flag:

- #105 changed `resolveTenant` to take a `kind` and return `engine,label`
  (5 args / 6 returns); #103's `reset.go` still called the 4-arg form.
- #105 replaced the `defaultPgDumper()` helper with `SelectDumper(d, kind)`;
  #103's `db pull` still called the removed helper.

Both call sites now use the merged signatures (pg kind, extra returns discarded).
Build, `go vet`, full `go test ./internal/...`, and `make determinism` all green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gustavobertoi
gustavobertoi merged commit 0421d43 into main Jul 1, 2026
4 checks passed
@gustavobertoi
gustavobertoi deleted the fix/reset-resolvetenant-signature branch July 1, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant