endless

endless copied to clipboard

a process is running , then i modified some code ,then, i try to build it again. and it shows the error msg above. i know the reason, but, i...

raoxiaoya

Support Http2.0

1

Support Http2.0

snowdream

fork() should use cmd.Run() rather than cmd.Start()

1

func (c *Cmd) Run() error { if err := c.Start(); err != nil { return err } return c.Wait() // if execute the command fails，return error } I use endless...

EricHouang

Change to log hammer message only when actually hammered. Before this change, hammer message is confusing when parent process is already STATE_TERMINATE and doing another job after Serve.

KeiichiHirobe

zgzwangxin

modify example handler func name

ptechen

- Avoid zombie processes, There is no wait subprocess state, which may lead to zombie process in subprocesses. - Active termination to eliminate http.Serve error messages

thinkeridea

Tarektouati

endless.NewServer() Struct Variable

2

I want to make a struct like this: ``` type App struct { Server *endless.endlessServer Router *gin.Engine } func (a *App) Initialize(config *config.Config) { a.Server = endless.NewServer(fmt.Sprintf(":%d", a.Config.Server.Port), a.Router) }...

Dentrax

syscall.SIGUSR1,syscall.SIGUSR2,syscall.SIGTSTP,syscall.Kill makes endless unusable on windows

4

i found `endless` uses `syscall.SIGUSR1`,`syscall.SIGUSR2`,`syscall.SIGTSTP`,`syscall.Kill`, these things are not defined on Go 1.6.2 on windows. so codes using `endless` can not even be compiled. endless: 2cdc20a776897c0f406853c048c33e2c1a9f0ebf would you please fix...

bruceauyeung