[jira] [Commented] (FOP-2481) AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks

2021-11-29 Thread TLX (Jira)


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

TLX commented on FOP-2481:
--

Okay, I found the answer myself: A block-container that contains only 
absolutely positioned children counts as empty to the algorithm. That way it 
will crash everything by leading to that AssertionError.
Solution: Assing span="all" to that block-container. By doing so it won't 
trigger the column-distribution algorithm.

It would be great if this could throw a regular exception that explains what's 
wrong. AssertionErrors shouldn't be used to catch invalid user input.


> AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks
> ---
>
> Key: FOP-2481
> URL: https://issues.apache.org/jira/browse/FOP-2481
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Priority: Major
> Attachments: exception.fo
>
>
> AssertionError
>   at 
> org.apache.fop.layoutmgr.BalancingColumnBreakingAlgorithm.getInitialBreaks(BalancingColumnBreakingAlgorithm.java:171)
> export FOP_OPTS=-ea
> fop exception.fo out.pdf



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (FOP-2481) AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks

2021-11-29 Thread TLX (Jira)


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

TLX commented on FOP-2481:
--

Since this is still unsolved, could anyone please give any hint how to avoid 
this assertion from failing when using Apache FOP as someone who doesn't know 
anything about this Knuth stuff? All I did was define a 2-column layout with a 
"span='all'" block-container in it. None of them is empty, which is different 
from the example file here in this ticket. I really have no idea how to work 
around this. My .fo data is valid in my opinion.
I don't want to turn of assertion checking for my whole application server 
either. The code in BalancingColumnBreakingAlgorithm.getInitialBreaks as well 
as the explanation by [~adelmelle] are making me suspect it wouldn't help 
anyway.

> AssertionError at BalancingColumnBreakingAlgorithm.getInitialBreaks
> ---
>
> Key: FOP-2481
> URL: https://issues.apache.org/jira/browse/FOP-2481
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Priority: Major
> Attachments: exception.fo
>
>
> AssertionError
>   at 
> org.apache.fop.layoutmgr.BalancingColumnBreakingAlgorithm.getInitialBreaks(BalancingColumnBreakingAlgorithm.java:171)
> export FOP_OPTS=-ea
> fop exception.fo out.pdf



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


buildbot failure in on fop-trunk

2021-11-29 Thread buildbot
The Buildbot has detected a new failure on builder fop-trunk while building . 
Full details are available at:
https://ci.apache.org/builders/fop-trunk/builds/1820

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: The Nightly scheduler named 'fopNightly' triggered this build
Build Source Stamp: [branch xmlgraphics/fop/trunk] HEAD
Blamelist: 

BUILD FAILED: failed compile

Sincerely,
 -The Buildbot