10000 README: fix the reStructuredText formatting. · dotlambda/fluent-logger-python@77f2ac1 · GitHub
[go: up one dir, main page]

Skip to content

Commit 77f2ac1

Browse files
author
Fujimoto Seiji
committed
README: fix the reStructuredText formatting.
* `# hash` is not recognized as a section header. * `_underscore_` does not show a text with italics font style.
1 parent f357a2d commit 77f2ac1

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -348,10 +348,11 @@ or for the python logging interface:
348348
sure the communication thread terminates and it's joined correctly. Otherwise the program won't exit, waiting for
349349
the thread, unless forcibly killed.
350350

351-
#### Circular queue mode
351+
Circular queue mode
352+
+++++++++++++++++++
352353

353354
In some applications it can be especially important to guarantee that the logging process won't block under *any*
354-
circumstance, even when it's logging faster than the sending thread could handle (_backpressure_). In this case it's
355+
circumstance, even when it's logging faster than the sending thread could handle (*backpressure*). In this case it's
355356
possible to enable the `circular queue` mode, by passing `True` in the `queue_circular` parameter of
356357
``asyncsender.FluentSender`` or ``asynchandler.FluentHandler``. By doing so the thread doing the logging won't block
357358
even when the queue is full, the new event will be added to the queue by discarding the oldest one.

0 commit comments

Comments
 (0)
0