Coflow support
Coflow is built and supported by one developer. The fastest way to get help is an email with the details below.
Contact
candidathector@gmail.com — subject “Coflow support”; the button above also fills in a bug-report template
Messages are read and answered by the developer who wrote the code.
What to include in a bug report
With these, most problems can be reproduced and fixed without back-and-forth.
- Your VS Code version: Help › About (on macOS: Code › About Visual Studio Code).
- Your Coflow version: in the Extensions view, next to the name.
- The Coflow log: open the Output panel (
Ctrl+Shift+U) and pick Coflow in its list, or run the command Coflow: Show Log. Copy the lines around the error. - Your operating system and Python version (
python --versionin the interpreter Coflow uses). - What you did and what you expected. A screenshot of the map helps. If you can, a small project or file that shows the problem.
Please do not send code you are not allowed to share. A small made-up example that shows the problem is just as useful.
Troubleshooting
“Python interpreter not found”, or the map says it couldn't analyze the project
Coflow needs Python 3.10 or newer. It uses the interpreter selected in the Python extension, else python3. Pick one with Python: Select Interpreter, or set the full path in the setting coflow.pythonPath (for example /usr/bin/python3 or C:\Python312\python.exe). The error message has Select Interpreter and Set Python Path buttons, and Show Log says which interpreter was tried.
Coflow is disabled, or the map does not open (Restricted Mode)
Coflow runs your Python interpreter, and Record a Run… runs your code, so it only works in a trusted folder. Run Workspaces: Manage Workspace Trust and trust the folder, then open the map again. Virtual workspaces (files that are not on disk) are not supported.
The map is empty
Coflow maps Python projects. Open the folder that contains your code (not a single file), and check that coflow.exclude does not leave it out. Virtual environments, node_modules, build folders and caches are always left out.
A big project is slow, or the analysis stops
An analysis stops after two minutes. Leave out folders you do not need with coflow.exclude (such as legacy/** or generated code), and turn off coflow.analyzeOnSave to refresh only when you ask (Coflow: Refresh Map). Wide levels are shown at a readable size: pan, or use Search map to jump.
A link I expected is missing, or drawn dashed
Calls through getattr, dependency injection or dictionaries of handlers cannot always be proven by reading the code; those links are dashed or missing. Record a run to see exactly what happened.
Something is hidden on the map
Open View Options (⋯ on the map): each option says how many things it hides, and the map shows “N hidden here”. Reset View Options goes back to the defaults.
More help
- Common questions (privacy, languages, license) are answered on the Coflow page.
- What Coflow does with your code: the privacy statement.
- Changelog