Christopher Foo

DAEParser.supportsData assumes ByteArrayData.position is 0

2

I found that if I enabled the default parsers and include my own custom subclassed parsers, it will throw an EOF error: ``` Called from away3d.library.Asset3DLibrary::loadData line 123 Called from...

DAEParser throws exception on Std::parseFloat on Neko target

1

I'm trying to load a DAE file but it's throwing an exception on the Neko target trying to parse a value that is already a float. ``` Called from sys.io.FileOutput::$statics...

A tool that launches the library and does a REPL loop with commands like: - `login user pass` - `show previous-packet`: print out the last packet in human readable form...

There should be a layer in the library that records protocol communication in a well defined manner. For example, it should dump out a JSON document per line for every...

The RPC server (`notaol.rpc`) is kind of clunky. Its intended usage is that a higher level client, such as a QT application or a command line client, will launch the...

There should be tool, maybe named `notaol.atomizer`, that you can do things like: - `python3 notaol.atomizer assemble < fdo_script` that outputs the binary stream - `python3 notaol.atomizer disassemble < data_capture`...

See https://github.com/chfoo/warcat/issues/10#issuecomment-196939147 for details

Support older Python 2.7

2

With chfoo/wpull being a success at supporting Python 2 using the latest lib3to2, Warcat shouldn't have problems with being backported.

Support warnings when WARC field name casing don't match hanzo's warc-tools.

1

For example, hanzo's warc-tools expects `WARC-Type` and not `Warc-Type`. The ISO spec says that field names are case-insensitive, but implementations may not follow the spec closely. The verify should warn...

Field names should be case-insensitive

1

Also reported here: https://bitbucket.org/rajbot/warc-tools/issue/1 . I'm creating this issue here on GitHub so others may know about this issue as well. > According to the WARC ISO 28500 Version 1...