@kapa.ai - as per my requirement I will have to add onedrive connector as source. I have added that from marketplace. Now I will have to customize the code of ondrive connector. I have already setup the repo but is there a way to debug the code. I have my setup on linux. And I am using Visual studio code to connect to remote linux machine using SSH extension.

To debug the code of the OneDrive connector, you can follow these steps: 1. Clone the Airbyte repository to your local machine. 2. Navigate to the directory of the OneDrive connector in the cloned repository. 3. Open the connector's code in Visual Studio Code. 4. Set breakpoints in the code where you want the execution to pause. 5. Run the connector in debug mode. Unfortunately, the knowledge sources provided do not contain specific instructions on how to run the connector in debug mode. However, you can typically do this by running the connector with a special flag or in a special mode that enables debugging. You might also be able to attach a debugger to the running connector process. For more detailed instructions, you may want to refer to the [Airbyte documentation](https://docs.airbyte.com/integrations/sources/microsoft-onedrive) or ask for help in the [Airbyte community](https://discuss.airbyte.io/t/863). Please note that modifying the code of the OneDrive connector may affect its ability to receive updates from the Airbyte repository. If you need to customize the behavior of the connector, consider creating a new connector based on the OneDrive connector, so that you can maintain your customizations separately.

@kapa.ai How can I create my custom connector and copy the existing onedrive connector code for achieving the same functionality

A message from kapa.ai

To create a custom connector based on the existing OneDrive connector, you can follow these steps: 1. Clone the Airbyte repository to your local machine. 2. Navigate to the directory of the OneDrive connector in the cloned repository. 3. Copy the entire directory of the OneDrive connector and paste it into a new directory. This new directory will be the home for your custom connector. 4. Rename the connector and update the necessary files (like the Dockerfile, README, etc.) to reflect the new name of your custom connector. 5. Make your desired modifications to the connector's code. Once you've created your custom connector, you can build and push it to a Docker registry. Here's how you can do it: 1. Build and tag your connector image locally, e.g.:

docker build . -t my-custom-connectors/source-custom:0.1.0

2. Create your image tag with

docker tag

command. The structure of the remote tag depends on your cloud provider's container registry service. 3. Use

docker push <image-name>:<tag>

to push the image to your private Docker registry. You can then use this custom connector in your Airbyte instance by specifying the Docker image name of your custom connector when you set up a new source or destination. For more detailed instructions on creating a custom connector, you can refer to the [Airbyte documentation](https://docs.airbyte.com/connector-development/connector-builder-ui/overview). Please note that you'll need to maintain your custom connector separately from the Airbyte repository. This means that you'll need to manually merge any updates from the original OneDrive connector into your custom connector.

@kapa.ai I am using existing one drive connector. And want to customize. For debugging it, I am trying write the logs to my file. Now after making the change in code what command I will need to fire im order to build it.

A message from kapa.ai

After making changes to your connector's code, you need to rebuild the Docker image for your connector. You can do this by running the following command from the connector module directory (

airbyte-integrations/connectors/destination-<name>

):

bash ./gradlew :airbyte-integrations:connectors:destination-<name>:build

Replace

<name>

with the name of your connector. This command builds a Docker image with your connector's code and tags it with the

dev

tag. Please note that each time you make a change to your implementation, you need to re-build the connector image using the above command. This is because the Docker image contains a snapshot of your connector's code at the time the image was built. Any changes you make to the code after building the image will not be included in the image unless you rebuild it. For more information, you can refer to the [Airbyte documentation](https://docs.airbyte.com/connector-development/tutorials/building-a-java-destination#directly-running-the-destination-using-docker).

