-
Notifications
You must be signed in to change notification settings - Fork 105
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
Cannot return null for non-nullable field Token.asset. #909
Comments
Sorry for the bug report on New Years Eve @Kammerlo ! BTW Happy New Year to you, our "b*tt saviour" as I said to Nicolas Cerny on Buenos Aires |
Hey @zxpectre, Happy new Year as well :D I'm happy to help! <3 This issue looks like there went something wrong with the token syncing. I adjusted the way it is done last month to speed up the process. The tokens were they newly created and queried directly after or was this an old token? |
Hi @Kammerlo, any news? is not even self-healing after time passes, more queries are failing, I bet is stucked on a loop at 99% asset processing. I do not know for certain that only new assets are the issue but it seems new mints are triggering it.
|
Restarted one instance, but was no good.
Weird thing is that was working fine since your last update, during last weeks of 2024, not sure what changed on-chain that could cause this, or maybe is time/epoch related?. Also is a mainnet-only issue as far as we can tell. |
Hi @zxpectre |
Sure @Kammerlo, thank you! , is
I restarted first server, background and hasura, and then the full setup with node and db-sync included. Same results not only on the restarted instance but also on all the other deployed production instances as mentioned you before. Is not a local state issue. At this point we are not sure if we should downgrade versions now as an emergency measure or if that would not be compatible with newer node, ogmios and dbsync versions |
@zxpectre There is an issue with the postgres database. So at least in my case. Could you please check if you are getting the same logs in the postgres container |
It's still stuck |
I can confirm I have no issues on the db logs @Kammerlo |
I joined your discord server, we can have a call there today and try to find a solution. |
Summary
Same query we were using since ages is now triggering some errors along with full or partial response data.
This on all our mainnet instances, some running latest versions
8.3.2
, some with previous8.3.1
Steps to reproduce the bug
Actual Result
Expected Result
Response without errors
Environment
https://ar02.gamechanger.finance:2087/manifest/
Platform
Platform version
Ubuntu server 20.24
Runtime
Runtime version
podman version 4.9.3 | Docker Compose version v2.28.1
The text was updated successfully, but these errors were encountered: