t; --
> (Unsigned mail from my phone)
>
>
>
> Original message
> From: Benjamin Schollnick
> Date: 10/1/21 15:41 (GMT+10:00)
> To: django-users@googlegroups.com
> Subject: Re: Apple M1 Silicon + Django = weird results
>
> Okay, a further up
.Good luckMike--(Unsigned
mail from my phone)
Original message From: Benjamin Schollnick
Date: 10/1/21 15:41 (GMT+10:00) To:
django-users@googlegroups.com Subject: Re: Apple M1 Silicon + Django = weird
results Okay, a further update.While rewrite the code, did seem to make a
mar
Okay, a further update.
While rewrite the code, did seem to make a marginal difference, the corruption
issue persisted intermittently.
Just today, I did some more digging, and I remembered that I turned on Jumbo
Frames for my ethernet port on the M1 Mac Mini.
Turning that off, at first glanc
Just an update.
Working my way through the problem, it appears that either the data is being
written truncated to the database, or Pillow is generating a truncated image
preview (which is being stored to the database).
The later is more likely, since I am seeing no other data corruption errors.
> Have you tried the download with various browsers? I wonder if Safari or
> Chrome released at the same time as the M1 chips is causing different Range
> header behavior than that code is designed to handle. So it might not be the
> M1 chip, but just an unrelated change in browser software tha
Looking at that code for RangedFileResponse, I'm kind of skeptical that it
properly implements the Range header. Try removing that bit and see if it
works.
Have you tried the download with various browsers? I wonder if Safari or
Chrome released at the same time as the M1 chips is causing different
Folks,
I’m using django for an online gallery application, and I’ve seen some weird
results since switching over to the M1 Mac Mini.
(Please note, I am running it under Rosetta / Intel Translation, since pillow
doesn’t seem to build under M1 native).
So this could be a quirk of Rosetta, Django,
7 matches
Mail list logo
