-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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]: sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported #4309
Comments
I am unable to reproduce this error. Maybe you can make a short video so I can better see what is going on. |
i have the same issue when i try to deploy a nodejs app with nixpacks |
Sorry for the late reply output.mp4 |
Same there. I started getting this when I redeployed a container and it failed, rolling back to the previous one. The metrics were set to last 5 minutes, but there was no data yet, and this started popping every few seconds. I am not 100% confident in the origin of the error though, but I can say I do have the metrics activated too and that they don't load so it seems like the error is coming from there. Edit: five minutes have passed (notice the time in the tray) and it did stop popping up and it started showing data. Seems like that was indeed the cause. |
Related to coollabsio#4309 Fix the 'sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported' error on the metrics page. * Update the `getMemoryMetrics` method in `app/Models/Server.php` to handle NULL values for the "usedPercent" field by setting them to 0.0. * Add a check for NULL values in the `getMemoryMetrics` method before converting to float64.
Error Message and Logs
sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.369
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
No response
The text was updated successfully, but these errors were encountered: