https://gist.github.com/arxheryyy/27b95cb8b7edc49d7208a66dba9ca382
Here's the link to the code on my 'Github' Please help me take a look
I kept getting this error being thrown back at me and I don't know why I've looked through the code multiple times but cant find anything.
So you are obviously getting the error thrown inside this switch there, between the lines 30 and 36, as you try to use bot.command instead of bot.commands ! bot.command is not set anywhere.
Related
I'm attempting to configure a header filter where I'm able to select multiple options to filter on. I'm using v5.2.2 and it keeps throwing an Uncaught TypeError.
Uncaught TypeError: this.initialValues.join is not a function List.js:73:50
I've tried a few different configuration options such as using the valuesLoopup set to 'active' or a hard coded set of values. I just wanted to double check on here to see if I'm doing something wrong before I submit it as a bug.
Here's a JSFiddle of my functioning setup. If I uncomment the multiselect configuration on line 45, the error get's thrown.
I found the problem thanks to someone pointing to another post on setting up header filters. Thanks! Looks like I forgot to specify the headerFilterFunc to be "in" which I'm guessing is required with the multiselect option.
Edit: Never mind. This didn't work.
I'm trying to open a workbook with exceljs and get the following error:
Error: 162:67: duplicate attribute: o:relid.
at SaxesParser.makeError (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:410:16)
at SaxesParser.fail (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:422:26)
at SaxesParser.processAttribsPlain (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:1944:22)
at SaxesParser.openSelfClosingTag (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:1976:14)
at SaxesParser.sOpenTagSlash (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:1432:18)
at SaxesParser.write (C:\Users\tiedemann\Development\mbes32-events\node_modules\saxes\saxes.js:481:36)
at module.exports (C:\Users\tiedemann\Development\mbes32-events\node_modules\exceljs\lib\utils\parse-sax.js:21:17)
at async VmlNotesXform.parse (C:\Users\tiedemann\Development\mbes32-events\node_modules\exceljs\lib\xlsx\xform\base-xform.js:60:22)
I really tried hard to find any informations on that error. But can't make sense out of the informations google give me. Could anyone of you give me a hint what is wrong here?
I guess it has something todo with the xml. But I can't figure out what exactly todo or change in my file.
Please help!
Thanks.
I found the error. In the file was a circular reference in one of the cells. After removing the formular from that cell and saving the workbbok again. The error disappered. Wished the error message were more helpful in advance.
I've recently been trying to use the Demo Parser for reading CSGO *.dem files. It shouldn't be too difficult but for some reason it doesn't like it when I try to read the file. I keep getting the same error: "cannot remove non-existent entity".
Anyone else run into this issue?
I'm using the NodeJS code here: https://github.com/Brammz/csgo-demofile-parser and a sample of a *.dem file can be accessed here: https://www.dropbox.com/s/vk3tcy03tz5w254/test.dem?dl=0
Anyone know this error? https://imgur.com/a/8FhjxU1
"Unhandled Rejection (SyntaxError): Unexpected token P in JSON at position 0...
I don't know how an error message can get any more vague. I also followed a guide which apparently has worked for many people but for whatever reason I run into this error...
This is the guide I followed verbatim. https://youtu.be/8bNlffXEcC0
And I also followed other guides that are the same thing
But I keep running into this weird error message when it's time to display.
I'm guessing I have a weird version of node or something?
I'm working on a Windows Store app and I'm getting a WinRT error that doesn't really give me any information so I would like to know how to understand these sorts of errors.
Basically I get the error on the following line which is called inside OnPointerPressed:
m_gestureRecognizer->ProcessDownEvent(args->GetCurrentPoint(nullptr));
The error is:
First-chance exception at 0x76F54B32 (KernelBase.dll) in DXAML2.exe: 0x40080201: WinRT originate error (parameters: 0x80070057, 0x00000044, 0x03CEE72C).
This error didn't used to appear, the only thing I've changed is that this line is now wrapped in an if clause which tests if the current pointer's PointerId is the same as one I've stored just using == such as:
if(args->GetCurrentPoint(nullptr)->PointerId == m_UIPointerID)
I have no idea why this has started happening.
So my question is in two parts:
More generally, how do I understand what an error such as the above means?
And does anyone know this error has suddenly started happening now that I check the pointerId?
Thanks for your time.
P.S. I guess another thing that has changed is that there will already be 2 pointers on the screen (the one that gets pushed into this GestureRecognizer) as well as another one, hence the PointerId check.
"How to Decipher such an error"...
For any WinRT originate error, you can take the third address in the parameters list (in your example, 0x03CEE72C), and find a description of your error in the memory window.
While debugging, break when your error is thrown and open the memory window via Debug -> Windows -> Memory -> Memory 1
Copy and paste the address to get your "easy-to-find" error message.
As Raman said - it's good to look up the hex values shown. The first one is the memory location which won't tell you much without the symbols/source, which in this case is reported directly by Windows. Perhaps the public symbols can shed some more light on where the error came from, but the error code lookups are more helpful.
If you Bing for 0x80070057 you will find an MSDN article on Common HRESULT Values which lists
E_INVALIDARG : One or more arguments are not valid : 0x80070057
It doesn't give you all the details of course, so you're off to theorize. Perhaps you can only call args->GetCurrentPoint(nullptr) once and you should store/reuse the value? Maybe gesture recognizer is not configured correctly? Maybe the app window is not visible at the time the exception is thrown or the thread is wrong. Maybe some expected calls to gesture recognizer were missed due to filtering those out with these "if" statements.