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

See

Jenkins build is still unstable: airavata-dev #1312

See

Jenkins build is still unstable: airavata-dev #1311

See

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

See

Jenkins build is still unstable: airavata-dev #1310

See

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

See

Jenkins build is still unstable: airavata-dev #1309

See

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

See

Jenkins build is still unstable: airavata-dev #1308

See

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

See

Jenkins build is still unstable: airavata-dev #1307

See

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

See

Jenkins build is still unstable: airavata-dev #1306

See

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

See

Jenkins build is still unstable: airavata-dev #1305

See

Jenkins build is still unstable: airavata-dev #1304

See

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

See

[jira] [Commented] (AIRAVATA-2153) Added comment to Gateway request is not available when the record is viewed again

[ https://issues.apache.org/jira/browse/AIRAVATA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658483#comment-15658483 ] Eroma commented on AIRAVATA-2153: - Still the same saved comments are not available when viewed again >

[jira] [Closed] (AIRAVATA-2155) 'Deactivate Gateway' button should exists only for gateway requests which are approved.

[ https://issues.apache.org/jira/browse/AIRAVATA-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2155. --- tested and verified in https://dev.scigap.org/ Now upon creating the tenant only 'Deactivate Gateway'

[jira] [Closed] (AIRAVATA-2025) When clicked 'Approved' for a gateway request error exception thrown

[ https://issues.apache.org/jira/browse/AIRAVATA-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2025. --- tested and verified in https://dev.scigap.org/ when a gateway request is submitted SciGaP admin can use

[jira] [Closed] (AIRAVATA-2030) Cannot login to WSO2 IS using newly created gateways admin username and password

[ https://issues.apache.org/jira/browse/AIRAVATA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2030. --- tested and verified in https://dev.scigap.org/ Now the tenant get created successfully and can login to IS

[jira] [Created] (AIRAVATA-2224) Contact email given for gateway requests page need to change

Eroma created AIRAVATA-2224: --- Summary: Contact email given for gateway requests page need to change Key: AIRAVATA-2224 URL: https://issues.apache.org/jira/browse/AIRAVATA-2224 Project: Airavata

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

[ https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658328#comment-15658328 ] ASF GitHub Bot commented on AIRAVATA-2163: -- Github user anujbhan closed the pull request at:

[GitHub] airavata issue #74: AIRAVATA-2163: Optimising the cred store data model

Github user anujbhan commented on the issue: https://github.com/apache/airavata/pull/74 https://github.com/apache/airavata/pull/76, refer this 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

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

[ https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658327#comment-15658327 ] ASF GitHub Bot commented on AIRAVATA-2163: -- Github user anujbhan commented on the issue:

[GitHub] airavata pull request #74: AIRAVATA-2163: Optimising the cred store data mod...

Github user anujbhan closed the pull request at: https://github.com/apache/airavata/pull/74 --- 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

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

GitHub user anujbhan opened a pull request: https://github.com/apache/airavata/pull/76 Optimise cred store data models This pull request resolves the merge conflicts in https://github.com/apache/airavata/pull/74 and also adds few incremental changes to credential-storestub pom

[jira] [Closed] (AIRAVATA-1654) Document all possible job state mismatches in Airavata.

[ https://issues.apache.org/jira/browse/AIRAVATA-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1654. --- > Document all possible job state mismatches in Airavata. >

[jira] [Closed] (AIRAVATA-1568) Integrate XBAYA with Airavata Workflow Engine/ Workflow Interpreter

[ https://issues.apache.org/jira/browse/AIRAVATA-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1568. --- > Integrate XBAYA with Airavata Workflow Engine/ Workflow Interpreter >

[jira] [Closed] (AIRAVATA-1540) XBaya GUI froze when an experiment is launched. Killed the XBaya process but didn't work

[ https://issues.apache.org/jira/browse/AIRAVATA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1540. --- XBAYA not integrated and update with Airavata 0.16. Hence this is not a valid feature/functional scenario any

[jira] [Closed] (AIRAVATA-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

[ https://issues.apache.org/jira/browse/AIRAVATA-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2190. --- tested and verified in https://dev.seagrid.org > User A shared a single experiment with User B, read access.

[jira] [Closed] (AIRAVATA-2196) Both users with 'Read' access and 'Write' access should NOT have the same set of privileges in PGA

[ https://issues.apache.org/jira/browse/AIRAVATA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2196. --- tested and verified in https://dev.seagrid.org/ When experiments shared with READ access Can clone and

[jira] [Commented] (AIRAVATA-2195) Shared user will end up with an experiment which he has no permission to view

[ https://issues.apache.org/jira/browse/AIRAVATA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658128#comment-15658128 ] Marcus Christie commented on AIRAVATA-2195: --- This is basically done. I just need to test with

[jira] [Closed] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal

[ https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2080. --- tested and verified in https://dev.seagrid.org/ Project summary can be viewed successfully. Even with shared

[jira] [Closed] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user

[ https://issues.apache.org/jira/browse/AIRAVATA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2021. --- tested and verified in https://dev.seagrid.org/ When user A shared a single experiment with User B, only the

[jira] [Closed] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module

[ https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2120. --- > Application deployments are merged together when tried to create a new > deployment in same resource using

Jenkins build is back to stable : airavata-dev #1300

See

Jenkins build is back to stable : airavata-dev » Airavata Registry Core #1300

See

[jira] [Updated] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2193: -- Assignee: Eroma (was: Marcus Christie) > When projects of other users are available

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657909#comment-15657909 ] Marcus Christie commented on AIRAVATA-2193: --- This is on dev.seagrid.org and should be fixed

[jira] [Updated] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2193: -- Description: Currently in Experiment creation we only show the project name. When

[jira] [Resolved] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2212. --- Resolution: Fixed > Experiment Auto Refresh may try to reload the page while

[jira] [Closed] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie closed AIRAVATA-2212. - > Experiment Auto Refresh may try to reload the page while reloading the page >

[jira] [Reopened] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie reopened AIRAVATA-2212: --- > Experiment Auto Refresh may try to reload the page while reloading the page >

[jira] [Updated] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2212: -- Fix Version/s: 0.17-SNAPSHOT > Experiment Auto Refresh may try to reload the page

[jira] [Resolved] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2212. --- Resolution: Fixed > Experiment Auto Refresh may try to reload the page while

[jira] [Closed] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie closed AIRAVATA-2212. - > Experiment Auto Refresh may try to reload the page while reloading the page >

[jira] [Resolved] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal

[ https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2080. --- Resolution: Fixed > When tried to view the project summary

[jira] [Commented] (AIRAVATA-2015) When a gateway user shares a project or an experiment have a notification sent

[ https://issues.apache.org/jira/browse/AIRAVATA-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657848#comment-15657848 ] Supun Chathuranga Nakandala commented on AIRAVATA-2015: --- [~eroma_a] Can't we

[jira] [Closed] (AIRAVATA-1927) In SEAGrid desktop client NanoCAD window 'Import Structure' screen is not opening

[ https://issues.apache.org/jira/browse/AIRAVATA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1927. --- tested and verified in production SEAGrid desktop client. Now the import structure opens when clicked on

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

See

Jenkins build is still unstable: airavata-dev #1299

See

[jira] [Updated] (AIRAVATA-2064) In ultrascan production PGA cannot view outputs. Getting the attached error

[ https://issues.apache.org/jira/browse/AIRAVATA-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2064: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > In

[jira] [Resolved] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module

[ https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2120. --- Resolution: Won't Fix > Application deployments are merged

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

See

Jenkins build is still unstable: airavata-dev #1298

See

[jira] [Resolved] (AIRAVATA-2175) Prevent changing project owner

[ https://issues.apache.org/jira/browse/AIRAVATA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2175. --- Resolution: Fixed > Prevent changing project owner >

[jira] [Commented] (AIRAVATA-2175) Prevent changing project owner

[ https://issues.apache.org/jira/browse/AIRAVATA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657609#comment-15657609 ] ASF subversion and git services commented on AIRAVATA-2175: --- Commit

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657590#comment-15657590 ] ASF subversion and git services commented on AIRAVATA-2212: --- Commit

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657594#comment-15657594 ] ASF GitHub Bot commented on AIRAVATA-2193: -- Github user asfgit closed the pull request at:

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657592#comment-15657592 ] ASF subversion and git services commented on AIRAVATA-2212: --- Commit

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657591#comment-15657591 ] ASF subversion and git services commented on AIRAVATA-2193: --- Commit

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657593#comment-15657593 ] ASF GitHub Bot commented on AIRAVATA-2212: -- Github user asfgit closed the pull request at:

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

[ https://issues.apache.org/jira/browse/AIRAVATA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657587#comment-15657587 ] ASF GitHub Bot commented on AIRAVATA-2163: -- Github user scnakandala commented on the issue:

[jira] [Closed] (AIRAVATA-1960) Ability to mark inputs as 'Optional'. These are not mandatory to be available at create experiment.

[ https://issues.apache.org/jira/browse/AIRAVATA-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1960. --- tested and verified in https://dev.seagrid.org/ We can enable optional inputs at application interface

[GitHub] airavata issue #74: AIRAVATA-2163: Optimising the cred store data model

Github user scnakandala commented on the issue: https://github.com/apache/airavata/pull/74 @anujbhan Is this an active pull request ? If so can you fix the 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

[jira] [Commented] (AIRAVATA-2206) When the SEAGrid rich client times out have the login page to appear for logins

[ https://issues.apache.org/jira/browse/AIRAVATA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657582#comment-15657582 ] Supun Chathuranga Nakandala commented on AIRAVATA-2206: --- [~eroma_a] when this

[jira] [Resolved] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API

[ https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2185. --- Resolution: Fixed > Add OWNER ResourcePermissionType to

[jira] [Commented] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API

[ https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657578#comment-15657578 ] ASF subversion and git services commented on AIRAVATA-2185: --- Commit

[jira] [Updated] (AIRAVATA-2223) Support for data sharing disabled

[ https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2223: -- Fix Version/s: 0.17-SNAPSHOT > Support for data sharing disabled >

[jira] [Closed] (AIRAVATA-1997) Gateway ID saved as project name. Default Project not existing for new users.

[ https://issues.apache.org/jira/browse/AIRAVATA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-1997. --- tested and verified in https://dev.seagrid.org/ > Gateway ID saved as project name. Default Project not

[jira] [Resolved] (AIRAVATA-2196) Both users with 'Read' access and 'Write' access should NOT have the same set of privileges in PGA

[ https://issues.apache.org/jira/browse/AIRAVATA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-2196. - Resolution: Fixed > Both users with 'Read' access and 'Write' access should NOT have the same set >

[jira] [Resolved] (AIRAVATA-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.

[ https://issues.apache.org/jira/browse/AIRAVATA-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-2190. - Resolution: Fixed > User A shared a single experiment with User B, read access. Project is also >

[jira] [Commented] (AIRAVATA-2195) Shared user will end up with an experiment which he has no permission to view

[ https://issues.apache.org/jira/browse/AIRAVATA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657562#comment-15657562 ] Marcus Christie commented on AIRAVATA-2195: --- I don't think I can implement this until

[jira] [Commented] (AIRAVATA-2223) Support for data sharing disabled

[ https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657543#comment-15657543 ] Suresh Marru commented on AIRAVATA-2223: Since this is a " experimental feature" and needs more

[jira] [Closed] (AIRAVATA-2202) Experiment data not available in https://data.seagrid.org/

[ https://issues.apache.org/jira/browse/AIRAVATA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2202. --- tested and verified in production seagrid and https://data.seagrid.org Now soon after the job and experiment

[jira] [Commented] (AIRAVATA-2223) Support for data sharing disabled

[ https://issues.apache.org/jira/browse/AIRAVATA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657520#comment-15657520 ] Marcus Christie commented on AIRAVATA-2223: --- [~eroma_a], [~smarru], Just want to confirm

[jira] [Closed] (AIRAVATA-2081) Error exception thrown when clicked on clone for an experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2081. --- tested and verified in https://dev.seagrid.org > Error exception thrown when clicked on clone for an

[jira] [Created] (AIRAVATA-2223) Support for data sharing disabled

Marcus Christie created AIRAVATA-2223: - Summary: Support for data sharing disabled Key: AIRAVATA-2223 URL: https://issues.apache.org/jira/browse/AIRAVATA-2223 Project: Airavata Issue

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

See

Jenkins build is still unstable: airavata-dev #1297

See

[jira] [Closed] (AIRAVATA-2213) Experiment Summary is not getting refreshed!

[ https://issues.apache.org/jira/browse/AIRAVATA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2213. --- tested and verified in https://dev.seagrid.org/ Now the Experiment summary gets experiment and job statuses

[jira] [Resolved] (AIRAVATA-2213) Experiment Summary is not getting refreshed!

[ https://issues.apache.org/jira/browse/AIRAVATA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-2213. - Resolution: Fixed > Experiment Summary is not getting refreshed! >

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

See

Jenkins build is still unstable: airavata-dev #1296

See

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657369#comment-15657369 ] ASF GitHub Bot commented on AIRAVATA-2193: -- Github user machristie commented on the issue:

[jira] [Commented] (AIRAVATA-2193) When projects of other users are available for experiment creation cannot figure out to whom it belongs

[ https://issues.apache.org/jira/browse/AIRAVATA-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657366#comment-15657366 ] ASF GitHub Bot commented on AIRAVATA-2193: -- GitHub user machristie opened a pull request:

[GitHub] airavata-php-gateway issue #37: AIRAVATA-2193 Distinguish projects owned by ...

Github user machristie commented on the issue: https://github.com/apache/airavata-php-gateway/pull/37 @scnakandala can you review when you get a chance? Thanks. --- 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

[GitHub] airavata-php-gateway pull request #37: AIRAVATA-2193 Distinguish projects ow...

GitHub user machristie opened a pull request: https://github.com/apache/airavata-php-gateway/pull/37 AIRAVATA-2193 Distinguish projects owned by other users You can merge this pull request into a Git repository by running: $ git pull

[jira] [Assigned] (AIRAVATA-2207) Gateway admins cannot view experiments launched by gateway users in Experiment Statistics

[ https://issues.apache.org/jira/browse/AIRAVATA-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie reassigned AIRAVATA-2207: - Assignee: Eroma (was: Marcus Christie) > Gateway admins cannot view

[jira] [Commented] (AIRAVATA-2207) Gateway admins cannot view experiments launched by gateway users in Experiment Statistics

[ https://issues.apache.org/jira/browse/AIRAVATA-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657266#comment-15657266 ] Marcus Christie commented on AIRAVATA-2207: --- I've deployed this fix to dev.seagrid.org and

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

See

Jenkins build is still unstable: airavata-dev #1295

See

[jira] [Closed] (AIRAVATA-2188) Created user account in gateway portal has no roles displayed or no roles can be assigned!

[ https://issues.apache.org/jira/browse/AIRAVATA-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2188. --- tested and verified in https://dev.seagrid.org Roles are getting assigned correctly. > Created user account

[jira] [Resolved] (AIRAVATA-2188) Created user account in gateway portal has no roles displayed or no roles can be assigned!

[ https://issues.apache.org/jira/browse/AIRAVATA-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma resolved AIRAVATA-2188. - Resolution: Fixed > Created user account in gateway portal has no roles displayed or no roles can >

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

See

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657093#comment-15657093 ] ASF GitHub Bot commented on AIRAVATA-2212: -- Github user machristie commented on the issue:

[GitHub] airavata-php-gateway issue #36: AIRAVATA-2212 Using setInterval so status ch...

Github user machristie commented on the issue: https://github.com/apache/airavata-php-gateway/pull/36 @scnakandala I found a bug in my solution. This PR fixes it. Can you please review when you get a chance? --- If your project is set up for it, you can reply to this email and have

[jira] [Commented] (AIRAVATA-2212) Experiment Auto Refresh may try to reload the page while reloading the page

[ https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657086#comment-15657086 ] ASF GitHub Bot commented on AIRAVATA-2212: -- GitHub user machristie opened a pull request:

[GitHub] airavata-php-gateway pull request #36: AIRAVATA-2212 Using setInterval so st...

GitHub user machristie opened a pull request: https://github.com/apache/airavata-php-gateway/pull/36 AIRAVATA-2212 Using setInterval so status check is turned back on The way it was implemented with setTimeout the status checking (autoRefresh) wouldn't start again once it was

  1   2   >