@kapa.ai getting below buid error. elcome to Gradle 8.6! Here are the highlights of this release: - Configurable encryption key for configuration cache - Build init improvements - Build authoring improvements For more details see https://docs.gradle.org/8.6/release-notes.html Starting a Gradle Daemon, 2 incompatible Daemons could not be reused, use --status for details FAILURE: Build failed with an exception. * Where: Build file '/home/3rdisearch-dev/project/airbyte/airbyte/airbyte-integrations/connectors/source-mysql-v2/build.gradle' line: 12 * What went wrong: A problem occurred evaluating project 'airbyte integrationsconnectors:source-mysql-v2'. > Could not get unknown property 'first' for project 'airbyte cdkbulkcorebulk-cdk-core-base' of type org.gradle.api.Project. * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Get more help at https://help.gradle.org. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

A message from kapa.ai

New message text here

@kapa.ai when does main.py of source-mictosoft-onedrive gets called.

A message from kapa.ai

The

main.py

of the

source-microsoft-onedrive

connector is the entry point for the connector and it gets called when you run the connector. When you set up a new source in Airbyte and choose Microsoft OneDrive, Airbyte internally runs the

main.py

script of the

source-microsoft-onedrive

connector. This script handles the command line arguments and invokes the appropriate function based on the command you're running (like

check

,

discover

,

read

etc.). For example, if you're running the

check

command to check the connection to the Microsoft OneDrive, Airbyte will internally execute something like

python main.py check --config config.json

. Here,

main.py

is the script being run,

check

is the command, and

--config config.json

is an argument specifying the configuration file. You can also manually run the

main.py

script for debugging or development purposes. For example, you can run

python main.py spec

to output the JSON schema for the connector's configuration. For more information, you can refer to the [Airbyte documentation](https://docs.airbyte.com/connector-development/tutorials/the-hard-way/build-a-connector-the-hard-way#implement-the-spec-operation) and the [source code of the connector](https://docs.airbyte.com/integrations/sources/microsoft-onedrive).

@kapa.ai Which file gets called when we click on sync now.

A message from kapa.ai

When you click the "Sync Now" button in the Airbyte UI, it triggers an API request to the

/sync

endpoint. This is handled by the

syncConnection

function in the

ConnectionApiController

