Skip to content

--tmp-outdir-prefix /calrissian/tmp and /calrissian/tmp/ behave differently #171

@fabricebrito

Description

@fabricebrito

A trailing slash in the value of the --tmp-outdir-prefix CLI option provide different output results

image: ghcr.io/duke-gcb/calrissian/calrissian:0.16.0
          command: ["calrissian"]
          args:
            - --stdout 
            - /calrissian/results.json
            - --stderr 
            - /calrissian/app.log
            - --max-ram 
            - 4G
            - --max-cores 
            - "8"
            - --tmp-outdir-prefix 
            - /calrissian/tmp 
            - --outdir
            - /calrissian/results
            - --usage-report 
            - /calrissian/usage.json
            - --tool-logs-basepath 
            - /calrissian/logs
            - /app-package/app-package.cwl
            - /inputs/params.yaml

Without the trailing slash:

 "stac_catalog": {
        "location": "file:///calrissian/results/tmpblxy91p7",

With the trailing slash:

{
    "stac_catalog": {
        "location": "file:///calrissian/results/lvm_l4cj",

Using --tmp-outdir-prefix /calrissian/tmp-aaa we get:

{
    "stac_catalog": {
        "location": "file:///calrissian/results/tmp-aaabxuod1w_",

A trailing slash should not change the url "pattern" of a parameter taking a directory

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions