The reason this happens is one parse error is the cause of a second parse error. The first parse error encountered is:
Parse Error: Separator ',' not found. This parse error is has a schema context (line 100, data position 3). That parse error caused some backtracking and was wrapped with another parse error: Parse Error: Failed to parse infix separator. The first PE is the cause of the second. The error message tries to be helpful and provide the second PE as well as the cause, so the string looks something like this: Second PE reason. Cause: First PE reason First PE context Second PE context Both PE happen to have the same context, so it looks like duplicate information. Apparently we also print the first PE separate, so it again there's even more duplication. This is pretty confusing and isn't clear which context is associate with with PE/Cause. I'll open a ticket to imrove this particular diagnostic issue. - Steve On 6/19/20 8:27 AM, Roger L Costello wrote: > Hi Folks, > > Here’s an error message that I just got: > > [error] Parse Error: Failed to parse infix separator. Cause: Parse Error: > Separator ',' not found > > Schema context: sequence[1] Location line 100 column 14 in > file:/C:/apache-daffodil-2.6.0-incubating-bin/test/test.dfdl.xsd > > Data location was preceding byte 3. > > Schema context: sequence[1] Location line 100 column 14 in > file:/C:/apache-daffodil-2.6.0-incubating-bin/test/test.dfdl.xsd > > Data location was preceding byte 3 > > [error] Parse Error: Separator ',' not found > > Schema context: sequence[1] Location line 100 column 14 in > file:/C:/apache-daffodil-2.6.0-incubating-bin/test/test.dfdl.xsd > > Data location was preceding byte 3 > > Notice that this part is repeated 3 times: > > Schema context: sequence[1] Location line 100 column 14 in > file:/C:/apache-daffodil-2.6.0-incubating-bin/test/test.dfdl.xsd > > Data location was preceding byte 3. > > Why 3 times? > > /Roger >
