Roger's Brain Dump

make: *** No rule to make target `signbit.o’, needed by `miniruby’.  Stop.

meant “you’re going to need a fresh checkout of trunk, son”

appears from

http://www.tex.ac.uk/ctan/obsolete/macros/latex/contrib/subfigure/subfigure.pdf

that you add

\makeatletter\renewcommand{\p@subfigure}{}\renewcommand{\@thesubfigure}{\thesubfigure:\hskip\subfiglabelskip}\makeatother
\setcounter{lofdepth}{2}

before you run the

\listoffigures

command

Also note that if the captions of the subfigure don’t appear, you may need to do you caption like

\caption[Automatic Swarming under varyied load this one appears in the LoF]{Automatic Swarming under varyied load this one is the caption}

javax.management.NotCompliantMBeanException: MBean class org.familysearch.digitalarchive.presreaper.PreservationControllerImpl does not implement DynamicMBean, neither follows the Standard MBean conventions (javax.management.NotCompliantMBeanException: Class org.familysearch.digitalarchive.presreaper.PreservationControllerImpl is not a JMX compliant Standard MBean) nor the MXBean conventions (javax.management.NotCompliantMBeanException: org.familysearch.digitalarchive.presreaper.PreservationControllerImpl: Class org.familysearch.digitalarchive.presreaper.PreservationControllerImpl is not a JMX compliant MXBean)

meant “your ThisIsMyClassMBean must declare its fields like

public int getSomething() ” (normal getter and setter syntax)

it also meant “your implementation class has to have the same name as the interface — otherwise use a JMX Bean”

http://www.javaworld.com/community/node/1186

*** ERROR in Document controller: <Redcar::AutoPairer::DocumentController>NoMethodError: undefined method `scope_at’ for com.redcareditor.mate.MateText@190ffa7:Java::ComRedcareditorMate::MateTextE:/installs/ruby191p376/lib/ruby/gems/1.9.1/gems/redcar-0.3.2dev/plugins/edit_view_swt/lib/edit_view_swt/document.rb:154:in `scope_at’E:/installs/ruby191p376/lib/ruby/gems/1.9.1/gems/redcar-0.3.2dev

meant “you need to upgrade your java-mateview.jar “

E:\installs\ruby191p376\lib\ruby\gems\1.9.1\gems\redcar-0.3.2dev>git submodule update vendor\java-mateviewfatal: Needed a single revisionUnable to find current revision in submodule path ‘vendor/java-mateview’
E:\installs\ruby191p376\lib\ruby\gems\1.9.1\gems\redcar-0.3.2dev>rm -rf vendor\java-mateview
E:\installs\ruby191p376\lib\ruby\gems\1.9.1\gems\redcar-0.3.2dev>git submodule init vendor\java-mateview

C:\dev\ruby\downloads\ruby_trunk>makeruby ./tool/generic_erb.rb -c -o known_errors.inc ./template/known_errors.inc.tmpl ./defs/known_errors.defmake: ruby: Command not foundmake: *** [known_errors.inc] Error 127

meant “do a fresh checkout this thing doesn’t clean right”

C:\dev\ruby\downloads\ruby_trunk>makeruby -Ks ./tool/insns2vm.rb –srcdir=”.” insns.incc:\dev\ruby\downloads\ruby_trunk\ruby.exe: unknown encoding name – Windows-31J (RuntimeError)make: *** [insns.inc] Error 1

By default mod_rails does “ok” cacheing of static files.

For example for each page the browser will request “has this static file changed?” from apache, apache will say no, and there won’t be a huge slowdown, but there is still some slowdown.

To avoid it, set your static content to never expire (since it doesn’t need to because of the ?timestamp that rails already affixes).

http://zargony.com/2009/01/22/let-browsers-cache-static-files-to-greatly-speed-up-your-site

http://jamescrisp.blogspot.com/2007/04/improve-rails-performance-through.html

see http://betterlogic.com/roger/?p=489

enjoy!

javax.management.AttributeNotFoundException: No such attribute: RequestOverLastMinute

meant "your attribute has to be
RequestOverLastMinute
for the getter
getRequestOverLastMinute

Testsuite: org.familysearch.digitalarchive.dasstoragecellws.schema.HistoryTrackerTestTests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.094 sec
Testcase: initializationError(org.familysearch.digitalarchive.dasstoragecellws.schema.HistoryTrackerTest):        Caused an ERRORNo runnable methodsjava.lang.Exception: No runnable methods        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

Test org.familysearch.digitalarchive.dasstoragecellws.schema.HistoryTrackerTest FAILEDtest:Deleting: b:\TEST-org.familysearch.digitalarchive.dasstoragecellws.schema.HistoryTrackerTest.xmlBUILD SUCCESSFUL (total time: 10 seconds)

meant “you need to add an @Test to the beginning of one of your testable methods in the test class–and there *has* to be at least one or it will throw this!”