[REGRESSION] `threads: -1` in `profiles.yml` causes panic

[dataders]

Describe the bug

This is on main as of 2 PM EST on 2025-09-09.

So far as I've known, threads: -1 was a valid config that meant: use as many threads as you can/want.

Today I got this off a debug build. Removing threads: -1 resolved the issue, and results in the same behavior IRRC, just wanted to flag because:

• it's a panic
• -1 is an integer (from my experience as a math major at least)! Though perhaps this is a YAML parsed as a float? Idk

panic: panicked at fs/sa/crates/dbt-fusion-adapter/src/sql_engine.rs:111:17:
threads must be an integer if specified

What version of dbt Fusion is this bug in? (find out by running dbt --version)

> dbtd --version
dbt-fusion 2.0.0-preview.10

> where dbtd
/Users/dataders/Developer/fs/target/debug/dbt

> dbtf parse
dbt-fusion 2.0.0-preview.10 (v2.0.0-preview.10-9-g015211d3a9 2025-09-09 13:34:44)
dbt-fusion 2.0.0-preview.10

To Reproduce

1. Open this workspace
2. Follow the instructions in the README

Or follow the original instructions below:

add threads: -1 to any profiles.yml

Expected behavior

It shouldn't panic!

[dbeatty10]

@dataders I was able to reproduce this doing a dev build against commit 27b6bfcc99 for threads: -1 within profiles.yml.

Interestingly, I wasn't able to set the --threads "-1" flag for the most recent released version of the CLI.

[fa-assistant]

🧹 Stale Issue Detected

This issue has had no meaningful activity for 167 days.

If this is still relevant, please:

• Comment with an update, or
• Add the cleanup/keep label to exempt it from future cleanup scans.

If no action is taken within 30 days, this issue will be scheduled for auto-close with a 7-day grace period.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[eliasdefaria]

Since core doesn't support, I'm closing as removing threads as a property altogether will achieve the behavior described