graphprotocol / graphprotocol/indexer-rs
Error messages while aggregate a closing allocation
@shiyasmohd is already working on this.
Since Feb 1, 2025.
- Dominant language
- Rust
- Stars
- 31
- Forks
- 29
- Avg merge
- 13h 9m
- Merged PRs (30d)
- 13
Description
Problem
When you have a lot of receipts for older allocations that were already being closed, once it starts an allocation, it sends a SenderAccountMessage::UpdateReceiptFees to let the sender account know about the updated value.
As soon as it gets the message, it verifies that the count is bigger than the limit, and triggers a rav request for that specific allocation. While trying to send a request to the allocation, it was already closed, and no allocation actor was found, giving this message
ERROR indexer_tap_agent::agent::sender_account: There was an error while requesting a RAV., error: Error while getting allocation actor 0x....
Solution
We have a flag called "blocked_allocation" which is added when sender account closes an allocation.
If the allocation is blocked (closing), we shouldn't trigger an allocation for counter_greater_receipt_limit.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.