[GitHub] [airavata-mft-portal] dependabot[bot] opened a new pull request, #32: Bump json5 and @vue/cli-service in /airavata_mft/static/common

[GitBox]

dependabot[bot] opened a new pull request, #32:
URL: https://github.com/apache/airavata-mft-portal/pull/32

   Bumps [json5](https://github.com/json5/json5) to 2.2.3 and updates ancestor 
dependencies [json5](https://github.com/json5/json5), 
[json5](https://github.com/json5/json5) and 
[@vue/cli-service](https://github.com/vuejs/vue-cli/tree/HEAD/packages/@vue/cli-service).
 These dependencies need to be updated together.
   
   Updates `json5` from 2.1.3 to 2.2.3
   
   Release notes
   Sourced from https://github.com/json5/json5/releases;>json5's releases.
   
   v2.2.3
   
   Fix: json5@2.2.3 is now the 'latest' release according to npm instead of 
v1.0.2. (https://github-redirect.dependabot.com/json5/json5/issues/299;>#299)
   
   v2.2.2
   
   Fix: Properties with the name __proto__ are added to 
objects and arrays.
   (https://github-redirect.dependabot.com/json5/json5/issues/199;>#199) 
This also fixes a prototype pollution vulnerability reported by
   Jonathan Gregson! (https://github-redirect.dependabot.com/json5/json5/issues/295;>#295).
   
   v2.2.1
   
   Fix: Removed dependence on minimist to patch CVE-2021-44906. (https://github-redirect.dependabot.com/json5/json5/issues/266;>#266)
   
   v2.2.0
   
   New: Accurate and documented TypeScript declarations are now included. 
There is no need to install @types/json5. (https://github-redirect.dependabot.com/json5/json5/issues/236;>#236, 
https://github-redirect.dependabot.com/json5/json5/issues/244;>#244)
   
   
   
   
   Changelog
   Sourced from https://github.com/json5/json5/blob/main/CHANGELOG.md;>json5's 
changelog.
   
   v2.2.3 [https://github.com/json5/json5/tree/v2.2.3;>code, 
https://github.com/json5/json5/compare/v2.2.2...v2.2.3;>diff]
   
   Fix: json5@2.2.3 is now the 'latest' release according to npm instead of
   v1.0.2. (https://github-redirect.dependabot.com/json5/json5/issues/299;>#299)
   
   v2.2.2 [https://github.com/json5/json5/tree/v2.2.2;>code, 
https://github.com/json5/json5/compare/v2.2.1...v2.2.2;>diff]
   
   Fix: Properties with the name __proto__ are added to 
objects and arrays.
   (https://github-redirect.dependabot.com/json5/json5/issues/199;>#199) 
This also fixes a prototype pollution vulnerability reported by
   Jonathan Gregson! (https://github-redirect.dependabot.com/json5/json5/issues/295;>#295).
   
   v2.2.1 [https://github.com/json5/json5/tree/v2.2.1;>code, 
https://github.com/json5/json5/compare/v2.2.0...v2.2.1;>diff]
   
   Fix: Removed dependence on minimist to patch CVE-2021-44906. (https://github-redirect.dependabot.com/json5/json5/issues/266;>#266)
   
   v2.2.0 [https://github.com/json5/json5/tree/v2.2.0;>code, 
https://github.com/json5/json5/compare/v2.1.3...v2.2.0;>diff]
   
   New: Accurate and documented TypeScript declarations are now included. 
There
   is no need to install @types/json5. (https://github-redirect.dependabot.com/json5/json5/issues/236;>#236, 
https://github-redirect.dependabot.com/json5/json5/issues/244;>#244)
   
   
   
   
   Commits
   
   https://github.com/json5/json5/commit/c3a75242772a5026a49c4017a16d9b3543b62776;>c3a7524
 2.2.3
   https://github.com/json5/json5/commit/94fd06d82eeed225fa172f6fb2ca27375cbd2e39;>94fd06d
 docs: update CHANGELOG for v2.2.3
   https://github.com/json5/json5/commit/3b8cebf0c474a8b20c78bd75c89cca0c4dce84ce;>3b8cebf
 docs(security): use GitHub security advisories
   https://github.com/json5/json5/commit/f0fd9e194dde282caff114a110f4fac635f3a62c;>f0fd9e1
 docs: publish a security policy
   https://github.com/json5/json5/commit/6a91a05fffeda16ff6b3b5008b6b340d42d31ec0;>6a91a05
 docs(template): bug - bug report
   https://github.com/json5/json5/commit/14f8cb186e8abdfaccf6527171da7b1224374650;>14f8cb1
 2.2.2
   https://github.com/json5/json5/commit/10cc7ca9169b59c5e0f5afc03dbd870cd06bcc46;>10cc7ca
 docs: update CHANGELOG for v2.2.2
   https://github.com/json5/json5/commit/7774c1097993bc3ce9f0ac4b722a32bf7d6871c8;>7774c10
 fix: add proto to objects and arrays
   https://github.com/json5/json5/commit/edde30abd8b22facf2c06c72586b9f6edf12700d;>edde30a
 Readme: slight tweak to intro
   https://github.com/json5/json5/commit/97286f8bd542c89dcee096bc05dd28ed2dfc1e16;>97286f8
 Improve example in readme
   Additional commits viewable in https://github.com/json5/json5/compare/v2.1.3...v2.2.3;>compare 
view
   
   
   
   
   Updates `json5` from 1.0.1 to 2.2.3
   
   Release notes
   Sourced from https://github.com/json5/json5/releases;>json5's releases.
   
   v2.2.3
   
   Fix: json5@2.2.3 is now the 'latest' release according to npm instead of 
v1.0.2. (https://github-redirect.dependabot.com/json5/json5/issues/299;>#299)
   
   v2.2.2
   
   Fix: Properties with the name __proto__ are added to 
objects and arrays.
   (https://github-redirect.dependabot.com/json5/json5/issues/199;>#199) 
This also fixes a prototype pollution vulnerability reported by
   Jonathan Gregson! (https://github-redirect.dependabot.com/json5/json5/issues/295;>#295).
   
   

Re: Regarding Pre and Post job commands in Airavata

[Suresh Marru]

Hi All,

We need to fork this discussion into three threads:

1. Implicit Workflow: The pre, post, and job submitter commands at the 
conceptual level are all within one process and within a task of that process. 
In this approach, we do not have granular monitoring and fault tolerance or 
reaction to the success/failure of these individual steps (for instance, of the 
pre-job fails, the job script is still executed). 

2. Explicit and dependent Workflow: All pre, post, and job steps can be made 
into separate tasks within a single process. In this approach, we can react to 
and control the flow between these steps based on the execution status. 

3. Classic Workflows: In these, we create individual processes which have 
subtasks and are treated at a higher level, like workflow engines or 
orchestrators. 

Hi Dinuka, 

I'd like to point out that the response to your question depends on how you are 
looking at it. For instance, the SLURM implements category 1 (above) in a 
single execution file. You can implement HTC pre and post-job scenarios using 
HTConfor DAG without any changes to the framework by making them individual 
tasks within HTCondor. Still, for Airavata, they will be one task. The obvious 
downside is you will loose granular monitoring and reaction to failures of 
individual steps. If you approach it as category 2 or 3, that will lead to a 
broader discussion and changes to the framework.

Suresh

> On Jan 5, 2023, at 10:28 AM, Pamidighantam, Sudhakar V 
>  wrote:
> 
> Dimuthu:
>  
> For gateway with specific applications the application or executable needs to 
> be transferred along with the user inputs to the condor pool, which may 
> require unpacking a tar ball or other mechanisms and identify the actual 
> executable by a driver script. The driver script is the current executable 
> application in the gateway but the actual executable or a container (the 
> tarball above) also need to transferred before the execution can be set up. 
> These steps require a pre job script or a way to add additional 
> transfer_input_files instructions at the connecting HT condor host.
>  
> Of course dags are quite diverse and can be used for various other usecases 
> such as parameter sweeps with different inputs (which again could be packaged 
> in tarballs and need extraction after staging) etc..
>  
> Thanks,
> Sudhakar. 
>  
> From: DImuthu Upeksha 
> Reply-To: "dev@airavata.apache.org" 
> Date: Thursday, January 5, 2023 at 10:14 AM
> To: "dev@airavata.apache.org" 
> Subject: Re: Regarding Pre and Post job commands in Airavata
>  
> Hi Dinuka,
>  
> Sorry for the late reply. It is great to explore options to integrate Dag 
> capabilities into the job submitter. We already have some form of HTCondor 
> support in Airavata. Can you summarize the difference between what we already 
> have for HTCondor and this Dag feature? I am specifically looking for 
> practical usages instead of technical differences.
>  
> Thanks
> Dimuthu 
>  
> On Sun, Jan 1, 2023 at 10:35 AM Dinuka De Silva  > wrote:
>> Hi,
>>  
>> The current implementation of mapping these (Pre, Post, etc. job commands) 
>> to the job scheduler script has assumed the job scheduler script to be a 
>> type of shell script. So, the order of the execution is based on the order 
>> of the commands listed in the script which is as below.
>>  
>> - Module Commands
>> - Pre Job Commands
>> - Job Submitter Command
>> - Post Job Commands
>>  
>> The scheduler script of SLURM, FORK, LSF, UGE, and PBS are shell scripts 
>> while HTCondor and maybe some other job schedulers have different file 
>> types. The script grammar in HTCondor does not support appending shell 
>> scripts inside. Now, we are needing to support Pre, Post, and other commands 
>> for HTCondor realizing the current design doesn't support it. 
>>  
>> In HTCondor there's an option [1] to configure pre and post-scripts to be 
>> executed at the worker instance. But then the script has to be Dag and the 
>> pre-script, post-script and job-script are to be separate files. So, I tried 
>> a sample and planning to put this to airavata.
>>  
>> [1] 
>> https://htcondor.readthedocs.io/en/latest/users-manual/dagman-workflows.html 
>> 
>>  
>> Thanks & Regards,
>> Dinuka

Re: Airavata MetaSchedular

[Eroma Abeysinghe]

Hi Emre,

Happy New Year !!!
We are carrying out our planning activities, so let me check our
schedules and send you a time.

Thanks,
Eroma

On Thu, Jan 5, 2023 at 10:58 AM Emre Brookes 
wrote:

> Hi Eroma,
>
> Hope you had good holidays and Happy 2023!
>
> When can we schedule our first meeting?
>
> Thanks,
> Emre
>
>
> Eroma Abeysinghe wrote:
> > Hi Emre,
> >
> > Yes, We'll meet with you in January to discuss the implementation and
> > testing with UltraScan.
> > Currently, the initial testing is being planned for the implementation.
> >
> > Thanks,
> > Eroma
> >
> >
> >
> > On Thu, Dec 8, 2022 at 9:07 AM Emre Brookes  > > wrote:
> >
> > Hi Isuru,
> >
> > Thanks for the updates. Great to see progress is being made.
> > I plan to dive into the UltraScan side of this starting in January,
> > perhaps we can setup a meeting early January to see what is
> > implemented,
> > how the new UltraScan microservice can be integrated & begin
> > planning/running some tests?
> >
> > Best wishes,
> > Emre
> >
> >
> > Isuru Ranawaka wrote:
> > > *EXTERNAL EMAIL*
> > >
> > > Hi all,
> > >
> > > We have implemented the initial phase of the Airavata
> > Metascheduler.
> > > Following is the finalized architecture at this phase.
> > >
> > > image.png
> > > Airavata Experiments can be configured for auto-scheduling and for
> > > such Experiments Orchestrator invokes meta scheduler to check
> > whether
> > > the Experiment is schedulable. If it is schedulable Orchestrator
> > > submits the respective Process of the Experiment to Helix Framework
> > > for instant scheduling otherwise Experiment and Process are Queued.
> > >
> > >
> > > *Metascheduler Architecture*
> > >
> > > image.png
> > >
> > > Process scanner scans for already queued
> > Processes
> > > periodically and sends those Process information to the
> > MetaScheduler
> > > Engine. Metascheduler Engine evaluates the chance of successful
> > > submission based on configured scheduling policies. If it is
> > > submittable MetaScheduler engine invokes Orchestrator APIs to
> > initiate
> > > the Job Submission for those Processes through Helix Framework.
> > >
> > >   * Compute Resource Monitoring Service
> > >
> > > Compute resource monitoring service uses Airavata Group Resource
> > > Profile information to periodically monitor configured Remote
> > Compute
> > > Resources and update the status of the Queues in the registry. So
> > > the information is consumed by Metacheduler Engine to schedule or
> > > reschedule Processes.
> > >
> > >
> > >
> > > thanks
> > > Isuru
> > >
> > >
> > >
> > >
> > > On Tue, Oct 4, 2022 at 7:41 AM Isuru Ranawaka
> > mailto:irjan...@gmail.com>
> > > >> wrote:
> > >
> > > Hi all,
> > >
> > > Airavata MetaSchedular is a managed job submission framework
> for
> > > High-Performance Computing resources. Basically, It handles
> > >
> > >  *
> > >
> > > User-based load balancing of Jobs between resource queues.
> > >
> > >  *
> > >
> > > Dynamic Job scheduling across compute resources
> > >
> > >  *
> > >
> > > Job queueing and managed submissions
> > >
> > > and the following document [1] contains the captured use cases.
> > > Please have a look and make suggestions, comments are highly
> > > appreciated.
> > >  I will update the thread as I proceed with the implementation.
> > >
> > > thanks
> > > Isuru
> > >
> > >
> > >
> > >
> >  [1]
> https://docs.google.com/document/d/1i_cAR7ulNpkEATt0VW4-xoYZyZTQbdnNAJVbnAlMI4I/edit?usp=sharing
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1i_cAR7ulNpkEATt0VW4-xoYZyZTQbdnNAJVbnAlMI4I%2Fedit%3Fusp%3Dsharing=05%7C01%7Cemre.brookes%40mso.umt.edu%7Cbe901cb022944847525b08dad9273cd3%7C68407ce503da49ffaf0a724be0d37c9d%7C0%7C0%7C638061059806579260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=nS4gzBpdmOWF04SLIpJeCwZEAjDsEPipQzUsaVz7L30%3D=0
> >
> > >
> >  <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1i_cAR7ulNpkEATt0VW4-xoYZyZTQbdnNAJVbnAlMI4I%2Fedit%3Fusp%3Dsharing=05%7C01%7Cemre.brookes%40mso.umt.edu%7Cef364bd1eacf40f9084708dad7c05f78%7C68407ce503da49ffaf0a724be0d37c9d%7C0%7C0%7C638059518517375866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=TakGZiJUBDCypMJMjsD0yNrjayREybgM8JBtQVu9hJM%3D=0
> > <
> 

Re: Airavata MetaSchedular

[Emre Brookes]

Hi Eroma,

Hope you had good holidays and Happy 2023!

When can we schedule our first meeting?

Thanks,
Emre


Eroma Abeysinghe wrote:

Hi Emre,

Yes, We'll meet with you in January to discuss the implementation and 
testing with UltraScan.

Currently, the initial testing is being planned for the implementation.

Thanks,
Eroma



On Thu, Dec 8, 2022 at 9:07 AM Emre Brookes > wrote:


Hi Isuru,

Thanks for the updates. Great to see progress is being made.
I plan to dive into the UltraScan side of this starting in January,
perhaps we can setup a meeting early January to see what is
implemented,
how the new UltraScan microservice can be integrated & begin
planning/running some tests?

Best wishes,
Emre


Isuru Ranawaka wrote:
> *EXTERNAL EMAIL*
>
> Hi all,
>
> We have implemented the initial phase of the Airavata
Metascheduler.
> Following is the finalized architecture at this phase.
>
> image.png
> Airavata Experiments can be configured for auto-scheduling and for
> such Experiments Orchestrator invokes meta scheduler to check
whether
> the Experiment is schedulable. If it is schedulable Orchestrator
> submits the respective Process of the Experiment to Helix Framework
> for instant scheduling otherwise Experiment and Process are Queued.
>
>
> *Metascheduler Architecture*
>
> image.png
>
>                     Process scanner scans for already queued
Processes
> periodically and sends those Process information to the
MetaScheduler
> Engine. Metascheduler Engine evaluates the chance of successful
> submission based on configured scheduling policies. If it is
> submittable MetaScheduler engine invokes Orchestrator APIs to
initiate
> the Job Submission for those Processes through Helix Framework.
>
>   * Compute Resource Monitoring Service
>
> Compute resource monitoring service uses Airavata Group Resource
> Profile information to periodically monitor configured Remote
Compute
> Resources and update the status of the Queues in the registry. So
> the information is consumed by Metacheduler Engine to schedule or
> reschedule Processes.
>
>
>
> thanks
> Isuru
>
>
>
>
> On Tue, Oct 4, 2022 at 7:41 AM Isuru Ranawaka
mailto:irjan...@gmail.com>
> >> wrote:
>
>     Hi all,
>
>     Airavata MetaSchedular is a managed job submission framework for
>     High-Performance Computing resources. Basically, It handles
>
>      *
>
>         User-based load balancing of Jobs between resource queues.
>
>      *
>
>         Dynamic Job scheduling across compute resources
>
>      *
>
>         Job queueing and managed submissions
>
>     and the following document [1] contains the captured use cases.
>     Please have a look and make suggestions, comments are highly
>     appreciated.
>      I will update the thread as I proceed with the implementation.
>
>     thanks
>     Isuru
>
>
>
>   
 
[1]https://docs.google.com/document/d/1i_cAR7ulNpkEATt0VW4-xoYZyZTQbdnNAJVbnAlMI4I/edit?usp=sharing


>   
 
>
>
>
>     --
>     Research Software Engineer
>     Indiana University, IN
>
>
>
> --
> Research Software Engineer
> Indiana University, IN
>
>
> CAUTION: This 

Re: Regarding Pre and Post job commands in Airavata

[Pamidighantam, Sudhakar V]

Dimuthu:

For gateway with specific applications the application or executable needs to 
be transferred along with the user inputs to the condor pool, which may require 
unpacking a tar ball or other mechanisms and identify the actual executable by 
a driver script. The driver script is the current executable application in the 
gateway but the actual executable or a container (the tarball above) also need 
to transferred before the execution can be set up. These steps require a pre 
job script or a way to add additional transfer_input_files instructions at the 
connecting HT condor host.

Of course dags are quite diverse and can be used for various other usecases 
such as parameter sweeps with different inputs (which again could be packaged 
in tarballs and need extraction after staging) etc..

Thanks,
Sudhakar.

From: DImuthu Upeksha 
Reply-To: "dev@airavata.apache.org" 
Date: Thursday, January 5, 2023 at 10:14 AM
To: "dev@airavata.apache.org" 
Subject: Re: Regarding Pre and Post job commands in Airavata

Hi Dinuka,

Sorry for the late reply. It is great to explore options to integrate Dag 
capabilities into the job submitter. We already have some form of HTCondor 
support in Airavata. Can you summarize the difference between what we already 
have for HTCondor and this Dag feature? I am specifically looking for practical 
usages instead of technical differences.

Thanks
Dimuthu

On Sun, Jan 1, 2023 at 10:35 AM Dinuka De Silva 
mailto:l.dinukadesi...@gmail.com>> wrote:
Hi,

The current implementation of mapping these (Pre, Post, etc. job commands) to 
the job scheduler script has assumed the job scheduler script to be a type of 
shell script. So, the order of the execution is based on the order of the 
commands listed in the script which is as below.

- Module Commands
- Pre Job Commands
- Job Submitter Command
- Post Job Commands

The scheduler script of SLURM, FORK, LSF, UGE, and PBS are shell scripts while 
HTCondor and maybe some other job schedulers have different file types. The 
script grammar in HTCondor does not support appending shell scripts inside. 
Now, we are needing to support Pre, Post, and other commands for HTCondor 
realizing the current design doesn't support it.

In HTCondor there's an option [1] to configure pre and post-scripts to be 
executed at the worker instance. But then the script has to be Dag and the 
pre-script, post-script and job-script are to be separate files. So, I tried a 
sample and planning to put this to airavata.

[1] 
https://htcondor.readthedocs.io/en/latest/users-manual/dagman-workflows.html

Thanks & Regards,
Dinuka

Re: Regarding Pre and Post job commands in Airavata

[DImuthu Upeksha]

Hi Dinuka,

Sorry for the late reply. It is great to explore options to integrate Dag
capabilities into the job submitter. We already have some form of HTCondor
support in Airavata. Can you summarize the difference between what we
already have for HTCondor and this Dag feature? I am specifically looking
for practical usages instead of technical differences.

Thanks
Dimuthu

On Sun, Jan 1, 2023 at 10:35 AM Dinuka De Silva 
wrote:

> Hi,
>
> The current implementation of mapping these (Pre, Post, etc. job commands)
> to the job scheduler script has assumed the job scheduler script to be a
> type of shell script. So, the order of the execution is based on the order
> of the commands listed in the script which is as below.
>
> - Module Commands
> - Pre Job Commands
> - Job Submitter Command
> - Post Job Commands
>
> The scheduler script of SLURM, FORK, LSF, UGE, and PBS are shell scripts
> while HTCondor and maybe some other job schedulers have different file
> types. The script grammar in HTCondor does not support appending
> shell scripts inside. Now, we are needing to support Pre, Post, and other
> commands for HTCondor realizing the current design doesn't support it.
>
> In HTCondor there's an option [1] to configure pre and post-scripts to be
> executed at the worker instance. But then the script has to be Dag and the
> pre-script, post-script and job-script are to be separate files. So, I
> tried a sample and planning to put this to airavata.
>
> [1]
> https://htcondor.readthedocs.io/en/latest/users-manual/dagman-workflows.html
>
> Thanks & Regards,
> Dinuka
>
>
>

Re: How to setup the latest pga portal

[Suresh Marru]

Hi Dinuka,

These libraries are already within Airavata repo, so do not commit them, but 
rather fix the ide-integration to copy them into the right place on-demand. See:

https://github.com/apache/airavata-php-gateway/tree/master/app/libraries 
 

 
https://github.com/apache/airavata/tree/master/airavata-api/airavata-client-sdks/airavata-php-sdk/src/main/resources/lib
 


The first link is indeed copied from generated thrift libraries from Airavata, 
so copying them back will make it redundant. 

Suresh

> On Jan 5, 2023, at 8:00 AM, Dinuka De Silva  wrote:
> 
> Hi,
> 
> I found one workaround. 
> 
> Instead of copying everything from airavata-php-gateway, I copied only 
> "airavata-php-gateway/app/libraries/Airavata" to 
> "airavata/modules/ide-integration/src/main/containers/pga/airavata-php-gateway/app/libraries"
>  and then it works even though I'm not certain of the exact issue.
> 
> However, now I could get the latest pga code to work within airavata 
> repository, should I commit this code? I assume it's not meant to commit but 
> if I do whoever wants to set up this wouldn't have to go through what I did.
> 
> Thanks & Regards,
> Dinuka
> 
> On Wed, Jan 4, 2023 at 10:59 PM Dinuka De Silva  > wrote:
> Hi,
> 
> I'm trying to set up the latest code from airavata-php-portal [1] on my local 
> machine. I need that for creating and testing some HTCondor compute 
> resources. Here's how I tried.
> 
> I copied the latest source from airavata-php-portal to 
> "airavata/modules/ide-integration/src/main/containers/pga" path in the 
> airavata repository and ran "docker compose up" on the same directory. And I 
> end up with the following errors on the command line.
> 
> (base) dinukadesilva@Dinukas-MacBook-Pro pga % docker compose up
> [+] Running 1/0
>  ⠿ Container pga-pga-1  Created   
>   
>0.0s
> Attaching to pga-pga-1
> pga-pga-1  | 
> pga-pga-1  |   
>   
> pga-pga-1  |   [UnexpectedValueException]  
> 
> pga-pga-1 exited with code 1
> (base) dinukadesilva@Dinukas-MacBook-Pro pga % 
> 
> 
> But, if I do the same steps without copying the latest airavata-php-portal, 
> it works fine, and pga portal up and runs perfectly. 
> 
> Thanks & Regards,
> Dinuka
> 
> [1] https://github.com/apache/airavata-php-gateway 
> 

Re: How to setup the latest pga portal

[Dinuka De Silva]

Hi,

I found one workaround.

Instead of copying everything from airavata-php-gateway, I copied only
*"airavata-php-gateway/app/libraries/Airavata"* to
*"airavata/modules/ide-integration/src/main/containers/pga/airavata-php-gateway/app/libraries"
*and then it works even though I'm not certain of the exact issue.

However, now I could get the latest pga code to work within airavata
repository, should I commit this code? I assume it's not meant to commit
but if I do whoever wants to set up this wouldn't have to go through what I
did.

Thanks & Regards,
Dinuka

On Wed, Jan 4, 2023 at 10:59 PM Dinuka De Silva 
wrote:

> Hi,
>
> I'm trying to set up the latest code from airavata-php-portal [1] on my
> local machine. I need that for creating and testing some HTCondor compute
> resources. Here's how I tried.
>
> I copied the latest source from airavata-php-portal to
> "airavata/modules/ide-integration/src/main/containers/pga" path in the
> airavata repository and ran "docker compose up" on the same directory. And
> I end up with the following errors on the command line.
>
>
>
>
>
>
> *(base) dinukadesilva@Dinukas-MacBook-Pro pga % docker compose up[+]
> Running 1/0 ⠿ Container pga-pga-1  Created
>
>0.0sAttaching to pga-pga-1pga-pga-1  | pga-pga-1
>  |   *
>
> *pga-pga-1  |   [UnexpectedValueException]  *
>
>
> *pga-pga-1 exited with code 1(base) dinukadesilva@Dinukas-MacBook-Pro pga
> % *
>
>
> But, if I do the same steps without copying the
> latest airavata-php-portal, it works fine, and pga portal up and runs
> perfectly.
>
> Thanks & Regards,
> Dinuka
>
> [1] https://github.com/apache/airavata-php-gateway
>