Potential bug; Flask v1.1.2 fails with MATRX visualization

[jwaa]

Describe the bug
See this report at the AIMS project. It describes a connection failure between the JS server-client and their custom visualization Flask server.

To Reproduce
Should be test if this same bug applies to the MATRX Visualizer.

Expected behavior
Correctly loading of the pages, due to a succesful connection between the visualization server and the JS server-client.

Screenshots
If it fails you see this on localhost:3000

Stacktrace
A stacktrace can be viewed in your browser's console.

Additional context
The issue might be due to a combination of how MATRX uses Flask and the Flask v1.1.2 patch. However, this seems unlikely as the visualization_server.py is a very simple Flask server. Furthermore, the Flask issue list does not show an apparent report of such an issue, this combined with the relative few patch release of Flask (about once or twice a year), it is unlikely that this issue will be fixed soon.

A simple solution for us would be to fix the dependency of Flask to v1.1.1 and ignore these bug fixes. But only if MATRX suffers the same bug, if not it is a bug in the custom visualization of AIMS.

[thaije]

Flask can be finicky with file paths, and the Flask 1.1.2 patch seems to have changed something in the pointing to the static folder with static web files of our visualization web server. In AIMS this was solved by changing how the paths were defined, something which was already done in the newer versions of MATRX.

However, it is worth it to investigate if using the url_for() function can solve the issues with file paths forever, as used here.

Thus, there should be no problems with MATRX and Flask 1.1.2 itself. If someone still has this problem, please report it in this issue and I'll take another look.

[jwaa]

In response to this bug in AIMS the Flask dependency for MATRX is now fixed to v1.1.1, I will set this back to =>v1.1.1 in a hotfix today.