Repository navigation
Dangling symlink in the project directory crashes bundling with FileNotFoundError #898
Description
🤖 A dangling symlink anywhere in the project directory makes manifest and bundle creation crash with FileNotFoundError.
Repro
mkdir p && cd p
printf 'from flask import Flask\napp = Flask(__name__)\n' > app.py
echo flask > requirements.txt
ln -s /nonexistent/data.csv data.csv
rsconnect write-manifest api .[ERROR]
Internal error: [Errno 2] No such file or directory: './data.csv'
A common way to hit this is a project .venv whose base interpreter was removed. If the .venv has no pyvenv.cfg, it isn't recognized as a virtual environment, gets walked, and the broken .venv/bin/python link crashes bundling.
Expected
Skip broken symlinks with a warning, or fail with a clear message naming the file. No traceback.
Found during live QA of #892 against Posit Connect. Reproduced on 1.32.0 and current main (0287aca3).
Activity
tdstein commentedon Oct 28, 2026
🤖 Steering for PR #907: the only failing check is
Integration tests against Connect 2024.03.0. In it,tests/test_agent_cli_e2e.py::test_node_preflight_uses_saved_oauth_and_preserves_project_filesfailed withassert 'unknown' == 'ok'on the Node preflightstatus.This looks like a flake, not a regression from the change:
prerelease-test, and every Ubuntu and macOS unit-test job.node/npm, not the Connect version under test.file_checksumraisingRSConnectExceptionfor dangling symlinks) is not on the Node preflight path.To fix:
gh run rerun 40721976651 --failed). If you can't re-run CI, push no code changes and say so in the handoff.preflightJSON output from the log and investigate whystatusisunknownbefore changing anything. Check whethernode/npmresolved differently on that runner.just lintanduv run pytest tests/test_bundle.pystill pass.