Poll state does not exist error

[m-schieder]

If an assignment.delete is executed, the following error occurs in the autoupdate service logs:

Error: getting next message: creating later data: get restricted data: restricting data: calling collection poll modefunc C with ids [235 234]: calling restricter with same ids: getting value for element 235: poll/235/state does not exist.

[ostcar]

Could you make sure, that the database is valid after the assignment.delete action?

Is seams, that the client has requested the polls with ids 235 and 234 but the poll with id 235 does not exist.

Do you know the client request? Did the Client request the poll 235 directly or was it interectly via another collection? In later case, there could be a reference in the database to the deleted poll.

Are you able to reproduce the error?

[m-schieder]

Are you able to reproduce the error?

Create an assignment. Create a poll. Start the poll. Delete the assignment.

The poll you delete has the id with which the autoupdate has a problem.
The data looks intact. It seems that the au wants to access poll/xx/state but the poll is already set to deletet.

Do you know the client request?

No, I don't know

[ostcar]

There are different bugs. Probably one in the client, one in the backend and one in the autoupdate.

When a poll gets started, the client, you can see the following output in the browser console:

[autoupdate] stream closed: active_polls:subscription [autoupdate.service.ts:243:24](https://localhost:8000/src/app/site/services/autoupdate/autoupdate.service.ts)
[autoupdate] new request: active_polls:subscription 
Array [ {…}, {…} ]

I think it is not good, that the client creates new requests. It would be better if the client would/could send a request like "give me all polls, that are active". If this would be the case, the deleted poll would not be requested.

When the Backend deletes an active poll, it seems, that it does not informs the vote-service about it. There should be a message in the vote service Receiving clear request, but I can not detect it.

This should be fixed independently from this issue, because the vote service should know about deleted polls to manage its own data.

If the Backend would inform the vote-service about deleted polls, the error from this issue would probably not happen.

The error happens, if the client requests the field poll/has_voted_user_ids. This fields does not exist in the database (at the moment, it will be in the database after we merged rel-db). The error happens, because when a poll gets deleted, this field does still exist. When it gets requested, the autoupate-service has to calculate the restriction for it, and requests other fields from the same poll, like poll/stat. Since they do not exist, the error occurs.

I could add some dirty fixes in the autoupdate, but I think it would be better, if the Backend could inform the vote service about deleted polls.

@rrenkert Could this also fix your bug about to much data in in the vote-service? Did you delete active polls for your tests? If so, it is not an issue in the vote service, since the vote service can not clean up its data, when it does not get informed, that the poll was deleted.

[rrenkert]

Yes, I deleted an active poll and never saw a message like Receiving clear request in the vote-service logs. I think the most important issue is the backend part. Can you please create an issue in the backend repo containing the information how to inform the vote-service about the deletion?

[Elblinator]

This could have been fixed by OpenSlides/openslides-backend#2951
Needs testing