[🐞] v2 Signal attribute is not updated during async task

[GrandSchtroumpf]

Which component is affected?

Qwik Runtime

Describe the bug

const counter = useSignal(0);
useVisibleTask$(async () => {
  await new Promise(res => setTimeout(res, 1000));
  counter.value = 10;
  await new Promise(res => setTimeout(res, 1000));
  counter.value = 100;
});
return <p>{counter.value}</p>;

In v1, I would see 0, 10, 100
In v2, I see 0, 100

Reproduction

https://stackblitz.com/edit/github-cwknwkth?file=src%2Froutes%2Findex.tsx

Steps to reproduce

Run this code in v1

const counter = useSignal(0);
useVisibleTask$(async () => {
  await new Promise(res => setTimeout(res, 1000));
  counter.value = 10;
  await new Promise(res => setTimeout(res, 1000));
  counter.value = 100;
});
return <p>{counter.value}</p>;

see 0, 10, 100

Run migration script: pnpm qwik migrate-v2

Run code again:
see 0, 100

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor
    Memory: 16.52 GB / 31.18 GB
  Binaries:
    Node: 22.8.0 - ~\.nvm\versions\node\v22.8.0\bin\node.EXE
    npm: 10.9.0 - ~\.nvm\versions\node\v22.8.0\bin\npm.CMD
    pnpm: 9.10.0 - ~\.nvm\versions\node\v22.8.0\bin\pnpm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.65)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    typescript: 5.5.4 => 5.5.4
    undici: 6.19.0 => 6.19.0
    vite: 5.3.5 => 5.3.5

Additional Information

No response

[wmertens]

@Varixo we may have to run chores with higher priority while tasks are async running Wout.

…

On Wed, 29 Jan 2025, 17:06 François, ***@***.***> wrote: Which component is affected? Qwik Runtime Describe the bug const counter = useSignal(0);useVisibleTask$(async () => { await new Promise(res => setTimeout(res, 1000)); counter.value = 10; await new Promise(res => setTimeout(res, 1000)); counter.value = 100;});return <p>{counter.value}</p>; In v1, I would see 0, 10, 100 In v2, I see 0, 100 Reproduction https://stackblitz.com/edit/github-cwknwkth?file=src%2Froutes%2Findex.tsx Steps to reproduce Run this code in v1 const counter = useSignal(0);useVisibleTask$(async () => { await new Promise(res => setTimeout(res, 1000)); counter.value = 10; await new Promise(res => setTimeout(res, 1000)); counter.value = 100;});return <p>{counter.value}</p>; see 0, 10, 100 Run migration script: pnpm qwik migrate-v2 Run code again: see 0, 100 System Info System: OS: Windows 11 10.0.26100 CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor Memory: 16.52 GB / 31.18 GB Binaries: Node: 22.8.0 - ~\.nvm\versions\node\v22.8.0\bin\node.EXE npm: 10.9.0 - ~\.nvm\versions\node\v22.8.0\bin\npm.CMD pnpm: 9.10.0 - ~\.nvm\versions\node\v22.8.0\bin\pnpm.CMD Browsers: Edge: Chromium (129.0.2792.65) Internet Explorer: 11.0.26100.1882 npmPackages: typescript: 5.5.4 => 5.5.4 undici: 6.19.0 => 6.19.0 vite: 5.3.5 => 5.3.5 Additional Information *No response* — Reply to this email directly, view it on GitHub <#7296>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAANNFTJF2IB2KTYEPKTHB32ND4BJAVCNFSM6AAAAABWDG5GZGVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAYTQNRTGY3DCMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[wmertens]

playground repro: https://qwikdev-build-v2.qwik-8nx.pages.dev/playground/#f=Q0o0xuYG2BKNDqL2BTORizdY4CuhR5YSkQkKEjrgQh2YXW0RVmkYAN2ngFGcQgoShH4FzAJfA1hggqQRlRVIREfB0MDAQBNsKMhasIV6wDwMLJ1tgXIQcSoZBjYNlCOQc0w1irpaWLYZzTRDL9MAAA