I am using Composer and I can successfully deploy chaincode to my infra. The problem is that after any refresh or restart of composer-playground, composer is not reconnecting to the correct version of my chain code so I loose all changes ....
I think I have an issue with the versionning.
Is there any wait to change the "From" version in the composer UI ?
I deployed successfully a first bna on my infra
So the problem is apparently coming from Firefox, same manipulation on chrome works fine and connect to last version of the chaincode. A colleague of mine tried on the same Firefox version as mine and it works fine ! So it's not only an issue with the Firefox version but with my own Firefox. Cache cleaning did not fix it!
Have you tried deploying the playground to your local, not sure if you are accessing the playground via the web or not.
Related
i have ddev running locally on my windows machine.
I worked all the time on my TYPO3 installation, it was working fine and the only thing i did yesterday was to patch it from 9.5.18 to 9.5.19. Even after that, it worked fine.
As i wanted to start today, i get the message
The requested resource "" was not found
, when I want to get to the backend (/typo3). The installtool is working but has no styling at all.
The Front End is working fine.
here is an image of the error
Any idea where i can could take a look at? I already restarted my machine, ddev, docker and went back to an older composer.lock, composer dumpautoload and cleared typo3temp but nothing worked.
I had this on a previous update a few weeks ago on 1 installation while I was updating a few dozen. What fixed it was deleting typo3conf/PackageStates.php. I did have to turn on all the extensions again after that of course, but it still worked after I'd done that. As this was only in 1 installation and the others were fine I didn't investigate it further so I don't know what caused it or if there's a better solution. Not a real answer, but perhaps it will help you.
I built a system with laravel-admin and guzzle. I send api requests to Shopify with Guzzle and everything works fine on my local environment. However, when I try to create a product in production , it gives me this error.
IDN conversion failed
I looked into it on Google, and it seems Guzzle is giving me this error because I get the error only when I try to create the kinds of products that I sync with Shopify with guzzle.
There is not much information about the error on Google, and I am lost as to why it is happening. Has anyone experienced the same issue?
Could you please add PHP and Guzzle versions to the question? I'm one of the authors of this feature, and (unfortunately) there were some issues related in specific cases. But to say something I need more details.
Generally, try to upgrade to the latest version. Things probably should be fine with the latest Guzzle 6.5.2.
I've also suddenly started running into this issue. I have PHP version 7.2.30 running on the server and cURL version 7.19.7.
It worked fine yesterday, and wasn't working properly this morning. Nothing has changed, other than I upgraded Laravel and all dependencies. However, I think the particular code in the Guzzle Utils.php file where this error is being triggered has been around for quite a while. I tried downgrading Laravel to versions from much earlier this year, and Guzzle stayed the same.
We recently updated our web server, but that didn't make a difference to the PHP version nor should it have affected configuration.
This error I'm getting right now is baffling and I have no idea how to troubleshoot it.
EDIT: I found a simple work around for this problem through server configuration. After digging through the codebase in Laravel I noticed that Symfony provides polyfils if the intl extension is not installed. As such, I just disabled the intl extension on the server, which caused it to use the polyfils, which resolved the problem for me.
I checked first to see what version of ICU the intl was using, and it was an older version and hence the reason I got the errors.
So if you are running Laravel or anything else Symfony based and are having this problem, this could be a simple solution if you can't upgrade to a newer version of PHP for whatever reason. We are running a Plesk-based server, so we are dependent on them providing PHP and all the various extensions and we can't control their upgrade timing.
If you don't have that problem, then your other option would be to upgrade your PHP yourself and ensure the intl extension is up to date and compiled against a more current version of ICU.
I have been running a pretty old version of Homestead for years. At various times, I have tried updating a few times. I always got an error about being unable to resolve a package. Since the version of Homestead that I was running was technically working, I probably left my old version of Homestead running a bit longer than I should have.
I finally buckled down and worked through updating it. Everything appears to be back like it was except for one frustrating difference. Many of the projects in my Homestead interact with one another, oAuth, API integrations, etc., and while I can visit any project in my browser like before, none of the projects can resolve one another.
I always receive a curl error:
cURL error 6: Could not resolve host:
So, for example, one project that relies on an API call to another project for a dropdown list in a form, the API call never resolves and I can't populate the form.
Has anyone experienced anything similar? Any thoughts on what may be causing this? I have Googled around without much luck.
The problem initially started when I updated my laravel/homestead box. So, I thought that maybe the update corrupted the box somehow. I have run vagrant destroy and then vagrant add laravel/homestead to reinstall the newest version and the issue is still there. I noticed that the newest version that installs is 8.0.0-alpha2, so I tried specifying vagrant add --box-version 7.3.1 (the latest stable that doesn't have alpha or beta in the name) and again I am getting the same issue.
GuzzleHttp \ Exception \ ConnectException
cURL error 6: Could not resolve host: outside-project.local (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser.
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser. I would expect that projects can resolve each other just like they did before I tried updating Homestead.
If any one else is experiencing this, here is how I got it working:
vagrant ssh and add any projects that need to communicate with one another to the /etc/hosts file.
I just discovered Laravel Dusk, and I was excited to use it in my project. However, it can't seem to get it to work. I followed the Laravel Documentation to install Dusk. When I run php artisan dusk in the terminal, I get
[Symfony\Component\Process\Exception\RuntimeException]
TTY mode is not supported on Windows platform.
I found this (https://github.com/laravel/dusk/pull/13/files) which is supposed to fix it I think, but I still get the error.
Also, I attempted to run the Dusk tests through PhpStorm following the accepted answer here (https://laracasts.com/discuss/channels/testing/dusk-via-phpstorm), but I get a Class config does not exist error. Many people said that this caused by a space in the .env file, but that is not my issue.
Can anyone help me figure out what is going on with Laravel Dusk in my setup? My Laravel project is 5.4 and I'm using Laravel Dusk 1.0 and PhpStorm is 2017.2.1
You can install chromedriver into windows on your own, and try not to use the version that is shipped with laravel dusk. Remember that, your chromedriver version needs to match your currently installed Chrome version, and when Chrome gets updated, then you need to update/reinstall chromedriver manually again. Hopefully it does not happen too often, and when there are updates, you benefit from using latest versions, which I find really nice :)
Download it here.
After installing chromedriver, you need to start it from command line (just issue command in your download/install directory chromedriver) or add it as service (which I do not prefer, cause I want to have control of which service is running on 9515 port).
Finally you need to comment out // static::startChromeDriver(); in your DuskTestCase.php, which tries to start laravel dusk included chromedriver, cause in this case, you are already running one.
Run dusk tests again and all should be working fine.
I don't know what your system setup is, but I am using this workaround on windows 10 with Laravel 5.5, dusk 2.0, which still causes problems, when chrome gets updated.
BTW. Just to mention. This also works with CI workflows using docker. You can read more about it here
I have installed Laravel on shared hosting using softoculous. Now I am facing an issue. I have followed SO Answer which did not work for me. How can I manually install laravelcollective package. I also don't have SSH enabled. Therefore, I can't use composer. Everything except package is working fine. I also ran artisan commands using
\Artisan::call()
but sadly nothing has worked for me.
I see only one solution you should upload your vendor folder from your local computer to your server. Although its not a recommended way its probably your only option