Prod Release 24/07/2024 #916
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
darunrs
commented
Jul 23, 2024
•
darunrs
commented
- feat: revamp BOS component Dashboard Nav, BOS component explorer, introduce launchpad prototype, and added 404 fallback. (feat: revamp BOS component Dashboard Nav, BOS component explorer, introduce launchpad prototype, and added 404 fallback. #867)
- chore: code separation of launchpad (chore: code separation of launchpad #905)
- refactor: Fetch Database Connection Parameters in Stream Handler (refactor: Fetch Database Connection Parameters in Stream Handler #890)
- feat: converted wizard dummy file to ts, added additional testcases (feat: converted wizard dummy file to ts, added additional testcases #911)
- feat: use QueryAPI Indexer for Explorers and added pagination (feat: use QueryAPI Indexer for Explorers and added pagination #907)
- feat: Add metric for receiver block backfill failures (feat: Add metric for receiver block backfill failures #912)
- feat: Programmatically Execute Indexer Locally (feat: Programmatically Execute Indexer Locally #908)
- fix: Implement retry on tracking foreign keys and resolve hasura env issue (fix: Implement retry on tracking foreign keys and resolve hasura env issue #919)
- fix: Add gensonjs to changed selectMethod and selectEvent to proper TS shape (fix: Add gensonjs to changed selectMethod and selectEvent to proper TS shape #918)
- Add how to run frontend to README (Add how to run frontend to README #921)
…roduce launchpad prototype, and added 404 fallback. (#867) added BOS component launchpad, and a general 404 fallback. revamped and integrated launchpad with new navigation with style reword for better alignment towards future styles https://www.loom.com/share/bc9ed95387e5451f94fac65eac2bb146?sid=a3763829-bc5c-4c67-af06-9433762570f5
code cleanup/separation into separate BOS component
Due to our migration of Provisioning logic to a separate API in Runner, we can expect that an Indexers resources will be initialized before we reach the point of executing blocks. So, it is no longer necessary to lazy init DmlHandler or IndexerMeta due to not having the connection parameters at the time of class initialization. Worker can poll for these params before even beginning to execute any blocks. This also continues to simplify both the code and behavior of the execute function.
…911) converted the generateCode dummy file to TS and added additional testcases.
QueryAPI Indexer's explore page now fetches from Indexers and will default to NEAR RPC request if something goes wrong. Added Pagination/Loading more for All Indexers
Adds a metric for tracking receiver block backfill status. Since the backfill has an end state, I can't rely on constantly incrementing a counter. Instead, I use a gauge and check for non zero values. If the backfill starts and completes without issue, the value will be 0. But, if the backfill fails, it will increment the gauge and then skip to Lake backfill, leaving the gauge at a nonzero value. We can alert on this. If the stream is restarted, then a successful attempt at the backfill will reset the gauge to 0.
This PR sets up a local indexer class which leverages the in memory dml handler class and a no op indexer meta class to fully execute indexer logic locally on a block. The class is responsible for downloading block data and providing helper functions to abstract testing logic away. This PR also sets up a core-indexers folder which is used to verify that the created local indexer is actually capable of executing indexer code locally. The core-indexers folder may be temporary as we do intend to eventually publish a testing framework npm package. For the time being, it uses relative imports to work.
…issue (#919) This PR adds exponential retry for the tracking of foreign keys. For now I'm keeping the implementation of expo retry in provisioner light for two reasons: 1. I want to confirm that expo retry actually solves the issue. 2. I plan to refactor the provisioning process entirely. I also noticed a bug where the env variables were being set to empty in all cases instead of only if null. I fix this bug as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.