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

Instantiate instance when adding through admin interface #1067

Merged
merged 37 commits into from
Mar 17, 2019

Conversation

maackle
Copy link
Collaborator

@maackle maackle commented Feb 28, 2019

This PR has become a collection of improvements needed/useful for Holo interceptr:

  • Actually instantiate instance when creating through admin interface (the original intent of this PR)

  • Use Content-type: application/json for remote signing service HTTP requests

  • Check for duplicate IDs during integrity check

  • I have added a summary of my changes to the changelog

@willemolding willemolding self-requested a review February 28, 2019 22:35
@maackle maackle changed the title Start instance when adding through admin interface Instantiate instance when adding through admin interface Feb 28, 2019
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.

Yep 👍

@willemolding willemolding self-requested a review February 28, 2019 23:31
zippy
zippy previously requested changes Mar 1, 2019
Copy link
Member

@zippy zippy left a comment

Choose a reason for hiding this comment

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

This looks good, except please look into the windows CI fail. It looks like it may be a real issue.

@maackle
Copy link
Collaborator Author

maackle commented Mar 6, 2019

Yeah, this does seem to have a legitimate problem, but I'm still stumped on it. It's Windows-only and seems to be because of some invalid state: https://travis-ci.com/holochain/holochain-rust/jobs/182848921

@thedavidmeister
Copy link
Contributor

@maackle could you take those three things outlined in the PR description and deliver them one at a time?

that might help us isolate the windows issue while unblocking 2/3rds of the work (lucky dip)

@willemolding
Copy link
Collaborator

Running these tests locally I was unable to recreate the error that is seen in CI. I ran the tests over 10 times in a row and it passed every time.

This suggests the error is due to some specifics of the CI environment. I suggest we disable the test for windows in the CI and make note to revisit it at a later date.

@@ -1182,28 +1197,52 @@ type = 'http'"#,
}

#[test]
#[cfg(not(windows))]
Copy link
Contributor

Choose a reason for hiding this comment

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

@willemolding please use #[cfg(feature = "broken-tests")] rather than elide for windows

otherwise there is no way of knowing what is permanently/by design not applicable to windows and what is a poor test

Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a way to do that but also have it run for the other non-windows OS?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, I would like to keep the test in for our Linux tests on CircleCI. We definitely have to log this with an issue for future investigation and we could also just link this PR in a comment on this line. But I definitely prefer #[cfg(not(windows))] over #[cfg(feature = "broken-tests")] in this case.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@thedavidmeister made the change you suggested in Mattermost #[cfg(any(not(windows), feature = "broken-tests"))]. CI is passing looks like we are all good

@zippy zippy self-requested a review March 14, 2019 02:50
@zippy zippy dismissed their stale review March 14, 2019 02:52

becasue it's no longer relevant

@maackle
Copy link
Collaborator Author

maackle commented Mar 14, 2019

@thedavidmeister sorry just seeing your comment

could you take those three things outlined in the PR description and deliver them one at a time

The only important thing needed for Holo is the first item, which this PR was originally created to address, and the test failure is definitely due to that change, which you can see from the earliest commits in this PR. The rest is just nice-to-haves. So, if the main benefit of splitting this up is to unblock the other two points, I don't see this as worthwhile, since the other two points are not pressing.

@thedavidmeister
Copy link
Contributor

@willemolding @maackle all good, approved with the any flag for that broken test

@thedavidmeister thedavidmeister merged commit a762d23 into develop Mar 17, 2019
@zippy zippy deleted the auto-start-instance branch July 5, 2019 13:30
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.

6 participants