Maxximiliann
defmodule PythonProcessAPI do
require Logger
def process_output(foo, _, python_path) do
Print.text("Results received from #{python_path}.")
Logger.info("#{inspect(foo)}, __MODULE__, line 8")
end
def connect(data, python_path) do
port =
:erlang.open_port(
{:spawn, python_path},
[:binary, packet: 4]
)
execute = fn input ->
send(port, {self(), {:command, :erlang.term_to_binary({input})}})
receive do
foo ->
process_output(foo, data, python_path)
end
end
execute.(data)
end
end
#my_python_process.py
import sys
import simplejson as json
from loguru import logger
from conversion import to_string
from erlastic import port_connection, Atom as atom
from some_library.errors import (BaseError, AuthenticationError, PermissionDenied,
ArgumentsRequired, BadRequest, BadResponse,
NullResponse, InvalidAddress, NotSupported, NetworkError, DDoSProtection,
RateLimitExceeded, OnMaintenance, InvalidNonce, RequestTimeout)
mailbox, port = port_connection()
@logger.catch
def submit_report(success_status, report, arg1, arg2, arg3):
logger.info("Processing report . . . ")
full_report = report | {
'arg1': arg1, 'arg2': arg2, 'arg3': arg3}
full_report_json = json.dumps(full_report)
try:
port.send((atom(success_status), (full_report_json)))
logger.info("Transmitted report . . . ")
except (BrokenPipeError) as error:
logger.exception(error)
sys.exit()
finally:
sys.exit()
@logger.catch
def fetch_params():
for params_data in mailbox:
params_hash = to_string(params_data)
return params_hash[0]
@logger.catch
def some_function():
params_json = fetch_params()
params = json.loads(params_json)
arg1, arg2, arg3 = params
try:
submission_report = some_operation(params)
except (BaseError, AuthenticationError, PermissionDenied,
ArgumentsRequired, BadRequest, BadResponse,
NullResponse, InvalidAddress, NotSupported, NetworkError, DDoSProtection,
RateLimitExceeded, OnMaintenance, InvalidNonce, RequestTimeout) as error:
logger.exception(error)
logger.info(params)
submit_report(
'error', {'error': str(error)}, arg1, arg2, arg3)
except Exception as crash_report:
logger.exception(crash_report)
logger.info(params)
submit_report('error', {'error': str(
crash_report)}, arg1, arg2, arg3)
else:
submit_report(
'ok', submission_report, arg1, arg2, arg3)
@ logger.catch
def main():
some_function()
if __name__ == '__main__':
main()
The problem we’re having is that data can be passed to the Python process successfully but the return message never reaches the Elixir side. All success messages from the Python end are logged, but there are no exceptions or error messages to go on. We’re at a loss for how to diagnose what’s wrong. Suggestions? Recommendations?
Trending in Questions
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
Anyone here using Honeybadger?
My Honeybadger account is being overwhelmed with noise from some bots. Seeing a lot of
Bandit.HTTPError...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #elixirconf-us
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
derek-zhou
Can’t comment on the python side.
You are only handling one message in the elixir side. Is it intentional? Maybe the message is still in the inbox. try flush() in iex.
kokolegorille
Can’t comment on erlastic, but I have been using erlport lately with python.
This blog post is really nice…
https://medium.com/stuart-engineering/how-we-use-python-within-elixir-486eb4d266f9