Skip to content

fix(hybrid cache): Only call apply on child caches in the success state #14428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gabe-l-hart
Copy link
Contributor

There are conditions where the two child conditions can end up with different status values based on the logic in the init_update constructor for llama_kv_cache_unified_context which can conditionally set status to either LLAMA_MEMORY_STATUS_SUCCESS or LLAMA_MEMORY_STATUS_NO_UPDATE.

See full discussion:
#13550 (comment)

Branch: HybridCacheApplyLogic

There are conditions where the two child conditions can end up with
different status values based on the logic in the init_update constructor
for llama_kv_cache_unified_context which can conditionally set status to
either LLAMA_MEMORY_STATUS_SUCCESS or LLAMA_MEMORY_STATUS_NO_UPDATE.

See full discussion:
ggml-org#13550 (comment)

Branch: HybridCacheApplyLogic

Signed-off-by: Gabe Goodhart <[email protected]>
@ggerganov
Copy link
Member

Could you confirm that #14438 also works?

I think it is better to make apply() work with and without updates, so that we don't have to add extra logic in the "hybrid" memories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants