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

Fix CloudFront client API unused variable #3179

Closed
1 task
bkuhlmann opened this issue Feb 1, 2025 · 2 comments · Fixed by #3181
Closed
1 task

Fix CloudFront client API unused variable #3179

bkuhlmann opened this issue Feb 1, 2025 · 2 comments · Fixed by #3181
Assignees
Labels
bug This issue is a bug.

Comments

@bkuhlmann
Copy link

bkuhlmann commented Feb 1, 2025

Describe the bug

Hello. 👋 I'm seeing the following warning in my logs:

$HOME/.cache/frum/versions/3.4.1/lib/ruby/gems/3.4.0/gems/aws-sdk-cloudfront-1.109.0/lib/aws-sdk-cloudfront/client_api.rb:680: warning: assigned but unused variable - listConflictingAliasesMaxItemsInteger

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

I would not expect to see this warning especially if listConflictingAliasesMaxItemsInteger is never used.

Current Behavior

See above.

Reproduction Steps

I would expect you'd be able to see this crop up in your test suite when adding the following to the top of your test suite:

$VERBOSE=true

Possible Solution

If you delete listConflictingAliasesMaxItemsInteger, the issue will go away.

Additional Information/Context

No response

Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version

aws-sdk-cloudfront 1.109.0

Environment details (Version of Ruby, OS environment)

ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +PRISM [arm64-darwin24.2.0]

@bkuhlmann bkuhlmann added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 1, 2025
@mullermp mullermp removed the needs-triage This issue or PR still needs to be triaged. label Feb 3, 2025
Copy link

github-actions bot commented Feb 5, 2025

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

@richardwang1124
Copy link
Contributor

Hello! Thank you for bringing this issue to our attention. We have merged a fix for this issue and it will be part of tomorrow's release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants