Long Vu
Long Vu
I am getting something here. Running only the hanging notebook in Jenkins, I got Kernel died while it tries to import the various modules at the beginning of the notebook...
> That's essentially the error that we often see when running some of these tests. Look through the failing builds on GitHub, and you'll see that kernels often die randomly....
> > That's essentially the error that we often see when running some of these tests. Look through the failing builds on GitHub, and you'll see that kernels often die...
FYI, the Beta env on PAVICS has the broken env py310-240419 and the Gamma has the working env py310-240411.
Just a note that for the Jupyter env, we moved to python 3.11 and the hanging error is gone !
@NyakudyaA FYI @fmigneault is a collegue of mine. He is more well versed in Github automation than I am.
> [@tlvu](https://github.com/tlvu) I will take a look tonight, in the meantime you can check the commits that updated the password file `git log -- scripts/update_passwords.sh` Right on the money @NyakudyaA...
To have an image that is closest to your 2.27.2 published image `kartoza/geoserver:2.27.2--v2025.08.05` I have also generated `pavics/geoserver:2.27.2--v2025.08.05-kartoza-rollback-update_passwords.sh-to-v2.26.1--2025.01.03--ae25c98` that works with our data. Dockerfile: ```dockerfile FROM kartoza/geoserver:2.27.2--v2025.08.05 ADD https://raw.githubusercontent.com/kartoza/docker-geoserver/refs/tags/v2.26.1--2025.01.03--ae25c98/scripts/update_passwords.sh /scripts/update_passwords.sh...
> can you test the PR associated with this fix and revert @NyakudyaA I used your new release `kartoza/geoserver:2.27.2--v2025.09.09` and got this different error below so my server still can...
> what env variables are you using for the upgrade https://github.com/bird-house/birdhouse-deploy/blob/45f59d3fd3a3dcb6c175da08105e0ede899b9bd1/birdhouse/components/geoserver/docker-compose-extra.yml#L14-L23 I do not have `GEOSERVER_SECURITY_MODE: preserve`. Should I add it explicitly? Isn't `preserve` the default value? > Can you...