bunch of stuff broke in awslambda with 4.11.1 release
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by inspecting commit 8cd7a25e5d3c65aee7e3e12d7abf9465c4a0d3c8 and the AWS Lambda resource definitions it changed. The issue says MaximumConcurrency disappeared but promises more details later; establish which Lambda properties broke and identify their affected tests before proposing a fix. Done means the reported regressions are reproduced and the relevant tests pass.
Written by the indexing model from the issue text.
Description
I will update this issue later with more detail but stuff like MaximumConcurrency has disappeared:
https://github.com/cloudtools/troposphere/commit/8cd7a25e5d3c65aee7e3e12d7abf9465c4a0d3c8
- Dominant language
- Python
- Stars
- 4.9k
- Forks
- 1.4k
- Avg merge
- 10d 1h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudtools/troposphere
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
cloudtools/troposphere#2294 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cloudtools/troposphere#2205 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cloudtools/troposphere#2186 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cloudtools/troposphere#2152 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
cloudtools/troposphere#2148 ·
All issues in cloudtools/troposphere
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vllm-project/vllm#64845 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dekobon/big-code-analysis#1729 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pydantic/pydantic-ai#12091 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100