-
Notifications
You must be signed in to change notification settings - Fork 16
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
parameters are not rendered by default #360
Comments
I found that the errors in #319 that aren't related to pickling all go away when |
Title: Disable Parameter Rendering by Default and Add Configuration Option for EnablingProblemParameters are being rendered by default in AppMap data, which is resource-intensive and increases data size. Users should have the option to enable this feature by setting AnalysisCurrently, AppMap renders the values of parameters automatically, and users need an option to disable this rendering by default. The configuration already exists to turn this feature on or off using the The Proposed Changes
Detailed Changes
@property
def display_params(self):
"""
Return True if APPMAP_DISPLAY_PARAMS is set to 'true', otherwise False.
"""
return self.get("APPMAP_DISPLAY_PARAMS", "false").lower() == "true"
# If we're asked to display parameters, make a best-effort attempt
# to get a string value for the parameter using repr(). If parameter
# display is disabled, or repr() has raised, just formulate a value
# from the class and id.
value = None
if Env.current.display_params:
try:
value = repr(val)
except Exception: # pylint: disable=broad-except
pass
if Env.current.display_params:
ret.update(_describe_schema(name, val, 0, max_depth)) SummaryBy ensuring that rendering of parameter values is not done by default and can be enabled through the |
Having the values of parameters in AppMap data isn't all that helpful. They're expensive to compute, and they take up a lot of space. Don't convert them to strings by default. Allow the user to turn on rendering (by setting
APPMAP_DISPLAY_PARAMS=true
).The text was updated successfully, but these errors were encountered: