Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

trigger-service log level

See original GitHub issue

I’m using trigger-service-1.18.0.jar and can see logs in DEBUG level. for example this secion in the code ( from trigger/Runner.scala file):

freeTriggerSubmits(clientTime, v = updateWithNewState) .leftMap( _.expect( "TriggerRule new state", { case DamlTuple2(SUnit, newState) => logger.debug(s"New state: $newState") newState }, ).orConverterException )

prints in DEBUG mode the content of the contract. How can that be avoided? How can I control the logging level of the service?

Issue Analytics

State:
Created 2 years ago
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

cocreaturecommented, Mar 3, 2022

that’s right, we set it explicitly in the sdk config so it doesn’t matter what is in the JAR https://github.com/digital-asset/daml/blob/b2d6f8014c12848cc8f9f3537c5de4bc1732b504/release/sdk-config.yaml.tmpl#L85

0reactions

stefanobaghino-dacommented, Mar 3, 2022

@moritzkiefer-da are you aware of whether this is done on purpose to avoid issues with the SDK assistant?

no by accident

Ok, thanks. I assume this means that putting it explicitly into the JAR will not result in problems with the SDK assistant (that we know of). Let me know if my assumption is incorrect.