Skip to content

🔥 feat: Add config for Timeout middleware #3604

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 2 commits into from
Jul 20, 2025

Conversation

ReneWerner87
Copy link
Member

Summary

  • make timeout middleware configurable via Config
  • document new Config struct and update code examples
  • mention timeout middleware changes in whats_new
  • add comprehensive tests
  • revert .golangci.yml changes
  • add migration example in docs

Testing

  • make format
  • make lint (fails: unsupported version of config)
  • make test

https://chatgpt.com/codex/tasks/task_e_687cda110df083268e34701e17ff98e7

@Copilot Copilot AI review requested due to automatic review settings July 20, 2025 12:52
@ReneWerner87 ReneWerner87 requested a review from a team as a code owner July 20, 2025 12:52
Copy link
Contributor

coderabbitai bot commented Jul 20, 2025

Walkthrough

The timeout middleware has been refactored to use a new Config struct for configuration, replacing positional parameters in its constructor. Documentation and tests were updated to reflect this change. The middleware now supports conditional skipping and custom timeout handlers, and new tests cover these features and edge cases.

Changes

File(s) Change Summary
docs/middleware/timeout.md, docs/whats_new.md Updated documentation to describe and demonstrate the new timeout.Config struct and revised middleware usage.
middleware/timeout/config.go Added new file defining the Config struct, its defaults, and a helper for configuration normalization.
middleware/timeout/timeout.go Refactored middleware to accept Config, updated function signatures, and added support for custom handlers.
middleware/timeout/timeout_test.go Updated tests to use Config, added new test cases for negative durations and custom timeout handlers.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Fiber
    participant TimeoutMiddleware
    participant Handler

    Client->>Fiber: Sends Request
    Fiber->>TimeoutMiddleware: Passes Request
    TimeoutMiddleware->>TimeoutMiddleware: Checks Config (Next, Timeout, OnTimeout, Errors)
    alt Next returns true
        TimeoutMiddleware->>Fiber: Skips middleware, calls next handler
    else Timeout > 0
        TimeoutMiddleware->>Handler: Runs handler with timeout context
        alt Handler completes in time
            Handler-->>TimeoutMiddleware: Returns response
            TimeoutMiddleware-->>Fiber: Passes response
        else Timeout occurs or custom error
            alt OnTimeout handler set
                TimeoutMiddleware->>OnTimeout: Invokes custom handler
                OnTimeout-->>TimeoutMiddleware: Returns custom response
            else
                TimeoutMiddleware-->>Fiber: Returns fiber.ErrRequestTimeout
            end
        end
    else
        TimeoutMiddleware->>Handler: Runs handler without timeout
        Handler-->>TimeoutMiddleware: Returns response
        TimeoutMiddleware-->>Fiber: Passes response
    end
    Fiber-->>Client: Sends Response
Loading

Possibly related PRs

  • gofiber/fiber#3382: Changes Fiber context to implement context.Context, directly affecting how the timeout middleware creates and uses contexts.
  • gofiber/fiber#3275: Refactors and enhances the timeout middleware, related to this PR's refactoring but does not introduce the Config struct.

Suggested labels

✏️ Feature, 📒 Documentation, v3

Suggested reviewers

  • sixcolors
  • efectn
  • gaby

Poem

In the garden of code where timeouts bloom,
A new config struct brings much more room.
Custom handlers hop in, skipping’s now neat,
Docs and tests refreshed for a treat.
With every request, the middleware’s spry—
A rabbit’s delight as the seconds hop by!
🐇⏳


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ef2f9d2 and bc1e66e.

📒 Files selected for processing (1)
  • docs/middleware/timeout.md (5 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/middleware/timeout.md
⏰ 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). (4)
  • GitHub Check: unit (1.24.x, macos-13)
  • GitHub Check: Compare
  • GitHub Check: unit (1.24.x, windows-latest)
  • GitHub Check: repeated

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
Contributor

@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 @ReneWerner87, 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 refactors the timeout middleware to introduce a more robust and extensible configuration mechanism. By moving from simple parameters to a dedicated Config struct, it provides developers with fine-grained control over timeout behavior, custom error handling, and middleware skipping, enhancing the middleware's utility and adaptability.

Highlights

  • Configurable Timeout Middleware: The timeout middleware can now be configured using a new Config struct, replacing the previous fixed time.Duration and error parameters. This allows for more flexible and powerful control over timeout behavior.
  • New Configuration Options: The Config struct introduces several new options: Next (a function to skip the middleware), OnTimeout (a custom handler to execute on timeout), and Errors (a list of custom errors to treat as timeouts), alongside the Timeout duration.
  • Updated API and Documentation: The New function signature for the timeout middleware has been updated to accept the Config struct. Corresponding documentation in docs/middleware/timeout.md and docs/whats_new.md has been added and updated, including migration examples.
  • Comprehensive Testing: Existing tests have been updated, and new tests have been added to ensure full coverage of the new configuration options, including scenarios for negative timeout durations, custom timeout handlers, and various error handling cases.
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.

@ReneWerner87 ReneWerner87 added this to v3 Jul 20, 2025
Copy link
Contributor

@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 refactors the timeout middleware to be configurable through a Config struct instead of accepting timeout duration and errors as separate parameters. The changes improve the middleware's flexibility by allowing customization of timeout behavior, error handling, and conditional execution.

  • Introduces a new Config struct with fields for timeout duration, custom timeout handler, error list, and skip condition
  • Updates the New function signature to accept variadic Config parameters instead of separate duration and error parameters
  • Adds comprehensive test coverage for new configuration options and edge cases

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
middleware/timeout/config.go New configuration struct and default handling logic
middleware/timeout/timeout.go Updated middleware implementation to use Config struct
middleware/timeout/timeout_test.go Enhanced test suite with new test cases for configuration options
docs/middleware/timeout.md Updated documentation with new API and configuration table
docs/whats_new.md Migration guide and changelog entries for the API changes
Comments suppressed due to low confidence (2)

middleware/timeout/timeout_test.go:173

  • This test directly calls the internal runHandler function but doesn't use t.Parallel() like other test functions. Consider adding t.Parallel() for consistency with the testing pattern used throughout this file.
func TestRunHandler_DefaultOnTimeout(t *testing.T) {

middleware/timeout/timeout_test.go:186

  • This test directly calls the internal runHandler function but doesn't use t.Parallel() like other test functions. Consider adding t.Parallel() for consistency with the testing pattern used throughout this file.
func TestRunHandler_CustomOnTimeout(t *testing.T) {

Copy link

codecov bot commented Jul 20, 2025

Codecov Report

Attention: Patch coverage is 92.10526% with 3 lines in your changes missing coverage. Please review.

Project coverage is 90.97%. Comparing base (5dffcb6) to head (bc1e66e).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
middleware/timeout/timeout.go 84.21% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3604      +/-   ##
==========================================
+ Coverage   90.93%   90.97%   +0.04%     
==========================================
  Files         111      112       +1     
  Lines       11236    11260      +24     
==========================================
+ Hits        10217    10244      +27     
+ Misses        764      762       -2     
+ Partials      255      254       -1     
Flag Coverage Δ
unittests 90.97% <92.10%> (+0.04%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

Copy link
Contributor

@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 introduces a Config struct to enhance the timeout middleware's flexibility. The changes are well-implemented, but context propagation for timeouts and code simplification can be improved.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Member

@gaby gaby left a comment

Choose a reason for hiding this comment

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

LGTM, just one small thing

@gaby gaby changed the title Add Config for timeout middleware 🔥 feat: Add config for Timeout middleware Jul 20, 2025
github-actions[bot]

This comment was marked as outdated.

@ReneWerner87 ReneWerner87 merged commit 05f8ac0 into main Jul 20, 2025
14 of 15 checks passed
@ReneWerner87 ReneWerner87 deleted the codex/2025-07-20-12-52-50 branch July 20, 2025 13:22
@github-project-automation github-project-automation bot moved this to Done in v3 Jul 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants