Moritz Kiefer 6d3ae219d1 Improve logging and debugging of DAML triggers (#3210) ... - We now display `trace` messages so they can be used for debugging. - I’ve removed the log message from the low-level API since it is confusing as it is not exposed via the high-level API and somewhat redundant since you can use `trace` for debugging. If there is a demand for proper logging support we might want to add it back at some point. - We now display errors from speedy properly. This is mainly important for calls to `error` since we previously lost the error message. - Logging messages go through a proper logging library now and the internal debugging stuff is only displayed at debug level so not by default. - We log failed completions at warning level to ease debugging.		2019-10-17 10:21:56 +00:00
..
src/main	Improve logging and debugging of DAML triggers (#3210)	2019-10-17 10:21:56 +00:00
BUILD.bazel	Improve logging and debugging of DAML triggers (#3210)	2019-10-17 10:21:56 +00:00