MassBank / MassBank-data

Official repository of open data MassBank records
77 stars 60 forks source link

MassBank record validator takes ages to build #134

Closed MaliRemorker closed 4 years ago

MaliRemorker commented 4 years ago

We are trying to install the validator according to the README instructions. The maven build proces,

mvn -q -f .scripts/MassBank-web/MassBank-Project/MassBank-lib/pom.xml install

takes very long time to complete. After rerunning it without the --quiet option, we noticed that the build waits for ages whenever it tries to download a POM file from a link starting with https://gose.fiehnlab.ucdavis.edu. Just to experiment, I tried downloading one of the POMs from that URL using plain wget, including and excluding the certificate checking, trying separately ipv4 and ipv6 and that route also took ages to complete, independent of the settings.

I realise this is a network issue, but is there a way to get the full source tree and thus avoid maven downloading the dependencies from the net?

@schymane and @anjuraj15 just for your notice.

meier-rene commented 4 years ago

I'm very sorry, but I don't know what to do against it. Its taking a while here two, but after 2 min it should be done.

MaliRemorker commented 4 years ago

We are still debugging this our side. @meier-rene @schymane @anjuraj15 , I tried building on my home linux box, with the system almost identical to the one in the institute and it worked like a charm. Same build time like Rene reported. The obvious difference is the IP address I ran the process from.

Yesterday, I used this same laptop from the institute and it suffered the same problems like our institute's machine.

@meier-rene given that it is likely that the problems arise our side of the equation, we could close this issue. But, it could also be that the solution may help the future masses of MassBank users.

MaliRemorker commented 4 years ago

After consulting the Uni Luxembourg IT team, we realised that all outgoing traffic, except the standard HTTP(S) ports are blocked for us by default.

However, some of the maven build dependencies are accessed on the port 55000. For example, http://gose.fiehnlab.ucdavis.edu:55000/content/groups/public/edu/ucdavis/fiehnlab/splash/core/1.8/core-1.8.pom

I guess that we are not the only university in the world blocking outgoing ports by default, so maybe it is good to know this.