kvii

> 应该是个 bug，对windows平台的经验不多，如果可以，直接使用 mg daemon run 来运行服务。 直接运行 mg daemon run 会占用当前 terminal。所以不能用这条命令运行一个后台服务。

No. It's just I don't want it to open. You can reopen it if you want. Consider to use [service](https://pkg.go.dev/github.com/kardianos/service)? I have used this package for my business code.

I've create a PR to fix this.

It will FAIL when I call `go test -timeout 15s github.com/go-rod/rod` multiple. ``` txt go test -timeout 15s github.com/go-rod/rod ok github.com/go-rod/rod 9.284s go test -timeout 15s github.com/go-rod/rod parallel test 10...

> Because all test cases share the `g.page` pool, if you are leaking something all other tests that use `g.page` will be affected. I executed `go test`, a shell command...

Maybe go cached something between two `go test`. So can I understand that as long as the first test passes, it will be fine?

The context of p is already done. So `proto.FetchEnable` will return an error of `"context canceled"`. Will `proto.FetchEnable.Call` still be issued even if the context has done?

Should we check if ctx has been done before the request will be sent? #704

Note the bug of context is still exits. As we discussed in #704, we don't know if the request is actually sent when the context is done.

That means we need to write some code like below: ```go for { cur := c.Next() if cur == nil { return nil } // ... } ``` Or we...