App freeze when send action in iOS simulator 15.0 if debugger is not attached

Description
Hello guys,
i'm new adopter in the composable architecture, the architecture seems good to me, but i face problem when i build and run my application to iOS simulator 15.0 it work fine my app can run perfectly, but if i stop running xcode and start my app directly by tapping app icon in simulator the app start freezing when i start to send action.
I don't know why, i also try provided example Search Project from this repostitory, it also freeze when i directly open the app from simulator by tapping app icon (without running xcode build & run)
I want to know why and how to solve this, does it will freeze as well in real device, since my application deployment target is 15.0 and i can did not have the device with iOS 15.0 to test it
Here is log file that i got when running the app
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 36DB9CF2-9295-447C-B846-3CE86ADBDCA2
CrashReporter Key:   AB298619-58B2-EAD9-670E-A937D1544BA9
Hardware Model:      MacBookPro18,1
Process:             Search [12075]
Path:                /Users/USER/Library/Developer/CoreSimulator/Devices/AC2344A6-3420-4BDF-87A5-9FA088C8849F/data/Containers/Bundle/Application/C615A1E2-3EF3-41F1-AD3C-931BE7B99F4A/Search.app/Search
Identifier:          co.pointfree.Search
Version:             1.0 (1)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd_sim [11538]
Coalition:           com.apple.CoreSimulator.SimDevice.AC2344A6-3420-4BDF-87A5-9FA088C8849F [1149]
Responsible Process: SimulatorTrampoline [1684]

Date/Time:           2023-09-13 09:35:17.5615 +0700
Launch Time:         2023-09-13 09:35:04.9137 +0700
OS Version:          macOS 13.4 (22F66)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: FRONTBOARD<PHONE_NUMBER>
<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:[application<co.pointfree.Search>:12075] failed to terminate gracefully after 5.0s
ProcessVisibility: Unknown
ProcessState: Running
WatchdogEvent: process-exit
WatchdogVisibility: Background
WatchdogCPUStatistics: (
"Elapsed total CPU time (seconds): 17.090 (user 10.320, system 6.770), 31% CPU",
"Elapsed application CPU time (seconds): 4.713, 9% CPU"
) reportType:CrashLog maxTerminationResistance:Interactive>

Triggered by Thread:  0

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1c7f861fc syscall_thread_switch + 8
1   libdispatch.dylib             	       0x180122b38 __DISPATCH_WAIT_FOR_ENQUEUER__ + 44
2   libdispatch.dylib             	       0x180117f44 _dispatch_main_queue_callback_4CF + 592
3   CoreFoundation                	       0x18034fc34 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
4   CoreFoundation                	       0x18034a1a4 __CFRunLoopRun + 2448
5   CoreFoundation                	       0x180349308 CFRunLoopRunSpecific + 572
6   GraphicsServices              	       0x18bf025ec GSEventRunModal + 160
7   UIKitCore                     	       0x184d3b4e0 -[UIApplication _run] + 992
8   UIKitCore                     	       0x184d3ffc0 UIApplicationMain + 112
9   SwiftUI                       	       0x1b93bed98 closure #1 in KitRendererCommon(_:) + 160
10  SwiftUI                       	       0x1b93becf4 runApp<A>(_:) + 164
11  SwiftUI                       	       0x1b8e12fb0 static App.main() + 80
12  Search                        	       0x100763154 static SearchApp.$main() + 160 (SearchApp.swift:4)
13  Search                        	       0x10076320c main + 12
14  dyld_sim                      	       0x101059c04 start_sim + 20
15  dyld                          	       0x101161f28 start + 2236

Thread 1:
0   libsystem_pthread.dylib       	       0x1c7fde634 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib       	       0x1c7fde634 start_wqthread + 0

Thread 3:: com.apple.uikit.eventfetch-thread
0   libsystem_kernel.dylib        	       0x1c7f86190 mach_msg2_trap + 8
1   libsystem_kernel.dylib        	       0x1c7f97258 mach_msg2_internal + 76
2   libsystem_kernel.dylib        	       0x1c7f8e398 mach_msg_overwrite + 540
3   libsystem_kernel.dylib        	       0x1c7f86500 mach_msg + 20
4   CoreFoundation                	       0x18034f770 __CFRunLoopServiceMachPort + 368
5   CoreFoundation                	       0x180349c84 __CFRunLoopRun + 1136
6   CoreFoundation                	       0x180349308 CFRunLoopRunSpecific + 572
7   Foundation                    	       0x180810a68 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 232
8   Foundation                    	       0x180810d20 -[NSRunLoop(NSRunLoop) runUntilDate:] + 88
9   UIKitCore                     	       0x184def638 -[UIEventFetcher threadMain] + 472
10  Foundation                    	       0x18083a4f4 __NSThread__start__ + 772
11  libsystem_pthread.dylib       	       0x1c7fe3428 _pthread_start + 116
12  libsystem_pthread.dylib       	       0x1c7fde648 thread_start + 8

Thread 4:
0   libsystem_pthread.dylib       	       0x1c7fde634 start_wqthread + 0

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x0000000000000004   x2: 0x00000000037c3fa4   x3: 0x0000000000000001
    x4: 0x0000000000000000   x5: 0x0000000000000819   x6: 0x0000000000000000   x7: 0x0000000000000000
    x8: 0x0000000000000000   x9: 0x0000000000000000  x10: 0xfffffffe7fe6d42b  x11: 0x0000000500000000
   x12: 0x0080000000000000  x13: 0x0000004000000001  x14: 0x0060001500001f01  x15: 0x0060001500001f01
   x16: 0xffffffffffffffc3  x17: 0x0060001500001f01  x18: 0x0000000000000000  x19: 0x000000014651d740
   x20: 0x00000000037c3fa4  x21: 0x00000001da81b370  x22: 0x0000000000000000  x23: 0x00000001d6408d40
   x24: 0x000000000000000f  x25: 0x000000014651d730  x26: 0x0000000000000000  x27: 0x0000000000000000
   x28: 0x0000000000000000   fp: 0x000000016f6ad340   lr: 0x0000000180122b38
    sp: 0x000000016f6ad330   pc: 0x00000001c7f861fc cpsr: 0x60001000
   far: 0x000000016be0f7d8  esr: 0x56000080  Address size fault

Binary Images:
       0x10115c000 -        0x1011ebfff dyld (*) <bd993f39-c902-37d6-8bd8-6d827c7f121e> /usr/lib/dyld
       0x101058000 -        0x101093fff dyld_sim (*) <cc38080d-7c09-357a-b552-db1b456781ce> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/dyld_sim
       0x100750000 -        0x100a1ffff co.pointfree.Search (1.0) <2b456848-c867-3380-a86e-078be974106f> /Users/USER/Library/Developer/CoreSimulator/Devices/AC2344A6-3420-4BDF-87A5-9FA088C8849F/data/Containers/Bundle/Application/C615A1E2-3EF3-41F1-AD3C-931BE7B99F4A/Search.app/Search
       0x1010f0000 -        0x1010fbfff libobjc-trampolines.dylib (*) <a93817cc-8f74-3435-a719-034429e1417c> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libobjc-trampolines.dylib
       0x1c7f85000 -        0x1c7fbcfff libsystem_kernel.dylib (*) <f91811dc-efe8-3dfa-9553-71defa7ed45f> /usr/lib/system/libsystem_kernel.dylib
       0x180107000 -        0x180149fff libdispatch.dylib (*) <0d3a8420-f29e-3699-aa94-3597b8eca236> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib
       0x1802cb000 -        0x180677fff com.apple.CoreFoundation (6.9) <6cbe5db0-f3ed-3227-a6b6-df5dbe7642aa> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
       0x18beff000 -        0x18bf07fff com.apple.GraphicsServices (1.0) <5de73649-0b11-3099-9a52-7ce3c01a8d93> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
       0x184137000 -        0x1855b7fff com.apple.UIKitCore (1.0) <5cb38825-44d8-33eb-b2f4-90e8d179c29e> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore
       0x1b8a25000 -        0x1b97e4fff com.apple.SwiftUI (<IP_ADDRESS>.102) <9ea09c48-18ac-31b7-bb1a-12fa6e66f3f3> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/SwiftUI.framework/SwiftUI
       0x1c7fdc000 -        0x1c7fe8fff libsystem_pthread.dylib (*) <ba7c01fe-353b-3146-a7c6-f2bb8a0fa842> /usr/lib/system/libsystem_pthread.dylib
       0x1806ea000 -        0x1809a9fff com.apple.Foundation (6.9) <e14c8373-8298-3e74-afc5-61dddc413228> /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/Foundation.framework/Foundation

EOF

-----------
Full Report
-----------

