Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Make depth retrieval more resilient to poisoning #5515

Merged
merged 2 commits into from
Dec 12, 2024
Merged

Conversation

dubzzz
Copy link
Owner

@dubzzz dubzzz commented Dec 12, 2024

Description

Retrieving the depth is a shared operations that can be leveraged by various of our arbitraries. Its current implementation was possibly leading to poisoning crashes into some very specific circumstances. This PR drops a few remaing problematic cases.

In theory, while backing ourselves against poisoning is important for us, it should not bring any visible difference to our users except into very corrupted and vulnerable code they could have wrote.

ChecklistDon't delete this checklist and make sure you do the following before opening the PR

  • The name of my PR follows gitmoji specification
  • My PR references one of several related issues (if any)
    • New features or breaking changes must come with an associated Issue or Discussion
    • My PR does not add any new dependency without an associated Issue or Discussion
  • My PR includes bumps details, please run yarn bump and flag the impacts properly
  • My PR adds relevant tests and they would have failed without my PR (when applicable)

Advanced

  • Category: 🐛 Fix a bug
  • Impacts: None expected, should be more resilient to poisoning

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Retrieving the depth is a shared operations that can be leveraged by various of our arbitraries. Its current implementation was possibly leading to poisoning crashes into some very specific circumstances. This PR drops a few remaing problematic cases.

In theory, while backing ourselves against poisoning is important for us, it should not bring any visible difference to our users except into very corrupted and vulnerable code they could have wrote.
Copy link

changeset-bot bot commented Dec 12, 2024

🦋 Changeset detected

Latest commit: 507593f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
fast-check Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

pkg-pr-new bot commented Dec 12, 2024

Open in Stackblitz@fast-check/examples

@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@5515

@fast-check/expect-type

npm i https://pkg.pr.new/@fast-check/expect-type@5515

fast-check

npm i https://pkg.pr.new/fast-check@5515

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@5515

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@5515

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@5515

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@5515

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@5515

commit: 507593f

@dubzzz dubzzz enabled auto-merge (squash) December 12, 2024 23:00
Copy link

codecov bot commented Dec 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.91%. Comparing base (6d9dc46) to head (507593f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5515   +/-   ##
=======================================
  Coverage   94.91%   94.91%           
=======================================
  Files         235      235           
  Lines       10040    10041    +1     
  Branches     2838     2840    +2     
=======================================
+ Hits         9529     9530    +1     
  Misses        511      511           
Flag Coverage Δ
unit-tests 94.91% <100.00%> (+<0.01%) ⬆️
unit-tests-18.x-Linux 94.91% <100.00%> (+<0.01%) ⬆️
unit-tests-20.x-Linux 94.91% <100.00%> (+<0.01%) ⬆️
unit-tests-22.x-Linux 94.91% <100.00%> (+0.05%) ⬆️
unit-tests-latest-Linux 94.91% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

👋 A preview of the new documentation is available at: http://675b6e0b6c1b9b1f6a12ebc2--dubzzz-fast-check.netlify.app

@dubzzz dubzzz merged commit 19fe7c6 into main Dec 12, 2024
59 checks passed
@dubzzz dubzzz deleted the depth-fix branch December 12, 2024 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant