-
Notifications
You must be signed in to change notification settings - Fork 1
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
Most recent round of allocation not showing in GH or allocator.tech #53
Comments
@kevzak Do I assume correctly that these 1300TiBs were handled manually, completely outside allocator.tech infrastructure? |
No @kacperzuk-neti it was completed inside allocator.tech. That's the issue. It was completed and never showed after in allocator.tech or github but it does exist onchain |
@willscott do you have any details on this not working Keyko deploy? @kevzak Looks like it may be difficult to recover, but we'll try. Do you by any chance have the Cid of the message that granted the datacap? |
I can't prove it, but I think any allocations made between May 13 and when your team took over are probably like this - not showing properly in allocator.tech/github |
I can't find the root cause, but luckily it looks like it's not any allocations made between May 13 and the takeover. For example, here we have allocations on May 14th and 16th: https://allocator.tech/application/Blockchain-World-News/FIL-DC-Allocator/f1iilvoccl27nyy5ejsrxrz4b2huepu5xjlffnu7q . We'll revisit finding the root cause if this happens again (as we'll have logs and other tools now to investigate). For now, I'll fix this manually (hopefully even today). |
@kacperzuk-neti anything here? |
@kevzak state updated, please confirm that it's correct now. |
looks good |
A client was given 1300TiBs on May 17 but this allocation does not show:
@willscott mentioned its likely related to last Keyko deploy that didn't work. Can the system be refreshed?
The text was updated successfully, but these errors were encountered: