-
Notifications
You must be signed in to change notification settings - Fork 94
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
Convert to number error when storing a value in float64 during execution of provider-defined function #914
Labels
bug
Something isn't working
reflection
Issues and PRs about the reflection subsystem used to convert between attr.Values and Go values.
types
Issues and pull requests about our types abstraction and implementations.
Comments
bflad
added
types
Issues and pull requests about our types abstraction and implementations.
reflection
Issues and PRs about the reflection subsystem used to convert between attr.Values and Go values.
labels
Jan 30, 2024
bendbennett
added a commit
that referenced
this issue
Feb 6, 2024
) * The reflect.Number function was handling float32 and float64 values by determining whether the value in the *big.Float generated through calling val.As() was an exact representation by examining the accuracy produced when calling Float32() or Float64() on the *big.Float * The reflect.Number function has been altered to verify whether the string representation, generated by calling Text(), of the generated *big.Float and a *big.Float created from the float32 or float64 value are identical
bendbennett
added a commit
that referenced
this issue
Feb 6, 2024
bendbennett
added a commit
that referenced
this issue
Feb 22, 2024
…via string representation (#919) * Alter handling of float32 and float64 values within reflect.Number (#914) * The reflect.Number function was handling float32 and float64 values by determining whether the value in the *big.Float generated through calling val.As() was an exact representation by examining the accuracy produced when calling Float32() or Float64() on the *big.Float * The reflect.Number function has been altered to verify whether the string representation, generated by calling Text(), of the generated *big.Float and a *big.Float created from the float32 or float64 value are identical * Removing AllowRoundingNumbers option and modifying reflect.Number accordingly (#914)
bendbennett
added a commit
to hashicorp/terraform-provider-corner
that referenced
this issue
Feb 22, 2024
Latest terraform-plugin-framework contains fix for: * hashicorp/terraform-plugin-framework#914 * hashicorp/terraform-plugin-framework#919
bendbennett
added a commit
to hashicorp/terraform-provider-corner
that referenced
this issue
Mar 6, 2024
* Adding function tests for framework protocol 5 & 6 and protocol 6 mux providers (#202) * Adding copyright headers (#202) * Linting (#202) * Adding function tests for protocol v5 and protocol v6 providers (#202) * Amending provider defined function tests for number until bug fix on go.cty is released (#202) * Adding function testing for mux providers (#202) * Adding function testing for tf6to5provider (#202) * Adding copyright headers (#202) * Bumping terraform-plugin-framework version to latest (#202) Latest terraform-plugin-framework contains fix for: * hashicorp/terraform-plugin-framework#914 * hashicorp/terraform-plugin-framework#919 * Bumping terraform-plugin-testing to v1.7.0 (#202) * Refactoring to return function.FuncError (#202) * Updates following code review (#202)
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Something isn't working
reflection
Issues and PRs about the reflection subsystem used to convert between attr.Values and Go values.
types
Issues and pull requests about our types abstraction and implementations.
Module version
Relevant provider source code
Terraform Configuration Files
Following is the configuration used during execution of the test.
Debug Output
https://gist.github.com/bendbennett/ea6aadc53b2e53e66eda630f6b638e64
Expected Behavior
Test should run sucessfully.
Actual Behavior
Following error is generated:
Steps to Reproduce
v1.8.0
is released).The text was updated successfully, but these errors were encountered: