Closed bchool closed 6 years ago
Thanks for the report, we'll take a look ASAP :smile:
Thanks for your speed.
The problem persists with a different message:
t {code: 1, data: {…}, message: "no such object", name: "t", stack: "t: no such object↵ at t.
I have tried two different methods: First I have tested it pulling the changes from the git repository. After I reverted to an snapshot and then I changed the import ip to ip-utils and ran yarn build with the same result.
Ok, that's a different issue. Please open a new issue for this :)
Then, when you reproduce it, please go to Settings > Logs, find the corresponding error log (which should be the first one in the list), click on the eye button on the right side :eye: and paste the whole trace in the new issue.
Context
Expected behavior
After click on the plus symbol of the Allowed IPs of a VIF configured over a locked network, and choose an IP from the list, it is configured as the new one allowed ip for that VIF.
Current behavior
The list of IPs is displayed to choose from, but after do it nothing happens, and show "index.js:1 Uncaught TypeError: (0 , z.isIp) is not a function" by the console. This behavior started to occur with version 5.17. I don't remember node version.