Unexpected Application Error!
A <Select.Item /> must have a value prop that is not an empty string. This is because the Select value can be set to an empty string to clear the selection and show the placeholder.
HR<@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:541:15021
yb@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:38:16998
eC@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:1571
b_@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:46001
v_@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39768
pI@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39696
Bp@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39547
o1@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:35914
dC@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:36717
ko@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:38:3274
zn/<@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:34246
I'd be happy to provide any additional details if necessary.
Originally created by @safeboot on GitHub (Aug 31, 2024).
## How to Replicate
1. Create a Build and leave the Builder blank
2. Go into Builders and create Builder
3. Head back into Build section and select any Build
## More Details
- Core Version: v1.13.4
- Periphery Version: v1.13.29 / 2463ed38
- Docker Version: v27.1.1
- Operating System: TrueNAS Scale v24.10-BETA01
## Error Message
```
Unexpected Application Error!
A <Select.Item /> must have a value prop that is not an empty string. This is because the Select value can be set to an empty string to clear the selection and show the placeholder.
HR<@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:541:15021
yb@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:38:16998
eC@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:1571
b_@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:46001
v_@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39768
pI@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39696
Bp@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:39547
o1@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:35914
dC@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:36717
ko@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:38:3274
zn/<@http://192.168.0.100:9120/assets/index-Cj-U6oYk.js:40:34246
```
I'd be happy to provide any additional details if necessary.
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.
@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](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.
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.
@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
Additionally here is the log file I compiled so you can trace what happened. After 66d31f104219023c6faa8ebe is when the bug arose, I have no idea what caused it. Hope this helps. monitorlog.txt
@safeboot commented on GitHub (Sep 1, 2024):
Additionally here is the log file I compiled so you can trace what happened. After `66d31f104219023c6faa8ebe` is when the bug arose, I have no idea what caused it. Hope this helps.
[monitorlog.txt](https://github.com/user-attachments/files/16828126/monitorlog.txt)
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.
@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.
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?
@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?
Awesome, that seems to have fixed it. Although I had to rename my folders from monitor-... to komodo-... 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.
@safeboot commented on GitHub (Sep 2, 2024):
Awesome, that seems to have fixed it. Although I had to rename my folders from `monitor-...` to `komodo-...` 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.
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.
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.