search

OpenSlides / openslides-autoupdate-service

Autoupdate service for OpenSlides 4+
MIT License
2 stars 21 forks source link

Projector content not updated after cache reset #775

Closed bastianjoel closed 11 months ago

bastianjoel commented 1 year ago

After a cache reset the projector content of e.g. countdown do not get updated anymore.

bastianjoel commented 1 year ago

Connections that were open previous to the cache reset still do not receive data after cache reset.

ostcar commented 1 year ago

I can not reproduce this.

I started the service with CACHE_RESET: 10s and even added some logging to see, that the cache really gets resetted.

Then I created two topics and projected them alternated, after a cache reset. Everything works fine.

Even when I reset this change https://github.com/OpenSlides/openslides-autoupdate-service/pull/776, everything works fine for me.

Can you tell me what I have to do to reproduce this?

bastianjoel commented 1 year ago

We did this with the countdown slide.

ostcar commented 1 year ago

What exactly did you do?

I did the following:

  1. Start the countdown.
  2. Wait until the cache reset
  3. Stop the countdown
  4. Wait until the cache reset
  5. Start the countdown again

Everything works for me

bastianjoel commented 1 year ago

As far as I remember we did the following:

  1. Project countdown (do not start)
  2. Wait for cache reset
  3. Start the countdown

After that we did not receive the countdown start on a connection that was opened prior to the cache reset. New connections did receive the update. But I guess this is the same as in step 3.-5.. I will try to reproduce this on monday and give you more detailed feedback.

bastianjoel commented 1 year ago

I cannot reproduce this either. @peb-adr @m-schieder could you give any more info on how to reproduce?

jsangmeister commented 11 months ago

Can this be closed? @peb-adr @m-schieder @bastianjoel

m-schieder commented 11 months ago

We were observing this behavior during an event and it coincided perfectly with the cache reset. Since then I have not heard that this has happened again. As we don't know exactly how we can reproduce it, I think the issue can be closed. We can open it again when it reappears.