Skip to content

fix: correct returnsuccess redis status key#4

Open
Luzijano wants to merge 1 commit into
BitgesellOfficial:mainfrom
Luzijano:fix-return-success-redis-key
Open

fix: correct returnsuccess redis status key#4
Luzijano wants to merge 1 commit into
BitgesellOfficial:mainfrom
Luzijano:fix-return-success-redis-key

Conversation

@Luzijano
Copy link
Copy Markdown

Summary

  • Fix the returnsuccess Redis status set key from brdigeops:returnsuccess to bridgeops:returnsuccess.
  • Add regression tests covering the bridge operation Redis namespace and the returnsuccess mapping.

Why

The misspelled Redis key can split returned-success operations into a different namespace than the other bridge operation status sets, making successful return tracking inconsistent.

Validation

  • RED before fix: go test ./config failed on returnsuccess Redis key = "brdigeops:returnsuccess".
  • GREEN after fix: go test ./config
  • Regression suite: go test ./...

Bounty context

This is submitted as a small reliability/test-coverage improvement under the Bitgesell bounty/improvement program and aligns with #3.

AI assistance was used to inspect the issue, write the regression tests, and validate the fix.

Signed-off-by: Lucijano JL. <218673409+Luzijano@users.noreply.github.com>
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