Hi Marvin
this issue is a bug in our client library, there's nothing the user can
do about it. The good news though is that the fix is on it's way, wont
take long until it'll be available in the nightly update sites. For more
details look here: *https://issues.jboss.org/browse/JBIDE-26879
*
The other issue regarding the oc binary that you brought up is not
related. Still great that you brought this up, we didnt notice this so
far. Could I ask you to file a jira for this at
http://issues.jboss.org/browse/JBIDE (component "openshift")? Would be
most awesome. Thanks!
Cheers
Andre
**
Am 13.10.19 um 18:31 schrieb Daniel Veillard:
Hi,
On Sun, Oct 13, 2019 at 10:26:05AM -0400, Just Marvin wrote:
Hi,
One more detail that perhaps need to be addressed:
[image: image.png]
That oc binary came from the CRC install, so not sure why CRS is
unhappy.
Regards,
Marvin
Support of CRC will come in next release of CodeReady Studio likely
around the end of the month, we want to make sure we have a GA'ed version
of CRC and not just the candidate release to have testing done, and then
have the release with CRC support.
Again asking for a bit of patience :-)
Daniel
On Sun, Oct 13, 2019 at 10:17 AM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:
Hi,
I'm using CodeReady Studio, and trying to point to my CRC install
(which I assume should work - please let me know if that is a misguided
notion). Here is what I get with the developer/developer oc login:
[image: image.png]
How do I fix this problem?
Regards,
Marvin
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
