Concutest Community Project

I just did an upgrade to WordPress 3.0. Everything seems to be working, but if you notice any problems, please let me know.

I just performed an WordPress auto-upgrade to version 2.9.

If you notice any errors on this blog, please let me know.

And another quick upgrade to WordPress 2.8.4 due to a vulnerability in the previous version.

I think I actually experienced attempts to exploit this problem: During the last two days, I received numerous unrequested password reset notifications for the administrator accounts on my blogs.

I just managed to do a WordPress auto-upgrade for the first time in a while. When it didn’t work this time, I searched the WordPress support forums and found out that the .htaccess file had to be fixed for users of 1&1.

This blog is now running on WordPress 2.8.3. The Markdown plugin stopped working in a very strange way, so I updated to a different Markdown plugin. Then I had to change the “next/previous page” links, but now everything seems to work.

If you notice any errors on this blog, please let me know.

I just upgraded to WordPress 2.7. Everything seems to work as usual now. I did have to update the WP-Email, WP-Print and WP-Sticky plugins, and regenerate the permalinks.

Now, of course, the entire administration side of WordPress looks different, and I have to get used to it, but in general I have to say it looks nice. If you notice any errors on this blog, please let me know.

I just upgraded the blog software to WordPress 2.6.2. If you notice any problems, please let me know.

I just upgraded the blog software to WordPress 2.6. Fortunately, this time the upgrade was much easier than the last time, and I didn’t have to mess with the email and print features separately. Everything seems to be working fine, and I’m keeping my fingers crossed.

TODO: Explain

TODO: Explain

TODO: Explain

TODO: Explain

TODO: Explain

TODO: Explain

TODO: Explain

TODO: Explain

Consider the invokeAndWait method in the javax.swing.SwingUtilities class:

You give it a Runnable, and Java will execute it in the event thread, and then return to you once that is done. This normally works, but what if you call the method from the event thread? In that case, Java will put the Runnable at the end of the event queue, and then wait for it to be executed, but it never will be executed, because the current event is waiting for that Runnable to finish. Calling javax.swing.SwingUtilities.invokeAndWait from within the event thread is a recipe for an instant deadlock!

Therefore, the concurrency invariant for that method is “do not run it in the event thread”.

This invariant can be ensured by prefixing the invokeAndWait method with the Concutest ThreadChecker annotation @NotEventThread:

package javax.swing;
 
import edu.rice.cs.cunit.threadCheck.predicates.NotEventThread;
// ...
public class SwingUtilities {
  // ...
  @NotEventThread
  public static void invokeAndWait(Runnable doRun)
    throws InterruptedException, InvocationTargetException {
    // ...
  }
  // ...
}