Resetting the FSM in GEMSupervisor corrupts the terminal output

[lpetre-ulb]

Brief summary of issue

While testing FSM state transitions, I noticed that moving to the Resetting state corrupts the terminal log output. The result can bee seen in the "current behavior" section.

Types of issue

• Bug report (report an issue with the code)
• Feature request (request for change which adds functionality)

Expected Behavior

Log output should never get corrupted.

Current Behavior

When moving to the Resetting state, the terminal output gets corrupted and never recovers by itself.

18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - GEMFSM::changeState()
18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - GEMFSM::received command Reset
18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - Firing GEMFSM for event Reset
18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - initial state is: Halted
18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - new state is: Halted
18 Mar 2020 10:07:10.387 [140148359386880] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - [GEMFSMApplication::reset] reset called, current state: Resetting
18 Mar 2020 10:07:10.387 [140148359386880] INFO  gem-shelf01-amc02 <> - basic check: HwGenericAMC pointer valid
18 Mar 2020 10:07:10.387 [140149390489344] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - GEMFSM::stateChanged:Current state is: [Resetting]
18 Mar 2020 10:07:10.387 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::hw::amc::AMCManager.instance(0) <> - changeState::sending command Reset newStateName Resetting
18 Mar 2020 10:07:10.390 [140148359386880] INFO  gem-shelf01-amc02 <> - HwGenericAMC found boardID
18 Mar 2020 10:07:10.390 [140148359386880] INFO  gem-shelf01-amc02 <> - m_links 0x00000fff 0x1 << gtx = 00000001
18 Mar 2020 10:07:10.391 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::supervisor::GEMSupervisor.instance(0) <> - GEMSupervisor::globalStateChanged(H,t)
18 Mar 2020 10:07:10.391 [140149002331904] INFO  ch.cern.gem904daq04.p:20502.gem::supervisor::GEMSupervisor.instance(0) <> - GEMSupervisor::resetAction GlobalState = Resetting with GlobalStateMessage = @@
@@@@
18 M▒⎼ 2▮2▮ 1▮:▮7:1▮↓391 [14▮149▮▮23319▮4] INFO  c▒↓ce⎼┼↓±e└9▮4d▒─▮4↓⎻:2▮5▮2↓±e└::⎽┤⎻e⎼┴☃⎽⎺⎼::GEMS┤⎻e⎼┴☃⎽⎺⎼↓☃┼⎽├▒┼ce(▮) <> ↑ GEMFSMA⎻⎻┌☃c▒├☃⎺┼::⎼e⎽e├ F☃⎼☃┼± 'I⎽I┼☃├☃▒┌' ☃┼├⎺ ├▒e FSM
18 M▒⎼ 2▮2▮ 1▮:▮7:1▮↓391 [14▮149▮▮23319▮4] INFO  c▒↓ce⎼┼↓±e└9▮4d▒─▮4↓⎻:2▮5▮2↓±e└::⎽┤⎻e⎼┴☃⎽⎺⎼::GEMS┤⎻e⎼┴☃⎽⎺⎼↓☃┼⎽├▒┼ce(▮) <> ↑ [GEMFSMA⎻⎻┌☃c▒├☃⎺┼::°☃⎼eE┴e┼├] °☃⎼eE┴e┼├(I⎽I┼☃├☃▒┌)
18 M▒⎼ 2▮2▮ 1▮:▮7:1▮↓391 [14▮149▮▮23319▮4] INFO  c▒↓ce⎼┼↓±e└9▮4d▒─▮4↓⎻:2▮5▮2↓±e└::⎽┤⎻e⎼┴☃⎽⎺⎼::GEMS┤⎻e⎼┴☃⎽⎺⎼↓☃┼⎽├▒┼ce(▮) <> ↑ GEMFSM::°☃⎼eE┴e┼├(I⎽I┼☃├☃▒┌)
18 M▒⎼ 2▮2▮ 1▮:▮7:1▮↓391 [14▮149356918528] INFO  c▒↓ce⎼┼↓±e└9▮4d▒─▮4↓⎻:2▮5▮2↓±e└::⎽┤⎻e⎼┴☃⎽⎺⎼::GEMS┤⎻e⎼┴☃⎽⎺⎼↓☃┼⎽├▒┼ce(▮) <> ↑ GEMFSM::⎽├▒├eC▒▒┼±ed:C┤⎼⎼e┼├ ⎽├▒├e ☃⎽: [I┼☃├☃▒┌]
18 M▒⎼ 2▮2▮ 1▮:▮7:1▮↓392 [14▮14835938688▮] INFO  ±e└↑⎽▒e┌°▮1↑▒└c▮2 <> ↑ ±├│▮ ⎻⎼e⎽e┼├(198912)

Steps to Reproduce (for bugs)

1. Click Reset in the GEMSupervisor Web GUI (tested from the Halted state).
2. Look at the beautiful log output!

Possible Solution (for bugs)

Not really sure what is the bug, probably an invalid gets inserted. In any case, tis bug is low priority.

Context

Testing FSM state transitions

Your Environment

• Version used: 43dfbf5
• Shell used: bash inside tmux

[lpetre-ulb]

Cannot reproduce after the last set of commits and the migration to the mono-repo.