Open Noggog opened 2 weeks ago
This might be a case of correlation not being causation, but as soon as 0.27 released my syncs started failing during our testing of ticket #48. Does Spriggit rely on the internet at all for this synchronization process?
It does rely on internet
https://mutagen-modding.github.io/Spriggit/translation-packages/
as well as downloading past CLI
releases when translating older targets.
I would like to get it to a spot where it might not hit the internet at all after the first "run" against a specific version. (but dev builds might wig it out and always redownload things)
Are you getting the FileNotFoundException
exception when having your errors?
Are you getting the
FileNotFoundException
exception when having your errors?
It was the exception that was occurring when 0.27 released.
From the log I posted in #48
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.IO.FileNotFoundException: Could not find file 'C:\Users\Admin\AppData\Local\Temp\n1vfzhhd.s40\CheatTerminal.esp'.
File name: 'C:\Users\Admin\AppData\Local\Temp\n1vfzhhd.s40\CheatTerminal.esp'
Gotcha. Looking closer, your FileNotFound
error was failing due to:
0.27.0-d
version (probably due to our dev version tinkering)I think that's a different thing to improve, which I've made a card for here #87
This card is specifically around a FileNotFound
error where the missing file is a dll required for the translation packages
System.IO.FileNotFoundException: File name: 'Mutagen.Bethesda.Serialization.Yaml, Version=1.23.0.0...
which i think is a slightly different cause/issue
Are you still getting the FileNotFound exceptions when running currently? If so, is it the #87 style?
I think that's a different thing to improve, which I've made a card for here #87
When I worked on a project that reduced 8 mainframes into one giant Spring Batch project, we ran into these similar kinds of esoteric errors. A lot of "FileNotFound" "Class cast exceptions from Object to Object" I even have one printed out and posted on my wall that says "Cannot cast from java.com.dao.Fas91 to java.com.dao.Fas91" which we still to this day never solved. Anyway, what we eventually had to do was starting throwing our own custom exceptions from within the handlers so that when caught, we could use instanceof to figure out what actually was the problem. Maybe the UI could use that as some kind of way to determine what to display to the user? Giving the user helpful information when an exception (edge case) occurs is always hard because you never know how the user is going to use your program until they do. But in this case, had it printed something like "Expected version 0.26, but got unexpected 0.27.0-d version" that would at least make me think I'm out of date.
Are you still getting the FileNotFound exceptions when running currently? If so, is it the #87 style?
No. I've actually batch streamed the process of sorting -> syncing to git where instead of loading the spriggit UI, I just run a BAT file then it sorts and syncs it to Git in one click.
Probably can nuke temp and try again? I thought it did this already, but can double check the logic