influxdata / influxdata/kapacitor
panic: runtime error: invalid memory address or nil pointer dereference
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Kapacitor 1.3.3 on Windows
happened when try to start a stream task
```
kapacitord -config custom.conf
'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::
##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:
##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:
#####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::
##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::
2017/11/24 19:33:06 Using configuration at: custom.conf
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x48 pc=0x5ada1d]
goroutine 161 [running]:
panic(0x1d23000, 0xc042010080)
/usr/local/go/src/runtime/panic.go:500 +0x1af
github.com/influxdata/kapacitor/services/replay.(*Service).doRecordStream(0xc042239ce0, 0xc04221b530, 0x24, 0x0, 0x0, 0xed1a9fad7, 0xc03afa09a8, 0x2ed2e20, 0xc0423f7420, 0x1, ...)
/root/go/src/github.com/influxdata/kapacitor/services/replay/service.go:1256 +0x11d
github.com/influxdata/kapacitor/services/replay.(*Service).handleRecordStream.func1(0xc042475d80, 0xc042239ce0, 0xc0424dad40, 0xc0424db240, 0xc04221b530, 0x24, 0xc0426e78c0, 0x39, 0x0, 0x0, ...)
/root/go/src/github.com/influxdata/kapacitor/services/replay/service.go:622 +0x12c
created by github.com/influxdata/kapacitor/services/replay.(*Service).handleRecordStream
/root/go/src/github.com/influxdata/kapacitor/services/replay/service.go:624 +0x4f0
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with services/replay/service.go at doRecordStream, line 1256, then inspect handleRecordStream around lines 622-624. Reproduce the panic using Kapacitor 1.3.3 on Windows with `kapacitord -config custom.conf` and a stream task. Done means identifying and preventing the nil pointer dereference, with a regression test if the relevant test location can be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100