Snapshot only generates screenshots with english localization

New Issue Checklist

[x] Updated fastlane to the latest version
[x] have read the Contribution Guidelines

Issue Description
The topic basically describes the issue. The screenshots folder contains the folders en-US and de-DE. The screenshots in the de-DE folder have english localization, though. There don't seem to be an issue in the console when I run snapshot. I have both storyboard localization and a Localizable.strings file(s). What did I miss? Thanks for your help!
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

✅ output when running snapshot ✅
$ snapshot
[16:17:30]: Successfully loaded '/Users/nandersen/Documents/Swift/lactase3/fastlane/Snapfile' 📄
+----------------------------+------------------------------------------------------------------------------------------+
|                                      Detected Values from './fastlane/Snapfile'                                       |
+----------------------------+------------------------------------------------------------------------------------------+
| devices                    | ["iPhone 6", "iPhone 6 Plus", "iPhone 5", "iPad Pro (12.9 inch)", "iPad Pro (9.7 inch)"] |
| languages                  | ["en-US", "de-DE"]                                                                       |
| scheme                     | Lactase3                                                                                |
| output_directory           | ./screenshots                                                                            |
| clear_previous_screenshots | true                                                                                |
+----------------------------+------------------------------------------------------------------------------------------+
[16:17:30]: Successfully loaded '/Users/nandersen/Documents/Swift/lactase3/fastlane/Snapfile' 📄
[16:17:30]: No values defined in './fastlane/Snapfile'
[16:17:30]: $ xcodebuild -list -workspace ./Lactase3.xcworkspace
+----------------------------+---------------------------------------------------------------------+
|                                   Summary for snapshot 1.16.3                                    |
+----------------------------+---------------------------------------------------------------------+
| devices                    | ["iPhone 6", "iPhone 6 Plus", "iPhone 5", "iPad Pro (12.9 inch)"... |
| languages                  | ["en-US", "de-DE"]                                                  |
| scheme                     | Lactase3                                                            |
| output_directory           | /Users/nandersen/Documents/Swift/lactase3/screenshots               |
| clear_previous_screenshots | true                                                                |
| workspace                  | ./Lactase3.xcworkspace                                              |
| launch_arguments           | [""]                                                                |
| skip_open_summary          | false                                                               |
| reinstall_app              | false                                                               |
| erase_simulator            | false                                                               |
| localize_simulator         | false                                                               |
| app_identifier             | com.nikolajandersen.lactase3                                        |
| buildlog_path              | ~/Library/Logs/snapshot                                             |
| clean                      | false                                                               |
| number_of_retries          | 1                                                                   |
| stop_after_first_error     | false                                                               |
| xcode_path                 | /Applications/Xcode.app                                             |
+----------------------------+---------------------------------------------------------------------+
[16:17:32]: Clearing previously generated screenshots
[16:17:32]: Building and running project - this might take some time...
[16:17:32]: snapshot run 1 of 10
[16:17:32]: Patching '/Users/nandersen/Library/Preferences/com.apple.iphonesimulator.plist' to scale simulator to 100%
[16:17:34]: $ xcodebuild clean -showBuildSettings -workspace ./Lactase3.xcworkspace -scheme Lactase3
[16:17:35]: ------------------------
[16:17:35]: --- iPhone 6 - en-US ---
[16:17:35]: ------------------------
[16:17:35]: $ set -o pipefail && xcodebuild -workspace ./Lactase3.xcworkspace -scheme Lactase3 -derivedDataPath '/var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie' -destination 'platform=iOS Simulator,id=1F301651-323E-4CE4-8837-AAE366508153,OS=10.1' FASTLANE_SNAPSHOT=YES build test | tee /Users/nandersen/Library/Logs/snapshot/Lactase3-Lactase3.log | xcpretty
[16:17:35]: ▸ Loading...
[16:17:37]: ▸ Building Pods/Font-Awesome-Swift-Font-Awesome-Swift [Debug]
[16:17:37]: ▸ Check Dependencies
[16:17:37]: ▸ Processing ResourceBundle-Font-Awesome-Swift-Info.plist
[16:17:37]: ▸ Copying Font-Awesome-Swift/Source/FontAwesome.ttf
[16:17:37]: Running Tests: ▸ Touching Font-Awesome-Swift.bundle
[16:17:37]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Font-Awesome-Swift/Font-Awesome-Swift.bundle
[16:17:37]: ▸ Building Pods/SCLAlertView [Debug]
[16:17:37]: ▸ Check Dependencies
[16:17:37]: ▸ Processing Info.plist
[16:17:37]: ▸ Compiling SCLAlertView.swift
[16:17:41]: ▸ Compiling SCLExtensions.swift
[16:17:48]: ▸ Compiling SCLAlertView-dummy.m
[16:17:50]: ▸ Compiling SCLAlertView_vers.c
[16:17:53]: ▸ Linking SCLAlertView
[16:17:56]: ▸ Copying SCLAlertView-umbrella.h
[16:18:03]: Running Tests: ▸ Touching SCLAlertView.framework
[16:18:05]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/SCLAlertView/SCLAlertView.framework
[16:18:05]: ▸ Building Pods/Realm [Debug]
[16:18:05]: ▸ Check Dependencies
[16:18:05]: ▸ Processing Info.plist
[16:18:05]: ▸ Compiling collection_notifications.cpp
[16:18:05]: ▸ Compiling collection_change_builder.cpp
[16:18:05]: ▸ Compiling collection_notifier.cpp
[16:18:05]: ▸ Compiling external_commit_helper.cpp
[16:18:05]: ▸ Compiling format.cpp
[16:18:05]: ▸ Compiling handover.cpp
[16:18:05]: ▸ Compiling index_set.cpp
[16:18:05]: ▸ Compiling keychain_helper.cpp
[16:18:05]: ▸ Compiling list.cpp
[16:18:05]: ▸ Compiling list_notifier.cpp
[16:18:05]: ▸ Compiling object_schema.cpp
[16:18:05]: ▸ Compiling object_store.cpp
[16:18:05]: ▸ Compiling placeholder.cpp
[16:18:05]: ▸ Compiling Realm-dummy.m
[16:18:05]: ▸ Compiling realm_coordinator.cpp
[16:18:05]: ▸ Compiling results.cpp
[16:18:05]: ▸ Compiling results_notifier.cpp
[16:18:05]: ▸ Compiling RLMAccessor.mm
[16:18:05]: ▸ Compiling RLMAnalytics.mm
[16:18:05]: ▸ Compiling RLMArray.mm
[16:18:05]: ▸ Compiling RLMArrayLinkView.mm
[16:18:05]: ▸ Compiling RLMAuthResponseModel.m
[16:18:05]: ▸ Compiling RLMClassInfo.mm
[16:18:05]: ▸ Compiling RLMCollection.mm
[16:18:05]: ▸ Compiling RLMConstants.m
[16:18:05]: ▸ Compiling RLMListBase.mm
[16:18:05]: ▸ Compiling RLMMigration.mm
[16:18:05]: ▸ Compiling RLMNetworkClient.m
[16:18:05]: ▸ Compiling RLMObject.mm
[16:18:05]: ▸ Compiling RLMObjectBase.mm
[16:18:05]: ▸ Compiling RLMObjectSchema.mm
[16:18:05]: ▸ Compiling RLMObjectStore.mm
[16:18:05]: ▸ Compiling RLMObservation.mm
[16:18:05]: ▸ Compiling RLMOptionalBase.mm
[16:18:05]: ▸ Compiling RLMPredicateUtil.mm
[16:18:05]: ▸ Compiling RLMProperty.mm
[16:18:05]: ▸ Compiling RLMQueryUtil.mm
[16:18:05]: ▸ Compiling RLMRealm.mm
[16:18:05]: ▸ Compiling RLMRealmConfiguration+Sync.mm
[16:18:05]: ▸ Compiling RLMRealmConfiguration.mm
[16:18:05]: ▸ Compiling RLMRealmUtil.mm
[16:18:05]: ▸ Compiling RLMResults.mm
[16:18:05]: ▸ Compiling RLMSchema.mm
[16:18:05]: ▸ Compiling RLMSwiftSupport.m
[16:18:05]: ▸ Compiling RLMSyncConfiguration.mm
[16:18:05]: ▸ Compiling RLMSyncCredential.m
[16:18:05]: ▸ Compiling RLMSyncFileManager.mm
[16:18:05]: ▸ Compiling RLMSyncManager.mm
[16:18:05]: ▸ Compiling RLMSyncSession.mm
[16:18:05]: ▸ Compiling RLMSyncSessionHandle.mm
[16:18:05]: ▸ Compiling RLMSyncUser.mm
[16:18:05]: ▸ Compiling RLMSyncUtil.mm
[16:18:05]: ▸ Compiling RLMTokenModels.m
[16:18:05]: ▸ Compiling RLMUpdateChecker.mm
[16:18:05]: ▸ Compiling RLMUtil.mm
[16:18:05]: ▸ Compiling schema.cpp
[16:18:05]: ▸ Compiling shared_realm.cpp
[16:18:06]: ▸ Compiling sync_manager.cpp
[16:18:06]: ▸ Compiling sync_metadata.cpp
[16:18:06]: ▸ Compiling sync_session.cpp
[16:18:06]: ▸ ⚠  /Users/nandersen/Documents/Swift/lactase3/Pods/Realm/Realm/ObjectStore/src/sync_session.cpp:293:17: enumeration values 'invalid_error' and 'disabled_session' not handled in switch [-Wswitch]
[16:18:06]: ▸ switch (strong_code) {
[16:18:06]: ▸                 ^
[16:18:06]: ▸ Compiling thread_confined.cpp
[16:18:06]: ▸ Compiling transact_log_handler.cpp
[16:18:07]: ▸ Compiling weak_realm_notifier.cpp
[16:18:07]: ▸ Compiling Realm_vers.c
[16:18:07]: ▸ Linking Realm
[16:18:08]: ▸ Copying Realm/include/RLMAccessor.h
[16:18:08]: ▸ Copying Realm/include/RLMArray_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMListBase.h
[16:18:08]: ▸ Copying Realm/include/RLMMigration_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMObjectSchema_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMObject_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMObjectStore.h
[16:18:08]: ▸ Copying Realm/include/RLMOptionalBase.h
[16:18:08]: ▸ Copying Realm/include/RLMRealm_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMProperty_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMRealmConfiguration_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMResults_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMSchema_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncConfiguration_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncSession_Private.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncUtil_Private.h
[16:18:08]: ▸ Copying Realm/include/Realm.h
[16:18:08]: ▸ Copying Realm/include/RLMArray.h
[16:18:08]: ▸ Copying Realm/include/RLMCollection.h
[16:18:08]: ▸ Copying Realm/include/RLMConstants.h
[16:18:08]: ▸ Copying Realm/include/RLMListBase.h
[16:18:08]: ▸ Copying Realm/include/RLMObject.h
[16:18:08]: ▸ Copying Realm/include/RLMMigration.h
[16:18:08]: ▸ Copying Realm/include/RLMObjectBase.h
[16:18:08]: ▸ Copying Realm/include/RLMObjectBase_Dynamic.h
[16:18:08]: ▸ Copying Realm/include/RLMOptionalBase.h
[16:18:08]: ▸ Copying Realm/include/RLMObjectSchema.h
[16:18:08]: ▸ Copying Realm/include/RLMPlatform.h
[16:18:08]: ▸ Copying Realm/include/RLMProperty.h
[16:18:08]: ▸ Copying Realm/include/RLMRealm.h
[16:18:08]: ▸ Copying Realm/include/RLMRealm_Dynamic.h
[16:18:08]: ▸ Copying Realm/include/RLMRealmConfiguration+Sync.h
[16:18:08]: ▸ Copying Realm/include/RLMRealmConfiguration.h
[16:18:08]: ▸ Copying Realm/include/RLMResults.h
[16:18:08]: ▸ Copying Realm/include/RLMSchema.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncConfiguration.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncCredential.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncManager.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncSession.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncUtil.h
[16:18:08]: ▸ Copying Realm/include/RLMSyncUser.h
[16:18:08]: Running Tests: ▸ Touching Realm.framework
[16:18:08]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Realm/Realm.framework
[16:18:08]: ▸ Building Pods/Font-Awesome-Swift [Debug]
[16:18:08]: ▸ Check Dependencies
[16:18:08]: ▸ Processing Info.plist
[16:18:08]: ▸ Compiling FAIcon.swift
[16:18:08]: ▸ Compiling Font-Awesome-Swift-dummy.m
[16:18:08]: ▸ Compiling Font_Awesome_Swift_vers.c
[16:18:08]: ▸ Linking Font_Awesome_Swift
[16:18:08]: ▸ Copying /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Font-Awesome-Swift/Font-Awesome-Swift.bundle
[16:18:08]: ▸ Copying Font-Awesome-Swift-umbrella.h
[16:18:08]: Running Tests: ▸ Touching Font_Awesome_Swift.framework
[16:18:08]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Font-Awesome-Swift/Font_Awesome_Swift.framework
[16:18:08]: ▸ Building Pods/RealmSwift [Debug]
[16:18:08]: ▸ Check Dependencies
[16:18:08]: ▸ Processing Info.plist
[16:18:11]: ▸ Compiling RealmSwift-dummy.m
[16:18:11]: ▸ Compiling RealmSwift_vers.c
[16:18:11]: ▸ Linking RealmSwift
[16:18:11]: ▸ Copying RealmSwift-umbrella.h
[16:18:11]: Running Tests: ▸ Touching RealmSwift.framework
[16:18:11]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/RealmSwift/RealmSwift.framework
[16:18:11]: ▸ Building Pods/Pods-Lactase3 [Debug]
[16:18:11]: ▸ Check Dependencies
[16:18:11]: ▸ Processing Info.plist
[16:18:11]: ▸ Compiling Pods-Lactase3-dummy.m
[16:18:12]: ▸ Compiling Pods_Lactase3_vers.c
[16:18:12]: ▸ Copying Pods-Lactase3-umbrella.h
[16:18:12]: Running Tests: ▸ Touching Pods_Lactase3.framework
[16:18:12]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Pods_Lactase3.framework
[16:18:12]: ▸ Building Lactase3/Lactase3 [Debug]
[16:18:12]: ▸ Check Dependencies
[16:18:12]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:18:12]: ▸ Compiling AlertService.swift
[16:18:14]: ▸ Compiling GramService.swift
[16:18:14]: ▸ Compiling PersonsTableViewController.swift
[16:18:14]: ▸ Compiling LunchesTableViewController.swift
[16:18:14]: ▸ Compiling Lunch.swift
[16:18:14]: ▸ Compiling User.swift
[16:18:14]: ▸ Compiling PlistReader.swift
[16:18:14]: ▸ Compiling Extensions.swift
[16:18:14]: ▸ Compiling LunchDetailViewController.swift
[16:18:14]: ▸ Compiling PlistConverter.swift
[16:18:14]: ▸ Compiling AppDelegate.swift
[16:18:14]: ▸ Compiling SettingsTableViewController.swift
[16:18:15]: ▸ Linking Lactase3
[16:18:15]: ▸ ⚠  ld: object file (/var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Pods_Lactase3.framework/Pods_Lactase3(Pods-Lactase3-dummy.o)) was built for newer iOS version (10.0) than being linked (9.3)
[16:18:15]: ▸ ⚠  ld: object file (/var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Pods_Lactase3.framework/Pods_Lactase3(Pods_Lactase3_vers.o)) was built for newer iOS version (10.0) than being linked (9.3)
[16:18:15]: ▸ Copying Localizable.strings
[16:18:15]: ▸ Copying Localizable.strings
[16:18:15]: ▸ Copying Localizable.strings
[16:18:15]: ▸ Copying en.plist
[16:18:15]: ▸ Copying de.plist
[16:18:15]: ▸ Copying da.plist
[16:18:15]: ▸ Compiling LaunchScreen.storyboard
[16:18:17]: ▸ Compiling Main.storyboard
[16:18:18]: ▸ Processing Info.plist
[16:18:18]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:18:19]: ▸ Running script '[CP] Copy Pods Resources'
[16:18:19]: ▸ Running script 'Run Script'
[16:18:19]: ▸ DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Lactase3.app.dSYM at path /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app.dSYM
[16:18:20]: Running Tests: ▸ Touching Lactase3.app
[16:18:20]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app
[16:18:20]: ▸ Build Succeeded
[16:18:20]: ▸ 2016-11-19 16:18:20.967 xcodebuild[52286:10541809] [MT] IDETestOperationsObserverDebug: (8AE8364C-55DC-4C0A-9418-0A3F1813F787) Beginning test session Lactase3UITests-8AE8364C-55DC-4C0A-9418-0A3F1813F787 at 2016-11-19 16:18:20.964 with Xcode 8B62 on target <DVTiPhoneSimulator: 0x7fb48ad0b770> {
[16:18:20]: ▸ SimDevice: SimDevice : iPhone 6 (1F301651-323E-4CE4-8837-AAE366508153) : state={ Shutdown } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 10.1 (14B72) - com.apple.CoreSimulator.SimRuntime.iOS-10-1 }
[16:18:20]: ▸ } (10.1 (14B72))
[16:18:20]: ▸ 2016-11-19 16:18:20.968 xcodebuild[52286:10541819]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[16:18:20]: ▸ /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Logs/Test/C2E57459-AB92-4ACC-9D53-0DE705D69B9D/Session-Lactase3UITests-2016-11-19_161820-mA7kgF.log
[16:18:21]: ▸ 2016-11-19 16:18:21.061 xcodebuild[52286:10541809] [MT] IDETestOperationsObserverDebug: (FB4D09D3-FF41-4F1B-9BAF-6D6B83D9FC32) Beginning test session Lactase3Tests-FB4D09D3-FF41-4F1B-9BAF-6D6B83D9FC32 at 2016-11-19 16:18:21.061 with Xcode 8B62 on target <DVTiPhoneSimulator: 0x7fb48ad0b770> {
[16:18:21]: ▸ SimDevice: SimDevice : iPhone 6 (1F301651-323E-4CE4-8837-AAE366508153) : state={ Shutdown } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 10.1 (14B72) - com.apple.CoreSimulator.SimRuntime.iOS-10-1 }
[16:18:21]: ▸ } (10.1 (14B72))
[16:18:21]: ▸ 2016-11-19 16:18:21.061 xcodebuild[52286:10541817]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[16:18:21]: ▸ /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Logs/Test/C2E57459-AB92-4ACC-9D53-0DE705D69B9D/Session-Lactase3Tests-2016-11-19_161821-982g6W.log
[16:18:21]: ▸ Building Pods/Font-Awesome-Swift-Font-Awesome-Swift [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Pods/SCLAlertView [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Pods/Pods-Lactase3Tests [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Processing Info.plist
[16:18:21]: ▸ Compiling Pods-Lactase3Tests-dummy.m
[16:18:21]: ▸ Compiling Pods_Lactase3Tests_vers.c
[16:18:21]: ▸ Copying Pods-Lactase3Tests-umbrella.h
[16:18:21]: Running Tests: ▸ Touching Pods_Lactase3Tests.framework
[16:18:21]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Pods_Lactase3Tests.framework
[16:18:21]: ▸ Building Pods/Pods-Lactase3UITests [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Processing Info.plist
[16:18:21]: ▸ Compiling Pods-Lactase3UITests-dummy.m
[16:18:21]: ▸ Compiling Pods_Lactase3UITests_vers.c
[16:18:21]: ▸ Copying Pods-Lactase3UITests-umbrella.h
[16:18:21]: Running Tests: ▸ Touching Pods_Lactase3UITests.framework
[16:18:21]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Pods_Lactase3UITests.framework
[16:18:21]: ▸ Building Pods/Realm [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Pods/Font-Awesome-Swift [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Pods/RealmSwift [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Pods/Pods-Lactase3 [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Building Lactase3/Lactase3 [Debug]
[16:18:21]: ▸ Check Dependencies
[16:18:21]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:18:21]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:18:22]: ▸ Running script '[CP] Copy Pods Resources'
[16:18:22]: ▸ Running script 'Run Script'
[16:18:22]: ▸ DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Lactase3.app.dSYM at path /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app.dSYM
[16:18:22]: ▸ Building Lactase3/Lactase3Tests [Debug]
[16:18:22]: ▸ Check Dependencies
[16:18:22]: ▸ Processing Info.plist
[16:18:22]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:18:22]: ▸ Compiling Lactase3Tests.swift
[16:18:25]: ▸ Linking Lactase3Tests
[16:18:26]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:18:26]: ▸ Running script '[CP] Copy Pods Resources'
[16:18:27]: Running Tests: ▸ Touching Lactase3Tests.xctest
[16:18:27]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app/PlugIns/Lactase3Tests.xctest
[16:18:28]: ▸ Building Lactase3/Lactase3UITests [Debug]
[16:18:28]: ▸ Check Dependencies
[16:18:28]: ▸ Processing Info.plist
[16:18:28]: ▸ Preprocessing /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Agents/XCTRunner.app/Info.plist
[16:18:28]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:18:28]: ▸ Compiling Lactase3UITests.swift
[16:18:28]: ▸ Compiling SnapshotHelper.swift
[16:18:28]: ▸ Compiling Lactase3Screenshots.swift
[16:18:28]: ▸ Linking Lactase3UITests
[16:18:28]: ▸ Running script '[CP] Copy Pods Resources'
[16:18:28]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:18:28]: Running Tests: ▸ Touching Lactase3UITests.xctest
[16:18:28]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3UITests-Runner.app/PlugIns/Lactase3UITests.xctest
[16:19:12]: ▸ Test Succeeded
[16:19:12]: ▸ All tests
[16:19:12]: ▸ Test Suite Lactase3UITests.xctest started
[16:19:12]: ▸ Lactase3UITests
[16:19:12]: ▸ ✓ testExample (22.813 seconds)
[16:19:12]: ▸ 	 Executed 1 test, with 0 failures (0 unexpected) in 22.813 (22.816) seconds
[16:19:12]: ▸
[16:19:12]: ▸ All tests
[16:19:12]: ▸ Test Suite Lactase3Tests.xctest started
[16:19:12]: ▸ Lactase3Tests
[16:19:12]: ▸ ✓ testExample (0.003 seconds)
[16:19:12]: ▸ ◷ testPerformanceExample measured (0.000 seconds)
[16:19:12]: ▸ ✓ testPerformanceExample (0.446 seconds)
[16:19:12]: ▸ 	 Executed 2 tests, with 0 failures (0 unexpected) in 0.450 (0.455) seconds
[16:19:12]: ▸
[16:19:12]: Collecting screenshots...
[16:19:12]: Found 3 screenshots...
[16:19:12]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/en-US/iPhone6-LunchesTable.png'...
[16:19:12]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/en-US/iPhone6-NewLunch.png'...
[16:19:12]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/en-US/iPhone6-Settings.png'...
[16:19:12]: snapshot run 2 of 10
[16:19:12]: Patching '/Users/nandersen/Library/Preferences/com.apple.iphonesimulator.plist' to scale simulator to 100%
[16:19:15]: ------------------------
[16:19:15]: --- iPhone 6 - de-DE ---
[16:19:15]: ------------------------
[16:19:15]: $ set -o pipefail && xcodebuild -workspace ./Lactase3.xcworkspace -scheme Lactase3 -derivedDataPath '/var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie' -destination 'platform=iOS Simulator,id=1F301651-323E-4CE4-8837-AAE366508153,OS=10.1' FASTLANE_SNAPSHOT=YES build test | tee /Users/nandersen/Library/Logs/snapshot/Lactase3-Lactase3.log | xcpretty
[16:19:15]: ▸ Loading...
[16:19:17]: ▸ Building Pods/Realm [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Pods/Font-Awesome-Swift-Font-Awesome-Swift [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Pods/SCLAlertView [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Pods/Font-Awesome-Swift [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Pods/RealmSwift [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Pods/Pods-Lactase3 [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Building Lactase3/Lactase3 [Debug]
[16:19:17]: ▸ Check Dependencies
[16:19:17]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:19:17]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:19:18]: ▸ Running script '[CP] Copy Pods Resources'
[16:19:18]: ▸ Running script 'Run Script'
[16:19:18]: ▸ DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Lactase3.app.dSYM at path /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app.dSYM
[16:19:18]: ▸ Build Succeeded
[16:19:18]: ▸ 2016-11-19 16:19:18.430 xcodebuild[53131:10547053] [MT] IDETestOperationsObserverDebug: (C07B5545-C95F-481C-832E-ECECD67C78FE) Beginning test session Lactase3UITests-C07B5545-C95F-481C-832E-ECECD67C78FE at 2016-11-19 16:19:18.429 with Xcode 8B62 on target <DVTiPhoneSimulator: 0x7f9e288d5390> {
[16:19:18]: ▸ SimDevice: SimDevice : iPhone 6 (1F301651-323E-4CE4-8837-AAE366508153) : state={ Shutting Down } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 10.1 (14B72) - com.apple.CoreSimulator.SimRuntime.iOS-10-1 }
[16:19:18]: ▸ } (10.1 (14B72))
[16:19:18]: ▸ 2016-11-19 16:19:18.430 xcodebuild[53131:10547055]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[16:19:18]: ▸ /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Logs/Test/C97431C8-0CAF-49FD-95B9-9D082EE5A620/Session-Lactase3UITests-2016-11-19_161918-O8b1Am.log
[16:19:18]: ▸ 2016-11-19 16:19:18.463 xcodebuild[53131:10547053] [MT] IDETestOperationsObserverDebug: (0C794CA3-E110-4C72-8065-81DFC49089F9) Beginning test session Lactase3Tests-0C794CA3-E110-4C72-8065-81DFC49089F9 at 2016-11-19 16:19:18.462 with Xcode 8B62 on target <DVTiPhoneSimulator: 0x7f9e288d5390> {
[16:19:18]: ▸ SimDevice: SimDevice : iPhone 6 (1F301651-323E-4CE4-8837-AAE366508153) : state={ Shutting Down } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPhone-6 } runtime={ SimRuntime : 10.1 (14B72) - com.apple.CoreSimulator.SimRuntime.iOS-10-1 }
[16:19:18]: ▸ } (10.1 (14B72))
[16:19:18]: ▸ 2016-11-19 16:19:18.463 xcodebuild[53131:10547056]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[16:19:18]: ▸ /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Logs/Test/C97431C8-0CAF-49FD-95B9-9D082EE5A620/Session-Lactase3Tests-2016-11-19_161918-T6lT5z.log
[16:19:18]: ▸ Building Pods/SCLAlertView [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Pods-Lactase3UITests [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Pods-Lactase3Tests [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Realm [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Font-Awesome-Swift-Font-Awesome-Swift [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Font-Awesome-Swift [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/RealmSwift [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Pods/Pods-Lactase3 [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Building Lactase3/Lactase3 [Debug]
[16:19:18]: ▸ Check Dependencies
[16:19:18]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:19:18]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:19:19]: ▸ Running script '[CP] Copy Pods Resources'
[16:19:19]: ▸ Running script 'Run Script'
[16:19:19]: ▸ DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Lactase3.app.dSYM at path /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app.dSYM
[16:19:19]: ▸ Building Lactase3/Lactase3UITests [Debug]
[16:19:19]: ▸ Check Dependencies
[16:19:19]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:19:19]: ▸ Running script '[CP] Copy Pods Resources'
[16:19:19]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:19:19]: ▸ Building Lactase3/Lactase3Tests [Debug]
[16:19:19]: ▸ Check Dependencies
[16:19:19]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:19:19]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:19:19]: ▸ Running script '[CP] Copy Pods Resources'
[16:20:09]: ▸ Test Succeeded
[16:20:09]: ▸ All tests
[16:20:09]: ▸ Test Suite Lactase3UITests.xctest started
[16:20:09]: ▸ Lactase3UITests
[16:20:09]: ▸ ✓ testExample (21.759 seconds)
[16:20:09]: ▸ 	 Executed 1 test, with 0 failures (0 unexpected) in 21.759 (21.762) seconds
[16:20:09]: ▸
[16:20:09]: ▸ All tests
[16:20:09]: ▸ Test Suite Lactase3Tests.xctest started
[16:20:09]: ▸ Lactase3Tests
[16:20:09]: ▸ ✓ testExample (0.001 seconds)
[16:20:09]: ▸ ◷ testPerformanceExample measured (0.000 seconds)
[16:20:09]: ▸ ✓ testPerformanceExample (0.521 seconds)
[16:20:09]: ▸ 	 Executed 2 tests, with 0 failures (0 unexpected) in 0.522 (0.526) seconds
[16:20:09]: ▸
[16:20:09]: Collecting screenshots...
[16:20:09]: Found 3 screenshots...
[16:20:09]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/de-DE/iPhone6-LunchesTable.png'...
[16:20:09]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/de-DE/iPhone6-NewLunch.png'...
[16:20:09]: Copying '/Users/nandersen/Documents/Swift/lactase3/screenshots/de-DE/iPhone6-Settings.png'...
[16:20:09]: snapshot run 3 of 10
[16:20:09]: Patching '/Users/nandersen/Library/Preferences/com.apple.iphonesimulator.plist' to scale simulator to 100%
[16:20:12]: -----------------------------
[16:20:12]: --- iPhone 6 Plus - en-US ---
[16:20:12]: -----------------------------
[16:20:12]: $ set -o pipefail && xcodebuild -workspace ./Lactase3.xcworkspace -scheme Lactase3 -derivedDataPath '/var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie' -destination 'platform=iOS Simulator,id=00D74E0F-D316-4733-9151-0E62B5012E31,OS=10.1' FASTLANE_SNAPSHOT=YES build test | tee /Users/nandersen/Library/Logs/snapshot/Lactase3-Lactase3.log | xcpretty
[16:20:12]: ▸ Loading...
[16:20:13]: ▸ Building Pods/Realm [Debug]
[16:20:13]: ▸ Check Dependencies
[16:20:14]: ▸ Building Pods/SCLAlertView [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Building Pods/Font-Awesome-Swift-Font-Awesome-Swift [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Building Pods/Font-Awesome-Swift [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Building Pods/RealmSwift [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Building Pods/Pods-Lactase3 [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Building Lactase3/Lactase3 [Debug]
[16:20:14]: ▸ Check Dependencies
[16:20:14]: ▸ Running script '[CP] Check Pods Manifest.lock'
[16:20:14]: ▸ Processing Info.plist
[16:20:14]: ▸ Running script '[CP] Embed Pods Frameworks'
[16:20:14]: ▸ Running script '[CP] Copy Pods Resources'
[16:20:14]: ▸ Running script 'Run Script'
[16:20:14]: ▸ DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process Lactase3.app.dSYM at path /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app.dSYM
[16:20:15]: ▸ Signing /var/folders/wn/p7_f1kdx4770l4x04fgkbyxw0000gp/T/snapshot_derived20161119-52208-fimrie/Build/Products/Debug-iphonesimulator/Lactase3.app
^C^C
Cancelled... use --verbose to show the stack trace

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.1

Ruby
2.3.1

Bundler?
false

Git
git version 2.6.3

Installation Source
/Users/nandersen/.rbenv/versions/2.3.1/bin/fastlane

Host
Mac OS X 10.12.1 (16B2555)

Ruby Lib Dir
/Users/nandersen/.rbenv/versions/2.3.1/lib

OpenSSL Version
OpenSSL 1.0.2h  3 May 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.1

System Locale

Variable
Value

LANG
de_DE.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "1.109.0"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    cocoapods

  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: "Lactase") # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    gym(scheme: "Lactase") # Build your app - more options available
    deliver(force: true)
    # frameit
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "com.nikolajandersen.lactase3" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "NZ2298R6XY"  # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

credentials_manager
0.16.2
✅ Up-To-Date

spaceship
0.37.0
✅ Up-To-Date

fastlane_core
0.56.0
✅ Up-To-Date

deliver
1.15.1
✅ Up-To-Date

snapshot
1.16.3
✅ Up-To-Date

frameit
3.0.0
✅ Up-To-Date

pem
1.4.0
✅ Up-To-Date

cert
1.4.4
✅ Up-To-Date

sigh
1.11.2
✅ Up-To-Date

produce
1.3.0
✅ Up-To-Date

gym
1.12.0
✅ Up-To-Date

pilot
1.12.1
✅ Up-To-Date

scan
0.14.1
✅ Up-To-Date

supply
0.7.1
✅ Up-To-Date

match
0.11.0
✅ Up-To-Date

screengrab
0.5.6
✅ Up-To-Date

fastlane
1.110.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

highline
1.7.8

commander
4.4.0

terminal-table
1.4.5

json
1.8.3

multipart-post
2.0.0

faraday
0.10.0

faraday_middleware
0.10.1

dotenv
2.1.1

net-ssh
3.2.0

net-sftp
2.1.2

plist
3.2.0

rubyzip
1.1.7

security
0.1.3

krausefx-shenzhen
0.14.11

slack-notifier
1.5.1

i18n
0.7.0

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.8.3

activesupport
4.2.7

colored
1.2

claide
1.0.0

xcodeproj
1.2.0

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

public_suffix
2.0.4

addressable
2.5.0

credentials_manager
0.16.2

multi_xml
0.5.5

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161021

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
1.6.8

xcode-install
2.0.9

word_wrap
1.0.0

multi_json
1.12.1

babosa
1.0.2

excon
0.54.0

gh_inspector
1.0.2

fastlane_core
0.56.0

bundler
1.12.5

mini_magick
4.5.1

xcpretty-travis-formatter
0.0.4

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
<IP_ADDRESS>

google-api-client
0.9.20

io-console
0.4.5

generated on: 2016-11-19

Have you tried setting snapshot's localize_simulator option to true?

Thanks for you quick help @milch, that was it. I've overlooked this option when I looked through snapshot's help in the terminal.
If I'm not mistaken, the default generated snapfile has already set some to-translate locales. This made me think that the screenshot localization is activated per default.

@andersennl Thanks for following up. Localize simulator was implemented after the ability to localize the apps content based on your settings. This is why they are separate.


It's possible to change color and fontSize of the placeholder?

Hello!
I'm trying to change the default color of the placeholder to another color, but I don't have found on the options something explains how I can do that. 😢

Hi,
Could you check if you can change the color and fontSize of a normal TextInput?
Please, provide a code working with normal react-native text input and not working with masked text input, ok?
o/

I was able to resolve the problem with normal react-native properties! 😆
Thanks o/


Fix newline and single quotes escaping issues

This PR fixes an unintended behavior that results in a malformed script, with a newline on top of the shebang and with the messages not correctly being escaped.

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

2.2.1
GitHub release

Your semantic-release bot :package::rocket:


0.52 - CORS issue with JS Remote Debugging when using xip.io

Is this a bug report?
Yes.

Have you read the Contributing Guidelines?
Yes.
Environment
Environment:
OS: macOS High Sierra 10.13.2
Node: 9.4.0
Yarn: Not Found
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: ^16.2.0 => 16.2.0
react-native: ^0.52.0 => 0.52.0
Target Platform: iOS 8

Steps to Reproduce

Note: I upgraded to 0.52 last night using react-native-git-upgrade, it had been working previously on 0.51.

Run development app on real iOS device, which loads the JS bundle from http://<IP_ADDRESS>.xip.io:8081/index.delta?platform=ios&dev=true&minify=false
Enable JS Remote debug tools, which opens http://localhost:8081/debugger-ui/ in Chrome.
Bundle reloads and Chrome DevTools console displays the following error:

Failed to load http://<IP_ADDRESS>.xip.io:8081/index.delta?platform=ios&dev=true&minify=false: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8081' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Expected Behavior

App should load correctly and not throw an error when trying to debug JS remotely.
Actual Behavior

Failed to load http://<IP_ADDRESS>.xip.io:8081/index.delta?platform=ios&dev=true&minify=false: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8081' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Fresh react-native app using react-native init.

https://github.com/njbmartin/react-native-xip

It is possible to monkey patch if you can't wait for new release

Copy the contents of this file and paste it into node_modules/react-native/local-cli/server/middleware/getDevToolsMiddleware.js
Install patch-package by running yarn add --dev patch-package postinstall-prepare
Run yarn patch-package react-native, a file should be created in patches/react-native+0.52.patch, this file needs to be committed in your repository
Add the following script into your package.json and run yarn install, or you can run yarn patch-package directly if needed"scripts": {
  "prepare": "patch-package"
}

You can find more details on monkey patching in patch-package repo.

Same program here (react-native version 0.52.2), then I downgrade to 0.51.0, it still happened......
But finally I have found a way to solve this problem, maybe it can help you
And now react-native Version is 0.51.0,
react version is 16.0.0,
run on my iPhone X and Simulator, everything is OK.

Start remote JS Debugging in your device or your simulator;
2.Then open your Chrome, you will see a "React Native Debugger" page;
3.New a Tab, type chrome://apps/, then search "react developer tools", download and install it;
4.If react developer tools did not work, new a tab, type chrome://extensions/, and enter extensions manager;
5.Find React Developer Tools, enabled "Allow access to file URLs";
6.After finished above, go back to your iPhone or your Simulator, reload your RN App;

We face the same issue. Unsure how this is not a high priority candidate for a fix, I guess people don't need to debug their code on real devices?
We will downgrade to 0.51.0 to see if it fixes the issue. Will edit this post with an update.

@njbmartin sent a PR to fix this two weeks ago (thank you!), which was merged and released with 0.53.x.

After upgrading React Native to 0.53.0, the problem still exists. Please advise, thank you.

Remember to restart your packager and restart your browsers (or at least the debugger tab) after upgrading.

Upgrade 0.53.0 then watchman watch-del-all && react-native start --reset-cache. That will work for you guys.

If you are on 0.53.0 then change IP to localhost.

Thanks @akash-cp it worked!

I am using expo, when I updated for 0.53, I got a error:
react version mismatch between react-native 0.53.0 and native-scripts 0.52
package.json:
"expo": "^25.0.0"
"react": "16.2.0"
"react-native": "0.52.0"

+1

I am facing the same issue as @luanfelipecosta. I have the same package.json.
I tried running watchman watch-del-all && react-native start --reset-cache,but it did not fix it. I tried deleting the node_modules and re-installing the packages, that also doesn't fix the issue.
I think we should wait for this doc to get updated: https://github.com/react-community/create-react-native-app/blob/master/VERSIONS.md.

The latest version of expo uses<EMAIL_ADDRESS>and therefore any projects created using CRN might face this issue.
The fix I did was not hotfixed into 0.52 but is available in the latest<EMAIL_ADDRESS>As CRN is now the default method of creating React Native apps, either expo needs to be updated to use 0.53 or this fix needs to be hotfixed in 0.52.

@kanteankit
a workaround for this problem (who is using expo) is install a CORS Toggle in google chrome.
http://bit.ly/2o4mVNI
for me worked as a charm.

@njbmartin So what you are saying is we should wait for Expo to release a new version that supports<EMAIL_ADDRESS>

@njbmartin ah yes. You are right, I was using expo sdk 25 and ran into this issue.
@luanfelipecosta's suggestion works for me. Thanks man!

I'm still facing the same issue. I've tried all the possible solutions stated above but to no avail.
I have tried to upgrade RN to 0.53.3, yet it still gives the same problem.
Am on expo version 25.0.0.

Google Chrome plugin COORS Toggle as @luanfelipecosta suggested, works awesome ( http://bit.ly/2o4mVNI )

Upgrade react native to 0.53.3
watchman watch-del-all && react-native start --reset-cache
Start Remote JS Debugging
If the URL in Chrome is not http://localhost:8081/debugger-ui/, change it.

Upgraded to 0.53.3 and ran command watchman watch-del-all && react-native start --reset-cache.
Get this when launch in Debug mode...
debug-issue-google-photo

Been getting this since about the same time this Issue appeared (Jan 15). Any time I create a CRNA app and try to debug it with Chrome.  To get by, I would downgrade Expo and react native to previous versions: EXPO SDK to 24, React to 16.0.0, React Native to 0.51.x (matching the row shown for Expo SDK version 24.0.0. at https://github.com/react-community/create-react-native-app/blob/master/VERSIONS.md).  I hadn't created a new CRNA app for a few weeks until today. Tried it and got the same thing.  Came back here to see if there was any new news and saw the Google CORS Toggle suggestion from @luanfelipecosta. As others have reported, it works great. Hopefully this problem will get resolved before long, but until then, the CORS toggle is a quick and painless fix. Thanks  @luanfelipecosta!

CORS Toggle might work great, but they ask for the permission "Read and change all your data on the websites that you visit"

@dgrcode you can find the source of it here if you're worried; https://github.com/demesne/cors-toggle

<EMAIL_ADDRESS>removed the use of xip.io which should solves this issue without the need for all the hacks suggested above. You can read more about it in the commit 40a8434

Try to install CORS toggle extension, it helped me with similar problem

I updated to<EMAIL_ADDRESS>still have the same issue.

Looking the changelog, it should be fixed in the 54.0:
"Fix JS debugger issues related to CORS (29f8354)"

@alainib These warnings are intended and expected behavior

Using http://localhost:8081/debugger-ui/ instead of http://<IP_ADDRESS>:8081/debugger-ui/ worked for me.

Thanks @akash-cp it worked!

rayronvictor style solved my problem too.

disabling the CORS plugin in chrome made it work!

Just ... click on it (on the chrome plugins bar - right side) and disable the "Enable cross-origin resource  sharing".

The solution for this problem is simply install the extension "Allow-Control-Allow-Origin" in your chrome browser. this works for me you all can try.

@arfa123 You save my day! Thanks. The extension "Allow-Control-Allow-Origin" .
Just remember to disable it when not using because i cause trouble with some website.

If you also use Webstorm, you can do this.

like @rayronvictor Using http://localhost:8081/debugger-ui/ instead of http://<IP_ADDRESS>:8081/debugger-ui/ worked for me.

IDK why it's happening with 0.53. For now we can proceed with localhost instead of your machine IP address. http://localhost:8081/debugger-ui/

I'm having this issue with RN 0.55.4. Localhost or my machine's IP didn't work. The only thing that worked for me was disabling CORS via the chrome extension.

not work for me.

problem solved, it's work me. http://localhost:8081/debugger-ui/

Note that http://<IP_ADDRESS>:8081/debugger-ui/ specifically doesn't seem to work, for CORS reasons.

In my case it is solved by deleting in Application debug menu "Dev Stettings" -> "Debug server host & port for device" erase all ip and port. after that it works again. JS Debug Remotly.

Working with RN 0.55.4, Iphone 12.1.1, google chrome latest as of Dec, 2018.
I solved it by using my IP address instead of "localhost"
http://<IP_ADDRESS>:8081/debugger-ui/

Adding this Extension to Chrome solves this issue:
Allow CORS: Access-Control-Allow-origin


Extract calculator library

Calculator complexity is growing and growing. @frederikbosch do you think it would make sense to extract them to a separate library? Using calculators might make sense in other cases as well and our would be a good base for an abstract library.

True. It is growing. But actually is it only the rounding problem that is giving complexity. For me, I rather see Money as a library without any dependencies. Not even within the own organization. Embedding the code always leaves us with the possibility to add/remove a method when we need to within the scope of this library. No waiting for external libs that have created their own dependencies with their own BC issues.
If people want to use our calculators, they can grab the code, or ask to abstract them in another library.
What I do think is necessary is that we do some more abstractions regarding rounding. These blocks in the BcMath and Gmp calculator can be much cleaner. I'd say we focus on that.

Sounds reasonable. Is it a blocker for the release? It seems to me that it's mostly optimization, no API break is necessary.

Great! I think we can do optimization without BC break.


Verify transitive dependencies

Currently, relative packages are not installed through yarn / npm, but simply extracted. While in general that works great, it might cause issues if there are differences between the transitive dependencies of the local package, and the published one. It would be great to detect and fix that.

npm supports installing tarball, so we can run install here - https://github.com/mweststrate/relative-deps/blob/master/index.js#L150

Yeah, biggest problem is that it makes the process very slow. So for
development purposes it is not really suitable imho. But probably we could
do something smart, like install from tarball only if package.json changed
or something.
Op ma 15 jul. 2019 21:56 schreef Dmitrii Kanatnikov <
<EMAIL_ADDRESS>
npm supports installing tarball, so we can run install here -
https://github.com/mweststrate/relative-deps/blob/master/index.js#L150
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mweststrate/relative-deps/issues/6?email_source=notifications&email_token=AAN4NBB3323BAEWCKXMM7VLP7TI5NA5CNFSM4H2YU4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ6ZFRI#issuecomment-511546053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAN4NBC2IO3ESC6NK7EUA53P7TI5NANCNFSM4H2YU4GQ
.

So for development purposes it is not really suitable imho

Most often yes, but what if package has deps that cannot be deduped?
node_modules
  lodash@3
  relative-dep
    node_modules
      lodash@2

I don't know how often does this happen. I suppose that for UI lib it is not good to have deps (better to have peerDeps and devDeps for tests), but for server lib it is quite normal situation. Maybe I am wrong

I think this can be quite simply supported: on first install / changed
package.json do a normal npm install of the tarball. On incremental
installs, remove everything but the node_modules and update from the
tarball.
On Tue, Jul 16, 2019 at 11:28 AM Dmitrii Kanatnikov <
<EMAIL_ADDRESS>wrote:

So for development purposes it is not really suitable imho
Most often yes, but what if package has deps that cannot be deduped?
node_modules
lodash@3
relative-dep
node_modules
lodash@2
I don't know how often does this happen. I suppose that for UI lib it is
not good to have deps (better to have peerDeps and devDeps for tests), but
for server lib it is quite normal situation. Maybe I am wrong
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mweststrate/relative-deps/issues/6?email_source=notifications&email_token=AAN4NBENRBL5YSROX3ABUH3P7WIEPA5CNFSM4H2YU4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AIUAA#issuecomment-511740416,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAN4NBEPCNFJF525WOLLSI3P7WIEPANCNFSM4H2YU4GQ
.


Excel export

Maybe we should use http://docs.python-tablib.org/en/latest/? It supports export to all major spreadsheet formats without any third-party dependencies.

Yes, it is a good option. I'm an almost inactive tablib core commiter.
I didn't used it because it does not support generators, like the CSV export works.
For XLSX, it is not easy to do like a generator and tablib is a good fit, but other formats can work like export_csv.
I can fallback to tablib for formats not defined as export_xxx. I'll rewrite this pull request to use tablib.

Done. Export using tablib. Set the export_type and it'll just work for any tablib type.
I'm not sure if tablib must be a hard dependency.

I submitted a pull request to @iurisilvio's branch with some changes (and the ability to add multiple export_types): https://github.com/iurisilvio/flask-admin/pull/1
Great work! @iurisilvio

Thanks @pawl! I merged your PR and it is already here. You implemented my next steps. :+1:


chore(preset_env_base): Upgrade browserslist-rs to 0.13

Description:
Upgrade browserslist-rs, there was a major version change because wasm-pack functionality was split out into a feature:
https://github.com/browserslist/browserslist-rs/compare/v0.12.4...v0.13.0
BREAKING CHANGE:
Related issue (if exists):

As far as I can tell, the failing tests doesn't even build for wasm. So I have no idea why they fail

Then I'll fix them. swc_core one is about Wasm plugins and the swc_css_prefixer is about updating test references. (Browser data changed)

Thank you!


Catch TypeError thrown by Safari if invalid entryType passed

Closes #166

This change is

Codecov Report

Merging #167 into master will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #167      +/-   ##
==========================================
- Coverage    95.9%   95.79%   -0.11%
==========================================
  Files          30       30
  Lines         855      857       +2
  Branches      148      148
==========================================
+ Hits          820      821       +1
- Misses         35       36       +1

Impacted Files
Coverage Δ

src/long-tasks-recorder.ts
90.9% <0%> (-9.1%)
:arrow_down:

Continue to review full report at Codecov.

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


Badge: option to show short/full versions of contents

Simplified version without icon to toggle Badge contents. Selecting text from Badge doesn't trigger state changing.
For version with small icon clicking area much smaller => harder to click => worse UI/UX.
close  #1236
close  #1400

Moved <Badge/> styling to CSS Modules, checked intended behavior.
https://user-images.githubusercontent.com/9607060/125440038-521fb43e-8517-492c-89a1-903edfdae91f.mov


Update python minimum supported version

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

This bumps the minimum supported version of Python to 3.7 as support for 3.6 was dropped in release 2.0.0. Installing 2.0.0 on 3.6 causes errors on import.

@langmm Thanks!


Update the experimental emojis and some basic readme content

In Win11, the emojis we were using to indicate experimental became "End" emojis, updating that to be a refresh symbol that's hopefully refresh on both Win10 and Win11 (I don't have a Win10 device to test with anymore though).
Also made a couple minor updates to the readme to ensure we weren't promising 100% incremental usage for 1.0 since XAML Islands is no longer part of 1.0.

Heads up: 🔄 is supposed to be U+1F501 | CLOCKWISE RIGHTWARDS AND LEFTWARDS OPEN CIRCLE ARROWS. You might want to file a bug internally on Edge, font team, or all of the above.

Ah thanks @riverar, yeah it seemed odd and incorrect that our emojis ended up like that, I'll try to find the right contacts about that!

@andrewleader If you need a bug vehicle, https://aka.ms/AAeki3c

Thanks! I'll merge now, I'm also working with the emoji team, I heard that they have some emoji changes they're aware of and am confirming if this previous icon was one of them, but for now switching to this other icon.

@andrewleader You just merged in typos that I pointed out in review.

Agh idk how I missed those comments, sorry and thank you! #1701


Set format_preset: humanize when generating metrics views

Closes https://github.com/rilldata/rill/issues/5893

Our docs indicate that the default format is humanize so is it possible that we have a gap in implementation either in docs or in code ?

@djbarnwal says they are changing this default to unformatted, so that's why this change was needed.

Is it possible to create a enum for all presets?

Good idea, added it to the code quality backlog


Update XML files to contain schema for xml-validation and crowdin compliance

https://support.crowdin.com/file-formats/xliff/
wants
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">

Thank you!


Force assertions enabled for all test case builds

This is done by sanitycheck, but not manual builds and it keeps biting us, especially when testing on real hardware. Force assertions on for all tests, disabling them for benchmarks.

@andyross good idea

Codecov Report

Merging #7890 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7890      +/-   ##
==========================================
+ Coverage   55.02%   55.03%   +0.01%
==========================================
  Files         483      483
  Lines       53970    53957      -13
  Branches    10501    10488      -13
==========================================
  Hits        29696    29696
+ Misses      19986    19985       -1
+ Partials     4288     4276      -12

Impacted Files
Coverage Δ

subsys/logging/kernel_event_logger.c
57.5% <0%> (+1.4%)
:arrow_up:

include/crypto/cipher.h
100% <0%> (+33.33%)
:arrow_up:

Continue to review full report at Codecov.

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

Might be worth patching sanitycheck to remove/deprecate the --enable/disable-asserts option

Deprecating is warning the users that something will be removed in the future but commit 29599f6d80bb made the options no-ops immediately.
Assuming asserts are on by default, I think --enable-asserts should print a "NO-OP kept for backward compatibility" warning while --disable-asserts is harmful (it just hit me) hence it should be removed.
Or maybe both can be just removed by now, it's been almost a year?


Add Field or Relation: lower items in the list are below browser screen

When adding a new relation or a new field of the object, the lower items of the drop down list are below the browser screen. This happens even with the slider of the tool area ('Seitenleiste') pushed to the lowest position.

Happens with the latest changes of iD (2.15.0), was not present with earlier versions. Using a Firefox browser 67.0 (latest)

Oh this was fixed awhile back.


K8s: Use new High Availability documentation instead of deprecated podmaster/hyperkube

Podmaster is deprecated.
We should use the new high availability documentation to set up our K8s cluster: http://kubernetes.io/docs/admin/high-availability/
Obsoletes #1661

Ansible version (ansible --version): 1.9.4
Python version (python --version): 2.7.11
Git commit hash or branch: master
Cloud Environment: all
Terraform version (terraform version): 0.7.0

kelseyhightower/kubernetes-the-hard-way will also be super useful for moving this forward.

This is waiting on the resolution of one of these two issues:

upstream: https://github.com/MustWin/kubernetes/issues/10
our packaging: https://github.com/asteris-llc/kubernetes-packaging/issues/4


Fixing flow errors

Summary
Fixing flow errors
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit tests passed
[x] Ran make flow to ensure type checking passed

Are these not being checked automatically? Shouldn't those errors have failed the build on Jenkins?

Yes, I though that, is part of the Makefile test task requirements, but maybe jenkins is not using directly the Make tasks.


Typos on Makefile and app crash

Hi,
I'm trying to compile rawandroid under WSL following the excellent guidelines but in the makefile:

ANDROIDVERSION is set to 29 but should be 24.
in the AndroidManifest.xml part, "PACKAGENAME=$(PACKAGENAME)" is missing and under WSL envsubst do not works! It fills with empty strings! (Any hint ?? )

Then, when I fix this small issues, the uploaded application keeps crashing, last string I see after "make run" is: Starting: Intent { cmp=org.yourorg.cnfgtest/android.app.NativeActivity }
Thank you for your time.

change the android:value tag to have the same name as your app
<meta-data android:name="android.app.lib_name" android:value="my_test"/>
I had the same issue and found it very frustrating, but if you check the AndroidManifest.xml.template you will see
<meta-data android:name="android.app.lib_name" android:value="${APPNAME}"/>
so I guess it's not so much an error but unclear instructions

Do you have a recommendation for how to update the README?

Hi,
I'm trying to compile rawandroid under WSL following the excellent guidelines but in the makefile:

ANDROIDVERSION is set to 29 but should be 24.
in the AndroidManifest.xml part, "PACKAGENAME=$(PACKAGENAME)" is missing and under WSL envsubst do not works! It fills with empty strings! (Any hint ?? )

Then, when I fix this small issues, the uploaded application keeps crashing, last string I see after "make run" is: Starting: Intent { cmp=org.yourorg.cnfgtest/android.app.NativeActivity }
Thank you for your time.

Hi, I have installed under WSL too. I'm facing the same problems. I changed  package="${PACKAGENAME}" to package="com.makecapk"   in the AndroidManifest.xml .   cnfgtest.apk built successfully but when I install in my android running android 10, it shows There was a problem parsing the package.  In logcat this is shown ::
  1507 20884 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x2010000 cmp=com.android.packageinstaller/.DeleteStagedFileOnResult (has extras)} from uid 10114
  1507  1895 I ActivityTaskManager: Displayed com.android.packageinstaller/.InstallStaging: +323ms
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@c6cee38
  1507  1695 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x10000 cmp=com.android.packageinstaller/.PackageInstallerActivity (has extras)} from uid 10114
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@7a23213
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.

Did you resolve the issues ?    I don't know android app development. Please guide me.
Thanks.

Hi,
I'm trying to compile rawandroid under WSL following the excellent guidelines but in the makefile:

ANDROIDVERSION is set to 29 but should be 24.
in the AndroidManifest.xml part, "PACKAGENAME=$(PACKAGENAME)" is missing and under WSL envsubst do not works! It fills with empty strings! (Any hint ?? )

Then, when I fix this small issues, the uploaded application keeps crashing, last string I see after "make run" is: Starting: Intent { cmp=org.yourorg.cnfgtest/android.app.NativeActivity }
Thank you for your time.

Hi, I have installed under WSL too. I'm facing the same problems. I changed package="${PACKAGENAME}" to package="com.makecapk"  in the AndroidManifest.xml . cnfgtest.apk built successfully but when I install in my android phone running android 10, it shows There was a problem parsing the package. In logcat this is shown ::
  1507 20884 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x2010000 cmp=com.android.packageinstaller/.DeleteStagedFileOnResult (has extras)} from uid 10114
  1507  1895 I ActivityTaskManager: Displayed com.android.packageinstaller/.InstallStaging: +323ms
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@c6cee38
  1507  1695 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x10000 cmp=com.android.packageinstaller/.PackageInstallerActivity (has extras)} from uid 10114
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@7a23213
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.

Did you resolve the issues ? I don't know android app development. Please guide me.
Thanks.

Yes, I solved.
This is my first attempt to android development too but I think you must use same packagena as specified in the first lines of Makefile: org.yourorg.cnfgtest

Hi,
I'm trying to compile rawandroid under WSL following the excellent guidelines but in the makefile:

ANDROIDVERSION is set to 29 but should be 24.
in the AndroidManifest.xml part, "PACKAGENAME=$(PACKAGENAME)" is missing and under WSL envsubst do not works! It fills with empty strings! (Any hint ?? )

Then, when I fix this small issues, the uploaded application keeps crashing, last string I see after "make run" is: Starting: Intent { cmp=org.yourorg.cnfgtest/android.app.NativeActivity }
Thank you for your time.

Hi, I have installed under WSL too. I'm facing the same problems. I changed package="${PACKAGENAME}" to package="com.makecapk"  in the AndroidManifest.xml . cnfgtest.apk built successfully but when I install in my android phone running android 10, it shows There was a problem parsing the package. In logcat this is shown ::
  1507 20884 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x2010000 cmp=com.android.packageinstaller/.DeleteStagedFileOnResult (has extras)} from uid 10114
  1507  1895 I ActivityTaskManager: Displayed com.android.packageinstaller/.InstallStaging: +323ms
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@c6cee38
  1507  1695 I ActivityTaskManager: START u0 {act=android.intent.action.VIEW dat=file:///data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk flg=0x10000 cmp=com.android.packageinstaller/.PackageInstallerActivity (has extras)} from uid 10114
  15224 15224 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@7a23213
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.
  15224 15224 W ackageinstalle: resources.arsc in APK '/data/user_de/0/com.android.packageinstaller/no_backup/package6828865154129075590.apk' is compressed.

Did you resolve the issues ? I don't know android app development. Please guide me.
Thanks.

Yes, I solved.
This is my first attempt to android development too but I think you must use same packagena as specified in the first lines of Makefile: org.yourorg.cnfgtest

Thanks. I have manually filled all the ${ } field values in the AndroidManifest.xml  from Makefile. Now the app is running well.

I was able to generate a valid AndroidManifest.xml from Makefile under WSL.
I don't know if it works on other platforms.
I use sed instead of envsubst:
AndroidManifest.xml :
	rm -rf AndroidManifest.xml
	cp AndroidManifest.xml.template AndroidManifest.xml
	sed -i -e 's/$${ANDROIDVERSION}/$(ANDROIDVERSION)/' \
		-e 's/$${ANDROIDTARGET}/$(ANDROIDTARGET)/' \
		-e 's/$${APPNAME}/$(APPNAME)/' \
		-e 's/$${LABEL}/$(LABEL)/' \
		-e 's/$${PACKAGENAME}/$(PACKAGENAME)/' \
		AndroidManifest.xml

I was able to generate a valid AndroidManifest.xml from Makefile under WSL.
I don't know if it works on other platforms.
I use sed instead of envsubst:
AndroidManifest.xml :
	rm -rf AndroidManifest.xml
	cp AndroidManifest.xml.template AndroidManifest.xml
	sed -i -e 's/$${ANDROIDVERSION}/$(ANDROIDVERSION)/' \
		-e 's/$${ANDROIDTARGET}/$(ANDROIDTARGET)/' \
		-e 's/$${APPNAME}/$(APPNAME)/' \
		-e 's/$${LABEL}/$(LABEL)/' \
		-e 's/$${PACKAGENAME}/$(PACKAGENAME)/' \
		AndroidManifest.xml

Sorry to bother you again.  Just one more.   adb is failing to send & open apk. I'm getting these errors .
adb server version (41) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
make: *** [Makefile:178: push] Error 1

I have tried some of the solutions given online. But none of them are working. Could you help ?

Make sure your phone is connected and USB debugging is activated. On the first time it should ask to trust this computer. Maybe try to run one if the example apps in Android Studio to test the USB debugging. You seem to have more than one adb installed, not sure if that could be an actual problem.


Issue running op3_bringup

Hello, I am currently trying to run the tutorials from the e-manual for the ROBOTIS OP3.
I am doing section 5.1 of the tutorials. I run the sudo command to kill the demo service. Although when I run the command:
$ roslaunch op3_bringup op3_bringup.launch
I get the following error.

Can you please help me with this issue, I am not sure if I am not running an appropriate file or what the issue is. Thank you!

Hi @lachg258,
I'm sorry about the late response.
The first warning indicates that the camera package cannot find the calibration file which is not necessary for the OP3 default demo. If you need to utilize camera for specific visual operation, please calibrate the camera.
The deprecation warning doesn't affect to the operation, but warns you that there will be deprecated feature in the camera package.
Thank you.

This issue will be closed as there isn't any recent activity. Please feel free to reopen when necessary.


Create PyPI release for python

Hello,
This is related to issue #282.
With this PR:

A setup.py file is added.
Circleci workflow is updated to release the package on PyPI when a tag starting with v is created.

Need to address the following:

Get a username and password for PyPI. The username will be added in config.yml (<username>), whereas the password will be stored in $PYPI_PASSWORD env variable in circleci.
Review the metadata in setup.py and decide what the author and author_email values should be. I also used delta.io as the package name since delta was used already.
Added pyspark as an install dependency (i.e. will get installed when you do pip install delta.io) but whether it needs to stay there is open for discussion.

 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.

this is awesome. i am unfortunately not knowledgeable about how to do pypi release, so i have do some homework myself to learn more about it.

Hello @tdas, afaict all you need to do is create an account for delta-io on PyPI https://pypi.org/account/register/ and store the password ($PYPI_PASSWORD) as a secret in circleci. Also I think it makes more sense to rename the package from delta.io to delta-io.

Hey @nicktgr15 I was doing my homework learning about pypi releases and I was wondering

Have you tested this out using test.pypi.org? At the first glance, I am not sure how this script would work. It seems to only package the python directory and not the delta JARs that are needed for python code to work. Fu

Furthermore, if you have tested with test.pypi.org (or manually), have you made sure that it works with pyspark? That is, pyspark is able to correctly find the python class and the JARs?

subscribing to know when it's released...

Hello @tdas,
Created a release under https://test.pypi.org/project/delta.io/0.5.0/ using twine upload --repository-url https://test.pypi.org/legacy/ dist/*. The artifacts under dist are created using python setup.py bdist_wheel and  python setup.py sdist. (these steps are already available in the circleci conf file on the PR).
I have some pyspark tests where I'm using delta and I was able to pip install the dependency from test.pypi.org pip install -i https://test.pypi.org/simple/ delta.io==0.5.0 and run them without issues.  Note that in my spark conf during the tests I'm using .set("spark.jars.packages", "io.delta:delta-core_2.11:0.5.0").
Hope the above helps.

@nicktgr15 That's awesome! Thank you for testing it out comprehensively. This is cool! However, it looks like the pip installation is not self-contained as you have to add .set("spark.jars.packages", "io.delta:delta-core_2.11:0.5.0"). What this is doing is it's getting the python files only from the pip installation of delta, and then getting the jar files from the maven release (setting the cof to io.delta:delta-core_2.11:0.5.0 is doing exactly that).
This is quite suboptimal. The point of any such package installations systems is that they are self-contained and automatically handles all its dependencies without requiring the user to configure additional things. This, unfortunately, is not self-contained.
In fact, this can be a recipe for disaster. One can easily misconfigure their project to cause a mismatch between the python version and the jar version. E.g., someone runs their python project on a different system with a different version of pip delta installed without remembering to update the SparkConf accordingly. Such situations can be very hard to debug. In contrast, the current solution with pyspark --packages io.delta:delta-core_2.11:0.5.0 is self-contained as this one setting/command-line arg will take care of configuring both python and java, thus avoiding any scope of version mismatch.
Now I don't have a very good solution off the top of my head to fix this. I know that jars can be packaged insides wheels (pyspark does that in its pypi packaging). However, the real challenge is packaging the jar such that after pip installation, pyspark is able to find those jars and automatically put them in the classpath for the spark JVM process. There may exist other projects that have done something like this that we can learn from, but I dont know of any.

subscribing

Hi @tdas,
Yes, your concern makes sense.
I had a look for pyspark packages with python wrappers for scala/java libraries (there aren't many) and providing the packages/jars separately seems to be a common (bad?) practice. Examples include:

https://github.com/JohnSnowLabs/spark-nlp, where they provide a start() method to set the spark.jars.packages conf param https://github.com/JohnSnowLabs/spark-nlp/blob/master/python/sparknlp/init.py#L40 or they suggest to create the session manually https://github.com/JohnSnowLabs/spark-nlp/blame/master/README.md#L247.
https://github.com/locationtech-labs/geopyspark, in this case they also have a config init method https://github.com/locationtech-labs/geopyspark/blob/master/geopyspark/init.py#L118 where spark.jars is getting set. The jars are downloaded separately. (this project is not under active development)

Apart from the above thought, I realised that there's a workaround to solve this problem, without releasing a pypi package. e.g. https://github.com/Azure/mmlspark
spark = pyspark.sql.SparkSession.builder.appName("MyApp") \
            .config("spark.jars.packages", "com.microsoft.ml.spark:mmlspark_2.11:1.0.0-rc1") \
            .config("spark.jars.repositories", "https://mmlspark.azureedge.net/maven") \
            .getOrCreate()
import mmlspark

were the session is created first and afterwards you can import mmlspark.
In my case with delta (when using spark.jars.packages) the following doesn't work because delta is not installed
from delta.tables import DeltaTable

def delta_table_exists(path):
    return DeltaTable.isDeltaTable(identifier=path, sparkSession=get_spark_session())

however, the following works fine (because the delta import is executed inside the spark session).
def delta_table_exists(path):
    from delta.tables import DeltaTable
    return DeltaTable.isDeltaTable(identifier=path, sparkSession=get_spark_session())

Of course static code analysis doesn't work very well with this approach.

This is a great find and definitely worth documenting! Can you update the original issue #282 with this alternative? I will try to add this to the online docs as well, maybe in the quick-start guide.
In addition, from your survey, it seems like there is no clean solution for making it work with pypi packaging. And this import-after-session-creation seems to be a much cleaner approach. In that case, I am inclined to drop this pypi packaging attempt for now.
Nonetheless, thank you very much for investigating!!!

Sad, that this seems so complicated. In the current situation: is there any possibility that static code analyzers (e.g. My IDE pycharm or Pylint) can recognize that
from delta.tables import DeltaTable

is a valid import and I can use autocompletion etc.?

This has been done by https://github.com/delta-io/delta/commit/98c66a64d7ab60fc27ba790d7ef3df82bd76c3cb


Create dependabot.yml

Create a new dependabot.yml to help keep dependencies updated.
https://help.github.com/en/github/administering-a-repository/configuration-options-for-dependency-updates

@thomas-nilsson-irfu would that generate the PRs for all deps, or only security deps ? Or just raise dependabot alerts ?

@thomas-nilsson-irfu would that generate the PRs for all deps, or only security deps ? Or just raise dependabot alerts ?

Dear @gotson, adding this dependabot file will only result in the bot @dependabot opening new MR for all the dependencies listed in https://github.com/xerial/sqlite-jdbc/blob/master/pom.xml, if they have been updated from the specified version.
In MR from @dependabot there is also some extracted information from the dependencies, if they are providing it in things like release notes. I have seen some MR opened by @dependabot with release notes referencing security issues (CVE's etc), but typically @dependabot is indifferent in regards to why a new upstream dependent package was released...
The opened MR can be controlled via simple comments to @dependabot.

One example can be seen in https://github.com/irfu/irfu-matlab/pull/94.

Given the project has zero dependencies, only test deps, i would prefer that it checks only for security updates.
We do however use github-actions ecosystem, and i would see some value in having those updates coming along.


multiple domains on single alb?

Is it possible to have multiple domains in a single ingress/alb?

Yep, they just need to be defined within the same ingress resource currently.

I've tried without success. It creates a single ALB, but a different Target Groups for each Services defined in the ingress file. But, the created ALB will associate with only one Target Group... ): is it normal?

Yep, they just need to be defined within the same ingress resource currently.

But that leads to the restriction that you must use the same certificate for all domains, correct @bigkraig?

Left some suggestions for this restriction in #352 @tillkahlbrock

right, we need to implement support for SNI which is now being tracked in #238


Table name fct_multiple_sources_joined could be misleading as it includes unioned sources as well

The table fct_multiple_sources_joined contains the models joining from multiple sources, as expected, but it also contains models that are unioning from multiple sources (which in some cases might make sense).
We could potentially rename the model from fct_multiple_sources_joined to fct_multiple_sources_joined_or_unioned. But at the same time, it would be good to have a way to flag the unions vs joins.
In our Internal Analytics project the current convention is to prepend the stg/base model name with unioned

Do we still want to rename this model?

I feel like it, yes. A few ideas for new names:

fct_multiple_sources_used_in_model
fct_multiple_sources_in_single_model
fct_multiple_sources_in_model

The initial discussion about union vs join and the "flag" is already available with the ability to define exceptions now. So people could easily exclude all the %_unioned from being reported.


 Help is available under --help.
Sleep for 3600s

It's due to a change in the TOS. @thomastweets has been good enough to create a new version that works:
https://hub.docker.com/r/thomastweets/docker-letsencrypt-nginx-proxy-companion/
But FYI, it doesn't work with the staging server.

@alastaircoote that must be something else. Just got the same error while trying to get a cert for a .рф domain for the first time and got this (it is defined as .xn--p1ai in my ENV). Tried replacing jrcs/letsencrypt-nginx-proxy-companion with thomastweets/docker-letsencrypt-nginx-proxy-companion, but that did not help too.
It seems like this repo's image has got a right hash for the ToS because they haven't changed anything since August and I've been successfully getting certs for ASCII (non-IDE) domains since then.
This issue is likely to be a duplicate for https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/130, which is probably still topical although marked as fixed. The reason why I decided to get a cert for an IDE domain is because they became supported by Letsencrypt just a few hours ago: https://github.com/letsencrypt/boulder/issues/2277#issuecomment-265830438

Thank's @alastaircoote. I'll consider this for production. Do you know why it doesn't work with the staging server ?

Yes, I take it back - it did work for me, and issued a cert for one subdomain. But now I'm trying with another and it's failing, so I'm not sure what is going on. The core problem seems to be relying on simp_le, which seems to be kind of dead:
https://github.com/kuba/simp_le/issues/118

/cc  @jsha

OK, I believe I have a fix. But I should preface this by saying that I am not well versed in either LetsEncrypt or SSL certs in general, so if I were you I wouldn't trust me.
As mentioned in the issue I linked to, simp_le pull request #112 seems to fix the issue, but it hasn't been merged. So I made a fork of this repo that switches to the acme-0.8 branch before it builds:
https://github.com/alastaircoote/docker-letsencrypt-nginx-proxy-companion
Then put that on Docker hub:
https://hub.docker.com/r/alastaircoote/docker-letsencrypt-nginx-proxy-companion/
It's working for me. But as I say, this needs someone with more knowledge than me to look it over if you're going to use it in a production environment or anything like that.

@alastaircoote Great ! Works for me too (staging mode). I'll try with production mode.

I agree that seems like the right choice. Older version of the acme package had a bug where they would fail if presented with any fields in the directory that they didn't recognize. Upgrading to a more recent acme package fixes it.

@alastaircoote your fix is the good one. It works in production too. Thank's

@Dabada why did you close this issue? Even if it works in alastaircoote/docker-letsencrypt-nginx-proxy-companion it doesn't mean that it works in the JrCs version (=this repository). IMO this is still an issue with jrcs.

Agree on keeping this open, if only so that people can find it on the issues page (it's how I found it).
I've submitted pull request #132 to incorporate my change into this repo - I'd much rather do that than have more and more people using my branch, which I won't be actively maintaining.

It needs to stay open. I had the problem yesterday and this issue was necessary

@Dabada this project is broken and a lot of users experiment this problem in production!
This issue should be re-open and @alastaircoote temp fixed should be merge until a better solution is fount.

While this is slightly off-topic, is @JrCs even active on this project anymore? If not, wouldn't it be better just to fork this repo and move to that permanently?

@mlaitinen (and others), you are right. The issues is reopened.

@alastaircoote fix still runs into #128 for me.

@thatbudakguy that looks like a totally different error to me - this only fixes the Wrong directory fields error others have encountered.

@alastaircoote absolutely; sorry for off-topic - just wondering if anyone else has deployed the fix and also run into #128, since I'm at a loss

@thatbudakguy Yes, I am having exactly the same problem. I use @alastaircoote fork and I am still running into #128.

Glad it isn't just me!

Just today I tried using this image for the first time and I encountered this issue.

I don't know what the fix here is.  It looks like docker-gen is interacting with the letsencrypt api with the acme python module ( part of letsencrypt ).
Last week, letsencrypt changed the response from the /directory endpoint
I guess its we need to make docker-gen live with this.
I assume acme works with letsencrypt's api, since they're part of the same project.

AFAIK, the problems described in this issue appear fixed when using the branch I made, and will hopefully go away when the pull request is merged
This doesn't apply to the problems in #128 though.

The Issue is not fixed for me using @thomastweets ...
Still get this :
Creating/renewal gitlab.domain.tld certificates... (gitlab.domain.tld)
2016/12/13 15:37:35 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs'
2016/12/13 15:37:35 Watching docker events
2016/12/13 15:37:35 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs'
2016-12-13 15:37:36,246:INFO:simp_le:1211: Generating new account key
2016-12-13 15:37:40,587:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1401, in main
    return main_with_exceptions(cli_args)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1386, in main_with_exceptions
    persist_new_data(args, existing_data)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1282, in persist_new_data
    client = registered_client(args, existing_data.account_key)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1224, in registered_client
    client = acme_client.Client(directory=args.server, key=key, net=net)
  File "build/bdist.linux-x86_64/egg/acme/client.py", line 63, in __init__
    self.net.get(directory).json())
  File "build/bdist.linux-x86_64/egg/acme/messages.py", line 169, in from_json
    raise jose.DeserializationError(str(error))
DeserializationError: Deserialization error: Wrong directory fields

Unhandled error has happened, traceback is above

@trash-anger try using https://hub.docker.com/r/alastaircoote/docker-letsencrypt-nginx-proxy-companion/

Oh yeah !!!! Thank you !!! ;) 👍

@alastaircoote hey man you are really dope! :D

Thanks @alastaircoote
Was trying to figure this one out for quite a while.
Your solution worked perfectly.

@alastaircoote works like a charm, thanks, bro!

Thanks @JrCs, for not forsaking us! ;) Switching back from @alastaircoote's.
And thanks @alastaircoote for the quick fix!

Happy to help. I strongly encourage everyone move back to this repo as I won't be maintaining my fork!


Correct noised reach calculation in fulfillDirectReachAndFrequencyMeasurement in EDP simulator

This PR should fix https://github.com/world-federation-of-advertisers/cross-media-measurement/issues/808

This change is

src/main/kotlin/org/wfanet/measurement/loadtest/dataprovider/EdpSimulator.kt line 835 at r1 (raw file):
Previously, riemanli (Rieman) wrote…
I wonder if it's necessary to have this function public.

I think so since it needs to be unit tested?

src/main/kotlin/org/wfanet/measurement/loadtest/dataprovider/EdpSimulator.kt line 835 at r1 (raw file):
Previously, kungfucraig (Craig Wright) wrote…
@stevenwarejones that makes sense to me

Thanks for your feedback Steven! I discussed with the team yesterday and there’s a need to support adding Gaussian noise in the future. In that case, it will make sense to create an interface to support different types of noise distributions. I would like to handle that in a separate PR since the main purpose of this PR is to fix the calculation of noised reach value. For this PR, I will keep this function private for now and test the changes with public API in EDP simulator as Sanjay suggested.

src/main/kotlin/org/wfanet/measurement/loadtest/dataprovider/EdpSimulator.kt line 835 at r1 (raw file):
Previously, iverson52000 (Albert Hsu) wrote…
Thanks for your feedback Steven! I discussed with the team yesterday and there’s a need to support adding Gaussian noise in the future. In that case, it will make sense to create an interface to support different types of noise distributions. I would like to handle that in a separate PR since the main purpose of this PR is to fix the calculation of noised reach value. For this PR, I will keep this function private for now and test the changes with public API in EDP simulator as Sanjay suggested.

Done

src/main/kotlin/org/wfanet/measurement/loadtest/dataprovider/EdpSimulator.kt line 693 at r3 (raw file):
Previously, iverson52000 (Albert Hsu) wrote…
Sure it's more explicit with this name

Done


Request to search for record changes in change history

Is your feature request related to a problem? Please describe.
In some environments there are hundreds to thousands of changes per day, looking for past changes can be challenging.  The change history page is just one page with no search options.
Describe the solution you'd like
Adding search options by fields: ID, User, record name, date range, and if status is completed or failed.
Describe alternatives you've considered
N/A
Additional context
N/A

Related to this is that we need an approach to archiving older changes.  @kontrolldkaos is all history imperative?  Should retention be a config option?

@pauljamescleary it definitely needs to be a config setting if there is support for archiving. Feedback that we've gotten is that all "significant" changes should be kept indefinitely.
Significant changes were basically identified as anything but TTL changes. Everything else was needed for later analysis.
For enterprise users, they can come up with custom archiving strategies at the DB level. Ex: archive or replicate change records to a data lake for reporting and analysis.
As it stands the larger challenge is the unsearchable binary blobs, IMO.

@remerle makes sense, we can stand up new indexes on record changes and pull fields out of the blob.  We have done this previously via a migration script.  Ew, by the looks of it we have nothing broken out for mysql.  Not a fun migration for existing installs if there is a lot of data, but the code itself should be minimal.
We could add a recordSetId column+index, that would allow us searches by record type, record name, fqdn, and even group by joining through to recordset table.
In addition

add a userId column+index
status column+index

Note: there appears to already be a created index on that table, so we should be fine to search by time already.

Related to this is that we need an approach to archiving older changes. @kontrolldkaos is all history imperative? Should retention be a config option?

Yes retention should be a config option. Some organizations may not need that long of retention, while others may. To archive, I'd look into stripping certain changes that aren't that important, mainly TTL changes/adjustments.

and I should have read Ryan's replies...yep..he has it covered.

Ok, I think this is good to be implemented?  Perhaps we have a "Ready" label @remerle ?

Flyway migration to add the columns
A "programmatic" flyway migration that populates the columns (this will take a long time to run.  If done as a flyway migration, it will delay the restart of VinylDNS until it is complete which maybe ok for us due to our release pipeline.  Release notes should make this very clear
Add additional query support in the record change repository to take in the following fields

user id
record mask - to be used in a LIKE clause; our convention is to support wildcards and replace with %
start time (Instant)
end time (Instant)
status

@kontrolldkaos what do you mean by "ID", are you talking about batch changes / DNS requests?

@pauljamescleary I think we might want a migration script as part of our migration path.  I'd be concerned for organizations that have 10s of millions of recordset changes waiting on Flyway to do it's thing and holding up the startup of the app.  Having the ability to non-destructively migrate production data outside of the release pipeline might be a good option.
I think this is conceptually pretty straightforward and ready to go.

@kontrolldkaos what do you mean by "ID", are you talking about batch changes / DNS requests?

Yes I am talking about batch change ID.

@remerle I haven't looked into it, but perhaps we can have flyway run certain migrations out of band, as opposed to on startup by default.  Having that lever to override will allow people to proceed carefully.  Need to fully document that in the Release Notes

Removing this from ready in favor of a wholly revisiting the BLOBs and pulling data up into columns (#975). Implementing #975 will open the door to many features such as this.

Closing in favor of #975


Improve interface to tpcf_jackknife

The tpcf_jackknife interface "feels" quite different from the tpcf function, and has some surprising defaults (box size 250 Mpc etc). The user shouldn't be required to pass randoms but just a number of randoms, and the box size / period parameters should interact somehow.

Another unexpected behavior is the following: if Nsample > max_sample_size, the function also returns cross-correlations! The reason is that the samples get randomly down-sampled independently, after sample1 = sample2 (if no cross-correlation desired) and np.all(sample1 == sample2) operations thereafter. The latter then gives false and makes the function think that the user has passed two different samples.
I'd get rid of the (sample1 == sample2) checks altogether and replace them with a flag that is evaluated once at the very beginning.

This is great.  keep finding all these little things.  I will fix them in one swoop when Andrew and I update the pair counter next week.

I agree with the randoms issue too.  Although, there should be a random seed keyword argument, so as to make the calculation repeatable.

Both of these issues should be fixed in the next pull request.


Initial docker-compose

@marcusnogueiraa can you review?

Everything is fine, my daughter. Later, as the application grows, we have to add Redis and MongoDB Images to Docker Compose. There will be a task in the Backlog for this. For now, everything is OK. Thanks for the contribution =)
@sheiely
I'm closing the issue.


Minor fixes/enhancement for discovery

Description
As above
Fixes # (issue)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Locally with docker-molecule, soak cluster
Test Configuration:
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

 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.


PIC-3499 create missing hibernate envers index in prod

I am wondering why this is something that needs to be done manually, shouldn't the migration framework handle/support this? Did a bit of digging and this came up https://stackoverflow.com/questions/26221688/hibernate-envers-revinfo-table-doesnt-exist

Those configurations have caused more problems and were also major reason for current instability of the service (Accidentally, leaving in framework's hands to create/update the tables.)


Help >> about

Seems that it shows same version all the time when npm started from master.

I don't get it... What are you talking about? 😰

I've noticed this too. The About dialog always shows the latest git tag (such as 0.7.1) even though it's built from 0.7.1 + 100 commits. Ideally, the about menu would show the version as 0.7.1-<git_hash> just like you'd get from git describe.

Oh, now I get it 😄 Thanks for the clarification @flybayer 😄


Fix another is defined bug

What is the context of this PR?
Fix for a bug in Runner from adding the "is defined" PR
How to review

Check code
Tests Pass

 "Is defined" bugs


Feature 68

Implemented logging functionality for htmlviewer.  Accounts for css bug in htmlviewer and includes some refactoring for readability.

Assuming that since this is saying there are no conflicts that the master as of yesterday afternoon has been re-merged into this branch and there are no issues.


Using latest CAPC (v0.4.7-rc3) release to fix several bugs

Issue #, if available:
Description of changes:
Changenotes: https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/releases/tag/v0.4.7-rc3
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.11

/cc @abhay-krishna @jaxesn

/lgtm
/approve