Skip to content

Conversation

jchorl
Copy link

@jchorl jchorl commented Feb 12, 2025

I noticed that some script payloads can be large (MBs), especially when templating in thousands of input files.

Many firewalls are averse to large payloads, and in many cases, it just doesn't make sense to sling megabytes across a network.

I propose a config option to omit the whole script from payloads here.

Unfortunately, I hit some snags while testing. I tried in amazoncorretto docker images, 17, 19 and 21. None of them built out of the box using most up-to-date nextflow.

I ran once (per the readme):

    echo "includeBuild('../nextflow')" >> settings.gradle

And then:

make compile

After using java19 and updating gradle-wrapper.properties to match nextflow, I got the furthest but failed with:

bash-4.2# make compile
./gradlew :nextflow:exportClasspath compileGroovy
> Task :plugins:nf-weblog:compileGroovy FAILED

[Incubating] Problems report is available at: file:///home/j/third-party/nf-weblog/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':plugins:nf-weblog:compileGroovy'.
> Cannot infer Groovy class path because no Groovy Jar was found on class path: [/home/j/third-party/nextflow/modules/nextflow/build/libs/nextflow-24.12.0-edge-one.jar, /root/.gradle/caches/modules-2/files-2.1/org.pf4j/pf4j/3.4.1/6ba44242fa925f48af1784b3e57d9ab7fd186215/pf4j-3.4.1.jar, /root/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/1.7.25/da76ca59f6a57ee3102f8f9bd9cee742973efa8a/slf4j-api-1.7.25.jar, /root/.gradle/caches/modules-2/files-2.1/com.github.zafarkhaja/java-semver/0.9.0/59a83ca73c72a5e25b3f0b1bb305230a11000329/java-semver-0.9.0.jar, /home/j/third-party/nf-weblog/plugins/nf-weblog/build/classes/java/main]

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Anyway, if you point me in the right direction to get this built/tested, happy to do so. Im also happy to update the docs.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant