ango/django/pull/10733
>
>
>
> *From: *Lahiru Jayathilake
> *Reply-To: *"dev@airavata.apache.org"
> *Date: *Tuesday, May 14, 2019 at 12:18 PM
> *To: *"dev@airavata.apache.org"
> *Subject: *Re: Setup a development environment for Airavata
>
>
>
://github.com/django/django/pull/10733
From: Lahiru Jayathilake
Reply-To: "dev@airavata.apache.org"
Date: Tuesday, May 14, 2019 at 12:18 PM
To: "dev@airavata.apache.org"
Subject: Re: Setup a development environment for Airavata
Hi Marcus,
Yes "python3 manage.py
Hi Marcus,
Yes "*python3 manage.py migrate*" ran successfully with no errors.
Python version - 3.7.3
OS - macOS Mojave version 10.14.4
Regards,
Lahiru
On Tue, 14 May 2019 at 03:26, Christie, Marcus Aaron
wrote:
> Hi Lahiru,
>
> Did “python3 manage.py migrate” finish without errors?
>
> Also
Hello Marcus,
It got resolved after npm version update. It was 3.6.2 previously and got
updated to 6.9.0, everything works fine now.
Thanks,
Keerthi
On Fri, Mar 15, 2019 at 2:11 PM Christie, Marcus Aaron
wrote:
> Hi Keerthi,
>
> On Mar 15, 2019, at 11:16 AM, Keerthi N wrote:
>
> The Django
Hi Keerthi,
> On Mar 15, 2019, at 11:16 AM, Keerthi N wrote:
>
> The Django portal build is successful and has no errors, although it has
> couple of warnings (skipping failed optional dependency /chokidar/fsevents,
> not compatible with os:fsevents@1.2.7).
> There are no errors in the
e in the pull request and it might solve the issue.
>
> Thanks and Regards,
>
> Sai Rohith Achanta.
>
>
>
> *From: *DImuthu Upeksha
> *Reply-To: *"dev@airavata.apache.org"
> *Date: *Friday, March 15, 2019 at 12:17 PM
> *To: *Airavata Dev
> *Subject: *
Reply-To: "dev@airavata.apache.org"
Date: Friday, March 15, 2019 at 12:17 PM
To: Airavata Dev
Subject: Re: Setup a development environment for Airavata
Hi Keerthi,
For the database issue, we found the root cause. There was an issue in database
initialization script and we fixed it.
Hi Keerthi,
For the database issue, we found the root cause. There was an issue in
database initialization script and we fixed it. Rohith will soon send a PR
and once it is applied, you can start recreating containers. Before running
docker compose, please make sure to delete *database_data* (not
Hello Marcus,
The Django portal build is successful and has no errors, although it has
couple of warnings (skipping failed optional dependency /chokidar/fsevents,
not compatible with os:fsevents@1.2.7).
There are no errors in the Network tab, but the cosole has all alerts that
are appeared on
Hi Keerthi,
> On Mar 14, 2019, at 2:15 PM, Keerthi N wrote:
>
> Yes you are right, I remember that and tried multiple times from start to
> finish but no difference. Can there be any other issue?
Those errors in the Django portal looks like the Javascript code failed to
build. Did you get
Yes you are right, I remember that and tried multiple times from start to
finish but no difference. Can there be any other issue?
On Thu, Mar 14, 2019 at 1:10 PM DImuthu Upeksha
wrote:
> Hi Keerthi,
>
> I think this is related to the same issue that you have faced at the
> class. Some JPA
Hi Keerthi,
I think this is related to the same issue that you have faced at the class.
Some JPA entity classes were not optimized in the build time. Do not remove
anything from persistence.xml and that will cause issues. Try running mvn
clean install -DskipTests once for whole project.
Dimuthu
You might have some process running (local rabbitmq) acquiring port 5672
and 15672. Search for the process id by netstat -tulpn | grep 5672. First
you have to stop this process. Also make sure that all the ports mentioned
here [5] are free in your machine. If nothing works, try restarting your
Yes I have done that and executed docker system prune as well but the
error still persists.
On Thu, Mar 14, 2019 at 10:15 AM DImuthu Upeksha
wrote:
> Hi Keerthi,
>
> You have to cleanup old resources by running "docker-compose down" and
> "docker-compose rm". You might be running docker-compose
Hi Keerthi,
You have to cleanup old resources by running "docker-compose down" and
"docker-compose rm". You might be running docker-compose up more than once.
And make sure that, no related container is running in "docker ps" output.
Dimuthu
On Thu, Mar 14, 2019 at 9:59 AM Keerthi N wrote:
>
Hi Keerthi,
Build was fixed. You can try now after a git pull
Dimuthu
On Wed, Mar 13, 2019 at 5:20 PM Keerthi N wrote:
> Hi DImuthu,
>
> Yes that works for docker-compose up. But the mvn build failed after git
> pull at Airavata load testing client. The error says actual and formal
>
Hi Keerthi,
Can you try now?
Dimuthu
On Wed, Mar 13, 2019 at 12:50 PM Keerthi N wrote:
> Hello DImuthu,
>
> The "docker-compose up" step fails with pull access denied for
> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>
> Thanks,
> Keerthi
>
> On Wed, Mar 13, 2019 at
Hi Folks,
Since Airavata is a multi server platform with lots of components and
configurations, it is quite challenging for a new developer to get started
with the code base and setup a running Airavata deployment locally. To
address that, we came up with a standalone deployment guide [1] which
18 matches
Mail list logo
