VM upgrade, 502 error persists, code mystery.

Monday, December 16, 2024

Tried again today, same problem with 502. Not sure what the hell is going on.

I've decided to bite the bullet and upgrade to a better VM. I'm going with:

2 vCPUs
8 GB
100 GB
5 TB
$42/mo

I'm still getting the 502. Seems like the start endpoint isn't getting called. Not sure when this stopped working, but I'm very confused.

I did a bunch of stuff, but ultimately no code changes, and it works now. No idea why. Very frustrating.

The test running seems to be broken though, as sometimes I get 500 response for no obvious reason.

I do see this, though: Failed to execute command: signal: killed. Makes me wonder, is something killing the execution of the command before it finishes?

When running the chapter 2, I get this:

/usr/share/dotnet/sdk/8.0.403/NuGet.targets(465,5): error MSB3202: The project file "/tmp/tsetasdtasdt/testing-in-dotnet/Shop.Tests/Shop.Tests.csproj" was not found. [/tmp/tsetasdtasdt/testing-in-dotnet/Shop.sln]

Seems like the whole idea of just running dotnet test inside the directory will not work. I will need to explore how dotnet test decides which projects to restore and see how to make it work for my use case.

The performance seems to be great though (when it works). I hope I can sustain this with more users.