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

Resolved Git issues: Unable to refresh

  1. Issue
0
Votes
Undo
  1. Dan Black
    Dan Black
  2. PowerBuilder
  3. Wednesday, 15 January 2020 22:45 PM UTC

Hi,

I am using PB2017 R3 Build 1915.

I am trying to merge a feature branch and develop branch together. I received a number of conflicts (which was expected), and worked through resolving the conflicts (outside of the PB IDE). I committed my merge conflict resolutions to the branch and now i want to have the changes show in PB.

My understanding of things is that I need to refresh the target/workspace and do an incremental build and all will be right with the world.

However, refresh gives an error each time, see attached compile_failure.PNG. Clicking ok doesn't do much, it seems to stop the refresh - it jumps from "Importing" to the "Successful get of ..." section.

Inspecting the objects, or even just the first one that the error came up for ("Importing datawindow.srd..."), with edit source or edit shows that the latest changes have not been refreshed.

Refreshing multiple times does seem to work it's way through other objects, still failing but on the next object. But again, inspecting the code shows that the changes have not been refreshed (imported) into the PBLs.

Has anyone encountered this issue? Have I done something horribly wrong (other than choosing to program for a living - lol, that's where I'm at now)?

Thanks,

Dan

 

 

Attachments (1)
compile_failure.PNG compile_failure.PNG
  1. Git
  2. PowerBuilder
Unable to use AES256 DB Encryption with Power buil...
Stopping an exception from bubbling up the call st...
Responses (3)
Dan Black
Dan Black Accepted Answer Pending Moderation
  1. Wednesday, 15 January 2020 23:47 PM UTC
  2. PowerBuilder
  3. # 1

Update:

I also thought I'd try rebuilding the pbls from the command line with orcascript.

start session
set debug false
set exeinfo property companyname "Microquest Inc."
set exeinfo property productname "Healthquest EMR"
set exeinfo property copyright "1993-2020"
set exeinfo property description "Healthquest Electronic Medical Record System by Microquest Inc."
set exeinfo property fileversion "4"
set exeinfo property fileversionnum "4.3.30.0"
set exeinfo property productversion "4"
set exeinfo property productversionnum "4.3.30.0"
scc set connect property logfile "createpbls.log"
scc set connect property localprojpath ".\"
scc connect offline
scc set target "healthquest.pbt" "importonly"
scc refresh target full
build library "healthq.pbl" "" pbd
build library "base.pbl" "" pbd
build library "system.pbl" "" pbd
build library "client.pbl" "" pbd
build library "appoint.pbl" "" pbd
build library "claims.pbl" "" pbd
build library "charting.pbl" "" pbd
build library "dddw.pbl" "" pbd
build library "claimrep.pbl" "" pbd
build library "clienrep.pbl" "" pbd
build library "msystem.pbl" "" pbd
build library "ap.pbl" "" pbd
build library "ah.pbl" "" pbd
build library "bsystem.pbl" "" pbd
build library "gl.pbl" "" pbd
build library "scans.pbl" "" pbd
build library "letters.pbl" "" pbd
build library "worklist.pbl" "" pbd
build library "referral.pbl" "" pbd
build library "wcbrr.pbl" "" pbd
build library "xml.pbl" "" pbd
build library "comms.pbl" "" pbd
build library "spb.pbl" "" pbd
build library "mpb.pbl" "" pbd
build library "hqforms.pbl" "" pbd
build library "hqforms2.pbl" "" pbd
build library "oldcode.pbl" "" pbd
build library "prescribeit.pbl" "" pbd
build executable "healthquest.exe" "hqicon.ico" "mbs_hq4.pbr" "YYYYYYYYYYYYYYYYYYYYYYYYYYYY" newvstylecontrols
scc close
end session

The log file gets to "Bootstrapping Application..." there are no errors in the command line, but in the event viewer I can see that orcascr170.exe has crashed (see attached).

Attachments (1)
appcrash.PNG appcrash.PNG
Comment
There are no comments made yet.
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 January 2020 06:53 AM UTC
  2. PowerBuilder
  3. # 2

When you still see the compile error while refreshing, it indicates that there are still unresolved syntax errors caused by the merge. You may try refreshing the project one PBL a time to narrow down the objects in error and fix them using edit source one by one. After you went through all the PBLs, you should be able to do a full build in PB. And then you OrcaScript should work.

Comment
Dan Black
  1. Dan Black
  2. Friday, 17 January 2020 19:39 PM UTC
This could have been the issue, but I have confirmed that there are no syntax errors.



In fact, between one of the .sru files it was failing on and one from a workspace with no issues, they are exactly the same, at the byte level.
  1. Helpful
Tom Jiang @Appeon
  1. Tom Jiang @Appeon
  2. Friday, 14 February 2020 01:28 AM UTC
Another thing you may check is that some git environment changes the line break CR+LF v.s. LF, which would also cause a compile error and make it fail to import/refresh an object.
  1. Helpful
There are no comments made yet.
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Thursday, 16 January 2020 08:23 AM UTC
  2. PowerBuilder
  3. # 3

Hi Dan,

yes, OracScript is triggy with complex applications.

Try to replace

scc refresh target full

with

scc refresh target 3pass
build application full

 

HTH,

René

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.