You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As currently implemented, the flag name should probably be "client.line-wait",
as it controls max duration between stream.append.entry(), and not duration between send.batch().
Not clear what original intent was.
Either flag name/description should be changed, or implementation changed from
for {
maxWait.Reset(c.cfg.BatchWait)
select {
.
.
.
}
}
to
maxWait.Reset(c.cfg.BatchWait)
for {
select {
.
.
.
case <-maxWait.C:
.
.
.
maxWait.Reset(c.cfg.BatchWait)
}
}
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
A stale issue or PR that will automatically be closed.
label
Sep 3, 2019
As currently implemented, the flag name should probably be "client.line-wait",
as it controls max duration between stream.append.entry(), and not duration between send.batch().
Not clear what original intent was.
Either flag name/description should be changed, or implementation changed from
to
The text was updated successfully, but these errors were encountered: