-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
udpipe2teitok.pl tries to write to folder as if it were a file #6
Comments
Should be solved now - it now creates the folder if it does not exist, and it does more checks to figure out how to properly name the output files. |
Thanks Maarten ... but ... err ...where's the commit? Under https://github.com/ufal/teitok-tools/commits/master/ I only see 78d93e9 as the most recent one? Do I overlook something? |
I saw a newer commit de76fa4 and merged it. The behavior changed but the bug is still there. how to reproduceI've simplified the bug reproduction by moving the sample data and a hard-coded explicit script call into the code repo. To reproduce, do
which executes this perl script (which should be executable without docker as well):
where what's the output:The command output is
after which I have three new folders
The two folders
interpretationI don't know what causes the almost empty xml file, but as for the conllu file, I suspect a missing |
Okay, specifying a tmp folder explicitly works. E.g.
|
description
the script fails to create output files but instead creates folders with the target names of the output files. E.g. input file is
DEU_001.txt
, then the console output is:but no files
udpipeDEU_001.conllu
orudpipeDEU_001.xml
are created. Instead there are folders with such names:I guess a
/
is missing? I.e. it should beudpipe/DEU_001.conllu
?how to reproduce
I've created a branch in my veld repos
udpipe2teitok_bug_reproduction
After this, the output folders instead of files are created in the code submodule
which would show these four folders (of two input files https://github.com/veldhub/veld_chain__demo_teitok-tools/tree/udpipe2teitok_bug_reproduction/data/udpipe2teitok/in ):
The text was updated successfully, but these errors were encountered: