Basic EOS Programming - Discussion

Quick update on the apparent bug with building a helloworld contract on EOS Studio Web:

Today I don’t get the “Internal Server Error, real status: 500” error message, but when I attempt to build the contract, it is running in a loop and not getting anywhere… I had to delete the project to stop the loop.

Yesterday, I reported the bug (the Internal Server Error one) on EOS Studio’s Telegram and on EOS Studio Community (https://community.eosstudio.io/), let’s see if it helps…

In the meantime, I am moving on from EOS 101 to EOS 201 as suggested.

See you guys :slightly_smiling_face:

2 Likes

Awesome sir! please let us know what the EOS Studio’s Telegram Community reply to you about that issue.

Really appreciate your help. :smiley:

PD: if you want, just watch how to install the Nodeos & Cleos categories on the EOS 201, after you figure how they work, you can go back to EOS 101 but instead of using the EOStudio, use your local Nodeos & Cleos instead. Here you can find some useful tutorials that i made for myself when i was learning EOS. EOS Tips/Tweaks/Tutorials.

Carlos Z.

2 Likes

Good news, the EOS Studio admin on Telegram announced they fixed the build issue. @filip @ivga80 @thecil

I managed now to build the helloworld contract (and the hellotable contract in a subsequent episode (in Tables Programming)).

@chaneltiana @franky You may want to have a look and build again, it might work for you as well.

I just have an issue with deploying the helloworld contract. I get the following error message: Unknown action hi in contract xyz (xyz stands for my contract name). However, I was able to deploy the next contract in the course, hellotable. I will keep looking for the solution :slightly_smiling_face:

By the way, does anybody know what “ricardian” means (“ricardian clause file”, “ricardian contract”)?

1 Like

YES, excellent sir! :partying_face: I try it myself and EOStudio is completely working again! Thank you for your effort, really appreciated!

Ricardian clause file is a programming agreement that is used on the EOS constitution to en-law all developers to play by defined rules in order to not harm the network.

You can read them here: EOS User Agreement.

Also here you can read more about them to have a better understanding: What are Ricardian Contracts? A Complete Guide.

Carlos Z.

1 Like

Hey swisscrypto!

Beschte dank, jetzt funktionierts! :slight_smile:

Ciaao

1 Like

Hey franky!

Yes, building is working now!

Are you Swiss German??

See you!

Blockchain &Bitcoin 101, Ethereum 101, C++, Javascript, Trading& Technical Analysis, Business Masterclass

But I have another problem. I am running an online version on Windows (Cloud) and I am not able to create an new account. I only use small letters but no name works. The create button is hidden and gets not visible to click. Doesn´t work with Firefox and Brave Browser and Chrome. When I click on the local I am also getting no information about blocks (There is the message blocks info not available). What is the problem here? AntiVirus?

Hello sir, could you please be a little more detailed? maybe some screenshots will help us to understand better the issue that you are facing.

Did you mean on EOStudio? are you logged in with your github account?

If you have any doubt, please let us know so we can help you! :slight_smile:

Carlos Z.

Yes, on EOStudio. Below you find a screenshot. I am logged in with a github account. I created a new one!

@KryptoDr
Ok let me see if i understand it well, you cannot create account when you try to run EOStudio locally right (this probably would not work if you do not have a Local Node running on the machine).

You may want to try to change it to “Network: Cloud”, remember that EOStudio use the testnet, they are running their own testnet node to made it work properly for the users.

image

If you choose there the “custom” option, you have to configure your self a local NODEOS node along with other configurations inside the EOStudio configs, so i advice to just use Cloud network instead.

PD: Could you describe how are you using a online version on windows (cloud), did you mean your own VPS?

If you have any doubt, please let us know so we can help you! :slight_smile:

Carlos Z.

Sorry for my bad description. I am using https://app.eosstudio.io/ and I am logged in via my github account which I created for this course. I am connected to the Network Cloud you described in your post. My notebook is running on Windows 10. I am not using it locally. Thanks for your time and answer.
Below a screenshot that I am using the Cloud network

Ok, I try it myself and im getting the same error, the “create” button does not activate.

  • I know an account should be MAX 12 letters, still not working.
  • different name than bob, like bobkryptodr12, not working either.

I will contact the EOStudio telegram community to see if there is a problem related to this.

In the meantime, I advice: continue the course if you want to (or you feel up to the challenge), try to understand really deep how to install Cleos & Nodeos (filip explain it with more detail in EOS 201). Because right now it looks like is a problem with EOStudio.

PD: if you want, just watch how to install the Nodeos & Cleos categories on the EOS 201, after you figure how they work, you can go back to EOS 101 but instead of using the EOStudio, use your local Nodeos & Cleos instead. Here you can find some useful tutorials that i made for myself when i was learning EOS. EOS Tips/Tweaks/Tutorials..

I will let you know any reply that EOStudio community gave to me.

If you have any doubt, please let us know so we can help you! :slight_smile:

Carlos Z.

Hi all,

I have not been on here in the last week due to finals.

I have been able to solve my last problem that I mentioned in this chat; however, now I have a new problem. Once my project is built, I can not deploy it. I saw that @swisscrypto had the same problem. Were you able to find a solution? Please let me know, thank you!

I’m still waiting for an answero from EOStudio team. The post above your last reply is an advice if you feel up to the challenge. :slightly_smiling_face:

Still, i will be here to help you.

Carlos Z.

Hi @chaneltiana,

While we are waiting for an answer from EOS Studio team:

Is it the helloworld project you want to deploy?

Are you on Windows, Mac or Linux? Are you using EOS Studio Web or the local version?

Hi @swisscrypto,

Yes, the helloworld project is what I would like to deploy, and I am using the EOS Studio Web on Windows

1 Like

Cool! I am using EOS Studio Web on Windows as well, so we can easily compare.

Yes I encountered an issue nine days ago, and the EOS Studio team fixed the building issue. Five days ago, building and deploying the helloworld contract worked for me.

I just attempted to build it and deploy it again today: I encountered the “Internal Server Error, real status: 500” error again, but still a messaged popped up saying that the contract was successfully built (not sure it was really built because it was very quick), so I tried to deploy it, but it failed (“Deploy Failed”, “Failed to fetch”). Is it the same message that you get?

Here is the helloworld.cpp code that I have:

(The helloworld.hpp file is empty.)

Do you have the same code in helloworld.cpp?

Yes, I have the same exact code, and I am getting the same message when deploying. Not too sure of other ways to resolve the issue

2 Likes

@swisscrypto & @chaneltiana, the issues is probably directly from the EOStudio, the EOStudio version of windows is just a direct access to the same webpage, also you could try to run your own local node in order to use it instead the cloud node from EOSstudio, but the process could be a little complicate:

If you really want to continue over the course i can try to help you, but remember that could be complicated and you will need a decent PC for it, thats why i prefer to send you guys through the EOS 201 section of Nodeos & Cleos setup that install the EOSstudio locally, because you dont neet to have a powerfull PC and at the end you will have to learn how to deploy your own node.

Documentation to install EOSstudio locally:

You can follow those guides to deploy your own EOSstudio locally, or you could watch the EOS Programming 201 / Categories / Setup / System Requirements to install your own Nodeos & Cleos in a VM to later used has a solution for the issue with EOSstudio. Then you will be able to continue over the EOS 101 & 201 with the advantage that you finish one of the categories and later used for the next categories. Is up to you guys.

Still i will be here to help you with everything i can. :muscle:
Remember you can find some useful tutorials that i made for myself when i was learning EOS. EOS Tips/Tweaks/Tutorials..

If you have any doubt, please let us know so we can help you! :slight_smile:

Carlos Z.

2 Likes

@swisscrypto
Yes…you too?

1 Like