codex

12,439 Commits 4,703 Branches 1,500 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
Benjamin Carlsson	d13db678cb	Stop applying macOS background priority to managed daemons (#54763 ) ## What changed Launch managed app-server and updater processes directly through the shared background command helper, removing the macOS `taskpolicy -b` wrapper and its availability probe. Remove the associated launch-policy tests and macOS daemon-startup test serialization. Retain the 30-second macOS readiness timeout because older updaters can pass background policy to replacement daemons during upgrades. GitOrigin-RevId: d8620a49139bd2a5c226c624cf7908e06ba7ba38	2026-10-17 02:19:20 +00:00
Benjamin Carlsson	97ebf2d94d	Run managed daemon processes at background priority on macOS (#54401 ) ## What changed - Launch managed processes through `taskpolicy -b` on macOS when a five-second probe succeeds, preserving the managed process PID. Fall back to direct launch if the probe fails or times out. - Increase the macOS startup timeout from 10 to 30 seconds to accommodate background CPU and I/O scheduling, and serialize daemon startup test fixtures on macOS. - Use the shared background command helper and retain `CREATE_NO_WINDOW` alongside Windows detachment flags. ## Testing Add macOS tests for PID preservation, background priority when available, and direct-launch fallback after a probe timeout. GitOrigin-RevId: ab3328e2e8f62218ac9602e4172563c00056875b	2026-10-15 20:00:15 +00:00
Eric Traut	cda82a2c68	Recover daemon startup and updater re-exec after cwd deletion (#49819 ) ## Why Managed daemons and updaters can outlive their launching directory. Restarts and updater replacement need to keep working after that directory is removed. ## What changed - Share working-directory preparation between background launches and Unix updater re-execution. Fall back to the daemon state directory when the Unix working directory is missing, while retaining usable working directories and the existing Windows state-directory behavior. - Preserve configured `CODEX_HOME` paths and valid symlink aliases, and make certificate and AWS environment paths absolute before launching children. Handle both `npm_config_cafile` and `NPM_CONFIG_CAFILE`, preserving supported home-relative values. - Log warnings when scheduled daemon updates fail. ## Testing Add Unix regression coverage for restarting the daemon and updater from a deleted working directory, and for updater re-execution with preserved environment paths, `CODEX_HOME` symlink aliases, and a Linux non-Unicode home path. GitOrigin-RevId: f45aefd8ff060adc6e025badf0bb8c81f842bf88	2026-10-01 02:06:50 +00:00

Author

SHA1

Message

Date

Benjamin Carlsson

d13db678cb

Stop applying macOS background priority to managed daemons (#54763 )

## What changed

Launch managed app-server and updater processes directly through the shared background command helper, removing the macOS `taskpolicy -b` wrapper and its availability probe. Remove the associated launch-policy tests and macOS daemon-startup test serialization.

Retain the 30-second macOS readiness timeout because older updaters can pass background policy to replacement daemons during upgrades.

GitOrigin-RevId: d8620a49139bd2a5c226c624cf7908e06ba7ba38

2026-10-17 02:19:20 +00:00

Benjamin Carlsson

97ebf2d94d

Run managed daemon processes at background priority on macOS (#54401 )

## What changed

- Launch managed processes through `taskpolicy -b` on macOS when a five-second probe succeeds, preserving the managed process PID. Fall back to direct launch if the probe fails or times out.
- Increase the macOS startup timeout from 10 to 30 seconds to accommodate background CPU and I/O scheduling, and serialize daemon startup test fixtures on macOS.
- Use the shared background command helper and retain `CREATE_NO_WINDOW` alongside Windows detachment flags.

## Testing

Add macOS tests for PID preservation, background priority when available, and direct-launch fallback after a probe timeout.

GitOrigin-RevId: ab3328e2e8f62218ac9602e4172563c00056875b

2026-10-15 20:00:15 +00:00

Eric Traut

cda82a2c68

Recover daemon startup and updater re-exec after cwd deletion (#49819 )

## Why

Managed daemons and updaters can outlive their launching directory. Restarts and updater replacement need to keep working after that directory is removed.

## What changed

- Share working-directory preparation between background launches and Unix updater re-execution. Fall back to the daemon state directory when the Unix working directory is missing, while retaining usable working directories and the existing Windows state-directory behavior.
- Preserve configured `CODEX_HOME` paths and valid symlink aliases, and make certificate and AWS environment paths absolute before launching children. Handle both `npm_config_cafile` and `NPM_CONFIG_CAFILE`, preserving supported home-relative values.
- Log warnings when scheduled daemon updates fail.

## Testing

Add Unix regression coverage for restarting the daemon and updater from a deleted working directory, and for updater re-execution with preserved environment paths, `CODEX_HOME` symlink aliases, and a Linux non-Unicode home path.

GitOrigin-RevId: f45aefd8ff060adc6e025badf0bb8c81f842bf88

2026-10-01 02:06:50 +00:00