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 }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
Just like in any major code language, we should have a try/catch scenario to intercept events that trigger script errors, so we can handle them gracefully.
For example: An HTTP request from an external source is made to an in-world server, to deliver an inventory item of a specified name. Currently, if this item does not exist, a script error is thrown and all subsequent lines are executed as if nothing went wrong. In this scenario, it would send back a 200 response, not knowing something went wrong.
Ideally, in this scenario, we should be able to catch when the script error occurs and return something other than a 200.
Why is this feature important to you? How would it benefit the community?
It would be of benefit to any sort of inventory delivery system, so an error response can be appropriately handled, perhaps immediately being able to send a notification to developers and process a refund without waiting on a timeout, or (heaven forbid) accepting payment for something unable to be delivered.
Similar logic can be applied for cases such as llRezObject, where errors can be cleanly handled rather than filling DEBUG_CHANNEL with data.
Original Jira Fields
Field
Value
Issue
BUG-229174
Summary
Add try/catch to LSL
Type
New Feature Request
Priority
Unset
Status
Closed
Resolution
Unactionable
Reporter
Amalia Irata (amalia.irata)
Created at
2020-08-02T23:32:20Z
Updated at
2020-08-05T17:50:34Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2020-08-05T12:50:34.024-0500',
'How would you like the feature to work?': 'Just like in any major code language, we should have a try/catch scenario to intercept events that trigger script errors, so we can handle them gracefully. \r\n\r\nFor example: An HTTP request from an external source is made to an in-world server, to deliver an inventory item of a specified name. Currently, if this item does not exist, a script error is thrown and all subsequent lines are executed as if nothing went wrong. In this scenario, it would send back a 200 response, not knowing something went wrong.\r\n\r\nIdeally, in this scenario, we should be able to catch when the script error occurs and return something other than a 200.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': 'It would be of benefit to any sort of inventory delivery system, so an error response can be appropriately handled, perhaps immediately being able to send a notification to developers and process a refund without waiting on a timeout, or (heaven forbid) accepting payment for something unable to be delivered.\r\n\r\nSimilar logic can be applied for cases such as llRezObject, where errors can be cleanly handled rather than filling DEBUG_CHANNEL with data.',
}
The text was updated successfully, but these errors were encountered:
Incoming suggestions are reviewed in the order they are received by a team of Lindens with diverse areas of expertise. We consider a number of factors: Is this change possible? Will it increase lag? Will it break existing content? Is it likely that the number of residents using this feature will justify the time to develop it? This wiki page further describes the reasoning we use: http://wiki.secondlife.com/wiki/Feature_Requests
This particular suggestion, unfortunately, cannot be tackled at this time. However, we regularly review previously deferred suggestions when circumstances change or resources become available.
We are grateful for the time you took to submit this feature request. We hope that you are not discouraged from submitting others in the future. Many excellent ideas to improve Second Life come from you, our residents. We can’t do it alone.
Thank you for your continued commitment to Second Life.
How would you like the feature to work?
Just like in any major code language, we should have a try/catch scenario to intercept events that trigger script errors, so we can handle them gracefully.
For example: An HTTP request from an external source is made to an in-world server, to deliver an inventory item of a specified name. Currently, if this item does not exist, a script error is thrown and all subsequent lines are executed as if nothing went wrong. In this scenario, it would send back a 200 response, not knowing something went wrong.
Ideally, in this scenario, we should be able to catch when the script error occurs and return something other than a 200.
Why is this feature important to you? How would it benefit the community?
It would be of benefit to any sort of inventory delivery system, so an error response can be appropriately handled, perhaps immediately being able to send a notification to developers and process a refund without waiting on a timeout, or (heaven forbid) accepting payment for something unable to be delivered.
Similar logic can be applied for cases such as llRezObject, where errors can be cleanly handled rather than filling DEBUG_CHANNEL with data.
Original Jira Fields
The text was updated successfully, but these errors were encountered: