QwikDev / QwikDev/qwik

[🐞] [V2] useVisibleTask$ doesn't get re-triggered if it modifies a tracked signal as part of the task.

Open
#8,656 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug runtime
Dominant language
TypeScript
Stars
22.1k
Forks
1.4k
Avg merge
1d 10h
Merged PRs (30d)
52

Description

Which component is affected?

Qwik Runtime

Describe the bug

If Im tracking a signal and changing it as part of a use visible task, it won't get re-triggered.

** Notice that useTask$ works as expected, or at least it seems to be working, maybe its just because it runs at the server first.

Reproduction

https://qwikdev-build-v2.qwik-8nx.pages.dev/playground/#f=7VbbCoJAEP2VwZcsUtEHI8n%2Bog%2BIvCSJQgQRtv%2Fe2d1ZW8UeJHrLB1lnZnfGYfacYw1NvImnhmY9xjRl0HT8pUxh%2Fq9KtKY%2F0w1RmeWLbOfOaVrvdD42Ze7Qkxxe7l3LrraPcdjtmK1Fn520xUUOtYWoKkh%2B%2BbjaAO00TSnU8yGfYEW8OjTMP4omQWxgANCFYSVl5VCoADBQARKGFSBnMB4kqw23lu7t9QKElGJDUapvNq8CkzqwqNfqH%2FtItskUTZH%2BF%2BURS15PBAjKa%2FCGOUd2ug8xfeVIvMUaQwFNBsgpHwktMoYwr8rqfCETzZWd1PVFibcE1YUkyhnJxENV%2Bhlmwq0lpOfAzGBy%2FyDzC5B5AQ

Steps to reproduce

enter the url, see It says "no change".
If you uncomment the stuff I did there with the set timeout, and comment out the assignment out of the settimout.. you will see the correct behavior, e.g it will say "changed" as expected.

System Info
-
Additional Information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Qwik playground reproduction and verify the "no change" result using useVisibleTask$. Compare it with the stated useTask$ behavior and the setTimeout variant. Done means changing a tracked signal inside useVisibleTask$ causes the task to re-trigger as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.