Max Ammann

I just stumbled upon this while fixing a bug :D Can you publish the fixed version on npm? :)

Setting ``` 'auth.bruteforce.protection.enabled' => false, ``` works around the issue. I believe maybe some functions in cospend are too heavily rate limited?

@xgreenx Let me know how you want the corpus to be delivered :) I suggest an external repository that can be public or private. Private might be better to start...

> Just an overall question: do you have any ideas on how it can be integrated into our CI on a daily basis? My idea was to experiment with https://google.github.io/clusterfuzzlite/...

@xgreenx Here is the CFL PR: https://github.com/FuelLabs/fuel-vm/pull/727

@xgreenx I think we want to add the no-changelog tag to this PR. Also the wasm checks seem to depend on the base branch being in the fuel-vm repository.

The private corpus is currently stored in this private repo: https://github.com/trail-of-forks/fuel-vm-fuzz-corpus

This is ready now. Note that you maybe want to remove the existing `fuzz_targets/grammar_aware.rs` fuzzer which is broken. That would also remove the `arbitrary` dependency.

Did anyone try syncthing yet for such a usecase? Using a backup tool instead of rsync seems like a "misuse" of tools. Even though it might work, goals are different.

I thought synching might have a one-sync mode which only runs one. But that does not exist.