Connection Issue with Tapipy Library in Custom Jupyter App

[mosoriob]

Description:
We are experiencing a problem with our custom Jupyter application when including the tapipy library in the requirements. The application installs and runs but fails to establish a secure connection.

Steps to Reproduce:

1. Create a Jupyter application with the basic template.
2. Add tapipy to the requirements.
3. Deploy the application.
4. Observe that the application fails to establish a secure connection.

Expected Behavior:
The application should run and connect securely with tapipy included in the requirements.

Actual Behavior:
The application installs and runs but fails to establish a secure connection when tapipy is included in the requirements.

Additional Information:

• Removing tapipy from the requirements allows the application to load and connect successfully.
• Installing tapipy interactively in a Jupyter notebook works without issues.
• The issue seems to be specific to our custom Jupyter applications. The kernels work fine in the Portal HPC lab app.
• The secure connection issue arises when tapipy is installed, either via Docker or as part of the application requirements.

Logs/Screenshots:
(Include any relevant logs or screenshots that could help in diagnosing the problem.)

Potential Cause:
The problem might be related to how tapipy interacts with the environment setup in our custom applications.

Suggested Actions:

1. Investigate the environment setup differences between our custom applications and the Portal HPC lab app.
2. Test installing tapipy in different stages of the application setup to pinpoint where the connection issue arises.
3. Check for any known compatibility issues or bugs with tapipy and the specific versions of dependencies we are using.

[mosoriob]

Test #1: Install tapipy in a running environment

Result

Connection doesn't close

Notes

Packages conflicted between Jupyter server and tapi

jupyter-events 0.10.0 requires jsonschema[format-nongpl]>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.
jupyterlab-server 2.27.2 requires jsonschema>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.

Logs

Apptainer> which python
/work/07025/mosorio/ls6/miniconda3/envs/llm/bin/python
Apptainer> pip install tapipy

openapi_core, tapipy
  Attempting uninstall: urllib3
    Found existing installation: urllib3 2.2.1
    Uninstalling urllib3-2.2.1:
      Successfully uninstalled urllib3-2.2.1
  Attempting uninstall: jsonschema
    Found existing installation: jsonschema 4.22.0
    Uninstalling jsonschema-4.22.0:
      Successfully uninstalled jsonschema-4.22.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
jupyter-events 0.10.0 requires jsonschema[format-nongpl]>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.
jupyterlab-server 2.27.2 requires jsonschema>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.
Successfully installed PyJWT-2.8.0 atomicwrites-1.4.1 cloudpickle-3.0.0 cryptography-42.0.8 isodate-0.6.1 jsonschema-4.17.3 jsonschema-spec-0.1.6 lazy-object-proxy-1.10.0 more-itertools-10.3.0 openapi-schema-validator-0.3.4 openapi_core-0.16.0 openapi_spec_validator-0.5.4 parse-1.20.2 pathable-0.4.3 pyrsistent-0.20.0 tapipy-1.6.3 urllib3-1.26.19 werkzeug-3.0.3
Apptainer> 

[mosoriob]

Test #2: Add tapipy to requeriments.txt and create a new app

Results

• App is not available
• We can reproduce the error
• Draft7Validator(TyperError: create.<locals>.Validator.__init__() got an unexpected keyword argument 'registry' jupyter/jupyter_core#369
• There is a dependency conflict between jupyter and tapipy
  jupyter-events 0.10.0 requires jsonschema[format-nongpl]>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.
  jupyterlab-server 2.27.2 requires jsonschema>=4.18.0, but you have jsonschema 4.17.3 which is incompatible.

Notes

jupyter/jupyter_core#369