Files
luxe/.config/nextest.toml
Evan Whittaker a0666d6c81 luxe 0.1.4: remembered models, wheel-driven lists, and a steadier phone app
- luxe starts on the model you last chose in this project, then the last one anywhere. Signing in
  opens the model picker instead of choosing for you.
- Every list in a modal takes the mouse wheel and a draggable scrollbar.
- The phone app shows reasoning in full, stays put while you read back through a long session, and
  shows a question's answer on its card.
- On Windows, luxe update replaces the running luxe, and a signed-in install no longer sees setup
  again.
- The file tree no longer shows "engine busy" in a large project, loop output is easier to follow,
  and the name is written lowercase.

The CHANGELOG has the full list.
2026-10-20 13:51:34 -05:00

25 lines
1.3 KiB
TOML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Nextest configuration — https://nexte.st/docs/configuration/
#
# The point of this file is a per-test timeout safety net. luxe's test *execution* is fast
# (~30s for the whole workspace once compiled), but a genuinely hung or runaway test — e.g. a
# process-spawning integration test that never reaps its child, or the historical review-gate
# fork bomb — could otherwise wedge the machine for many minutes. Nextest kills any test that
# exceeds the bound below, so a hang costs seconds, not a lost session.
[profile.default]
# A test running longer than `period` is flagged slow; after `terminate-after` such periods it
# is terminated (SIGTERM, then SIGKILL after `grace-period`). 30s × 4 = a 120s hard cap — an
# order of magnitude above the slowest real test (~11s), so it only ever fires on a true hang.
slow-timeout = { period = "30s", terminate-after = 4, grace-period = "5s" }
# Print failing test output inline and again in the final summary so hangs/flakes are obvious.
failure-output = "immediate-final"
final-status-level = "slow"
# Local runs shouldn't mask flakiness by retrying.
retries = 0
# `cargo nextest run --profile ci` — tighter cap, never fail-fast so one hang can't hide others.
[profile.ci]
slow-timeout = { period = "30s", terminate-after = 3, grace-period = "5s" }
fail-fast = false
failure-output = "immediate-final"