date:20161212


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743165#comment-15743165
 ] 

Supun Chathuranga Nakandala commented on AIRAVATA-2247:
---

>From my initial check, I think this is coming because of the iterative user 
>profile information retrieval from IS.

> 'TSocket read 0 bytes' error when PGA calls getAllNotifications
> ---
>
> Key: AIRAVATA-2247
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2247
> Project: Airavata
>  Issue Type: Bug
>  Components: Airavata API, PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Getting the following error intermittently in PGA
> {noformat}
> [2016-12-01 16:40:05] production.ERROR: exception 
> 'Thrift\Exception\TTransportException' with message
>  'TSocket read 0 bytes' in 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TSocket.php:26
> 9
> Stack trace:
> #0 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TTransport.php(74):
>  Thrift\Transport\T
> Socket->read(4)
> #1 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(305):
>  Thrift\Transp
> ort\TTransport->readAll(4)
> #2 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(197):
>  Thrift\Protoc
> ol\TBinaryProtocol->readI32(NULL)
> #3 
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4960): 
> Thrift\Protocol\TBinar
> yProtocol->readMessageBegin(NULL, 0, 0)
> #4 
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4928): 
> Airavata\API\AiravataC
> lient->recv_getAllNotifications()
> #5 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(21
> 1): 
> Airavata\API\AiravataClient->getAllNotifications(Object(Airavata\Model\Security\AuthzToken),
>  'sea
> grid')
> #6 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368): 
> Illuminate\Support\Facades\Fa
> cade::__callStatic('getAllNotificat...', Array)
> #7 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368): 
> Airavata\Facades\Airavata::ge
> tAllNotifications(Object(Airavata\Model\Security\AuthzToken), 'seagrid')
> #8 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(214): 
> CommonUtilities::get_all_noti
> ces()
> #9 
> /var/www/portals/dev-seagrid/app/storage/views/5300885e7f238cf07a10aa6eceb271f8(37):
>  CommonUtiliti
> es::create_nav_bar()
> #10 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #11 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57): 
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #12 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
>  Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #13 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
>  Illumina
> te\View\View->getContents()
> #14 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
>  Illuminat
> e\View\View->renderContents()
> #15 
> /var/www/portals/dev-seagrid/app/storage/views/d7a45c81bb507afc6ab5ba9806a3833d(60):
>  Illuminate\V
> iew\View->render()
> #16 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #17 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57): 
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #18 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
>  Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #19 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
>  Illumina
> te\View\View->getContents()
> #20 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
>  Illuminat
> e\View\View->renderContents()
> #21 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Http/Response.php(43):
>  Illum
> inate\View\View->render()
> #22 
> /var/www/portals/dev-seagrid/vendor/symfony/http-foundation/Response.php(202):
>  Illuminate\Http\Re
> sponse->setContent(Object(Illuminate\View\View))
> #23 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1501):
>  Sy
> mfony\Component\HttpFoundation\Response->__construct(Object(Illuminate\View\View))
> #24 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1036):

[jira] [Commented] (AIRAVATA-2203) Migrate user profiles from IS to Airavata Internal Registry

2016-12-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743144#comment-15743144
 ] 

ASF GitHub Bot commented on AIRAVATA-2203:
--

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/84
  
https://issues.apache.org/jira/browse/AIRAVATA-2203



> Migrate user profiles from IS to Airavata Internal Registry
> ---
>
> Key: AIRAVATA-2203
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2203
> Project: Airavata
>  Issue Type: Task
>Affects Versions: 0.16
>Reporter: Anuj Bhandar
>Assignee: Anuj Bhandar
>  Labels: GATask
>
> Migrating the User profiles from WSO2 IS for all tenants to Airavata internal 
> registry



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata issue #84: User profile migration module

2016-12-12 Thread anujbhan

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/84
  
https://issues.apache.org/jira/browse/AIRAVATA-2203



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] airavata pull request #84: User profile migration module

2016-12-12 Thread anujbhan

GitHub user anujbhan opened a pull request:

https://github.com/apache/airavata/pull/84

User profile migration module

_Contains_
 *  Workspace catalog registry module from Registry-refractoring branch
 *  User-Profile Thrift service
 *  User-Profile-migration module

