package.cache.lock: openBinaryFile: resource busy (file is locked)

After this message sometimes hie stops working. Only "Loading..." shows up on hover.
Sometimes a notification panel is shown in  the lower right of the window, containing this message. But hie works albeit not fully functional. Some hover panels don't open afterwards.
hie version: Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
The hie log is as follows:
2019-12-01 15:27:59.6526704 [ThreadId 3] - run entered for hie-wrapper(hie-wrapper) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 15:27:59.6526704 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 15:27:59.6526704 [ThreadId 3] - Operating system:mingw32
2019-12-01 15:28:00.2930678 [ThreadId 3] - Cradle directory:C:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 15:28:00.2930678 [ThreadId 3] - Using stack GHC version
2019-12-01 15:28:01.0472908 [ThreadId 3] - Project GHC version:8.6.5
2019-12-01 15:28:01.0472908 [ThreadId 3] - hie exe candidates :["hie-8.6.5.exe","hie-8.6.exe","hie.exe"]
2019-12-01 15:28:01.0492623 [ThreadId 3] - found hie exe at:C:\Users\zmtemp\AppData\Roaming\local\bin\hie-8.6.5.exe
2019-12-01 15:28:01.0492623 [ThreadId 3] - args:["--lsp"]
2019-12-01 15:28:01.0502622 [ThreadId 3] - launching ....

2019-12-01 15:28:01.4565329 [ThreadId 3] - Using stack GHC version
2019-12-01 15:28:01.8933973 [ThreadId 3] - Run entered for HIE(hie-8.6.5.exe) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 15:28:01.8933973 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 15:28:01.8933973 [ThreadId 3] - args:["--lsp"]
2019-12-01 15:28:03.5199904 [ThreadId 9] - Using stack GHC version
Using hie version: Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
Using hoogle db at: C:\Users\zmtemp\AppData\Roaming\hoogle\default-haskell-5.0.17.hoo
[Error - 15:43:04] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
[Error - 15:43:42] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
[Error - 15:43:42] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
[Error - 16:00:58] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
[Error - 16:01:43] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
[Error - 16:02:24] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])
C:\\Users\zmtemp\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\lib\package.conf.d\package.cache.lock: openBinaryFile: resource busy (file is locked)

Hi, there are two elements in the log that are not normal:
[Error - 15:43:04] haskell-lsp:no handler for. Object (fromList [("jsonrpc",String "2.0"),("params",Object (fromList [("value",String "off")])),("method",String "$/setTraceNotification")])

and
C:\\Users\zmtemp\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\lib\package.conf.d\package.cache.lock: openBinaryFile: resource busy (file is locked)

maybe one is caused by the other.
how you got hie? if building from source, which commit?
what version of the haskell lang server extension are you using (latest is 0.31)?
The file mentioned in the log is effectively locked after the hie execution (f.e. you can delete it normally)?

 I have just fetched the changes but I decided not to compile because the changes are insignificant or irrelevant.
Haskell lang server version is the latest one: 0.0.31.
I'll try to delete the file in question when the message will appear again.

@jneira same situation again and I have just been able to delete package.cache.lock. The editor shows "Loading..." only on hover.
hie-8.6.5.exe and hie-wrapper.exe are being listed in the task list, but no CPU usage. May be restarting the hie would have been handy in these cases, preventing to rerun the editor frequently.
This time the hie log is this:
2019-12-01 19:37:33.5972246 [ThreadId 3] - run entered for hie-wrapper(hie-wrapper) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 19:37:33.5997636 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:33.600688 [ThreadId 3] - Operating system:mingw32
2019-12-01 19:37:34.8872551 [ThreadId 3] - Cradle directory:C:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:34.8881577 [ThreadId 3] - Using stack GHC version
2019-12-01 19:37:35.5334821 [ThreadId 3] - Project GHC version:8.6.5
2019-12-01 19:37:35.5337774 [ThreadId 3] - hie exe candidates :["hie-8.6.5.exe","hie-8.6.exe","hie.exe"]
2019-12-01 19:37:35.5337774 [ThreadId 3] - found hie exe at:C:\Users\zmtemp\AppData\Roaming\local\bin\hie-8.6.5.exe
2019-12-01 19:37:35.5347753 [ThreadId 3] - args:["--lsp"]
2019-12-01 19:37:35.5347753 [ThreadId 3] - launching ....

2019-12-01 19:37:35.5545484 [ThreadId 3] - Using stack GHC version
2019-12-01 19:37:36.146784 [ThreadId 3] - Run entered for HIE(hie-8.6.5.exe) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 19:37:36.146784 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:36.1477831 [ThreadId 3] - args:["--lsp"]
2019-12-01 19:37:36.5039207 [ThreadId 9] - Using stack GHC version
Using hie version: Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
Using hoogle db at: C:\Users\zmtemp\AppData\Roaming\hoogle\default-haskell-5.0.17.hoo
C:\\Users\zmtemp\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\lib\package.conf.d\package.cache.lock: openBinaryFile: resource busy (file is locked)

@jneira I have killed the hie-wrapper.exe. hie-8.6.5.exe is also killed automatically and both restarted immediately. After that the editor functionality reestablished.
Log follows:
2019-12-01 19:37:33.5972246 [ThreadId 3] - run entered for hie-wrapper(hie-wrapper) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 19:37:33.5997636 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:33.600688 [ThreadId 3] - Operating system:mingw32
2019-12-01 19:37:34.8872551 [ThreadId 3] - Cradle directory:C:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:34.8881577 [ThreadId 3] - Using stack GHC version
2019-12-01 19:37:35.5334821 [ThreadId 3] - Project GHC version:8.6.5
2019-12-01 19:37:35.5337774 [ThreadId 3] - hie exe candidates :["hie-8.6.5.exe","hie-8.6.exe","hie.exe"]
2019-12-01 19:37:35.5337774 [ThreadId 3] - found hie exe at:C:\Users\zmtemp\AppData\Roaming\local\bin\hie-8.6.5.exe
2019-12-01 19:37:35.5347753 [ThreadId 3] - args:["--lsp"]
2019-12-01 19:37:35.5347753 [ThreadId 3] - launching ....

2019-12-01 19:37:35.5545484 [ThreadId 3] - Using stack GHC version
2019-12-01 19:37:36.146784 [ThreadId 3] - Run entered for HIE(hie-8.6.5.exe) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 19:37:36.146784 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 19:37:36.1477831 [ThreadId 3] - args:["--lsp"]
2019-12-01 19:37:36.5039207 [ThreadId 9] - Using stack GHC version
Using hie version: Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
Using hoogle db at: C:\Users\zmtemp\AppData\Roaming\hoogle\default-haskell-5.0.17.hoo
C:\\Users\zmtemp\AppData\Local\Programs\stack\x86_64-windows\ghc-8.6.5\lib\package.conf.d\package.cache.lock: openBinaryFile: resource busy (file is locked)
[Info  - 20:46:37] Connection to server got closed. Server will restart.
[Error - 20:46:37] Request textDocument/documentSymbol failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/documentHighlight failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/formatting failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
[Error - 20:46:37] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:36201)
	at Object.dispose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90254)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:90429)
	at D.handleConnectionClosed (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:157:34664)
	at t (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:88578)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at $ (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:28132)
	at invoke (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230177)
	at n.fire (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:230907)
	at t.StreamMessageWriter.fireClose (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252458)
	at Socket.<anonymous> (c:\Users\zmtemp\.vscode-insiders\extensions\alanz.vscode-hie-server-0.0.31\dist\extension.js:1:252825)
	at Socket.emit (events.js:200:13)
	at Pipe.<anonymous> (net.js:586:12)
