WRN_GeneratorFailedDuringGeneration isn't helpful without a StackTrace
See original GitHub issueI currently have a source generator that fails with:
CSC : warning CS8785: Generator 'MySourceGenerator' failed to generate source. It will not contribute to the output and compilation errors may occur as a result. Exception was of type 'ArgumentOutOfRangeException' with message 'Specified argument was out of the range of valid values.'
I think providing a StackTrace will be very useful.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:14 (12 by maintainers)
Top Results From Across the Web
NullPointerException in Java with no StackTrace
The exception that is being logged has overloaded some methods to obscure the stacktrace. If that is the case, the exception won't be...
Read more >Is it good practice to use NoStackTrace in scala?
This stack trace is very helpful when debugging problems to try to figure out where things are getting called from. One of the...
Read more >Should a stack trace be in the error message presented to ...
To us, a stack trace looks like an extremely useful piece of information to provide a developer. To a user, it looks like...
Read more >Programming without a stack trace: When abstractions ...
This stack trace includes a lot of not-very-useful information related to reflection from the JUnit test framework.
Read more >Stack Trace: How to Debug Your Application With a ...
A stack trace can tell you a lot about the health of your application. Learn more about using a stack trace's valuable info...
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
@xakep139 We don’t currently have the resources to work on resolving this, but if someone submitted a pull request to implement the behavior described in https://github.com/dotnet/roslyn/issues/48008#issuecomment-1341131212 it would significantly improve the timeline for delivering this fix. 😄
Folks, were there any updates on that issue?