You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both commands below fail to show any difference and do not start at the step given as an argument. I looked through the database that the pilot uses, and it contains every single piece of output and input, steps, etc., in a nicely formatted pack of data. I'm confused as to why it is not working, or rather if I am misunderstanding the use of them, what is the function of these/why is what I thought it to be not a feature?
It would be beyond helpful if the database could simply move the steps that follow the step argument given in the initiation/resume to a separate table. This would allow for an alternate route if you want to revert to the now redacted steps and start anew from that step in the argument.
Either way, I'm super grateful for this project. It has helped me immensely, and I am thankful to everyone who put so much time and effort into making this amazing. β€οΈ
β When using: β step=1151 skip_until_dev_step=1151
β β The project should start at the specified step given in the argument. (...I think, hopefully?)
Actual Output
Note the bolded step arguments:
------------------ LOADING PROJECT ----------------------
ExApp(app_id=27fa92f1-cbe2-4925-882d-e927770ff76d)
--------------------------------------------------------------
START
? Did you make any changes to "ExApp" project files since last time you used Pythagora? no
β Project_description
β Architecture
β Environment_setup
β Development_planning
Starting development...
Implementing task #4: Implement real-time blah blah blah.
Starting task #4 implementation...
{
"relevant_files": [
"./server.js",
"./public/js/socket.js"
]
}
Saving file C:\Users\12166\Desktop\gpt-pilot-main\workspace\ExApp\.env
Saving file C:\Users\12166\Desktop\gpt-pilot-main\workspace\ExApp\package.json
Saving file C:\Users\12166\Desktop\gpt-pilot-main\workspace\ExApp\server.js
// many more
**Dev step 1156**
Additional Information
Notice that despite input of "step=1151" and "skip_until_dev_step=1151", Pilot started at "Dev step 1156".
Each iteration that I try again, it begins one more step advanced from the previous start.
OS: Windows 10
Python Version: 3.8.5
Database: SQLite
The text was updated successfully, but these errors were encountered:
Additionally, a way to interrupt current execution as it stands, with custom commands to roll back a step, or multiple, or edit the current task if Pilot is moving off course, would be double amazing.
techjeylabs
changed the title
When attempting to use 'skip_until_dev_step' or just 'step' β No change. π’ [Bug]:
[Bug]: When attempting to use 'skip_until_dev_step' or just 'step' β No change. π’ [Bug]:
May 15, 2024
Version
Command-line (Python) version
Operating System
Windows 10
What happened?
Description
Both commands below fail to show any difference and do not start at the step given as an argument. I looked through the database that the pilot uses, and it contains every single piece of output and input, steps, etc., in a nicely formatted pack of data. I'm confused as to why it is not working, or rather if I am misunderstanding the use of them, what is the function of these/why is what I thought it to be not a feature?
It would be beyond helpful if the database could simply move the steps that follow the step argument given in the initiation/resume to a separate table. This would allow for an alternate route if you want to revert to the now redacted steps and start anew from that step in the argument.
Either way, I'm super grateful for this project. It has helped me immensely, and I am thankful to everyone who put so much time and effort into making this amazing. β€οΈ
Commands Executed
Expected Behavior
β When using: β
step=1151
skip_until_dev_step=1151
β β The project should start at the specified step given in the argument. (...I think, hopefully?)
Actual Output
Note the bolded step arguments:
Additional Information
The text was updated successfully, but these errors were encountered: