Redis zombies in Wing Console

[skorfmann]

I tried this:

bring cloud;
bring ex;
bring util;

let queue = new cloud.Queue();
let redis = new ex.Redis();

queue.setConsumer(inflight (message: str) => {
  redis.set("hello", message);
}, timeout: 3s);

test "Hello, world!" {
  queue.push("world!");

  let found = util.waitUntil((): bool => {
    log("Checking if redis key exists");
    redis.get("hello") != nil;
  });

  assert("world!" == "${redis.get("hello")}");
}

and run wing it in the same directory

This happened:

For each invocation of wing it, two redis containers are started. When stopping the the console, both redis containers are still running.

1st invocation

2nd invocation

I expected this:

All supporting processes / containers for the Wing console being stopped along with the console itself

Is there a workaround?

kill the docker containers manually

Component

Wing Console

Wing Version

0.24.31

Node.js Version

v18.16.0

Platform(s)

MacOS

Anything else?

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[staycoolcall911]

Just noticed I had 168 docker containers running on my machine 😄
Didn't affect my laptops performance much.
Let's prioritize that as p2.

[ekeren]

moved to p1

[monadabot]

Congrats! 🚀 This was released in Wing 0.25.7.