Right now all the icons have an external link which make them:

• Prone to change/deletion
• Different size,format and resolution
• Various images are transferred over HTTP instead of HTTPS (which might become a problem in future as more and more browser start to block HTTP on HTTPS sites).
• External server might under-perform

My suggestion is to make a folder in the repository which has

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

Steps to reproduce

https://hexdocs.pm/distillery/extensibility/custom_commands.html

release_ctl eval --mfa "Mix.Tasks.MyTask.run/1" --argv -- "$@"

Should be :

release_ctl eval "Mix.Tasks.MyTask.run/1" --argv -- "$@"

Folks are getting mixed up by that, and also applying it incorrectly when attempting to

release_remote_ctl rpc "Mix.Tasks.MyTask.run/1" -

Ijust learn elixir and got in stuck in topic Documentation I run code in iex like in example but cannot get same result

iex(27)> defmodule Greeter do
...(27)>   @moduledoc """
...(27)>   Provides a function `hello/1` to greet a human
...(27)>   """
...(27)> 
...(27)>   def 

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

Using v3.1, tuples do not encode:

iex(1)> Poison.encode({1, 2})
{:error, {:invalid, {1, 2}}}

I think encoding to an array would be more robust. If that is a no-go, documenting the inability to encode tuples would be an improvement.

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)

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

We should either show good Elixir style in all koans or add a koan at the end that shows good elixir style.

This is just a reminder to double-check what we have.

https://github.com/niftyn8/elixir_style_guide

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:

The Overview section shows example of Article factory:

  def article_factory do
    %MyApp.Article{
      title: "Use ExMachina!",
      # associations are inserted when you call `insert`
      author: build(:user),
    }
  end

However, in Ecto Associations section there is following snippet:

def article_factory do
  %Article{
    title: "Use ExM

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.

Hello,

Could you add the pop-up documentation of a function/variable when we press Ctrl + Q? For now it shows No documentation found. even if I used @doc on the function.

Thanks

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

On the ExAdmin.Index page under Override the Actions Column a macro or function named safe_concat is used to join the results of the link_to methods together. I couldn't find reference to this so I rolled my own. For reference, here's the version that I created:

defp safe_concat(list) do
  list
  |> Enum.map(fn x -> Phoenix.

FYI
Readme says:

def deps do
  [{:coherence, "~> 0.6"}]
end

However, in https://hex.pm/packages/coherence it only has version 0.5.2. Users get this error:

➜  path-to-project git:(master) ✗ mix deps.get
** (Mix) No matching version for coherence ~> 0.6 (from: mix.exs) in registry

The latest version is: 0.5.2

See screenshot. Thank you!

![screen s

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

Precheck

I didn't find any existing issues (open or closed) that cover this.

I think my Dialyzer and Erlex are up-to-date but I could be wrong – please let me know.

Environment

$ elixir --version
Erlang/OTP 21 [erts-10.2.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe]

Elixir 1.8.0 (compiled with Erlang/OTP 20)
$ cat mix.lock | grep dialyxir
  "dia

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