id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1510	modifying SDMF file fails when tahoe.cfg's k/N differs from file	warner	Brian Warner <warner@…>	"I found a regression in the SDMF publish code when I happened to try to update an old directory that I'd created with k=3/N=20. My current tahoe.cfg uses k=3/N=10. The exception is a !NotEnoughServersError that wraps an !AssertionError in {{{mutable.layout.SDMFSlotWriteProxy.finish_publishing}}}, where it notices that it doesn't have all the share pieces it needs (it's missing sharedata, blockhashes, and sharehashes, but it has verification_key, encprivkey, and signature).

The publish process has several dictionaries that are keyed by share number. It looks like some of them are being filled with shnums that depend upon what the current tahoe.cfg has for {{{shares.total}}}, whereas others are filled according to which existing shares were actually found. If tahoe.cfg has changed in the meantime, {{{finish_publishing()}}} will be called on shnums that were never handled in the earlier methods.

I've attached a unit test which exercises this case in a pretty narrow way.

This is a blocker for 1.9
"	defect	closed	critical	1.9.0	code-mutable	1.9.0a1	fixed