secondlife / secondlife/viewer

Lua Debug Console Run button not functioning

Open
#1,909 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug triage
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Environment

Second Life Release 7.1.9.9746418574 (64bit)
Release Notes

You are at 6.9, 152.5, 23.0 in Pasta Cake located at simhost-07c6878b4a755f512.agni
SLURL: http://maps.secondlife.com/secondlife/Pasta%20Cake/7/152/23
(global coordinates 332,039.0, 305,560.0, 23.0)
Second Life Server 2024-06-11.9458617693
Release Notes

CPU: 12th Gen Intel(R) Core(TM) i9-12900HK (2918.4 MHz)
Memory: 32440 MB
OS Version: Microsoft Windows 10 64-bit (Build 19044.3086)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2

Windows Graphics Driver Version: 31.0.15.4659
OpenGL Version: 4.6.0 NVIDIA 546.59

Window size: 1278x1368
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 10000kbit/s
LOD factor: 1.5
Render quality: 4
Texture memory: 4095MB
Disk cache: Max size 1638.4 MB (100.0% used)

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Studio 2.02.20
Dullahan: 1.14.0.202310131404
CEF: 118.4.1+g3dd6078+chromium-118.0.5993.54
Chromium: 118.0.5993.54
LibVLC Version: 3.0.16
Voice Server Version: Not Connected
Packets Lost: 0/990 (0.0%)
July 02 2024 08:38:14

Description

Run button in Lua Debug floater is no longer running opened scripts
Scripts will automatically run once after opening them via Browse. It's not possible to re-run them with Run after this.
Current behaviour: https://gyazo.com/124661890afc4f49a7657ed8fe6c4ef0
Previous behaviour: https://gyazo.com/0dfa69a474d7310e9bb35757952c383f (Second Life Test 7.1.7.9018993715 )

Reproduction steps
  1. Open any script via Lua Debug console
  2. Stop the script execution if required and click Execute to clear the console
  3. Click Run

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the problem from the Lua Debug console by opening a script, stopping it if needed, clearing the console with Execute, and clicking Run. Trace the console's Run action and compare it with the previous behavior shown in the issue; done means an opened script runs again after being stopped or cleared.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.