Error Code 134 on Deploy of Base Repo

[seve]

Have you experienced this bug with the latest version of the template?

Yes

Steps to Reproduce

Initialize project using npx create-remix@latest --template remix-run/blues-stack
run through first steps in README
push to repo
GHA fails to deploy

Expected Behavior

Deploy succeeds without any modifications

Actual Behavior

GHA fails with the following logs:

Error release_command failed running on machine 4d89605f907287 with exit code 134.
Check its logs: here's the last 100 lines below, or run 'fly logs -i 4d89605f907287':
  Pulling container image <OMITTED>
  Successfully prepared image <OMITTED>(4.673965443s)
  Configuring firecracker
  [    0.032823] PCI: Fatal: No config space access function found
   INFO Starting init (commit: 5b8fb02)...
   INFO Preparing to run: `docker-entrypoint.sh bash ./scripts/migrate.sh` as root
   INFO [fly api proxy] listening at /.fly/api
  2024/04/16 00:18:13 listening on [<OMITTED>]:22 (DNS: [fdaa::3]:53)
  Machine created and started in 5.362s
  Setting up swapspace version 1, size = 2 GiB (2147479552 bytes)
  no label, UUID=<OMITTED>
  npm WARN exec The following package was not found and will be installed: prisma@5.12.1
  <--- Last few GCs --->
  [324:0x5453850]     6142 ms: Mark-sweep (reduce) 252.5 (258.2) -> 252.0 (258.7) MB, 122.6 / 0.0 ms  (average mu = 0.570, current mu = 0.271) allocation failure; scavenge might not succeed
  [324:0x5453850]     6269 ms: Mark-sweep (reduce) 253.0 (258.7) -> 253.0 (259.7) MB, 124.4 / 0.0 ms  (average mu = 0.368, current mu = 0.024) allocation failure; scavenge might not succeed
  <--- JS stacktrace --->
  FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
   1: 0xb9a330 node::Abort() [npm exec prisma migrate deploy]
   2: 0xaa07ee  [npm exec prisma migrate deploy]
   3: 0xd71ed0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [npm exec prisma migrate deploy]
   4: 0xd72277 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [npm exec prisma migrate deploy]
   5: 0xf4f635  [npm exec prisma migrate deploy]
   6: 0xf61b0d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [npm exec prisma migrate deploy]
   7: 0xf3c1fe v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
   8: 0xf3d5c7 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
   9: 0xf1db40 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
  10: 0xf155b4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
  11: 0xf17868 v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [npm exec prisma migrate deploy]
  12: 0x1057999 v8::internal::JsonParser<unsigned short>::MakeString(v8::internal::JsonString const&, v8::internal::Handle<v8::internal::String>) [npm exec prisma migrate deploy]
  13: 0x10596b6 v8::internal::JsonParser<unsigned short>::ParseJsonValue() [npm exec prisma migrate deploy]
  14: 0x105a19f v8::internal::JsonParser<unsigned short>::ParseJson() [npm exec prisma migrate deploy]
  15: 0xdf7983 v8::internal::Builtin_JsonParse(int, unsigned long*, v8::internal::Isolate*) [npm exec prisma migrate deploy]
  16: 0x1710839  [npm exec prisma migrate deploy]
  ./scripts/migrate.sh: line 9:   324 Aborted                 npx prisma migrate deploy

(note that the swapfile is set to 2GB in this log, but it fails on the default swapfile size as well)

Related: #170

[mthomps4]

+1 Seeing the same in a fresh clone / Fly setup following the Readme.

[benwaffle]

Swap space now has to be set via the swap_size_mb option in fly.toml - https://fly.io/docs/reference/configuration/#swap_size_mb-option