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

Conda lock file may not be rendered correctly #721

Open
pditommaso opened this issue Oct 27, 2024 · 3 comments · May be fixed by #727
Open

Conda lock file may not be rendered correctly #721

pditommaso opened this issue Oct 27, 2024 · 3 comments · May be fixed by #727
Assignees

Comments

@pditommaso
Copy link
Collaborator

pditommaso commented Oct 27, 2024

The Conda lock file may not be collected correctly in some cases.

In the following example the following content is reported as Conda lock file

"     && cat environment.lock     && echo "

https://wave.seqera.io/view/builds/bd-1fc239026070d9d3_2

@munishchouhan
Copy link
Member

I will look into it

@munishchouhan munishchouhan self-assigned this Oct 28, 2024
@munishchouhan
Copy link
Member

weird working in local:
Screenshot 2024-10-28 at 15 25 09

@munishchouhan
Copy link
Member

ok i found the issue

the current approach has a bug
where if the image is cached, then the docker image won't run and therefore no condalock file in the logs
like in this case, first run has condafile

https://wave.seqera.io/view/builds/bd-1fc239026070d9d3_1

I will work on the fix

@munishchouhan munishchouhan linked a pull request Oct 29, 2024 that will close this issue
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 a pull request may close this issue.

2 participants