On Wed, 27 Jul 2016 10:24:13 -0400
"evan@evan-borden.com"
Good day,
I am pleased to announce the release of network 2.6.3.0. This release is primarily focused on stability, but includes a few new APIs. Thank you to the contributors for their continued excellence.
Woohoo! I've updated network package from 2.6.2.1 to 2.6.3.0 and noticed a few package packages started failing tests with seemingly the same point to network changes. Release notes don't point to chages in exception delivery. Do you think the following failures are package bugs or subtle network change?
Failed to emerge dev-haskell/simple-sendfile-0.2.25, Log file: '/tmp/portage-tmpdir/portage/dev-haskell/simple-sendfile-0.2.25/temp/build.log' Failed to emerge dev-haskell/fluent-logger-0.2.3.1, Log file: '/tmp/portage-tmpdir/portage/dev-haskell/fluent-logger-0.2.3.1/temp/build.log' Failed to emerge dev-haskell/http-client-0.4.30, Log file: '/tmp/portage-tmpdir/portage/dev-haskell/http-client-0.4.30/temp/build.log' Failed to emerge dev-haskell/dbus-0.10.12, Log file: '/tmp/portage-tmpdir/portage/dev-haskell/dbus-0.10.12/temp/build.log'
simple-sendfile-0.2.25 Failures: test/SendfileSpec.hs:30: 1) Sendfile.sendfile sends an entire file uncaught exception: IOException of type EOF (Network.Socket.recvBuf: end of file (end of file)) fluent-logger-0.2.3.1 Network.Fluent.Logger post fluent-logger-spec: Network.Socket.recvBuf: end of file (end of file) http-client-0.4.30 spec-nonet: Network.Socket.recvBuf: end of file (end of file) connecting to missing server gives nice error message extra headers after 100 #49 dbus-0.10.12 Test suite dbus_tests: RUNNING... dbus_tests: Network.Socket.recvBuf: end of file (end of file) [ ABORT ] Transport.handle-lost-connection Test aborted due to exception: TransportError {transportErrorMessage = "Network.Socket.recvBuf: end of file (end of file)", t ransportErrorAddress = Just (Address "tcp:family=ipv4,host=localhost,port=52067")} -- Sergei