After upgrading to TS v10.5.0.cl-148, cs_tools tools scriptability export throws an error on hundreds of TS objects

[bmofkn]

Our TS cluster was upgraded on Thursday, Jan 9, 2025 from v10.4 to v10.5. We are also using cs_tools v1.5.12. Ever since upgrading our cluster, the following commands fail on hundreds of TS objects in our cluster:

cs_tools tools scriptability export --include-types liveboard --include-system-content ./ --config prod_ts

Typical liveboard extract error message:
ERROR - PinboardEDocProto.__init__() got an unexpected keyword argument 'ordered_chips' supplied data does not produce a valid TML (Liveboard) document

cs_tools tools scriptability export --include-types table --include-system-content ./ --config prod_ts

Typical table extract error message:
ERROR - LogicalTableEDocProto.__init__() got an unexpected keyword argument 'properties' supplied data does not produce a valid TML (Table) document

cs_tools tools scriptability export --include-types worksheet --include-system-content ./ --config prod_ts

Typical worksheet extract error message:
ERROR - WorksheetEDocProtoQueryProperties.__init__() got an unexpected keyword argument 'sage_config' supplied data does not produce a valid TML (Worksheet) document

Any ideas on a fix or workaround? Thanks!

[boonhapus]

This is expected @bmofkn (see: thoughtspot_tml#25 & v2.2.0+) -- the TML spec evolved to include some new mandatory parameters. Can you run cs_tools self sync and then try your flow again?

[bmofkn]

Thanks for the quick reply @boonhapus! I swear I searched for "ordered_chips" in the Discussions area and didn't find a reference... next time I'll search Issues as well 🙂.

I ran cs_tools self sync and re-ran my daily script... 100% error free 🎉. Thanks a bunch!

Quick question: I usually run cs_tools self update every day... should I also be running cs_tools self sync daily?

[boonhapus]

@bmofkn If it works fine without breaking the environment, then there's no harm in it. 😄 Some of the self commands have... unexpected behavior that I've (hopefully, finally) resolved for the 1.6 build that's coming in a week or so.

All it does is run an upgrade thoughtspot_tml command in the virtual environment.