fbefa05d48
- Switch to our own simpler token bucket, since x/time/rate is missing necessary stuff (can't provide your own time func; can't check the current bucket contents) and it's overkill anyway. - Add tests that actually include advancing time. - Don't remove the rate limit on a message until there's enough room to print at least two more of them. When we do, we'll also print how many we dropped, as a contextual reminder that some were previously lost. (This is more like how the Linux kernel does it.) - Reformat the [RATE LIMITED] messages to be shorter, and to not corrupt original message. Instead, we print the message, then print its format string. - Use %q instead of \"%s\", for more accurate parsing later, if the format string contained quotes. Fixes #1772 Signed-off-by: Avery Pennarun <apenwarr@tailscale.com> |
||
|---|---|---|
| .. | ||
| empty | ||
| flagtype | ||
| ipproto | ||
| key | ||
| logger | ||
| netmap | ||
| nettype | ||
| opt | ||
| pad32 | ||
| persist | ||
| preftype | ||
| strbuilder | ||
| structs | ||
| wgkey | ||