Skip to content

Bug: useRealtimeRun continues fetching run data after completion in v3.3.5 #1538

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EnriqueSantos-dev opened this issue Dec 6, 2024 · 1 comment

Comments

@EnriqueSantos-dev
Copy link

Provide environment information

System:
OS: Linux 5.15 Ubuntu 24.04 LTS 24.04 LTS (Noble Numbat)
CPU: (16) x64 AMD Ryzen 7 7700 8-Core Processor
Memory: 11.72 GB / 15.20 GB
Container: Yes
Shell: 3.7.0 - /usr/bin/fish
Binaries:
Node: 20.17.0 - ~/.local/share/nvm/v20.17.0/bin/node
npm: 10.8.2 - ~/.local/share/nvm/v20.17.0/bin/npm
pnpm: 9.10.0 - ~/.local/share/nvm/v20.17.0/bin/pnpm

Describe the bug

The useRealtimeRun hook keeps making requests even after the run has been completed, causing unnecessary network load.

Reproduction repo

https://github.com/EnriqueSantos-dev/nextjs-realtime-simple-demo

To reproduce

  1. Copy the contents of .env.local.example, paste them into a new .env file, and populate it with your environment variables.
  2. Update the placeholder project reference in the trigger.config.ts file.

Additional information

2024-12-06.13-58-51.mp4
@ericallam
Copy link
Member

Thanks for the report, will be digging into this on Monday!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants