Tyler Waters

FWIW, I added an option to `seneca-web-adapter-express` to ... stop doing that. The real problem was with using `print('test')` with `request$` and `response$` - turns out it takes a while...

I've got a PR that fixes this: https://github.com/blueshirts/seneca-pino-adapter/pull/3 Hopefully @blueshirts can merge that & publish a fixed version.

@philippem would it make sense to declare the queues/exchanges with `autoDelete: true`? If the listener goes away by way of changing the pins, its consumers should also go away -...

I've also added a commit to the linked PR to improve performance a bit. For each operation it finds, it's writing out an incomplete file. Fortunately, the last one always...

@philsturgeon @fmvilas friendly bump.... Just had one of our developers hit this issue. Looking into how to fix the max file descriptors thing on their OS, but it would be...

`db:seed:all` doesn't appear to work when run multiple times. For migrations, a row is inserted into `SequelizeMeta` by the name of the file that was run, and subsequent runs will...

Err....scratch that, by default, seed uses `none` for it's storage mechanism, so `db:seed:all` will attempt to run all them every time. You can configure migrations/seeds to use different storage mechanisms....

Dug through the code a little bit, this message is returned by "gubu" which seems to do message validation now. I found it can be disabled by applying the following...

I can also confirm at least one performance issue. Looks like this was introduced between 3.16.0 => 3.17.0 Our tests use a `beforeEach` hook to initialize seneca, add a bunch...

I used `npm@^7` to update dependencies and it _seems_ to have updated both `yarn.lock` and `package-lock.json` files... probably fine :)