Async /run does not work when testing locally

[abaybektursun]

Describe the bug
When I create a handler runpod.serverless.start({"handler": async_generator_handler})
Only http://localhost:8000/runsync triggers async_generator_handler
However when posting against http://localhost:8000/run async_generator_handler is not triggered. Just returns

{"id":"test-20023617-4048-4f73-9511-8ae17a1ad7a5","status":"IN_PROGRESS"}

But nothing happens in the backend

To Reproduce
Steps to reproduce the behavior:

1. Implement async handler
2. Start the local server

runpod.serverless.start(
    {
        "handler": async_handler
    }
)

3. Do a request: curl -X POST -H "Content-Type: application/json" -d '{"input":{}}' http://localhost:8000/run
4. Observer how async_handler is not triggered

Expected behavior
async_handler should be triggered.

Desktop (please complete the following information):

• OS: Ubuntu 23
• Version: Runpod python SDK: 1.6.2

Also posted in Discord support: https://www.answeroverflow.com/m/1219122522612830279

[discordianfish]

@justinmerrell Is there a timeline to fix this? It would make local development and testing so much easier if I could use async / status locally. Just storing the job status in memory would be sufficient.

[discordianfish]

Hrm maybe I'm missing something because from looking at the code, it seems that it should actually:

• add jobs:

  runpod-python/runpod/serverless/modules/rp_fastapi.py

  Line 292 in f6971a8

  job_list.add_job(assigned_job_id, job_request.input, job_request.webhook)

• and return them on status:

  runpod-python/runpod/serverless/modules/rp_fastapi.py

  Line 331 in f6971a8

  stashed_job = job_list.get_job(job_id)

But it seems that when I try to get the job status it always returns:

"status": "FAILED",
"error": "Job ID not found"

[geovanisouza92]

But it seems that when I try to get the job status it always returns:

"status": "FAILED", "error": "Job ID not found"

Same here. My guess it's removing the jobs from memory 🤔

[xerdink]

also have the same problem

[discordianfish]

Looks like it removes the job here:

runpod-python/runpod/serverless/modules/rp_fastapi.py

Line 388 in f6971a8

job_list.remove_job(job.id)

I don't get why.. looks like on the first request its still there and then gets removed by this.

[petem24]

Same issue here. Very annoying

[petem24]

@justinmerrell any timeline on this? It makes local development extremely frustrating

[Ostefanini]

Looks like calling the POST/status/{job-id} execute the job

[chemaguerra]

Same problem here. I receive {"detail":"Not Found"} when testing /run locally.