Long key gets truncated in the UI

My workflow tries to improve cache coherence by using hierarchical keys, consisting of a fixed prefix followed by two hashes from differently variable file sources. This results in a long primary key, but then the key appears to be effectively truncated accordingly to a log message, like in this run:

  with:
    path: ~/.cargo/registry
    key: Linux-cargo-registry-v1-2ac2a43cb7f80b945a11345b0eb9f4ff41596ba78129ad7cb130f7023f302239-91eba4bcc27b55c7ecf9bef264ba33101e7c0f7a4eb56f1f676a8e4f4da54f45
    restore-keys: Linux-cargo-registry-v1-2ac2a43cb7f80b945a11345b0eb9f4ff41596ba78129ad7cb130f7023f302239-
  Linux-cargo-registry-v1-
  
  env:
    GIT_AUTHOR_NAME: GitHub CI
    GIT_AUTHOR_EMAIL: [redacted]@users.noreply.github.com
    GIT_COMMITTER_NAME: GitHub CI
    GIT_COMMITTER_EMAIL: [redacted]@users.noreply.github.com
Cache Size: ~122 MB (128144670 B)
/bin/tar -xz -f /home/runner/work/_temp/49b4284a-c2a3-42ae-8448-a3a1e9cc9ed2/cache.tgz -C /home/runner/.cargo/registry
Cache restored from key: Linux-cargo-registry-

Perhaps some script unwittingly applies pretty printing with word wrapping to a YAML file somewhere?

[gimenete]

Ok, found the issue. A fix is done, pending of being deployed.

[mzabaluev]

Long keys are displayed correctly now, thank you!