More specific JSON errors about awe

[wtangiit]

This fails at json unmarshal. The workflow doc parsing functionality are
relying on the json unmarshal function in the standard Go library
(encoding/json) to convert the json stream to a Go struct, and the error
msg is reported by that library function. I think it is not easy for now to
report finer-grained error msg if we are using the standard Go library .

Thus for now, we have to make sure the job template follows the json
specification in the document. On the roadmap, we will have better workflow
parsing framework, that will have better workflow checking and debug
capability.

On Tue, Jun 10, 2014 at 3:28 PM, MrCreosote [email protected]
wrote:

Would it be possible to give the location of the error in the JSON when
JSON parse errors occur? For example:

crusherofheads@icrushdeheads:~/awe_sec$ curl -X POST -F
[email protected] http://localhost:7080/job
{"status":400,"data":null,"error":["json: cannot unmarshal number into Go
value of type string"]}

That's really hard to debug. In this case it turns out that the depends
fields in tasks must be strings, not numbers, which was the cause of the
error.

—
Reply to this email directly or view it on GitHub
#236.

[wgerlach]

This is a known issue in Go, see https://code.google.com/p/go/issues/detail?id=6716