Swift issue (@MiniTabBar)

Hi,
[I closed the issue by mistake]
I am using NativeScript 3.0.0,  tns-ios 3.0.1.
After installing the plugin and tns run ios:
i can see in the terminal that it is downloading from git: Pre-downloading: MiniTabBar from https://github.com/rhanbIT/MiniTabBar.git
, and then i get the above error.
Thanks
Nir
=========OutPut from Terminal==============
tns run ios
Executing before-prepare hook from /Users/nirmiron/DEV/NScriptTests/vForms/hooks/before-prepare/nativescript-dev-typescript.js
Found peer TypeScript 2.2.2
Preparing project...
Successfully prepared plugin nativescript-angular for ios.
Successfully prepared plugin nativescript-intl for ios.
Successfully prepared plugin nativescript-bottombar for ios.
Successfully prepared plugin nativescript-iqkeyboardmanager for ios.
Successfully prepared plugin nativescript-theme-core for ios.
Successfully prepared plugin tns-core-modules for ios.
Successfully prepared plugin tns-core-modules-widgets for ios.
Installing pods...
Analyzing dependencies
Pre-downloading: MiniTabBar from https://github.com/rhanbIT/MiniTabBar.git
Downloading dependencies
Using IQKeyboardManager (4.0.8)
Installing MiniTabBar (1.0.2)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There are 2 dependencies from the Podfile and 2 total pods installed.
Project successfully prepared (ios)
Searching for devices...
Building project...
Build settings from command line:
ARCHS = i386 x86_64
CODE_SIGN_IDENTITY =
CONFIGURATION_BUILD_DIR = /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator
ONLY_ACTIVE_ARCH = NO
SDKROOT = iphonesimulator10.3
SHARED_PRECOMPS_DIR = /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/sharedpch
VALID_ARCHS = i386 x86_64
=== BUILD TARGET MiniTabBar OF PROJECT Pods WITH CONFIGURATION Debug ===
Check dependencies
Write auxiliary files
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-generated-files.hmap
/bin/mkdir -p /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar-OutputFileMap.json
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-all-target-headers.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/module.modulemap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-own-target-headers.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/unextended-module.modulemap
/bin/mkdir -p /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources/MiniTabBar_vers.c
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/swift-overrides.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.LinkFileList
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-all-non-framework-target-headers.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/unextended-module-overlay.yaml
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar.hmap
/bin/mkdir -p /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/i386
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/i386/MiniTabBar-OutputFileMap.json
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-project-headers.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/all-product-headers.yaml
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/i386/MiniTabBar.LinkFileList
Create product structure
/bin/mkdir -p /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/MiniTabBar.framework/Modules
/bin/mkdir -p /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/MiniTabBar.framework/Headers
ProcessInfoPlistFile /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/MiniTabBar.framework/Info.plist Target\ Support\ Files/MiniTabBar/Info.plist
cd /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/nirmiron/.rvm/bin:/Users/nirmiron/Library/Android/sdk/tools:/Users/nirmiron/Library/Android/sdk/platform-tools"
builtin-infoPlistUtility /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Target\ Support\ Files/MiniTabBar/Info.plist -expandbuildsettings -format binary -platform iphonesimulator -o /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/MiniTabBar.framework/Info.plist
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
cd /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
export DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/nirmiron/.rvm/bin:/Users/nirmiron/Library/Android/sdk/tools:/Users/nirmiron/Library/Android/sdk/platform-tools"
export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.3.sdk
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -incremental -module-name MiniTabBar -Onone -D COCOAPODS -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.3.sdk -target x86_64-apple-ios8.0 -g -module-cache-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/ModuleCache -Xfrontend -serialize-debugging-options -enable-testing -I /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -F /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -c -j8 /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift -output-file-map /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar-OutputFileMap.json -parseable-output -serialize-diagnostics -emit-dependencies -emit-module -emit-module-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.swiftmodule -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-generated-files.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-own-target-headers.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-project-headers.hmap -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/include -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Private -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Public -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources/x86_64 -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources -Xcc -DPOD_CONFIGURATION_DEBUG=1 -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -emit-objc-header -emit-objc-header-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar-Swift.h -import-underlying-module -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/unextended-module-overlay.yaml -Xcc -working-directory/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
CompileSwift normal x86_64 /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift
cd /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c -primary-file /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift -target x86_64-apple-ios8.0 -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.3.sdk -I /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -F /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -enable-testing -g -import-underlying-module -module-cache-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -serialize-debugging-options -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-generated-files.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-own-target-headers.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-project-headers.hmap -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/include -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Private -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Public -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources/x86_64 -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources -Xcc -DPOD_CONFIGURATION_DEBUG=1 -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/unextended-module-overlay.yaml -Xcc -working-directory/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods -emit-module-doc-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar~partial.swiftdoc -serialize-diagnostics-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.dia -Onone -module-name MiniTabBar -emit-module-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar~partial.swiftmodule -emit-dependencies-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.d -emit-reference-dependencies-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.swiftdeps -o /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBar.o
/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift:73:60: error: value of optional type 'Int?' not unwrapped; did you mean to use '!' or '?'?
self.backgroundColor = self.itemViews[self.currentSelectedIndex].getItemBarBackgroundColor();
^
!
CompileSwift normal x86_64 /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift
cd /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift -primary-file /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift -target x86_64-apple-ios8.0 -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.3.sdk -I /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -F /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator -enable-testing -g -import-underlying-module -module-cache-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -serialize-debugging-options -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-generated-files.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-own-target-headers.hmap -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/MiniTabBar-project-headers.hmap -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/include -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Private -Xcc -I/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Headers/Public -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources/x86_64 -Xcc -I/Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/DerivedSources -Xcc -DPOD_CONFIGURATION_DEBUG=1 -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -ivfsoverlay -Xcc /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/unextended-module-overlay.yaml -Xcc -working-directory/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods -emit-module-doc-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView~partial.swiftdoc -serialize-diagnostics-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView.dia -Onone -module-name MiniTabBar -emit-module-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView~partial.swiftmodule -emit-dependencies-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView.d -emit-reference-dependencies-path /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView.swiftdeps -o /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/MiniTabBar.build/Objects-normal/x86_64/MiniTabBarItemView.o
/Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift:101:44: error: value of optional type 'UIColor?' not unwrapped; did you mean to use '!' or '?'?
return self.item.barBackgroundColor?
^
(                            )!
=== BUILD TARGET IQKeyboardManager OF PROJECT Pods WITH CONFIGURATION Debug ===
Check dependencies
Write auxiliary files
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/IQKeyboardManager.build/IQKeyboardManager-project-headers.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/IQKeyboardManager.build/IQKeyboardManager.hmap
write-file /Users/nirmiron/Library/Developer/Xcode/DerivedData/vForms-ggpbfgkafkbdzpgxjpyriwlavuih/Build/Intermediates/Pods.build/Debug-iphonesimulator/IQKeyboardManager.build/IQKeyboardManager-all-target-headers.hmap
ProcessInfoPlistFile /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/IQKeyboardManager.framework/Info.plist Target\ Support\ Files/IQKeyboardManager/Info.plist
cd /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/nirmiron/.rvm/bin:/Users/nirmiron/Library/Android/sdk/tools:/Users/nirmiron/Library/Android/sdk/platform-tools"
builtin-infoPlistUtility /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/Target\ Support\ Files/IQKeyboardManager/Info.plist -expandbuildsettings -format binary -platform iphonesimulator -o /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/build/emulator/IQKeyboardManager.framework/Info.plist
** BUILD FAILED **
The following build commands failed:
CompileSwift normal x86_64 /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBar.swift
CompileSwift normal x86_64 /Users/nirmiron/DEV/NScriptTests/vForms/platforms/ios/Pods/MiniTabBar/MiniTabBar/Classes/MiniTabBarItemView.swift
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(3 failures)
Multiple errors were thrown:
Command xcodebuild failed with exit code 65

Facing same problem, i tried to change .swift after that the build is success but another comes while app inittializing

Will check this out tomorrow 👍

I'm having the same problem, I think it's related to the fact that you specify the git url in the pod and not a specific version, so if they break the source and commit, also nativescript-bottombar will be broken...I think it would be better to stick to a specific version (and future patches) in order to make each build predictable...

I confirm that changing the pod to:
pod 'MiniTabBar', '1.0.2'

fixes the issue...

sorry to write again, idk if it's related to the package change but I've just tried running the app (it compiles just fine) and I get this runtime error:
file:///app/tns_modules/nativescript-bottombar/src/ios/bottombar.js:113:54: JS ERROR ReferenceError: Can't find variable: MiniTabBarDelegate

The MiniTabBarDelegate protocol is in the Swift file for version 1.0.2, so I'm not sure why it gives that error...

Hi @demetrio812 ,
Thank you for the feedback, actually i'm pointing the pod to a github on purpose because it's a fork I made to bring new features to the Swift library. So if you point back the pod to the original url it won't work. Will work on this today stay tuned !

Fixed issue in the Swift library, no need to update the package! Juste follow these steps to get the latest code and test it:

rm -rf platforms
tns run ios


KV not populated when using  --local

Hello,
I am working on a personnal project. it works really well in production. congratulation to all Cloudflare team.
nevertheless when doing some debug locally npx wrangler dev --local --persist, I would expect wrnagler to populate a local KV (under .wrangler/state I guess) But it does not happen and as I use KV to store static assets my site does not display (it all ended with a bare 404).
Am I wrong assuming that wrangler will act as a local KV ? Do I miss some arg on the wrangler command ?
My project can be found here : fsgtTT29-cloudflare
As a side note my worker also uses a D1 database that persists well locally in .wrangler/state/d1.
Thanks for your help

Thanks for reporting this! It looks like you're trying to load static assets from the KV namespace DEVASSETS. Workers Sites will always store static assets in the __STATIC_CONTENT KV namespace. The docs page https://developers.cloudflare.com/workers/platform/sites/start-from-worker has a good example of how to load assets from a Workers Sites namespace.
I'm going to close this for now, but if that doesn't solve your issue feel free to comment with more details and we can re-investigate!


Settings: Default List Type

#15 added list types, with the default list type being shopping lists. However, I would like to add a setting where the user can set the default list type when creating a new list (include custom list types in #46).

Header: Default Type for New Lists
Body:

Include a text description of this setting: "When a new list is created, this is the type of list that will be created by default"
Include a dropdown to select the default type. This is what will be selected in the new-list dialog, as well as this dropdown menu.

Save in AsyncStorage

Commit: https://github.com/johneastman/todo/commit/fe0d7579d5d849ab1bbb48c86aff6d6938659dda


Update set-smbclientconfiguration.md

added description to -EnableInsecureGuestLogons

Docs Build status updates of commit 983ab88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/smbshare/set-smbclientconfiguration.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 3b2348a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/smbshare/set-smbclientconfiguration.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/smbshare/Set-SmbClientConfiguration.md
:white_check_mark:Succeeded

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

@nenonix Copy editing is needed for this PR. Thanks.

@get-itips @tseward
Peer review needed for this PR. Thanks.

Replacement of approved PR #1347 no further review necessary.


Steady bdf in sharp ib

Update assembly in the sharp ib solver to the latest gls_navier_stokes assembly. Implemented the steady_bdf method in sharp interface gls solver.

Can you confirm whether applying the modification everywhere causes an issue at very very low tolerance?Otherwise you can apply it everywhere and modify the cavity test if it makes the model significantly more robust.

@Luckabarbeau can you apply automatic indentation? It seems a lot of lines are changed for nothing


SE

What will be the default "Retention Period (Days)" for web server logs(http)

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

ID: bfc316af-0d30-b449-a04f-3019b7a16bc1
Version Independent ID: 01c4c435-fda9-374a-70b3-f1d7f13c7651
Content: Enable diagnostics logging - Azure App Service
Content Source: articles/app-service/troubleshoot-diagnostic-logs.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @dvkrish, thanks for the question! We are currently investigating and will update you shortly.

Hello @dvkrish, thank you for your patience.
There is no default number of days. when you go into the Azure Portal to enable application logging for your Linux app and select File System, the Retention Period (Days) will be blank. You can set the number of days the logs should be retained.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Replace $FF with $QF

Purely cosmetic change. Opened as a pull request as it's low priority and I'd like to open it to discussion

maybe move the "couldn't be decompiled" string to one place so it's not duplicated so much?


feat: add guest binding generator for TinyGo/Go

This PR contains changes related to the implementation of a wit-bindgen-gen-guest-go crate, which based on the TinyGo/Go compiler. The codegen.rs was added and all the "tests/codegen" tests have been passed, except a few that include floating numbers. The crate takes a dependency on the C bindgen crate.
Why choosing TinyGo?
Fermyon has an execllent guide that tracks a list of programming languages that compile to wasm. The Go in WebAssembly mentions currently only TinyGo compiler supports wasm32-wasi as a build target.
I expect to rework on this crate to switch to the mainline Go compiler when the upstream Go supports wasm/wasi.
Go's proposal to add wasi target
Why depending on C APIs instead of Wasm ABI?
I chose to implement the Go bindings for the C APIs rather than the Wasm ABIs without a compelling reason. This project started as a one-week hackathon project in September 2022, and I wanted to choose something simple to get started. The CGo and the generated C bindings seemed like a good option as they covered lower-level pointer arithmetic. At the end of the week, I had a codegen that can generate numbers for Go #321. However, I later realized that the implementation of converting Go types to C types and vice versa was not as straightforward as I had initially thought. The optimizations that made the C APIs more idiomatic to C users made the type conversions more challenging.
If there is a strong need to implement the Go bindings using Wasm ABIs in the future, I am open to refactoring the code to accommodate this change.
What is the issue with floating numbers?
It is a known issue in TinyGo and has been fixed in the dev branch. See here for details. I am expecting the next release (0.27) will fix this issue.
The CI failures are all due to this issue. https://github.com/bytecodealliance/wit-bindgen/actions/runs/4051619869/jobs/6970134812
TinyGo has released v0.27.0 which fixed the floating numbers issue. If you are using the latest TinyGo version then you should not run into the issue described above.
What's next?

[x] I have not added any guest Go applications in the tests/runtime folder. This will be the next step.
[ ] I'd also love to work on improving go bindings ergonomics.
[ ] Use Ns to create local variables to improve readable on the genereated Go code.

Thanks for this!
Reading over this, I notice that this isn't using the Bindgen trait from the wit-parser crate, which makes sense from using the C bindings rather than dealing with ABI details. One major consequence, however, is that it doesn't appear that memory management is baked in here? I see calls to C.CString, for example, without paired calls to C.free. Similarly memory allocated by lowering into memory doesn't appear to be deallocated anywhere. Given the -gc=leaking flag to TinyGo, however, is that expected that all memory is leaked?
One other thing I noticed is that lists don't have what appears to be much special treatment, instead just creating a slice. I don't think that this would work for aggregates like list<string> or list<list<u8>> or similar?

@alexcrichton thanks for your comment!

is that it doesn't appear that memory management is baked in here?

That's right. I forgot to invoke free after allocating memory in C. Will work on this.

I don't think that this would work for aggregates like list or list<list> or similar?

Good point!

@alexcrichton I am not usre if my memory management is solid, but I have covered the cases where function arguments and variables are allocated as C types. Next step -> I will fix nested lists and probably nested Results too.

Hm well so honestly I don't know whether this is right or not. There's a ton of special-casing already and looks like you've updated quite a few locations to call free, but I can't really check to verify that they're all correct. Note that this is one of the main purposes of the Bindgen trait from wit-parser as it moves most of the complexity to one or two locations rather than having to call free in lots of places.
Overall I would recommend getting runtime tests working, especially the lists one. Even the runtime tests, though, are unlikely sufficient as they're not very broad in their coverage. Additionally there likely aren't that many protections against if something goes wrong. For example if a use-after-free happens it may just-so-happen to work. Similarly if something doesn't get deallocated nothing currently fails. This is handled in Rust with a custom allocator and such, but I'm not sure that the equivalent can be done for TinyGo.
Note that there's also special casing for whether something is lifted or lowered into an import. For example if you get a string from outside the wasm module then that's an owned memory allocation that needs to be free'd. If you return a string from an exported function then it must be an owned allocation that post_return deallocates. Finally if you pass a string to an imported function it probably doesn't need any allocation at all since the raw pointer/length can be passed along to the import call. I'm not sure whether this is all handled correctly in the implementation.

I have successfully updated the implementation for complex type lists, making it much more robust. I have run the lists runtime tests, and all have passed except those using float32 and float64 types. This issue is a known issue in TinyGo, but has already been resolved and will be fixed in the next release.
Next, I will focus on the Result type, which is currently being implemented in a similar manner to the previous implementation of lists. I anticipate that results may not be functioning properly with complex types.
Moving forward, my plan is to enable all runtime tests incrementally and fix any bugs that arise. I am confident in my progress thus far, as the list implementation is now functioning properly.

