I’m having a problem with the local testnet faucet which was fine yesterday. I have git pulled, but don’t think that’s the reason. This has been working flawlessly for weeks.
Is anyone else running local testnets, and have you seen this issue, any clues. Thanks, more here:
@chriso I’m puzzled (as so often) about the above. safenode-manager says the faucet is running but there’s no process called faucet so I don’t know if its config is messed up.
I’ve been trying to ‘stop’ and ‘reset’ but that says I need to be root, and when I do that I can’t run cargo. Is there a simple manual way for me to clear things out to start again in case the services settings have become messed up?
I’m not sure why there would be no faucet process, but stop and reset do not apply to local networks.
Everything for operating on local networks is under the local subcommand.
Ah thanks, I tend to forget that and think that building with ‘local discovery’ is what flips the switch to local.
I’ll try and remember next time, but I rarely look at the options because my aliases take care of everything normally.
I don’t know what might have borked things.
Can you tell me if the local wallet is kept isolated from any regular wallet on the same machine?
I’ve tended to assume they will mess each other up, and so I wipe .local/share/safe whenever I start a local testnet, but developers will need a better solution than that so they can test locally and on public networks interchangeably.
It would be good to have guidance on things like this, on how to develop apps, in addition to documenting the APIs.
I think you’re referring to the wallet on the client side here? As opposed to the node wallets?
At the moment, the client wallet wouldn’t be isolated from another client wallet that was being used with a remote network. There’s only one of them, as far as I’m aware.
Correct, that’s an issue then. Is there a good way for me to raise this and similar things around development. It doesn’t seem suitable for github but I don’t know where else.
I think if you pointed out where specific documentation was lacking for the APIs, those would be fair as Github issues. Also, some kind of isolated wallet I think would be good to add as an issue.
As for guidance on app development, I’m not sure about that. I’d imagine it’s something that people like Jim will be wanting to address seriously at some point before the October launch.
@JimCollinson any thoughts 