anchor.diff:  is why this debugging feature should only be activated in a controlled manner, as a last
   resort.
   
  +[[checkpoint-alternative]]
   === The `checkpoint()` Alternative
   
   The debug mode is global and affects every single operator assembled into a `Flux` or a
  
positive.code: NOTE: When both global debugging and local `checkpoint()` are enabled, checkpointed
  snapshot stacks are appended as suppressed error output after the observing operator
  graph and following the same declarative order.
  
  == Logging a Sequence
  
  
negative.code: [[debug-activate]]
  == Activating Debug Mode
  
  WARNING: this section describes the easiest but also the slowest way to enable
  the debugging capabitilies due to the fact that it captures the stacktrace on every operator.
  See <<checkpoint-alternative>> for a more fine grained way of debugging,
  and <<reactor-tools-debug>> for a more advanced and performant global option.
  
  Even though the stacktrace was still able to convey some information for someone with a
  bit of experience, we can see that it is not ideal by itself in more advanced cases.
  
  