endless takes over param handling about endless HOT 3 CLOSED

i believe this is due to when/where/how you call flag.Parse()

endless allows other flags to be defined, preserves them, and appends its own at the end.

have a look here: https://gist.github.com/fvbock/855a980deed441cc31cd

if you compile and run that:

$ go build -o flags flags.go
$ ./flags -paramA pValA -paramB
2015/06/30 14:55:15 Got passed: [-paramA pValA -paramB]  # this is from os.Args[1:]
2015/06/30 14:55:15 paramA pValA
2015/06/30 14:55:15 paramB true
2015/06/30 14:55:16 22335 localhost:4242

Now send SIGHUP

$ kill -1 22335

2015/06/30 14:55:30 22335 Received SIGHUP. forking.
2015/06/30 14:55:30 Got passed: [-paramA pValA -paramB -continue]
2015/06/30 14:55:30 paramA pValA
2015/06/30 14:55:30 paramB true
2015/06/30 14:55:30 22351 localhost:4242

the original parameters are kept and endless appends it's own parameters at the end.

does this help?

from endless.

When I posted the issue, it briefly crossed my mind that it might be a library interaction, but the lateness of the hour left me too lazy to test it.

It turns out that this is an interaction between endless and my favorite drop-in flag parsing library by namsral. Try this code and the pattern fails. Use the Go standard flag library and it succeeds.

I don't yet know in which library the issue lies, so I'll withdraw the ticket until I can investigate further.

Thanks for the speedy and civil response.

from endless.

Really closed. This is not an endless issue. For the curious, this can be followed in namsral/flag.

from endless.