Skip to content

Conversation

@gabe-l-hart
Copy link
Collaborator

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.

@gabe-l-hart
Copy link
Collaborator Author

@ggerganov Confirmed, #14438 also fixes the issue. Closing this one in favor of it

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