Hi everyone, I am facing an issue running a Python script that uses OpenCV in 0CodeKit of the Make scenario, and I’d like some help troubleshooting it. I have a Make scenario that involves three Python modules running in sequence inside 0CodeKit:
- First Python Module → Fetches access & refresh tokens from Box.
- Second Python Module (Asynchronous Execution) → Uses OpenCV to process an image and should output the processed image file path.
- Third Python Module → Uploads the processed image to Box again.
Initially, I faced issues installing OpenCV (cv2) inside 0CodeKit. I tried using: • opencv-python • opencv-python-headless Both failed to install due to missing build dependencies like cmake, gcc, and scikit-build. This indicates that 0CodeKit does not fully support OpenCV out of the box. I tried switching to Run Asynchronous Python Code (Advanced) module. However the Asynchronous module does not return a result variable, only a task id and status with a message. In my script, the third module needs the processed image path from module 2 but because there is no result available in the asynchronous module, the workflow is broken. I cannot add a custom webhook too as webhooks can only be added at the beginning of a script. My queries:
- Is there a way to retrieve the final output (file_path) from an Asynchronous Execution module using the Task ID?
- Can 0CodeKit support OpenCV (cv2) in any way, or is it completely unsupported?
- Is there an alternative solution within 0CodeKit to pass the processed image path from an async module to the next script?
- Would it be better to use a different platform like PythonAnywhere, where I can host the script and call it via SSH in Make?
I would really appreciate any insights or suggestions. Thanks in advance for your help!