EtherReum: Remx Idi Fif Freeze on Contracting Mistakes Call
Suppose that Simith Etherem developers and use popular development, Remix goes, numerous users will have reports on the problem with the freezes wee go freezes of stama contracts. This problem is frustrated, special for those who are still learning the intake of smart contracts.
What is it:
When the agreement calls Orota function, there was a time that a diet casts a mistake. We discovered the case, this was not resurrected by Clall, and it goes freezing in response to a certificate of execution. The freezing of OCCUP is going to use with the technical call of the “jerk happening”, which allows for asynchronous enforcement of the code. Howver, the wax of smooth errors (watching the contract error), goes freezing to it to cope with unexpected events.
* Influence:
This problem with the importance of delay in developing and eliminating errors, it is difficult to identify identity and solve problems in smart contracts. The developers rely on features for removing the Remix mistakes, which can be disrupted by freezing behavior. Furthermore, incorrect errors can be confusing and frustrating wet to solve the problem.
* You are:
Fortunately, there is a manner for this problem. In an unfavorable position when executing a contract to return error, use the following clip to a remix configuration file (usually marble.Json ‘):
`S.
{
"Events": {{
"Call": {{
“Enable”: false,
Error handling ": matte
Iche
Iche
// ... other configurations.
Iche
` S.
The events disappear when they make mistakes in mistakes, developers are transmitted by behavior and continue to work on their marks. In addition, this repair should be carefully determined, making it to give developers a trunkhost problems.
*Conclusion:
Although remix is going freezing with mistakes uncomfortable for some essera, simply a change in configuration can change the problem. Understanding when events work and disappear from it, developers can provide effort and frustrating reduction caused by this limit.