Introduce a memory leak to check the k6 tests - follow up on #5213 #5214
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
Related to #5179 by @obulat
Description
Between the versions of 2.1.7 and 2.2.5, Pinia has fixed the problem that was causing a memory leak when initializing a store from an existing object (probably in fix: reference the store directly in storeToRefs to ensure correct reactivity after HMR). This means that #5179 alone is not enough to introduce a memory leak, we need to downgrade pinia as well.
Testing Instructions
This change will only be used to test k6 in staging, and will be reversed later.
Checklist
Update index.md
).main
) or a parent feature branch.ov just catalog/generate-docs
for catalogPRs) or the media properties generator (
ov just catalog/generate-docs media-props
for the catalog or
ov just api/generate-docs
for the API) where applicable.Developer Certificate of Origin
Developer Certificate of Origin