-
Notifications
You must be signed in to change notification settings - Fork 276
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
[refactor] #3874: Removes IsAssetDefinitionOwnerQuery
#3920
Conversation
Hello, Ben. |
Hi there, will do. |
no
you execute |
|
Thanks for the help. I'm getting problems with the
The error looks like its coming from snapshot creation, when I run the tests more verbosely the line
Please advise on next steps. Let me know how to provide any other information that may be helpful. |
run |
Yes I have run this locally and I receive the error above with the tests in |
Pull Request Test Coverage Report for Build 6405672609
💛 - Coveralls |
oh, you also have to run: |
Okay, will do. Is this in the developer docs somewhere? |
I have done this and am getting the following error Finished release [optimized] target(s) in 3m 08s
Running `target/release/kagami validator`
error: unrecognized subcommand 'validator' Is there any documentation I can look at for kagami/these commands? What is their purpose? |
sorry, I forgot we changed API for this recently. This command rebuilds |
@benhhack I hope you will fix CI errors so we can merge this |
Yes, am working my way through trying to figure out commit squashing/message amending since its not something I've done before. |
@benhhack you still have a conflict to resolve :) |
@benhhack hi, can we expect an update this week? |
Hi yes, will be working on this tomorrow |
Hi @mversic. I'm unsure how to solve this conflict since I can't view the wasm file. Do you have any tips? I'd love to learn more about what's going on to pointing to any resources would also be very helpful. I should also point out that not all the tests are passing despite running the commands you mentioned. Do you have any ideas? |
yes, you cannot see contents of a binary file. You have to build new |
I have just done that and I see that the conflicts are not resolved. |
have you fetched latest changes from iroha2-dev and rebased your PR? First do that, then rebuild |
Yeah I have but will try that again. |
you have not rebased to latest iroha2-dev. Check what is latest commit (that is not yours) on your branch and what is latest commit on iroha2-dev. You will see additional commits on iroha2-dev branch |
The DCO check is now failing because some of the commits I've rebased on top of seem not to have signoffs. |
DCO is the least of your concerns. Somehow you have made a mess of your local git history. Github now shows that you have modified 99 files. You will have to fix this |
How is it looking now @mversic ? |
@benhhack please fix failing CI jobs, all tests are passing but you have formatting issues |
Apologies, have run nightly and pushed the changes. |
@benhhack please squash your commits into 1 and I will approve your PR |
@mversic I'm struggling with the squashing because of the validator.wasm merge conflicts. A standard interactive rebase isn't working. Do you have any tips? |
Sure, this will be completed tomorrow. When I update the branch would you recommend I update with a rebase or a merge? |
We use rebase workflow. Also, there is some more conflicts now that you have to resolve |
Signed-off-by: benhhack <[email protected]>
Signed-off-by: benhhack <[email protected]>
@mversic all the updates have definitely confused things, one of the recent ones also seems to have overlapping work with this one here. Again apologies for taking so long with this. I appreciate the assistance and I'm learning a lot. I'm going to refork the repository in its most updated form and work from there so that I can have a clean commit history without all the merging. |
Description
Removed all instances of
IsAssetDefinitionOwner
except for some:In
wasm/validator/src/permission.rs
and `/default.rsWith the function
I am unsure what to replace this result with. I have tried replacing it with
FindAssetDefinitionById
(since this is said to do the exact same thing as is asset definition owner in #3874) but this creates build errors. Should I delete everything that uses theis_asset_definition_owner
function as well?Linked issue
Remove
IsAssetDefinitionOwnerQuery
This query was introduced only for the purposes of validator. Since #3442 we can use
FindAssetDefinitionById
to do the exact same thing.Closes #3442
Checklist
CONTRIBUTING.md