-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
-
NDS Sprint 39
Now that we have multiple modules in the UI, it might be nice to get a bit more info on where potential errors are coming from.
In most cases, the file name should be enough, but for shared code we might glean a bit more information from the context under which the error occurred.
The above is true, but there are lots of blank log messages in the container logs that will need to be addressed before we can modify the message contents.
- mentioned in
-
Page Loading...