ElixirWeekly

Issue #78 - Live-debugging an Elixir Memory/process Leak

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

This week in Elixir

Elasticsearch
Elasticsearch is a new Elixir library for interacting with Elasticsearch. Since it’s based on protocols and behaviours, so it’s both easy to use and flexible.

Live-debugging an Elixir Memory/process Leak
Orestis has been diagnosing a process leak (that manifested as a memory leak) using the remote console - heureka!

Pattern Matcher for Protocols
Aleksei blogged about how one could pattern match function clauses against the implementations of a protocol.

Periodic Tasks with Elixir - Part 2
In part 2, Ville shows us an alternative implementation and how to deal with drift.

Ecto Queries Using "fragment" in Elixir
Rohen wrote this short article about using "fragment" in Ecto queries.

Elixir Users' Survey 2017
This is Josh's yearly Elixir Survey. Participating in the survey is greatly appreciated and gives extra karma points!

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).