GitoxideLabs/gitoxide · error

populated above

Error message

populated above

What it means

`Submodule::active_state_mut()` lazily populates an internal `IsActiveState` cache and then unwraps it with `expect("populated above")`. The panic indicates the lazy-population loop above failed to set the state despite the code path assuming it did — an internal invariant of the submodule caching logic. It should be unreachable for correct inputs.

Solutions

1. Report this as a bug to gitoxide with the repository reproducing it — the invariant assumes population always happens.
2. Work around by using the non-mut `active_state()`/platform accessors if available, or re-open the repository.
3. Sanitize submodule config: ensure each `.gitmodules` entry has a matching `submodule.<name>.path`/`url` in `.git/config` or is absent entirely.

// ensure submodule exists in index and .gitmodules
let subs = repo.submodules()?; // iterate instead of hand-crafted lookups

match repo.submodules() { Ok(subs) => ..., Err(e) => eprintln!("submodule access failed: {e}") } // panics abort the process; guard inputs instead

When it happens

Trigger: Calling `active_state_mut()` on a submodule whose active-state computation returned without populating the cache; practically unreachable but reachable if submodule lookup or config parsing silently produces an empty state (e.g. a submodule entry whose path/config lookups misbehave).

Common situations: Working in repositories with hand-edited `.gitmodules` or `.git/config` submodule sections that don't match the index; unusual submodule setups where the name-to-path mapping is inconsistent.

Understand the failure class

Background: "This is a bug, please report it": internal invariant violations, unreachable panics, and SNH errors explained — this error's family across 47 libraries.

Related errors

• visit_non_tree() called us
• BUG: ResolvedSignatures don't exist here when nothing is set
• initial hunks are never ancestors
• resolution present if ID can be used as fallback
• find returned a cached commit, so we expect cache to be…

AI-assisted analysis of GitoxideLabs/gitoxide@e73179060b (2026-09-08). Data as JSON: /api/errors/3023dfbc480929c1. Report an issue: GitHub.

Appendix: source

Thrown at gix/src/submodule/mod.rs:78

    ) -> Result<(RefMut<'_, IsActivePlatform>, RefMut<'_, gix_worktree::Stack>), is_active::Error> {
        let mut state = self.is_active.borrow_mut();
        if state.is_none() {
            let platform = self
                .modules
                .is_active_platform(&self.repo.config.resolved, self.repo.config.pathspec_defaults()?)?;
            let index = self.index()?;
            let attributes = self
                .repo
                .attributes_only(
                    &index,
                    gix_worktree::stack::state::attributes::Source::WorktreeThenIdMapping
                        .adjust_for_bare(self.repo.is_bare()),
                )?
                .detach();
            *state = Some(IsActiveState { platform, attributes });
        }
        Ok(RefMut::map_split(state, |opt| {
            let state = opt.as_mut().expect("populated above");
            (&mut state.platform, &mut state.attributes)
        }))
    }
}

struct IsActiveState {
    platform: IsActivePlatform,
    attributes: gix_worktree::Stack,
}

///Access
impl Submodule<'_> {
    /// Return the submodule's configured name as it appears in `submodule.<name>.*`.
    ///
    /// Note that this name is not guaranteed to be valid and may contain traversal components if
    /// the configuration was crafted manually.
    ///
    /// Use [`validated_name()`](Self::validated_name()) to obtain a validated submodule name.

View on GitHub (pinned to e73179060b)