[WIP] Swift 3

Ran the Swift 3 migration tool and updated the RealmSwift API for the changes in master.

[x] 🚫 Currently blocked by rdar://27141382. Hopefully, Xcode 8b2 will fix these errors
[x] ⚠ Depends on unreleased Swift 3 changes for RealmSwift in the master branch of realm-cocoa
[x] ⚠ Depends on Roobiq/RBQSafeRealmObject#2. Will redo submodule commit after dependent PR is merged.

Dependendencies now integrated using CocoaPods instead of git submodules

Strange build issue is resolved in Xcode 8b2 (8S162m) 🎉

What is the status of this PR? Will this be released soon?

Sorry I will try to pick up on this next week. Realm is announcing something new next week and I have been heads down all summer.

Status on this?

@phatblat @bigfish24 any ETA on the Swift 3 support?

Ok, It seems that no one is willing to merge this.
@phatblat Thank you very much for this update, I was unfortunately unable to get this working with your forked pods, could you point me to correct way how to get this working temporarily?
Thank you

@syky27 You can install an unreleased version of a pod from a branch using the following:
pod 'RBQFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'

Almost forgot, since RBQSafeRealmObject is a dependency of this library and its Swift 3 migration is still (in-progress](https://github.com/Roobiq/RBQSafeRealmObject/pull/2), you'll want to include it from a branch as well, but that dependency should be before RBQFetchedResultsController, so that it uses the modified version instead of a released version.
pod 'RBQSafeRealmObject', git: 'https://github.com/phatblat/RBQSafeRealmObject.git', branch: 'swift-3'
pod 'RBQFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'

@phatblat and @syky27 sorry this has sat idle for so long. Not much I can say other than I sincerely apologize. Added @phatblat as a contributor to both repos... if things are ready do you want to merge, if not I can do so too?

Well this is getting better, @phatblat I was trying that exactly as you suggested now, but I still could not build because some error, and now when I wanted to give you the error, cocoapods are acting crazy, I need to do gem cleanup in a sec, cannot really do it now...

 This is entirely my fault and I should have addressed it far sooner.

@phatblat So I fixed my cocoapods installation the build error I am getting is:
/Users/syky/optify/optify-ios/Pods/RBQFetchedResultsController/RBQFetchedResultsController/Source/CacheObjects/RBQObjectCacheObject.h:10:9: 'RBQSafeRealmObject.h' file not found

In RBQObjectCacheObject.h file.

@syky27 do you have use_frameworks! In your Podfile? That import needs to be changed to work with frameworks/modules. I'll update it tomorrow.

@bigfish24 thanks for adding me as a contributor! I'll double check my changes, test them in Xcode 8.1 and merge when things look good.

Hi, @phatblat did you find a time to get to this?

Could someone please merge this? Or at least provide me with solution? @phatblat you said that the import needs to be changed but you did not provide me with solution.
I know that I am really pressing on this, it's kinda critical for me.
Thank you in advance.

@syky27 I think I fixed the issues. I was more than just the import, there was a missing dependency in the pod specs as well. My swift-3 branches have the fix now.
Now just need to review these changes in a real app to make sure I've caught everything. If you have a chance to test these changes, that would help a lot!

Thanks you @phatblat, that is what I thought, because even when I was using your branch I was not able to compile this due missing dependencies.
Thank you for the hard work.
I will try to test it later today.
Is this all I need to do?
pod 'RBQSafeRealmObject', git: 'https://github.com/phatblat/RBQSafeRealmObject.git', branch: 'swift-3'
pod 'RBQFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'

@phatblat Hi, I am still unable to build, still getting this:
'RBQSafeRealmObject.h' file not found

This is my podfile:
  pod 'RBQSafeRealmObject', git: 'https://github.com/phatblat/RBQSafeRealmObject.git', branch: 'swift-3'
  pod 'SwiftFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'

Is it on my side, does your fix work? Or is it still WIP?

@syky27 This is still a WIP. I forgot that this repo has RBQSafeRealmObject as a git submodule. That may be why you're getting the "file not found" error. CocoaPods doesn't init submodules when dependencies are included from a branch unless you add submodules: true. However, when I got past that error, I got several "duplicate symbols" errors because the dependencies are being included twice.
I'm going to try removing the submodules now that CocoaPods knows about this library's dependencies.

Hi, even after you removed submodules, nothing has changed for me :(

@syky27 Strange. Removing the submodules resolved the import issues in the cocoapods example projects. Make sure to run pod update so that CocoaPods pulls in the latest commit instead of using the one in your Podfile.lock.

@phatblat So I have deintegrated cocoapods, removed Podfile.lock, cleaned project & derived data, basically I tried everything... My Podfile looks like this:
# Uncomment this line to define a global platform for your project
 platform :ios, '9.0'

target 'OPTIFY' do
  # Comment this line if you're not using Swift and don't want to use dynamic frameworks
  use_frameworks!

  # Pods for OPTIFY
...
...
...
  # REALM
  pod 'RealmSwift'
  pod 'SwiftFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3', :submodules => true

...
...
...

  target 'OPTIFYTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'OPTIFYUITests' do
    inherit! :search_paths
    # Pods for testing
  end

end

post_install do |installer|
	installer.pods_project.targets.each do |target|
		target.build_configurations.each do |config|
			config.build_settings['SWIFT_VERSION'] = '3.0'
		end
	end
end

And I am still getting  this:

In RBQSafeRealmObject.m

Because I still for some reason have v0.7.1 of RealmObject

HI, I got further this time but I am getting nasty seg. fault
CompileSwift normal arm64 /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift
    cd /Users/syky/optify/optify-ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/syky/optify/optify-ios/OPTIFY/APIWrapper.swift /Users/syky/optify/optify-ios/OPTIFY/K.swift /Users/syky/optify/optify-ios/OPTIFY/Examination.swift /Users/syky/optify/optify-ios/OPTIFY/ExaminationForm.swift /Users/syky/optify/optify-ios/OPTIFY/AppDelegate.swift -primary-file /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/CustomersTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerValidator.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerForm.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Customer.swift /Users/syky/optify/optify-ios/OPTIFY/Device.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Examination.swift /Users/syky/optify/optify-ios/OPTIFY/Randomizer.swift /Users/syky/optify/optify-ios/OPTIFY/Customer.swift -target arm64-apple-ios9.3 -Xllvm -aarch64-use-tbi -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.1.sdk -I /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Alamofire -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Eureka -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Localize-Swift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/PKHUD -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Realm -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmSwift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmUtilities -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftyJSON -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Validator -F /Users/syky/optify/optify-ios/Pods/Crashlytics/iOS -F /Users/syky/optify/optify-ios/Pods/Fabric/iOS -F /Users/syky/optify/optify-ios/Carthage/Build/iOS -enable-testing -g -module-cache-path /Users/syky/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -D COCOAPODS -D DEBUG -serialize-debugging-options -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-generated-files.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-own-target-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-project-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/include -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Crashlytics -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Fabric -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources/arm64 -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -working-directory/Users/syky/optify/optify-ios -emit-module-doc-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftdoc -Onone -module-name OPTIFY -emit-module-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftmodule -serialize-diagnostics-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.dia -emit-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.d -emit-reference-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.swiftdeps -o /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.o -embed-bitcode-marker

/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:144:109: error: use of undeclared type 'SafeObject'
    public func controller<T : Object>(_ controller: FetchedResultsController<T>, didChangeObject anObject: SafeObject<T>, atIndexPath indexPath: IndexPath, forChangeType type: NSFetchedResultsChangeType, newIndexPath: IndexPath) {
                                                                                ^~~~~~~~~~
/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:151:101: error: use of undeclared type 'RealmSafeObject'
    func controllerDidChangeObject<T : Object>(_ controller: FetchedResultsController<T>, anObject: RealmSafeObject<T>, indexPath: IndexPath?, changeType: NSFetchedResultsChangeType, newIndexPath: IndexPath?) {
                                                                                ^~~~~~~~~~~~~~~
<built-in>:2:14: note: in module 'RBQFetchedResultsController' imported from <built-in>:3:
#define __clang__ 1
             ^
/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController/RBQFetchedResultsController.framework/Headers/RLMObject+SafeObject.h:16:12: warning: duplicate definition of category 'SafeObject' on interface 'RLMObject'
@interface RLMObject (SafeObject)
           ^
/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject/RBQSafeRealmObject.framework/Headers/RLMObject+SafeObject.h:16:12: note: previous definition is here
@interface RLMObject (SafeObject)
           ^
0  swift                    0x0000000107bf3a3d PrintStackTraceSignalHandler(void*) + 45
1  swift                    0x0000000107bf3466 SignalHandler(int) + 470
2  libsystem_platform.dylib 0x00007fffb4e9cbba _sigtramp + 26
3  libsystem_platform.dylib<PHONE_NUMBER>00000000 _sigtramp +<PHONE_NUMBER>
4  swift                    0x00000001055808a6 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 806
5  swift                    0x0000000105581610 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 4240
6  swift                    0x00000001055809f3 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 1139
7  swift                    0x0000000105580b2e swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 1454
8  swift                    0x00000001055820dc swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 7004
9  swift                    0x000000010557e294 swift::ModuleFile::getDecl(llvm::PointerEmbeddedInt<unsigned int, 31>, llvm::Optional<swift::DeclContext*>) + 39268
10 swift                    0x0000000105589367 swift::ModuleFile::loadAllMembers(swift::Decl*, unsigned long long) + 647
11 swift                    0x000000010579c4ea (anonymous namespace)::hasFailableInits(swift::NominalTypeDecl*, swift::constraints::ConstraintSystem*) + 362
12 swift                    0x000000010579bfd2 (anonymous namespace)::ConstraintGenerator::visitApplyExpr(swift::ApplyExpr*) + 642
13 swift                    0x00000001057959d0 (anonymous namespace)::ConstraintWalker::walkToExprPost(swift::Expr*) + 64
14 swift                    0x000000010590ea0c (anonymous namespace)::Traversal::visit(swift::Expr*) + 6812
15 swift                    0x0000000105791368 swift::constraints::ConstraintSystem::generateConstraints(swift::Expr*) + 424
16 swift                    0x00000001057cdd0a swift::constraints::ConstraintSystem::solve(swift::Expr*&, swift::Type, swift::ExprTypeCheckListener*, llvm::SmallVectorImpl<swift::constraints::Solution>&, swift::FreeTypeVariableBinding) + 4570
17 swift                    0x000000010580df62 swift::TypeChecker::solveForExpression(swift::Expr*&, swift::DeclContext*, swift::Type, swift::FreeTypeVariableBinding, swift::ExprTypeCheckListener*, swift::constraints::ConstraintSystem&, llvm::SmallVectorImpl<swift::constraints::Solution>&, swift::OptionSet<swift::TypeCheckExprFlags, unsigned int>) + 482
18 swift                    0x0000000105810576 swift::TypeChecker::typeCheckExpression(swift::Expr*&, swift::DeclContext*, swift::TypeLoc, swift::ContextualTypePurpose, swift::OptionSet<swift::TypeCheckExprFlags, unsigned int>, swift::ExprTypeCheckListener*, swift::constraints::ConstraintSystem*) + 630
19 swift                    0x0000000105892d38 swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 488
20 swift                    0x0000000105891d5d swift::TypeChecker::typeCheckFunctionBodyUntil(swift::FuncDecl*, swift::SourceLoc) + 365
21 swift                    0x00000001058963fc swift::TypeChecker::typeCheckAbstractFunctionBody(swift::AbstractFunctionDecl*) + 188
22 swift                    0x0000000105849aba swift::performTypeChecking(swift::SourceFile&, swift::TopLevelContext&, swift::OptionSet<swift::TypeCheckingFlags, unsigned int>, unsigned int, unsigned int) + 6714
23 swift                    0x00000001054f931b swift::CompilerInstance::performSema() + 5675
24 swift                    0x0000000104f9ca4d performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&, swift::FrontendObserver*) + 2765
25 swift                    0x0000000104f99f70 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 17856
26 swift                    0x0000000104f5693e main + 8302
27 libdyld.dylib            0x00007fffb4c8f255 start + 1
Stack dump:
0.	Program arguments: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/syky/optify/optify-ios/OPTIFY/APIWrapper.swift /Users/syky/optify/optify-ios/OPTIFY/K.swift /Users/syky/optify/optify-ios/OPTIFY/Examination.swift /Users/syky/optify/optify-ios/OPTIFY/ExaminationForm.swift /Users/syky/optify/optify-ios/OPTIFY/AppDelegate.swift -primary-file /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/CustomersTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerValidator.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerForm.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Customer.swift /Users/syky/optify/optify-ios/OPTIFY/Device.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Examination.swift /Users/syky/optify/optify-ios/OPTIFY/Randomizer.swift /Users/syky/optify/optify-ios/OPTIFY/Customer.swift -target arm64-apple-ios9.3 -Xllvm -aarch64-use-tbi -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.1.sdk -I /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Alamofire -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Eureka -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Localize-Swift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/PKHUD -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Realm -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmSwift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmUtilities -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftyJSON -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Validator -F /Users/syky/optify/optify-ios/Pods/Crashlytics/iOS -F /Users/syky/optify/optify-ios/Pods/Fabric/iOS -F /Users/syky/optify/optify-ios/Carthage/Build/iOS -enable-testing -g -module-cache-path /Users/syky/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -D COCOAPODS -D DEBUG -serialize-debugging-options -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-generated-files.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-own-target-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-project-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/include -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Crashlytics -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Fabric -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources/arm64 -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -working-directory/Users/syky/optify/optify-ios -emit-module-doc-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftdoc -Onone -module-name OPTIFY -emit-module-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftmodule -serialize-diagnostics-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.dia -emit-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.d -emit-reference-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.swiftdeps -o /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.o -embed-bitcode-marker
1.	While type-checking 'viewDidLoad' at /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:27:14
2.	While type-checking expression at [/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:47:3 - line:47:156] RangeText="self.fetchedResultsController = FetchedResultsController<Examination>(fetchRequest: fetchRequest, sectionNameKeyPath: "examinationID", cacheName: "cache")"
3.	While loading members for declaration 0x7fc31596e250 at <invalid loc>
4.	While deserializing 'controller' (FuncDecl #157)

I missed an import. That error is fixed now in Roobiq/RBQSafeRealmObject#5 released as 1.0.1. My swift-3 branch is now outdated.

OK, well while Using RBQSafeRealmObject (1.0.1)

File not found in RBQSafeRealmObject.m

Ah, the problem is in the Swift spec. It's including an old file, but resolving that leads to duplicate symbols. I'll have a fix up for the spec later.

Just did

Seg fault:
CompileSwift normal arm64 /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift
    cd /Users/syky/optify/optify-ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/syky/optify/optify-ios/OPTIFY/APIWrapper.swift /Users/syky/optify/optify-ios/OPTIFY/K.swift /Users/syky/optify/optify-ios/OPTIFY/Examination.swift /Users/syky/optify/optify-ios/OPTIFY/ExaminationForm.swift /Users/syky/optify/optify-ios/OPTIFY/AppDelegate.swift -primary-file /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/CustomersTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerValidator.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerForm.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Customer.swift /Users/syky/optify/optify-ios/OPTIFY/Device.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Examination.swift /Users/syky/optify/optify-ios/OPTIFY/Randomizer.swift /Users/syky/optify/optify-ios/OPTIFY/Customer.swift -target arm64-apple-ios9.3 -Xllvm -aarch64-use-tbi -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.1.sdk -I /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Alamofire -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Eureka -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Localize-Swift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/PKHUD -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Realm -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmSwift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmUtilities -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftyJSON -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Validator -F /Users/syky/optify/optify-ios/Pods/Crashlytics/iOS -F /Users/syky/optify/optify-ios/Pods/Fabric/iOS -F /Users/syky/optify/optify-ios/Carthage/Build/iOS -enable-testing -g -module-cache-path /Users/syky/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -D COCOAPODS -D DEBUG -serialize-debugging-options -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-generated-files.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-own-target-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-project-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/include -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Crashlytics -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Fabric -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources/arm64 -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -working-directory/Users/syky/optify/optify-ios -emit-module-doc-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftdoc -Onone -module-name OPTIFY -emit-module-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftmodule -serialize-diagnostics-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.dia -emit-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.d -emit-reference-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.swiftdeps -o /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.o -embed-bitcode-marker

/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:144:109: error: use of undeclared type 'SafeObject'
    public func controller<T : Object>(_ controller: FetchedResultsController<T>, didChangeObject anObject: SafeObject<T>, atIndexPath indexPath: IndexPath, forChangeType type: NSFetchedResultsChangeType, newIndexPath: IndexPath) {
                                                                                ^~~~~~~~~~
/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:151:101: error: use of undeclared type 'SafeObject'
    func controllerDidChangeObject<T : Object>(_ controller: FetchedResultsController<T>, anObject: SafeObject<T>, indexPath: IndexPath?, changeType: NSFetchedResultsChangeType, newIndexPath: IndexPath?) {
                                                                                ^~~~~~~~~~
<built-in>:2:14: note: in module 'RBQFetchedResultsController' imported from <built-in>:3:
#define __clang__ 1
             ^
/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController/RBQFetchedResultsController.framework/Headers/RLMObject+SafeObject.h:16:12: warning: duplicate definition of category 'SafeObject' on interface 'RLMObject'
@interface RLMObject (SafeObject)
           ^
/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject/RBQSafeRealmObject.framework/Headers/RLMObject+SafeObject.h:16:12: note: previous definition is here
@interface RLMObject (SafeObject)
           ^
0  swift                    0x000000010536ea3d PrintStackTraceSignalHandler(void*) + 45
1  swift                    0x000000010536e466 SignalHandler(int) + 470
2  libsystem_platform.dylib 0x00007fffb4e9cbba _sigtramp + 26
3  libsystem_platform.dylib<PHONE_NUMBER>00000000 _sigtramp +<PHONE_NUMBER>
4  swift                    0x0000000102cfb8a6 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 806
5  swift                    0x0000000102cfc610 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 4240
6  swift                    0x0000000102cfb9f3 swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 1139
7  swift                    0x0000000102cfbb2e swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 1454
8  swift                    0x0000000102cfd0dc swift::ModuleFile::getType(llvm::PointerEmbeddedInt<unsigned int, 31>) + 7004
9  swift                    0x0000000102cf9294 swift::ModuleFile::getDecl(llvm::PointerEmbeddedInt<unsigned int, 31>, llvm::Optional<swift::DeclContext*>) + 39268
10 swift                    0x0000000102d04367 swift::ModuleFile::loadAllMembers(swift::Decl*, unsigned long long) + 647
11 swift                    0x0000000102f174ea (anonymous namespace)::hasFailableInits(swift::NominalTypeDecl*, swift::constraints::ConstraintSystem*) + 362
12 swift                    0x0000000102f16fd2 (anonymous namespace)::ConstraintGenerator::visitApplyExpr(swift::ApplyExpr*) + 642
13 swift                    0x0000000102f109d0 (anonymous namespace)::ConstraintWalker::walkToExprPost(swift::Expr*) + 64
14 swift                    0x0000000103089a0c (anonymous namespace)::Traversal::visit(swift::Expr*) + 6812
15 swift                    0x0000000102f0c368 swift::constraints::ConstraintSystem::generateConstraints(swift::Expr*) + 424
16 swift                    0x0000000102f48d0a swift::constraints::ConstraintSystem::solve(swift::Expr*&, swift::Type, swift::ExprTypeCheckListener*, llvm::SmallVectorImpl<swift::constraints::Solution>&, swift::FreeTypeVariableBinding) + 4570
17 swift                    0x0000000102f88f62 swift::TypeChecker::solveForExpression(swift::Expr*&, swift::DeclContext*, swift::Type, swift::FreeTypeVariableBinding, swift::ExprTypeCheckListener*, swift::constraints::ConstraintSystem&, llvm::SmallVectorImpl<swift::constraints::Solution>&, swift::OptionSet<swift::TypeCheckExprFlags, unsigned int>) + 482
18 swift                    0x0000000102f8b576 swift::TypeChecker::typeCheckExpression(swift::Expr*&, swift::DeclContext*, swift::TypeLoc, swift::ContextualTypePurpose, swift::OptionSet<swift::TypeCheckExprFlags, unsigned int>, swift::ExprTypeCheckListener*, swift::constraints::ConstraintSystem*) + 630
19 swift                    0x000000010300dd38 swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 488
20 swift                    0x000000010300cd5d swift::TypeChecker::typeCheckFunctionBodyUntil(swift::FuncDecl*, swift::SourceLoc) + 365
21 swift                    0x00000001030113fc swift::TypeChecker::typeCheckAbstractFunctionBody(swift::AbstractFunctionDecl*) + 188
22 swift                    0x0000000102fc4aba swift::performTypeChecking(swift::SourceFile&, swift::TopLevelContext&, swift::OptionSet<swift::TypeCheckingFlags, unsigned int>, unsigned int, unsigned int) + 6714
23 swift                    0x0000000102c7431b swift::CompilerInstance::performSema() + 5675
24 swift                    0x0000000102717a4d performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&, swift::FrontendObserver*) + 2765
25 swift                    0x0000000102714f70 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 17856
26 swift                    0x00000001026d193e main + 8302
27 libdyld.dylib            0x00007fffb4c8f255 start + 1
Stack dump:
0.	Program arguments: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/syky/optify/optify-ios/OPTIFY/APIWrapper.swift /Users/syky/optify/optify-ios/OPTIFY/K.swift /Users/syky/optify/optify-ios/OPTIFY/Examination.swift /Users/syky/optify/optify-ios/OPTIFY/ExaminationForm.swift /Users/syky/optify/optify-ios/OPTIFY/AppDelegate.swift -primary-file /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/CustomersTableViewController.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerValidator.swift /Users/syky/optify/optify-ios/OPTIFY/NewCustomerForm.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Customer.swift /Users/syky/optify/optify-ios/OPTIFY/Device.swift /Users/syky/optify/optify-ios/OPTIFY/APIWrapper+Examination.swift /Users/syky/optify/optify-ios/OPTIFY/Randomizer.swift /Users/syky/optify/optify-ios/OPTIFY/Customer.swift -target arm64-apple-ios9.3 -Xllvm -aarch64-use-tbi -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.1.sdk -I /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Alamofire -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Eureka -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Localize-Swift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/PKHUD -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RBQSafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Realm -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmSwift -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/RealmUtilities -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SafeRealmObject -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftFetchedResultsController -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/SwiftyJSON -F /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/Validator -F /Users/syky/optify/optify-ios/Pods/Crashlytics/iOS -F /Users/syky/optify/optify-ios/Pods/Fabric/iOS -F /Users/syky/optify/optify-ios/Carthage/Build/iOS -enable-testing -g -module-cache-path /Users/syky/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -D COCOAPODS -D DEBUG -serialize-debugging-options -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-generated-files.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-own-target-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-all-non-framework-target-headers.hmap -Xcc -ivfsoverlay -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/all-product-headers.yaml -Xcc -iquote -Xcc /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/OPTIFY-project-headers.hmap -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Products/Debug-iphoneos/include -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Crashlytics -Xcc -I/Users/syky/optify/optify-ios/Pods/Headers/Public/Fabric -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources/arm64 -Xcc -I/Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/DerivedSources -Xcc -DDEBUG=1 -Xcc -DCOCOAPODS=1 -Xcc -working-directory/Users/syky/optify/optify-ios -emit-module-doc-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftdoc -Onone -module-name OPTIFY -emit-module-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController~partial.swiftmodule -serialize-diagnostics-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.dia -emit-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.d -emit-reference-dependencies-path /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.swiftdeps -o /Users/syky/Library/Developer/Xcode/DerivedData/OPTIFY-gniqdvszrvdjhwaqvfoeylrkkksg/Build/Intermediates/OPTIFY.build/Debug-iphoneos/OPTIFY.build/Objects-normal/arm64/ExaminationsTableViewController.o -embed-bitcode-marker
1.	While type-checking 'viewDidLoad' at /Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:27:14
2.	While type-checking expression at [/Users/syky/optify/optify-ios/OPTIFY/ExaminationsTableViewController.swift:47:3 - line:47:156] RangeText="self.fetchedResultsController = FetchedResultsController<Examination>(fetchRequest: fetchRequest, sectionNameKeyPath: "examinationID", cacheName: "cache")"
3.	While loading members for declaration 0x7fb04422f650 at <invalid loc>
4.	While deserializing 'controller' (FuncDecl #157)

Thanks for this detail! Buried in that output are two issues:

ExaminationsTableViewController.swift:144:109: error: use of undeclared type 'SafeObject'
RBQFetchedResultsController.framework/Headers/RLMObject+SafeObject.h:16:12: warning: duplicate definition of category 'SafeObject' on interface 'RLMObject'

The first issue looks like you need to add an import SafeRealmObject in ExaminationsTableViewController. Previously, both of the safe object libraries were bundled inside the Swift version

I see what's going on here. Since this repo contains 2 distinct pods, you will need 2 Podfile entries to pull in boy prerelease versions.
pod 'RealmSwift'
pod 'RBQFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'
pod 'SwiftFetchedResultsController', git: 'https://github.com/phatblat/RBQFetchedResultsController.git', branch: 'swift-3'
pod 'RBQSafeRealmObject' # not actually necessary now
Currently, you're getting the latest released version of RBQFetchedResultsController, which doesn't have the fixes.

Ou yeah buddy this is first 'Build Succeeded' I see on this project for almost a month.
Good Work 🎉

But, I am getting EXC_BAD_INSTRUCTION now.
in FetchedResultsController.swift

And call stack looks like this:

Yay, progress!  🎉
I'll look into that DelegateProxy init method. That may have been auto-inserted by the Swift 3 migration.

I see what happened here. During migration the NS got stripped off of NSObject, the base class. However, now Object is being interpreted as the RealmSwift.Object class. The fit-its probably prompted me to add the missing required constructors for a Realm model object. As the Realm is initialized, this DelegateProxy is being created since it claims to be part of the schema.

OMG, so much work...

Just tried out the branch and the Swift example which compiles but crashes at:
FetchedResultsController.swift:
/**
    Retrieve the Object for a given index path

    :warning: Returned object is not thread-safe.

    :param: indexPath the index path of the object

    :returns: Object
    */
    open func objectAtIndexPath(_ indexPath: IndexPath) -> T? {

        if let rlmObject = self.rbqFetchedResultsController.object(at: indexPath) {

            return unsafeBitCast(rlmObject, to: T.self)
        }

        return nil
    }

to fix:
/**
    Retrieve the Object for a given index path

    :warning: Returned object is not thread-safe.

    :param: indexPath the index path of the object

    :returns: Object
    */
    open func objectAtIndexPath(_ indexPath: IndexPath) -> T? {

        if let rlmObject = self.rbqFetchedResultsController.object(at: indexPath) {

            return unsafeBitCast(rlmObject as! RLMObjectBase, to: T.self)
        }

        return nil
    }

Also RBQSafeRealmObject needs updated as well: https://github.com/Roobiq/RBQSafeRealmObject/issues/7

RBQSafeRealmObject has been updated to 1.0.3: https://github.com/Roobiq/RBQSafeRealmObject/releases/tag/v1.0.3 (also pushed to Cocoapods)

Thanks for the feedback! I'll see if I can fix these things up this weekend.

How was your weekend?

It's been busy lately, but this is ready for review again.

So I ran my project and I got "Xcode auto correction "syntax" error" with the red dot with white circle inside, so I clicked it, and it autofilled this for me:
/**
     Notifies the delegate that a fetched object has been changed due to an add, remove, move, or update. Enables FetchedResultsController change tracking.

     Changes are reported with the following heuristics:

     On add and remove operations, only the added/removed object is reported. It’s assumed that all objects that come after the affected object are also moved, but these moves are not reported.

     A move is reported when the changed attribute on the object is one of the sort descriptors used in the fetch request. An update of the object is assumed in this case, but no separate update message is sent to the delegate.

     An update is reported when an object’s state changes, but the changed attributes aren’t part of the sort keys.

     :param: controller controller instance that noticed the change on its fetched objects
     :param: anObject changed object represented as a SafeObject for thread safety
     :param: indexPath indexPath of changed object (nil for inserts)
     :param: type indicates if the change was an insert, delete, move, or update
     :param: newIndexPath the destination path for inserted or moved objects, nil otherwise
     */
    public func controller<T : Object>(_ controller: FetchedResultsController<T>, didChangeObject anObject: SafeObject<T>, atIndexPath indexPath: IndexPath?, forChangeType type: NSFetchedResultsChangeType, newIndexPath: IndexPath?) {
        <#code#>
    }

My old protcol method implementation looked like this:
public func controller<T : Object>(_ controller: FetchedResultsController<T>, didChangeObject anObject: SafeObject<T>, atIndexPath indexPath: IndexPath, forChangeType type: NSFetchedResultsChangeType, newIndexPath: IndexPath) {
    }

I can see the change from Optional IndexPath to NonOptional, but I believe that the code documentation should to get pasted into my code :)

And when I build and run the project I am getting SIGABRT in RealmConfiguration.swift:180
With following:
Could not cast value of type 'RBQSectionCacheObject' (0x10e01b560) to 'RealmSwift.Object' (0x10ea16390).

What are the missing pieces to get this change merged?  This is the last piece that our project needs to fully convert to Swift 3 / xCode 8.

This PR is the only thing keeping me from choosing Realm for my projects at work and at home. I know, it's open source and all that, but unless Realm has a drop-in replacement for the fetched results controller, it's a really tough sell to the team.
It would be nice if the nice folks at Realm could supply this and not rely on a third-party to provide it.

Sorry for the delay in finishing this up. I believe all the changes necessary are done, I just haven't been able to test it to verify that everything is working correctly. I'll plan to merge this tomorrow, allowing one last day for feedback.

@phatblat see my last comment I am getting an error

Ah, I'm getting the same error when running the "Swift" (no suffix) example project.
Could not cast value of type 'RBQSectionCacheObject' (0x1096e5a98) to 'RealmSwift.Object' (0x10a19e390).

It's blowing up in toRLMConfiguration when retrieving configuration.objectTypes in order to copy over to rlmConfiguration.objectClasses. It's trying to cast RBQSectionCacheObject to RealmSwift.Object, but it is a subclass of RLMObject.
It looks like RealmSwift assumes that all objects that are part of the schema will be instances of RealmSwift.Object with no mix-and-match of the objc version of the framework. I hope this doesn't mean all the cache objects need to be reimplemented in Swift.

Ok will look into, I am sure I can find a way to convert between the types.

Too bad Realm isn't casting to RLMObjectBase as it's a common super class.

RealmSwiftObject == RealmSwift.Object

What's the reason that these cache objects extend RLMObject? Seems like they aren't part of the schema and don't need to be persisted, just stored temporarily in memory.

Nevermind. I see now that they are being stored in a cacheRealm.

This is actually an odd bug because typically at Realm we don't recommend to mix ObjC and Swift together, so the ObjC class definition actually doesn't play nice with the objectTypes getter in the Realm Swift framework. However, what's ironic is that you wouldn't actually hit this when using RBQFetchedResultsController as a framework because the cache object models would be isolated in the framework.... however, the Swift example the files are included directly in the project!

Ok this is really ugly but using Swift's limited reflection here is how I could get around it:
        // Hack to get around issue with cache objects appearing in Realm
        // when building RBQFRC not as a framework
        let mirror = Mirror(reflecting: configuration)
        for child in mirror.children {
            if "customSchema" == child.label {
                let customSchema = child.value as! RLMSchema

                let schemaSubset = customSchema.objectSchema.filter({ (objectSchema) -> Bool in
                    let cacheObjectNames = ["RBQControllerCacheObject",
                                            "RBQObjectCacheObject",
                                            "RBQSectionCacheObject"]

                    if cacheObjectNames.contains(objectSchema.objectName) {
                        return false
                    }

                    return true
                })

                let objectTypes = schemaSubset.map { $0.objectClass as! Object.Type }

                rlmConfiguration.objectClasses = objectTypes.map { (type) -> AnyClass in
                    return type
                }
            }
        }

With my change this should be good to go to merge 👍

We can remove this hack once a new release of Realm Swift is released that exposes converter functions to support interoperability of Swift and ObjC Realm objects: https://github.com/realm/realm-cocoa/blob/master/RealmSwift/ObjectiveCSupport.swift#L139-L147

Barring surprises, we're planning on releasing Realm Swift 2.1.1 today.

2.1.1 is out: https://github.com/realm/realm-cocoa/releases/tag/v2.1.1

Let's get this fix in for backwards compatibility and then update to use new 2.1.1 APIs

Sounds good

LGTM. Thanks everyone for helping with this long-running PR!

👏🎉🎉


Check the element exists

Check the DOM node exists before attempting to remove it.
Closes #3302.

Hey there,
was this fix already incorporated into Vue.js? I just ran into this and I don't know how to fix it.
Thank you.

@grafa no because it is not recommended that the DOM be manipulated.

Well I'm getting this error when I change data in my grid which is based on v-for. I do use track-by but without luck to get rid of this error.
My opinion is when I do call a method in given variable, the variable should be tested first.
I.e.
cleanup()  {
    if (myString)
        myString.trim()
   ...
}

Its jsut one line of code, one simple test.


Changing the LANG or PRICE for the first time lets flicker all content

It seems all content is re-rendered by switching language or price for the first time for any reason. Maybe that's an issue with current useContext implementation...?

Same issue if we open the header menu for the first time in mobile view. All content seems to be re-rendered then:

It seems this issue based on "embedded fonts" only. By disabling all embedded fonts (just commenting out some lines of code here), all flickering is gone ...


autoconnect setting does not default correctly

If autoconnect is not specified on the connecter the client won't connect.

This belongs on the connector.


[Snyk] Upgrade eslint-plugin-react from 7.34.4 to 7.35.0

Snyk has created this PR to upgrade eslint-plugin-react from 7.34.4 to 7.35.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released on 23 days ago.

Release notes

Package name: eslint-plugin-react

7.35.0 - 2024-07-20Added

support eslint v9 (#3759 @ mdjermanovic)
export flat configs from plugin root and fix flat config crash (#3694 @ bradzacher @ mdjermanovic)
add jsx-props-no-spread-multi (#3724 @ SimonSchick)
forbid-component-props: add propNamePattern to allow / disallow prop name patterns (#3774 @ akulsr0)
jsx-handler-names: support ignoring component names (#3772 @ akulsr0)
version settings: Allow react defaultVersion to be configurable (#3771 @ onlywei)
jsx-closing-tag-location: add line-aligned option (#3777 @ kimtaejin3)
no-danger: add customComponentNames option (#3748 @ akulsr0)

Fixed

no-invalid-html-attribute: substitute placeholders in suggestion messages (#3759 @ mdjermanovic)
sort-prop-types: single line type ending without semicolon (#3784 @ akulsr0)
require-default-props: report when required props have default value (#3785 @ akulsr0)

Changed

[Refactor] variableUtil: Avoid creating a single flat variable scope for each lookup (#3782 @ DanielRosenwasser)

7.34.4 - 2024-07-13Fixed

prop-types: fix className missing in prop validation false negative (#3749 @ akulsr0)
sort-prop-types: Check for undefined before accessing node.typeAnnotation.typeAnnotation (#3779 @ tylerlaprade)

    from eslint-plugin-react GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

This is already in main. I guess Snyk created the PR when the previous one (#244) still had merge conflicts.
Closing.


Update pick-right-solution.md with another Turnkey

Added Nirmata to both On-Prem and Cloud as we offer both solutions

/lgtm
/approve

Hey, @bitbucket90, sorry for jumping the gun, but can you sign the CLA first? Thanks!
/approve cancel

Added to my organization and confirmed emails match. CLA is signed.


7 topics including papers upto 2016

RE and SSBSE included. Need to include ISSTA
Topic 0: model, systems, based, software, approach, design, paper, models, requirements, components
Topic 1: software, engineering, research, development, tools, business, project, web, challenges, process
Topic 2: software, quality, change, study, bug, changes, maintenance, paper, process, development
Topic 3: program, analysis, programs, data, static, dynamic, technique, java, paper, execution
Topic 4: test, testing, cases, techniques, fault, tests, coverage, suite, based, faults
Topic 5: oriented, object, product, languages, aspect, programming, features, feature, concerns, line
Topic 6: code, source, software, approach, information, tool, based, paper, program, tools

ISSTA Included.
Topic 0: software, requirements, engineering, development, process, research, paper, systems, project, quality
Topic 1: model, systems, based, models, approach, paper, components, requirements, software, component
Topic 2: web, applications, security, application, users, user, mobile, client, services, data
Topic 3: test, program, testing, analysis, programs, technique, execution, techniques, based, approach
Topic 4: language, code, object, programming, oriented, program, languages, java, design, reverse
Topic 5: bug, metrics, quality, bugs, reports, software, models, performance, defects, data
Topic 6: code, software, source, developers, approach, information, changes, paper, based, change

Notice topic terms stability

originals, plus updates, and some similar numbering scheme


Set JKAN and opendata.scot to use live data

This is likely to be a CTC24 item.
After the opendata.scot domain and JKAN test setup (see #19 ) . This issue is to point the opendata.scot domain to use the live data we've already collected and are storing in: https://github.com/OpenDataScotland/the_od_bods/blob/main/data/merged_output.csv
This will include:

changing the source of data
customising JKAN to use & display our data features (filesize, owner, sourceURL etc.)
testing to ensure any changes to merged_output.csv WILL be picked up by JKAN and displayed on opendata.scot

@ormiret has done this, all 427 of our original datasets now living happily in JKAN. closing task.


Search for a resource in a group by resource display_name

There is a search_group_by_name(name,group_id=0) and it works
ngwapi = pyngw.Pyngw(ngw_url = 'https://sandbox.nextgis.com', login = 'administrator', password = 'demodemo')
ngwapi.search_group_by_name('Examples',group_id=0)
> 2

the question is how to get an id of a resource, knowing its group_id and display_name of the resourse
Something like:
ngwapi.search_by_name('madcity',group_id=3)
>11

ready #11


Retain zoom & state of the dispatch graph while opening & closing electron side bar

Please add your planning poker estimate with ZenHub @Prasy12


Some fields seem incorrect and the table header layout needs to adjust on the VM detail page

Steps to reproduce:

Create a VM selecting a ubuntu OS
Check on the detail page

Result:

Operating System and Time Zone are populated with Guest agent required, are these expected?
The tables are not in the same header layout

close in favor of https://github.com/rancher/harvester-ui/pull/205


Document whether all interceptors are rerun after refresh

It's a bit unclear from the docs what interceptors are (re-)run once the fresh is done. For example, if we have two interceptors:

Add the Authorization header (e.g. by retrieving a JWT from local storage).
refreshAuthLogic

What happens to

The request that triggered the auth refresh? Does both (1) and (2) get rerun for this request or only interceptors after (2), if any?
Any requests that got paused? Did they get paused before or after (1)?

This is more of an axios-related question as to how the interceptors are running, but as far as I remember (I haven't work with axios for a while now) the request interceptors are no longer ran for the request caught in refreshAuthLogic. Might be work to double-check with the axios thought.


jruby-9.4

Fixes #
This pull introduces/changes:
*
*

Codecov Report
Base: 93.49% // Head: 93.09% // Decreases project coverage by -0.40% :warning:

Coverage data is based on head (0894acc) compared to base (203f272).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1686      +/-   ##
==========================================
- Coverage   93.49%   93.09%   -0.40%
==========================================
  Files         128      128
  Lines        5812     5796      -16
==========================================
- Hits         5434     5396      -38
- Misses        378      400      +22

Impacted Files
Coverage Δ

lib/active_graph/shared/marshal.rb
66.66% <0.00%> (-33.34%)
:arrow_down:

lib/active_graph/core/schema.rb
88.00% <0.00%> (-12.00%)
:arrow_down:

lib/active_graph/core/label.rb
73.80% <0.00%> (-11.08%)
:arrow_down:

lib/active_graph/attribute_set.rb
87.50% <0.00%> (-6.25%)
:arrow_down:

lib/active_graph/core/record.rb
96.00% <0.00%> (-4.00%)
:arrow_down:

lib/active_graph/migrations/schema.rb
92.85% <0.00%> (-3.58%)
:arrow_down:

lib/active_graph/migrations/helpers.rb
93.33% <0.00%> (-3.34%)
:arrow_down:

lib/active_graph/shared/enum.rb
94.80% <0.00%> (-1.35%)
:arrow_down:

lib/active_graph/core/query_clauses.rb
95.36% <0.00%> (-0.52%)
:arrow_down:

lib/active_graph/railtie.rb
73.77% <0.00%> (-0.43%)
:arrow_down:

... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Lint HTML

Currently the HTML is not pure HTML5 (my mistake!!), as, for example, it still includes /> on image tags.
It would be great if we could install an HTML5 linter to catch this now and in future.

This might be difficult since we don't actually have HTML files we have template files that just happen to output HTML. If you're aware of something that can handle that that'd be great, otherwise I'll see what I can find!

https://pypi.python.org/pypi/html-linter/0.1.3 (or something else) with https://github.com/deezer/template-remover ?


address warning and do something extra rather silently run

Addresses this issue by printing the result, so it no longer runs silently.
Also, the build requires a tarball url.  As it is now, it it uses my fork as the source of the pull request since the target exists there.  I propose once this pull request is accepted, I do a followup to change the location of the pull.  I suggest we do this in this order because until the pull request is merged, the build will fail since the new tarball is not in the zot repo.

You are welcome and thanks.  Once its merged, I'll do the followup on the tarball location change.


vue-cli init with some unknown error : Uncaught SyntaxError: Use of const in strict mode.

when I initial a new project, I used commands as follows:
vue init webpack my-pro
cd my-pro/
npm install
npm run dev
then, it shows :
" DONE Compiled successfully in 5653ms
Your application is running here: http://localhost:8080" in command line",
but when I open chrome and address in localhost:8080,
there is an error:
"Uncaught SyntaxError: Use of const in strict mode. "
so, how could I solve it?
ps: node version v8.8.0

Hm, that's weird. Could you just double check that you are using node 8.8.0? As long as you are on node greater than v4, you should be good to go.
Could you just describe your environment a little more? node, npm versions, OS, etc.
Are you running your app from the OS cli or using some IDE?

OK, my OS is ubuntu 14.04.  node v8.8.0 npm 5.4.2, vue 2.9.2.
No one had such a problem before. So confused!!!!!

I can't reproduce this (I'm on OS X though).
Does the error tell you where that syntax error is happening?

Well, I use command "vue init browserify my-bro", and everything's ok.
I'll show you everything  that happend on me.
Ops, why can't I paste any picture here?

I think I got the same error, there are something helpful for me:
https://github.com/webpack/webpack-dev-server/issues/1105
https://github.com/mrdulin/blog/issues/35
there are two way to resolved it:

use webpack-dev-server version 2.7.1;
set babel-loader include webpack-dev-server/client/index.js;

I resolve it like that:
set ./build/webpack.base.config.js
{
  test: /\.js$/,
  loader: 'babel-loader',
  include: [resolve('src'), resolve('test'), resolve('node_modules/webpack-dev-server/client')]
},

Hm, that's a weird choice by the maintainers.
I think we should add this workaround to the template.
Thanks for getting to the bottom of this.

I just pushed that fix to the develop branch, anyone interested can test it out with
vue init webpack#develop

I update my OS to Ubuntu 14.04. and then everything is OK.

Thank you very much!

I met the same problem
and i did it like that
1、use webpack-dev-server version 2.7.1;
2、set babel-loader include webpack-dev-server/client/index.js;
but it did not work, i dont know how to resolve it
who could do me a favor?

I think I got the same error, there are something helpful for me:
webpack/webpack-dev-server#1105
mrdulin/blog#35
there are two way to resolved it:

use webpack-dev-server version 2.7.1;
set babel-loader include webpack-dev-server/client/index.js;

I resolve it like that:
set ./build/webpack.base.config.js
{
  test: /\.js$/,
  loader: 'babel-loader',
  include: [resolve('src'), resolve('test'), resolve('node_modules/webpack-dev-server/client')]
},

我这边设置 没有用啊

I think I got the same error, there are something helpful for me:
webpack/webpack-dev-server#1105
mrdulin/blog#35
there are two way to resolved it:

use webpack-dev-server version 2.7.1;
set babel-loader include webpack-dev-server/client/index.js;

I resolve it like that:
set ./build/webpack.base.config.js
{
  test: /\.js$/,
  loader: 'babel-loader',
  include: [resolve('src'), resolve('test'), resolve('node_modules/webpack-dev-server/client')]
},

我这边设置 没有用啊

我也是不生效


RFC: Fixing ListView with items of varying heights

I've made a small PR to fix a tiny bug in ListView, but actually have more changes ready to _scroll() and populate().
Before I submit the PR, I'd like to ask a few questions:-

Should this behaviour be optional (new BooleanProperty)?
What would the performance hit be (ballpark)?

So firstly, how ListView currently works is that it guesses how big the underlying gridlayout needs to be in populate(). The problem is this calculation only happens when populate is called without a specific istart/iend. And it's a guess. If this is wrong, there's either additional blank space at the bottom of the list or some items don't show.
The thing is, this guess is based on averaging the size of elements, and when the elements have a fixed height (most common scenario) there's no problem. There is a 'sizes' dict which stores real sizes of views, but it isn't used directly in calculating the gridlayout's height.
I believe correct behaviour is to:-
A) Bind a simple function to each view's height (this is so the height of views can change dynamically) which updates the _sizes dict and calls populate()
B) Update container.height on al calls to populate() rather than just calls which do not specify a start/end.
C) The _scroll function also uses estimation to guess which indices to use. Since we have a _sizes dict, we don't need to guess, we can simply iterate and know exactly what indice to show.
I've implemented the above behaviour and am ready to submit a PR once the two questions are answered. I'm particularly concerned about 2) because of the liberal use of bound functions (can be unbound when the itemview is cleared) as well as increased calls to populate, and more accessing of _sizes.

This would solve my problem! Please make this happen!
It would be nice to be able to change the height of list items by selecting them (to see more of their contents).

@fekga, this may be doable in the future with RecycleView (currently possible but a bit tricky to get it right), you could give it a try, unless you must use ListView.
https://github.com/kivy-garden/garden.recycleview

@ngoonee, we are happy to see you contribute, and I also think we should have been clearer about our intentions regarding ListView.
The ListView api is generally ragarded as bad, both by the community and the core devs, and the widget is plagued by dozens of (stalling) issues. This has led to a new initiative, RecycleView. I've recently added a note about RV in the ListView docs to help users discover this new widget.
RV already works quite well for the most general use cases, and there is a plan to improve it and lift it in the main Kivy repo.
This also means people may not be too keen to review ListView issues and prs, and your work may go to waste. I would suggest to focus on other parts of kivy for new contributions to avoid this possibility. TextInput has a nice list of bugs for example.
Thank you for your work, and we are looking forward to future contributions. :wink:

Thanks @dessant, I've noticed how bad performance is for ListView, which resulted in this RFC. Of course, after wrestling with it a bit more someone recommended recycleview, which I'm now using instead of ListView (except in legacy code). I concur that ListView should go away and be replaced by RecycleView, the difference in speed is just obscene.


Ghost 4.22 crashes during startup with a read-only container

Description:
I'm using Ghost in a container (Kubernetes) environment and for better security all containers must run as non-root user and with read-only permissions in this environment.
An upgrade from Ghost 4.21 to 4.22 was not possible. The container crashes during startup with following exception:
[2021-11-11 11:16:42] ERROR EROFS: read-only file system, unlink '/var/lib/ghost/versions/4.22.0/core/frontend/public/cards.min.css'

EROFS: read-only file system, unlink '/var/lib/ghost/versions/4.22.0/core/frontend/public/cards.min.css'

Error ID:
    d929b720-42e0-11ec-9323-f74cb84b376c

Error Code:
    EROFS

How to reproduce:
It is easy to reproduce on a local docker environment.
Create a folder for the Ghost content and mount that to a read-only container of Ghost 4.21:
mkdir content421
docker run -d --name ghost421 --read-only -e url=http://localhost:2368 -p 2368:2368 -v ${PWD}/content421:/var/lib/ghost/content ghost:4.21.0

Ghost 4.21.0 will start up without problems and web should be reachable under http://localhost:2368.
Kill the container to free TCP port 2368:
docker kill ghost421
Doing the same for Ghost 4.22.0 will show the error described above:
mkdir content422
docker run --name ghost422 -d --read-only -e url=http://localhost:2368 -p 2368:2368 -v ${PWD}/content422:/var/lib/ghost/content ghost:4.22.0

Ghost tries to create/access some file outside of the mounted content-folder during startup of V4.22 -- That was not the case with V4.21.
Please analyze and fix!

I'm not sure if "read-only filesystem" is a feature Ghost offers, I'd see if the upstream project has more insight into this https://github.com/TryGhost/Ghost since we only maintain the containerized version of Ghost and aren't affiliated with its development or featureset
If it supports a read-only filesystem outside of a container environment then we could see where the containerized version differs in that regard but otherwise this seems like a side-effect of a code change upstream so I'm not sure if there's anything actionable we could do to remedy it

Hi! 👋🏻 Although I haven't tested, the latest version of Ghost shouldn't have this problem and the issue can be closed.
We had an issue where we dynamically wrote files to the code folder during runtime, which breaks when the container is read-only. Our fix was to change the destination file to the content/public folder. 🙂

Yes.. I can confirm the bug is gone - Tested with Ghost 4.34.x
Thank you!


Out-of-bounds read when no flags are passed to zinit()

An out-of-bounds read occurs when zinit(argv, (Flag[]){}, 0) is called.

Wrong compile of test; not an actual issue


[hotfix] Fix a typo in the watermark docs

FYI: The Chinese version of this file is already translated and, therefore, does not need to be changed.

Thanks for review. Merging ...


[Bug] When switching to new versions of KM and LLamaSharp, there was a slowdown

Context / Scenario
After upgrading from KM 0.61 and LLamaSharp 0.13 to the latest versions, the processing ImportDocumentAsync/AskAsync speed has significantly decreased, almost 2 times.
All settings and equipment are the same. I see that the GPU is now less loaded, previously CUDA was loaded more than 80%.
Import:

Ask:

How do I get back to my previous speed?
Thanks.
What happened?
GPU load is more than 80%
Importance
edge case
Platform, Language, Versions
Operating system: Windows 11
.NET runtime version: 8.0.8
LLamaSharp version: 0.16.0
KernelMemory: 0.71...
CUDA version (if you are using cuda backend): 12
CPU & GPU device: CPU or GPU, Intel Core Ultra 9 & RTX 3090
Relevant log output

hi @aropb you should try loading LLamaSharp backend explicitly, see https://github.com/microsoft/kernel-memory/blob/main/service/Service/Service.csproj
unfortunately llamasharp doesn't allow to load all the backends and choose one at runtime, so you need to compile the code manually, after adding CUDA (in your case).
you could also opt for ollama, which I believe doesn't suffer from this limitation

Everything was done correctly and the backend was installed, of course, because it worked on version 0.13.0 and is working now, but slower!

Unfortunately, I don't understand how I can use something other than LlamaSharp with KM.

nevermind, I spent some time today testing the feasibility of ollama, and unfortunately the underlying OpenAI connector doesn't work with it. Ollama provides an openai compatible endpoint, but the connector we're using in SK/KM doesn't work 100% with, throwing exceptions. About ollama, someone will need to add a new connector, if needed.
About llamasharp perf, I can only suggest reaching out to that project team.

Update: KM v0.72 now includes an Ollama connector, making it extremely easier to work with local models

@aropb there's a new version out with new LLamasharp libs version, in case you want to give it a test

This problem is LLamaSharp


Error code="610"

Good afternoon, I have such a problem that whatever I hiccups, he gives me only this error
I took a sample CRUD SDK substituted all authorization variables
created several invoices in the sandbox and I want to get them from sdk but I get only an error
What's wrong ???
http://joxi.ru/E2peLgXtaMzyXA
http://joxi.ru/krDq4DGSJzeXXm
relID<PHONE_NUMBER>046319180
http://joxi.ru/zANe4VGt6z3oX2
http://joxi.ru/nAyYQ8ofjMKDDA

@lovik1468 Can you send me the app details and realmId? It sounds like the invoice Id 22 might not exist.

What details are you interested in and where can I get them?
On the screenshots you can see that 22 invoice is and is active
Maybe something is wrong with the settings of the sandbox itself
realmId<PHONE_NUMBER>044851490

00019-Request-1587927294-0.txt
00020-Response-1587927296-0.txt
00021-Request-1587929525-0.txt
00022-Response-1587929527-0.txt
Here are the error logs that he gives me I tried to create an invoice and tried to get it
Perhaps something is wrong in my sandbox settings?

Update please, documentation as you might have guessed that the invoice id is not a number but a get parameter when you open it for editing!


[Improvement] YARN_CONF_DIR shall be added to kyuubi server classpath as HADOOP_CONF_DIR

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
YARN_CONF_DIR aslo contains configurations for kyuubi server to respect
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

please assign to me

please assign to me

@jiaoqingbo done, thank you !

please assign to me

@jiaoqingbo done, thank you !

please assign to @SteNicholas，he has submitted a more reasonable pr ，thx

thank you @jiaoqingbo and @SteNicholas !


Cleanup getting started page

Remove user managed cache from getting-started.
Present a full xml including the namespaces.
Talk about XML right after Java.
Other minor formatting on getting-started

No daggy fix was dedided. Now rebased.


un-gzip data when using rest client

there is a header that can be used to identify gzip content:
Content-Encoding: gzip

works for lzma, deflate and gzip. couldn't find brotli library i can easily pull from maven. should be included in next release


categories index RSS doesn't match content

The content of my categories listings doesn't match the content of the XML indexes.
http://www.xaprb.com/categories/databases/
http://www.xaprb.com/categories/databases/index.xml
The index.xml contains the content of all articles, not just those from the category.
You can see my templates on github.com/xaprb/xaprb.com. Under layouts/indexes/ you'll see I have category.xml and category.html. The .xml file seems to be ignored, and the ../rss.xml is used instead. But if I copy ../rss.xml into layouts/indexes/ it is still ignored. I can't figure out how to get a category RSS template to override the global RSS template. On http://hugo.spf13.com/layout/variables there isn't any documentation for .Data.Pages which is what I think I need to access in such an index layout.

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.


stream_settings: Reorder contents in stream settings and create stream UI

Contents in the stream settings and create stream UI are reordered to make it more consistent.
Fixes:  #23327

Screenshots and screen captures:
https://user-images.githubusercontent.com/53159963/201831922-3e62091c-81eb-44cc-9a32-e0d2814d74e9.mov
https://user-images.githubusercontent.com/53159963/201831745-f80afd0f-4afa-4187-a4b5-68b24114e8a5.mov

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

I tested the PR, and it looks good!
The only problem I noticed is that the announcement stream does not live-update if it's changed while the user has the form open. Is that something that could be fixed?

Anyhow, @sahil839 perhaps it makes sense for you to review at this point and comment on the question above as well.

And regarding live updating the announcement stream name, it can be done by adding a function to stream_ui_updates which will be called in server_event_dispatch.js when recieving realm/update event for notifications_stream_id. The new function can just update the label of the setting using jquery or hide the checkbox itself if notification stream setting is disabled.

@Rixant will you have time to update this in the next few days?

@Rixant will you have time to update this in the next few days?

@timabbott , I have been busy for last few weeks. I will works on this long weekend(tomorrow).

@alya @sahil839 Will all streams in announcement stream will have # as a privacy icon?

@alya @sahil839 Will all streams in announcement stream will have # as a privacy icon?

No... You can see for yourself that it's possible to select a private stream for announcements.

@alya @sahil839 Will all streams in announcement stream will have # as a privacy icon?

No... You can see for yourself that it's possible to select a private stream for announcements.

Thanks, Fixed it.

@sahil839 , Could you please review it?

@alya , This is up for review.

The issue #23327 has been updated (sub-task added in the second task) to include the fix for case when announcement stream is private which the user is not subscribed to. It would probably be better to do it in its separate own commit.

@sahil839 , updated.

New PR https://github.com/zulip/zulip/pull/23833 opened in replacement.


API docs still pointing here, despite deprecation

https://apidocs.imgur.com/?version=latest
Under the Example code section, it lists this python project first, as the Official Python library.
If it is deprecated, can that link be removed? I got a fair way through the process before swearing under my breath when realising this repo is deprecated.

Also, if this is deprecated there should be somewhere (easy to access) a link to an alternative.

Quick Google search brings up this project (WIP) https://pypi.org/project/imgur-python/

Almost a year later and their docs are still pointing here :rofl:

Almost a year later and their docs are still pointing here :rofl:

Another year and a half and their docs are still pointing here lol.


Mount syslog config file and update srl and grafana

Due to limitation with go-git on how to handle unix domain sockets, we will now mount the config and not the config dir, such that the syslog-ng.ctl will not show up in the config die on the host and thereby go-git will not have to mess with it.

good stuff, thnx
i updated some containers in this PR as well.


Update version number

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 49.67%. Comparing base (1f97be0) to head (92a9f5f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #399   +/-   ##
=======================================
  Coverage   49.67%   49.67%
=======================================
  Files           9        9
  Lines         781      781
=======================================
  Hits          388      388
  Misses        383      383
  Partials       10       10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feat(kclvm-windows): Add konfig test for windows.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

issue #379

2. What is the scope of this PR (e.g. component or file name):

Add Konfig test for windows.
Konfig - https://github.com/KusionStack/konfig
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[x] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.562%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1612

Relevant Lines:
1780

💛  - Coveralls


my project messy with new update

whats happen? why???

It's not a good way to use “with”. At that time, I was just learning about Flutter. The new version of Flutter is modeled after the official JSON plugin. It will be more helpful for adding more functions in the future. Of course the inevitable user will update something, sorry about that


Cannot enqueue Handshake after already enqueuing a Hand shake. question

Hello,
how to fix this err?
error connecting: Error: Cannot enqueue Handshake after already enqueuing a Hand
shake.
I call MYSQL in callback :(

This is not related to steam-tradeoffers.


Inconsistency in keep argument for save_checkpoint and save_checkpoint_multiprocess

There seems to be an inconsistency in keep argument for save_checkpoint and save_checkpoint_multiprocess
System information
Internal
Problem you have encountered:
I am trying to migrate to using the Orbax Checkpointer w flax.save_checkpoint_multiprocess and have noticed an inconsistency in behavior between

current and past behavior w flax checkpointing
save_checkpoint and save_checkpoint_multiprocess

The method save_checkpoint calls save first for the current checkpoint and then removes excessive checkpoints, but the save_checkpoint_multiprocess calls remove first and then saves the current checkpoint.
What you expected to happen:
In the past when specifying keep=N for the save method, the number of checkpoints at the end of the save_checkpoint call was equal to N. Currently when calling save_checkpoint_multiprocess.py the number of checkpoints after the save is equal to N+1.
Logs, error messages, etc:
Internal

In save_checkpoint_multiprocess, we remove old checkpoints before writing new ones, which results in the total number of checkpoints to be keep+1. This is because Orbax AsyncCheckpointer does not support custom on-commit callback and it is impossible to explicitly delete old checkpoints after the current checkpoint is async-saved.
In save_checkpoint, the removal always happens after save, and we kept it that way for backward compatibility. Maybe it makes more sense to unify the behavior. Either way, I should make it more explicit in the API doc.


docs: promql compatibility list

Signed-off-by: Ruihang Xia<EMAIL_ADDRESS>Add the PromQL compatibility list page

@Wenjie0329 Please take a look

Hi, @waynexia. Are you still working on this PR? If it's ready for review, we can do it.

Hi, @waynexia. Are you still working on this PR? If it's ready for review, we can do it.

Thanks for reminding. I'm improving the compatibility these days, which may continue for around 1~2 weeks. During this period, this document may require rapid changes, so I plan to update it after the functionality is stable. I'll convert this PR to draft for now.

I've updated this doc, PTAL again 🙇♂

@xtang @Wenjie0329 Can we merge this PR? Looks like it's ok.


./do.sh lint throws errors for keygenerator.js and rsaes.js

Running Closure linter on current codebase throws a few errors. This is a known issue and will be fixed shortly with a new release of linter. Please do not correct the code in the following files:
./do.sh lint
Running Closure Linter...
----- FILE  :  ./src/javascript/crypto/e2e/openpgp/keygenerator.js -----
Line 88, E:0002: Missing space before "("
Line 101, E:0002: Missing space before "("
Line 116, E:0002: Missing space before "("
Line 118, E:0002: Missing space before "("
----- FILE  :  ./src/javascript/crypto/e2e/scheme/rsaes.js -----
Line 55, E:0002: Missing space before "("
Line 71, E:0002: Missing space before "("
Found 6 errors, including 0 new errors, in 2 files (278 files OK).

The installation code for Closure linter are (temporarily) outdated. In order to install the newest version of Closure Linter, instead of:
sudo easy_install http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz

one should do
sudo apt-get install python-pip
sudo pip install https://closure-linter.googlecode.com/svn/trunk/

which installs directly from the latest HEAD of the src repository.


prompt: update powerlevel10k submodule to v1.16.0

Release notes:

https://github.com/romkatv/powerlevel10k/releases/tag/v1.16.0

LGTM! Thanks!


Add support for AES CFB mode in _CryptoExtras

Motivation
We have AES support in _CryptoExtras for CBC, CTR, and GCM-SIV modes; but we do not have support for CFB.
Modifications

Add support for AES-CFB, backed by BoringSSL, with the same shape of API as we provide for AES CTR.
Copy RFCVector decoder from Crypto tests to CryptoExtrasTests.
Add test vectors from NIST.

Result
New API added to support AES-CFB.

Thanks @Lukasa I just push an update that renamed Nonce to IV, throughout. Otherwise no changes since your review. I'll leave it with you to merge whenever it's a good time.


fix: Updated sm size for DatePicker, Input, Number Input, and Search Input

Description
Previously, Form input elements had different sm sizes.
Button             -> 24px
Datepicker      -> 22px
Input                -> 22px
Search Input   -> 28px
Number Input -> 22px
Select              -> 24px
This PR updates all these to 24px.
Fixes https://github.com/appsmithorg/appsmith/issues/34599
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual on storybook
Manual on main repo
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] 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
[ ] New and existing unit tests pass locally with my changes

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/generate-alpha


Add head-tag attributes

Hi,
is it possible to add head-tag attributes (ex.  for ogp)?
Use case:
<head prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb# article: http://ogp.me/ns/article#">
</head>

thanks.

It's possible yes, just use headAttrs :)


[v4] Introduce variable for customizing margin-bottom for "p"

_reboot.scss has:
p {
  margin-top: 0;
  margin-bottom: 1rem;
}

However the value is hardcoded. It would be nice to have it exported to _variables.scss so that people can customize (_custom.scss was nice but looks like it's removed now).

It's the same with breadcrumb, as I reported in issue #23016

I'd also like to see this change. Personally I like having the same margin for lots of block-level elements. p, figure, ul, ol, table, etc. I think that bootstrap3 based these margin-bottoms off of $line-height-computed (sometimes ($line-height-computed / 2)). Either way, it seems like a var is more flexible and clean than overriding css.

I would like to work on this for beta 2

Sorry @BhaveshSGupta but I'm already working on this alognwith https://github.com/twbs/bootstrap/issues/23016

@BhaveshSGupta Sorry but I was already working on this. I just noticed your comment.

Should be able to manage margin-bottom of  and  in the same way, no?


Stable/newton

@pjbreaux this is a merge forward from mitaka

Here's a link to the tests demonstrating success:
http://jenkins.pdbld.f5net.com/job/openstack/job/driver/job/newton/job/za_test_11.6.1_undercloud_vxlan/7/console

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@pjbreaux your button await-eth in its most green state.

@zancas: Please provide a full commit message.

@pjbreaux look!