[enhancement] Mir servers should allow client connections only after server start-up has finished
Bug #1451844 reported by
Alexandros Frantzis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
Medium
|
Alexandros Frantzis | ||
| mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Vivid |
New
|
Undecided
|
Unassigned | ||
Bug Description
Mir servers should allow client connections only after start-up has finished, to avoid races with components that are in the process of initializing.
Related branches
lp:~afrantzis/mir/accept-connections-only-when-server-is-ready
- Alan Griffiths: Approve
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 152 lines (+27/-27)2 files modifiedsrc/server/display_server.cpp (+21/-21)
tests/integration-tests/test_display_server_main_loop_events.cpp (+6/-6)
| Changed in mir: | |
| status: | New → In Progress |
| Changed in mir: | |
| milestone: | none → 0.14.0 |
| summary: |
- Mir servers should allow client connections only after server start-up - has finished + [enhancement] Mir servers should allow client connections only after + server start-up has finished |
| tags: | added: enhancement |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #1 |
| Changed in mir: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in mir (Ubuntu): | |
| status: | New → Fix Released |
| Changed in mir: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.14.0