Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 155
    • Issues 155
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Merge Requests
  • !363

Merged
Opened 6 months ago by Przemyslaw Kaminski@cgenie
  • Report abuse
Report abuse

Resolve "Job workers & persistence"

Related to #238

This is huge rewrite of our infrastructure into async job workers. I tried to make it as unobtrusive as possible. Basically you should just run the server as normal, then run the worker with something like:

cabal v2-run gargantext-cli -- worker run --name default

And remember to add this to .toml:


[worker]

# After this number of seconds, the job will be available again.
# You can set timeout for each job individually and this is the
# preferred method over using defaultVt.
default_visibility_timeout = 1

# default delay before job is visible to the worker
default_delay = 0

[worker.database]
host = "127.0.0.1"
port = 5432
name = "pgmq"
user = "gargantua"
pass = "<pass>"

[[worker.definitions]]
name = "default"
queue = "default"

(it's in the .toml_toModify anyways).

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b 238-dev-async-job-worker origin/238-dev-async-job-worker

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/dev
git merge --no-ff 238-dev-async-job-worker

Step 4. Push the result of the merge to GitLab

git push origin dev

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

Request to merge 238-dev-async-job-worker into dev
  • Email patches
  • Plain diff
Pipeline #6993 passed for 35306b4d on 238-dev-async-job-worker

          Merged by delanoe 5 months ago

          The changes were merged into dev with 91e1f0a6

          Mentions #238

          Pipeline #7005 canceled for 91e1f0a6 on dev
                  • Discussion 3
                  • Commits 68
                  • Pipelines 67
                  • Changes 141
                  • Loading...
                  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
                  Please register or sign in to reply
                  Assignee
                  Assign to
                  Epic 0.0.7
                  Milestone
                  Epic 0.0.7
                  Assign milestone
                  None
                  Time tracking
                  No estimate or time spent
                  0
                  Labels
                  None
                  Assign labels
                  • View project labels
                  Lock merge request
                  Unlocked
                  participants
                  Reference: gargantext/haskell-gargantext!363

                  Revert this merge request

                  This will create a new commit in order to revert the existing changes.

                  Switch branch
                  Cancel
                  A new branch will be created in your fork and a new merge request will be started.

                  Cherry-pick this merge request

                  Switch branch
                  Cancel
                  A new branch will be created in your fork and a new merge request will be started.