{"app_name":"Search","timestamp":"2023-09-13 09:35:17.00 +0700","app_version":"1.0","slice_uuid":"2b456848-c867-3380-a86e-078be974106f","build_version":"1","platform":7,"bundleID":"co.pointfree.Search","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.4 (22F66)","roots_installed":0,"name":"Search","incident_id":"36DB9CF2-9295-447C-B846-3CE86ADBDCA2"}
{
  "uptime" : 1000,
  "procRole" : "Foreground",
  "version" : 2,
  "userID" : 501,
  "deployVersion" : 210,
  "modelCode" : "MacBookPro18,1",
  "coalitionID" : 1149,
  "osVersion" : {
    "train" : "macOS 13.4",
    "build" : "22F66",
    "releaseType" : "User"
  },
  "captureTime" : "2023-09-13 09:35:17.5615 +0700",
  "incident" : "36DB9CF2-9295-447C-B846-3CE86ADBDCA2",
  "pid" : 12075,
  "translated" : false,
  "cpuType" : "ARM-64",
  "roots_installed" : 0,
  "bug_type" : "309",
  "procLaunch" : "2023-09-13 09:35:04.9137 +0700",
  "procStartAbsTime" :<PHONE_NUMBER>5,
  "procExitAbsTime" :<PHONE_NUMBER>3,
  "procName" : "Search",
  "procPath" : "\/Users\/USER\/Library\/Developer\/CoreSimulator\/Devices\/AC2344A6-3420-4BDF-87A5-9FA088C8849F\/data\/Containers\/Bundle\/Application\/C615A1E2-3EF3-41F1-AD3C-931BE7B99F4A\/Search.app\/Search",
  "bundleInfo" : {"CFBundleShortVersionString":"1.0","CFBundleVersion":"1","CFBundleIdentifier":"co.pointfree.Search"},
  "storeInfo" : {"deviceIdentifierForVendor":"760ED7CF-A1DF-55E6-BF8C-C889D01B30BB","thirdParty":true},
  "parentProc" : "launchd_sim",
  "parentPid" : 11538,
  "coalitionName" : "com.apple.CoreSimulator.SimDevice.AC2344A6-3420-4BDF-87A5-9FA088C8849F",
  "crashReporterKey" : "AB298619-58B2-EAD9-670E-A937D1544BA9",
  "responsiblePid" : 1684,
  "responsibleProc" : "SimulatorTrampoline",
  "codeSigningID" : "co.pointfree.Search",
  "codeSigningTeamID" : "",
  "codeSigningFlags" : 570425861,
  "codeSigningValidationCategory" : 10,
  "codeSigningTrustLevel" : 0,
  "sip" : "enabled",
  "exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGKILL"},
  "termination" : {"code":2343432205,"flags":6,"namespace":"FRONTBOARD","reasons":["<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:[application<co.pointfree.Search>:12075] failed to terminate gracefully after 5.0s","ProcessVisibility: Unknown","ProcessState: Running","WatchdogEvent: process-exit","WatchdogVisibility: Background","WatchdogCPUStatistics: (","\"Elapsed total CPU time (seconds): 17.090 (user 10.320, system 6.770), 31% CPU\",","\"Elapsed application CPU time (seconds): 4.713, 9% CPU\"",") reportType:CrashLog maxTerminationResistance:Interactive>"]},
  "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":68,"task_for_pid":7},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
  "faultingThread" : 0,
  "threads" : [{"triggered":true,"id":61155,"threadState":{"x":[{"value":0},{"value":4},{"value":58474404},{"value":1},{"value":0},{"value":2073},{"value":0},{"value":0},{"value":0},{"value":0},{"value":18446744067265451051},{"value":21474836480},{"value":36028797018963968},{"value":274877906945},{"value":27021687958544129},{"value":27021687958544129},{"value":18446744073709551555},{"value":27021687958544129},{"value":0},{"value":5474735936},{"value":58474404},{"value":7960900464,"symbolLocation":16,"symbol":"taskHeapMetadata"},{"value":0},{"value":7889521984,"symbolLocation":0,"symbol":"_dispatch_main_q"},{"value":15},{"value":5474735920},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6443641656},"cpsr":{"value":1610616832},"fp":{"value":6164239168},"sp":{"value":6164239152},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":7649911292,"matchesCrashFrame":1},"far":{"value":6104872920}},"queue":"com.apple.main-thread","frames":[{"imageOffset":4604,"symbol":"syscall_thread_switch","symbolLocation":8,"imageIndex":4},{"imageOffset":113464,"symbol":"__DISPATCH_WAIT_FOR_ENQUEUER__","symbolLocation":44,"imageIndex":5},{"imageOffset":69444,"symbol":"_dispatch_main_queue_callback_4CF","symbolLocation":592,"imageIndex":5},{"imageOffset":543796,"symbol":"__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__","symbolLocation":12,"imageIndex":6},{"imageOffset":520612,"symbol":"__CFRunLoopRun","symbolLocation":2448,"imageIndex":6},{"imageOffset":516872,"symbol":"CFRunLoopRunSpecific","symbolLocation":572,"imageIndex":6},{"imageOffset":13804,"symbol":"GSEventRunModal","symbolLocation":160,"imageIndex":7},{"imageOffset":12600544,"symbol":"-[UIApplication _run]","symbolLocation":992,"imageIndex":8},{"imageOffset":12619712,"symbol":"UIApplicationMain","symbolLocation":112,"imageIndex":8},{"imageOffset":10067352,"symbol":"closure #1 in KitRendererCommon(_:)","symbolLocation":160,"imageIndex":9},{"imageOffset":10067188,"symbol":"runApp<A>(_:)","symbolLocation":164,"imageIndex":9},{"imageOffset":4120496,"symbol":"static App.main()","symbolLocation":80,"imageIndex":9},{"imageOffset":78164,"sourceLine":4,"sourceFile":"SearchApp.swift","symbol":"static SearchApp.$main()","imageIndex":2,"symbolLocation":160},{"imageOffset":78348,"sourceFile":"SearchApp.swift","symbol":"main","symbolLocation":12,"imageIndex":2},{"imageOffset":7172,"symbol":"start_sim","symbolLocation":20,"imageIndex":1},{"imageOffset":24360,"symbol":"start","symbolLocation":2236,"imageIndex":0}]},{"id":61174,"frames":[{"imageOffset":9780,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":10}]},{"id":61176,"frames":[{"imageOffset":9780,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":10}]},{"id":61178,"name":"com.apple.uikit.eventfetch-thread","frames":[{"imageOffset":4496,"symbol":"mach_msg2_trap","symbolLocation":8,"imageIndex":4},{"imageOffset":74328,"symbol":"mach_msg2_internal","symbolLocation":76,"imageIndex":4},{"imageOffset":37784,"symbol":"mach_msg_overwrite","symbolLocation":540,"imageIndex":4},{"imageOffset":5376,"symbol":"mach_msg","symbolLocation":20,"imageIndex":4},{"imageOffset":542576,"symbol":"__CFRunLoopServiceMachPort","symbolLocation":368,"imageIndex":6},{"imageOffset":519300,"symbol":"__CFRunLoopRun","symbolLocation":1136,"imageIndex":6},{"imageOffset":516872,"symbol":"CFRunLoopRunSpecific","symbolLocation":572,"imageIndex":6},{"imageOffset":1206888,"symbol":"-[NSRunLoop(NSRunLoop) runMode:beforeDate:]","symbolLocation":232,"imageIndex":11},{"imageOffset":1207584,"symbol":"-[NSRunLoop(NSRunLoop) runUntilDate:]","symbolLocation":88,"imageIndex":11},{"imageOffset":13338168,"symbol":"-[UIEventFetcher threadMain]","symbolLocation":472,"imageIndex":8},{"imageOffset":1377524,"symbol":"__NSThread__start__","symbolLocation":772,"imageIndex":11},{"imageOffset":29736,"symbol":"_pthread_start","symbolLocation":116,"imageIndex":10},{"imageOffset":9800,"symbol":"thread_start","symbolLocation":8,"imageIndex":10}]},{"id":61181,"frames":[{"imageOffset":9780,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":10}]}],
  "usedImages" : [
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "size" : 589824,
    "uuid" : "bd993f39-c902-37d6-8bd8-6d827c7f121e",
    "path" : "\/usr\/lib\/dyld",
    "name" : "dyld"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "size" : 245760,
    "uuid" : "cc38080d-7c09-357a-b552-db1b456781ce",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/usr\/lib\/dyld_sim",
    "name" : "dyld_sim"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "1.0",
    "CFBundleIdentifier" : "co.pointfree.Search",
    "size" : 2949120,
    "uuid" : "2b456848-c867-3380-a86e-078be974106f",
    "path" : "\/Users\/USER\/Library\/Developer\/CoreSimulator\/Devices\/AC2344A6-3420-4BDF-87A5-9FA088C8849F\/data\/Containers\/Bundle\/Application\/C615A1E2-3EF3-41F1-AD3C-931BE7B99F4A\/Search.app\/Search",
    "name" : "Search",
    "CFBundleVersion" : "1"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "size" : 49152,
    "uuid" : "a93817cc-8f74-3435-a719-034429e1417c",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/usr\/lib\/libobjc-trampolines.dylib",
    "name" : "libobjc-trampolines.dylib"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "size" : 229376,
    "uuid" : "f91811dc-efe8-3dfa-9553-71defa7ed45f",
    "path" : "\/usr\/lib\/system\/libsystem_kernel.dylib",
    "name" : "libsystem_kernel.dylib"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "size" : 274432,
    "uuid" : "0d3a8420-f29e-3699-aa94-3597b8eca236",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/usr\/lib\/system\/libdispatch.dylib",
    "name" : "libdispatch.dylib"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "6.9",
    "CFBundleIdentifier" : "com.apple.CoreFoundation",
    "size" : 3854336,
    "uuid" : "6cbe5db0-f3ed-3227-a6b6-df5dbe7642aa",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/System\/Library\/Frameworks\/CoreFoundation.framework\/CoreFoundation",
    "name" : "CoreFoundation",
    "CFBundleVersion" : "1854"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "1.0",
    "CFBundleIdentifier" : "com.apple.GraphicsServices",
    "size" : 36864,
    "uuid" : "5de73649-0b11-3099-9a52-7ce3c01a8d93",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/System\/Library\/PrivateFrameworks\/GraphicsServices.framework\/GraphicsServices",
    "name" : "GraphicsServices",
    "CFBundleVersion" : "1.0"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "1.0",
    "CFBundleIdentifier" : "com.apple.UIKitCore",
    "size" : 21499904,
    "uuid" : "5cb38825-44d8-33eb-b2f4-90e8d179c29e",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/System\/Library\/PrivateFrameworks\/UIKitCore.framework\/UIKitCore",
    "name" : "UIKitCore",
    "CFBundleVersion" : "5067.3.107"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "<IP_ADDRESS>.102",
    "CFBundleIdentifier" : "com.apple.SwiftUI",
    "size" : 14417920,
    "uuid" : "9ea09c48-18ac-31b7-bb1a-12fa6e66f3f3",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/System\/Library\/Frameworks\/SwiftUI.framework\/SwiftUI",
    "name" : "SwiftUI",
    "CFBundleVersion" : "<IP_ADDRESS>.102"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "size" : 53248,
    "uuid" : "ba7c01fe-353b-3146-a7c6-f2bb8a0fa842",
    "path" : "\/usr\/lib\/system\/libsystem_pthread.dylib",
    "name" : "libsystem_pthread.dylib"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "6.9",
    "CFBundleIdentifier" : "com.apple.Foundation",
    "size" : 2883584,
    "uuid" : "e14c8373-8298-3e74-afc5-61dddc413228",
    "path" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 15.0.simruntime\/Contents\/Resources\/RuntimeRoot\/System\/Library\/Frameworks\/Foundation.framework\/Foundation",
    "name" : "Foundation",
    "CFBundleVersion" : "1854"
  }
],
  "sharedCache" : {
  "base" :<PHONE_NUMBER>,
  "size" :<PHONE_NUMBER>,
  "uuid" : "eb51e136-9e77-3be9-9d45-c0d3bfe7aace"
},
  "vmSummary" : "ReadOnly portion of Libraries: Total=895.1M resident=0K(0%) swapped_out_or_unallocated=895.1M(100%)\nWritable regions: Total=610.0M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=610.0M(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nActivity Tracing                   256K        1 \nColorSync                          128K        5 \nCoreAnimation                      304K        4 \nFoundation                          16K        1 \nKernel Alloc Once                   32K        1 \nMALLOC                           213.7M       38 \nMALLOC guard page                  128K        8 \nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.1M        5 \nStack                             10.1M        5 \nVM_ALLOCATE                       1056K        2 \n__DATA                            15.9M      406 \n__DATA_CONST                      34.7M      407 \n__DATA_DIRTY                        50K        9 \n__FONT_DATA                          4K        1 \n__LINKEDIT                       510.5M        5 \n__OBJC_RO                         61.8M        1 \n__OBJC_RW                         3040K        1 \n__TEXT                           384.6M      415 \n__UNICODE                          588K        1 \ndyld private memory               1568K        5 \nmapped file                      156.7M        8 \nshared memory                       16K        1 \n===========                     =======  ======= \nTOTAL                              1.8G     1331 \nTOTAL, minus reserved VM space     1.4G     1331 \n",
  "legacyInfo" : {
  "threadTriggered" : {
    "queue" : "com.apple.main-thread"
  }
},
  "logWritingSignature" : "40368b710c14f7c82fa849df6f1be471c76a601b",
  "trialInfo" : {
  "rollouts" : [
    {
      "rolloutId" : "60da5e84ab0ca017dace9abf",
      "factorPackIds" : {

      },
      "deploymentId" : 240000008
    },
    {
      "rolloutId" : "62c74108bcb0435c2153f963",
      "factorPackIds" : {
        "SIRI_TEXT_TO_SPEECH" : "64dab7fd2cc76d455338aa84"
      },
      "deploymentId" : 240000325
    }
  ],
  "experiments" : [
    {
      "treatmentId" : "3a3cf641-8471-4e4e-9ad4-81d0ede970fd",
      "experimentId" : "64a84dae90d82611a0bd7d3d",
      "deploymentId" : 400000004
    },
    {
      "treatmentId" : "d28d100b-301c-49ae-b6c9-57930102d4d4",
      "experimentId" : "64466b09a3b9440a82a18c34",
      "deploymentId" : 400000002
    }
  ]
}
}

Model: MacBookPro18,1, BootROM 8422.121.1, proc 10:8:2 processors, 16 GB, SMC
Graphics: Apple M1 Pro, Apple M1 Pro, Built-In
Display: Color LCD, 3456 x 2234 Retina, Main, MirrorOff, Online
Memory Module: LPDDR5, Samsung
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x4387), wl0: Apr  7 2023 15:18:26 version <IP_ADDRESS>.8.7.146 FWID 01-aff1b48a
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB31Bus
USB Device: USB31Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.

Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
my application will not freeze when i open directly by tapping app icon in simulator
Actual behavior
My application freezes when start to send action to reducer, but it works well when i run my application via xcode Build & Run
Steps to reproduce

