[ 
https://issues.apache.org/jira/browse/DAFFODIL-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358869#comment-16358869
 ] 

Dave Thompson commented on DAFFODIL-1843:
-----------------------------------------

Correction: Latest updates were add8c5a6f82f25073475a4d6c7ae94fb5ca6e01a.

> Unparser bitOrder change and OVC (outputValueCalc) interaction
> --------------------------------------------------------------
>
>                 Key: DAFFODIL-1843
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1843
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, Unparsing
>    Affects Versions: 2.0.0
>            Reporter: Michael Beckerle
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> See test test_bitOrderOVC1.
> This issue was discovered in the Link16 DFDL schema, and reproduced here in 
> an isolated context.
> This test shows that a spurious Runtime SDE is detected due to a 
> bitOrderChange. This has to do with the unparser having to back-up to fill in 
> a suspension for an outputValueCalc element, and losing the bitOrder that 
> should be maintained/captured for that usage. 
> At least that's my theory.
> This test should work, but gets a Runtime SDE:
> {code}edu.illinois.ncsa.daffodil.tdml.TDMLException: Runtime Schema 
> Definition Error: Data output stream DOS(id=5, Active, Direct Absolute from 0 
> to 27 (length 27)) with bitOrder 'leastSignificantBitFirst' not on a byte 
> boundary, cannot be populated from DOS(id=6, Finished, Buffered Absolute from 
> 27 to 40 (length 13), data=1F000000000000000000000000000000 no following) 
> with bitOrder 'mostSignificantBitFirst'.
> Schema context: NNN Location line 64 column 18 in 
> file:/tmp/s1_9132734461290850031.dfdl.xsd
> Data location was preceding byte 3
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to