2019.10.3 LTS Patch Release

Hi @Stephu, can you please let us know what is the error you are receiving? Also, in what .gitconfig file you have set up the proxy? You can find more details on how to add a proxy to a git config file here: Configure Git to use a proxy · GitHub

Hi @coramia
I tried it on each level:


I use the default proxy which I use on my workstation.

At the moment I use tortoise git an everything is running with that. I do not understand why uipath do proper integrate this settings to the studio.

I can also push and pull directly in powershell console.

In the log i have the following entries:

11:43:49.2889 => [DEBUG] [StudioTraceListener] [1] Execute System.ValueTuple`2[System.String,LibGit2Sharp.Commit] b__0(System.Threading.CancellationToken)
11:43:49.3189 => [INFO] [UiPath.Studio.Shared.Logging.OutputLogger] [1] Änderungen wurden erfolgreich an origin/master gepusht.

This is wrong. Because after inset user an passwort the dialog comes all the time again after pressing enter

Thank you for the details, @Stephu. Can you please try to set the proxy settings using the username and password, as well, and let us know what happens?
[http]
[http “https://domain.com”]
proxy = http://**proxyUsername:proxyPassword**@proxy.server.com:port
sslVerify = false

Our proxy is without authentication.
In the case I work with a generated token it works. But I cannot use my azure devops login like I use for example in tortoise git to connect with repo…

As a summary for this topic, the issue @Stephu was facing was not git proxy related. The .gitconfig file was correctly configured and the proxy details were taken into account, as the generated personal access token demonstrated.
The case here was that the Git repository he was trying to clone is hosted on an Azure DevOps Server, with 2-factor authentication enabled. Currently, we do not support this type of authentication for Git, but it is on the roadmap for future releases. (Managing Projects with GIT)

1 Like

We are on 2019.10.14 - is 2019.10.3 earlier or later than 2019.10.14? Is 2019.10.3 really 2019.10.30?

There needs to be more clarity on the version naming and what “order” they’re in.

On solution is to press in AzureDevOps Git Repo on “Generate Git Credentials”: image
With this user and password it works.

1 Like

Hello @postwick,
Starting 2019.10 we have decoupled the build versions of Studio & Orchestrator.
To properly document this, we have updated the following:

Please let us know if we can help with additional details.

what are difference between this feature and Elasticsearch?

@alexandra.vaidos @loginerror Will ES and Kibana 6.5.4 supported by 2019.10.3? If not, what version does this patch release support?

Thanks.

As far as I know, 6.x and 7.x are both supported (that’s what the requirements page says too: Software Requirements).
But I would note that 6.5.4 is a bit old/ will be EOL-ed in May - wouldn’t hurt to upgrade to 6.8.x at least (that upgrade should be smooth; from 6.x to 7.x might be a bit trickier, and from what I know, going to 6.8 first is recommended anyway).
Going further, we’ll probably always support versions that are not EOL at the moment of our release, but might drop support for EOL versions.

3 Likes

@virgilp Thanks!

Anyone knows if the product UiPath Insights is going to be released for community edition? :slight_smile:

This is great fix, does anyone have the link to download the enterprise version please?
regards…!!

1 Like

Hi @ANSHUL

It is available here :slight_smile:
https://platform.uipath.com/portal_/resourceCenter

Thanks

1 Like

That’s really awesome!! :clap: Good Work!!

The installer shows 19.10.4 already?!?

Hello @Lunk! We have released today a 19.10.4 patch. Related forum post soon to be published. Till then, see here release notes: 2019.10.4.

2 Likes