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 175
    • Issues 175
    • 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
  • Issues
  • #268

Closed
Open
Opened Sep 28, 2023 by Przemyslaw Kaminski@cgenie
  • Report abuse
  • New issue
Report abuse New issue

Broken hash generation for notes documents

Create a new database from scratch. In your private folder, add a new corpus, then add a 'Notes' folder. Edit the markdown file in codi md.

Stop the server. Remove your database. Recreate it. Repeat the steps above to create corpus and notes folders.

Suddenly, your old codimd document is back.

I haven't analyzed but I think our hash id generation is broken. I guess this is so because codimd accepts any string after / as a document id.

So, as a frame_id in Notes hyperdata we have a string with 64 characters like 5cca7bfa92c5e05836acdf0ef3621a90d22dfab34fd5971ad9568cee34aa6cd0 yet it is reproducible :)

Edited Sep 28, 2023 by Przemyslaw Kaminski
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#268