presync feedback loop - subcommand indexing status #11
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
hopeyen
added
size:medium
hopeyen
requested review from
neriumrevolta
and removed request for
chriswessels
neriumrevolta
previously approved these changes
Aug 28, 2023
hopeyen
dismissed
neriumrevolta’s stale review
The merge-base changed after approval.
hopeyen
force-pushed
the
hope/subcommand-indexing-status
branch
from
20c48f9
to
3731d3b
Compare
|
rebased to latest dev |
neriumrevolta
approved these changes
Aug 28, 2023
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.
Description
After sending
UpgradeIntentMessage, a developer can periodically check the indexing status of the new subgraph deployment at the public APIs of the indexers who actively allocates on the current version of the subgraph.Same arguments here can be used as the argument for
UpgradeIntentMessage.Example usage
Expected output
Issue link (if applicable)
Resolves #8
Checklist