dherman

Until this is addressed, here's how I've been working around this: This script generates the set of filter flags needed to run any given task ```bash targetScript="$1" mapfile -t <

@sushantdhiman So even setting the `idle` option to `1` and waiting 10 seconds after making the last query, no resets are occurring on the connection. The underlying problem is that...

@sushantdhiman It should be reset because if you're setting things like `SESSION_CONTEXT` variables, changing state global to the connection like `XACT_ABORT`, etc., then you would be required to know exactly...

Unless I'm mistaken, `afterConnect` is only invoked when acquiring a brand new connection which is actually the only time you *don't* need to reset it. The actual hooks that I...

Don't believe this has been addressed, so still relevant.

@Narretz That timing bug always existed actually. If you invert the condition and have `ctrl.ready` be `true` at compile time, the ngIf always transcluded before the templateRequest finished returning which...

@Narretz I've got some stuff to ship this week so I doubt I'll really be able to do much looking into this (unless I somehow find free time after work)...

@moneytree-doug Less brittle actually. Not only will you appropriately notify the parent when you're actually available, but you'll also get errors in your console if the directive is used outside...