Config panel not showing despite working app
Opened this issue · 8 comments
Hi all,
I'm facing a small issue where the config panel for the app doesn't load, even though all backups are done and successful !
Adding more details here, I have 3 instances
- 2 instances where the backups are successful, and these are the ones where I can't access the config panel (that I could access before the first backup)
- 1 instance where the backup is failed, where I can access the config panel without any problem.
Therefore, it seems that this problem arises only when the latest backup was successful !
Any idea on how to solve this ? It's a real blocker !
This happens to me too, my yunohost-api.log shows:
logs
2024-06-09 13:54:58,401 DEBUG moulinette.actionsmap process - processing action [24231.63]: yunohost.app.info with args={'app': 'borg', 'full': True}
2024-06-09 13:54:58,432 WARNING yunohost.app (unknown function) - [24231.63] Failed to get label for app borg ?
2024-06-09 13:54:58,432 DEBUG moulinette.actionsmap process - action [24231.63] executed in 0.031s
2024-06-09 13:54:58,433 INFO geventwebsocket.handler (unknown function) - 127.0.0.1 - - [2024-06-09 13:54:58] "GET /apps/borg?full&locale=de HTTP/1.1" 200 12220 0.034057
2024-06-09 13:54:58,497 DEBUG geventwebsocket.handler (unknown function) - Initializing WebSocket
2024-06-09 13:54:58,497 DEBUG geventwebsocket.handler (unknown function) - Validating WebSocket request
2024-06-09 13:54:58,498 DEBUG moulinette.actionsmap process - loading python module yunohost.user took 0.000s
2024-06-09 13:54:58,498 DEBUG moulinette.actionsmap process - processing action [24231.64]: yunohost.user.permission.list with args={'apps': [], 'short': False, 'full': True}
2024-06-09 13:54:58,504 DEBUG moulinette.actionsmap process - action [24231.64] executed in 0.006s
2024-06-09 13:54:58,506 INFO geventwebsocket.handler (unknown function) - 127.0.0.1 - - [2024-06-09 13:54:58] "GET /users/permissions?full&locale=de HTTP/1.1" 200 880 0.009804
Where the Failed to get label for app borg ? gets my attention.
Same issue here, whether it's a fresh install with no repo initialized, an app with failed backup or a successful one...
Same issue on a fresh install... but thanks for the work guys !!!
Same issue here!
@clicit @elbubar @Enthouane @shukon FYI this bug is solved with testing branch, that should be merged soon
Great news, thanks !