rust-lang

I was trying to use CE to show case address sanitizers

With GCC a typical output might look like

READ of size 4 at 0x7ffdb0b840dc thread T0
    #0 0x4012d2 in main /app/example.cpp:6
    #1 0x7f0f0fc790b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc

As preparation for a possible inclusion into rust-lang we should replace the external actions we use with e.g. scripts that do the same.

rust-lang/std-dev-guide#7 (comment)

That PR also shows how that could be done:
https://github.com/rust-lang/std-dev-guide/pull/7/files

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-core

Motivation

The Collect trait currently has several methods with default implementations that return an Option or some other "empty" or "default" type. In many cases, this isn't because it makes sense for those methods to be optional, but because they were added after v0.1.0 was released and making them mandatory would have been a

Add Windows artifact support in the install script similar to what we will do for Mac OS in #433

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.

When I first set out to study abroad, I knew it would be a life changing experience for me. Along the way I made new friends, tried new foods, and, most importantly: learned new languages.

As a result, I've decided to move on from my English-speaking past. I've successfully converted all of my personal stack to non-English except for one: this application.

My use case is: I use this script t

especially for less obvious but lengthy code snippets!

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

Maybe relevant to #3.

This is specifically for fluvio's modules where we have a CRUD-like interface on the CLI.

• topic
• smartmodule
• connector
• table

The basics we want to cover is:

• Happy path creation, listing, deletion (and describe, update, if those are options)
• Failure path creation and deletion

The strategy is still TBD, but it seems practical to just focus on what we can do with the CLI.
(A