gae123 / sd2 Goto Github PK

Version 0.14.1 shuts down with WARNING MAIN:LOOP:EX 'config' if there is no config key in config.yaml. Expected result was the config to include default values from the schema but it appears not to be working properly. Will investigate further and update this issue with findings and possibly a PR

It appears that when a new file is created in a new directory, sd2 notices the change and tries to use scp to copy the file to the remote server. However since the directory is new too it doesn't yet exist on the server and the scp command fails. It can then takes several minutes before the rsync command runs and does a full sync of the directory/files.

It would be nice if sd2 could notice when the scp command files, and do an immediate 'rsync'. Or maybe wait a couple of seconds in case there is a flurry of file changes (e.g. what happens when you do a 'git pull').

I created a config.yaml that had a tab character in it, which the yaml parser doesn't like:

yaml.scanner.ScannerError: while scanning for the next token
found character '\t' that cannot start any token
  in "<unicode string>", line 37, column 1:
    	enabled: true
    ^

When I saved this file, the sd2 daemon process immediately died. The only in the logs that I could find was this:

2018-09-20 14:42:35 44097 INFO     SD2INIT:EE

It was only by running sd2 again that I found out what the problem was.

Steps to reproduce:

• In your editing host (own workspace) remove a folder that is supposed to be RSYNCed. In my case it was the .kube folder.

• After sd2 is running and the containers on the development machine are up and running, kill a container

• According to the logs an RSYNC for the missing directory fails, and the development host is eventually marked as unhealthy, causing sd2 to skip checks for docker.