[BUG] Clear state does not clear error state

[Codewithpabitra]

Describe the bug
When after pasting a repo link user click generate , then it fails . So this is a big issue (I saw You are working on it) . But I found another one. after clicking clear button the input fields get clear but the error shown before does not go away. means the error state does not get clear. I have noticed on the deployed URL.

To Reproduce
Steps to reproduce the behavior:

1. Go to "try now" click on it
2. paste any repo url (public prefered) and click generate . If it fails see the error.
3. click clear button -> input fields get clear , but error remain same displayed. (NOT EXPECTED)

Expected behavior
After clicking "clear" the input fields as well as the error should gone away.

Environment Details

• OS/Environment: [e.g. Windows 11]
• Runtime/Version: [e.g. Node v20, Python 3.11, Docker]
• Browser (if UI bug): [e.g. Chrome 124]

Screenshots & Logs
after clicking "Clear" button

[github-actions]

👋 Hello @Codewithpabitra! Thanks for opening this issue and showing interest in contributing to the project.

Please sit back and relax a bit until this issue gets assigned to you. A maintainer will review it shortly.

In the meantime, feel free to check out our Contributing Guidelines. Happy coding! 🚀

[Codewithpabitra]

Hello , I would like to work on this issue . To solve this issue have to clear the error state only maybe with empty string.

Could you please assign it to me as the part of ssoc'26.
/assign ssoc

[abhro05]

@Codewithpabitra assigned to you!!

[abhro05]

@Codewithpabitra any update on your work?

[Codewithpabitra]

hello @abhro05 someone fixed this issue . he / she added setError(""); in the handleClear() function which now clear the error state ->

here

const handleClear = () => { setRepoUrl(""); setCustomInstructions(""); setMarkdownOutput(""); setJobPhase(''); setJobMessage(''); setJobProgress({ filesProcessed: 0, totalFiles: 0 }); setError(''); if (eventSourceRef.current) { eventSourceRef.current.close(); } };

therefore the issue can be closed now .