INDRA (Integrated Network and Dynamical Reasoning Assembler) is an automated model assembly system interfacing with NLP systems and databases to collect knowledge, and through a process of assembly, produce causal graphs and dynamical models.
Build the CoGEx docker locally and ensure the docker builds from the branch for CoGEx and for indralab_auth_tools to provide the full updates. Make sure the build is tagged with something else than latest to not overwrite the current running service.
Run the docker locally and check that login and curation capabilities work as expected (although actually logging in probably won't work as login typically requires https) as well as looking for any other issues that come from updates.
Repeat the build and deploy steps for the current service and check again that everything works (especially the actual login functionality).
Repeat the whole process for emmaa (which runs on a separate server) and indra_db (which uses lambda + api gateway)
Upgrading to
Flask>=3,<4
comes with a second order consequence: currently we useflask-jwt-extended<4
, which requiresFlask<2.0,>=1.0
. However, upgradingflask-jwt-extended
to be compatible withFlask>=3,<4
comes with an api change documented here: https://flask-jwt-extended.readthedocs.io/en/stable/v4_upgrade_guide.html#api-changesIn short, we need to replace all instances of the decorator
@jwt_optional
with@jwt_required(optional=True)
wherever we update toFlask>=3,<4
.Related: https://github.com/gyorilab/gilda/issues/137
I'll try to list all places in downstream repositories in sorger/gyorilab where we would need to make the change:
To test the upgrade
indralab_auth_tools
to provide the full updates. Make sure the build is tagged with something else thanlatest
to not overwrite the current running service.https
) as well as looking for any other issues that come from updates.Testing