Opened 7 years ago

Last modified 7 years ago

#1750 closed enhancement

WCPS error reporting issues — at Version 2

Reported by: Dimitar Misev Owned by: Bang Pham Huu
Priority: major Milestone: 9.7
Component: petascope Version: development
Keywords: Cc:
Complexity: Medium

Description (last modified by Dimitar Misev)

I got these errors:

  • A parsing error occurred at position=4:69. Offending symbol is=[@41,143:143=',',<14>,4:69]. Parser message=no viable alternative at input 'coveragehillShadeover$pxx(imageCrsDomain($c[E(1049795:1059795),N(7740205:7750205)]),

The problem is that the query fragment after input has all the spaces removed, which is confusing.

  • A parsing error occurred at position=10:170. Offending symbol is=[@306,632:632=')',<70>,10:170]. Parser message=mismatched input ')' expecting {AND, ',', '/', '.', '=', '>', '>=', IS, '[', '<', '<=', '-', '*', '!=', OR, OVERLAY, '+', XOR}

The problem is that it is unclear what position=10:170 and Offending symbol is=[@306,632:632=')',<70>,10:170] mean.

Change History (2)

comment:1 by Bang Pham Huu, 7 years ago

Resolution: invalid
Status: newclosed

comment:2 by Dimitar Misev, 7 years ago

Component: wcsclientpetascope
Description: modified (diff)
Resolution: invalid
Status: closedreopened
Summary: WS client should replace \n with space in WCPS queriesWCPS error reporting issues
Note: See TracTickets for help on using tickets.