Built from User Interface Validation Warning: .sections[0] should NOT have additional property: filteredItems

[thorrrr]

Environment

Self-Hosted (Docker)

System

Arcclinux XFCE Any Browser Warning Shows

Version

Dashy version 2.1.1

Describe the problem

Clean install used example to conf file to launch then deleted the two example section that are in by default.
I then from a virgin conf fie build 3 sections bog standard all the same local apps from servers wit all same option open new tab and check status all created by User Interface.

All items appear look fine except several status checks show red or yellow -to grey even though they are open!
But main issue is if i check Update Confuration area it shows Warnings
"Validation Warning: .sections[0] should NOT have additional property: filteredItems"

https://i.imgur.com/bD2g7jD.png

Additional info

No response

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[jrozelle]

same here

[awptechnologies]

Same here. When checking the conf.yml in data directory i don't see them. When viewing config on web page they show up. I have tried to delete and save config but they are still present on refresh.

[awptechnologies]

Also when saving config from web page it adds this to the conf.yml above all the titles.... &ref_0

[dflahaut]

same issue for me ...

[LarryT8959]

I have the same problem. Has anyone received help on this?
Thanks

[mamekedi]

Same issue here

[J-Davis21]

+1

[NATroutter]

i have same issue
it would be nice to have solution for this....

[louisjg]

Also have this issue.

[Sulphuric-16]

Just to add, I am also having the same issue. Appears just to be a bug for now.

[acecase]

Looks like this is a bug : )

I'm curious if this is causing some build/update script on the backend to fail because I also can't get changes that I make in the ui editor to stick/update reliably. If I edit the conf.yml directly and build they work fine.

Just wondering if I should keep troubleshooting that or wait for this to be fixed.

[Vyerni]

Even when those sections are removed, they appear to be re-added automatically

[LarryT8959]

Same here. I avoid using UI for editing, only in config file.Sent from my iPhoneOn Dec 3, 2023, at 2:26 PM, Vyerni ***@***.***> wrote: Even when those sections are removed, they appear to be re-added automatically —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[Chay751]

+1

[upstairs-at-erics]

same here

[Chay751]

您好，已收到邮件！

[pheiduck]

Still a valid thing, have this issue too.
But it is just a warning.

[FuXXz]

Surely you can expect something.
Namely that this project is marked as "inactive" for the protection of humanity.
Some maintainers do this so that software like this doesn't waste my time.
Despite the respect for the programmer, I really have respect for such achievements. But to leave a bunch of bugs unanswered for years is just disgusting.

I discovered the software a few days ago and tested it in several environments. Local, VPS, Docker, Docker on stock Ubuntu, unraid, Synology. It doesn't matter, I get half the issue list up and down many errors.
All known, for many months.

[LarryT8959]

Let me know if you find something.

…

On Feb 17, 2024, at 3:43 AM, Alex Griffin ***@***.***> wrote: Let's figure out how to fix it then, it's probably pretty simple. — Reply to this email directly, view it on GitHub <#1361 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTIOBIO2GZHJKN6SDK3YUBUSTAVCNFSM6AAAAAA6O3DPNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZHEYDGNZUHA>. You are receiving this because you commented.

[CrazyWolf13]

See here for a potentian fix. #1403 (comment)
I'll try to push a fix if I can confirm that it fixes the problem

[sorousheta]

same issue

[CrazyWolf13]

Hi @sorousheta
Hi all

This issue has / should be resolved, a PR with a fix was submitted and accepted.
As soon as the 2.1.2 wil release it should be resolved for everyone.

Can you confirm that you are still experiencing this issue with the last build from source?
https://github.com/Lissy93/dashy?tab=readme-ov-file#deploying-from-source-

Note: For the warnings in the log to go away, a user needs to rebuild, edit any item through web-ui, then rebuild again.
Then all the errors should go away.

GitHub - Lissy93/dashy: 🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more!

🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more! - Lissy93/dashy

[CrazyWolf13]

Thanks to @Lissy93 the faulty tags inside the conf.yml will get stripped out automatically, so there is no need to rebuild, edit through gui and rebuild again.

[LarryT8959]

I still have the issue. When will new version be released?

…

On Feb 27, 2024, at 12:45 AM, Tobias ***@***.***> wrote: Hi @sorousheta <https://github.com/sorousheta> Hi all This issue has should be resolved, a PR with a fix was submitted and accepted. As soon as the 2.1.2 wil release it should be resolved for everyone. Can you confirm that you are still experiencing this issue with the last build from source? https://github.com/Lissy93/dashy?tab=readme-ov-file#deploying-from-source- Note: For the warnings in the log to go away, a user needs to rebuild, edit any item through web-ui, then rebuild again. Then all the errors should go away. — Reply to this email directly, view it on GitHub <#1361 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTJXHEVQHAHTCKZO463YVVXIPAVCNFSM6AAAAAA6O3DPNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVHAZTCMRUGQ>. You are receiving this because you commented.

[CrazyWolf13]

Should get released in the next few days (maybe this or next week)

[liss-bot]

The fix for this issue has now been released in 2.1.2 ✨

If you haven't done so already, please update your instance to 2.1.2 or later. See 2.1.2 for full info.

Feel free to reach out if you need any more support. If you are enjoying Dashy, consider supporting the project.