-
Notifications
You must be signed in to change notification settings - Fork 151
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
Orchestration skips session creation without error output #127
Comments
@derschatta Thanks for the report, that's an odd one. Are you able to create the equivalent synchronization session manually with |
Yes I was able to create a sync session manually using the same mutagen.yml file without the 'alpha' and 'beta' specified in it. |
No errors or any other indicators why it's not working with |
Just to make sure we're on the same page, can you clarify what you mean by using the same Does it work if you use |
If I run Same goes for project start. If I run File for manual sync create I used:
compared to the one in the issue description I've tried for project start. |
Yes, it is reproducable. running terminate and start does not change anything, project is still not started. |
Not at the moment. This is my fault for not explaining this particularly well in the documentation. So the only configuration file that's pulled in by default is
That's correct,
It's strange that there's absolutely no output. I guess this'll need some debugging. If it's not too much trouble, can you tell me the following:
|
Ok, well, I set it up using the -c param anyway.
code is 0.
0.10.0
Nope.
ZSH |
Hey,
I've tried to use the new orchestration feature without success.
I set up a basic mutagen.yml file:
and tried starting the project from the folder where I've put the mutagen.yml file with
mutagen project start
No error or success output. The session did not get started:
Sync list is empty too
If I try starting it again I get
So apparently something is running but no showing?
Happy to give you any more information you need.
Running MacOS 10.14.5, Docker 2.1.0.0
The text was updated successfully, but these errors were encountered: