Error when using numeric_set_attr
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Inspect lib/aws-record/record/attributes.rb around line 437 and locate the NumericSetMarshaler initializer used by numeric_set_attr. Confirm the initializer accepts the arguments passed there and verify that creating a numeric_set_attr no longer raises the reported ArgumentError; the payload does not name a test file to run.
Written by the indexing model from the issue text.
Description
Describe the feature
When creating an attribute with numeric_set_attr, I get the following error:
/usr/local/bundle/gems/aws-record-2.14.0/lib/aws-record/record/attributes.rb:437:in 'BasicObject#initialize': wrong number of arguments (given 1, expected 0) (ArgumentError)
attr(name, Marshalers::NumericSetMarshaler.new(opts), opts)
It looks like the initializer for Marshalers::NumericSetMarshaler is not properly defined. I'll submit a pull request.
Use Case
n/a
Proposed Solution
I will submit a PR
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
aws-sdk-ruby-record version used
2.15.2
Environment details (OS name and version, etc.)
Linux
- Dominant language
- Ruby
- Stars
- 318
- Forks
- 44
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 aws/aws-record-ruby
-
BuildableSearch#complete!.to_a auto-paginates silently and Limit is per-page (companion to #153)Openfeature-request
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-record-ruby#157 · 2 comments ·
-
feature-request
Difficulty 5/5 Over a week Newbie friendliness 38/100
aws/aws-record-ruby#155 · 1 comment ·
-
feature-request p2 queued
Difficulty 4/5 3-5 days Newbie friendliness 48/100
aws/aws-record-ruby#153 · 2 comments ·
-
feature-request
Difficulty 5/5 Over a week Newbie friendliness 35/100
aws/aws-record-ruby#152 · 3 comments ·
-
feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aws/aws-record-ruby#147 · 1 comment ·
All issues in aws/aws-record-ruby
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
benbalter/jekyll-include-cache#55 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
grafana/pyroscope#5729 · 1 comment ·
Maintainers usually reply within 1 day
-
`rake gemcutter:index:update` fails on Ruby 4.0Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rubygems/rubygems.org#6895 ·
Maintainers usually reply within 1 day