Miles Richardson

thanks for fast response. I'm a bit confused (sorry, new to go).... should I create the custom dialer when starting the proxy, or for every new connect tunnel?

I noticed the same problem of **high cpu usage in code helper** today. Uninstalling this extension solved the problem. In fact I did not even realize I had this extension...

@quezak As a temporary solution, you can install from git from master. This repository was transferred to me by @dgrtwo @dgrtwo - Do you have access to some pypi account...

I have personally never used parse-server for pushes, so I'm not sure what the support is support to be like here. This might be a question for the parse-server repo...

I'm not personally using LiveQuery and am therefore not familiar with it. But I welcome anyone who is to open a pull request.

@SovcikJoe I'm not sure why your `__eq__` is not working, however I have not looked into it much. But I would be VERY hesitant to add this functionality. Since Python...

@KevinHu2014 All the "default" Parse classes are prefixed with `_`, e.g. `_User`, `_Role`, and in this case, `_Installation`. You query them like you would any other class.

This will become a more urgent issue as [Node 18 moves to active status in October](https://nodejs.org/en/about/releases/). In Node 18, native fetch is enabled by default using an [undici implementation](https://nodejs.org/de/blog/announcements/v18-release-announce/#fetch-experimental). At...

Hey @kettanaito thanks for the reply! I actually started working on this yesterday and came to mostly the same conclusions. I realized that the reason msw wasn't intercepting native fetch...

Not sure, but this sounds related to to [changes in Jest global injection](https://jestjs.io/blog/2022/04/25/jest-28#all-nodejs-globals), which will cause it to inject the node-native `fetch`, which will not be intercepted. I recommend verifying...