gruntjs - compass socket hangup with grunt serve -

-

I was running grunt-contrib-compass@0.6.0 and it was aborted by error: 

  node_module / grunt-content-comp / node_module / tmp / lib / tmp.js: throwing 261; ^ Error: TCP on Socket.emit (events.js: 95: 17) at Socket.Sat Cloessiston (http: js: 1526: 23). On the Close (NET JS: 465: 12)

I have upgraded to grunt-contrib-compass@1.0.1 and now it exits now, but it is the following errors / Generate warnings (this does not come out when it happens, though it is fatal) 

  Fatal error: dangling the socket Fatal error: The socket is hanging

Which I can only assume is the problem with better error handling than throwing this error Area is a way to get better information? This is the compass part of my grunted file 

  compass: {option: {sassDir: '<% = yeoman.app% & gt; / Styles ', cssDir:' .mp / styles ', Generated Images DIR:' .mpp / image / generate ', image:' <% = yeoman.app% & gt; / Images ', javascriptsDir:' & lt;% = yeoman.app% & gt; / Scripts ', FontDeir:' & lt; '/ Images', httpGeneratedImagesPath: '/ images / generated', httpFontsPath: 'Styles / Fonts', relativeAssets: false, trace: true}, dist: {}, server: {options: {debugInfo: true}}}, / Code>


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more