Hi Suhail,
No, we do not utilize cryosparc live at the moment.
2021-02-09 14:18:26,802 RTP INFO === STARTED ===
2021-02-09 14:18:26,803 RTP.BACKGROUND_WORKER INFO === STARTED ===
* Serving Flask app "rtp_manager" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: off
2021-02-09 15:32:33,131 RTP INFO === STARTED ===
2021-02-09 15:32:33,132 RTP.BACKGROUND_WORKER INFO === STARTED ===
* Serving Flask app "rtp_manager" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: off
2021-02-09 17:15:25,958 RTP INFO === STARTED ===
2021-02-09 17:15:25,958 RTP.BACKGROUND_WORKER INFO === STARTED ===
* Serving Flask app "rtp_manager" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production deployment.
Use a production WSGI server instead.
* Debug mode: off
I found the following output with log app, maybe it is relevant?
cryosparcm log app
(node:30331) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
(node:30331) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
(node:30331) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
(node:31850) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:31850) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
(node:31850) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
(node:31850) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
this is just a short selection of such entries.
Cheers
Lukas