joeduffy b06a708f11 Use Fprint, not Fprintf, so we don't format messages ... I noticed in our Docker builds, we often end up seeing %(MISSING)! style messages, which were an indication we were trying to format them. The reason was the presence of %c's in the stream, and the fact that we passed said messages to Fprintf. We were careful in all other layers to use the message on the "right hand side" of any *f calls, but in this instance, we used Fprintf and passed the message on the "left hand side", triggering formatting. It turns out we've already formatted everything by the time we get here, so there's no need -- we can just use Fprint instead.		2017-10-26 10:30:30 -07:00
..
colors	Rename pulumi-fabric to pulumi	2017-09-21 19:18:21 -07:00
diag.go	Clarify aspects of using the DCO	2017-06-26 14:46:34 -07:00
doc.go	Clarify aspects of using the DCO	2017-06-26 14:46:34 -07:00
pos.go	Clarify aspects of using the DCO	2017-06-26 14:46:34 -07:00
sink.go	Use Fprint, not Fprintf, so we don't format messages	2017-10-26 10:30:30 -07:00
sink_test.go	Improve output formatting	2017-09-23 05:20:11 -07:00