Memento.update does not always work when an extension is starting up

[karrtikr]

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.75.0-insider (user setup)
OS: Windows_NT x64 10.0.22518

Steps to Reproduce:

See ExtensionContext.globalState: https://code.visualstudio.com/api/references/vscode-api#ExtensionContext:

await globalState.update(<key>, newValue);
const valueAfterUpdate = globalState.get(<key>, undefined);
if (JSON.stringify(valueAfterUpdate) != JSON.stringify(newValue)) {
    // Error: This condition should never be true, but it is being hit.
}

This has been failing for Python extension when type of newValue is string, and in some cases an array object.

Workaround: We've observed that if we reset the storage first, and then try updating it, it works in most cases: (implementation in Python extension)

await globalState.update(<key>, undefined);
await globalState.update(<key>, newValue);
const valueAfterUpdate = globalState.get(<key>, undefined);
if (JSON.stringify(valueAfterUpdate) != JSON.stringify(newValue)) {
    // This condition is not hit.
}

Once the extension completely finishes loading, we do not see this bug.

[bpasero]

Does this reproduce in a minimal hello world extension? And if so, please share the code of a minimal extension.

[VSCodeTriageBot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!