Detox server doesn't get initialized on iOS and JavaScript Timers -> busy Javascript Timers

Hey mates, I am trying to make e2e tests using Detox
and i have faced problem as Detox server doesn't get initialized
and I get the following too :
detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)
I hope that logs are not too long but here are the logs that I have in the artifact.
4D59B341-1D72-4537-A7A6-2685607D41FC 2020-02-19 15-16-51Z.startup
detox[48831] INFO:  [DetoxServer.js] server listening on localhost:50871...
detox[48831] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:50871
detox[48831] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [exec.js/EXEC_CMD, #0] applesimutils --list --byType "iPhone X"
detox[48831] DEBUG: [exec.js/EXEC_CMD, #1] applesimutils --list --byId 4D59B341-1D72-4537-A7A6-2685607D41FC --maxResults 1
detox[48831] DEBUG: [exec.js/EXEC_CMD, #2] /usr/bin/xcrun simctl uninstall 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/EXEC_TRY, #2] Uninstalling com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #2] com.snowflake.hike uninstalled
detox[48831] DEBUG: [exec.js/EXEC_CMD, #3] /usr/bin/xcrun simctl install 4D59B341-1D72-4537-A7A6-2685607D41FC "/Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app"
detox[48831] DEBUG: [exec.js/EXEC_TRY, #3] Installing /Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #3] /Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app installed
detox[48831] DEBUG: [exec.js/EXEC_CMD, #4] /usr/bin/xcrun simctl terminate 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/EXEC_TRY, #4] Terminating com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #4] com.snowflake.hike terminated
detox[48831] DEBUG: [exec.js/EXEC_CMD, #5] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #6] [pid=48872] /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate "processImagePath beginsWith \"/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app\""
detox[48831] DEBUG: [exec.js/EXEC_CMD, #7] SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/snowflake/Library/Detox/ios/647caee43d053e07344915b0d5b71c85cb0b4733/Detox.framework/Detox" /usr/bin/xcrun simctl launch 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike --args -detoxServer "ws://localhost:50871" -detoxSessionId "c5f11579-4c6f-6735-87be-96d91fe111d8" -detoxPrintBusyIdleResources "YES"
detox[48831] DEBUG: [exec.js/EXEC_TRY, #7] Launching com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_CMD, #8] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] INFO:  [AppleSimUtils.js] com.snowflake.hike launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate 'process == snowflake'
detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)
detox[48831] DEBUG: [DetoxServer.js/LOGIN] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 48872]: /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate processImagePath beginsWith "/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app"
detox[48831] DEBUG: [exec.js/EXEC_CMD, #9] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #10] [pid=49499] /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate "processImagePath beginsWith \"/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app\""
detox[48831] DEBUG: [exec.js/EXEC_CMD, #11] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC screenshot "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/ac4574f8-0716-40bd-9cdc-bc4dc6d0ffdb.detox.png"
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #12] [pid=49503] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC recordVideo /private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync Timer: Tracking Timer <__NSCFTimer: 0x600003b0dd40>
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync Timer: Tracking Timer <__NSCFTimer: 0x600003b0dd40>
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync Timer: Tracking Timer <__NSCFTimer: 0x600003b0dd40>
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.facebook.react.ShadowQueue
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.facebook.react.ShadowQueue
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.facebook.react.ShadowQueue
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] DEBUG: [exec.js/EXEC_CMD, #13] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC screenshot "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/f98b8fab-208a-4d78-8153-d261dce44d90.detox.png"
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 49503]: /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC recordVideo /private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [SimulatorRecordVideoPlugin.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/test.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/ac4574f8-0716-40bd-9cdc-bc4dc6d0ffdb.detox.png" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/testStart.png
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/f98b8fab-208a-4d78-8153-d261dce44d90.detox.png" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/testDone.png
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 49499]: /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate processImagePath beginsWith "/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app"
detox[48831] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:
  (id = 1) invoke: {"target":{"type":"Invocation","value":{"target":{"type":"EarlGrey","value":"instance"},"method":"detox_selectElementWithMatcher:","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"GREYMatchers"},"method":"detoxMatcherForText:","args":[{"type":"NSString","value":"Personalized to You"}]}}]}},"method":"assertWithMatcher:","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"GREYMatchers"},"method":"matcherForSufficientlyVisible","args":[]}}]}
  (id = -1000) reactNativeReload: {}

That might be the reason why the test "Example should show GET STARTED button" has timed out.

detox[48831] DEBUG: [SimulatorLogRecording.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/90c3bf5e-026e-42f8-a462-d8d32e57fd77.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/process.log
detox[48831] DEBUG: [SimulatorLogRecording.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/864b0986-f94b-481a-8f81-6132f73f6558.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/4D59B341-1D72-4537-A7A6-2685607D41FC 2020-02-19 15-16-51Z.startup.log
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/053ef6fa-1c4f-4f4a-bfc7-c7a0973c182a.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/detox_pid_48831.json.log
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/dc0d2b5c-4d65-471e-850e-f86af80747d8.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/detox_pid_48831.log
detox[48831] DEBUG: [DetoxServer.js/DISCONNECT] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/DISCONNECT] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=tester not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)
detox[48831] DEBUG: [DetoxServer.js/WS_CLOSE] Detox server connections terminated gracefully

process.log
Filtering the log data using "processImagePath BEGINSWITH "/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app""
Timestamp               Ty Process[PID:TID]
2020-02-19 17:12:50.038 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.038 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.038 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.038 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.038 I  snowflake[48884:9d3f4] [com.wix.Detox:WXJSTimerObservationIdlingResource] Removing observed timer 17836
2020-02-19 17:12:50.039 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] WXRunLoopIdlingResource -> busy React Native thread is busy.
2020-02-19 17:12:50.039 I  snowflake[48884:9d3f4] [com.wix.Detox:WXJSTimerObservationIdlingResource] Observing timer: 17837 d: 0.001 r: 0
2020-02-19 17:12:50.039 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] WXRunLoopIdlingResource -> busy React Native thread is busy.
2020-02-19 17:12:50.039 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.039 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.039 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.054 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.055 I  snowflake[48884:9d3f4] [com.wix.Detox:WXJSTimerObservationIdlingResource] Removing observed timer 17837
2020-02-19 17:12:50.055 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] WXRunLoopIdlingResource -> busy React Native thread is busy.
2020-02-19 17:12:50.055 I  snowflake[48884:9d3f4] [com.wix.Detox:WXJSTimerObservationIdlingResource] Observing timer: 17838 d: 0.001 r: 0
2020-02-19 17:12:50.056 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] WXRunLoopIdlingResource -> busy React Native thread is busy.
2020-02-19 17:12:50.056 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.056 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers
2020-02-19 17:12:50.056 Db snowflake[48884:9d39b] [com.wix.Detox:EarlGreyStatistics] JavaScript Timers -> busy Javascript Timers

detox_pid_48831.log
detox[48831] INFO:  [DetoxServer.js] server listening on localhost:50871...
detox[48831] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:50871
detox[48831] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [exec.js/EXEC_CMD, #0] applesimutils --list --byType "iPhone X"
detox[48831] DEBUG: [exec.js/EXEC_CMD, #1] applesimutils --list --byId 4D59B341-1D72-4537-A7A6-2685607D41FC --maxResults 1
detox[48831] DEBUG: [exec.js/EXEC_CMD, #2] /usr/bin/xcrun simctl uninstall 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/EXEC_TRY, #2] Uninstalling com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #2] com.snowflake.hike uninstalled
detox[48831] DEBUG: [exec.js/EXEC_CMD, #3] /usr/bin/xcrun simctl install 4D59B341-1D72-4537-A7A6-2685607D41FC "/Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app"
detox[48831] DEBUG: [exec.js/EXEC_TRY, #3] Installing /Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #3] /Users/snowflake/DevSquads/snowflake/snowflake-react-native/ios/build/snowflake/Build/Products/Debug-iphonesimulator/snowflake.app installed
detox[48831] DEBUG: [exec.js/EXEC_CMD, #4] /usr/bin/xcrun simctl terminate 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/EXEC_TRY, #4] Terminating com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_SUCCESS, #4] com.snowflake.hike terminated
detox[48831] DEBUG: [exec.js/EXEC_CMD, #5] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #6] [pid=48872] /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate "processImagePath beginsWith \"/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app\""
detox[48831] DEBUG: [exec.js/EXEC_CMD, #7] SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/snowflake/Library/Detox/ios/647caee43d053e07344915b0d5b71c85cb0b4733/Detox.framework/Detox" /usr/bin/xcrun simctl launch 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike --args -detoxServer "ws://localhost:50871" -detoxSessionId "c5f11579-4c6f-6735-87be-96d91fe111d8" -detoxPrintBusyIdleResources "YES"
detox[48831] DEBUG: [exec.js/EXEC_TRY, #7] Launching com.snowflake.hike...
detox[48831] DEBUG: [exec.js/EXEC_CMD, #8] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] INFO:  [AppleSimUtils.js] com.snowflake.hike launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate 'process == snowflake'
detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)
detox[48831] DEBUG: [DetoxServer.js/LOGIN] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 48872]: /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate processImagePath beginsWith "/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app"
detox[48831] DEBUG: [exec.js/EXEC_CMD, #9] /usr/bin/xcrun simctl get_app_container 4D59B341-1D72-4537-A7A6-2685607D41FC com.snowflake.hike
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #10] [pid=49499] /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate "processImagePath beginsWith \"/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app\""
detox[48831] DEBUG: [exec.js/EXEC_CMD, #11] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC screenshot "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/ac4574f8-0716-40bd-9cdc-bc4dc6d0ffdb.detox.png"
detox[48831] DEBUG: [exec.js/SPAWN_CMD, #12] [pid=49503] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC recordVideo /private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync WXRunLoopIdlingResource: React Native thread is busy.
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [exec.js/EXEC_CMD, #13] /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC screenshot "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/f98b8fab-208a-4d78-8153-d261dce44d90.detox.png"
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 49503]: /usr/bin/xcrun simctl io 4D59B341-1D72-4537-A7A6-2685607D41FC recordVideo /private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [SimulatorRecordVideoPlugin.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/c0179e52-2fb0-49ab-90b8-30dc9dfa43db.detox.mp4" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/test.mp4
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/ac4574f8-0716-40bd-9cdc-bc4dc6d0ffdb.detox.png" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/testStart.png
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/f98b8fab-208a-4d78-8153-d261dce44d90.detox.png" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/testDone.png
detox[48831] INFO:  [actions.js] Sync JavaScript Timers: Javascript Timers
detox[48831] INFO:  [actions.js] Sync Dispatch Queue: com.apple.main-thread
detox[48831] DEBUG: [exec.js/KILL] sending SIGINT to [pid = 49499]: /usr/bin/xcrun simctl spawn 4D59B341-1D72-4537-A7A6-2685607D41FC log stream --level debug --style compact --predicate processImagePath beginsWith "/Users/snowflake/Library/Developer/CoreSimulator/Devices/4D59B341-1D72-4537-A7A6-2685607D41FC/data/Containers/Bundle/Application/0C2DE3FE-41FB-40C4-A0A6-7EC5819FD51E/snowflake.app"
detox[48831] WARN:  [Client.js/PENDING_REQUESTS] App has not responded to the network requests below:
  (id = 1) invoke: {"target":{"type":"Invocation","value":{"target":{"type":"EarlGrey","value":"instance"},"method":"detox_selectElementWithMatcher:","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"GREYMatchers"},"method":"detoxMatcherForText:","args":[{"type":"NSString","value":"Personalized to You"}]}}]}},"method":"assertWithMatcher:","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"GREYMatchers"},"method":"matcherForSufficientlyVisible","args":[]}}]}
  (id = -1000) reactNativeReload: {}

That might be the reason why the test "Example should show GET STARTED button" has timed out.

detox[48831] DEBUG: [SimulatorLogRecording.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/90c3bf5e-026e-42f8-a462-d8d32e57fd77.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/✗ Example should show GET STARTED button/process.log
detox[48831] DEBUG: [SimulatorLogRecording.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/864b0986-f94b-481a-8f81-6132f73f6558.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/4D59B341-1D72-4537-A7A6-2685607D41FC 2020-02-19 15-16-51Z.startup.log
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/053ef6fa-1c4f-4f4a-bfc7-c7a0973c182a.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/detox_pid_48831.json.log
detox[48831] DEBUG: [Artifact.js/MOVE_FILE] moving "/private/var/folders/35/t0nqj9vd2zd735xf5d05ybzr0000gn/T/dc0d2b5c-4d65-471e-850e-f86af80747d8.detox.log" to artifacts/ios.sim.debug.2020-02-19 15-07-46Z/detox_pid_48831.log
detox[48831] DEBUG: [DetoxServer.js/DISCONNECT] role=tester, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/DISCONNECT] role=testee, sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8
detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=tester not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)
detox[48831] DEBUG: [DetoxServer.js/WS_CLOSE] Detox server connections terminated gracefully

I'm having the same exact issue. Everything works fine with older versions of Detox but as soon as I update I get detox[48831] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=tester not connected, cannot fw action (sessionId=c5f11579-4c6f-6735-87be-96d91fe111d8)


String version of MISSING function

Reported by ansley b manke on 31 Mar 2009 18:09 UTC
See #1488. Desired behavior:
yes? let a = {"a",}
yes? list a
             VARIABLE : {"a",}
             SUBSET   : 2 points (X)
 1   / 1:"a"
 2   / 2:""

yes? list missing(a,"z")
    VARIABLE : MISSING(A,"z") SUBSET : 2 points (X)
    1 / 1:....
    2 / 2:....

Instead would expect to get {"a","z"}.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1652

Modified by ansley.b.manke on 31 Mar 2009 18:10 UTC

Comment by ansley.b.manke on 11 Jul 2017 17:05 UTC
#1796 duplicates this and has more comments and a workaround.


Internationalization for numerical values

The siunitx package not only comes equipped with \unit{} but also with \num{}. With this, users can configure their language and the package will insert group separators accordingly and use . or , for decimal places.
For example, the preamble could include something along these lines:
\usepackage{siunitx}
\sisetup{
	locale=DE,
	group-separator={,},
	group-digits=integer,
	quotient-mode=fraction,per-mode=symbol}

It's easy to incorporate it here:
https://github.com/paul019/python_to_latex/blob/b7739e6a3851d7adf3c542faf0be3d49ba0fd154/python_to_latex.py#L49-L50
Simply replace it by this:
def round_to_n_decimal_places(v: float, n: int):
    res = "{:.{}f}".format(v, int(n))
    return "\\num{" + res + "}"

and the results.tex file will look like this:
\newcommand*{\resultG}{(\num{9.0} \pm \num{1.2}) \cdot 10^{\num{2}}}

(maybe you want to improve this such that we don't have \num{.} in the exponents like 10^{\num{2})
Edit: One could also use \qty{1.23}{\meter \per \second^2} as an example instead of specifying num and unit separately. I don't know if this has any advantages though. Maybe the spacing between value and unit is a bit better in this case?

Just for our reference, to be implemented in next alpha version:
\sisetup{separate-uncertainty=true, exponent-product=\cdot}
\NewDocumentCommand{\UncertSys}{}{_{\text{sys}}}
\NewDocumentCommand{\UncertStat}{}{_{\text{stat}}}
\sisetup{input-digits=0123456789\UncertStat\UncertSys}
\begin{align}
    \num{1.3 \pm 0.3\UncertSys \pm 0.02\UncertStat e10}\\
    \qty{1.3 \pm 0.2\UncertSys}{\N\per\g}
\end{align}


Support for quoted keys and values with special symbols

String.validateSymbols() in ktoml-core-jvm:0.5.0 performs an extra trimQuotes(), which prevents assignment to quoted keys containing special symbols.
For example, consider the following line of valid (per language docs) TOML:
"androidx.activity:activity-compose" = {}

This yields the following exception:
ParseException: <...>: Not able to parse the key: ["androidx.activity:activity-compose"] as it contains invalid symbols.

+1 to this. Using single quotes succeeds to parse, but the resulting keys have the quotes in the name, i.e.:
'foo:' = 'bar'

Would result to:
mapOf("'foo:'" to "bar")

The quotes are applied inconsistently to the keys and values.


Download Campaign attachments

Closes #1031: Adds a toolbar to the LDTWebViewController to download file to device and creates a UIDocumentInteractionController to open the file.
@lkpttn -- Can you add a mock of what the button should look like? We're not tied to using the UINavigationController.toolbar or UIBarButtonItem -- this was quickest way to get up and running.
Screenshots

@lkpttn Download button in self.navigationItem.rightBarButtonItem:

We're going to use a small tab bar (44pt / 88px) to hold the Open In... button that downloads the PDF and presents the Open In modals.

@lkpttn -- Updated with designs per Slack discussion today.

Also adding error message if user attempts to "Open file" without network connection, as the button press downloads the file to device and then presents the UIDocumentInteractionController menu.

👍


fix error condition

And make sure plugins are up to date
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

can't wait :-)


data set

Can you share the data sets you use ?The link you gave is no longer good.

The use of some datasets need agree with the protocol. In addition, DukeMTMC has not be allowed to be used in academic papers. You can send an e-mail to the authors of corresponding dataset for download link.

thank you.
------------------ 原始邮件 ------------------
发件人:                                                                                "guxinqian/TKP"                                                                                @.>;
发送时间: 2022年9月20日(星期二) 上午10:41
@.>;
<EMAIL_ADDRESS>主题: Re: [guxinqian/TKP] data set (Issue #8)
The use of some datasets need agree with the protocol. In addition, DukeMTMC has not be allowed to be used in academic papers. You can send an e-mail to the authors of corresponding dataset for download link.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Does the iLIDS-VID dataset also need to send an email to the author to get a download link ?

iLIDS-VID does not involve the protocol of usage. You can send an email to me(xinqiangu@gmail.com). Then, I send my iLIDS-VID datset to you.


Enable setting minres initial vector

Reference issue
Closes https://github.com/scipy/scipy/issues/6843
What does this implement/fix?
Makes sure scipy.sparse.linalg.isolve.minres uses parameter x0 correctly.
Additional information
Combines https://github.com/scipy/scipy/pull/6887 and https://github.com/scipy/scipy/pull/7080
Tests for x0 are added to test_minres not to test_iterative where they can be tested for more solvers. A first attempt gave some errors and I'm not familiar enough with all solvers to fix it immediately. If requested, I can look into it.

thanks, merged


Multiple assert support

I combined the two fields Message and StackTrace on the TestPropertiesView and I'm displaying all the results found. The display could use some color or at least bold fonts but I don't want to do it until we resolve whether we are keeping the ExpandingLabel control, because it will be done differently depending on whether we keep or drop it. I did improve the TipWindow display a little bit.
For testing this, if you want to see it work. the NUnit 3 adapter demo program is a good choice as it has a number of tests with multiple failing asserts, failures plus warnings and failures plus errors.

Last comment before i go to the other piece. This change mentions added multiple assert support. I would like to see a multiple assert in the mock assembly so i can pull it up here and see how this change makes it look.

I'll do some refactoring as you suggest.
As for mock-assembly, it has traditionally been used to test counting of errors, failures, etc. and I've pushed back in the past when people added code to it to demonstrate various other features. I've been using NUnit3TestDemo.dll for the purpose of showing what multiple asserts, warnings, etc. look like. It's part of the nunit 3 adapter project, but it could easily be copied here for that use. What do you think?

Regarding TipWIndow, I'd rather not spend any more time cleaning it up until we decide whether or not to keep it.

It's part of the nunit 3 adapter project, but it could easily be copied here for that use. What do you think?

yes. I pulled down the adapter project and ran cake to build it and get the assembly and it is failing when it gets to the NUnit3TestAdapterInstall.csproj (I initially pasted the error, but I don't want to clutter up this pull request with non-related things... HEY I'M GETTING BETTER! Strange that it isn't working because it looks like it is looking for vs2017 which I have installed)

@immeraufdemhund I was a bit afraid that the idea of tip window and expanding fields on hover was a bit old-fashioned. But since you seem to like the idea, I'll clean it up a bit and keep it for now.

I think that should cover all the comments - ready to review again.

They appeared only after I added the new demo project, which makes no sense at all. I'm looking into it.

Silly mistake!

Interesting... I just noticed that Visual Studio uses a very similar display to my TipWindow when you hover over the stack trace in an exception notice.

Just a few visual changes while waiting for re-review:

All three large text boxes are now fixed font - looks better that way.
Top border moved up one pixel, left border left one pixel.
Increase padding within window around the text.


Datetime Handling

Hi team!
Really enjoying the package. I am working with snow remote sensing and this has been really useful for automating the comparison of our RS results to stations.
I am wondering if it would be possible to add functionality to handle DateTime objects. I was thinking, assuming you provide a DateTime object instead of a string it would run:
def parse_datetime(datetime_obj):
    return datetime_obj.strftime('%Y') + datetime_obj.strftime('%m') + datetime_obj.strftime('%d') + datetime_obj.strftime('%H') + datetime_obj.strftime('%M')

from datetime import datetime
if isinstance(user_input_start, datetime):
    user_input_start = parse_datetime(user_input_start)

Happy to parse it myself just might be nice to handle pandas datetime objects within the package.

Hi @ZachKeskinen,
I have a spinoff of this python library called SynopticPy that you might want to try. It works a little differently, but does accept datetime input (it even returns the data as a Pandas DataFrame).

I don't know who maintains this repo anymore. I got your notification because apparently I "watch" it; that must have been from a few years ago. Haha!

Hey @blaylockbk
Thanks for the reply. That is good info the repo isn't maintained anymore and explains the datetime issues. I'll migrate over to the SynopticPy and swap the code over since I am just starting at this point.
Thanks!


javaudf Fix string format in java udf

Proposed changes
In #12456 , terminating zero has been dropped in ColumnString so we need to do adaption in Java UDF
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 38.01 seconds
load time: 571 seconds
storage size:<PHONE_NUMBER>4 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221101080047_clickbench_pr_37220.html


Feature request : Simplify Communication between Isolates in Dart with Channels

Proposal: Simplify Communication between Isolates in Dart with Channels

Problem
The current communication mechanism between isolates in Dart involves messages, ReceivePort, and SendPort. These terms can be confusing, and the process of setting up communication between isolates can be complicated.
Proposed Solution
Introduce a Channel structure, similar to the Go language, which simplifies the communication between isolates. A Channel would provide a more intuitive abstraction, making it easier for developers to work with isolates in Dart.
Example
Here's an example of how the Channel structure could be used in Dart:
  // Create a channel for communication between isolates
  final channel = UniChannel<String>();

  // Spawn a new isolate using SpawnWithChannel the channel's SendPort
  Isolate.spawnWithChannel(isolateFunction, channel);

  // Send a message through the channel
  await for (final value in channel) {
    print('Isolate received value: $value');
  }
}

// Isolate function
void isolateFunction(Channel<string> c) {
  // Receive and process the message
   for(int i =0;i<100;i++)
{
   c.send(sum) ;
}
}

Benefits
- Simplifies the communication setup between isolates.
- Provides a more intuitive abstraction for developers.
- Makes it easier to manage and close communication channels.
Conclusion
Introducing a Channel structure for communication between isolates in Dart would simplify the process and provide a more intuitive abstraction for developers. This change would make it easier for developers to work with isolates and manage communication channels in their applications.

You could implement this as a separate package - I don't really see how this is important enough to warrant an entry in the SDK.
Most Isolate use cases would probably need to associate the "request" with the "response" which this doesn't offer, so it's only really useful for dispatching work to another isolate, waiting asynchronously for that isolate to do the work and then resuming - which is exactly what Isolate.run does, but in a persistent isolate instead of spawning a new one every time.

cc @lrhn and @mkustermann

Not sure how much this differs from a ReceivePort, other than being typed.
Not unless there is some implicit closing involved, say when the isolate you send it to is closed.
That's also dangerous.
But compare the code above to:
  // Create a channel for communication between isolates
  final channel = TypedReceivePort<String>();

  // Spawn a new isolate using SpawnWithChannel the channel's SendPort
  Isolate.spawn(isolateFunction, channel.sendPort);

  // Send a message through the channel
  await for (final value in channel) {
    print('Isolate received value: $value');
  }
}

// Isolate function.
void isolateFunction(TypedSendPort<String> c) {
  // Receive and process the message
   for(int i =0; i < 100; i++) {
     c.send(sum) ;
  }
  c.close();
}

where we just define typed wrappers around ReceivePort and SendPort.
class TypedReceivePort<T> extends Stream<T> {
  final ReceivePort _port = RawReceivePort();
  void cancel() {
    _port.cancel();
  }
  StreamSubscription<T> listen(void Function(T)? onData, {Function? onError, void Function()? onDone, bool cancelOnError = false) {
    return _port.cast<T>.listen(onData, onError: onError, onDone: onDone, cancelOnError: cancelOnError);
  }
  TypedSendPort<T> get sendPort => TypedSendPort<T>(_port.sendPort);
}
class TypedSendPort<T> {
  final SendPort _port;
  TypedSendPort(this._port);
  void send(T value) {
    _port.send(value);
  }
}

I'd rather make an abstraction over sending a stream, say:
class Isolate {
  // ...
  static Stream<T> runStream<T>(Stream<T> Function() computation) { ... }
}

which works like Isolate.run, but returns a stream at both ends, and forwards events and pushback between the isolates.
(My biggest conundrum around that is whether to forward pause/cancel events or use Isolate.pause/Isolate.kill instead.)

In Go channels are somewhat symmetric: The channel can be passed around to any go routine. Any go routine can perform blocking writes / reads.
In Dart we have an inherent asymmetry built in:

The created ReceivePort belongs to an isolate, it cannot be passed around to other isolates, other isolates cannot listen on it. The isolate will get notified asynchronously once events arrive.
The corresponding SendPort can be arbitrarily passed around across isolates. Any isolate can send messages.

This asymmetry naturally will lead to different interfaces for the receiver than the sender.


WebView error on Android 6 (API 23) and lower on debug and release build types

On all Android 6 devices and lower I'm getting this error:

X509Util: Error creating trust manager (com.appmattus.certificatetransparency.internal.verifier.CertificateTransparencyTrustManager): java.lang.IllegalArgumentException: tm is an instance of com.appmattus.certificatetransparency.internal.verifier.CertificateTransparencyTrustManager which is not a supported type of X509TrustManager

This results in "Webpage not available (net:ERR_FAILED)" error and you can only catch this error in the onReceivedError function inside of the WebViewClient class.
I'm using installCertificateTransparencyProvider method for setting up the library.
More info:

lib version v1.1.1 (latest)
minifyEnabled false
minSdkVersion 21
targetSdkVersion 32
compileSdkVersion 32

As I understand there is a good explanation here why this is happening. I would be grateful if @mattmook you can look at this because we are using your lib in production and except for this it is really great and easy to use. You did a really good job.

If anybody is wondering I fixed this issue by implementing a custom WebViewClient and overriding shouldInterceptRequest with OkHttp library that isn't affected with this issue.
override fun shouldInterceptRequest(view: WebView, request: WebResourceRequest): WebResourceResponse? {             val okHttpRequest: Request = Request.Builder().url(request.url.toString()).build()             return try {                 val response: Response = okHttp.newCall(okHttpRequest).execute()                 WebResourceResponse("", "", response.body?.byteStream())             } catch (e: IOException) {                 Timber.e(e)                 null             }         }

Looking at the error this looks as though you've got two instances of CT installed, could that be the case?

I'm not sure how feasible it will be to fix this given the explanation linked.
You have to be careful with the above "fix" as it will only apply to GET requests so if your WebView uses POST requests then these will no doubt either not apply CT checks or fail with the same original exception.

@kancic I'm now using the latest version of CT 2.2.1, kotlin 1.8.20, AGP 7.4 and I cannot reproduce it anymore

Closing this issue as won't fix as there is no way around it. The best I can do is offer a note in the readme to warn that the Java Security Provider will cause issues on API 23 and lower.


Update 030-crud.mdx

Fix typography error under Cascading Deletes (deleting related records) section, the diff in Post model are both optional.

Good spot, thank you!


Expose chart

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Ready to merge and just end the saga behind this little ticket.
Good opportunity to improve our documentation on how you DO modify one of these charts.

Yay!


ModuleNotFoundError: No module named 'easydict'

Hello,
Thank you for sharing your project!
I have a problem when run easy_example.py, it can't find the module named 'easydict'. I have no idea to fix it. Would you please do me a favor?
ModuleNotFoundError: No module named 'easydict'

Same error. Where is the 'easydict' module?


[FLOC-3404] Release improvements

Improve the release process, automate more of it, make less steps.
Fixes FLOC-3404.
Docs build for modified release instructions:
http://build.clusterhq.com/results/docs/release-improvements-FLOC-3404/build-11077/gettinginvolved/infrastructure/release-process.html

Thanks!
A few questions & a couple of things to clean up. Please resubmit (and feel free to ping me on slack when you do so).

Reviewed 3 of 3 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

admin/release.py, line 797 [r1] (raw file):
Is this actually true? Don't we sometimes do releases where we fix up something critical in a release branch?

admin/release.py, line 868 [r1] (raw file):
:grey_question: Strongly consider factoring everything below this into a separate function, initialize_release, that takes version, path, and top_level as parameters.

admin/release.py, line 869 [r1] (raw file):
Please delete commented-out code.

admin/release.py, line 871 [r1] (raw file):
Why are you doing sys.stdout.write rather than print?

admin/release.py, line 872 [r1] (raw file):
Please delete commented-out code.

admin/release.py, line 877 [r1] (raw file):
I think it would make this easier to follow if you put a blank line before each of these announcements. It would help divide this long function up into natural stanzas.

admin/release.py, line 909 [r1] (raw file):
Are we sure this is the only case where it will happen? Is it possible that this will mask more serious errors?

Comments from the review on Reviewable.io

admin/release.py, line 797 [r1] (raw file):
We might base a release off something other than master, i.e. another release branch, but only when something's gone wrong - which means the regular release instructions aren't reliable in such rare cases anyway. We're supposed to now do regular releases off master and have dropped pre-releases.

Comments from the review on Reviewable.io

admin/release.py, line 868 [r1] (raw file):
Will do!

Comments from the review on Reviewable.io

admin/release.py, line 871 [r1] (raw file):
No special reason other than it's a habit from writing tests where sys might be parameterised for a fake.

 We could potentially narrow this down further, but I don't think the risk of it coming up for some other reason is high enough to make it worth doing....not much serious can go wrong with attempting to commit here.

Comments from the review on Reviewable.io

admin/release.py, line 909 [r1] (raw file):
(we have an admin test that will fail in the event that anything else that caused this exception meant the licence file didn't get updated when it needed to be)

Comments from the review on Reviewable.io

Thanks!

Reviewed 3 of 3 files at r1, 1 of 1 files at r2, 2 of 2 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

admin/release.py, line 871 [r1] (raw file):
:grey_question: OK. I'd suggest either changing to print or adding an output parameter that defaults to sys.stdout. Now that there's more whitespace though, I think it's less important, so up to you whether to bother.

admin/release.py, line 909 [r1] (raw file):
OK. Having an admin test is a good cover. Thanks.

Comments from the review on Reviewable.io


OpenSSL 1.0.1t suddenly evaluates expiry certificate wrongly

Hi,
I have used a daily python bot for www.bomengids.nl for several years. It runs in a vm.
Three days ago it suddenly failed. I investigated and opensll was the culprit. Now its probably an old version, because the code and vm is from 2016.  I did update to the latest version for
However, the error is so basic I thought I would bring it your attention anyway.
OK: this is the version with the error:
OpenSSL 1.0.1t
runs on / uname -a
Linux core 3.16.0-10-amd64 #1 SMP Debian 3.16.81-1 (2020-01-17) x86_64 GNU/Linux
This is the error:
root@core twython/prod# openssl s_client -connect www.bomengids.nl:443
CONNECTED(00000003)
depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root
verify error:num=10:certificate has expired
notAfter=May 30 10:48:38 2020 GMT
verify return:0

On my desktop ubuntu you can see the certificate is fine:
OpenSSL 1.1.1  11 Sep 2018
runs on    uname -a
Linux 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
mate2018:~$ openssl s_client -connect www.bomengids.nl:443
CONNECTED(00000005)
depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
verify return:1
depth=1 C = FR, ST = Paris, L = Paris, O = Gandi, CN = Gandi Standard SSL CA 2
verify return:1
depth=0 OU = Domain Control Validated, OU = PositiveSSL Multi-Domain, CN = www.bomengids.nl
verify return:1

I did not expect openssl would make such an error (if thats true), even an old version and since it occured suddenly three days ago, it might pop up elsewhere too.
greetings and thanks for the f(ine software)

Did you check the time setting on each machine (did you run date)?

The AddTrust certificate has expired, but that website is still
sending that to you, and you still have it in your trust store.
I believe that since version 1.1.0 the default algorithm has
changed and properly tries a different certificate if it's
expired.
As workaround, on Ubuntu, you can edit /etc/ca-certificates.conf
and put a "!" before the mozilla/AddTrust_External_Root.crt
line and then run update-ca-certificates

Here is another HOWTO to fix it.
https://www.agwa.name/blog/post/fixing_the_addtrust_root_expiration

Did you check the time setting on each machine (did you run date)?

did not check that previously, but good point.
date
Mon Jun  1 10:22:23 UTC 2020
So that checks out ok
and error still there
Start Time:<PHONE_NUMBER>
Timeout   : 300 (sec)
Verify return code: 10 (certificate has expired)

Here is another HOWTO to fix it.
https://www.agwa.name/blog/post/fixing_the_addtrust_root_expiration

thank you, indeed my website testend on
https://whatsmychaincert.com/?www.bomengids.nl
shows:
www.bomengids.nl has a trusted chain containing an expired certificate. This chain will work with modern web browsers but may fail with older clients, notably OpenSSL 1.0.x. Download a chain without the expired certificate
I will try to fix it. Learned something new today :)

The AddTrust certificate has expired, but that website is still sending that to you, and you still have it in your trust store. I believe that since version 1.1.0 the default algorithm has changed and properly tries a different certificate if it's expired. As workaround, on Ubuntu, you can edit /etc/ca-certificates.conf and put a "!" before the mozilla/AddTrust_External_Root.crt line and then run update-ca-certificates

And that worked fine! Thank you!

I'm a bit horrified at the news of modern browsers accepting a certificate chain where a link is expired... even worse if it's a trust anchor.

I've removed the "bug" category, mostly because the "bug" is in an age old openssl version that we haven't supported for a long time. The question has been answered and accepted, time to close.

I'm a bit horrified at the news of modern browsers accepting a certificate chain where a link is expired... even worse if it's a trust anchor.

I hope they just build a valid chain to a newly added trusted root.

I'm a bit horrified at the news of modern browsers accepting a certificate chain where a link is expired... even worse if it's a trust anchor.

I believe there is an alternative trust anchor that is not expired, so the behaviour is correct. OpenSSL 1.0.x failed if the first trust anchor it comes to is expired, even if there is an alternative one that isn't.

This twitter thread might be useful. https://twitter.com/sleevi_/status/1266647545675210753

I'm a bit horrified at the news of modern browsers accepting a certificate chain where a link is expired... even worse if it's a trust anchor.

They might accept it if they can find an alternate chain.  I.e., what OpenSSL added in 1.1.0
That website message is misleading/incomplete.

I'm a bit horrified at the news of modern browsers accepting a certificate chain where a link is expired... even worse if it's a trust anchor.

LOL, no it is totally correct because there are many (3) trust chaines (to AddTrust External CA Root, USERTrust RSA Certification Authority and AAA Certificate Services), only 1 is expired. See https://tools.ietf.org/html/rfc4158 https://gist.github.com/minaguib/c8db186af450bceaaa7c452b76a9901b#gistcomment-3327448

I believe that since version 1.1.0 the default algorithm has changed and properly tries a different certificate if it's expired.

This implemented it, no? 4 years ago. https://github.com/openssl/openssl/commit/0daccd4dc1f1ac62181738a91714f35472e50f3c


Import name of child component being the same as the name of the Parent triggers an infinite recursion.

Vue version
3.4.19
Link to minimal reproduction
https://codesandbox.io/p/devbox/boring-lena-3l8wxy
play.vuejs.org
Steps to reproduce
Have a Parent component with name "A"
Import and render child component A
code should look like this:
<script>
import A from "./A.vue";//Child Component
....//Rest of imports

export default {
  name: "A",
  ....//Rest of the Parent
 }

What is expected?
Throw an error that the parent component should not have the same name as a child component
What is actually happening?
Infinite recursion, in cases where the components are more complex the pc freezes or the browser kills the page.
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 2.55 GB / 14.45 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 121.0.6167.139
    Chromium: 121.0.6167.184

Any additional comments?
In the example there is an "i", it is an invalid variable that triggers the warning that shows that  is infinitely mounted.
I had 2 components A & B, where they are used independently, a new feature required both A & B, initially I've made a copy of A and imported B, then I changed the Parent to import both A and B but the property name stayed the same as A in the Parent, so
Parent.name= "A"
A.name="A"
B.name="B"
which triggered this infinite recursion until Chrome killed the browser page.
Apparently the bug happens also if the name of the parent is the same as the import name of the child component,
so if I
import A from './A.vue"
and Parent.name="A"
even if A.name="AComponent"
the bug also triggers

the codesandbox link is not found.

https://play.vuejs.org

It's a recursive component but it's not terminating, so that's normal

I can reproduce with vue-playground.
Can I try this issue?


Fix #1021

Thanks for the PR!
Could you please briefly describe what was wrong and how it was fixed?
Also, is it possible to add test case for this case?

@asi1024 Cloud you add test?

Some bugs still exist.  I will fix it as soon as possible.

I made another PR #1167. This PR removes input_num from the feature and resolves this problem.


Publicize paginator's result_key_iters()

For ages now, I've been doing the "ask botocore to paginate for me, iterate over its pages, then iterate over the items in the result" canonical code. But after implementing some paginators and realizing that the paginator config includes the result_key key, I started wondering why botocore didn't abstract the pages away from us completely. Poking around the source code, I found the undocumented but perfect result_key_iters() method, which allowed me to flatten all my page iteration and avoid looking up the (hugely inconsistent) result keys by hand.
Is there a reason this isn't part of the public documented API? I imagine part of it is because there can occasionally be multiple result keys and the ensuing API design might be less obvious, but I wouldn't let the perfect be the enemy of the good. It's already far more pleasant than the repetitive stuff we all write daily for pagination.

This isn't public currently because it's specific to the botocore implementation of pagination and it differs from how the auto-pagination works in other SDKs (ruby, go, etc. they only offer page iteration). Botocore is a little different here because it powers the AWS CLI which has it's own special requirements for pagination (result key aggregation).
I also think the interface for this function is a little strange. Ideally, I think we would support item level iteration with an interface like this maybe:
# Create a reusable Paginator
paginator = client.get_paginator('list_objects')

for item in paginator.paginate(Bucket='my-bucket').items_iterator():
    # gives you each item in the default result_key (`Contents`).
    print(item)

And if there were multiple paginated result keys the items_iterator could take an optional result_key param that defaults to the default result key.
Either way, marking this as a feature request for item level pagination.

Thanks for clarifying! Yes, I basically just want to not have to think about the pages when I know botocore has enough information to avoid it 😄

@joguSD also, your proposed interface seems fine. Basically, it seems like this would be pretty good:
def items_iterator(self, result_key=None):
    if result_key:
        # Some way to look up the result_key_iters by key name, since the index is meaningless to anyone who doesn't have the paginator JSON in front of them
    else:
        return self.result_key_iters()[0]

Does it seem like a PR adding that would be useful? I don't want to do the work if you think it'll just sit in limbo for years, but it also seems pretty nice 😄

Hi. Any news on that?
Or can I get relult_key from a Paginator object, please?


[Fix] Fix the height of whole application

Right now as you can the height of the application keeps on increasing as we add more data, but it should be fixed!!

hi @Aman-Mandal  please assign this to me

Good luck @najeebkp


Missing scanner in the stores

Can't buy items because there is no scanner:

Maybe the scanner falls through the ground like in #28

The scanner is right where it's supposed to be, it's just not active:

Activating the object with Unity Runtime Editor makes it show up:

I don't know how to properly solve this. @Insprill any ideas?

Probably something with the PlayerDistanceMultipleGameObjectsOptimizer or PlayerDistanceGameObjectsDisabler, whichever one it uses. Most likely it isn't getting added.

this issue has disappeared.


Webview on linux does not support HTTP/2 or HTTP/3

What OS are you using (uname -a, or Windows version)?
Linux debian 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
This is a VM but I've received the same reports from full installs aswell across multiple distros.
What programming language are you using (C/C++/Go/Rust)?
go version go1.22.5 linux/amd64
What did you expect to see and what you saw instead?
I expect to see HTTP/2 or HTTP/3 connections, however webview on linux only uses HTTP/1.1.
Reproduction:
package main

import webview "github.com/webview/webview_go"

func main() {
	w := webview.New(true)
	defer w.Destroy()

	w.Navigate("https://cloudflare.com/cdn-cgi/trace")
	w.Run()
}

Note the http=http/1.1 line. On macOS or Windows it's using HTTP/2 or HTTP/3 where supported.

Sadly webview_go is currently pinned to webkit2gtk-4.0.
Bumped to 4.1 in our CI and build failed:
go build github.com/webview/webview_go:
# pkg-config --cflags  -- gtk+-3.0 webkit2gtk-4.0
Package webkit2gtk-4.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `webkit2gtk-4.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'webkit2gtk-4.0', required by 'virtual:world', not found
pkg-config: exit status 1

Should probably open an issue about it in the go repo...


Does not transition from stuck into non-sticky (default)

Fixes
There is a case when current instance is in a stuck state, and then something changes scroll position to be 0 so it should get to the default state, but currently state does not change. This change fixes that.
I can add tests, but first please let me know if this is reasonable.

@yowainwright Pushed test changes. Please let me know what you think

@krasnoukhov this is great work. I might piggy-back and a teeny-weeny bit if needed but your work will be in a new release very very soon! 🙏


[Feature Request] Docker image

There are any chance to have a docker image available?
Best regards,

it is very convenient to deploy via docker

DOCKER
Use Python 3.11 as the base image
FROM python:3.11
Set working directory
WORKDIR /work
Set pip to use Tsinghua mirror
RUN pip config set global.index-url https://pypi.tuna.tsinghua.edu.cn/simple/
Upgrade pip
RUN pip install --upgrade pip
Install git
RUN apt-get update && apt-get install -y git
Clone the repository
RUN git clone https://github.com/severian42/GraphRAG-Local-UI.git
Set working directory to the cloned repo
WORKDIR /work/GraphRAG-Local-UI
Install requirements
RUN pip install -r requirements.txt
Expose port 7860
EXPOSE 7860
Command to run the application
CMD ["python", "app.py"]
Here's the English translation of your question for GitHub:
Issue:
When executing inside the Docker container:
docker exec -it graphrag bash
wget http://<IP_ADDRESS>:7860

The service is accessible.
However, when trying:
wget http://<IP_ADDRESS>:7860

The service is not accessible.
Furthermore, when accessing from outside the container:
wget http://<IP_ADDRESS>:7860

The service is not accessible.
This suggests that the service is only bound to localhost within the container and is not properly exposed or accessible from outside the container or on other network interfaces.


API updates to support function level autocomplete

The main change here is to update the MessagingProvider methods to accept the relevant option bags for each type in support of https://github.com/Azure/azure-sdk-for-net/issues/21124. This helps because it will allow customizing the options that gets passed into the provider by taking into account the ServiceBusTriggerAttribute properties when calling from the ServiceBusListener.
I also updated the MessagingProvider and MessageProcessor methods to be protected as they do not need to be public for the expected usage scenarios.

/cc @apranaseth @alrod can you take a look?

/azp run net - servicebus - tests

/azp run net - servicebus - tests


Hotfix: Add call to set missing totalScore property

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Client: I followed the coding and design guidelines.

Description

Fix https://github.com/ls1intum/Artemis/issues/3243. Now when reviewing a tutor example submission you can see the total points.
Steps for Testing

Log in to Artemis
Navigate to Course Administration
..
Testing steps as described in the issue #3243

Test Coverage

Screenshots

Tested on TS2. Works as intended for both imported and newly created modeling exercises.  Good job!


Remove group_vars/all.yml

It's common practice to try and put all variables in the hosts /
inventory file rather than in group_vars/ (so you only have to edit one
file such as inventory or hosts.sample)
For example, some very-large Ansible projects using this characteristic:
https://github.com/kubernetes-incubator/kubespray
https://github.com/openshift/openshift-ansible

ping @kairen


Add Generated destructors.

This change is

crates/cairo-lang-lowering/src/lower/test_data/closure line 110 at r1 (raw file):

    ^**^
note: Trait has no implementation in context: core::traits::Drop::<test::PanicDestructable>.
note: Trait has no implementation in context: core::traits::Destruct::<test::PanicDestructable>.

Still checking where this is coming from.
Code quote:
error: Variable not dropped.
 --> lib.cairo:10:5
    || {
    ^**^
note: Trait has no implementation in context: core::traits::Drop::<test::PanicDestructable>.
note: Trait has no implementation in context: core::traits::Destruct::<test::PanicDestructable>.

crates/cairo-lang-lowering/src/lower/mod.rs line 1757 at r1 (raw file):
Previously, orizi wrote…
this is just the setup of the returned unit type?

yes

crates/cairo-lang-lowering/src/lower/test_data/closure line 110 at r1 (raw file):
Previously, orizi wrote…
any thoughts?

It comes from the borrower checker.

crates/cairo-lang-lowering/src/lower/test_data/closure line 110 at r1 (raw file):
Previously, ilyalesokhin-starkware wrote…
It comes from the borrower checker.

https://reviewable.io/reviews/starkware-libs/cairo/6220


auto deploy

Is it supposed to work like this:

hexo server at the server where my site is hosted or locally
browse mysite.com/admin/ or localhost:4000/admin/
create/edit/delete post
hit Deploy button (which I think you are going to add) and the static files will be copied to the desired place (via rsync, for example)

?

right, i'm planning to support that feature, thanks for you comment :smile:

OK, so I say :+1: for this feature!


Added Illustrator for developers post

Added post from Lightning Talk on Illustrator for Developers. Thanks!

Looks good, just fix the link that I commented on and I will merge it. I changed the link already so you'll just have to basically copy and paste.


Update File wokring workflow and setup pandas util

Related to the https://github.com/chimplie/google-documents/projects/1#card-12532216


NETOBSERV-116: Fix namespace deployment

Changed route between frontend and backend since the backend now use proxy alias to be namespace agnostic.

/hold
To coordinate both PR merge

/unhold

/approve


Change default XPath expression

The default XPath expression we use in the DefaultXMLSigner class is not(ancestor-or-self::ds:Signature). Apparently dotnet software gets confused by this, so we should change the default to not(ancestor-or-self::*[local-name()='Signature' and namespace-uri()='http://www.w3.org/2000/09/xmldsig#']).
@Razumain Both versions seem to work for the reference signature service.

Fixed in PR https://github.com/idsec-solutions/signservice-commons/pull/3.


Identify approach to inject cosmos secrets during build in Customer env

Spoke with the customer and there isn't a way to inject build secrets within the build pipeline. Only option was to pass it through the command line arguments but that is not ideal at all. We may need to revisit whether we want to run unit tests during the build phase for ngsa-java or have it similar to the dotnet version

Based on the findings from customer and possible workarounds, team will disable executing unit tests build time which will resolve the issue requiring cosmos db secret injections.


Unit Test Setup and Integration

Summary

[x] Setup unit tests
[x] Add unit test for components , pages and hooks
[x] Update CI/CD config for unit tests
[x] Add SonarQube integration

Screenshots

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Split FunctionParameterSyntax and related types

FunctionParameterSyntax was used in a number of cases (function parameter, closure parameter and enum case parameter) and because it needs to satisfy all of them all its parameters are optional. Split it into three different types that have non-optional children.
rdar://106874808

@swift-ci Please test

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test macOS

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test macOS

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test macOS

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test Linux

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test Windows

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test macOS

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test macOS

https://github.com/apple/swift/pull/64697
https://github.com/apple/swift-format/pull/495
https://github.com/apple/swift-stress-tester/pull/229
@swift-ci Please test Windows


Mark generated ANTLR files as such

Implements #4409, https://github.com/github/linguist/pull/4404#issuecomment-460610853
Matches .g files that have "generated by Xtest" on their second line.
My knowledge of Ruby is nil (null?) so hopefully I did this right.

Okay think I might be done with the PRs...


Firebase Auth: Unexpected update behavior (iOS)

Describe the bug
As reported in some other issues here, I've updated from an older version of cordova-plugin-firebase to this plugin. Yesterday I was finally able to build my app on iOS again. So I've uploaded a new beta version to TestFlight. The new (internal) TestFlight beta has already been approved.
What keeps me concerned is the fact, that TestFlight doesn't allow me to upgrade my existing app (installed from the App Store). It only offers to install it, which means the current version gets replaced and data is lost!
The app I'm talking about, uses Firebase Auth to login users anonymously. With that UID it stores some data in the realtime database and FireStore.
With this update, the user isn't logged in anymore. After installing the newest beta from TestFlight, all the data is lost. This is really a break, that I cannot afford. My (free) app has around 75.000 users. So if everyone loses his data, because of whatever the reason is, this is a deal breaker to me.

Additional context
I've also updated the cordova-ios platform with this update and some other cordova plugins as well.
Here are some additional informations:
 ~> ionic info

Ionic:

   Ionic CLI          : 5.0.2 (/usr/local/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.0

Cordova:

   Cordova CLI       : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms : android 8.0.0, ios 5.0.1
   Cordova Plugins   : cordova-plugin-ionic 5.3.0, cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 4.1.1, (and 28 other plugins)

Utility:

   cordova-res : 0.3.0
   native-run  : 0.2.5

System:

   Android SDK Tools : 26.1.1 (/Users/svzi/Library/Android/sdk)
   ios-deploy        : 1.9.2
   ios-sim           : 8.0.1
   NodeJS            : v8.11.3 (/usr/local/bin/node)
   npm               : 5.6.0
   OS                : macOS Mojave
   Xcode             : Xcode 10.2.1 Build version 10E1001

Any help would be really much appreciated!
Cheers,
Sven

With this update, the user isn't logged in anymore.

Is this because TestFlight forces you to re-install the app? (changes to this plugin cannot be the cause of that).
Or because you are now able to update the existing app but the new version of the Firebase SDK is not preserving the data from the previous installed version?

Is this because TestFlight forces you to re-install the app? (changes to this plugin cannot be the cause of that).
Or because you are now able to update the existing app but the new version of the Firebase SDK is not preserving the data from the previous installed version?

I simply don't know if this plugin could be the cause of it. I simply don't know what could be the cause of this mess in general and how to find the cause. 🤷🏼♂
You're really sure that the changes to this plugin can not be the cause of it? Do you have any idea, what could be cause that TestFlight isn't serving the newest beta version as update? How can this happen? I thought it had something to do with the changes I made. For me it seems to be reasonable that some of the updated libs is causing this issue. But as I already stated, I have no clue...

Unlike Android (where APK is bytecode that can be inspected at upload by the Play Store), iOS apps are compiled C binaries which means there's no way that App Store Connect can inspect the contents to see what libs have changed/are present.
The most likely explanation for this is related to signing of the app.
I only experienced a situation like this once before when distributing iOS apps outside of the App Store via Enterprise distribution. In that case, the new version of the app had been signed with a different certificate than the installed one, so it was not possible to update.
Are you sure that you didn't have a development version installed on your device when trying to update it via TestFlight?
I suggest carrying out this test:

Delete existing app off device
Install live version via App Store
Run and sign in with Firebase
Try to update via TestFlight

The most likely explanation for this is related to signing of the app.
I only experienced a situation like this once before when distributing iOS apps outside of the App Store via Enterprise distribution. In that case, the new version of the app had been signed with a different certificate than the installed one, so it was not possible to update.

😱
The provisioning profiles are only valid for one year, as far as I know. So I replaced the signing certificates as well. 🤦♂
Under this circumstances does that mean when somebody creates new signing certificates for his iOS Firebase app with anonymous user, that all the user data is lost with a new version of the app? I can't believe that! 🤬

Your signing certificates are only used for validation by the App Store - when Apple publishes an iOS app in the App Store it resigns with their own distribution certificate.
That means even if your uploaded app is signed with a different certificate (because the old one expired), it won't matter because Apple will resign it when publishing to the App Store anyway.
I presume the same resigning must take place for TestFlight builds otherwise you wouldn't be able to update an app installed from the App Store (signed with Apple distribution cert) with one from TestFlight  unless it was signed with the same cert.

That's something I would assume as well, but then I don't get the point why my app isn't updatable via TestFlight (only install and replace the current installation and the anonymous user that is currently signed in). 🤔

Did you try my test steps above?

Yup, that were my exact steps. I removed the installed app. Did a fresh install and opened the app. Completed my "Welcome Wizard" and created some user content. Closed app, re-opened it. Everything was still in place, as expected. Started TestFlight and it's only showing "install" instead of "update". When I tap "install" TestFlight even warns me, that this will replace my existing installation and data could be lost! When I install it, all that is true. I will start again with the "Welcome Wizard" (which usually only appears on first start of the app) and my content is gone. 😢

Sounds like the issue is with App Store Connect/TestFlight - you should be able to update.
Try these things (in order):

Uninstall/reinstall TestFlight app
In App Store Connect, open your app page

Select TestFlight tab
Select Builds > iOS
Select your build
Click "Expire build" button (top-right)
Build and upload a new build to App Store Connect

All done, except the new build is just uploading...
Just one question, do you have any experience with platforms like bitrise.io? I wonder if such kind of service would help me avoid such issues in the future...

I haven't encountered bitrise.io before but it seems like a new cloud build service.
I have had experience with others in the past: Phonegap Build and Telerik AppBuilder and I ended moving away from both back to a local build environment because they didn't give enough fine-grain control over the build.
My recommendation would be to stick with a local build environment if you are comfortable operating it. Remote cloud build services are OK if you lack the skills to setup your own local build environment but they come at the cost of flexibility and fine-grain control over your build process, not to mention debugging.

Thanks for your advice! I backed away from such kind of services the last couple of years as well. But this experience really let me re-think about all that stuff... At least bitrise.io is offering the ability to debug your project locally with the same settings (with there open sourced cli tools): https://discuss.bitrise.io/t/how-to-debug-your-build-locally-it-works-on-my-mac-pc-but-not-on-bitrise-io/392
But I'm still not sold. Just hoped you had some good experience with it, because you quickly became someone I trust about such type of questions.
Btw, after removing my latest build from TestFlight, I figured out that my last beta (uploaded about 3 or 4 weeks ago) already served the initial issue of this topic. It's not updatable on the version I've installed from the App Store. So, even if you wouldn't have explained why your modifications could not be the reason, it would be clear that this issue has nothing todo with what you did.
Good for you, but bad for me. Do you have any idea on how to fix this? If I would publish a new version, about 25.000 users of mine would lose their data. That's not acceptable, but not publishing any more updates to the app isn't acceptable as well. :-(

I'm out of ideas when it comes to this TestFlight update issue.
I would suggest that if searching Google and Stackoverflow comes up with nothing, you contact Apple tech support. After all, we pay our $99/year Apple Membership fee so should be able to tech support included with that! I'm pretty sure there's a way to ask this kind of question via App Store Connect...

I've just set a task for one of our junior devs to investigate bitrise.io and report back on whether they think it's any good. I'll let you know the result 😉

You're completely right about the Apple support. I've already had a call in the meanwhile. The person on the phone couldn't help me, but he will send me an email where I can reply with some further informations and screenshots, so he can forward it to someone with more knowledge in this topic.
Appreciate that you put on of your juniors devs on the bitrise investigation! Can't await to hear back about that topic. 👍


Update references to api keys in new relic user config

Dependent on https://github.com/newrelic/demo-deployer/pull/33
Resolves #31
Use docs.newrelic.com as a single source of truth, instead of having to manage steps to obtain keys in multiple places.

@alexronquillo this looks good.
Could I ask you to merge the latest main into this branch and to update the git actions deploy file which were referencing the deploy configs in tutorial/user_stories. There should be 6 files like this one .github\workflows\staging-aws-hello.yml


Multiple calls to defined type wildfly::host::server_config cause "Duplicate resource" error

Affected Puppet, Ruby, OS and module versions/distributions

Puppet/Ruby/Distribution: any
Module version: all probably since commit f80573f3, which allows this type to manage domains

How to reproduce
This happened when trying to replace the server groups with wildfly service active. This requires one call to wildfly::host::server_config to remove default groups, and another to create a replacement group. Simplified code excerpt:
  wildfly::host::server_config { ['server-one', 'server-two']:
    ensure   => absent,
  }
  if $configure_default_server {
    wildfly::host::server_config { $default_server_name:
      server_group => $default_server_group_name,
    }
  }

What are you seeing
First Puppet agent run fails with:
Error: Could not set 'present' on ensure: Failed with: {
  "host-failure-descriptions"=>{
    "master"=>"WFLYCTL0212: Duplicate resource [(\"host\" => \"master\"), (\"server-config\" => \"app\")]"
  }
} for {
  "address":[{"host":"master"},{"server-config":"app"}],
  "operation":"add",
  "auto-start":true,
  "group":"app-server-group",
  "socket-binding-port-offset":0,
  "operation-headers":null
}

What behaviour did you expect instead
Module should remove and add groups normally.
Any additional information you'd like to impart
All calls to wildfly_resource in wildfly::host::server_config use the same title: /host=${hostname}/server-config=${server_name} and wildfly_resource type uses this path as namevar. My suggested fix is to use title/name as namevar in wildfly_resource type and create unique titles in its calls in wildfly::host::server_config.

was this in before, or did i break it while migratin' it to vox?

Several attempts to reproduce the issue, with CentOS/Rock/RHEL 7 to 9 and Puppet 5 to 7, in different overall situations, all failed miserably. I'll take it as a failure not related to the module itself, but some misuse in my environment, and close this.
I'll reopen if ever I can find a setup which throws the error.


Clarification regarding ApprovingApplicationCausesPreparingTheEmbedding.RequestForOldRelease

We have two initiating request for this ApprovingApplicationCausesPreparingTheEmbedding.RequestForOldRelease callback.
initiating-requests:
- server-name: /v1/regard-updated-approval-status
uuid: ro-2-1-0-op-s-is-003
- server-name: /v1/update-operation-key
uuid: ro-2-1-0-op-s-bm-010
But , as per the concept , /v1/update-operation-key(ro-2-1-0-op-s-bm-010) only will be the initiating request for this forwarding.
Clarification required :
I think , /v1/regard-updated-approval-status(ro-2-1-0-op-s-is-003) is included because , the major API that initiates the ApprovingApplicationCausesPreparingTheEmbedding forwarding is this API and that’s the reason for the inclusion of this API as an initiating request.
Kindly please let me know whether this understanding is correct.
(Also the same doubt applicable for the RequestForUpdatingNewReleaseClient forwarding)

In AP_v2.1.0_spec, the AP://v1/inform-about-preceding-release had a security: apiKeyAuth statement.
In RO_v2.1.0_spec, The ApprovingApplicationCausesPreparingTheEmbedding process had a CreateLinkToGetOldRelease forwarding before the RequestForOldRelease forwarding.
So, it made sense to wait for RO://v1/update-operation-key providing the correct OperationKey for addressing AP://v1/inform-about-preceding-release.
In AP_v2.1.1_spec, it has been decided to remove the security: apiKeyAuth statement from AP://v1/inform-about-preceding-release according to AP issue#934.
The CreateLinkToGetOldRelease forwarding has been removed from the ApprovingApplicationCausesPreparingTheEmbedding process.
No, OperationKey will be provided via RO://v1/update-operation-key.
Consequently, it can no longer be an initiating-requests and has been removed from the ForwardingList and the CONFIGfile.


Detect Recursive structs

I cannot share my structs but somehow I have structs that relate to structs that relate back to structs so the body or ret param for the EndPoint function is recursive.
The code just freezes on:
sw.GenerateDocs()

I think it's a Struct similar to this:
type InParam struct {
 Other *InParam
}

I hope this helps. I love the idea of this project

Fixed in release v1.0.0


updated difficulty level for maximum-subarray

updated difficulty level Easy to Medium for maximum-subarray

Thanks, someone has made another PR at #291, so closing this. Appreciate it all the same!


Codepen demo doesn't work for me

Codepen demo doesn't work for me. It's just white page and nothing more. I don't know what further information might be useful to you, but taking a look at the network tab seems that graphql requests are successful too, so it's not a network issue.

It seems symlinks don't work properly with unpkg/npm. I have added back svg-loader.min.js here 284983a474a6d6b7b027ae3978c7d9c8666014f5.
This has fixed the problem.
https://codepen.io/shubhamjainco/pen/rNyBVmY


data bag

Could you please share your data bag with me???

You can try using any of the datasets for the cars project. For the blogposts, I used table

Thanks so much!