Karl Bartel
Karl Bartel
I just noticed that this is a duplicate of the closed issue https://github.com/liljencrantz/crush/issues/42. I'll keep this open to make it easier for others to find until it is fixed.
The CI jobs seem stuck. Should I do a new push to trigger them again or is there a better way to deal with it?
After rebasing on develop, I get a reproducible semgrep fail in CI: ``` Command failed with output: fatal: Not a valid object name develop Failed to run 'git cat-file -e...
> Can you try rebasing this one more time? Done, but CI still fails with `We cannot run this job using the selected resource class. Please check your configuration and...
Now that the testnet is ready, what is the state of this issue?
Ok, then I'll move this to a [different epic](https://github.com/celo-org/op-geth/issues/130), since that is not included in the current testnet.
Please do the changes that don't depend on CIP-66 (FeeCurrencyWhiteList => FeeCurrencyDirectory) now without waiting for CIP-66, since that will still take a while. If that is a signifiant amount...
CIP-66 won't be in during the alfajores migration and is also not at the top of the priority list after that. Please don't wait for CIP-66 to update the docs!
I rebased the PR on the latest `optimism` branch. Is there anything else I can do to push this forward?
I rebased the PR again. Please let me know whether there is interest in this change or not.