Skip to content

apply fix for podman container labels dict #12526

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

Merged
merged 3 commits into from
Apr 18, 2025
Merged

Conversation

TheWolfNL
Copy link
Contributor

Motivation

The existing PR seems to be waiting on a small change, so to speed up the process I made the change here.

Related Bug report

Changes

When invoking _transform_container_labels, I added a check to veryify is the supplied parameter is already a Dict, which is the default in Podman. if so return the Dict, otherwise split the string and transform it into a Dict as usual.

semver: patch

@localstack-bot
Copy link
Collaborator

localstack-bot commented Apr 15, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

Copy link
Collaborator

@localstack-bot localstack-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to LocalStack! Thanks for raising your first Pull Request and landing in your contributions. Our team will reach out with any reviews or feedbacks that we have shortly. We recommend joining our Slack Community and share your PR on the #community channel to share your contributions with us. Please make sure you are following our contributing guidelines and our Code of Conduct.

@TheWolfNL
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

Copy link
Member

@dfangl dfangl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @TheWolfNL for taking this over! Sadly your PR also has a linting error, could you fix those issues (using make format, for example) to get the CI to pass?

@TheWolfNL TheWolfNL requested a review from dfangl April 15, 2025 20:28
@TheWolfNL
Copy link
Contributor Author

Thanks @TheWolfNL for taking this over! Sadly your PR also has a linting error, could you fix those issues (using make format, for example) to get the CI to pass?

Should be fixed now 👍🏻

@dfangl dfangl added the semver: patch Non-breaking changes which can be included in patch releases label Apr 17, 2025
Copy link
Member

@dfangl dfangl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more change to make it python 3.9 compatible, I just discovered it by running more workflows.
Another thing: You have been committing with an email address linked to one github account, but created the PR and signed the CLA with the other. This leads to the CLA bot to complain, currently. Could you either sign the CLA with the other account as well (just comment here), or change the email in the commits to another one connected to the other account, and force push from the @TheWolfNL account? This would make the PR fully green :)

@playground-tjeerd
Copy link
Contributor

I have read the CLA Document and I hereby sign the CLA

@TheWolfNL TheWolfNL requested a review from dfangl April 17, 2025 21:11
Copy link
Member

@dfangl dfangl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything is green, thanks for your PR!

@dfangl dfangl merged commit 5e8dc09 into localstack:master Apr 18, 2025
29 checks passed
@TheWolfNL
Copy link
Contributor Author

@dfangl do you happen to know when a new release is planned? I could not find any info regarding a release schedule of sorts.

@dfangl
Copy link
Member

dfangl commented May 7, 2025

Hi @TheWolfNL
The next release is planned the 8th of May.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver: patch Non-breaking changes which can be included in patch releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants