Myasnikov Daniil
2b2b75a550
Three gaps a mutation pass found, all in terms nothing asserted. The install step's `if:` was pinned on one of its two conjuncts. Losing `steps.target.outcome == 'success'` from it specifically is worse than losing it elsewhere: a matrix leg whose label is absent skips `Set target branch`, so the merged-backport guard skips too, so `steps.guard.outputs.already_merged` is the empty string and `!= 'true'` is true. The install step would then run on a leg whose checkout has skipped -- no working tree -- and its `sed` on hack/backport-git-shim.sh would fail on a missing file under `set -eu`. A red `previous` leg on every PR carrying only `kind/backport`, sitting next to a delivered backport. The pin is now the whole condition on all three gated steps, plus each conjunct's own count. The first attempt at that pin asserted three occurrences of the conjunct where the file has four -- the guard's own gate is `steps.target.outcome == 'success'` alone, since it is what decides `already_merged` and cannot also test it. Three is exactly what the mutant produces, so the pin agreed with the mutant and disagreed with the file: green on the mutation it was written to catch, red on HEAD. Instrumenting the count is what showed it; reading it again would not have. The wrapper's passthrough listed `--continue`, `--skip` and `--quit` beside `--abort`, and only `--abort` was asserted. Those three are unreachable from the pinned action, so dropping them broke nothing and nothing reported it. Asserted on the message rather than the exit code, because the exit code does not discriminate -- measured on git 2.55, `--continue` and `--skip` answer 128 either way and differ only in whether git says "--empty cannot be used with". And docs/release.md's manual cherry-pick fallback, in the section directly below the new one, walked an operator into the same wall the wrapper removes for the bot: without the two flags, a commit that is empty or already upstream stops the pick with "The previous cherry-pick is now empty" and no hint that carrying on is the right move. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.