Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error messages while aggregate a closing allocation #598

Open
gusinacio opened this issue Jan 31, 2025 · 0 comments · May be fixed by #600
Open

Error messages while aggregate a closing allocation #598

gusinacio opened this issue Jan 31, 2025 · 0 comments · May be fixed by #600
Assignees
Labels
meta:good-first-issue Good for newcomers p2 Medium priority type:bug Something isn't working

Comments

@gusinacio
Copy link
Member

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.

@gusinacio gusinacio added meta:good-first-issue Good for newcomers type:bug Something isn't working p2 Medium priority labels Jan 31, 2025
@shiyasmohd shiyasmohd self-assigned this Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta:good-first-issue Good for newcomers p2 Medium priority type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants