Skip to content
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

chore: fix typos #813

Merged
merged 1 commit into from
Oct 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -788,7 +788,7 @@ Allocation amounts must be non-negative numbers. To resolve this issue ensure th

**Summary**

Action was not executed succesfully: contracts paused or operator not authorized.
Action was not executed successfully: contracts paused or operator not authorized.

**Solution**

Expand Down Expand Up @@ -842,7 +842,7 @@ Failed to resolve POI: POI not available for deployment at current epoch start b

**Solution**

This error typically indicates a subgraph deployment that is too far behind the chain head to resolve a valid POI for closing the allocation. To succesfully resolve the POI and close the allocation you'll need to wait for the index node to sync the deployment enough to generate a POI for the current epoch start block. If you do not want to wait to sync you may choose to forfeit indexing rewards for the allocation by force closing it with a 0 POI by creating an unallocate or reallocate action item: `graph indexer actions queue unallocate/reallocate <deployment-id> <allocation-id> 0 true`.
This error typically indicates a subgraph deployment that is too far behind the chain head to resolve a valid POI for closing the allocation. To successfully resolve the POI and close the allocation you'll need to wait for the index node to sync the deployment enough to generate a POI for the current epoch start block. If you do not want to wait to sync you may choose to forfeit indexing rewards for the allocation by force closing it with a 0 POI by creating an unallocate or reallocate action item: `graph indexer actions queue unallocate/reallocate <deployment-id> <allocation-id> 0 true`.

## IE068

Expand Down
2 changes: 1 addition & 1 deletion packages/indexer-cli/src/commands/indexer/rules/delete.ts
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ module.exports = {
// Since we are not deleting all rules, we must require a protocol network from the user
if (!protocolNetwork) {
throw Error(
'The --netowrk option must be used when deleting a glboal Indexing Rule',
'The --network option must be used when deleting a glboal Indexing Rule',
)
}
const chainAlias = resolveChainAlias(protocolNetwork)
Expand Down
2 changes: 1 addition & 1 deletion packages/indexer-cli/src/commands/indexer/rules/get.ts
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ module.exports = {
} else {
if (!protocolNetwork) {
throw Error(
'The --netowrk option must be used when quering for a single Indexing Rule',
'The --network option must be used when quering for a single Indexing Rule',
)
}
const ruleIdentifier = { identifier, protocolNetwork }
Expand Down