Skip to content
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

Improve consistency with neo's codebase #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

corollari
Copy link
Contributor

@corollari corollari commented Jan 25, 2020

I've been trying to make sure that the NeoPubSub plugin only broadcasts events that are not the result of a FAULTy script execution, and while I think that the current plugin accomplishes this, after checking neo's code I changed the extension's code in order to make sure that only script executions that end up being committed are processed.
Essentially I've replicated the check that is done on neo.

Again, with a high probability this PR doesn't change anything, so feel free to close it. I'm just creating it because after spending some time researching it and implementing this solution I thought it may interesting to other ppl.

@corollari
Copy link
Contributor Author

@hal0x2328 thoughts?

@hal0x2328
Copy link
Member

Looks good to me

Copy link
Member

@shargon shargon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I Think that it's for HALT only

@corollari
Copy link
Contributor Author

corollari commented Feb 23, 2020

I Think that it's for HALT only

What do you mean? That checking against fault is the same as checking for HALT?

@shargon
Copy link
Member

shargon commented Feb 23, 2020

BREAK is other possible state, so we only should accept HALT

@corollari
Copy link
Contributor Author

I see, so if both checks are not equivalent, isn't it better to use the check that is used in the neo codebase when verifying if the changes made by the script should be commited?

That is, isn't the point of this check to make sure that only script execution results which end up being committed get their events relayed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants