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

Looking into tracking the delay between when a change in the data happens and the eventual publish_subscription broadcast that sends a message out to each subscribed user, there's currently no easy way to retrieve that information.

Being able to measure how long it takes for the system to process an update and push it out to subscribed users would be nice to have from a performance benchmarki

This issue is to track the work for improving the documentation:

• Split up guides/pages on topics to provide softer introductions with specific pages for more detailed content
• Provide intro page with basic rationale of releases, terminology, and starting points for different languages (i.e. I'm coming from Ruby or Python, here is how OTP releases compare).
• Provide doc to prov

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

A tutorial that goes through steps from start to finish on setting up elixirscript in a phoenix application. Aimed at beginners.

For big scale schedulers, it would be nice if the user could manipulate those gen_stage values:

• max_demand of the Quantum.ExecutorSupervisor
• Possibility to start more than one Quantum.ExecutorSupervisor (even on multiple Cluster Nodes)

Environment

• Erlang version (20):

• Elixir version (1.6.2):

• Operating system: Debian 8.6

• Nerves Environment Info:
  Pkg: nerves_system_br
  Vsn: 1.2.2
  Type: system_platform
  BuildRunner: nil

  Pkg: nerves_system_orangepi_pcplus
  Vsn: 0.0.52
  Type: system
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:

Steps to reproduce

iex> t1 = "2019-04-03T21:07:45Z" |> Timex.parse!("{ISO:Extended:Z}") |> Timex.to_datetime("Europe/Berlin")
#DateTime<2019-04-03 23:07:45+02:00 CEST Europe/Berlin>
iex> Timex.day(t1)
93
iex> t2 = "2019-04-03T22:07:45Z" |> Timex.parse!("{ISO:Extended:Z}") |> Timex.to_datetime("Europe/Berlin")
#DateTime<2019-04-04 00:07:45+02:00 CEST Europe/Berlin>
iex> Timex.

My redis instance does not listen on TCP. Instead it is only serving over unix socket. I can't seem find that Exq supports unix sockets instead of TCP. I've tried different ways of configuring Exq to connect over unix socket but I've always greeted with a connection error message.

Does Exq support unix sockets or not?

Turns out this is a whitelist that defaults to []. We just got bit pretty hard by this behavior being hidden, so it's worth calling out in the docs. Effectively we had a bunch of plugs all acting on the presence of query params and were very confused why they never seemed to actually trip. This whitelist behavior was very unexpected.

Seems to have been added quite a while back in https://git

I am getting random {:error, :closed} from :hackeny.send_body/2 and Tesla.client crashes with following stack trace.

 {:EXIT, #PID<0.23655.28>, {{:badmatch, {:error, :closed}}, [{
Tesla.Adapter.Hackney, :"-request_stream/5-fun-0-", 3, [file: 'lib/tesla/adapter/hackney.ex', line: 74]}, 
{Enum, :"-reduce/3-anonymous-2-", 3, [file: 'lib/enum.ex', line: 3015]}, 
{Stream, :do_transform_e