Files

T

Developer f0ae9483f3 fix: use repository name for workspace mount target

WORKSPACE_NAME was computed from os.path.basename(repo_path), so when a
workspace path ended in a directory like 'main', the container mount target
became /home/user/main instead of /home/user/{repo-name}.

- Use GitRepository.name for WORKSPACE_NAME/REPO_NAME in manifest and
  legacy dockerfile flows
- Add unit test verifying prepare_manifest_instance uses repo.name even
  when the workspace path basename differs

Quality gates:
- pytest tests/unit: 213 passed
- ruff: clean on changed files
- mypy: clean on changed files

2026-06-15 08:54:01 +00:00

805 B

Raw Blame History

apps/api/src/services/tool (index)

dir: apps/api/src/services/tool

role

Manages lifecycle and runtime environment for Docker-based tool execution instances including repository access, configuration, and network connectivity.

parent

index: apps/api/src/services/.pi-map.index.md map: apps/api/src/services/.pi-map.md

children

apps/api/src/services/tool/.ruff_cache index: apps/api/src/services/tool/.ruff_cache/.pi-map.index.md map: apps/api/src/services/tool/.ruff_cache/.pi-map.md

files

instance_service.py

links

index: apps/api/src/services/tool/.pi-map.index.md map: apps/api/src/services/tool/.pi-map.md

workflows

change tool behavior read: instance_service.py
explore tool subdirectories index: apps/api/src/services/tool/.ruff_cache/.pi-map.index.md

805 B Raw Blame History