Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrapper has no active children left - bootstrap has failed #401

Open
hunterlester opened this issue Oct 24, 2018 · 1 comment
Open
Labels

Comments

@hunterlester
Copy link
Contributor

Reproductions steps:

  • Run a local test network
  • Execute browser and connect to test network
  • Approve authorisation request when prompted
  • Run API playground, create an app, authorise it, and connect it to network using loginFromUri
  • The first connection should be successful
  • Run loginFromUri again and it should fail with a -2000: Unexpected (probably a logic error): Could not connect to the SAFE Network in API playground client and a Bootstrapper has no active children left - bootstrap has failed in the terminal running the browser.
  • Then execute another application, like web-hosting-manager, and it should successfully connect to network and you'll observe a 5th client connection in the safe_vault --first terminal.
@hunterlester hunterlester self-assigned this Oct 24, 2018
@hunterlester
Copy link
Contributor Author

I'm still experiencing this error after running at least 8 nodes, I tried 25 as well, and making sure that white listed config properties are null and not [ ].

For reference:

safe_vault.crust.config
{
  "hard_coded_contacts": [],
  "whitelisted_node_ips": null,
  "whitelisted_client_ips": null,
  "force_acceptor_port_in_ext_ep": false,
  "dev": {
    "disable_external_reachability_requirement": true
  }
}
safe_vault.routing.config
{
  "dev": {
    "allow_multiple_lan_nodes": true,
    "disable_client_rate_limiter": true,
    "disable_resource_proof": true,
    "min_section_size": 10
  }
}
safe_vault.vault.config
{
  "dev": {
    "disable_mutation_limit": true
  }
}

I can successfully create another connection in the API playground if I create a new app, by changing the name and vendor credentials, etc.

Why this is an issue is because developers need to refresh a tab when testing code, which might consist of connecting an app to the network, which has already been connected.
This is not the case on Alpha 2. A dev can run loginFromUri multiple times on the same URI without error.

@hunterlester hunterlester removed their assignment Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant