Skip to content

fix: rename cache key for tree details builds to avoid key collision#1849

Open
gustavobtflores wants to merge 1 commit intokernelci:mainfrom
gustavobtflores:fix/tree-details-cache-key-collision
Open

fix: rename cache key for tree details builds to avoid key collision#1849
gustavobtflores wants to merge 1 commit intokernelci:mainfrom
gustavobtflores:fix/tree-details-cache-key-collision

Conversation

@gustavobtflores
Copy link
Copy Markdown
Contributor

Description

Fixes a cache key collision between get_tree_details_builds and get_tree_data(data_type="builds"). Both functions used the identical cache key "treeDetailsBuilds", causing the summary endpoint to populate the cache with dict rows. When the builds endpoint subsequently accessed that cache, get_tree_data tried to read those dicts as tuples via positional indexing row[0], triggering KeyError: 0.

Changes

  • Renamed get_tree_details_builds cache key from "treeDetailsBuilds" to "treeDetailsBuildsDirect" to avoid collision with get_tree_data

@gustavobtflores gustavobtflores self-assigned this Apr 10, 2026
@gustavobtflores gustavobtflores added the bug Something isn't working label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant