You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Paul Banks de58eb1820 Fixes #3891: agent monitor no longer unresponsive before logs stream. ... The root cause is actually that the agent's streaming HTTP API didn't flush until the first log line was found which commonly was pretty soon since the default level is INFO. In cases where there were no logs immediately due to level for instance, the client gets stuck in the HTTP code waiting on a response packet from the server before we enter the loop that checks the shutdown channel from the signal handler. This fix flushes the initial status immediately on the streaming endpoint which lets the client code get into it's expected state where it's listening for shutdown or log lines.		7 years ago
..
agent	…
catalog	remove golint warnings	7 years ago
event	…
exec	…
flags	Pull http config flag merge into public method	7 years ago
forceleave	…
info	…
join	…
keygen	…
keyring	…
kv	Adds -base64 support to kv get command.	7 years ago
leave	…
lock	…
maint	…
members	…
monitor	Fixes #3891: agent monitor no longer unresponsive before logs stream.	7 years ago
operator	Fix typo	7 years ago
reload	…
rtt	remove golint warnings	7 years ago
snapshot	…
validate	…
version	…
watch	…
commands_oss.go	…
registry.go	…