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

Beam JIRA Bot commented on BEAM-1453:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> Unicode chars in local file system paths break dataflow runner tests.
> ---------------------------------------------------------------------
>
>                 Key: BEAM-1453
>                 URL: https://issues.apache.org/jira/browse/BEAM-1453
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Pei He
>            Priority: P2
>              Labels: stale-P2
>
> toResourceIdentifier("/根目录/") failed with following error, and I think it 
> fails with any unicode chars, probably related to: 
> http://stackoverflow.com/questions/37409379/invalidpathexception-for-chinese-filename
> testGetCurrentDirectoryInUnix(org.apache.beam.sdk.io.LocalResourceIdTest)  
> Time elapsed: 0.011 sec  <<< ERROR!
> java.nio.file.InvalidPathException: Malformed input or input contains 
> unmappable characters: /???
> at sun.nio.fs.UnixPath.encode(UnixPath.java:147)
> at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
> at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
> at java.nio.file.Paths.get(Paths.java:84)
> at 
> org.apache.beam.sdk.io.LocalResourceIdTest.toResourceIdentifier(LocalResourceIdTest.java:244)
> at 
> org.apache.beam.sdk.io.LocalResourceIdTest.testGetCurrentDirectoryInUnix(LocalResourceIdTest.java:204)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at 
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to