Brandon Slaght

I too am at 9.2. I would be willing to test if there are plans for more backwards compatibility. If not I may just bite the bullet and see if...

I am encountering this error. Running `sfdx force:source:push -f --loglevel fatal`. I removed almost everything from my `force-app` folder to see if a specific piece of metadata was causing this...

> @slaght if you go to Help > Developer Tools in VS Code, you usually can see additional information on the source of an error. You can also try running...

I am seeing a similar issue with [wry ](https://github.com/billryoung/sfdx-wry-plugin) after updating to 7.163.0 from version 7.156.1, and a teammate is experiencing the same issue. The plugin still links properly though,...

> Can you provide the output from `sfdx version --verbose`? I'm wondering if the issue might be related to the node version and/or the operating system I had to downgrade...

> I reproduced this issue in _both_ pre-7.163.0 versions and post-7.163.0 versions if I do not compile the plugin after linking it. If, however, I compile the plugin I see...

@mdonnalley tried linking the plugin both before and after installing it and did not resolve the issue. This is also on the new 7.164.2 release

Multiple projects and environments experiencing this issue. Can someone confirm that `SFDX_DISABLE_DNS_CHECK` actually exists? It's not listed in the [documentation](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_env_variables.htm), and doesn't seem to completely fix the issue.