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
Is your feature request related to a problem? Please describe.
Using functions with callback cause stacktrace to be reseted - if this is even correct word, in example below you don't know what caused potential bug. On big servers it can be problematic.
Implement function like "getStackTrace" and option to enable/disable showing stacktraces during errors/warnings - server side mtaserver.conf configuration like:
<developmentMode>
<enabled>true</enabled> -- set to "false" in production
<errorLogging>stacktraces<errorLogging>
<warningLogging>stacktraces<warningLogging>
</developmentMode>
Server and client should be able to append stacktrace data therefore you know origin of error even if it happened in different resource on other side
Describe alternatives you've considered
Use forks
Additional context
After that you code above print more or less how javascript prints errors:
stack traceback:
stacktrace\server.lua:14: in triggered event
stacktrace\server.lua:2: in setTimer
stacktrace\server.lua:3: in setTimer
stacktrace\server.lua:6: in function <stacktrace\server.lua:3>
and in more complex examples: cross-resource, across-network stacktrace should add annotations and look like:
stacktrace\client.lua:10: triggered network event
stacktrace\server.lua:14: from network triggered event
stacktrace\server.lua:2: in setTimer
stacktrace\server.lua:3: in setTimer
stacktrace\server.lua:6: transition to other resource
otherResource\server.lua:6: in function <otherResource\server.lua:3>
Security Policy
I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Using functions with callback cause stacktrace to be reseted - if this is even correct word, in example below you don't know what caused potential bug. On big servers it can be problematic.
Describe the solution you'd like
Implement function like "getStackTrace" and option to enable/disable showing stacktraces during errors/warnings - server side mtaserver.conf configuration like:
Server and client should be able to append stacktrace data therefore you know origin of error even if it happened in different resource on other side
Describe alternatives you've considered
Use forks
Additional context
After that you code above print more or less how javascript prints errors:
and in more complex examples: cross-resource, across-network stacktrace should add annotations and look like:
Security Policy
The text was updated successfully, but these errors were encountered: