Skip to content

fix: compatible with urllib@2 timeout string format #580

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

Merged
merged 1 commit into from
Jul 7, 2025

Conversation

fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Jul 7, 2025

close hyj1991/easy-monitor#166

Summary by CodeRabbit

  • Bug Fixes

    • Improved timeout handling to support string-formatted timeout values, ensuring they are correctly interpreted.
  • Tests

    • Added a test to verify that specifying timeout as a string value works as expected and triggers the appropriate timeout error.

@fengmk2 fengmk2 requested a review from Copilot July 7, 2025 03:28
Copy link

coderabbitai bot commented Jul 7, 2025

Walkthrough

The changes update the handling of the timeout option in the HTTP client to support string-formatted timeouts, ensuring they are parsed as integers before assignment. A new test is added to verify that string timeouts are interpreted correctly and trigger the expected timeout error.

Changes

File(s) Change Summary
src/HttpClient.ts Updated timeout assignment logic to support string-formatted timeouts by parsing them as ints.
test/options.timeout.test.ts Added a test to verify string-formatted timeout values are handled and trigger timeout errors.

Assessment against linked issues

Objective Addressed Explanation
Ensure HTTP client supports string-formatted timeout values to prevent InvalidArgumentError (#166)

Poem

A rabbit hops with nimble feet,
Through timeouts parsed both string and neat.
No errors now, the tests delight,
For numbers, strings—they both work right!
With paws that code and whiskers bright,
The client’s future’s looking light.
🐇⏲️

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/HttpClient.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-eggache".

(The package "eslint-plugin-eggache" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-eggache@latest --save-dev

The plugin "eslint-plugin-eggache" was referenced from the config file in ".eslintrc » eslint-config-egg/typescript » ./index.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

test/options.timeout.test.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-eggache".

(The package "eslint-plugin-eggache" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-eggache@latest --save-dev

The plugin "eslint-plugin-eggache" was referenced from the config file in ".eslintrc » eslint-config-egg/typescript » ./index.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Warning

Review ran into problems

🔥 Problems

Check-run timed out after 90 seconds. Some checks/pipelines were still in progress when the timeout was reached. Consider increasing the reviews.tools.github-checks.timeout_ms value in your CodeRabbit configuration to allow more time for checks to complete.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @fengmk2, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a compatibility issue within the HttpClient by enhancing its timeout handling mechanism. It introduces the ability to correctly interpret and process timeout values provided as strings, aligning its behavior with external libraries like urllib@2. A new test case has been added to confirm the robustness and correctness of this updated timeout parsing logic.

Highlights

  • Timeout Handling Compatibility: Modified the HttpClient to correctly parse string-formatted timeout values by converting them to integers using parseInt(). This ensures compatibility with urllib@2's expected timeout string format, preventing potential issues when timeout is provided as a string instead of a number or tuple.
  • New Test Coverage: Added a new test case (should timeout support string format) to test/options.timeout.test.ts. This test specifically verifies that passing a string value for the timeout option correctly triggers a timeout and that the resulting error details (name, message, cause) are as expected, validating the implemented compatibility fix.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@fengmk2 fengmk2 requested review from killagu and akitaSummer July 7, 2025 03:29
@fengmk2 fengmk2 enabled auto-merge (squash) July 7, 2025 03:29
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds compatibility for string-formatted timeout values by parsing them into integers and includes a corresponding test.

  • Update HttpClient to parse string timeouts for urllib@2 compatibility
  • Add a new test case to verify timeout behavior when provided as a string

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
test/options.timeout.test.ts Added test verifying string-format timeout handling
src/HttpClient.ts Parse string timeout values to integer for compatibility
Comments suppressed due to low confidence (1)

test/options.timeout.test.ts:44

  • [nitpick] The test title is a bit awkward; consider renaming it to "should support timeout as a string format" for clarity.
  it('should timeout support string format', async () => {

Copy link

pkg-pr-new bot commented Jul 7, 2025

Open in StackBlitz

npm i https://pkg.pr.new/node-modules/urllib@580

commit: 26fd25d

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds compatibility for string-based timeout values, as was supported in urllib@2. The implementation correctly handles string-to-number conversion, and a new test case validates this behavior. I've made one suggestion to improve the robustness of the string parsing by explicitly specifying the radix. Overall, the change is clear and well-tested.

Copy link

codecov bot commented Jul 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.64%. Comparing base (d09d316) to head (26fd25d).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #580   +/-   ##
=======================================
  Coverage   95.64%   95.64%           
=======================================
  Files          11       11           
  Lines        1355     1355           
  Branches      312      313    +1     
=======================================
  Hits         1296     1296           
  Misses         55       55           
  Partials        4        4           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/HttpClient.ts (1)

372-373: Improve robustness of string timeout parsing.

The implementation correctly addresses the compatibility requirement, but could be more robust in handling edge cases.

Consider the following improvements:

-        // compatible with urllib@2 timeout string format
-        headersTimeout = bodyTimeout = typeof args.timeout === 'string' ? parseInt(args.timeout) : args.timeout;
+        // compatible with urllib@2 timeout string format
+        headersTimeout = bodyTimeout = typeof args.timeout === 'string' ? parseInt(args.timeout, 10) : args.timeout;

Rationale:

  • Specifying radix 10 ensures consistent decimal parsing
  • However, consider if additional validation is needed for invalid string formats (e.g., parseInt('abc', 10) returns NaN)

Since this is for urllib@2 compatibility, the current approach might be intentionally minimal to match the expected behavior.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 36641dd and 26fd25d.

📒 Files selected for processing (2)
  • src/HttpClient.ts (1 hunks)
  • test/options.timeout.test.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
test/options.timeout.test.ts (1)
test/cjs/index.js (2)
  • assert (2-2)
  • urllib (3-3)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
  • GitHub Check: Node.js / Test (windows-latest, 16)
  • GitHub Check: Node.js / Test (macos-latest, 22)
  • GitHub Check: Node.js / Test (macos-latest, 18)
  • GitHub Check: Node.js / Test (windows-latest, 18)
  • GitHub Check: Node.js / Test (macos-latest, 16)
  • GitHub Check: Node.js / Test (macos-latest, 24)
  • GitHub Check: Node.js / Test (ubuntu-latest, 16)
  • GitHub Check: Node.js / Test (windows-latest, 24)
  • GitHub Check: Node.js / Test (windows-latest, 20)
  • GitHub Check: Node.js / Test (macos-latest, 20)
  • GitHub Check: Node.js / Test (ubuntu-latest, 20)
  • GitHub Check: Node.js / Test (ubuntu-latest, 18)
  • GitHub Check: Node.js / Test (windows-latest, 22)
  • GitHub Check: Node.js / Test (ubuntu-latest, 24)
  • GitHub Check: Node.js / Test (ubuntu-latest, 22)
🔇 Additional comments (1)
test/options.timeout.test.ts (1)

44-63: Excellent test coverage for string timeout compatibility.

The test case effectively validates the string timeout format compatibility:

  • Mirrors the existing numeric timeout test structure
  • Verifies identical error behavior for both string and numeric inputs
  • Includes appropriate TypeScript error handling with @ts-expect-error

The test confirms that timeout: '10' produces the same HttpClientRequestTimeoutError with identical properties as timeout: 10, ensuring backward compatibility is maintained.

@fengmk2 fengmk2 requested a review from gxkl July 7, 2025 03:39
Copy link
Member

@killagu killagu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fengmk2 fengmk2 disabled auto-merge July 7, 2025 05:38
@fengmk2 fengmk2 added this pull request to the merge queue Jul 7, 2025
Merged via the queue into master with commit 5eaf790 Jul 7, 2025
25 checks passed
@fengmk2 fengmk2 deleted the compatible-timeout-string-format branch July 7, 2025 05:42
fengmk2 pushed a commit that referenced this pull request Jul 7, 2025
[skip ci]

## [4.7.1](v4.7.0...v4.7.1) (2025-07-07)

### Bug Fixes

* compatible with urllib@2 timeout string format ([#580](#580)) ([5eaf790](5eaf790))
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.

upload_file 命令异常
2 participants