Issue in data type of row

[ashish-gupta-2]

sample.yaml

tosca_definitions_version: tosca_simple_yaml_1_3

metadata:
  template_name: Inputs and Outputs Example
  template_author: Puccini
topology_template:

  inputs:
    cores:
      type: integer
      default: 4
      constraints:
      - less_than: 8

  node_templates:
    server:
      type: tosca:Compute
      capabilities:
        host:
          properties:
            num_cpus: { get_input: cores }
      attributes:
        public_address: "10.11.111.121"
  outputs:
    url:
      type: string
      value: { concat: [ 'http://', { get_attribute: [ server, public_address ] }, ':8080' ] }

function-call.go

  if data, ok := map_["row"]; ok {
              if functionCall.Row, ok = asInt(data); !ok {
                  return nil, fmt.Errorf("malformed function call, \"row\" not an integer: %T", data)
              }
          }

    if data, ok := map_["column"]; ok {
        if functionCall.Column, ok = asInt(data); !ok {
            return nil, fmt.Errorf("malformed function call, \"column\" not an integer: %T", data)
        }
    }

we are using below js script for coerce in our js file

const traversal = require('tosca.lib.traversal');
traversal.coerce();

It is taking row number as float64 rather than integer due to which below issue is coming :

GoError: malformed function call, "row" not an integer: float64 at internal:tosca.lib.traversal:158:9(58)

the same thing is working fine while using CLI command :

puccini-tosca compile -c <filename>

[tliron]

Thanks for this! Are you using a build from git main or is this the latest downloaded version?

[ashish-gupta-2]

@tliron We are using the latest downloaded version v0.20.1

[tliron]

Could you please test with the latest git build? It should be very easy, see this guide.

[ashish-gupta-2]

Will try that , are you planning to release latest git code main branch . Last release(v0.20.1) happened on 28-Feb-2022

[tliron]

There is a major fix I've been working for a while regarding constraints. As soon as it's fixed and tested I will release.

It could be that the bug you've discovered still exists, I just want to make sure, it sounds like something I already fixed.

[tliron]

The recent commits made a major refactoring to how values and function calls are parsed, normalized, and coerced. Could you please check now with the recent commit and let me know if you have issues? Otherwise, is there a way you can share your test case with me to help debug it?