Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 5 commits
- 14 files changed
- 3 contributors
Commits on May 24, 2024
-
fix: don't print PR title in github workflow (#218)
Printing the PR title can open the door for remote code execution, so this commit removes it to be on the safe side.
-
feat: Add fuzzers for BTreeMap and MinHeap (#217)
- Added two fuzzers `stable_btreemap_multiple_ops_persistent` and `stable_minheap_multiple_ops_persistent` - Added a CI job to check if the fuzzers can be built. However, the fuzzers are not run on CI yet. To run a fuzzer locally, ```sh rustup toolchain install nightly cargo install cargo-fuzz cargo +nightly fuzz run stable_btreemap_multiple_ops_persistent ```
Commits on May 28, 2024
-
fix(ci): Sanitize PR title by using ENV (#219)
As a follow up to #218 we need to further sanitize by using the intermediate step of using an environment variable to avoid possible script injection attack.
Commits on Jun 7, 2024
-
fix: grow memory when necessary in
BaseVec::set. (#222)## Problem `BaseVec`, which is the underlying data structure used by `StableVec` and `StableMinHeap` provides a `set` method that allows the caller to change the value of an element at a specified index. The `set` method used the `memory.write` method, which assumed that there is always enough memory to rewrite the element. This assumption would've been fine if other methods like `pu 8000 sh` always allocated the maximum amount of space for every element. Currently though, `push` only allocates the amount needed to store the element that's being pushed. ## Solution There are two possible solutions: 1. Modify `push` to always allocate the maximum size of an element. 2. Modify `set` to grow the memory as needed as it's rewriting an element. This commit implements solution 2, which is both simpler and more performant.
Commits on Jun 10, 2024
-
chore: bump version to 0.6.5 (#223)
Prepares a new release to include a fix to `BaseVec`.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.6.4...v0.6.5