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

Error parsing config - v1.1 #43

Closed
grigio opened this issue Jul 18, 2013 · 10 comments
Closed

Error parsing config - v1.1 #43

grigio opened this issue Jul 18, 2013 · 10 comments

Comments

@grigio
Copy link

grigio commented Jul 18, 2013

Hi, I get the error above and the Hosts menu isn't generated.
I tried to clean ssh config and .shuttle.json but it is still there.
How to debug it?

@daften
Copy link

daften commented Jul 19, 2013

When shuttle is launched and there is no .shuttle.json. It is not generated either. I've downloaded an older version atm

@fitztrev
Copy link
Owner

#35 changed when the default config file gets created. It should create it when Shuttle opens. If that's not the case for you, I'll have to look into why.

@daften
Copy link

daften commented Jul 19, 2013

If I can create a debug log, please let me know (how) :)

@grigio
Copy link
Author

grigio commented Jul 19, 2013

@fitztrev I removed both and I see no errors and no items.
If I re-enable my ssh config (or even an empty one) I get the parsing error again

@mjbaldwin
Copy link

I just downloaded it and got the same parsing error. The problem is multiple "_comment" keys. If you delete the second and third ones, it works. Or just change them to "_comment2", "_comment3". Obviously, JSON can't have multiple identical keys in the same object.

@thoro
Copy link
Contributor

thoro commented Jul 21, 2013

Weird, because I don't get these errors, even with the identical keys! Maybe something else?

@grigio
Copy link
Author

grigio commented Jul 21, 2013

@mjbaldwin good sight! Yeah it fix the parsing. thanks

@mjbaldwin
Copy link

In case it matters, I'm on OSX 10.7.5. Downloaded Shuttle yesterday.

@jayhealey
Copy link

I encountered the same problem after download this morning.

@mjbaldwin's fix works perfectly.

Removing the duplicate "_comment" lines fixed it

@thoro
Copy link
Contributor

thoro commented Jul 22, 2013

I'm on OSX 10.8.4, here it seems irrelevant. Maybe #44 should be added, at least it won't confuse anyone then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants