Closed MrSerth closed 1 week ago
What's the difference between developer-defined jobs and library-defined jobs in the CodeOcean context? Is this Solid Queue wording? 🤔
I chose this wording myself and would define the terms as follows:
app/jobs
.SolidCable::TrimJob
(see here), that is expected to be run regularly. The default for SolidCable::TrimJob
is once per day. Despite the newly introduced SolidCable job, there are other jobs included through the framework or library (like for ActiveStorage, or when mails are delivered later).Seems like I have to read more about Solid Queue soonish. 😇
Yes, that's definitely recommended! Solid Queue is now a default with Rails 8, so feel free to read more about it :+1.
Attention: Patch coverage is 66.66667%
with 4 lines
in your changes missing coverage. Please review.
Project coverage is 69.53%. Comparing base (
80b2ae6
) to head (7d3e17f
). Report is 2 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
app/jobs/concerns/active_record_logging.rb | 50.00% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
With these changes, we introduce a dedicated job backend for CodeOcean and migrate away from the default
:async
backend. This will improve reliability and allow for future introduction of developer-defined jobs. For now, the backend is mainly used for library-defined jobs.This PR assumes that the following PR is merged first:
2524
However, since the PR linked is mainly about documentation, this is not a show-stopper.