Chunk uploads from worker to Moodle to allow archives being larger than $CFG->maxbytes value

[tmtsc]

If the archive file is larger than the system-wide setting maxbytes, the job fails ('errortype': 'fileoversized', 'error': '[[maxbytes]]').
(The archive could be created without issues when the maxbytes value was temporarily increased for testing purposes.)

Is there a way to work around this? The maxbytes value is crucial in various other contexts (e.g., upload size limits for course materials and submissions), and therefore cannot be increased specifically for the quiz archiver.

We considered assigning the "course:ignorefilesizelimits" permission to the quiz_archiver role, but it appears to have no effect.

[ngandrass]

Hi @tmtsc,

thanks for reporting this. I can reproduce this problem by setting $CFG->maxbytes to a value smaller than the archive that is being uploaded.

I'm currently unsure if we can circumvent this issue in any way since $CFG->maxbytes is meant to be a global site limit that is independent of the course- or user-specific upload limit and therefore not affected by the moodle/course:ignorefilesizelimits capability.

Are you aware that you can set different upload limits for course files and submissions? Maybe this already is able to solve your problem :)

[ngandrass]

Okay, the system wide maxbytes setting is strictly enforced during uploads via the web service API, see:

https://github.com/moodle/moodle/blob/09590d30cf1da96b51340662beca72be53690022/public/webservice/upload.php#L107-L112

Therefore please check if you are able to raise this setting, sorry :(

[tmtsc]

@ngandrass Thank you very much for your tips and research.
So I need to find alternative solutions. Adjusting the specific course upload limit may not be sufficient, as it is a default setting that can be modified by course teachers (as far as I know, there's no way to prevent this) - but still, thanks for the hint!

[ngandrass]

@tmtsc Thanks for your response. In this case the only solution I see right now would be to split the upload process into smaller chunks that are then combined back to the larger original file on the Moodle server itself. While this will cause additional load, this would circumvent the upload limit we are running into here.

I'll leave this issue open as a possible feature for future releases :)