You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Go-plugin relies on stdout to handshake, however, stdout is likely to be polluted by other modules inited before go-plugin. For example, in module A:
funcinit() {
fmt.Println("Hey, this happens before init of go-plugin")
}
As for handshake, do we have alternatives to stdout?
The text was updated successfully, but these errors were encountered:
I would challenge it isn't "likely to be polluted" since we've used go-plugin in a number of projects with hundreds of transitive Go dependencies and have never once had an issue. I'd argue its fairly hostile for anything to output to stdout in an init function. 😄
There are no plans currently to use anything other than stdout for the handshake. There have been requests to enable some functionality of redirecting stdout after the handshake but so far we've been against that as well (to just keep it flexible for how we modify the handshake in the future).
I'd recommend if you need non-stdout support that you fork the project for your needs.
Hi,
Go-plugin relies on stdout to handshake, however, stdout is likely to be polluted by other modules inited before go-plugin. For example, in module A:
As for handshake, do we have alternatives to stdout?
The text was updated successfully, but these errors were encountered: