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

Describe the bug

Will cause ugly failures on named startup.

see master.rs, crates/client/src/serialize/txt/rdata_parsers/null.rs, crates/server/src/store/forwarder/authority.rs

This issue is fairly easy and most beginners should be comfortable implementing algorithms of their choice in Rust. In case of any problem, raise an issue or just discuss below.

Sorting

• Bubble Sort(#1)
• Heap Sort (#27)
• Insertion Sort(#6)
• Quick Sort (#1 )
• Merge Sort ()
• Radix Sort (#47)
• Selection Sort ()
• Shell Sort ()
• Coun

Bug Report

Version

-> % cargo tree | grep tracing
├── tracing v0.1.13
│   ├── tracing-attributes v0.1.7
│   └── tracing-core v0.1.10
├── tracing-futures v0.2.4
│   └── tracing v0.1.13 (*)
├── tracing-log v0.1.1
│   └── tracing-core v0.1.10 (*)
├── tracing-subscriber

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

Maybe relevant to #3.

Cargo.toml should probably have the licence in and inclusion in the root.

I think you want this in Cargo.toml:
license = "GPL-2.0-only"

Perhaps the AUTHORS file from busybox as well.

Great work!

The section titled Building RusytHermit only shows how to build AGAINST the published version of Rusty-Hermit - not how to build libhermit yourself.

I have a crate that has N rust accel functions.

When I rebuild this crate, even if I don't touch those N functions, it seems to trigger N nvptx-accel rebuilds.

Is this avoidable?

I was just about to open a bug about how slow rust-embed was performing in release mode...

... then I found that I was accidentally embedding a 70Mb+ node_modules directory. Oops. (Still, it did seem rather slow for a mere 70MB but maybe that's because it's a lot of small files?)

It would be nice if I could embed some directory, but exclude some large subdirectories from that embed. Ex:

If someone could flesh out the WebPack documentation, that would be amazingly helpful :)
Right now the templates are progressing forward, but require some manual intervention to add the Bulma styling, as well as the FontAwesome resources.

Updates can be done here.
https://github.com/Aardwolf-Social/aardwolf/blob/banjo/More-Documentation-Updates/doc/SETUP-WEBPACK.md

The crate https://crates.io/crates/divans contains a documentation link that is actually a link to a blog post. A link to the API documentation would be useful, too.

Right now we can install dotenv-linter something like this:

# Linux
$ curl https://github.com/mgrachev/dotenv-linter/releases/download/v1.1.2/dotenv-linter-linux-x86_64.tar.gz -sSfL | tar -xzf - 

# Alpine Linux
$ wget https://github.com/mgrachev/dotenv-linter/releases/download/v1.1.2/dotenv-linter-alpine-x86_64.tar.gz -O - -q | tar -xzf -

# macOS
$ curl https://github.com/mgrachev

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

The reference says:

When used on a trait declaration, a call expression of an expression statement to a function that returns an impl trait of that trait violates the unused_must_use lint.

But it also applies to dyn Trait, not just impl Trait.

There should be a derive proc-macro alternative to the macro_rules enum_from_primitive!{..} because it doesn't play well with other such macros like custom_derive!{..}.

I think it would make sense to have it as part of this crate, because it already contains many useful derives for enums.

It's pretty trivial to add documentation attributes to items generated by a procedural macro, especially in Metered's macros where the registry structures are built using the quote! macro. One would simply annotate the structs and fields with a bunch `#[doc = "The doc comes here"] attributes (the strings have to be constructed dynamically before the quote invocation, to make sure it refers to th

I went through the documentation and have not found:

1. how to specify a certain version of Rust compiler?
2. how to enable Rust nightly compiler?
   Thanks!

We have the benchmark example, but it's a poor example, to be honest. We also have no examples of the full spectrum usage: creating the receiver/sinks, logging metrics, setting up an exporter/recorder, etc.

This could be a single-file example, it could be a toy example app in a separate repo under the metrics-rs organization, anything really.