stty: stdin isn't a terminal

[kmayer]

So there a couple of things that are wrong. The first is that I put a comma on the line, because I thought the config file was Ruby and Shell. My bad, perhaps documentation bad? Since comments are prefixed with hashes anyway, include the shebang on line 1 of the example file so we all know what type of file we're dealing with.

The error is because whatever is processing the config file is firing up an interactive shell, somehow.

$ cat mine
sample: test.check "true", "true"
$

{"result": false, "changing": true}

stty: stdin isn't a terminal

[cppforlife]

It's neither ruby or shell. It's the same format as Procfile so having a shebang doesn't really makes sense imho though docs should probably state format more clearly.

'stdin...' error comes from running the actual command with bash -l. In the example you give it would run: bash -lc 'test.check true true'. I haven't really looked at how to prevent that from happening but am open for suggestions.

[kmayer]

Thanks for the response, it helped me narrow things down:

$ cd /Applications/Checkman.app/Contents/Resources
$ bash -lc './test.check true true'  < /dev/null
stty: stdin isn't a terminal
{"result":true,"changing":true}
$ bash -c './test.check true true'  < /dev/null
{"result":true,"changing":true}

So I then dug around,

bash -xlc './test.check true true'  < /dev/null

... and many, many lines later ...

+ source /Users/kmayer/.bash_profile_includes/ctrl-o.sh
++ stty discard undef
stty: stdin isn't a terminal

That's a bug in the ctrl-o.sh script -- it should have a guard against non-interactive shells. (I didn't write it, I think it was provided by http://github.com/pivotal/pivotal_workstation -- but since I work for Pivotal, I can fix it myself).

We can call this bug closed, but this is probably a good wiki entry on how to debug configurations:

---

Debugging tips

If you're Checkman file isn't doing what you expect, or there's unexpected output, you might have a bash profile that is misbehaving.

(This example assumes that your current working directory is /Applications/Checkman.app/Contents/Resources)

$ cd /Applications/Checkman.app/Contents/Resources

Checkman runs a check file like so (in this example, test.check but it could be anything):

$ bash -lc './test.check true true' < /dev/null

The output should be a parseable JSON object:

$ bash -lc './test.check true true' < /dev/null
{"result":true,"changing":true}

But, if you get something weird, e.g.

$ bash -lc './test.check true true'  < /dev/null
stty: stdin isn't a terminal
{"result":true,"changing":true}

Try running the script with the -x option:

$ bash -xlc './test.check true true'  < /dev/null

This will print every line executed by bash (and it could be very, very many lines, depending on the complexity of your environment). Search for the offending text and that should narrow down the problem.

[cppforlife]

I've added debugging section to Readme file with more details: new debugging window and a wiki entry. Thanks for writing up your findings. Looking forward for more feedback =)