Issues noticed while dockerizing the bq connection to flapi#1
Merged
jrosskopf merged 6 commits intoDataZooDE:mainfrom Nov 6, 2024
Merged
Issues noticed while dockerizing the bq connection to flapi#1jrosskopf merged 6 commits intoDataZooDE:mainfrom
jrosskopf merged 6 commits intoDataZooDE:mainfrom
Conversation
Collaborator
Author
|
Thanks for checking but I still face the following errors : Issue 1 : Sub directories are not scanned properly for SQL files to cacheI believe it is not scanning the recommendations folder for SQL files ? Issue 2 : Empty server response from server |
jrosskopf
approved these changes
Oct 31, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The document describes the issues encountered while setting up the docker-compose-bigquery environment.
Issue 1: bigquery extension fails to load sometimes
The error message in the logs is:
Issue 2: With no erros or warnings, the container fails with error code 139.
The error message in the logs is:
Issue 3: Swagger UI does not show api specs