Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Javascript Error #43

Open
gjzs opened this issue Jul 17, 2024 · 1 comment
Open

Javascript Error #43

gjzs opened this issue Jul 17, 2024 · 1 comment

Comments

@gjzs
Copy link

gjzs commented Jul 17, 2024

This bugreport was generated by Othernet Skylark:

An unexpected error occured, maybe a bug.

Please report this if you think this is a bug.
Include a brief description on how the error occured, and if you can; how to replicate it

Expected behaviour clicked on news, but received error message

Actual behaviour clicked on the news icon

Steps to reproduce the error closed api and tried again, same error

(Optinal) Browser and OS information Mozilla Firefox 128.0 (64-bit), Windows 11 Pro

128.0 (64-bit) --
{"userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0","platform":"Win32","language":"en-US","appVersion":"5.0 (Windows)"}

Stack Trace

ApplicationNewsWindow.prototype.init/populate/<@http://192.168.11.175/packages/skylark/News/combined.js:109:56
VFS.scandir/<@http://192.168.11.175/osjs.js:11729:14
_finished@http://192.168.11.175/osjs.js:11558:15
request/vfsRequestCallback/</<@http://192.168.11.175/osjs.js:11539:23
_Handler.prototype.onVFSRequestCompleted@http://192.168.11.175/osjs.js:11253:5
request/vfsRequestCallback/<@http://192.168.11.175/osjs.js:11533:13
scandir/<@http://192.168.11.175/osjs.js:12417:17
internalRequest/<@http://192.168.11.175/osjs.js:12341:15
_apiCall/<@http://192.168.11.175/osjs.js:2255:9
onsuccess@http://192.168.11.175/osjs.js:10998:19
onReadyStateChange@http://192.168.11.175/osjs.js:1674:16

@AvinashMarkad
Copy link

By methodically checking for syntax issues, verifying data structures, and using debugging tools, you can resolve most JavaScript errors, including those that might be reported as "Error #43". If you can provide more details about the specific error or context, further guidance can be offered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants