2.5 is not the easiest section to follow. I can't exactly describe what, but more information and examples overall could help.

What happened

Accidentally omitting document content returns 500 Internal Server Error with a body of {"message":"Internal error","uri":"/new_index"}

What was expected

Emitting any kind of helpful message would be helpful. Also, in my experience, when the client receives a 500 response, there is usually something informative on the server-side. But in this case, the server e

Feature Request

Crates

tracing::instrument

Motivation

The tracing::instrument proc macro is incredibly useful, and the docs encourage users to use it, as well as set a level. Not all users read documentation, so many use defaults. (Like me)

By default, they seem to decorate at all logging levels, which can impact performance for users in unexpected ways.

We met thi

The app should wake up the screens when it switches inputs under Linux, the same as it does under Windows and MacOS, e.g. implement wake_displays.

https://github.com/magnet/metered-rs

Maybe relevant to #3.

In cases where a variable is used, the linter should not complain if it is not listed alphabetically.

This is correct:

FOO=something
BAR="$FOO or other"

This is NOT correct:

BAR="$FOO or other"
FOO=something

Workaround:

• Add a comment

FOO=something

# BAR uses FOO
BAR="$FOO or other"

"getting started" section should work on windows 10 wsl2. but I have no machine for the verification temporarily...