Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: processing directory is not configurable #926

Open
jraddaoui opened this issue Apr 19, 2024 · 1 comment
Open

Problem: processing directory is not configurable #926

jraddaoui opened this issue Apr 19, 2024 · 1 comment

Comments

@jraddaoui
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

The download activity places the package in the default temporary directory, as returned by os.TempDir, which reads:

TempDir returns the default directory to use for temporary files.

On Unix systems, it returns $TMPDIR if non-empty, else /tmp. On Windows, it uses GetTempPath, returning the first non-empty value from %TMP%, %TEMP%, %USERPROFILE%, or the Windows directory. On Plan 9, it returns /tmp.

The directory is neither guaranteed to exist nor have accessible permissions.

Additionally, we may want to set it to a different directory for performance reasons, like having a faster filesystem in another path or trying to avoid move operation between shared directories (a3m, preprocessing).

Describe the solution you'd like

I'd like a configuration option to set a processing directory, to be used by the download and other activities that may need it.

Describe alternatives you've considered

None.

Additional context

The initial preprocessing child workflow implementation uses the preprocessing shared path as destination for the downloaded package when preprocessing is enabled (#861).

@jraddaoui
Copy link
Collaborator Author

Kind of related: #864

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

No branches or pull requests

1 participant