Page MenuHomeDevCentral

Initialize broker and notifications
ClosedPublic

Authored by dereckson on Nov 17 2017, 03:13.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 27, 11:17
Unknown Object (File)
Wed, Mar 27, 04:35
Unknown Object (File)
Wed, Mar 27, 04:35
Unknown Object (File)
Sat, Mar 23, 14:18
Unknown Object (File)
Fri, Mar 22, 06:05
Unknown Object (File)
Fri, Mar 22, 05:50
Unknown Object (File)
Thu, Mar 21, 07:54
Unknown Object (File)
Thu, Mar 21, 04:27
Subscribers
None

Details

Summary

After 90 seconds, enough to allow the egg to connect to Freenode
and join every channel, load first the broker, then the notifications
code (the notifications code depends of the broker).

This responsibility was previously for the configuration file.

It's more convenient to move this part to the application code,
especially as the bot-specific configuration file is now standardized.

Ref T1309

Test Plan

Restart Wearg, check it connects to broker

Diff Detail

Repository
rVIPER ViperServ scripts
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Nov 17 2017, 03:13
dereckson added inline comments.
Wearg/Time.tcl
8

03:28 <wearg> [03:28:50] Tcl error [dcc:source]: formal parameter "()" is an array element

dereckson marked an inline comment as done.

Fix proc syntax error

This revision is now accepted and ready to land.Nov 17 2017, 03:30
03:29 <dereckson> .tcl mq connected
03:29 <wearg> Tcl error: invalid command name "mq"
03:29 <dereckson> .tcl onload
03:29 <wearg> Tcl: {* * * * ::notifications::channel_notify} {DockerHub * * * ::notifications::docker_build_summary}
03:29 <dereckson> .tcl mq connected
03:29 <wearg> Tcl: 1
This revision was automatically updated to reflect the committed changes.