-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: slow starting warm-up feature #622
feat: slow starting warm-up feature #622
Conversation
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
|
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.5 #622 +/- ##
===============================================
Coverage ? 14.73%
===============================================
Files ? 871
Lines ? 63510
Branches ? 0
===============================================
Hits ? 9359
Misses ? 53967
Partials ? 184
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
2e717ef
to
c12c46d
Compare
❗❗❗ git rebase HEAD~1 --signoff
git push --force-with-lease origin release/v1.5.0-alpha.11 |
c12c46d
to
0720e5a
Compare
Signed-off-by: Cybwan <[email protected]> Signed-off-by: Lin Yang <[email protected]>
0720e5a
to
ae16270
Compare
/lgtm |
Description:
add slow starting warm-up feature
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