WS transport error: unexpected opcode when calling set_code()

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
Our runtime devnet chain is actually on polkadot-v0.9.38, and we added some new pallets to the runtime.
The chain is working well when using the native runtime in a development environment.
When we try to upgrade the runtime on the devnet, after signing the transaction, the node is just closing the connection with the following message:
ws transport error: unexpected opcode: Continue:
The runtime WASM blob is the compressed one and is about 1.2Mb.
Any idea on what is happening here ? I've found nothing talking about this one.
Steps to reproduce
No response

Hello @niklasad1, sorry for the late reply we wasn't focused on the problem but it does still happen and we can't actually upgrade our runtime cause of this.
We are transmitting the transaction via polkadot-js, from this url:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-test.allfeat.io#/sudo
We also tried directly from the extrinsics tab with a sudo unchecked weight call into a system.setCode() call but the same thing happen.
The node is run from this command:
cargo run --release -- --base-path /mnt/symphonie_storage/  --chain symphonie --validator --name Symphonie01 --rpc-cors all
(on the master branch of [our node/runtime repo](https://github.com/Allfeat/Allfeat - The upgraded wasm blob is compiled from the remove-tokens-pallets branch))
there aren't much informations from the logs also, u'll find it in the linked file l_og.txt_, just search for the error keyword cause yeah that's noisy.
log.txt

Update from various tests that I just did:
It happen on any extrinsic if I upload a file for a Bytes input.
It does work if the file have a really tiny size, but start to happen if the file exceed ~500Kb or ~600Kb...

Ok thanks for the update, it's could something that occurs if a websocket message are sent by several TCP packets but weird that it differs between chains.

Kinda weird that it was never reported before also, it seems like I'm the only one having this issue for such a critical feature. I tested on differents computers/browsers and the problem always occurs the same.

I have captured TCP packets from my client side with input and output to the node during the wasm extrinsic upload.
Not a network expert tho so maybe you could check if u see anything abnormal ?
I guess the sending begin on frame ~15 and the node close connection on frame ~2166
wasm_payload_upload_to_node1.pcapng.zip

Got it to work, tried on a higher quality network and it worked !
Guess is that my poor quality network was causing too much TCP packets being lost as we can notice on the captures I posted and causing soketto to misread the ws message.


Investigate if React.lazy helps with bundle

In an app we could use React.lazy to load components in separate bundles. However since this is a library that gets compiled down to es6 im not certain that the code will still be split.
if it is we should look at lazy load on the modal screens

Tried it out. It does not help. as i suspected npm modules cant really use async import internally. it gets converted to sync.


'NSInternalInconsistencyException', reason: 'Failed to initialize IO ports for device IO client.'

Hi all
Bluepill is great tool for running tests in parallel, but I've got pretty weird error while starting iPhone simulators. Meanwhile it runs perfectly well on iPad. Any ideas on what is causing this issue?
[  INFO  ] Using xctestrun configuration
[  INFO  ] This is Bluepill v2.1.0-21-gb0944ab
[  INFO  ] Running with 2 simulators.
[  INFO  ] Packed tests into 3 bundles
[  INFO  ] Started Simulator 1 (PID 6902).
[  INFO  ] (BP-1) Running Tests. Attempt Number 1.
[  INFO  ] (BP-1) [Attempt 1] Create Simulator
[  INFO  ] 1 Simulator still running. [1]
[  INFO  ] Using 189 of 2048 processes.
[  INFO  ] Started Simulator 2 (PID 6923).
[  INFO  ] (BP-2) Running Tests. Attempt Number 1.
[  INFO  ] (BP-2) [Attempt 1] Create Simulator
[  INFO  ] (BP-1) Starting SimulatorScreenshotService for device:362A073F-EFC4-4B64-8265-B43494A55853
[  INFO  ] (BP-1) Booting a simulator without launching Simulator app
[  INFO  ] (BP-2) Starting SimulatorScreenshotService for device:15476C05-CD96-4F05-8102-ABE7271FE26B
[  INFO  ] (BP-2) Booting a simulator without launching Simulator app
 bp[6923:26705] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
 bp[6902:26784] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
 bp[6902:26697] *** Assertion failure in -[SimDeviceIOClient ioPorts](), /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-494.33/CoreSimulator/SimDeviceIOClient.m:62
 bp[6923:26757] *** Assertion failure in -[SimDeviceIOClient ioPorts](), /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-494.33/CoreSimulator/SimDeviceIOClient.m:62
 bp[6923:26757] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to initialize IO ports for device IO client.'
 *** First throw call stack:
 (
 	0   CoreFoundation                      0x00007fffc267357b __exceptionPreprocess + 171
 	1   libobjc.A.dylib                     0x00007fffd78d21da objc_exception_throw + 48
 	2   CoreFoundation                      0x00007fffc2678132 +[NSException raise:format:arguments:] + 98
 	3   Foundation                          0x00007fffc4147da6 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
 	4   CoreSimulator                       0x000000010bf69dc1 -[SimDeviceIOClient ioPorts] + 412
 	5   SimulatorKit                        0x000000010c1aff67 +[SimDeviceFramebufferService portForDisplayClass:io:] + 98
 	6   SimulatorKit                        0x000000010c1b1581 __54-[SimDeviceFramebufferService registerClient:onQueue:]_block_invoke.194 + 220
 	7   libdispatch.dylib                   0x00007fffd8186524 _dispatch_call_block_and_release + 12
 	8   libdispatch.dylib                   0x00007fffd817d8fc _dispatch_client_callout + 8
 	9   libdispatch.dylib                   0x00007fffd81939a0 _dispatch_queue_serial_drain + 896
 	10  libdispatch.dylib                   0x00007fffd8186306 _dispatch_queue_invoke + 1046
 	11  libdispatch.dylib                   0x00007fffd817f6b5 _dispatch_root_queue_drain + 476
 	12  libdispatch.dylib                   0x00007fffd817f48c _dispatch_worker_thread3 + 99
 	13  libsystem_pthread.dylib             0x00007fffd83cc5a2 _pthread_wqthread + 1299
 	14  libsystem_pthread.dylib             0x00007fffd83cc07d start_wqthread + 13
 )
 libc++abi.dylib: 2018-03-21 17:31:03.666 bp[6902:26697] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to initialize IO ports for device IO client.'
 *** First throw call stack:
 (
 	0   CoreFoundation                      0x00007fffc267357b __exceptionPreprocess + 171
 	1   libobjc.A.dylib                     0x00007fffd78d21da objc_exception_throw + 48
 	2   CoreFoundation                      0x00007fffc2678132 +[NSException raise:format:arguments:] + 98
 	3   Foundation                          0x00007fffc4147da6 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
 	4   CoreSimulator                       0x000000010eb84dc1 -[SimDeviceIOClient ioPorts] + 412
 	5   SimulatorKit                        0x000000010edcaf67 +[SimDeviceFramebufferService portForDisplayClass:io:] + 98
 	6   SimulatorKit                        0x000000010edcc581 __54-[SimDeviceFramebufferService registerClient:onQueue:]_block_invoke.194 + 220
 	7   libdispatch.dylib                   0x00007fffd8186524 _dispatch_call_block_and_release + 12
 	8   libdispatch.dylib                   0x00007fffd817d8fc _dispatch_client_callout + 8
 	9   libdispatch.dylib                   0x00007fffd81939a0 _dispatch_queue_serial_drain + 896
 	10  libdispatch.dylib                   0x00007fffd8186306 _dispatch_queue_invoke + 1046
 	11  libdispatch.dylib                   0x00007fffd817f6b5 _dispatch_root_queue_drain + 476
 	12  libdispatch.dylib                   0x00007fffd817f48c _dispatch_worker_thread3 + 99
 	13  libsystem_pthread.dylib             0x00007fffd83cc5a2 _pthread_wqthread + 1299
 	14  libsystem_pthread.dylib             0x00007fffd83cc07d start_wqthread + 13
 )
 terminating with uncaught exception of type NSException
 libc++abi.dylib: terminating with uncaught exception of type NSException
 [  INFO  ] Simulator 1 (PID 6902) has finished with exit code 6.
 [  INFO  ] Simulator 2 (PID 6923) has finished with exit code 6.
 [  INFO  ] PID 6902 exited 6.
 [  INFO  ] PID 6923 exited 6.

What version of Xcode are you using?

XCode version 9.2 (9C40b)

Bluepill v2.1.0-21-gb0944ab (the version you're using), won't work with Xcode 9.2. You need the latest release v(2.2.0).

I'm using master branch and built bluepill from there. Isn't v2.2.0 merged to master?
Also, it works well with xcode 9.2, I have all tests running and passing on iPad, it only fail to create simulators for iPhone which is super weird.

I've also tried with released version 2.2.0
Same error for iPhone :(
16:03:39 {47976} 20180322.160339 [  INFO  ] Using xctestrun configuration
16:03:39 {47976} 20180322.160339 [  INFO  ] This is Bluepill v2.2.0
16:03:39 {47976} 20180322.160339 [  INFO  ] Running with 2 simulators.
16:03:39 {47976} 20180322.160339 [  INFO  ] Packed tests into 3 bundles
16:03:39 {47976} 20180322.160339 [  INFO  ] Started Simulator 1 (PID 47996).
16:03:40 {47996} 20180322.160340 [  INFO  ] (BP-1) Running Tests. Attempt Number 1.
16:03:40 {47996} 20180322.160340 [  INFO  ] (BP-1) [Attempt 1] Create Simulator
16:03:40 {47976} 20180322.160340 [  INFO  ] 1 Simulator still running. [1]
16:03:40 {47976} 20180322.160340 [  INFO  ] Using 186 of 2048 processes.
16:03:40 {47976} 20180322.160340 [  INFO  ] Started Simulator 2 (PID 48017).
16:03:41 {48017} 20180322.160341 [  INFO  ] (BP-2) Running Tests. Attempt Number 1.
16:03:41 {48017} 20180322.160341 [  INFO  ] (BP-2) [Attempt 1] Create Simulator
16:03:43 {47996} 20180322.160343 [  INFO  ] (BP-1) Starting SimulatorScreenshotService for device:80975385-25EA-43F3-926D-9D2EBD1D75F9
16:03:43 {47996} 20180322.160343 [  INFO  ] (BP-1) Booting a simulator without launching Simulator app
16:03:44 {48017} 20180322.160344 [  INFO  ] (BP-2) Starting SimulatorScreenshotService for device:AC11F86E-9DD1-4114-9886-EEBA2D3703F7
16:03:44 {48017} 20180322.160344 [  INFO  ] (BP-2) Booting a simulator without launching Simulator app
16:03:44 2018-03-22 16:03:44.437 bp[48017:458348] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
16:03:44 2018-03-22 16:03:44.437 bp[47996:458224] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
16:03:44 2018-03-22 16:03:44.438 bp[47996:458355] *** Assertion failure in -[SimDeviceIOClient ioPorts](), /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-494.33/CoreSimulator/SimDeviceIOClient.m:62
16:03:44 2018-03-22 16:03:44.439 bp[48017:458295] *** Assertion failure in -[SimDeviceIOClient ioPorts](), /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-494.33/CoreSimulator/SimDeviceIOClient.m:62
16:03:44 2018-03-22 16:03:44.439 bp[47996:458355] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to initialize IO ports for device IO client.'
16:03:44 *** First throw call stack:
16:03:44 (
16:03:44 	0   CoreFoundation                      0x00007fffc267357b __exceptionPreprocess + 171
16:03:44 	1   libobjc.A.dylib                     0x00007fffd78d21da objc_exception_throw + 48
16:03:44 	2   CoreFoundation                      0x00007fffc2678132 +[NSException raise:format:arguments:] + 98
16:03:44 	3   Foundation                          0x00007fffc4147da6 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
16:03:44 	4   CoreSimulator                       0x0000000105fe3dc1 -[SimDeviceIOClient ioPorts] + 412
16:03:44 	5   SimulatorKit                        0x0000000106227f67 +[SimDeviceFramebufferService portForDisplayClass:io:] + 98
16:03:44 	6   SimulatorKit                        0x0000000106229581 __54-[SimDeviceFramebufferService registerClient:onQueue:]_block_invoke.194 + 220
16:03:44 	7   libdispatch.dylib                   0x00007fffd8186524 _dispatch_call_block_and_release + 12
16:03:44 	8   libdispatch.dylib                   0x00007fffd817d8fc _dispatch_client_callout + 8
16:03:44 	9   libdispatch.dylib                   0x00007fffd81939a0 _dispatch_queue_serial_drain + 896
16:03:44 	10  libdispatch.dylib                   0x00007fffd8186306 _dispatch_queue_invoke + 1046
16:03:44 	11  libdispatch.dylib                   0x00007fffd817f6b5 _dispatch_root_queue_drain + 476
16:03:44 	12  libdispatch.dylib                   0x00007fffd817f48c _dispatch_worker_thread3 + 99
16:03:44 	13  libsystem_pthread.dylib             0x00007fffd83cc5a2 _pthread_wqthread + 1299
16:03:44 	14  libsystem_pthread.dylib             0x00007fffd83cc07d start_wqthread + 13
16:03:44 )
16:03:44 libc++abi.dylib: terminating with uncaught exception of type NSException
16:03:44 2018-03-22 16:03:44.439 bp[48017:458295] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to initialize IO ports for device IO client.'
16:03:44 *** First throw call stack:
16:03:44 (
16:03:44 	0   CoreFoundation                      0x00007fffc267357b __exceptionPreprocess + 171
16:03:44 	1   libobjc.A.dylib                     0x00007fffd78d21da objc_exception_throw + 48
16:03:44 	2   CoreFoundation                      0x00007fffc2678132 +[NSException raise:format:arguments:] + 98
16:03:44 	3   Foundation                          0x00007fffc4147da6 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
16:03:44 	4   CoreSimulator                       0x000000010f04edc1 -[SimDeviceIOClient ioPorts] + 412
16:03:44 	5   SimulatorKit                        0x000000010f295f67 +[SimDeviceFramebufferService portForDisplayClass:io:] + 98
16:03:44 	6   SimulatorKit                        0x000000010f297581 __54-[SimDeviceFramebufferService registerClient:onQueue:]_block_invoke.194 + 220
16:03:44 	7   libdispatch.dylib                   0x00007fffd8186524 _dispatch_call_block_and_release + 12
16:03:44 	8   libdispatch.dylib                   0x00007fffd817d8fc _dispatch_client_callout + 8
16:03:44 	9   libdispatch.dylib                   0x00007fffd81939a0 _dispatch_queue_serial_drain + 896
16:03:44 	10  libdispatch.dylib                   0x00007fffd8186306 _dispatch_queue_invoke + 1046
16:03:44 	11  libdispatch.dylib                   0x00007fffd817f6b5 _dispatch_root_queue_drain + 476
16:03:44 	12  libdispatch.dylib                   0x00007fffd817f48c _dispatch_worker_thread3 + 99
16:03:44 	13  libsystem_pthread.dylib             0x00007fffd83cc5a2 _pthread_wqthread + 1299
16:03:44 	14  libsystem_pthread.dylib             0x00007fffd83cc07d start_wqthread + 13
16:03:44 )
16:03:44 libc++abi.dylib: terminating with uncaught exception of type NSException
16:03:44 {47976} 20180322.160344 [  INFO  ] Simulator 2 (PID 48017) has finished with exit code 6.
16:03:44 {47976} 20180322.160344 [  INFO  ] Simulator 1 (PID 47996) has finished with exit code 6.
16:03:44 {47976} 20180322.160344 [  INFO  ] PID 48017 exited 6.
16:03:44 {47976} 20180322.160344 [  INFO  ] PID 47996 exited 6.
16:03:44 {47976} 20180322.160344 [  INFO  ] Started Simulator 3 (PID 48042).
16:03:45 {48042} 20180322.160345 [  INFO  ] (BP-3) Running Tests. Attempt Number 1.
16:03:45 {48042} 20180322.160345 [  INFO  ] (BP-3) [Attempt 1] Create Simulator
16:03:47 {48042} 20180322.160347 [  INFO  ] (BP-3) Starting SimulatorScreenshotService for device:89059D52-F441-43B2-BC07-94083C8EC72D
16:03:47 {48042} 20180322.160347 [  INFO  ] (BP-3) Booting a simulator without launching Simulator app
16:03:47 {48042} 20180322.160347 [  INFO  ] (BP-3) Simulator 89059D52-F441-43B2-BC07-94083C8EC72D achieved the BOOTED state Booted
16:03:47 {48042} 20180322.160347 [  INFO  ] (BP-3) Completed: [Attempt 1] Create Simulator 89059D52-F441-43B2-BC07-94083C8EC72D
16:03:47 {48042} 20180322.160347 [  INFO  ] (BP-3) [Attempt 1] Install Application
16:04:10 {47976} 20180322.160410 [  INFO  ] 1 Simulator still running. [3]
16:04:10 {47976} 20180322.160410 [  INFO  ] Using 261 of 2048 processes.
16:04:28 {48042} 20180322.160428 [  INFO  ] (BP-3) Completed: [Attempt 1] Install Application
16:04:28 {48042} 20180322.160428 [  INFO  ] (BP-3) [Attempt 1] Launch Application
16:04:38 {48042} 20180322.160438 [  INFO  ] (BP-3) Launch succeeded
16:04:38 {48042} 20180322.160438 [  INFO  ] (BP-3) No error
16:04:38 {48042} 20180322.160438 [  INFO  ] (BP-3) Completion block for launch
16:04:38 {48042} 20180322.160438 [  INFO  ] (BP-3) Calling completion block with: (null) - 48180
16:04:38 {48042} 20180322.160438 [  INFO  ] (BP-3) Completed: [Attempt 1] Launch Application
16:04:39 {48042} 20180322.160439 [  INFO  ] (BP-3) Got proxy channel request from test bundle

Tests works well when debugging from xcode. Sometimes tests also just work with no reason and crash on next run. Could it be something with SimulatorScreenshotService? Like, when trying to start it there is some racing condition and some network ports are already in use by another simulator instance?

What are the steps to reproduce the error?
I think your hypothesis makes sense as I see:
16:03:43 {47996} 20180322.160343 [  INFO  ] (BP-1) Starting SimulatorScreenshotService for device:80975385-25EA-43F3-926D-9D2EBD1D75F9
16:03:43 {47996} 20180322.160343 [  INFO  ] (BP-1) Booting a simulator without launching Simulator app
16:03:44 {48017} 20180322.160344 [  INFO  ] (BP-2) Starting SimulatorScreenshotService for device:AC11F86E-9DD1-4114-9886-EEBA2D3703F7
BP-1 and BP-2 try to start SimulatorScreenshotService at the same time.

Thanks for the info! Have you tried to turn the SimulatorScreenshotService off using "screenshots-directory" flag and see if it still happens?

Well, we need those screenshots, but I will give it a try to see what will happen.

You may want to delete all the simulators and restart the node, then try again. Let me know if you still have issues.

Deleting all simulators and restarting node helped. I got it all running without screenshots. Thanks for valuable advice!!!!
Next step I'm planning to take: running is all with screenshots ON.

Hi Pavlo, I have the same issue "CoreSimulatorService connection interrupted.  Resubscribing to notifications."
I'm trying to figure out a solution, but no luck. As you say, it can be a problem with the screenshots. Now, I'm going to disable them. Is it possible that you can help me with a definitive solution?
Many thanks!

I went long and I'm afraid that it's also a bit wrong path :)
So, I've added sleep(30); to https://github.com/linkedin/bluepill/blob/master/Bluepill-runner/Bluepill-runner/BPRunner.m#L265. This gives first simulator 30 seconds to start before even trying to start second simulator. From what I think: SimulatorScreenshotService is failing to start on second simulator because some network port is just being taken by first simulator. So, straight-forward sleep solved that issue for me.

Thank you very much for the help @PavloBasiuk. I applied the change and so far it has worked excellently 👍

@rocker1976 - can you make a PR with those changes? So, it will be in main branch :)

@PavloBasiuk
Today I've received two times the error: CoreSimulatorService connection interrupted.  Resubscribing to notifications.
Here the log 1:
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) All Tests Completed.
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) DTXConnection disconnected.
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) Socket transport disconneted
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) BPDEBUGGING finished
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) [Attempt 1] Delete Simulator
20:27:16 {37225} 20180819.132717 [  INFO  ] (BP-3) Shutting down Simulator
20:27:16 2018-08-19 13:27:17.859 bp[37372:204967] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:27:17 2018-08-19 13:27:17.861 bp[37523:201041] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:27:17 2018-08-19 13:27:17.862 bp[37665:204764] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:27:17 2018-08-19 13:27:17.862 bp[37225:200835] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:27:17 {37372} 20180819.132718 [  ERROR ] (BP-4) Launch application during UI tests failed Error Domain=NSMachErrorDomain Code=-308 "(ipc/mig) server died"
20:27:17 {37372} 20180819.132718 [  INFO  ] (BP-4) Daemon connection Disconnected.
20:27:17 {37372} 20180819.132718 [  INFO  ] (BP-4) DTXSocketTransport disconnected
20:27:17 {37225} 20180819.132718 [  ERROR ] (BP-3) Shutting down Simulator failed: Error returned in reply: Connection interrupted
20:27:17 {37225} 20180819.132718 [  ERROR ] (BP-3) Completed: [Attempt 1] Delete Simulator E397D094-D780-40C5-9E7F-A5A37F476ECA
20:27:17 {37225} 20180819.132718 [  ERROR ] (BP-3) Error returned in reply: Connection interrupted
20:27:17 {37225} 20180819.132718 [  INFO  ] (BP-3) No more tests to run.
Here log 2:
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) All Tests Completed.
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) Socket transport disconneted
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) DTXConnection disconnected.
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) BPDEBUGGING finished
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) [Attempt 1] Delete Simulator
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) Shutting down Simulator
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) Daemon connection Disconnected.
20:33:49 {36401} 20180818.133350 [  INFO  ] (BP-2) DTXSocketTransport disconnected
20:33:49 2018-08-18 13:33:50.477 bp[36902:203336] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:33:49 2018-08-18 13:33:50.477 bp[36532:205171] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:33:49 2018-08-18 13:33:50.479 bp[36663:219288] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:33:49 2018-08-18 13:33:50.480 bp[36401:221186] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:33:49 2018-08-18 13:33:50.985 bp[36767:217194] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
20:33:49 {36532} 20180818.133351 [  INFO  ] (BP-3) Daemon connection Disconnected.
20:33:49 {36532} 20180818.133351 [  INFO  ] (BP-3) DTXSocketTransport disconnected
20:33:49 {36767} 20180818.133351 [  INFO  ] (BP-5) DTXSocketTransport disconnected
20:33:49 {36767} 20180818.133351 [  INFO  ] (BP-5) Daemon connection Disconnected.
20:33:49 {36767} 20180818.133351 [  INFO  ] (BP-5) DTXConnection disconnected.
20:33:49 {36767} 20180818.133351 [  INFO  ] (BP-5) Socket transport disconneted
20:33:49 {36663} 20180818.133351 [  INFO  ] (BP-4) DTXConnection disconnected.
20:33:49 {36663} 20180818.133351 [  INFO  ] (BP-4) Socket transport disconneted
Could you please confirm if I put the sleep sentence in the right place?
File: BPRunner.m
Code:
[task launch];
@synchronized(self) {
[taskList addObject:[NSString stringWithFormat:@"%lu", taskNumber]];
[self.nsTaskList addObject:task];
[bundles removeObjectAtIndex:0];
[BPUtils printInfo:INFO withString:@"Started Simulator %lu (PID %d).", taskNumber, [task processIdentifier]];
sleep(30);       <---  New line
launchedTasks++;
}
}
sleep(1);
if (seconds % 30 == 0) {


Sever Memory Leak Issues on Production

Current behavior
1. Images — only requests to image resources
Very high cpu and memory usage when requesting images to the server, it manages to serve 239 req/s and response time skyrockets to 2000ms.

2. PWA — only requests to urls
This test only made requests to urls like /es or /modelo-mahou-bears.html?color=azul. Basically homepage, category views and product views very high cpu and memory usage and server struggles to serve a very low number of requests. Response time of curl to homepage url is about 2.3s after clearing cache and about 0.7s with cache hit.
First test was made with 20 Virtual users, and the server just managed to cope with the traffic.  Server managed to serve 17req/s with an average res. time of 286.28ms

Second test was made with 50 virtual users and server was struggling and finally run out of resources.

Also, memory is leaking as node processes increase in memory usage with each request (to 1-1.5GB quickly). This was initially causing our servers to run out of memory and restart
We have mitigated this by configuration in our process manager (Phusion Passenger), by setting up the min and max node processes and also using the passenger_max_requests which shuts down processes when they reach X number of requests, which we have configured to 2000 requests/process.
This has prevented servers running out of memory and now usage is stable as processes are continuously recycled. However, we know this is a workaround and we should find the source of the memory leak/s.
This is 2 tests compared — 1 with 30 Virtual Users and another with 100 Virtual Users

Expected behavior
We'd expect the PWA to perform as described here https://medium.com/the-vue-storefront-journal/vue-storefront-performance-tests-and-architecture-ready-for-traffic-peaks-279c4c783412
Steps to reproduce the issue
We used http://k6.io/ for stress tests.
Repository

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[x] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: Irrelevant
OS: Ubuntu
Node: 10.x
Code Version: 1.10

Staging server
Staging server where the tests above have been performed has 8 CPUs / 16GB RAM and it is used for M2 + VSF PWA +  VSF API + ElasticSearch.
Production server
Similar tests have been done in production with only slightly better results.
W1/W2: 8 cpus + 12GB RAM — each in charge of pwa + vsf api + magento api

Hi @allozaur. I'm not sure if this is a bug. The memory leaks usually came from the theme/custom modules and VSF1.10/1.11/1.12 don't have the known memory leaks in the default theme at the moment. Check the mixins and other features commonly known for making our life harder with the memory leaks, please.
Please make sure you're running a sufficient number of concurrent processes as Node.js is threadless and too heavy concurrent traffic can lead to deadlocks.
Another option is to use [Varnish Cache])(https://docs.vuestorefront.io/guide/cookbook/checklist.html#_17-vsf-cache-varnish), Fastly or OpenResty with LuaProxy with SSR cache enabled - for both VSF-API and VSF.
Then you might want to disable SSR at all (as it's the main reason for slow responses): https://github.com/DivanteLtd/vue-storefront/issues/4089

Hi all, I am from the Jimmy Lion team.  First of all thanks for your help!
I just performed a tests with default vsf 1.10.0 code with default theme in our test server.
Test made concurrent requests to this url https://staging.jimmylion.com/es
This are the results:

This is the evolution of the memory consumption by the node processes in charge of the pwa:
before test started

1 minute into test

2 minutes into test

3 minutes into test

4 minutes into test

5 minutes into test

a few seconds after test ended:

As you can see, memory keeps building up in processes and seems that it is not liberated
If I keep the test running 1-2 minutes more the server runs out of memory and restarts
This tests have been made disabling the passenger_max_requests (per process) which we have set in production to control the memory usage
@pkarw what do you thing about this results?
I will. repeat tests with 1.10.6 now

Repeated test with vsf 1.10.6 and got very similar results.  Did not appreciate a performance boost and memory still gets accumulated in node processes
test with 1.10.0 (blue) and 1.10.6 (green) compared:

This is the evolution of the memory consumption by the node processes in charge of the pwa:
before test started

1 minute into test

2 minutes into test

3 minutes into test

4 minutes into test

5 minutes into test

So we did a last test using pm2 as a process manager (instead of Phusion Passenger) and results were very similar (actually a little worst)
This was the memory per process about 4 minutes after the test, when the server restarted because it run out of memory:

We increased the max_memory_restart in. ecosystem.json to 2G so we could test the memory leak

We're experiencing the same issue in production using Vue storefront with the Capybara theme, elasticsearch and Magento. We currently have a restart policy set for the storefront container as workaround.
I will keep an eye on this thread and will add to it if I have new insights.

@lukeromanowicz can we do a leak-testing on 1.10 and then 1.11, 1.12 on the default-theme first and then 1.12 with Capybara?

From 1.10 we've got some fixes in regards to memory leaks already applied - not sure if this would be helpfull here but I'm just pasting it for a reference: https://github.com/DivanteLtd/vue-storefront/pulls?q=is%3Apr+memory+is%3Aclosed

@pkarw found the cause, it was the dynamicConfigReload setting.
This setting is causing memory leaking both in 1.10.0 and 1.10.6 with default theme

@pablogiralt thanks for your insight into this issue. I think we should rethink implementation of dynamicConfigReload. We use hacky way to reload config
    const cachedConfigModule = require.cache[require.resolve('config')]
    if (cachedConfigModule) {
      delete cachedConfigModule.parent.children
      delete require.cache[require.resolve('config')]
    }
    config = require('config') // reload config

Maybe we should pass updated config into request context https://github.com/DivanteLtd/vue-storefront/blob/lts-1.10/core/scripts/server.js#L173 and then updated config will be only in vuex state :thinking: But config module will be untouched.

@gibkigonzo you are welcome. Thanks for your help too

In addition to the above for Capybara users, the following also helped in resolving our memory leak issue:
https://github.com/DivanteLtd/vsf-capybara/pull/420

@gibkigonzo thats not a bad idea however most of users custom code use “import config from “config”” and this hack was imposed to keep the dynamic config reload compatible with this old semantic. I’m wondering if we could somehow maybe return just a Vuex state config reference from the “config” module in order to implement what you suggested?

There was one more issue reported by @pablogiralt in regarding to that

Seemingly when the dynamic config is off the cacheInvalidationHandler (core/scripts/server.ts) doesn’t have access to the invalidation key config variable.
There was suggestion on slack to turn the dybamicConfigRelod off by default so we just need to make sure this cache invalidation works fine when it’s disabled ok?

@gibkigonzo I’ve looked at it a little bit and I think the problem is cause because we’re using require clause for re-loading the config https://github.com/DivanteLtd/vue-storefront/blob/4f74dc61e0c96e799ea8fbc81fb786c2a2d0828c/core/scripts/server.ts#L292
I mean it’s being passed via context as you suggested and the is merged into config used by the fronted day app in here (assign): https://github.com/DivanteLtd/vue-storefront/blob/4f74dc61e0c96e799ea8fbc81fb786c2a2d0828c/core/client-entry.ts#L20
After this asssign, because “import config from config” returns just a singleton (for the frontend app the config is generated as json file by webpack: ) all subsequent imports from config returns this, modified object
This assignment is in the clien-entry so it’s rather not the reason of the leak. It must be the way we re-load config in server.ts
The thing is that while in the client layer the config is just json file (it’s generated here: https://github.com/DivanteLtd/vue-storefront/blob/c80a1351c7d5c9e35434b1ed89fff2fc24084871/core/scripts/generate-files.ts) in the server.ta we are using node-config module with all its logic to process configs: https://github.com/lorenwest/node-config
Probably we can change the way we load config from:
https://github.com/DivanteLtd/vue-storefront/blob/lts-1.10/core/scripts/server.js#L173
To: https://github.com/lorenwest/node-config/wiki/Using-Config-Utilities#loadfileconfigsdirectory
Or jus reading just the configs as raw json, merging them together (at least: default->local->production in this sequence) and then merging back into node-config
Please try out this way guys and if it solves the issue prepare a PR

Seems #4655 fixes the issue for us.
Not sure if changing config in runtime still works with this change, as we do not use this at the moment


[Candidate 2v2 Oil Carnage ZH v1] Some rocks float above terrain

Observed behaviour
Some rocks float above terrain.
Expected behavior
Rocks sit tight on terrain.
Screenshots

thx fixed

all fixed all send it to u via discord

There are still some left.

Still one left

i ll send again then

Looks unchanged to me.


storageos: Add etcd mTLS support

This adds etcd mTLS support in the storageos deployment.
Also moves the constants and functions used in daemonset from deploy
file to daemonset file.

Rebased.

I've tested the changes and they work.


Inheritance of events is broken on IE11

The following test was passed before using your polyfill.
Note: ev is a click event object.
IE 11.0.0 (Windows 7 0.0.0) Unit: lib/dom bind click FAILED
        AssertionError:   #

          assert(ev instanceof Event)
                 |  |          |
                 |  false      #function#
                 PointerEvent{}

@falsandtru hi, thanks for reporting this.  I don't recognise this test, is this a third party test suite?  Can you give us a live example URL at which to run the test?  We ideally are looking for a test that includes only code from our service and as little code as possible to reproduce the issue.

Thanks for replying. Here is a test. Can you repro?
Note: I'm using Mocha and power-assert for tests.
    it('click', done => {
      const a = document.createElement('a');
      a.addEventListener('click', ev => {
        assert(ev instanceof Event);
        done();
      });
      document.createDocumentFragment().appendChild(a);
      a.click();
    });

That really doesn't give me all the info I need.  For example I don't know what polyfills you're loading.  A live test URL is the best way for me to help you here.  Could you use a tool like JSBin to demo the problem?

Okay. http://jsbin.com/ludihajufu/1/edit?html,console

Ah, OK. So in IE11, the Event object is not a constructor, so you can't do new Event. This is fixed by the polyfill, but a side effect is that because it redefines Event, the prototype chain between constructors that inherit from Event and the Event object is broken, so your PointerEvent instance is no longer an instance of Event.  I think I can fix this with https://github.com/Financial-Times/polyfill-service/pull/713.
What do you think?

It works fine :+1:


[Potential Bug] export dynatrace_iam_group return empty result

Describe the bug
After following the Terraform documentation to configure the required provider and Dynatrace provider (dt_env_url, dt_api_token, iam_client_id, etc.) and calling the exporter by:
.\.terraform\providers\registry.terraform.io\dynatrace-oss\dynatrace\1.35.2\windows_amd64\terraform-provider-dynatrace_v1.35.2.exe -export dynatrace_iam_group
we receive the following output in the terminal:

Post-Processing Resources ...
Writing ___resources___.tf
Writing ___datasources___.tf
- dynatrace_iam_group
Writing main.tf
Writing ___variables___.tf
Writing ___providers___.tf
Executing 'terraform init'

and also we get the following files in the (default) output directory:

It seems that we do not receive the resources and we double checked the scope for the OAuth Client. We do have the required scope as stated in prerequisites.
Expected behavior
The resources in the specific output directory.
Desktop (please complete the following information):

OS: Windows
Version: Windows 10 Enterprise 22H2

Hello @arnauagithub,
Let's check whether this is perhaps a simple configuration issue. The export functionality requires environment variables to be set. The example shown in prerequisites isn't particularly clear about that, I'm afraid.
So, before executing terraform-provider-dynatrace_v1.35.2.exe -export dynatrace_iam_group you should have the following environment variables defined.
DT_CLIENT_ID=dt####.########
DT_ACCOUNT_ID=urn:dtaccount:########-####-####-####-############
DT_CLIENT_SECRET=dt####.########.################################################################

The prefix urn:dtaccount: for DT_ACCOUNT_ID is meanwhile optional, but it doesn't hurt to add it for diagnosis.
In addition to that you can also define the environment variables
DYNATRACE_DEBUG=true
DT_DEBUG_IAM_BEARER=true

which would produce a log file with additional information regarding oauth communication.
If none of that helps, I can offer to jump on a zoom call with you where we can figure out the root case here together. Feel free to reach out to us via<EMAIL_ADDRESS>if that's an option for you.
best regards,
Reinhard

Dear Reinhard,
thank you very much for the information. We used the DT_CLIENT_ID, DT_ACCOUNT_ID and DT_CLIENT_SECRET and also added the urn:dtaccount: for DT_ACCOUNT_ID.
Now it works!
Please add this to the documentation.
Thank you very much and best regads,
Arnel


SEC_ERROR_REUSED_ISSUER_AND_SERIAL Secure Connection Failed

Description
Firefox displaying SEC_ERROR_REUSED_ISSUER_AND_SERIAL error when attempting to connect to the openshift console.
Environment
Operating system: Fedora release 28 (Twenty Eight)
OpenShift versions:
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://<IP_ADDRESS>:8443
openshift v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657

Steps to reproduce
While following the instructions at: https://docs.aerogear.org/aerogear/latest/getting-started.html#prerequisites

oc cluster up
git clone https://github.com/aerogear/mobile-core.git
cd mobile-core
git checkout 1.0.0
./installer/install.sh
opened https://<IP_ADDRESS>:8443/console/ in Firefox 61.0

HI @davidkirwan,
Thanks for your feedback. This repo is now deprecated and is replaced by Mobile Developer Console. Could you please give it a try and if you still experience the same problem, please open a new issue in that project.
Thanks.


Remove api segment from enable api url

The change in #2198 left a trailing /api/ segment in the enable API links (see #2195). This removes it.

Codecov Report

Merging #2230 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2230   +/-   ##
=========================================
  Coverage     86.89%   86.89%
  Complexity     5122     5122
=========================================
  Files           452      452
  Lines         20304    20304
  Branches       2175     2175
=========================================
  Hits          17643    17643
  Misses         1892     1892
  Partials        769      769

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 8f95d3b...310c03f. Read the comment docs.


ISS-492 added support for yaml as step file

ISSUE-492 added support for yaml as step file
This is a PR in response to #492
Checklist:

[x] Unit tests added

[ ] Integration tests added

[x] Test names are meaningful

[x] Feature manually tested

[ ] Branch build passed

[x] No 'package.*' in the imports

[ ] Relevant Wiki page updated with clear instruction for the end user

[ ] Not applicable. This was only a refactor change, no functional or behaviour changes were introduced

[ ] Http test added to http-testing module(if applicable) ?

[x] Not applicable. The changes did not affect HTTP automation flow

[ ] Kafka test added to kafka-testing module(if applicable) ?

[x] Not applicable. The changes did not affect Kafka automation flow

#492


Indentation issues

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: macOS 14.4.1
- Continue: 0.8.23
- IDE: VSCode 1.87.2
- Ollama v0.1.29

Description
I have a problem with indentations, somehow continue breaks indentation when I try to edit / generate code. The model provides correct code but it is not applied correctly. I hope the attached movie explains the issue better than words :)
https://github.com/continuedev/continue/assets/95582824/69883496-4a08-458f-a91b-d568052f8794
I tried adjusting VS code settings regarding indentations, tabulations, paste formatting - nothing helped.
[edit] Changed .mov to .mp4 movie format
To reproduce

create new python file
CMD+I (ask Continue to generate new code)
enter simple prompt "generate fibonacci sequence"
all "elif" statements and "else" statement are indented too far

Log output
No response

@PawelSzpyt thanks for the clear video! I have a few improvements on the way for cmd+I that should clean this up

i have same bug with v0.9.202 (pre-release) version. it also appears when using "Optimize this Code" shortcut.

@vills what LLM are you using? This seems very much to be a model-specific problem

@sestinj Tried both gpt-4o and gpt-4o mini. Also tried llama3.1 and mistral-nemo through Ollama. And claude sonnet. With all this models indent issue persist.


[UX Improvement] Connection list improvement

[User Story]
As a Monitor, I want to, for a single address space, view all connections along with their authenticated identity, age, last activity time, ingress/egress rates, and protocol
[Task]
Provide a design proposal for the connection list usability improvement

Firstly improve aesthetics and usabilities based on the current functions, wireframe can be found here: https://redhat.invisionapp.com/share/WDOQSTTPU7J Reference #1847


Issue with HQ UK

There was an issue today with HQ UK. The questions were pulled successfully, but there were no results.
`Question detected.
Question 12 out of 12
Which of these countries has NEVER been invaded by Great Britain?
['Cuba', 'Vietnam', 'Paraguay']
Searching
['Cuba', 'Vietnam', 'Paraguay']
['countries', 'never', 'invaded', 'great', 'britain']
[]
Running method 1
{'cuba': 0, 'vietnam': 0, 'paraguay': 0}
Running method 2
{'Cuba': {'cuba': 0}, 'Vietnam': {'vietnam': 0}, 'Paraguay': {'paraguay': 0}}
[('Which', 'NNP'), ('of', 'IN'), ('these', 'DT'), ('countries', 'NNS'), ('has', 'VBZ'), ('NEVER', 'RB'), ('been', 'VBN'), ('invaded', 'VBN'), ('by', 'IN'), ('Great', 'NNP'), ('Britain', 'NNP'), ('?', '.')]
Question nouns: ['great britain']
Running method 3
Search processed
URLs fetched
Cuba: {}
Vietnam: {}
Paraguay: {}
Keyword scores: {'Cuba': 0, 'Vietnam': 0, 'Paraguay': 0}
Noun scores: {'Cuba': 0, 'Vietnam': 0, 'Paraguay': 0}
Search took 1.0620067119598389 seconds
Socket closed`

Does UK version work on Android platform? I tried to download but got the us version

You need a uk phone number i believe

did you just use a uk user id and bearer token to get the questions to pull? I'm trying to run this as well

Very weird issue, I will look into it. Is it specific to UK or does this happen on both?


OAK-10741 : updated logs for fullGc

Not sure if enabling this in general would be a good option, I worry it could be very verbose when running any other oak-run command. Wouldn't be better if we add a new argument like --debug to fullGC commands that enable the logging?

@Joscorbe I have updated the log to INFO for fullGc.


Add Teletrace to the landscape

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Hi @taylorwaggoner - can you help please? It seems like the build is broken?

@ranrib the deploy preview looks correct to me, but you need to correctly sign off for the DCO check to pass https://github.com/cncf/landscape/pull/3175/checks?check_run_id=13193752052

Thanks.
LGTM


Standup Internal instance of Retrospected

Description:

Team agreed to use this tool moving forward.  To ensure data privacy, we need to stand up a private instance within our team.

Service is deployed to helium in AKS and s secured with Valid SSl cert
LINK


Moldova 2

Source
https://trm.md/ro/moldova-2
Channels
Moldova2.md
Notes
No response

Same as in #1682


Livestream: stop pinned comments from appearing as latest

Ticket
Closes #6879: Previously pinned livestream comments show as latest
Issue
comment.List will always display the pinned comment first, hence the problem when the chat is refreshed.
Approach
Completely split pinned comments from top-level comments in the Reducer, and the let the GUI (e.g. regular comments, livestream comments) decide how they want to display it.
For the case of livestream, there is no need to repeat the pinned comments in the regular chat area, since there is a dedicated area on top.

LGTM!
It is kind of strange that the other pinned comments disappear from the list, but I think that's okay / kind of expected.

Yeah, it's kind of all-or-nothing for now until comment.List has the ability to not float pinned comments to the top, so that it'll be in the correct sort order.  Briefly discussed in v3 pagination.


NetworkKey feature request

Hello AlCalzone,
Loving the library but was curious if there was a timeline on the NetworkKey feature? I would love to assist if you need a bit of developer muscle, considering this library for an IOT project at my startup. If all goes well this code would be the core of a few key integrations. I sponsored you as a first step towards hopefully a long partnership.
Sincerely,
Royce

S0 security is already implemented, just not documented. The options argument of the driver constructor has a property networkKey, which accepts a 16-byte buffer. Example:
const driver = new Driver("COM4", {
	networkKey: Buffer.from([
		// You probably shouldn't use this key:
		1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
	])
})

The beginInclusion method in the controller accepts a boolean parameter to indicate whether the inclusion should be performed non-secure. By default, if a network key is set, the driver tries to include the device securely:
// secure:
const inclusionStarted = await driver.controller.beginInclusion(/* or false */);
// non-secure:
const inclusionStarted = await driver.controller.beginInclusion(true);

Note that some devices require a different activation for secure inclusion. E.g. Aeotec devices only include the Security CC in their NIF if the button was pressed twice in a short time.

I sponsored you as a first step towards hopefully a long partnership.

Thanks for that :)

Thank you so much for the rapid response!! I will be tinkering with this over the weekend and waking up to such detailed explanations really made my day!!!

I'm going to close this thread as it seems to be a non-issue. Feel free to reopen if necessary.


Test framework and enabling libcrux tests

This PR introduces an opemls_test macro to replace the rstest approach. This allows us checking for features in the provider at runtime and thus enabling more tests, esp. for the libcrux backend (#1250).
This works towards #1543.
And even thou it looks big, it's mostly replacing the test attributes.

There's a weird issue where coverage build fails with simd instructions in libcrux. I disabled that for now in https://github.com/openmls/openmls/pull/1573/commits/28b5d448995245675d20aeb72f68dfb501b29785.
I also kept unsupported ciphersuites in the build for cross compiled tests. This is not great, but the only way for now https://github.com/openmls/openmls/pull/1573/commits/34c48a0e6045b79de02fba7d6de3da925b51f319.

I filed #1574


Sync stack - merge main.

API changes have been detected in com.azure:azure-security-keyvault-keys. You can review API changes here

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core-tracing-opentelemetry. You can review API changes here
API changes
+         @Override public HttpResponse processSynchronously(HttpPipelineCallContext context, HttpPipelineNextPolicy next)

API changes have been detected in com.azure.resourcemanager:azure-resourcemanager. You can review API changes here

API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-appservice. You can review API changes here

API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-compute. You can review API changes here

API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-containerservice. You can review API changes here

API changes have been detected in com.azure:azure-identity. You can review API changes here
API changes
-     @Immutable
-         public T identityLogOptions(IdentityLogOptions identityLogOptions)
-     }
-     @Fluent
-     public final class IdentityLogOptions {
-         public IdentityLogOptions()
-         public boolean isLoggingAccountIdentifiersAllowed()
-         public IdentityLogOptions setLoggingAccountIdentifiersAllowed(boolean allowLoggingAccountIdentifiers)


Hide notifications counter while still displaying the button

I would love to be able to hide the notification counter (i.e. the blue number displaying the number of unread notifications) while still keeping the notification icon on screen.

Use Case: I want to be able tweet out things without getting distracted in the mornings during work sessions. But seeing the notifications makes me wonder who they're from, etc. I could disable the button altogether, as that's currently an option. But I still want the button to be on screen in case I want to go through the notifications at a later time (usually in the evening).
Thank you for a great extension! ♥

No plans to do this for now, but this can potentially be done with userstyles (https://userstyles.org/) or something like Ublock Origin https://github.com/gorhill/uBlock :)


Error after latest update.

The package.json is looking for a .js file but the dist folder only contains .cjs
Error: Cannot find module<EMAIL_ADDRESS>

Can confirm that changing package.json references of index.js to index.cjs fixes this.

I can +1 this

+1
Getting same issue here

+1 same error

+1,
@thelegendtubaguy thanks for the workaround.


added if-check in JointStateSubscriber to handle fixed joints

Added if-check to JointStateSubscriber to handle case where the robot's JointState message contains a joint that does not have an associated JointStateWriter in Unity. This happens when a robot's JointState message contains fixed joints. The Baxter robot does this, for example.

The solution you posted works for me! Semantically identical, and more efficient.

That's great @dwhit !
How shall we proceed?
Do you want to update your pull request (i.e. commit my suggested changes on your fork?
.. or shall I close this pull reqest and commit these changes myself?

pull request is updated!

thank you @dwhit !


[shardformer] support sharded checkpointing IO for hybrid parallel plugin

Support checkpointing IO for hybrid parallel plugin, should handle tp/pp/zero properly. First complete the sharded case for both model and optimizer.
The feature to be implemented should include:

Sharded saving of model: saving model to multiple files under the same checkpoint directory.
Sharded loading of model: loading model from multiple files under the same checkpoint directory.
Sharded saving of optimizer: saving optimizer to multiple files under the same checkpoint directory.
Sharded loading of optimizer: loading optimizer from multiple files under the same checkpoint directory.

sharded optimizer saving & sharded optimizer loading completed:  #4540


Support setting cloud_roleName for availability testing

We have different microservices that we test for availability. All other metrics are correlated by service using the cloud_roleName property. Can this be set for availability tests?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 10858323-1827-1c73-b93a-7c133bae54ba
Version Independent ID: 3ed5fda4-c916-dcb0-a3b2-a0bb534d8bdb
Content: Monitor availability and responsiveness of any web site
Content Source: articles/application-insights/app-insights-monitor-web-app-availability.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@craigsmitham Thank you for the feedback!  We are investigating this and will get back to you shortly.

@craigsmitham I haven't been able to find anything in the documentation that would verify if this can be set specifically for availability tests.  I'm going to see if the author is able to confirm this.

That may work. We'll revisit our setup and see if there would be any potential issues with this approach.


2.0.0 with tests

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy
[x] Ensured the license file is being packaged.

Carries on with #2 (which would be dangerous to merge due to the dependency change):

fix graphql-core >=2.2,<3
add tests (based on github tag)
remove vendored license (now included in tarball)
generally modernize recipe
add self (@bollwyvl) as maintainer

@carlodri: interested in co-maintainership?

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance.

@bollwyvl thanks for the ping, I don't know if I can be of much help (I'm not a graphql user myself), so I would skip this one. However, if you want a maintenance pal, I'm happy to be thrown in!

Bringing in the src because the tests are not distributed in the pypi
tarball, and it seemed like getting some tests working would help prevent
putting out bad builds while they're bumping make revs all over the chain.
On Tue, Jul 16, 2019, 03:33 Carlo<EMAIL_ADDRESS>wrote:

@carlodri commented on this pull request.
In recipe/meta.yaml
https://github.com/conda-forge/graphql-relay-feedstock/pull/3#discussion_r303763375
:

version: {{ version }}

source:

fn: {{ name }}-{{ version }}.{{ bundle }}
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.{{ bundle }}
{{ hash_type }}: {{ hash }}

url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz

sha256: 7fa74661246e826ef939ee92e768f698df167a7617361ab399901eaebf80dce6
folder: dist

url: https://github.com/graphql-python/{{ name }}-py/archive/v{{ version }}.tar.gz

why do you need to manually pull this in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/graphql-relay-feedstock/pull/3?email_source=notifications&email_token=AAALCRH4RJIZNE4KN4B2TSDP7V2UNA5CNFSM4ID35WRKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6QVRZI#pullrequestreview-262232293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAALCRBOTRNZNM2PBJLZVPDP7V2UNANCNFSM4ID35WRA
.

And if you're not looking for more chores, @carlodri, I totally understand!
On Tue, Jul 16, 2019, 09:04 Nicholas Bollweg<EMAIL_ADDRESS>wrote:

Bringing in the src because the tests are not distributed in the pypi
tarball, and it seemed like getting some tests working would help prevent
putting out bad builds while they're bumping make revs all over the chain.
On Tue, Jul 16, 2019, 03:33 Carlo<EMAIL_ADDRESS>wrote:

@carlodri commented on this pull request.
In recipe/meta.yaml
https://github.com/conda-forge/graphql-relay-feedstock/pull/3#discussion_r303763375
:

version: {{ version }}

source:

fn: {{ name }}-{{ version }}.{{ bundle }}
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.{{ bundle }}
{{ hash_type }}: {{ hash }}

url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz

sha256: 7fa74661246e826ef939ee92e768f698df167a7617361ab399901eaebf80dce6
folder: dist

url: https://github.com/graphql-python/{{ name }}-py/archive/v{{ version }}.tar.gz

why do you need to manually pull this in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/graphql-relay-feedstock/pull/3?email_source=notifications&email_token=AAALCRH4RJIZNE4KN4B2TSDP7V2UNA5CNFSM4ID35WRKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6QVRZI#pullrequestreview-262232293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAALCRBOTRNZNM2PBJLZVPDP7V2UNANCNFSM4ID35WRA
.

ok I see your point on tests, sure!
As for the maintenance, yes, I will skip this one for the moment, thanks!

@pmlandwehr can you please merge? This is blocking updates downstream. Thanks!


psutil Error

For ipop-vpn_lnx-beta1r05 running the controller on my Ubuntu 14.04.5 laptop throws an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/vd/ipop-vpn_lnx-beta1r05/controller/Controller.py", line 32, in <module>
    main()
  File "/home/vd/ipop-vpn_lnx-beta1r05/controller/Controller.py", line 21, in main
    while checkTincanState() == False:
  File "/home/vd/ipop-vpn_lnx-beta1r05/controller/Controller.py", line 12, in checkTincanState
    if process.name().find("tincan")!=-1 or process.name() == "ipop-tincan":
TypeError: 'str' object is not callable

A quick fix for that would be:
In Controller.py lines 5-14:
# Function checks the system process table for Tincan process
def checkTincanState():
    for process in psutil.process_iter():
-       if type(process) is str:
-           if process.find("tincan")!=-1 or process == "ipop-tincan":
-               return True
-       else:
-           if process.name().find("tincan")!=-1 or process.name() == "ipop-tincan":
-               return True
    return False

# Function checks the system process table for Tincan process
def checkTincanState():
    for process in psutil.process_iter():
+       if str(process).find("tincan")!=-1 or process == "ipop-tincan":
+           return True
    return False

It was working fine right out of the box on a VM on the same laptop and also on my other machine with exactly the same operating system.
Vahid

The problem is most probably because of psutil version. The psutil on my laptop is 1.2.1 but on the other machine is 5.2.0. As far as I know, I installed both of them the same way.


Validate type of each element of array where the array has the value and required type

I have an array of attributes which represent a list of fields that the user can enter values into. Each element has a type, e.g. STRING, INTEGER, etc. I tried using vuelidate to validate that the value entered into each field corresponds with the type of that field.
In the template section I have:
<b-row v-for="(attribute, index) in userCase2" :key="attribute.name" :class="{invalid: $v.userCase2.$each[index].$error}">
       <b-col md="4" style="background-color:whitesmoke">{{ attribute.name }}: </b-col>
       <b-col md="4" style="background-color:whitesmoke">{{ attribute.type }} </b-col>

       <b-col md="4" style="background-color:whitesmoke">
                <input :class="{ error: $v.userCase2.$each[index].userValue.$error }" @input="$v.userCase2.$each[index].userValue.$touch()" v-model.number="attribute.userValue">
       </b-col>
</b-row>

And in the validation section looks like this, where, as you can see, I don't know how to address the type of each element. I have tried using $each and all sorts of variations, but to no avail.
  validations () {
    if (????=='INTEGER') {
      return {
        userCase2: {
          $each: {
            userValue: {
              required,
              numeric
            }
          }
        }
      }
    }
    else {
      return {
        userCase2: {
          $each: {
            userValue: {
              required,
              email
            }
          }
        }
      }
    }
  },

Any help will be most appreciated.

Are you trying to do something like the thing mentioned in here? https://github.com/monterail/vuelidate/issues/166#issuecomment-319924309


Cli testing, squashed, some minor improvements

This is basically pull request #193, squashed, and with recent changes merged.  It also has a minor bugfix, and has an env-var option "QUILT_TEST_CLI_SUBPROC=True", which, if set, will cause it to use subprocesses for testing, instead of the current (faster) method.

@dimaryaz after recent breakage, I asked @eode to create a framework for testing the CLI, incl catching if the CLI accidentally changes.  From here, we can add detailed CLI tests for subtle details, e.g. error messages, return codes, etc.  This is a starter projectthis and his first commit.
@eode Dima is lead eng and can get backed up with code reviews.    Thx!

Please add a short one line comment explaining the performance issue.  If
you can make it less hacky, that would great ideally moving the hacky code
from command.py to some file in test/ where hacks are (more) allowed.
On Nov 27, 2017 11:04 AM, "eode"<EMAIL_ADDRESS>wrote:

@eode commented on this pull request.
In quilt/tools/command.py
https://github.com/quiltdata/quilt-compiler/pull/198#discussion_r153291371
:

@@ -67,8 +68,19 @@

LOG_TIMEOUT = 3  # 3 seconds
-VERSION = pkg_resources.require('quilt')[0].version
+try:

VERSION = pkg_resources.require('quilt')[0].version
+except pkg_resources.DistributionNotFound:

Not installed, so we'll get the version manually.

try:

   mydir = os.path.abspath(stack()[0][1])

   pkgdir = os.path.join('/', *mydir.split(os.path.sep)[:-3])

   text = open(os.path.join(pkgdir, 'setup.py')).read()

   text = text.split('\nQUILT_VERSION = ', 1)[1]

It is super-hacky, but at the time it was written, the goal was to enable
invoking main.py from the tests directory so that pytest runs main.py,
without an install, and without creating any new files -- although, some of
those restrictions may have been made in part simply as questions on the
job description. Also, this was before I was really familiar with the
codebase, and before I had a deeper understanding of what's needed.
Calling from the CLI is technically more complete, but it's significantly
slower, and with modifications I've added to main.py, isn't absolutely
necessary. The likelihood that there will be a significant difference
between doing a syscall of ['quilt'] + quilt_args vs calling
main.argument_parser() and main.main(args) is fairly small.
I'd be happy to either store the version in a separate version file and
read that, or simply forego actual CLI calls altogether in favor of
simulated CLI calls.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/quiltdata/quilt-compiler/pull/198#discussion_r153291371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUcPVT9NCl20kYVrYFES9JmxIK01-M_ks5s6we2gaJpZM4Qqk1C
.
--
You received this message because you are subscribed to the Google Groups
"Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/a/qu
iltdata.io/d/msgid/dev/quiltdata/quilt-compiler/pull/198/rev
iew/79275976%40github.com
https://groups.google.com/a/quiltdata.io/d/msgid/dev/quiltdata/quilt-compiler/pull/198/review/79275976%40github.com?utm_medium=email&utm_source=footer
.

@quiltdata Re: One-line comment about quilt performance issue:  That's issue #194, and I've circumvented it by defaulting to not using an actual CLI call, but using main.argument_parser() and main.main(args) instead.  Commented as #NOTE: in test_cli.py.

@dimaryaz I think this is ready for a re-review.

..improved some commnets [sic].  Also, minor bugfix re: reading version using cli during Subprocess mode in test_cli.  Verified that this works with QUILT_TEST_CLI_SUBPROC both True and False.  This should be set to True on CI testing for more thorough testing of the cli.


Add incorrect-matches-operation example

I'm currently fixing some CI failures attributable to the Rust 1.73 release. So, you may not be able to fix some failures for your PR until I am done with that. Apologies.

I rebased this branch on top of latest master.


Route adds two questions marks to location

Example: http://jsbin.com/lezaqareve/1/
Click the button twice.
On the second time, the console prints "http://null.jsbin.com/runner??hello=world"

Work around is to use m.route.mode = 'pathname';

I believe this solution worked by accident.
m.route.mode = search (the default) inserts "?"
m.route.mode = hash inserts "#"
m.route.mode = pathname inserts "" (an empty string)
That empty string is there, you just can't see it :wink:
This is the signature of this particular use of m.route:
void route(String path [, any params] [, Boolean shouldReplaceHistory])
"path" should be listed in the routes object (the example doesn't create routes, it uses m.mount directly). When a routes object has been created, redirecting to a non existent path (including the empty string) fails quietly. But without a routes object, Mithril attempts to assemble a route (I assume because the path can't be checked against a non existent routes object).
I think it should be an error to call m.route with a path that is not in the routes object even when no routes object exists.
I wonder if all calls to m.route should should fail when no routes object exists.

Exactly; I looked through the source and saw that I could use 'pathname' as a workaround.
It probably should error without using a route object. The reason I'm using it like that is because it's a single page with no other routes, but I want bi-directional bindings between the url parameters and my model. I was hoping I could rely on mithril for the window.onpopstate event, but apparently can't. I'm probably using mithril outside its intended usage for this usecase.

I wonder if all calls to m.route should should fail when no routes object exists.

I reckon they should. We already have an error for when m.route.param is called before route initialisation.
Somebody once opened a ticket about the API disparity between m.route.mode and others in that this is pretty much the only Mithril API hook that allows direct setting (m.attrs[ x ] would be another ;) ) whereas the convention is to use functions to pass in the value. This could be another area to get valuable error catchment in.

I'm probably using mithril outside its intended usage for this usecase.

@Naddiseo I think if you're building anything that's more complex than TODO MVC and using Mithril's 'less core' functionality (XHR, routing, promises — basically everything that isn't about view rendering), you're going to find a need to extend or complement the API at some point.
My app deals with a host of web services and involves such things as query parameters in the URI that change as the user types. The goal (for development sanity and user convenience) is to make everything as RESTful as possible.
Because URI abstraction is difficult enough regardless of Mithril's API, I'm using URIjs (which I highly recommend — W3C URL API has nothing on this). With the number of people implicitly relying on URIs to make the Internet work and the prevalence of SPAs , you'd think getting the 2 to interop cleanly would be easy. It's not the case. URIs are hella difficult.
If you don't mind ditching users without pushState (or 'HTML5 history API') and your server can dish out the same thing I when browsers require any subpath on your app domain, then pathname is the best choice. If not, go for hash. The problem with both hash and query is that they hack / override part of the browser Location API, and the native API is ambiguous and dumb. Personally I think it's far easier to sacrifice native hash logic (scrolling into view the element whose ID corresponds with the hash string). YMMV.

@barneycarroll, here's how I got around the limitations: http://jsbin.com/purojinoho/5/edit?js,console,output
I would have preferred to use mithril for the popstate event. I'm only using it so that using history back didn't cause a page refresh, and I can have some sort of perma links.

@Naddiseo Mithril effectively uses popstate and hashchange as far as I've seen — reload has never been a problem and should be reported as a bug AFAIC. Because Mithril's default attitude to route change is that it requires a full redraw (ie trashing the whole DOM and building the next view from scratch) I've extended all my top level components to invoke m.redraw.strategy( 'diff' ) to prevent huge lags as the user types and the route updates (the controller, in turn, makes me requests based on the new route params).

@barneycarroll, it only adds the event listeners if you install with m.route($el, default, routes). I'm running into the issue that I have a variable number of search parameters, so I can't easily use pathname/hash to store the data..

For clarity: my application relies on ultra responsive search to render complex data. I have been able to render non-trivial views (ie every search result invokes its own component which renders a non-trivial view [complex nested DOM] and may make extra HTTP requests itself — all the while holding a stateful UI while being a part of an occlusion culled lazy loading list) and Mithril's routing has not blocked me in the slightest. What has blocked me is default component behaviour (destroy and rebuild the view by default — whereas I want to diff all the time), but that's another story.

@Naddiseo fancy getting on Gitter to discuss gory details? https://gitter.im/lhorie/mithril.js?at=551323bac183f73134d03e00

I think calling m.route if you mounted using m.mount falls under undefined behavior


pyright update

do we really need to update pyright?

do we really need to update pyright?

after mvp yes, old does lots of false positives
required changes will also improve typing


Edit out "new"

Edit

Docs Build status updates of commit 681a702:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 681a702:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/message-analyzer-docs-pr, working directory: W:\ibgb-s, target branch: live, target branch commit:<PHONE_NUMBER>32f37b5e724813b1d0a616dab157ce, source commit: 681a702cdfa026ade20008fa0da36623cc95aaed.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 522d46b:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 522d46b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

message-analyzer-guide/microsoft-message-analyzer-operating-guide.md
:bulb:Suggestion

Details

message-analyzer-guide/microsoft-message-analyzer-operating-guide.md

Line 22: [Suggestion] Link 'https://docs.microsoft.com/en-us/message-analyzer/opbuildpdf/toc.pdf?branch=live' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Make examples from Coffea-casa gallery to be opened directly in CMSAF (if user is allowed)

Ideally I was thinking here about similiar approach used in SWAN gallery examples, where you can open notebook directly in SWAN: https://swan-gallery.web.cern.ch/notebooks/root_primer/OldSummerStudentsCourse/2017/examples/notebooks/Macro1_cpp.html

Duplicated issue: https://github.com/CoffeaTeam/coffea-casa/issues/299 and https://github.com/CoffeaTeam/coffea-casa/issues/300


"SQLDirect" Feature

Hi,
Are you going to publish the changes you have made to allow "SQLDirect": "Update SQL Direct Query String"?
Thanks

Changes will be published in the next release this week! The extension will have an action called: Update SQL Direct Query String

Any update on this? It hasnt made it to the Marketplace yet.


Error in RestServer.php

Created a new Virtual Host, fresh install of RestServer.
Copied the example over to the root folder of the Virtual Host and got the following error.
PHP Parse error:  syntax error, unexpected '[' in /RestServer/source/Jacwright/RestServer/RestServer.php on line 250
Checked the RestServer.php on line 250 and the error makes no sense.
Any ideas?

I second that. 	$call[2] = []; makes no sense to me or my code hinter either...

'[]' is a notation for array initialization and is supported in PHP 5.4 and above. If your PHP version is less than 5.4, you can simply replace this statement by:-
$call[2] = array();

thanks farooquiyasir! I was suspecting something on those lines :-)
sorry!

Either syntax works. If you'd like to submit a PR for array(); instead of []; I'd be happy to merge it.


How to fix the dependency graph to resolve deduplicate errors ?

I'm facing some deduplicate errors like below. I'd like to resolve them cleanly by fixing my dependency graph. How can I do that ? How can I find out what libraries are importing the conflicting dependencies and is there anything I can do about it ?
An example of deduplicate errors:
[error] (assembly) deduplicate: different file contents found in the following:
[error] /home/guillaume/.cache/coursier/v1/https/repo1.maven.org/maven2/org/reactivestreams/reactive-streams-flow-adapters/1.0.2/reactive-streams-flow-adapters-1.0.2.jar:org/reactivestreams/FlowAdapters$FlowPublisherFromReactive.class
[error] /home/guillaume/.cache/coursier/v1/https/repo1.maven.org/maven2/org/reactivestreams/reactive-streams/1.0.3/reactive-streams-1.0.3.jar:org/reactivestreams/FlowAdapters$FlowPublisherFromReactive.class

Here is a list of my dependencies, if it helps:
    libraryDependencies += "com.fasterxml.jackson.core" % "jackson-databind" % "2.12.2",
    libraryDependencies += "com.novocode" % "junit-interface" % "0.11" % "test",
    libraryDependencies += "com.softwaremill.sttp.client3" %% "core" % "3.3.6",
    libraryDependencies += "com.softwaremill.sttp.client3" %% "httpclient-backend-zio" % "3.3.6",
    libraryDependencies += "dev.zio" %% "zio" % "1.0.9",
    // libraryDependencies += "dev.zio" %% "zio-streams" % "1.0.9",
    libraryDependencies += "org.apache.commons" % "commons-compress" % "1.20",
    libraryDependencies += "org.scalactic" %% "scalactic" % "3.2.9",
    libraryDependencies += "org.scalatest" %% "scalatest" % "3.2.9" % "test",
    libraryDependencies += ("tech.sparse" %%  "toml-scala" % "0.2.2").cross(CrossVersion.for3Use2_13),

We use GitHub to track bugs and todo lists. Please use Stackoverflow for general questions - https://github.com/sbt/sbt-assembly/blob/develop/CONTRIBUTING.md#where-to-file-a-bug-report

Oops, sorry about that.


[BEAM-690] Backoff in the DirectRunner if no work is available

Implementing backoff as described in the JIRA ticker for [BEAM-690]. Basically this PR:

adds new DriverState (CONTINUE_THROTTLE) that signals that no work was available
performs capped exponential backoff in the ExecutorServiceParallelExecutor when CONTINUE_THROTTLE is encountered

@tgroh , you are probably the most suitable reviewer

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

This LGTM, but I am far from a direct runner expert, so asking for a double check, for suggestions that I can be missing.
R: @ryanskraba @lukecwik

Thanks for the feedback guys. To be honest I'm no longer convinced this is the right thing to do. It does indeed decrease the CPU consumption significantly, however, at least in our case it is not enough. It turns out that even if the pipeline is completely empty, the driver goes
THROTTLE, THROTTLE, CONTINUE, THROTTLE, THROTTLE, CONTINUE, ... and so on ...
So effectively the active loop becomes loop with 15 ms sleep (average of 10 and 20 ms). Because the code performed in the active phase is itself non-trivial, this still puts easily measurable load on the CPU. I was able to achieve some further minor improvements by doing some low-level changes in how the driver works with collections, but it became obvious that (at least in my quite specific use-case) this leads nowhere.
I was able to come up with an alternative (applicative) solution that simply blocks the DirectRunner threads when the pipeline is empty and only resumes the DirectRunner loop when new data enter the pipeline.
I'll keep on thinking about this for a while yet and then probably close this PR unless I figure out how to make it really useful...

I couldn't bring this any further and so I'm closing this PR.


Dependency on local copies of CommandLine libs

I tried to make my own code-gen project by following "SimplePocos" example, but the project cannot be compiled because the library depends on two local copies of the CommandLine project libraries:
    <PackageReference Include="System.CommandLine" Version="2.0.0-codegencs" />
    <PackageReference Include="System.CommandLine.NamingConventionBinder" Version="2.0.0-codegencs" />

Is it possible maybe to update it to the latest published beta4 version?

I'm sorry for the poor/outdated documentation.
The latest version of the sample template SimplePocos is here - and it doesn't require you to rebuild our forked version of System.CommandLine. All nuget dependencies are published. (To run templates like SimplePoco you don't need to rebuild the library and toolkit).
If you need to rebuild all libraries and tools, there are PowerShell scripts in the src folder. The right order would be:

build-external.ps1 is what initializes the required git submodules, including my fork of System.CommandLine.
build-core.ps1
build-models.ps1
build-tools.ps1
build-visualstudio.ps1

Thank you for fast response! I was able to run the template using dotnet-codegencs CLI, but also would also have intellisense when I author the template. This forces me to reference your DLLs and it doesn't seem to be possible because of those dependencies.
Unless I do something wrong.

I also stumbled upon a confusion around ILogger interface. Judging by name I expected the standard .NET logger, while it turned out to be your custom one. Another confusion is that the interface have only async methods, but is used synchronously everywhere across the template.

