Zachary Wimer

@twizmwazin Should I also update `setup.cfg` to say `Programming Language :: Python :: 3.8`? Right now it says `Programming Language :: Python :: 3.6` even though `python_requires = >= 3.8`

> > @twizmwazin Should I also update `setup.cfg` to say `Programming Language :: Python :: 3.8`? Right now it says `Programming Language :: Python :: 3.6` even though `python_requires =...

Ping @rhelmot

The `test_java.test_fauxware` test is failing; which, since it is java, I assume is because of the breaking semantic change.

Fixed the string length calculations. The only failing test case is `test_techniques.test_indirectcfi`; this failed due to a timeout. @ltfish I reran the test and it passed. I'm not sure if...

Ping @ltfish

Ping @ltfish Regenerate all caches please

Actually, this looks like an interaction with `strings.py`'s `__init__`. Note that here `strings` edits `kwargs`: https://github.com/angr/claripy/blob/696f1c08c2996c5350867685462d1245070a996d/claripy/ast/strings.py#L31 `Bits`' `self.length = kwargs['length']` would be a no-op if `kwargs` were not edited between...

Suggested solution: 1. Refactor all String ops not to use bit lengths rather than byte lengths. 2. Remove `kwargs['length'] *= 8` from `String`'s `__init__` (really this is part of 1)...

This can be triggered from within `Base`'s new function via the concrete backend constructing an object, it being returned from new, then edited after `__init__` runs.