Connect heartbeat if state created in render. Also fix config cleanup bug #8407

[freddyaboulton]

Description

Noticed a bug where the heartbeat was not established if a state variable was created in a render.
In the process of fixing that, I noticed that components were not being removed from the old config. The rendered_in key is in props, not the top level component config.

🎯 PRs Should Target Issues

Before your create a PR, please check to see if there is an existing issue for this change. If not, please create an issue before you create this PR, unless the fix is very small.

Not adhering to this guideline will result in the PR being closed.

Tests

1. PRs will only be merged if tests pass on CI. To run the tests locally, please set up your Gradio environment locally and run the tests: bash scripts/run_all_tests.sh

2. You may need to run the linters: bash scripts/format_backend.sh and bash scripts/format_frontend.sh

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
🦄	Changes	detecting...

---

Install Gradio from this PR

pip install https://gradio-builds.s3.amazonaws.com/24c3ef3d7b12a35a60568aa64297602b7e1436ba/gradio-4.31.5-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@24c3ef3d7b12a35a60568aa64297602b7e1436ba#subdirectory=client/python"

Install Gradio JS Client from this PR

npm install https://gradio-builds.s3.amazonaws.com/24c3ef3d7b12a35a60568aa64297602b7e1436ba/gradio-client-0.19.4.tgz

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
@gradio/client	patch
gradio	patch

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Connect heartbeat if state created in render. Also fix config cleanup bug #8407

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[aliabid94]

Would it be a bad idea to remove this complexity entirely and just always maintain a heartbeat? Now the configs can change, I feel like it's a lot of complexity to keep track of whethers there's any state variables to track, and it doesn't seem like we'd consume a lot of resources by just always having a heartbeat. (Sorry should've suggested this earlier)

[freddyaboulton]

My concern there is running into the 6 concurrent connection limit if you open multiple tabs of the same demo.

[aliabid94]

we could use long polling then instead for the connect heartbeat, no? e.g. we send a POST request every 10 min, and if we haven't received anything in 30 min for an app we clear it out.

I think this would cut down complexity a lot, and in the current approach we still could hit the 6 connection limit on any app that has state.

[aliabid94]

LGTM!

[freddyaboulton]

Thanks @aliabid94 !