-
Notifications
You must be signed in to change notification settings - Fork 334
WPB-20728 background job for user group to channel association #4797
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
base: gdifolco/WPB-19713_user-groups-channels-list
Are you sure you want to change the base?
WPB-20728 background job for user group to channel association #4797
Conversation
ff76698
to
7d72068
Compare
c71074e
to
b4af1e1
Compare
7d72068
to
a09bc11
Compare
# Maximum number of in-flight jobs per process | ||
concurrency: 8 | ||
# Per-attempt timeout in seconds | ||
jobTimeout: 60 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this something we want to define per job type? deleting users takes less time than scanning a huge table for inconsistencies.
i have little context, though. maybe i'm thinking ahead to far.
-- You should have received a copy of the GNU Affero General Public License along | ||
-- with this program. If not, see <https://www.gnu.org/licenses/>. | ||
|
||
module Wire.API.BackgroundJobs where |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i know we're using wire-api for way more than our types containing rest api artefacts, but is this pushing it too far? this module is not used in any service other than background worker, and i think it shouldn't be. move to background-worker subsystem?
import Wire.BackgroundJobsRunner.Interpreter (interpretBackgroundJobsRunner) | ||
import Wire.BackgroundWorker.Env (AppT) | ||
|
||
dispatchJob :: Job -> AppT IO (Either Text ()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe something with more structure than Text
for the errors?
@battermann I have pushed the new jobs from the interpreter, I have fixed the job processing, and injected the options on the Haskell side. Tests and k8s are left to be done. Not touched: Matthias review and |
58ad87b
to
e967a41
Compare
Checklist
changelog.d