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

JSON file path is not match between Get Start and openweave-code #8

Open
hevakelcj opened this issue Dec 29, 2018 · 1 comment
Open

Comments

@hevakelcj
Copy link

When I study happy follow page below:
https://codelabs.developers.google.com/codelabs/happy-weave-getting-started/#7

I found that loading pre-defined topology with access point (AP) and service nodes command is not correct.
this is what it says:
$ weave-state-load ~/happy/topologies/thread_wifi_ap_service.json
And the implementation should be:
$ weave-state-load ~/happy/topologies/standalone/thread_wifi_ap_service.json

Corresponding,
$ weave-state-load ~/happy/topologies/thread_wifi_ap_internet.json
Should be:
$ weave-state-load ~/happy/topologies/dynamic/thread_wifi_ap_internet.json

@Vyrastas
Copy link
Contributor

Vyrastas commented Jan 3, 2019

Hi @hevakelcj -

I'm unable to replicate this. When I follow the installation and setup instructions detailed on the Get Started page of that Codelab, the commands you reference work as written. The topologies in the happy repo are all in the topologies directory. They are only split into dynamic and standalone for the sample topologies included with the openweave-core repo, but the Codelab is designed to use the ones included with happy only.

jenniexie pushed a commit to jenniexie/happy that referenced this issue Mar 6, 2019
…assisted-pairing-failure to nest/master

Squashed commit of the following:

commit c6568679abd667b053b4716331d8a06b528c10d7
Author: james woodyatt <jhw@google.com>
Date:   Wed Jan 17 14:22:40 2018 -0800

    Correct merge error: retain patch from LwIP 1.4 to netif_create_ip6_linklocal_address.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants