Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: e2b-dev/runtime
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: e2b-dev/runtime
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: api-cluster-cache-ttl
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 2 files changed
  • 1 contributor

Commits on Jul 30, 2026

  1. Bound in-memory cluster configuration freshness 

    Revalidate each remote cluster configuration after five minutes plus jitter. Rebuild only changed clients, publish replacements atomically, and retain the old client when refresh initialization fails.
    @matthewlouisbrockman
    matthewlouisbrockman committed Jul 30, 2026
    Configuration menu
    Copy the full SHA
    1479674 View commit details
    Browse the repository at this point in the history

  2. Refresh changed cluster configs on every sync 

    The cluster synchronizer already reads every active cluster row every 15 seconds. Compare those rows with the published client configuration immediately instead of adding a separate TTL and jitter schedule; unchanged clients remain stable, while failed replacements retain the old client for retry on the next sync.
    @matthewlouisbrockman
    matthewlouisbrockman committed Jul 30, 2026
    Configuration menu
    Copy the full SHA
    38c5dff View commit details
    Browse the repository at this point in the history
Loading