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
yaojingguo opened this issue
Aug 20, 2021
· 6 comments
Labels
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.
After skimming Go net/rpc source code (last commit: e9e0d1e), I found that no test scenario exists for using done channel for two RPC calls. I suggest adding a test scenario for this case.
If you have a suggested improvement for tests, you don't have to create an issue for it. You can just send the change. If you want to check with maintainers first, https://groups.google.com/g/golang-dev is a good place for this kind of communication (specifically, for working on the Go project itself). See https://golang.org/doc/contribute.
mknyszek
added
NeedsFix
The path to resolution is known, but the work has not been done.
Testing
An issue that has been verified to require only test changes, not just a test failure.
labels
Aug 20, 2021
The net/rpc package is frozen and not accepting new features. While a new test is not a feature, aside from tests associated with bugfixes adding more test cases doesn't seem like a good use of anyone's time.
The Go function allows the reuse of the done channel argument. But neither net/rpc's doc nor its test cases show such a usage. So I think that it is worth of time to add such a test scenario.
NeedsFixThe path to resolution is known, but the work has not been done.TestingAn issue that has been verified to require only test changes, not just a test failure.
After skimming Go
net/rpc
source code (last commit: e9e0d1e), I found that no test scenario exists for usingdone
channel for two RPC calls. I suggest adding a test scenario for this case.The following code shows the scenario details:
The text was updated successfully, but these errors were encountered: