rust-lang

Describe the bug

Attempting to view the documentation for an ARM64 instruction results in an unhelpful error message: ‘There was an error fetching the documentation for this opcode ([object Object]).’

Steps to reproduce

0. Visit godbolt.org
1. Select an ARM64 compiler
2. Enter some code
3. In the assembly pane, click on a mnemonic and press Ctrl+F8.

Expected behavior

• Document

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

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

Feature Request

Crates

tracing-subscriber

Motivation

I want to be able to make an extension trait on SubscriberBuilder that offers builder-style configuration of my custom event/field formatters similarly to how it has methods to configure the default formatters. This would allow me to copy the current API so my crate will be familiar to users and easy to adopt. That mea

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!

Leave --help and --version intact for compatibility.

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

Maybe relevant to #3.

In order to fulfill use case for bulk read and write, we need to limit consume when it reaches certain criteria instead of waiting for further inputs. In order to that we should provide 'end` options:

$ fluvio consume my_topic -B --end <offset>

<end_option> is optional. if it is not specified, it would read to current offset at ti