Skip to content

fix(remote): dial remote plugins through passthrough - #246

Merged
ZergsLaw merged 1 commit into
mainfrom
fix/remote-plugin-passthrough
Oct 25, 2026
Merged

ZergsLaw merged 1 commit into
mainfrom
fix/remote-plugin-passthrough

Conversation

@ZergsLaw

Copy link
Copy Markdown
Contributor

easyp generate with a remote: plugin connected through grpc-go's default dns:/// resolver, which queries the configured nameservers itself; on a machine whose first nameserver does not answer — a VPN's, in the case that surfaced this — every connection waited about 20 s before falling back, localhost included. The executor now dials passthrough:///host:port, so the system resolver answers at dial time, and a host given without a port gets 443 as the dns resolver assumed. The same change lands in the service SDK (easyp-tech/service#45). Adds the first test for parsePluginURL together with the dial target.

🤖 Generated with Claude Code

grpc-go's default dns resolver queries the nameservers itself, and on a
machine whose first one does not answer (a VPN's) it waited ~20s on every
connection to a remote plugin service, localhost included. passthrough lets
the system resolver answer at dial time; a host without a port gets 443, as
the dns resolver assumed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ZergsLaw
ZergsLaw merged commit 62fe940 into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant