joshuef/peruse

IPC error: StringError(Utf8("invalid utf-8: corrupt contents"))

happybeing opened this issue · 3 comments

happybeing commented

In Peruse WebID POC I'm intermittently getting the error:

IPC error: StringError(Utf8("invalid utf-8: corrupt contents"))

I think it happens immediately after accepting Peruse access request to my account while logging in.

happybeing commented

Update: interestingly after getting the above error I have the same symptoms as issue #95 so this may be the reason, not what I said there.

JPL1 commented

I also had this the first time I logged in, but it went away after I restarted. I often find I have to restart Peruse to get it connecting properly #53 - so not solved for me. IPC error ossible related?

joshuef commented

This is something we'd seen against the mock network. And we'd assumed it was a bug there, clearly that's not the case though 😞

(There's a JIRA for this, will link when I can find it).

Can anyone experiencing this please post the last ~50 lines of Peruse browser logs just after the failed login (as opposed to SAFE network logs), which should be found:

on Linux: ~/.config/Peruse/log.log
on OS X: ~/Library/Logs/Peruse/log.log
on Windows: %USERPROFILE%\AppData\Roaming\Peruse\log.log

It's not something I've been able to pin down at all yet (was happening seemingly at random on mock), so hopefully more logs should elucidate this.

Thanks @theWebalyst @JPL1 !