class in the Airbyte Server. Here is the relevant code snippet from the [knowledge source](https://github.com/airbytehq/airbyte/discussions/33811):

java @Override   @Post(uri = "/sync")   @Secured({EDITOR})   @SecuredWorkspace   @ExecuteOn(AirbyteTaskExecutors.SCHEDULER)   public JobInfoRead syncConnection(@Body final ConnectionIdRequestBody connectionIdRequestBody) {     return ApiHelper.execute(() -> schedulerHandler.syncConnection(connectionIdRequestBody));   }

This function takes a

ConnectionIdRequestBody

object as input, which contains the ID of the connection to be synced. The function then calls the

syncConnection

method of the

SchedulerHandler

class, which starts the sync process. Please note that the actual data extraction is performed by the specific source connector for the connection being synced. The source connector is a separate component that is responsible for connecting to the data source and extracting data. The specific file or function within the source connector that is called during the sync process depends on the implementation of the connector.

@kapa.ai For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 8s 2024-09-26T232154.390+0530 [LIFECYCLE] [org.gradle.internal.buildevents.TaskExecutionStatisticsReporter] 7 actionable tasks: 7 up-to-date 2024-09-26T232154.390+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' started 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Build finished for file system watching' 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' completed 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache executionHistory.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory/executionHistory.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory). 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache outputFiles.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup). 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier) 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) was closed 0 times. 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule). 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 0 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 13 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.431+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.ResolutionResultsStoreFactory] Deleted 4 resolution results binary files in 0.0 secs 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Run build' 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Run build' completed 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on worker lease 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopping 0 deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopped deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) was closed 0 times. 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS metadata (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/vcsMetadata) was closed 0 times. 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) has last been fully cleaned up 2 hours ago 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) was closed 0 times. 2024-09-26T232154.442+0530 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build. 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@60943381 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 26: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Success[value=org.gradle.launcher.exec.BuildActionResult@5fe1ce85] from daemon DaemonInfo{pid=1825832, address=[e04c2830-5cd7-4dee-8dbc-6a55b94ead1c port:45965, addresses:[/127.0.0.1]], state=Idle, lastBusy=1727372882033, context=DefaultDaemonContext[uid=2f9d8c81-6adf-43a2-a42d-0e57470ff30d,javaHome=/usr/lib/jvm/java-17-openjdk-17.0.12.0.7-2.0.1.el9.x86_64,daemonRegistryDir=/home/3rdisearch-dev/.gradle/daemon,pid=1825832,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,daemonOpts=-Xss4m,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx8g,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]} (build should be done). 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: dispatching class org.gradle.launcher.daemon.protocol.Finished 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 2024-09-26T232213.385+0530 [LIFECYCLE] [org.gradle.launcher.cli.DebugLoggerWarningAction] ############################################################################# WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING Debug level logging will leak security sensitive information!

A message from kapa.ai

Sorry @Ritu Wadhwani, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

@kapa.ai - this is on debug mode For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 8s 2024-09-26T232154.390+0530 [LIFECYCLE] [org.gradle.internal.buildevents.TaskExecutionStatisticsReporter] 7 actionable tasks: 7 up-to-date 2024-09-26T232154.390+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' started 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Build finished for file system watching' 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' completed 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache executionHistory.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory/executionHistory.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory). 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache outputFiles.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup). 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier) 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) was closed 0 times. 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule). 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 0 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 13 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.431+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.ResolutionResultsStoreFactory] Deleted 4 resolution results binary files in 0.0 secs 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Run build' 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Run build' completed 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on worker lease 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopping 0 deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopped deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) was closed 0 times. 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS metadata (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/vcsMetadata) was closed 0 times. 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) has last been fully cleaned up 2 hours ago 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) was closed 0 times. 2024-09-26T232154.442+0530 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build. 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@60943381 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 26: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Success[value=org.gradle.launcher.exec.BuildActionResult@5fe1ce85] from daemon DaemonInfo{pid=1825832, address=[e04c2830-5cd7-4dee-8dbc-6a55b94ead1c port:45965, addresses:[/127.0.0.1]], state=Idle, lastBusy=1727372882033, context=DefaultDaemonContext[uid=2f9d8c81-6adf-43a2-a42d-0e57470ff30d,javaHome=/usr/lib/jvm/java-17-openjdk-17.0.12.0.7-2.0.1.el9.x86_64,daemonRegistryDir=/home/3rdisearch-dev/.gradle/daemon,pid=1825832,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,daemonOpts=-Xss4m,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx8g,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]} (build should be done). 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: dispatching class org.gradle.launcher.daemon.protocol.Finished 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 2024-09-26T232213.385+0530 [LIFECYCLE] [org.gradle.launcher.cli.DebugLoggerWarningAction] ############################################################################# WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING Debug level logging will leak security sensitive information!

A message from kapa.ai

Sorry @Ritu Wadhwani, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

Hi @kapa.ai - For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 8s 2024-09-26T232154.390+0530 [LIFECYCLE] [org.gradle.internal.buildevents.TaskExecutionStatisticsReporter] 7 actionable tasks: 7 up-to-date 2024-09-26T232154.390+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' started 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Build finished for file system watching' 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' completed 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache executionHistory.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory/executionHistory.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory). 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache outputFiles.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup). 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier) 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) was closed 0 times. 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule). 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 0 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 13 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.431+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.ResolutionResultsStoreFactory] Deleted 4 resolution results binary files in 0.0 secs 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Run build' 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Run build' completed 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on worker lease 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopping 0 deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopped deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) was closed 0 times. 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS metadata (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/vcsMetadata) was closed 0 times. 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) has last been fully cleaned up 2 hours ago 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) was closed 0 times. 2024-09-26T232154.442+0530 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build. 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@60943381 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 26: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Success[value=org.gradle.launcher.exec.BuildActionResult@5fe1ce85] from daemon DaemonInfo{pid=1825832, address=[e04c2830-5cd7-4dee-8dbc-6a55b94ead1c port:45965, addresses:[/127.0.0.1]], state=Idle, lastBusy=1727372882033, context=DefaultDaemonContext[uid=2f9d8c81-6adf-43a2-a42d-0e57470ff30d,javaHome=/usr/lib/jvm/java-17-openjdk-17.0.12.0.7-2.0.1.el9.x86_64,daemonRegistryDir=/home/3rdisearch-dev/.gradle/daemon,pid=1825832,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,daemonOpts=-Xss4m,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx8g,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]} (build should be done). 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: dispatching class org.gradle.launcher.daemon.protocol.Finished 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 2024-09-26T232213.385+0530 [LIFECYCLE] [org.gradle.launcher.cli.DebugLoggerWarningAction] ############################################################################# WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING Debug level logging will leak security sensitive information!

A message from kapa.ai

Sorry @Ritu Wadhwani, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

@kapa.ai For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] 2024-09-26T232154.390+0530 [ERROR] [org.gradle.internal.buildevents.BuildResultLogger] BUILD FAILED in 8s 2024-09-26T232154.390+0530 [LIFECYCLE] [org.gradle.internal.buildevents.TaskExecutionStatisticsReporter] 7 actionable tasks: 7 up-to-date 2024-09-26T232154.390+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' started 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Build finished for file system watching' 2024-09-26T232154.392+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Build finished for file system watching' completed 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache executionHistory.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory/executionHistory.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on execution history cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/8.6/executionHistory). 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.btree.BTreePersistentIndexedCache] Closing cache outputFiles.bin (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin) 2024-09-26T232154.427+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/buildSrc/.gradle/buildOutputCleanup). 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier) 2024-09-26T232154.428+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-supplier (/home/3rdisearch-dev/.gradle/caches/8.6/md-supplier). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache Build cache (/home/3rdisearch-dev/.gradle/caches/build-cache-1) was closed 0 times. 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on Build Output Cleanup Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/buildOutputCleanup). 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule) 2024-09-26T232154.429+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on cache directory md-rule (/home/3rdisearch-dev/.gradle/caches/8.6/md-rule). 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 0 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.430+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.CachedStoreFactory] Resolution result cache closed. Cache reads: 0, disk reads: 13 (avg: 0.0 secs, total: 0.0 secs) 2024-09-26T232154.431+0530 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.resolveengine.store.ResolutionResultsStoreFactory] Deleted 4 resolution results binary files in 0.0 secs 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Run build' 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Run build' completed 2024-09-26T232154.435+0530 [DEBUG] [org.gradle.internal.resources.AbstractTrackedResourceLock] Daemon worker Thread 6: released lock on worker lease 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopping 0 deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.deployment.internal.DefaultDeploymentRegistry] Stopped deployment handles 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) has last been fully cleaned up 2 hours ago 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS Checkout Cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/vcs-1) was closed 0 times. 2024-09-26T232154.437+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache VCS metadata (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/vcsMetadata) was closed 0 times. 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on checksums cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/checksums). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Releasing file lock for file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes) 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on file hash cache (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/fileHashes). 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultPersistentDirectoryStore] dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) has last been fully cleaned up 2 hours ago 2024-09-26T232154.438+0530 [DEBUG] [org.gradle.cache.internal.DefaultCacheCoordinator] Cache dependencies-accessors (/home/3rdisearch-dev/project/airbyte/airbyte/.gradle/8.6/dependencies-accessors) was closed 0 times. 2024-09-26T232154.442+0530 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has finished executing the build. 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@60943381 2024-09-26T232213.382+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 26: dispatching class org.gradle.launcher.daemon.protocol.CloseInput 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Success[value=org.gradle.launcher.exec.BuildActionResult@5fe1ce85] from daemon DaemonInfo{pid=1825832, address=[e04c2830-5cd7-4dee-8dbc-6a55b94ead1c port:45965, addresses:[/127.0.0.1]], state=Idle, lastBusy=1727372882033, context=DefaultDaemonContext[uid=2f9d8c81-6adf-43a2-a42d-0e57470ff30d,javaHome=/usr/lib/jvm/java-17-openjdk-17.0.12.0.7-2.0.1.el9.x86_64,daemonRegistryDir=/home/3rdisearch-dev/.gradle/daemon,pid=1825832,idleTimeout=10800000,priority=NORMAL,applyInstrumentationAgent=true,daemonOpts=-Xss4m,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx8g,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]} (build should be done). 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: dispatching class org.gradle.launcher.daemon.protocol.Finished 2024-09-26T232213.383+0530 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop 2024-09-26T232213.385+0530 [LIFECYCLE] [org.gradle.launcher.cli.DebugLoggerWarningAction] ############################################################################# WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING Debug level logging will leak security sensitive information!

