Context is preserved between two runPromise calls

Running the command in sequence preserves the context. I would expect that each call would create a clean context, like is the case with run

Is that normal behavior?

    await namespace.runPromise(async () => {
        set("foo", "bar");
        const foo = get("foo");
        console.log("VAELU", foo);
      })
     
    await namespace.runPromise(async () => {
      const foo = get("foo");
      console.log("Value", foo); // Here is prints "bar" instead of undefined
    });

[samwyma]

Just come across this issue, too. Changed to using runAndReturn instead, and that seems to have fixed it for me. Should just be a literal swap out since it will be returning the promise of your async methods

[yagodorea]

I’m dealing with something like this. I have a system that receives HTTP requests and also subscribes to Pubsub topics, it creates a new context for each HTTP request (with ns.run()) and every Pubsub message (with ns.runAndReturn()).

Each transaction is supposed to generate a new transactionId (UUID), unless it is sent over by headers or in the message metadata, in that case a new context is created with but with the received transactionId, so we can trace the related transactions over our microservices.

The problem is we’re seeing the same transactionId being repeated a lot across thousands of different unrelated requests, and we can only assume it’s an issue with cls-hooked (and not the uuid generation lib).

I don’t know if it’s related to this issue, because I’m not using the ns.runPromise(), but it might be… I’m not yet able to consistently reproduce it, and as soon as I can, I’ll post here or create a separate issue.