Ivan Zhuravlev

@icebob This one affects `emit` and `broadcast` with an enabled balancer, which becomes a problem.

check this ``` RUN npm run build \ && npm prune \ && mkdir -p /logs/moleculer \ && touch /logs/moleculer/all.log ```

or ``` RUN npm run build \ && npm prune \ && mkdir -m 0755 -p /logs/moleculer ```

Released in [v0.14.19](https://github.com/moleculerjs/moleculer/releases/tag/v0.14.19) by PR #1048

> Any updates? I'll try to get it done this weekend

It actually turned out to be not as easy a task as I thought when I created this issue. I will need to discuss this with the team. The good...

This: https://github.com/moleculerjs/moleculer-web/blob/5c2a1ff3d51b4b74cc063c3a3f3fa1ad75571248/src/index.js#L579 and this: https://github.com/moleculerjs/moleculer-web/blob/5c2a1ff3d51b4b74cc063c3a3f3fa1ad75571248/src/index.js#L584 is this logic required in some cases? Now the correct values come to ```$params``` and when req is passed, they are lost for validation ```js...

@AndreMaz yes, you can do a nested check. Question need to split logic for stream? We cannot pass there other parameters except in the url. Fields in multipart are defined...

@AndreMaz I will suggest an option later. I need to conduct several tests and figure out what changes can be made in order to maintain compatibility and performance.

I will update my thoughts on this issue. I believe that it would be correct to remove `stream` from `ctx.params` and leave the parameters in `ctx.params` universal. And for `stream`...