HIPE | Hierarchic Image Processing Engine | GPU library

The issue was in my original configuration file config/config.exs.

I had

I see no R14B05 anywhere, only R14B01-R14B04.

http://erlang.org/download/ and http://erlang.org/documentation/ seems to have old files.

doc-5.8.5 is for Erlang/OTP R14B04, and the next one, which is doc-5.9, is for Erlang/OTP R15B. There does not appear to be a R14B05 one, so perhaps it indeed could be a typo. Perhaps they thought 5.8.5 was R14B05?

You could try contacting the authors as well, just in case.

This is a race condition when you have shell history enabled. There's an open report here.

Because the disk_log is started after the user process, there is a chance for race conditions on shutdown, where disk_log will terminate before group, which will fail to log.

Furthermore, if disk_log terminates BEFORE the shell starts, then the whole shell will fail to start, which will trigger another shell recursively, until the system finally shuts down. This can be reproduced with this command:

$ erl -kernel shell_history true -s init restart

Erlang doesn't have classes, so the class in question probably has something to do with "the viewer" software. According to this, it's an Apple issue.

This is an issue of using Erlang/OTP 23 and Elixir 1.9.4 simultaneously.

Elixir 1.9 is older than OTP 23, but elixir fully leverages OTP, so it relies on some warnings/messages coming from erlang compiler during compilation.

That said, downgrading OTP to the version Elixir 1.9 is aware of (21 would be fine, I believe,) or upgrading Elixir to the recent 1.11.1 would fix the issue producing fancy

I had Erlang 23 and RabbitMQ Server 3.8.2 (they are not fully compatible so I decided to upgrade RabbitMQ Server to 3.8.9 because I had some problems running my app)

I have a cluster with one node on AWS EC2 instance of Ubuntu 20.04 (unconfigured yet properly as RabbitMQ advises via plugin - I plan to do it later).

What I did and it worked for me (following commands executed under sudo or root sudo su):

1. It's important to shutdown not just stop_app as Erlang also needs to be stopped and stop_app only stops RabbitMQ Server leaving Erlang on which would later might give you error while starting new version of the RabbitMQ Server - for port 25672 being busy with another app:

   rabbitmqctl shutdown

2. Change in rabbitmq file from old version (I had for some strange reason 3.8.8 instead of 3.8.2 which I run) to a new one - in my case 3.8.9:

   vim /etc/apt/preferences.d/rabbitmq

3. Recheck if dependencies are installed:

   apt-get -y install socat logrotate init-system-helpers adduser

4. Install wget if you don't have it:

   apt-get -y install wget

5. Download latest .deb package of server installation file:

   wget https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.8.9/rabbitmq-server_3.8.9-1_all.deb

6. Install it:

   dpkg -i rabbitmq-server_3.8.9-1_all.deb

7. Remove distro:

   rm rabbitmq-server_3.8.9-1_all.deb

8. Check if server stopped (may be redundant command):

   service rabbitmq-server stop

9. Restart server:

   service rabbitmq-server restart

10. Check server status:

    rabbitmq-server status

11. If it gives you an error BOOT FAILED. Distribution port 25672 is in use by another node, check who uses that port it may be that Erlang uses that port:

    lsof -i :25672

12. Start RabbitMQ app:

    rabbitmqctl start_app

13. Check status of node:

    rabbitmqctl status

You should see upgraded RabbitMQ Server version (in my case 3.8.9) along with you recent Erlang version (in my case 23)

Example of use crypto:crypto_one_time/5:

Go to the page: https://www.erlang-solutions.com/resources/download.html and download the latest version for raspbian buster.

Then in Raspbian type

From the docs:

-s Mod [Func [Arg1, Arg2, ...]](init flag)
Makes init call the specified function. Func defaults to start. If no arguments are provided, the function is assumed to be of arity 0. Otherwise it is assumed to be of arity 1, taking the list [Arg1,Arg2,...] as argument. All arguments are passed as atoms. See init(3).

1. Because of this line:

   If no arguments are provided, the function is assumed to be of arity 0. Otherwise it is assumed to be of arity 1, taking the list [Arg1,Arg2,...] as argument.

   your function is going to receive a list as the sole argument.

2. Because of this line:

   All arguments are passed as atoms.

   all the arguments in the list are going to be atoms.

Therefore, you need to pick out the head of the list to get the sole argument, and then you have to convert the atom to an integer in order to use the == comparison with another integer. Like this: