3 Commits

Include renames

Author	SHA1	Message	Date
dc	3445107d9a	fix: name the startupservice launcher button "Show log"	2026-10-23 03:01:23 +00:00
dc	ad2da45389	fix: offer the launcher on the globvars failure modal too ... The globvars check in licence.service reports a failed startupservice run as well, so its modal needs the service name for the new-window button - that was the fourth startup failure path and the only one still a dead end. Also guard the decodeURIComponent call in the Cypress drive/folder intercept, so a lone '%' in a URL cannot throw inside the handler and abort the request.	2026-10-23 02:17:49 +00:00
dc	40f61331aa	feat: run startupservice in a new window from its error modal ... When the startupservice fails, the modal is a dead end: the adapter returned no log, so there is nothing to act on. The modal now offers a button that runs the same service through the JES / STP web app in a new browser window, where the SAS log is returned as the page body. `_debug=131` is always added (the log is the point), and `_executionTasks` is never included, so on Viya the run is not submitted as a Compute task and cannot hit the execution-task timeout. The URL is built by `buildServiceUrl`, which works for SAS 9, Viya and SASjs Server, and is the same shape the deploy configurator already uses to open makedata. The startup failure modals now carry the service name, which is what shows the button: all three failure branches (malformed response, missing properties, request rejected) pass `public/startupservice`.	2026-10-23 01:15:31 +00:00