Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[10.x] Add progress option to PendingBatch #49099

Closed
wants to merge 1 commit into from
Closed

[10.x] Add progress option to PendingBatch #49099

wants to merge 1 commit into from

Conversation

orkhanahmadov
Copy link
Contributor

The goal is to invoke a callback every time a job in batch successfully executes. Useful when we want to fire an event on progress, which will send a broadcast message to the user with a real progress percentage using \Illuminate\Bus\Batch progress value.

I named the new option progress, I believe it makes sense because a callback will be called only when the batch progresses. But feel free to rename it, or request rename.

@mvynhb
Copy link

mvynhb commented Nov 27, 2023

@orkhanahmadov

Shouldn't the progress callback be called on both successful and failed jobs? As I understand the current progress percentage logic is based on both successful and failed jobs.

@orkhanahmadov
Copy link
Contributor Author

orkhanahmadov commented Nov 27, 2023

@orkhanahmadov

Shouldn't the progress callback be called on both successful and failed jobs? As I understand the current progress percentage logic is based on both successful and failed jobs.

@mvynhb I believe it is not necessary. Batch already runs catch callbacks when a job in the batch fails. catch callbacks also receive a Batch instance, there you can still see the progress and everything that the Batch instance contains.
https://laravel.com/docs/10.x/queues#dispatching-batches

@taylorotwell
Copy link
Member

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!

If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants