[
https://issues.apache.org/jira/browse/AIRAVATA-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493569#comment-17493569
]
ASF subversion and git services commented on AIRAVATA-3557:
-----------------------------------------------------------
Commit b40a7419975dfe6b32f282b9e3e7e17f5b6d21e6 in airavata-django-portal's
branch refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=b40a741 ]
AIRAVATA-3557 Only allow fetching outputs if job ACTIVE
> Update Experiment Summary to display intermediate output files
> --------------------------------------------------------------
>
> Key: AIRAVATA-3557
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3557
> Project: Airavata
> Issue Type: Sub-task
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> From mailing list discussion:
> {quote}As for UI, you're right. Currently the output file UI only displays
> when an experiment is COMPLETED. I'm thinking of having a panel for each
> output file that will display once the experiment is EXECUTING. Each panel
> will have a button to fetch the current file. When the fetch is executing the
> button is disabled and a spinner displays with a message that the file is
> being fetched. Once the file is fetched, if it is a text file (and maybe
> within some max file size limit) then it will display in the panel and the
> user can scroll through the file. This is the main use case, retrieving the
> current value of a log file or STDOUT or something similar. If the file is
> too large or binary then instead of displaying the file directly there will
> be a download button. That's the general idea.{quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)