Hi the Airbyte team 👋 I opened a PR fixing a long-standing source-gitlab bug: groups with >100 projects only sync the first 100, leaving merge_requests, commits, etc. incomplete. The root cause: project discovery reads the embedded projects array from GET

/groups/:id

(capped at 100) instead of the paginated GET

/groups/:id/projects

. Fixes #56916 (auto-closed by a bot, but still reproduces on master). PR: https://github.com/airbytehq/airbyte/pull/79707 Would appreciate a maintainer running

/run-connector-tests

and a review. Many thanks🙏

I've got an update to our connector waiting from Feb 😞 https://github.com/airbytehq/airbyte/pull/73740 .. is anyone available to look?

https://airbytehq.slack.com/archives/C054V9JFTC6/p1782147116962339 if anyone has a chance to look. mongo airbyte connection is essentially broken for a few of our connections and want to avoid forking the connector

Hi Airbyte Team ! I submitted two community connector PRs and all CI checks are passing. Could a maintainer take a look when they have time? It's my first time I upload connectors for my company, so please tell me if everything is ok ! github.com/airbytehq/airbyte/pull/79709 github.com/airbytehq/airbyte/pull/79710

Does the airbyte team have any SLA on reviewing code that is fully approved? Have a few PRs that are blocking some syncing on our side and would really like to get these merged.

It's an endless nightmare getting stuff merged @Henry Bogardus 😞 we have stuff open since Feb. It's been 12 months of battling to get stuff merged. It doesn't make sense to me as I feel like the whole power of an ETL product is the things it connects to, but we get no love.

hello all, i am currently working on the development of clickhouse connector to support multi-node, the only issue is that the custom connector is working only with stdio+ jsonl transport and not with socket + protobuf which causes the connector to insert slow. i have looked that the config is passed from the platform and stdio + jsonl are the default config in the env file. From testing perspective, can someone help me understand. is it because of the original definition id or there is a logic i am missing out on. it would be a great help , thanks.

Hi Airbyte Team 👋 I proposed this PR to make the

destination-gcs

connector much more fast thanks to sockets, aligned with destination-s3 connector 🏎️ Could you help me to review, validate and merge this PR ? 🙏 Thanks a lot !

Hi team! I'm looking for a time-sensitive review of a

source-salesforce

PR due to new security requirements: github.com/airbytehq/airbyte/pull/80892. The Salesforce connector breaks under Salesforce's OAuth Refresh Token Rotation mandate, and enforcement began June 25. Can a maintainer comment

/run-connector-tests

and queue this for review? Happy to turn feedback around same-day. Thanks!

Hello community, I reported an issue regarding the Connector Builder / Declarative CDK a while ago, and I would heavily appreciate it if someone from the team could take a look, as it severely impacts sync performance. When using

incremental_dependency: true

on parent-child streams, the child stream drops its cursor context after the first sync, forcing the parent stream into an unexpected full refresh loop on subsequent syncs (making them 100x–1000x slower). I just updated the issue with a comprehensive root-cause analysis (assisted by GitHub Copilot and verified against the latest Concurrent CDK source code). I also provided: 1. A functional connector-level workaround using custom components (StateMigration) that anyone can apply today. 2. The exact lines in the CDK core (

substream_partition_router.py

) where the context is being lost. Here is the link to the issue: github.com/airbytehq/airbyte/issues/61567 Could you please help review the proposed architectural fix or provide recommendations to get this merged? Thanks!

<!subteam^S01SHT8BSCU> are we wasting our times trying to maintain community connectors? Should we build something decentralised where people can just copy-paste the latest connector instead?

Is airbyte planning on supporting connection directly to Microsoft Fabric Warehouse ??? Has anyone been able to connect it?

Hi team 👋 . Could I get a maintainer review on a source-gong fix? PR #82260 — github.com/airbytehq/airbyte/pull/82260 Fixes #78480 (source-gong 429 / rate-limit failures) What it does:

callTranscripts

currently sends one POST /calls/transcript request per call (SubstreamPartitionRouter with a single callId), so backfills blow past Gong’s ~3 req/s rate limit and ~10k/day quota. The PR wraps the existing router in a GroupingPartitionRouter (group_size: 100) so one request covers up to 100 calls — ~99% fewer requests. Manifest-only change + a unit test; preserves the private-call filter and started cursor, no schema change/reset. Validated against a live Gong tenant: array callIds accepted, 100/request → 200, cursor pagination works alongside callIds. Status: CLA signed ✅, all fork-accessible checks green. The only red checks are the fork “No Creds” connector test and the progressive-rollout gate — both need maintainer-side action (/run-connector-tests + rollout bypass). Would appreciate someone running the credentialed suite and taking a look 🙏 (edited)

hey i made a pr to add jwt auth for salesforce, can someone help me get this reviewed? github.com/airbytehq/airbyte/pull/80788

Hi team, I submitted an issue a month ago, and the AI autoreply said they would have the issue routed to oncall, but I have no clue how to track the oncall progress. This one is fairly important for us github.com/airbytehq/airbyte/issues/80250 any ideas?

Hi team! 👋 I've been investigating a silent data-loss bug in

source-snowflake

(currently on

1.0.5

, but I confirmed it's still reproducible on

1.1.0

) reported here: github.com/airbytehq/airbyte/issues/70257 (filed by someone else back in December). Incremental syncs return 0 records when the stored cursor checkpoint equals the current

MAX(cursor_field)

, with no error. Root cause looks like:

SnowflakeLocalDateTimeAccessor

in

SnowflakeFieldTypes.kt

truncates nanosecond precision down to microseconds when reading the

MAX(cursor)

value used to build the query's upper bound, but the actual column values in Snowflake keep full nanosecond precision. When the sync window collapses to a single point (

cursor == MAX

), the truncated upper bound ends up strictly less than the real value of the row(s) it's meant to include, so the WHERE clause silently excludes them. The fix would live entirely in the connector's own source, not the shared Bulk CDK. Before I put together a PR: I noticed the contributing guide mentions community contributions to "the data replication platform" stopped being accepted in mid-2025, and the accepted-contributions list is framed around API/Connector-Builder connectors. Since Snowflake is a JDBC/Kotlin connector, is a bug fix like this still in scope for a community PR, or should this go through another channel? Happy to open the PR either way if someone can point me in the right direction. Thanks!

Hi! I opened PR #82690 for issue #27171, adding an optional JSONL stringify mode for Hive JsonSerDe compatibility. The Bulk CDK checks pass. The destination compatibility jobs fail before running because the fork PR lacks connector test configuration, and I asked for confirmation in the PR. Could a maintainer confirm whether this CDK/destination-related contribution is in scope for review and whether the compatibility jobs can be rerun with the required configuration?

hello 👋 the source-postgres connector suffers from lots of bugs since

3.8.x

2 months old release, examples: • github.com/airbytehq/airbyte/issues/80939 • github.com/airbytehq/airbyte/issues/80295 • github.com/airbytehq/airbyte/issues/81431 • github.com/airbytehq/airbyte/issues/81397 • github.com/airbytehq/airbyte/issues/47547 • github.com/airbytehq/airbyte/issues/79109 👉 do you have any visibility regarding a solid fix ? ⚠️ this is blocking for this 🏎️ speeded up destination v2 adoption as

Change Data Capture

is unusuable 😕 thank you!

Hey everyone! Does anyone experience problem with Paypal and Bing connectors? We started getting this error all of a sudden. We use native connectors.

Hey everyone, I am trying to create a custom connector for Reddit Ads API (Endpoint: ads-api.reddit.com/docs/v3/api/get-a-report) using Connector Builder UI. Has anyone done it before?