2019-12-01 20:46:38.3751534 [ThreadId 3] - run entered for hie-wrapper(hie-wrapper) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 20:46:38.3811134 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 20:46:38.3811134 [ThreadId 3] - Operating system:mingw32
2019-12-01 20:46:39.8954898 [ThreadId 3] - Cradle directory:C:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 20:46:39.8965407 [ThreadId 3] - Using stack GHC version
2019-12-01 20:46:40.7478971 [ThreadId 3] - Project GHC version:8.6.5
2019-12-01 20:46:40.748895 [ThreadId 3] - hie exe candidates :["hie-8.6.5.exe","hie-8.6.exe","hie.exe"]
2019-12-01 20:46:40.7498923 [ThreadId 3] - found hie exe at:C:\Users\zmtemp\AppData\Roaming\local\bin\hie-8.6.5.exe
2019-12-01 20:46:40.7498923 [ThreadId 3] - args:["--lsp"]
2019-12-01 20:46:40.7515372 [ThreadId 3] - launching ....

2019-12-01 20:46:40.7877558 [ThreadId 3] - Using stack GHC version
2019-12-01 20:46:41.6859842 [ThreadId 3] - Run entered for HIE(hie-8.6.5.exe) Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
2019-12-01 20:46:41.6869851 [ThreadId 3] - Current directory:c:\Users\zmtemp\Desktop\haskell\advent-of-code
2019-12-01 20:46:41.6869851 [ThreadId 3] - args:["--lsp"]
2019-12-01 20:46:41.7358986 [ThreadId 9] - Using stack GHC version
Using hie version: Version <IP_ADDRESS> (3112 commits) x86_64 ghc-8.6.5
Using hoogle db at: C:\Users\zmtemp\AppData\Roaming\hoogle\default-haskell-5.0.17.hoo

Hmm, ok, could you set the log more verbose and try again, sharing the output?, You can do it setting "languageServerHaskell.trace.server": "verbose" in the extension settings
I assume you can build the project with stack build in a console with no problem.

Yes I can build the project in console.
I changed the log output to verbose and since then hie (or haskell language server extension) didn't stop any more. May be the problem is something related to timing.
You can download the last verbose log output file from http://www.adyazilim.com.tr/upload/vscode-hie/vscode-hie-log.zip

I think this is a bug in cabal-install fixed by https://github.com/haskell/hackage-security/pull/230

@MuratOzsoyler as it is not reproduced consistently and depends on a upstream fix i think we could close this one. Feel free to reopen if you hit the problem again


The plugin is not retrying on specific errors and dropping the data on error 400

(check apply)

[x] read the contribution guideline
[ ] (optional) already reported 3rd party upstream repository or mailing list if you use k8s addon or helm charts.

Steps to replicate
He had a case that the  max open shards had been reached in Openeasrch so fluentd was getting an error
Error:
[warn]: #0 send an error event to @ERROR: error_class=Fluent::Plugin::OpenSearchErrorHandler::OpenSearchError error="400 - Rejected by OpenSearch [error type]: illegal_argument_exception [reason]: 'Validation Failed: 1: this action would add [2] total shards, but this cluster currently has [2999]/[3000] maximum shards open;'"

The error is ok and expected, but we did not expect to lose the data.
Once we increased the maximum number of open shards in opensearch the old logs were never being pushed.
Looks like the fluentd is not retrying on error 400 and dropping data.
We want to not lose the data due to some temporary misconfiguration on the Opensearch or if there is some limit being reached.
Configuration
<match **>
  @log_level info
  @type opensearch
  host "#{ENV['OPENSEARCH_URL']}"
  port 443
  user "#{ENV['OPENSEARCH_USERNAME']}"
  password "#{ENV['OPENSEARCH_FLUENTD_PASSWORD']}"
  include_timestamp true
  scheme https
  ssl_verify false
  ssl_version TLSv1_2

  id_key _hash
  index_date_pattern "now/d"
  target_index_key target_index
  index_name xxxxxx
  templates {"fluentd-logs-template": "/opt/bitnami/fluentd/conf/template.conf"}
  reload_connections false
  reconnect_on_error true
  reload_on_failure true
  log_os_400_reason true
  bulk_message_request_threshold 20m
  tag_key fluentd
  request_timeout 15s

  <buffer>
    @type file
    path /opt/bitnami/fluentd/logs/buffers/
    flush_thread_count 2
    flush_interval 10s
    chunk_limit_size 160m
    total_limit_size 58g
  </buffer>
</match>

Expected Behavior or What you need to ask
We expected the data to be stored in the buffer and retry till it was successful and not lose the data. How to achieve that when getting similar errors?
Using Fluentd and OpenSearch plugin versions

Ubuntu

Kubernetes

Fluentd
fluentd 1.16.2

OpenSearch plugin version
fluent-plugin-opensearch (1.1.4)
opensearch-ruby (3.0.1)

OpenSearch version
v 2.10.0

Created duplicate https://github.com/fluent/fluent-plugin-opensearch/issues/134 since the bot does not reopen it


bug: unsupported treasury network

Treasuries network is pulled from a small exhaustive list of networks on v2, compared to v1, which have a more broad networks support.
This is making v2 spaces using not recognized networks to fail, e.g https://snapshot.box/#/s:test.wa0x6e.eth/treasury/2/tokens

Existing but not enabled network will fail with Network XXX is not enabled
Unrecognized network will be just ignored (test space mentioned above has a third treasuries not shown, see https://hub.snapshot.org/api/spaces/test.wa0x6e.eth)

See #830

Will be covered by https://github.com/snapshot-labs/sx-monorepo/issues/830


Add platform specification when building binaries

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Write a Python program to find area of a square

Description
Write a Python program to find area of a square
Area of square = Side^2
Side : 2

Area : 4

How to contribute

Save the solution in find-area-of-a-square.py file
Add find-area-of-a-square.py file in find-area-of-a-square folder

!assign


README: Remove go install that does not work

Closes #3730

This will start working once we tag the next release.

This will start working once we tag the next release.

Great nevermind.


Add support for MacOS

Just changed some of the scripts to start and build, also may fix the node-hid mismatch problem.

Nice, I'll merge once I test on linux/macos

Nice thing to note too is that macOS (at least I don't think so) needs sudo/admin for hid (as the compiled app starts up fine without admin)

@stevelacy New release soon? Will there be a new WIN64 build too?
PS: Offtopic... Do you know about MSIHiddenFun too?

I do not know of MSIHiddenFun

Awesome, I would also want to help with this compatibility for mac, but I don't know if it's still being worked on. Regardless, I will add my changes too.

Sorry for the long delay, I just tested it on macos (crazy :smile:)


Docs: 插件文档的示意图更新

[x] application manager @alvinhui
[x] codemod @alvinhui
[x] doctor @fyangstudio
[ ] material-helper @alvinhui
[x] project-creator @alvinhui
[x] react-refactor @luhc228
[x] style-helper @fyangstudio
[x] time-master @alvinhui

Codecov Report

Merging #7 (d76b319) into release/1.0.0 (c60fcf2) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/1.0.0       #7   +/-   ##
==============================================
  Coverage          57.14%   57.14%
==============================================
  Files                  1        1
  Lines                 70       70
  Branches              18       18
==============================================
  Hits                  40       40
  Misses                30       30

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c60fcf2...d76b319. Read the comment docs.


Dependabot actions are failing/stuck

https://github.com/ansys/pyfluent/pulls/app%2Fdependabot

The CodeQL part of the issue is resolved, but the vale action is still not running correctly:

Moving this vale issue to a new issue for clarity, the codeQL/dependabot issue is resolved.


Duplicate AppSync "Sync" operations performed when there's a GSI @Index

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have read the guide for submitting bug reports.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
8.0.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
api
Amplify Commands
push
Describe the bug
When a secondary @index is applied to model entity foo, and the syncFoo graphql operation is called, two duplicate AppSync "Sync" operations are performed.

first one with a "proper" query specification (which uses the correct index, if correctly specified in the filter expression for the query) in the Query.syncFoo.preAuth.1.req.vtl pipeline function
next one that uses a plain filter/scan which does not use the correct index later in the pipeline, from Query.syncFoo.req.vtl

When an app's usage patterns necessitate using a GSI for a "sync" operation this completely negates the benefit of attempting to use a GSI.
Expected behavior
When there's a secondary @index applied to a model entity and the syncFoo graphql operation is called with a filter expression that matches the index field, a single AppSync "Sync" operation should be performed using a query and an index and no full table scans should ever be performed.
This behaviour is explicitly stated in the documentation.
Reproduction steps

use the schema below
amplify api gql-compile
examine the generated resolvers
Note the Query.syncFoos.preAuth.1.req.vtl which performs a proper query
Note the Query.syncFoos.req.vtl which performs a duplicate query with a full table scan

GraphQL schema(s)

type Foo @model
{
  id: ID!
  userId: ID! @index(name: "byUserId", queryField: "fooByUserId")
}

Log output
No response
Additional information
When looking at my AppSync logs (turn on verbosity and all field logging), I can confirm that both queries are actually being performed, and you can see that the initial query actually throws out the results in the response mapping. My suspicion is that the CLI code that's constructing the pipeline resolver from the different functions is placing them in the pipeline incorrectly. To me, it seems the contents of the Query.syncFoos.req.vtl shouldn't be there at all, and instead should just be replaced with the contents of Query.syncFoo.preAuth.1.req.vtl
Unfortunately this issue currently is a hard blocker, since I have a table with a non-trivial amount of data in it and I'm performing syncs on data that has an "owner" field which has the @index on it and it will be far, far too slow and/or expensive to perform syncs using table scans.

Just wanted to add a note that it seems the following issues are likely duplicates to this one:

https://github.com/aws-amplify/amplify-category-api/issues/718
https://github.com/aws-amplify/amplify-category-api/issues/977


SSO db failover event flow from kibana

Background:
identify event flow from kibana and timestamp for each event after db pod starts to have API connection timeout
Tasks:

kibana query to filter events
track time between issues start to resolve
identify the cause with DXC support

@ShellyXueHan 👋  is this still an issue?


docs: improve navigation

Summary of Changes

Separate README for GitHub
Remove recursive link to full documentation from README of full documentation
Hide navigation of home page to emphasize the navigation bar at the top
Some other tweaks to the navigation settings

:tada: This PR is included in version 0.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.12.0
GitHub release

Your semantic-release bot :package::rocket:


Remove future plans from README

Right now the claims made aren't true and they just add confusion. "Interspatial parsing" was meant to refer to parsing a file when it changes and only parsing the change and then placing it back into the AST, but I think I just came up with that name, there's probably an actual name for it.
cc @hzoo

Yep sounds good to me!

"Interspatial parsing"

That does sound pretty interesting to me, and I guess maybe that can be related to the whole immutable ast and caching that stuff?


How to stop scrolling from left if we are at index 0.(Bouncing)

How can we stop scrolling from left if we are at index 0 and stop scrolling from right if we are at last index.
I tried :-  @lucoceano
override func scrollViewDidScroll(_ scrollView: UIScrollView) {
    if currentIndex == 0 && scrollView.contentOffset.x < scrollView.bounds.size.width {
        scrollView.contentOffset = CGPoint(x: scrollView.bounds.size.width, y: 0)
    } else if currentIndex == (viewControllers.count - 1) && scrollView.contentOffset.x > scrollView.bounds.size.width {
        scrollView.contentOffset = CGPoint(x: scrollView.bounds.size.width, y: 0)
    }
    //reloadData()
}

override func scrollViewWillEndDragging(_ scrollView: UIScrollView, withVelocity velocity: CGPoint, targetContentOffset: UnsafeMutablePointer<CGPoint>) {

    if currentIndex == 0 && scrollView.contentOffset.x < scrollView.bounds.size.width {
        scrollView.contentOffset = CGPoint(x: scrollView.bounds.size.width, y: 0)
    } else if currentIndex ==  (viewControllers.count - 1) && scrollView.contentOffset.x > scrollView.bounds.size.width {
        scrollView.contentOffset = CGPoint(x: scrollView.bounds.size.width, y: 0)
    }
}

Not working.
Thanks

So for what I understood you just wanna stop bouncing?
Please take a look at this

I tried the same but when click on tab its giving an exception.
I don't know how can I resolve it.
Please tell me if click on a tab also we can change the tab indicator and index?
Thanks

What exception? Please post some code here

Exception :-
'Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'No view controller managing visible view <UIView: 0x7fc3ad90ed70; frame = (0 0; 320 458); autoresize = W+H; layer = <CALayer: 0x60800003dda0>>'
Even tab indicator is also not updating.
Code you can see in my question.
Thanks


Document zlib options

Based on the zlib options, it seems like there are some extra properties that can be used but aren't very well documented there either (level, memLevel, and strategy). Does it make sense to at least show which ones can be accepted?

All options are passed to zlib. You can look up the zlib docs separately if you need to know the details. :)
Usually you wouldn't touch those things, they already default to the optimal sweet spot levels on nearly every machine.

So I had thought about doing this back at the beginning of 2014, but gave up, because I couldn't just copy Node.js docs, had to read and come up with good explanations of the stuff from the zlib man page, and have to check that those explanations actually match what Node.js is doing.
@ilanbiala if you're willing to do this, I would happily add it/accept a PR :)

@dougwilson how explanatory do you think it should be?

how explanatory do you think it should be?

Probably just good enough so you don't have to consult any other docs to understand what they mean, since that's what it does right now (points you to read another doc source). So like an explanation that makes sense, the type and range of values the option takes.

like this?
https://github.com/kesla/node-snappy/blob/master/benchmark/benchmark.js
level: zlib.Z_BEST_SPEED
memLevel: zlib.Z_MAX_MEMLEVEL

Usually you wouldn't touch those things, they already default to the optimal sweet spot levels on nearly every machine.

can I suggest these zlib options as default?
https://gist.github.com/hex7c0/25165f2f4650dfe16832

Why would we use those as defaults? Those values are not going to be worth your while. :)
Max speed will be faster, but compress way too little. Max memory is also certainly unnecessary, otherwise it would be the default.

@hex7c0 Hmmm, benchmarks look promising though.

@Fishrock123 I use @kesla's benchmark
so the file is this 46Kb
from http://nodejs.org/api/zlib.html#zlib_memory_usage_tuning

memLevel = 8 (default values)

from http://zlib.net/manual.html#Constants

The memLevel parameter specifies how much memory should be allocated for the internal compression state. memLevel=1 uses minimum memory but is slow and reduces compression ratio; memLevel=9 uses maximum memory for optimal speed. The default value is 8. See zconf.h for total memory usage as a function of windowBits and memLevel.

with zlib.Z_MAX_MEMLEVEL (maybe) you can raise to 9

regard compression/speed
46155 bytes no compression
14105 bytes default compression
16481 bytes zlib.Z_BEST_SPEED compression
there isn't too much difference :) +2376 bytes

@Fishrock123 do those settings make sense?

If someone wants them documented here, please see https://github.com/expressjs/compression/issues/28#issuecomment-68645901 . What I need is a specific list of the options and exactly what they do and what values they accept (and their complete value range).

This is an example of what I'm looking for: https://github.com/expressjs/compression/commit/c5b813e319e33cb5feb0237de065a25d6c3bde6b


Microbit: Empty value in show block breaks program execution

Describe the bug

The program gets 'stuck' when an empty text block is used with a show text or character block. Any code after these blocks will not execute.

To Reproduce
Steps to reproduce the behavior:

Go to show text block
Delete the text in the string block
Add any code after
Run simulation and see error

Expected behavior

A warning, e.g. 'this block will not execute' or 'missing input'
Program should continue after this block, any program after this block should execute

Screenshots

In the program below, the image is never displayed

Device information

Desktop
Windows 10
Chrome

As far as I can tell this seems like a duplicate of #455.


How to configure WalletConnectProvider with local network rpc

I am trying to set up WalletConnectProvider as a provider option of Web3Modal on the localhost ("http://localhost:8545") network.

For some reason, when I don't set the network property, the modal works but it is trying to use the Infura API

When I set the network property, it throws this error:

"No chainId found match ${network}".

I found it works when using http://<IP_ADDRESS>:8545/ for the rpc configuration

chainId is invalid in web3modal, you should use network param. but there is a default network list in chain.ts, you cannot use custom network.
There is a hack. I think web3modal should support chainId param.
walletconnect: {
      package: WalletConnectProvider, // required
      options: {
        rpc: {
          1: "https://eth-mainnet.alchemyapi.io/v2/",
          56: "https://bsc-dataseed.binance.org/",
          137: "https://rpc-mainnet.maticvigil.com",
          421611: "your localhost"
        },
        // matic binance mainnet
        network: 'arbitrum-rinkeby'
      }
    }

@wuzhengyan2015 As I understood WalletConnect just does not work with http provider

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


Handle IPv6 in zeroconf

Description: If the API host is an IPv6 address, inet_aton will fail.
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

@rcloran This looks good to go once you have fixed the Farcy comments


Validate demonstrations

chat → a list of content blocks
json → JSON that fits the schema

Rough Plan

Add ClickHouse materialized views for inference tables indexed/sorted by id (migration needs to populate older data)
Feedback endpoint queries with target_id (demonstrations always apply at inference level)
If it's a chat function, demonstration should be a list of content blocks (maybe also a simple version - if JSON string, it's a single text block). If it's a JSON function, it should be a JSON value that matches the output schema (must account for dynamic output schemas).


Failed to perform, curl: (5) getaddrinfo() thread failed to start

I'm trying to run a curl-cffi script with AsyncSession and ~80 threads without any proxies
It performs well for a while, but then, all the threads encounter this error, and I have to restart the program to continue running it:
Failed to perform, curl: (5) getaddrinfo() thread failed to start. See https://curl.se/libcurl/c/libcurl-errors.html first for more details.

Is there any problem with my side? Or it is the server side that having this problem ? I tried both proxy and non-proxy code, both produced this error!

Were you using ~80 coroutines or ~80 threads? Mixing threads and eventloops is not a great idea, generally. Try use processes instead.
Anyway, in the future, the upstream curl-impersonate will be built with c-ares by default, which should solve all the DNS resolution problems.

Thanks for addressing it!

