I am trying to clone a ChangeMan ZMF git connector in Vs Code. It is getting errors from the git-remote-ZMF.exe. It fails with both the Rest Service 8.3.0 and 8.3.1 with hofix.

S C:\\Users\\bre6052\\Git_ZMF> git clone ZMF://zmf_serzmfp/AT01000712 zmfRepo

Cloning into 'zmfRepo'...

Traceback (most recent call last):

 File "git-remote-ZMF.py", line 1534, in <module>

 File "git-remote-ZMF.py", line 1522, in main

 File "common.py", line 378, in init_logging

 File "logging\\__init__.py", line 2040, in basicConfig

 File "logging\\__init__.py", line 1169, in __init__

 File "logging\\__init__.py", line 1201, in _open

FileNotFoundError: [Errno 2] No such file or directory: 'C:\\\\Users\\\\bre6052\\\\Git_ZMF\\\\Logs\\\\git-ZMF.log'

[92348] Failed to execute script 'git-remote-ZMF' due to unhandled exception!

fatal: remote helper 'ZMF' aborted session

PS C:\\Users\\bre6052\\Git_ZMF> git clone ZMF://zmf_serzmfp/AT01000712 AT01000712

Hi Lisa,

Did you define a logfile directory and create the environment variable which tells the git ZMF connector where the logfile should go ?

i.e. (from the ZMF user guide):

Define the environment variable which tells the facility where to write log messages (for example):

ZMF_GIT_LOGFILE=D:\\GitDev\\ZMF\\logs\\git-ZMF.log

If you have already done this please use the command    set    (no operands) in a command window to list all environment variables so we can see what it has been set to ?

Thanks

All the best - Steve

I just noticed that the manual doesn't explicitly call out the need to create the logfile directory prior to using the gitZMF connector. It must exist.

I have submitted a ticket to get that added to the documentation.

Yes.  I have defined the log file as an enviromental variable.

But did you create the logfile directory ?  The error you are showing has, in the past, been 100% because the logfile directory does not yet exist.

In some future release of this function we will create it for you but, right now, it needs to exist before you try to use the function.

Yes, the directory is created, and data is being written to the logfile.

And you're still seeing the same error message ?, i.e.

FileNotFoundError: [Errno 2] No such file or directory: 'C:\\\\Users\\\\bre6052\\\\Git_ZMF\\\\Logs\\\\git-ZMF.log'

I don't understand that if the logfile is being written to.

Can you attach the logfile and the command window output from your latest attempt to use the gitZMF connector ?

Thanks

PS C:\\Users\\bre6052\\ZMFGit> git clone ZMF://zmf_serzmfn/TE01001110 GitR
Cloning into 'GitR'...
Traceback (most recent call last):
  File "git-remote-ZMF.py", line 1534, in <module>
  File "git-remote-ZMF.py", line 1527, in main
  File "git-remote-ZMF.py", line 47, in __init__
  File "git-remote-ZMF.py", line 268, in parse_url
  File "json\\__init__.py", line 346, in loads
  File "json\\decoder.py", line 337, in decode
  File "json\\decoder.py", line 355, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
[25636] Failed to execute script 'git-remote-ZMF' due to unhandled exception!
fatal: remote helper 'ZMF' aborted session
PS C:\\Users\\bre6052\\ZMFGit> 

It looks as if the json parsing code has developed a disliking for the output from the zowe zmf cli command. I'm at a loss as to why this should suddenly be happening to code that has been working fine for 2 years.

I have been able to recreate the problem.

The ideal solution would be to work out why this has suddenly stopped working. I can see how to fix this with a code change but that will take some time. It would be much better if I can work out why it has stopped working.

More on this to follow

All the best - Steve

I uninstalled @rocketsoftware/zmf-cli-plugin and installed microfocus-zmf-cli-plugin-2.0.4.tgz.   I am now able to use git to clone my package as a repository

I uninstalled @rocketsoftware/zmf-cli-plugin and installed microfocus-zmf-cli-plugin-2.0.4.tgz.   I am now able to use git to clone my package as a repository

That's good to know - thanks Lisa.

We'll be looking at what changed in the 2.0.8 cli to cause this problem.