You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
desk: .wslconfig value parsing differs from WSL (repeated keys, trailing comments, line continuation) #387
Follow-ups from the re-check of #354 (comment #354 (comment)). All are older than #354; start-desk.ps1 reads .wslconfig differently from WSL's own parser (configfile.cpp) in these cases:
Repeated keys: the script takes the last value, WSL the first. A memory cap raised by hand can be lowered.
# comment after a value:memory=20GB # raised is treated as unreadable and replaced with the default.
A value line ending in \: WSL joins the next line onto it, so a key on that line can be swallowed without anyone noticing.
Each needs a test row that matches WSL's parser (the re-check ported it to Python and fuzzed it; reuse that approach). Fail-closed: when unsure, refuse and say why, never overwrite a value the owner set.
Activity
desk: pin the .wslconfig read-back and the fuzz refusals in tests (#387…
desk: read .wslconfig values the way WSL does (repeated keys, comment…
desk: read .wslconfig values the way WSL does (repeated keys, comment…
desk: read .wslconfig values the way WSL does (repeated keys, comment…
desk: read .wslconfig values the way WSL does (repeated keys, comment…