sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Segfault when profiling with_stack=True on model with jit.optimize_for_inference
Labels: oncall: jit

### 🐛 Describe the bug

The Python process segfaults whenever I run the pytorch profiler using with_stack=True on a model that has had torch.jit.optimize_for_inference() called on it. 

```python
import torch
import torchvision.models as models
from torch.profiler import profile, record_function, ProfilerActivity
model = models.resnet18().cuda()
inputs = torch.randn(5, 3, 224, 224).cuda()
model = torch.jit.script(model)
model = torch.jit.optimize_for_inference(model)

with profile(activities=[ProfilerActivity.CPU], with_stack=True) as prof:
    model(inputs)
```

```
Segmentation fault (core dumped)
```

The .crash file in /var/crash is 605MB and this should be easy to reproduce, so I haven't attached that, but let me know if there's anything else you need.

### Versions

Collecting environment information...
PyTorch version: 1.12.1+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.8.5 (default, Jul 28 2020, 12:59:40)  [GCC 9.3.0] (64-bit runtime)
Python platform: Linux-5.4.0-47-generic-x86_64-with-glibc2.29
Is CUDA available: True
CUDA runtime version: 10.2.89
GPU models and configuration:
GPU 0: NVIDIA GeForce RTX 2080 Ti
GPU 1: NVIDIA GeForce RTX 2080 Ti
GPU 2: NVIDIA GeForce RTX 2080 Ti
GPU 3: NVIDIA GeForce RTX 2080 Ti
GPU 4: NVIDIA GeForce RTX 2080 Ti
GPU 5: NVIDIA GeForce RTX 2080 Ti
GPU 6: NVIDIA GeForce RTX 2080 Ti
GPU 7: NVIDIA GeForce RTX 2080 Ti

Nvidia driver version: 510.73.05
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.0.4
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.0.4
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.2
[pip3] torch==1.12.1
[pip3] torchvision==0.13.1
[conda] Could not collect
Repository: go
Issue: x/sys/unix: KeyctlString() panics for key types that can legally contain "no payload at all
Labels: compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fhofmann/.cache/go-build"
GOENV="/home/fhofmann/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/fhofmann/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/fhofmann/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/fhofmann/build/KRN/key-play/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3959267050=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

https://go.dev/play/p/60ZtM3V4_Io

This program needs to run on Linux - and not in a dev/play container (where the `keyctl` syscall is masked).
On a VM, it panics thus:
<pre>
$ ./main 
panic: runtime error: slice bounds out of range [:-1]

goroutine 1 [running]:
golang.org/x/sys/unix.KeyctlString(0x49aa72?, 0x40bcdd?)
	/home/fhofmann/go/pkg/mod/golang.org/x/sys@v0.0.0-20220808155132-1c4a2a72c664/unix/syscall_linux.go:1399 +0xb8
main.main()
	/home/fhofmann/build/KRN/key-play/main.go:18 +0xc5
</pre>

This is because `unix.KeyctlString()` _assumes_ key lengths are _always_ > 0 (and it can "strip the trailing null byte") at the very least. But It is possible for certain key types (keyrings, notably) to be "legally empty", and a `unix.KeyctlBuffer()` on these _will_ correctly return zero for the length..


### What did you expect to see?

Not panic.
Return`"", nil` (zero-length content, no error). This would be trivially achievable by changing https://github.com/golang/sys/blob/master/unix/syscall_linux.go#L1392,
```
if err != nil {
        return "", err
}
```
into:
```
if err != nil || length == 0 {
...
```

### What did you see instead?

Panic in go standard lib. Completely unnecessary.
Repository: node
Issue: `fs.copyFile` fails if source is readonly and target is a WSL volume
Labels: fs

### Version

v18.7.0

### Platform

Linux 774484ed2c79 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 Linux

### Subsystem

fs

### What steps will reproduce the bug?

