-
Notifications
You must be signed in to change notification settings - Fork 23
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
Getting confused with syntax and versions #31
Comments
Hello, I have no idea right now why there would be a difference about the "commands" definition inside the configuration (at first glance, it looks fine with your example). I would suggest to use 1.0.6 (available again). |
Yes I changed my post after I discovered it. 1.0.6 Was not visible but after I logged in and went to releases I found it. |
Correct, this is a new field only in 1.0.6 (i thought the problem was with commands). |
Well it is both then, if AvoidDualUDPSending is used with 1.0.5 (which the sol.json suggests) then the commands don't work properly. In fact only the sleep command is functional. |
Yes, i fully understand now : because of the extra (unknown) configuration field while running 1.0.5, the loading configuration was failing - after that, the program was still pursuing its execution, but with default values (sleep command is configured as a default one). Hence the behavior you spotted. I'll get it corrected (by stopping the program in case of any configuration errors, it's way safer / nicer this way). |
Closing as this is now corrected through #32 + 1.0.7-SNAPSHOT |
I have downloaded the 1.0.6 snapshot version here a couple of weeks ago.
But now I don't understand this:
sol.json:
works fine with what presumably is the 1.0.6 Version (11MB filesize, date Oct 17)
If I use it on 1.0.5 only the sleep command would be functional. For the rest I get "not found" errors.
Any explanation for that?
I can't find any syntax issues.
I have to add: If I leave
out, it works with 1.0.5
But this section is part of the 1.0.5 sol.json
The text was updated successfully, but these errors were encountered: