device (table) Content
| 01JR04CD2SDQ3GYQP28AQJSK74 | buildkitsandbox | "SINGLETON" | UNKNOWN | { "global_cpu_info": { "cpu_usage": 17.555683, "name": "cpu", "vendor_id": "", "brand": "", "frequency": 0 }, "cpus": [ { "cpu_usage": 0.0, "name": "cpu0", "vendor_id": "AuthenticAMD", "brand": "AMD EPYC 7763 64-Core Processor", "frequency": 3240 }, { "cpu_usage": 0.0, "name": "cpu1", "vendor_id": "AuthenticAMD", "brand": "AMD EPYC 7763 64-Core Processor", "frequency": 3240 }, { "cpu_usage": 0.0, "name": "cpu2", "vendor_id": "AuthenticAMD", "brand": "AMD EPYC 7763 64-Core Processor", "frequency": 3240 }, { "cpu_usage": 0.0, "name": "cpu3", "vendor_id": "AuthenticAMD", "brand": "AMD EPYC 7763 64-Core Processor", "frequency": 3240 } ], "physical_core_count": 2, "total_memory": 16766767104, "free_memory": 5641416704, "available_memory": 15275843584, "used_memory": 1490923520, "total_swap": 4294963200, "free_swap": 4294963200, "used_swap": 0, "uptime": 190, "boot_time": 1743761132, "load_average": { "one": 1.58, "five": 0.73, "fifteen": 0.28 }, "name": "Debian GNU/Linux", "kernel_version": "6.8.0-1021-azure", "os_version": "12", "long_os_version": "Linux 12 Debian GNU/Linux", "distribution_id": "debian", "host_name": "buildkitsandbox" } | {"sqlpage":"^0.34.0","pgwire":"^0.22.0","rusqlite":"^0.32.1","sqlean":"0.27.1"} | 2025-04-04 10:08:43 | UNKNOWN | 2025-04-04 10:31:35 |
Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.
Error in query number 6:
Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:
SELECT 'text' AS component,
(SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
⬆️
'(Page ' || $current_page || ' of ' || $total_pages || ') ' ||
Backtrace
sql parser error: Expected: ), found: $current_page at Line: 42, Column: 35"console/content/table/device.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.