I am experiencing extremely slow Vetur initialisation after every time VS code is restarted.
It helps a bit if I don't npm run serve straight away into my development environment, because otherwise Vetur initialisation would just hang forever. But it is still very slow even if I let it run for a bit before starting to do my work.
Google doesn't seem to be able to find an answer for this, so I would appreciate if anyone got a hint as to the problem?
Related
Below you can see the output I get when I try to run npx react-native run-android. It suggests some options to try in order to further pinpoint the problem, however they don't work with the aforementioned command so I assume that they are related to a gradle (just an educated guess).
I know ZERO about gradle; I have just seen the name here and there and in the output shown below. So please keep that in mind when you answer. If I need to learn how to run some gradle command(s) directly, please be as verbose as possible in your answer.
The project was working fine just a bit ago, but I wanted the ability to force portrait mode for certain screens but without configuring my entire app to always have to stick to portrait mode. So I found what looked to be a solution in the react-native-orientation-locker module. I installed it with yarn and then proceeded to update files as directed: https://www.npmjs.com/package/react-native-orientation-locker.
After updating the appropriate files, I got an error that suggested axios was the problem. I uninstalled and reinstalled axios. After that didn't work, I proceeded to undo all the file changes I had just made. Then I uninstalled the react-native-orientation-locker module.
To my knowledge, I have undone everything I did between the time the project worked and stopped working.
Sadly, I had not put this into source control yet (a mistake I won't make again), so I can't revert.
Where to go from here?
Problems like this are hard to pin point. What you can do is open the android project in android studio and see the logs as the project is being assembled. I assume you do not have much knowledge about android either so you might need some senior resource to help you.
What I usually do in this case is open android studio and if I am lucky enough, it tells me which file has an issue and I go to the file and do what android studio suggests me. Some times it fixes the problem and sometimes it doesn't.
Another thing I would like to mention is that the documentation of the package you are using is important to follow. I assume you did that already but I would suggest to review it narrowly and closely.
Another guess I can tell you is try to go to your-project/android/build.gradle and over there, you'll see something like this in the start. The package you are using mentions something about target SDK 27. I think you should check that out too. May be it helps
Lastly I would say always use source control while working with react native. It can easily blow up at any time so you should always have a safety net to fallback to :)
We have currently about 200 test features. We start to face something strange, most of the times tests are just stuck and would not proceed when we run mvn test command as the following:
mvn clean test -Dcucumber.options="--tags $tags" -Dtest=TestRunner -Dkarate.env=$env
Some tests would run as it was perfectly fine. But at some point the rest will just stuck as it it hangs.
We run the tests in parallel using 10 threads.
It stucks like this
Anybody experienced similar things? Any ideas what could possibly went wrong?
Thanks
This should be fixed in 0.9.5.RC3 - it is stable to use for API testing, so I recommend you upgrade.
If anyone faces this problem for any other version of Karate, please understand that the best (and possibly only) way to troubleshoot or solve this - is to follow this process: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue
I actually have the same problem as you but I can't comment because of reputation, my project works with Gradle and I'm using IntelliJ IDEA and JDK1.8(at another moment before all this I tried Jetbrains SDK11 but had the same problem, I downgraded to java 8 and everything worked again) on this ocassion I did as peter said and upgraded to 0.9.5.RC4 but still when I execute some of my features they never end, for example, I'm currently working on a very simple feature that calls another feature for login, it works for many other features but for this one it appears to get to the end of its execution and never go back to the caller feature, as I was running out of options I made a new simple project copied the resources folder I store my features in and my run parallel class and tried again but it behaves in the same way, the execution never ends.
I'll upload an image with my screen while it executes as you can see it's been executing for 15 minutes
projectView
So, I've had an Azure Dev spaces project running for a while. Up until recently, it was working fine. Now, It is stuck at "Syncronizing files".
Is there any way to debug what's going on?
Cancelling the azds up command and restarting the terminal solves the problem for me whenever I am stuck anywhere. When even that doesn't work, it is a good idea to run az login once in a while.
I'm using GraphDB Free 8.4.1 in research project and sometimes it gets stucked without any obvious reason. Process is running, but it is not possible to connect to repository, not even from workbench. It just stops responding.
I have to kill the GraphDB and then run it again.
I'm aware, that free edition allows only 2 queries in parallel, but i would not expect it would get stucked. I tried to reproduce this by making 30 parallel SPARQL queries, but everything worked ok.
There is no exception, nothing in error log, nothing in main log.
Please, where could be the problem?
Thank you very much in advance.
You can diagnose the problem by running jstack on the GraphDB process. This will give us details about the process activity.
I decided to build my own Vue SSR template that I could use for my projects. It's partially based on this example. Everything was fine and worked as expected. And it still does on the dev-server) But when I'd built the app for production I suddenly discovered that it was totally dead. I got no errors, no warnings, no other signs that could point out the direction where I should search for the answers whatsoever... And it's just blowing my mind!
The app works perfectly on dev-server but in production, it appears to be totally dead as client-side hydration somehow fails.
I'm not sure what it is really... Or maybe I'm just stupid enough to miss something very simple here. I just don't know. I spent so much time trying to solve this... But found nothing, and I feel pretty helpless. So any help would be appreciated!
Found it! It was so simple that it’s actually very funny.
That’s what will happen if you accidentally define a wrong entry point for your client bundle in webpack config.
So be aware!
Hopefully, it would save some time for someone)