-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contract in not compiling in remix #251
Comments
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI am a Python programmer and my skill can leverage into this issue when I deploy contract and interact with contract using Python programming by creating a Python script How I plan on tackling this issueI can approach this issue by creating a Python script that will be used in deploying the contract using Python language using starknet.py also i will be able to interact with the deployed contract also in python. Thank you |
I’m Kevin from Dojo Coding, and I would like to address issue #251 regarding contract compilation in Remix. To resolve this, I would first verify that the correct compiler version is being used. Next, I would analyze the specific error messages to pinpoint the issue, simplifying the code if necessary to isolate the problem. I would also ensure all dependencies are up-to-date and test the compilation in other environments like Truffle or Hardhat to determine if the issue is specific to Remix. @abhi8960git |
Hi @abhi8960git can I work on this ? |
Hey @ShantelPeters! |
@ShantelPeters can you try reproducing this issue, because I believe it should be fixed |
Alright I’ll look into it then @varex83 |
Hello, my name is Kevin and I belong to Dojo Coding. I would like to apply for this issue and help resolve it. I have experience in configuring registries and resolving similar errors, and I believe I can effectively contribute to finding a solution. To address and resolve this issue, I would first analyze the error message to understand its root cause. I would identify the tool or package manager that is generating the problem and review its configuration, specifically the registry URL it is trying to access. If I find that it is pointing to a placeholder or incorrect URL, I would update the configuration to use the correct official registry URL. Additionally, I would check for any environment variables or additional configurations that might be overriding this setting. Once the adjustments are made, I would test the connection again to ensure the problem has been resolved and that the tool is functioning correctly. My approach is based on a systematic solution to ensure that the error does not recur. @abhi8960git |
Hey @KevinMB0220! |
Caused by:
0: failed to fetch registry config
1: error sending request for url (https://there-is-no-default-registry-yet.com/config.json): error trying to connect: dns error: failed to lookup address information: Name or service not known
2: error trying to connect: dns error: failed to lookup address information: Name or service not known
3: dns error: failed to lookup address information: Name or service not known
4: failed to lookup address information: Name or service not known
The text was updated successfully, but these errors were encountered: