-
Notifications
You must be signed in to change notification settings - Fork 8
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
Replace Tornado with asyncio #45
Conversation
Reviewer's Guide by SourceryThis pull request replaces the Tornado framework with asyncio for asynchronous operations. The change modernizes the codebase, reduces dependencies, and significantly simplifies the code structure. The main modifications include updating the WHOIS querying mechanism, implementing a new asynchronous server, and adjusting the caching functionality to work with asyncio. Sequence diagram for WHOIS query process with asynciosequenceDiagram
participant Client
participant Server
participant WhoisService
Client->>Server: Send WHOIS query
Server->>WhoisService: Forward query
WhoisService-->>Server: Return WHOIS data
Server-->>Client: Send WHOIS data
Updated class diagram for caching and WHOIS clientclassDiagram
class LFU {
-cache
-max_age
-max_size
-queue
}
class Caching {
+async wrapped(query)
}
class Client {
+async query_whois(host, port, query) : str
}
Caching --> LFU
Caching --> Client
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @kgaughan - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding explicit error handling in the new asyncio code to prevent silent failures and ensure robust operation.
- Implement timeout mechanisms in the
query_whois
function and other network operations to handle unresponsive WHOIS servers.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
@sourcery-ai review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @kgaughan - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
This shrinks the code down significantly, future proofs things somewhat, and means there's one less dependency.
Summary by Sourcery
Enhancements: