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.
multi-document error triggered incorrectly
See original GitHub issueIf the first non-comment line of a file does not contain a :, it will incorrectly trigger the multi-document error.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Problems with clustered Mongodb 4.x multi-document ...
I have a problem with MongoDB cluster when it comes to use ... error during query :: caused by :: Transaction 4 has...
Read more >Strange behavior of Multi-Document Transaction
I'm just experimenting with transaction to understand how it works and to foresee and prevent all possible errors.
Read more >MongoDB Multi-Document Transaction Fails When ... - Percona
This feature has caused multi-document transaction writes to fail for one of my customers. In this blog post, we will look into the...
Read more >C# Multi-Document Transaction Error - MongoDB
I use 5 threads to execute transactions in parallel and encounter lots of 251 errors: MongoCommandException, 251, “NoSuchTransaction” ...
Read more >WriteConflict error with MongoDB #12814 - prisma ... - GitHub
I have fixed this issue as well, the solution was to use MongoDB to create the collections before seeding. The problem is, when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s not valid. But the validation should generate a specific error about that instead of highlighting the entire file and complaining about multi-document files being invalid.
Yes, the fix will be in the language service. We’ve been tracking all the bugs here instead of splitting them up.
Fixed in https://github.com/microsoft/azure-pipelines-vscode/releases/tag/v1.155.0