-
Notifications
You must be signed in to change notification settings - Fork 296
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
pindexer: swap_volume_over_window contains null values #4933
Comments
github-actions
bot
added
the
needs-refinement
unclear, incomplete, or stub issue that needs work
label
Nov 18, 2024
conorsch
removed
the
needs-refinement
unclear, incomplete, or stub issue that needs work
label
Nov 18, 2024
Filed this early: I'm going to try again to reproduce to confirm the inputs and outputs were correct. |
Ah-ha, container image was stale, so I wasn't testing against latest code. Image builds broke a few hours ago, with merge of #4930. Investigating... |
2 tasks
conorsch
added a commit
that referenced
this issue
Nov 19, 2024
## Describe your changes Follow-up to #4930, in which we inadvertently broken container builds, due to a workspace dependency being introduced. We don't build container images on every PR push, so CI passed fine, only failing when trying to build/deploy post-merge. Tacked on a small change to address. For testing, leave it to me: I'll re-deploy after this lands to get it going. ## Issue ticket number and link Refs #4933. ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > build logic only, no changes to consensus
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While testing recent
pindexer
bug fixes by rerunningpindexer
from block zero, I encountered a failure on thepenumbra-1
chain:To Reproduce
Steps to reproduce the behavior:
penumbra-1
chain (i used a dump from height 2129921, available here: https://artifacts.plinfra.net/penumbra-1/)Expected behavior
Pindexer syncs up to current height and is happy.
Additional context
I'm surprised that when dealing with dumps,
pindexer
works fine. Only when I restore that dump to a db and hook up pindexer ingesting a live source db does the error occur.The text was updated successfully, but these errors were encountered: