@Artem Astapenko - we’re still debugging some internal issues on the backend which is why

connections/sync

just fails mysteriously right now now and why you never get any logs in

jobs/list

. i can provide you with an example of what the json output will look like from that endpoint, but it might not be until tomorrow that we actually get it working properly. lmk what i can do in the short term to mess up your progress as little as possible.

I am not current able to docker-compose build locally (

docker-compose -f docker-compose.build.yaml build

). it looks like the container is running out of space when trying to install node dependencies.

2020-09-10T16:16:55.596+0000 [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] > Task :dataline-webapp:npmInstall
2020-09-10T16:17:19.819+0000 [ERROR] [system.err] npm WARN tar ENOSPC: no space left on device, write

and

2020-09-10T16:17:24.369+0000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Caused by: org.gradle.process.internal.ExecException: Process 'command 'npm'' finished with non-zero exit value 228

full logs when running gradle build with debug:

Guys, 1 more error:

Request URL: <http://localhost:8001/api/v1/source_implementations/discover_schema>
Body: { sourceImplementationId: "60b7efbe-bae4-4094-a154-380a6274a76d" }
Status Code: 500 Internal Server Error

Hey artem, I notice that src/config you're hardcoding the api to be

apiUrl: "<http://localhost:8001/api/v1/>"

hey artem, our goal for the day is to "Get it to work" by end of day. we are fixing the last broken windows

artem, i merged a change that does this

api fall back on empty schema on no job output

btw, tests are failing for some reason. Something about that files changed.

@charles could you please check why build is failing on ‘ensure no file change’ my branch has no other changes except ts files. ( and recently I tried to fix editorconfig. It also doesn’t help )

Guys I just noticed that token for segment in task is not working. Could you send me the correct one?

Hi all. I totally forgot that I have a flight tonight. Could we move our call to tomorrow?

For check connection I know what needs to be done and I can also implement it. I need to replace call for create source to call on web_backend.

any chance you can mock it for now? (just have a string with the id of the job so you can see the issue in the frontend)

If I specify correct source but bad destination, will I have some logs? Or I should specify bigquery to get them?

artem, i’m not sure i understand this yet. do you mind explaining it again? maybe with an example? i’m having trouble understanding what API calls you’re making.

can somebody send me a screenshot of the CSV placeholder?

@Artem Astapenko - I’m seeing build failures because the build can’t find react-dom. I put up a PR that I think “fixes” it, but I sorta doubt this is actually the preferred way of fixing it. Would you mind taking a look? Here’s my PR.

Charles, small question: for source_implementation update and destination_implementation update, we can handle check_connection on frontend. The issue is that any implementation that we can do now will be confusing for user - because he will update, we will check values, return him error in case of error but actually new values will be stored instead of old one.

regarding the service icon, I'm actually wondering about removing the circle around the icon. it would rendre like this: https://www.figma.com/file/AODY4oi15iI5l0fbxHvobt/Daxtarity?node-id=6768%3A43 https://www.figma.com/file/AODY4oi15iI5l0fbxHvobt/Daxtarity?node-id=5782%3A43257 https://www.figma.com/file/AODY4oi15iI5l0fbxHvobt/Daxtarity?node-id=5856%3A0 what do you think?

hum that will be a problem for Jared's video, since he wants to demo that feature. Is there an ugly solution that we can implement and work on the real solution tomorrow?

also I don't want to block the segment analytics piece on the uuids. so if it is the last thing, let merge it, we will address it in a different release

okay. i will add an

onboardingComplete

flag tomorrow, and we can use that?

also heads up, we are pushing our launch back a day. we did a lot of testing this evening and still have some bugs we want to work out.

@Artem Astapenko - do you need anything to get this PR across the finish line? https://github.com/airbytehq/airbyte/pull/418/files

@Artem Astapenko are you able to merge yourself or you need me to do it?

any update on Segment?

Hi @Artem Astapenko just want to confirm that https://github.com/airbytehq/airbyte/pull/471 it is not ready to review (still a draft PR)

do you think the new Admin section should have a Settings icon instead?

Are we going to store prefilled data on frontend or as some default implementation on backend?

the frontend should not store any prefilled data. It will come from the backend.

In case we want to skip onboarding, how are we going to create destination? It is not possible to create it via UI right now

why would we skip onboarding?

Do we already have backend to change version of docker image and add new images?

The API that will go up is in https://github.com/airbytehq/airbyte/pull/479 — getting this merged as soon as I can so you can work against it. Might go in later tonight or this weekend.

Not important thing but for meta in index.html we have

<meta
      name="description"
      content="Web site created using create-react-app"
    />

shouldn’t we set some better description?

ignore