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

When following USERMANUAL.md I get this error:TypeError: __init__() got an unexpected keyword argument 'unbound_message' #241

Open
manmat opened this issue May 3, 2023 · 3 comments

Comments

@manmat
Copy link

manmat commented May 3, 2023

I am using Cloud Shell and when I am trying to run the first commend with CloudDQ I get this:

$ python3 clouddq_executable.zip --help
Traceback (most recent call last):
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/clouddq/clouddq/main.py", line 32, in <module>
    from clouddq.integration.bigquery.dq_target_table_utils import TargetTable
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/clouddq/clouddq/integration/bigquery/dq_target_table_utils.py", line 24, in <module>
    from clouddq.log import JsonEncoderDatetime
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/clouddq/clouddq/log.py", line 23, in <module>
    from google.cloud.logging.handlers import CloudLoggingHandler
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging/__init__.py", line 18, in <module>
    from google.cloud.logging_v2 import __version__
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging_v2/__init__.py", line 25, in <module>
    from google.cloud.logging_v2.client import Client
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging_v2/client.py", line 37, in <module>
    from google.cloud.logging_v2.handlers import CloudLoggingHandler
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging_v2/handlers/__init__.py", line 17, in <module>
    from google.cloud.logging_v2.handlers.app_engine import AppEngineHandler
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging_v2/handlers/app_engine.py", line 24, in <module>
    from google.cloud.logging_v2.handlers._helpers import get_request_data
  File "/tmp/Bazel.runfiles__m9_ww0t/runfiles/py_deps/pypi__google_cloud_logging/google/cloud/logging_v2/handlers/_helpers.py", line 22, in <module>
    import flask
  File "/usr/local/lib/python3.9/dist-packages/flask/__init__.py", line 4, in <module>
    from . import json as json
  File "/usr/local/lib/python3.9/dist-packages/flask/json/__init__.py", line 8, in <module>
    from ..globals import current_app
  File "/usr/local/lib/python3.9/dist-packages/flask/globals.py", line 56, in <module>
    app_ctx: "AppContext" = LocalProxy(  # type: ignore[assignment]
TypeError: __init__() got an unexpected keyword argument 'unbound_message'

I tried with version 1.0.0 and 1.0.7

@sumeshpremraj
Copy link

sumeshpremraj commented May 8, 2023

I have the same error with CloudDQ 1.0.5

@danielholgate
Copy link

danielholgate commented May 11, 2023

Same for me with CloudDQ v1.0.7, with both Python version 3.9.2 and 3.9.7

@sumeshpremraj
Copy link

This does not happen for me when clouddq is run within a Python virtual environment. The problem is perhaps with conflicts from system level packages.

Since this is an issue with upstream packages Flask/werkzeug, I looked at their issues and ended up at
pallets/flask#4790 which details this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants