Spaces:
Running
on
Zero
Running
on
Zero
sf
Browse files- controllers/{chats/OpenInterpreter.py → Chat/Chat.py} +0 -0
- controllers/{chat → Chat}/__init__.py +0 -0
- controllers/{chat/Chat.py → OpenInterpreter/OpenInterpreter.py} +2 -1
- controllers/{chats → OpenInterpreter}/__init__.py +0 -0
- controllers/{postg → PostGres}/.gpteng/memory/logs/all_output.txt +0 -0
- controllers/{postg → PostGres}/.gpteng/memory/logs/gen_entrypoint_chat.txt +0 -0
- controllers/{postg/DataBase.py → PostGres/PostGres.py} +0 -0
- controllers/{postg → PostGres}/__init__.py +0 -0
- controllers/{postg → PostGres}/database.py +0 -0
- controllers/{postg → PostGres}/models/ride.py +0 -0
- controllers/{postg → PostGres}/prompt +0 -0
- controllers/{postg → PostGres}/requirements.txt +0 -0
- controllers/{postg → PostGres}/run.sh +0 -0
- controllers/test/.gpteng/memory/logs/all_output.txt +0 -146
- controllers/test/.gpteng/memory/logs/gen_entrypoint_chat.txt +0 -79
- mysite/gradio/gradio_config.py +1 -1
- routers/ai/prompt +1 -1
controllers/{chats/OpenInterpreter.py → Chat/Chat.py}
RENAMED
File without changes
|
controllers/{chat → Chat}/__init__.py
RENAMED
File without changes
|
controllers/{chat/Chat.py → OpenInterpreter/OpenInterpreter.py}
RENAMED
@@ -67,8 +67,9 @@ def chat_with_interpreter(
|
|
67 |
): # , openai_api_key):
|
68 |
# Set the API key for the interpreter
|
69 |
# interpreter.llm.api_key = openai_api_key
|
70 |
-
|
71 |
if message == "reset":
|
|
|
72 |
interpreter.reset()
|
73 |
return "Interpreter reset", history
|
74 |
full_response = ""
|
|
|
67 |
): # , openai_api_key):
|
68 |
# Set the API key for the interpreter
|
69 |
# interpreter.llm.api_key = openai_api_key
|
70 |
+
|
71 |
if message == "reset":
|
72 |
+
interpreter.messages = []
|
73 |
interpreter.reset()
|
74 |
return "Interpreter reset", history
|
75 |
full_response = ""
|
controllers/{chats → OpenInterpreter}/__init__.py
RENAMED
File without changes
|
controllers/{postg → PostGres}/.gpteng/memory/logs/all_output.txt
RENAMED
File without changes
|
controllers/{postg → PostGres}/.gpteng/memory/logs/gen_entrypoint_chat.txt
RENAMED
File without changes
|
controllers/{postg/DataBase.py → PostGres/PostGres.py}
RENAMED
File without changes
|
controllers/{postg → PostGres}/__init__.py
RENAMED
File without changes
|
controllers/{postg → PostGres}/database.py
RENAMED
File without changes
|
controllers/{postg → PostGres}/models/ride.py
RENAMED
File without changes
|
controllers/{postg → PostGres}/prompt
RENAMED
File without changes
|
controllers/{postg → PostGres}/requirements.txt
RENAMED
File without changes
|
controllers/{postg → PostGres}/run.sh
RENAMED
File without changes
|
controllers/test/.gpteng/memory/logs/all_output.txt
DELETED
@@ -1,146 +0,0 @@
|
|
1 |
-
|
2 |
-
2024-06-06T08:15:25.594683
|
3 |
-
================================ System Message ================================
|
4 |
-
|
5 |
-
You will get instructions for code to write.
|
6 |
-
You will write a very long answer. Make sure that every detail of the architecture is, in the end, implemented as code.
|
7 |
-
Think step by step and reason yourself to the correct decisions to make sure we get it right.
|
8 |
-
First lay out the names of the core classes, functions, methods that will be necessary, As well as a quick comment on their purpose.
|
9 |
-
|
10 |
-
You will output the content of each file necessary to achieve the goal, including ALL code.
|
11 |
-
Represent files like so:
|
12 |
-
|
13 |
-
FILENAME
|
14 |
-
```
|
15 |
-
CODE
|
16 |
-
```
|
17 |
-
|
18 |
-
The following tokens must be replaced like so:
|
19 |
-
FILENAME is the lowercase combined path and file name including the file extension
|
20 |
-
CODE is the code in the file
|
21 |
-
|
22 |
-
Example representation of a file:
|
23 |
-
|
24 |
-
src/hello_world.py
|
25 |
-
```
|
26 |
-
print("Hello World")
|
27 |
-
```
|
28 |
-
|
29 |
-
Do not comment on what every file does. Please note that the code should be fully functional. No placeholders.
|
30 |
-
|
31 |
-
|
32 |
-
You will start with the "entrypoint" file, then go to the ones that are imported by that file, and so on.
|
33 |
-
Please note that the code should be fully functional. No placeholders.
|
34 |
-
|
35 |
-
Follow a language and framework appropriate best practice file naming convention.
|
36 |
-
Make sure that files contain all imports, types etc. The code should be fully functional. Make sure that code in different files are compatible with each other.
|
37 |
-
Ensure to implement all code, if you are unsure, write a plausible implementation.
|
38 |
-
Include module dependency or package manager dependency definition file.
|
39 |
-
Before you finish, double check that all parts of the architecture is present in the files.
|
40 |
-
|
41 |
-
When you are done, write finish with "this concludes a fully working implementation".
|
42 |
-
|
43 |
-
Useful to know:
|
44 |
-
Almost always put different classes in different files.
|
45 |
-
Always use the programming language the user asks for.
|
46 |
-
For Python, you always create an appropriate requirements.txt file.
|
47 |
-
For NodeJS, you always create an appropriate package.json file.
|
48 |
-
Always add a comment briefly describing the purpose of the function definition.
|
49 |
-
Add comments explaining very complex bits of logic.
|
50 |
-
Always follow the best practices for the requested languages for folder/file structure and how to package the project.
|
51 |
-
|
52 |
-
|
53 |
-
Python toolbelt preferences:
|
54 |
-
- pytest
|
55 |
-
- dataclasses
|
56 |
-
|
57 |
-
|
58 |
-
================================ Human Message =================================
|
59 |
-
|
60 |
-
Request: y
|
61 |
-
|
62 |
-
================================== Ai Message ==================================
|
63 |
-
|
64 |
-
I'm happy to help! However, I need more information about the project you want me to implement. Could you please provide more details about the project, such as:
|
65 |
-
|
66 |
-
* What is the project about? (e.g., web application, game, data analysis tool)
|
67 |
-
* What features does it need to have?
|
68 |
-
* Are there any specific technologies or frameworks you want me to use?
|
69 |
-
* Are there any specific requirements or constraints I should be aware of?
|
70 |
-
|
71 |
-
Once I have a better understanding of your project, I can start designing the architecture and implementing the code.
|
72 |
-
|
73 |
-
Please provide more information, and I'll be happy to help!
|
74 |
-
|
75 |
-
2024-06-06T08:16:10.259654
|
76 |
-
================================ System Message ================================
|
77 |
-
|
78 |
-
You will get instructions for code to write.
|
79 |
-
You will write a very long answer. Make sure that every detail of the architecture is, in the end, implemented as code.
|
80 |
-
Think step by step and reason yourself to the correct decisions to make sure we get it right.
|
81 |
-
First lay out the names of the core classes, functions, methods that will be necessary, As well as a quick comment on their purpose.
|
82 |
-
|
83 |
-
You will output the content of each file necessary to achieve the goal, including ALL code.
|
84 |
-
Represent files like so:
|
85 |
-
|
86 |
-
FILENAME
|
87 |
-
```
|
88 |
-
CODE
|
89 |
-
```
|
90 |
-
|
91 |
-
The following tokens must be replaced like so:
|
92 |
-
FILENAME is the lowercase combined path and file name including the file extension
|
93 |
-
CODE is the code in the file
|
94 |
-
|
95 |
-
Example representation of a file:
|
96 |
-
|
97 |
-
src/hello_world.py
|
98 |
-
```
|
99 |
-
print("Hello World")
|
100 |
-
```
|
101 |
-
|
102 |
-
Do not comment on what every file does. Please note that the code should be fully functional. No placeholders.
|
103 |
-
|
104 |
-
|
105 |
-
You will start with the "entrypoint" file, then go to the ones that are imported by that file, and so on.
|
106 |
-
Please note that the code should be fully functional. No placeholders.
|
107 |
-
|
108 |
-
Follow a language and framework appropriate best practice file naming convention.
|
109 |
-
Make sure that files contain all imports, types etc. The code should be fully functional. Make sure that code in different files are compatible with each other.
|
110 |
-
Ensure to implement all code, if you are unsure, write a plausible implementation.
|
111 |
-
Include module dependency or package manager dependency definition file.
|
112 |
-
Before you finish, double check that all parts of the architecture is present in the files.
|
113 |
-
|
114 |
-
When you are done, write finish with "this concludes a fully working implementation".
|
115 |
-
|
116 |
-
Useful to know:
|
117 |
-
Almost always put different classes in different files.
|
118 |
-
Always use the programming language the user asks for.
|
119 |
-
For Python, you always create an appropriate requirements.txt file.
|
120 |
-
For NodeJS, you always create an appropriate package.json file.
|
121 |
-
Always add a comment briefly describing the purpose of the function definition.
|
122 |
-
Add comments explaining very complex bits of logic.
|
123 |
-
Always follow the best practices for the requested languages for folder/file structure and how to package the project.
|
124 |
-
|
125 |
-
|
126 |
-
Python toolbelt preferences:
|
127 |
-
- pytest
|
128 |
-
- dataclasses
|
129 |
-
|
130 |
-
|
131 |
-
================================ Human Message =================================
|
132 |
-
|
133 |
-
Request: y
|
134 |
-
|
135 |
-
================================== Ai Message ==================================
|
136 |
-
|
137 |
-
I'm happy to help! However, I need more information about the project you want me to implement. Could you please provide more details about the project, such as:
|
138 |
-
|
139 |
-
* What is the project about? (e.g., web application, game, chatbot, etc.)
|
140 |
-
* What features do you want to implement?
|
141 |
-
* Are there any specific technologies or frameworks you want to use?
|
142 |
-
* Are there any specific requirements or constraints I should be aware of?
|
143 |
-
|
144 |
-
Once I have a better understanding of your project, I can start implementing it in Python.
|
145 |
-
|
146 |
-
Please provide more information, and I'll be happy to help!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
controllers/test/.gpteng/memory/logs/gen_entrypoint_chat.txt
DELETED
@@ -1,79 +0,0 @@
|
|
1 |
-
|
2 |
-
2024-06-06T08:15:26.181845
|
3 |
-
================================ System Message ================================
|
4 |
-
|
5 |
-
You will get information about a codebase that is currently on disk in the current folder.
|
6 |
-
The user will ask you to write a script that runs the code in a specific way.
|
7 |
-
You will answer with code blocks that include all the necessary terminal commands.
|
8 |
-
Do not install globally. Do not use sudo.
|
9 |
-
Do not explain the code, just give the commands.
|
10 |
-
Do not use placeholders, use example values (like . for a folder argument) if necessary.
|
11 |
-
|
12 |
-
|
13 |
-
================================ Human Message =================================
|
14 |
-
|
15 |
-
|
16 |
-
Make a unix script that
|
17 |
-
a) installs dependencies
|
18 |
-
b) runs all necessary parts of the codebase (in parallel if necessary)
|
19 |
-
|
20 |
-
Information about the codebase:
|
21 |
-
|
22 |
-
```
|
23 |
-
```
|
24 |
-
|
25 |
-
================================== Ai Message ==================================
|
26 |
-
|
27 |
-
Here is a Unix script that installs dependencies and runs the codebase:
|
28 |
-
```
|
29 |
-
#!/bin/bash
|
30 |
-
|
31 |
-
# Install dependencies
|
32 |
-
pip install -r requirements.txt
|
33 |
-
|
34 |
-
# Run the codebase
|
35 |
-
python -m main &
|
36 |
-
python -m worker &
|
37 |
-
python -m api
|
38 |
-
|
39 |
-
wait
|
40 |
-
```
|
41 |
-
Note: This script assumes that the codebase has a `requirements.txt` file for dependencies, a `main.py` file as the main entry point, a `worker.py` file as a worker process, and an `api.py` file as the API server. Adjust the script according to your actual codebase structure.
|
42 |
-
|
43 |
-
2024-06-06T08:16:10.822878
|
44 |
-
================================ System Message ================================
|
45 |
-
|
46 |
-
You will get information about a codebase that is currently on disk in the current folder.
|
47 |
-
The user will ask you to write a script that runs the code in a specific way.
|
48 |
-
You will answer with code blocks that include all the necessary terminal commands.
|
49 |
-
Do not install globally. Do not use sudo.
|
50 |
-
Do not explain the code, just give the commands.
|
51 |
-
Do not use placeholders, use example values (like . for a folder argument) if necessary.
|
52 |
-
|
53 |
-
|
54 |
-
================================ Human Message =================================
|
55 |
-
|
56 |
-
|
57 |
-
Make a unix script that
|
58 |
-
a) installs dependencies
|
59 |
-
b) runs all necessary parts of the codebase (in parallel if necessary)
|
60 |
-
|
61 |
-
Information about the codebase:
|
62 |
-
|
63 |
-
```
|
64 |
-
```
|
65 |
-
|
66 |
-
================================== Ai Message ==================================
|
67 |
-
|
68 |
-
Here is a Unix script that installs dependencies and runs the codebase:
|
69 |
-
```
|
70 |
-
#!/bin/bash
|
71 |
-
|
72 |
-
# Install dependencies
|
73 |
-
pip install -r requirements.txt
|
74 |
-
|
75 |
-
# Run the codebase
|
76 |
-
python -m main & python -m worker &
|
77 |
-
python -m api
|
78 |
-
```
|
79 |
-
Note: This script assumes that the codebase has a `requirements.txt` file for dependencies, a `main.py` file as the main entry point, a `worker.py` file that can be run in parallel, and an `api.py` file that depends on the other two. Adjust the script according to your actual codebase structure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mysite/gradio/gradio_config.py
CHANGED
@@ -50,7 +50,7 @@ def setup_gradio_interfaces():
|
|
50 |
)
|
51 |
|
52 |
default_interfaces = [democs]#,demo]
|
53 |
-
default_names = ["仕様書から作成","
|
54 |
|
55 |
gradio_interfaces, gradio_names = include_gradio_interfaces()
|
56 |
|
|
|
50 |
)
|
51 |
|
52 |
default_interfaces = [democs]#,demo]
|
53 |
+
default_names = ["仕様書から作成","OpenInterpreter","Chat","DataBase"]#"demo"]
|
54 |
|
55 |
gradio_interfaces, gradio_names = include_gradio_interfaces()
|
56 |
|
routers/ai/prompt
CHANGED
@@ -1 +1 @@
|
|
1 |
-
|
|
|
1 |
+
y
|