gluwa / creditcoin Goto Github PK

Question
I saw your implementation for fetching block author. Can anyone please explain a bit how it's working?

Here is the code link: https://github.com/gluwa/creditcoin/blob/ea6d284704563459b08aa261d026a8cf3d7e0a65/pallets/rewards/src/lib.rs#L86C4-L88C7

If I tried to use the same code to fetch the block author then I didn't get anything.

The gluwa/ci-linux:production image on Docker hub doesn't match with current creditcoin Dockerfile.
I tried to build from 2.0.0-beta-6 version.

Question

Please include information such as the following: is your question to clarify an existing resource
or are you asking about something new? what are you trying to accomplish? where have you looked for
answers?

this error msg keep showing

When building a creditcoin:2.0.0-beta-5 docker image with the provided 'Dockerfile', I got the following error.
There is something inconsistent with the image 'gluwa/ci-linux'.
So I built the image with the latest Ubuntu image and it worked.

My environment: Ubuntu 18.04

-- Docker image build error

error: could not rename component file from '/root/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/wasm32-unknown-unknown/lib' to '/root/.rustup/tmp/aqaj9q7qkyuqf7jg_dir/bk': Invalid cross-device link (os error 18)

The command '/bin/bash -c source ~/.cargo/env && rustup default stable && rustup update nightly && rustup update stable && rustup target add wasm32-unknown-unknown --toolchain nightly' returned a non-zero code: 1

-- Dockerfile built successfully

FROM ubuntu:latest
ARG DEBIAN_FRONTEND=noninteractive
RUN apt-get update -y
ENV TZ=Etc
RUN apt-get install -y tzdata
RUN apt-get install -y cmake pkg-config libssl-dev git build-essential clang libclang-dev curl

RUN curl https://sh.rustup.rs -sSf | sh -s -- -y
RUN /bin/bash -c 'source ~/.cargo/env && rustup default stable && rustup update nightly && rustup update stable && rustup target add wasm32-unknown-unknown --toolchain nightly'

WORKDIR /creditcoin-node
COPY Cargo.toml .
COPY Cargo.lock .
ADD node /creditcoin-node/node
ADD pallets /creditcoin-node/pallets
ADD primitives /creditcoin-node/primitives
ADD runtime /creditcoin-node/runtime
ADD sha3pow /creditcoin-node/sha3pow
ADD chainspecs /creditcoin-node/chainspecs
RUN /bin/bash -c 'source ~/.cargo/env && cargo build --release'

EXPOSE 30333/tcp
EXPOSE 30333/udp
EXPOSE 9944 9933 9615
RUN /bin/bash -c 'cp /creditcoin-node/target/release/creditcoin-node /bin/creditcoin-node'
COPY chainspecs .
ENTRYPOINT [ "/bin/creditcoin-node" ]

Description

"Thread 'tokio-runtime-worker' panicked at 'Externalities not allowed to fail within runtime: "Trie lookup error: Database missing expected key: 0xa477a913b393137dbdcacd786fd153d69ad0462d47f09189ce91e7e313f10418"', /creditcoin-node/.cargo/git/checkouts/substrate-ef6be82d837dee7f/4e22d40/primitives/state-machine/src/ext.rs:192"

Steps to Reproduce

Replace the example steps below with actual steps to reproduce the bug you're reporting.

1. Download corrupted paritydb folder from https://www.dropbox.com/scl/fi/lbxwkrwpytyhk4oscid6k/paritydb.zip?rlkey=t38reqkdlqluh13kr0polw1ra&dl=0
2. Extract paritydb contents into existing data folder
3. Start Creditcoin validator (2.3.0 or 2.3.1)
4. See error

Expected vs. Actual Behavior

Validator ran normally and resolved any issue automatically

Environment

Docker version 24.0.6, build ed223bc
gluwa/creditcoin:latest (c581f6e1081f) Created 2 weeks ago - 577MB
Docker Compose version v2.22.0-desktop.2

• Operating system: Microsoft Windows 11 Pro Insider Preview (10.0.23570 N/A Build 23570)
• Template version/tag: gluwa/creditcoin:latest (c581f6e1081f)
• Rust version (run rustup show):

Logs, Errors or Screenshots

Logs: https://pastebin.com/raw/qrX18eDe
ParityDB folder: https://www.dropbox.com/scl/fi/lbxwkrwpytyhk4oscid6k

Additional Information

Description

Tell us what happened. In particular, be specific about any changes you made to this template.
Ideally, provide a link to your project's GitHub repository. Please note that we are not able to
support all conceivable changes to this template project, but the more information you are able to
provide the more equipped we will be to help.

Steps to Reproduce

Replace the example steps below with actual steps to reproduce the bug you're reporting.

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected vs. Actual Behavior

What did you expect to happen after you followed the steps you described in the last section? What
actually happened?

Environment

Describe the environment in which you encountered this bug. Use the list below as a starting point
and add additional information if you think it's relevant.

• Operating system: MAC-OS M1
• Template version/tag: 2.0.0-beta.6-5fb837a-x86_64-macos
• Rust version (run rustup show):

Logs, Errors or Screenshots

Please provide the text of any logs or errors that you experienced; if
applicable, provide screenshots to help illustrate the problem.

Additional Information

Please add any other details that you think may help us solve your problem.

Version: 2.0.0-beta.6-5fb837a-x86_64-macos

0: ___jit_debug_register_code
1: ___jit_debug_register_code
2: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
3: ___jit_debug_register_code
4: ___jit_debug_register_code
5: ___jit_debug_register_code
6: ___jit_debug_register_code
7: ___jit_debug_register_code
8: ___jit_debug_register_code
9: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
10: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
11: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
12: __mh_execute_header
13: __mh_execute_header
14: __mh_execute_header
15: __mh_execute_header
16: __mh_execute_header
17: __mh_execute_header
18: __mh_execute_header
19: __mh_execute_header
20: __mh_execute_header
21: __mh_execute_header
22: __mh_execute_header
23: __mh_execute_header
24: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
25: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
26: __ZN7rocksdb6ribbon6detail34BandingConfigHelper1MaybeSupportedILNS0_25ConstructionFailureChanceE1ELy128ELb0ELb0ELb1EE11GetNumSlotsEj
27: ___jit_debug_register_code
28: __pthread_deallocate

Thread 'tokio-runtime-worker' panicked at 'Multiaddr is known to be valid.: UnknownProtocolId(255016928)', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/multiaddr-0.13.0/src/lib.rs:276

os : mac os monterey
chipset : m1
2.0.0-beta-6

This error occurred twice while in use

creditcoin-node(79637,0x173ea3000) malloc: Heap corruption detected, free list is damaged at 0x600003ea18a0
Incorrect guard value: 3
creditcoin-node(79637,0x173ea3000) malloc: *** set a breakpoint in malloc_error_break to debug
zsh: abort ./creditcoin-node --validator --name username --telemetry-url --bootnodes --chain

Hello 👋

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@dobermann-pinscher) has found a potential issue, which I would be eager to share with you.

Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.

Looking forward to hearing from you 👍

(cc @huntr-helper)