I just installed the version 1.21 of pestphp/pest for a small php library.
Installations works until I try running ./vendor/bin/pest
I keep getting this error: Exclusive locks are not supported for this stream
Research on this error has proven unsuccessful as I could not find a similar case.
Please let me know if you've experienced this before and how you fixed it.
Thanks!
I have figured out the issue.
I was running the application from the htdocs of the vm version of xampp running on my laptop.
Taking the project out of here into another directory solved this issue.
Hope this saves someone else some time.
Related
I've been using gcloud command for deploying my app in app engine for weeks.
But one day (today) It starts to fail.
gcloud command gives me
Didn't expected \Google\Cloud at this moment.
in my console.
I reinstalled python and google sdk, but I can't be able to execute it again.
I recheck my path environment variables.
I'm using windows.
I'm lost with this issue.
It would appreciate any kind of clue.
This is an already known issue which is occurring often. This happens when it updates to Cloud SDK version 274.0.0 in Windows. You may find more information here.
There is a workaround provided in this Stackoverflow post
I built an Electron app on 64-bit windows machine and it runs well on other machines.
But today, I ran it on my 32-bit atom processor windows machine and I got the following error message.
I tried npm update but it doesn't work too.
the error message is,
How can I fix it? : (
Thank you for reading my question.
You don't have access rights. Try running as an administrator or change permissions.
Also you may try checking, if antivirus has blocked this process.
I am trying to get Sonarr running on my xubuntu server as it is the last thing i need to move to decommission my windows server. I've gotten emby running with mono without issue, but I'm getting this error when trying to run sonarr:
Corlib not in sync with this runtime: expected corlib version 111, found 138.
Loaded from: /usr/lib/mono/4.5/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.
I've tried updating my packages with the mono main channels, then beta channels, then the alpha channels and continue to receive this exact problem. go-mono.com/daily doesn't resolve in my browser.
Any answer's I've found on forums for this issue seem to just say to get the thing straight from the mono repos to cure the issue, which I did from the beginning.
If this helps at all, before this issue I had the mscorlib not found error, because there was no /usr/local/lib/mono or wherever it is suppose to be and I had to symlink /usr/local/mono i think (not sure on those paths exactly, my brain is about fried at this point.) This is on Xubuntu 14.04 LTS
Can anyone point me in the right direction?
Issue:
XAMPP Server crash in regular interval with the MSVCR110.dll error.
Our analysis:
We upgrade the RAM size from 8 GB to 64GB
Stops few background process to reduce the load in CPU.
Some solution suggested to install below software, we did. But still no result.
http://www.microsoft.com/en-us/download/details.aspx?id=30679#
Lastly we reinstall fresh XAMPP tool to the server. No luck yet.
We think that some expert help requires to overcome this issue.
Please suggest.
I have had just the same issue!
The only solution that has solved my case is to download and put the dll in the place from here http://fix4dll.com/Msvcr110_dll
Hope this helps!
I'm trying to install ppl011 using brew and it fails.
The story began when I did rvm requirements. It failed during the gcc46 step. When I tried to install gcc46 itself, it failed while installing ppl011. Eventually, I was able to generate these: https://gist.github.com/ege02/9490126
I have been googling this for the past 24 hours. I'm also new to OSX/Linux so I pretty much have no idea what I'm doing. I'd appreciate some guidance!
I'll add this in case it helps someone. It turned out that the issue was caused by an incompatibility with the (as of this writing) recently released Command Line Tools 5.1. Downgrading to CLT 5.0.1 allowed me to work around the issue. More details here.