#1243 closed defect (fixed)

WCPS1.5_Cannot parse identifier, max

Reported by: bphamhuu Owned by:
Priority: major Milestone: 10.0
Component: petascope Version: development
Keywords: Cc: dmisev, vmerticariu
Complexity: Medium

Description

47-get-metadata-identifier.test

for c in ( mr )
return
identifier(c)

WCPS1.5 returns error

   <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.WCPSProcessingError : A parsing error occurred at position=3:0. 
Offending symbol is=[@7,23:32='identifier',&lt;78&gt;,3:0]. 
Parser message=no viable alternative at input 'identifier'.</ows:ExceptionText>
    </ows:Exception>

Change History (2)

comment:1 Changed 20 months ago by bphamhuu

  • Summary changed from WCPS1.5_Cannot parse identifier to WCPS1.5_Cannot parse identifier, max

60-boolean_scalar_expr-t372.test

for c in (mr)
   return (max(c[i(100:100),j(100:100)]) = 1)

WCPS2.0 returns error

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.WCPSProcessingError : A parsing error occurred at position=2:11. Offending symbol is=[@8,25:27='max',&lt;43&gt;,2:11]. 
Parser message=no viable alternative at input '(max'.</ows:ExceptionText>
    </ows:Exception>

comment:2 Changed 16 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed

patch was accepted, close ticket.

Note: See TracTickets for help on using tickets.