Repository navigation
Count lightfuzz baseline URLs against spider distance - #3523
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #3523 +/- ##
=====================================
- Coverage 91% 91% -0%
=====================================
Files 461 461
Lines 49625 49644 +19
=====================================
+ Hits 44769 44779 +10
- Misses 4856 4865 +9 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
📊 Performance Benchmark Report
📈 Detailed Results (All Benchmarks)
🎯 Performance Summary+ 2 improvements 🚀
29 unchanged ✅🔍 Significant Changes (>10%)
🐍 Python Version 3.11.17 |
en0f
approved these changes
Oct 13, 2026
Draft
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
speculate emits a
URL_UNVERIFIEDfor anHTTP_RESPONSEwhose URL isn't already in its history. For lightfuzz baseline responses, that URL came from a link on another page, but the new event started at spider distance 0 with nospider-dangertag, so it was visited regardless ofweb.spider_distance. Since lightfuzz re-mines its own baselines, URLs could chain well past the configured limits.speculate now tags these
spider-danger, so they cost a hop like any excavated link. The URL is still emitted and still visited when it's within the spider limits.