migrate all time env vars to timedelta

[benedikt-bartscher]

follow-up of #7131

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge. One warning-location bug is non-blocking.

Findings

1.  Generated frames look like users ▶

Summary

Time-based environment variables now use timedelta values with unit suffixes, while old names keep working during migration. Deprecation warnings also skip generated frames so they point to real user code.

• Duration settings accept values such as 2m, while bare numbers still mean seconds.
• Old millisecond and second-based names warn once and suggest their unit-suffixed replacements.
• App, database, websocket, browser, disk-state, and Redis code convert durations for their existing callers.
• Deprecation locations skip <string> and <frozen ...> frames but keep interactive user locations.

_{Reviews (7) · Last reviewed commit: "Fix two review findings on the duration ..."}

[codspeed-hq]

Merging this PR will not alter performance

✅ 40 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing benedikt-bartscher:migrate-envvar-timedelta (58fc137) with main (2f63cb3)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

No issues found across 13 files

_{Re-trigger cubic}

[cubic-dev-ai]

All reported issues were addressed across 10 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[greptile-apps]

This skips only <string> and <frozen ...>. A generated frame such as <attrs generated init reflex.Thing> reaches Path.resolve(), so _get_first_non_framework_frame stops there and reports a fake file. Keep interactive names as user frames, but skip other generated bracketed names. Apply the same fix in log.py.

[cubic-dev-ai]

1 issue found across 10 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/reflex-base/src/reflex_base/utils/console.py">

<violation number="1" location="packages/reflex-base/src/reflex_base/utils/console.py:363">
P2: Skip generated bracketed filenames such as `<attrs generated init reflex.Thing>` before calling `Path.resolve()`, and apply the same predicate in `log.py`. Otherwise deprecation lookup reports the generated pseudo-frame as a fake user file.</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Skip generated bracketed filenames such as <attrs generated init reflex.Thing> before calling Path.resolve(), and apply the same predicate in log.py. Otherwise deprecation lookup reports the generated pseudo-frame as a fake user file.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/reflex-base/src/reflex_base/utils/console.py, line 363:

<comment>Skip generated bracketed filenames such as `<attrs generated init reflex.Thing>` before calling `Path.resolve()`, and apply the same predicate in `log.py`. Otherwise deprecation lookup reports the generated pseudo-frame as a fake user file.</comment>

<file context>
@@ -353,6 +353,15 @@ def _is_framework_filename(filename: str) -> bool:
+    # would depend on where the app was started from. Other bracketed names are
+    # left alone on purpose: `<stdin>` and an `<ipython-input-N-...>` cell are
+    # exactly where an interactive user would look for their own call.
+    if filename == "<string>" or filename.startswith("<frozen "):
+        return True
     frame_path = Path(filename).resolve()
</file context>