github-vet / github-vet/rangeloop-pointer-findings
emqx/kuiper: xstream/operators/join_operator.go; 22 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [emqx/kuiper](https://www.github.com/emqx/kuiper) at [xstream/operators/join_operator.go](https://github.com/emqx/kuiper/blob/91eacc9baea40bd1dedf0267c18ef39a3296c829/xstream/operators/join_operator.go#L226-L247)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to right was used in a composite literal at line 230
[Click here to see the code in its original context.](https://github.com/emqx/kuiper/blob/91eacc9baea40bd1dedf0267c18ef39a3296c829/xstream/operators/join_operator.go#L226-L247)
Click here to show the 22 line(s) of Go which triggered the analyzer.
```go
for _, right := range rights {
if join.JoinType == xsql.CROSS_JOIN {
merged.AddTuple(right)
} else {
ve := &xsql.ValuerEval{Valuer: xsql.MultiValuer(&left, &right, fv)}
result := ve.Eval(join.Expr)
switch val := result.(type) {
case error:
return nil, val
case bool:
if val {
if join.JoinType == xsql.INNER_JOIN && !innerAppend {
merged.AddTuples(left.Tuples)
innerAppend = true
}
merged.AddTuple(right)
}
default:
return nil, fmt.Errorf("invalid join condition that returns non-bool value %[1]T(%[1]v)", val)
}
}
}
```
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 91eacc9baea40bd1dedf0267c18ef39a3296c829
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with xstream/operators/join_operator.go at lines 226-247 and read the reported range-loop pointer finding in its Go context. Verify whether the references to right remain valid for the intended join evaluation, then leave the issue reaction that records Bug, Mitigated, or Desirable Behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100