preciz
I’m calling Nx.from_binary(binary, :u8)
If the binary_size is above 2147483647 (which is 2^31 - 1) then it raises the below error:
iex(dev@dev)49> Nx.from_binary(binary_part(bin, 0, 2147483647), :u8)
#Nx.Tensor<
u8[2147483647]
EXLA.Backend<host:0, 0.4210033359.2202140741.62473>
[0, 0, 0, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, ...]
>
iex(dev@dev)50> Nx.from_binary(binary_part(bin, 0, 2147483648), :u8)
** (RuntimeError) Unable to get dimensions.
(exla 0.7.2) lib/exla/shape.ex:89: EXLA.Shape.unwrap!/1
(exla 0.7.2) lib/exla/shape.ex:29: EXLA.Shape.make_shape/2
(exla 0.7.2) lib/exla/backend.ex:45: EXLA.Backend.from_binary/3
iex:50: (file)
Is this intended behavior or fundamental limitation? I don’t find it documented in EXLA or NX.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
polvalente
This is probably a bug. Please try out
mainbranch with{:exla, github: "elixir-nx/nx", sparse: "exla"}, and if the problem persists, open an issue so that I can tackle it.We’ve just merged a new PR yesterday that changes shape handling, so this might have gone away.
polvalente
Actually, I might have found the bug
Please try the branch:
pv-fix/exla-get-tuplepreciz
This branch definitely fixes it, tried with a huge binary.
I hope it will be merged soon, until then I will use it from GitHub. Thanks for the fix!
polvalente
Awesome! I just have to think about how to test this and it’ll be merged