The solution Noel mentioned about setting autocrlf=true is now implemented as a feature of PowerBuilder 2019 R3.  Beta is currently available and final release is most likely early December 2020.

I was running into this exact problem but only on my own machine. Other devs working on the same repo were not running into this problem. Turns out it was an issue with line endings. By default git has autocrlf enabled so when fetching files it converts all files to CRLF. I recently changed my git config to disable autocrlf which caused me to have a mix of line endings in the ws_objects folder and any objects that had LF endings would fail.

My fix was to scrap my local repo and then clone from scratch like this:

git clone <URL> --config core.autocrlf=true

This allows me to leave autocrlf disabled globally but have it enabled locally for any PowerBuilder related projects.

We are also experiencing this.  We have 6 developers working simultaneously, so we have a lot of feature branches and pull requests so our develop branch (where we "Refresh" from) is constantly changing.

Whenever we do a refresh (whether it's on the Workspace, Target, or individual PBL) we get the "One or more PB Objects failed to compile..." message.

We can click OK and it appears to refresh, but too often objects do not get updated.

The code base is solid - a full build before or after finishes cleanly.  So there isn't a conflict with anything code-related.  

The object referenced as the offender is always the 1st object in the PBL (if refreshing the workspace or target, the 1st object in the 1st PBL - usually a datawindow in our instance, which further supports it's not a code issue).

Please see my attachment - the example is the 1st datawindow in the refreshed PBL.

Has anyone else seen this behavior, and if so - come up with a solution?

I can open a formal bug report if requested.

Thanks,

John

Hi John,

This happens when there is a conflict in some object that causes the IDE to fail to compile the object after importing the source code. You may press OK on this dialog and then do a full build to find out where the error is and then use Edit Source to resolve the conflict. 

BTW, the reason that others don't have this issue may be that they don't have local changes that would result in a conflict like yours. If your local changes are not important, a simple solution would be remove your local workspace folder and connect to the server to create the workspace again.

Regards,

Tom Jiang