-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: upgrade oa and oc-verify #544
Conversation
This pull request introduces 2 alerts when merging 4a4acf5 into 59c837d - view on LGTM.com new alerts:
|
ed073c7
to
4fee7bf
Compare
4fee7bf
to
0b980c7
Compare
This pull request introduces 1 alert when merging 0b980c7 into 6610de1 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 22d1b2e into 6610de1 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 3bcacfc into 6610de1 - view on LGTM.com new alerts:
|
OK so I'm done w handling a To test locallyHere's how it looks like. If you want to test,
Here's how it'd look likeIn the case of a 429 rate limit (caused by user who flood the verifier), or a 502 bad gateway (caused by Cloudflare Ethereum Gateway), we don't know for certain that "This certificate is not valid". My question@Nebulis I'm not sure if it's conflicting to say both "certificate is not valid" and "unable to connect to the Ethereum network". People might get confused, what do yall think? If we want to make "This certificate is not valid" dynamic, problem is that it's static currently... might need a few other changes? |
This pull request introduces 1 alert when merging d4d3662 into 6610de1 - view on LGTM.com new alerts:
|
@gjj yeah the label certificate is not valid is problematic here let's change that too |
testcase still wip
This pull request introduces 1 alert when merging d4dc403 into 6610de1 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 3233cb2 into 6610de1 - view on LGTM.com new alerts:
|
For future reference, HTTP-related errors from Ethers: https://github.com/ethers-io/ethers.js/blob/9640e864a68b4a9e84e820f0ceaf1eb56c66715f/packages/web/src.ts/index.ts Can confirm that |
This pull request introduces 1 alert when merging 5dabb6e into 9e243f3 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 4593af3 into 9e243f3 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging f710b90 into 9e243f3 - view on LGTM.com new alerts:
|
- i'm not sure why, but somehow it was left out?
This pull request introduces 1 alert when merging 9e28d9f into b8ee5c0 - view on LGTM.com new alerts:
|
- also refactored some tests - removed OpenAttestationDocument from CertificateViewer (bug with eslint, as it's not picking it up)
- also removed extra ' from some test case names
- fixed some mistakes in the test inputs
errors.push(TYPES.SERVER_ERROR); | ||
} else if (invalidArgument(verificationStatus)) { | ||
// if the error is because of the merkleRoot, it should already be handled by the DOCUMENT_INTEGRITY fragment | ||
// empty here so that it's not caught by ETHERS_UNHANDLED_ERROR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Nebulis ok so previously I discovered that merkleRoot
s that were invalid (odd length, incorrect length/not 64 chars, contains non-hexcadecimal values) were not handled.
Now that it's handled, we expect it to show "Certificate has been tampered with" instead, and that is handled by DOCUMENT_INTEGRITY
instead of DOCUMENT_STATUS
. If we don't have this, the cases above will get caught by the else
block and thus resulting in the "Unhandled error" message.
Not sure what you think about having this check, but nothing is in here? (It should already be handled by this line https://github.com/OpenCerts/opencerts-website/pull/544/files#diff-ad34607bf39b4b3c4414917cf9b807f8R22)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is for ga right ? at least this could give us mor einformation about what really happened
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(explained)
</span> | ||
<div className={css["secondary-links"]}> | ||
<span> | ||
<Link href=" "> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will reload the page isnt it ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changed to not use Link
. instead, it's now a span
element. text-link
css class now includes cursor: pointer
also added button role for the link
needs Open-Attestation/decentralized-renderer-react-components#28