- Command Prompt
```sh
docker run --rm -it ^
-e "CODE=require('fs').copyFileSync('/tmp/file', '/target/file')" ^
-v "%TEMP%:/target" ^
node:alpine ^
sh -c "touch /tmp/file && chmod -w /tmp/file && node -e 'eval(process.env.CODE)'"
```

- Git Bash
```sh
docker run --rm -it \
-e "CODE=require('fs').copyFileSync('/tmp/file', '/target/file')" \
-v "$TEMP:/target" \
node:alpine \
sh -c "touch /tmp/file && chmod -w /tmp/file && node -e 'eval(process.env.CODE)'"
```

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior?

No error.

### What do you see instead?

```
node:internal/fs/utils:348
    throw err;
    ^

Error: EACCES: permission denied, copyfile '/tmp/file' -> '/target/file'
    at Object.copyFileSync (node:fs:2866:3)
    at eval (eval at <anonymous> ([eval]:1:1), <anonymous>:1:15)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:76:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:75:60)
    at node:internal/main/eval_string:27:3 {
  errno: -13,
  syscall: 'copyfile',
  code: 'EACCES',
  path: '/tmp/file',
  dest: '/target/file'
}
```

### Additional information

- https://github.com/nodejs/node/issues/37284
Repository: pytorch
Issue: Speedup for adding images to tensorboard
Labels: oncall: visualization

### 🚀 The feature, motivation and pitch

This is my first contribution to pytorch, i will try to follow all protocols but please tell me if i am doing something wrong.
### The motivation
Adding very big matplotlib figures is slow due to unnecessary casting and scaling, this can be sped up significantly. 

 ### The concrete problem
I create big figures using matplotlib in a training callback after each epoch. I would like to add these figures to tensorboard. The add_figure method currently basically renders the image as a figure and then adds it as an image. 

https://github.com/pytorch/pytorch/blob/822a8e057fa4e6a6a8413d22bae2c1a5aa853134/torch/utils/tensorboard/writer.py#L748-L754

The method add_image creates a serialized summary and adds it to the file writer. 
https://github.com/pytorch/pytorch/blob/822a8e057fa4e6a6a8413d22bae2c1a5aa853134/torch/utils/tensorboard/writer.py#L614-L616

The creation of the image summary has these lines, where the image is casted to float, multiplied by a scale factor (either 255 or 1) and casted back to uint8. In my case the "tensor" is already an ndarray with type uint8, so the cast to float, multiplication and cast back to uint8 is unnecessary. 
https://github.com/pytorch/pytorch/blob/822a8e057fa4e6a6a8413d22bae2c1a5aa853134/torch/utils/tensorboard/summary.py#L443-L446


I'm very confident that these lines cause my speed problem . I localized them via printf debugging, then inserted condition (as shown below) and now it works much faster.


### Proposed solution 
Add a condition whether the cast-scale-cast-back is necessary, something to the effect of: 
```python
if tensor.dtype != np.uint8 or scale_factor != 1.0:
        tensor = tensor.astype(np.float32)
        tensor = (tensor * scale_factor).astype(np.uint8)
```





### Alternatives
I have considered ignoring the problem since it is only on epoch end anyway, but especially in debugging it can be very annoying when adding an image to tensorboard takes that long.

### Additional context

_No response_
Repository: react-native
Issue: [TextInput] input cannot be controlled
Labels: Issue: Author Provided Repro,Component: TextInput,Needs: Triage :mag:,Never gets stale

### Description

`TextInput` value cannot be controlled. Given the following JSX, I expected that typing in the input would do nothing to match behaviour on web:

```jsx
<TextInput value="" />
```

## Actual behaviour

The value typed by the user flickers on screen before being removed.

https://user-images.githubusercontent.com/175330/185148394-c13e74b7-1319-4948-ae1c-38968a651aa7.MP4

### Version

0.70.0-rc.2

### Output of `npx react-native info`

