fix: fix RampsController flaky test

[amitabh94]

Explanation

• What is the current state of things and why does it need to change?
  The test "evicts oldest entries when cache exceeds max size" in RampsController.test.ts was flaky. It used 5ms setTimeout delays to create distinct timestamps for cache entries, which was too short for reliable execution in CI environments due to Date.now() resolution limitations and execution timing variations under load. This led to non-deterministic cache eviction order.
• What is the solution your changes offer and how does it work?
  The setTimeout delays within this specific test have been increased from 5ms to 20ms. This provides a more robust time separation between cache entries, ensuring distinct timestamps and consistent eviction behavior, thereby resolving the flakiness.

References

• Fixes a flaky test in RampsController.test.ts.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Slack Thread

  

---

Note

Low Risk
Test-only timing tweak; no production code paths are changed, with minimal risk beyond slightly longer test runtime.

Overview
Makes the RampsController cache-eviction test deterministic in CI by increasing the inter-request delay used to create distinct timestamps.

In RampsController.test.ts, the cache eviction test now waits 20ms (was 5ms) between executeRequest calls so the “oldest entry” eviction order is stable.

^{Written by Cursor Bugbot for commit 063cbe7. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}