IronMurphy 05297813ae

fix(lark): publish the CLI runtime files atomically (#6618) ...

* fix(lark): publish the CLI runtime files atomically

install_shim wrote the shim, the launcher and the runtime marker with a
truncating open. The sandbox chmods the launcher 0o755 and execs it, so a crash
mid-write left an executable fragment, and the marker is parsed as JSON. Publish
through a temporary file plus os.replace, as the storage backends already do.

* style: drop the unused import ruff flags

* fix(lark): publish runtime permissions atomically

Set file permissions on temporary files before os.replace() to ensure
the launcher, shim, and runtime marker are atomically published with
correct permissions (0o755 for executables, 0o644 for the marker).

This addresses reviewer feedback from PR #6591:
- Permissions are now set before the atomic replace operation
- Prevents brief window where files have incorrect permissions
- The runtime marker now has mode 0o644 instead of 0600 (mkstemp default)

Also updates test_lark_shim_atomic.py:
- Fixes test_atomic_helper to match new function signature
- Adds test_install_shim_publishes_correct_permissions to verify
  launcher/shim (0o755) and marker (0o644) permissions

Co-authored-by: IronMurphy <hepushuo@gmail.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>

2026-10-11 08:17:14 +08:00

..

__init__.py

feat: add Lark CLI integration (#3971)

2026-07-26 08:09:17 +08:00

lark_broker.py

fix(lark): publish the CLI runtime files atomically (#6618)

2026-10-11 08:17:14 +08:00

lark_cli.py

fix(integrations): decode lark-cli and npm output as UTF-8 (#6590)

2026-10-10 14:28:10 +08:00