fix(consumer): Respect timeout config in lib_curl & fork_curl
#81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes the documented
timeout(milliseconds) passed via config options inPostHog::initeffective for event delivery.What’s included
timeout(ms) to theHttpClientconstructor (default remains 10000 ms).timeoutms → integer seconds usingceiland append curl flags:--max-time <seconds>(curl docs)--connect-timeout <seconds>(curl docs)Backwards compatibility
timeoutis not specified or is <= 0 it is treated as unlimited. This matches previous behavior.timeoutis > 0, events captured viaPostHog::capture(...)will now honor the configured timeout for bothlib_curlandfork_curlconsumers. Previously, this value was ignored by those consumers, so requests could wait longer than intended.Tests
HttpClientreceives the configured options.