Repository navigation
chore: update tornado to 6.6 - #1122
Conversation
Signed-off-by: Andre Manoel <amanoel@nvidia.com>
[Medium impact] The PR appears safe to merge; no actionable issues were found. SummaryRaises the notebook dependency floor to Tornado 6.6 to address the advisories described in the PR.
Reviews (2) · Last reviewed commit: "Merge branch 'main' into andreatnvidia/c..." · Reviewed by Greptile |
svcnvidia-nemo-ci
left a comment
There was a problem hiding this comment.
No Critical or Warning findings.
The notebook dependency floor, lock requirement metadata, and Tornado package record are consistent. Reviewed the affected installation, notebook execution, and security-audit paths; no introduced defect was identified.
Validation was static only. Tests, dependency resolution, audits, and Jupyter smoke checks were not executed, and upstream advisory ranges and artifact hashes were not independently verified.
Note: formal approval is not available for this request, so this review is posted as a comment only.
Review generated by codex. This was a full review. Request a full review with /review reset=true.
nabinchha
left a comment
There was a problem hiding this comment.
Thanks for putting this together, @andreatnvidia!
Summary
PR #1122 raises the notebook dependency floor to tornado>=6.6,<7 and updates its lock entry, matching the stated intent. Reviewed commit 0678acb4fa57220e04b59058300c49c9fc5ddb89.
Findings
No actionable findings.
What Looks Good
- The dependency floor and lock requirement metadata agree; unrelated dependency records remain unchanged.
- Tornado 6.6 requires Python 3.11+, matching the workspace and all three packages. This is consistent with the upstream release notes.
- All 43 locked Tornado artifacts match PyPI metadata for URL, SHA256, and size.
Residual Risk
Independent checks passed: uv lock --check --offline, uv audit --locked (189 packages; no known vulnerabilities or adverse project statuses), the generated security-constraints check, and Ruff's pyproject check. The author’s unit tests, E2E audit, and Jupyter runtime smoke tests were not repeated.
Verdict
Ship it — no introduced defects identified.
This review was generated by an AI assistant.
📋 Summary
The workspace dependency audit fails on three advisories in Tornado 6.5.10. Update the notebook dependency to Tornado 6.6, which fixes the open redirect and HTTP parsing denial-of-service issues, so the committed workspace lock passes the audit.
🔗 Related Issue
N/A. Addresses the existing dependency-audit failure reported on #1120.
🔄 Changes
tornado>=6.6,<7.🧪 Testing
/api/statusrequest.✅ Checklist