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

indexer-common: Fix bug in isDeploymentWorthAllocatingTowards() #480

Merged
merged 1 commit into from
Sep 10, 2022

Conversation

fordN
Copy link
Contributor

@fordN fordN commented Sep 10, 2022

The bug affected indexing-rules using minSignal thresholds without a 'maxSignal' threshold set. In this scenario the indexer-agent would find all rules above the minSignal threshold not worthy of allocating to because they didn't also have a maxSignal threshold set. This check has now been fixed to only use the maxSignal threshold if one is set.

I also took the opportunity to make some minor updates to:

  • update error reference page url: use main branch
  • use consistent subgraph naming convention: indexer-agent/${networkSubgraphDeployment.ipfsHash.slice(-10)}.

- The bug affected indexing-rules using `minSignal` thresholds without a
'maxSignal' threshold set
- Also made some minor updates to:
    - update error reference page url: use `main` branch
    - use consistent subgraph naming convention:
      `indexer-agent/${networkSubgraphDeployment.ipfsHash.slice(-10)}`
@fordN fordN merged commit 0b6ed28 into main Sep 10, 2022
@fordN fordN deleted the ford/fixes branch September 10, 2022 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant