JohanVrijdaghs
Member
- Joined
- Jan 27, 2018
- Messages
- 43
- Reaction score
- 12
- Country
he just changed the chrome edition from a 87 to 88, as also the chromedriver, for the time being: it worksYou're going to have to call your neighbour again
Tell them to create a file called logging.yaml in the config/ sub-directory that looks like this:
Change the path to the output log file to something suitable.Code:version: 1 formatters: standard: format: "%(asctime)s.%(msecs)03d | %(message)s" datefmt: "%H:%M:%S" handlers: file: class: "logging.FileHandler" formatter: "standard" filename: "c:/temp/vasl-templates.log" mode: "w" loggers: vasl_mod: level: "DEBUG" handlers: [ "file"] vassal_shim: level: "DEBUG" handlers: [ "file" ]
Create another file called logback-test.xml in the same directory as vasl-templates.exe (i.e. not the same directory as above) that looks like this:
Change the path to the output log file to something suitable.Code:<configuration debug="false"> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>c:/temp/vassal-shim.log</file> <append>False</append> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss} | %msg%n</pattern> </encoder> </appender> <root level="WARN"> <appender-ref ref="FILE" /> </root> <logger name="vassal_shim.VassalShim" level="DEBUG" /> <logger name="vassal_shim.LabelArea" level="WARN" /> </configuration>
Restart the program, try to update a scenario, so that the error happens again. Then post the log files here.