-
Notifications
You must be signed in to change notification settings - Fork 11.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get a response in interactive mode #1423
Comments
Hi. I also encountered this error(in Windows), for temporal solution i use main.exe from Releases, it work fine. |
The same here, using Win10 64bit, Codeblocks, TDM64-gcc, never had a problem till last severe changes- using last format, after return main freezes, control c works as described before. Maine.exe from Release works as expected. |
Dirty patch for issue (#1423) and (#1432) Line numbers refer to file main.cpp version 13c351a and 79b2d5b ========
|
Less dirty and faster patch for issue (#1423) and (#1432) Line numbers refer to file common.cpp version 63d2046 525 HANDLE hConIn = GetStdHandle(STD_INPUT_HANDLE); So comment lines 531 and 532 out. |
I think this is related to the Windows version of GCC (mingw?). When built with the MS or Intel compilers the code works as expected. I'm working on a a fix that just deals with the Windows key events when in Windows. Windows already got its own If anyone want to open a bug report with them, here's the code that should work, but gets stuck on
|
Can you try out #1462 and verify that it fixes the problem for you? If you don't know how to checkout a pull request you can apply this patch with |
Hello, patch #1462 works with code::blocks and TDM64-gcc. Thank you |
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
I am expecting AI responses to my responses, allowing for a 2-way conversation.
Current Behavior
Once it's my turn to provide a prompt and I press enter, the CPU will reach around 30% and then never generate a response at any point, no longer how long it's left to run. I'm always forced to sigint using Ctrl+C in order to terminate llama.cpp
I've also tried it with 7B, but the result is sadly still the same.
Environment and Context
Please provide detailed information about your computer setup. This is important in case the issue is not reproducible except for under certain specific conditions.
Intel(R) Core(TM) i7-6820HK CPU @ 2.70GHz with 32GB of RAM at 2400MHz
Windows 10 v1909
Steps to Reproduce
run parameters as per usual, attempt to respond, and simply wait. --keep is not necessary, that was merely the result of my last test run to see if it changed anything.
Failure Logs
The text was updated successfully, but these errors were encountered: