If we try to get children of a name by globbing name/* and it fails, we don't show any errors, we just show no children found.
This is because the error comes back as a "glob error item", in most cases we ignore glob errors since they can be about things we truly don't care to show to the user ( like globbing a/b// may return a glob error saying a/b/z/ is inaccessible which is mostly irrelevant) but I think we need to special case glob errors that are about the actual name we are trying to glob. Namespace client may need to change to accommodate this (e.g. if globing name/* and name is inaccessible, instead of a glob error item, the call to .glob() should return an actual error)
If we try to get children of a name by globbing name/* and it fails, we don't show any errors, we just show no children found.
This is because the error comes back as a "glob error item", in most cases we ignore glob errors since they can be about things we truly don't care to show to the user ( like globbing a/b// may return a glob error saying a/b/z/ is inaccessible which is mostly irrelevant) but I think we need to special case glob errors that are about the actual name we are trying to glob. Namespace client may need to change to accommodate this (e.g. if globing name/* and name is inaccessible, instead of a glob error item, the call to .glob() should return an actual error)
https://github.com/vanadium/browser/issues/18 might be enough to handle this.