tangled.org
the default slog logger caused indigo/identity to emit logs when resolving identities. using a bespoke logger in the guard subcommand fixes this.
Signed-off-by: oppiliappan me@oppi.li
Monorepo for Tangled — https://tangled.org
guard: supress logging #745
closed
opened by
oppi.li
targeting
master
from
push-ykxtvrlpxwrl
expand 1 commit
hide 1 commit
guard: supress logging
the default slog logger caused indigo/identity to emit logs when
resolving identities. using a bespoke logger in the guard subcommand
fixes this.
Signed-off-by: oppiliappan <me@oppi.li>
boltless.me
I've moved part of the guard logics to internal server in #700 which also address this issue a bit (ignore all outdated title/description, see the commit.)
Do we want to move all guard logics to internal server instead? would be helpful in other directions too e.g. greeting with user handle in ssh -T
uhh why the comment is duplicated. I pressed the button once. I lost the network log after second comment so can't check what happend.
that could be interesting. perhaps we could convert the knot keys command to do something similar as well.
that change can be sumbmitted independent of the rest of the stack, it is a bit hard to merge now because it is it the middle of the other changes in that patch.
Can we merge the stack below the #684? #684 is there only to share my dev setup but I think all 702~701 are fine to merge.
this PR is no longer required!
closed without merging
I've moved part of the guard logics to internal server in #700 which also address this issue a bit (ignore all outdated title/description, see the commit.)
Do we want to move all guard logics to internal server instead? would be helpful in other directions too e.g. greeting with user handle in
ssh -T