#recursive dagql calls without the output
1 messages · Page 1 of 1 (latest)
here's an example....
I end up with a red error, which is confusing to the user.
and even if it was a WARN, it's still way too much information (it's akin to logging each syscall)
Here's my actual usecase to illustrate how it'll affect users.
it seems very similar to https://github.com/dagger/dagger/issues/11604 🤔
looks like there's a span.Ignore? Maybe I can set this when making my sub call?
@random wigeon look into Check.run similar problem i think
interesting.... do I need to create a new span, something like https://github.com/alexcb/dagger/blob/34cffaeeda3951b2c4f1285db8f8dc6111e7c30d/core/checks.go#L137 ?
thanks for that! I think this does it for me:
ctx, span := Tracer(ctx).Start(ctx, fmt.Sprintf("file %s", file),
telemetry.Internal(),
)
defer telemetry.EndWithCause(span, nil)