fix: virtual machine monitor. #602
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
cybwan
requested review from
reaver-flomesh,
naqvis,
caishu97 and
i0r3k
as code owners
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 Enforce verified commitsWonderful, this rule succeeded.Make sure that we have verified commits
🟢 Enforce linear historyWonderful, this rule succeeded.Make sure that we have a linear history, no merge commits are allowed
|
reaver-flomesh
approved these changes
Dec 31, 2024
reaver-flomesh
added
area/connector
reaver-flomesh
force-pushed
the
release/v1.4.17-alpha.1
branch
2 times, most recently
from
97977d1 to
ef33aa7
Compare
|
❗❗❗ git rebase HEAD~1 --signoff
git push --force-with-lease origin release/v1.4.17-alpha.1 |
reaver-flomesh
force-pushed
the
release/v1.4.17-alpha.1
branch
3 times, most recently
from
1c4d408 to
470077c
Compare
Signed-off-by: Cybwan <[email protected]> Signed-off-by: Lin Yang <[email protected]>
reaver-flomesh
force-pushed
the
release/v1.4.17-alpha.1
branch
from
470077c to
92d1019
Compare
|
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## release/v1.4 #602 +/- ##
===============================================
Coverage ? 14.16%
===============================================
Files ? 820
Lines ? 65280
Branches ? 0
===============================================
Hits ? 9245
Misses ? 55860
Partials ? 175
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
/lgtm |
github-actions
bot
added
ok-to-merge
mergify bot
pushed a commit
that referenced
this pull request
Dec 31, 2024
fix virtual machine monitor. Signed-off-by: Cybwan <[email protected]> Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 59b8f26)
reaver-flomesh
pushed a commit
that referenced
this pull request
Dec 31, 2024
fix virtual machine monitor. Signed-off-by: Cybwan <[email protected]> Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 59b8f26) Signed-off-by: Lin Yang <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Dec 31, 2024
fix: virtual machine monitor. (#602) fix virtual machine monitor. (cherry picked from commit 59b8f26) Signed-off-by: Cybwan <[email protected]> Signed-off-by: Lin Yang <[email protected]> Co-authored-by: Cybwan <[email protected]>
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:
fix virtual machine monitor.
Testing done:
Done
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project? no
Is this a breaking change? no
Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)? no