Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Bug: Amount of notifications shown is not correct

    Support
    notifications
    4
    3
    178
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • fbartels
      fbartels App Dev last edited by girish

      Prelude: Redis on my Nextcloud app seems to have. repeatedly run out of memory and was automatically restarted. Creating a notification for each incident a notification was created. This brought me to two realisations:

      Bug #1: Clicking on "Mark All as Read" (weird casing by the way) only marks the notifications on the current page as read and not on any of the other pages

      Bug #2: The number of notifications shown in the top bar only ever goes to 100 (even if there are more).

      The second one is a bit harder to describe therefore I made a video as well: https://youtu.be/RZ6IGbeigN4?t=6 (you can stop watching at 0:11)

      Steps to reproduce:

      • have more than 100 unread notifications
      • click on "Mark All as Read"
        • you will see that the displayed amount of notification dropping to 80
      • reload the Cloudron dashboard and the counter will be back at 100
        • while observing the behaviour the counter even went down to zero

      Cloudron is at v7.1.3 (Ubuntu 20.04.2 LTS)

      Edit: Actually even after going through all pages, I still have two unread notifications left.

      girish 1 Reply Last reply Reply Quote 2
      • girish
        girish Staff @fbartels last edited by

        @fbartels thanks for reporting, I have noticed this as well at times. I don't like the UI that one has to dig through all notifications to clear things.

        Will get this fixed for next release but leave this as unsolved for now.

        1 Reply Last reply Reply Quote 1
        • Topic has been marked as a question  girish girish 
        • Referenced by  fbartels fbartels 
        • nebulon
          nebulon Staff last edited by

          This should be fixed with the next release. There were a couple of state issues which needed fixing.

          1 Reply Last reply Reply Quote 3
          • Topic has been marked as solved  nebulon nebulon 
          • First post
            Last post
          Powered by NodeBB