Skip to content

ast.literal_eval crash when log_config is not provided #182

Description

@kenanaKYD

When no log_config is passed, the SDK creates a default LogConfiguration
with enable_log=True, then calls ast.literal_eval(json.dumps(details))
where details contains non-serializable Python objects, causing:

malformed node or string on line 1: <ast.Name object at 0x...>

Path: authenticationsdk/core/MerchantConfiguration.py ~line 401

Fix: either skip the literal_eval (just use json.dumps directly for logging),
or default enable_log to False when no log_config is provided.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions