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
read(write(record)) != record #57
Comments
ikreymer
added a commit
that referenced
this issue
Feb 20, 2020
- Fix issue #104 where utf-8 canonicalization caused record to be written with incorrect content-length - Fix issue #57 where protocol is set as statusline in correctly - fill payload_length when reading warc records - always support tell() to LimitReader and BufferedReader() - bump version to 1.7.2
ikreymer
added a commit
that referenced
this issue
Mar 1, 2020
* Fixes related to reading record and writing same record back out: - Fix issue #104 where utf-8 canonicalization caused record to be written with incorrect content-length - Fix issue #57 where protocol is set as statusline in correctly - fill payload_length when reading warc records - always support tell() to LimitReader and BufferedReader() - bump version to 1.7.2 * fix tests for py27, add py38
This should now be a fixed, I added a unit test based on your example above: Released in 1.7.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Records read back from a file just written should be equal to the Python object written. This is something I discovered while writing tests for an application using warcio. Test case:
results in the following assertion failure:
The text was updated successfully, but these errors were encountered: