Skip to content

Bug: TN cache validation error isn't precise #1096

@outerlook

Description

@outerlook

hey @lwtsn I see that two fields have different cases:

[extensions.tn_cache]
enabled = "true"

streams_inline = '''
[
  {
-    "streamId": "stf37ad83c0b92c7419925b7633c0e62",
-    "dataProvider": "0x4710a8d8f0d845da110086812a32de6d90d7ff5c",
+    "stream_id": "stf37ad83c0b92c7419925b7633c0e62",
+    "data_provider": "0x4710a8d8f0d845da110086812a32de6d90d7ff5c",
    "cron_schedule": "0 * * * *",
    "include_children": false
  }
]
'''

Please try this and let me know if it works

Originally posted by @outerlook in #64

that error doesn't inform well what field was missing. This information could save us time

Aug 04 07:35:06 index-fun-truf-node-dev kwild[1587745]: 2025-08-04 07:35:06.705 [ERR] tn_cache: failed to process configuration {error=configuration validation failed: spec 0: ethereum_address validation failed: required field cannot be empty

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions