[Feature] Quick connection timeout for anonymous snowplow tracking

[b-per]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

More info in #9336

I was running dbt-duckdb on a place (no Internet), and saw that any run was hanging for 30s. It ran a few models for a couple of seconds, then stopped for 30 seconds, and then ran the rest of the models.

I tried the following and had the same behaviour:

• Wifi Off
• Wifi On, not connected to any network
• Wifi On, connected to a network but without Internet access

When running with DO_NOT_TRACK=1, then run doesn't hang

Expected Behavior

dbt shouldn't wait 30 seconds to send tracking info when there is no access to the Internet or to the tracking endpoint

Steps To Reproduce

• deactivate Wifi/Internet
• perform a dbt run on a small model (this will need to use a local DW, like postgres, or duckdb)
• dbt hangs for 30 secs

Relevant log output

No response

Environment

- OS: MacOS

Which database adapter are you using with dbt?

other (mention it in "Additional Context")

Additional Context

Saw the behaviour with dbt-duckdb but this is not dependent on the adapter.

Relevant code seems to be here

dbt-core/core/dbt/tracking.py

Line 59 in afb2d61

{"buffer_size": 30} if SNOWPLOW_TRACKER_VERSION < Version("0.13.0") else {"batch_size": 30}

[dbeatty10]

Thanks for opening this @b-per !

It seems reasonable to give the anonymous tracking a quick shot and give up after a very short amount of time (1 or 2 seconds total) if it isn't able to establish a connection (rather than 30 seconds before giving up).

Re-labeling this as a feature request. Also labeling this as help_wanted for someone in the community to pick up.

Ancillary question

Which version of dbt-core did you see this in?

The {"buffer_size": 30} ... part wasn't added until #9680 just a few days ago. Although I didn't check one way or the other, I'm not aware of us back-porting and releasing this in 1.7.x.

[b-per]

I tested the behaviour on version 1.7 I believe. So it is there for previous versions as well.

From what I see the PR #9680 didn't introduce {"buffer_size": 30}. It moved it to another part of the code though.