Erlang
Erlang is a general-purpose, concurrent, functional programming language, and a garbage-collected runtime system. The term Erlang is used interchangeably with Erlang/OTP, or Open Telecom Platform (OTP), which consists of the Erlang runtime system, several ready-to-use components (OTP) mainly written in Erlang, and a set of design principles for Erlang programs.
Here are 2,729 public repositories matching this topic...
-
Updated
Mar 1, 2022 - Erlang
-
Updated
Feb 28, 2022 - Python
-
Updated
Jan 26, 2022 - Erlang
-
Updated
Dec 20, 2021
-
Updated
Mar 1, 2022 - Erlang
-
Updated
Mar 26, 2021 - Rust
Environment
- VerneMQ Version: 1.11.0
- OS:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic - Erlang/OTP version (if building from source): 19
- VerneMQ configuration (vernemq.conf) or the changes from the default
- Cluster size/standalone:
Expected behaviour
Connection to Redis server running on unixsocket, configured within Lua scr
Currently, if you create an environment from a process that has the permission to call lunatic::process::allow_namespace it can give greater permissions to sub-processes spawned into the new environment than it has itself.
The lunatic::process::allow_namespace host function should first check if we have permissions for the namespace before allowing us to add it to other environments. Simila
-
Updated
Feb 10, 2022 - Erlang
-
Updated
Feb 28, 2022 - Elixir
-
Updated
Sep 23, 2021 - Erlang
-
Updated
Mar 1, 2022 - Erlang
-
Updated
Jun 2, 2020 - Erlang
-
Updated
Nov 23, 2021 - Elixir
-
Updated
Feb 3, 2022 - Shell
-
Updated
Feb 28, 2022 - Erlang
-
Updated
Mar 1, 2020
-
Updated
Jun 13, 2020 - Erlang
-
Updated
Feb 25, 2022 - Go
-
Updated
Feb 4, 2022 - C
-
Updated
Feb 10, 2022 - CSS
-
Updated
Oct 30, 2021 - Erlang
Created by Joe Armstrong, Robert Virding, Mike Williams
Released December 8, 1998
- Organization
- erlang
- Website
- www.erlang.org
- Wikipedia
- Wikipedia
Steps to reproduce
Run
asdf. In help output a line is printed for theasdf envcommand:I would assume
<command>is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.FY