Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug: TN cache validation error isn't precise

Open
  • Is something wrong?
#1,096 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
backend

Research direction

Reproduce the failure through the tn_cache configuration path using the streams_inline example and the logged validation error. Trace the configuration validation entry point to determine where the missing field is lost. Done means the error identifies the specific invalid or missing field instead of only reporting that a required field is empty.

Written by the indexing model from the issue text.

Description

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
Dominant language
Go
Stars
7
Forks
3
Avg merge
3h 2m
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.