-
This isn't urgent, but I wanted to record it while I had a stacktrace. I made a change to the underlying messages table and added a field, which eventually caused a panic downstream.
```
panic: r…
-
When filing a bug, please include the following headings if
possible. Any example text in this template can be deleted.
#### Overview of the Issue
Some of the unit tests are failing on a panic …
-
Was perusing panics today and found this. It has happened 15 times over the last 30 days, running various near tip versions > v13
```go
panic: assignment to entry in nil map
goroutine 616 [runn…
-
#### Overview of the Issue
#### Reproduction Steps
Steps to reproduce this issue,…
-
List of minor improvements / missing things from docs at https://vitess.io/docs/18.0/reference/vreplication/movetables/ and https://vitess.io/docs/18.0/reference/vreplication/reshard/
- [ ] Documen…
-
looks like this might be a race condition on startup? I've only seen it once, so it's not common nor a major concern for us, just noting in case it is indicative of any deeper issues
```go
panic: …
-
Was perusing panics today and found this. It has happened 12 times over the last 30 days, running inside the Go driver at v0.12.2
```go
panic: runtime error: index out of range [2] with length 2
…
-
Scenario:
* Sharded keyspace
* Use a vschema like this with a reference table:
```
{
"sharded": true,
"vindexes": {
"hash": {
"type": "hash"
}
},
"tables": {
…
-
Today the Vitess Development Version is 17.0. And in the getting started local install docs, installing vitess section, we mention the previous major release of 16.0: https://vitess.io/docs/17.0/get-s…
-
This is a tracking issue for the rework of information schema. We would like to rethink and rework how the information schema is handled in Vitess. So far, we have three items:
- https://github.com/v…