I have seen this issue appear online a few times, the CPU locks at 100% when throwing a bad reference.
This happened because the local ‘lock’ used by the rolodex file loader, was not releasing correctly when a
lookup occurred, that could not be found via a rolodex file lookup.
https://github.com/daveshanley/vacuum/issues/393
Signed-off-by: quobix <dave@quobix.com>
currently it pre-indexes everything in the root. This behavior is undesirable out of the box, so it now looks recursively by default.
Signed-off-by: quobix <dave@quobix.com>
Every `Build()` method now requires a `context.Context`. This is so the rolodex knows where to resolve from when locating relative links. Without knowing where we are, there is no way to resolve anything. This new mechanism allows the model to recurse across as many files as required to locate references, without loosing track of where we are in the process.
Signed-off-by: quobix <dave@quobix.com>
To make this work correctly, this needs completely shaking up and a transfer of ownership. The index is now local,
the rolodex is now global.
Signed-off-by: quobix <dave@quobix.com>
