Value provenance tracking #345

Open
opened 2025-12-30 01:23:42 +01:00 by adam · 0 comments
Owner

Originally created by @bioball on GitHub (Sep 2, 2025).

To improve debugging, it would be beneficial to track the provenance of values (where values come from), and show this information in error messages, or through specialized evaluation modes.

Some ideas:

  • Capture both source sections and stack frames when values are initialized
  • Map source sections in rendered output (e.g. YAML) back to provenance information
Originally created by @bioball on GitHub (Sep 2, 2025). To improve debugging, it would be beneficial to track the provenance of values (where values come from), and show this information in error messages, or through specialized evaluation modes. Some ideas: * Capture both source sections and stack frames when values are initialized * Map source sections in rendered output (e.g. YAML) back to provenance information
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pkl#345