Bad traces cause panics #174

Closed
opened 2023-01-25 22:17:18 +00:00 by sam · 0 comments
Owner

Describe the bug

Reproduction steps
Steps to reproduce the behavior:

  1. trace somewhere where the end is a SERVFAIL
  2. it crashes

Expected behaviour
A bad trace should not cause a panic

Screenshots / Logs

panic: invalid argument to Intn

goroutine 1 [running]:
math/rand.(*Rand).Intn(0x8f3020?, 0xc000012018?)
        /usr/local/go/src/math/rand/rand.go:168 +0x65
main.run({0xc0000220a0, 0x5, 0x5})
        /drone/src/main.go:120 +0x4c5
main.main()
        /drone/src/main.go:22 +0x32

math.Rand panics when it is given an upper bound less than or equal to 0

System information (please complete the following information):

  • OS: Debian
  • Version: awl version 0.6.0, built with go1.19.3

Additional context
N/A

**Describe the bug** **Reproduction steps** Steps to reproduce the behavior: 1. trace somewhere where the end is a SERVFAIL 2. it crashes **Expected behaviour** A bad trace should not cause a panic **Screenshots / Logs** ``` panic: invalid argument to Intn goroutine 1 [running]: math/rand.(*Rand).Intn(0x8f3020?, 0xc000012018?) /usr/local/go/src/math/rand/rand.go:168 +0x65 main.run({0xc0000220a0, 0x5, 0x5}) /drone/src/main.go:120 +0x4c5 main.main() /drone/src/main.go:22 +0x32 ``` math.Rand panics when it is given an upper bound less than or equal to 0 **System information (please complete the following information):** - OS: Debian - Version: `awl version 0.6.0, built with go1.19.3` **Additional context** N/A
sam closed this issue 2023-01-31 16:08:07 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sam/awl#174
No description provided.