superical
superical
@TomFrost It would be great if I could have this PR reviewed and merged because this will help many Electron projects to continue using Cryptex. Thanks!
@TomFrost I agree that it makes more sense to use that. I will check on that and probably update the PR again very soon.
> Are you using a framework like hardhat? Can you run `crytic-compile ` and let us know if that works? @0xalpharush I'm having similar issue as @patelvishal1401 with manticore not...
@0xalpharush I'm having a similar issue. I've tried calling my library functions explicitly and still don't see the coverage being updated. Are there other workarounds to this?
After spending over an hour grappling with this issue, it seems like my problem was with the token (which is stored as a secret) missing in codecov when triggering via...
Ah... Glad to know that it's the official way to do it.👍 Is this even mentioned in the documentation? I didn't find anything about this issue. I ended up trying...
Do these api (deployNewTitleEscrow) and cli (open-attestation deploy title-escrow) behave the same ?
> I tried to create a new title escrow using api from node-js Which nodejs API are you referring to?
Do these api (deployNewTitleEscrow) and cli (open-attestation deploy title-escrow) behave the same ?
This sounds like a question more with the token registry if I understood you correctly? Which version are you using?
Do these api (deployNewTitleEscrow) and cli (open-attestation deploy title-escrow) behave the same ?
Btw, if you are using v3.2, you shouldn't have to create title escrow manually.🙂
When we say the "context", can I presume it's referring to the URLs in the `@context` section of a document? If that's what it's referred to, would it make sense...