Skip to content

Conversation

@mina86
Copy link
Contributor

@mina86 mina86 commented Aug 15, 2023

This addresses the following two warnings:

warning: .../code/parachain/frame/call-filter/Cargo.toml: unused manifest key: dependencies.support.package
warning: .../code/parachain/frame/call-filter/Cargo.toml: unused manifest key: dependencies.system.package

Funnily enough, removing the package keys did affect the compilation
and broke stuff. However, the obvious solution was to just use full
names of the packages (which we already had in workspace Cargo.toml)
rather than renaming them.

Required for merge:

  • pr-workflow-check / draft-release-check is ✅ success
  • Other rules GitHub shows you, or can be read in configuration

Makes review faster:

  • PR title is my best effort to provide summary of changes and has clear text to be part of release notes
  • I marked PR by misc label if it should not be in release notes
  • Linked Zenhub/Github/Slack/etc reference if one exists
  • I was clear on what type of deployment required to release my changes (node, runtime, contract, indexer, on chain operation, frontend, infrastructure) if any in PR title or description
  • Added reviewer into Reviewers
  • I tagged(@) or used other form of notification of one person who I think can handle best review of this PR
  • I have proved that PR has no general regressions of relevant features and processes required to release into production
  • Any dependency updates made, was done according guides from relevant dependency
  • Clicking all checkboxes
  • Adding detailed description of changes when it feels appropriate (for example when PR is big)

This addresses the following two warnings:

    warning: /srv/mpn/comp/composable/code/parachain/frame/call-filter/Cargo.toml: unused manifest key: dependencies.support.package
    warning: /srv/mpn/comp/composable/code/parachain/frame/call-filter/Cargo.toml: unused manifest key: dependencies.system.package

Funnily enough, removing the package keys *did* affect the compilation
and broke stuff.  However, the obvious solution was to just use full
names of the packages (which we already had in workspace Cargo.toml)
rather than renaming them.
@mina86 mina86 added the Misc I marked PR by `misc` label if it should not be in release notes #owned:terraform label Aug 15, 2023
@github-actions
Copy link

Pull reviewers stats

Stats of the last 30 days for composable:

User Total reviews Time to review Total comments
dzmitry-lahoda 26 12h 15m 19
blasrodri 20 1h 17m 12
mina86 16 1d 34m 82
RustNinja 16 1h 11m 2
kkast 12 3h 53m 7
vmarkushin 3 7h 2
JafarAz 3 9h 25m 0
0xBrainjar2 1 3d 17h 35m 6

@github-actions
Copy link

# run Composable node
nix run "github:ComposableFi/composable/refs/pull/4071/merge" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed
# run local Picasso DevNet (for CosmWasm development)
nix run "github:ComposableFi/composable/refs/pull/4071/merge#devnet-picasso" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 
# CosmWasm on Substrate CLI tool
nix run "github:ComposableFi/composable/refs/pull/4071/merge#ccw" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 
# run cross chain devnet with Dotsama and Cosmos nodes 
nix run "github:ComposableFi/composable/refs/pull/4071/merge#devnet-xc-fresh" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed 
# or same with docker
nix build "github:ComposableFi/composable/refs/pull/4071/merge#devnet-xc-image" --allow-import-from-derivation --extra-experimental-features "flakes nix-command" --no-sandbox --accept-flake-config --option sandbox relaxed \
&& docker load --input result && docker run -it --entrypoint bash devnet-xc:latest -c /bin/devnet-xc-fresh 

About nix

@mina86 mina86 changed the title Fix cargo warnings chore: fix cargo warnings Aug 15, 2023
@mina86 mina86 enabled auto-merge August 15, 2023 01:46
@mina86 mina86 requested a review from kkast August 15, 2023 01:47
@dzmitry-lahoda
Copy link
Contributor

@kkast is on vacation. also, super good to fix warnings, but without making warnings to be ci error these may return in future

@dzmitry-lahoda dzmitry-lahoda self-requested a review August 15, 2023 09:07
@mina86 mina86 added this pull request to the merge queue Aug 15, 2023
Merged via the queue into main with commit 23405ff Aug 15, 2023
@mina86 mina86 deleted the mpn/c branch August 15, 2023 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Misc I marked PR by `misc` label if it should not be in release notes #owned:terraform

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants