Conversation
…ir, Clojure, Rust, Swift, Bun/Deno) (Ghbounty#158)
bounties.list/get reported the raw on-chain mirror (issues.state, issues.submission_count), which lags reality: the relayer never flips state=resolved on devnet and the frontend cannot update submission_count under creator-only RLS. Mirror the dashboard's deriveStatus: live submissions count, submission_reviews.approved flag, bounty_meta.closed_by_user / closed_by_cap_at. Add derived status bucket + chain_id to list/get responses and filter on the derived bucket so status=open means actually claimable. Fixes Ghbounty#167
|
@aagear is attempting to deploy a commit to the weareghbounty-6269's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Issue #167 reports that MCP
bounties.listshows all eight bounties asopenwith zero submissions, while the signed-in dashboard shows reviewing/capped/paid records with nonzero PR counts (e.g. bountyd232f106…capped,1bd19d23…paid).Root cause:
bounties.list/bounties.getreturn the raw on-chain mirror columns, which lag reality:issues.stateonly flips toresolvedwhen the relayer runs (never on devnet), while the dashboard treats anysubmission_reviews.approved = trueas already paid.issues.submission_countlags forever because only the bounty creator can UPDATE it under RLS; the dashboard counts the livesubmissionstable instead.bounty_meta.closed_by_cap_at) and manually closed (closed_by_user) bounties still readstate = open.Fix
Mirror the dashboard's
deriveStatus(frontend/lib/data.ts) in the MCP:apps/mcp/lib/tools/bounties/status.ts:deriveBountyStatus()+fetchBountyEnrichment()(live submission counts per PDA and approved-submission flags, both soft-failing to the mirror column on error).bounties.list/bounties.getnow return astatusbucket (open | reviewing | capped | closed | paid), the livesubmission_count, andchain_id— answering the "which supported endpoint exposes authoritative claimability and chain/network information" question from Authenticated MCP profile lacks existing wallet mapping; bounty state differs from dashboard #167.filter.statusnow matches the derived bucket (legacyresolved/cancelledvalues still accepted, mapped topaid/closed), sostatus=openmeans actually claimable instead of "relayer hasn't run yet".The wallet-mapping half of #167 (
github_handle/wallet_pubkeynull inwhoami) is covered by the open PRs #141 and #140.Testing
pnpm vitest runin apps/mcp: 56 passed (new cases: reviewing from live count, capped, paid via approved review, open-filter excludes reviewing)pnpm typecheckcleanFixes #167