Awasu
Tuesday 18th July 2017 7:45 PM [Awasu News]

The first translation of Awasu 3.1 has been baking for a while, and is now ready to step out. Cláudio Mantovani Vieira was kind enough to do the translation, and it looks great :clap: There's just something about seeing Awasu running in a different language that is way cool; you shoulda seen the Arabic one, that was seriously freaky 🙂

If you'd like to translate Awasu into your favorite language, drop us a line, and if you happen to speak German or Russian, since we have translations for Awasu 3.0, the job's already half-done!

Thursday 13th July 2017 7:47 PM [Tutorial]

An Awasu user recently asked for some help in getting their Python code to work with Awasu, and while the problem turned out to be related to text encoding (which is not, strictly speaking, anything to do with Awasu), since this is such a common issue, I thought I'd write up some notes on how all it works.

The canonical introductory article on the subject is, of course, Joel Spolsky's The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)", but these notes will be a more practical guide, along the lines of "How do I get my code to *?@#'ing work?!?!"[1]Now, there's a meme for you 🙂 .

Note that while this tutorial has separate sections on Python 2 and Python 3, even if you're only using one version of Python, you should read both sections if you want to really understand how things work.

This stuff is tricky to get your head around at first, but once you figure it out, it's actually not too bad. The problem is that even when you've got your code right, you start receiving content from elsewhere that is wrong, which breaks your code, so you change it to handle that content, but then your code breaks when you receive content from somewhere else that is doing things correctly[2]Or also doing things incorrectly, but in a different way :wall: , and you get stuck in a cycle where your code never works properly :wall: Hopefully, these notes will help you know when your code is right, and you can stick to your guns and start yelling at the other guy to fix their code... 🙂

   [ + ]

1. Now, there's a meme for you 🙂
2. Or also doing things incorrectly, but in a different way :wall:
Wednesday 26th April 2017 9:53 PM [Awasu News]


We have Pi Day, we have Square Root Day, there's even a Weed Day; well, today is Awasu Day.

Awasu listens on port 2604 for HTTP API requests, and while I realize y'all in the USA write your dates backwards, here in Australia, today is 26/04, and so it's insanely appropriate to announce the release of Awasu 3.1 here.

It's better, faster, sexier than ever before - check out the features here and here - and even better, no price increase! :clap:

So, grab it while it's hot, and I'm off to the pub... :jig:

Wednesday 22nd March 2017 2:39 PM [Awasu News]

Awasu 3.1.rc1 has been released here.

Most of the work for this release was for the installer, which will upgrade your existing installation to 3.1, if you're running 3.0, or any of the 3.0.x betas. If you're running a 2.x version, or (eek!) a 1.x version, please contact us for details on how to upgrade.

The documentation has also been updated, and is available here (a CHM version will be coming later).

Note to self: if anyone asks you to do installer work, run away! It's a horrible job, testing on different versions of Windows, with many different scenarios that need to be verified. But it's all done now, so I'll let this release bake before pushing out the final 3.1 general release in a few weeks. Woo hoo!

Thursday 16th February 2017 9:21 PM [Awasu News]

Awasu 3.0.4 has been released here.

A final round of optimizations, enhancements and bug fixes - this'll be the last one before the 3.1 general release, which shouldn't be too far away.

Tuesday 31st January 2017 9:27 PM [Awasu News]

Awasu 3.0.4.alpha3 has been released here, mostly minor bug fixes and enhancements. Only a few things left to do, and that'll close off this release cycle - woo hoo! :clap:

Wednesday 25th January 2017 6:05 PM [General]

Awasu has had many optimizations made to it over the past few releases, and one of them was a change to how it captures output from plugins. The old code used to set up temp files to capture stdout and stderr, configured the plugin process to send its output to them, then read the captured content when the plugin finished. This was changed in 3.0.4.alpha2 to use in-memory buffers, thus removing the need to use slow disk files.