Hello! A new column called _network_details_ was added to the Stripe's disputes table, we tried hitting their API end point and it is indeed available. However, after refreshing our connector's source schema in Airbyte this column did not appear. We also tried updating our Stripe connector which also did not solve the issue. Perhaps anyone knows how we could add this new column to our Stripe connector and how long this process might take?

Hi everyone, I'm researching ways to use AI agents to improve the connector development experience. I'm wondering: - Does Airbyte have an open-source implementation for AI-assisted connector generation? - Which repository contains the related code? - Is it based on Airbyte Agent SDK, Connector Builder, or other internal components? I'd like to contribute ideas and improvements around: - API documentation understanding - schema inference - connector YAML/config generation - developer experience improvements If there is a contributor group or discussion channel for this topic, I'd appreciate any guidance. Thank you!

Hi Team, I submitted a PR for updates to the Uptick source connector: github.com/airbytehq/airbyte/pull/83710 Could I please request a review

Anybody uses MySQL as destination? There are no docs about why 0 precision columns from Snowflake create decimal(38,9( rather than integer?

Hi Team! I have a PR open on source-float since June that's still waiting for a review: github.com/airbytehq/airbyte/pull/79087 It adds two streams from the Float Reports API —

reports-people

and

reports-projects

(aggregated scheduling/utilization data) — plus an optional

end_date

config field. Manifest-only, 0.0.56 → 0.1.0, existing streams untouched. I've just merged latest master, so it's conflict-free and mergeable again. Would appreciate a review whenever someone has time — happy to make changes.

Hi team 👋 We have several open PR waiting for Airbyte team approval, please could you consider them ? 🙏 🔴 Blocking data collect (current connector is down) • Goldcast new API interface 🟠 Blocking our upgrade to speed-mode GCS destination v1.0.0 (fields regressions) • Goldcast event_members schemaless • Hubspot marketing_email &amp; owners missing fields 🟡 Blocking new business needs implementations • LinkedIn Ads video stream • Chift executions stream and schemaless management Thanks a lot, and happy to help 🙂

Hi Team/@Richelle Herrli I've been facing an issue where the data movement from GCS to Snowflake creates junk column on every run when authenticated with Service Account. The issue was raised a couple of months back here. Since there was no resolution provided, I made the changes and raised a PR, can somebody please help in reviewing this so that we can be unblocked? Thank you!

Hi team 👋, any plan for this issue github.com/airbytehq/airbyte/issues/82729? I think the AI integration code is getting there github.com/airbytehq/airbyte/pull/82731

Hi everyone, I’ve submitted a feature request to Airbyte for configuring CPU and memory resources per connection directly from the UI. Airbyte already supports connection-specific resource requirements internally, but today this typically requires changing the internal database manually. In environments with many connections, this makes resource management harder than it should be. The main use case is that not every connection has the same workload. For example, a lightweight CDC connection may only need a small amount of CPU and memory, while another connection doing a large initial sync or heavy batch load may need much more. Being able to configure these values per connection from the UI would help avoid both over-provisioning and under-provisioning. If this would be useful in your environment as well, please consider upvoting the feature request. More upvotes can help show the Airbyte team that there is broader demand for this capability. github.com/airbytehq/airbyte/discussions/85061

Hey everyone 👋 We’re running Airbyte 2.0 and during routine container scanning we’ve identified several OS-level vulnerabilities in Airbyte-provided base images: •

airbyte/container-orchestrator

•

airbyte/connector-sidecar

•

airbyte/workload-init-container

The vulnerabilities appear to originate from the Java base image bundled with these containers — so they’re outside our control to patch directly. We’ve followed the reporting process outlined in the Airbyte security docs and sent the details to

<mailto:security@airbyte.io|security@airbyte.io>

, and even after multiple follow ups, haven’t received a response yet. A couple of questions for the community: 1. Has anyone else run into OS-level CVEs in these Airbyte core images? If so, how did you get them addressed? 2. Is there a better channel to reach the Airbyte security team — GitHub issue, Slack, or otherwise? Any pointers would be really appreciated! 🙏