Skip to content

fix: port CSS lock/sweep hardening - #144

Open
bourgeoa wants to merge 2 commits into
mainfrom
fix/clear-lock
Open

fix: port CSS lock/sweep hardening#144
bourgeoa wants to merge 2 commits into
mainfrom
fix/clear-lock

Conversation

@bourgeoa

Copy link
Copy Markdown
Member
  • scope the 4 expiring-storage sweeps to their own containers
  • bound lock-acquisition retries (attemptSettings)
  • guard proper-lockfile updateLock race via patch-package
  • add adapter storage @id (patch-package) for the sweep override
  • fix SafeBaseLoginAccountStorage build (TS2415, generator types)

- scope the 4 expiring-storage sweeps to their own containers
- bound lock-acquisition retries (attemptSettings)
- guard proper-lockfile updateLock race via patch-package
- add adapter storage @id (patch-package) for the sweep override
- fix SafeBaseLoginAccountStorage build (TS2415, generator types)
The FileSystemResourceLocker override targets an instance that only exists in configs using the file resource locker. test.json uses the memory locker, so keeping the override in pivot-overrides.json broke the test suite. Move it to a dedicated file imported only by the file-locker configs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Memory leak on maintenance clear locks, cookies

1 participant