And now D7482 just decided to do the opposite... It's green ¯\_(ツ)_/¯.
The only thing i can see that explains it is that i tagged swh.model...

That last diff fixed it in the end...
My docker tryout agreed [1] (contrary to jenkins diff for some reason).
So i pushed and jenkins dev build got green again [2] (finally).

D7480 should fix it?

D7480 should fix it?

It seems to have fixed it!
Great. Thanks.

try copying this syntax for the code block:

https://forge.softwareheritage.org/source/swh-storage/browse/master/swh/storage/cli.py$213-223

try copying this syntax for the code block:

Step to tentatively reproduce the issue:

• create the docker image jenkins run locally
• connect to it
• setup the container to run as jenkins does

Tentatively trying to reproduce the ci issue:

$ cd $SWH_CI_ENVIRONMENT_HOME/swh-jenkins-dockerfile
# build the image
$ make swh-jenkins/sphinx
$ cd $SWH_ENVIRONMENT_HOME/swh-docs
$ docker run -ti -v $PWD:/src/swh-docs/ --entrypoint bash swh-jenkins/sphinx
-> $ git clone https://forge.softwareheritage.org/source/swh-environment.git
-> $ cd swh-environment
# copy out the local diffs (or git checkout from staging as you wish)
-> $ crudini --del .mrconfig snippets
-> $ crudini --del .mrconfig swh-py-template
-> $ mr -j 8 -t update
-> $ cd swh-docs
# install the locally mount the swh-docs "changes" to debug
-> $ rsync -avz --exclude .tox /src/swh-docs/ ./
-> $ git clean -dfx
-> $ SPHINXOPTS='-W -q --keep-going -w errors.log' SPHINXOPTCOLOR='--no-color' tox -e sphinx-dev
...

To no avail ^
Not reproduced exactly the same issue.
And it's taking forever like the ci build...

I agree that having actually "working" examples in the doc is a must.

This page should contain a link to the different guides and to the guided tour.
Also, when the guided tour is published, would this page disappear?
by clicking on help you enter the guided tour but you might want access to specific guides and FAQ.

Is this page enough?
https://docs.softwareheritage.org/sysadm/mirror-operations/planning.html

Another option by @anlambert for better visibility:

• put it in the homepage I think, maybe by adding a new sentence in the Overview section

I think the proper place for that link would be the Permalinks tab.

It's deployed and the fix is ok \m/!

Pushed a fix and triggered a deployment of the docs.
Hopefully, this will fix it.

oh yes, definitely. No idea why I made them relative

oh yes, definitely. No idea why I made them relative

Paths are hardcoded with relative values so depending on the depth, it won't work [1] [2].

It seems to be when we are on any page from the devel instance (below the main menu page of that instance).
The getting started for example also shows this.

got a list of weirdness types here: https://github.com/dulwich/dulwich/pull/927 and https://github.com/dulwich/dulwich/issues/931

A simple cp command in swh-docs Makefile can do the trick, but we need a generic way of adding files/folder in the swh-docs build directory.