Patrik Bäckström
Patrik Bäckström
Would be super duper if this was merged!
I'm running into the same issue with the example code from the documentation. My document doesn't even open without a repair which result in the entire content of the document...
I had the same issue before, and it's discussed here: https://github.com/damienbod/angular-auth-oidc-client/issues/1566
I'm not sure Google actually fully supports OIDC yet. I might be wrong because I honestly don't know exactly what is required. But, for example, they always return an opaque...
They do however have a revocation endpoint. So I guess you should distinguish between providers with and without revocation endpoints and then logoff locally with .logoffLocal() to clear your storage...
Thanks for the quick reply. I found out a few things and I'll try to summarise them here. Ask me to clarify if needed, because this issue kinda changed direction....
+1 on this. Why is the task not exposed? Typescript complains about it. I guess a try catch in the schedule() callback would solve the issue but why not make...
Not sure what the status of this PR is, but it seems to fix the issues with error handling for me. Without this fix, sometimes the EPIPE error is not...
Some more information. I've added a test case which passes a too large stream through scanStream (which was my initial problem). The fix suggested in this PR helps in catching...