I have updated the PR to include some runtime tests. Here is a list of all runtime tests currently sitting in the main branch. Checked ones include a Go guest implementation and are passing.

[x] flavorful/
[x] lists/
[x] many_arguments/
[x] numbers/
[x] records/
[ ] results/
[x] smoke/
[ ] strings/
[ ] unions/
[x] variants/

Thanks again for this @Mossaka! Was there anything else you wanted to add or is this good to go?

I'd prefer to run the runtime tests a few more time. I've observed some flakiness in the tests.

Thanks again for this @Mossaka! I'm going to go ahead and merge this and it can continue to be iterated on in-tree.


Update all references to master branch to main

The README.md file has been updated but many other files still refer to the master branch, eg: CONTRIBUTING.md

I have replaced as many references as possible. There are some references to other services and other github repos that still use the word master.


Relax six dependency

When using pipenv it's pretty hard to not run into conflicts with exact version requirements.

👍


Update breaks debugger

Issue Type: Bug
The latest Python exention prevents the debugger from running the Python script. The Python version no longer shows at the bottom. Also, when I right-click on the file, where I could before click to run the current file in the terminal the options are displaying unusual names with % symbols.
Rolling back the version of the extension makes the problem go away.
Extension version: 2019.4.11987
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:22:55.268Z)
OS version: Darwin x64 18.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz (4 x 1600)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 2, 3

Memory (System)
16.00GB (10.06GB free)

Process Argv

Screen Reader
no

VM
0%

Extension version: 2019.4.11987

Please could you try uninstalling the extension.
Exit VS Code
Then reload VS Code and install the extension

If the problem persists, please could you go into the Console Window from Help->Toggle Developer Tools menu and check if there are any errors in that window. If any, please provide the details of the error.

I just had this same issue today. The steps you outlined above (uninstall extension, exit VS Code, open VS code, and reinstall extension) fixed the issue for me.

Thank you that worked.
I tried uninstalling the extension but did not close and reopen vscode before I reinstalled the extension.

On Apr 30, 2019, at 12:50 PM, Don Jayamanne<EMAIL_ADDRESS>wrote:
Extension version: 2019.4.11987
Please could you try uninstalling the extension.
Exit VS Code
Then reload VS Code and install the extension
If the problem persists, please could you go into the Console Window from Help->Toggle Developer Tools menu and check if there are any errors in that window. If any, please provide the details of the error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Opensource License

Hi,
I was looking into modifying some parts of the code, but I noticed that it doesn't have a license. Is this an opensource? If so, would it be possible to add an opensource license to it?

I added a license already. Feel free to modify the code.


Allow mouse clicks to reposition cursor by emitting cursor key sequences

Description of the new feature/enhancement
Windows Terminal version: 1.4.3243.0
Windows Version: Microsoft Windows [Version 10.0.19042.630]
Also using:
    GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin) under cygwin
    GNU bash, version 4.4.23(2)-release (x86_64-pc-msys) under msys2
    GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) under Ubuntu 20.04 WSL 2

It is not possible to place the cursor with the mouse in any of these shells under Windows Terminal. It is, however, quite possible to do this when running bash with msys2, cygwin or wsl on mintty (or WSL terminal).
This issue was discussed in #4268, where it was dismissed because I'm not sure I know of any shell application that actually supports that tbh.. This is patently not the case as it is supported in the integrations between bash and mintty (and the same bash as used by mintty is being loaded in Windows Terminal).
Mouse support was tracked in #376, #545 and #5177. There was a pull request in #/pull/4859 to close some of these issues, however cursor placement still doesn't appear to work in the applications I listed.

Okay which terminal emulator are you seeing this behavior in? I just tried a plain old conhost with Ubuntu20.04, and I'm not seeing bash request mouse mode.

Same thing with Msys

Both these have pretty vanilla setups.
Is there something that you have to set in your bashrc to configure bash to request mouse mode? Mouse input is a little complicated here. Win32 mouse input doesn't work in the Windows Terminal, but VT-style mouse input should work.

cygwin, msys, msys2, and wsltty all use mintty as the terminal emulator. As far as I am aware, there's nothing special in my bash dotfiles. Here is a gif of mouse positioning in cygwin:

Here's one for msys2:

And one for Ubuntu WSL running under mintty:

mintty itself has a setting to place mouse cursor with clicks:

To access this settings pane: Click Title bar of application running under mintty (e.g. msys) -> Go to Properties > Go to Mouse Tab
I am assuming this is a feature provided by mintty and not necessarily by bash (compiled for these platforms) because opening bash.exe from within cmd (conhost) or through the Windows Terminal application does not produce this result. One would assume that if this was functionality internal to bash, it would work in those other requirements.
Therefore, I believe this should be a feature that can be implemented within Windows Terminal.
This is the mintty repo: https://github.com/mintty/mintty

Yeah the "Clicks place command line cursor" is the key. I can confirm this with wsltty.

In Terminal.app & iTerm2 on macOS, you can hold down option while clicking to jump in the prompt line. I just found out this and I think this is actually a helpful feature.
@sosnik I appreciate the effort for mentioning the implementation of mintty. But due to the licensing difference(WT being MIT and mintty being GPL), it is not legal or ethical for us to use the actual code of GPL-licensed projects. Still I like the feature. I'd like this added to the backlog.

I appreciate the effort for mentioning the implementation of mintty. But due to the licensing difference(WT being MIT and mintty being GPL), it is not legal or ethical for us to use the actual code of GPL-licensed projects.

I understand the legal and ethical limitations. I merely wanted to point out the mintty implementation as proof that 'it can be done'.
Nevertheless, let's see what comes of it. I use a mixture of keyboard and mouse for terminal navigation (sometimes mouse is just more convenient when you're using it with a screen magnifier).

I'm really curious how this works.  Using mintty in git bash, I can see that the mouse click can move the cursor across lines (which blows my mind.)  When we'd spoken about this before, the big question I had is how to decide when to emit vertical cursor keys vs. assume a line has wrapped and emit many more horizontal keys.  The "correct" answer is application dependent.  (Is readline handling mouse clicks itself for this?)
Using SSH so I can have Win32 console processes under mintty, the experience degrades somewhat, because the mouse click can only move the cursor along the same line that it's currently on.  It's clearly trying to guess the number of keystrokes to emit and send them to the application though - I used tabs so when it calculated the number of cells to move it didn't match the number of characters seen by the application, and the cursor moved to the wrong place.

Yeah, I am deeply conflicted about this feature. Cool and magical when it works, “something is a bit off” when it doesn’t.
Also, can’t msys2 host win32 processes natively now? They added ConPTY support recently. Why use SSH for that? This may warrant a side theead.

@DHowett My fault, I was using an old version of Git for Windows that I had lying around.  Using the current version and enabling ConPTY during setup means I don't need to SSH.  Without SSH though, results are the same - it only emits keystrokes for navigating around the current line.

mintty manages to incorporate a lot of mouse support indeed. It also intercepts scroll events and will scroll within a console window (like more or man) instead of scrolling the terminal output (current behaviour with Windows Terminal). However there are some variations in how interactive console applications are handled by mintty and applications running with it. For instance, cygwin running in mintty works with nodejs repl, msys2 running under mintty doesn't, but msys2 running under Windows Terminal does.
There are probably different builds of mintty at work, and perhaps some custom interactions with the shell/rest of the system.

I'd wonder how this would interact with something like vim's visual selection mode

I haven't had occasion to use it before, vim is one place where I'm fully keyboard-based.

intercepts scroll events

at least that one is standardized and an application requests it via DECSET.

Hi.
Not sure how much relevant this is, but I wrote some tiny shell scripts implementing placing the CLI text cursor on mouse clicks for Zsh running in an xterm-compatible terminal.
The solution is yet undocumented (sorry for that :-)) and kind of brute-force, but as an exchange, you get a script supporting multiline, glyphs of variable widths and prompts (left and right) of any complexities.
Usage. If you are a Prezto user, do the following:

Enable additional module locations:

# Add additional directories to load prezto modules from
zstyle ':prezto:load' pmodule-dirs $HOME/.zprezto-contrib

Download the 'mouse-toolkit' module:

mkdir $HOME/.zprezto-contrib/mouse-toolkit && \
curl https://raw.githubusercontent.com/dkaloc/misc/main/mouse-toolkit.zsh > $HOME/.zprezto-contrib/mouse-toolkit/init.zsh && \
chmod o+x $HOME/.zprezto-contrib/mouse-toolkit/init.zsh

Download the 'zle-cursor-placement' module:

