What kind of problem are you reporting?

• Access related problem
• Service related problem
• Data related problem

Some of the entries in the conda-analytics conda_environment.yml should be updated. This is low priority. In the cases I've listed where updating a non-pinned package will break the environment, I think it's unlikely for those updates to be triggered unintentionally. It's still worth closing off the pathway since it's so easy to do.

These two lines should be added to the file:

• jupyter_core=5.5 #pinned
  • The base version is 5.5.0.conda update jupyter_core updates to 5.7.2, which makes the environment unable to launch.
• jupyterlab_server=2.25 #pinned
  • The base version is 2.25.2. conda update jupyterlab_server updates to 2.27.2, which makes the environment unable to launch.

These two lines should be updated:

• sqlalchemy<2.0 #pinned
  • The base version is 1.4.49. Without the pin, conda update sqlalchemy updates to 2.0.31, which makes the environment unable to launch.
• git+https://github.com/wikimedia/wmfdata-python.git@release
  • Currently, the line explicitly specifies v2.3.0, but I think new versions of Wmfdata can be safely assumed to work in our environment 😁

This line should be removed from the file:

• urllib3<2.0
  • The underlying problem in T345309 has been resolved since the Presto coordinator now uses a TLS certificate with subjectAltName populated)