#1192: Conference chat: people still listed after a crash can be invited back #1397
No reviewers
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream!1397
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "TheSlowly/Slipstream:conference-readd-1192"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #1192.
The add-people picker refused anyone still on the conference's participant list, which can stay stale after a crash. Conferences now only refuse yourself; re-inviting someone still present just repeats the invite.
Superseded by
3dc65d085fon main; closing.Thanks! The #1192 fix already landed on main through the Beta 6 port (
3dc65d085f, a narrower version that lets a retained, departed speaker be re-invited). This PR also drops the whole already-in-conference check, which would let someone still active be invited twice, so closing it rather than merging. If there's a case the landed fix misses, a small follow-up on current main is welcome.Pull request closed