Repository navigation
Mycelia submodule clone fails due to missing commit reference #265
Description
Summary
Cloning Chronicle with the Mycelia submodule enabled fails because the submodule
points to a commit that no longer exists in the remote repository.
Since Mycelia is optional, this currently blocks the setup for users who do not
intend to use it.
Steps to Reproduce
git clone --recursive https://github.com/SimpleOpenSoftware/chronicle.gitor
git submodule update --init --recursiveActual Result
fatal: remote error: upload-pack: not our ref <commit>
fatal: Fetched in submodule path 'extras/mycelia', but it did not contain <commit>.The clone/setup process stops here.
Expected Result
- Users should be able to complete setup without Mycelia, since it is optional.
- A broken Mycelia submodule should not block Chronicle installation.
Environment
- OS : Ubuntu(WSL2 on windows)
- Git version : default ubuntu package
- Chronicle setup via quickstart.md & README.md
Notes / Suggestions
- Update the Mycelia submodule commit reference to a valid commit
- Mycelia opt-in (do not require --recursive by default)
- Document an official workaround for skipping Mycelia during clone/setup
- Handle submodule failure gracefully during setup
I’m happy to submit a documentation PR clarifying that Mycelia is optional and how to proceed without it.
Activity
AnkushMalaker commentedon Jan 18, 2026
I'm actually not sure how much we wanna have mycelia support in this repo. Mycelia has built its own audio pipeline, it may make sense to process and use mycelia side by side with chronicle, or merge them (not necessarily in the same repo) but some how architecture wise, such that we don't have to deal with mycelia setup. For now its deadcode as I don't think this works.
cc @thestumonkey can confirm ?
futureisAJASU commentedon Jan 20, 2026
Got it, thanks for the clarification.
My intention here wasn’t to suggest Mycelia should be a first-class or long-term supported component in this repo, but mainly to prevent users from getting blocked during setup due to the broken submodule reference.
If the direction is to treat Mycelia as deprecated / dead code for now, I’m totally fine updating the docs to make that explicit, or removing the workaround once the architectural direction is clearer.
Happy to adjust based on where the project wants to go.
AnkushMalaker commentedon Feb 24, 2026
Hi, I endedup cleaning a lot of deadcode including half implemented mycelia integrations, and submodule. Closing. Feel free to open if any issue persists. Thanks! @futureisAJASU