Repository navigation
Fix USENIX discovery coverage and add QUIC-Attacker findings - #38
myleshorton wants to merge 2 commits into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (6)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe crawler now includes the USENIX Security technical-sessions page and separates page parsing from fetching. Tests cover final-program parsing and deduplication. The corpus adds a QUIC-Attacker paper record and three related evaluation findings. ChangesUSENIX Security crawl expansion
QUIC-Attacker corpus entry
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant CrawlLoop
participant fetchUSENIXSecurity
participant parseUSENIXSecurity
CrawlLoop->>fetchUSENIXSecurity: fetch technical-sessions and cycle pages
fetchUSENIXSecurity->>parseUSENIXSecurity: pass page text, URL, and year
parseUSENIXSecurity-->>fetchUSENIXSecurity: return candidate records
fetchUSENIXSecurity-->>CrawlLoop: provide parsed records
Merge Risk: ⚪ Minimal · up to The crawler and corpus additions pass the applicable checks with no demonstrated merge-blocking risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 2 files. (4 skipped: 4 unsupported.) ✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
|
@copilot resolve the merge conflicts on this branch. |
# Conflicts: # cmd/corpus-crawl/main.go Co-authored-by: myleshorton <1143966+myleshorton@users.noreply.github.com>
Resolved the conflict and merged |
The USENIX crawler only visited cycle acceptance pages, omitting papers available in the final technical program. On September 7, the 2026 Cycle 2 URL returned 404, and neither QUIC-Attacker nor the Geedge source-code paper appeared on Cycle 1. Include the final program for both supported years and recognize “Geedge” in the title filter. Existing identity deduplication handles overlap between pages.
Add QUIC-Attacker with three source-grounded findings on compatibility, frame-placement security, and reusable evaluation catalogs. Its relevance to protocol generation is explicitly distinguished from a demonstrated censorship-evasion result.
The public-site audit found the other 13 papers already published with extracted findings. Geedge was ingested August 24 through net4people. The Mini was inaccessible during this audit, so its per-run logs were not inspected; the source-page coverage gap was reproduced directly.
Validation: Go build, vet, and all tests passed; corpus bundling and static-site generation passed (492 papers, 2,131 findings). A regression test covers final-program inclusion, parsing both USENIX titles, title filtering, and duplicate recognition.
Summary by CodeRabbit
New Features
Bug Fixes