Can't get 4.6.36 to work. Not responding after installation

braca19452f9m · June 9, 2024, 10:17pm

Well, it’s my fault for trying to install the latest version. I was on 4.6.16 and installed 4.6.36. The only thing that I get is “not responding” after installing. I’m running Windows 11. Here’s a list of what I’ve tried.

Ran as Administrator, no dice. Deleting all folders from %appdata% Local and Roaming and then reinstalling. Tried removing files via Terminal, same result. When I remove everything, the program asks me to install dependencies and plug in the roaster before clicking yes. I do so, it installs dependencies, but then it just goes to “not responding” after launch. The only thing I can do is install RoasTime 3.4.1. Please, I can make do somehow with 3.4.1, but if you can at least give me some link to download the 4.6.16, which was working and will be again, if I can get my hands on it, I’d appreciate it. The only thing I can download from Aillio is 4.6.36. Thanks in advance for any help.

Edit: So, I’ve tried and managed to install it on my desktop, which I can’t carry around as it weighs a ton. I have even tried transferring the installation to the laptop, folder by folder, but to no avail. There must be something bothering it, but I can’t quite figure out what. And I surely can’t imagine why 4.6.16 and 3.4.1 work.

Edit 2: Well, I’ve found an old download of the 4.3.2 version, and it also works. For now, I’m keeping that one, but there is something wrong with the new one. Here’s the log to facilitate things.

{“caller”:{“PC”:5372492331,“Func”:{},“Function”:“github.com/mattscamp/zerousb.(*ZeroUSB).Log",“File”:“C:/Users/runneradmin/go/pkg/mod/github.com/mattscamp/[email protected]/zerousb.go”,“Line”:87,“Entry”:5372492288},“version”:"v1.11.2”}
[2024-06-10T00:32:33.710Z] (12) [ERROR] | roastime-main | ERROR from backend!
{“version”:“PACKAGE_VERSION”,“error”:“The operation was aborted”}
[2024-06-10T00:32:33.711Z] (13) [ERROR] | roastime-main | ERROR from comms!
{“version”:“PACKAGE_VERSION”,“error”:“The operation was aborted”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“roastime-main version changed, blowing up deps directory.”,“sequence”:“1”,“time”:1717981174455,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Nuking the dependencies.”,“sequence”:“2”,“time”:1717981174456,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Checking for updates to apply.”,“sequence”:“3”,“time”:1717981174456,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Starting dependencies…”,“sequence”:“4”,“time”:1717981174457,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“5”,“time”:1717981174522,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“6”,“time”:1717981174522,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Checking for updates to apply.”,“sequence”:“1”,“time”:1717981176649,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Starting dependencies…”,“sequence”:“2”,“time”:1717981176651,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“3”,“time”:1717981176772,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“4”,“time”:1717981176773,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“5”,“time”:1717981176785,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“6”,“time”:1717981176785,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“roastime-main is at version 4.6.36”,“sequence”:“0”,“time”:1717981176632,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“7”,“time”:1717981177794,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“8”,“time”:1717981177816,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“9”,“time”:1717981177834,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“10”,“time”:1717981177851,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“11”,“time”:1717981177853,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“12”,“time”:1717981177853,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“13”,“time”:1717981177853,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“14”,“time”:1717981177853,“version”:“2.0.0”}
{“context”:{“logLevel”:30,“service”:2,“version”:“4.6.36”},“message”:“Loading packaged version of FE as override path did not exist.”,“sequence”:“15”,“time”:1717981178857,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“16”,“time”:1717981178909,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“17”,“time”:1717981178933,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“18”,“time”:1717981178952,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“19”,“time”:1717981178972,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“20”,“time”:1717981178990,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“21”,“time”:1717981179006,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“22”,“time”:1717981179024,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“23”,“time”:1717981179040,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“24”,“time”:1717981179059,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“25”,“time”:1717981179059,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“26”,“time”:1717981179059,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“27”,“time”:1717981179060,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“28”,“time”:1717981179060,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“29”,“time”:1717981179060,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“30”,“time”:1717981179060,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“31”,“time”:1717981179060,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“32”,“time”:1717981179923,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“33”,“time”:1717981179924,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“34”,“time”:1717981179954,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“35”,“time”:1717981179978,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“36”,“time”:1717981179999,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“37”,“time”:1717981180010,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“38”,“time”:1717981180020,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“39”,“time”:1717981180021,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“40”,“time”:1717981180021,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“41”,“time”:1717981180021,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“42”,“time”:1717981180021,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“43”,“time”:1717981180021,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“44”,“time”:1717981180034,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“45”,“time”:1717981180034,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“46”,“time”:1717981180063,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“47”,“time”:1717981180071,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“48”,“time”:1717981180081,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“49”,“time”:1717981180090,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“50”,“time”:1717981180099,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“51”,“time”:1717981180108,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“52”,“time”:1717981180117,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“53”,“time”:1717981180127,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“54”,“time”:1717981180136,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“55”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“56”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“57”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“58”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“59”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“60”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“61”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“62”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“63”,“time”:1717981180138,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“64”,“time”:1717981180952,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“65”,“time”:1717981180967,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“66”,“time”:1717981180980,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“67”,“time”:1717981180989,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“68”,“time”:1717981180990,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“69”,“time”:1717981180990,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“70”,“time”:1717981180990,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“71”,“time”:1717981180990,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“72”,“time”:1717981181025,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“73”,“time”:1717981181037,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“74”,“time”:1717981181050,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“75”,“time”:1717981181061,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“76”,“time”:1717981181072,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“77”,“time”:1717981181084,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“78”,“time”:1717981181094,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“79”,“time”:1717981181107,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“80”,“time”:1717981181120,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“81”,“time”:1717981181134,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“82”,“time”:1717981181143,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“83”,“time”:1717981181156,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“84”,“time”:1717981181168,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“85”,“time”:1717981181180,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“86”,“time”:1717981181192,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“87”,“time”:1717981181205,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“88”,“time”:1717981181219,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“89”,“time”:1717981181234,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“90”,“time”:1717981181243,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“91”,“time”:1717981181256,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“92”,“time”:1717981181269,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“93”,“time”:1717981181284,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“94”,“time”:1717981181298,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“95”,“time”:1717981181309,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“96”,“time”:1717981181322,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“97”,“time”:1717981181337,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“98”,“time”:1717981181352,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“99”,“time”:1717981181362,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“100”,“time”:1717981181366,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“101”,“time”:1717981181366,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“102”,“time”:1717981181366,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“103”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“104”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“105”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“106”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“107”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“108”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“109”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“110”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“111”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“112”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:"roastime-backend: child process exited with code

braca19452f9m · June 10, 2024, 1:12am

-4058",“sequence”:“113”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“114”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“115”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“116”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“117”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“118”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“119”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“120”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“121”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“122”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“123”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“124”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“125”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“126”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“127”,“time”:1717981181367,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“128”,“time”:1717981182008,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“129”,“time”:1717981182050,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“130”,“time”:1717981182071,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“131”,“time”:1717981182085,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“132”,“time”:1717981182099,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“133”,“time”:1717981182109,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“134”,“time”:1717981182122,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“135”,“time”:1717981182134,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“136”,“time”:1717981182144,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“137”,“time”:1717981182156,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“138”,“time”:1717981182169,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“139”,“time”:1717981182181,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“140”,“time”:1717981182191,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“141”,“time”:1717981182203,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“142”,“time”:1717981182216,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“143”,“time”:1717981182226,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“144”,“time”:1717981182238,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“145”,“time”:1717981182254,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“146”,“time”:1717981182267,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“147”,“time”:1717981182284,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“148”,“time”:1717981182299,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“149”,“time”:1717981182308,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“150”,“time”:1717981182321,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“151”,“time”:1717981182335,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“152”,“time”:1717981182349,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“153”,“time”:1717981182359,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“154”,“time”:1717981182371,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“155”,“time”:1717981182384,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“156”,“time”:1717981182397,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“157”,“time”:1717981182407,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“158”,“time”:1717981182420,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“159”,“time”:1717981182433,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“160”,“time”:1717981182443,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“161”,“time”:1717981182455,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“162”,“time”:1717981182469,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“163”,“time”:1717981182482,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“164”,“time”:1717981182492,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“165”,“time”:1717981182505,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“166”,“time”:1717981182519,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“167”,“time”:1717981182534,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“168”,“time”:1717981182544,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“169”,“time”:1717981182557,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“170”,“time”:1717981182570,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“171”,“time”:1717981182584,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“172”,“time”:1717981182597,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“173”,“time”:1717981182608,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“174”,“time”:1717981182621,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“175”,“time”:1717981182635,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“176”,“time”:1717981182648,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“177”,“time”:1717981182659,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“178”,“time”:1717981182671,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“179”,“time”:1717981182685,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“180”,“time”:1717981182702,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“181”,“time”:1717981182716,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“182”,“time”:1717981182726,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“183”,“time”:1717981182739,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“184”,“time”:1717981182754,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“185”,“time”:1717981182769,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“186”,“time”:1717981182785,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“187”,“time”:1717981182799,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“188”,“time”:1717981182810,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-comms-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from comms!”,“sequence”:“189”,“time”:1717981182823,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“190”,“time”:1717981182837,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“191”,“time”:1717981182850,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“192”,“time”:1717981182854,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“193”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“194”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“195”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“196”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“197”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“198”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“199”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“200”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“201”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“202”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“203”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“204”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“205”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“206”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“207”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“208”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“209”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“210”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“211”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“212”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“213”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“214”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“215”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“216”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“217”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“218”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“219”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“220”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“221”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“222”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“223”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“224”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“225”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“226”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“227”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“228”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“229”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“230”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“231”,“time”:1717981182855,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“232”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“233”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“234”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“235”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“236”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“237”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“238”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“239”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“240”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“241”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“242”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“243”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“244”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“245”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“246”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“247”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“248”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“249”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“250”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“251”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“252”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-comms: child process exited with code -4058”,“sequence”:“253”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“254”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“255”,“time”:1717981182856,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“256”,“time”:1717981183034,“version”:“2.0.0”}
{“context”:{“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“roastime-backend: child process exited with code -4058”,“sequence”:“257”,“time”:1717981183035,“version”:“2.0.0”}
{“context”:{“err”:“spawn C:\Users\\AppData\Local\RoasTime\app-4.6.36\resources/deps/roastime-backend-win-x64.exe ENOENT”,“logLevel”:50,“service”:2,“version”:“4.6.36”},“message”:“ERROR from backend!”,“sequence”:“258”,“time”:1717981183091,“version”:“2.0.0”}

jeffaillio · June 11, 2024, 6:26am

Hey @braca19452f9m, thanks for taking the time to write out your troubleshooting steps. We’re looking into this, but it seems like the deps failed to completely install on your machine.

braca19452f9m · June 11, 2024, 1:07pm

Thank you so much, jeffaillio. I understand the what, but I don’t get the why. In the meantime, I’ve tried manually adding exceptions to the firewall, disabling said firewall and antivirus, reinstalling dependencies with older version and then trying again. Also worth mentioning that, while I do get the prompt to allow dependencies with all previous versions, the prompt doesn’t arrive with 4.6.36 and goes straight to launch. It almost seems like the installer is truncated at a certain point. Since you’ve linked another thread with the same problem, it must be that some machines have problems with it, depending on hardware, but you’ll be able to figure it out since you have the right tools. I don’t think this is something that could be relevant, but I’ll throw it out there. The OS on my laptop is in Italian, while on my desktop, where 4.6.36 manages to install, is in English. Once again thank you very much for looking into it. I do like my apps being the latest version.

bab · June 11, 2024, 4:56pm

Jeff-

To add to the data…

I’m having a similar issue to @braca19452f9m with a fresh install on a new replacement laptop with Win11 Pro. To this point I’ve not had issues with installing RT-2, -3 or -4 on any of three earlier laptops. Something odd about my current instance, so the post above stands out for me.

Bruce

jeffaillio · June 13, 2024, 8:10am

Hey all, thanks for the additional info. Just a quick follow up here, but could you check your task manager and see how many roastime related processes are running?

braca19452f9m · June 13, 2024, 12:04pm

The working (previous) one gives 8, while 4.6.36 gives 4, probably due to its inability to launch dependencies, since those are the 4 missing.

Edit: On my desktop, where I manage to install the 4.6.36 version, it also gives 8 in the task manager, which is normal. I really have no idea what could be preventing it on the laptop.

Edit 2: Also, the folder roast-time, in the Roaming folder, is not created during installation on the laptop, just the RoasTime folder. The proper installation on the desktop lasts longer.

bab · June 13, 2024, 6:53pm

Looks like a total of 4…

Bruce

braca19452f9m · June 18, 2024, 8:58pm

Just to add a couple more things. I’ve tried installing in safe mode, but got the same result. I’ve also noticed a strange thing. If I go into properties and select the “Run as administrator” box, the installer will fail to launch, but if I right click on the file and select “Run as administrator” from the dropdown menu it will launch. But this is true for all versions, or at least those in my possession. Since I think it might be something related to HW configuration, I’ll just leave that here too.

Intel i7 8550u 1.8GHz
Intel UHD graphics + AMD Radeon R7 M340
8GB RAM
Intel 256GB SSD

I am working with 4.3.2 currently, since I couldn’t find the 4.6.16, so I will be patient.

Simone Lia: Patience – cartoon | Life and style | The Guardian

jeffaillio · June 19, 2024, 9:23am

Thanks @braca19452f9m we’ve been troubleshooting this and similar issues through a couple of support cases, and they mainly appear to be device specific. It seems that the installation of dependencies sometimes gets blocked for various reasons, however, in many cases, users have had success by manually installing the drivers using Zadig.

If you’re willing to give it a try, the instructions are as follows:

First power up your Bullet
When it is ready connect it to your laptop/PC using the supplied USB-cable
Download Zadig from here: https://github.com/pbatard/libwdi/releases/download/v1.4.1/zadig-2.7.exe 12
Run the downloaded file (zadig-2.7.exe)
Choose “Options” and make sure “List All Devices” has been checked
Choose the “Aillio LTD….” Interface. If there is more than one interface choose the one that ends with “1”
Click ”Install”
When the installation has been completed then restart RoasTime 4

Jeff

braca19452f9m · June 19, 2024, 1:43pm

I now see I haven’t listed Zadig in my troubleshooting steps, however I have tried it exactly with the suggested steps. I’m very thorough so I went through all possible solutions before posting here. Sincerely, I cannot see how I can fix this. I do manage to fix everything when there’s something I can do, but I think I’ve ran out of options here long ago. Even tried to compare the installers with Hex Editor, hoping I’d find something, but 4.3.2 and 4.6.36 have more differences than similarities. And I would guess that if the problem were within the drivers, I’d also have issues installing other RoasTime 4 versions. Let me be clear, I am roasting with the 4.3.2 version. I could use 4.6.16 if it were available, as I was prior to the installation, or any other RoasTime 4 version. Shouldn’t those versions have problems if it were the driver, or anything else that I could do? Also, shouldn’t the program itself install without the roaster connected and launch dependencies later on when you connect the roaster? Oh yes, it should, as do all the versions prior to this one, but with 4.6.36 it does not. If you look at my posts, this is the first time I’ve ever reported an issue. Yeah, there was the thing with the roaster hanging if you press PRS on your computer to finish the roast when the dead man alarm goes off, but I just press the PRS on the machine now. What this means is that all conventional troubleshooting has failed and I need help. If I get it good, if not I’ll just use the 4.3.2.

In summary, the 4.6.36 version fails to launch after installation. It’s just a white “Not responding” window. It does not launch dependencies, it does not launch proxy, it does not launch comms, it does not launch client, it just hangs there. And please believe me when I say that I 've tried everything and beyond. The one thing that comes to mind is trying one of those uninstallers that claim to remove everything, but I don’t see how that would help. However, I haven’t given up, although I know there’s nothing I can do, and will continue my futile attempts.

mcaillio · June 22, 2024, 11:45pm

Hey @braca19452f9m , sorry for the late reply. I am traveling with my family right now so haven’t been as available as usual. I think at this point the best way to figure this out is for me to jump on a call with you. I made some changes to the driver installation flow (runs extra checks to see if the driver is already installed) in that version and is the only thing I can imagine may be potentially causing your issue. Maybe one of those checks starts and stalls for some reason which would block the thread and possibly result in what you are experiencing.

Are you on the public slack? Can you send me a DM and we can chat this week?

mcaillio · July 16, 2024, 4:55pm

FYI - something broke with path escaping in this update of dependencies. We were able to fix this issue by renaming the user’s path to not have a space. We will get a fix out, but feel free to create a new user in the meantime if you have a similar issue.