Eddy Ashton

Thanks for the rapid response. Removing the `configurable` lines didn't help, the `config.ini` produced is identical and both validators are still run: ``` $ cat main.cpp ... auto create =...

@jafri I _think_ the right way to handle `REVERT` (from `eevm::Processor`'s perspective) is: - return `ExitReason::reverted`, either by throwing a special exception type or mimicking the halt-handler used by `STOP`...

I've been thinking about this further, and convinced myself again that its actually safe to permanently delete things, as any other 'real' conflicts would be caught by other dependencies, or...

Hi @OR13. We do have some quickstart/sandbox tools, but not a docker compose setup. To run a [sandbox](https://microsoft.github.io/CCF/main/build_apps/run_app.html#running-ccf-applications) instance in the published [`ccf-app-ci`](https://microsoft.github.io/CCF/main/contribute/build_setup.html#build-container) container, you can run: ``` $ docker...

This is still outstanding.

eg: #4058, #3203

I sketched out an extension to our LRU to handle automatic size-based eviction for this kind of use case, but eventually convinced myself it wasn't a useful approach. There are...

A related issue is that the table definitions don't actually include the necessary pieces to _use_ those tables, if they rely on some custom serialisers. I don't have a sample...

I corrected the comment on this recently, but the host-side implementation will still throw. We should remove that behaviour, and add a throw or abort if appropriate at each calling...

Another instance: https://dev.azure.com/MSRC-CCF/CCF/_build/results?buildId=14858&view=logs&j=88dd69b5-c778-5f1c-f9ac-1398f4203929&t=f18b20af-6d89-55d5-5278-1002871723a4&l=19155 This time in `ws_logging_raft`, which is the first time I've noticed it in a test that doesn't involve recovery.