New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Second Close Roll-Call not shared between servers #1898

Open

3 of 6 tasks

4xiom5 opened this issue May 30, 2024 · 0 comments

Open

3 of 6 tasks

[BUG] Second Close Roll-Call not shared between servers #1898

4xiom5 opened this issue May 30, 2024 · 0 comments

Labels

be1-go be2-scala bug

Contributor

4xiom5 commented May 30, 2024

Description (Actual behavior)

When a Roll-Call is reopened then closed again.

Expected behavior

A clear and concise description of what you expected to happen.

How to reproduce

Create a Roll-Call
Open it
Close it
Reopen it
Close it again
The second close message is not propagated

Version & Environment

This bug was reproduced on:

Commit: aa04c3a

Front-ends:

Fe1-Web (please include browser's names & version)
Fe2-Android (please specify if phone or emulation, and Android version)
Not applicable

Back-ends:

Be1-Go
Be2-Scala
Not applicable

Workaround

None

Impact

Roll-Call is shown as open on clients. Mose features cannot be used.

Possible root cause

Problem in rumor sharing

The text was updated successfully, but these errors were encountered:

4xiom5 added bug be2-scala be1-go labels

4xiom5 assigned 4xiom5 and unassigned 4xiom5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment