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
  • Issues
  • #217

Closed
Open
Opened May 30, 2023 by delanoe@anoe
  • Report abuse
  • New issue
Report abuse New issue

Ngrams Status change

Since the Ngrams Table optimization, some change of status of ngrams are not stored any more.

To reproduce it, go on dev instance and check your AnoeCgenie Team, you will find the StatusChangeIssue (you could download the docs and ngrams as json file).

Here is the video to reproduce the critical issue: https://dl.gargantext.org/2023-05-30-1722_statusChangeIssue.ogv

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
Critical
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#217