You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a hard issue to close but I'd like it if it was easier to follow the client update process in the logs:
It's certainly already possible with debug logging but requires a lot of reading and probably a fairly deep understanding of the components.
I'd like to see
the major specification steps (the ones required to see which branches the code took in validating metadata)
State changes in "trusted metadata set" with
local metadata loads
metadata downloads
...without any other logs getting in the way
This is specifically not a 1.0 blocker: just moving a TODO item from code to issue tracker
The text was updated successfully, but these errors were encountered:
jku
pushed a commit
to jku/python-tuf
that referenced
this issue
Jan 28, 2022
First TODO is now handled (or we have PRs already).
Second TODO is moved to issue theupdateframework#1804.
Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
This might be a hard issue to close but I'd like it if it was easier to follow the client update process in the logs:
It's certainly already possible with debug logging but requires a lot of reading and probably a fairly deep understanding of the components.
I'd like to see
...without any other logs getting in the way
This is specifically not a 1.0 blocker: just moving a TODO item from code to issue tracker
The text was updated successfully, but these errors were encountered: