fix: validate shell byte limit types #336

Open
nsaspy wants to merge 0 commits from rage/290-shell-byte-limits into main
Owner

Closes #290. Advances #5.

RED first: direct CommandPolicy construction currently accepts bool/float byte limits, which can either silently collapse to one byte or fail later during output slicing instead of failing closed at policy construction.

No cancellation side channel; no Zara Core changes.

Closes #290. Advances #5. RED first: direct `CommandPolicy` construction currently accepts bool/float byte limits, which can either silently collapse to one byte or fail later during output slicing instead of failing closed at policy construction. No cancellation side channel; no Zara Core changes.
Some checks failed
CI / test (pull_request) Failing after 17s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/290-shell-byte-limits:rage/290-shell-byte-limits
git switch rage/290-shell-byte-limits

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/290-shell-byte-limits
git switch rage/290-shell-byte-limits
git rebase main
git switch main
git merge --ff-only rage/290-shell-byte-limits
git switch rage/290-shell-byte-limits
git rebase main
git switch main
git merge --no-ff rage/290-shell-byte-limits
git switch main
git merge --squash rage/290-shell-byte-limits
git switch main
git merge --ff-only rage/290-shell-byte-limits
git switch main
git merge rage/290-shell-byte-limits
git push origin main
Sign in to join this conversation.
No description provided.