Pull and Push fetch failed using tolgee CLI

[vanyalazarova]

Tolgee cli has been installed globally. Configuration and used commands are on the screen.

[JanCizmar]

Hey! I have assigned this to @stepan662 .

I would just say, that it would be beneficial to print more about the error, since the fetch failed doesn't tell us a lot.

[stepan662]

I've improved error logging in #156, could you use the newest version and check if the error is clearer? (you can also use --verbose parameter to show more info about the error)

[vanyalazarova]

@stepan662 I used version 2.8.3

[JanCizmar]

This looks like something specific issue to windows. I would guess also maybe to @vanyalazarova configuration.

@vanyalazarova Do you by any chance have some company specific network/certificates configuration on your PC?

[mfrieling]

I have the same problem but with Tolgee CLI 2.9.0 I get a different error:

When doing the same (HTTP POST) request with Postman I get the same result, but when doing a HTTP GET request it works. We are using a self-hosted instance and it's Tolgee version is 3.47.1, so unfortunately not the newest one.

[cyyynthia]

Just pinging @OmarHamdann who reported a similar issue on old ticket #32 -- Sorry for the delay; try running it again with --verbose using latest CLI version, the error should be clearer and help troubleshooting.

[stepan662]

@mfrieling you might need to upgrade tolgee platform

[mfrieling]

@mfrieling you might need to upgrade tolgee platform

@stepan662 yes of course, but that is not as easy as it sounds because it's hosted by the customer and IT departments of big companies sometimes are difficult to handle, get systems updates and config changes done.

Apart from that, such a breaking change should only happen in major versions and not minors according to semver rules. And from 3.47 to 3.107 is not a major version change. And if you have a valid reason to do such a change in a minor version, you should either make sure other component (CLI, SDK) are still compatible/able to handle the old version as well or provide a version compatibility matrix for platform, SDK and CLI.

[stepan662]

The problem is that this is not actually a breaking change on the backend part, the problem is that the newest cli is using some feature that is not supported on the older backend.

It's not an easy problem to solve, I'm thinking we could provide some compatibility table, where we would say which version is compatible with what cli version.