You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From https://2i2c.freshdesk.com/a/tickets/594, they are getting errors about PROJ environment variables not being set. This is because the conda environment is not being activated before the notebook server starts. The PATH env vars we set account for most of what conda activate does, but turns out conda activate also sets environment variables!
So we should properly activate the conda environment before starting the notebook server.
The text was updated successfully, but these errors were encountered:
I think PROJ is the only package I know of that is affected by this, as it uses the conda package to actually set environment variables. Otherwise, I am generally not too concerned :)
From https://2i2c.freshdesk.com/a/tickets/594, they are getting errors about PROJ environment variables not being set. This is because the conda environment is not being activated before the notebook server starts. The PATH env vars we set account for most of what conda activate does, but turns out conda activate also sets environment variables!
So we should properly activate the conda environment before starting the notebook server.
The text was updated successfully, but these errors were encountered: