Hello team, I'm trying out the AirByte Low Code Connector. AirByte released the part-2 of the tutorial in youtube yesterday. Was trying out according to the tutorial and the steps mentioned in the docs. During this step: https://docs.airbyte.com/connector-development/config-based/tutorial/incremental-reads After adding the

stream_slicer

Just before moving to this https://docs.airbyte.com/connector-development/config-based/tutorial/incremental-reads#supporting-incremental-syncs we check if the stream_slicer is working or not. i run this command

python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json

But getting this error: [ATTACHED THE LOG IN A FILE] Can anyone help, please?

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2725 to ensure timely resolution!

@[DEPRECATED] Marcos Marx How to reslove this?

Hey looks to me like there is an issue with data can you check if the data is as expected

@Harshith (Airbyte) I'm fetching data from Api Layer. It's free and always up and suggested by the AirByte docs for basic config to try out the low code connector. And data is coming when fetching without the stream_slicer codes added in the

exchange_rates_api.yaml

file. So, the data is being read after the end of this portion of docs: https://docs.airbyte.com/connector-development/config-based/tutorial/reading-data When I move to step-5, and add the properties of start_date, it still works and I can read data from the same command. But after adding the stream_slicer codes, I again check as per the doc suggests, and then I get the error I mentioned in the main msg.

Hey could you move the code to public git and share so that I can help in a better way

@Harshith (Airbyte) here's the github repo link: https://github.com/Meraj-Kazi/airbyte/tree/low-code-shopify I'm sending you the

secrets/config.json

file contents in inbox. Please lemme know if you need any more details. I followed the official docs.

Sure will take a look

@Harshith (Airbyte) So, it's an actual issue right? I thought I'm doing something wrong.

It looks to me like a data issue but created on so that team can also add a perspective. Since it is new not everyone has a complete picture. simple smile

@Harshith (Airbyte) Thanks man! Will keep an eye on the Github Issue.