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

Resolved PB2022 GIT Connect to Workspace: out of Memory

  1. How-to
0
Votes
Undo
  1. André Monz
    André Monz
  2. PowerBuilder
  3. Tuesday, 15 November 2022 14:34 PM UTC

Hello Community,

we have our Repository on a self hosted gitlab-Server.
With Powerbuilder 2021 the 'Connect to Workspace' Workflow works fine and
ends with

Connecting to workspace received objects: 12905, total objects: 12906.
Connecting to workspace received objects: 12906, total objects: 12906.
Download workspace success.
Writing source control information...
Opening workspace...
Open workspace success.
Refresh
Refreshing, please wait...
Refresh completed.
Connecting to workspace completed (15:00:00)
 ---------- Done Source Control
The checkout directory looks normal, git, ws_objects, pbls etc.

The same with Powerbuilder 2022 ends with

Connecting to workspace received objects: 12905, total objects: 12906.
Connecting to workspace received objects: 12906, total objects: 12906.
Git detail error info: Out of memory
Git client error code: Generic error.
Git fails to connect to workspace.
Connecting to workspace completed (15:24:18)
 ---------- Done Source Control

The errors tab contains:
 ---------- Source Control: Errors   (15:24:18)
Git detail error info: Out of memory
Git client error code: Generic error.
Git fails to connect to workspace.
 ---------- Finished Errors   (15:24:18)
The checkout directory is totally empty.

Any advice here is very welcome. :)

 

Outlook email integration from PowerBuilder
Webbrowser PB 2022 PDF Pagemode
Responses (3)
André Monz
André Monz Accepted Answer Pending Moderation
  1. Friday, 18 November 2022 07:25 AM UTC
  2. PowerBuilder
  3. # 1

FYI:

This 'Bug' ist still unresolved, but:

- Appeon can't repoduce it. (i can't supply a testcase).
- On my Coworkers PC the error occurs too with this project.
- a connect to another (less objects) project on the same GIT-Server works fine.

Since manual GIT-Clone works, its not a big problem (for me).

 

 

 

Comment
There are no comments made yet.
André Monz
André Monz Accepted Answer Pending Moderation
  1. Wednesday, 16 November 2022 06:14 AM UTC
  2. PowerBuilder
  3. # 2

Hello Kitty,

thank you for your response.
I will report a new bug as you advised.

Regards,
André

 

Comment
There are no comments made yet.
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 16 November 2022 05:01 AM UTC
  2. PowerBuilder
  3. # 3

Hi André Monz,

 

Thanks for reporting the issue. From the error message, it seems to be an error from the underlying git code.

 

I suggest that you report a bug via our support ticketing system at https://www.appeon.com/standardsupport/newbug and include as much information as possible about the situation of your application, as well as all the technical specifications of your environment. Please add all relevant error messages, error logs, screenshots, and a replicable test case. Once the ticket has been opened, our support staff will take a look at your case and respond in the ticket thread.

 

BTW, with PowerBuilder 2022, you can clone the repository using a third-party tool like TortoiseGit and then open the workspace from PowerBuilder 2022. This will also activate source control for Git with PowerBuilder 2022.

 

Regards,

Kitty

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.