Internal server error, CodeRunner deployment.

General
1

Hi guys,

I’m writing you in order to report a problem that I have during my server code deployment, via CodeRunner.

While I’m trying to upload the servercode, by running ./Coderunner.sh in the console, I have the following error:

Internal server error with id 6569B0A5-D17E-BEAA-FF3E-48623B6EE400

I really don’t understand what’s the problem.
Could you help me to resolve such an issue?

Thank you

2

I’ve been getting this a lot today too but I just downloaded a new copy of CodeRunner from the Code Generator screen and the problem went away.

3

Thanks for you feedback.
Yes, we have updated our servers today.

4

Thank you Simon, so kind of you!!
It fixed all my problems.

I really don’t understand why it happens, I would like to understand this I order to fix similar problems in the future.

5

That would be nice if you can create a section on the website where we can get such informations.
In this way the developers know when the server is updating.

6

The updated code runner SDK is also now available on our website (version 3.0.15)

7

Can there be some kind of e-mail notification / subscribe list for this kind of thing so when it happens we’re not left confused and searching for an appropriate issue in support to work out what happened?

8

When there is an update, we notify every single support topic that’s waiting for a fix in a given update.

9

ok, but I didn’t have an issue until after the release was made when I came to deploy a service update and it didn’t work because i was using code runner 3.0.12. i’ve updated to 3.0.16 now and the deploy worked.

is there something i can subscribe to so i get an e-mail each time a new version of code runner is released, or perhaps just get an e-mail when the new version addresses breaking changes so the previous version will no longer work?

perhaps just checking for an update should be my first port of call when something doesn’t work…

10

I am afraid we’d be spamming a lot of people if we were to notify when we update any of the 5 SDKs, 3 code runners, the core service and 3 standalone packages (that’s essentially 12 products). I suggest checking for an update if you run into a problem.

Regards,
Mark