Error with Intellij Heroku Integration - heroku

I'm currently using the Intellij Heroku Integration plugin, and i'm trying to set up the basic connection to heroku. But when i try to set the SSH key, which is just a basic SSH key generated by the command
ssh-keygen -t rsa -C "your_email#example.com"
i get this error:
am i supposed to do something different to generate the key?
*extra details on what i've done that might be screwing this up:
- i tried to install the plugin on community edition (now trying with the full edition)
- i deleted a few outdated versions of heroku on my pc and reinstalled just the CLI
any clues how to fix this? or is heroku integration just broken? i also get:
when i try to click for help, so maybe the plugin files are corrupted? any help would be appreciated, thanks!

as #CrazyCoder mentioned this is a bug, where the API used by IntelliJ was dropped in April 2017 by Heroku.
This should be fixed with IntelliJ 2017.3 onwards.
Edit
Version 173.3727.22 is still shipped with the Heroku integration 1.0, so the problem remains.
You will have to manually install the new version of the plugin, found here:
https://plugins.jetbrains.com/plugin/7605-heroku-integration

Related

Unable to download Red Hat CodeReady Studio in eclipse

I am trying to install Red Hat CodeReady Studio from eclipse marketplace but I keep getting the below error:
Unable to read repository at <https://devstudio.redhat.com/12/stable/composite/12.9.0/content.xml>
Error Stack
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.ibm.jsse2.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:177)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:397)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Any Help would be much appreciated
I have tried latest Eclipse(2019-12) and installed CRS 12.13.0.GA without issues.
Which Eclipse version have you tried?
It looks like like you are trying to install quite old version of CRS.
Josef
PS: You can use JIRA for reporting issues with CRS: https://issues.redhat.com/projects/JBDS/ or witj JBoss Tools https://issues.redhat.com/projects/JBIDE/

Installing latest version of Open Shift locally

I have successfully installed Open Shift locally on my Ubuntu laptop using this guide:
https://blog.openshift.com/using-openshift-3-on-your-local-environment/
using this vagrant file:
https://www.openshift.org/vm/Vagrantfile
But its a fairly old version, 1.2.0:
https://app.vagrantup.com/thesteve0/boxes/openshift-origin
Any suggestion on how to update to e.g. latest or 3.6/3.7 using the above guide?
That is an old guide for deploying OpenShift locally. They have switched to using Minishift for local development. I recommend giving that a try for a more up to date environment!
Here docs.openshift.com/container-platform/3.5/install_config/upgrading/automated_upgrades.html#install-config-upgrading-automated-upgrades it's an article about how you can automatically upgrade the openshift. I hope this will help You!

Version error when installing docker toolbox on OSX

I'm new to docker and have been following the guide, trying to install the toolbox version v1.10.0-rc1. All seems to have gone well until I try the hello-world example and then I get:
Error response from daemon: client is newer than server (client API
version: 1.22, server API version: 1.21)
I see there is much online about similar errors, however all attempts so far have failed, and being unfamiliar with docker, the suggested solutions are somewhat cryptic.
Has any had a similar issue and found a solution?
Many thanks
Docker tool box is being used in old mac and or windows system.
today there are differnt approaches to install docker on your mac.
In case your mac isn't that old try install it from here

Getting Google App to work

I've followed all the steps here https://console.developers.google.com/start/appengine?_ga=1.82598931.449716086.1415074596 successfully up to step 5.3. When I try to start the server:
dev_appserver.py appengine-try-python-flask
I get the following output:
-bash: dev_appserver.py: command not found
I'm on a Mac running OS X 10.10. Any ideas what I'm doing wrong?
I'm running Python 2.7.6.
It seems like you didn't correctly add the dev_appserver (and other GAE tools) to the bash.
Did you restart your shell(s) to pick up the new environment changes?
If you did and the problem still persists, you can try downloading manually the GAE SDK.
After that, open the GoogleAppEngineLauncher, and just click OK on 'Make command symlinks'. This will solve your issue.
It's all easily explained in the official documentation:
Download and Install the Google App Engine SDK

svn commands hang on Mac

Need a help again. Whenever I try to run any svn command from command line on MacOS X 10.7, it hangs.
I have no clue why that's happening. svn commands work fine from within IntelliJ.
Can anyone help me find out what the problem is? Any help will be very much appreciated.
Thanks
Perhaps you need to use a proxy server to talk to the SVN repository, and you've got the proxy server configured in IntelliJ but not at the command line. Here's a random blog post showing how to set up proxies for SVN command-line tools.
I was able to solve the problem by moving to newer version:
...$ svn --version
svn, version 1.6.17 (r1128011)
compiled Aug 26 2011, 09:41:54

Resources