mirror of
https://github.com/haproxy/haproxy.git
synced 2026-07-11 02:02:18 -04:00
09814345d5
Some server setups leak the CGI's stderr into the response body (e.g. inetd-style servers where fd 2 is the client socket): since stderr is unbuffered and stdout is buffered, a git error message then lands *before* the "OK <n>" line, and the applied-count check failed with a cryptic "server applied only ? of N changes" although everything had been applied. Scan the whole response for the lines of interest (the "OK <n>" count, the "conflict" and "warning" lines) instead of assuming they come first, dump the raw response to the console when no count is found at all to ease diagnosis, and display the server's warning lines (such as the new "git commit failed" one) next to the save status so that a recording problem is visible from the page instead of being buried in a server log. |
||
|---|---|---|
| .. | ||
| base64 | ||
| coccinelle | ||
| flags | ||
| gdb | ||
| h2 | ||
| haring | ||
| hpack | ||
| ncpu | ||
| patchbot | ||
| phash | ||
| plug_qdisc | ||
| poll | ||
| qpack | ||
| sslkeylogger | ||
| tcploop | ||
| term_events | ||
| trace | ||
| udp | ||