Moritz Kiefer 4460cb5e08 Fix trace statement handling in DAML Script service (#7292) ... * Fix trace statement handling in DAML Script service This PR makes sure that we get both trace statements coming from the ledger client as well as from the ledger server. In the script service those are two different Speedy machines so we need to interleave them. This is a bit messy so let me explain the steps (apologies for not splitting it up but I think it’s easier to understand the motivation when it is a single PR): 1. Abstract over the tracelog interface. The ringbuffer doesn’t makes sense for our purposes and is annoying to clear. 2. Pass in the respective fields of `Machine` to `Conversions` instead of the whole machine. This is both a simpler design (passing around mutable objects scares me) and it allows us to assemble the fields from different machines. 3. Initialize the ledger machine with a simple ArrayBuffer tracelog. 4. After `submit` and `submitMustFail` copy the tracelog from the ledger to the client. fixes #7280 changelog_begin changelog_end * Address review feedback changelog_begin changelog_end		2020-09-01 17:15:48 +00:00
..
client	Add :json command to DAML REPL (#7202)	2020-08-21 14:53:06 +00:00
protos	Add :json command to DAML REPL (#7202)	2020-08-21 14:53:06 +00:00
server	Fix trace statement handling in DAML Script service (#7292)	2020-09-01 17:15:48 +00:00