Thank you for fast response! I was able to run the template using dotnet-codegencs CLI, but also would also have intellisense when I author the template. This forces me to reference your DLLs and it doesn't seem to be possible because of those dependencies.

Did you open SimplePocos.csproj in Visual Studio? Did it restore the nuget references? And yet you don't get intellisense?

I also stumbled upon a confusion around ILogger interface. Judging by name I expected the standard .NET logger, while it turned out to be your custom one.

Microsoft ILogger takes only a regular string, which doesn't allow messages to use colors, that's why I've used my own. But yeah, probably I should add support for injecting a regular MS ILogger.

Another confusion is that the interface have only async methods, but is used synchronously everywhere across the template.

Despite having async definition (I forgot the reason), the methods are all sync, so it doesn't matter if you await the task or not. And in case it makes it easier for people who are not familiar with async/await.

Did you open SimplePocos.csproj in Visual Studio? Did it restore the nuget references? And yet you don't get intellisense?

In fact I created my own project with the same dependencies as yours and it doesn't compile. Now tried the same with your solution and see the same build error. (Just in case I use Rider, but I don't expect any difference in build behavior).

Microsoft ILogger takes only a regular string, which doesn't allow messages to use colors, that's why I've used my own. But yeah, probably I should add support for injecting a regular MS ILogger.