System:
    OS: macOS 12.5
    CPU: (10) arm64 Apple M1 Max
    Memory: 108.61 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.7.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 8.15.0 - /usr/local/bin/npm
    Watchman: 2022.08.15.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8815526
    Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.16 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

- Open snack at https://snack.expo.dev/YtYVsPnOU
- Click iOS (or Android, although it's more intermittent there) 
- Type in the input and note that your value flickers in before being removed

### Snack, code example, screenshot, or link to a repository

https://snack.expo.dev/YtYVsPnOU
Repository: rust
Issue: Reference to `std::fmt::Debug` not using full path in "multiple applicable items in scope" error
Labels: A-diagnostics,T-compiler,D-invalid-suggestion

Given the following code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=970c9bebd80f042e27af0cdfb3309579

```rust
#![allow(unused_imports, unreachable_code)]
use std::fmt::{Debug as _, Display as _};

fn main() {
    0u32.fmt(todo!());
}
```

The current output is:

```
Compiling playground v0.0.1 (/playground)
error[E0034]: multiple applicable items in scope
 --> src/main.rs:5:10
  |
5 |     0u32.fmt(todo!());
  |          ^^^ multiple `fmt` found
  |
  = note: candidate #1 is defined in an impl of the trait `Debug` for the type `u32`
  = note: candidate #2 is defined in an impl of the trait `std::fmt::Display` for the type `u32`
help: disambiguate the associated function for candidate #1
  |
5 |     Debug::fmt(&0u32, _);
  |     ~~~~~~~~~~~~~~~~~~~~
help: disambiguate the associated function for candidate #2
  |
5 |     std::fmt::Display::fmt(&0u32, _);
  |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0034`.
error: could not compile `playground` due to previous error
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

```
Compiling playground v0.0.1 (/playground)
error[E0034]: multiple applicable items in scope
 --> src/main.rs:5:10
  |
5 |     0u32.fmt(todo!());
  |          ^^^ multiple `fmt` found
  |
  = note: candidate #1 is defined in an impl of the trait `std::fmt::Debug` for the type `u32`
  = note: candidate #2 is defined in an impl of the trait `std::fmt::Display` for the type `u32`
help: disambiguate the associated function for candidate #1
  |
5 |     std::fmt::Debug::fmt(&0u32, _);
  |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
help: disambiguate the associated function for candidate #2
  |
5 |     std::fmt::Display::fmt(&0u32, _);
  |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0034`.
error: could not compile `playground` due to previous error
```

If you apply the original suggestion, you get a compile error, because `Debug` (the *trait*) is not in scope. `Debug` (the *derive macro*) is, however. I suspect that's what's causing this? And why it doesn't happen for Display, because Display doesn't *have* a derive macro.

@rustbot label D-invalid-suggestion

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"obeis"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: Three finger tap not working
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.61.1

### Running as admin

- [X] Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

1. Turn on Keyboard Manager
2. Swap Alt and Window key
3. Open Firefox or vscode
4. Open multiple tab pages
5. Tap with three fingers on any tab

![image](https://user-images.githubusercontent.com/39730824/185173322-78d6a153-9e5c-47f4-9d57-dadc08cf3279.png)

### ✔️ Expected Behavior

Close tab

### ❌ Actual Behavior

Don't close tab

### Other Software

_No response_
Repository: vscode
Issue: editor.unicodeHighlight.ambiguousCharacters not accessible
Labels: accessibility,under-discussion,unicode-highlight

Have an ambiguous character in your editor. Notice how we render this specially so user can detect the ambiguous character.
Turn on a screen reader and notice that the screen reader does not ready anything specially when you visit the line with the ambiguous character. 

Some ideas on what we could do:
- play an aria live event when caret is on the ambiguous character. The aria live event would announce the exact character code.
- play an audio cue when on a line with an ambiguous character

ideas by @dantegagne - VS is also facing this problem

Assigning to September so we reserve some time to think about this next milestone.
Repository: flutter
Issue: iOS PlatformView should not allow non-zero origin.
Labels: platform-ios,engine,a: platform-views,P3,team-ios,triaged-ios

iOS PlatformView was designed around the assumption that the app code is the source of the truth of the PlatformView's frame. Currently, there is no code in the PlatformViewsController to prevent a PlatformView developer to make the PlatformView rendering outside of its parent view. They can simply add an origin and the embedded UIView will render outside of the widget's frame. 
This violates some assumptions in the PlatformView code. 
For example:

- PlatformView's overlay frame is calculated based on the ChildClippingView's frame, which is the parent of the embedded UIView. 
- PlatformView's touch event is handled by the touch interceptor view, which is the parent of the embedded UIView. The embedded UIView is assumed to be the same frame of the touch interceptor view. 
- Rendering offscreen breaks certain functionalities of PlatformView, for example, the blur filter does not work properly when the embedded UIView is offscreen. 

The frame of embeddedView contains 2 parts: origin and size.
The PlatformView's size is correct due to the [autoresizing mask](https://github.com/flutter/engine/blob/main/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews.mm#L826). 
The PlatformView's origin is not always correct as it is not enforced anywhere. Our own scenario tests also used a [(50, 50)](https://github.com/flutter/engine/blob/main/testing/scenario_app/ios/Scenarios/Scenarios/TextPlatformView.m#L78) as origin of the PlatformView, which should be prevented. 

We should add an enforcement in the PlatformViewController so that the origin of the PlatformView will never be none-zero. Because this might break some PlatformViews if they were using a none-zero origin, we should do this in 2-stepped release. 

- [ ] 1. Add a FML_DCHECK at every frame to check the origin of the PlatformView. Add a warning message if the origin is none-zero. Update the scenario app to use zero origin.
- [ ] 2. Add a logic that if the origin of the PlatformView is none-zero, resets the origin to zero. Update the warning message to indicate such reset has happend.
Repository: vscode
Issue: Preserve remote kernel connection when using Continue Working On
Labels: feature-request,continue-working-on

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

We gain the ability to preserve uncommitted changes when using Continue Working On--it would also be great to preserve the active kernel connection, which is possible with a remote kernel connection that stays alive and accessible independent of the current workspace location.

Although we can start with unauthenticated kernels for exploration purposes, this likely eventually requires a different auth story than what we have now--since controllers are registered by extensions, and remote kernel connections are generally protected by some kind of auth, we ideally would not want extensions to have to prompt for auth when using Continue Working On as well. The ideal user experience here IMO would be 'once I have authorized an extension in one place that VS Code is installed, signing into VS Code in another location should be sufficient to authorize that extension in that location as well'...cc @tylerleonhardt for that though :)
Repository: go
Issue: cmd/go: remove test dependency on gopkg.in service
Labels: Testing,NeedsFix,GoCommand

```
#!watchflakes
post <- pkg == "cmd/go" && test == "TestScript" && (`reading https://gopkg\.in` || `https fetch: Get "https://gopkg\.in`)
```

The `gopkg.in` service has occasional downtime (most recently https://github.com/niemeyer/gopkg/issues/78).
Some of the `cmd/go` tests of `gopkg.in` modules are isolated from outages by the Go module proxy, but unfortunately others fail when the service is down.

As far as I can tell, the `go-import` metadata served by `gopkg.in` is mostly static. (It may add some value in serving up-to-date `go-source` metadata, but `cmd/go` does not depend on that metadata.) Since we're going to have a test-local HTTPS server anyway for #27494, perhaps we can migrate the `gopkg.in` tests to use that server with static `go-import` metadata instead.
Repository: pytorch
Issue: test_profiler_experimental_tree_cuda_detailed is too unstable, and as its CUDA only difficult to regen
Labels: high priority,triage review,module: tests,triaged,oncall: profiler

### 🐛 Describe the bug

This test is a double whammy:

* It's an expect test, but for piles of internal data which can wobble on unrelated changes for no good reason...
* and it's a CUDA only test, which means that if you have a failure on a CPU build, you have no way of easily regenerating the output

This test has had to be repeatedly updated for unrelated changes multiple times in its lifetime. I am going to disable it for now and we should discuss how exactly this test should actually be written.

cc @ezyang @gchanan @zou3519 @mruberry @robieta @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb 

### Versions

master
Repository: PowerToys
Issue: Switch between rounded and non-rounded corners based on window corners in windows 11
Labels: Idea-Enhancement,Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

It would be nice if the border could switch between rounded and non-rounded corners based on window corners in windows 11.

### Scenario when this would be used?

Not all windows have rounded corners, this would make the non rounded corners have a better looking border.

### Supporting information

For eg. I faced this on the settings window for the spacedesk app which has sharp corners and the rounded border looks weird.
I've faced this with other apps as well, but I can't remember them specifically right now
![explorer_i4xu8xkzna](https://user-images.githubusercontent.com/47380919/185200887-3b38708f-ed92-44d0-95f1-165b4c8ded1e.png)
.
Repository: rust
Issue: #[deny(overflowing_literals)] is not triggered on proc macro output without a source span
Labels: A-lints,T-compiler,C-bug,A-proc-macros,L-overflowing_literals

Proc macros will not trigger `#[deny(overflowing_literals)]` if the violating output literal is not associated with an input span. It does not matter if the input span is a literal or completely unrelated. This is unexpected, as an overflowing literal should always be checked regardless of how it was generated.

proc macro lib.rs:
```rust
extern crate proc_macro;

#[proc_macro]
pub fn no_overflow_error_without_span(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
    // Convert the input to/from string to remove span info
    let value_str = input.to_string();
    let mut output = proc_macro::TokenStream::new();
    output.extend([
        "pub const PEAR: u8 = "
            .parse::<proc_macro::TokenStream>()
            .unwrap(),
        value_str.parse().unwrap(),
        ";".parse().unwrap(),
    ]);
    output
}

#[proc_macro]
pub fn overflow_error_with_unrelated_span(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
    let mut input = input.into_iter();
    let in_token = input.next().expect("single token");
    assert!(input.next().is_none(), "more than one token");

    let value_str = "256".to_string();
    let mut value_token: proc_macro::TokenTree = value_str
        .parse::<proc_macro::TokenStream>()
        .unwrap()
        .into_iter()
        .next()
        .unwrap();
    value_token.set_span(in_token.span());
    let mut output = proc_macro::TokenStream::new();
    output.extend([
        "pub const BANANA: u8 = "
            .parse::<proc_macro::TokenStream>()
            .unwrap(),
        value_token.into(),
        ";".parse().unwrap(),
    ]);
    output
}

#[proc_macro]
pub fn overflow_error_with_passthrough(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
    let mut output = proc_macro::TokenStream::new();
    output.extend([
        "pub const APPLE: u8 = "
            .parse::<proc_macro::TokenStream>()
            .unwrap(),
        input,
        ";".parse().unwrap(),
    ]);
    output
}

```

test:
```rust

// Errors out as expected
overflow_error_with_passthrough!(256);

// Gives an expected overflow error even though the span is completely unrelated to the overflow.
overflow_error_with_unrelated_span!(blah);

// No error here! This is unexpected. PEAR is equal to 0 as it implicitly overflowed.
no_overflow_error_without_span!(256);
```


`rustc --version --verbose`:
```
$ rustc --version --verbose
rustc 1.64.0-nightly (87588a2af 2022-07-13)
binary: rustc
commit-hash: 87588a2afd9ca903366f0deaf84d805f34469384
commit-date: 2022-07-13
host: x86_64-unknown-linux-gnu
release: 1.64.0-nightly
LLVM version: 14.0.6
```