In case anyone fancies diving into a tricky error while using SAFE for decentralising git repositories (that would be cool wouldn’t it), I’ve created an issue with details of how to reproduce it.
It might help just to have someone else run through this and discuss it with me, so don’t feel you need to be an expert (I’m not clearly ) to help with this. I’ll be happy to help anyone get set up, so it would be a useful learning for anyone who wants that.
The above actually shows how to reproduce two bugs. The second I haven’t looked into much yet, but by all means have a go at either. The second might be unrelated, although one bug often solves another.
Did you follow the instructions exactly - commands, environment variables etc?
I think so… though I’m down with flu atm so all is a bit foggy.
The only difference seemed trivial that nothing of ~/SAFE existed so I created the two folders and then _public/tests/data1/
Edit: you were prompting for git 2.19.1 … which I missed. That’s the only difference I can spot from the abc you laid down.
Simply, where those didn’t exist, I created them as empty folders - given that’s a common problem that location doesn’t exist.
You’re right, likely I wasn’t using a mounted SAFE Drive… just trying that now for the first time; though while the browser requests authorizing, there isn’t an obvious request from SAFE FUSE…