Text format parser ignoring EOF format error

[zeroware]

I wrote a custom exporter and forgot to add a line return \n at the end of the file.
Prometheus displayed that my target was healthy but my metrics were not parsed.

This is low priority but we should have some kind of error message.

Note : previous versions of prometheus returned an EOF error.

[fabxc]

That is probably caused by the new decoder, which in theory supports
streaming. EOF is a signal that the stream is done.
If it happens while parsing a metric, I think the underlying parser should
explicitly state that it is a premature EOF.

On Fri, Oct 2, 2015, 8:24 AM Zero notifications@github.com wrote:

I wrote a custom exporter and forgot to add a line return \n at the end
of the file.
Prometheus displayed that my target was healthy but my metrics were not
parsed.

This is low priority but we should have some kind of error message.

Note : previous versions of prometheus returned an EOF error.

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

[beorn7]

Needs updated vendoring to take effect in head.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.