-
Notifications
You must be signed in to change notification settings - Fork 97
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
Refuse relative path for remote in coordinator #538
Conversation
@Gege-Wang please help me check it in remote daemon |
@XxChang Hi, I think the machine who executes |
So this work on aws EC2 right? And now you should be able to spawn multiple-daemon example without using the same folder structure right? |
Good point! @XxChang Could you add an additional check in |
Sure, but if we do that. The "coordinator_addr" optional flag in |
I meant as a requirement for absolute paths. Relative paths should be only allowed if the CLI, the coordinator, and the daemon(s) are all on the same machine. So you can still use |
Add additional check in Also modify the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Thanks! Looks very good!
Maybe i will let Philipp have a look and merge it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates and thanks for finding a way to free up enough space on CI!
I left one suggestion, otherwise this looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Only allow absolute path for remote daemon in coordinator,
modified from #534
See option 2 in #535