Skip to content
This repository has been archived by the owner on Jun 25, 2021. It is now read-only.

Patch for Vault Handle Put behaviour; #424

Merged

Conversation

benjaminbollen
Copy link

send back put response to Client;
on FailedToStoreData from ManagedNode with different data, apply patch

Review on Reviewable

send back put response to Client;
on FailedToStoreData from ManagedNode with different data, apply patch
@maidsafe-highfive
Copy link

r? @inetic

(maidsafe_highfive has picked a reviewer for you, use r? to override)

@benjaminbollen
Copy link
Author

r? @dirvine

@maidsafe-highfive maidsafe-highfive assigned dirvine and unassigned inetic Jun 25, 2015
@benjaminbollen
Copy link
Author

successfully confirmed consistent behaviour for routing example with this patch; should fix PutResponse on REply to actual client even in big networks -- not tested on big enough network to confirm

@benjaminbollen
Copy link
Author

Also successfully passes the self_authentication example;

conclusion: this PR patches routing to ensure that Vaults Safecoin measurement is not explicitly broken;

we can only explicitly test the safecoin farming rate after the payload-issue is resolved in Vaults

resolves #423

@dirvine
Copy link
Member

dirvine commented Jun 25, 2015

Reviewed 1 of 1 files at r2.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.


Comments from the review on Reviewable.io

dirvine added a commit that referenced this pull request Jun 25, 2015
…edToStoreData

Patch for Vault Handle Put behaviour;
@dirvine dirvine merged commit 7fc0b9a into maidsafe:master Jun 25, 2015
@benjaminbollen benjaminbollen deleted the patch_routing_handle_FailedToStoreData branch August 14, 2015 11:28
maqi pushed a commit to maqi/routing that referenced this pull request Oct 6, 2016
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.

None yet

4 participants