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

Binary FBX starting from 7500 version has different size of null-record - 25 null bytes instead of 13 in previous versions, this should be taken into account when loading binary FBX. Binary FBX of version 7500 can be produced by exporting any model from Blender. Also it has u64 end_offset, num_attrib, attrib_list_len in header of node instead of u32 for previous versions.
Starting point: `f

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

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

Maybe relevant to #3.

Example:

# .env
test

Actual behavior:

If we run dotenv-linter against a .env file with the test key, we will see only one warning:

$ dotenv-linter .env
Checking .env
.env:1 KeyWithoutValue: The test key should be with a value or have an equal sign

Found 1 problem

If we fix that file and run check again, we will see another warning:

$ 

Change all Widgets so they use the inverse color selected state, if applicable.