Vladimir Kotal

I am curious what kind of resource problem this is.

These are probably just userland threads of the same process. The green color indicates them - try pressing Shift+H to toggle the thread view. See https://unix.stackexchange.com/questions/10362/why-does-htop-show-more-process-than-ps and https://peteris.rocks/blog/htop/

Similarly, try running `pstree -p` on the indexer process ID with and without `-T`. Actually, when you run without `-T` and with `-t` it will even display Java thread names.

Also, to get overall info on resources/process/threads in a Docker container, use `docker container stats`. For more detailed view with threads you can use `docker container top -eLf`

The build failed with: ``` christian-korneck/update-container-description-action@v1 is not allowed to be used in oracle/opengrok. Actions in this workflow must be: within a repository that belongs to your Enterprise account, created...

Because of internal regulations, third party Github actions cannot be used. Rewriting `docker.sh` to Python.

I hit a number of limitations of https://github.com/docker/docker-py (which I deem serious enough) so will rewrite just the README uploading part.

https://tombrow.com/dark-mode-website-css

Don't worry about squashing the changesets. I am well aware you craft the csets carefully. In general I squash only csets that are not of value w.r.t. history like small...

What is inside these files ? i.e. what analyzer was used to index them ?