[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22810:
-------------------------------
Reporter: Rob Stryker (was: Viacheslav Kabanovich)
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Rob Stryker
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.5.1.AM1
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBTIS-1151) Section 508 - VPAT Compatibility
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1151?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1151:
-----------------------------------
** Track email thread:
Rick Wagner
4:33 PM (18 hours ago)
to devtools-progr., Wagner
Hello DevTools-Program,
CEE has fielded a handful of cases from US government customers that have an interest in product accessibility. The requests usually come in the form of a request for a 'VPAT', which is a document that explains our level of compliance with regulation called 'section 508' [1].
Red Hat offers a VPAT for EAP, but little else. On behalf of our government customers, we'd like to ask if it's possible to provide something for IDE evaluators who ask about a VPAT for DevStudio. (We have had cases.)
There's an RFE open for JBTSIS, it's at [2]. Perhaps this is better provided as an RFE for DevStudio, that's easily arranged if it's deemed proper.
Please consider, discuss further as needed. It seems possible that providing a VPAT might lend some advantages in dealing with government customers (and will probably lead to a better product, anyway.)
Thanks,
Rick
[1] https://www.section508.gov/content/sell/vpat
[2] https://issues.jboss.org/browse/JBTIS-1151
Ronald Pacheco <rpacheco(a)redhat.com>
4:45 PM (18 hours ago)
to Rick, devtools-progr., Wagner
On Tue, Aug 1, 2017 at 4:33 PM, Rick Wagner <rwagner(a)redhat.com> wrote:
Hello DevTools-Program,
CEE has fielded a handful of cases from US government customers that have an interest in product accessibility. The requests usually come in the form of a request for a 'VPAT', which is a document that explains our level of compliance with regulation called 'section 508' [1].
Red Hat offers a VPAT for EAP, but little else.
Not really. I did the RHEL 7 one a few months ago, Red hat Storage did theirs recently, and OpenStack is creating theirs. Satellie has theirs, too.
Please see https://access.redhat.com/articles/2918071#section-508-8
On behalf of our government customers, we'd like to ask if it's possible to provide something for IDE evaluators who ask about a VPAT for DevStudio. (We have had cases.)
There's an RFE open for JBTSIS, it's at [2]. Perhaps this is better provided as an RFE for DevStudio, that's easily arranged if it's deemed proper.
Please consider, discuss further as needed. It seems possible that providing a VPAT might lend some advantages in dealing with government customers (and will probably lead to a better product, anyway.)
Thanks,
Rick
[1] https://www.section508.gov/content/sell/vpat
[2] https://issues.jboss.org/browse/JBTIS-1151
--
RON PACHECO
DIRECTOR, PRODUCT MANAGEMENT, PLATFORMS BU
Red Hat
rpacheco(a)redhat.com T: 978-392-3912
TRIED. TESTED. TRUSTED.
@redhatnews Red Hat Red Hat
Bob Davis
5:17 PM (17 hours ago)
to Rick, devtools-progr., Wagner
Hey Rick -
Should this be something we consider for everything that DevTools does that has a GUI?
On its face, it seems like something we should just do, unless it's super time consuming or difficult.
Bob
Rick Wagner
8:18 AM (2 hours ago)
to Bob, devtools-progr., Wagner
Hi Bob and All,
I think it is something we should consider for wider use. (As Ron pointed out, other RH products are doing it.)
It seems like it might help with government sales (perhaps more so in the future, hard to judge), and it just seems like a good thing to do.
Probably we should evaluate it to see what kind of effort is required. GSS considers this a 'nice to have', so if our findings indicate it's not practical, we'll be happy with the status quo. But if we can add it without much trouble, it seems like there are upsides.
My .02,
Rick
Jean-Francois Maury
8:36 AM (2 hours ago)
to Rick, Wagner, devtools-progr.
Looked at the Microsoft reports for VS and they are very detailed so we need an accessibility expert there
Jeff
Rich Sharples <rsharple(a)redhat.com>
8:47 AM (2 hours ago)
to Bob, Rick, devtools-progr., Wagner
Quite simply - if you want to be considered for any us gov agencies - federal or state - you will need to comply with 508 to some degree. A VPAT is the lowest acceptable bar.
For MW products we still contract out the evaluation - it's around $25k per product major
Release (excluding any required remediation work). At some point it may be more cost effective to do this work ourselves - we've discussed that numerous times over the years.
Bob Davis
9:25 AM (1 hour ago)
to Rich, devtools-progr., Wagner, Rick
So this is a significant LOE as compared to say, the EARF?
I'd be interested in seeing what the possible return on that investment would be - how would having a VPAT for DevStudio drive sales in MW or RHEL? What are these gov users using now, and is that "workaround" working for them? Would they even use DevStudio if it were an option?
Rich Sharples <rsharple(a)redhat.com>
9:34 AM (1 hour ago)
to Bob, devtools-progr., Wagner, Rick
On Wed, Aug 2, 2017 at 9:25 AM, Bob Davis <bodavis(a)redhat.com> wrote:
So this is a significant LOE as compared to say, the EARF?
I'd be interested in seeing what the possible return on that investment would be - how would having a VPAT for DevStudio drive sales in MW or RHEL? What are these gov users using now, and is that "workaround" working for them? Would they even use DevStudio if it were an option?
Good questions for our very large NA public sector team - you may want to start with Jim Tyrell.
Ronald Pacheco <rpacheco(a)redhat.com>
9:36 AM (1 hour ago)
to Rick, Wagner, devtools-progr.
The reason the other teams have provided updates is because customers in the public sector (which also includes education, local governments, defense, etc.) added the VPAT declaration as a bid requirement. From my perspective, it helps to provide clarity on what we deliver and support as well as what we don't.
HTH
Ron
Ronald Pacheco <rpacheco(a)redhat.com>
9:38 AM (1 hour ago)
to Rick, Wagner, devtools-progr.
FWIW, it was not very heavy lifting. In fact, even a PM can do the bulk of the work in less than 1 week. ;-)
Paul Leacu <pleacu(a)redhat.com>
9:50 AM (1 hour ago)
to Catherine, Andrej, Ronald, Rick, Wagner, devtools-progr.
Hey - ccing Catherine Robson as this is really a UX discussion
Just for comparison - here's the OpenShift 3.1 VPAT:
https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf
and here's an older EAP VPAT provided by an outside vendor:
https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-...
Given just Devstudio (+ Integration Stack layered tooling for SOA, DataVirt and B*MS) - this appears to be a pretty daunting task. To be able to accurately address each "Section 1194" criteria would require QE and engineering participation. Then there's the rest of DevTools. I guess the confusing part is exactly how accurately do they need these criteria answered?
--paull
Ronald Pacheco
9:54 AM (1 hour ago)
to me, Catherine, Andrej, Rick, Wagner, devtools-progr.
If it helps, here's the draft I used
https://docs.google.com/a/redhat.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj...
> Section 508 - VPAT Compatibility
> --------------------------------
>
> Key: JBTIS-1151
> URL: https://issues.jboss.org/browse/JBTIS-1151
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 10.3.0.GA
> Environment:
> Reporter: Wagner Queiroz
> Assignee: Paul Leacu
> Priority: Minor
>
> Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release.
> Ref: https://mojo.redhat.com/docs/DOC-28860
> Some useful info before going to a formal evaluation:
> https://mojo.redhat.com/docs/DOC-175787
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24790:
-------------------------------------
Story Points: 2
> Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24790
> URL: https://issues.jboss.org/browse/JBIDE-24790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: screenshot-1.png
>
>
> When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes).
> Furthermore the text field and browse button are not properly aligned with the right border, there's a gap.
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24790:
------------------------------------------
merged into master
> Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24790
> URL: https://issues.jboss.org/browse/JBIDE-24790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: screenshot-1.png
>
>
> When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes).
> Furthermore the text field and browse button are not properly aligned with the right border, there's a gap.
> !screenshot-1.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24675?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-24675.
------------------------------
Resolution: Won't Fix
Since the same functionality is already being tested in the p2director tests (headless) and the reddeer tests (UI), Lukas and I have decided to deprecate and disable these install-grinder tests as we no longer need them.
I've therefore renamed (adding *DEPRECATED_* suffix) and moved the jobs to the 10.x view [0].
I've also moved the 10.x install grinder stuff into that view, so we no longer need the old devstudio_installation_tests view, which has been deleted.
And I moved the p2director install tests for master branch into the master view [1].
So, we have that test [1], plus the composite install test [2], and all these [3].
[0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24675
> URL: https://issues.jboss.org/browse/JBIDE-24675
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: install-tests
> Affects Versions: 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 4.5.0.Final
>
>
> {code}
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi)
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace )
> 15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec
> 15:52:02
> 15:52:02 Testcase: testInstall took 26.254 sec
> 15:52:02 Caused an ERROR
> 15:52:02 Internal error
> 15:52:02 java.lang.RuntimeException: Internal error
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh...
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
> 15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
> 15:52:02 at java.lang.Thread.run(Thread.java:748)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24704) Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24704?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-24704.
---------------------------------
> Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing
> --------------------------------------------------------------------------------
>
> Key: JBIDE-24704
> URL: https://issues.jboss.org/browse/JBIDE-24704
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.5.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: cdk, central-ci, jenkins
> Fix For: 4.5.0.Final
>
>
> It was found out, that cdk3 can be started in CLI on win7-x64 slave with pre-installed virtualbox in central ci env. and so, I am planning to:
> * prepare machine as a new snapshot in openstack images section, tune possible bugs
> * create new template/label in jenkins for this machine
> * create a job in jenkins that would test cdk3 start up on this slave
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months