Can't debug findOne results in VSCode when instance is populated with related OneToMany / ManyToMany relation.

[sebastiaanviaene]

Describe the bug

• Since we switched to Mikro v6 we noticed some very weird behaviour when running findOne queries.
• This only happens in VSCode as far as we know.
• When I try to hover over the result it does not show anything
• When I try to open the local variable in the sidebar of VSCode it keeps loading
• The node process responsible for the debugger also spikes to 100% CPU and is clearly stuck
• Not populating the instance works and using find to get a list also works
• My colleague tried using WebStorm / Chrome debugger and there it works without issues

I've created a repo forking the reproduction one and with minimal changes was able to reproduce the behaviour (as you can see in the image above)

Reproduction

Forked from mikro-orm/reproduction:

https://github.com/sebastiaanviaene/mikro-orm-reproduction

What driver are you using?

@mikro-orm/sqlite (reproduction)
@mikro-orm/postgresql (my project)

MikroORM version

tried 6.1.7 & 6.2.1 in my project, the reproduction one uses next

Node.js version

20.9.0

Operating system

MacOS

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
• The provided reproduction is a minimal reproducible example of the bug.

[B4nan]

Sounds like something you should report to vscode instead of here. Will take a look later today, but since it works fine in webstorm and not in vscode…

[B4nan]

I do call inspect internally, that's true, but from inside the inspect method - it needs to be triggered from outside first. It's clearly used when processing the entity itself, not just for its properties, just verified that as well locally.

[connor4312]

Oh, you're right. I didn't know that started happening.

Looks like console.log passes a depth of 2 when calling the function. The VS Code doesn't pass any depth when it's called as I implemented that before depth was added as a standard argument in Node 16. We should probably pass that too, added in microsoft/vscode-js-debug#2007

[B4nan]

Ok, so it was all about a missing depth, now I get it. Did the same in the ORM, that sounds reasonable: f706c06.

[connor4312]

yea, I'm guessing there's some cycles in the object and an undefined depth made it try to recurse infinitely

[sebastiaanviaene]

Thanks for taking care of this guys, appreciated!