agola/internal/services
Simone Gotti 85876310af readdb: fix deadlock in Run method
In runservice readdb Run method we could end with a deadlock if two of the
goroutines that call HandleEvents.* try to write to the errCh at the same
time before the errCh is read. If this happens one of the two will be blocked on
writing to the channel but the read won't happen since it'll blocked by
wg.Wait().

Fix this doing:
* use a buffered channel large as the number of executed goroutines.
* create a new errCh at every loop (so we'll ignore later errors after the first
one)

Note: we could also use a non blocking send to avoid this situation but we
should also start the wg.Wait before the goroutines or earlier errors could be
lost causing another kind of hang.
2019-07-23 14:56:26 +02:00
..
common *: use vanity url 2019-07-01 11:40:20 +02:00
config config: remove unused gatewayURL from gitserver config 2019-07-04 10:55:12 +02:00
configstore readdb: fix deadlock in Run method 2019-07-23 14:56:26 +02:00
executor k8s driver: start goroutines after setup 2019-07-10 21:55:26 +02:00
gateway service: handle cors config and use it only on gateway 2019-07-13 23:15:00 +02:00
gitserver service/*: log error only if nil 2019-07-04 15:50:37 +02:00
notification notification: fix linter errors 2019-07-02 15:54:47 +02:00
runservice readdb: fix deadlock in Run method 2019-07-23 14:56:26 +02:00
scheduler scheduler: fix linter errors 2019-07-02 15:56:14 +02:00
types *: add remote source option to disable registration/login 2019-07-05 13:33:29 +02:00