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 159
    • Issues 159
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • 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
  • !79

Merged
Opened Feb 09, 2022 by Alp Mestanogullari@amestanogullari
  • Report abuse
Report abuse

Add client executable to run 'scripts' against a running Garg backend

"Scripts" in this case is just the script function in bin/gargantext-client/Script.hs, which currently contains a rather simple initial example of hitting the API, and tracking some GHC RTS allocation metric while doing a bunch of queries to the garg server. We can decide what a more complete/useful/helpful example would be in this MR or in a subsequent one, I don't mind.

All the infrastructure is there to use the entirety of the backend's API in those scripts, from tweaking node related things to submitting and polling jobs. If the steps were to be timed, we could also track duration of each step and be able to observe improvements through allocation metrics, GC cycles/time, execution time. We can build some higher level blocks for managing jobs or generating some interesting initial state if facing a fresh/local garg instance. You get the idea, this is pretty flexible and can be used to support various "experiments", as we've described before.

I tried to be generous with the comments.

Check out, review, and merge locally

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

git fetch origin
git checkout -b client-executable origin/client-executable

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 client-executable

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.

  • Discussion 0
  • Commits 1
  • Pipelines 1
  • Changes 9
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!79

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.