Open alexeych0 opened 10 months ago
I believe I'm hitting this as well and it's related to the usage of asyncio. Only have a couple of guesses here but another plugin could be calling asyncio.run()
but the code definitely doesn't wait for the clone to finish for me as well.
Eventually, wasn't able to locate the problem. But, the issue is resolved for us after we migrated Gitlab runners to k8s. Maybe it was something with the runner config or with the vm it was previously executed on
I would agree that it was a runner config after playing with this plugin a bit. It's not the async like I implied at first.
I'm using multirepo plugin with
nav_repos
config:mkdocs.yml
:Everything works fine, when I run
mkdocs serve
/mkdocs build
locally. However, when building the docs from Gitlab CI job, I'm facing the issue that remote repositories are cloned only when the documentation already has been built. As a result, the output directorysite
doesn't have the imported repos, causing 404 errors.Here's the example:
Notice line 10. Normally,
developers-doc
import is started and completed right after the log "Multirepo plugin importing docs...". But somehow running this command from Gitlab Runner alters this behavior and its execution postponed until it's already too late.Do you have any ideas what's happening here?