Upgrade 0.47.7 to 0.48.5 causes duplicate listing of dashboard names

HI,

Just upgraded to 0.48.5 from 0.47.7 and i am seeing double/triple :slight_smile: in some collections, some dashboard names are shown several times (2-3 times), but the links point to the same dashboard.

Sometimes, editing the dashboard (no changes, just "edit" then "save") made the duplicate disappear, but not always...

Any ideas on how to clean this ?

image

Running Metabase as a service on Debian 18.04 with latest JDK

# java --version
openjdk 21.0.2 2024-01-16 LTS
OpenJDK Runtime Environment Microsoft-8905927 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Microsoft-8905927 (build 21.0.2+13-LTS, mixed mode, sharing)
# cat /etc/systemd/system/metabase.service
[Unit]
Description=Metabase server
After=syslog.target
After=network.target

[Service]
WorkingDirectory=/opt/metabase/
#ExecStart=/usr/bin/java -jar /opt/metabase/v0.47.7/metabase.jar
ExecStart=/usr/bin/java -jar /opt/metabase/v0.48.5/metabase.jar
EnvironmentFile=/etc/default/metabase
User=metabase
Type=simple
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=metabase
SuccessExitStatus=143
TimeoutStopSec=120
Restart=always

[Install]
WantedBy=multi-user.target

Thanks,
Gabriel

Do you see actually duplicate rows in the dashboard table in the database?

I can check this, but i don't know in which table to look into...

Found it:

Metabase screen:

PHPMyAdmin:

Noticed that, if i edit the dashboard name, add a character, then remove it, it cleans up:

Same here, I also found some duplicates after updating from 0.47.6
After the update, it also set "Last Updated Date" to the date of the update (for all questions/dashboards). Which is embarrassing, now I don't recognize the old questions...

same thread as Questions and Dashboards Duplicated in UI

unfortunately we need to find a way to reproduce this

@gabriel.moscalu seems that the DB has unique dashboards, is that correct? then this should be a frontend issue

Hi @Luiggi

i tend to agree with you: the DB records look OK, it's probably a matter of frontend...

Maybe a way to clear the caches & reload everything from DB might help, or maybe a way to clean restart?