Skip to content

Build process has hardcoded developers home path into binary #49

@mjclarke94

Description

@mjclarke94

@jessie-young

Hey,

I just tried to use this tool to spin up a ray cluster but ran into this issue:

 uv run daft provisioned up
Error: TOML parse error at line 1, column 1
  |
1 | [setup]
  | ^^^^^^^
The path, "/Users/jessieyoung/.ssh/keys/daft/daft-key", does not exist

Did a quick scan of the repo itself and couldn't find your home directory hardcoded in anywhere, and found that the issue went away if I reinstalled without using the binary:

uv add daft-cli --no-binary-package daft-cli --reinstall-package daft-cli

My best guess is that the build was run on your local machine and that somewhere a path is getting set as a const at build time. I've not been able to hunt it down but strings daft | fgrep "/Users/jessieyoung/" shows a lot of build artifacts in addition to consts containing that string.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions