-
-
Notifications
You must be signed in to change notification settings - Fork 136
System.err: java.io.IOException: Broken pipe ("Sync operation is taking too long") #1241
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
Comments
I notice this issue may be similar and/or related to this one: NativeScript/nativescript-cli#4227 |
Upon further investigation, I discovered the typescript version I was using was one version too high for the latest release of Angular. I also found that the nativescript version 5.2.0-next-2018-12-20-172434-01 was not compatible with some plugins. I downgraded typescript to 3.1.1 and nativescript to 5.1, and have successfully saved code changes without livesync stopping. Before closing this issue, I'd like to test some more. |
Well. It seems I'm back to losing the connection: After further changes and rebuild I received the following error: [18-12-26 08:21:47.021] Error detected during LiveSync on J6NPCV0026363FH for D:\FasterTableApp\FasterTable. Error: Socket Error: |
Back on the emulator, livesync appears to work as long code changes are minor. For example, changing code as to how an event is handled caused no error. However, after adding a component or an element, for example, I just added a @ViewChild and ElementRef requiring the imports in the component to change resulted in "Sync operation in progress..." about six times, and then failure "Sync operation is taking too long." |
I have simplified and added this issue to the Nativescript Angular issues repository. |
Uh oh!
There was an error while loading. Please reload this page.
Environment
√ Component nativescript has 5.1.0 version and is up to date.
√ Component tns-core-modules has 5.2.0-next-2018-12-20-172434-01 version and is up to date.
√ Component tns-android has 5.2.0-2018-12-20-092429-01 version and is up to date.
Describe the bug
When using "tns run android" after making a change to the project, livesync causes errors both on an emulator and in an android device. Although the errors are different, they appear to be related. After livesync on a device, the ECONNREFUSED error occurs. On the emulator, I receive:
"System.err: java.io.IOException: Broken pipe
System.err: at android.net.LocalSocketImpl.writeba_native(Native Method)
System.err: at android.net.LocalSocketImpl.access$500(LocalSocketImpl.java:36)
System.err: at android.net.LocalSocketImpl$SocketOutputStream.write(LocalSocketImpl.java:144)
System.err: at android.net.LocalSocketImpl$SocketOutputStream.write(LocalSocketImpl.java:131)
System.err: at com.tns.NativeScriptSyncServiceSocketImpl$LiveSyncWorker.closeWithError(NativeScriptSyncServiceSocketImpl.java:424)
System.err: at com.tns.NativeScriptSyncServiceSocketImpl$LiveSyncWorker.run(NativeScriptSyncServiceSocketImpl.java:187)
System.err: at java.lang.Thread.run(Thread.java:764)"
Both cause webpack to stop running.
To Reproduce
I do not know how to reproduce this error.
Expected behavior
Livesync should work to refresh the project.
Sample project
This is a very large project, and would be difficult to post to the playground.
Additional context
The text was updated successfully, but these errors were encountered: