[JBoss JIRA] (JBDS-3624) Error while parsing response from auth server
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3624?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3624:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Developer Platform)
Key: JBDS-3624 (was: DEVEX-73)
Workflow: CDW v1 (was: jira)
Component/s: (was: Installer)
Fix Version/s: 9.1.0.CR1
(was: Christmas 2015)
> Error while parsing response from auth server
> ---------------------------------------------
>
> Key: JBDS-3624
> URL: https://issues.jboss.org/browse/JBDS-3624
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: auth-error.png
>
>
> # npm start
> # type "asdf" to username field
> # type "asdf" to password field
> # open dev tools (Ctrl + Shift + i on Linux)
> # click "Log in" button
> result:
> This stack trace appears in console log:
> {code}
> SyntaxError: Unexpected token I
> at Object.parse (native)
> at fromJson (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:1274:14)
> at defaultHttpResponseTransform (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9463:16)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9554:12
> at forEach (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:343:20)
> at transformData (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9553:3)
> at transformResponse (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:10322:21)
> at processQueue (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14795:28)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14811:27
> at Scope.$eval (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:16055:28)
> {code}
> JSON.parse failes because the server returned "Invalid user credentials for user asdf"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3625) Vagrant delivered by installer has no vagrant.exe
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3625?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3625:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Developer Platform)
Key: JBDS-3625 (was: DEVEX-98)
Workflow: CDW v1 (was: jira)
Component/s: (was: Installer)
Affects Version/s: (was: Christmas 2015)
Fix Version/s: 9.1.0.CR1
(was: Beta)
> Vagrant delivered by installer has no vagrant.exe
> -------------------------------------------------
>
> Key: JBDS-3625
> URL: https://issues.jboss.org/browse/JBDS-3625
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Environment: Windows x86_64
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> As [~hardy.ferentschik] pointed out in DEVEX-90 vagrant from installer (see https://github.com/redhat-developer-tooling/vagrant-distribution) has no vagrant.exe, but original vagrant installer does have it.
> That should be fixed in vagrant distributed by installer, because current tools implementation expects vagrant.exe to be available.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3618) Progress does not reflect actual amount of work done
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3618?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3618:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Developer Platform)
Key: JBDS-3618 (was: DEVEX-107)
Workflow: CDW v1 (was: jira)
Component/s: (was: Installer)
> Progress does not reflect actual amount of work done
> ----------------------------------------------------
>
> Key: JBDS-3618
> URL: https://issues.jboss.org/browse/JBDS-3618
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Reporter: Jan Richter
> Priority: Minor
> Labels: havoc
>
> It seems the current way the progress tracking is implemented is simply by giving an initial time estimate for each component. The progress bars then just count down the supplied time with no relation to the actual progress achieved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3617:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Developer Platform)
Key: JBDS-3617 (was: DEVEX-90)
Workflow: CDW v1 (was: jira)
Component/s: (was: Installer)
Affects Version/s: (was: Christmas 2015)
> Cannot run vagrant after running installer
> ------------------------------------------
>
> Key: JBDS-3617
> URL: https://issues.jboss.org/browse/JBDS-3617
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Environment: Windows 10
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc
> Attachments: Vagrant.png
>
>
> See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer.
> Exception occurred executing command line.
> {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3619) Script authorization error
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3619?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3619:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Developer Platform)
Key: JBDS-3619 (was: DEVEX-94)
Workflow: CDW v1 (was: jira)
Component/s: (was: Installer)
> Script authorization error
> --------------------------
>
> Key: JBDS-3619
> URL: https://issues.jboss.org/browse/JBDS-3619
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Reporter: Shane Bryzak
> Labels: havoc
> Attachments: screenshot.png
>
>
> !screenshot.png|thumbnail!
> The above error happens after all components have been downloaded. Running Windows 10.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3620) Account page should take into consideration that login request can be long term operation
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3620?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3620:
--------------------------------
> Account page should take into consideration that login request can be long term operation
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3620
> URL: https://issues.jboss.org/browse/JBDS-3620
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> Would be good to:
> 1. Show progress animation;
> 2. Lock [Log In] button;
> 3. Have a timeout for login operation with error show in the end and button unlocked for another attempt.
> Currently auth fails in browser with error below
> {code}Gateway Timeout
> The proxy server did not receive a timely response from the upstream server.
> Reference #1.5434d417.1452674127.644f0c55
> {code}
> which makes installer to look like being in broken state:
> - no errors;
> - [Log In] can be pressed many times without any reaction
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month