nickserver.git/test, branch 0.9.0 [nickserver] silence Celluloid.logger in tests 2016-10-02T13:05:02+00:00 Azul azul@riseup.net 2016-10-02T13:05:02+00:00 5967c4a568aff2c5e73e3ab933aa68d25387aeb1 Introduced CelluloidTest as a test class for all tests that depend on Celluloid being up and running. 
Introduced CelluloidTest as a test class for all tests that depend on
Celluloid being up and running.
change default adapter to CelluloidHttp 2016-09-30T10:47:32+00:00 Azul azul@riseup.net 2016-09-30T10:47:32+00:00 ab31d9ca7dca20c873a7240482d1736d0f6b6dae Turns out without this nickserver will not respond to multiple concurrent requests. 
Turns out without this nickserver will not respond to multiple concurrent requests.
minor: test: fix * interpreted as arg prefix warning 2016-09-30T10:46:05+00:00 Azul azul@riseup.net 2016-09-30T10:46:05+00:00 0d4a43cf03f4efeeed1d380c931ab72184346ea1 






logging: use proper logger
2016-09-30T09:59:20+00:00

Azul
azul@riseup.net

2016-09-30T09:59:20+00:00

8ee1d1cb70bee8c938966e4e042b4929ced8b1a3

This way the logs do not interfere with test output





This way the logs do not interfere with test output







skip tests with ConnectionErrors
2016-09-29T10:56:14+00:00

Azul
azul@riseup.net

2016-09-29T10:56:14+00:00

4cd842927a60e4e81915da22983f216ccd54d6a3

We handle these errors nicely in the dispatcher and have tests for that.
Tests should fail or err out when running into exceptions we are not
handling yet. But for these it's better to just skip.





We handle these errors nicely in the dispatcher and have tests for that.
Tests should fail or err out when running into exceptions we are not
handling yet. But for these it's better to just skip.







use plain http.rb rather than celluloid i/o
2016-09-24T10:02:12+00:00

Azul
azul@riseup.net

2016-09-24T10:00:56+00:00

5a93f2d29c96e649440101f2d1ca28247631b59e

Turns out http.rb does not support celluloid i/o andymore and we were not making
use of it anyway.

Here's what https://github.com/httprb/http/wiki/Thread-Safety says:
(NOTE: this gem previously supported Celluloid::IO, but that support was removed to add the current timeout backend. It may be added back in a future version)

So now we have a plain http.rb adapter and use that as the default.
This prevents actors from crashing in the adapter (as we don't have any).





Turns out http.rb does not support celluloid i/o andymore and we were not making
use of it anyway.

Here's what https://github.com/httprb/http/wiki/Thread-Safety says:
(NOTE: this gem previously supported Celluloid::IO, but that support was removed to add the current timeout backend. It may be added back in a future version)

So now we have a plain http.rb adapter and use that as the default.
This prevents actors from crashing in the adapter (as we don't have any).







test: rename so no name is duplicated
2016-09-24T09:56:59+00:00

Azul
azul@riseup.net

2016-09-24T09:56:59+00:00

c32bce3399eb1bca8987a49ecc89700458803250












test: some very basic functional tests
2016-09-23T13:54:34+00:00

Azul
azul@riseup.net

2016-09-23T13:54:34+00:00

906724ff074710c7078b2d8423edd2477283b2e1












hand on connection errors to dispatcher so it can handle it
2016-09-22T09:31:01+00:00

Azul
azul@riseup.net

2016-09-22T09:31:01+00:00

1202e3b03c3bb88cd3a63dae3866167564f1d25d












feature: 502 on ConnectionErrors
2016-09-22T09:07:47+00:00

Azul
azul@riseup.net

2016-09-22T09:07:47+00:00

48cdd4b1ee0685674aa998d4daa295656d80ead3

If one source raises a 502 and no other handler has any result we'll
respond with a 502 - bad gateway.





If one source raises a 502 and no other handler has any result we'll
respond with a 502 - bad gateway.