Closed philschleier closed 4 months ago
which version of vacuum did you test against?
v0.9.7
ok, this is nuts. I will fix.
This problem was in libopenapi
. In v0.15.12
it was fixed, the resolver was not continuing down a path correctly once finding a sibling node that uses a reference.
I added a test to make sure this loop is closed permanently.
https://github.com/pb33f/libopenapi/blob/main/index/resolver_test.go#L1339
The upstream fix is available in v0.9.8
of vacuum.
The following spec causes vacuum to spin infinitely and consume all available memory:
Not sure what to call it, not even sure if it's valid, but probably shouldn't break vacuum...