yaml parse syntax?

[devOramaMan]

I get issues when parsing the configuration file (me: p4transfer newb).

Python 3.10.12

Does someone have a example config file? the expected syntax for each field? etc

ruamel.yaml.parser.ParserError: expected '', but found ('',)
in "./transfer.cfg", line 12, column 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/andreas/p4transfer/P4Transfer.py", line 2626, in replicate
self.setupReplicate()
File "/home/andreas/p4transfer/P4Transfer.py", line 2576, in setupReplicate
self.readConfig()
File "/home/andreas/p4transfer/P4Transfer.py", line 2338, in readConfig
raise P4TConfigException('Could not read config file %s: %s' % (self.options.config, str(e)))
P4TConfigException: Could not read config file ./transfer.cfg: expected '', but found ('',)
in "./transfer.cfg", line 12, column 1

2 # Save this output to a file to e.g. transfer.yaml and edit it for your configuration
3
4 # counter_name: Unique counter on target server to use for recording source changes processed. No spaces.
5 # Name sensibly if you have multiple instances transferring into the same target p4 repository.
6 # The counter value represents the last transferred change number - script will start from next change.
7 # If not set, or 0 then transfer will start from first change.
8 counter_name:0
9
10 # case_sensitive: Set this to True if source/target servers are both case sensitive.
11 # Otherwise case inconsistencies can cause problems when conversion runs on Linux
12 case_sensitive: True
13
14 # historical_start_change: Set this if you require P4Transfer to start with this changelist.
15 # A historical start is useful if you have 100,000 changelists in source server and want to only
16 # transfer the last 10,000. Set this value to the first change to be transferred.
17 # Once you have set this value and started a transfer DO NOT MODIFY IT or you will potentially
18 # mess up integration history etc!!!!!
19 # IMPORTANT NOTE: setting this value causes extra work to be done for every integration to adjust
20 # revision ranges - thus slowing down transfers.
21 # If not set, or 0 then transfer starts from the value of counter_name above, and assumes that ALL HISTORY
22 # of included files is transferred.
23 historical_start_change:
24
25 # instance_name: Name of the instance of P4Transfer - for emails etc. Spaces allowed.
26 instance_name: Perforce Transfer from XYZ
27