tree c3546c3adf0a979ef2e187a9d4786be8d99ada56
parent 29496b851fb76652c876fac853de7231a9307b9e
author Jacques Pienaar <jpienaar@google.com> 1680537255 -0700
committer GitHub <noreply@github.com> 1680537255 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkKvanCRBK7hj4Ov3rIwAASr8IAHNDoNh1cu9zxgt6BWekeRfW
 xu4i/yCyXLa4qgQUAP0PBy3C+YcxVoFeFMxQ16KrfH6tz/HX7mO8RLYmOZ8Z5Z0s
 0V5Dd6hWPyPrt368VfHeHU3SI6heDI2yCZLgI7mWIuU4F5Euva9fQ8Ykimrzspog
 PAA77qCTUXTgLRQ4bILCouJWqYIyPcIR5vlTsVnhAOwMV5FCfIqQy4u8GUpUjE1G
 81KaH8l31Ms2U7BRyfcTB3jH0tEuJTFqm6L7dA6c1yZRK1XXkrgXg3+qFujkQURu
 p9AcM7z7vFZhXc01wR547v4ugyjnBFxzi4vScBM+Bp6mWmEgjtuGIQ3Pj2RZZag=
 =D13B
 -----END PGP SIGNATURE-----
 

Fix XLA import path (#12898)

The pipeline wasn't following the route documented post refactoring,
which led to tuples not being handled correctly: the flatten tuple pass
required CF form to operate on and not SCF form.

We can make this a bit more automatic (and we have the tracking bug to
avoid even specifying type here).

This is for the legacy import path.