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

Catch the AutoloadNotAllowedException also for legacy jobs #23901

Merged
merged 1 commit into from
Apr 11, 2016

Conversation

MorrisJobke
Copy link
Contributor

This was reported by @benediktg in owncloud/files_antivirus#98 (comment)

@karlitschek I would like to backport this to stable9, is this okay?

* same as #18839 for legacy jobs
* avoids spamming the log with useless entries
@MorrisJobke MorrisJobke added this to the 9.1-current milestone Apr 11, 2016
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @icewind1991 and @DeepDiver1975 to be potential reviewers

@MorrisJobke
Copy link
Contributor Author

@Xenopathic @nickvergessen @benediktg @LukasReschke Please review :)

@nickvergessen
Copy link
Contributor

👍

call_user_func($argument);
}
} catch (AutoloadNotAllowedException $e) {
// job is from a disabled app, ignore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe log this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the idea - we don't want to log it. That's what is done today and what #18839 also removed ;)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why wouldn't you want to log this. If it happens and you get such an entry, just delete it manually and it wont show up again?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we outsource our own fault of properly unregister background jobs to the user? 😕

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well silently ignoring and always looping over is at least not the right way...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then we should drop it somehow.

@icewind1991
Copy link
Contributor

👍 looks good

@karlitschek
Copy link
Contributor

great catch. please backport

@DeepDiver1975 DeepDiver1975 merged commit ddbb9b7 into master Apr 11, 2016
@DeepDiver1975 DeepDiver1975 deleted the catch-autoloader-exception-in-legacy-jobs branch April 11, 2016 12:06
@MorrisJobke
Copy link
Contributor Author

stable9: #23930

@nickvergessen
Copy link
Contributor

Backported to 8.2: #24508 because it was reported there as well #24487

@lock
Copy link

lock bot commented Aug 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants