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

[Bug]: Can't deploy a Python Poetry app containing a .tool-versions file. (Probably upstream bug) #4567

Open
Nevsor opened this issue Dec 13, 2024 · 2 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@Nevsor
Copy link

Nevsor commented Dec 13, 2024

Error Message and Logs

When trying to deploy a Python Poetry app, where I set the poetry version in .tool-versions, nixpacks outputs a line Using poetry version from .tool-versions: 1.8.5 before the toml file, which makes the toml parser trying to parse the build plan quit with an error message:

Error message

Here is the output of nixpacks plan:

Image

Here is the code line that errors:

$parsed = Toml::Parse($this->nixpacks_plan);

Coolify Version

v4.0.0-beta.377

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

Assuming this is an unintended behaviour of nixpacks, Coolify just needs to wait for my PR to land into a nixpacks release and use that version instead.

If the output turns out to be intended, Coolify needs to somehow check for the existence of other output lines before the toml file and skip those.

@Nevsor Nevsor added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 13, 2024
@Nevsor
Copy link
Author

Nevsor commented Dec 29, 2024

This will be fixed by this nixpacks PR: railwayapp/nixpacks#1249

@CoderJoshDK
Copy link

The above PR (and the original linked upstream PR from Nevsor) are merged in. Now you will need to wait for the next patch release, and this problem should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants