Skip to content
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.

Fix holding-list/eavi mismatch bug for Update entries #2204

Merged
merged 2 commits into from
Jul 31, 2020
Merged

Conversation

zippy
Copy link
Member

@zippy zippy commented Jul 29, 2020

PR summary

fixed bug in calculating entry address of a Content EntryAspect

testing/benchmarking notes

( if any manual testing or benchmarking was/should be done, add notes and/or screenshots here )

followups

( any new tickets/concerns that were discovered or created during this work but aren't in scope for review here )

changelog

  • if this is a code change that effects some consumer (e.g. zome developers) of holochain core, then it has been added to our between-release changelog with the format
- summary of change [PR#1234](https://github.com/holochain/holochain-rust/pull/1234)

documentation

Copy link
Collaborator

@lucksus lucksus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel pretty certain, this change is correct - and the old version was not.

Some(ref updated_entry) => updated_entry.clone(),
None => header.entry_address().clone(),
},
EntryAspect::Content(_, header) => header.entry_address().clone(),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, for a Content aspect, the base (=entry_address) is always exactly the address of that content - even in the case of this entry being an update to another one.

@zippy zippy marked this pull request as ready for review July 31, 2020 13:58
@zippy zippy merged commit 40fc749 into develop Jul 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants