frostfs-node/cmd
Aleksey Savchuk 4919b6a206
All checks were successful
Vulncheck / Vulncheck (push) Successful in 1m14s
Pre-commit hooks / Pre-commit (push) Successful in 1m51s
Build / Build Components (push) Successful in 2m1s
Tests and linters / Run gofumpt (push) Successful in 2m38s
Tests and linters / Tests (push) Successful in 2m53s
Tests and linters / Staticcheck (push) Successful in 3m9s
Tests and linters / Lint (push) Successful in 4m5s
Tests and linters / gopls check (push) Successful in 4m34s
OCI image / Build container images (push) Successful in 4m58s
Tests and linters / Tests with -race (push) Successful in 5m59s
[#1689] node/config: Allow zero max_ops in RPC limits config
The limiter allows zeros for limits, meaning "this operation is
disabled".  However, the config didn't allow zero due to the lack of
distinction between "no value" and "zero" - cast functions read both
`nil` and zero as zero.

Now, the config allows a zero limit. Added tests.

Managing such cases should be easier after #1610.

Change-Id: Ifc840732390b2feb975f230573b34bf479406e05
Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
2025-03-21 17:00:40 +03:00
..
frostfs-adm [#1678] adm: Fix frostfs-adm morph list-subjects & list-group-subjects 2025-03-14 13:42:29 +00:00
frostfs-cli [#1695] mod: Bump frostfs-observability version 2025-03-21 13:28:02 +03:00
frostfs-ir [#1619] logger: Simplify logger config reloading 2025-03-21 09:03:54 +00:00
frostfs-lens [#1671] Use slices.Delete() where possible 2025-03-13 08:12:20 +00:00
frostfs-node [#1689] node/config: Allow zero max_ops in RPC limits config 2025-03-21 17:00:40 +03:00
internal/common [#1519] cli: Make descriptive help for--rule option 2024-11-25 07:21:05 +00:00