mirror of
https://github.com/moghtech/komodo.git
synced 2026-03-22 16:40:41 -05:00
[Bug] "A <Select.Item /> must have a value prop that is not an empty string." after creating a Builder #37
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @safeboot on GitHub (Aug 31, 2024).
How to Replicate
More Details
2463ed38Error Message
I'd be happy to provide any additional details if necessary.
@mbecker20 commented on GitHub (Aug 31, 2024):
Thank you for the clear bug report.
To start, I added some more validations around the Select Items in this commit. This will avoid the UI breaking with this message, but may not fix an underlying issue: https://github.com/mbecker20/monitor/commit/697a00ed61f3c1b2b5a6d9593da482c066fc41d0. This will be included in 1.14 coming very shortly.
I also added a backend validation preventing creating of resource with empty string "" name. I doubt this is your issue of course but it reminded me that empty string names will cause issues all over the place.
Unfortunately I can't reproduce this on Mac + Brave browser, what browser are you using? And it would be great to provide a screen recording while reproducing the issue so I can see exactly the steps you take.
@safeboot commented on GitHub (Sep 1, 2024):
Hey, so here is the update. I have a test server that is running the same versions as my main one (the one with the issue) however when I try to replicate it, it seems to be working normally. I am using Firefox on Windows 11. I have uploaded a screen recording so please take a look at my issue, as well as a screen recording of me trying to replicate the issue on my test server.
https://github.com/user-attachments/assets/b46f4ba2-c0f0-4620-96d5-c898f5beec15
https://github.com/user-attachments/assets/800513aa-39e8-4b65-ab69-f184308ddfe0
@safeboot commented on GitHub (Sep 1, 2024):
Additionally here is the log file I compiled so you can trace what happened. After
66d31f104219023c6faa8ebeis when the bug arose, I have no idea what caused it. Hope this helps.monitorlog.txt
@safeboot commented on GitHub (Sep 2, 2024):
Hey, would it help you out if I could send over the database and anything regarding the app? I'll see if I can make a copy and replicate the issue.
@mbecker20 commented on GitHub (Sep 2, 2024):
Hey, I don't need anything else at this point, I just got 1.14 rc out this weekend so was focused there. Any chance you could try out this release and see if it fixes the issue?
@safeboot commented on GitHub (Sep 2, 2024):
Awesome, that seems to have fixed it. Although I had to rename my folders from
monitor-...tokomodo-...so I have lost my database somehow (lol I don't mind, nothing prod related was on there) but now everything seems to be working.@mbecker20 commented on GitHub (Sep 2, 2024):
Awesome thanks! If it's using a docker volume for the database data, you just need to attach the old one to Mongo. I added a note about this to the release notes.