Symfony2 run bin/vendors git error - symfony

I downloaded the latest symfony2 (2.0.10) and tried to run bin/vendors install but it prints the following:
Installing/Updating symfony
Cloning into /Users/i/sf2_proj/vendor/symfony...
error: Failed connect to github.com:80; Operation timed out while accessing http://github.com/symfony/symfony.git/info/refs
fatal: HTTP request failed

try using git:// instead of http:// in your deps file

Changing http:// to https:// also works

Related

Redmine is not working properly. How I can solve this issue?

Please help me with Redmine. I had a working Redmine at FreeBSD 11.2-RELEASE-p4 with Nginx and Passenger. But after some latest updates, my Redmine is not working properly.
I have an error in passenger.log:
[ E 2018-10-09 16:10:01.0750 42785/Tb
age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for
application /usr/local/www/redmine: The application encountered the
following error: undefined method `active_record' for
(NoMethodError) Error ID: 8412e2de Error details saved to:
/tmp/passenger-error-wIhbfb.html
What can I do with these errors?
You should try to install the gems required, just go to where the redmine code is and type
bundle install
Restart nginx and see if keep saying the same error.

How to use VersionPress to clone across servers?

I would like to clone a WordPress site that is already in VersionPress to a new server.
The instructions are generally only listed for cloning on the current server. I have one server dedicated to Dev and another for Production
I tried the following command line:
wp vp clone
--name=sitename
--ssh=username#site.school.edu
--path=/var/www/html/folder
--url=https://site.school.edu/destination
--dbname=mydb
--dbuser=myuser
--dbpass=mypass
--dbhost=xxx.xxx.xxx.xxx
--dbprefix=wp-
--force
However after I login to the remote ssh server, I get this error:
Fatal error: Call to undefined function apply_filters() in /var/www/html/atwiki/wp-includes/load.php on line 317
Error: Cannot connect over SSH using provided configuration.
Any ideas?
Here's a blog post on how to achieve that today. We will have a more polished way in the future.

Failure installing sbt: "Server access Error: java.security.cert.CertificateException:"

When I try to install error messages, it fails to download. I get error messages like this:
[error] Server access Error: java.security.cert.CertificateException: No subject alternative DNS name matching repo.scala-sbt.org found. url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-pgp/scala_2.10/sbt_0.13/0.8.3/ivys/ivy.xml
I can confirm, when accessing via my browser, that the certificate installed for the domain repo.scala-sbt.org is actually the certificate for repo.typesafe.com, and this seems to be the source of the error. It doesn't appear to be a DNS issue as http://repo.scala-sbt.org/ (insecure) works.
Please see https://github.com/sbt/sbt/issues/2125 for the workarounds. Specifically "http" should not be used.
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
Edit: This issue is now resolved. No workarounds should be required.
As a temporary workaround, add the file ~/.sbt/0.13/plugins/temp.sbt with the following contents:
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
You'll still see the error, but sbt will be able to find the dependency for which it is searching when accessing https://dl.bintray.com/sbt/sbt-plugin-releases directly (the place to which repo.scala-sbt.org presently redirects).
Upgrading nss package on CentOS worked for me.
sudo yum upgrade nss

Assertion failure when using puphpet

I am trying to use the hhvm, but then i try and run my test script i get an 502 Bad Gateway (nginx) error message
so i tried to run it in terminal and i get the following error message:
$ hhvm /var/www/public/test.php
Assertion failure: /tmp/tmp.3Ty7dCXWJ2/hphp/runtime/base/rds.cpp:426: void HPHP::rds::initPersistentCache(): assertion `s_tc_fd != -1' failed.
Aborted
but when i run it using sudo it works!
$ sudo hhvm /var/www/public/test.php
hello world
What did i do wrong? i have tried updating the owner of a file and changed the permissions of hhvm, but this didn't work.
You shouldn't be getting assertion failures in a release build of HHVM. Can you please file an issue on GitHub so we can track the bug? Make sure to include your OS as well as the output of hhvm --version.

swagger-document-override/md-override-loader - FAILED

I am able to generate code using Autorest with my api when I host it on a server 2012R2 running IIS
However when I try to run it with the localhost url I get a could not read message.
I can read swagger.json in the browser
I am using the command
autorest --input-file=https://localhost:44348/api-docs/v1/swagger.json
--output-folder=generated --csharp --namespace=DD.MyApp.Connector
The output is
AutoRest code generation utility [version: 2.0.4283; node: v10.11.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core 'C:\Users\kirst\.autorest\#microsoft.azure_autorest-core#2.0.4289\node_modules\#microsoft.azure\autorest-core\dist' (2.0.4289)
Loading AutoRest extension '#microsoft.azure/autorest.csharp' (~2.3.79->2.3.82)
Loading AutoRest extension '#microsoft.azure/autorest.modeler' (2.3.55->2.3.55)
FATAL: swagger-document-override/md-override-loader - FAILED
FATAL: Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
FATAL: swagger-document/loader - FAILED
FATAL: Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
Process() cancelled due to exception : Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
Error: Could not read 'https://localhost:44348/api-docs/v1/swagger.json'.
After studying the issue on github I tried starting the api using dotnet run
but it did not help.
I tried running autorest in a dos command shell with admin priviledge
As per the github issue I can save the swagger.json to a file and generate the code by referencing the file.
That isn't a great solution.
Are you attempting to use https with localhost ? If you haven't put a certificate on there, you shouldn't be using https.
Try it with http://localhost...

Resources