22 bytes when something like 537680268 bytes are really expected...
This leads to a positive cache hit and the rest of my workflow continues as if the cache object has been restored when it really wasn't in the s3 bucket at all. Later in the workflow everything fails when if I had known the hit was incorrect, I could have build the asset in the workflow.
These changes add a cache-size output to the action so that other steps can decide if they want to trust a cache hit.
Changes
I'm seeing some cache-hits that are basically empty?
22 bytes when something like 537680268 bytes are really expected...
This leads to a positive cache hit and the rest of my workflow continues as if the cache object has been restored when it really wasn't in the s3 bucket at all. Later in the workflow everything fails when if I had known the hit was incorrect, I could have build the asset in the workflow.
These changes add a
cache-size
output to the action so that other steps can decide if they want to trust a cache hit.Fix Issues