Warning: server timed out after hitting its 5s timeout!

[peterpostmann]

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

yes

Steps to Reproduce

Create a folder on a windows drive from within WSL and setup project there

mkdir /mnt/c/dev
cd dev 
npx create-remix --template remix-run/grunge-stack

-- or --

npm run validate

Result:

✓ Sandbox Started file watcher
Watching Remix app in development mode...
⚠️  Test routes enabled.
⚠️ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠️ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠️ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
⚠️ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!
...

If the project is created in a linux folder (e.g. ~/dev/) it works just fine.

Expected Behavior

Tests run through

Actual Behavior

⚠️ Warning: mnt/c/dev/chess2/server timed out after hitting its 5s timeout!

is repeated forever

[bdegiglioD6]

Did you ever find a solution to this?

[peterpostmann]

I couldn't get it run on a windows filesystem (/mnt/c), but this error didn't occure if run on a linux filesstem (~/)

[gggiovanny]

I'm experiencing the same issue :(

[alexmk92]

Following the Arc documentation, you can configure the execution time of your Lambda handler, here's my app.arc

@app
my-app-id

@arc
env true

@http
/*
  method any
  src server

@static

@aws
timeout 60              <-- default exec time of your handler is 5s, up it to 60 in dev (my prod one is still 5s)
memory 256
concurrency 10          <-- if running in prod, I noticed some 500 errors, upping concurrency fixes this
region eu-west-2

[github-actions]

This issue has been automatically marked stale because we haven't received a response from the original author in a while 🙈. This automation helps keep the issue tracker clean from issues that are not actionable. Please reach out if you have more information for us or you think this issue shouldn't be closed! 🙂 If you don't do so within 7 days, this issue will be automatically closed.

[github-actions]

This issue has been automatically closed because we didn't hear anything from the original author after the previous notice.