Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] didn#t save #603

Closed
4 tasks done
robbyatbln opened this issue Apr 16, 2022 · 12 comments
Closed
4 tasks done

[BUG] didn#t save #603

robbyatbln opened this issue Apr 16, 2022 · 12 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed 📌 Keep Open [ISSUE][PR] Prevent auto-closing 🛩️ Released 2.1.2

Comments

@robbyatbln
Copy link

Environment

Self-Hosted (Bare Metal)

Version

Dashy version 2.0.7

Describe the problem

Hello if i save the config to disk and reload the page all ist gone lokal save works but so i cant see it on other browser.
by robby

Additional info

No response

Please tick the boxes

@robbyatbln robbyatbln added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Apr 16, 2022
@liss-bot
Copy link
Collaborator

Welcome to Dashy 👋
It's great to have you here, but unfortunately your ticket has been closed to prevent spam. Before reopening this issue, please ensure the following criteria are met.

Issues are sometimes closed when users:

  • Have only recently joined GitHub
  • Have not yet stared this repository
  • Have not previously interacted with the repo

Before you reopen this issue, please also ensure that:

  • You have checked that a similar issue does not already exist
  • You have checked the documentation for an existing solution
  • You have completed the relevant sections in the Issue template

Once you have verified the above standards are met, you may reopen this issue. Sorry for any inconvenience caused, I'm just a bot, and sometimes make mistakes 🤖

@robbyatbln
Copy link
Author

hy liss-bot thats not helpfull, is there any tutorial how can i fix it looks like the conf.yml goes always back to the start conf.yml

@Lissy93
Copy link
Owner

Lissy93 commented Apr 16, 2022

There's some info about config troubleshooting in the Troubleshooting Guide.

But your question isn't very clear, do you have an error message, console output, etc?

@robbyatbln
Copy link
Author

robbyatbln commented Apr 16, 2022

https://1drv.ms/v/s!AtKm83CUlTGflbwGV3ivnSZhkBp44g
here is a Little try to explain thanks for helping

MP4 File

@Lissy93
Copy link
Owner

Lissy93 commented Apr 16, 2022

Thanks

Here's a couple of things to try:

  • Check if the conf.yml file on disk has been updated
  • Check the console for error messages
  • Try rebuilding the app (Config --> Rebuild)
  • Try clearing local data / using incognito (Config --> Clear data)

In the meantime, you can go to the export menu, and copy the changes to disk manually (Config --> Export). Or just use Docker, as I know this works in Docker.

@scumola
Copy link

scumola commented Jun 7, 2022

I'm having this same issue. Using as a proxmox container and from the latest git release. I just installed the Ubuntu 22.04 container image, git pull'd the source, did npm run build and npm run. I'm starting the app using crontab entry like:

@reboot cd /root/dashy && /usr/bin/npm start

I have the same exact issue. The config file gets saved (old one gets backed up), but when I hit the reload button in the browser, I get the original config values. Going back into the config file after the refresh happens, I see the original config values.. Prior to hitting the refresh button, I can see the new config values in the config file on the server-side. Doing a re-build does fix the issue, but I need to allocate 4Gb of ram and 4 cores to my container in order to build the application. Would be nice to not have to rebuild it every time I need to make a change so I can keep the container resources down to a minimum. To me this sounds like a weird caching thing somewhere maybe?

@Lissy93
Copy link
Owner

Lissy93 commented Jun 8, 2022

Lemme reopen...

@Lissy93 Lissy93 reopened this Jun 8, 2022
@scumola
Copy link

scumola commented Jun 9, 2022

So @Lissy93 I found that in the docker container, it happens too, but only immediately. I guess it's re-building behind the scenes? After a while, the docker container retains the new changes, but if Dashy is loaded into a new browser window right away after saving changes, I get the old version of the config for 30-ish seconds, and then the new changes show up.

In the proxmox container, the new changes don't take effect unless a manual build is triggered, then the changes are permanent.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Jun 9, 2022
@ghzgod
Copy link

ghzgod commented Jun 19, 2022

This is happening for me too. It takes quite some time to take the new changes after saving to disk. Sometimes it doesn't change at all, other times it makes a change 30-60 seconds after I hit save.

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Jun 20, 2022
@liss-bot
Copy link
Collaborator

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

@liss-bot liss-bot added the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Jul 20, 2022
@Lissy93
Copy link
Owner

Lissy93 commented Jul 20, 2022

Still relevant...
will be addressed in #799

@liss-bot liss-bot added 📌 Keep Open [ISSUE][PR] Prevent auto-closing and removed ⚰️ Stale [ISSUE] [PR] No activity for over 1 month labels Jul 21, 2022
@CrazyWolf13 CrazyWolf13 added ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed 🛩️ Released 2.1.2 labels Mar 3, 2024
@github-project-automation github-project-automation bot moved this to Awaiting Triage in Dashy V3 Mar 3, 2024
@CrazyWolf13
Copy link
Collaborator

Hi
This problems seems to be related to dashy not automatically rebuilding on changes, see #1479 and #1290 (comment)
A new release has just been published, which should fix this issue, so please upgrade to the latest version.
If this is not the case just respond back to this ticket and I'll reopen this issue.
Thanks and have a nice day.

@github-project-automation github-project-automation bot moved this from Awaiting Triage to Done in Dashy V3 Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed 📌 Keep Open [ISSUE][PR] Prevent auto-closing 🛩️ Released 2.1.2
Projects
Status: Done
Development

No branches or pull requests

6 participants