Search Results for "mfbyas-2-0"

Absinthe is the GraphQL toolkit for Elixir, an implementation of the GraphQL specification built to suit the language's capabilities and idiomatic style. If you're new to GraphQL, we suggest you read up a bit on GraphQL's foundational principles before you dive into Absinthe. Absinthe's functionality generally falls into two broad areas. Defines the structure of data entities and the relationships between, as well as the available queries, mutations, and subscriptions, using an elegant...

Explorer brings series (one-dimensional) and data frames (two-dimensional) to Elixir for fast data exploration.

Ueberauth is a two-phase authentication framework that provides a clear API, allowing for many strategies to be created and shared within the community. It is heavily inspired by Omniauth. You could call it a port but it is significantly different in operation, but almost the same concept. Huge hat tip to Intridea. Ueberauth provides only the initial authentication challenge, (initial OAuth flow, collecting the information from a login form, etc). It does not authenticate each request, that's...

... in and out of the node, number of garbage collector runs, words of memory that were garbage collected, and the global reductions count for the node. Total scheduler utilization will equal 1.0 when all schedulers have been active all the time between the two refresh intervals. The result being that there is a decent chunk of CPU usage that would be mostly free for scheduling actual Erlang work (assuming the schedulers are busy waiting more than trying to select tasks to run).

Jupyter's kernel for Elixir. You can manage your packages in runtime with Boyle. Name of the package honours remarkable chemist, Robert Boyle. This package allows you to manage your Elixir virtual enviromnent without need of restarting erlang virtual machine. Boyle installs environment into ./envs/you_new_environment directory and creates new mix project there with requested dependencies. It keeps takes care of fetching, compiling and loading/unloading modules from dependencies list of that...

The Gun library doesn't have a full 2.0 release yet, so we depend on :grcp_gun 2.0.1 for now. This is the same as :gun 2.0.0-rc.2, but Hex doesn't let us depend on RC versions for releases. Generate Elixir code from the proto file as protobuf-elixir shows(especially the gRPC Support section). Implement the server-side code and remember to return the expected message types. You can start the gRPC server as a supervised process. First, add GRPC.Server.Supervisor to your supervision tree.

... in the test environment. build/2 is a function call. As such, it gets evaluated immediately. By default, ExMachina will merge the attributes you pass into build/insert into your factory. But if you want full control of your attributes, you can define your factory as accepting one argument, the attributes being passed into your factory.

Erlang and Elixir make it very easy to send messages between processes even across the network, but there are a few pitfalls. Sending a message to many PIDs across the network also copies the message across the network many times. Send calls cost about 70 µs/op so doing them in a loop eventually gets too expensive. Manifold distributes the work of sending messages to the remote nodes of the PIDs, which guarantees that the sending processes at most only calls send/2 equal to the number...