Custom Query (1174 matches)
Results (367 - 369 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #288 | cant-reproduce | Feed metadata now missing from blog pages | ||
| Description |
http://mediagoblin.org/news/index.html Used to be that the feed URL was set in the headers... that's not the case any more. I don't know how to add it back to just that section :) Assigning to Will! (Or, should we make the feed metadata in the headers on every page?) |
|||
| #5068 | fixed | File extension matching fails with relative paths | ||
| Description |
media_types/__init__.py:109:
if filename.find('.') > 0:
should be: Because otherwise files of the form "./blah.mp4" don't work, which happens with the localfiles plugin. |
|||
| #834 | duplicate | File upload size limited by available system memory | ||
| Description |
File uploads appear to be limited by the amount of memory available on the system. In particular, I receive a MemoryError from queue_file.write(submitted_file.read())' in the mediagoblin/submit/lib.py file. This occurs when the file size I upload exceeds 1.7GB -- things worked fine for files less than 1.7GB . I do not have any max_file_size specified and coincidentally 1.7GB is the amount of unused RAM I have available on my server (including swap). These errors occur during the upload phase of the publishing process, before any transcoding is attempted. By watching top, it can be seen that memory usage keeps growing, including swap usage, and if all memory is used up then the upload fails. If the transfer completes without running out of memory then all used memory is freed and transcoding proceeds. This to me seems indicative of either a memory leak in the file copying process, or that file copying reads the entire file into RAM before writing it back out. Regardless the cause, it poses a severe limitation on Mediagoblin deployment using small device servers and hosted slices where one might be charged for or have limitations placed on RAM usage. Note: I have added an additional gigabyte of RAM to my server and was able to upload larger files, but still encountered this bug when the file size was greater than 2.7GB . |
|||