Yes, I know that it doesn't support colors. I use Spectre.Console myself to get the nice output. But it may be for a reason - logging is not the same as console output, in general case logs should not contain ANSI-sequences.
In my opinion, it is better to rename your class somehow. Otherwise it would be always a confusion.
The same is valid for *Async methods. If they are sync, they must not follow async naming rules and must not return Task. Otherwise it is confusing and may repel users.
Sorry for being picky! :) I think it's a great project, and would like to see it go further.

Now tried the same with your solution and see the same build error

In the past I've published a nuget package which was refering to this private nuget dependency (System.CommandLine* v codegencs-2.0.0) (I think I've removed and marked as deprecated version), but I don't think that's the case here (assuming you're using latest CodegenCS.Runtime - it's using this System.CommandLine* 2.0.0-beta4.22272.1 that you've mentioned). If you check YourProject.deps.json you might be able to find who is refering to this private nuget. And maybe updating references might fix this bad-dependency.

I created my own project with the same dependencies as yours

I've missed that.
So..  probably you're pointing to the CSPROJ instead of using the NUGET, right? In this case, CSPROJ will need those local versions. So.. getting back to my first reply - did you try the build-external.ps1? It should build all forked versions that you need.

Rick, I tried to open your solution where SimplePoco is located. Got the
same result. The screenshot I provided us from an attempt to build your
solution.
Custom build scripts won't help here because the IDE builds sources itself
in background. It cannot get all necessary dependencies (your private build
of Command Line library is transitively referenced by your Runtime library)
and falls.
If you cannot link to the officially released command line package, then
maybe you can bundle your forked version to your library? Likely it will
solve the problem.
On Tue, Jun 6, 2023, 19:25 Rick Drizin @.***> wrote:

I created my own project with the same dependencies as yours
I've missed that.
So.. probably you're pointing to the CSPROJ instead of using the NUGET,
right? In this case, CSPROJ will need those local versions. So.. getting
back to my first reply - did you try the build-external.ps1? It should
build all forked versions that you need.
—
Reply to this email directly, view it on GitHub
https://github.com/CodegenCS/CodegenCS/issues/18#issuecomment-1579176656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2ZVO2OV7BXFUGESQ4PSLXJ5RZNANCNFSM6AAAAAAY3IBPS4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, I found out what happened:
CodegenCS.Models 3.0.0 was published with those bad references (System.CommandLine private version).
After a few days, I noticed the problem and republished 3.0.1 fixed, then I "unlisted" package 3.0.0. But it's still there (not sure if I can totally delete it).
Since CodegenCS.Models.DbSchema 3.0.0 (which is still the latest) was built using CodegenCS.Models 3.0.0, it still has this transitive dependency of the private version.
Quick fix: add <PackageReference Include="CodegenCS.Models" Version="3.0.1" />. Then build should work (in obj/project.assets.json you won't find the bad reference anymore).

Yes, it helped. Thank you very much!
But please consider my opinion around ILogger confusion and the correct usage of "*Async" pattern. It will make the library much easier to use in other apps.

Sure thing. How would you call that class to avoid this confusion? I'll also investigate if I can replace my colorful console by the aforementioned Spectre.Console.

FWIW now templates can be written using async Tasks.


Sometimes .meta is OK after all

We need to update the spec still, but coming soon:

Bundle.entry[1].resource[Immunization] should not include .meta elements

won't be quite right -- it should be OK for an Immunization .meta.security[].code to be populated with one of the allowable IAL values (see http://build.fhir.org/ig/dvci/vaccine-credential-ig/branches/main/#identity-assurance).

https://github.com/smart-on-fhir/health-cards/pull/117 to track the update on the main spec

Thanks for the heads up

Extra requirement: make the SDK version 0.4.4-1 (with a "pre-release" tag -1), this will allow us to start comparing incremental versions of the SDK and let people know of a new update, and not just when the spec/SDK version is bumped.

Fixed by #49.


In the Kubeflow 1.9.1, How do i access at KServe through istio-ingress-gateway svc

/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I used this code that you guys support
What did you expect to happen:
Traceback (most recent call last):
  File "/Users/reconlabs/Desktop/luke/recon/management-mlops/test2.py", line 119, in <module>
    _auth_session = get_istio_auth_session(url=KUBEFLOW_ENDPOINT, username=KUBEFLOW_USERNAME, password=KUBEFLOW_PASSWORD)
  File "/Users/reconlabs/Desktop/luke/recon/management-mlops/test2.py", line 33, in get_istio_auth_session
    raise RuntimeError(f"HTTP status code '{resp.status_code}' for GET against: {url}")
RuntimeError: HTTP status code '403' for GET against: http://localhost:8080

It raised 403 error

It seems that the kubeflow added some button for dex
How to access at KServe ?

Environment:

Istio Version: 1.22.1
Knative Version: 1.12.4
KServe Version: 0.13.0
Kubeflow version: 1.9.1
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm] istio_dex
Minikube/Kind version:
Kubernetes version: (use kubectl version): v1.31.1
OS (e.g. from /etc/os-release): Mac

I solved using below code i change
response = session.get(f"{HOST}/oauth2/start?rd=%2Foauth2", **_kargs, allow_redirects=True)


Add new volunteer Fariol Blondeau

I'm a frontend developper and volunter to belong to this amazing community

Hello @codewithshubhi why don't you merge my PR?

@codewithshubhi thanks ✨


Add warning when monotonicity is forced in the input to histogram_quantile

Inputs to histogram_quantile must be monotonic for the results to be accurate. However, due to various reasons, sometimes it is not monotonic, so we apply a hack to make it monotonic, but then the results may not be accurate, so we should inform the user with a warning.

@beorn7 As discussed on Slack


Content on Hackage/Stackage

Looking for feedback on the following!

Hackage/Stackage and where to find and install libraries
Haskell can be confusing. Or rather, the Haskell ecosystem can get pretty confusing. Turns out installing a library is super easy nonetheless, but it's worth going through it real quick.
Hackage
In the beginning, it was Hackage. Hackage is just a website where users upload packages, pretty much as you would do with npmjs.com. You then list your dependencies in package.yml (which, you guessed it, is basically package.json in node.js) and you're good to go.
Fun times
Have you ever looked inside the node_modules folder?
In node.js, dependencies that have other dependencies are installed within the dependency. You end up with node_modules nested into other node_modules. That's because a dependency can exist at different versions even in the same project.
Whether that's good or not I'll leave it to you to decide (hint, it's a bit shit). The important bit is that this is not how GHC works. GHC expects a specific package to exist only once at a fixed version (within the same project). This means that if two packages share a dependency, they'll have to agree on which version to use.
Now imagine 10 or 15 packages all depending on the same package, but with different version constraints. Dependency resolution becomes impossible.
Stackage
Remember how we talked about the nice people behind the build tool stack — well, who could have possibly invented stackage?
That's right, it's them striking again. (shout out FP Complete).
Their solution to the dependency problem (which, by the way, is in no way specific to Haskell, other languages have exactly the same problem) was to curate a set of packages that are known to work together and put them into a package set.
In other words, the job of working out which packages build together (and most importantly, at which version) is taken care of.
This is massively useful! It means when you need to install a package, you just open package.yml and add a new entry under the dependencies field without pinning a specific version (unless you have a very good reason to).
Packages that are not on Stackage
First of all, is Hackage deprecated? Absolutely not, Hackage is still the source for all the packages in Stackage. And I'm just used to the way documentation looks on the Hackage website that I spend pretty much all of my time there and zero time on the Stackage one.
But it may happen that a package on Hackage is not present on Stackage. In fact, a lot of packages (either forgotten, never updated or not deemed production ready) can be found on Hackage but never make it to Stackage. It could also happen that a package was at some point in a Stackage package set, but because it failed to build or couldn't be maintained anymore, it got dropped in a more recent package set.
In a nutshell, you should be able to find everything you need, especially in the beginning. When you'll find yourself needing a package that's only available on Hackage, stack will warn you and will provide instructions on how to tweak your stack.yml file accordingly. It's super painless and working with a package set is really really nice.

Merged 🚢


Allow conditionally using KMS for tfvars bucket

This allows using AES256 encryption for the tfvars bucket, rather than creating and using a KMS key. Defaults to using the KMS key.

I do wonder if  we shoudl default the other way round.


Error while connected to MySQL through ssh tunnel

This error happens whether I connect to MySQL by configurating the ssh tunnel directly in DBeaver, or making an ssh tunnel on my machine myself with ssh -g -L.
The connection initially works, but when I try to access data or browse the tables, every time an action is issue, an error pops up with an error message saying "Connection with [..] lost, Query execution failed, SQL Error, No operations allowed after connection closed".

java -version returns :
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

Do you able to browse tables? Does connection breaks only when you trying to select data?
Anyhow - please post debug log (https://github.com/serge-rider/dbeaver/wiki/Log-files) here or on<EMAIL_ADDRESS>

Ultimately I can read the tables, but the error about the "read timeout" pops up all the time, any action I do. I click reconnect and it works but it's disrupting. Here's the debug log (using 4.1.2 actually)
dbeaver-debug.log.txt

Did you set any keep-alive configuration (in SSH settings or in general connection settings)?
If yes - try to set it to 0 (disable).
Any custom driver properties?
Check that tunnel connect timeout is big enough (on SSH settings page).
Also, according to https://sourceforge.net/p/jsch/support-requests/23/ :

Be sure that the host we are connecting to is not in ~/.ssh/known_hosts (e.g. empty it)

I removed the target host from my ~/ssh/known_hosts, I disabled TCPKeepAlive (it is enabled by default in debian jessie's ssh), I have set a connect timeout of 10000ms, a Keep-Alive of 0ms. It works OK the first table I open, but any further action I do I get the very same error of "Communications link failure".

Weird.
Please post debug log again. Something bad happens with SSH tunnel and there should be some errors in logs.

There isn't any activity about this ticket very long time. It will be closed. However, if you think that it is actual just let us know.


Colorscheme does not work well if it is not the only colorscheme installed

I like this colorscheme, but I tend to switch between colorschemes and unlike every other colorscheme I have installed, this one only seems to work properly if it is used as the only colorscheme. Other colorschemes only extend the config when their setup method is called and then apply them when the colorscheme is loaded using colorscheme <name>, which allows adding multiple colorschemes to for example a lazy plugin spec and setting them all up.
Calling colorscheme darkvoid after another colorscheme has been set also does not work proplerly as highlights are not cleared when darkvoid is applied.
I made a small fix for these issued so that I could use the colorscheme and have opened a PR https://github.com/Aliqyan-21/darkvoid.nvim/pull/7, as I think this would benefit more people.

Hello @gustavkrist, thanks for finding this bug and fixing this issue, I have merged your PR as it makes the colorscheme more flexible and helps for the seamless transition between different colorschemes!