#30506: Auto-reloading with StatReloader very intermittently throws "ValueError:
embedded null byte".
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Liam):
Replying to [comment:3 Tom Forbes]:
> Hey Keryn,
> Have you tried removing `resolve()` yourself, and did it fix the issue?
>
> I chose to use `resolve()` to try and work around a corner case with
symlinks, and to generally just normalize the paths to prevent
duplication.
>
> Also, regarding your comment above, you would need to use
`print(repr(path))`, as I think the print machinery stops at the first
null byte found (hence just `/Users`, which should never be monitored by
itself).
>
> If you can provide me some more information I'm more than willing to
look into this, or consider removing the `resolve()` call.
Hi Tom,
I am also getting this error, see here for the stackoverflow question
which I have attempted to answer:
https://stackoverflow.com/questions/56406965/django-valueerror-embedded-
null-byte/56685648#56685648
What is really odd is that it doesn't error every time and looks to error
on a random file each time. I believe the issue is caused by having a venv
within the top level directory but might be wrong.
Bug is on all versions of django >= 2.2.0
--
Ticket URL: <https://code.djangoproject.com/ticket/30506#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.7edf0452cf5d0011d5486bb43f03d493%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
