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 164
    • Issues 164
    • 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
  • !418

Open
Opened Jun 16, 2025 by Alfredo Di Napoli@AlfredoDiNapoli
  • Report abuse
Report abuse

Report errors/warnings for `insertMasterDocs` individually

Fixes #476.

I have eventually settled on a design where if the ngrams can't be extracted, the document(s) are still inserted; the idea would be that if the NLP server is temporarily unavailable we can regenerate the ngrams at a later stage.

I wasn't able to catch potential exceptions being thrown by insertMasterDoc due to #480 which I will need to investigate.

Of course inserting documents individually is going to be less efficient than inserting them into batches, but we gain individual atomicity and a rollback transaction won't affect whole blocks of documents.

Edited Jun 16, 2025 by Alfredo Di Napoli

Check out, review, and merge locally

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

git fetch origin
git checkout -b adinapoli/issue-476 origin/adinapoli/issue-476

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 adinapoli/issue-476

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 6
  • Pipelines 5
  • Changes 12
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
1
Labels
Beta quality (merge at your own risk)
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!418