chore: PRT - fireblocks with consumer fix on session management. 27/02/25 #1977
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
feat: FB - Added periodic provider probe
…test_block_metric feat: FB - Added provider_endpoint to lava_consumer_latest_provider_block
…s_metrics feat: FB add provider endpoint to qos metrics
…into PRT-fb-branch-with-offline-policy-v-4-2-4
…RT-add-lava-consumer-blocked-providers-metrics-new
…roviders-metrics-new
# Description Closes: #XXXX <!-- Add a description of the changes that this PR introduces and the files that are the most critical to review. --> --- ## Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... * [ ] read the [contribution guide](https://github.com/lavanet/lava/blob/main/CONTRIBUTING.md) * [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title, you can find examples of the prefixes below: <!-- * `feat`: A new feature * `fix`: A bug fix * `docs`: Documentation only changes * `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) * `refactor`: A code change that neither fixes a bug nor adds a feature * `perf`: A code change that improves performance * `test`: Adding missing tests or correcting existing tests * `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) * `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) * `chore`: Other changes that don't modify src or test files * `revert`: Reverts a previous commit --> * [ ] confirmed `!` in the type prefix if API or client breaking change * [ ] targeted the `main` branch * [ ] provided a link to the relevant issue or specification * [ ] reviewed "Files changed" and left comments if necessary * [ ] included the necessary unit and integration tests * [ ] updated the relevant documentation or specification, including comments for [documenting Go code](https://blog.golang.org/godoc) * [ ] confirmed all CI checks have passed ## Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... * [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title * [ ] confirmed all author checklist items have been addressed * [ ] reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage
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
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!in the type prefix if API or client breaking changemainbranchReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...