A message from kapa.ai

Sorry @Ritu Wadhwani, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

@kapa.ai 2024-09-26 184217 [46mplatform[0m > Docker volume job log path: /tmp/workspace/e3cc7823-99da-4ac5-811b-8d6ada7a6510/0/logs.log 2024-09-26 184217 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.63.13 2024-09-26 184217 [46mplatform[0m > 2024-09-26 184217 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0' 2024-09-26 184217 [46mplatform[0m > ----- START DISCOVER SOURCE CATALOG ----- 2024-09-26 184217 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0' 2024-09-26 184217 [46mplatform[0m > 2024-09-26 184217 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1' 2024-09-26 184217 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1' 2024-09-26 184217 [46mplatform[0m > Checking if airbyte/source-microsoft-onedrive:0.2.20 exists... 2024-09-26 184217 [46mplatform[0m > airbyte/source-microsoft-onedrive:0.2.20 was found locally. 2024-09-26 184217 [46mplatform[0m > Creating docker container = source-microsoft-onedrive-discover-e3cc7823-99da-4ac5-811b-8d6ada7a6510-0-biiyw with resources io.airbyte.config.ResourceRequirements@631f92[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=,additionalProperties={}] and allowedHosts null 2024-09-26 184217 [46mplatform[0m > Preparing command: docker run --rm --init -i -w /data/e3cc7823-99da-4ac5-811b-8d6ada7a6510/0 --log-driver none --name source-microsoft-onedrive-discover-e3cc7823-99da-4ac5-811b-8d6ada7a6510-0-biiyw --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/source-microsoft-onedrive:0.2.20 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=http://host.docker.internal:4317 -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.63.13 -e WORKER_JOB_ID=e3cc7823-99da-4ac5-811b-8d6ada7a6510 airbyte/source-microsoft-onedrive:0.2.20 discover --config source_config.json 2024-09-26 184217 [46mplatform[0m > Reading messages from protocol version 0.2.0 2024-09-26 184222 [46mplatform[0m > 2024-09-26 184222 [46mplatform[0m > ----- END DISCOVER SOURCE CATALOG ----- 2024-09-26 184222 [46mplatform[0m >

A message from kapa.ai

The log you've shared indicates that Airbyte is running the

discover

command for the

source-microsoft-onedrive

connector. This command is used to discover the schema for the source. Here's a breakdown of what's happening: 1. Airbyte checks if the Docker image for the

source-microsoft-onedrive

connector exists locally. 2. The Docker image is found locally. 3. Airbyte creates a Docker container for the

discover

command. 4. Airbyte prepares the command to run the Docker container. This command includes various environment variables and arguments. 5. The Docker container is run with the

discover

command and the

source_config.json

configuration file. 6. Airbyte reads messages from the connector using protocol version 0.2.0. 7. The

discover

command finishes running. If you're having issues with the

discover

command, you might want to check the

source_config.json

file to make sure it's correctly configured. If you're still having issues, you might want to ask for help in the [Airbyte community](https://discuss.airbyte.io/).