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 6
    • Merge Requests 6
  • 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
  • !367

Merged
Opened Nov 20, 2024 by Grégoire Locqueville@glocqueville
  • Report abuse
Report abuse

Let users create a Subcorpus

@AlfredoDiNapoli would you be able to look into the following problem?

This MR's Changes

I added a command to create a subcorpus and a route to launch it. This addresses #384.

The code compiles fine.

The Problem

We tested the new route with @anoe using the Swagger interface, but we get Error: Unauthorized as a server response.

Various Sanity Checks/Things We've Tried:

We did authenticate beforehand (getting a token using the auth route, then clicking the Authorize button and copypasting the token, and checking that it says "Authorized").

We tried copypasting the Swagger-generated curl command; the command exits without output, and the subcorpus command does not get executed either (see attached screenshot)

Screenshot_from_2024-11-20_16-09-22

We tried adding a print statement to the subcorpus command to check that the problem lies with it not being called (and not to it being called but behaving the wrong way), and indeed it does not get called.

Edited Nov 21, 2024 by Grégoire Locqueville

Check out, review, and merge locally

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

git fetch origin
git checkout -b 384-let-users-create-a-subcorpus origin/384-let-users-create-a-subcorpus

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 384-let-users-create-a-subcorpus

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 4
  • Commits 2
  • Pipelines 1
  • Changes 12
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
1
Labels
New feature
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!367

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.