This repository has been archived by the owner on May 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 333
feat(all): disable no beacon client seen warning #279
Merged
Merged
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
Codecov Report
@@ Coverage Diff @@
## main #279 +/- ##
==========================================
+ Coverage 51.31% 52.05% +0.73%
==========================================
Files 36 36
Lines 3788 3840 +52
==========================================
+ Hits 1944 1999 +55
+ Misses 1589 1584 -5
- Partials 255 257 +2
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
davidtaikocha
approved these changes
Jun 15, 2023
davidtaikocha
added a commit
that referenced
this pull request
Jun 15, 2023
Co-authored-by: David <[email protected]>
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
By on interval calling ExchangeTransitionConfigurationV1 through the engine, lastTransitionUpdate gets updated and the beacon warning is consequently never triggered. Default TransitionConfiguration used according to execution api specs