I've noticed a big upsurge in the prevalence of this bug since 3.2.3 or so. It's now happening once or twice a night. Basically I dock and get no responce from the server when trying to repair or buy ammo or sell cargo. I get m_waiting = 8 messages in console. If I undock and redock the problem is fixed.

The problem with undocking and redocking is there's a high probability you'll lose your cargo. I get the m_waiting things a LOT, especially when I play for longer amounts of time.

Wanna know what freaks me out? Dying and rebuying a ship, undocking and flying back into battle, THEN noticing that the rebuy only bought you 6 missiles, the number you had when you died.

Hmmmmmmmmmmmmmm
mmmmmmmmmmmmmmm
mmmmmmmmmmmmmm.

Yah, sometimes when i dock and repair and re arm, my console is full with m_waiting = 8, or was it 4?

I've seen 8, 6 and 3. No 4 yet. I'll keep trying. ;-P

Thanks, I'm still looking into it.

Basically that m_waiting means that your client is waiting for a response from the server for some action that was performed.
That action is defined by the number.
For example, 8 is cargo being loaded/unloaded/unloaded&sold.
It's supposed to grey out buttons to prevent you from doing anything else but there are some places where that doesn't happen. Theoretically it should be cleared up when the status says something like Blah completed or something to that effect.
Giving it some time should be enough but apparently it isn't which makes me think there is a condition happening that I am not taking into account that isn't sending back a response (whether success or an error code). I'm pretty sure I got all of them but lag may be causing something to not work right.
I'm hoping I can get it cleared up soon though.

I think what happens is that when the grey buttons don't show up, the client continues with another operation at a fast speed. For instance, I dock, unload & sell cargo, click Repair, select and hit "r" a dozen times, then go to ammo, select it, and click "b" a dozen times. In that sequence do I see the most m_waiting = X's.

Hmm, yeah, I think the client may be re-enabling the action button when you switch tabs, even when it's not supposed to.