Slackbot
12/04/2025, 10:12 AMkapa.ai
12/04/2025, 10:13 AMspotlessStylingApply / Prettier “Starting server failed” Spotless is using Prettier (via an embedded Node/npm runtime) to format JSON/YAML resources as part of the Gradle build. The errors: > prettier-format(...ServerStartException) Starting server failed mean the Prettier “server” that Spotless spins up could not start. This is the same styling/Prettier integration mentioned in the forum thread about Spotless failures in local environments, where the problem was with the Spotless + npm setup rather than Airbyte code itself.[[Spotless styling](https://discuss.airbyte.io/t/2124)] From the available docs, there isn’t a specific Airbyte-side fix; the guidance is to fix your local environment/IDE/Gradle configuration (e.g., ensuring Node/npm are correctly available to Gradle/Spotless), or adjust your tooling so Spotless can find npm. [[Spotless styling](https://discuss.airbyte.io/t/2124)] If you only need to work on a connector, you can avoid the full platform build (and thus Spotless platform styling) by building just your connector, as suggested in another thread: bash ./gradlew airbyte-integrations:connectors:your-connector:build [[Failure to build](https://discuss.airbyte.io/t/1410)] When you do need the full platform build, make sure your local dev environment follows the “developing locally” instructions (correct JDK, Node, npm, etc.) and that IntelliJ/Gradle are using that environment. [[Developing locally 1.6](https://docs.airbyte.com/platform/1.6/contributing-to-airbyte/developing-locally#platform-contributions); [Formatting code 1.6](https://docs.airbyte.com/platform/1.6/contributing-to-airbyte/developing-locally#formatting-code)] 2. airbyte-db:jooq:generateConfigsDatabaseJooq (exit value 255) The generateConfigsDatabaseJooq task generates jOOQ classes against the Airbyte config DB. The logs you shared don’t include the underlying cause; they just show the Java process exiting with 255. There are several jOOQ-related errors in the forum, but they all occur at runtime (e.g. missing workspace FK, bad column type) rather than during the generate...Jooq build step, and none of the provided sources gives a concrete fix for a non‑zero exit 255 in this task.[[Failed to create pg source](https://discuss.airbyte.io/t/1902); [Airbyte wont start 0.40.30](https://discuss.airbyte.io/t/3843); [External Postgres DB](https://discuss.airbyte.io/t/1264)] Based on the docs and forum content you provided, there is no explicit, documented solution for this specific generateConfigsDatabaseJooq failure. The official docs only cover running a full build: bash ./gradlew build and, for platform dev, formatting via: bash ./gradlew format from the airbyte-platform root.[[Developing locally 1.7](https://docs.airbyte.com/platform/1.7/contributing-to-airbyte/developing-locally#platform-contributions); [Formatting code 1.7](https://docs.airbyte.com/platform/1.7/contributing-to-airbyte/developing-locally#formatting-code)] --- Because the knowledge sources don’t include the full stack trace for your generateConfigsDatabaseJooq error or a troubleshooting section for it, I can’t give a precise fix beyond: - Ensure your local environment matches the “developing locally” prerequisites (JDK, Node/npm, etc.). - Re‑run with --stacktrace and --info and, if the issue persists, open a new topic on discuss.airbyte.io with the full generateConfigsDatabaseJooq stack trace, referencing that this is failing during a platform build. If you share that full stack trace, I can help interpret it, but the current knowledge sources don’t document this exact failure mode.kanchalkumar karale
12/04/2025, 10:33 AMkapa.ai
12/04/2025, 10:33 AMkapa.ai
12/04/2025, 10:33 AMabctl + kind (Kubernetes in Docker) rather than docker-compose. Below is the documented flow, pulled from the “Quickstart” and “Developing locally” pages for recent platform versions. --- ### 1. Install prerequisites From the “Developing Locally – Prerequisites” docs (1.6–1.8):[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] Required to build Airbyte locally: - Java 21 - Node 20 - Python 3.10 - Docker - jq Recommended: - A version manager like pyenv or jenv to juggle versions.[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] For working with the abctl-managed local cluster, also install: - kind (Kubernetes in Docker) - kubectl These are used to inspect pods, logs, etc. in the Airbyte dev cluster.[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] --- ### 2. Install Docker Desktop Follow Docker Desktop instructions for your OS and keep it running in the background.[[OSS quickstart](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-1-install-docker-desktop)] - Mac / Windows / Linux links are provided in the quickstart. - On Linux headless VMs you can use Docker Engine instead.[[OSS quickstart](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-1-install-docker-desktop)] Airbyte runs on Kubernetes; locally it uses Docker to spin up a Kubernetes cluster. --- ### 3. Install abctl The detailed abctl installation steps are referenced but not fully included in the excerpts you provided. All “Developing locally” docs say to follow the Quickstart to install abctl.[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] So the flow is: 1. Go to the OSS Quickstart (Platform → Using Airbyte → Getting Started → Quickstart).[[OSS quickstart](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart)] 2. Follow Part 2: Install abctl there (the exact commands are not shown in your snippets, so I can’t quote them). The same applies for the “Next” docs namespace.[[OSS quickstart next](https://docs.airbyte.com/platform/next/using-airbyte/getting-started/oss-quickstart)] --- ### 4. Run Airbyte locally with abctl From Part 3: Run Airbyte in the Quickstart (current and “Next” docs):[[Run Airbyte](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte); [Run Airbyte next](https://docs.airbyte.com/platform/next/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte)] Basic local dev install (on localhost): bash # Docker Desktop running in background abctl local install - If you see a warning like Readiness probe failed: HTTP probe failed with statuscode: 503, you can let installation continue; you may just need more resources. See “Suggested resources” in the quickstart.[[Run Airbyte](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte)] Expose Airbyte over HTTP on a custom host: bash abctl local install --host <http://example.com|example.com> # if running over plain HTTP abctl local install --host <http://example.com|example.com> --insecure-cookies The --insecure-cookies flag is needed if you get the “failed to set a cookie / disable secure cookies” error over HTTP.[[Run Airbyte](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte)] Low-resource mode (fewer than 4 CPUs): bash abctl local install --low-resource-mode Note: low-resource mode disables the Connector Builder.[[Run Airbyte](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte)] Installation may take up to ~30 minutes depending on your connection. When it completes, Airbyte is available at: - <http://localhost:8000> (default) or - the host you provided with --host.[[Run Airbyte](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#part-3-run-airbyte)] Keep Docker Desktop running; if you quit it, restart Docker Desktop to bring the cluster back up. --- ### 5. Confirm dev cluster & inspect pods For development work, the docs recommend using kind + kubectl with the abctl-created cluster:[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] Configure your `kubectl`: bash kind export kubeconfig -n airbyte-abctl kubectl get pods -n airbyte-abctl You should see pods like airbyte-abctl-server-..., airbyte-abctl-webapp-..., etc.[[Dev locally 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#prerequisites)] View logs for a pod: bash kubectl logs -n airbyte-abctl airbyte-abctl-server-<pod-id> --- ### 6. Build the Platform for development If you’re contributing to the platform code: 1. Fork and clone airbyte-platform.[[Platform contrib 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#platform-contributions)] bash git clone git@github.com:{YOUR_USERNAME}/airbyte-platform.git cd airbyte-platform 2. Ensure abctl is running correctly: bash abctl local status 3. Build with Gradle: bash ./gradlew build This builds all code, runs unit tests, and produces JARs and Docker images.[[Platform contrib 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#platform-contributions)] 4. Optionally tune Gradle workers with GRADLE_OPTS or --max-workers.[[Platform contrib 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#platform-contributions)] To use your locally-built images in the abctl cluster: bash kind load docker-image airbyte/server:dev --name airbyte-abctl # in your values.yaml server: image: tag: dev # then abctl local install --values values.yaml [[Platform contrib 1.8](https://docs.airbyte.com/platform/1.8/contributing-to-airbyte/developing-locally#platform-contributions)] --- ### 7. Older docker-compose quickstart (legacy) The YouTube tutorial you included uses `docker-compose`: bash git clone <https://github.com/airbytehq/airbyte.git> cd airbyte docker-compose up [[YouTube dev env]()] However, the current docs and dev guides consistently point to abctl + Kubernetes as the supported path, not docker-compose. The knowledge sources do not provide updated docker-compose instructions beyond that video, so for “latest steps” you should follow the abctl-based flow above. --- If you tell me whether you’re focusing on platform development or just building/testing connectors, I can narrow this down further using the same docs.