Orchestration skips session creation without error output

[derschatta]

Hey,
I've tried to use the new orchestration feature without success.
I set up a basic mutagen.yml file:

sync:
  totara:
    alpha: "/path/to/my/local/src"
    beta: "docker://totara_sync/path/to/my/remote/src"
    ignore:
      vcs: true
      paths:
        - ".idea"
        - .DS_Store
    symlink:
      mode: ignore
    permissions:
      defaultFileMode: 0644
      defaultDirectoryMode: 0755

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:

⇒  mutagen project list        
Forwarding sessions:
--------------------------------------------------------------------------------
No sessions found
--------------------------------------------------------------------------------

Synchronization sessions:
--------------------------------------------------------------------------------
No sessions found
--------------------------------------------------------------------------------

Sync list is empty too

⇒  mutagen sync list           
--------------------------------------------------------------------------------
No sessions found
--------------------------------------------------------------------------------

If I try starting it again I get

⇒  mutagen project start    
Error: project already running

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

[xenoscopic]

@derschatta Thanks for the report, that's an odd one. Are you able to create the equivalent synchronization session manually with mutagen sync create? That might give more information about any error that's occurring, but I'm surprised that it wasn't printed out by the mutagen project start command.

[derschatta]

Yes I was able to create a sync session manually using the same mutagen.yml file without the 'alpha' and 'beta' specified in it.

[derschatta]

No errors or any other indicators why it's not working with mutagen sync create

[xenoscopic]

Yes I was able to create a sync session manually using the same mutagen.yml file without the 'alpha' and 'beta' specified in it.

Just to make sure we're on the same page, can you clarify what you mean by using the same mutagen.yml file without the alpha/beta keys. Do you mean that you used an equivalent YAML configuration file with session defaults, e.g. in ~/.mutagen.yml or with the -c/--configuration-file flag?

Does it work if you use mutagen project terminate and then run mutagen project start again? Or is it reproducible?

[derschatta]

If I run mutagen sync create in the same folder as a mutagen.yml file containing the configuration the command uses that file automatically, right? That's what I did.

Same goes for project start. If I run mutagen project start it should use the mutagen.yml file in the folder I run the command in.

File for manual sync create I used:

sync:
  defaults:
    ignore:
      vcs: true
      paths:
        - ".idea"
        - .DS_Store
    symlink:
      mode: ignore
    permissions:
      defaultFileMode: 0644
      defaultDirectoryMode: 0755

compared to the one in the issue description I've tried for project start.

[derschatta]

Does it work if you use mutagen project terminate and then run mutagen project start again? Or is it reproducible?

Yes, it is reproducable. running terminate and start does not change anything, project is still not started.

[xenoscopic]

If I run mutagen sync create in the same folder as a mutagen.yml file containing the configuration the command uses that file automatically, right? That's what I did.

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 ~/.mutagen.yml. A mutagen.yml file in the current directory (even one with defaults specified) is only used by the mutagen project commands. This behavior probably ought to change. The idea with mutagen.yml files is that they're supposed to be self-contained descriptions of the configuration for a project, but it might make sense to pull defaults values out of them as well. Perhaps it would have been better to name these something like mutagen-project.yml. Because I can easily see how this is very unintuitive.

Same goes for project start. If I run mutagen project start it should use the mutagen.yml file in the folder I run the command in.

That's correct, mutagen project start will use these files.

Yes, it is reproducable. running terminate and start does not change anything, project is still not started.

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:

• If you run mutagen project terminate, and then run mutagen project start, can you tell me the exit code for the latter command (i.e. $?)?
• What does mutagen version print?
• Does running mutagen daemon stop/mutagen daemon start (and then retrying mutagen project start) help?
• What shell are you using?

[derschatta]

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 ~/.mutagen.yml. A mutagen.yml file in the current directory (even one with defaults specified) is only used by the mutagen project commands. This behavior probably ought to change. The idea with mutagen.yml files is that they're supposed to be self-contained descriptions of the configuration for a project, but it might make sense to pull defaults values out of them as well. Perhaps it would have been better to name these something like mutagen-project.yml. Because I can easily see how this is very unintuitive.

Ok, well, I set it up using the -c param anyway.

If you run mutagen project terminate, and then run mutagen project start, can you tell me the exit code for the latter command (i.e. $?)?

code is 0.

What does mutagen version print?

0.10.0

Does running mutagen daemon stop/mutagen daemon start (and then retrying mutagen project start) help?

Nope.

What shell are you using?

ZSH