_Note_
 *  I did not find the new feature branch which was specifically created 
for putting this code, hence submitting to develop
 *  No sensitive information is committed, hence the migration module will 
not work out-of-box, will need the server cert file and credentials to run.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anujbhan/airavata userProfileMigration

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata/pull/84.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #84


commit d9a69ae546736ce3265b6b5cedeeb6a2361293d8
Author: Anuj Bhandar 
Date:   2016-12-12T20:00:27Z

migrating user-profile service and new registry components to develop branch

commit 49afd997f2f30ccabb83a30059f0e4483553a640
Author: Anuj Bhandar 
Date:   2016-12-12T20:51:57Z

adding the user-profile migration module to develop branch




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: airavata-dev #2030

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2030

2016-12-12 Thread Apache Jenkins Server

See

[jira] [Created] (AIRAVATA-2271) All date time fields in PGA should use single format of showing the date and time.

2016-12-12 Thread Eroma (JIRA)

Eroma created AIRAVATA-2271:
---

 Summary: All date time fields in PGA should use single format of 
showing the date and time.
 Key: AIRAVATA-2271
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2271
 Project: Airavata
  Issue Type: Bug
  Components: PGA PHP Web Gateway
 Environment: PGA

Reporter: Eroma
Assignee: Marcus Christie


Currently in PGA we use date time fields in
Browse experiment
Set gateway preference
Create Notices
List experiments in Experiment Statistics.

Except for experiment statistics all other UIs should use a uniform way of 
showing this calendar field. Currently we use different ways, some are kept 
empty, some has current date time, etc...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AIRAVATA-2271) All date time fields in PGA should use single format of showing the date and time.

2016-12-12 Thread Eroma (JIRA)


 [ 
https://issues.apache.org/jira/browse/AIRAVATA-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eroma updated AIRAVATA-2271:

Priority: Minor  (was: Major)

> All date time fields in PGA should use single format of showing the date and 
> time.
> --
>
> Key: AIRAVATA-2271
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2271
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: PGA
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Minor
>
> Currently in PGA we use date time fields in
> Browse experiment
> Set gateway preference
> Create Notices
> List experiments in Experiment Statistics.
> Except for experiment statistics all other UIs should use a uniform way of 
> showing this calendar field. Currently we use different ways, some are kept 
> empty, some has current date time, etc...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-1792) Implement ability for admin to search for experiments using the created user as well

2016-12-12 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742832#comment-15742832
 ] 

Marcus Christie commented on AIRAVATA-1792:
---

Discussed with Eroma:
* username filtering will do substring matching instead of exact matching. So 
"marcus" will match "marcus", "marcus-user", etc.
** I'll likewise do the same with resource and application name matching

> Implement ability for admin to search for experiments using the created user 
> as well
> 
>
> Key: AIRAVATA-1792
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1792
> Project: Airavata
>  Issue Type: New Feature
>  Components: PGA PHP Web Gateway
>Affects Versions: 0.15
> Environment: https://testdrive.airavata.org/portal/pga/public/
>Reporter: Eroma
>Assignee: Marcus Christie
> Fix For: 0.17-SNAPSHOT
>
>
> Currently admin user can search for experiments in the Admin Dashboard --> 
> Experiment Statistics page by giving a date range. Along with the date range 
> please implement the ability to search by giving the experiment created user 
> as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: airavata-dev #2029

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2029

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev #2028

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2028

2016-12-12 Thread Apache Jenkins Server

See

[GitHub] airavata issue #76: Optimise cred store data models

2016-12-12 Thread anujbhan

Github user anujbhan commented on the issue:

https://github.com/apache/airavata/pull/76
  
making a new pull request with resolved conflicts


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AIRAVATA-2163) optimize credential store data models

2016-12-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742618#comment-15742618
 ] 

ASF GitHub Bot commented on AIRAVATA-2163:
--

GitHub user anujbhan opened a pull request:

https://github.com/apache/airavata/pull/83

Credential store data model optimization

https://issues.apache.org/jira/browse/AIRAVATA-2163

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anujbhan/airavata cred-opt

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #83


