Sean R. Abraham

Thanks for that, @johejo. I'm trying to figure out how in the world to get this working in a Bazel context, in which we use a third party JS gRPC...

This repo seems to effectively be dead. I've had better luck with this fork lately. It includes some fixes from the last 4 years. https://github.com/jayked/MMM-GoogleTasks

(This may be off-topic, since actually the problem I observed is one in the live fork of this repo (jayked). This jgauth repo doesn't seem to have the same issue.)...

I dug in a bit more tonight. I found a way to reliably reproduce the problem and I came up with a fix: https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/pull/238 The problem can be reliably reproduced...

Thanks! I can imagine a few ways forward. Maybe the best would be to try to have the fetch call distinguish the type of HTTP error. You could reasonably fail...

Oh yeah, true, I should've called out 401. I'm a total novice with Node and JavaScript generally, but if it's easy enough to get a status code from the failed...

@klaernie here's an enhanced version. Let me know what you think. I don't love how complicated the error checking becomes, but oh well :S. Also I'm not sure what would...

Thanks! I've been using this module for a while now and I really like it, so I'm happy to help give back :D. I'll enhance that code snippet a bit...

@riannucci this issue can be closed

I started consistently seeing this problem today, and it's because `codecov/codecov-action@v4` is now (newly?) connecting to `ingest.codecov.io`. We use a step in our runners (step-security/harden-runner) that blocks calls to unallowed...