[jira] [Resolved] (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:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2153. Resolution: Fixed > Added comment to Gateway request is not available when the record is viewed > again > - > > Key: AIRAVATA-2153 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2153 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Added comment to Gateway request is not available when the record is viewed > again. > SciGaP admin viewed a gateway request and then added a comment and clicked > update gateway. > 1. When SciGaP admin viewed the comment again it is not displayed in comment > section. > 2. In DB table 'GATEWAY' the added comment is saved in 'DECLINED_REASON'. > 3. Only added a comment and already the status in GATEWAY table is APPROVED. > 4. For the gateway requested PI the status is showed as APPROVED. Added > comments are displayed there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=15572987#comment-15572987 ] ASF subversion and git services commented on AIRAVATA-2153: --- Commit cd9117642430b329f39c69ba540591cc312ee13e in airavata-php-gateway's branch refs/heads/develop from [~ndoshi] [ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=cd91176 ] Fix for AIRAVATA-2153 > Added comment to Gateway request is not available when the record is viewed > again > - > > Key: AIRAVATA-2153 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2153 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Added comment to Gateway request is not available when the record is viewed > again. > SciGaP admin viewed a gateway request and then added a comment and clicked > update gateway. > 1. When SciGaP admin viewed the comment again it is not displayed in comment > section. > 2. In DB table 'GATEWAY' the added comment is saved in 'DECLINED_REASON'. > 3. Only added a comment and already the status in GATEWAY table is APPROVED. > 4. For the gateway requested PI the status is showed as APPROVED. Added > comments are displayed there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2154) Show more details of the gateway request to the gateway PI (request owner)
[ https://issues.apache.org/jira/browse/AIRAVATA-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572988#comment-15572988 ] ASF subversion and git services commented on AIRAVATA-2154: --- Commit 12827c150573fff948f6521a178fb515495af9ef in airavata-php-gateway's branch refs/heads/develop from [~ndoshi] [ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=12827c1 ] Changes added requested in AIRAVATA-2154 > Show more details of the gateway request to the gateway PI (request owner) > -- > > Key: AIRAVATA-2154 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2154 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi >Priority: Minor > > Currently once the gateway request is submitted only shows > 1. Gateway Name > 2. Creation Time > 3. Gateway Request Status > 4. Actions > 5. Comment > Should also add to above list > 1. Gateway URL > 2. Project details > 3. Project Abstract -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15572903#comment-15572903 ] ASF subversion and git services commented on AIRAVATA-2155: --- Commit 44df849993c299d974db1540d14efd29b1a1ba24 in airavata-php-gateway's branch refs/heads/develop from [~ndoshi] [ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=44df849 ] AIRAVATA-2155 fix. > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. > --- > > Key: AIRAVATA-2155 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2155 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (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 ] Nipurn Doshi resolved AIRAVATA-2155. Resolution: Fixed > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. > --- > > Key: AIRAVATA-2155 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2155 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] airavata pull request #54: Adding SSH Credential summary data model
Github user asfgit closed the pull request at: https://github.com/apache/airavata/pull/54 --- 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-2150) Invoke an MPI program run through a Mesos framework
[ https://issues.apache.org/jira/browse/AIRAVATA-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572270#comment-15572270 ] Mangirish Wagle commented on AIRAVATA-2150: --- Currently blocked due to Mesos cluster environment issues. > Invoke an MPI program run through a Mesos framework > --- > > Key: AIRAVATA-2150 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2150 > Project: Airavata > Issue Type: Task > Components: GFac >Reporter: Mangirish Wagle >Assignee: Mangirish Wagle > > Using the MPI library invoke MPI scripts through Mesos frameworks like > Marathon/ Chronos/ Apache Aurora. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2149) Compare MPI Libraries
[ https://issues.apache.org/jira/browse/AIRAVATA-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572267#comment-15572267 ] Mangirish Wagle commented on AIRAVATA-2149: --- Have a working solution with MPICH library. But I need to check if the "BSD Like" license of MPICH would be acceptable. Alternatively I am trying out OpenMPI library. > Compare MPI Libraries > - > > Key: AIRAVATA-2149 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2149 > Project: Airavata > Issue Type: Task > Components: GFac >Reporter: Mangirish Wagle >Assignee: Mangirish Wagle > Labels: Y790 > > Compare MPI libraries (MPICH and OpenMPI) and figure out the appropriate for > Airavata Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-2166) Support for uploading subdirectory
Dale Wang created AIRAVATA-2166: --- Summary: Support for uploading subdirectory Key: AIRAVATA-2166 URL: https://issues.apache.org/jira/browse/AIRAVATA-2166 Project: Airavata Issue Type: New Feature Reporter: Dale Wang We want to upload a sub-directory of files that is needed in the working directory for simulations executed by PHASTA gateway. https://phasta.scigap.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2152) UI for to add compute resource/storage allocations
[ https://issues.apache.org/jira/browse/AIRAVATA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571994#comment-15571994 ] Marcus Christie commented on AIRAVATA-2152: --- See also: https://lists.apache.org/thread.html/1687cd77dfedfc1b5e9e4d0341aeb7d0a1b35afdf9c8863898eb19a4@%3Cdev.airavata.apache.org%3E Only show these new options on the dashboard when the user has the 'individual-account-role-name' > UI for to add compute resource/storage allocations > -- > > Key: AIRAVATA-2152 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2152 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Marcus Christie >Assignee: Marcus Christie > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2165) In Firefox, portal pages are loaded twice more, with errors
[
https://issues.apache.org/jira/browse/AIRAVATA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2165:
--
Attachment: AIRAVATA-2165_firefox_network.png
> In Firefox, portal pages are loaded twice more, with errors
> ---
>
> Key: AIRAVATA-2165
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2165
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
> Attachments: AIRAVATA-2165_firefox_network.png
>
>
> In Firefox (doesn't seem to affect Safari or Chrome), every time a portal
> page loads, the page gets loaded again, twice.
> I tracked this down to this part of the web page
> {code:xml}
>
> src="">
> src="">
> {code}
> Apparently the empty {{src}} path is interpreted as meaning that the current
> URL should be loaded as a script.
> Since the web page is loaded into a
[jira] [Updated] (AIRAVATA-2165) In Firefox, portal pages are loaded twice more, with errors
[
https://issues.apache.org/jira/browse/AIRAVATA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2165:
--
Description:
In Firefox (doesn't seem to affect Safari or Chrome), every time a portal page
loads, the page gets loaded again, twice.
I tracked this down to this part of the web page
{code:xml}
{code}
Apparently the empty {{src}} path is interpreted as meaning that the current
URL should be loaded as a script.
Since the web page is loaded into a {{}} tag, the browser tries to
interpret it as JavaScript but fails, so I also see this in the console
{noformat}
09:04:27.443 SyntaxError: expected expression, got '<'1dashboard:1
09:04:27.891 SyntaxError: expected expression, got '<'1dashboard:1
{noformat}
For the most part this is harmless. But since it loads the whole page 3 times,
it takes about 3 times as long to load each page. Also, some of the JavaScript
only runs on the {{$(document).ready(..)}} event, and this code won't run until
the page is loaded 3 times, during which time interactive portions of the page
are unavailable.
I verified that this bug affects seagrid.org as well.
I'll post a screenshot of the network requests which will show the loading of
the page three times as well as the console errors.
!AIRAVATA\-2165_firefox_network.png|thumbnail!
was:
In Firefox (doesn't seem to affect Safari or Chrome), every time a portal page
loads, the page gets loaded again, twice.
I tracked this down to this part of the web page
{code:xml}