Simon Tretter

I found a "solution" ;-), it's about the mdns query in my case. especially because I have more than one network device, even though [mdns](https://github.com/mafintosh/multicast-dns) should broadcast on all devices:...

I've seen there is also another PR hanging arround regarding this issue. I've solved this for me now by: 1.) disabling progress updates globally via nuxt.config: ``` axios: { progress:...

hi @manniL, my last comment is more like a different approach, by just disabling the module's indicator and set up my own. Would you like me to adapt these changes...

I ended up with following error object: ```ts const config = error.response?.config || error.config; err.response = { data: error.response.data, status: error.response.status, statusText: error.response.statusText, headers: error.response.headers, config: config && { url:...

Bascially it would be just here: https://github.com/googleapis/gaxios/blob/bf6afebe9bb50261d0aed5ae128853f977682773/src/retry.ts#L73 to chagne this line to: ```ts const backoff = config.backoffHandler && config.backoffHandler(err) || new Promise(resolve => { setTimeout(resolve, delay); }); ``` and backoffHandler...

Yes, in this case you can do whatever you want to do... Including exponential back off

For everyone who is using nuxt, here is a workaround: https://github.com/vuejs/vue/issues/9847#issuecomment-626154095

Related issue on my side: I cannot use .on().. as it says on is not a defined method, I guess because it cannot find the corret import of eventemitter

Looking into similiar issues on our end right now. If you find something, let me know please!

 this looks quite crazy, I will do some more tests tomorrow to see if it is really related to the cleanup method in node-cache.