microsoft / microsoft/Power-Fx
LSP crash: Collection was modified; enumeration operation may not execute.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.4k
- Forks
- 358
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 3
Description
On .Net 4.6.2.
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.List1.Enumerator.MoveNextRare()
at System.Linq.Enumerable.WhereListIterator1.MoveNext()
at System.Linq.Enumerable.d__931.MoveNext()
at Microsoft.PowerFx.Intellisense.IntellisenseResult..ctor(IIntellisenseData data, List1 suggestions, IEnumerable`1 possibleOverloads)
at Microsoft.PowerFx.Intellisense.Intellisense.Finalize(IIntellisenseContext context, IntellisenseData intellisenseData, CultureInfo culture)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Microsoft.PowerFx.Intellisense.Intellisense.Finalize and IntellisenseResult..ctor, using the reported .NET 4.6.2 stack trace to trace which suggestions or possibleOverloads collection changes during enumeration. Done means the reported LSP scenario no longer raises InvalidOperationException; the issue names no source file or regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100