Failed to compile contracts without error logs

Sway
1

forc build return error without showing any errors, any ideas?

error: Could not generate the entry method. See errors above for more details.
____

  Aborting due to 1 error.
error: Failed to compile contracts

Fuelup show

Installed toolchains
--------------------
latest-x86_64-unknown-linux-gnu (default)
nightly-x86_64-unknown-linux-gnu
nightly-2024-05-28-x86_64-unknown-linux-gnu
testnet-x86_64-unknown-linux-gnu

active toolchain
----------------
latest-x86_64-unknown-linux-gnu (default)
  forc : 0.66.5
    - forc-client
      - forc-deploy : 0.66.5
      - forc-run : 0.66.5
    - forc-crypto : 0.66.5
    - forc-debug : 0.66.5
    - forc-doc : 0.66.5
    - forc-fmt : 0.66.5
    - forc-lsp : 0.66.5
    - forc-tx : 0.66.5
    - forc-wallet : 0.11.1
  fuel-core : 0.40.0
  fuel-core-keygen : 0.40.0

fuels versions
--------------
forc : 0.66.10
forc-wallet : 0.66.9
2

Hey @eesheng, hope you are doing well. Could you share the code so that I can reproduce it locally?

3

Hi yes, GitHub - Yune-Protocol/v1-core

To reproduce the error, run forc build within the Vault directory.

4

@eesheng it seems to be an issue with the interface. maybe it is not being imported correctly. I will further look into it but it seems that an interface is being the issue here

5

Hi interfaces are imported correctly, it did compiled correctly but after some changes to functions, it somehow shows this errors. It is peculiar that it’s not logging anything.

6

I commented out the YuneVault implementation and it was compiling correctly. then I again uncommented the Vault implementation, and the error started popping up again. Thus, it has narrowed down to the Vault.

7

I am coordinating with the team on it. will get back to you soon

8

@eesheng, the issue was that the contract had multiple methods with the same name total_supply. One from the SRC20 and other from the YuneVault. I renamed one of the method to total_supply2 and it worked. Here is the code for the ref. The confusion arose because the compiler was not generating a friendly error.

9

Wow awesome thanks, I think it’s best to include an error log for utilizing same function name.