-
**Issue Description:**
The current exception handling in `NGramClusterer.class` within the Vicino library prevents proper reporting of exceptions. When an `ExecutionException` is thrown by `FutureTas…
-
I just ran into a scenario where instead of seeing an exception that informs me of an issue with my bytecode generation, I see a `StackOverflowError` instead.
The repeating part of the overflow is:
…
raner updated
4 months ago
-
Certain exceptions need to show up in the "error" field in the scoreboard, but do not.
It might be helpful if they showed up in a popup window.
-
I am encountering exceptions during logging, due to EF Core passing unserializable `state` data to `ILogger.Log()` calls.
Specifically, looking at the `SaveChangesFailed` log event:
https://gith…
-
When transforms or modifiers fail, Bowler prints an error, and stringifies the exception, but this doesn't always help understand what the actual problem is (sometimes it just prints the Node, which i…
-
Currently in Kadira we get lots of exceptions that look like this:
[client] Exception in tempalte helper:
As there is no more detail they all get grouped together which can be painful to wade th…
-
Currently, the `DefaultUnhandledExceptionsReporter` stores only one exception and the number of unhandled exceptions in an interval. However, this implementation lacks sufficient information for effec…
-
buster exception reporting will report 'undefined' unless an exception complies with buster.js by having a 'name' property. To display a message it also must have a 'message' property. This makes debu…
-
@troyhunt Do you want to put in sentry or similar into the mix? Allow for capturing and alerting on Exceptions?
-
## Search Terms
Crash, Maximum call stack size exceeded, fork-ts-checker-webpack-plugin
## Suggestion
Improve crash logs by dumping statements, file names, line number and everything that might h…