The trace client fails to restrict which tables are traced #1141
Assignees
Labels
T:Bug
Type: Bug (confirmed)
Comments
This was referenced Nov 28, 2023
evan-forbes
added a commit
that referenced
this issue
Nov 29, 2023
## Description There's an viper property or potential bug that stops us from overriding the default values for slices of strings. The "solution" atm is to use a string and parse it later like animals later. Unfortunately I think this is breaking since we're changing what a config is doing so tbh I'm not sure if we can ever include this in v1. If that's the case then we might want to consider not merging this to v0.34.x-celestia and only to main. closes #1141 --------- Co-authored-by: Rootul P <rootulp@gmail.com>
evan-forbes
added a commit
that referenced
this issue
Dec 4, 2023
## Description There's an viper [property or potential bug](spf13/viper#1366) that stops us from overriding the default values for slices of strings. The "solution" atm is to use a string and parse it later like animals later. closes #1141 --------- Co-authored-by: Rootul P <rootulp@gmail.com>
This was referenced Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The trace client is supposed to have the ability to select what is traced. This is currently not case, where everything gets traced. This becomes problematic in testground tests, where we need to collect specific data from all nodes, but must avoid overloading an influx instance with all trace data from 100+ nodes.
The text was updated successfully, but these errors were encountered: