Timeline

View changes from
going back days
by author

Tickets opened and closed Repository changesets Wiki changes

10/06/17:

17:11 Changeset [18911] by tbretz

Some typos

17:10 Changeset [18910] by tbretz

First version of the program reading the bias crate temp sensors

09/27/17:

23:04 FlareAlertsSent edited by Daniela Dorner

added alert of tonight (diff)

09/18/17:

16:43 Changeset [18909] by tbretz

Moved setting connection parameters from a global variable (without setter) to the connection call.

13:27 Changeset [18908] by tbretz

Added output for ongoing crate reset.

09/17/17:

23:43 FlareAlertsSent edited by Daniela Dorner

added alert of tonight (diff)

09/16/17:

12:37 Changeset [18907] by tbretz

Updated some informations.

09/14/17:

23:22 Changeset [18906] by Daniela Dorner

fixed two bugs, added filling of informaion in DB

16:48 FlareAlertsSent edited by Daniela Dorner

added 2 alerts from August (diff)

15:56 FlareAlertsSent edited by dneise

typo (diff)

09/12/17:

08:57 Changeset [18905] by dneise

Remove SQM_CONTROL check in Startup, since the device is broken.

09/07/17:

17:15 Changeset [18904] by dneise

increase timeout to 30sec, just to make sure it is not too short, while I am away over the weekend.

13:55 Changeset [18903] by dneise

Setting startup Handler loop timeouts to 5000ms. We saw endless loops in Main.js during startup now several times reported by shifters. They happened either during startup in the evening or after Main.js re-start in the middle of the night. Main.js would report to be "Running" but do nothing for ever. Some shifters would only notice after a long time. Shifthelper would not notice it ever. These Handler.loops running without any timeout were most probably the reason. I checked the log for usual times, they were in the range of 0..1400ms. So I think setting it to 5sec should be fine.