compiler api doesn't work in deployment mode

[haughty tiger]

Try to provide all relevant information in your post concisely. This includes:

• Include all relevant information in your post: https://stackoverflow.com/help/how-to-ask
• Provide any steps or things you may have already attempted to try to solve the problem at hand

[lavish cloud]

I've been working on an API in Go that compiles and runs user-provided code. It works perfectly fine in development mode, but when I deployed it on Render, the /compile route doesn't seem to work. However, all other routes are functioning as expected.

[lavish cloud]

is this enough information ?

[haughty tiger]

i still have no idea what "doesn't seem to work" actually means, nor any example input. what's the input you're providing? what's the output? what is the expected output? what have you tried?

[lavish cloud]

https://pastebin.com/kUmE7ay1

[errant jetty]

we have https://play.go.dev , make your runnable example there

[lavish cloud]

{
    "code": "package main\n\nimport \"fmt\"\n\nfunc main() {\n\tfmt.Println(\"Hello, world Cool!\")\n}"
}
``` suppose this is the input so end output will be just a result string "Hello, world Cool!

which works fine in local server but if i test it on deployed server it always get stuck with a timeout warning

I think it can't install any package

@errant jetty

[errant jetty]

yes if you are compiling your code first time, it will be a little bit slower.

just wait

[lavish cloud]

it doesn't even work

always throw timeout error

[errant jetty]

what error

there are a lot timeout errors, which one do you mean

[lavish cloud]

Error: Timeout was reached

[errant jetty]

well so as hhhapz said, you are not providing enough informations

read the link he sent

[lavish cloud]

I already provided the information I had

[errant jetty]

okay, have you tried run the code on the server from shell?

[lavish cloud]

this is running on a hobby account

[errant jetty]

so that's why

[lavish cloud]

for testing purposes

[errant jetty]

you need pay for better server

then you don't get timeout

[lavish cloud]

that's a weird answer but nvm

[errant jetty]

It's not go complier issue, but your deploy server's problem. Your server does not want you to compile code there

find another one which have higher time limit or pay for higher limit