MW 1.15, SMW trunk 1.5.0.a-SVN svn info says r63655, SIO trunk (that's 
the only thing in SVN anyways).
Everything cept SIO can be seen at 
http://wiki.commonjs.org/wiki/Special:Version (Note that FlaggedRevs was 
installed AFTER the SIO issue)
#set_internal is commented out but can be seen at 
http://wiki.commonjs.org/index.php?title=Template:Spec/implementation&action=edit
 
<http://wiki.commonjs.org/index.php?title=Template:Spec/implementation&action=edit>
Only page affected was http://wiki.commonjs.org/wiki/Modules/1.0
The same SIO call was probably included in one or two other pages, but 
the job queue didn't obsess over them. Though don't know if their data 
made it into the cache.
SMWAdmin's update data was also used, don't know if that was before or 
after SIO going berserk.
Berserk job didn't go away even after uninstall until the refresh job 
was manually removed from the db. However the berserk job only came into 
existence when SIO was installed.


~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

Yaron Koren wrote:
> This may be the least helpful bug report I've ever received... what 
> versions of MW, SMW and SIO are you using? And did this happen for 
> every internal object you tried? And what does the relevant 
> #set_internal call look like?
>
> -Yaron
>
> On Fri, Mar 12, 2010 at 11:14 PM, Daniel Friesen 
> <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     I found a bit of a bug in Semantic Internal Objects.
>
>     Using SIO caused my Job queue to go berserk. Jobs would run constantly
>     centered on a single page that was using SIO. When I took a closer
>     look
>     at the database the page names actually had #'s in them, in other
>     words
>     they were for internal objects. however these numbers were up above
>     3000, SIO was basically generating insane jobs to refresh data that
>     shouldn't exist and going berserk on the job queue running forever.
>
>     --
>     ~Daniel Friesen (Dantman, Nadir-Seen-Fire)
>     [http://daniel.friesen.name]
>
>
>     
> ------------------------------------------------------------------------------
>     Download Intel&#174; Parallel Studio Eval
>     Try the new software tools for yourself. Speed compiling, find bugs
>     proactively, and fine-tune applications for parallel performance.
>     See why Intel Parallel Studio got high marks during beta.
>     http://p.sf.net/sfu/intel-sw-dev
>     _______________________________________________
>     Semediawiki-devel mailing list
>     [email protected]
>     <mailto:[email protected]>
>     https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>
>
>
>
> -- 
> WikiWorks · MediaWiki Consulting · http://wikiworks.com
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> Semediawiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>   


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Semediawiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to