You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When $maxTaskPayloadInBytes is greater than 100000 (by default), the \Spatie\Async\Runtime\ParentRuntime::encodeTask function creates a temporary file in the /tmp directory.
if (strlen($serializedTask) > $maxTaskPayloadInBytes) {
// Write the serialized task to a temporary file and package it as a `FileTask`:$filename = tempnam(sys_get_temp_dir(), 'spatie_async_task_');
file_put_contents($filename, $serializedTask);
$file_task = newFileTask($filename);
$serializedTask = base64_encode(serialize($file_task));
}
However, this function is called twice, resulting in two temporary files being created. At the end of the process, only one of these files is removed, leaving the other as a lingering temporary file.
The \VXM\Async\Runtime\ParentRuntime::createProcess method calls its parent method \Spatie\Async\Runtime\ParentRuntime::createProcess. Is there a specific reason for this? With this approach, everything looks to work fine
When
$maxTaskPayloadInBytes
is greater than 100000 (by default), the\Spatie\Async\Runtime\ParentRuntime::encodeTask
function creates a temporary file in the/tmp
directory.However, this function is called twice, resulting in two temporary files being created. At the end of the process, only one of these files is removed, leaving the other as a lingering temporary file.
The
\VXM\Async\Runtime\ParentRuntime::createProcess
method calls its parent method\Spatie\Async\Runtime\ParentRuntime::createProcess
. Is there a specific reason for this? With this approach, everything looks to work fineThe text was updated successfully, but these errors were encountered: