Historically there was an oversight (my bad, alas) where the nodeErrorToFrontendError didn't handle the case for NoUserFound and instead of emitting a FrontendError it's simply exploding with an undefined.

The reason why that was left there was that I wasn't sure about how to represent the error to the frontend (without leaking information etc) and I think I have simply forgot, and things got merged with that.

We should remove that and also switch to use Gargantext.Prelude in that module, so that uses of undefined would be marked as warnings at compilation time; if that was the case, I'd have noticed (hopefully 😉 ).