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

Steps to reproduce

• Install a new plugin, asdf plugin-add nodejs, for example
• Try to install the same plugin again

You should notice that the message that the plugin were already installed was an stderr

Expected behavior

Since this is not actually an error, it should only return the message, without any error status. This is important because some automation scripts can

Environment

• OS:
• Erlang/OTP:
• EMQ:

Description

The official website's client programming Javascript unsubscribe function is missing one letter, it should be unsubscribe, and the unubscribe on the official website is printed as undefined

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

Is your feature request related to a problem? Please describe.
I want to use mod_http_upload option external_secret with an self-written php script. To be able to enforce a per user quota, I have to somehow get the JID (or a hash of it) out of the PUT URL.

Describe the solution you'd like
I already inspected the URL mod_http_upload with external_secret generates. It seems to h

If there is a means to do this then I apologize and would someone please point to it or document it for easier use. The erlang NIF guide shows the load funtion as:

int (*load)(ErlNifEnv* env, void** priv_data, ERL_NIF_TERM load_info)

I am unable to find a way to do that with rustler but it is something I need as my NIF does some setup when the module loads and I want to be able to access

As mentioned in #1299 the new on_deliver and on_session_expired hooks should be supported in the plugins and properly documented:

• update webhooks
• update diversity
• update plugin hook
• update vernemq_dev

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

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

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

The compiler should be able to render markdown or html documentation from modules compiled. For now we can include the names and type of functions and data structures exported, and later add support for additional textual documentation from comments etc.

As reported on leo-project/leofs#1156 (comment), there are some users who can't find any information on how to stop/cancel the compaction because what compaction operations we provide through leofs-adm are

• compact start
• compact suspend
• compact resume
• compact status

so there is no stop/cancel commands.

Unfortunately actually we haven't impl

Hello,
While looking at this project for an open source class looking at a software's inclusiveness, something that was found that could be beneficial would be creating some guidelines on how a person could help contribute to this project.

Whether it be basic instructions on fixing existing issues or working on enhancements, or even some information on who or how to contact people that could

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

MongooseIM version: 3.4
Erlang/OTP version: Erlang/OTP 21 [erts-10.3.1]

`2020-02-28 07:35:20.354 [error] <0.4174.0>@mongoose_acc:jid_from_params:223 gen_fsm <0.4174.0> in state session_established terminated with reason: no match of right hand value error in mongoose_acc:jid_from_params/3 line 223
2020-02-28 07:35:20.354 [error] <0.4174.0>@mongoose_acc:jid_from_params:223 CRASH REPORT Process

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

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",
         "    ",
     

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

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:

The current definition uses OpenAPI 2. OpenAPI 3 provides interesting features which c