1
70%
develop: 70%

Ran 31 Jul 2024 06:25AM UTC

Files 105

Run time 4s

Badge

Embed ▾

Committed 31 Jul 2024 06:17AM UTC coverage: 69.695% (-0.2%) from 69.895%

Job # 10175102977.1

Build Type

push

github

Committed by

web-flow

Commit Message

Fix inconsistent SocketsManager objects (#2444)

On import of mslib.mscolab.server initialize_managers was called once,
hooking events up to handlers in a SocketsManager instance and
initializing the Flask app with the Flask-SocketIO extension. Then, in
handle_start, initialize_managers was called a second time, creating
another SocketsManager object, overwriting the instance saved with the
SocketIO object, and trying to initialize the Flask app with it again.

The last step does not work though, a Flask app can only be initialized
once with each extension (i.e. the sockio.init_app(app) call can only be
done once per Flask app object).

What this led to is that the Flask-SocketIO extension was using the
first SocketsManager object to handle incoming events, while the server
side was using the second SocketsManager object when it called methods
on sockio.sm.

This changes the startup process to do the initialization just once.

Run Details

13679 of 19627 relevant lines covered (69.69%)

0.7 hits per line

Open-MSS / MSS / 10175102977 / 1
70%
develop: 70%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10175102977.1

Open-MSS / MSS / 10175102977 / 1 70% develop: 70%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10175102977.1

Open-MSS / MSS / 10175102977 / 1
70%
develop: 70%

README BADGES
x