Michał Piotrowski
Michał Piotrowski
I can see there is a branch [adt/lager_use_logger-option](https://github.com/erlang-lager/lager/tree/adt/lager_use_logger-option), which as far as I understand helps to integrate Erlang's built in logger with lagger. Are there any chances to get this...
This PR doesn't set erlang cookie for the prod node build with `rebar3`'s prod profile. Only dev nodes have erlang cookie set in their `vm.args` file and the test node....
Hi, Is there a chance for a new tag and hex package? I can see the latest release is almost 2 years old and many commits happened after that.
I've created this [1] `proper_statem` which tests sending messages between XMPP users connected over BOSH or WS. In some cases the generated commands look like this: ``` erlang [{set,{var,1},{call,bosh_interleave_reqs,connect_carol,[]}}, {set,{var,2},{call,bosh_interleave_reqs,connect_geralt,[]}},...
Details in issue comments.
I think each group or at least groups: **moderator**, **admin** (including admin_membersonly), **occupant** and **owner** should be moved to their own suites. Current muc_SUITE.erl file is far to big... ~4k...
Proposed changes include: * implementation of bind 2.0 as described in this [proto XEP](http://xmpp.org/extensions/inbox/bind2.0.html) * removal of `escalus_session:bind/2` - it is not needed * `escalus_session:bind/3` returns client data with jid...
According to RFC [6120 secion 4.2](https://tools.ietf.org/html/rfc6120#section-4.2) it's allowed to add from attr to initial stream header. This may be used by load balancer to distribute users based on jids.
Inspired by http://tech.nextroll.com/blog/dev/2020/02/25/erlang-rebar3-format.html I wanted to try the `rebar3 format` plugin with exml.