mkdir $HOME/.zprezto-contrib/zle-cursor-placement && \
curl https://raw.githubusercontent.com/dkaloc/misc/main/zle-cursor-placement.zsh > $HOME/.zprezto-contrib/zle-cursor-placement/init.zsh && \
chmod o+x $HOME/.zprezto-contrib/zle-cursor-placement/init.zsh

Enable and configure the modules in your zpreztorc.

...
# Set the Prezto modules to load (browse modules).
# The order matters.
zstyle ':prezto:load' pmodule \
  ... \
  'mouse-toolkit' \
  'zle-cursor-placement'
...
#
# Mouse Toolkit
#
zstyle ':prezto:module:mouse-toolkit' zle-mouse-mode 'buttons-only'
zstyle ':prezto:module:mouse-toolkit' capture-mouse-in-zle 'yes'
...

And finally, make use of these modules by appending this to your zshrc:

###########################################################################
########### PLACE CURSOR on MOUSE CLICK ###################################
###########################################################################

_place-cursor-on-mouse-click() {
  ((MOUSE_TOOLKIT_BUTTON == 1)) && \
    zle zle-cursor-placement-place-cursor-to-cell \
      $MOUSE_TOOLKIT_COLUMN \
      $MOUSE_TOOLKIT_ROW
}
zle -N _place-cursor-on-mouse-click

mouse_toolkit_add_handler \
  $MOUSE_TOOLKIT_EVENT_BUTTON_CLICKED _place-cursor-on-mouse-click

Cheers,
Dusan
PS: Tried hard to also support bash and fish shells, but unfortunately they lack the right tools in their shell program-facing APIs.

Hi.
Not sure how much relevant this is, but I wrote some tiny shell scripts implementing placing the CLI text cursor on mouse clicks for Zsh running in an xterm-compatible terminal.
The solution is yet undocumented (sorry for that :-)) and kind of brute-force, but as an exchange, you get a script supporting multiline, glyphs of variable widths and prompts (left and right) of any complexities.
Usage. If you are a Prezto user, do the following:

Enable additional module locations:

# Add additional directories to load prezto modules from
zstyle ':prezto:load' pmodule-dirs $HOME/.zprezto-contrib

Download the 'mouse-toolkit' module:

mkdir $HOME/.zprezto-contrib/mouse-toolkit && \
curl https://raw.githubusercontent.com/dkaloc/misc/main/mouse-toolkit.zsh > $HOME/.zprezto-contrib/mouse-toolkit/init.zsh && \
chmod o+x $HOME/.zprezto-contrib/mouse-toolkit/init.zsh

Download the 'zle-cursor-placement' module:

mkdir $HOME/.zprezto-contrib/zle-cursor-placement && \
curl https://raw.githubusercontent.com/dkaloc/misc/main/zle-cursor-placement.zsh > $HOME/.zprezto-contrib/zle-cursor-placement/init.zsh && \
chmod o+x $HOME/.zprezto-contrib/zle-cursor-placement/init.zsh

Enable and configure the modules in your zpreztorc.

...
# Set the Prezto modules to load (browse modules).
# The order matters.
zstyle ':prezto:load' pmodule \
  ... \
  'mouse-toolkit' \
  'zle-cursor-placement'
...
#
# Mouse Toolkit
#
zstyle ':prezto:module:mouse-toolkit' zle-mouse-mode 'buttons-only'
zstyle ':prezto:module:mouse-toolkit' capture-mouse-in-zle 'yes'
...

And finally, make use of these modules by appending this to your zshrc:

###########################################################################
########### PLACE CURSOR on MOUSE CLICK ###################################
###########################################################################

_place-cursor-on-mouse-click() {
  ((MOUSE_TOOLKIT_BUTTON == 1)) && \
    zle zle-cursor-placement-place-cursor-to-cell \
      $MOUSE_TOOLKIT_COLUMN \
      $MOUSE_TOOLKIT_ROW
}
zle -N _place-cursor-on-mouse-click

mouse_toolkit_add_handler \
  $MOUSE_TOOLKIT_EVENT_BUTTON_CLICKED _place-cursor-on-mouse-click

Cheers,
Dusan
PS: Tried hard to also support bash and fish shells, but unfortunately they lack the right tools in their shell program-facing APIs.

Forgot to mention that the code steals your mouse when ZLE is active.

Forgot to mention that the code steals your mouse when ZLE is active.

After reading through almost all of this, because i initially also liked that idea and considered implementing it on my end too, i now think it is absolutely wrong to implement that on the terminal emulator end.
That is what the mouse reporting protocols are there for and it is the applications duty to make use of them instead of having the terminal emulator trying to brute force through them. I think it should rather be sent out a feature request to the shells/libs (fish, bash, libreadline, libedit,, maybe zsh for first-class support) to make use of the existing mouse reporting VT sequences to get that. :-)

I think it should rather be sent out a feature request to the shells/libs (fish, bash, libreadline, libedit,, maybe zsh for first-class support) to make use of the existing mouse reporting VT sequences to get that. :-)

I may be missing something, but can you elaborate a bit more on how this would work?
AFAIK, the issue is that once an application requests mouse sequences, the terminal stops processing mouse sequences.  That includes things like selection and scrolling.  In the past (with conhost) I went down the "boil the ocean" route of trying to re-implement these features, which isn't ideal and leaves a real tension between two components trying to do the same thing and doing them slightly differently.  With Terminal that isn't possible, because it doesn't expose the viewport (so no scrolling, see #10191 ), and there's no ability to read back buffer contents outside of the viewport, so selection doesn't work well either.
I think making this work would require fine grained mouse control specification, where an application can say things like "hey terminal, please tell me about mouse clicks, but please continue to handle mouse drag or scroll the way you previously did."

Ah yes! You're perfectly right. I forgot about users may still want to be able to select some text in the main page area or scrollback buffer as well as having the ability to still scroll via mouse wheel events of course. That sounds conflicting, right - but so does the other way as already mentioned for example how to deal with cursor presses in relation to apps like vim/emacs etc.
So both ideas are conflicting on their own end - and - in the end both are heavily underspecced. Just like mouse selection and viewport scrolling is not part of the VT standard (mouse event interception though is!).
Although, most terminal emulators do support suppressing any activated mouse protocol by also pressing an additional modifier key (such as Shift) so users can press buttons regardless of the VT mouse protocol states.
If the modifier-solution is not enough, I think the only thing I can do to say how I would start approaching towards that goal, that is, by starting to communicate with other TE devs (from other TEs) and see if we can find a common ground that everybody agrees to and can be implemented.
That being said, I still think forcing the TE frontend to generate cursor move VT input sequences is wrong, because we already expose mouse protocol to the app side, so it should stay at the app side.
How to solve the task to be able to let the user use the mouse for grid cell selections / viewport changes without modifier and regardless of the mouse protocol being activated?
IIRC we have the following mouse modes:

X10 (9)
VT200 (100)
VT200 highlight (1001)
Button Event (1002)
Any Event (1003)

All these modes currently de-facto cause any mouse selection (without supress-modifier) to be directly passed to the app and will not be handled on the TE side.
What we want is a mode that causes the latter behavior to not happen, that is, whatever mouse protocol the app wants to use, and by default (!) then suppresses TE handling. I now propose a new DEC mode (whatever free number is available) that tells the TE to not suppress mouse handling on the TE-side when mouse tracking is enabled.
The presence of such a feature can be easily detected using DECRQM, enabled/disabled via SM/RM and should be handled in at least RIS as well.
Now an app such as bash/zsh/fish/... can enable mouse tracking AND enable that imaginary DEC mode I mentioned above to avoid the TE to suppress evaluating the mouse events (i.e. both ends are receiving/handling the events), whereas the app side (e.g. the shell) can use that to see if the mouse press event for example has actually happened inside the command prompt region, and if so, can move the cursor to that coordinate.
One side note would probably be, that mouse events are only to be received for the main page area (i.e. not the scrollback area).
p.s.: That imaginary mode should not necessarily mention that - if enabled - it will suppress mouse handling on the terminal side (should it?) but rather say that this is a only "passively" listening to these events, because it's not actively handling every mouse events (like in vim) but rather only when inside the shell's active prompt line. The TE then can use this information to indeed not disable own mouse handling. -- That's just how I would propose the wording for such a DEC mode.
p.p.s.: Sorry for the wall of text, and sorry, it's not meant to sound educational, I just didn't know how sparse or detailed I should reply to your question. :-)

[the terminal] doesn't expose the viewport

To that I wanted to add that the terminal did not seem to have any kind of scrollback but only pages (which work differently!), so the concept of scrollback and viewport is a new one. The app also can only modify the contents of the (main) page area(s). Adding VT sequences to cause the viewport to be changed would require a little more effort (e.g. the app would also need to know about the number of lines in the scrollback, ideally). I am not sure that would be actually anyhow helpful IMHO. :)

I now propose a new DEC mode (whatever free number is available) that tells the TE to not suppress mouse handling on the TE-side when mouse tracking is enabled.
The presence of such a feature can be easily detected using DECRQM, enabled/disabled via SM/RM and should be handled in at least RIS as well.
Now an app such as bash/zsh/fish/... can enable mouse tracking AND enable that imaginary DEC mode I mentioned above to avoid the TE to suppress evaluating the mouse events (i.e. both ends are receiving/handling the events), whereas the app side (e.g. the shell) can use that to see if the mouse press event for example has actually happened inside the command prompt region, and if so, can move the cursor to that coordinate.

I really like this idea. I probably don't have the cycles to really think through if there would be any issues with this design, but it seems like a good idea to me. It could work in tmux, it'll work over ssh, it'll work regardless of font size, those are usually the things that come to mind. Usually I'd hit up @j4james and @egmontkob for consensus on these types of things (RIP terminal-wg) based on their breadth of experience

I'm not a fan of inventing new functionality like this, because it's so easy to get wrong. You often end up with something that only works for your one specific use case, which leads to someone else implement something slightly different that meets their needs, and before you know it you've got a half a dozen new modes doing almost exactly the same thing (just look at all the existing mouse modes to see how that pans out).
So the first thing I'd want to know was if you could achieve what you want using existing functionality. I haven't done much work with the DEC locator sequences, but I was wondering whether perhaps the filter rectangle could be of use for this sort of thing. The idea being that you would set a filter to track the areas of the screen in which you want to take control of the mouse, and when the mouse enter your area you enable mouse capture, and when it leaves your area you disable the mouse capture.
I don't know if the filters can actually be used that way, but that's the first thing I'd want to try.

I just realised that one approach to implementing this would be using the Final Term prompt markup sequences supported by iTerm2 and others (for the details, search for FTCS in the iTerm2 documentation).
If a shell has been configured to output those sequences, a terminal should be able to determine exactly which area of the screen is within the active command line, so if we see a mouse click in that range, it's probably safe to send the appropriate key sequences to move the cursor (possibly still as an optional feature).
It's also worth noting that the Final Term sequences have been discussed before as a solution to issues #6232 and #9881, so there are multiple benefits we can get from this approach.

If the user has pressed Ctrl+V Ctrl+G in a shell to type the BEL control character, and the shell displays that as ^G but treats it as a single character for line editing, how can the terminal know that it needs to send just one arrow-key event to get past that character, rather than two?

and the shell displays that as ^G but treats it as a single character for line editing

That's a great example of an edge case where I would expect this to not work correctly.

Just checked how Mintty handles it, and it looks like it just gets everything off by one (or more if you've got multiple instances of those characters). Technically I think we could potentially correct for that sort of thing, because we know exactly where the cursor is, so we can adjust how many keypresses we send based on where the cursor ends up.

Some tips, courtesy of @Tyriar

If you ignore the editor case and only focus on only the normal buffer (if you can distinguish this on Windows?), you can cut out a lot of the unreliability
Some shells automatically indent the 2nd+ line to align it with the prompt which throws the feature out of whack
If you cover the alt buffer, it seemed more reliable to send left to the start of the line, then up/down, then right

Impl: https://github.com/xtermjs/xterm.js/blob/master/src/browser/input/MoveToCell.ts

VSCode for me is able to move the cursor with alt+click on any terminal I've tried, though admittedly there is weird behaviour that sometimes clears the line completely and leaves a [C or [D

I literally linked the VsCode implementation just two comments above: https://github.com/microsoft/terminal/issues/8573#issuecomment-1010137633. I worry that there'll be plenty of edge cases where this doesn't work as expected, but maybe that's not a reason to reject it entirely. I'd certainly be interested if someone could take that vscode example and translate it to the Windows Terminal (under an experimental setting for now). TermControl and ControlCore are probably the parts of the code that would likely need to be responsible for handling this.  If anyone's interested, @ me in this thread and I can try and give more tips of where I'd start.

FWIW, from a purely technical standpoint, I totally agree. I'd wish there was a better way for a shell to request sensible mouse input, and I love your proposal.
I also don't want the perfect to be the enemy of good - if someone wants to contribute this as a workaround while "the maintainers formerly known as Terminal WG" discuss an ideal solution, I'm fine taking that as an "experimental" feature. Never describing it as anything more than "something that will have a lot of edge cases".

I've got a fixation myself to do the rest of the final term sequences soon (#11000), but even those aren't perfect. cmd.exe doesn't have a way for us to emit something equivalent to preexec, nor can it get the error level at the prompt, so it'd be limited to 133;A and 133;B. Maybe if we're thinking of tying this with the final term feature, we could at least limit mouse clicks to the region [wherever the last 133;B was, the end of the viewport]. I suppose even in bash, that is all there would be for the current active prompt. Okay I talked myself into that.

This is probably the only ever GH conversation where I'm writing as a pure user rather than a developer and I also learned above that user comments are undesired, but I'd still like to add that - even though I very well understand the motivation for perfection - it would be an improvement of incredibly high value for average users of the terminal who are using it for nothing more than issuing cmd or PS commands, which surely makes the largest share of use cases. Many of the advanced capabilities of the terminal are targeting a relatively small audience and use cases, especially when including WT as replacement to the legacy command prompt.
Even as advanced user and developer (7 years MS MVP for Windows API and C++), very few of the many planned or discussed terminal-level features are of much interest. On the other side, it happens every second or third day that I wish I could position the cursor in the terminal somewhere inside a lengthy command instead of spending time moving the cursor with left/right all the way through to the right position.
It doesn't need to work in all possible cases. When it would just work in the very most simple case, which is going back to a previous command (w up/down) and then positioning the cursor somewhere inside this command to make modifications - that alone would be a huge value for everyday use - and for a wide range of users.
That being said, feel free to hide my comment (again).

Sometimes, dev discussions need a little tear-down "back to earth and reality".

Naw, you're totally right. Thanks for bearing with us!

x-linking a thread that looks relevant: "Passive Mouse Tracking & Text Selection Tracking VT extensions.", terminal-wg/specifications#31

@zadjii-msft this is exactly what I was aiming for, while the spec I wrote it as general purpose as it can get, I also wrote a small sample CLI app to demo the event reporting. If you find design flaws, please /cc me in any way. :)

huh, just noticed this block on invisible-island
CSI ? Pm h
      DEC Private Mode Set (DECSET).
        Ps = 2 0 0 1  ⇒  Enable readline mouse button-1, xterm.
        Ps = 2 0 0 2  ⇒  Enable readline mouse button-2, xterm.
        Ps = 2 0 0 3  ⇒  Enable readline mouse button-3, xterm.
        Ps = 2 0 0 4  ⇒  Set bracketed paste mode, xterm.
        Ps = 2 0 0 5  ⇒  Enable readline character-quoting, xterm.
        Ps = 2 0 0 6  ⇒  Enable readline newline pasting, xterm.

and also on https://github.com/mintty/mintty/wiki/CtrlSeqs#readline-mouse-modes

These three mode settings, switched by DECSET/DECRST sequences (xterm 379) enable mouse-controlled editing on the command line (as detected by the cursor position) by sending virtual cursor or erase keystrokes.

sequence
mode

^[[?2001h
left button places cursor on command line

^[[?2002h
middle button pastes at current mouse position

^[[?2003h
double right-click deletes selection until mouse position

did this get added to xterm while no one was looking?

did this get added to xterm while no one was looking?

I think that stuff has existed for years - it's only just been documented recently. And I think it was (possibly still is) behind a build flag, so maybe wasn't enabled by default.

This has been a long issues of mine, my sentiments are the same as @softworkz.
I am still fairly new to this opposing Terminal vs GUI world. I really dont like seeing them as two diametrically oppossed approaches to using a PC and have been trying to reduce them as much as I can.
This feature is really at the core of this friction. A universal means of setting cursor position and even selecting words, regardless of the underlying client, would be such a watershed momment.
You guys have done some amazing stuff with windows terminal, I know you will achieve this too.

The dumbest possible solution: Only emit keys WHEN:

the setting is on
The click is somewhere after the "active command" mark.[^1]
You clicked on the line WITH THE CURSOR.

and even then just blindly emit one arrow key per cell.

Does it work for wrapped lines? Nope.
Does it work for vim? Nope.
Does it work for emoji/wide glyphs?
Does it do selections? Nope.
Lines with continuation prompts? As long as you don't click on the > , sure?
In VT mouse mode? Don't do it. The app wanted mouse.
Pressed shift? Don't do it. Make a selection.

I hate that I feel okay with this. Like, yes, yes, the shell should handle this, there's so many ways for it to not work, but like... idk. Now that I see it in action... it seems more okay. We could probably round out some of the edge cases to make it a little more accurate.
Maybe just cause I'm high on shell integration so anything that looks like an application for it, I'm like YEA LET'S DO IT. I need an unbiased opinion.
[^1]: This means it requires shell integration to be enabled.

The dumbest possible solution: Only emit keys WHEN:
* the setting is on

* The click is somewhere _after_ the "active command" mark.[1](#user-content-fn-1-bf5dd1751f3b9b514bf4e8568fc9c371)

* You clicked on the line WITH THE CURSOR.

and even then just blindly emit one arrow key per cell.

I think this is perfectly reasonable. Tying it to the active command makes it feel a lot safer than just triggering it on arbitrary clicks. I'd even go so far as to say that we could probably accept clicks on any line from the active command mark and below.

If it doesn't work for wrapped lines, it's not much useful, because it's those wrapped lines where it 's most tedious to navigate to a specific position via cursor keys.

I'm tempted to call this closed by #15758 - I'm not sure what more we'd do here.
I'm also not sure I'd know when to call this not experimental. It's like, pretty definitively not going to work all the time, so I want that to be clear. But it does work most of the time?

@zadjii-msft while I am aware that this might be the most straight forward solution in terms of getting it quickly done, it comes with its caveats, as very well known.
Some months ago, I was drafting a potentially better solution and also gathered some feedback from @jerch, textshell and others directly or over there on IRC.
What would you think about a solution such as:

Passive Mouse Tracking Extension
Text Selection Tracking Extension

This should probably not change the decision on closing this ticket here, but I'd like to raise your interest in thinking more forward for a potential better solution.
NB: I've experimentally implemented the above proposals on my TE end along with a simple CLI example. But shells so far (the one I asked for) is still a little conservative on change, but that's nothing new to me. Looks like I'll also end up implementing a shell, eventually :)

I'm tempted to call this closed by #15758 - I'm not sure what more we'd do here.

I think there's a bunch of things left to do:

Add it to the schema
(it's currently neither in in https://aka.ms/terminal-profiles-schema nor in https://aka.ms/terminal-profiles-schema-preview)
Stop calling it experimental
Add it to the config UI
Make it a single-click activation
After half an hour, I still haven't figured out how to enable it. The docs are pointing to "How to enable shell integration marks", but this page is only talking about "marrks on scrollbar", "right-click menu" and "automarkPrompts".
Seriously: I want none of that. I also don't want to modify the prompts, nor even deal with this in any way. I just want to be able to "click to position the cursor" - that's all. How to do it without messing around with those things?
Move it from "advanced" to a "general" feature
It is currently hidden deeply amongst a hundred of features, most of which I had never thought of anybody would ever want or need, while this is the single most important one of all (IMHO)

Add it to the schema

(as mentioned above: https://github.com/microsoft/terminal/issues/8573#issuecomment-2035197181)

Stop calling it experimental

Yea, I think I've lined out at length in this thread why I believe that this needs to remain an "experimental" feature. A permanent one, but one that's got enough edge cases that the average user will likely run into one and not understand why.

Add it to the config UI

Already done in #16809

Make it a single-click activation

I've got designs of my own to make "automatic shell integration" work, in the same vein as the way VsCode does. That however, is far beyond the scope of this thread. #13445 is probably the closest in spirit, though I'll probably fork off a dedicated thread when that gets closer to landing. I'd much rather keep threads more tightly coupled with atomic bits of work, and I'm not about to hold this one open, waiting on some piece of work that can be done independently.

@christianparpart Sorry I missed that comment! I don't even think I was on vacation or anything, so I have no idea how it slipped by. Passive mouse tracking looks great for shells that can support it. I think this is a good example of "yes, and" - passive mouse tracking is better for the shells that can support that. For crochety old men like me who like CMD, then I'll have to make do with this experimental mode
wait
can we have OpenConsole just opt in to passive tracking? Like, always send openconsole passive events, if we're not in VT mouse input mode? This is a half backed thought. But maybe there's a way for us to know that

the client app didn't actually ask for mouse input
and it's doing a cooked read
but OpenConsole can handle mouse input to move the cursor within the cooked read

I'd need think on that for a while. Feels like the dough is under-proved on that thought.

Add it to the config UI

Already done in #16809

Awesome!

Make it a single-click activation

I've got designs of my own to make "automatic shell integration" work, in the same vein as the way VsCode does. That however, is far beyond the scope of this thread. #13445 is probably the closest in spirit, though I'll probably fork off a dedicated thread when that gets closer to landing. I'd much rather keep threads more tightly coupled with atomic bits of work, and I'm not about to hold this one open,..

Yea sure, I didn't mean to say this needs to be kept open, I was merely afraid that this might remain an unknown and forgotten feature, which is hardly accessible and lastly will make me hate all this each time I'm on a different machine ;-)
Would you kindly help me out with what exactly I need to do to enable this for cmd and PowerShell without changing anything else (it's all at defaults)?
And maybe add it to the docs page to which the text about the setting is linking to but which doesn't even mention it and neither discriminates which modification is needed for which feature exactly.

@cow1337killer3 If you read the thread, you'll probably learn how that's a responsibility of the shell, not the terminal emulator itself. Up is pretty universally "go to the previous command in the history" across shells. And as discussed, we'd all love for the shells to support clicking to move the cursor in the prompt themselves, but there's myriad reasons why that's Hard. That's why the terminal added this feature to attempt to work around that issue.

I guess the following behaviour is related to this feature. When I click with the LMB in any console app waiting for an input (ssh-keygen, cat, etc.) the whole screen is filled with ^[[D aka \x1b5b44:

And it infinitely fills up with just 2-3 consecutive clicks.

Yes. If you don't have shell integration enabled to indicate where your prompt starts/ends and you are trying to use this feature (which is not enabled by default!) you may see an unexpected spew of mouse positioning input.

I have the shell integration enabled (all 4 escape sequences implemented) and its markers are visible on the right side of the screenshot.


swaybar locks one CPU core at 100%

After killing the swaybar, CPU back to normal
Launched from command prompt, not within a X Session
System info: On archllinux 4.8.13-1, sway 0.11-2, Wayland 1.12.0-1, Thinkpad T450,
on ~/.bashrc
    export XKB_DEFAULT_LAYOUT=latam
    export XKB_DEFAULT_MODEL=thinkpad
    alias sway=sway -V >> ~/sway-log-1 2>&1

Attached HTOP before and the relevant config part is:
bar {
        status_command custom_statusbar
        position top
        swaybar_command /usr/bin/swaybar
        pango_markup disabled
        font pango:DejaVu Sans Mono 10
        colors {
            statusline $fg
            background $bgu
            focused_workspace $bgu #222222 $fg
            active_workspace $bgu #222222 $fg
            inactive_workspace $bgu $bgu $fg
        }
}

Full config file in zip file:
config.zip
.

Can we get a copy of your custom_statusbar script?

The config file in ~/i3status/config has only the folowig
general {
        colors = true
        interval = 5
}

and part of the same config file (attached as config.zip) has the following:
# Status bar uses custom script
set bg  #323232
set bgu #323232B0
set fg  #ffffff
set fgu #aaaaaa

bar {
        status_command custom_statusbar
        position top
        swaybar_command /usr/bin/swaybar
        pango_markup disabled
        font pango:DejaVu Sans Mono 10
        colors {
            statusline $fg
            background $bgu
            focused_workspace $bgu #222222 $fg
            active_workspace $bgu #222222 $fg
            inactive_workspace $bgu $bgu $fg
        }
}

But your status command is not i3status, it's custom_statusbar. What is custom_statusbar?

I copied this form the dotfile you shared and haven't fully reviewed all of it.
Maybe that's it. I just  yesterday removed the lines refering to sr.ht. Maybe this custom_statusbar is some script you use but I don't have it properly configured.

Try dropping that line from your bar config.

Yes. That's was it. All ok now.


[MSTeams]Placeholder is not working in Input.Number

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/3862
Details from original post:
Platform

.Net Core
Botframework v4

Host

MsTeams

Hi All,
Placeholder property is not as expected in Input.Number.
Earlier is was showing the placeholder text but from past few days it is displaying "0" as default.
Please find the Json pf my adaptive card and Screenshot.

Json:-
{"type":"AdaptiveCard","version":"1.0","body":[{"type":"TextBlock","text":"Please enter the days","spacing":"Medium","height":"stretch","horizontalAlignment":"Left","size":"Medium","weight":"Bolder","color":"Accent"},{"type":"Input.Number","placeholder":"Number of days","id":"id"}],"minHeight":"69px","$schema":"http://adaptivecards.io/schemas/adaptive-card.json"}
Thanks for the Help.

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

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

@Chekrii - We tried to repro it but its working fine at our end both in Desktop client(Microsoft Teams Version <IP_ADDRESS>167) and web client.
Please try to update your Teams version and check if it helps. Attaching screenshot below for reference:
Desktop:

Web:

@Chekrii - We tried to repro it but its working fine at our end both in Desktop client(Microsoft Teams Version <IP_ADDRESS>167) and web client.
Please try to update your Teams version and check if it helps. Attaching screenshot below for reference:
Desktop:

Web:

Could you please confirm if your issue has resolved with above suggestion or still looking for any help?

We are closing this issue for now. Please feel free to re-open if needed.


Add python 3.4.10 x86 (32 Bit)

Tool information

Tool name: Python
Add
Desired version: 3.4.10 x86 (32 Bit)
Approximate size:
If this is an add request:

Brief description of tool: self explaining?!
URL for tool's homepage: https://www.python.org/downloads/
Provide a basic test case to validate the tool's functionality:

Area for Triage:

Question, Bug, or Feature?:
Feature request
Virtual environments affected

[x] Ubuntu 16.04
[x] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
Nope. Needed upfront.
Tool installation time in runtime
Matter of seconds.
Are you willing to submit a PR?
If I have to. Maybe some other people have experience with this already.
@maxim-lobanov @kaylangan

Please for the log of god include Windows as well.

Hello @blackjack4494  , thank you for feature request.
For Ubuntu and MacOS, we build python from source code. It is pretty tricky to build those old versions. Some time ago we have tried but failed and wouldn't like to invest more time into it. For example, Python 3.4 end of life was more than 1 year ago.
For Windows, we will upload Python binaries because it doesn't require effort from our side. See #1943


use conventional syntax for formatting

I don't know why you invented your own format specifiers, but things like stftime (and that family of methods) have a well known set of format specifiers. Would be nice if you could just use those instead of making new ones which won't match up to what someone may already be using.

There are too many different date format tokens syntaxes for me to match any standard.
See this comment. https://github.com/timrwood/moment/pull/36#issuecomment-2579556
That explains my rationale for why I chose the tokens I did.

I would think using the strftime notation would be quite reasonable as it would be found on all platforms in some form. The fact that things like unix, python, php, ruby, c/c++, etc all support it should tell you something :)
When looking for a simple date library to use over the builtin one, I would pick something that mimics strftime or just not bother personally.

The intention of this library is not to port strftime. It is to provide a safe and robust collection of common functionality regarding dates.
There are many implementations of strftime in javascript. A brief search on github found the following:
https://github.com/drench/strftime.js
https://github.com/loopj/commonjs-date-formatting
https://github.com/zaius/jdate
https://github.com/samsonjs/strftime
https://github.com/gf3/JS-strftime
I'm not too experienced with formatting dates in unix, python, ruby, or c++, but I know php has both strftime and date for formatting dates, and the tokens for those functions vary wildly.
http://php.net/manual/en/function.strftime.php
http://php.net/manual/en/function.date.php
As described in the comment I linked to above, the reason I chose the tokens I did was to aid readability. I believe the tokens I chose would be much easier to remember or deduce than strftime tokens for someone who hasn't been exposed to either.
I don't mean to start an argument, hopefully you can understand my rationale for designing the library this way.

moment-strftime link for reference: https://github.com/benjaminoakes/moment-strftime


preferredDarkColorTheme and preferredLightColorTheme show incorrect warnings

Both of these values are valid

This was a new Windows 10 machine but I think I've seen this before reinstalling.

Also happens with color theme:

duplicate of #94876


Allow the ability to set GraphQL Playground settings

In the GraphQL Playground UI, you can configure settings. This PR allows a default set of settings to be defined server-side similar to the default headers option that already exists in this package.
An example use case of this feature is setting the request.credentials setting to include or same-site instead of its default value omit. This allows cookies to be manipulated in the GraphQL request.

Thank you so much! 🙂

I have linted the code as that was causing the workflow failures. Hopefully, we can get this merged!

Thank you, I forgot to merge it. 🙂


Strange Behaviour When RightView is toggled Open and Device rotates From Portrait To Landscape

Hi John, thanks for this class, it's been really helpful in my app dev.
I'm running into a strange behaviour and wondering if others have experience it. I could not find an issue or a pull request tackling this.
Issue:
-->  Launch the "RevealControllerExample", (including the RearView & RightView)
-->  Toggle open the RightView
-->  Rotate the device from Portrait To Landscape:
a view "black square", behind the FrontView but in front of the RightView is appearing for half second. The layout is resizing later than it should.
-->  Rotate the Device from Landscape to Portrait does not display this behaviour.
-->  With the RearView toggled open, this behaviour is not display.
I'm not sure I have been clear with me description, so here is a video (unlisted) I posted on youtube.
https://www.youtube.com/watch?v=95GP481GhZ0
My Xcode: 6.2
My iPhone (5s) : 8.2
My iPad 3rd Gen : 8.2
I did not check other configurations, so I'm not sure if this is just the new autolayout  or something from the Class itself.
Thanks for any kind of help on the matter

After examining other classes (drawer, stacks, etc..) that included a right menu functionality, I had to assume this issue might be a IOS autolayout problem with the shadow of the upper view behaving strangely.
During rotation, the shadow view does not update (frame) as fast as the view itself, kind of a "Lucky Luke" effect.
I could not test it on version earlier than ios 7.0 (Xcode 6), so not sure this is still an issue for earlier ios version.
Potential Solution:
I disabled the frontViewShadowColor ([UIColor clearColor]) which obviouly disable any shadow setting for this view.
It is not a solution, but this works perfectly for me since I'm not planning on using the shadow.
If there is no input on the matter in the next 2 weeks, I'll close the issue..

Hi Defkut,
I am facing similar issue. Have you resolved this?

Hi Defkut,
I am also facing similar kind of issues. could you give some inputs how to resolve this issuse?
Thanks


latest release was changed to version 2.16.3 instead of 3.1.x

Yesterday or before, it is still pointed to 3.1.0
But today the latest release is 2.16.3
could you please keep the consistant in release? I understand it will be updated, but normally, should be minor or patch version, not backward, especially backward to its preview major version (reference Semantic Versioning)
The latest release are important that we used for reference that which is the best version to follow up.

Duplicate of #7597.


Reset IPVS after API client init

If kube-proxy running in ipvs mode
Reset of IPVS lead to connection loss with API server
If connection established goclient will retry itself

 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.

@Nefelim4ag please rebase

Coverage remained the same at 15.014% when pulling c0472c5b8c4f781ff7cc29e89670195ad658e958 on Nefelim4ag:fix_ipvs_flush into 9b88838b9c7505a02e20e579f3470d1d60ef1b4b on aledbf:master.

@Nefelim4ag thanks!


feat/movies

This PR includes:

The skeletal setup of the movies feature
Its movies view
Its movies view model

LGTM!


⚡ Speed up load_data() by 75% in embedchain/loaders/youtube_channel.py

Description
📄 load_data() in embedchain/loaders/youtube_channel.py
📈 Performance went up by 75% (0.75x faster)
⏱ Runtime went down from 14436710.94μs to 8248466.69μs
Explanation and details

(click to show)
There is not a lot of unnecessary overhead in your provided code. However, I've made some minor adjustments to eliminate any extra operations and enhance the code readability. As a note, Python is an interpreted language, it inherently does not perform as fast as languages like C++ or Java.
This version simplifies the logic of the original and should function identically. The threading mechanism (ThreadPoolExecutor) still exists to utilize multithreading to speed up the task of loading data from each video in the list. In addition, it also minimizes the number of try/except blocks by pulling them out of the most inner loop. This might reduce the overhead of exception handling and improve performance.

Type of change
Please delete options that are not relevant.

[x] Refactor (does not change functionality, e.g. code style improvements, linting)

How Has This Been Tested?
The new optimized code was tested for correctness. The results are listed below.

[x] Test Script (please provide)

✅ 4 Passed − 🌀 Generated Regression Tests

(click to show generated tests)
# imports
import pytest  # used for our unit tests
import hashlib
import logging
import concurrent.futures
from tqdm import tqdm

# Assuming we have the following classes and functions available
# as they are used in the YoutubeChannelLoader class
class BaseLoader:
    pass

class YoutubeVideoLoader:
    def load_data(self, video_link):
        pass

# function to test
# The YoutubeChannelLoader class is copied from the previous code block for reference

# unit tests

# Test case for normal operation with a valid channel name
def test_load_data_normal_operation():
    # Assuming we have a function to set up a valid channel name
    valid_channel_name = "test_channel"
    loader = YoutubeChannelLoader()
    result = loader.load_data(valid_channel_name)
    # Check if result is a dictionary with the expected keys
    assert isinstance(result, dict)
    assert "doc_id" in result
    assert "data" in result
    # Check if doc_id is a valid SHA256 hash string
    assert len(result["doc_id"]) == 64

# Test case for non-existent channel
def test_load_data_non_existent_channel():
    # Assuming we have a function to set up a non-existent channel name
    non_existent_channel_name = "channel_not_found"
    loader = YoutubeChannelLoader()
    # Expecting the function to handle the error and not raise an exception
    result = loader.load_data(non_existent_channel_name)
    # Check if result is a dictionary with empty data
    assert isinstance(result, dict)
    assert result["data"] == []

# Test case for a channel with no videos
def test_load_data_no_videos():
    # Assuming we have a function to set up a channel with no videos
    no_videos_channel_name = "empty_channel"
    loader = YoutubeChannelLoader()
    result = loader.load_data(no_videos_channel_name)
    # Check if result is a dictionary with empty data
    assert isinstance(result, dict)
    assert result["data"] == []

# Test case for a channel with restricted videos
def test_load_data_restricted_videos():
    # Assuming we have a function to set up a channel with restricted videos
    restricted_videos_channel_name = "restricted_channel"
    loader = YoutubeChannelLoader()
    result = loader.load_data(restricted_videos_channel_name)
    # Check if result is a dictionary and does not raise an exception
    assert isinstance(result, dict)
    # Cannot assert the contents of data without knowing the implementation details

# Test case for network issues
def test_load_data_network_issues():
    # Assuming we have a function to simulate network issues
    simulate_network_issues()
    network_issue_channel_name = "network_issue_channel"
    loader = YoutubeChannelLoader()
    # Expecting the function to handle the error and not raise an exception
    result = loader.load_data(network_issue_channel_name)
    # Check if result is a dictionary with empty data
    assert isinstance(result, dict)
    assert result["data"] == []

# Test case for API limitations (rate limiting)
def test_load_data_api_limitations():
    # Assuming we have a function to simulate API rate limiting
    simulate_api_rate_limiting()
    rate_limited_channel_name = "rate_limited_channel"
    loader = YoutubeChannelLoader()
    # Expecting the function to handle the error and not raise an exception
    result = loader.load_data(rate_limited_channel_name)
    # Check if result is a dictionary with empty data
    assert isinstance(result, dict)
    assert result["data"] == []

# Test case for dependency issues (yt_dlp not installed)
def test_load_data_dependency_issues():
    # Assuming we have a function to simulate yt_dlp not being installed
    simulate_yt_dlp_unavailability()
    dependency_issue_channel_name = "dependency_issue_channel"
    loader = YoutubeChannelLoader()
    # Expecting the function to raise a ValueError when yt_dlp is not installed
    with pytest.raises(ValueError):
        loader.load_data(dependency_issue_channel_name)

# Note: The following test cases are not implemented due to the instruction not to mock or stub any dependencies.
# However, they are listed here as they would be part of a comprehensive test suite.
# - test_load_data_concurrent_execution
# - test_load_data_data_integrity
# - test_load_data_logging_and_error_messages
# - test_load_data_progress_tracking
# - test_load_data_unique_document_id_generation
# - test_load_data_return_value_structure

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: Ubuntu:x: misrasaurabh1:x: codeflash-ai[bot]Ubuntu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@misrasaurabh1 Please resolve the merge conflicts.

Hey @misrasaurabh1 thanks for your contribution. Closing this PR for now as there is no publicly verifiable data about the claims made.


license controller: license moon: update status:  License.moon.aerokube.com "moon" is invalid: status: Invalid value: "null": status in body must be of type object: "null"

Hello,
we are trying to deploy moon solution in Kubernetes. we are getting this issue in moon logs.
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: starting new session
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: creating config map
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: config map created
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: creating pod
2022/06/07 04:25:37 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: pod created
2022/06/07 04:25:37 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: waiting pod
2022/06/07 04:25:52 moon-649646cd49-5hqnc: license controller: license moon: update status:  License.moon.aerokube.com "moon" is invalid: status: Invalid value: "null": status in body must be of type object: "null"
2022/06/07 04:26:01 moon-649646cd49-rp9wc: license controller: license moon: update status:  License.moon.aerokube.com "moon" is invalid: status: Invalid value: "null": status in body must be of type object: "null"
W0607 04:28:35.878388       1 reflector.go:442] pkg/mod/k8s.io/client-go@v0.23.3/tools/cache/reflector.go:167: watch of *v1.Pod ended with: an error on the server ("unable to decode an event from the watch stream: context canceled") has prevented the request from succeeding
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: client disconnected while waited for resources
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: deleting pod
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: pod deleted
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: deleting config map
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon: chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: config map deleted

@ramveluru this should be related to some unexpected Kubernetes cluster restart by cluster administrator.

Looks like there was something with kubernetes itself, may be api-server
restarted or oom killed, please check it.
вт, 7 июн. 2022 г., 07:29 ramveluru @.***>:

Hello,
we are trying to deploy moon solution in Kubernetes. we are getting this
issue in moon logs.
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: starting new
session
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: creating
config map
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: config map
created
2022/06/07 04:25:36 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: creating pod
2022/06/07 04:25:37 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: pod created
2022/06/07 04:25:37 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: waiting pod
2022/06/07 04:25:52 moon-649646cd49-5hqnc: license controller: license
moon: update status: License.moon.aerokube.com "moon" is invalid: status:
Invalid value: "null": status in body must be of type object: "null"
2022/06/07 04:26:01 moon-649646cd49-rp9wc: license controller: license
moon: update status: License.moon.aerokube.com "moon" is invalid: status:
Invalid value: "null": status in body must be of type object: "null"
W0607 04:28:35.878388 1 reflector.go:442] pkg/mod/
@.***/tools/cache/reflector.go:167: watch of *v1.Pod
ended with: an error on the server ("unable to decode an event from the
watch stream: context canceled") has prevented the request from succeeding
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: client
disconnected while waited for resources
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: deleting pod
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: pod deleted
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: deleting
config map
2022/06/07 04:28:35 moon-649646cd49-rp9wc: moon:
chrome-101-0-4951-64-1-674ae7e7-d570-42ac-9f32-cd950424bbac: config map
deleted
—
Reply to this email directly, view it on GitHub
https://github.com/aerokube/moon/issues/329, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKY23POLQR7IBUFOSXM7VTVN3F2NANCNFSM5YBP6EOQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Same issue with moon2 and eks.

@aandryashin which version should I use for moon deployments? Now my version is 1.23.

Known to work in 1.21. Looks like the issue is wrong value, please check it.
чт, 12 янв. 2023 г., 15:53 Gleb @.***>:

@aandryashin https://github.com/aandryashin which version should I use
for moon deployments? Now my version is 1.23.
—
Reply to this email directly, view it on GitHub
https://github.com/aerokube/moon/issues/329#issuecomment-1380293732, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKY23NP2MDZS64YIRQBGPLWR75DNANCNFSM5YBP6EOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is not a moon issue. Im so sorry.
Solution: do not forget to change your AWS Load balancer idle timeout. Default is 60 sec.


Update sql-data-warehouse-get-started-provision-powershell.md

Update link to Azure PowerShell module installer.

Hi @sonyam, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (sonyama). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

#Sign-Off


Improve Slack Updater

Improves the slack updater by properly formatting the results to make them readable, and sends the exact failed tests into the thread so that we won't hit a character limit, as slack's is 3k per message with their current api setup.
An example looks like the following for one section (there are only 2 on single GPU, but 3 on multi-gpu):

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Dataset source?

Outstanding job! I just can't seem to find the link to the dataset in the cited paper

Sorry, I forget to include the data preparing script. I will update the repo these days.

@FlyToYourMooN I have updated the repo with data preparation instructions.
I will close this issue now. Feel free to open it again if there is still something wrong.
Thanks~