-
## Ranges
```rust
7566651-7566655
7566656-7566663
7566664-7566669
7566670-7566675
7566676-7566681
7566682-7566688
7566689-7566692
7566693-7566700
7566701-7566707
7566708-7566714
7566715-…
-
After upgrading Parca to v0.22 (and Parca Agent to v0.32) I'm seeing it constantly crashing with this panic:
```
{"addr":":7070","caller":"server.go:90","level":"info","msg":"starting server","na…
-
```
➜ RUST_BACKTRACE=1 cargo run --example gelu -F cuda
Finished `dev` profile [optimized + debuginfo] target(s) in 0.22s
Running `target/debug/examples/gelu`
thread 'main' panicked at /…
-
### Describe the bug
```bash
Error: failed to handle: index out of bounds: the len is 15 but the index is 18
Stack backtrace:
0:
1:
2:
3:
4:
5:
6: _ZZN4node14Thr…
-
### Bug report
One of our indexers suddenly started crashing with the following. We're not sure why.
### Relevant log output
```Shell
thread 'tokio-runtime-worker' panicked at 'failed to parse mapp…
-
### Is there an existing issue for the same bug?
- [X] I have checked the existing issues.
### Branch Name
1.2-dev
### Commit ID
f797a1b4abe1f94fad0aa1231e98ae9359790a5d
### Other En…
-
A lot of `Command::new` are spawned twice as `.status()` and `.output()` internally spawn a process and wait for it to complete. Only one should be used `.output()` which also contains `.status`.
T…
-
## Description
I was messing around with divergent operations to see how `jj` handles abandoning a commit while also trying to edit it concurrently, and I found this crash in `jj op show`.
## St…
-
Another entry for `blocked-on-adopting-ui_test`. We will want a test that we emit something like this for a multithreaded panic:
```
thread 'Builder #1' panicked at $HOME/work/pgrx/pgrx/src/fcinfo.r…
-
**Describe the bug**
After upgrading os from 1.7.0 to 1.8.0 with two tenants seeing otel core and otel pod are in crashloopbackoff state
**Steps to reproduce**
1. Bringup up Vanquish High with 1.…