Enable MultiProcessor in processor.go

[karenychen]

User can add more than one receiver to listen to with go-shuttle's Processor.

Use NewMultiProcessor() to initialize a list of receivers in a Processor

Note: max concurrency count is shared across all receivers.

MultiProcessor is not yet compatible with LockRenewer.

[coveralls]

Pull Request Test Coverage Report for Build 8776717166

Details

• 81 of 94 (86.17%) changed or added relevant lines in 2 files are covered.
• 5 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.2%) to 85.417%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
v2/processor.go	76	79	96.2%
v2/metrics/processor/types.go	5	15	33.33%

Files with Coverage Reduction	New Missed Lines	%
v2/metrics/processor/types.go	2	80.73%
v2/lockrenewer.go	3	95.24%

Totals
Change from base Build 8699030379:	-0.2%
Covered Lines:	738
Relevant Lines:	864

---

💛 - Coveralls

[serbrech]

Here, if startOne panics, or if the cahnnel is closed for example, and we try to push err on it, we will not call wg.Done() because we don't recover from the panic, I believe.
So I think that the wg.Wait() will keep us stuck forever.

could you try to add a test for that by generating a panic somehow inside startOne ?

[serbrech]

in terms of fixing it, I've been itching to use conc library in go-shuttle, but unsure whether that's wise as a library.
we should handle the panic I think...

[karenychen]

added panic handling + UTs

[serbrech]

Ok let's get this in. we might want to adjust some things once we write integration code around it.