Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure on detecting changes on GameData on MM #20

Open
Lisias opened this issue Apr 8, 2023 · 2 comments
Open

Failure on detecting changes on GameData on MM #20

Lisias opened this issue Apr 8, 2023 · 2 comments
Assignees
Labels
bug Something isn't working Not My Fault Not my Fault! I'm innocent! :)

Comments

@Lisias
Copy link

Lisias commented Apr 8, 2023

On net-lisias-ksp/KSP-Recall#65 I had my arse bitten by MM (Forum), that I was still using on my Acceptance tests (the ones I do before shipping things).

Evidences pinpoints the code that checks the ConfigCache integrity.

MM (Forum) is terribly prone to false negatives because it doesn't recon that DIGEST IS NOT the same as IDENTITY, so on my fork I added a new criteria to help on reducing the false negatives.

So, when I updated Recall to 0.4.0.0, I'm betting I had caused (by absolute lack of luck) a digest collision - and so the Config Cache wasn't invalidated and I tested a bad code using an old Cache from the time the code wasn't bad, and didn't noticed anything wrong due some failsafes that Recall have. I should probably issue a warning on the KSP.log when a Recall failsafe is triggered.

Anyway. I had a digest collision on the GameData, but MM (forum) still adds an additional digest for the symbols created by code (see ModuleManagerSupport.cs on my add'ons), and I think that digest should had detect the change even on the MM (Forum).

Since this specific piece of code is still similar on this Fork, it's reasonable to assume that this potential weakness is also affecting this fork.

This issue is to remind me to look on this matter and enhance the Cache integrity code so we can close yet another door for a potential problem.

@Lisias Lisias self-assigned this Apr 8, 2023
@Lisias Lisias added the enhancement New feature or request label Apr 8, 2023
@Lisias Lisias changed the title Failure on detecting changes on GameData on MM (Forum) Failure on detecting changes on GameData on MM Jun 16, 2023
@Lisias
Copy link
Author

Lisias commented Jun 16, 2023

HA!!! I WAS INNOCENT AFTER ALL!!! :) (or, at very least, not entirely guilty!!!)

Fellow Kerbonaut kurgut was bitten by this bug too!!!

So there's still one cache validation bug left on the code for sure!!!! :)

His last change was Rational Resources (what's probably only the trigger, as I didn't used it when I got screwed) and some custom made patches (and these ones, I had on the my affected rig!).

By inspecting these new material I hope to find some common ground that will lead me to the cause of the problem!!!

KSP.log.zip

More detailed info: Logs for Lisias.zip

@Lisias Lisias added bug Something isn't working support support (no bug) Not My Fault Not my Fault! I'm innocent! :) and removed enhancement New feature or request labels Jun 16, 2023
@Lisias Lisias removed the support support (no bug) label Mar 10, 2024
@Lisias
Copy link
Author

Lisias commented Mar 10, 2024

Why I added the "Support" label on this? o.O

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Not My Fault Not my Fault! I'm innocent! :)
Projects
None yet
Development

No branches or pull requests

1 participant