I tried with 30 threads, but the same thing happened
async def main():
    tasks = []
    semaphore = asyncio.Semaphore(30)
    with open("ref_list_task_test.txt", "r") as f:
        ref_code_json_list = [line.strip() for line in f.readlines()]
    for ref_code_json in ref_code_json_list:
        ref_json = json.loads(ref_code_json)
        for name, ref_code in ref_json.items():
            if name in ["orbit"]:
                for _ in range(8):
                    tasks.append(process_tool(semaphore, ref_code))

    await asyncio.gather(*tasks, return_exceptions=True)

    ```
    Here is my main function. What should I modify? @yifeikong

Try to change the version

Use older version you meant?

The problem is not the number of threads. And c-ares will not help here.
It's just that your dns-server can't handle so many requests.
The solution is simple: configure your system to use several fast dns-servers (<IP_ADDRESS>.1, <IP_ADDRESS>, <IP_ADDRESS>.8, <IP_ADDRESS>.9, and so on).

@deedy5 I did think about  that, but I tested on some Virtual Private Server, they ran exactly 510 lines then this error started happening (just as my main computer).

I tested with Google DNS, and everything works well, for now :D.
Thank @deedy5 !

I tested with Google DNS, and everything works well, for now :D. Thank @deedy5 !

Not working...............

curl-impersonate

curl-impersonate,is this updated?


Use the new Async Server to replace analysis threads

Builds on #3033 and #3049.

I'm concerned about having an unbounded number of processes running, more opportunities for zombie processes.  What if we only created one other process for all async tasks, saved that pid, and explicitly kill it at the next startup?
That other process would have a pool of QThread workers.  Then we have worst case one zombie process, that gets cleaned up at startup.  We'd also give priority to the libs in the target environment, but provide the ones in the root environment as fallback.
@goanpeca, @ccordoba12, @Nodd, thoughts?

I'm +1 for that. Please go ahead with one server only :-)

Sound good stevo

I think we need two servers: one that is running in a target environment, and one that is running in the current environment.  The current environment would be used for things that don't rely on the target environment, removing the need for complicated path overrides in the target environment.

Also, if possible, we should avoid using Qt in the target environment, since that is a huge can of worms.

we should avoid using Qt in the target environment meaning?

We shouldn't require it to be installed in the target project environment, and I'm not sure if we can "patch" it in, especially across python versions.

Ahh ok.
I never thought we needed to do that... the idea is to have a root env for spyder and spyder plugins and a spyder infrastructure to be able to call python modules that are specific to python versions (pep, jedi, rope, ipython backend etc...). There is no Qt python stuff that we would need to have in place in the specific environment.

These are actually two new types of plugins: async_root, and async_env, and I think should be treated similarly to other plugins.

So, when we start the AsyncRoot server, it provides those plugins, and when we start the AsyncEnv server, it provides those plugins.

We write the two pids to spyder.lock, and clear those pids at startup.

Candidates for root: widgets/findinfiles/SearchThread, widgets/pydocgui/PydocServer, plugins/help/SphinxThread, workers/updates/WorkerUpdates, widgets/externalshell/monitor/Monitor, widgets/externalshell/introspection/NotificationThread, widgets/editor/AnalysisThread
Candidates for env:  utils/introspection/*

:+1:

My thoughts:

I would like to see widgets/editor/AnalysisThread as part of the env server, not the root one
Things related to our Python consoles monitor should be left as they are. They are tricky and hard to debug. Besides, I'm planning to deprecate our Python console in the future (precisely because of this).
I don't see the need to touch SearchThread, PydocServer, SphinxThread and WorkerUpdates. IMHO they are fine as Qt threads :-)

@ccordoba12 By deprecating our Python console, you mean keeping ipython only ? If that's the case I'm strongly against it, I run my scripts in a new python interpreter almost exclusively.

@Nodd, I mean that I'm planning to move our Python console to be a third-party plugin, so others can help me to maintain it (if they want to keep using it) because having two consoles is too much of a burden :-)

I don't see myself having time to implement this for 3.0beta4.

Here is the API sketch I made:
class AsyncService:

    """The base async service that runs in the current env"""

    def __init__(self, executable=None, env=None):
        # set up the zmq socket
        pass

    def setup(self):
        """Set up the QProcess - this is intended to be overridden"""
        # discover base plugins, pass to the qprocess

    def start(self):
        """Start the QProcess"""
        # Set up the socket notifier and heartbeat

    def request(self, plugin, func_name, *args, **kwargs):
        """Send a request to the provider, returning the request id"""

class AsyncEnvService(AsyncService):

    def setup(self):
        pass
        # discover env plugins, add to PYTHONPATH, set up qprocess

class AsyncManager:

    def __init__(self):
        # gets the port and the list of plugins to load from argv
        pass

class AsyncPlugin:
    pass

class AsyncEnvPlugin:

    """A plugin that should run in a target environment."""
    libs = []  # Libs to load in the target environment

Thanks @blink1073!

This is superseded by issue #4742.


SDK does not call callback

Expected Behavior
When use a batch of 10 events or 30 millisec, when the quantity or time is reached the SDK should trigger the callback for each event that was added.
Current Behavior
I am using a batch of 10 events or 30 millisec, when the quantity or time is reached the SDK triggers the callback (onLogEventServerResponse) only once.
Steps to Reproduce
  private val callBackAmplitude = object : AmplitudeCallbacks() {
      override fun onLogEventServerResponse(event: AmplitudeEvent, status: Int, message: String?) {
        logger.warn("Status: $status - Message: $message - Event: $event")
      }
    }

 val client = Amplitude.getInstance().also {
    it.init(apiKey)
    it.setEventUploadThreshold(10)
    it.setEventUploadPeriodMillis(30000)
    it.useBatchMode(true)
    it.setCallbacks(callBackAmplitude)
  }
 client.logEvent(event)

Environment

implementation 'com.amplitude:java-sdk:1.12.0'

@izaaz can you help?

Guys, sorry for the issue, there is no problem, the SDK works correctly.
It would be interesting to add documentation stating that any error that occurs in the callback will not be propagated. This happens due to the thread that the SDK runs.


Can't Build

Can't Build the Addon
"Could not find meteor-client-0.5.2-SNAPSHOT.jar (meteordevelopment:meteor-client:0.5.2-SNAPSHOT:20230123.224945-43).
Searched in the following locations:
https://maven.meteordev.org/snapshots/meteordevelopment/meteor-client/0.5.2-SNAPSHOT/meteor-client-0.5.2-20230123.224945-43.jar"

Fixed the issue by deleting the cache folder in Home directory.


Fine-tuning on Dark Face

Dear author, thank you so much for the brilliant work!
I tried to reimplement your results on Dark Face following your instructions but got some bad results (an mAP of 0.2 on your val split). Since setting up the fine-tuning step is very simple by only modifying the paths to Dark Face dataset and pretrained model, I am very confused what goes wrong. Could you please share some advice? Thank you.

Hello, please check these:
(1) Could you get my results on Dark-Face use our pre-train model.
(2) Have you load the correct pre-train model? Or have you change the config file?

Maybe, you use the different version of UG2 dataset, since I use the first version UG2 dataset, so maybe you use the newer version UG2 dataset?

If the EXDark results you run is OK, right?
I'll check it after the CVPR ddl and reply to you later~

Sorry for the late reply, I've check and confirm that the results isn't wrong, the command is:

and the results should be:

Please confirm that you get same mmdetection version and mmcv version.
. And the command should be same as mine.
Thanks for your interests in my paper, any question please drop here ~


CrashLoopBackOff in node with GRE tunnel after upgrading from Cilium 1.7 to 1.8

Bug report
I'm having trouble with Cilium in one of the nodes of my cluster after upgrading from 1.7.x to 1.8.4 (using Kubespray). The special thing about this node is that it's connected to the rest of the node private network through a GRE tunnel. It worked well with Cilium 1.7.2 and Kubernetes 1.16.
General Information

Cilium version:

Client: 1.8.4 17d623853 2020-09-30T17:31:44-07:00 go version go1.14.9 linux/amd64
Daemon: 1.8.4 17d623853 2020-09-30T17:31:44-07:00 go version go1.14.9 linux/amd64

Kernel version: 5.4.0-52-generic
Orchestration system version in use: Kubernetes 1.17.9 (previously 1.16)
Link to relevant artifacts (policies, deployments scripts, ...) -
Generate and upload a system zip: (too big to be attached) see

How to reproduce the issue

Create a GRE tunnel to connect the faulty node to the private network where the rest of nodes are:

ip tunnel add tunnel0 remote x.x.x.x local y.y.y.y mode gre
ip link set tunnel0 up
ip addr add <IP_ADDRESS>/20 dev tunnel0
ip route add <IP_ADDRESS>/20 dev tunnel0

Update Kubernetes and Cilium (in my case, using Kubespray)

Result: Cilium works on all nodes but the one with the tunnel interface, where the pod (cilium-5jst9 in he dump) enters CrashLoopBackOff. Other cilium pods are restarted periodically due to a livingProbe failure (I think related to one failing), but networking works in those nodes. The failing cilium pod's log contains an error line that mentions the GRE tunnel interface on that server:
level=error msg="Command execution failed" cmd="[/var/lib/cilium/bpf/init.sh /var/lib/cilium/bpf /var/run/cilium/state <IP_ADDRESS> <nil> vxlan enp35s0;tunnel0 <nil> <nil> 1500 false <nil> true true false /var/run/cilium/cgroupv2 /sys/fs/bpf true true v2 enp35s0=0xce2477a8;tunnel0=0x658010ac <nil> 32]" error="exit status 1" subsys=datapath-loader

Thank you.

@Boca13 thanks for opening the issue, what's the output of ip a s from the node running cilium-5jst9?

Thank you for your reply, @aanm.
The output of ip a s is:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp35s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether a8:a1:59:38:e6:3b brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope global enp35s0
       valid_lft forever preferred_lft forever
    inet6 2a01:4f8:242:2317::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::aaa1:59ff:fe38:e63b/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:2b:c7:fc:7c brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
4: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
    link/gre <IP_ADDRESS> brd <IP_ADDRESS>
5: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: nodelocaldns: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
    link/ether b2:d7:b5:2c:12:52 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 brd <IP_ADDRESS> scope global nodelocaldns
       valid_lft forever preferred_lft forever
11: tunnel0@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1476 qdisc noqueue state UNKNOWN group default qlen 1000
    link/gre <IP_ADDRESS> peer <IP_ADDRESS>
    inet <IP_ADDRESS>/20 scope global tunnel0
       valid_lft forever preferred_lft forever
    inet6 fe80::200:5efe:a877:24ce/64 scope link
       valid_lft forever preferred_lft forever
18: lxcc49345b3acbd@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 8a:94:b6:e9:58:b8 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::8894:b6ff:fee9:58b8/64 scope link
       valid_lft forever preferred_lft forever
24: cilium_net@cilium_host: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:49:bd:92:d8:e4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3849:bdff:fe92:d8e4/64 scope link
       valid_lft forever preferred_lft forever
25: cilium_host@cilium_net: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:18:ae:c7:02:e0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5418:aeff:fec7:2e0/64 scope link
       valid_lft forever preferred_lft forever

@Boca13 and ip route show?

root@dedicated-1 ~ # ip route show
default via x.x.x.x dev enp35s0 proto static onlink
<IP_ADDRESS>/20 dev tunnel0 scope link
<IP_ADDRESS>/20 dev tunnel0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown

I did an initial triage to this issue. It seems tunnel0 is being considered as part of the list of nodeport devices by the automatic discovery introduced in 1.8.

Thank you, @aanm, it seems so. I wonder if there's any parameter that I could change in the configmap to exclude or limit the list of devices to the pertinent interfaces.
Thank you again for your help.

The problem is that tunnel0 doesn't have L2 addr:  You can set devices via devices: ... which will disable the auto-detection. Anyway, if you are using tunnel0 to connect to other k8s nodes, then BPF NodePort won't work when accessed from outside (you might need to disable it).
Closing, as it is a duplicate of https://github.com/cilium/cilium/issues/12317.


bride-log node

bridge-log node
The Bridge-log node provides functionality to filter the Zigbee2MQTT log.
Requirements
The user should get a UI to filter the log types.

If a log is selected, a node output is dynamically created.
By default, the node provides one output per log type.
There should be a switch to direct all messages to one output instead of one per message type.

Example payloads
{"message":"announce","meta":{"friendly_name":"0x14b457fffe4572a9"},"type":"device_announced"}
{"message":"left_network","meta":{"friendly_name":"0x14b457fffe4572a9"},"type":"device_removed"}
{"message":"interview_started","meta":{"friendly_name":"0x14b457fffe4572a9"},"type":"pairing"}
{"message":{"friendly_name":"0x14b457fffe4572a9"},"type":"device_connected"}
{"message":"interview_failed","meta":{"friendly_name":"0x14b457fffe4572a9"},"type":"pairing"}
{"message":{"from":"0x14b457fffe4572a9","to":"Fernbedienung 2"},"type":"device_renamed"}

@Dirnei what do you think about the style for the checkboxes in the config.

I prefer the last three. I also tried that with icons but that looks to cluttered.

The last ones are preffered. In addition i would lower the size of your descriptioin


In the new version of OBSIDIAN, In real -time previews, the dual -chain title of the label does not change the color.

In the new version of OBSIDIAN, use TAG to change the title color.
There is also an A tag to split the title into the title to store information. So to modify the newly added, in SuperCharged-Links-Gen, add a new control of the A tag below the title. Only to repair this problem.
If it is only modified to a tag to A, it will cause other colors to not display before.

In fact, manual can be solved, but after clicking the plug-in, SuperCharged-Links-Gen will be automatically updated. Need to be rewritten

This should be solved in the latest update. Please let me know otherwise.

Hi!

It is working on Mac OS
It is not working on IOS and on iPad OS


Improve vector binops evaluation.

Against all expectations, this particular piece of code did not win any obfuscation contests. So we might as well turn it into something normal.
This is not to say that it is trivial now, but it's easy enough to dig into it in a few minutes.
Also, it is more strict regarding empty/unset labels - they are a value as anything else and will raise errors respectively. Before, that was prevented which caused wishy-washy semantics. (Minor breaking change for people who didn't match their labels properly.) This is also more aligned with the idea in #494.
Now we no longer have to pretend to understand why vector binops work :balloon:  :tada:
Also, better errors.

@juliusv

:+1:


-vsync

How to set -vsync parameter? Thanks.

Don't believe it's supported by the API itself, but can be done via .addExtraArgs("-vsync", "vfr"), for example.

I'll close this, as the question seems to be answered.
Feel free to re-open if this is not the case.


Adding support for i18n-debug

See https://github.com/fphilipe/i18n-debug. We may need to observe if
this adds any significant time to builds.
Below is example output that is written to
.internal_test_app/log/test.log:
[i18n-debug] en.simple_form.labels.file_set.files => nil
[i18n-debug] en.simple_form.labels.file_set.files => nil
[i18n-debug] en.simple_form.labels.defaults.files => "Upload a file"
[i18n-debug] en.simple_form.required.text => "required"
[i18n-debug] en.simple_form.required.mark => "*"
[i18n-debug] en.simple_form.required.html => "required"
[i18n-debug] en.simple_form.hints.file_set.files => nil
[i18n-debug] en.simple_form.hints.file_set.files => nil
[i18n-debug] en.simple_form.hints.defaults.files => nil
[i18n-debug] en.simple_form.hints.defaults.files => nil
[i18n-debug] en.simple_form.hints.file_set.files => nil
[i18n-debug] en.simple_form.hints.file_set.files => nil
[i18n-debug] en.simple_form.hints.defaults.files => nil
[i18n-debug] en.simple_form.hints.defaults.files => nil
[i18n-debug] en.activemodel.models.file_set => nil
[i18n-debug] en.activemodel.models.active_fedora/base => nil
[i18n-debug] en.helpers.submit.file_set.update => nil
[i18n-debug] en.helpers.submit.update => "Save"

While the specs are running, I was running the following command to see
what translation keys was hit or missed:
tail -f .internal_test_app/log/test.log

@projecthydra-labs/hyrax-code-reviewers

Related to https://github.com/projecthydra-labs/hyku/pull/629

@jeremyf how frequent is that output? is that the full output right now? It looks like it may have the potential to make the (already noisy) logs very noisy. Did you consider a report (rake task?). Or are you hoping the noise will cause us to address issues with i18n?

@hackmastera At present, anytime there is a request to I18n it would be logged.
It would be possible to require an ENV be set for the logging to occur (e.g. require 'i18n-debug' if ENV['i18n_debug'])

+1 on the ENV idea; I would even be okay with the ENV turning it off if more people want to see this in the logs on a regular basis (i.e. expect to incorporate whatever will be required to deal with the messages into their workflow)

@hackmastera @jeremyf Made the change y'all discussed. I know @jcoyne also discussed this with @jeremyf but I couldn't find that thread, so I'd be glad to hear your thoughts on this too.
Note that I also created this wiki page as a companion to this PR: https://github.com/projecthydra-labs/hyrax/wiki/Testing-internationalization-(i18n)-support

Rebased.

@jcoyne Re-review?

@jcoyne OK, think I've got it now.


feat: 20231103 release

Fix #530
Fix #557
Fix #574
Fix #575

:tada: This PR is included in version 6.35.0 :tada:
The release is available on:

GitHub release
v6.35.0

Your semantic-release bot :package::rocket:


Add the common label to the operator Pod

Resolves https://github.ibm.com/IBMPrivateCloud/roadmap/issues/59790
@rwhundley pls review - thanks!

Adapted for Operator SDK layout here: https://github.com/IBM/ibm-iam-operator/pull/762


[test-operator] Fix a variable name in the README

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve


Nodejs: Cannot find module 'graphicsjs'

After successful installation package with npm, i write to server.js
var G=require('graphicsjs')
and at startup receive Error: Cannot find module 'graphicsjs'
Package version: 1.3.2

@A134025
Unfortunately, the current version of GraphicsJS is not available for using with NodeJS as it's a browser specific module and it requires a window object and many other browser specific features.


Bug in dataset aggregation, LET/D variables

Reported by ansley b manke on 30 Oct 2013 21:52 UTC
Steve ran into this example:

    ! create dummy datasets so we'll have named file variables to play with
    CANCEL DATA/ALL
    let fv1 = 1
    let fvx = x[   let fvz = Z[k=1:3](i=1:3]
)
    SAVE/CLOBBER/QUIET/FILE=my_file_vars.nc fv1, fvx, fvz
    SAVE/CLOBBER/QUIET/FILE=other_file_vars.nc fv1
    SAVE/CLOBBER/QUIET/FILE=another_file_vars.nc fv1
    CAN VAR/ALL

use  my_file_vars, other_file_vars, another_file_vars
set data 1

! aggregation in which some members are uvars

let/d=other_file_vars   fvx = fv1 + x[fvx = 2*fv1 + x[gx=fvx[d=1](gx=fvx[d=1],i=1:3]
let/d=another_file_vars),i=1:3]
sh grid fvx[grid fvx[d=3](d=2]
sh)

define data/agg my_uvar_agg = my_file_vars, other_file_vars, another_file_vars
sh dat

results in, for the aggretation,
    4> MY_UVAR_AGG  (default)  Ferret-defined Ensemble dataset
 name     title                             I         J         K         L         M         N
 FV1      1                                ...       ...       ...       ...       1:3       ...
 **ERROR: error defining aggregate dataset: grids for LET/D variables do not match for aggregate datasetFVX
sh dat
Command file, command group, or REPEAT execution aborted
 FVX      X[                      :-...7 :-777...-7777 :...77 :-77...:-7777 ...       ...

For one thing, the grid output is screwy with those -7777's, but in fact the aggregation should work for variable FVX. SHOW GRID for FVXd=1, FVX[d=2], etc show the same grid.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2098

Comment by ansley.b.manke on 30 Oct 2013 22:32 UTC
To clarify, other examples making ensembles that involve LET/D variables have been working successfully.
The bug is fixed in is_aggregate_grid.F, getting the grid of the user-defined variables in the ensemble. The datasets now make a correct ensemble of the variable FVS.
The incorrect grid listing seen with the error message is fixed in show_data_set_vars.F. A status flag is set if grid number cannot be determined and at that point we should exit from the routine. The flag wasn't being checked.

Modified by ansley.b.manke on 1 Nov 2013 16:36 UTC


[EN] Feedback for: /tools/setup/device-testing/devtools-emulator.html

https://developers.google.com/tools/chrome-devtools?hl=en
This link is broken. Please verify.

What page linked you to this?

I found the bad link at https://developers.google.com/web/tools/?hl=en
'Chrome DevTools' (404 https://developers.google.com/tools/chrome-devtools )
The proper link should be
https://developers.google.com/web/tools/chrome-devtools/?hl=en

Fixed.


Refactor version.getPrograms to be called from versionRepository

Description
Refactors places that call version.getPrograms() to use a new function getProgramsForVersion(). The new function calls version.getPrograms() for now, but in the future we'll set up caching for non-draft versions within that function. For now, no functionality is updated with this change.
This is very similar to https://github.com/civiform/civiform/pull/5711
See more information in doc
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release | database >

Issue(s) this completes
Related to https://github.com/civiform/civiform/issues/5724

this lgtm! is there a need to refactor tests as well?

Good question, thanks for checking! If we want to more officially deprecate the method in the future, we'll want to refactor the tests too, but these are fine to leave as is for now.


Cannot update root RCS backend after store creation

Summary
I have an existing store (coming from pass) that, I believe, does not have an associated git repository (is there a way to check that?).
I want to initialize one (i.e. switch it to the gitcli RCS backend) to do synchronization, but it doesn't work.
Steps To Reproduce

Run gopass git init. (This gives Initializing git repository (noop) ... and Git initialized, but I can re-run the same command and get the same result, so I'm not sure it works.)
Run gopass git remote add origin … (This prints nothing.)
Run gopass sync. (This prints WARNING: Mount uses RCS backend 'noop'. Not syncing! even though my path contains gpgcli-gitcli-fs+file://….

Expected behavior
Git repository should be initialized and synced.
Environment

OS: ArchLinux
OS version: Linux antoyo-laptop 5.7.8-arch1-1 #1 SMP PREEMPT Thu, 09 Jul 2020 16:34:01 +0000 x86_64 GNU/Linux
gopass Version:

gopass 1.9.2 (2020-07-13 14:34:42) go1.14.4 linux amd64
<root>     - gpg 2.2.21 - noop 0.0.0 -   fs 0.1.0
Available Crypto Backends: age, gpgcli, plain, xc
Available RCS Backends: gitcli, noop
Available Storage Backends: fs, inmem

Installation method: ArchLinux repository

The line <root>     - gpg 2.2.21 - noop 0.0.0 -   fs 0.1.0 seem to indicate that the root mount is using the noop backend, but I cannot figure out how to change it to gitcli.
Additional context
If it's not possible to change the RCS backend of the root mount, how can I workaround this issue?

Thanks for reporting this. That sounds like a bug (gopass git init doesn't seem to override the RCS noop backend and performs a no-op git init).
Will try to reproduce it.
As a workaround you can always initialize git yourself in the password store directory and gopass should detect that on the next run.

So, I've tested this and it seems to work with the current master.
Roughly what I did:
$ mkdir testhome
$ export GOPASS_HOMEDIR=testhome
$ gopass setup
# not adding a git remote
$ mkdir testrepo
$ cd testrepo && git init --bare
$ gopass git init
$ gopass git remote add origin testrepo
$ gopass git push

So, I've tested this and it seems to work with the current master.
Roughly what I did:
$ mkdir testhome
$ export GOPASS_HOMEDIR=testhome
$ gopass setup
# not adding a git remote
$ mkdir testrepo
$ cd testrepo && git init --bare
$ gopass git init
$ gopass git remote add origin testrepo
$ gopass git push


Rspec tests freeze as soon as DatabaseCleaner begins to work

I'm in the middle of a painful upgrade from Rails 5.2.7 to 6.1 (as well as Ruby 2.7.6 to 3.1.4) and DatabaseCleaner is the bulk of my headache. At this point the specs are just freezing as soon as the cleaner begins its work. My setup is rather complicated but based on everything I've pieced together I believe my syntax is correct for what I'm trying to accomplish.
I have a two database setup: Postgres and a legacy mysql database that both need to be cleaned. Here is what I currently have in my rails helper including required files which there isn't much documentation on. I have a hunch maybe I have too many or two few requires.
Relevant Gems
  capybara (~> 3.39)
  capybara-screenshot
  database_cleaner-active_record
  geckodriver-helper
  selenium-webdriver (~> 4.11)

database.yml
default: &default
  adapter: postgresql
  encoding: unicode
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  host: localhost

test:
  <<: *default
  database: test_db

test_legacy:
  url: <%= ENV['LEGACY_DB_TEST_URL'] %>
  adapter: mysql2
  connect_timeout:

rails_helper.rb
  require 'spec_helper'
  require 'rspec/rails'
  require 'devise'
  require 'support/devise_login_helper'
  require 'support/factory_bot'
  require 'paper_trail/frameworks/rspec'
  require 'selenium/webdriver'
  require 'capybara/rails'
  require 'database_cleaner/active_record'
  require 'support/select2_helper'
  require 'support/feature_spec_helpers/wait_for_ajax'
  require 'support/feature_spec_helpers/sessions'
  require 'capybara-screenshot/rspec'

  config.use_transactional_fixtures = false

  config.before(:suite) do
    if config.use_transactional_fixtures?
      raise(<<-MSG)
        Delete line `config.use_transactional_fixtures = true` from rails_helper.rb
        (or set it to false) to prevent uncommitted transactions being used in
        JavaScript-dependent specs.

        During testing, the app-under-test that the browser driver connects to
        uses a different database connection to the database connection used by
        the spec. The app's database connection would not be able to access
        uncommitted transaction data setup over the spec's database connection.
      MSG
    end
    DatabaseCleaner[:active_record, db: :test_legacy].clean_with(:truncation)
    DatabaseCleaner[:active_record, db: ApplicationRecord].clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })
    DatabaseCleaner.strategy = :transaction
  end

  config.after(:all) do
    DatabaseCleaner[:active_record, db: :test_legacy].clean_with(:truncation)
    DatabaseCleaner[:active_record, db: ApplicationRecord].clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })
  end

  config.before(:each) do |example|
    if example.metadata[:js]
      DatabaseCleaner.strategy = :truncation
    elsif example.metadata[:type] == :feature
      # :rack_test driver's Rack app under test shares database connection
      # with the specs, so continue to use transaction strategy for speed.
      driver_shares_db_connection_with_specs = Capybara.current_driver == :rack_test

      unless driver_shares_db_connection_with_specs
        # Driver is probably for an external browser with an app
        # under test that does *not* share a database connection with the
        # specs, so use truncation strategy.
        DatabaseCleaner.strategy = :truncation
      end
    end
  end

  config.before(:each) do
    DatabaseCleaner[:active_record, db: :test_legacy].start
    DatabaseCleaner[:active_record, db: ApplicationRecord].start
  end

  config.append_after(:each) do
    DatabaseCleaner[:active_record, db: :test_legacy].clean
    DatabaseCleaner[:active_record, db: ApplicationRecord].clean
  end

for the line:
DatabaseCleaner[:active_record, db: ApplicationRecord].clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })

I've tried several different things including:
DatabaseCleaner[:active_record, db: :test].clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })

and
DatabaseCleaner[:active_record].clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })

and
DatabaseCleaner.clean_with(:truncation, { except: %w[submission_statuses submission_definitions] })

All with no success. It's frustrating because there is zero to go off of here. The test suite just stops running with no errors:
The test.log file looks like this:
   (0.2ms)  SELECT @@FOREIGN_KEY_CHECKS
   (0.1ms)  SET FOREIGN_KEY_CHECKS = 0
   (0.6ms)  select table_name from information_schema.views where table_schema = 'legacy_test'

and it only chokes on the legacy because it's cleaning comes first in the code, if I switch the order it chokes on the Postgres DB instead.
I've removed DB cleaner altogether and turned back on use_transactional_fixtures just as a test  and my tests run fine until I run a test that uses the legacy database. The transactional fixtures apparently only works for the one main postgres db.
I found some old questions about this very same thing that had been closed so I wanted to post my question here to see if others are experiencing the same issue.
Looking forward to your help! Thanks!

Well after several hours of trying things I just threw up my hands and rebooted my machine and the problem seems to have gone away


Load first program rather than dataset

This PR changes which document is autoloaded when Dataflow is first loaded in the browser.  Instead of loading the newest document, we first try to load the newest program document.  If there are no programs, then we load the newest document of any type.  If there are no documents, then we create a new document.

Yeah, that

I admit I don't know enough about CLUE documents to recall how this loading works, and how exactly this changes it. I'm slightly confused by the logic -- it looks like we're prioritizing documents that don't have relays or data? But that's probably just not me understanding it.

The dfHasRelay and dfHasDataStorage flags were added to indicate a completed or run program of 1 of 2 types.  So what this is really doing is putting programs (which in user-facing vernacular means "un-run, editable programs") ahead of completed runs.

@sfentress This pic shows what we are trying to load and which documents the flags correspond to:


Implement additional parameter for contract deployment

See neo-project/neo#2239.

And it'd be nice to fix neo-project/neo#2236 while we're here.

And it'd be nice to fix neo-project/neo#2236 while we're here.

And we can do neo-project/neo#2242 at the same time if we're to implement #1683 first.

And we can do neo-project/neo#2242 at the same time if we're to implement #1683 first.


Difficulty Training with my Dataset, Generating white Blank images after 960kimg

Hallo,
thank you for your distinguishable and appreciated effort making this Paper and its implementation. I am currently trying to train the model on my dataset (which consists of ~2700 Forest Roads Images, but the model produces blank white images after the 960kimg mark. could this be due to the big difference between my dataset statistics and the Landscape Dataset statistics you offered in the Paper Supplemental Document.
** Landscape Dataset / overexposed pixels: 2.5% / underexposed pixels: 9.2%
** my Forest Dataset / overexposed pixels: 6.69% / underexposed pixels: 0.47%
In addition, should I nearly match the Histogram of mean pixel intensities found in Figure 1? because my dataset Histogram of mean pixel intensities is significantly different?
Thanks a lot!

Hi, I encountered the same problem. I even used the LDR dataset provided by the author: https://github.com/Hans1984/GlowGAN/issues/1#issuecomment-1822347862.
After nearly 1000kimg, the output image tends to be blank white images. To be more specific, the change in FID is as follows:

I am wondering if you have solved the problem. Thank you!

After a detailed discussion in the email, Ahmad’s issue was that he trained directly at a resolution of 256×256. However, StyleGAN-XL requires progressive training, starting from 16×16 and 32×32, up to 256×256. By making this adjustment, he was able to train successfully. I hope this is helpful to you.

Thanks for your immediate reply! I encountered the same problem you mentioned. I suspect this must be the issue.
As a further question, how did you process the dataset into a smaller size? Did you resize it directly or use more complex preprocessing methods?
Thank you again for your immediate and helpful response!

Oh, maybe I can refer to the preprocessing method used in StyleGAN-XL.

I don’t think complex downsampling is necessary. You can refer to the original paper.

Thank you very much for your prompt reply.


Module Assessment

This is the core service of Assessment.

I have developed this Service @mqpasta closing this issue