• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Powerbuilder writes "UTF - 8" encoding to Git commits

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Powerbuilder writes "UTF - 8" encoding to Git commits

  1. Issue
0
Votes
Undo
  1. Rolf Knaden
    Rolf Knaden
  2. PowerBuilder
  3. Tuesday, 5 March 2019 08:08 AM UTC

Hi all.

We are using a Git repository to store our powerbuilder sources and a Teamcity server to build a setup from it.
Now, when I commit changes to Git from inside Powerbuilder, this commit contains an "encoding UTF - 8".
And that's a problem for Teamcity. When such a commit is the last one done, it always encounters an "IllegalCharsetNameException" error:

[08:32:50]Collecting changes in 1 VCS root
[08:32:50]Failed to collect changes, error: Error collecting changes for VCS repository '"https://gitlabconject.planon-fm.com/conjectFM/Client.git#refs/heads/master" {instance id=19, parent internal id=2, parent id=Client_Http1040469conjectFMClientGitRefsHeadsMaster, description: "https://gitlabconject.planon-fm.com/conjectFM/Client.git#refs/heads/master"}' Collecting changes failed: java.nio.charset.IllegalCharsetNameException: UTF - 8
[08:32:50]Failed to collect changes, error: Error collecting changes for VCS repository '"https://gitlabconject.planon-fm.com/conjectFM/Client.git#refs/heads/master" {instance id=19, parent internal id=2, parent id=Client_Http1040469conjectFMClientGitRefsHeadsMaster, description: "https://gitlabconject.planon-fm.com/conjectFM/Client.git#refs/heads/master"}' Collecting changes failed: java.nio.charset.IllegalCharsetNameException: UTF - 8
[08:32:50]Build finished

You see that encoding in the list of commits. In the screenshot below the third last is such a commit done with powerbuilder:

When I do the git commit not from inside Powerbuilder but with others tools (e.g. Sourcetree or TortoiseGit), as you can see the last and second last commit, there is no such "encoding UTF - 8" written to the commit and Teamcity has no problems with it.

Does anyone know, why Powerbuilder writes "UTF - 8" to the commit?
Shouldn't it be "UTF-8" correctly, if any?
How can I prevent this by changing settings in Powerbuilder?

Thanks for any hints.

Rolf

  1. Encoding
  2. Git
Does someone already used GitLab/Kubernete for CI/...
Closing main windows on a dockable MDI frame app
Responses (3)
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Friday, 8 March 2019 13:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi Rolf,

What is the command you use to get the output? I tried git log but don't see the "UTF - 8" anywhere.

Regards,

Tom Jiang

Comment
There are no comments made yet.
Rolf Knaden
Rolf Knaden Accepted Answer Pending Moderation
  1. Monday, 11 March 2019 05:43 AM UTC
  2. PowerBuilder
  3. # 2

Hi Tom

It's this:

git log --all --pretty=raw

Comment
Tom Jiang @Appeon
  1. Tom Jiang @Appeon
  2. Wednesday, 13 March 2019 02:47 AM UTC
Hi Rolf,



I can reproduce the issue. Please open a ticket at https://www.appeon.com/standardsupport/newbug to better track the issue. Thanks!



Regards,



Tom Jiang
  1. Helpful
There are no comments made yet.
Gordon Leishman
Gordon Leishman Accepted Answer Pending Moderation
  1. Friday, 21 June 2019 01:29 AM UTC
  2. PowerBuilder
  3. # 3

Hi Tom/Rolf,

I am in the process of trying to switch from using PushOK to native PB GIT but am having this same Team City build issue. 

I am finding though that once I have any commit in my branch with the UTF - 8 bit in it, my build fails regardless of whether it is the last commit.

So I don't really have a workaround for the issue, other than doing all of my commits outside of PB or continuing to use PushOK (please no!!).

I notice from the bug that has been raised (Bug 2478) that this is officially fixed in 2019, however, we are currently using 2017 R3 and will not be upgrading to 2019 for at least 6 months to a year (company policy).

So I have also downloaded the fixed 2017 R3 DLL from the bug and this appears to fix the problem.

Am I able to use this DLL in production and is it supported by Appeon?

If not, will there be an MR release for 2017 R3 that includes this fix?

Thanks
Gordon

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.