Sprite destroy, getting 500s

[siscia]

Hello team,

I am getting 500 when trying to destroy my sprites.

I am not quite sure what is the issue, but I am not able to find anything in the status dashboard.

% sprite destroy acem-eval-20-acem-c10f1e2b
About to destroy sprite acem-eval-20-acem-c10f1e2b

Error: Failed to destroy sprite: API error (status 500)

[fpo3]

Having the same issue

[halfer]

Try adding --debug to your command to see what is happening under the hood.

[siscia]

Tried, mostly for curiosity.

But the logs are all quite useless and they confirm that it is a 500 error server side.

[aezell_fly]

Thanks for reporting this. We pushed a fix out for this last night (EST time in the US). Let us know if it’s still not working correctly.

[siscia]

Thanks Alex,

It is sprites a system I can trust for production or it is still beta?

I see errors coming out of my application, those errors are due to 500 on sprites.

Do I have a dashboard or communication from fly.io that the system was having issues to tell my boss?

The next question my boss will ask is why I chose a system that has issues? And the answer I hope to provide is that sprites rarely has issues and indeed their availability dashboard is almost always green.

Do I have this business assurance?

[halfer]

I’d say it’s still beta. Tell your boss to calm down

(Fly would probably disagree with me, they probably want people to use it for production systems. I personally think its main use-case is prototypes, scratch-pads, and experiments, where high availability does not matter so much).