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

"TypeError: data.rpc-reply.rpc-error.error-message.trim is not a function" with wrong xml configuration #2

Open
balaji07s opened this issue Sep 14, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@balaji07s
Copy link

Hi team,

"If I push an XML configuration with a mistake using the Netconf client extension in VS Code, I receive an error message as follows:

TypeError: data.rpc-reply.rpc-error.error-message.trim is not a function

However, it should display the accurate error message provided by the Netconf server."

@jgroom33
Copy link

This reply triggers the same error:

<rpc-reply message-id="edit-config-2"
  xmlns:mef-fp="urn:ciena:params:xml:ns:yang:ciena-pn:ciena-mef-fp"
  xmlns:ncx="http://netconfcentral.org/ns/yuma-ncx" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>data-missing</error-tag>
    <error-severity>error</error-severity>
    <error-app-tag>instance-required</error-app-tag>
    <error-path>/mef-fp:fps/mef-fp:fp[mef-fp:name='remote-fp2']/mef-fp:classifier-list[1]</error-path>
    <error-message xml:lang="en">required value instance not found, or resource in use</error-message>
    <error-info>
      <bad-value>classifier-list</bad-value>
      <error-number>310</error-number>
    </error-info>
  </rpc-error>
</rpc-reply>

I suspect it is because xml:lang="en" not being handled.

@wisotzky wisotzky added the bug Something isn't working label Jun 3, 2024
@wisotzky wisotzky self-assigned this Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants