Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[RateLimiter] Deprecation "Implicit conversion from float x.xxx to int loses precision" #45949

Closed
@PabloKowalczyk

Description

@PabloKowalczyk

Symfony version(s) affected

6.0.7

Description

After updating RateLimiter component to6.0.7 tests starts to showing "Implicit conversion from float x.xxx to int loses precision" deprecation message. I'm using sliding window policy.

How to reproduce

Example Symfony config

# config/packages/framework.yamlframework:rate_limiter:foo_action:policy:sliding_windowlimit:15interval:'60 minutes'lock_factory:null

then try to use RateLimiter:

finalclass FooAction{publicfunction__construct(privatereadonlyRateLimiterFactory$fooActionLimiter,    ) {    }publicfunction__invoke()    {$limiter =$this->fooActionLimiter            ->create('test')        ;$limit =$limiter->consume();if (false ===$limit->isAccepted()) {thrownew \RuntimeException('Too many actions.');        }    }

Possible Solution

In\Symfony\Component\RateLimiter\Policy\SlidingWindow::getExpirationTime method,$this->windowEndAt andmicrotime return value arefloats, converting type should help:return (int) $this->windowEndAt + $this->intervalInSeconds - (int) microtime(true); or change return type tofloat:public function getExpirationTime(): float.

Additional Context

Earlier patch version (6.0.x) works without deprecation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp