Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make daemons working dir configurable #555

Closed

Conversation

Gege-Wang
Copy link
Collaborator

@Gege-Wang Gege-Wang commented Jun 14, 2024

This PR is for multiple-daemons:

  • path check. for a dataflow, if the number of machine > 1, skip all path exist check.

  • working_dir is configurable in cli, (the default value is "."), so the relative path is allowed again, like:
    dora daemon --machine-id A --working-dir examples/rust-dataflow

  • for local and remote, the working_dir is default "." or specified, not the directory of dataflow.yml. so dora up are also changed, if there are some dataflow running in one daemon(maybe it is inconvenient I think)
    dora up --working-dir examples/rust-dataflow

  • the dynamic node need directory same as dataflow(not sure), so there need more attention.

follow #535

@Gege-Wang Gege-Wang marked this pull request as ready for review June 19, 2024 09:13
Copy link
Collaborator

@haixuanTao haixuanTao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this adding a breaking change or not for local machine ? I'm not sure 🤔

.ok_or_else(|| eyre::eyre!("canonicalized dataflow path has no parent"))?
.to_owned();
pub async fn run_dataflow(dataflow_path: &Path, working_dir: PathBuf) -> eyre::Result<()> {
// let working_dir = dataflow_path
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't leave commented code within the codebase.

@@ -2281,6 +2281,7 @@ name = "dora-coordinator"
version = "0.3.4"
dependencies = [
"ctrlc",
"dirs 5.0.1",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still necessary?

@Gege-Wang Gege-Wang closed this Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants