shahryarjb
Hello friends, Imagine you want to download a tar file from hex.pm website.
I have this function and do not want to install req hex plugin. as you see I find the "contents.tar.gz" and it is the binary of file.
@spec download(download_type, pkg) :: okey_return | error_return
def download(:hex, %{app: app, tag: tag_name}) when not is_nil(tag_name) do
case build_url("https://repo.hex.pm/tarballs/#{app}-#{tag_name}.tar") do
%Req.Response{status: 200, body: body} ->
converted = Map.new(body, fn {key, value} -> {to_string(key), value} end)
{:ok, converted["contents.tar.gz"]}
_ ->
mix_global_err()
end
end
And downloader function:
defp build_url(location) do
[base_url: location]
|> Keyword.merge(Application.get_env(:mishka_installer, :downloader_req_options, []))
|> Keyword.merge(Application.get_env(:mishka_installer, :proxy, []))
|> Req.request!()
end
Now I want to mock it, so this is the place I can not be able to fix.
One of my function test is what does not work:
body = [
{~c"VERSION", "3"},
{~c"CHECKSUM", "1D5EC32825E5AF1B5CF58933F4C918909BC79E4391EBE2B9315B02705145B18F"},
{~c"metadata.config", "{<<\"app\">>,<<\"mishka_installer\">>}.\n{<<\"build_tools\">>"},
{~c"contents.tar.gz", <<31, 139, 8, 0, 0, 0>>}
]
body_iolist_to_binary =
Enum.reduce(body, "", fn {key, value}, acc -> acc <> "#{key}:#{value}\n" end)
|> :erlang.iolist_to_binary()
Req.Test.expect(Downloader, fn conn ->
conn
|> Plug.Conn.put_resp_content_type("application/octet-stream")
|> Plug.Conn.send_resp(200, body_iolist_to_binary)
end)
If I put body directly I have error!! I have no idea how can simulate the hex output.
It should be noted my function works as well, my problem is located in testing this
Thank you in advance
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 9 of 9 Posts
LostKobrakai
A tar file is not some kind of map, like you’re building here in your test. The body you get from
Reqhas the tar already extracted, which gives you a map (see Req.Steps — req v0.5.0). In your mock you need to build a proper.tarfile, e.g. by using:erl_tar.shahryarjb
I thought about it before, And I send a tar file binary like this
but it did not work and the tar output of me is a binary, not same like hex
another code i tested with
erl_tar.createThese are my test i could not be able to send the
send_respLostKobrakai
This looks to be a bug. Tracing in
Reqit determinestaras format on the real request, butbinfor the mocked request – hence no automatic decoding happening. You could work around this by disabling the built in decoding and doing it manually.LostKobrakai
https://github.com/wojtekmach/req/issues/375
shahryarjb
Ohh, thank you.
I just put my other test that can be done
LostKobrakai
This would be another workaround, where the content type won’t define a charset, which I guess in your case makes it match the actual response.
shahryarjb
Thank you.
Your code returns
** (Req.ArchiveError) tar unpacking failed: Checksum failed, for now Idecode_body: falseIt works for now
And my test
wojtekmach
Even if you end up not using req_hex, I’d still consider using hex_core to get more realistic tests. Here is an example:
Thanks @LostKobrakai for reporting the format detection bug btw.
application/octet-stream; charset=utf-8is not a proper content-type for tar, these bytes are not utf8. I’ll see if I can make any improvements anyway though.LostKobrakai
Good point. I didn’t really think about that tbh. So
Plug.Conn.put_resp_content_type(conn, "application/octet-stream", nil)is actually the way to go then, not just a workaround.