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

File Sync agent is disabled by default #3071

Closed
wtrocki opened this issue Nov 14, 2016 · 6 comments
Closed

File Sync agent is disabled by default #3071

wtrocki opened this issue Nov 14, 2016 · 6 comments
Assignees
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@wtrocki
Copy link

wtrocki commented Nov 14, 2016

Background

che mount command would fail if File Sync agent would be disabled.
It looks for me that by default all workspaces having Unison File Synchronizer option disabled.
If users wish to use file sync they need to enable it in workspace options.

screen shot 2016-11-14 at 9 52 55 pm

This information is missing from in documentation:
https://eclipse-che.readme.io/docs/desktop-ide-mounting

Required actions

Steps to reproduce

  1. Create default java workspace ( File Sync disabled)
  2. Try to sync it localy using guide: https://eclipse-che.readme.io/docs/desktop-ide-mounting
  3. che mount command returns no results - file sync failed.

My setup

Che version: master (ebe8ed9)
OS and version: MacOs X El Capitan
Docker version: Docker version 1.12.3, build 6b644ec
Che install: [command line/source code]

@wtrocki wtrocki changed the title [Docs] File Sync agent is disabled by default File Sync agent is disabled by default Nov 14, 2016
@TylerJewell
Copy link

Hi! So it should be the scenario where the sync agent is optional not required. If you do not have the sync agent sync does occur but the initial sync is a lot slower. If the sync utility is failing anyways then that is an outright bug for investigation.

The extra sync agent just makes sync faster and therefore disabled by default.

@TylerJewell
Copy link

@benoitf - FYI.

@wtrocki
Copy link
Author

wtrocki commented Nov 14, 2016

I did investigation why sync wasn't executed and it looks like

che action list-workspaces

returns no results on my machine. I have 2 workspaces with projects and sync enabled. Swagger api returns them properly. This feels like issue but it also could be something with my local setup.
I think that would be awesome if command line client would return some results in this case.

Quote from docs:

You can get a list of workspaces in a Che server that have an SSH agent deployed and are also a dev-machine where /projects are deployed. This means it is sync-ready.

What are also a dev-machine where /projects are deployed. means in this context?

@TylerJewell
Copy link

Before @benoitf investigates - can you confirm that you had the SSH agent deployed? While the sync agent is not required, the SSH agent is required. So when we do a list workspaces, we should list all workspaces and then give you a table of which workspaces have machines with the SSH agent deployed inside of it.

@TylerJewell TylerJewell added the kind/question Questions that haven't been identified as being feature requests or bugs. label Nov 15, 2016
@benoitf
Copy link
Contributor

benoitf commented Nov 15, 2016

hello @wtrocki
based on your information, you said you're using master with
ebe8ed9
which is 5.0.0-M6

new updates on che mount are on 5.0.0-M7. Also che.sh was defaulting to 4.7(latest) tag so I guess that it's why it's returning nothing

could you try

$ export CHE_UTILITY_VERSION="nightly"
$ che action list-workspaces

@wtrocki
Copy link
Author

wtrocki commented Nov 15, 2016

It works now. Closing as invalid. Sorry for troubles. Moving my local dev to 5.0.0 release tag.

@wtrocki wtrocki closed this as completed Nov 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.
Projects
None yet
Development

No branches or pull requests

3 participants