Download example project
https://github.com/pointfreeco/swift-composable-architecture/tree/main/Examples/Search
Change Minimum Deployment to iOS 15.0
Build and run in Simulator 15.0
Close xcode and open the app again directly by tapping app icon in simulator
Start typing and it will freeze

The Composable Architecture version information
1.2.0
Destination operating system
iOS 15 Simulator
Xcode version information
Xcode 14.3.0
Swift Compiler version information
swift-driver version: 1.75.2 Apple Swift version 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)
Target: arm64-apple-macosx13.0

@dwirandyh I can't reproduce this, which makes me think it's an Apple bug or local/temporary build issue, and not a bug with the library. I'm going to convert to a discussion for now, but if there's a reliable reproduction that points to an issue in TCA and not a more general bug in Apple's tools, please open another issue!


Add field in Score type to keep result info from go test -json

Running go test -json can provide more details that the frontend can show to the user. To simplify displaying these details, we should add a field to the Score object. We should decide whether to "modeled" the JSON output from go test -json in proto format or simply storing it as a JSON string.

We can add a new message type to score.proto to retain this information. See here and here for the Go struct to mimic.

Related to this, we should also remove the ISubmission type in the frontend and replace the computation of the passed / failed tests computation based on actual data from the build output. Currently, this is being computed using the score of each test instead of the actual passing/failing of the tests. See here for the old frontend and here for the new frontend.
We could also do this computation on the server and include the information in the BuildInfo struct that can be used directly in the frontend.

This will really only be useful if we implement corresponding stuff in the frontend.

Another idea came to mind related to this. We could add to score.proto either

A boolean aboveLimit which would allow tests like this score.getAboveLimit().
Or int32 MinScore which would allow tests like this score.getScore() >= score.getMinScore()

This would make it easier to use the score object in the frontend. This will require that the server initialize/augment the score object with score limit information from the assignment.

Correction: The limit / minimal score doesn't apply to each individual score object, but to the aggregate score. The aggregate score is currently in ag.proto:Submission. Maybe we need a minScore field in Submission instead.

Here is the proto message corresponding to the json output generated by go test -json:
message GoTestInfo {
    uint64 ID                      = 1;
    google.protobuf.Timestamp Time = 2;
    string Action                  = 3;
    string Package                 = 4;
    string Test                    = 5;
    double Elapsed                 = 6;
    string Output                  = 7;
}

This proto object could be serialized as JSON into the TestDetails field of the Score object for storage in the database and transmission to the frontend for displaying certain details.

A recent proposal has been raised to add parsing support for the go test -json output. We should wait for this to land or help it get landed.

There is this issue that would help simplify our score functions.


ROIcoin v<IP_ADDRESS>: it is not opening Links and Social Networks

Hey Guys,
I have just installed the wallet ROIcoin v<IP_ADDRESS>. It is working fine, except the links and social menu options. When I try open a link or a social network it returns the error
"Failed to run the default web browser. Input/output error."
I am using Linux Mint 18.3 and I have two web browsers: Google Chrome and FireFox.
Regards
JonathanLS

Hi Jonathan
You will need to set your default web browser in system settings->defails->application settings
QT5 is relying on xdg-settings to figure out your browser.
For me this works fine as long as you start ROIcoin-qt as the user you are logged into via the GUI.
So doing sudo for example in a terminal, wont work because xdg-settings don't get populated if you change user.

I put Google Chrome as my default web browser. Restarted it and opened the wallet. Same error.


test pull request

This pull request is a test to check if the checks are triggered.
Changes:

changed version number

I've added the following features:

added a stub for a get_info function that is a basis for recreating and storing objects in f3dasm
added .github workflow functionality to run tests on windows and macos (commented out for now!)
loosened scikit-learn dependency
added a sed command for job array formatting on HPC

I added the following

