Custom Query (121 matches)
Results (43 - 45 of 121)
|#118||fixed||Strange case where yaml.load should error but actually loads||xi||xi|
>>> yaml.load('-\n-3') [-3]
Adding a newline actually does produce the desired error:
>>> yaml.load('-\n-3\n') ... yaml.scanner.ScannerError: while scanning a simple key in "<string>", line 2, column 1: -3 ^ could not found expected ':' in "<string>", line 3, column 1: ^
|#120||fixed||typo in yaml.__init__.py||xi||py4fun@…|
line 46 in yaml.__init__.py contains a typo: "corresponSing" instead of "corresponDing"
|#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.