šŸ“ƒ Lua Alpha

General discussion and feedback on Second Life's SLua Alpha
Bugs with the Lua Plugin Websocket
Tested on: Viewer: Second Life Release 26.5.0.42122621216 (64bit) Simulator: Luau 2026-11-10.42914476267 OS: Ubuntu 26.04 The viewer crashes when the editor websocket port is already in use. If the viewer tries to start its websocket server on a port that is already bound (by another viewer), the viewer crashes — no graceful error, no fallback. Repro: run two viewers with their editor servers configured on the same port; the second one dies. system.ping response timestamp is truncated to signed int32. Spec: "The original timestamp from the request, echoed by the editor server." We send a ms epoch (~1.795e12); the response returns -222971890, which is exactly our value mod 2^32 interpreted as signed int32 (verified arithmetically against the send time). Since any real ms epoch overflows int32, the echo is always negative. system.ping response server_time = -2147483648 (INT32_MIN). Spec: "Unix timestamp in milliseconds when the response was generated." Every ping returns exactly INT32_MIN — looks like an uninitialised int32. The server clearly knows its time (system.getStats.uptime advances correctly). Compile errors return no result on the websocket. Saving a syntactically invalid script (content: just ] ) via object.content.save returns success: true with no compiled field and no diagnostics, and no script.compiled notification arrives — although the spec says compile diagnostics come back inline in the response. runtime.error's ItemRef.language reports "lsl" for Luau scripts that fail to compile. A Luau script ( object.list correctly shows vm=luau) that faults at runtime sends item.language: "lsl"; only the lua_script stack frames reveal it's Lua. This is partially a duplicate of https://feedback.secondlife.com/slua-alpha/p/scripts-with-a-compiler-error-forget-their-vm 6. When clicking "Explore in IDE", the object is not actually published unless: a websocket client is already connected to the viewer's editor server, or launching code (VS Code) succeeds In all other cases the click silently does nothing — no error shown, only a log warning. How to observe "not published": call object.list on the websocket (no parameters; returns the currently explored objects with their inventories) — it returns an empty list even though the button claims the object is being explored. The viewer log shows the cause at click time: WARNING LLProcess::launch : Could not locate 'code' on PATH -- launch will likely fail WARNING ScriptEditorWS launchVSCode : Failed to launch VS Code. ... with no corresponding publish entry. (With a websocket client connected, the same click publishes correctly — verified.) 7. system.getStats reports zeroed counters and an ambiguous method count After dozens of successful calls across multiple connections ( system.status , object.list , object.request , object.unpublish ), the response still shows "total_requests_handled": 0 and "total_notifications_sent": 0 . If total_notifications_sent counts notifications sent by the server, it should be at least as high as the number of completed handshakes, since every connection receives a session.ok notification — it stays 0 . The same response shows "global_method_count": 1 ; the server's own log shows exactly one global method registered at startup ( system.getStats ) with all other methods apparently per-connection. global_method_count may thus be as intended, but this should be clarified in the documentation. system.getStats is not in the public protocol documentation; if any of these fields are placeholders, it should be documented in external-editor-json-rpc.md --- These were tested with the help of an AI agent. Full notes in my repository: https://github.com/tapple/slsync
0
Ā·
Bug
lsl-luau discrepancy with mono: register exhaustion with concatenation & possible performance issue of list string casting
While trying to stress test / benchmark a comparison for (string) list and llDumpList2String , I came across a register exhaustion for a script in lsl-luau that works in mono. I'm reporting both as one canny because I'm unsure if these are related. A) First, for the benchmark: In LSO: === list-to-string benchmark: 100 iterations x 300 items === (string)list total = 1040.432007 ms mean = 10.404320 ms llDumpList2String total = 1896.921143 ms mean = 18.969212 ms ratio (string/dump) = 0.548485x === DONE === In Mono: === list-to-string benchmark: 100 iterations x 300 items === (string)list total = 226.023000 ms mean = 2.260230 ms llDumpList2String total = 316.186000 ms mean = 3.161860 ms ratio (string/dump) = 0.714842x === DONE === In LSL-LUAU: === list-to-string benchmark: 100 iterations x 300 items === (string)list total = 2287.902000 ms mean = 22.879020 ms llDumpList2String total = 589.087000 ms mean = 5.890871 ms ratio (string/dump) = 3.883810x === DONE === === list-to-string benchmark: 100 reps x 500 items === (string)list total = 4536.675000 ms mean = 45.366750 ms llDumpList2String total = 1022.474000 ms mean = 10.224740 ms ratio (string/dump) = 4.436957x === DONE === Something about how casting a list to a string is way worse in lsl-luau. My thought was that it's likely something that could be optimized if llDumpList2String is about 4x faster already. B) Second, a test script of the discrepancy is the following default { state_entry() { integer i = 1; string s = (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i ; llOwnerSay(s); } } It prints "1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111" in mono, but in lsl-luau it fails to compile with "Out of registers when trying to allocate 1 registers: exceeded limit 255" I doubt there are many real use cases where this would have an impact after switching off mono, but it is still a notable difference.
2
Ā·
Bug
Ā·
tracked
Load More
→