.coveragerc file for options on pytest-cov
removed unused optimizers (cmaesadam
added ways to save and load objects to a JSON-format
fixed compatibility issues with macOS and Windows
fixed issues #91 and #92
added notebooks/*.ipynb to .gitignore, but exluded !notebooks/tutorials/
removed hydra of requirements.txt: hydra-core is the right package!

changed version number
added a stub for a get_info function that is a basis for recreating and storing objects in f3dasm
added .github workflow functionality to run tests on windows and macos (commented out for now!)
loosened scikit-learn dependency
added a sed command for job array formatting on HPC
.coveragerc file for options on pytest-cov
removed unused optimizers (cmaesadam)
added ways to save and load objects to a JSON-format
fixed compatibility issues with macOS and Windows
fixed issues
output type is not correct #91 and
The link seems to be broken #92
added notebooks/*.ipynb to .gitignore, but exluded !notebooks/tutorials/
removed hydra of requirements.txt: hydra-core is the right package!


information_schema should be unprotected + raise exception on grant/revoke/deny

Codecov Report

:exclamation: No coverage uploaded for pull request base (schema_privileges@7ecae58). Click here to learn what that means.
The diff coverage is 92.85%.

@@                 Coverage Diff                  @@
##             schema_privileges    #5895   +/-   ##
====================================================
  Coverage                     ?   82.99%
  Complexity                   ?    12146
====================================================
  Files                        ?     1427
  Lines                        ?    46537
  Branches                     ?     5739
====================================================
  Hits                         ?    38625
  Misses                       ?     5238
  Partials                     ?     2674

Impacted Files
Coverage Δ
Complexity Δ

...main/java/io/crate/analyze/PrivilegesAnalyzer.java
94.59% <100%> (ø)
26 <5> (?)

.../main/java/io/crate/operation/user/Privileges.java
61.53% <66.66%> (ø)
7 <0> (?)

Continue to review full report at Codecov.

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


I want to make a Text Editor application.

Describe the project
This app will convert simple text into bold,italic,underlined and centered
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

Additional context
Add any other context or screenshots about the project here.
Screenshots

If applicable, add screenshots to help explain your problem.

I am intrested in these

Project is already present


Fix various typos

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

I adjusted/reduced the lines fixed, to not include the various "intended typos" mentioned in the review comments. This is ready to review again.

Hey @phil-davis thanks for the many many typo fixes. Much appreciated.
Cheers,
TP


Add Michael Salvati to challenge list

Description of changes

Issue Resolved

Fixes #

Wow! Thanks so much for your contribution. It means the world to us here at Operation Code.
As a token of our gratitude, please fill out this form to receive some stickers and a handwritten "thank you" note. ❤


Create Behavior Definition for Managed Scenario

Tutorial URL: https://developers.sap.com/tutorials/abap-environment-behavior.html
Hi everybody,
it is no big deal, but in Step 2.4 and 2.5 we are replacing the coding in Global Class and Local Types completly by copy/pasting something new in. Actually the only difference is, that we are adding the type tt_travel_update and this type is not used in the tutorial (probably in a further tutorial it is).
Wouldn't it make more sense, to add the type in the later tutorial when it is actually needed and here we do not adjust the generated coding.
IMHO replacing code with other code by just copy/pasting with no further explanation does not bring a lot of learning experience to the participant.
Best regards,
Sebastian Freilinger

Hi @freilinger,
thank you for your feedback. We will add more information to this step. We have to make these tutorials user-friendly and they also should be suitable for beginners, that's why we did it this way. But we will provide more information on the step you've mentioned.
Thank you.
Best regards,
Merve

Thanks a lot for caring, Merve.

@freilinger Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Add slack-invite link

Update way to join the slack.

Can one of the admins verify this patch?

Worked for me.


[Test] Add test to coverage topic unload and issue #538.

Motivation
Add test to coverage topic unload and for #538 .

Codecov Report

Merging #539 (d9f628d) into master (f2d5a28) will increase coverage by 0.60%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #539      +/-   ##
============================================
+ Coverage     73.92%   74.53%   +0.60%
- Complexity      599      602       +3
============================================
  Files            83       83
  Lines          2788     2788
  Branches        195      195
============================================
+ Hits           2061     2078      +17
+ Misses          601      585      -16
+ Partials        126      125       -1

Impacted Files
Coverage Δ

...e/pulsar/handlers/mqtt/utils/PulsarTopicUtils.java
76.36% <0.00%> (+1.81%)
:arrow_up:

...tt/support/DefaultProtocolMethodProcessorImpl.java
77.77% <0.00%> (+3.36%)
:arrow_up:

.../mqtt/messages/codes/mqtt3/Mqtt3SubReasonCode.java
100.00% <0.00%> (+11.11%)
:arrow_up:

...mqtt/messages/factory/MqttSubAckMessageHelper.java
91.17% <0.00%> (+11.76%)
:arrow_up:

Continue to review full report at Codecov.

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


Client Certification Expiry Date

hi
i want to set expiry date for my client
which lines of code or files should i edit?
Its so good to add an option to ask the servers admin for Expiry Date!
TNX

export EASYRSA_CERT_EXPIRE=30
Where 30 is the number of days.


[3.2] Batch of lightmapper fixes and minor improvements

Fix objects with no material being considered as fully transparent by the lightmapper. Fixes #46861.
Added "environment_min_light" property: gives artistic control over the shadow color.
Fixed "Custom Color" environment mode, it was ignored before.
Added "interior" property to BakedLightmapData: controls whether dynamic capture objects receive environment light or not. Fixes #46591.
Automatically update dynamic capture objects when the capture data changes (also works for "energy" which used to require object movement to trigger the update).
Added "use_in_baked_light" property to GridMap: controls whether the GridMap will be included in BakedLightmap bakes.
Set "flush zero" and "denormal zero" mode for SSE2 instructions in the Embree raycaster. According to Embree docs it should give a performance improvement.

Pushed a new version, all the comments should be addressed now :)

Thanks!

Added "environment_min_light" property: gives artistic control over the shadow color.

I was thinking about this since the "min_light" terminology reminds me a lot of the minlight functionality available in Quake lightmapping tools.
In particular, we may want to have an option to add the ambient lighting to the lightmap instead of clamping the darkest lighting values to avoid. Improved versions of the Quake light tool (such as the one linked above) provide this as an --addmin option:

−addmin
Changes the behaviour of minlight. Instead of increasing low light levels to the global minimum, add the global minimum light level to all style 0 lightmaps. This may help reducing the sometimes uniform minlight effect.

Is this already supported by configuring ambient light in the Environment?

@Calinou I was debating myself whether to add a "min" or an "add" option and I decided to go with "min" because it won't modify the overall brightness of the scene, it will only affect dark spots.
But I can see how a global "add" could also be useful. Right now you can set a custom environment color that adds light to the scene, but it takes geometry into account, so regions of the scene that are mostly covered wil not receive much of that light.


Unable to add the Virtual Environment in VsCode

Behaviour: Unable to add interpreter path in VsCode
Expected vs. Actual
when I try to add path of virtual env it is prompting something like ->

An Invalid Python interpreter is selected, please try changing it to enable features such as IntelliSense, linting, and debugging.

Previously when I use to add the python env path to the interpreter it works but,
Now its not working properly

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

dyld[68805]: Library not loaded: /Library/Frameworks/Python.framework/Versions/3.9/Python
  Referenced from: <890ACB28-1692-301B-9F2B-C4C559FC3ABC> /Users/env/bin/python3
  Reason: tried: '/Library/Frameworks/Python.framework/Versions/3.9/Python' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Library/Frameworks/Python.framework/Versions/3.9/Python' (no such file), '/Library/Frameworks/Python.framework/Versions/3.9/Python' (no such file), '/System/Library/Frameworks/Python.framework/Versions/3.9/Python' (no such file, not in dyld cache)
zsh: abort      python3 main.py

User Settings

languageServer: "Pylance"

Okay I figured out the solution that, actually the venv I was working on was not created on the system.
Recently I have updated and reset my Mac OS thats why I have the copy of the actual Venv, because of the Factory reset system files were deleted and I was not able to run the copied venv.

Solution : Need to create new Venv and write requirements into it, using following commands

To create the requirement.txt file, we can use the following command:
pip3 freeze > requirements.txt

Now that our Python requirements file is all set up, let's take a look at how to install packages from it.
pip install -r requirements.txt

@Sahil-B07 Have you tried the Python: Create Environment command from the python extension? we allow you to select requirements.txt files as a part of the process.

Yes @karthiknadig I figured out that and it works.
Creating a new Environment and writing requirements.txt into it works.
Really appreciate and Thanks for the help.


typo: Double word "see"

@nschonni : Thanks for your contribution! The author, @CarlRabeler, has been notified to review your proposed change.

#sign-off


Native example code for JS components is not equivalent with JQuery alternative

Expected Behavior
The native code examples provided should work without modifications and be equivalent to their JQuery counterpart.
Current Behavior
The current examples that should work on multiple document fragments use document.querySelector instead of document.querySelectorAll(). In addition there is no document ready wrapper.
Possible Solution
I should be able to come up with a PR.
Context
When copying the native code, parallax stopped working which triggered me to look into it.
Your Environment
Not relevant.

This is how I'd fix parallax. If that's OK, I'll fix the rest of the examples accordingly and create a PR.
diff --git a/jade/page-contents/parallax_content.html b/jade/page-contents/parallax_content.html
index 4ac65b35..14e58cfa 100644
--- a/jade/page-contents/parallax_content.html
+++ b/jade/page-contents/parallax_content.html
@@ -20,8 +20,12 @@

Initialization

-  var elem = document.querySelector('.parallax');
-  var instance = M.Parallax.init(elem, options);
+  document.addEventListener('DOMContentLoaded', function(event) {
+    var coll = document.querySelectorAll('.parallax');
+    coll.forEach(function(pxe, idx, lst) {
+      M.Parallax.init(pxe, options);
+    });
+  });

   // Or with jQuery

The init method supports querySelectorAll so you don't need to use a forEach.

Updated JS init code to use querySelectorAll in 1ce0d324e110da31aba7cabd36232870b0e63e3b


add folder structure from input to output

I specified the issue here - https://github.com/imagemin/imagemin/issues/191
Basically the folder structure from your input was not matching your output.  So I've put a fix to make sure any folders in your glob will be replicated in your output
e.g. input/foo/bar/my-img.jpg -> output/foo/bar/my-img.jpg

Hmm looks like it's failing on windows path, not sure if it's my test or my code.  Not a window's guys so not sure why the paths are not working?

this isn't added yet?

 Need it badly.

Closing for lack of activity. I also don't think this is the correct approach.

@sindresorhus what is the right approach?


Add gradient_average flag support for sparse grads

Added support for disabling the gradient average for sparse grads.
Logic copied from here: https://github.com/microsoft/DeepSpeed/blob/2210ebe70f68135b6b43e91323a7d96a403a2299/deepspeed/runtime/engine.py#L2172

@jeffra Looks like a problem with github action nv-lightning-v100

@jeffra Could you check this PR?

@Dipet, thanks!


Develop/audrey

removed RSS button

@simontoussaint I'm not sure you did

@pefavre anything that shouldn't be there?

The Subscribe button is still there:

Don't know who did that. I suspect a marketer with low integration knowledge.

@pefavre should be fixed now. Sorry for the double trouble!

Your changes must still be in local, because it's still not there :)
We'll investigate tomorrow


🆕 Software Suggestion | Session (ex-Loki Messenger)

Basic Information
Name: Session (ex-Loki Messenger)
Category: Encrypted Instant Messengers - Decentralized
URL: https://getsession.org/
Platforms: Desktop (Mac, Linux, Windows), Android, iOS
Description
Session (new name of the Loki Messenger) is an anonymous text messenger initially forked from the Signal messenger but completely reworked 3-hops onion routing protocol on top of asymmetrically encrypted messages to anonymize all interactions. E2EE is always enabled and only lokinet users can be contacted through the app. Supports 1-on-1, private groups and public rooms text chats. No phone number nor any private information is required to register. App is cross-platform, available on Windows, Linux, Android, iOS. All open-source, including clients.
In the future, Session will migrate to the Lokinet network (ex LOKI blockchain), a blockchain initially forked from Monero which works over a LLARP (Low Latency Anonymous Routing Protocol) onion routing layer using faster UDP packets, that will allow voice calls. Indeed, Session currently only supports text messages for now due to using a TCP onion routing, but  voice calls and maybe video are planned for later after migration to Lokinet (but no exact date planned)). It seems the blockchain is already online since years, but it's still in beta due to the LLARP protocol being tested out, whereas the blockchain technology used is relatively well established, the LLARP protocol is new and needs to be ironed out.
Why I am making the suggestion

Seems like a concurrent to BCM #1662, but it is entirely opensource (here for the messenger). The LLARP onion routing protocol is explained here and compared succinctly to TOR and I2P here (TL;DR: the goal is to retain the strong anonymity and security guarantees of both networks but with faster speed and easier network management - I can't describe more precisely as I am no expert). The messenger (Session) is discussed here. Blokt and SecureChatGuide reviewed it last year under beta (it still is but seems to be soon reaching the first stable release).
I think the messenger is the most directly useful part of the project right now, and hence the focus of this ticket, but the LOKI/LLARP network could also be added as an entry in Self-contained Networks (as suggested before #924) if someone with more expertise than me can understand the provided docs.
/EDIT: a technical preprint is available since 11/02/2020: https://arxiv.org/abs/2002.04609
/EDIT: Session's code was independently audited in April 2021: https://getsession.org/session-code-audit/
My connection with the software

No link, I am just interested in privacy protecting networks.

[x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.

Mmmm Maybe this ticket should be put on hold until the final release comes out, here is the introductory message when installing the software:

Thanks for testing Loki Messenger! This software is a beta version of the full Loki Messenger software suite, and so is missing some of the features the full version will have.
This version of Loki Messenger provides no guarantees of metadata privacy.
While your messages are secured using end to end encryption, in this beta version of Loki messenger, third parties (like your ISP or the Service Node network) can see who you’re talking to and when you’re sending or receiving messages.
It is also possible that third parties could correlate your public key to your IP address and your real identity if they learn your public key.
However, no one except you and your intended recipients will be able to see the contents of your messages. We recommend using existing methods, like Tor or I2P to mask your IP address while using Loki Messenger beta version.
As a beta, this software is still experimental. When things aren't working for you, or you feel confused by the app, please let us know by filing an issue on Github or making suggestions on Discord.

At least, it looks like they take security very seriously. Up to you guys to see whether you want to add the entry with a warning, or wait for the final release to fix these issues.

Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will be launching Session in a few days on Desktop, iOS and Android, so probably best to hold off until then for research/review.

@KeeJef that's great news to hear! Can't wait to test the stable release with all the anonymity features implemented :-)

My God, what an amazing application.
Thank you

New website: https://getsession.org/

Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will be launching Session in a few days on Desktop, iOS and Android, so probably best to hold off until then for research/review.

When exactly are you launching? Great project!

The app is already available, I have used it before posting this issue, but
some important features were missing such as group chat, but on the new
website it's written this is now possible, so i guess that's what was
meant, the deployment of the new release with these important group
features and security updates?
Le lun. 10 févr. 2020 à 16:10, 5a384507-18ce-417c-bb55-d4dfcc8883fe <
<EMAIL_ADDRESS>a écrit :

Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will
be launching Session in a few days on Desktop, iOS and Android, so probably
best to hold off until then for research/review.
When exactly are you launching? Great project!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/privacytoolsIO/privacytools.io/issues/1678?email_source=notifications&email_token=AAIRFXTMMKI6EJ6MOAU6ZSTRCFU77A5CNFSM4KOP2STKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELI3M7Y#issuecomment-584169087,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIRFXQYIG4FVLNCNXFIIMDRCFU77ANCNFSM4KOP2STA
.

The app is already available, I have used it before posting this issue, but some important features were missing such as group chat, but on the new website it's written this is now possible, so i guess that's what was meant, the deployment of the new release with these important group features and security updates? Le lun. 10 févr. 2020 à 16:10, 5a384507-18ce-417c-bb55-d4dfcc8883fe <<EMAIL_ADDRESS>a écrit :
…
Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will be launching Session in a few days on Desktop, iOS and Android, so probably best to hold off until then for research/review. When exactly are you launching? Great project! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1678?email_source=notifications&email_token=AAIRFXTMMKI6EJ6MOAU6ZSTRCFU77A5CNFSM4KOP2STKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELI3M7Y#issuecomment-584169087>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIRFXQYIG4FVLNCNXFIIMDRCFU77ANCNFSM4KOP2STA .

Yes, I meant the new features and security updates. I gave it a look on the desktop client but couldn't find a way of installing it on mobile without using Google  Play store, do  you know if the .apk is available somewhere?

Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will be launching Session in a few days on Desktop, iOS and Android, so probably best to hold off until then for research/review.

When exactly are you launching? Great project!

As mentioned above Session is now launched on all platforms at https://getsession.org , today we also published a whitepaper https://getsession.org/whitepaper which goes through the design in detail. We are still working through a number of issues discovered when we launched with Multi-device setups so that might not be working as expected if you encounter and edge case.

The app is already available, I have used it before posting this issue, but some important features were missing such as group chat, but on the new website it's written this is now possible, so i guess that's what was meant, the deployment of the new release with these important group features and security updates? Le lun. 10 févr. 2020 à 16:10, 5a384507-18ce-417c-bb55-d4dfcc8883fe <<EMAIL_ADDRESS>a écrit :
…
Hey, I'm the CTO on the Loki/Session project, just to confirm, yes we will be launching Session in a few days on Desktop, iOS and Android, so probably best to hold off until then for research/review. When exactly are you launching? Great project! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1678?email_source=notifications&email_token=AAIRFXTMMKI6EJ6MOAU6ZSTRCFU77A5CNFSM4KOP2STKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELI3M7Y#issuecomment-584169087>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIRFXQYIG4FVLNCNXFIIMDRCFU77ANCNFSM4KOP2STA .

Yes, I meant the new features and security updates. I gave it a look on the desktop client but couldn't find a way of installing it on mobile without using Google Play store, do you know if the .apk is available somewhere?

APKs are here, https://github.com/loki-project/session-android/releases , We will be trying to get into F-Droid repo shortly, we're just focusing on bugfixes for now since we just released.

@KeeJef Thanks a lot for the updates, I have updated this issue accordingly. Good luck with the post-release bugfixing, you've got an awesome project here!

Congrats, I  hope you get a stable release ASAP and your project is great!

Does this depend on the Google Services Framework? Aurora store shows a GSF dependency.

As they say during the beta, it has a traffic analyzer, then they will remove it in the stable version.

@wuniversales all analytics have already been removed from all platforms, that was done a few weeks ago when Session was released
Regarding Aurora store flagging Session as GSF dependent, not sure why that is happening, we have APK's that you can download directly here and those work fine without Google play, i will have a look into it on Monday though.

1.0.2 released and I'm impressed! I would like to see this being added.

1.0.2 released and I'm impressed! I would like to see this being added.

Yeah, it works pretty sweet and it doesn't have shitty Google dependencies like Signal.

1.0.2 released and I'm impressed! I would like to see this being added.

Yeah, it works pretty sweet and it doesn't have shitty Google dependencies like Signal.

Signal hasn't had the need to run on google for notifications for years now, and even with the google version, google only sees that you have a notification, not what the notification is about.
About Session now, what is the intended threatmodel? And also, what does it intend to solve over signal ( as of now, it seems to be a Signal fork with some blockchain stuff bolted on).

The threat model is defined in the whitepaper here https://arxiv.org/pdf/2002.04609.pdf
Since Session deploys proxy routing (1 hop, soon to be Onion routing 3 hops) inside it can deal with network level adversaries, as opposed to Signal in which the server can collect the sender and recipient IP addresses. Additionally it removes the need for phone numbers or email addresses as identifiers and instead uses public keys, which enhance anonymity as they are not linked to any real work identifier. Session also doesn't rely on central servers, messages are not stored on servers run solely by the developers or Loki foundation and instead are stored on Service Nodes run by community members, this makes the network resilient to being shutdown or compelled to run privacy compromising software distributions. There is more information contained in the whitepaper about how this is achieved and the properties it provides.

The threat model is defined in the whitepaper here https://arxiv.org/pdf/2002.04609.pdf
Since Session deploys proxy routing (1 hop, soon to be Onion routing 3 hops) inside it can deal with network level adversaries, as opposed to Signal in which the server can collect the sender and recipient IP addresses. Additionally it removes the need for phone numbers or email addresses as identifiers and instead uses public keys, which enhance anonymity as they are not linked to any real work identifier. Session also doesn't rely on central servers, messages are not stored on servers run solely by the developers or Loki foundation and instead are stored on Service Nodes run by community members, this makes the network resilient to being shutdown or compelled to run privacy compromising software distributions. There is more information contained in the whitepaper about how this is achieved and the properties it provides.

So it aims to solve signals ability to correlate conversation members via your own onion routing network ( as currently, signal can still correlate via IP, but not via  account's because of their sealed sender feature) and you deal with the phone number issue  with a blockchain?

So it aims to solve signals ability to correlate conversation members via your own onion routing network ( as currently, signal can still correlate via IP, but not via account's because of their sealed sender feature) and you deal with the phone number issue with a blockchain?

Yes it aims to resolve the IP address correlation, by using an Onion routing network. But no, it doesn't use a blockchain to solve the phone number issue, the public keys don't have any relationship to the blockchain, they are just public keys. The blockchain is used to incentivze the nodes in the network who store user messages and allow for asynchronous communications. You dont need to pay to send messages or use the messenger or anything, its abstracted away from the user.

Interesting. What happens if the user loses his private key? Also, are there any easy backup methods in place so the user can prevent losing said private key?

Interesting. What happens if the user loses his private key? Also, are there any easy backup methods in place so the user can prevent losing said private key?

The user is given access to and encouraged to write down their 12 word mnemonic seed when they create an account or at any time in the settings menu, with this phrase they can restore their private key (identity) and re-initiate previous sessions. In the future we will allow the user to password encrypt their seed and store it other locations, but that's not yet implemented

Sounds very promising. Im not sure if the software is mature enough to be a major recommendation just yet, and we also would have to see how the loki network will develop itself further (is it going to die down like most startup anonymity networks, or will it maybe thrive.) About that, if the worsed case scenario happens and loki doesn't make it, will it be possible to alter session to move to another platform like Tor?

About that, if the worsed case scenario happens and loki doesn't make it, will it be possible to alter session to move to another platform like Tor?

I don't anticipate that happening since the network is already about 1030 nodes strong. But technically, yes, it would require ripping the custom onion routing logic we have in our code out, but i see no reason it couldn't be done.

1.0.2 released and I'm impressed! I would like to see this being added.

Yeah, it works pretty sweet and it doesn't have shitty Google dependencies like Signal.

Signal hasn't had the need to run on google for notifications for years now, and even with the google version, google only sees that you have a notification, not what the notification is about.

Yes it need Google notifications, I downloaded the .apk from Signal recently and they won't let you install the software if you don't have Google store installed, and also if you don't have Google services install you need to enter to the application to receive messages, if not it goes kinda buggy and won't notify you, this issue doesn't happen with Session.

Sounds very promising. Im not sure if the software is mature enough to be a major recommendation just yet, and we also would have to see how the loki network will develop itself further (is it going to die down like most startup anonymity networks, or will it maybe thrive.) About that, if the worsed case scenario happens and loki doesn't make it, will it be possible to alter session to move to another platform like Tor?

I've been using it for almost two weeks now and I can say it works really really good, in comparison to Briar or Jami, which are also listed, if that's considered mature.

Super interesting discussion, thanks a lot guys! I also found their blog posts very interesting about their vision of private messaging, particularly the first one:

https://loki.network/2019/03/29/mls-and-federated-messaging/
https://getsession.org/onion-requests-session-new-message-routing-solution/
https://getsession.org/how-session-protects-your-anonymity-with-blockchain-and-crypto/
https://getsession.org/centralisation-vs-decentralisation-in-private-messaging/

@5a384507-18ce-417c-bb55-d4dfcc8883fe i have been using signal for more then 2 years without any google services on my device and recieve notifications perfectly fine.

As this was brought up in #general:privacytools.io, I checked it quickly and commented this:

I don't like it being Electron and I don't really understand their answer "Is Session peer-to-peer?" - what are service nodes, are they centralized only in their control or can anyone host them and are they federated? Otherwise it looks promising other than being Electron and I am not capable of auditing it

Emphasis I added for GitHub.

As this was brought up in #general:privacytools.io, I checked it quickly and commented this:

I don't like it being Electron and I don't really understand their answer "Is Session peer-to-peer?" - what are service nodes, are they centralized only in their control or can anyone host them and are they federated? Otherwise it looks promising other than being Electron and I am not capable of auditing it

Emphasis I added for GitHub.

The desktop version is Electron based primarily since we have forked the existing Signal applications. For us to develop and maintain native clients for all OS'es would be extremely resource intensive. Although we do recognize that Electron is not the most highly secure framework available.
Regarding the Service Node network. They are federated, and anyone with the required Loki stake can start running one and earn a reward for storing and routing user messages. The Loki foundation is not in control of the Service Node network, there are hundreds of individual node operators with altogether about 1050 Service Nodes in operation.
The reason Session isnt peer to peer is that you always connect to the Service Node network to send and store messages to other users, you never connect directly to another user as that would expose your IP address and limit the ability for messages to be sent asynchronously.

This would be great I’m deciding on switching to session as it doesn’t need a phone or email to sign up

This would be great I’m deciding on switching to session as it doesn’t need a phone or email to sign up

No reason to wait for it to be mentioned on PrivacyTools, why not switch now and tell us how it you found it.

This would be great I’m deciding on switching to session as it doesn’t need a phone or email to sign up

No reason to wait for it to be mentioned on PrivacyTools, why not switch now and tell us how it you found it.

Found it from reddit on the privacy section but I am gonna switch but if it was on privacy tools it would give me some reinsurance that it’s safe and secure. I know it’s a based on the electron blockchain which I heard wasn’t the best. But it does use signals protocol

I know it’s a based on the electron blockchain which I heard wasn’t the best.

It is not based on the Electron blockchain (AFIK that doesn't exist), the Desktop application is using the Electron Javascript framework, as is Signal. As @dngray said you can go ahead and have a go using Session, its still early days so the user experience isn't quite as easy as Signal and you might run into bugs.

Oh thanks for the correction that’s why you should believe some reddit user 😂

I think session will be a great addition to the site on day, but we are currently mostly waiting for it to become more mature as software and as a service (by seeing how the loki network will expand and grow.)

I have admired the effort of the loki team (don't know them). To try and make some kind of midway best of two tor and i2p together anonymity network, first of all.
Honestly I think it might be able to be posted as a rec, for people whom need only send messages to one another.
However when, if they implement actual voice calling tech in there I think this truly will spark a lot of peoples interest.

I have admired the effort of the loki team (don't know them). To try and make some kind of midway best of two tor and i2p together anonymity network, first of all.
Honestly I think it might be able to be posted as a rec, for people whom need only send messages to one another.
However when, if they implement actual voice calling tech in there I think this truly will spark a lot of peoples interest.

I don't think Session should be omitted from the Privacytools.io site, just because it doesn't have voice calls, there are a few things that we want to do before recommending that Session is listed on the site

The app is added to F-Droid
The cross platform refactor is finished (This is about 2-4 weeks away) this will vastly improve message sending reliability, especially when dealing with multi device functionality
Full three hop onion routing is enabled in Session, instead of one hop proxy routing.
Closed group size is expanded

These features are all actively being worked on right as we speak and i think when these features are in and testers from this group can see that they work reliably, then there would be no reason not to list Session in the messenger section.

Full three hop onion routing is enabled in Session, instead of one hop proxy routing.

I was going to mention the simplified routing scheme, but if the 3 hop onion routing is implemented soon, then that would be awesome!
I agree that even without voice calls, with the upcoming updates Session would be at least Worth Mentioning IMHO, until its stability is sufficiently field tested to potentially be a recommendation similarly to Briar (although I'm not sure whether it should be classified as P2P or Federated - Status.im which is based on Ethereum nodes is under Federated so maybe we should go along the same way for Session?)

BTW thanks a lot @KeeJef for taking the time to update us, that's really appreciated (and great work on Session!).
Ah I also just noticed you published a preprint, congratulations and great work! I'll add this to the top message for reference :-)

I don't think Session should be omitted from the Privacytools.io site, just because it doesn't have voice calls, there are a few things that we want to do before recommending that Session is listed on the site

Oh that wasn't what I was trying to imply. I'm just really thrilled if when it would get to that point.
For me it if at that point, if then working this would be my dream messenger come true so..

For me it if at that point, if then working this would be my dream messenger come true so..
@GintokiHub I agree with you and would very much like to see VoIP (and let's dream voice calling ;-) ) through the lokinet. Maybe someday! :D Right now the future of private messaging seems bright with the emerging implementations of E2EE in WebRTC using Secure Frames, and with the lokinet it would also be anonymous to some extent.

@KeeJef please let us know when the points you mentioned are ready for large use, I can test and make a PR :-)

Session has trackers from Google Firebase, doesn't seem like something PTIO should recommend.

@ph00lt0 I guess this issue explains why Firebase is used?
I remember reading a blog post about the difficulties with pushing updates to Android devices without using a connection to a centralized server that could diminish anonymity, maybe it was on the Session blog but I can't remember or find with Google where.

PS: it seems that using Firebase is optional, although enabled by default if I understand correctly the issue linked above?

PS: it seems that using Firebase is optional, although enabled by default if I understand correctly the issue linked above?

It's possible to use Firebase Cloud Messaging as a push service, but users can opt not to use it, and the setting screen is explicit enough (pop out after first run of app update) to consider it no harmful intention.

@subsys-R9boq8 this is exactly my point. It's not about the push notifications. Although I would say it should use alternative methods either way. The use of trackers like Firebase Analytics is just wrong.

@ph00lt0 Yes, and it also sounds strange, Firebase Analytics seems quite broke in Session-Android.

We have never actually used Firebase analytics in a production version of the application, these static code analyzers seemed to be picking up the inclusion of the Google Firebase library (Used for FCM) as and flagging that, but as of last week we have excluded those parts that were getting flagged by Exodus and now we are passing https://reports.exodus-privacy.eu.org/en/reports/network.loki.messenger/latest/.
You can see the PR here https://github.com/loki-project/session-android/pull/219
Regarding FCM for push it is only ever used if the user opts in to use it,and there is a big onboarding screen explaining the consequences/benefits, you can use Session Google free if you just use background notifications.

We have never actually used Firebase analytics in a production version of the application, these static code analyzers seemed to be picking up the inclusion of the Google Firebase library (Used for FCM) as and flagging that, but as of last week we have excluded those parts that were getting flagged by Exodus and now we are passing https://reports.exodus-privacy.eu.org/en/reports/network.loki.messenger/latest/.
You can see the PR here loki-project/session-android#219
Regarding FCM for push it is only ever used if the user opts in to use it,and there is a big onboarding screen explaining the consequences/benefits, you can use Session Google free if you just use background notifications.

Just checked the latest release and it's free of Firebase Analytics, thanks for the explanation!

thanks for clarifying @KeeJef

Seems ok, the only thing I don't trust is that it's based in Australia.

A political view research regarding the loki network, that i believe it's important to be mentioned and taken into account:
https://nitter.net/WPalant/status/1281540005190672384

I did look at the ABC article. It looks to be a similar situation to where the Tor Project find itself. Bad people can use good technology?
As we really don't know what was said, we can never determine to what extent "they helped". The word "inadvertent", might reflect they did not know who they were before helping them.

This German-language video shows Loki Network's main developer (Jeff/majestrate) pitch his baby on 8chan and being celebrated by the alt-right for it (at 27:46). For reference, Loki Network is the foundation of Session and developed by the same startup.

I did watch that video, and the only reference was this frame:

How do we actually know it was written by @majestrate and not copy pasted from somewhere else?

I am not convinced by the point raised either. First because I don't see any proof, only claims in the linked twitter thread, but also because that's basically the timeless security vs liberty philosophical and political problem. For example, medicine has always been used to conduct unethical experiments including torture or worse. This unfortunately shows that even the most honorable tools can be misused. Should we blame the tool, or the user who misuse?
IMO, the technical side also matters in this question. I think that as long as the tool is not operated by the developer and is opensource, who the developer is is ultimately irrelevant.

Guys, some of you have gone OT for very far, any issues that relate more to LokiNet than Session should be discussed at #1940 (Lokinet) but not #1678 (here).

just to die up a loose end (further mud flinging can go into #1940 )

How do we actually know it was written by @majestrate and not copy pasted from somewhere else?

the aforementioned post was on a former contributor's imageboard, and since imageboards love to steal each other's style sheets it makes sense that it was confused with 8chan. original post from the screenshot is from https://endchan.net/tech/res/12870.html

@majestrate thanks for clarifying that. I got this feeling from that CCC speaker that it felt like he just wanted to show a bunch of alt-right propaganda/meme/shock material to viewers, I think it could have done with a lot less of that and still gotten his point across.
We should get this back on-topic.

I might have missing some function, but I didn't see anything like Signal's "safety number". Why is that? Can session or the lower LokiNet platform prove that I am talking to the person with no insider interference (Like MITM), or is the platform naturally immune to this kind of attack?

@subsys-R9boq8 We do have the ability to view a users safety number on desktop, it should be on all platforms, not sure why it got removed. However the security model is quite different than Signal, since Signal users can change their underlying key pairs without breaking a session (Phone number is ultimate truth) whereas your identity (SessionID) in Session is actually your public key meaning you cant change it.
This means that if you talk to someone with X session ID, you know you are speaking to them and there is no TOFU or MITM attack possible (as long as the out of band Session ID sharing is done properly). However it still makes sense to have safety numbers because someone out of band might claim to be X person when they are Y person, if you speak to X person in real life or through some secure means then you can either compare Session ID's or safety numbers, however safety numbers are a little easier to compare (Have a QR code and nice formatted representation)

Why are you using legacy GPG version 1.4? https://github.com/loki-project/session-android/releases

@ZarusMods No particular reason, is there a compelling reason to update? CVE or something?

i use it
is great and is even better now that have added multi device sync

Ok thank you for your clarifications. I think it's time to make a PR, we'll
see what the peer reviews says.
To mabe my job easier, could you please clarify the following:
About forcing a new route, i meant to do something like Tor Browser is
doing, such as simply relaunching the whole client to force generate a new
random route. I understand the security issuks otherwise. The issue you
linked to already asked for this feature for performance reason (ie,
unreliable network) instead of security but implementing it will fit both.
About the nodes, i can see thad they are well distributed over the world,
nice charts. Can you precise who are currently running these nodes? Users
of the Oxen blockchain who are incentivized by the proof of stake algo or
are most nodes yours at the moment?
Finally, could you please clarify how the whole ecosystem is connected and
what each piece is doing in the big picture? Before i think lokinet was
supposed to be the blockchain and llarp combined, but now it seems that
Oxen is the blockchain which provides TCP onion routing and encryption ,
Lokinet which will be the llarp fast udp onion network that will work in
tandem with Oxen. Session uses Oxen only for now and in the future will use
both Oxen and Lokined, switching transparently when fast data transfer is
needed. Is that an accurate overview?
Le mar. 11 mai 2021 à 05:49, Kee Jefferys @.***> a
écrit :

@KeeJef https://github.com/KeeJef I have one suggestion about the
registration process on desktop, it doesn't require the user to copy/save
the private key as it does on mobile, so non technical users may
unknowingly lose their account if they create one on desktop and aren't
aware of how blockchains work.
Hmm this might be something we look into, if you wanted to file an issue
for that we could look at it in an upcoming release
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/privacytools/privacytools.io/issues/1678#issuecomment-837745751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIRFXUONJAQBF4IWYSVPPLTNCSLDANCNFSM4KOP2STA
.

About the nodes, i can see thad they are well distributed over the world,
nice charts. Can you precise who are currently running these nodes? Users
of the Oxen blockchain who are incentivized by the proof of stake algo or
are most nodes yours at the moment?

The vast majority of nodes in the network are run by community members, the largest single operator of Service Nodes in the network is the OPTF who runs about ~9% of the networks Service Nodes. Anyone can start a Service Node and begin earning rewards if they have the required stake to do so.

lokinet was supposed to be the blockchain and llarp combined, but now it seems that
Oxen is the blockchain which provides TCP onion routing and encryption ,
Lokinet which will be the llarp fast udp onion network that will work in
tandem with Oxen. Session uses Oxen only for now and in the future will use
both Oxen and Lokined, switching transparently when fast data transfer is
needed. Is that an accurate overview?

Session currently uses a system called onion requests for onion routing, which is TCP based, this system still uses the ~1750 Service Nodes to onion route all messages, but it doesn't use Lokinet. Onion requests are single shot, which means you send a request and get a response, they don't allow a user to hold a onion routed connection open with a Service Node or other Session client.
Lokinet is a different onion router which can route any IP based protocol, it also uses the Service Node network to create routes through the network, however because Lokinet can route any IP based protocol it is much more versatile, and it can keep connections open with the Service Node network to be able to stream data. Lokinet is slated for future implementation, since it will help us provide voice calling and other functionality.

Thank you @KeeJef for the additional clarifications.
I have opened a PR at #2293, it's going to take some time for review, hopefully the editorial board will greenlight it.

@KeeJef FYI as Oxen/Lokinet fits the criteria to be a future target of such attack vector: https://www.techradar.com/news/cryptocurrency-users-targeted-by-tor-network-exit-nodes

@KeeJef FYI as Oxen/Lokinet fits the criteria (crypto + onion routing) to be a future target of such attack vector: https://www.techradar.com/news/cryptocurrency-users-targeted-by-tor-network-exit-nodes

This is only really relevant for Lokinet, Session traffic doesn't exit the network in any way where it could be hijacked, Lokinet does have exits but doesn't have a publicly incentivised infrastructure yet, but yes we are aware of these issues in Tor.

@KeeJef FYI as Oxen/Lokinet fits the criteria (crypto + onion routing) to be a future target of such attack vector: https://www.techradar.com/news/cryptocurrency-users-targeted-by-tor-network-exit-nodes

i agree it could be a problem but it is probably far less of an issue as lokinet exits are not picking from a giant pool of randos, you manually choose your exit so if some bad actor is running an exit no one will use it (free market regulating itself etc), additionally as @KeeJef pointed out, session wont be using exits anyways so it is probably not an attack that is in scope for it.

Lokinet/Session aren't suitable for PTIO:

Lokinet/Session is based in Australia, which makes it a non-starter for PrivacyTools.io thanks to it's 2018 Access and Assistance Bill (AKA gov can force them to introduce vulnerabilities into their encryption tech and not disclose this) as well as the likely forthcoming Identify and Disrupt bill which allows hijacking darknet providers accounts (like Lokinet) if authorities believe serious crimes are taking place on it (i.e. every darknet provider in Australia is at risk).

https://github.com/privacytools/privacytools.io/issues/1940#issuecomment-853722071


Different behaviours between undefined property and optional

TypeScript Version:  nightly (2.0.0-dev.20160706)
Code
type A = { a: number | undefined };
const b: A = { a: undefined };
const c: A = {}; // error, property a is missing in type {}

Expected behavior:
no error
Actual behavior:
error
Seems bug, or by design?
update: same when not in strict null check mode.

This is by design. A property can be omitted only if it was declared with a ? modifier. So, { a?: number } says that a is optional and may be omitted (and undefined is automatically included in the type if it isn't explicitly specified), whereas { a: number | undefined } says that a must be specified and undefined is one of the permitted values.


fix(speedkit-image): added parent fetchKey prefix

SpeedkitImage

fetchKey from SpeedkitImage extended with $parent._fetchKey.

Why need to rely on parent's fetchKey? It still cann't solve the problem when parent's don't set the fetchKey. The component should handle this by itself. That's better.


dubbo 31.7版本中如何设置ReferenceBean的url、interface、group、payload

我项目原来使用的是2.7.19版本，因为要修复序列化的安全问题现在要升级到3.1.7版本；项目中使用了ReferenceBean设置url、interface、group，现在3.1.7中没有这些api直接设置了，无法直接上这个版本，来此求助，希望大神帮忙

这是之前的代码：
T service = (T)dubboServiceCache.computeIfAbsent(cacheKey, k -> {
log.debug("dubbo service not exist, ready to get one.");
ReferenceBean referenceBean = new ReferenceBean<>();
referenceBean.setApplicationContext(applicationContext);
referenceBean.setInterface(serviceClass);
if (timeout != null)
{
referenceBean.setTimeout(timeout);
}
        if (StringUtils.isNotBlank(group))
        {
            referenceBean.setGroup(group);
        }
        if (StringUtils.isNotBlank(ip) && port > 0)
        {
            referenceBean.setUrl("dubbo://" + ip + ":" + port);
        }

        ProtocolConfig protocolConfig = getBean(ProtocolConfig.class);
        if (protocolConfig.getPayload() != null)
        {
            Map<String, String> refParams = referenceBean.getParameters();
            if (null == refParams)
            {
                refParams = new HashMap<>();
            }

            refParams.put(Constants.PAYLOAD_KEY, protocolConfig.getPayload().toString());
            log.debug("magic set reference config parameters: {}", refParams);
            referenceBean.setParameters(refParams);
        }

You can create a ReferenceBean by chaining through ReferenceBeanBuilder, which can meet your needs of taking me with you.

You can create a ReferenceBean by chaining through ReferenceBeanBuilder, which can meet your needs of taking me with you.

Thank you very much for providing me with the solution by ReferenceBeanBuilder，I first created a ReferenceBeanBuilder object, and then set the url, timeout, and group properties,Finally, execute beanBuilder. build (); Is this way OK？
I have a few small questions，How to set payload and obtain a dubboService object in version 3.1.7，
This is the previous code：

Yes.You can configure the payload through ReferenceBeanBuidler#setParameters.The obtain a dubboService object operation is ReferenceBean#getObject.You can look at the source code, which may enhance your use of this area


Add LMove command for db & server

LMove command in redis.

@roseduan Please have a look at this PR.

OK, thanks for you review.


"Shader Packs..." button doesn't work on 1.21.4

Using the current latest version of Sodium, Iris & Reese's Sodium Options causes the "Shader Packs..." button in the video settings menu to not work. Nothing happens when clicking it.
Sodium version: mc1.21.4-0.6.2-fabric
Iris version: 1.8.3+1.21.4-fabric
Reese's Sodium Options version: mc1.21.4-1.8.1+fabric
No other mods installed

You can try to click on the top of "k" in "Shader Packs...".It works for me.

seems that this issue happens to me. robotkoer told me to edit or delete sodium config file and retry, so you can try that, Excederus

To be clear, the button only stops working when you hide the Sodium donate button. If it's visible (as it is on default Sodium config file), then it works.

To be clear, the button only stops working when you hide the Sodium donate button. If it's visible (as it is on default Sodium config file), then it works.

How do I make the donation button visible without deleting the sodium configuration files?

How do I make the donation button visible without deleting the sodium configuration files?

I solved it: Go to the instance folder > config > sodium-options.json
Set "has_cleared_donation_button" to false
"notifications": {
    "has_cleared_donation_button": false
}

Thank you @Kotiya-Sanae and @GIMMI42PIASTRATO, you're lifesavers!
Meanwhile, I can confirm that that this issue is still relevant.


Sorting of Winrate is not working properly

Describe the bug
Sorting of Winrate is not working properly
To Reproduce
https://lh3.googleusercontent.com/-SBLnVxYhM9A/XB0czGG9xkI/AAAAAAAAVbc/84y1LWPHvBgcvfwhF8HgM-Bj0NTJMoyEwCHMYCw/s0/2018-12-21_18-03-05.png
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
https://lh3.googleusercontent.com/-SBLnVxYhM9A/XB0czGG9xkI/AAAAAAAAVbc/84y1LWPHvBgcvfwhF8HgM-Bj0NTJMoyEwCHMYCw/s0/2018-12-21_18-03-05.png
Additional context
Add any other context about the problem here.

Fixed.


Updated sample_config with new InfluxConfig struct

InfluxConfig struct now requires 'database' not 'db'
Host & Port definition no longer allowed either - should be url

Thanks, sorry for the slop on that.

Thanks @paulstuart - I can see you're busy with changes. I've been updating my Grafana + InfluxDB + Influxsnmp setup. Looks like a few other changes needed in the sample config - it took me a little while to get the right config with mibs, regexp, etc. working. But wasn't too worried about pushing changes for those yet, since it looks like you're actively making changes.

Yes, I've been busy tweaking the code. It had been effectively dormant for
some time and now I'm putting it into play in multiple locations with a
significant number of devices to monitor. Changes today to allow for
multiple hosts per snmp config entry, for example (useful when you have
dozens of devices that differ only in their address).
It's definitely shaped by my needs but I want this to be useful for others
as well. Anything that isn't clear or if there's functionality you'd like
to see please create an issue on the repo and I'll do my best to resolve it
promptly.
On Tue, May 24, 2016 at 2:34 PM, Lindsay Hill<EMAIL_ADDRESS>wrote:

Thanks @paulstuart https://github.com/paulstuart - I can see you're
busy with changes. I've been updating my Grafana + InfluxDB + Influxsnmp
setup. Looks like a few other changes needed in the sample config - it took
me a little while to get the right config with mibs, regexp, etc. working.
But wasn't too worried about pushing changes for those yet, since it looks
like you're actively making changes.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/paulstuart/influxsnmp/pull/20#issuecomment-221403891


Samplers tutorial

This PR adds a notebook-like example for the sampling APIs.

Great tutorial! There's at least a rendering issue with our docs job, but nothing blocking.


LaTeX to Emmy converter

You probably thought of this already and this repo might not be the right place to talk about it, but if Emmy translates to LaTeX then it could do the opposite, which would be insane. I could open any academic paper and turn their proofs and formulas into executable code...

I love this idea! I've done a bit of the work here already, and I'd love to hear how this experience looks /feels to you:
https://mathlive.mentat.org/
This is an equation editor like you're suggesting, with the ability to generate "MathJSON" out of the editable LaTeX: https://mathlive.mentat.org/#mathjson
The idea is that I can turn that MathJSON blob into an emmy function, so you could take that example of yours and define f using the equation editor.
Let me know what else you're thinking here for this experience and let's make it happen.

looks like a katex bug there at the end, rendering `\coloneq` as `:-`...

Thank you for sharing! I think what you have is very useful for people who are already comfortable in LaTeX or with constructing equations in general. For a math noob like myself, I would be worried about making a mistake when trying to recreate something I saw in a paper.
I would be more confident in the MathJSON/Emmy output if I could copy-paste in LaTeX from somewhere else since I know there's no chance of human error. I have no idea how feasible that is!
Example: I'm reading a paper or Wikipedia article (example) and I come across a formula that I'd like to use in my own codebase:

I copy-paste the resulting string into a function that converts to Emmy:
(latex->emmy "\operatorname {Var} (X)=\sum _{i=1}^{n}p_{i}\cdot (x_{i}-\mu )^{2}")

Here's an example of GPT doing such conversion into Python. I chose Python since GPT is more likely to make mistakes in Clojure.

I like the idea of converting to Emmy for many reasons, one of which is that I can render it back into LaTeX which would be helpful to ensure that no mistakes were made in translation. When using GPT, I kind of have to hope that it worked unless I was already an expert in the formula / code.
Anyway, just an idea I had this morning. Glad you found it interesting!


Modify ClientPrefs to be much more user-accessible

I did a bunch of rewriting to ClientPrefs, added a new function called "getPref" to get a certain ClientPref (with a default value like how getGameplaySetting does it), and hopefully made it a little more lua-friendly.
It should also be completely compatible with old ClientPrefs; I only took all of the settings and put them in a map, plus separated load functions.
This is also my first PR, so be nice on me please :)

feels like an interesting thing to have, clientprefs rn is pretty messy in my opinion, glad someone did this already
looking forward for this one!

feels like an interesting thing to have, clientprefs rn is pretty messy in my opinion, glad someone did this already
looking forward for this one!

thanks haha, i actually was expecting to not be the first, but as it turns out i am, which is surprising--i actually have used a method that's similar for one of my previous projects

Would approve but what would happen to the luas that uses getPropertyFromClass("ClientPrefs") ?

that's a good question, i suppose it'd be obselete since it's now softcoded instead of you being able to just get the pref directly from the class, though in turn you can make a new lua function called 'getPref' and just replace all mentions of 'getPropertyFromClass' with 'getPref', though it doesn't really support 'legacy' scripts.
a way to mitigate this, i believe, would be to check if the lua script is trying to get a setting from ClientPrefs inside of the 'getPropertyFromClass' function, then try to get a pref, i.e
Lua_helper.add_callback(lua, "getPropertyFromClass", function(classVar:String, variable:String) {
	@:privateAccess
	var killMe:Array<String> = variable.split('.');
	if(killMe.length > 1) {
		var coverMeInPiss:Dynamic = getVarInArray(Type.resolveClass(classVar), killMe[0]);
		for (i in 1...killMe.length-1) {
			coverMeInPiss = getVarInArray(coverMeInPiss, killMe[i]);
		}
		return getVarInArray(coverMeInPiss, killMe[killMe.length-1]);
	}
	switch (classVar) // Legacy support
	{
		case 'ClientPrefs':
		{
			var pref:Dynamic = ClientPrefs.getPref(variable);
			if (pref != null) return pref;
		}
	}
	return getVarInArray(Type.resolveClass(classVar), variable);
});

this should hopefully fix it, and i think i'll actually implement this right now, sorry for not thinking about this lol

notice: images persist is not an option anymore, as it was "removed" in favor of a better and more efficient paths system

notice: images persist is not an option anymore, as it was "removed" in favor of a better and more efficient paths system

i know, thats why i commented it out

Alright, but it seems like a huge pain in the ass for those who port it over to their mod manually though, just saying.

just wanted to say, i can understand this, but it's actually not that hard from source--all i did in vscode was ctrl + shift + h and just go through every setting and replace with ClientPrefs.getPref('prefname') and that was about it, so it shouldn't be too bad hopefully

I see.

I should prob merge this to some private build, seems easier to use

Would approve if there were no merge conflicts

ty for telling me, i'll fix those rn

Would approve but what would happen to the luas that uses getPropertyFromClass("ClientPrefs") ?

that's a good question, i suppose it'd be obselete since it's now softcoded instead of you being able to just get the pref directly from the class, though in turn you can make a new lua function called 'getPref' and just replace all mentions of 'getPropertyFromClass' with 'getPref', though it doesn't really support 'legacy' scripts.
a way to mitigate this, i believe, would be to check if the lua script is trying to get a setting from ClientPrefs inside of the 'getPropertyFromClass' function, then try to get a pref, i.e
Lua_helper.add_callback(lua, "getPropertyFromClass", function(classVar:String, variable:String) {
	@:privateAccess
	var killMe:Array<String> = variable.split('.');
	if(killMe.length > 1) {
		var coverMeInPiss:Dynamic = getVarInArray(Type.resolveClass(classVar), killMe[0]);
		for (i in 1...killMe.length-1) {
			coverMeInPiss = getVarInArray(coverMeInPiss, killMe[i]);
		}
		return getVarInArray(coverMeInPiss, killMe[killMe.length-1]);
	}
	switch (classVar) // Legacy support
	{
		case 'ClientPrefs':
		{
			var pref:Dynamic = ClientPrefs.getPref(variable);
			if (pref != null) return pref;
		}
	}
	return getVarInArray(Type.resolveClass(classVar), variable);
});

this should hopefully fix it, and i think i'll actually implement this right now, sorry for not thinking about this lol

Does setPropertyFromClass have this check?

Would approve but what would happen to the luas that uses getPropertyFromClass("ClientPrefs") ?

that's a good question, i suppose it'd be obselete since it's now softcoded instead of you being able to just get the pref directly from the class, though in turn you can make a new lua function called 'getPref' and just replace all mentions of 'getPropertyFromClass' with 'getPref', though it doesn't really support 'legacy' scripts.

a way to mitigate this, i believe, would be to check if the lua script is trying to get a setting from ClientPrefs inside of the 'getPropertyFromClass' function, then try to get a pref, i.e

Lua_helper.add_callback(lua, "getPropertyFromClass", function(classVar:String, variable:String) {

@:privateAccess

var killMe:Array<String> = variable.split('.');

if(killMe.length > 1) {

  var coverMeInPiss:Dynamic = getVarInArray(Type.resolveClass(classVar), killMe[0]);

  for (i in 1...killMe.length-1) {

  	coverMeInPiss = getVarInArray(coverMeInPiss, killMe[i]);

  }

  return getVarInArray(coverMeInPiss, killMe[killMe.length-1]);

}

switch (classVar) // Legacy support

{

  case 'ClientPrefs':

  {

  	var pref:Dynamic = ClientPrefs.getPref(variable);

  	if (pref != null) return pref;

  }

}

return getVarInArray(Type.resolveClass(classVar), variable);

});

this should hopefully fix it, and i think i'll actually implement this right now, sorry for not thinking about this lol

Does setPropertyFromClass have this check?

yeah it should

aww man if this gets accepted ill have to remove the coment of psych emgine clientprefs sucking in my engine, good pr tho

idk if this'll get accepted since i like. massively rewrote clientprefs as a whole, @ShadowMario can decide on that, but this is good if you wanna modify psych engine yourself. so you can still keep that comment if you don't plan on adding this pr lol


Changed "Mac OSX" and "OSX" to "macOS"

Sorry, someone had to do it. :)
FYI: Mac OS -> Mac OS X -> OS X -> macOS

haha...thanks


Support Visual Studio 2019

The ffmpeg build currently fails when VS2019 is installed. I am working on getting VS2019 to build correctly...

I don't event have it installed.
I wish they stopped breaking toolchains every new release.

It was more a problem of the project files from the additonal libs (zlib, iconv and bzip2). They have some hand written conditions checking VS versions. Our library built just fine with VS2019 without any change.

I like VS2019, it's again a lot faster and snappier, compared to VS2017...

I got it working now with #129.
After pulling the changes, you need to run git submodule update to update all libs to latest version.

Seems to work all fine now, closing this...


Update Python 3.py

The code displays "Hello World"
I have improvised the code

It's purpose is to tell Python where the interpreter is but we don't know where it is.

Because this file is supposed to be executed, it should include this shebang.


[AutoDiff] Add #chainableGradient differential operator for seedable gradient

#chainableGradient takes a function and returns a function, which takes original parameters and a backpropagated adjoint, and computes vector-Jacobian products.
func f(_ x: Float) -> Float { ... }
let y = f(x)
let dz_dy = ...
let dz_dx = #chainableGradient(f)(x, dz_dy)

#chainableGradient corresponds to the gradient [seedable] instruction in SIL.
Sema and libSyntax are to be done separately. This is a random patch to unblock the progress towards a way to express seedable derivatives in Swift source code.

@swift-ci please test tensorflow

I'm happy to tackle Sema and Syntax for #chainableGradient if you'd like to work on other parts of autodiff. Let me know!

@dan-zheng Thx. Don't worry about it today. Let's try get more deabstraction bugs fixed.

@swift-ci please test tensorflow

@swift-ci please test tensorflow


CON-5001 Added check if no articleId is passed

Coverage decreased (-0.008%) to 41.582% when pulling 0438d1e159623ad207b51b5bd2935c4ccbd5b557 on CON-5001 into babc06d04da5ce77858688914897c32ca20d0578 on master.


Re-add a way to generate a single convex shape from the editor

It was removed after the implementation of VHACD. Generating a single shape can lead to better performance, so it may still be desired.
This also adds tooltips for several options in the Mesh menu.
This closes #35692.

Thanks!

Cherry-picked for 3.2.1.

I just downloaded Godot 3.2.2 for Mac, and there is no “Create Convex Static Body” in the Mesh menu. There is only “Create Trimesh Static Body”.
I’m not sure I understand what happened in this thread (I’m new to Godot), but shouldn’t “Create Convex Static Body” be in the Mesh menu?


[Feature Request] Tie codes to User entities instead of locks

Is your feature request related to a problem? Please describe.
Managing codes is slot-specific, not user-specific.
Describe the solution you'd like
Instead of managing each look individually, or with parent-child relationships, it would be great if the user entities could be extended with their specific configurations and then associated with specific locks.

I'm almost certain this would require some type of expansion of the person integration in Home Assistant core.

Quite possible, but I think the benefit would be great if we could help guide that integration. Anyway, just a thought.