Yes I’ve rolled back the changes to Sunday in both repos (see tag
wip-getcontainerbug-goodcode) even though none of them seem able to affect this area. This wasn’t happening as late as yesterday evening, so I’m as sure as I can be that it isn’t due to my changes to the code. This is why I wondered if it was problems with the network again - especially as the symptom was identical to the first time.
Also, I haven’t touched the auth code at all in months. I was making superficial changes to
safe-containers.js in safenetworkjs.
I put that test
getContainer('_public') call into
bin.js to check before it gets to any of the code I’ve been working on.
Don’t you think the error itself is infeasible? How can a request to access
_public result in that error? I really don’t know how to debug this.
The error looks suspicious to me which is why I’ve asked for help. I could create a simplified example, but I expect it will work - how could it not? So I think whatever the issue is that I’m triggering, it is worth finding out what is actually happening to cause that particular error message, because I think it is either a bug in the API, or reporting the wrong error, regardless of how I’m causing it to happen (if indeed I am - as I say, reverting to the earlier code hasn’t changed this).
I don’t know how to debug that so if you can’t help it will delay me while I learn how. If you can’t help debug, can you maybe try reproducing it?