Conversation
|
If the goal is to test on a random port, maybe we can simply use port 0 to avoid introducing an extra dependency? |
|
Well, we need to use the port number both in the argument to the test subject and in arguments to whatever will be making requests. Ideally, the platform could give us a way to reserve a port and then pass it to a CLI to use, but I guess that's too much to ask. So we need to keep track of ports across multiple threads 🤷 |
|
I converted this to draft because I have learned while working on #191 (which is also still draft for a different reason) that each such port must be reserved (locally, at least) to prevent port reuse which would result in failure. Such a mechanism is included in #191, so perhaps I shall focus on getting that through and subsequently the mechanism could be reused here. Although it is a trivial mechanism really. |
2 participants
No description provided.