Roblox Studio - Random Errors that i can't understand i get - lua

As you can see on the picture below I'm getting some errors in my code:
I have no clue why I'm getting these errors or what they mean and while they don't seem to do anything bad I would rather be able to get rid of them. So I'm asking if someone can tell me what they mean and how I would go around stopping them.
Here are the errors that are shown in the picture:
02:28:40.947 - Roact is not a valid member of CorePackages
02:28:40.949 - Requested module experienced an error while loading
02:28:40.950 - Requested module experienced an error while loading
02:28:40.953 - LocalizationPlugin is not a valid member of CorePackages
02:28:40.981 - LocalizationPlugin is not a valid member of CorePackages

Those errors are from scripts that are part of Roblox itself - you have no control over them and it's normal for them to have errors sometimes. Just ignore them.

The reason why you're getting these errors is because of the Roblox application you're using is using the same Lua engine Roblox uses to code their back-end. Basically, these errors are squawked out by the engine because of errors in Roblox's code. Now you can't fix this, but it doesn't really matter. To be honest, most of them just look like warnings, nothing to worry about. If you use Chrome Dev Tools on most websites you'll see console errors or warnings. They're nothing to worry about if they don't affect the functionality.
Edit: Other people might not get these errors as they may have a different version of the Roblox Lua Engine or their hardware/software may communicate better compared to yours.

Related

DirectX12: dxgi dll catastrophic failure when creating IDXGIFactory

I'm attempting to initialize an IDXGIFactory4 using the CreateFactory2 function however this throws out an error:
onecore\windows\directx\database\helperlibrary\lib\perappusersettingsqueryimpl.cpp(121)\dxgi.dll!00007FFBA0D6D7F8: (caller: 00007FFBA0D4D167) ReturnHr(1) tid(64d8) 8000FFFF Catastrophic failure
onecore\windows\directx\database\helperlibrary\lib\perappusersettingsqueryimpl.cpp(98)\dxgi.dll!00007FFBA0D6D4D0: (caller: 00007FFBA0D3E221) ReturnHr(2) tid(64d8) 8000FFFF Catastrophic failure
onecore\windows\directx\database\helperlibrary\lib\directxdatabasehelper.cpp(999)\dxgi.dll!00007FFBA0D6D4FC: (caller: 00007FFBA0D3E221) ReturnHr(3) tid(64d8) 8000FFFF Catastrophic failure
I have not found any similar error messages online.
I have attempted running the function on its own and initializing as a different IDXGIFactory (e.g. IDXGIFactory2) instead but both still lead to the same issue.
ComPtr<IDXGIFactory> dxgiFactory;
UINT factoryFlags = DXGI_CREATE_FACTORY_DEBUG;
ThrowIfFailed(CreateDXGIFactory2(factoryFlags, IID_PPV_ARGS(&dxgiFactory)));
This is not the error as you describe it.
There is no real failure, there is no catastrophy, there is no even exception and there is no error code returned to you from the API call. What you are seeing is a glitch in internal API implementation that emits debug output with these strange lines. Apparently it is a small problem in Microsoft's API implementation and the weird format of the message suggests it comes from use of wil in one the modules: they probably intended to remove this output from Release build of the software but somehow it worked out in a different way and unintended debug output passed through...
The message is likely to correspond to recoverable internal error condition which is then handled and your API call ends up being successful. Nothing to worry about, it's just up to Microsoft to make things cleaner.
These errors happen even with any Blank app straight from the templates (or sample apps from Microsoft Github repos) in Visual Studio 2019 (v16.9.1). It's only annoying, apps never crash nor hang. However, this never happend before.
I hope Microsoft better fix this soon (it's bad for nerves and mental health). You can do nothing about it.

When I turn on "hhvm" on Homestead, I don't get any syntax error or missing class error, just blank page

I am using homestead as my development environment, I turned on the hhvm option for the site
sites:
- map: homestead.app
to: /home/vagrant/Code/wheremyprojectis
hhvm: true
I found that when there is an exception, everything is fine, but If I forgot to use namespace, got syntax error in the blade templates, I got nothing, blank page. I go check the logs and still nothing, the debug option is true. It's quite frustrating until I turned off the hhvm option.
I know it is not a big deal, but I still want to know is there any way to fix this?
I experienced the same problem. I searched around and found that it seems to be intentional:
https://github.com/facebook/hhvm/issues/4818
https://github.com/facebook/hhvm/issues/2571
Now you can poke through the github issues mentioned above, as well as these stackoverflow questions:
Display fatal/notice errors in browser
hhvm-fastcgi + nginx how to make it display fatal errors in the browser
laravel 5 show blank page on server error (and no laravel log), running with hhvm and nginx
For the time being, it ultimately boils down to writing your own handler, which isn't too bad. You can also tail the errors at /var/log/hhvm/error.log. Any errors that you intentionally want going to the browser you could of course handle using Laravel's error handling and logging.
UPDATE:
I reported this issue(and a fix) to the Laravel github here:
https://github.com/laravel/framework/issues/8744

ZF2 - Error messages failing to display

I am using ZF2 with doctrine ORM and every so often error reporting fails and I get meaningless errors:
http://screencast.com/t/UgZMb89vZ
When it works correctly, errors look like:
http://screencast.com/t/RlOEZxuGUsfu
To bug test this I have run git bisect and have checked every change made between the time when proper errors are reported and when they fail.
Nothing obvious shows up.
My only solution to fixing this problem is to roll back to a version where error reporting is working and to re-add my changes.
Has anyone experienced a similar issue to this?

CGContext errors in iOS application

When I run my application it works well, but during transitions between its views I have a lot of CGContext errors in the console output, but the app still works well, no crashes or bugs I didn't see. Description: so I only run my app - all work well - but there appears error messages in the console:
And after any other view transition they appear again and again. So the question - how to fix this? And what may be the reason of this error messages? There a lot of views and code in my application so I don't even know what part is error-prone.But these messages appear after transitions between all views in my app. Thanks in advance.
Look for some method in your code where you call CGContextSaveGState, CGContextSetBlendMode, CGContextSetApha, etc. Chances are that you won´t find many places where you do that.
Well, if you find it, look for some statement (just before those listed in your console log) where a context is created, and try to understand why it fails. You may set a breakpoint on that line and inspect the parameters to the CGContextCreate call.
If you need more help, paste the code you have (hopefully) found.

Erlang error codes, need more details

I am trying to use the file:open(....) function in erlang but it doesn't seem to work. I keep getting an {error, eio} exception.
Ive looked into it in the erlang documentation and all i have found is that it is the posix error for input/output... go figure.
The file name im outputting in is in the formation of "C:/directory/file.txt"
Im not sure if this has something to do with it.
Is there anyway i can make erlang give me a more specific explanation to what is wrong?
Thanks,
Jack
Unfortunately I do not know of a way to find out more without peeking inside the Erlang/VM.
If you look in the windows erlang source code there are a bunch of different errors which could cause en eio error. You can find a list of them here. In order to figure out which specific one it is, I would attach with windbg and step through the code as instrumenting and recompiling it on windows is a pain.
You might also be able to use something like Process Monitor to find out which system calls are being made and what they return.

Resources