Is it normal for Sprites to get bricked constantly?

1

Just started using sprite.dev. Everything is great except that my sprites seem to constantly get put into an unreachable state. I have tried significantly reducing the network usage and memory usage of my tasks (very time consuming btw), and they still constantly get bricked.

Not really sure what to do, happens frequently. I’m basically just trying to run some agents to do dev work on sprites. My mac handles multiple of these types of sessions at once no problem, so I don’t think what I’m doing is anything crazy.

Is there something I’m doing wrong? No idea how to deal with this or how to get this to work. I’d prefer sprites just worked because the API is very good but it just seems to brick all the time for me

2

I don’t know the cause, but if you get one unbricked, maybe you can have a look in syslogs to see if there is some relevant grumbling in there.

Also, are you on the default 8GB RAM allocation, or the optional 16GB? I wonder if it borks due to an OOM error.

3

I just came into this forum because one of my sprites stopped responding, and even the restart button is not working.

Stuck in:

xxx's machine is stopping, so restart was refused. Please try again in a moment.

Update: it is working now, it was dead for ~5-10 minutes.

5

Sadly I’ve given up on sprites for now due to reliability issues. Super promising idea. Also I found the IO performance was underpar for workloads that have a lot of small files eg. node_modules. Happy to take another look at the next update!