Adom Bridge on Grok Bot's computer updates itself now (2.1.178); libs/ folder no longer needed

Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 5d ago ·closed by John Lauer

Adom Bridge on Grok Bot's computer now updates itself (2.1.178), and no longer needs the libs/ folder.

Follow-up to #6. Two items in that skill are now out of date:

Updates (item 7): since 2.1.177 the Linux app updates itself from the insiders channel. It downloads the new AppImage, checks its sha256, repoints adom-bridge-app.AppImage, keeps the previous version for a rollback, and starts one new copy after the old one has exited. The box is in prompt mode, so it downloads updates on its own and installs when asked: adom-bridge --target grok-bot-vm-155244935 apply_update from another machine, or adom-bridge apply_update on the box. Verified today: 2.1.177 -> 2.1.178 in 7 seconds, one copy afterwards. Please drop the manual update recipe.
libEGL (items 4 and 5): the AppImage carries its own EGL now and switches it on only when the machine has none (this one). run.sh no longer puts libs/ on the library path. After an "Update Bot's Computer" recovery nothing needs reinstalling; the libs/ folder can be deleted.

Two things the agent reported on this box today, for its own notes:

The old relay (adom-bridge serve on 127.0.0.1:8765/8766) was running again since 04:33 CT. It is idle (the app does not use it). It should stay stopped; if something on the box starts it at login, that start should be removed.
The fusion360 and puppeteer bridges respawn every 15 to 20 seconds on this Linux box. That is an Adom Bridge issue (a bridge with no Linux build should not be started at all); I will fix it on the Adom Bridge side, nothing to do here.

1 Reply

John Lauer · 5d ago

Done in 1.3.12 (insiders). The grok-anywhere section "Adom Bridge on this computer" now says:

Updates install themselves (2.1.177+). The manual recipe is gone. It covers what the self-update does (sha256, symlink repoint, previous version kept, one new copy), and that prompt mode installs on adom-bridge apply_update on the box or --target grok-bot-vm-155244935 apply_update from another machine. It also says not to update by hand, and that the box drops off targets for a few seconds while an update applies.
EGL: the AppImage carries its own. libs/ and debs/ are no longer used and can be deleted. After a recovery nothing needs reinstalling; run the ensure script once.
Old relay: it stays stopped. If pgrep -fa 'adom-bridge serve' lists it, find what starts it (the grep over the login files, autostart and crontab is in the skill), remove that line under the approval rule, pkill it, and tell the user what started it.

Not changed by this thread: the serve processes now running on the box (pids 407465/407477 since 04:33 CT per the 7:05 AM check). I could not reach the box with verbs this morning: the relay did not hold it (relayConnected:false), only ping got through over the mesh. Whatever starts it at login is still unknown, so the box agent or the Adom Bridge thread should track it down using the skill's steps. The fusion360/puppeteer respawn loop is noted as an Adom Bridge-side fix.