Skip to content

Fix bounty payment retry status flow#2789

Open
cybercraftsolutionsllc wants to merge 1 commit into
stakwork:masterfrom
cybercraftsolutionsllc:codex/payment-status-flow-1901
Open

Fix bounty payment retry status flow#2789
cybercraftsolutionsllc wants to merge 1 commit into
stakwork:masterfrom
cybercraftsolutionsllc:codex/payment-status-flow-1901

Conversation

@cybercraftsolutionsllc
Copy link
Copy Markdown

Fixes #1901

Summary

  • keep UpdateBountyPaymentStatus read-only for non-COMPLETE retry results
  • return the V2 bot status (PENDING or FAILED) instead of falling through to NOTPAID
  • add payment retry coverage for pending, failed, and completed status handling
  • add the missing generated GetBountyByUnlockCode database mock so handler tests compile against the current interface

Validation

  • go test ./handlers -run '^$' -count=1
  • git diff --check

go test ./handlers -run TestUpdateBountyPaymentStatus -count=1 is blocked locally because the Postgres test DB is not running at localhost:5532, and Docker Desktop's daemon is unavailable for docker compose -f docker/testdb-docker-compose.yml -p test_db up -d.

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.

Payment And Withdrawal Flow

2 participants