InvalidOperationException during build

[FantasyTeddy]

Description

In some of my projects I get the following error when building:

CSC : warning AD0001: Analyzer 'FluentAssertions.Analyzers.CollectionShouldHaveCountAnalyzer' threw an exception of type 'System.InvalidOperationException' with message 'This operation does not apply to an empty instance.'.

My guess is that the following IsEmpty check should happen before Peek():

fluentassertions.analyzers/src/FluentAssertions.Analyzers/Utilities/FluentAssertionsCSharpSyntaxVisitor.cs

Lines 74 to 78 in 686a33b

	var member = Members.Peek();
	if (Members.IsEmpty)
	{
	// no op
	}

If you need me to provide more information, let me know how and I will see what I can do.

Versions

• FluentAssertions.Analyzers 0.11.3
• .NET Framework 4.6.1

[Meir017]

can you provide a minimal code sample that will reproduce this error?

[FantasyTeddy]

Unfortunately not, because I don't know what's causing this to happen. The Debug output is not very informative and only tells me what I copied above.
How could I trace this down to see where the exception actually happens?

[Meir017]

@FantasyTeddy just released 0.11.4

[FantasyTeddy]

Unfortunately my guess was incorrect, I still have this exception in two of my projects with the new version...

[Meir017]

Could you create a repository with your code?

[jnyrup]

Note: It seems that error message is only used for:

• ImmutableQueue.Peek()
• ImmutableQueue.PeekRef()
• ImmutableStack.Peek()
• ImmutableStack.PeekRef()
  https://github.com/dotnet/corefx/search?q=InvalidEmptyOperation&unscoped_q=InvalidEmptyOperation

[FantasyTeddy]

The code base I am working with is business code from our company which unfortunately cannot be made public. I can do some digging if you give me some hints how I can get more information about this exception.

[csoltenborn]

I have the same issue, my repository is OS:

https://github.com/csoltenborn/GoogleTestAdapter

See build instructions in the Wiki...

[Meir017]

@csoltenborn is this still an issue?

[csoltenborn]

Sorry, can't comment on that - I moved on to different things... Meir Blachman ***@***.***> schrieb am So., 28. Mai 2023, 04:18:

…

@csoltenborn <https://github.com/csoltenborn> is this still an issue? — Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACWCQDYMQDV6LZOIYAKJFTXIJVUDANCNFSM4FQGJHEQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>