Skip to content

feature: Unable to infer lockfile of inline scripts from requirements.txt #5846

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

Open
st1020 opened this issue May 31, 2025 · 2 comments
Open
Assignees

Comments

@st1020
Copy link

st1020 commented May 31, 2025

As the documentation states: "When doing wmill script generate-metadata, if a requirements.txt is discovered, the closest one will be used as source-of-truth instead of being discovered from the imports in the script directly to generate the lockfile from the server."

But, when doing wmill flow generate-locks, the lockfiles of inline script always inferred from imports. And I didn't find a way to infer lockfile of inline scripts from requirements.txt.

I think we should make wmill flow generate-locks have the same behavior as wmill script generate-metadata in lockfile inference. Or at least should provide a way to infer lockfile of inline scripts from requirements.txt.

Thanks.

@rubenfiszel
Copy link
Contributor

Noted, it's part of our backlog as we put a strong focus on local development this quarter and the next

@st1020
Copy link
Author

st1020 commented Jun 1, 2025

Ok, can I overwrite lockfile directly as a temporary solution?

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

2 participants