You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you used the debugging guide to try to resolve the issue?
Have you checked our FAQs to make sure your question isn't answered there?
Have you checked to make sure your issue does not already exist?
Have you checked you are on the latest release of Pulsar?
What happened?
I originally discovered this issue on 1.108.0, but I was able to reproduce it with the latest codebase. It started with #733 , I wasn't able to run Pulsar on Ubuntu 20.04, but then the issue was found and the official answer is that I should wait for the next release and stay on 1.108.0 for now.
However, anytime I opened the editor (mostly in the morning, this will be relevant later), I got the notification that there's a new version (1.110.0) available. I always clicked on the "Dismiss this Version" button, but then I got it again the next day.
Pulsar version
1.108.0
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Ubuntu 20.04
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
Install a non-latest version of Pulsar (e.g.: 1.108.0)
Open Pulsar
When the pulsar-updater notification appears, click on "Dismiss this version" (e.g.: 1.110.0)
Close Pulsar and wait 5 hours (*)
Open Pulsar again
Expected behaviour: the pulsar-updater won't show the notification about 1.110.0
What happened? pulsar-updater is there again
Notes: I found it in the code that 5 hours is the current expire time, but you don't need to wait 5 hours, you can edit the localstorage for pulsar-updater:last-update-check 's createdOn value to trigger the bug earlier.
Additional Information:
No response
The text was updated successfully, but these errors were encountered:
Thanks in advance for your bug report!
What happened?
I originally discovered this issue on 1.108.0, but I was able to reproduce it with the latest codebase. It started with #733 , I wasn't able to run Pulsar on Ubuntu 20.04, but then the issue was found and the official answer is that I should wait for the next release and stay on 1.108.0 for now.
However, anytime I opened the editor (mostly in the morning, this will be relevant later), I got the notification that there's a new version (1.110.0) available. I always clicked on the "Dismiss this Version" button, but then I got it again the next day.
Pulsar version
1.108.0
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Ubuntu 20.04
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
Notes: I found it in the code that 5 hours is the current expire time, but you don't need to wait 5 hours, you can edit the localstorage for
pulsar-updater:last-update-check
's createdOn value to trigger the bug earlier.Additional Information:
No response
The text was updated successfully, but these errors were encountered: