Commit 0ba3089
committed
fix(model): raise ConfigError for empty time_column tuple
An empty time_column tuple, e.g. `INCREMENTAL_BY_TIME_RANGE (time_column ())`,
parsed into an empty exp.Tuple and TimeColumn.create indexed v.expressions[0]
without checking, so it surfaced a bare IndexError with no config context
instead of the ConfigError already used for the other empty/invalid
time_column inputs. Guard the empty tuple and raise the same
"Time Column cannot be empty." ConfigError.
Signed-off-by: Anas Khan <83116240+anxkhn@users.noreply.github.com>1 parent b0bc176 commit 0ba3089
2 files changed
Lines changed: 17 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
341 | 341 | | |
342 | 342 | | |
343 | 343 | | |
| 344 | + | |
| 345 | + | |
344 | 346 | | |
345 | 347 | | |
346 | 348 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2680 | 2680 | | |
2681 | 2681 | | |
2682 | 2682 | | |
| 2683 | + | |
| 2684 | + | |
| 2685 | + | |
| 2686 | + | |
| 2687 | + | |
| 2688 | + | |
| 2689 | + | |
| 2690 | + | |
| 2691 | + | |
| 2692 | + | |
| 2693 | + | |
| 2694 | + | |
| 2695 | + | |
| 2696 | + | |
| 2697 | + | |
2683 | 2698 | | |
2684 | 2699 | | |
2685 | 2700 | | |
| |||
0 commit comments