-
Notifications
You must be signed in to change notification settings - Fork 44
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
Miscellaneous fixes + get local env running again #57
Conversation
aalu1418
commented
Dec 17, 2021
•
edited
Loading
edited
- Update local testing environment to be compatible with latest gauntlet
- Remove extra large state log from reading state
- Log tx sig for debugging
- Return error in transmit go routine if context not cancelled
- tested? - to be addressed in separate PR
- Check against new contract + transmission state Contracts: Allow storing more historical data & refactor validator+proxy into store #74
- Update job spec parameter from RPC to URL (already done)
712856e
to
0f78fb9
Compare
context.Background(), // does not use libocr transmit context | ||
c.client.rpc, | ||
c.client.ws, | ||
tx, | ||
true, // skip preflight | ||
rpc.CommitmentConfirmed, | ||
); err != nil { | ||
) | ||
if err != nil { |
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.
We should report this error back to libocr if it happens while libocr context still didn't expire (timeout).
For example, if the SendAndConfirmTra..
errors immediately, we don't actually report these errors upstream, so libocr assumes success while more information is available.
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.
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.
oooh that's a good point. I'll give it a shot...and see if i can test it too
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.
update: this will be done in a separate PR. this PR is now for getting everything working again with recent program changes
88781cd
to
8d445b7
Compare
…o be addressed in separate PR
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.
lgtm
}), | ||
) | ||
).every((isValid) => isValid) | ||
this.flags.TESTING_ONLY_IGNORE_PAYEE_VALIDATION && |
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.
😢
input.operators.map(async ({ payee }) => { | ||
try { | ||
const info = await token.getAccountInfo(new PublicKey(payee)) | ||
return !!info.address |
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 a dangerous cast. Do we know address is a string? Can you make this specific
).every((isValid) => isValid) | ||
|
||
this.require( | ||
areValidPayees || !!input.allowFundRecipient, |
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.
😢
@topliceanu thanks for the review! i'll make a note to fix those things. I have ideas to improve some of them |