Debugging no longer supported in version 2.0 of Algorithm Terminal

Hey Greg,

Experiencing the same issue and I can't find a setting either.  Jared Broad can you shed some light on this?

Sounds like VSCode IDE is coming up!

Fred

Hey All – yes we're in the final stages of launching VSCode! It was live all Friday but we thought there were too many bugs to leave it active over the weekend so hid the upgrade option for now. Unfortunately sorry, this leaves debugging offline for the weekend but we'll bring it back early Monday. 😔

Thank you for your patience. The new environment is super exciting and powerful. It should let us offer even better services going forward. 

Hi,

I have now enabled the new environment but I get naming errors both on Algorithms (NameError : name 'QCAlgorithm' is not defined) and Notebooks (ModuleNotFoundError: No module named 'QuantBook').

I also get an window with the option of adding new imports needed but nothing seems to happen. Can you share the new imports that need to be added to existing Algos and Notebooks to have them working again?

Thanks!

Hey Francesco,

Add the following import to fix the QCAlgorithm issue:

from AlgorithmImports import *

That may fix your Research Notebook issue too. 

Best,

Aaron

“I also get a window with the option of adding new imports needed but nothing seems to happen.”

A couple of people have reported this Francesco; do you mind sharing the project with support? It might be an edge case we're not handling.

Is this with regards to the web-based IDE? I only ask because lately I've noticed I cannot hide the project navigation pane on e the left like I have been able to before and it really cramps the space on the coding and backtest results

Hi Aaron,
Thanks that fixes it for the Algorithm although I still have this error with the Notebook:
NameError: name 'QuantBook' is not defined
Do you know if there is a different import for the Notebook? I simply tried with import QuantBook but with no luck.

Hi Jared,
I'll send the details of my error also to the support. Thanks!

I sent these issues related to the above to support@quantconnect.com but got no reply back for 3 days now. I'm going to share them here maybe i get some help from the community. 

1. Debugging not working:

I get this error when i try and start the QC Debug service: Cannot read property 'port' of undefined

I tried to add a port and also to create a new project thinking this would be something that would happen to old projects but it does not. It's always the same.

If i try and start the backtesting with a breakpoint i get this error: connect ECONNREFUSED 51.161.86.24:32777

2. Forum support form does not work

I tried to submit this via the community forum but i get another error about the CKEditor.

3. Course tests require extra steps

Also now i have to add from AlgorithmImports import * to all the course lessons as they don't work without it anymore and none of the projects work either. 

Francesco, here is a link to the QuantBook class:

https://lean-api-docs.netlify.app/classQuantConnect_1_1Research_1_1QuantBook.html

You should be able to import it like the following (note I've not tested this):

from QuantConnect.Research import QuantBook

Hi Aaron,

Unfortunately it does not work either. 

/opt/miniconda3/lib/python3.6/site-packages/QuantConnect/__init__.py in <module>
    25 # Import the C# version of the current namespace
    26 del sys.modules["QuantConnect"]
---> 27 from clr import AddReference
    28 AddReference("QuantConnect.Common")
    29 from QuantConnect import *

ModuleNotFoundError: No module named 'clr'

Can anybody share a simple notebook working in the new environment?
I could use it as a base to understand what to change in my existing notebooks.

Thanks!
Francesco

Hi All

• Debugging works but is misleading – you need to press the Backtest button not the pop-up green play button. We'll try and address this today by wiring the green button to do the same action as the backtesting button.

• Research also had an issue that meant it didn't select the right kernel. It was resolved this morning, please stop the environment and restart it if cannot find QuantBook.

• Panel hiding coming soon James Hawkins. There's also a bug where if hide it using click border drag the panel disappears.

Thank you for your patience and feedback while we iron out the Beta 3.0 environment issues. We did not intend it for mass consumption yet! A lot more people picked up on the tiny message in debug panel than we expected 😂

Jared

Just an useful tip in case someone ran into an error similar to mine below. It's likely due to you have “Block third-party cookies” option selected in Chrome settings. Switched to “Allow all cookies” fixed it for me.

error loading webview: error: could not register service workers: notsupportederror: failed to register a serviceworker for scope ('https://9eec7e68-044b-4882-9c6b-38b32bb5f544.vscode-webview.net/insider/d372f9187401bd145a0a6e15ba369e2d82d02005/out/vs/workbench/contrib/webview/browser/pre/') with script ('https://9eec7e68-044b-4882-9c6b-38b32bb5f544.vscode-webview.net/insider/d372f9187401bd145a0a6e15ba369e2d82d02005/out/vs/workbench/contrib/webview/browser/pre/service-worker.js?v=4&vscode-resource-base-authority=vscode-resource.vscode-webview.net'): the user denied permission to use service worker..

The new IDE is just awesome. Many thanks for the great work as always Jared Broad .

Hi everyone,

Just tested out the new IDE with an algo that runs in 2.0. I saw it already has this appended to the top:

#region imports
from AlgorithmImports import *
#endregion

 but I received this error on backtest, thought I would contribute it here: 

During the algorithm initialization, the following exception has occurred: Loader.TryCreatePythonAlgorithm(): Unable to import python module ./cache/algorithm/main.pyc. AlgorithmPythonWrapper(): NameError : name 'QCAlgorithm' is not definedatclass Ocean(QCAlgorithm):===at Python.Runtime.PythonException.ThrowIfIsNull(IntPtr ob)at Python.Runtime.PythonEngine.ImportModule(String name)at Python.Runtime.Py.Import(String name)at QuantConnect.AlgorithmFactory.Python.Wrappers.AlgorithmPythonWrapper..ctor(String moduleName) at /LeanCloud/CI.Builder/bin/Debug/src/QuantConnect/Lean/AlgorithmFactory/Python/Wrappers/AlgorithmPythonWrapper.cs:line 74 in main.py: line 4NameError : name 'QCAlgorithm' is not defined

Also, I was unable to copy this text out of the editor (had to drag it) I guess the editor has its own clipboard? I also closed the console and am not sure how to get it back, oops.

Edit: It looks like backtest results page is not loading in now (was working before). 

Otherwise am excited for the transition. Looking forward to using 3.0 when it's ready.

Hey LE ; mind sending a support ticket in with the example code attached? Backtests of basic templates and others are working fine so we'll need to figure out the specific setup that caused it. It might be the environment or the code. 

Re: Backtest results; we deployed 3-4 times today if you can please retry and send through any issues with your support ticket 🙏 Thank you

Hi Jared,

I was unable to send a support ticket without a support a seat, but it seems to be working now. The error was pointing to line 4, so I added a blank line after #endregion in all my project files, and now it seems to work without issue? (Maybe some issue with python translation/interpretation - think I've had that before) Deleting the blank line does not seem to reintroduce the error. Hope my amateur debugging is of any help!

Backtest results are working again.

Two more non urgent notes: Will there be anyway to change the font size? And in dark mode, the second line in a plot is a dark color, somewhat hard to see. 

Cheers to the QC team on this upgrade!

LE, to change font size you can use VSCode's zoom in feature. 

You can access this via the VSCode command pallette, which you open with cmd/ctrl+shift+p once that appears, type in ‘zoom’ and select the zoom in command. 

You can bind this to a keyboard shortcut, but at the moment key bindings don't persist between sessions. The QC team will probably address this in a future release.

Thank you, ekz!

Did anybody experience issues in backtesting and debugging the algorithms in the new platform? 
Sometimes it seems that when I press the backtest button an earlier version of main.py is executed and not the latest one (even if I press build) and I have also issues in debugging the code. I would switch to the earlier platform while these models are figured out but the debugging is not available anymore on 2.0

Thanks!
Francesco