Custom Query (121 matches)
Results (37 - 39 of 121)
|#123||fixed||libyaml parser hangs when reading all in one read from a TCP socket.||xi||pem@…|
When setting a read handler (which uses read(2)) with yaml_parser_set_input() and reading from a socket descriptor, it happens that the entire yaml document is read in one call of the handler. This seems to confuse the parser (yaml_parser_load()) which calls the handler again, attempting to read more.
Forcing at least two packages from the client makes it work. The workaround was to make the client write and flush the leading "---" separately, and then dump the rest on the socket.
This is with libyaml 0.1.2. The client side is using SnakeYAML 1.1 (with java 1.6), both on openSuse 11.0.
|#86||wontfix||Use on socket connections with non blocking flag set||xi||oscar.ostlund@…|
I am trying to use yaml as a communication language between processes that are connected through sockets. When I open sockets, I use non blocking sockets. Thus when libyaml tries to read the file with fread, it returns an error. Indeed, as the non blocking flag is set, when there is nothing more to read, the fread call returns EWOULDBLOCK.
As a hack, I have modified the yaml_file_read_handler function to return 1 if errno == EWOULDBLOCK and !ferror in the other cases...
What do you think ?
Thanks for your help
|#163||fixed||PyYAML is not installable with Jython||xi||olt@…|
Installing PyYaml? with pip install under Jython doesn't work on a system that has a compiler. It checks for libyaml compatibility and then errors: "Compiling extensions is not supported on Jython"
Solution: Don't add ext_module for platform.system() == Java. See patch.