akash-network / akash-network/console
spend limit cannot be negative
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
Error: Query failed with (6): rpc error: code = Unknown desc = spend limit cannot be negative: invalid coins [cosmos/cosmos-sdk@v0.45.16/types/errors/errors.go:273] With gas wanted: '0' and gas used: '13206' : unknown request
at QueryClient.queryAbci (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/queryclient.ts:619:13)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Object.request (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/utils.ts:35:24)
at async Object.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/modules/tx/queries.ts:72:26)
at async SyncSigningStargateClient.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/signingstargateclient.ts:192:25)
at async BatchSigningClientService.estimateFee (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:280:27)
at async <anonymous> (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:210:21)
at async withSpan (webpack://akashnetwork/console-api/src/core/services/tracing/tracing.service.ts:169:20)
at async BatchSigningClientService.executeTxBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:202:12)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts, especially estimateFee and executeTxBatch, then trace the simulation request shown in the stack trace. The issue provides only the error output and does not define the intended fix or a way to verify completion, so the expected behavior needs clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100