Philip Dubé

https://github.com/rustwasm/wasm-pack/pull/712 It's actually a bug that wasm-pack isn't putting pkg where outDir expects it to go

Tests now failing in relation to #3535

These tests often seem to break in different ways with changes in master I'm not sure if that's a good or bad. ie whether that means these tests cover edge...

We do rely on the rewriting to some degree, `LIMIT 10` is originally a `LIMIT 10::int8` where `standard_planner` reduces the `FuncExpr` cast into a plain `Const` Also not sure how...

https://github.com/citusdata/citus/blob/4e3d40247353848bd724801b3499d3eed3206a9d/src/backend/distributed/planner/recursive_planning.c#L919-L927 Removing this fixes the task-tracker issue. So added explicitly recursively planning `LIMIT`/`OFFSET` where we recursively plan `HAVING`. I also had to add `scanState->PreExecScan = &CitusPreExecScan` to `TaskTrackerCreateScan` for it...

Both solutions could work. Update search order, & add optional `class_name` parameter

I was needing this, ended up writing all my code to use `Bytes` directly instead. Some responses were cached, meanwhile others computed

@ldez wal-g is a code example https://github.com/wal-g/wal-g/pull/1186 `structcheck` was complaining about `LazyCache`'s fields *(PS thanks for the help)*

not stale

@farooqch11 Your stacktrace is a bit odd. For one, save_last_enqueue_time should be at line 480, but your stacktrace is saying 473. Secondly, PR has `conn.hset redis_key, 'last_enqueue_time', @last_enqueue_time.strftime(LAST_ENQUEUE_TIME_FORMAT)` which should...