Skip to content
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

Command Details in execution traces #1232

Closed
sudesh0sudesh opened this issue Jul 22, 2024 · 0 comments · Fixed by #1449
Closed

Command Details in execution traces #1232

sudesh0sudesh opened this issue Jul 22, 2024 · 0 comments · Fixed by #1449
Assignees
Labels
feature use for describing a new feature to develop solved The issue has been solved
Milestone

Comments

@sudesh0sudesh
Copy link

sudesh0sudesh commented Jul 22, 2024

Use case

In atomic testings can we have what was the command sent to the machine after the variable changes in Traces of execution logs. Even before the completion of it's execution.

If the feature request is approved, would you be willing to submit a PR?

No

@sudesh0sudesh sudesh0sudesh added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jul 22, 2024
@jborozco jborozco added this to the Release 1.6.0 milestone Aug 22, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Aug 23, 2024
@damgouj damgouj linked a pull request Sep 16, 2024 that will close this issue
5 tasks
damgouj added a commit that referenced this issue Sep 18, 2024
@damgouj damgouj added the solved The issue has been solved label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved The issue has been solved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants