VSCode: Debug Strategies

[pharindoko]

Note: for support questions, please join our Discord server

• I'm submitting a ...
  [ X] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository

• Action taken (what you did)
  Created launch.json in VSCode with following settings

{
    "version": "0.2.0",
    "configurations": [

        {
            "name": "Launch Server",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/gekko.js",
            "cwd": "${workspaceRoot}",
            "preLaunchTask": null,
            "runtimeExecutable": null,
            "args": [
                "--ui",
                "--config", "config.js"
            ],
            "env": {
                "NODE_ENV": "development"
            },
            //"console": "internalConsole",
            "sourceMaps": false,
            "outFiles": []
        }
    ]
}

Set a breakpoint
Start to debug gekko.js and then get deeper into details to debug a strategy

• Expected result (what you hoped would happen)
  History data (local data) is available in history folder and will be loaded the same way as it does if I start gekko via commandline.
  No difference if I run it in a debug session or via commandline

• Actual result (unexpected outcome)
  I can debug into gekko.js and even import.js
  Issue:
  No local data or history data for back testing is available.
  When I try to run the importer to add additional data it fails I receive following error in Import.js

RECEIVED ERROR IN IMPORT 999433617504825
Child process has died.

Assumption - something wents wrong with backend (sqlite)
Can someone else try to replicate and see if it works ?

[gdomod]

same here. any help ?

[Nimrasol]

I made the same experience. Is there a solution available? Is there an other way to debug gecko with brake points? Thank you for the help!

[kalitas]

same here

[goldistan]

same here

[mikemichaelis]

I'm having the same issue, but discovered it has nothing to do with VS Code. If you execute node 8.10.0 in --inspect mode, gekko will not find any history data.

node --inspect gekko --ui

I also tried node 7.10.1 using the legacy debug protocol and it also fails to load historical data.

node --debug gekko --ui

[evertondanilo]

I found the bug:

Go to this file: Gekko\core\workers\dateRangeScan\parent.js

Original:

module.exports = function(config, done) {
  var debug = typeof v8debug === 'object';
  if (debug) {
    process.execArgv = [];
  }

Changed:

module.exports = function(config, done) {
  var debug = typeof v8debug === 'object';
  if (debug || config.debug) {  //LOOK HERE <<
    process.execArgv = [];
  }

So, what I've seen here is that when debugging we need to clear out the execArgv parameter. However the debug variable was set as false.

[askmike]

This was added here on purpose: #1666 by @mronus. Note @evertondanilo that this issue was opened before that PR was merged.

I don't use any of these tools in my debug flow and which way is best depends on how you are debugging I guess.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you feel this is very a important issue please reach out the maintainer of this project directly via e-mail: gekko at mvr dot me.