[paconn] Paconn Update Throws Error

[microsoft]

[paconn] Paconn Update Throws Error

[nk-gears]

I had a suspect that this happens due to a network latency. Then i created a VM in US Region and installed paconn and tried. To my surprise the same connector.json worked in just 20 seconds.

So, you need to check how to deal with the network latency due to geographical usage. I reside in India and i am decided not to use PACONN from my terminal anymore.

[maventis]

I have exactly the same issue and I agree with you @nk-gears, it seems to be latency-based as I tried the same as you except with a proxy instead, and it worked fine within 20 seconds.

[mmurshed]

Hi,
I think I have some idea about the problem. I think the rest call is returning with an empty response due to latency most likely. The CLI is trying to parse the empty response and fails with JSON error. The resolution would be to not parse empty response and output to console saying that it encountered and empty response.

Since latency isn't an issue for me I can't reproduce. Would any of you be willing to help me test this fix? @maventis @nk-gears

[nk-gears]

@mmurshed I started using a VPN (TunnelBear) and then run the paconn update. Now i no more have this error as the latency issue is resolved.

I can definitely test and send you the results related to the empty JSON fix. But that doesn't solves the actual problem which the users are facing on other side of the globe.

What i recommend is, when uploading the changes to the server via update, it will be great if you use some compression techniques while POSTing them to the PACONN server. This way we will have a huge benefit for users who have 400+ operations in a single swagger file.

[nk-gears]

@mmurshed Closing this as i am using VPN to paconn update to resolve latency.