search

singer-io / tap-quickbase

Singer.io tap for Quick Base API
GNU Affero General Public License v3.0
7 stars 3 forks source link

Getting an error on first integration #22

Closed isacolick closed 5 years ago

isacolick commented 5 years ago

Here is what I see in the logs. Unfortunately, I don't see much other info to go on

2018-11-20 12:18:16,742Z    tap -   File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_quickbase/qbconn.py", line 74, in query
2018-11-20 12:18:16,742Z    tap -     records = self.request(params, table_id, headers=headers).find('table').find('records')
2018-11-20 12:18:16,742Z    tap - AttributeError: 'NoneType' object has no attribute 'find'
2018-11-20 12:18:16,769Z   main - ERROR Target exited abnormally with status 1. Terminating tap.
2018-11-20 12:18:16,771Z   main - INFO Exit status is: Discovery succeeded. Tap failed with code 1 and error message: "'NoneType' object has no attribute 'find'". Target failed with code 1 and error message: "Expecting value: line 1 column 1 (char 0)".
luandy64 commented 5 years ago

Thanks for opening the issue! Are you comfortable running this yourself?

Assuming you are, I think the steps to identify what's going wrong here would be to break apart the records = assignment call chain into 3 distinct steps and then add whatever safety checks are needed to make it not raise.

isacolick commented 5 years ago

Thanks for asking. I'm using this via Stitch and connecting a Quickbase app to a Postgres DB. Other than the log information I shared, there's not much more I can share or do about the problem.

That being said, the stitch integration is still running - even though there are only four tables and maybe a couple of thousand rows of data. I think every run is getting to a point and then halting at a different point and with different errors. There's one table that it hasn't loaded yet while others it seems to have loaded multiple times.

Not sure this helps.

luandy64 commented 5 years ago

Seeing that this first happened 7 hours ago, I'm guessing the tap has tried to run again, correct? Are you seeing this same error in later runs? This might be an issue with things outside of the tap; and the only way to be sure of that is to monitor it for some time.

dmosorast commented 5 years ago

Closing this issue due to inactivity. Feel free to reopen if you are still seeing problems!