Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

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

Well, we need to check all the projects and remove outdated ones.

We declare this in the readme:

However, keep in mind that we don't accept mammoth's shit. Only active and interesting projects with good documentation are added. Dead and abandoned projects will be removed.

But, sadly at this moment, this project looks like a mammoth shit itself.

We really need to fix it. I think

Environment

• OS: RHEL 7.6
• Erlang/OTP:
• EMQ: 2.3.11

Description

I am using:

NIGINX --> Docker --> custom image with EMQ installed ( same host, SSL offload on nginx)

EMQ works and clients can connect but i see continous multiple crashes/proxy errors in the error.log

2019-08-27 12:12:31.287 [error] <0.11973.534> CRASH REPORT Process <0.11973.534> with 0 neighbou

See http://blog.erlang.org/ssl-logging-in-otp-22/ for a full description.

One could enable debug logging in Cowboy to see all the packets transmitted and what Cowboy thinks of them, something like that. Could make some client issues obvious in particular.

Summary

CouchDB keeps a list of purge infos to ensure that purges can be applied on a cluster without purged documents being re-introduced by internal replication.

It would be useful to make this list available for replication clients like PouchDB, who then could apply local purges on their own. I know PouchDB doesn’t implement purge just yet, but it’s something that folks will need befor

Environment

• ejabberd version: 20.03

Hi all,

I'm on the latest ejabberd and have found the JWT auth docs somewhat lacking - https://docs.ejabberd.im/admin/configuration/authentication/#jwt-authentication

I've created this post https://stackoverflow.com/questions/61490726/jwt-secret-to-use-with-ejabberd and once I have the solution I'd like to update the core docs as the [ProccessOn

Please i get this error trying to translate the following to new rustler syntax:

previous:

rustler_export_nifs!(
    "Elixir.Xtdlib.Native",
    [
        ("new", 0, new),
        ("send", 2, send),
        ("execute", 2, execute),
        ("recv", 2, receive, SchedulerFlags::DirtyIo),
    ],
    Some(on_load)
);

error: proc macro panicked
  --> src/lib.rs:91:1
   |

Hello.
Interested in the possibility of implementing the following functions for ACL MYSQL :

Add to Public and Subscribe ACL rules template variables %t (topic)
To implement the change of topics corrected in the section

example: Topic change on the fly

Public ACL

{

"pattern": "a/#",
....,
....,
....,
"modifiers": {

"topic": "%u/%t",
....,
....,
...

Part of our strategy for supporting elixir is by using the mix compiler located in lumen_elixir (abstr_out branch).

The format this emits is abstract erlang (.abstr), different from the regular erlang code used by the normal frontend (.erl).

In libeir_syntax_erl there is a [separate frontend](https://github.com/eirproject/eir/blob

I stumbled across <interaction> and ts_interaction_server, but I'm not sure what the use case is or how it is supposed to be used.

Has anyone used this recently and can add some documentation? Or explain to me how this works and I'll write something.

/cc @nniclausse

case x {
  _ if x == 1 -> "here we are using an Int literal"
}

• Int
• Float
• Tuple
• List
• Records
• String

If you pick up this ticket please no more than one implementation per PR please so that it is easier to review. Thanks!

Currently we have 3 (three!!!!) places for documentation:

1. wiki
2. READMEs
3. API docs (produced from doc-src)
   my proposal is to move everything to wiki. It will be pretty easy for READMEs as they written with markdown too. moving API docs will require much more work, but CB API is not so complicated and everything generated from code can be written once in markdown and changed on demand.

cos a

As described on the latter part of leo-project/leofs#1156 (comment),

You are right. it's best practice to take the backup whenever the cluster topology changes.

This should be documented and also we have to mention that users should take the backup whenever the records in S3 related table (users, endpoints, buckets) change.

Hello,

After taking a look at poolboy's README, I think this project could benefit from a more detailed introduction and mission statement on what the software accomplishes. This would greatly help with drawing in new contributors or people who may be less familiar with how pooling libraries work.

One thing that would also be helpful in this regard would be including a more detailed descri

We need to be able to (eventually) output docs for modules (e.g. javadoc, godoc, etc). I'm fine with something like

The block comment immediately preceding the first definition of a function (or its type specification) is used as the documentation for it. The block comment immediately preceding the module declaration is used as the overall module documentation.

And maybe use markdown for f

asdf is a tool to "manage multiple runtime versions with a single CLI tool". Erlang itself and other BEAM languages (e.g. Elixir) can be installed using it and it would be very nice to add Clojure on the BEAM to the mix.

Documentation to create asdf plugins here.

Repository created [here](https://github.co

It looks like the new parse_document's output is not the same as the deprecated parse. By using the example provided in the documentation:

html = """
  <html>
  <body>
    <div class="example"></div>
  </body>
  </html>
"""
Floki.parse_document(html)
{:ok,
 [
   {"html", [],
    [
      {"head", [], []},
      {"body", [],
       [
         "\n",
         "    ",
     

OTP 23.0-rc1 introduces EEP-48 style doc chunks and new functions for accessing documentation in the shell. See erlang/otp#2545 for more information.

I tried building OTP 23.0-rc1 with kerl (via asdf-erlang) but noticed the chunks are not generated, e.g. lib/stdlib-3.12/doc/chunks/array.chunk is not there. Should KERL_BUILD_DOCS=yes build them or there should be anot

Hello,

I am trying to make a POST request with Content-Type: multipart/form-data but cant find any documentation about how to construct such a request body.

Postman:

Hi,

I am using lager (tag 3.2.1), with the version of ranch (1.2.1 ) I noticed that error_lager_lager_h crashes with a case clause of the form:

error_logger_lager_h exited with reason

{'EXIT',{{case_clause,[Ref,{ack,<0.3770.0>,{error,normal}}]}, -- Ranch CRASH EVENT (2 params)

[{error_logger_lager_h,log_event,2[{file,"/home/ubuntu/transecur/_build/default/lib/lager/src/error_logge

请教一个问题哈，我这里使用镜像方式，做了个三台机器的集群。
其中有一个队列中的消息体较大，一个可能几k到几十k，导致队列变成了flow状态。同时在服务段出现了一个新的进程，如下，数量很多，有两台机器是各90个，另外一台机器是5个。我想了解下这个进程是做啥的呢，为啥有一台这么少，另外两台那么多，感觉像是有异常，没找到相关的日志。

/opt/erl17.5/lib/erlang/erts-6.4/bin/beam.smp -B -- -root /opt/erl17.5/lib/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.5/ebin -noshell -noinput -hidden -boot start_clean -sasl er

There is no formal documentation related to node update, what data to keep etc.