Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[bug] incorrect start location in many nodes

See original GitHub issue

Input:

while (true) // Comment
{
};

Currently while node starts with test node location, but should be start with while keyword. Same for other control structures. It would be great if you show how to fix such things (send a PR with fix) and i will start fix it self and send new PRs. This would speed up problem solving.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

ichiriaccommented, Oct 25, 2018

I’ll try to explain how you can fix bugs when it’s simple. Your help is much appreciated !

1reaction

alexander-akaitcommented, Oct 25, 2018

Here my email : i.chiriac@yahoo.com, email me and we can continue to chat with skype or whatever.

My English is very bad 😄 It’s better for me to type than talk, sorry.

Top Results From Across the Web

Bug - Incorrect output value with multiple Subgraph instances

When multiple instances of a Subgraph node are added and then executed in a Visual Scripting Graph, the output value of the last...

Node.js Bug Or Am I Doing it Wrong? ES Modules [closed]

json file in the file's subdirectory! Originally I had asked: is there any way I could somehow be accidentally telling Node "switch back...

Loop Start and End nodes not in same workflow error (with ...

the full workflow that I am seeing the error “Loop start and end nodes are not in the same workflow”. The simplified workflow...

On premise Service Fabric Cluster remove node problem. #836

If the node is in Down error state, you can select "Remove node state" from the Explorer UI consol, this will place the...

Confluence will not start due to fatal error in Confluence cluster

If the problem occurs shortly after startup in a single-node (non-clustered) deployment and it wasn't caused by multiple deployments, see if clustersafety table ......