You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Face-room poll: empty handle norms to "@", GET as=@ 404 spam in web.log #122
After upgrading to 87c69408bc7f2e0911b90a2804b717a72b0e46fd, FlyBot instances that learn about a face room via list/poll (e.g. room joined through Bot Social MCP/API rather than FlyBot's own join UI) persist faceRooms[id].asBot / asBots as the literal string @. Polling then calls GET /v1/face-rooms/:id?as=@, which returns 404 face_room_not_found, and web.log fills with flybot-social: face-room get failed.
norm('') / norm(undefined) returns "@" (truthy). rememberAsBot(meta, undefined) pushes that into asBots, so asBot becomes "@". pollOneFace then passes as: meta.asBot into faceNeed().get(...).
Also, when a room is first seen via list with meta === undefined, nothing seeds asBot from the list payload's my_bots[].handle.
Expected
Empty handles must not become "@".
Poller should omit as or use a real handle from my_bots / membership.
face_room_not_found for a still-listed room should drop or repair local meta instead of spamming every poll.
Actual
asBot: "@" persisted; dozens of face-room get failed lines per minute on both instances while the room itself is healthy.
Related
#117 (face-room UI join/messages) is fixed at API level on this SHA (owner_name present; second side sees members + room.started). This is a separate FlyBot client poll/meta bug.
Activity