Would it make sense to bundle the

seed

contents into the

scheduler

?

I’m seeing the following in the output of standard tests:

[        14 tests started         ]

but there are only 7 standard tests so it looks like we’re running each test twice. Is this a known issue or expected?

When we send metrics to segment, right now we exclude some tests right?

Is there a reason we’re excluding check connection failure tests from the standard source tests?

Who dares install Docker 3 and test Airbyte with it :)

I am battling with changing files

Had to apply the following to get it to compile on Ubuntu 20.04.1 LTS

diff --git a/build.gradle b/build.gradle
index 71239569..ad8fcaa2 100644
--- a/build.gradle
+++ b/build.gradle
@@ -1,7 +1,7 @@
 plugins {
     id 'base'
     id 'pmd'
-    id 'com.diffplug.spotless' version '5.7.0'
+    id 'com.diffplug.spotless' version '5.8.2'
 }

Or suffer a

Unable to store input properties for task ':com.diffplug.closet:spotlessJava'. Property 'steps' with value '[com.diffplug.spotless.FormatterStepImpl$Standard@2ac4ffae]' cannot be serialized.

@Justin Lawrence @Seth Goldberg thanks for the feedback in office hours about the lack of documentation for the API. I have added the api docs into the source in docs/api. if you open the index.html file that is in that directory in your browser you should be able to see the docs. For now we are just using the default docs generated by openapi so they aren't gorgeous, but hopefully they can give you a little more clarity on how the API works. If you're curious about the inspiration behind it, you can check out the slack api docs.

Did anyone you had success with FB Marketing API?

is it intentional that we don't write scheduler or server logs anywhere?

I have a build which keeps failing becase a file gets modified: https://github.com/airbytehq/airbyte/actions/runs/434293469 but I am unable to reproduce the file change locally (

./gradlew clean build

)

Hello @Jared Rhizor (Airbyte) ! Would you have an idea why the current docker-compose up in DEV mode on master does not seem to work properly unless i modify the

.env.dev

file with:

-CONFIG_ROOT=/tmp/config
+CONFIG_ROOT=/tmp/data

I'm not so sure why this was changed with the kube stuff

Let me know if it is ok to merge: https://github.com/airbytehq/airbyte/pull/1408

files that are not part of my PR. does it happen to someone else?

why do we have a format step before the build?

Hi, I'm kicking the tyres on the new Microsoft Team Source Connector. If I didn't correctly configure the application permission, the logs doesn't give me any clues why the syncing failed. The error message from the API call is not propagated through to the log (https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-microsoft-teams/source_microsoft_teams/source.py#L65). I've made a fix that I can submit. Should I create an issue and submit a PR?

Anyone else having issues with github in assigning reviewers. It's not able to find most of the team for some reason.

Should we be pushing the “bases” images to Docker Hub?

Hi Airbyte team! Thanks for helping out yesterday @charles! 😄 The error with the code was because one of the libraries used by the singer tap was updated and it was crashing, I forced to use an older version of that library. I was able to progress a little bit, but I'm getting another error, would someone be able give me a hint?

Hi Airbyte team! Do I need to submit a documentation for the source I'm developing similar to https://docs.airbyte.io/integrations/sources/braintree ? If yes, how/where do I do it?

is anyone else having to restart docker for mac somewhat frequently since the new update? the issue i'm seeing is that it is not removing bind mounts properly. it says they are removed them but then when i try to recreate the bind mounts it doesn't successfully create them (all the directories that get bound are empty). the only fix i have found is totally restarting docker for mac.

Hi team/charles! I'm working on the appsflyer integration, when I ran the second step in the checklist:

./gradlew :airbyte-integrations:connectors:source-appsflyer-singer:build

The task entered into an infinite loop (more than 10minutes, and was still running): The only thing I did was to add install_requires=tap-appsflyer in the setup.py

What do you think of these badges for connector build status?

Is there any api that airbyte exposes it's own health check? e.g.: the java server is up and running?

Does it possible to use the API to get status and trigger a Sync job?

I see that

web_backend

api is very similar to connections but it adds some info, what's the purpose of this api?

Hi Airbyte team! I'm working on the appsflyer connector, and I've 2 issues: 1. The tap-appsflyer defines in the setup.py the usage of pip package 'attrs==16.3.0', however pytest requires the 'attrs>=17'. When i run the gradlew integrationTest it fails. My solution was to force the usage of the 'attrs==19.1.0' in the Airbyte setup.py:

install_requires=["airbyte-protocol", "tap-appsflyer==0.0.12", "requests", "attrs==19.1.0"]

Is this solution ok? Otherwise I would have to submit a PR for singer and it usually takes some time, and I would rather not do it for now. 2. When I run the cmd below in the source-appsflyer-singer directory with venv activated, I get the error in the print, event though the appsflyer request succeeds.

python main_dev.py discover --config secrets/config.json

I've commited my changes in this branch

what do folks thing about applying an ordering to how the fields of the spec are exposed in the UI? the common issue we have is for say, the postgres spec, in the UI password appears before username. This is because all of these properties are effectively in a map so we don't get any order guarantees. i would like a way to describe the order of the fields. e.g. for postgres i think the most approach form is host, port, database, username, password.

Something we just ran into trying to help Kelvin create a Github dashboard from normalized outputs

Are we running CI on all PRs or only on PRs within team? I can’t see that it run for this https://github.com/airbytehq/airbyte/pull/1736