This worked pretty well, except for one rare, bizarre problem: if Awasu crashed was forcibly terminated via Task Manager while plugins were running, when it was restarted, it was unable to open the server socket it normally listens on for API requests, because another process had it open. The plugins would also hang indefinitely. Awasu was recently changed to automatically find an alternative port, which is kinda cool, but (1) it also kinda sucks if you have scripts that have this port hard-coded, and (2) it's indicative of a serious problem, a zombie kinda problem 🙁

When Awasu is started, it checks to see if another copy is already running, and transfers control to that if it is, so the old process was dead enough that the new copy of Awasu wasn't seeing it, but it was alive enough that it was keeping the old socket (and presumably other stuff) open.

I hate zombies.

I finally figured out what the problem was, and thought it might make a good blog post, since it was an interesting situation, and as a PSA to correct an omission in the MSDN example. However, when I went looking for the MSDN example, it did the necessary magic to avoid this problem :wall: but since it doesn't explain why it performs these incantations, it's maybe worth jotting down these notes for anyone else running into the same problem...

The problem

The old code[1]Error handling has been removed for clarity. created the pipe [2]Awasu captures both stdout and stderr, but stderr is not important for this example, and so is omitted. and launched the plugin process something like this:

// create a pipe to capture stdout
SECURITY_ATTRIBUTES secAttrs ; 
memset( &secAttrs , 0 , sizeof(secAttrs) ) ; 
secAttrs.nLength = sizeof(secAttrs) ; 
secAttrs.bInheritHandle = TRUE ; // the handles returned will be inheritable
HANDLE hStdoutRead , hStdoutWrite ; 
BOOL rc = CreatePipe( &hStdoutRead , &hStdoutWrite , &secAttrs , 0 ) ;

// start the child process
STARTUPINFO startupInfo ; 
memset( &startupInfo , 0 , sizeof(startupInfo) ) ; 
startupInfo.cb = sizeof(startupInfo) ; 
startupInfo.dwFlags = STARTF_USESHOWWINDOW | STARTF_USESTDHANDLES ;
startupInfo.wShowWindow = SW_HIDE ;
startupInfo.hStdOutput = hStdoutWrite ;
PROCESS_INFORMATION processInfo ;
BOOL rc = CreateProcess(
    NULL , pCmdLine ,
    NULL , NULL ,
    TRUE , // the child process will get our inheritable handles
    CREATE_NO_WINDOW ,
    NULL , pWorkingDir ,
    &startupInfo , &processInfo
) ;

The idea is that we create a pipe to capture the output from the plugin process, with 2 handles to access it[3]There are some things you need to be careful about when using this technique, but they are (sorta) well-known. One (hStdoutWrite) is given to the plugin process so that it can write to the pipe[4]It's actually connected to the process' stdout, and it doesn't even know anything funky is going on., while the other (hStdoutRead) is used by Awasu to read from it.

Inheriting handles

But what does it mean to inherit handles, anyway?

When you open something like a file, or socket, or registry key, the Windows kernel creates an in-memory object to manage it, then gives you a handle to it, which is an alias for the underlying kernel object. The thing about these aliases is:

  • they're only valid within one process (typically the one that opened the underlying object)
  • there can be more than one of them, even across multiple processes, referring to the same underlying object

When the code above runs, Windows creates the pipe buffer and 2 objects to manage reading/writing it, and gives us handles (i.e. aliases) to those underlying kernel objects:

  • handle #1 (an alias for kernel object #12[5]These numbers are internal to the kernel, and have no meaning to user programs.
  • handle #2 (an alias for kernel object #47)


When the child process is created, it inherits these handles[6]Because CreateProcess() was told to do this, and these handles were created as inheritable. i.e. it gets its own copy of them, that refer to the same underlying kernel objects:

The child process needs to inherit these, since it needs the pipe write handle. When it outputs something, it goes to hStdoutWrite[7]Because we passed it in to CreateProcess() as the process's stdout., and ends up in the pipe buffer. From there, Awasu can read it via its hStdoutRead handle.


The solution

You would think that if the reading end of a pipe disappears, anyone trying to write to it would get a "broken pipe" error, but as described above, the plugins would hang indefinitely and the parent awasu.exe got stuck in zombie limbo 🙁

