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
debug(cache): Add comprehensive logging for PVC cache debugging
Add detailed logging throughout the cache flow to diagnose the
TestCacheSingleRunWithPVC_SameName_Caches failure where Run3 with
a different PVC name incorrectly hits cache (expected COMPLETE,
got CACHED).
Logging added to:
- cache_test.go: Log execution states and cached_execution_id
- driver/cache.go: Log PVC names during fingerprint generation
- cacheutils/cache.go: Log cache key creation and query results
- task_store.go: Log SQL queries and returned tasks with fingerprints
This will help identify whether:
1. PVC parameters are being correctly resolved from DAG inputs
2. PVC names are included in cache key generation
3. Different PVC names produce different fingerprints
4. Database queries correctly filter by fingerprint
Related to PostgreSQL migration and V2 cache debugging.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
Signed-off-by: kaikaila <[email protected]>
"SELECT \"UUID\", \"Fingerprint\", \"MLMDExecutionID\", \"PipelineName\", \"Namespace\", \"RunUUID\", to_timestamp(\"CreatedTimestamp\") as created, to_timestamp(\"FinishedTimestamp\") as finished FROM tasks ORDER BY \"CreatedTimestamp\" DESC LIMIT 20;" \
0 commit comments