go to post Shanwen Liu · Dec 12 I still haven't figured out exactly what is causing this behavior, but I have found a fix: export all (force) forces a sync so CSP changes become known to git. Not the most ideal or elegant fix since I have to export every single file every time, but it works. Note that the normal export does not work. From my cursory glance at the code base, this seems to suggest that something is off about the "IsTempFileOutdated" function in the "ExportItem" function. I suspect it's returning false for me even though it should return true. Would love your thoughts on this!
go to post Shanwen Liu · Dec 11 Adding to source control seems to be fine on my end. The only weird thing is the output always come in duplicate (i.e. it tells me that it's been added twice, like the example in the post). Also, the new CSP files are added automatically for some reason - upon creating and saving, I don't need to run git add for it to be added. It completely skips over being untracked. I'm also noticing that it says "C:\InterSystems\IRIS\mgr\repo\TESTDB\csp\testdb\wrc.csp removed from uncommitted list" whenever I save changes in a CSP file, but that's the only output.
go to post Shanwen Liu · Dec 11 The only non-default mapping is for CSP. /CSP/ /csp/testdb csp/testdb/ The entire workspace definition is as follows: { "folders": [ { "uri": "isfs://local-test:TESTDB/csp/testdb?csp" }, ], "settings": { "objectscript.conn": { "active": true }, "objectscript.showExplorer": false } } The .vscode subdirectory is empty What perplexes me is how it knows about new and deleted files, but not any file changes. If it matters, I manually added these files with git add before knowing about baselining and at the time the workspace might not have been defined properly. Do you think that could have broken something? Edit: I tried again in a new namespace and used a properly defined workspace, and the same issue persists, so it's probably not an initial workspace definition issue.
