dfinity / dfinity/candid

Error after switching from version 0.10.14 to version 0.10.16

Open
#666 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
301
Forks
85
Avg merge
1h 4m
Merged PRs (30d)
4

Description

After switching canister dependency from 0.10.14 to 0.10.16, when I call extract-candid, I am getting an error message:

Error: Failed to call the function 'get_candid_pointer'

Caused by:
0: error while executing at wasm backtrace:
0: 0xe12c7 - fs_tests_backend.wasm!wasi::lib_generated::random_get::hc80c03217a531bdd
1: 0xdf3df - fs_tests_backend.wasm!std::sys::random::hashmap_random_keys::h26277e3d94315a2b
2: 0xbe18d - fs_tests_backend.wasm!candid::pretty::candid::DocComments::empty::h7cebd69a44b16a1f
3: 0x150e4 - fs_tests_backend.wasm!get_candid_pointer
4: 0xf9704 - fs_tests_backend.wasm!get_candid_pointer.command_export
1: function attempted to return an incompatible value
2: type mismatch: expected i32, found (ref null nofunc)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with extract-candid after switching the canister dependency from 0.10.14 to 0.10.16, then inspect the get_candid_pointer export and the wasm backtrace. Compare behavior between the two versions; done means extract-candid completes without the incompatible return-value or type-mismatch error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.