Repository navigation
Voxeltron 0.1.3
0.1.3 carries the fixes from the last round of 0.1.2 testing, which were
finished after the 0.1.2 release was cut, and three fixes found by testing
the published 0.1.2.
Security
- With Loki configured,
query_logsreads only logs for containers that belong to a Voxeltron deployment, and masks the deployment's secret values and personal data in every line, as the container-log path already did. Before, it passed the requested container name straight into a Loki query, so it could read any container's logs in Loki, unmasked. Output is capped at 64 KiB. structured_logsreturns only entries for containers that belong to a Voxeltron deployment, masked the same way, and its counts cover only what it returns. It still searches the daemon's local log store, not Loki.
Fixed
investigate_incident,analyze_logs,correlate_eventsandsuggest_fixanswer in about a second instead of timing out after 30 seconds. Each one used to start a second, hidden agent session with its own model calls. They now make no model calls:analyze_logssummarises the logs it is given, and the other three run root cause analysis directly, with a 3 second limit on each log and metric query, and report any evidence source that is not configured or timed out. They are now available without an AI provider too.suggest_fixanalyses the service the issue is about (service, orcontext.apporcontext.service). Before, it always looked up a placeholder service and failed. Without a known service it still returns recommendations and says root cause analysis was skipped.investigate_incidentandcorrelate_eventsno longer analyse a placeholder service when none is given. They skip root cause analysis, say why, and return their other findings.- When the model asks for several read-only tools in one reply, up to three more of them run straight away instead of each costing another model round trip. Tools that change anything still get their own turn.
- On Ubuntu, unattended upgrades no longer restart
voxeltrondin the middle of a deploy. The installer adds/etc/needrestart/conf.d/voxeltron.conf, so needrestart listsvoxeltrondas a deferred restart. Restart it yourself in a maintenance window after security updates. When you remove Voxeltron, delete that file too. vxl bootstrapwrites the same needrestart file as the installer, whether you log in as root or as a user with passwordless sudo.vxl daemon upgradewrites it too, so servers bootstrapped earlier get it on their next upgrade. Hosts without needrestart are left alone.vxl deployandvxl deploy productwait up to 10 seconds for a daemon that is restarting, instead of failing at once with "connection refused". Requests are sent only once a connection is up, so nothing is ever sent twice.scripts/install.sh --versionon Ubuntu downloads the version you asked for. Before, it read/etc/os-releasein a way that replaced the requested version with Ubuntu's own (such as "24.04.4 LTS (Noble Numbat)"), so the download failed. The site installer was not affected.vxl-admin --versionprintsvxl-admin <version>, asvoxeltrond --versionandvxl --versiondo. Before, it was rejected as an unexpected argument.- Release archives built on macOS no longer carry macOS extended attributes, so GNU tar on the server no longer prints "Ignoring unknown extended header keyword" while unpacking them.
Third-party notice. The Linux voxeltrond and vxl-admin include BusyBox, under the GNU General Public License, version 2 only. Its complete source is attached to this release (busybox_1.36.1-6ubuntu3.1.dsc and its files, with BUSYBOX-SOURCE-README.md); the licence and written offer are in NOTICE-busybox.md.