If we update our diagram to reflect Awasu disappearing, we can see what's happening:

The child process also inherited a copy of the pipe's read handle (even though it doesn't actually use it), and since the process is still running, Windows thinks the underlying kernel object is still in use and so can't close it. So, since something is still connected to the reading end of the pipe, it's still alive, the plugin merrily writes its output to the pipe buffer, until it fills up, and then waits for someone to read the output, to free up some space so that it can write out more output. Except, of course, the only thing with a read handle to the pipe is the child process itself[8]Which it never reads from, since it doesn't need to, that's Awasu's job., so it waits forever, and all this is also apparently enough to stop Windows from fully cleaning up the dead-but-not-quite Awasu process. Sigh...


Once we understand what's going on, the fix is easy: don't inherit the hStdoutRead handle. We set things up like this:


Now, if Awasu disappears, there are no more handles to the pipe's read handle, so Windows will close it, realize the pipe is broken, then returns an error to the plugin the next time it tries to write to it, and in the grand Shakespearian tradition, everyone dies as they should.



   [ + ]

1. Error handling has been removed for clarity.
2. Awasu captures both stdout and stderr, but stderr is not important for this example, and so is omitted.
3. There are some things you need to be careful about when using this technique, but they are (sorta) well-known
4. It's actually connected to the process' stdout, and it doesn't even know anything funky is going on.
5. These numbers are internal to the kernel, and have no meaning to user programs.
6. Because CreateProcess() was told to do this, and these handles were created as inheritable.
7. Because we passed it in to CreateProcess() as the process's stdout.
8. Which it never reads from, since it doesn't need to, that's Awasu's job.
Tuesday 3rd January 2017 9:07 PM [General]

I'm not a big one for browser plugins and add-ons, but one thing I absolutely love is this simple, but very cool, bookmarklet. In the author's own words:

I hate sticky headers. I want to kill sticky headers.

So I made this bookmarklet.

It removes those unbelievably annoying full-page overlays, header bars, chat boxes, anything that stays in a fixed position, from a web page[1]Technobabble: it looks for anything with a CSS position of "fixed" and removes it from the DOM.. I so want this in Awasu, so I was mulling over how best to implement it, when it occurred to me that you could already do it :wall:

Simply create a new user tool[2]Choose "Organize user tools..." from the Tools menu. called, say, "Kill stickies", with the following Javascript:
javascript:(function(){(function(){var i,elements=document.querySelectorAll('body *');for(i=0;i<elements.length;i++){if(getComputedStyle(elements[i]).position==='fixed'){elements[i].parentNode.removeChild(elements[i]);}}})()})()

Then, when you browse to a page that has these pesky things on it, just run the user tool and they'll be removed from the page! 😎

Wishing y'all a great and sticky-free 2017 ::-):

   [ + ]

1. Technobabble: it looks for anything with a CSS position of "fixed" and removes it from the DOM.
2. Choose "Organize user tools..." from the Tools menu.
Tuesday 29th November 2016 1:43 PM [Awasu News]

Awasu 3.0.4.alpha2 has been released here.

Lots of bug-fixes and optimizations, and while the change list might look a little short, some of the issues fixed were insanely difficult to track down. When something happens only after Awasu has been running under continuous heavy load for a week, it takes time to figure out what the problem is 🙁 But I've had several instances of Awasu running under load for 2 straight months now, so I think it's solid... 🙂

There also a bunch of fixes and improvements for corporate users, when Awasu is used in a domain, and connects to the internet via a proxy.

Monday 20th June 2016 8:30 PM [Awasu News]

Awasu 3.0.4.alpha1 has been released here. This will probably be the last release cycle before 3.1, so it'll be lots of minor enhancements and bug fixes from here on.

The most useful one in this release is the blocking of web-bugs. These are invisible images that publishers embed in their feeds, so that they can track when you read an item. When I was testing this feature, I was horrified at how many of these things were in there, so I'm very happy Awasu now strips them out.