Ethereum: The Fate Record no longer works for the Lib folder contracts
As a developer, it is not uncommon for you to find problems with registration and cleaning tools when writing smart contracts. In this article, we explore a problem that has been reported by several users, which makes the registration of FaceLera Faclice about the contracts stored in Liber Board.
Background
Foundry is a popular development tool used to test and clean smart contracts from Ethereum. Its registration feature allows developers to view the records of contract executions, helping cleaning and evidence. However, recent updates have made a change that could cause problems with “contracts stored in Liber Board.
The problem
The problem is how the foundry handles registration when it performs evidence in the smart contracts stored in the “lib” directory. More specifically, the registration features do not seem to be performed properly, which does not result in the registration output.
Symptoms
To diagnose the problem, several users have seen the following symptoms:
- No registration exit by running Fuzz tests in the contract code in the
lib/folder.
- The increase in the configuration of verbosity is no different (for example,
-v,-v, etc.).
- The verbosis level of up to -8 is tested.
Steps to reproduction
Follow these steps to reproduce the problem:
- Create a new Ethereum project with a device such as truffles or remix.
- Write a simple contract in the
lib/directory (such asHelloworld.sol) and reverse the” trufa translation “.
- Complete fuzz tests in your contract code using the casting, for example, “Foundry Test – -Target = Lib/Helloworld.Test”
- Check the console output for any registration message.
Solutions
To solve the problem, you can try the following solutions:
* Refresh the casting : Be sure to run the latest version of Foundry. You can check the updates on the Foundry website and download the update package.
* Check the verbosity configuration : Increase the level of verbosity to a higher value (such as -3 or -2) and see if this makes the difference. However, keep in mind that this can obscure other problems of registration features.
* Use the -debug flag : Try to use the` ‘
* Create a personalized registration output control : You can create a customized registration output control for the foundry to configure the registration behavior. This may include modification of the contract code and the foundry configuration.
Conclusion
The problem of registration of the contracts stored in “Lib” is a confidential problem that requires problem solving efforts. Following these steps, you must determine and solve this problem. Remember to update your foundry, increase the verbosis configuration (if any), or try individual registration managers to make the contract code work with the foundry registry.
More sources
- If you experience problems with the foundry of the foundry on another platform, contact the Future Community Forum to get more help.
- For further information on the development of Ethereum and testing smart contracts, I suggest that you consult the official Ethereum documentation and development resources.