infrastructure/nixos-config
infrastructure/nixos-config
19
0
Fork 0
Code Issues 6 Pull requests Projects Releases Packages Wiki Activity Actions

Update "Executing R2R locally" with how to do so using Cursor. #36

New issue
Closed
opened 2025-05-22 00:08:15 +00:00 by brent.edwards · 1 comment
brent.edwards commented 2025-05-22 00:08:15 +00:00
Member
Copy link

Right now, https://docs.cleverthis.com/en/CleverBRAG/local-R2R only has complete instructions on how to execute R2R under PyCharm.

But there is a note at the end:

The Dev Containers extension is only available in the PyCharm Professional edition. If you happen to run the Community edition, then a possible alternative is Visual Studio Code, for which there is a free Dev Containers extension.

In Visual Studio Code with the Dev Containers extension installed, open the cleverbrag-core project, and from the command palette run these two commands:

Dev Containers: Open Container Configuration File. (VSC should open the json file)
Dev Containers: Rebuild Containers
After the open the terminal to watch the command output ('view log'). When containers are built, you may continue the same way as if you'd connected to the server with PyCharm, see below.

Cursor is based on Visual Studio, so similar instructions should work. But these instructions don't have enough information. Here are some questions:

  1. Which dev containers extension should be installed? I found multiple extensions.
  2. Where do we find the "dev containers" command?
  3. Are there any indications of whether the user is in a dev container or on their Nix machine? Does opening a new terminal run that terminal inside the dev container or inside the Nix machine?

Sorry for being dumb; I have rarely used Visual Studio Code.

Right now, https://docs.cleverthis.com/en/CleverBRAG/local-R2R only has complete instructions on how to execute R2R under PyCharm. But there is a note at the end: > The Dev Containers extension is only available in the PyCharm Professional edition. If you happen to run the Community edition, then a possible alternative is Visual Studio Code, for which there is a free Dev Containers extension. > In Visual Studio Code with the Dev Containers extension installed, open the cleverbrag-core project, and from the command palette run these two commands: > Dev Containers: Open Container Configuration File. (VSC should open the json file) > Dev Containers: Rebuild Containers > After the open the terminal to watch the command output ('view log'). When containers are built, you may continue the same way as if you'd connected to the server with PyCharm, see below. Cursor is based on Visual Studio, so similar instructions should work. But these instructions don't have enough information. Here are some questions: 1. Which dev containers extension should be installed? I found multiple extensions. 2. Where do we find the "dev containers" command? 3. Are there any indications of whether the user is in a dev container or on their Nix machine? Does opening a new terminal run that terminal inside the dev container or inside the Nix machine? Sorry for being dumb; I have rarely used Visual Studio Code.
mngrif self-assigned this 2025-05-22 16:16:55 +00:00
mngrif commented 2025-05-22 16:17:04 +00:00
Member
Copy link

@brent.edwards we're maintaining a dev container because of our weird NixOS setup. it requires in-house builds of the extensions mentioned in this ticket due to a group ID conflict (a silly problem to have, indeed). we genuinely don't have the manpower to spare on figuring out how to tell vscode to use our builds.

also this is a function of vscode and not the OS so it's kindasorta out of our wheelhouse but is otherwise something that will be answered by careful perusal of vscode's documentation.

@brent.edwards we're maintaining __a__ dev container because of our weird NixOS setup. it requires in-house builds of the extensions mentioned in this ticket due to a group ID conflict (a silly problem to have, indeed). we genuinely don't have the manpower to spare on figuring out how to tell vscode to use our builds. also this is a function of vscode and not the OS so it's kindasorta out of our wheelhouse but is otherwise something that will be answered by careful perusal of vscode's documentation.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
longnight
frostmoon
envy_working
No results found.
Labels
Clear labels
  
Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.

  
Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
1 man-hours worth of work for an expert with no learning curve.

  
Points
13
13 man-hours worth of work for an expert with no learning curve.

  
Points
2
2 man-hours worth of work for an expert with no learning curve.

  
Points
21
21 man-hours worth of work for an expert with no learning curve.

  
Points
3
3 man-hours worth of work for an expert with no learning curve.

  
Points
34
34 man-hours worth of work for an expert with no learning curve.

  
Points
5
5 man-hours worth of work for an expert with no learning curve.

  
Points
55
55 man-hours worth of work for an expert with no learning curve.

  
Points
8
8 man-hours worth of work for an expert with no learning curve.

  
Points
88
88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
A ticket that represents the same content as an existing ticket.

  
State
In Progress
A ticket that is actively being developed.

  
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Bug
Something that doesnt work as intended.

  
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
An error or improvement needed in the documentation.

  
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
Some new functionality not present.

  
Type
Legendary
A type of Epic which will contain other Epics.

  
Type
Support
Someone needs help using the project.

  
Type
Task
A generic task that doesnt fit into the other type categories.

  
Type
Testing
Work exclusively focusing on fixing or expanding testing.

No labels
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
mngrif
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infrastructure/nixos-config#36
No description provided.