Derrick Stolee <derrickstolee@xxxxxxxxxx> writes: > After investigating some of the failures from creating a BUG() statement > when istate->repo is NULL I see several problems, and they are not related > to submodules for the most part. > > The first issues I've found are due to code paths that operate on the_index > without actually initializing it with a do_read_index(), or otherwise > initialize an index using a memset() instead of a common initializer. This > looks to be a frequent enough problem that solving it would require a > significant effort. It's not a quick fix. Thanks. It is not entirely unexpected X-<, considering how the connection from the in-core repository and the in-core index has been developed and evolved. So in short, istate->repo is not yet ready to be used, until the problems you identified are resolved? We probably should start paying down such technical debts. We've punted on them too many times, saying "yes this is klunky but what we have is good enough for adding this feature", I suspect? Thanks.
