influxdata
chore(outputs.mqtt): Rework templating to use TemplateMetric
Summary
The topic_prefix parameter is deprecated and will get removed in v1.35, so I updated the docs to not mention it anymore. In the meantime, I also migrated the custom template names to make use of the already existing TemplateMetric functionality.
This will also make the removal of TopicPrefix and TopicNameGenerator easier in the future. As an example, the HomieGenerator is already completely replaced.
Checklist
- [x] No AI generated code was used in this PR
Related issues
resolves #
Cypress is an extension on chrome. I was running into the same issue and getting 503. I fixed it by enabling permissions on the extension. Upper right hand where the three dots for settings
go to extensions and allow permissions
@pawelgalazka @brian-mann @jennifer-shehane I've never seen node processes look to the OS proxy configuration. Not saying that you can't expose OS configurations, but it's far more typical to see rc or pick your favorite shell export these to the runtime.
In my own employer's environment, besides SOCKS being strictly locked down, the OS proxy is not exposed to node and every developer has documentation to set up their shell, e.g., .zshenv, correctly.
Additionally, SOCKS support does not look like something out of the box for node, requiring a module. node supports most http_proxy variables.
Seems like this is node-specific.
- Setting browser SOCKS5 proxy via extension still fails, but accessing my resource on another tab of Cypress-launched browser works.
- Setting
http_proxyenv to usesocks5orsocks5hwill spit out error during test run:
Error: Invalid protocol: socks5h:
at Request.init (/Users/syazwan/Library/Caches/Cypress/3.1.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/request/request.js:454:31)
So node itself is not using proxy settings from extension. With the env set, other CLI like curl works as expected, but not Cypress.
Since this issue hasn't had activity in a while, we'll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we'd be happy to reopen.
@dejwsz I did not confirm. We haven't had comments on this issue in years, so hopefully it is fixed.
Well, after my tests with latest cypress it looks like it isn't. Finally I have just used another proxy so when you have already working socks5 proxy you can add another http -> socks5 one and configure cypress with it. And it works fine. So there is no direct support for socks5 as I found. I have used python's pproxy: https://pypi.org/project/pproxy/. Additionally for the node itself I had set: "npm config set proxy http://localhost:8080" before executing cypress process. For cypress I set such envs: --env HTTP_PROXY=http://localhost:8080,HTTPS_PROXY=http://localhost:8080,NO_PROXY=localhost Important thing to me was to send also DNS requests via it what is possible over socks5 and pproxy supports it too over http.
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.
