Evan Sultanik

This is a good idea. In the mean time, is Graphtage’s `-e` option sufficient?

Maybe if we add the full path to the output of `-e`?

The [`bugfix/xml-attr-loop-32`](https://github.com/trailofbits/graphtage/tree/bugfix/xml-attr-loop-32) branch fixes @chrisfw's original error case. @AndreiUlmeyda or @jacwil are you able to see if this also fixes your issues? ``` $ git clone https://github.com/trailofbits/graphtage.git $ cd graphtage...

Graphtage uses Python's built-in parser for XML and HTML; anything it can parse, Graphtage can parse. Can you give a more detailed example to reproduce the problem?

Graphtage already has an internal notion of edit distance, which is what it uses to output its progress bar when run from a TTY. The idea would be to: 1....

This is because Graphtage is (incorrectly) currently using Python's XML parser to parse HTML. This is a bug. We need to switch to an actual HTML parser. I will use...

☝️Those are the relevant commits in which the hack was implemented.

Also, make sure to log the actual HTTP response, because this will usually contain an error message from the client. This is currently lost in the exception handling.

Maybe we can use the Etherscan API to avoid the requirement of having a fully sync'd node to replay transactions? https://github.com/corpetty/py-etherscan-api/blob/master/examples/accounts/get_all_transactions.py

This is almost the same as #6422 and #6426