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

Generate default manifest file when compiling #109

Merged
merged 3 commits into from
Sep 27, 2019

Conversation

shargon
Copy link
Member

@shargon shargon commented Sep 17, 2019

Close #91

Fix ABI issues

@superboyiii This is the expected value for neo-cli

@shargon shargon changed the title Generate default manifest on compilation Generate default manifest file when compiling Sep 17, 2019
@superboyiii
Copy link
Member

Close #91

@superboyiii This is the expected value for neo-cli

Wow, great, Let me test it.

@shargon
Copy link
Member Author

shargon commented Sep 17, 2019

@superboyiii Please, could you try again?

@superboyiii
Copy link
Member

@superboyiii Please, could you try again?

Success! But there seems still something wrong on sc execution.
image
image

@shargon
Copy link
Member Author

shargon commented Sep 17, 2019

Strange... please, try without if (Runtime.Trigger == TriggerType.Application) or add other return in this else

@lock9
Copy link
Contributor

lock9 commented Sep 17, 2019

I decompiled the script deployed and it doesn't look healthy:
image

Shouldn't it have a "PUSHDATA2" or equivalent? My code can be broken, but I checked it manually and it seems that there is something wrong in the serialization of the smart contract

@shargon
Copy link
Member Author

shargon commented Sep 17, 2019

I will review it

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

@lock9 This is the deploy or the smartcontract? The deploy script looks good in my test, and the contract was created

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

The smart contract looks good too
image

I will review it with a real deploy

@superboyiii
Copy link
Member

superboyiii commented Sep 18, 2019

The smart contract looks good too
image

I will review it with a real deploy

Yes, you're right. If I remove the Runtime.Trigger, it works well.
image

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

Without remove the Trigger it works to me, is the same code you provide me

image

image

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

@superboyiii You are trying with RPC, could you test it by neo-cli?

@superboyiii
Copy link
Member

@superboyiii You are trying with RPC, could you test it by neo-cli?

Add the Trigger and invoke it inside neo-cli, still return "".
image
I'm using SmartContract.Framework 2.9.3.1, is it related to this issue?

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

Please, send me your nef and manifest file
This is mine.
sc.zip

@superboyiii
Copy link
Member

superboyiii commented Sep 18, 2019

@shargon Yours works well on mine. But I'm not sure which course is different between us. Here's mine.
owen.zip

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

@superboyiii Could you add your source? looks different as the first version

image

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

I'm using SmartContract.Framework 2.9.3.1, is it related to this issue?

I used the library inside the repository, not the nuget

@superboyiii
Copy link
Member

Oh, Maybe that's the point. I use the nuget, maybe it's incompatible.

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

@superboyiii this is the issue

The new version use this syscall

And the nuget version use this

So you need to use the library from the bin folder, until we release a nuget for 3x (wait for #106)

@neo-project neo-project deleted a comment from superboyiii Sep 18, 2019
@neo-project neo-project deleted a comment from superboyiii Sep 18, 2019
@superboyiii
Copy link
Member

All right. Let me try it again.

@shargon
Copy link
Member Author

shargon commented Sep 18, 2019

Also I added here neo-project/neo-node@2360e7a some checks in order to prevent this issues in the future.

@superboyiii
Copy link
Member

superboyiii commented Sep 19, 2019

Also I added here neo-project/neo-cli@2360e7a some checks in order to prevent this issues in the future.

@shargon Good job! Thanks for your suggestion, mine works well now.

@shargon shargon requested a review from erikzhang September 19, 2019 08:22
@shargon
Copy link
Member Author

shargon commented Sep 19, 2019

Thanks you!

@shargon
Copy link
Member Author

shargon commented Sep 26, 2019

Ping @lightszero

@lightszero lightszero merged commit 85a01f8 into neo-project:master Sep 27, 2019
@shargon shargon deleted the generate-manifest branch September 27, 2019 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Neon compiler isn't ready for NEO3 contract deployment
4 participants