The poller monitoring a test initiated by field selection can be cancelled when the selected binding changes.
Reproduction Steps
Initializing the field selection table:
Enter the edit workflow for a materialization with two or more bindings.
Change the selected binding in the Source Collections section of the form while the field selection table is still in a loading state.
Observe that the field selection table indefinitely remains in a loading state for all bindings. Inspecting the API calls made in the workflow reveals that the poller responsible for monitoring background test progress was cancelled when the selected binding changed.
Refreshing the field selection table:
Enter the edit workflow for a materialization with at least one binding.
Add a binding to the materialization.
Click the Next CTA.
Click the field selection Refresh button in the Source Collections section of the form.
Change the selected binding while the field selection table is still in a loading state.
Observe that the field selection table indefinitely remains in a loading state for all bindings. Inspecting the API calls made in the workflow reveals that the poller responsible for monitoring test progress was cancelled when the selected binding changed.
Expected
The field selection table should be initialized if the test succeeded in producing a built_spec and validation object. In the event of a failed test, the table should enter an idle state and the error should be handled appropriately. Additionally, the client state should enter an idle state once the test concludes.
Screenshots
Include a screenshot of what you saw when the bug happened.
Desktop
OS: Windows
Browser: Version 127.0.6533.90
Additional Context
All tests are initiated by the top-level field selection component (i.e., FieldSelectionViewer, src/components/editor/Bindings/FieldSelection/index.tsx). This component is unmounted whenever the selected binding changes.
Bug
The poller monitoring a test initiated by field selection can be cancelled when the selected binding changes.
Reproduction Steps
Initializing the field selection table:
Enter the edit workflow for a materialization with two or more bindings.
Change the selected binding in the Source Collections section of the form while the field selection table is still in a loading state.
Observe that the field selection table indefinitely remains in a loading state for all bindings. Inspecting the API calls made in the workflow reveals that the poller responsible for monitoring background test progress was cancelled when the selected binding changed.
Refreshing the field selection table:
Enter the edit workflow for a materialization with at least one binding.
Add a binding to the materialization.
Click the Next CTA.
Click the field selection Refresh button in the Source Collections section of the form.
Change the selected binding while the field selection table is still in a loading state.
Observe that the field selection table indefinitely remains in a loading state for all bindings. Inspecting the API calls made in the workflow reveals that the poller responsible for monitoring test progress was cancelled when the selected binding changed.
Expected
The field selection table should be initialized if the test succeeded in producing a
built_specandvalidationobject. In the event of a failed test, the table should enter an idle state and the error should be handled appropriately. Additionally, the client state should enter an idle state once the test concludes.Screenshots
Include a screenshot of what you saw when the bug happened.
Desktop
Additional Context
FieldSelectionViewer, src/components/editor/Bindings/FieldSelection/index.tsx). This component is unmounted whenever the selected binding changes.