feat: upload folder to workbench #31
Conversation
- Added new PanelHeaderFileUpload component - PanelHeaderFileUpload added to Workbench header section - Upload folder actions are added to workbench store
|
Hey, so I just tested this on my fork, and it uploads the files but the are not displayed in the workbench...I also get a broken pipe error when I do so: ✘ [ERROR] workerd/server/server.c++:3360: error: Uncaught exception: kj/async-io-unix.c++:778: disconnected: remote.worker_do_not_log; Request failed due to internal error stack: ✘ [ERROR] workerd/server/server.c++:3155: error: kj::getCaughtExceptionAsKj() = kj/async-io-unix.c++:186: disconnected: ::write(fd, buffer.begin(), buffer.size()): Broken pipe stack: I would really like to see this up and running. The biggest downside to Bolt.new is that it doesn't work all that well with existing codebases, so the ability to drop in a zip and have it on the workbench is a start in the right direction. |
That's sounds interesting because it's working fine on my side. Which browser are you using? Thanks in advance. |
|
so I just tried in Firefox and Chrome both have the same errors. I have attached to console log for your review. console-export-2024-10-23_10-20-6.txt
|
|
something else I have noticed, and this may be out of scope of this issue, when you first start Bolt there is no way to open the workbench until after you have started a conversation, nor is there a way start the conversation off with a file or folder. Probably out of scope for this particular issue but given what you are trying to do I thought I would see what your thoughts were. |
|
@r3d91ll
If you provide your re-production steps for the error, I'll try on my side as well. Thanks in advance. |
|
@cepicdalim This is awesome, thank you so much! I'll wait for @r3d91ll to get back with the issues he is running into. Otherwise I can do some testing with this soon before merging into main! I hope to add this in soon! How hard do you think it would be to make the AI aware of the changes without having to manually describe it in the next prompt? That would make this even better! |
that is the million dollar question right there...to my thinking we will need more than just some prompt engineering on the backend. I think we will find that there are a limited number of vanilla models out there that will have the necessary fine-tune training to use this framework effectively. I suspect it will take a model fine-tuned on this framework to use it effectively. However if we can find a model that works say 60% of the time then we should be able to generate enough training data to effectively fine-tune train a model. |
what do you mean by hydration issue? |
|
…-support # Conflicts: # app/lib/stores/workbench.ts
cepicdalim
changed the title
cepicdalim
changed the title
|
@r3d91ll, @coleam00 And the errors in your console not really related with this PR, I tried in master and got the same error as you got. For reproduction
|
|
Hi. can you tell me how to (brand new to git) get this branch....I have followed the instructions for the main anyllm only. But this is a feature I need badly. |
This is not a branch but a pull request from other fork. So you can check out the fork that contains this particular feature from |
|
Thank you. Can you give me the command I can type at the bash command prompt that will make me have this feature? |
|
@cepicdalim Thanks for the awesome feature addition. When tried base folder is uploaded in a nested directory. And ai is writing in root path.
Due to nested structure , ai is writing a new file at base folder |
|
No mine doesn't have that option |
|
|
Sorry for no reviews, I want to get to this, may be today |
|
Ok, got to review. I think this needs to be done differently a bit. There is useChat that connects and manages messages from AI When they change this code is run. }, [messages, isLoading, parseMessages]); It calls parseMessages + stores them in history. And chat also renders them. My proposal is to use that. When user uploads files we create new message probably use setMessages method from useChat AI will be aware, UI will update, WebContainer too, all things will trigger and so on. |
|
This pull request has been marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days. |
github-actions
bot
added
the
stale
github-actions
bot
removed
the
stale
|
AS folder import was merged closing this |
Use Case
Now users are able to upload their local folders to active workbench.
Changes
Way of Work
Negative Aspects
The AI won't be able to aware of changes. It make sense to give brief of the changes as a message behind the scene. Let's discuss it under an epic.