discovery: add logging at DEBUG level for orchestrator pool predicate function when using default on-chain selection #1335
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.
What does this pull request do? Explain your changes. (required)
This PR adds logging at the
DEBUG
level when eithersender.ValidateTicketParams
or the broadcastermaxPrice
check fails in theOrchestratorPool
predicate function that is used in default on-chain selection mode to filter out orchestrators that aren't usable for our B.This adds a little more insight when no orchestrators are found due to them all failing this predicate function, currently it would only log
0 responses , err=<nil>
.Not necessary to include this but since I added it for debugging purposes I might as well open a PR for it.
How did you test each of these updates (required)
used them to debug labrador deployment
Does this pull request close any open issues?
Checklist:
./test.sh
pass