https://github.com/ryanmcdermott/clean-code-javascript#dont-add-unneeded-context
Not so good:

const Car = {
  make: 'Honda',
  model: 'Accord',
  color: 'Blue'
};

function paintCar(car) {
  car.color = 'Red';
} 

// paintCar for a function name is redundant here and a simple paint(car) seems more intuitive.
Better:

const Car = {
  make: 'Honda',
  model: 'Acc

A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

I created this meta issue to track missing documentation. I added [x] even
thought documentation might not be complete. This point is just to make easier
to people to find what module needs documentation, so they can easier contribute
to documentation.

If you want to contribute to documentation there is snippet template,
M-x -> yas-snippet-insert ->Doom module readme
Or in org-mode you ca

Since Trax is a successor of tensor2tensor (according to the release notes of tensor2tensor v1.15.0), it would be helpful if you could provide examples for more advanced machine learning tasks. An outstanding feature of tensor2tensor are the numerous (and useful) examples which Trax is currently lacking. Such examples would especi

The API doesn't seem to be removing all tags when an article's tagList is an empty array.
Sending an array with an empty string properly removes all the tags.

Bug report

Describe the bug

Here is a clear and concise description of what the problem is:

Is it possible to implement tensorboard to monitoring the training sessions?

Description

Currently, setting coordinates in Z_STEPPER_ALIGN_XY that cannot be reached by the probe (due to a probe offset, for example) compiles successfully but fails during G32.

I'm suggesting adding a sanity check to make sure Z_STEPPER_ALIGN_XY is valid for the currently set bed size and probe offset.

It would be great to have an option for a module to not be auto started when then the "Setup" button is pressed on the Dreamview page. This flag could be given in the HMI.