#34674: Updating the file contents of a Django FileField during upload results 
in
I/O error
-------------------------------------+-------------------------------------
     Reporter:  Jeroen Jacobs        |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  File                 |                  Version:  4.2
  uploads/storage                    |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Hello Jeroen,

 Please don't re-open tickets closed by Django maintainers/fellows. The
 code you shared, while indeed uses the Django provided `FileField`, does
 make a custom/non traditional use of it. Please reach out to the user
 support channels as suggested, where you can get help on whether the
 approach you took to encrypt the file content is sound or if there are
 other considerations that are needed.

 I did read the ticket description, I understand you may feel frustrated
 but please follow the [https://www.djangoproject.com/conduct/ Django Code
 of Conduct], and please see
 [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/#reporting-bugs the guidelines on reporting bugs].

 The example code you provided is incomplete and does not work. There are
 undefined names and missing imports, and the stacktrace shows that a view
 and a form are involved which you did not provide. There is also lacking
 details of the settings of the project, such as the file storage backend
 that is being used.

 As recommended, please reach out for help in the user forum or Discord
 channel, where there may be a bigger audience able to help in getting to
 the root of the issue. If this is indeed a Django bug, please reopen with
 a small yet complete Django project with the necessary models and other
 files to reproduce (I'd advice leaving encryption out of the code to
 reduce the scope of the reproducer).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34674#comment:6>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070188e9ee3988-b41bf0f3-bc2e-4ee5-85eb-a5b934a03c35-000000%40eu-central-1.amazonses.com.

Reply via email to