[Bug 18483] Image cascading protection issues

2011-07-15 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18483

Dan Collins  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||en.wp.s...@gmail.com
 Resolution||WONTFIX

--- Comment #26 from Dan Collins  2011-07-16 02:25:05 UTC 
---
Cascading protection takes time to take effect. Updating the bug summary to
that effect, and since we know that, and per Andrew, a very simple workaround
exists, this is going to be WONTFIX.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 18483] Image cascading protection issues

2009-07-05 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18483





--- Comment #25 from Andrew Garrett   2009-07-05 
19:19:34 UTC ---
(In reply to comment #23)
> It seems that the issue is that the linktable updates that trigger cascading
> protection run through the job queue and are thus potentially delayed if the
> job queue is long.  The solution, therefore, is to ensure that the
> templatelinks and imagelinks tables are updated quickly after a
> cascade-protected page is updated.
> 
> IIRC someone (Tim?) is working on an improved job queue construction; as
> suggested in comment#12, a 'priority stream' should be considered in that
> system.  In the meantime (and perhaps even regardless), it would seem to be
> sensible to update these tables *immediately* as part of the page save, if the
> page is cascade-protected.  Since only admins can save cascade-protected 
> pages,
> this whould not be a DoS vector.

Requires serious rearchitecture, which is not justified by a minor problem for
which a basic workaround exists.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 18483] Image cascading protection issues

2009-07-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18483





--- Comment #24 from shubinat...@gmail.com  2009-07-04 15:02:23 UTC ---
Is there any progress on the bug? Happymelon's suggestion seems perfect. 
As I understand it, saving the page updates the link tables for only that page.
For cascading protection, this means admins have to null edit (purge doesn't
work) the Main Page. We could extend this so if (cascade protected) -> update
link tables of that page -> propagate link table updates upwards in the chain
of cascading protection. So in our example, updating Template:Did you know
would update the link tables of the Main Page, which would trigger cascading
protection instantaneously.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 18483] Image cascading protection issues

2009-05-01 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18483


Happy-melon  changed:

   What|Removed |Added

 CC||happy-me...@live.com




--- Comment #23 from Happy-melon   2009-05-01 15:59:17 
UTC ---
It seems that the issue is that the linktable updates that trigger cascading
protection run through the job queue and are thus potentially delayed if the
job queue is long.  The solution, therefore, is to ensure that the
templatelinks and imagelinks tables are updated quickly after a
cascade-protected page is updated.

IIRC someone (Tim?) is working on an improved job queue construction; as
suggested in comment#12, a 'priority stream' should be considered in that
system.  In the meantime (and perhaps even regardless), it would seem to be
sensible to update these tables *immediately* as part of the page save, if the
page is cascade-protected.  Since only admins can save cascade-protected pages,
this whould not be a DoS vector.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 18483] Image cascading protection issues

2009-04-22 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18483


gdon...@blueyonder.co.uk changed:

   What|Removed |Added

 CC||gdon...@blueyonder.co.uk
   Severity|enhancement |minor
Summary|Images on shared|Image cascading protection
   |repositories can't be   |issues
   |protected by cascading  |
   |protection  |




--- Comment #22 from gdon...@blueyonder.co.uk  2009-04-22 15:42:52 UTC ---
reverted summary since bug changed focus again to original issue


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l