commit 122fb8da06408b1f203006e88a97e923be4fbc2a
Author: Anuj Bhandar 
Date:   2016-12-12T09:18:06Z

migrating cred data models to airavata datamodel directory

commit c1b696badd3ccfa686cdb21ab2da0012ec7dd354
Author: Anuj Bhandar 
Date:   2016-12-12T16:58:57Z

introducing summary type, dependencies and code clean up




> optimize credential store data models
> -
>
> Key: AIRAVATA-2163
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2163
> Project: Airavata
>  Issue Type: Improvement
>  Components: Airavata API
> Environment: Development
>Reporter: Anuj Bhandar
>Assignee: Anuj Bhandar
>  Labels: GATask
> Fix For: 17
>
>
> This improvement is based on the following Pull request : 
> https://github.com/apache/airavata/pull/54.
> **Improvements agreed upon :** 
> Followings are few suggestions to improve your pull request.
> * We can do this in a better way by adding generic API method(to 
> AiravataAPIServer) like "getAllCredentialSummary" instead of adding API 
> method for each credential types eg: "getAllGatewaySSHPubKeysSummary" which 
> will return all the credential summary for that particular gatewayId. You may 
> be able to remove few redundant methods from Airavata API server.
> * Let's introduced one credential summary struct to all credential types, 
> how we differentiate is we have credential type enum field( SSH, PASSWD, CERT 
> etc ) in the credential summary thrift struct.
>  * Move credential data model thrift file to data model directory and 
> merge credential summary thrift file with it.
>  * Credential stubs still have date fields in generated thrift files, not 
> because your changes, but we need to fix it so remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] airavata pull request #83: Credential store data model optimization

2016-12-12 Thread anujbhan

GitHub user anujbhan opened a pull request:

https://github.com/apache/airavata/pull/83

Credential store data model optimization

https://issues.apache.org/jira/browse/AIRAVATA-2163

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anujbhan/airavata cred-opt

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/airavata/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #83


commit 122fb8da06408b1f203006e88a97e923be4fbc2a
Author: Anuj Bhandar 
Date:   2016-12-12T09:18:06Z

migrating cred data models to airavata datamodel directory

commit c1b696badd3ccfa686cdb21ab2da0012ec7dd354
Author: Anuj Bhandar 
Date:   2016-12-12T16:58:57Z

introducing summary type, dependencies and code clean up




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] airavata pull request #76: Optimise cred store data models

2016-12-12 Thread anujbhan

Github user anujbhan closed the pull request at:

https://github.com/apache/airavata/pull/76


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: airavata-dev #2027

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2027

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2026

2016-12-12 Thread Apache Jenkins Server

See

[jira] [Commented] (AIRAVATA-2270) When experiment ID consists '<' character cannot view the experiment details in experiment statistics.

2016-12-12 Thread Eroma (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742246#comment-15742246
 ] 

Eroma commented on AIRAVATA-2270:
-

we should check with other special characters included in the name as well.
~!@#$%^&*()_+?><,./;'":

> When experiment ID consists '<' character cannot view the experiment details 
> in experiment statistics.
> --
>
> Key: AIRAVATA-2270
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2270
> Project: Airavata
>  Issue Type: Bug
>  Components: PGA PHP Web Gateway
> Environment: https://dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>
> Experiment ID has experiment name as part of it.
> When we gave '<' as part of the experiment name the ID cannot be retrieved in 
> experiment statistics.
> No error message simply nothing gets retrieved. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AIRAVATA-2270) When experiment ID consists '<' character cannot view the experiment details in experiment statistics.

2016-12-12 Thread Eroma (JIRA)

Eroma created AIRAVATA-2270:
---

 Summary: When experiment ID consists '<' character cannot view the 
experiment details in experiment statistics.
 Key: AIRAVATA-2270
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2270
 Project: Airavata
  Issue Type: Bug
  Components: PGA PHP Web Gateway
 Environment: https://dev.seagrid.org
Reporter: Eroma
Assignee: Marcus Christie


Experiment ID has experiment name as part of it.
When we gave '<' as part of the experiment name the ID cannot be retrieved in 
experiment statistics.

No error message simply nothing gets retrieved. 





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AIRAVATA-2247) 'TSocket read 0 bytes' error when PGA calls getAllNotifications

