Consider sharing exception "blame" information to aid debugging

[1player]

I just got an error logged on my dashboard:

** (FunctionClauseError) no function clause matching in XXX.yyy/2

This is not enough to know to understand what exactly happened, and such information is available in the exception structure itself. The full body of the exception that can be extracted with Exception.blame/3 (https://hexdocs.pm/elixir/1.13/Exception.html#blame/3) which in this case would show the arguments passed to the function:

    The following arguments were given to XXX.yyy/2:

        # 1
        nil

        # 2
        []

    Attempted function clauses (showing 1 out of 1):

        def xxx(%Struct{} = a, b)

[unflxw]

HI @1player,

Unfortunately we cannot provide information about the specific arguments passed to the function, due to the risk of leaking personally identifiable information. However, the backtrace for the error should describe the shape of the arguments (in this example, the + operator is called with a string and an integer as arguments):

This is, however, missing from errors reported via the error backend, as the backtrace is not accessible then.