Alfonso Acosta
Alfonso Acosta
Note that, even if we remove the explicit queue, we are still using a pipe to read the data (with an associated buffer).
As @sreuland says, replacing the pipe with a two-way communication protocol would solve the problem but that's probably a lot of work to implement and propagate downstream.
Uhm, you still need to manage the captive core process (restart it on error etc ...)
Thanks for the issue. From what I gather you are getting a `NotFound` error for an account which doesn't exist. I think that's correct. > A split between NotFound errors...
A new method (e.g. `Args() []string`) could be added to [`Service`](https://godoc.org/github.com/kardianos/service#Service) without breaking backwards compatibility. Would you be interested in a PR?
The `Start()` method should also pass the arguments (and that one is tricky to change without breaking backwards compatibility)
Yes, Windows seems to distinguish between: * The arguments (`os.Args()`) passed to the Service Application binary managing services * The arguments (provided by `windows/svc.Execute()`) passed to a service on start....
I am going to wait for this until https://github.com/weaveworks/scope/pull/1041 is released with Scope 0.14
I would also find this useful!
@hawthorne-abendsen Thanks for the report, I'll be looking into this. To be sure the problem is on soroban-cli's side. Have you tried building the transaction through a different means than...