When I have a test set synced in the playground and I commit the prompt, I expect the test set to stay connected. Instead the playground silently drops to a local test set: the header dropdown flips from the test set name back to "Test set", and the "N unused testcase columns hidden" footer disappears from every row, taking those values out of view.
Creating an app from a draft prompt does the same thing, since it is the first commit.
Steps to reproduce:
- Prompts > Create new > New prompt > Completion. The draft prompt references only
{{country}}.
- Test set > Connect test set. Pick a test set with columns the prompt does not use (for example
completion_testset with country, guidelines, correct_answer). Select all rows, Load Selected.
- Each row shows a "Synced from testset" badge and a "1 unused testcase column hidden because the prompt does not reference them." footer.
- Click Create and create the app. The page lands on the new app's playground.
- The header now shows plain "Test set" (unsynced). The badges and unused-column footers are gone. Only the referenced column values survive.
The same happens on an existing app: connect the test set, edit the prompt, Commit as a new version. The sync drops on every commit.
Follow-on data loss: after the unsync, a page reload saves the rows into the URL snapshot as a local test set. The unused columns then lose their protection as test set data, and the next Run deletes them from the rows. The symptom from #4647 comes back through this path.
Reproduces on the dev deployment (v0.103.0); the same code runs on cloud.
When I have a test set synced in the playground and I commit the prompt, I expect the test set to stay connected. Instead the playground silently drops to a local test set: the header dropdown flips from the test set name back to "Test set", and the "N unused testcase columns hidden" footer disappears from every row, taking those values out of view.
Creating an app from a draft prompt does the same thing, since it is the first commit.
Steps to reproduce:
{{country}}.completion_testsetwithcountry,guidelines,correct_answer). Select all rows, Load Selected.The same happens on an existing app: connect the test set, edit the prompt, Commit as a new version. The sync drops on every commit.
Follow-on data loss: after the unsync, a page reload saves the rows into the URL snapshot as a local test set. The unused columns then lose their protection as test set data, and the next Run deletes them from the rows. The symptom from #4647 comes back through this path.
Reproduces on the dev deployment (v0.103.0); the same code runs on cloud.