debug: allow debug from remote cache config #6076
Conversation
|
Leaving draft for now as there seems to be an extra level of indirection when debugging remote source, that comes from output index being embedded into the cache key. I was aware of output index being stored as a separate value only in bolt but bit unexpected how these behave differently even in the |
Signed-off-by: Tonis Tiigi <[email protected]>
This adds extra level of indirection to the cache keys debug, making it more verbose but making sure that same digests are reported for remote cache. Signed-off-by: Tonis Tiigi <[email protected]>
tonistiigi
force-pushed
the
cache-debuginfo-db-remote
branch
from
dbb57d8 to
80e6c06
Compare
In order to fix this, I added the same indirection to the boltdb debug as well, so that both backends generate matching keys. Also added extra commit for better output:
|
Grouping the link digests to parent side (links pointing to current node) makes more sense than children side (links pointing to next nodes). This also reduces the duplicates in the output as previously same digest link could need plaintext under multiple nodes. Signed-off-by: Tonis Tiigi <[email protected]>
tonistiigi
force-pushed
the
cache-debuginfo-db-remote
branch
from
80e6c06 to
ac9317b
Compare
follow-up to #6061
Allows debugging from remote config passed via POST request in addition to debugging local cache store.