fix: fix memory pools & race issues #178
Merged
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.
fixes
a memory leak with recycled *Result in schema_props.go was causing
some invalid results when GC is under pressure (seen on go-swagger test)
reused after they are exhausted
and example validators
with go1.22, the race detector figured a race condition when expanding
the swagger schema for parameters (spec.go)
a parameter, deep clone the schema from the root spec. This is
performed once for a spec, so the perf impact should be negligible
tests
with the highest probability
build tag) to assert more thorough checks of the correctness of the
pools usage
Signed-off-by: Frederic BIDON fredbi@yahoo.com