Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wanghe-fit2cloud The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b2cd34c757
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `\`, `\\`, | ||
| `"`, `\"`, |
There was a problem hiding this comment.
Preserve command backslashes across TensorRT edit flow
Escaping every backslash in double-quoted env values changes how TensorRT commands round-trip through the UI: getCommand returns the raw serialized value, and the edit form only unescapes \" (see frontend/src/views/ai/model/tensorrt/operate/index.vue), not \\. After this change, commands containing backslashes (common in shell escaping) are shown/saved with extra backslashes, so reopening and saving an existing config can silently alter runtime command behavior.
Useful? React with 👍 / 👎.



No description provided.