Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source Bing Ads: Check failed #9509

Closed
VitaliiMaltsev opened this issue Jan 14, 2022 · 1 comment · Fixed by #9510
Closed

Source Bing Ads: Check failed #9509

VitaliiMaltsev opened this issue Jan 14, 2022 · 1 comment · Fixed by #9510
Assignees
Labels
needs-triage type/bug Something isn't working

Comments

@VitaliiMaltsev
Copy link
Contributor

During set up Bing Ads Source on UI check step failed with logs

The connection tests failed.
Internal Server Error: SQL [insert into "public"."actor" ("id", "workspace_id", "actor_definition_id", "name", "configuration", "actor_type", "tombstone", "created_at", "updated_at") values (cast(? as uuid), cast(? as uuid), cast(? as uuid), ?, cast(? as jsonb), ?::"public"."actor_type", ?, cast(? as timestamp with time zone), cast(? as timestamp with time zone))]; ERROR: insert or update on table "actor" violates foreign key constraint "actor_workspace_id_fkey" Detail: Key (workspace_id)=(5d5b24c5-e366-43d0-b59b-b180638ce2f2) is not present in table "workspace".

Expected Behavior

Setup should be successful

@VitaliiMaltsev VitaliiMaltsev added type/bug Something isn't working needs-triage labels Jan 14, 2022
@bazarnov
Copy link
Collaborator

This should be the issue with setup.py main requirements block.
We should update the main dependency of: bingads>=13.0.10 instead of bingads==13.0.10

@bazarnov bazarnov linked a pull request Jan 14, 2022 that will close this issue
11 tasks
@bazarnov bazarnov self-assigned this Jan 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage type/bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants