This has now been fixed in duckdb/duckdb#16397. Release version 1.2.1 includes the fix. The issue was two identically named macros were conflicting. The solution was to rename one of them.