2016-12-12 Thread Marcus Christie (JIRA)


[ 
https://issues.apache.org/jira/browse/AIRAVATA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742215#comment-15742215
 ] 

Marcus Christie commented on AIRAVATA-2247:
---

It seems to only happen when going to /project/create.

> 'TSocket read 0 bytes' error when PGA calls getAllNotifications
> ---
>
> Key: AIRAVATA-2247
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2247
> Project: Airavata
>  Issue Type: Bug
>  Components: Airavata API, PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Getting the following error intermittently in PGA
> {noformat}
> [2016-12-01 16:40:05] production.ERROR: exception 
> 'Thrift\Exception\TTransportException' with message
>  'TSocket read 0 bytes' in 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TSocket.php:26
> 9
> Stack trace:
> #0 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TTransport.php(74):
>  Thrift\Transport\T
> Socket->read(4)
> #1 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(305):
>  Thrift\Transp
> ort\TTransport->readAll(4)
> #2 
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(197):
>  Thrift\Protoc
> ol\TBinaryProtocol->readI32(NULL)
> #3 
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4960): 
> Thrift\Protocol\TBinar
> yProtocol->readMessageBegin(NULL, 0, 0)
> #4 
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4928): 
> Airavata\API\AiravataC
> lient->recv_getAllNotifications()
> #5 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(21
> 1): 
> Airavata\API\AiravataClient->getAllNotifications(Object(Airavata\Model\Security\AuthzToken),
>  'sea
> grid')
> #6 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368): 
> Illuminate\Support\Facades\Fa
> cade::__callStatic('getAllNotificat...', Array)
> #7 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368): 
> Airavata\Facades\Airavata::ge
> tAllNotifications(Object(Airavata\Model\Security\AuthzToken), 'seagrid')
> #8 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(214): 
> CommonUtilities::get_all_noti
> ces()
> #9 
> /var/www/portals/dev-seagrid/app/storage/views/5300885e7f238cf07a10aa6eceb271f8(37):
>  CommonUtiliti
> es::create_nav_bar()
> #10 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #11 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57): 
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #12 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
>  Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #13 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
>  Illumina
> te\View\View->getContents()
> #14 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
>  Illuminat
> e\View\View->renderContents()
> #15 
> /var/www/portals/dev-seagrid/app/storage/views/d7a45c81bb507afc6ab5ba9806a3833d(60):
>  Illuminate\V
> iew\View->render()
> #16 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #17 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57): 
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #18 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
>  Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #19 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
>  Illumina
> te\View\View->getContents()
> #20 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
>  Illuminat
> e\View\View->renderContents()
> #21 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Http/Response.php(43):
>  Illum
> inate\View\View->render()
> #22 
> /var/www/portals/dev-seagrid/vendor/symfony/http-foundation/Response.php(202):
>  Illuminate\Http\Re
> sponse->setContent(Object(Illuminate\View\View))
> #23 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1501):
>  Sy
> mfony\Component\HttpFoundation\Response->__construct(Object(Illuminate\View\View))
> #24 
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1036):
>  Illuminate\Routing\Router->prepareResponse(Object(Illuminate\Http\Request), 
>

Jenkins build is still unstable: airavata-dev #2025

2016-12-12 Thread Apache Jenkins Server

See

Jenkins build is still unstable: airavata-dev » Airavata Registry Core #2025

2016-12-12 Thread Apache Jenkins Server

See

[jira] [Created] (AIRAVATA-2269) The gateway admin cannot get access to the gateway even with 'admin' role

2016-12-12 Thread Eroma (JIRA)

Eroma created AIRAVATA-2269:
---

 Summary: The gateway admin cannot get access to the gateway even 
with 'admin' role
 Key: AIRAVATA-2269
 URL: https://issues.apache.org/jira/browse/AIRAVATA-2269
 Project: Airavata
  Issue Type: Bug
  Components: PGA PHP Web Gateway
 Environment: https://dev.scigap.org
http://test.scigap.org/
Reporter: Eroma
Assignee: Supun Chathuranga Nakandala


This is the PGA we set up after we created the tenant using 'Gateway Request' 
feature in dev.scigap.org



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)