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

Intra-conductor link propagation#2043

Open
maackle wants to merge 6 commits intodevelopfrom
intra-conductor-link-propagation
Open

Intra-conductor link propagation#2043
maackle wants to merge 6 commits intodevelopfrom
intra-conductor-link-propagation

Conversation

@maackle
Copy link
Collaborator

@maackle maackle commented Jan 6, 2020

PR summary

Adds a test that demonstrates whether or not links can propagate between instances of the same DNA on a single conductor. The viability of writing in-memory tests, and scaled up final-exam tests, relies on this result.

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

)

const posts2 = await alice.call('app2', 'simple', 'get_my_links',
{ base: alice.info('app2').agentAddress, status_request: 'Live' }
Copy link
Contributor

@StaticallyTypedAnxiety StaticallyTypedAnxiety Jan 15, 2020

Choose a reason for hiding this comment

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

Hey just trying to figure out what is happening because I wanted to take a look at it.

Should this be alice.info('app1').agentAddress? only asking because at this point we wont receieve any results from posts1 or posts2 because the link was created with a different agentAddress.

Context : tried printing out the addresses of these two agent addresses and are the same

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

omg...yes it should be. I just fixed it, let's see what the test says now..

@maackle maackle marked this pull request as ready for review January 21, 2020 06:35
@maackle
Copy link
Collaborator Author

maackle commented Jan 21, 2020

Turns out it works just fine 🤦‍♂️

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

2 participants