I get this error every 5 ~ 10 minutes while running my app.
My app doesn't stop or anything, but I think something needs to be done.
What is wrong and what should be done to avoid this error?
Some part of your code is calling registerPlugins, which is no longer needed... We need find out which package calls that and update it.
Related
I am new to loadrunner. I know error handling part. But recently I came across a situation in which I use a parameter unique each iteration setting. This data is exuastive in nature i.e I cannot use them again.
Now in my script getting error where where it shouldn't be. Probably at the breaking point of the application. So I want to print that parameter whenever it fails anywhere in the script.
Any idea how to achieve this ?
Thanks in advnace.
So Flow only works correctly the first time I run it, and then I have to restart my computer before it'll work correctly again.
Specifically, the problem I'm seeing is that we are using the Flow language to add type annotations to our JS code. Our linter script is setup to run flow type checking among other things. However, when I fix an issue in my code and then rerun the linter script, it still comes back with the exact same errors... BUT when it shows the piece of code where the error is supposed to be, it actually shows my updated code that's fixed.
So as an example, I had a file I copied into the project, that I didn't think I really needed, but maybe I would. So I copied it in just in case. Well then it came up with a bunch of linter errors, so I decided to just delete the file since I didn't really need it. So then I run "yarn lint --fix" again, but it's still complaining about that file, EVEN THOUGH THE FILE DOESN"T EXIST! Now interestingly, where the linter output is supposed to show the code for those errors it's just blank.
Or another example, let's say I had a couple of functions in my code:
100: function foo() {}
...
150: function bar() {}
And foo has a lot of errors because it was some throw away code I don't need anymore and so I just delete it. So the new code looks like:
100: function bar() {}
Well I rerun the linter and get an error like:
Error ------------------------ function foo has incorrect
something...blah blah
src/.../file.js
100| function bar() {}
I also tested this out on a coworker's machine and they got the same behavior that I did. So it's not something specific to my machine, although it could be specific to our project?
Note: There doesn't appear to be a tag for Flow, but I couldn't post without including at least one tag, so I used flowlang even though that's actually a different language :-( I'm assuming that anyone looking for flow would also use that tag since it's the closest.
The first time you launch Flow it starts up a background process that is then used for subsequent type checking. Unfortunately this background process is extremely slow, and buggy to boot. In linux you can run:
killall flow
To stop the background process. Then if you rerun the flow type checker, it will actually see all your latest changes.
I am a new to Node JS. I have included a module via npm install '<module_name>. It was built correctly and there was no errors. Now, I wanted to debug it, so I placed a few console.log('some text') in code blocks of the module to see if the code by passes that line. Anyway, none of the log statements were displayed.
I am wondering if I have to compile or something the modules after adding the log staements. Am I missing something here.
Your console.log statements are not being run, this could be caused by many things.
Assuming you have added the console.log statements to the module code in the node_modules directory of your app..
does the module have src and dist directories and you have not edited the code that is actually being run? (this relates to needing to recompile, but editing the actual code that the module is running will be quicker and easier)
if this is in a server or long running script it will need to be restarted to load the changes
is this in a browser which might be caching the code (turn off browser cache)
is the code where you added the log statements actually being hit?
I would make sure I had a console.log statement in a part of the code guaranteed to be hit, just as a sanity check.
For anyone coming here in the future, try console.error instead of console.log. For some decided reason or another, log was being overriding by the library I was monkey fixing. Took me way too long to find the culprit.
When trying to debug react native app on device, it takes really long time when "running 1 of 1 custom shell scripts". It will not fail, but just take long time. Is there anybody know what process is this? And how can we shorten this time? Thank you!
I didn't solve this one, but I did find out some information. For me, it seems that this is happening because the script hangs for ~15-30 seconds after it has completed the bundle (and asset copy). This is one of those cases where the main thread in a node script has completed, and node is just waiting for a promise to resolve before it quits ... and it waits too long. I was able to mitigate the problem by adding a call to process.exit(0) in the right place within react/native/local-cli, to wit:
https://github.com/facebook/react-native/blob/master/local-cli/cliEntry.js:116 (popping a .then(()=>process.exit(0) onto the end of that line.
Not an elegant solution but maybe some others can pick it up from there.
I had the same problem (Mac/iOS) after updating react-native from 0.47.2 to 0.48.2.
Then I came across a solution from this link (I think this is what worked for me).
Anyway what I did was reinstall watchman as shown below:
brew uninstall watchman
brew install watchman
Hope this helped.
I have problem with me51n. I have an include in EXIT_SAPLMEREQ_010 that has a bunch of codes which we use it to receive errors. The problem of mine is;
-When i run me51n with required datas(mat. number, quantity, etc.) I get some errors which also includes the error that I'm expecting on the first time, however when i terminate me51n and run it again with the same exact data, i dont get my error. I have debugged it and put a break point on my include in EXIT_SAPLMEREQ_010 and it never gets to my breakpoint on the second run. (It gets to the breakpoint on the first run but not the second one).
I dont know how but with the same material it works fine later again at the first time but still on the second time i cant get the error again.
Can anyone please help me on this?
Basically problem was the developement system from the beginning (sigh -_-). While having other errors rather than my errors, i assume my error gets stuck sometimes and never pop up because of the standard SAP procedure. So in test system (QA) me51n works perfectly when I'm just trying to have only my error.
Thanks for anyone who actually tried to help and I hope this might be useful sometime for someone in future.
Talha