States.Hash with a Hash object does not produce the same hash value as stepfunctions simulator
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 7
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
There is a pending spec demonstrating this issue:
- https://github.com/ManageIQ/floe/blob/a2bd4eef8d08b9ad7a49690755d760a0e37dad3c/spec/workflow/intrinsic_function_spec.rb#L717-L722
The fundamental problem is we don't know how the step functions simulator is serializing a JSON object such that they produce that hash value. Even so, this should only affect possible integrations between floe and amazon step functions, which is an unlikely combination.
Contributor 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.
Research direction
Start with the pending spec in spec/workflow/intrinsic_function_spec.rb around lines 717-722 and compare its States.Hash result with the referenced Step Functions simulator value. Investigate how the simulator serializes JSON objects; the issue is complete when the hashing behavior is understood and the spec produces the expected matching value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100