[ https://issues.apache.org/jira/browse/NIFI-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015655#comment-16015655 ]
Dmitry Lukyanov commented on NIFI-3853: --------------------------------------- Hello All, I've noted that starting from this [commit|https://github.com/apache/nifi/commit/6ffb78d40465daff3b77a3b426732b5b515e3233] all builds in nifi/master failed with {code}FAILURE! - java.nio.channels.OverlappingFileLockException in org.apache.nifi.controller.scheduling.TestProcessorLifecycle{code} https://travis-ci.org/apache/nifi/builds/232661536 I assumed that the new test class [StandardFlowSerializerTest.java|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/java/org/apache/nifi/controller/serialization/StandardFlowSerializerTest.java] provokes this exception in the next running [TestProcessorLifecycle.java|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/java/org/apache/nifi/controller/scheduling/TestProcessorLifecycle.java] so, when I commented test cases it in my [fork|https://github.com/dlukyanov/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/java/org/apache/nifi/controller/serialization/StandardFlowSerializerTest.java] - the build runs fine: https://travis-ci.org/apache/nifi/builds/233558346 > Escape configurations prior to writing flow.xml > ----------------------------------------------- > > Key: NIFI-3853 > URL: https://issues.apache.org/jira/browse/NIFI-3853 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Reporter: Matt Gilman > Assignee: Matt Gilman > Priority: Critical > Fix For: 1.3.0 > > > If invalid characters are entered through the UI, they can corrupt the > flow.xml.gz making it unparsable on future restarts. Once in this state, the > flow.xml.gz needs to be hand-edited to remove the invalid characters. > Characters outside the following ranges may cause issues: > {code} > #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)