-
Timers includes:
- [ ] bif erlang:start_timer/3
- [ ] bif erlang:start_timer/4
- [x] bif erlang:send_after/3
- [ ] bif erlang:send_after/4
- [ ] bif erlang:cancel_timer/1
- [ ] bif erlang:canc…
-
Steps to reproduce:
1) Get processes info -> Pids
Pids = [erlang:process_info(Pid, [registered_name,reductions,monitors,monitored_by,links]) ++ [{pid, Pid}] || Pid Data
Data = lists:sort(fun(A, …
menih updated
5 months ago
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### What happened?
I've upgraded to v1.31.0 and after the upgrade I noticed* that there's a beam.smp process chewi…
-
### Environment
- VerneMQ Version: 2.0.0-rc1-5-gf0e6dc15
- OS: Ubuntu 20.04
- Erlang/OTP version (if building from source):
- Cluster size/standalone:
### Current Behavior
VerneMQ receives suc…
-
It'd be great if pulsar actors could exchange messages directly with erlang processes.
Consider this a vague feature request :)
-
after months of running, erlang:memory() shows that binary used >44MB, etop shows that some processes used upto 55kB.
foldl updated
3 years ago
-
It seems that there's a pretty hefty bug with Eleveldb when you're using non-default Erlang schedulers ( https://erlang.org/doc/man/erl.html#+sbt ). When you use one of those scheduler flags to start …
-
Http interface would be a nice addition to alooger, so it could communicate with non-erlang processes (.NET ones for example).
-
Is there any preferred method of communication between processes? In particular using the underlying Erlang Node connections vs implementing something using `gen_tcp` or equivalent.
-
### Is your feature request related to a problem? Please describe.
amqp_client hasn't been updated since 3.12.14.
https://hex.pm/packages/amqp_client
### Describe the solution you'd like
Could y…