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.

Sign up for GitHub

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

Jump to bottom

flookup throws error #56

Open

GoogleCodeExporter opened this issue Mar 3, 2016 · 1 comment

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented Mar 3, 2016

I am testing TRMorph with server mode like this:

flookup -S -A 127.0.0.1 trmorph.fst

When I send "yetersizliği" word from UDP client, server is getting problem:

sendto() failed: Message too long

and client hung and wait forever

Original issue reported on code.google.com by [email protected] on 19 Sep 2014 at 2:47

The text was updated successfully, but these errors were encountered:

Author

GoogleCodeExporter commented Mar 3, 2016

Can't replicate this directly - apparently doesn't only have to do with the 
word "yetersizliği" since running that word through some other transducer with 
nc works fine.

What should the output(s) be? How is UDP message being sent (with nc?)? The 
error probably hinges on the particular transducer stored in trmorph.fst.

Original comment by [email protected] on 20 Sep 2014 at 12:38

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment