Uploaded image for project: 'network-transport-tcp'
  1. network-transport-tcp
  2. NTTCP-5

createTransport doesn't respect the use of "0" as a port number

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.2.0.2, 0.2.0.1, 0.2.0, 0.2.0.3, 0.3.0, 0.3.1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      Linux

      Description

      See https://cloud-haskell.atlassian.net/browse/DPSLN-9. If we pass "0" as the port (which means "pick an arbitrary free port"), the endpoint addressing will break, because instead of checking which port was actually assigned, we store "0" as our port number. This breaks d-p-simplelocalnet, for example.

      The simplest fix would be to disallow "0" as a port number, although that's perhaps not the most user-friendly thing to do.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                hyperthunk hyperthunk
                Reporter:
                hyperthunk hyperthunk
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: