Laravel recipe `artisan:migrate` task does not honor `default_timeout = null`

[calebdw]

• Deployer version: 7.0.2
• Deployment OS: Ubuntu 20

deploy.php

<?php

namespace Deployer;

require 'recipe/laravel.php';

set('default_timeout', null); // because of long-running migrations
set('shared_dirs', [
    'storage',
    'uploads',
]);

host('<host>')
    ->setLabels([
        'stage' => 'staging',
    ])
    ->setRemoteUser('<user>')
    ->setDeployPath('<path>');

task('deploy', [
    'deploy:prepare',
    'artisan:storage:link',
    'artisan:optimize:clear', // clear all caches
    'artisan:config:cache',
    'artisan:route:cache',
    'artisan:view:cache',
    'artisan:event:cache',
    'artisan:down',
    'artisan:migrate',
    'deploy:symlink',
    'artisan:up',
    'artisan:horizon:terminate',
    'deploy:unlock',
    'deploy:cleanup',
    'deploy:success',
]);

after('deploy:failed', 'deploy:unlock');

Hello, I recently upgraded to Deployer 7 and I just encountered a long-running migration that caused the deploy to fail after 300 seconds, despite default_timeout being set to null.

This used to work in Deployer 6 so not too sure what's going on...

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[calebdw]

Update:

Everything appears to be working correctly when default_timeout is set on the host level, not sure if this is the intended behaviour or not but it's not reflected in the docs from what I could tell...

The below code works:

<?php

namespace Deployer;

require 'recipe/laravel.php';

set('default_timeout', null); // does NOT work
set('shared_dirs', [
    'storage',
    'uploads',
]);

host('<host>')
    ->set('default_timeout', null) // works
    ->setLabels([
        'stage' => 'staging',
    ])
    ->setRemoteUser('<user>')
    ->setDeployPath('<path>');

// ...

[hashimaziz1]

How was this completed, as I've been getting a broken pipe for the last day or so with a long-running migration (large CSV file) using the GitHub Action. How can I rule out this being the issue? default_timeout config option is set to 6000 but I get a client_loop: send disconnect: Broken pipe error after about 5 minutes of migrating, and changing the SSH/server configs doesn't seem to make a difference.

[github-actions]

This issue has been automatically closed. Please, open a discussion for bug reports and feature requests.

Read more: [https://github.com//discussions/3888]