This is related to #31 but as it is specific to the supply test I'll make a separate one.
It would appear that the t/12-supply.t suffers a deadlock between the Supply and the client somehow.
If the parts of the test (i.e. the server and the client,) are run as separate processes, then it all works fine, however in the test the client times out before receiving any data.
Instrumentation of the test and library code indicates that the supply is being exhausted and that it is probable that the deadlock is occurring between the sockets somehow.
This is related to #31 but as it is specific to the supply test I'll make a separate one.
It would appear that the t/12-supply.t suffers a deadlock between the Supply and the client somehow.
If the parts of the test (i.e. the server and the client,) are run as separate processes, then it all works fine, however in the test the client times out before receiving any data.
Instrumentation of the test and library code indicates that the supply is being exhausted and that it is probable that the deadlock is occurring between the sockets somehow.
I'm looking at it with a view to fixing.