erlang | Development repository for the erlang cookbook | Infrastructure Automation library

Well, the title says it all: I'm wondering what is the reason why the BEAM doesn't garbage collect atoms. I'm aware of question How Erlang atoms can be garbage collected but, while related, it doesn't reply to why.

What is the Erlang/OTP release schedule? How many major versions are released per year, and is there a schedule you can link?

What versions have long-term support (LTS)?

erlang version = 1:24.0.2-1

rabbitmq-server version = 3.8.16-1

Recently installed latest rabbitmq on Ubuntu20. I verified that all was working fine and consumer was consuming the notification from messaging queue as required.

After approximately a day, rabbbitmq crashed as there was 0 disk space left.

After analysis found that around 10G was consumed by msg_store_transient, to which restarting rabbitmq solved the issue. But after a day, it happens again.

Can someone help me further?

I'm looking for a message queue implementation for python 3.6 (this exact version) that can be used to communicate between multiprocess.Processes, specifically, It should be a multiproducer, single consumer, fifo with priority receive of messages of application specific types (e.g. if there is an system message (in erlang terms) in the middle of the queue, and an normal message in the head of the queue, the next receive should return the system message rather than the normal one)

But I doubt there will be such an library, so the question becomes, is there any stdlib or third party lib that gives me a chunk of shared memory or better a list, so I can read write to a buffer backed but the memory/list and guard the order with something like mp.Lock?

multiprocessing.Manager uses tcp, and starts a new process

Setup: 3 node cluster of rabbitmq nodes(via docker), behind ha-proxy.

Version:

• RabbitMQ: 3.8.11
• Erlang: 23.2.3
• Spring-amqp: 1.7.3

Spring-boot(1.5.4) app with 3 queues.

1. defined as "exclusive", durable, auto-delete is false
2. defined as "SAC", durable, auto-delete is false
3. classic, durable, auto-delete is false

Policy:

Scenario:

1. When application starts at first, queues are registered correctly.
2. I bring down any node at random, if it is master node, the mirroring is triggered and one of the mirrored node becomes master.All fine so far.
3. When I bring that node up, it is when I start to get exceptions in the application logs:

Logs:

I have encountered some problems with dockerizing my rebar3 app. As I'm trying to run the app (after building) I receive an error /prod/bin/prod: line 272: /prod/erts-11.2.2.1/bin/erl: not found

This is my rebar.config:

Recently updated the macOS to Bigsur and as part of the update, I also updated the packages through homebrew. My coc.nvim plugin was not working so, I reinstalled the package. And after that, I am unable to see the color of my scheme (gruvbox) which is also installed as a plugin. Now the screen is all grey with the dark background (the background was dark even previously). I am attaching the vim settings for clarification. The syntax setting is enabled and it is rightly picking erlang, the termguicolors is set as well. I am using mac terminal to invoke vim.

Trying to run the example app, sellaprime app, from the programming erlang book. I tested the supervisor code with the testing function within the supervisor. So, the supervisor should be OK. The application gets loaded but the application start runs into problem with below error:

I am new to Elixir and I would like to learn how to debug Streams better.

It's common where I work to have operations performed on large datasets. This means that Streams are used heavily until the final operation, usually an Enum.sum().

But this unfortunately means several calls look indecipherable as they are composed of several undocumented Stream.map functions. (a problem we are currently fixing). I would like to see the state of the data as it passes from stream to stream for debugging. How is this normally accomplished?

Example: