You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue reporter to provide a detailed description of the issue in the space below
When validating a model, if the error count goes beyond 100 (I've seen as high as 40K), then it attempts to display all the errors in the console which results in the workspace freezing and becoming unusable. Therefore, I believe that have a better way to handle the errors would be helpful to avoid situations such as that. Once the error count exceeds 100, then instead of attempting to display each error and causing the workspace to crash, it would be better if a warning message appeared that had a message saying something about how the error count exceeded the limit of 100, validation failed, and the individual error messages will not be displayed.
The text was updated successfully, but these errors were encountered:
Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
When validating a model, if the error count goes beyond 100 (I've seen as high as 40K), then it attempts to display all the errors in the console which results in the workspace freezing and becoming unusable. Therefore, I believe that have a better way to handle the errors would be helpful to avoid situations such as that. Once the error count exceeds 100, then instead of attempting to display each error and causing the workspace to crash, it would be better if a warning message appeared that had a message saying something about how the error count exceeded the limit of 100, validation failed, and the individual error messages will not be displayed.
The text was updated successfully, but these errors were encountered: