On git-master, if you have an addon
foo.py with an added option
a = tctx.script(tdata.path("foo.py"))
ctx.options.foo gets updated, but the
configure of addon
a does not get called, and the addon therefor never re-configures itself to use the new option value.
@cortesi introduced this breaking change https://github.com/mitmproxy/mitmproxy/commit/236a2fb6fde4ff8837f85cf0a217f915b0bfed79#diff-e447662b406664bed7663e2bd8531104L115 in 236a2fb6f - looking at the diff, the previous behaviour make more sense to me: updating the options, and then calling
configure on the addon.
This currently blocks #2861 due to failing tests. I'm wondering if other tests are affected as well, but never got noticed due to default values that just happen to work out of the box...