swiftCompatibility50 and swiftCompatibilityDynamicReplacements error

Description
I get the following error after updating xcode to 11.0 (11A420a)
Undefined symbols for architecture x86_64:
  "__swift_FORCE_LOAD_$_swiftCompatibility50", referenced from:
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(AnimatedButton.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(AnimatedControl.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(AnimationSubview.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(CompatibleAnimationView.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(CompositionLayer.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(NullCompositionLayer.o)
      __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie in liblottie-ios.a(ImageCompositionLayer.o)
      ...
     (maybe you meant: __swift_FORCE_LOAD_$_swiftCompatibility50_$_lottie_react_native
, __swift_FORCE_LOAD_$_swiftCompatibility50_$_Lottie
)
  "__swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements", referenced from:
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(AnimatedButton.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(AnimatedControl.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(AnimationSubview.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(CompatibleAnimationView.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(CompositionLayer.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(NullCompositionLayer.o)
      __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie in liblottie-ios.a(ImageCompositionLayer.o)
      ...
     (maybe you meant: __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_lottie_react_native
, __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements_$_Lottie
)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I tried the solution of https://stackoverflow.com/questions/52536380/why-linker-link-static-libraries-with-errors-ios, but
Adding the following to Library search paths doesn't work
$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
Same for
$(TOOLCHAIN_DIR)/usr/lib/swift-5/$(PLATFORM_NAME)
I also created the bridge file, but still getting the above error.
Steps to Reproduce
package.json
"lottie-ios": "^3.1.3",
"lottie-react-native": "git+https://github.com/react-native-community/lottie-react-native.git",

yarn
cd ios && pod install
react-native run-ios

Versions
node: v10.16.0
yarn: 1.17.3

@let-aurn what worked for me is

remove Library search paths $(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
create Swift bridge file

 "lottie-ios": "3.1.3",
 "lottie-react-native": "^3.2.1"

4) Clean project
5) Build

Now I have more other errors now...

Click to see
 "Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.String.Type, forKey: A) throws -> Swift.String?", referenced from:
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      Lottie.ShapeItem.init(from: Swift.Decoder) throws -> Lottie.ShapeItem in liblottie-ios.a(ShapeItem.o)
      Lottie.TextAnimator.init(from: Swift.Decoder) throws -> Lottie.TextAnimator in liblottie-ios.a(TextAnimator.o)
  "Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Bool.Type, forKey: A) throws -> Swift.Bool?", referenced from:
      Lottie.BezierPath.init(from: Swift.Decoder) throws -> Lottie.BezierPath in liblottie-ios.a(BezierPath.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      Lottie.Mask.init(from: Swift.Decoder) throws -> Lottie.Mask in liblottie-ios.a(Mask.o)
      Lottie.ShapeItem.init(from: Swift.Decoder) throws -> Lottie.ShapeItem in liblottie-ios.a(ShapeItem.o)
      Lottie.TextDocument.init(from: Swift.Decoder) throws -> Lottie.TextDocument in liblottie-ios.a(TextDocument.o)
  "Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Double.Type, forKey: A) throws -> Swift.Double?", referenced from:
      Lottie.GradientStroke.init(from: Swift.Decoder) throws -> Lottie.GradientStroke in liblottie-ios.a(GradientStroke.o)
      Lottie.KeyframeData.init(from: Swift.Decoder) throws -> Lottie.KeyframeData<A> in liblottie-ios.a(Keyframe.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      Lottie.Stroke.init(from: Swift.Decoder) throws -> Lottie.Stroke in liblottie-ios.a(Stroke.o)
      Lottie.TextDocument.init(from: Swift.Decoder) throws -> Lottie.TextDocument in liblottie-ios.a(TextDocument.o)
  "Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Int.Type, forKey: A) throws -> Swift.Int?", referenced from:
      Lottie.KeyframeData.init(from: Swift.Decoder) throws -> Lottie.KeyframeData<A> in liblottie-ios.a(Keyframe.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
  "Swift.KeyedDecodingContainer.decodeIfPresent<A where A1: Swift.Decodable>(_: A1.Type, forKey: A) throws -> A1?", referenced from:
      Lottie.Animation.init(from: Swift.Decoder) throws -> Lottie.Animation in liblottie-ios.a(Animation.o)
      Lottie.Ellipse.init(from: Swift.Decoder) throws -> Lottie.Ellipse in liblottie-ios.a(Ellipse.o)
      Lottie.Fill.init(from: Swift.Decoder) throws -> Lottie.Fill in liblottie-ios.a(FillI.o)
      Lottie.GradientFill.init(from: Swift.Decoder) throws -> Lottie.GradientFill in liblottie-ios.a(GradientFill.o)
      Lottie.GradientStroke.init(from: Swift.Decoder) throws -> Lottie.GradientStroke in liblottie-ios.a(GradientStroke.o)
      Lottie.KeyframeData.init(from: Swift.Decoder) throws -> Lottie.KeyframeData<A> in liblottie-ios.a(Keyframe.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      ...
  "Swift.KeyedDecodingContainer.decode(_: Swift.String.Type, forKey: A) throws -> Swift.String", referenced from:
      Lottie.Animation.init(from: Swift.Decoder) throws -> Lottie.Animation in liblottie-ios.a(Animation.o)
      Lottie.Asset.init(from: Swift.Decoder) throws -> Lottie.Asset in liblottie-ios.a(Asset.o)
      Lottie.Font.init(from: Swift.Decoder) throws -> Lottie.Font in liblottie-ios.a(Font.o)
      Lottie.Glyph.init(from: Swift.Decoder) throws -> Lottie.Glyph in liblottie-ios.a(Glyph.o)
      Lottie.ImageAsset.init(from: Swift.Decoder) throws -> Lottie.ImageAsset in liblottie-ios.a(ImageAsset.o)
      Lottie.ImageLayerModel.init(from: Swift.Decoder) throws -> Lottie.ImageLayerModel in liblottie-ios.a(ImageLayerModel.o)
      Lottie.Marker.init(from: Swift.Decoder) throws -> Lottie.Marker in liblottie-ios.a(Marker.o)
      ...
  "Swift.KeyedDecodingContainer.decode(_: Swift.Double.Type, forKey: A) throws -> Swift.Double", referenced from:
      Lottie.Animation.init(from: Swift.Decoder) throws -> Lottie.Animation in liblottie-ios.a(Animation.o)
      Lottie.Font.init(from: Swift.Decoder) throws -> Lottie.Font in liblottie-ios.a(Font.o)
      Lottie.Glyph.init(from: Swift.Decoder) throws -> Lottie.Glyph in liblottie-ios.a(Glyph.o)
      Lottie.ImageAsset.init(from: Swift.Decoder) throws -> Lottie.ImageAsset in liblottie-ios.a(ImageAsset.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      Lottie.PreCompLayerModel.init(from: Swift.Decoder) throws -> Lottie.PreCompLayerModel in liblottie-ios.a(PreCompLayerModel.o)
      Lottie.SolidLayerModel.init(from: Swift.Decoder) throws -> Lottie.SolidLayerModel in liblottie-ios.a(SolidLayerModel.o)
      ...
  "Swift.KeyedDecodingContainer.decode(_: Swift.Int.Type, forKey: A) throws -> Swift.Int", referenced from:
      Lottie.Animation.init(from: Swift.Decoder) throws -> Lottie.Animation in liblottie-ios.a(Animation.o)
      Lottie.Asset.init(from: Swift.Decoder) throws -> Lottie.Asset in liblottie-ios.a(Asset.o)
      Lottie.GradientFill.init(from: Swift.Decoder) throws -> Lottie.GradientFill in liblottie-ios.a(GradientFill.o)
      Lottie.GradientStroke.init(from: Swift.Decoder) throws -> Lottie.GradientStroke in liblottie-ios.a(GradientStroke.o)
      Lottie.LayerModel.init(from: Swift.Decoder) throws -> Lottie.LayerModel in liblottie-ios.a(LayerModel.o)
      Lottie.TextDocument.init(from: Swift.Decoder) throws -> Lottie.TextDocument in liblottie-ios.a(TextDocument.o)
  "Swift.KeyedDecodingContainer.decode<A where A1: Swift.Decodable>(_: A1.Type, forKey: A) throws -> A1", referenced from:
      Lottie.Animation.init(from: Swift.Decoder) throws -> Lottie.Animation in liblottie-ios.a(Animation.o)
      Lottie.DashElement.init(from: Swift.Decoder) throws -> Lottie.DashElement in liblottie-ios.a(DashPattern.o)
      Lottie.Ellipse.init(from: Swift.Decoder) throws -> Lottie.Ellipse in liblottie-ios.a(Ellipse.o)
      Lottie.Fill.init(from: Swift.Decoder) throws -> Lottie.Fill in liblottie-ios.a(FillI.o)
      Lottie.FontList.init(from: Swift.Decoder) throws -> Lottie.FontList in liblottie-ios.a(Font.o)
      Lottie.GradientFill.init(from: Swift.Decoder) throws -> Lottie.GradientFill in liblottie-ios.a(GradientFill.o)
      Lottie.GradientStroke.init(from: Swift.Decoder) throws -> Lottie.GradientStroke in liblottie-ios.a(GradientStroke.o)
      ...

Here's the full list of the headlines (without the details)

Click to see
"protocol descriptor for Swift._SwiftNewtypeWrapper", referenced from:
"base conformance descriptor for Swift._SwiftNewtypeWrapper: Swift.RawRepresentable", referenced from:
"base conformance descriptor for Swift._SwiftNewtypeWrapper: Swift._HasCustomAnyHashableRepresentation", referenced from:
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.RawValue: Swift.Hashable>.hashValue.getter : Swift.Int", referenced from:
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.RawValue: Swift.Hashable>._rawHashValue(seed: Swift.Int) -> Swift.Int", referenced from:
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.RawValue: Swift.Hashable>._toCustomAnyHashable() -> Swift.AnyHashable?", referenced from:
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A: Swift.Hashable, A.RawValue: Swift.Hashable>.hash(into: inout Swift.Hasher) -> ()", referenced from:
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._forceBridgeFromObjectiveC(_: A.RawValue._ObjectiveCType, result: inout A?) -> ()", referenced from:
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._conditionallyBridgeFromObjectiveC(_: A.RawValue._ObjectiveCType, result: inout A?) -> Swift.Bool", referenced from:
"static (extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._unconditionallyBridgeFromObjectiveC(A.RawValue._ObjectiveCType?) -> A", referenced from:
"(extension in Swift):Swift._SwiftNewtypeWrapper< where A.RawValue: Swift._ObjectiveCBridgeable>._bridgeToObjectiveC() -> A.RawValue._ObjectiveCType", referenced from:
"protocol descriptor for Swift._ObjectiveCBridgeable", referenced from:
"method descriptor for static Swift._ObjectiveCBridgeable._forceBridgeFromObjectiveC(_: A._ObjectiveCType, result: inout A?) -> ()", referenced from:
"method descriptor for static Swift._ObjectiveCBridgeable._conditionallyBridgeFromObjectiveC(_: A._ObjectiveCType, result: inout A?) -> Swift.Bool", referenced from:
"method descriptor for static Swift._ObjectiveCBridgeable._unconditionallyBridgeFromObjectiveC(A._ObjectiveCType?) -> A", referenced from:
"method descriptor for Swift._ObjectiveCBridgeable._bridgeToObjectiveC() -> A._ObjectiveCType", referenced from:
"Swift._convertToAnyHashable<A where A: Swift.Hashable>(A) -> Swift.AnyHashable", referenced from:
"Swift._findStringSwitchCase(cases: [Swift.StaticString], string: Swift.String) -> Swift.Int", referenced from:
"Swift.KeyedDecodingContainer.nestedUnkeyedContainer(forKey: A) throws -> Swift.UnkeyedDecodingContainer", referenced from:
"Swift.KeyedDecodingContainer.nestedContainer<A where A1: Swift.CodingKey>(keyedBy: A1.Type, forKey: A) throws -> Swift.KeyedDecodingContainer<A1>", referenced from:
"Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.String.Type, forKey: A) throws -> Swift.String?", referenced from:
"Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Bool.Type, forKey: A) throws -> Swift.Bool?", referenced from:
"Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Double.Type, forKey: A) throws -> Swift.Double?", referenced from:
"Swift.KeyedDecodingContainer.decodeIfPresent(_: Swift.Int.Type, forKey: A) throws -> Swift.Int?", referenced from:
"Swift.KeyedDecodingContainer.decodeIfPresent<A where A1: Swift.Decodable>(_: A1.Type, forKey: A) throws -> A1?", referenced from:
"Swift.KeyedDecodingContainer.decode(_: Swift.String.Type, forKey: A) throws -> Swift.String", referenced from:
"Swift.KeyedDecodingContainer.decode(_: Swift.Double.Type, forKey: A) throws -> Swift.Double", referenced from:
"Swift.KeyedDecodingContainer.decode(_: Swift.Int.Type, forKey: A) throws -> Swift.Int", referenced from:
"Swift.KeyedDecodingContainer.decode<A where A1: Swift.Decodable>(_: A1.Type, forKey: A) throws -> A1", referenced from:
"Swift.KeyedDecodingContainer.contains(A) -> Swift.Bool", referenced from:
"type metadata accessor for Swift.KeyedDecodingContainer", referenced from:
"protocol conformance descriptor for Swift.KeyedDecodingContainer<A> : Swift.KeyedDecodingContainerProtocol in Swift", referenced from:
"Swift.KeyedEncodingContainer.nestedUnkeyedContainer(forKey: A) -> Swift.UnkeyedEncodingContainer", referenced from:
"Swift.KeyedEncodingContainer.nestedContainer<A where A1: Swift.CodingKey>(keyedBy: A1.Type, forKey: A) -> Swift.KeyedEncodingContainer<A1>", referenced from:
"Swift.KeyedEncodingContainer.encodeIfPresent(_: Swift.Bool?, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encodeIfPresent(_: Swift.Double?, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encodeIfPresent(_: Swift.Int?, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encodeIfPresent<A where A1: Swift.Encodable>(_: A1?, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encode(_: Swift.String, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encode(_: Swift.Bool, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encode(_: Swift.Double, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encode(_: Swift.Int, forKey: A) throws -> ()", referenced from:
"Swift.KeyedEncodingContainer.encode<A where A1: Swift.Encodable>(_: A1, forKey: A) throws -> ()", referenced from:
"type metadata accessor for Swift.KeyedEncodingContainer", referenced from:
"Swift._ContiguousArrayBuffer.firstElementAddress.getter : Swift.UnsafeMutablePointer<A>", referenced from:
"Swift._ContiguousArrayBuffer.owner.getter : Swift.AnyObject", referenced from:
"protocol descriptor for Swift.CustomStringConvertible", referenced from:
"method descriptor for Swift.CustomStringConvertible.description.getter : Swift.String", referenced from:
"dispatch thunk of Swift.UnkeyedDecodingContainer.nestedContainer<A where A1: Swift.CodingKey>(keyedBy: A1.Type) throws -> Swift.KeyedDecodingContainer<A1>", referenced from:
"dispatch thunk of Swift.UnkeyedDecodingContainer.count.getter : Swift.Int?", referenced from:
"dispatch thunk of Swift.UnkeyedDecodingContainer.decode(Swift.Double.Type) throws -> Swift.Double", referenced from:
"dispatch thunk of Swift.UnkeyedDecodingContainer.decode<A where A1: Swift.Decodable>(A1.Type) throws -> A1", referenced from:
"dispatch thunk of Swift.UnkeyedDecodingContainer.isAtEnd.getter : Swift.Bool", referenced from:
"dispatch thunk of Swift.UnkeyedEncodingContainer.encode<A where A1: Swift.Sequence, A1.Element: Swift.Encodable>(contentsOf: A1) throws -> ()", referenced from:
"dispatch thunk of Swift.UnkeyedEncodingContainer.encode(Swift.Double) throws -> ()", referenced from:
"dispatch thunk of Swift.UnkeyedEncodingContainer.encode<A where A1: Swift.Encodable>(A1) throws -> ()", referenced from:
"protocol descriptor for Swift.ExpressibleByArrayLiteral", referenced from:
"method descriptor for Swift.ExpressibleByArrayLiteral.init(arrayLiteral: A.ArrayLiteralElement...) -> A", referenced from:
"enum case for Swift.FloatingPointRoundingRule.towardZero(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"enum case for Swift.FloatingPointRoundingRule.awayFromZero(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"enum case for Swift.FloatingPointRoundingRule.toNearestOrEven(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"enum case for Swift.FloatingPointRoundingRule.toNearestOrAwayFromZero(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"enum case for Swift.FloatingPointRoundingRule.up(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"enum case for Swift.FloatingPointRoundingRule.down(Swift.FloatingPointRoundingRule.Type) -> Swift.FloatingPointRoundingRule", referenced from:
"type metadata accessor for Swift.FloatingPointRoundingRule", referenced from:
"Swift.DefaultStringInterpolation.appendInterpolation<A where A: Swift.CustomStringConvertible>(A) -> ()", referenced from:
"Swift.DefaultStringInterpolation.appendLiteral(Swift.String) -> ()", referenced from:
"Swift.DefaultStringInterpolation.init(literalCapacity: Swift.Int, interpolationCount: Swift.Int) -> Swift.DefaultStringInterpolation", referenced from:
"Swift._stdlib_isOSVersionAtLeast(Builtin.Word, Builtin.Word, Builtin.Word) -> Builtin.Int1", referenced from:
"Swift._allocateUninitializedArray<A>(Builtin.Word) -> ([A], Builtin.RawPointer)", referenced from:
"Swift._bridgeAnythingToObjectiveC<A>(A) -> Swift.AnyObject", referenced from:
"protocol descriptor for Swift.CustomDebugStringConvertible", referenced from:
"method descriptor for Swift.CustomDebugStringConvertible.debugDescription.getter : Swift.String", referenced from:
"dispatch thunk of Swift.SingleValueDecodingContainer.decode(Swift.Double.Type) throws -> Swift.Double", referenced from:
"dispatch thunk of Swift.SingleValueEncodingContainer.encode(Swift.Double) throws -> ()", referenced from:
"Swift.== infix<A where A: Swift.RawRepresentable, A.RawValue: Swift.Equatable>(A, A) -> Swift.Bool", referenced from:
"Swift.== infix(Any.Type?, Any.Type?) -> Swift.Bool", referenced from:
"protocol descriptor for Swift._HasCustomAnyHashableRepresentation", referenced from:
"method descriptor for Swift._HasCustomAnyHashableRepresentation._toCustomAnyHashable() -> Swift.AnyHashable?", referenced from:
"Swift.abs<A where A: Swift.Comparable, A: Swift.SignedNumeric>(A) -> A", referenced from:
"Swift.max<A where A: Swift.Comparable>(A, A) -> A", referenced from:
"Swift.max<A where A: Swift.Comparable>(A, A, A, A...) -> A", referenced from:
"Swift.min<A where A: Swift.Comparable>(A, A) -> A", referenced from:
"Swift.min<A where A: Swift.Comparable>(A, A, A, A...) -> A", referenced from:
"protocol descriptor for Swift.Error", referenced from:
"method descriptor for Swift.Error._getEmbeddedNSError() -> Swift.AnyObject?", referenced from:
"method descriptor for Swift.Error._code.getter : Swift.Int", referenced from:
"method descriptor for Swift.Error._domain.getter : Swift.String", referenced from:
"method descriptor for Swift.Error._userInfo.getter : Swift.AnyObject?", referenced from:
"(extension in Swift):Swift.Error._getEmbeddedNSError() -> Swift.AnyObject?", referenced from:
"(extension in Swift):Swift.Error._code.getter : Swift.Int", referenced from:
"(extension in Swift):Swift.Error._domain.getter : Swift.String", referenced from:
"(extension in Swift):Swift.Error._userInfo.getter : Swift.AnyObject?", referenced from:
"Swift.print(_: Any..., separator: Swift.String, terminator: Swift.String) -> ()", referenced from:
"Swift.Hasher.combine<A where A: Swift.Hashable>(A) -> ()", referenced from:
"type metadata for Swift.UInt32", referenced from:
"protocol witness table for Swift.UInt32 : Swift.Equatable in Swift", referenced from:
"protocol conformance descriptor for Swift.UInt32 : Swift.BinaryInteger in Swift", referenced from:
"protocol conformance descriptor for Swift.UInt32 : Swift.FixedWidthInteger in Swift", referenced from:
"Swift.stride<A where A: Swift.Strideable>(from: A, to: A, by: A.Stride) -> Swift.StrideTo<A>", referenced from:
"dispatch thunk of Swift.Decoder.unkeyedContainer() throws -> Swift.UnkeyedDecodingContainer", referenced from:
"dispatch thunk of Swift.Decoder.singleValueContainer() throws -> Swift.SingleValueDecodingContainer", referenced from:
"dispatch thunk of Swift.Decoder.container<A where A1: Swift.CodingKey>(keyedBy: A1.Type) throws -> Swift.KeyedDecodingContainer<A1>", referenced from:
"dispatch thunk of Swift.Encoder.unkeyedContainer() -> Swift.UnkeyedEncodingContainer", referenced from:
"dispatch thunk of Swift.Encoder.singleValueContainer() -> Swift.SingleValueEncodingContainer", referenced from:
"dispatch thunk of Swift.Encoder.container<A where A1: Swift.CodingKey>(keyedBy: A1.Type) -> Swift.KeyedEncodingContainer<A1>", referenced from:
"Swift.StrideTo.makeIterator() -> Swift.StrideToIterator<A>", referenced from:
"type metadata accessor for Swift.StrideTo", referenced from:
"protocol descriptor for Swift.CodingKey", referenced from:
"method descriptor for Swift.CodingKey.stringValue.getter : Swift.String", referenced from:
"method descriptor for Swift.CodingKey.init(stringValue: Swift.String) -> A?", referenced from:
"method descriptor for Swift.CodingKey.intValue.getter : Swift.Int?", referenced from:
"method descriptor for Swift.CodingKey.init(intValue: Swift.Int) -> A?", referenced from:
"base conformance descriptor for Swift.CodingKey: Swift.CustomStringConvertible", referenced from:
"base conformance descriptor for Swift.CodingKey: Swift.CustomDebugStringConvertible", referenced from:
"(extension in Swift):Swift.CodingKey.description.getter : Swift.String", referenced from:
"(extension in Swift):Swift.CodingKey.debugDescription.getter : Swift.String", referenced from:
"protocol descriptor for Swift.OptionSet", referenced from:
"method descriptor for Swift.OptionSet.init(rawValue: A.RawValue) -> A", referenced from:
"base conformance descriptor for Swift.OptionSet: Swift.RawRepresentable", referenced from:
"base conformance descriptor for Swift.OptionSet: Swift.SetAlgebra", referenced from:
"(extension in Swift):Swift.OptionSet< where A == A.Element>.insert(A) -> (inserted: Swift.Bool, memberAfterInsert: A)", referenced from:
"(extension in Swift):Swift.OptionSet< where A == A.Element>.remove(A) -> A?", referenced from:
"(extension in Swift):Swift.OptionSet< where A == A.Element>.update(with: A) -> A?", referenced from:
"(extension in Swift):Swift.OptionSet< where A == A.Element>.contains(A) -> Swift.Bool", referenced from:
"(extension in Swift):Swift.OptionSet.intersection(A) -> A", referenced from:
"(extension in Swift):Swift.OptionSet.symmetricDifference(A) -> A", referenced from:
"(extension in Swift):Swift.OptionSet.union(A) -> A", referenced from:
"(extension in Swift):Swift.OptionSet< where A.RawValue: Swift.FixedWidthInteger>.formIntersection(A) -> ()", referenced from:
"(extension in Swift):Swift.OptionSet< where A.RawValue: Swift.FixedWidthInteger>.formSymmetricDifference(A) -> ()", referenced from:
"(extension in Swift):Swift.OptionSet< where A.RawValue: Swift.FixedWidthInteger>.formUnion(A) -> ()", referenced from:
"(extension in Swift):Swift.OptionSet< where A.RawValue: Swift.FixedWidthInteger>.init() -> A", referenced from:
"protocol conformance descriptor for <A where A: Swift.Encodable> A? : Swift.Encodable in Swift", referenced from:
"type metadata for Swift.AnyObject", referenced from:
"type metadata for Any", referenced from:
"_OBJC_CLASS_$__TtCs12_SwiftObject", referenced from:
"_OBJC_METACLASS_$__TtCs12_SwiftObject", referenced from:
"__swiftEmptyArrayStorage", referenced from:
"__swift_FORCE_LOAD_$_swiftCompatibility50", referenced from:
"__swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements", referenced from:
"__swift_stdlib_reportUnimplementedInitializerInFile", referenced from:
"_swift_allocBox", referenced from:
"_swift_allocError", referenced from:
"_swift_allocObject", referenced from:
"_swift_allocateGenericClassMetadata", referenced from:
"_swift_allocateGenericValueMetadata", referenced from:
"_swift_beginAccess", referenced from:
"_swift_bridgeObjectRelease", referenced from:
"_swift_bridgeObjectRetain", referenced from:
"_swift_checkMetadataState", referenced from:
"_swift_deallocClassInstance", referenced from:
"_swift_deallocObject", referenced from:
"_swift_deallocPartialClassInstance", referenced from:
"_swift_dynamicCast", referenced from:
"_swift_dynamicCastClass", referenced from:
"_swift_dynamicCastMetatype", referenced from:
"_swift_dynamicCastObjCClassUnconditional", referenced from:
"_swift_endAccess", referenced from:
"_swift_errorRelease", referenced from:
"_swift_errorRetain", referenced from:
"_swift_getEnumTagSinglePayloadGeneric", referenced from:
"_swift_getExistentialTypeMetadata", referenced from:
"_swift_getForeignTypeMetadata", referenced from:
"_swift_getGenericMetadata", referenced from:
"_swift_getInitializedObjCClass", referenced from:
"_swift_getObjCClassFromMetadata", referenced from:
"_swift_getObjCClassMetadata", referenced from:
"_swift_getObjectType", referenced from:
"_swift_getSingletonMetadata", referenced from:
"_swift_getTupleTypeMetadata2", referenced from:
"_swift_getWitnessTable", referenced from:
"_swift_initClassMetadata2", referenced from:
"_swift_initStructMetadata", referenced from:
"_swift_isaMask", referenced from:
"_swift_makeBoxUnique", referenced from:
"_swift_once", referenced from:
"_swift_projectBox", referenced from:
"_swift_release", referenced from:
"_swift_retain", referenced from:
"_swift_storeEnumTagSinglePayloadGeneric", referenced from:
"_swift_unknownObjectRelease", referenced from:
"_swift_unknownObjectRetain", referenced from:
"_swift_unknownObjectWeakAssign", referenced from:
"_swift_unknownObjectWeakDestroy", referenced from:
"_swift_unknownObjectWeakInit", referenced from:
"_swift_unknownObjectWeakLoadStrong", referenced from:
"_swift_updateClassMetadata2", referenced from:
"_swift_willThrow", referenced from:
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Adding use_frameworks! in PodFile worked for me

Thanks @ywongweb! use_frameworks! resolved my issues as well!

Thanks!!

Open your workspace in Xcode
Right-click on Your App Name in the Project Navigator on the left, and click New File…
Create a single empty Swift file to the project (make sure that Your App Name target is selected when adding)
when Xcode asks, press Create Bridging Header and do not remove Swift file then. re-run your build.

@emrah88 after adding to pod file I got this error
[!] The 'Pods-xx' target has transitive dependencies that include statically linked binaries: (/Users/xxxx/Desktop/xx/ios/Pods/GoogleMaps/Base/Frameworks/GoogleMapsBase.framework, /Users/xxxx/Desktop/xx/ios/Pods/GoogleMaps/Maps/Frameworks/GoogleMaps.framework, and /Users/xxxx/Desktop/xx/ios/Pods/GoogleMaps/Maps/Frameworks/GoogleMapsCore.framework)

Create an empty Swift file in your project using Xcode.
Xcode will do everything for you.

@acalism @vladbars
I did as you guys said and it worked perfectly. Thanks a lot.
But now I have a blank swift file lying around in my project. I tried removing the file after a successful build but the error returns. Then I recreated the file and build is successful again.
Can you guys explain what purpose does this file serve? And shouldn't we be able to remove this file if it doesn't serve any purpose (please correct me if I wrong)?
Thanks.

Open your workspace in Xcode
Right-click on Your App Name in the Project Navigator on the left, and click New File…
Create a single empty Swift file to the project (make sure that Your App Name target is selected when adding)
when Xcode asks, press Create Bridging Header and do not remove Swift file then. re-run your build.

This worked for me. Thank you so much!

@acalism @vladbars
I did as you guys said and it worked perfectly. Thanks a lot.
But now I have a blank swift file lying around in my project. I tried removing the file after a successful build but the error returns. Then I recreated the file and build is successful again.
Can you guys explain what purpose does this file serve? And shouldn't we be able to remove this file if it doesn't serve any purpose (please correct me if I wrong)?
Thanks.

I'm also curious as to why this file works. The line that this adds is import Foundation but since this file is not being referenced anywhere else, what is this doing?

Open your workspace in Xcode
Right-click on Your App Name in the Project Navigator on the left, and click New File…
Create a single empty Swift file to the project (make sure that Your App Name target is selected when adding)
when Xcode asks, press Create Bridging Header and do not remove Swift file then. re-run your build.

Awesome ! Thanks you very much for the help :) This solution is working for me !


dsh: write output or update input file for tracking new state for rm

When using the rm command in dsh, the list of files is updated.  It would be nice to write this to an output list so someone can pick up where they left off if they stop and run dsh again at a later time.

This is now supported if the user also specifies -o when starting drm.
Let's addionally add a "write filename" command to let a user write to a file if they forgot to start drm with -o.

@sikich, this task would be a good intro to the guts of dsh for you.  This is really an experimental tool that I think could be really useful, but I'm not sure we want to fully support it on all systems (hence experimental).  Anyway, it seems to work well here so far.

The -o and --file options are good for v0.7.  The write command can come in a later release.


Move stuff out of libs and into package.json as dependencies

For easier maintenance, we want to move away from manual copies of the libs here:

Use npm to load and update these.

Closed with 1cba48a5b4c50f880bb941ac2b28181823c38cdd


Deletion confirmation after blacklist may move to popup?

I got a bit confused when using the deletion prompt after choosing to blacklist domains/urls.
Its a bit counterintuitive that the prompt appears in the middle of the page, also i could imagine that we will run into some problems on some pages, that disallow/block CSS injections?
May be possible to just use the whole popup, looking something like this?

Also ran into a few bugs.
The dialogue does not always pop up on the page.
Example when it happened the last time: http://startupmanagement.org/2017/06/10/tokenomics-a-business-guide-to-token-usage-utility-and-value/

closed with #71


@click not fired in elements inside a v-close-popper

Hello,
Between 5.1.0 and 5.1.1 the @click in elements inside a v-close-popper stopped working (expectation: click works and the popper closes): https://codesandbox.io/p/sandbox/floating-vue-click-5m6mm6
Is it supposed to work like this?
Thanks!
Edit: @kouts @mousedown works.
Linked example:
<template>

    <VDropdown>
      <button>Open popper</button>
      <template #popper>

1) Close on click OK

2) @click (stopped working on 5.1.1)

3) @mousedown (works)

      </template>
    </VDropdown>

    {{ list }}

</template>

I am experiencing the same issue, this problem already existed on the v2.0.0-beta.24 version on Mobile but now it's also a problem on desktop.

This is a workaround for VDropdown:
  <VDropdown ref="myDropdown">

          More

      <template #popper>

                   View file

      </template>
  </VDropdown>

I think this is because the event has changed to mousedown on v5.1,  @afv  can you try @mousedown="doSomething"?

Yeah, I certainly wasn't expecting a breaking change from a point release!

I'm also not sure why the change from click to mousedown maybe @Akryum can shed some light

Hmmm yes it looks like it's breaking things so it will be reverted

Hi @Akryum, thanks for reverting it, but now the v-close-popper does nothing?
https://codesandbox.io/p/sandbox/floating-vue-click-forked-mk7fwp?file=%2Fsrc%2FApp.vue


Is project discontinued? 该项目被放弃？

Greetings, pomelo is awesome, but there is no updates for a long time... Master branch build fails.  Is project discontinued by the founder?
pomelo, 非常有趣的项目，但没有更新，用户支持不进行......该项目被遗弃？

I have the same question to :).

Same here, did 2.0 move some where else?

Me too. Same question.

more than a month, have passed, and no answer

我也想知道，太可惜了

我认为，支持将不会是...

This project may be given up....I guess...Because this is a project created for a company (NetEase) 4 years ago. With workers leaving this company, nobody wants to continue to work for it...And I don't know whether NetEase uses this project, may not?
估计没人了吧....4年前的项目,开发者离开网易就没人维护了....再说网易他自己用这个(不怎么维护的)框架么...

继续维护的

and in english?

@kaktus42 project alive

@kaktus42 yeah alive


Can't run plugins after update G3nius-Tools

Run plugins problem after update G3nius-Tools.
If you have version under 0.0.4, After update may be your plugins not work. Because in version 0.0.4 symbolic links not supported. After that version, symbolic links uses for encrypted plugins.
Symbolic links just to save your disk space.

Solution 1:
You can delete it and reinstall from G3nius-Tools GitHub
Delete files you're downloaded, Then Redownload G3nius-Tools.

Solution 2 (Recommended):
Download from update API and install easily.
Linux commands one by one:

rm -r G3nius-Tools
mkdir G3nius-Tools
wget 'https://api.bugzone.ir/G3nius/Lastest.zip'
unzip Lastest.zip
rm Lastest.zip

Solution 3 (Advanced):
You can update just Updater plugin. Go to downloaded files and file G3n!us-Tools/plugins/Updater/. Then you can find and update main2.py and main3.py. You should download they're files from here.

NOTE:
If you installed plugin(s) manually, don't forget to be backup plugin folder. It will be deleted.

Name of script changed


Port scans are invoked despite pre-set values

I noticed that embedded cassandra attempted to scan a range of ports for Thrift, despite there is a defined value set at the builder.
This seems to be related to a "side-effect" coming from Optional.orElse(), where the else case is always evaluated.
See:
Link to source
Stackoverflow reference
The quick fix is to simply change them to orElseGet and wrap the existing function calls with a supplier (i.e. () -> blah)
If you like this idea, I could submit a PR that updates that particular function in ServerStarter.java

+1 for the PR

Sorry for the delay, the required changes are simple (see #328) ... but I wasn't able to run all the tests in my new environment due to latest java sdk version and window bash.
The CI build passed. However, I am not sure if that runs the tests under embedded module. If you have a working environment, you might want to run those tests against the branch from that PR.
Really appreciate the work you have done with this project. It helps us a lot with our dev environment.

Thanks for the PR


[CT-672] _relations_cache_for_schemas() takes 2 positional arguments but 3 were given

First time install of DBT (dbt-postgres)  on Ubuntu.

dbt init myFirstProject

Changed settings in ~/.dbt/profiles.yml

dbt run
returns:  _relations_cache_for_schemas() takes 2 positional arguments but 3 were given

Log files don't seem to give hints on the cause of the error. How can I find the cause of this error?

dbt --version

 installed version: 1.0.6
   latest version: 1.1.0

Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation

Plugins:
  - postgres: 1.1.0 - Up to date!

You're right.
dbt-mysql was installed before, but was removed because this is not maintained.
I'll start over with a clean VM. Thanks a million, I'm sure I'll be able to make progress now.


Dependency problems during vivid install

I know that vivid is officially unsupported but I figured I'd throw this up in case anyone cares
$ sudo sh ./crouton -r vivid -t xfce -n xfce -u
~~~~~ Successes removed for brevity ~~~~~~~~
dpkg: dependency problems prevent configuration of lsb-release:
 lsb-release depends on python3; however:
  Package python3 is not installed.
 lsb-release depends on python3:any (>= 3.3.2-2~); however:

dpkg: error processing package lsb-release (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ubuntu-minimal:
 ubuntu-minimal depends on lsb-release; however:
  Package lsb-release is not configured yet.
 ubuntu-minimal depends on python3; however:
  Package python3 is not installed.
 ubuntu-minimal depends on resolvconf; however:
  Package resolvconf is not installed.

dpkg: error processing package ubuntu-minimal (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of dh-python:
 dh-python depends on python3:any (>= 3.3.2-2~).

dpkg: error processing package dh-python (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 lsb-release
 ubuntu-minimal
 dh-python
Failed to complete chroot setup.
Unmounting /media/removable/SD Card/chroots/xfce...

It appears that the issue is primarily that python3 and resolvconf are missing. Adding these to the dependency list should fix it up.

See #1706.

Oh, thanks, didn't see that one. Definitely a duplicate then.


Fix: BO - dashactivity - module can't be SAVED properly

Added method "saveDashConfig"

Questions
Answers

Description?
The configuration should be saved

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/Prestashop#37033

How to test?

Hello @Codencode!
This is your first pull request on dashactivity repository of the PrestaShop project.
Thank you, and welcome to this Open Source community!

Thanks for the PR.
Some checks were not successful, could you check @Codencode ?

florine2623

Hi @florine2623,
I don’t think I can fix it because, from what I understand, in the definition of the ModuleCode::getPermission() method, the first parameter is defined as array, whereas it should be string.
PS <IP_ADDRESS>
https://github.com/PrestaShop/PrestaShop/blob/753bc2441bc21d79a366f3c7566a03da1ac915eb/classes/module/Module.php#L2768-L2779
PS 8.2.0
https://github.com/PrestaShop/PrestaShop/blob/327c9e42b556fcd676ff02376c00d8d8c3521061/classes/module/Module.php#L2587-L2598
I believe we should simply ignore the warning.

@Codencode Yeah, just add this error here. :-)
https://github.com/PrestaShop/dashactivity/blob/dev/tests/phpstan/phpstan-1.7.7.neon
and here also, because in 1.7.8 it's still an array in the docs and it will also scream at you
https://github.com/PrestaShop/dashactivity/blob/dev/tests/phpstan/phpstan-1.7.8.neon

@Hlavtox,
I hope I did well, I added the errors to the files in my repository and uploaded them.
I never added "ignoreErrors"
Thanks!

@Codencode Good job, all good now! :-)

@florine2623 Ready to go! :-)

@Codencode Good job, all good now! :-)

@Hlavtox Thank you!

Thanks everyone!


Item "Fast New Tab" in extension context menu should open fnt home page

This is the home page of fnt -- https://github.com/uid-11222/fast-new-tab/ .

Link to home page added.


feat(v4): add pick not deprecated

Created a helper function for picking not deprecated values.
const sorter = undefined;
const sorters = [{ id: 1 }];

const value = pickNotDeprecated(sorter, sorters) ?? [{ id: 5 }]; // [{ id: 1 }]

[x] Corresponding issues are created/updated or not needed
[x] Docs are updated/provided or not needed
[x] Examples are updated/provided or not needed
[x] TypeScript definitions are updated/provided or not needed
[x] Tests are updated/provided or not needed
[x] Changesets are provided or not needed

Hey @alicanerdurmaz,
Can you export this function from core/src/index.tsx?


Cilium Map Pressure metric goes above 100%

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
While testing scenarios where endpoint policy maps fill up, I noticed that the map pressure metric seems to go above 100%:
ex output:
cilium_bpf_map_pressure                               map_name="policy_02366"                                                                                3.886719

Which would indicate a size of 380%, this is likely caused by how the metric counts cached map entries that are being retried.
Cilium Version
head
Kernel Version
6.2.0-1009-azure
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-10-25T19:35:11Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Nice find! Do you have reproduction instructions or do you plan to follow up investigation on this? Otherwise I think that if someone else tries to reproduce, they may need a bit more context.

@joestringer Yup, I'm working on a fix here: https://github.com/cilium/cilium/pull/28184
Steps to reproduce are in the commit message.

I think we ended up deciding that it's actually desirable to the bpf map pressure metric exceed 100% because it serves as a signal for what the map should be in the case the user wants to adjust the map size.


Web breakpoint icon takes a while to show

Testing #97876
I probably waited 5s before I saw the breakpoint icon appear. I thought this was a bug, as when I launched a debug session and quickly switched tabs back and forth the breakpoint immediately switched. You can see in the example below where the breakpoint is hit when you navigate to the web page I then wait a bit long for the breakpoint icon to show up. Would expect this to appear immediately.
EDIT: Safari seems to show it immediately. So it appears Chrome + FF take the longest.

In FireFox this actually never gets shown if you restart the process and quickly switch tabs. In the end of this gif, I switch over and the icon is shown immediately:

Good catch. However this is just the browser blocking us I believe.
Also assigning to @bpasero but nothing we can do in May thus assigning to On Deck.

Maybe switching to web notifications instead would be a way out. Given this seems to be browser specific, setting upstream label.

/duplicate https://github.com/microsoft/vscode/issues/99223


tools/python: Use newer entry_point rule

the old rules_python entry_point rule has been removed in newer versions in favour of a new rule
in addition to that - the new rule also adds dep handling which was the reason we previously wrapped it so our customization is no longer required

/retest flakey mobile android

/retest flakey mobile ios


Add .erb extension to ERB icon list

Fixes #159
This adds the erb icon to the .erb extension in supportedExtensions.js Line: 34. Logged in Issue #159

:+1:


#1 Support multiple Markdown and Code Example directories

You can call "--md" and "--cef" multiple times, and swag will look for the right files in all of the directories.

BAD PR


After upgrading to 3.2, logs no longer show up at /var/log/push-jobs-client/current

Cookbook version
3.2
Chef-client version
Chef: 12.10.24
Platform Details
Oracle Linux Server release 7.1
Scenario:
After upgrading to 3.2, logs no longer show up at /var/log/push-jobs-client/current.
Steps to Reproduce:
Expected Result:
Log file available.
Actual Result:
No log file.

Based on https://github.com/chef-cookbooks/push-jobs/pull/87, now the service is configured using systemd

Your logs are now going to use journald as the service is running via the native systemd init provider

@tas50 Thank you for the pointer. The journald`` logs do not contain output from the command ran (like chef-client```), which was the default behaviour in the previous versions. Thanks

The workaround we found is to redirect the chef-client logs into a separate file. Modify /etc/chef/client.rb:
#Add below line to change log level and location
log_level                     :info
log_location    "/var/log/chef.log"


Think about how we deal with schema changes

Also need to provide a way for a host to specify the Initializer policy. I don't like it in the ServiceFactory ctor.

Ok, I think I've decided that migrations are going to be left to the consuming application to manage. We've tried to do migrations within the project itself and it's been a nightmare. I just tested and a consuming app can easily manage migrations for the DbContexts in IdSvr.Ef's assembly.

This is what I would suggest as well :+1:

@brockallen do you have an example of adding a DB migration to the consuming application? When we try to add one it thinks it needs to regenerate the entire schema of our DbContext.


Feature/voicemail

voicemail.md is the only relevant file changed.

resolved conflicts by using /voicebase-docs

Merged using command line process


Extend DeviceInfo Modul with functions for Storage Space (Android)

add function getAvailableExternalMemorySize() and getAvailableInternalMemorySize() to get informations about storage space

:-1: This belongs in https://github.com/johanneslumpe/react-native-fs not in this simple device query plugin.

@BigPun86 a fresher PR was created for iOS, with a better naming. Do you mind if your code is borrowed for #302 and this PR get closed?

Sure, Go ahead 💪🏽

Thank you buddy!

FYI, the new PR just made it, it should be live in 0.15.0 in a few days.


update mser.c  fix the height of a tree

hi sir:
when i debug the mser.c. i found the value of "n_hgt" and "hgt" is not always correct. then i found the code below in "mser.c":
vl_mser_pix nr_val = 0 ;
vl_uint     nr_idx = 0 ;
int         hgt   = r [ r_idx] .height ;
int         n_hgt = r [nr_idx] .height ;
r_idx = climb(r,   idx) ;
nr_idx = climb(r, n_idx) ;
it means that the "n_hgt" is always the height of r[0]. because the "nr_idx" is "0"  when the computer runs the code "int   n_hgt = r [nr_idx] .height ;".!!.
so i modify it like this:
vl_mser_pix nr_val = 0 ;
vl_uint     nr_idx = 0 ;
r_idx = climb(r,   idx) ;
nr_idx = climb(r, n_idx) ;
int         hgt   = r [ r_idx] .height ;
int         n_hgt = r [nr_idx] .height ;
it works correctly in my project. and thanks to the vl_feat, my project is success now!!!!

I also found this bug. why this bug has not been fixed for two years!

It looks that with this change mser not only works more correctly but also faster (30% for my usage scenario)

This change works faster for me too. #207 also references this


Add Japanese locale

Hi. I added a Japanese locale file for the project.
Thanks.

Coverage remained the same at 91.667% when pulling 9e4ae797a33f61a6784835141e3a8837238f1770 on ryohashimoto:locale_ja into 6a01bd1740b010358f34a851c7ddc0d5227a4c76 on ondrejbartas:master.

@ryohashimoto Thank you very much for your PR

Thanks


ci: Remove incorrect code comment and cargo clean

Recently while trying to fix CI I (Tobin) added a call to cargo clean and a code comment justifying it. This was merged because while not incorrect it is redundant since calling cargo with different RUSTFLAGS triggers a rebuild.

If this passes CI it means the recent ASAN issue was wholly caused by running cargo from the crate root - I'm still not sure exactly what was breaking though.

@tcharding my suspicion is that the ASAN issue is a nondeterministic bug and your "fix" just rearranged code in a way that stopped triggering it.
As for the rust-secp MSAN thing it looks like Elichai has dug into it and provided details on https://github.com/rust-bitcoin/rust-secp256k1/pull/573. Curious whether these issues are actually related or just a coincidence.

Oh I think it was the MSAN thing all along and we were running cargo commands from the crate root which would include bitcoin which depends on secp. Only running the sanitizer from hashes which doesn't depend on secp solved the problem by hiding it :)

Oh, lol! I think you're right.

Friendly bump please.


[Doc] Best practice guide

Need the best practice guide for Longhorn.
Recommended settings. Replica count, what's the underlying disk structure, recurring snapshot/backup etc

Available at https://github.com/yasker/longhorn/wiki/Best-practices-for-deploying-Longhorn-in-production for now. Will move to the doc later.

@catherineluse Can you help to move the guide at https://github.com/yasker/longhorn/wiki/Best-practices-for-deploying-Longhorn-in-production to the website?

The best practices guide has been added to the staging branch of the Longhorn website. https://github.com/longhorn/website/pull/102

Done.

I cannot find the merged PR https://github.com/longhorn/website/pull/102

I think we can close this issue because it's in staging now. https://staging.longhorn.io/docs/0.8.1/best-practices/


Added support for Juju Storage

Thanks for the review @lmlg there are a few things that I have not completely figured out (mostly sane detachment of disks). And need to implement a storage_updated event handler in charm to update the unit status. Will resolve your comments along with that. Apart from that this logic does two things nicely:

Automatically enrolls OSDs once disks are added to the unit.
Automatically enrolls OSDs with WAL/DB as soon as equal atleast one of each is available to the unit.
Trigger an event to notify charm about remaining wal/db/disk devices. (Charm will react to it by updating the charm status)


autoNumeric('get') returns error

Hi
I've got a simple input for the price but when I execute the code
$('#price').autoNumeric('get');
an error is thrown:
autoNumeric-min.js:35 Uncaught TypeError: false.test is not a function(…)

Please try using the unminified version.
It is also very help to post a jsfiddle so i can see first hand.
Thanks,
Bob
On 3/26/2016 4:35 AM, gigallo wrote:

Hi
I've got a simple input for the price but when I execute the code
$('#price').autoNumeric('get');
an error is thrown:
autoNumeric-min.js:35 Uncaught TypeError: false.test is not a function(…)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/BobKnothe/autoNumeric/issues/197

I've solved with the 2.0 version. When will it be definitive?


Create LICENSE

@all-contributors please add @mah51  for code, content, doc, design, maintenance, review.


Use nf_conntrack_count instead of wl -l

Currently the summary page of LuCI calls wc -l on the entire list of connections (/proc/net/nf_conntrack) in order to get the current connection count.
On thousands of active connections, this command could take several seconds or minutes to complete.
Instead, we can use the count provided by the kernel at /proc/sys/net/netfilter/nf_conntrack_count. The data is available instantly and will not hang the page.

Thank you for your PR @cfurgang ! I committed a slightly improved variant of your suggested change with 7ae244a26


ERC20 approveAndCall functionality

Implement approveAndCall token functionality to avoid multiple transactions for calling Deposit functions that require prior approval
Implementer: @NicholasDotSol
Feature buddy: @liamzebedee

@NicholasDotSol If I'm not mistaken this is implemented now since we have FundingScript and RedemptionScript, no?

^^ the answer is yes.


Is the project still being developed?

I found this IDE quite interesting and wondered if it was still being developed after nine years. It would be miserable if it had already been discontinued, because it is my most favourite code editor in ComputerCraft :)

It is not being developed lmfao. Go use cloud catcher: https://cloud-catcher.squiddev.cc/

Is there any alternative (even better) of this lol


Evaluate -fsanitize-minimal-runtime for possible hardening

In https://news.ycombinator.com/item?id=38478866 nlewycky reports the following:

Also! While the usual sanitizer runtime libraries aren't security hardened for use in production environments, but for UBSan there's -fsanitize-minimal-runtime which switches to a different runtime library that is intended for this purpose (or use -fsanitize-trap=... instead, which executes an illegal instruction on error). Note that if your program terminates with a UBSan error, an attacker who can check whether your program terminated or not could use that as a primitive to leak data, so consider the security impact on your use case carefully. UBSan has a quite small performance impact when building with optimization, so you could deploy to production with it enabled, or parts of it enabled.

I'd like some feedback from the various distros & such. Is there a big drawback to this? It sounds potentially helpful, but I don't have any experience doing this for production.

Has this been addressed by the C/C++ Compiler Hardening options guide?    @gkunz @thomasnyman @david-a-wheeler


Agda builder ignores deprecated modules

Describe the bug
Agda builder doesn't build deprecated modules
To Reproduce

Build Standard library
Realise Data.List.Any.agdai is not there

Expected behavior
I'm not sure if these should be included by i expect it is a good idea. This issue may be specific to standard library. We build the Everything.agda which does not include deprecated modules. However I have had a quick look and cannot see an alternative to this.
Notify maintainers
@turion
Metadata

system: "x86_64-linux"
host os: Linux 5.4.43, NixOS, 20.09pre227577.135073a87b7 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.5
channels(root): "nixos-20.09pre227577.135073a87b7, all-hies, emacs, home-manager, nixpkgs-wayland"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

IMHO, this is fine. Your documentation clearly states that an Everything.agda file is the default way to build something, following common Agda conventions. If that doesn't include certain files then it's primarily an upstream issue.

I only ask because this currently blocks building agda-categories

I only ask because this currently blocks building agda-categories

How so? Does agda-categories need that module?
In that case I'd suggesting to patch Everything.agda or forking the standard library on our side temporarily, and file an upstream bug.

Maybe I misunderstood. If agda-categories doesn't build because it needs a deprecated module, then agda-categories needs to be patched.

I asked for a tag to be placed on a commit that works, though the commit that "works" depends on a deprecated module (Data.List.Any). This has been fixed in later commits so I have made a comment on the issue and will wait for the result of that. Worst case a patch could be used so I'll close this


🐛 [firebase_ui_auth] SMSCodeInputScreen displays overflow error when an error message is displayed

Bug report
Describe the bug
SMSCodeInputScreen of phone login shows a render overflow error when an error message is displayed on entering an incorrect code. Have tried this on web, not on mobile.
Steps to reproduce
Steps to reproduce the behavior:

Create a login with phone provider as shown in the firebase_ui_auth example
Launch the app from IDE with Chrome as target device. Extend the browser window horizontally so that the phone icon and form are displayed side-by-side
Enter a valid/test phone number on the phone input screen and click Next
Enter an invalid code on code input screen and click Next
An error message is displayed under the code input and an overflow error appears for the buttons. If you don't see the error, extend the browser window horizontally. The overflow only appears for me after the window is >= 776px wide

Expected behavior
No render error

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[√] Flutter (Channel stable, 3.3.10, on Microsoft Windows [Version 10.0.19045.2364], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[√] Chrome - develop for the web
[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2021.2)
[√] VS Code (version 1.63.2)
[√] Connected device (3 available)
[√] HTTP Host Availability

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.18.6
Flutter SDK 3.3.10
testapp 1.0.0+1

dependencies:
- cloud_firestore 4.3.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.5
- firebase_auth 4.2.3 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.4.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_ui_auth 1.1.5 [email_validator firebase_auth firebase_core firebase_dynamic_links firebase_ui_localizations firebase_ui_oauth flutter flutter_localizations flutter_svg]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- go_router 6.0.0 [collection flutter flutter_web_plugins logging meta]

dev dependencies:
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection matcher material_color_utilities meta source_span stre
am_channel string_scanner term_glyph]

transitive dependencies:
- _flutterfire_internals 1.0.11 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- async 2.9.0 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.1
- clock 1.1.1
- cloud_firestore_platform_interface 5.10.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.2.0 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.16.0
- crypto 3.0.2 [typed_data]
- desktop_webview_auth 0.0.11 [crypto flutter http flutter_web_plugins plugin_platform_interface]
- email_validator 2.1.17
- fake_async 1.3.1 [clock collection]
- firebase_auth_platform_interface 6.11.6 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.2.3 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.5.2 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.0.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_dynamic_links 5.0.10 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.3+25 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_ui_localizations 1.0.2 [flutter flutter_localizations intl path]
- firebase_ui_oauth 1.1.5 [desktop_webview_auth firebase_auth firebase_ui_auth flutter_svg flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_svg 1.1.6 [flutter meta path_drawing vector_math xml]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- http 0.13.5 [async http_parser meta path]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.4
- lints 2.0.1
- logging 1.1.0
- matcher 0.12.12 [stack_trace]
- material_color_utilities 0.1.5
- meta 1.8.0
- path 1.8.2
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- petitparser 5.1.0 [meta]
- plugin_platform_interface 2.1.3 [meta]
- sky_engine 0.0.99
- source_span 1.9.0 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.1
- test_api 0.4.12 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.1 [collection]
- vector_math 2.1.2
- xml 6.1.0 [collection meta petitparser]

as of firebase_ui_auth 1.7.0 and Flutter 3.13.1 • channel stable – this is no longer reproducible.


Add bundle dir validations

Fixes #115.
Testing: successfully ran ./hack/test-all-local-registry.sh 5000.
Notes:
👋   - first time contributor!
I made the assumption that for a bundle to be considered a bundle, it needs to have the .imgpkg directory. And for it to be a valid bundle, it needs to also include the images.yml file in its directory. I wasn't sure if to qualify as a bundle actually the entire .imgpkg/images.yml must exist. If this is so, I would change the validations a bit.
There might be an opportunity to converge more of the related existing tests in the  push_test.go file into the table test added inside the TestBundleDirectoryErrors test. If this PR is going in the right direction, in regards to converging the other tests, I can:

do nothing
include that refactoring in this PR
open a separate PR just for that.

Let me know!

I believe I have addressed everything.


Fragment autocomplete doesn't work until prettier formats the string properly

Small thing:

^ Those aren't fields on Venue.
This should give me Venue fields, but it doesn't until I add a field, save, and it formats the spacing.
Now, once it's spaced properly, it does give me venue fields:

This is a similar issue to #127 it basically needs to find the spacing 😅
 i.e. it works here because there is a space after... Not entirely sure yet how to solve this but basically else it tries to fuse the suggestions with }.


Is isBetween active unexpectedly?

Whats going on here? its clear that deliverAt is between timeNowand timeNow + 2 hours.
  If you want to retain the original moment, you need to clone it before adding.  You can use either moment(timeNow).add(2,'h'), or the more explicit timeNow.clone().add(2,'h').  Both do the same thing.


Image is not sdm-enhanced

I see
% IMG './hostdir/source_images/2024-03-15-raspios-bookworm-arm64-lite.img' is not sdm-enhanced
  Logs and configuration updates will not be written

what does that mean?

Presumably you're seeing this on an sdm --burn or --burnfile command. The message is telling you that the IMG that you're burning has not been --customized with sdm, so the directory /etc/sdm and all the files sdm needs are not there.
Since that directory doesn't exist, there's no place for sdm to write the logs from the --burn* command.
Pretty much all other switches for the --burn* command are also not processed in this case. If you're still puzzled, please post the --burn* command you're using, and please confirm that you have NOT run --customize on the IMG before burning it.

Where did you get that understanding?
While it's true that a --burn* can do most customization as well, at least a minimal customize must be done to get the sdm "stuff" into the IMG (all in /etc/sdm) before you --burn*

I should add...--burn and --burnfile are equivalent except for the output. One goes to a disk type device and the other is to an IMG file.

The documentation is rather vague and disorganized. For the command line, typically, one would have something like sdm customize --the --set --of --customization --compatible --switches and sdm burn --the --set --of --burn --compatible --switches and so on. But I now have it working for the most part, which is terrific. This will really help with the setup. Thanks.

I'd be very interested in your feedback on where you think the documentation is "rather vague and disorganized".
Without constructive feedback from users it will likely remain as it is.
Thx

Maybe use the wiki or "read the docs", etc. It could use a bit more conceptual background about the workflow. There is a lot of detail and its hard to read through in a linear fashion. A lot of utilities have cmd input.file output.file rather than working in-place, so without some overview, its easy to think that eg --burnfile is like output.file in this sort of configuration.

I'll look into adding some documentation around switches that work in customize, burn, or both. But by the time I get it done you'll fully understand and won't need it 🤣

The switches that can be used with --burn and --burnfile are actually already documented here
The README on https://github.com/gitbls/sdm provides a complete overview of how to use sdm. There is also an index to all the documentation pages, and the link names are certainly helpful in knowing the contents of each page.
That said, I agree that there is a fair amount of documentation to wade through, so there may be a gap around providing workflow conceptual background information.  I'm not sure what that would look like relative to the existing documentation, so would very much appreciate your thoughts on this.


Update LOCALIZATION_CONTRIBUTORS

Changes
Added Mingi Ryu (mingiryu) to Korean

Implementation details

How to read this PR

Screenshots

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

thanks for the confirmation @0sophy1 👏


sort materials lists by field names

am I the only one that is annoyed by unalphabetical lists?

Personally I think category would be more useful as names are subjective/variable.
For example, say I was making a mod using birch/aspen or oak/apple different games call it different things with category I know its going to be woodstuff with alphabet I don't know where to look for it, under a or b/o?

yes, initially you may not know. But once you've figured out its 'woodstuff' then you'll see the other 'woods' next to it.

currently it's not so much a category based sorting either. It has more to do with dev-history :D

it's also a bit unfortunate that 'water_bucket' isn't called 'bucket_water' so it would naturally be under 'bucket'

Currently ya its unorganised.
I think instead of making alphabetical we should make it categorical, then semi alphabetical.
This would also help with things like gravel/flint, they belong together but arent named that same usually.
like:
--buckets/liquids
empty_bucket = "mcl_buckets:bucket_empty",
water_bucket = "mcl_buckets:bucket:bucket_water",
water_flowing = "mcl_core:water_flowing",
water_source = "mcl_core:water_source",
--woodstuffs
apple_leaves = "mcl_trees:leaves_oak",
apple_log = "mcl_trees:tree_oak",
apple_planks = "mcl_trees:wood_oak",
slab_wood = "mcl_stairs:slab_wood", --this is apple/oak so should be near apple/oak?
birch_leaves = "mcl_trees:leaves_birch",
birch_log = "mcl_trees:tree_birch",
birch_planks = "mcl_trees:wood_birch",
jungle_leaves = "mcl_trees:leaves_jungle",
--dyes alphabetical
dye_black = "mcl_dyes:black",
dye_blue = "mcl_dyes:blue",
dye_brown = "mcl_dyes:brown",
dye_cyan = "mcl_dyes:cyan",
dye_dark_green = "mcl_dyes:dark_green",
dye_dark_grey = "mcl_dyes:dark_grey",
dye_green = "mcl_dyes:green",
dye_grey = "mcl_dyes:grey",
dye_orange = "mcl_dyes:orange",
dye_pink = "mcl_dyes:pink",
dye_red = "mcl_dyes:red",
dye_violet = "mcl_dyes:violet",
dye_white = "mcl_dyes:white",
dye_yellow = "mcl_dyes:yellow",
--axes
--hoes
---picks
--shovels
--swords

I prefer straightup alphabetical.
Your category approach is certainly better than what it is now.
There may be troubles wit categories as some items may make sense in multiple categories. So devs would still have to use the search function to find things.
Of course if neither the fieldname nor the category is known to dev, he has to search.
IMO chances are greater that a dev would know the fieldname or at least have an idea and so alphabetical would be more useful.

i dont particularly care all that much, but i do think Kazooo's idea is pretty good. one could even argue that made materials should be grouped more like textures

I don't particularly care all that much, but I do think Kazooo's idea is pretty good. one could even argue that made materials should be grouped more like textures

made materials?


Feat: Add twitter CLI

Adding a command line interface for the twitter platform extraction and analytics.

For now, the analytics part logs are added. The extraction is still left to do.


[docs-only] Disable proof key validation for OnlyOffice

Description
Currently, we have a lot of problems with proof keys and onlyoffice.
Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

I checked CI. it's already disabled

It's disabled in CI because the wopi validator won't send the proofs, so all the requests would fail because we can't verify them.


Kron open issue

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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.462%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1195

Relevant Lines:
1321

💛  - Coveralls


Update the login/Keycloak docs page

Related to https://github.com/Quansight/qhub/issues/1076.
Changes introduced in this PR:

Update login/Keycloak page in docs: Installation > Login.
A few other various minor fixes in the docs

Types of changes
What types of changes does your PR introduce?
Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[x] No

Documentation
Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

[ ] Yes, docstrings
[x] Yes, main documentation
[ ] Yes, deprecation notices

Screenshot
Here's how the page looks after these changes:

Hi, @gabalafou thanks for opening this pull request and adding those considerations!!! I don't know if you need my comments in there or not, but I did it anyway :smiley:. We are still discussing the v0.4.1 post-release changes, and once that's done we can merge this!!! Thanks again for the contribution :rocket:


Debug not working with Julia v0.5

Installed v0.5 via homebrew, and added Debug via Pkg.add("Debug"). Ran some existing plotting code that was fine under 0.46 and got the following error:
INFO: Precompiling module Debug.
WARNING: symbol is deprecated, use Symbol instead.
in depwarn(::String, ::Symbol) at ./deprecated.jl:64
in symbol(::String, ::Vararg{String,N}) at ./deprecated.jl:30
in include_from_node1(::String) at ./loading.jl:488
in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in include_from_node1(::String) at ./loading.jl:488
in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in macro expansion; at ./none:2 [inlined]
in anonymous at ./:?
in eval(::Module, ::Any) at ./boot.jl:234
in eval(::Module, ::Any) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in process_options(::Base.JLOptions) at ./client.jl:239
in _start() at ./client.jl:318
in _start() at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
while loading /Users/jeffreyvarner/.julia/v0.5/Debug/src/AST.jl, in expression starting on line 62
WARNING: Method definition is_evaluable(Debug.AST.Node{Debug.AST.Location}) in module AST at /Users/jeffreyvarner/.julia/v0.5/Debug/src/AST.jl:120 overwritten at /Users/jeffreyvarner/.julia/v0.5/Debug/src/AST.jl:121.
ERROR: LoadError: LoadError: UndefVarError: SymbolNode not defined
in include_from_node1(::String) at ./loading.jl:488
in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in include_from_node1(::String) at ./loading.jl:488
in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in macro expansion; at ./none:2 [inlined]
in anonymous at ./:?
in eval(::Module, ::Any) at ./boot.jl:234
in eval(::Module, ::Any) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in process_options(::Base.JLOptions) at ./client.jl:239
in _start() at ./client.jl:318
in _start() at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
while loading /Users/jeffreyvarner/.julia/v0.5/Debug/src/Analysis.jl, in expression starting on line 51
while loading /Users/jeffreyvarner/.julia/v0.5/Debug/src/Debug.jl, in expression starting on line 7
ERROR: LoadError: Failed to precompile Debug to /Users/jeffreyvarner/.julia/lib/v0.5/Debug.ji.
in compilecache(::String) at ./loading.jl:593
in require(::Symbol) at ./loading.jl:422
in require(::Symbol) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
in include_from_node1(::String) at ./loading.jl:488
in include_from_node1(::String) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
while loading /Users/jeffreyvarner/Desktop/Desktop - Jeffrey’s MacBook Pro/julia_work/bigmac_julia_hybrid_fibrinolysis_v2/src/PlotAICPredictions.jl, in expression starting on line 3

I think this issue is very important. I am seeing a lot of bugs from Gallium.jl and I don't think Gallium is any useful at the moment.

The Symbol error is easy to fix. In AST.jl there are a few references to deprecated symbol instead of Symbol. But after that, you will find that SymbolNode is equally undefined and I can't figure out what its replacement is.

@toivoh Users need a working Debugger.

Same here
ERROR: LoadError: LoadError: UndefVarError: SymbolNode not defined
 in include_from_node1(::String) at ./loading.jl:488
 in include_from_node1(::String) at /usr/local/Cellar/julia/0.5.0/lib/julia/sys.dylib:?
 in include_from_node1(::String) at ./loading.jl:488
 in include_from_node1(::String) at /usr/local/Cellar/julia/0.5.0/lib/julia/sys.dylib:?
 in macro expansion; at ./none:2 [inlined]
 in anonymous at ./<missing>:?
 in eval(::Module, ::Any) at ./boot.jl:234
 in eval(::Module, ::Any) at /usr/local/Cellar/julia/0.5.0/lib/julia/sys.dylib:?
 in process_options(::Base.JLOptions) at ./client.jl:239
 in _start() at ./client.jl:318
 in _start() at /usr/local/Cellar/julia/0.5.0/lib/julia/sys.dylib:?
while loading /Users/adrian/.julia/v0.5/Debug/src/Analysis.jl, in expression starting on line 51
while loading /Users/adrian/.julia/v0.5/Debug/src/Debug.jl, in expression starting on line 7
------ ErrorException ------------------ Stacktrace (most recent call last)

 [1] — require(::Symbol) at sys.dylib:?

 [2] — require(::Symbol) at loading.jl:422

 [3] — compilecache(::String) at loading.jl:593

Failed to precompile Debug to /Users/adrian/.julia/lib/v0.5/Debug.ji.

I'm having the exact same problem as essenciary.

+1

I can't really help but this was the PR which removed SymbolNode: https://github.com/JuliaLang/julia/pull/15609
It introduced a new Slot which features sometimes where SymbolNode was before.  Maybe that works?

Same issue here. I have to stay on Julia 0.4.7 until Gallium is ready for use or Debug.jl can be used in Julia 0.5

I've switched my project to Gallium - it has a different workflow coming from Debug so it takes a bit of a change in mindset and possibly changes in code to accommodate. But it works great and it's the future (and present) of Julia debugging, so it's worth taking the time to switch.

Is there anything being done about the SymbolNode? Can we do it without SymbolNode?
Thanks


[BUG] Can't "un-choose" the Zone/Pod/Host for the VM deployment

Describe the bug
A clear and concise description of what the bug is.
Once a specific Zone/Pod/Cluster/Host has been selected, there is no way to "unselect it" i.e. to make sure no specific is selected/chosen for the VM deployment.

@utchoang can you add a fix to display an empty/default option (say 'Default' or label.default?) for the zone, pod, cluster and host dropdown whose internal zone/pod/cluster/host ID is null (so effectively saying no zone/pod/cluster/host is selected). Old UI it looks like this:


Packet verif function for structure check

Description
Current behavior of packet verification function (e.g. is_audio_packet() in audio.js) is only check head element value of passed Uint8Array.
If passed an array what first element is match to XX_PACKET_TYPE_ID by accident, it returns true: is packet.
There are not enough features. Finally, decoding functions requires structure checking. So modify verify functions to check structure.

I designed packet verify functions to throw error when packet is not matched to expected type, return nothing when matched.
By the design, packet type confirming code will be:
try:
  is_volume_modify_packet(raw_packet)
  # for volume-modify packet process
except:
  pass

try:
  is_lanes_info_packet(raw_packer)
  # for lanes-info packet process
except:
  pass

It is non prefer code, there are many blank expect code. Should be:
if is_volume_modify_packet(raw_packet):
  # for volume-modify packet process
  pass
elif is_lanes_info_packet(raw_packer):
  # for lanes-info packet process
  pass

By add an argument of switching error throwing/rising, fulfill each situation: detail error checking and simple confirming.
def is_volume_modify_packet(raw_packet, raise_on_invalid = False)


added get_insights() function for GitHub Repository class

Description

added get_insights() function in GitHub Repository class which returns the active pr count, active issue count, merged pr count, open pr count, closed issue count, new issue count, list of recent merged prs, list of recent open prs, list of recent closed issues, list ofrecent open issues

Resolves: [#511]
Checklist

Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?
[x] Have you updated the 'documentation.md' file with the method/function documentation?
[x] Have you sent a message along with the result or response?
[x] Have you used the try-catch technique?
[x] Has the method/class been added to the documentation (md file)?

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.
I appreciate your contribution.

Check it now @nikhil25803


No session routes on token authenticatable

Session routes (such as destroy_user_path) aren't being generated when using :token_authenticatable; only when adding :database_authenticatable, which I don't need nor want.
(Using Ruby 1.9.3p0, Rails 3.1.0, Warden 1.1.0, Devise 1.5.3, ORM 0.0.5, Faraday 0.7.5)

Thanks for the report. For now, you cAn work around the problem by defining the route yourself.

Here, I found it after a few hours of digging. It was "working" before, but was "(un)fixed" for some reason.
Commit 4fd866d in lib/devise/modules.rb:8

It should also be noted that session controller and routes are expected under default behavior, as someone who wouldn't want them, and opt for a stateless token would use config.skip_session_storage on :token_auth.


Delete old versions in cleanup

Hi.
This somewhat ties in to the upgrade diskussion:
I just updated my applications by force installing them. This lead to multiple versions on my machine.
I would have /opt/homebrew-cask/Caskroom/pycharm/3.3.x/ and /opt/homebrew-cask/Caskroom/pycharm/3.4.x/.
On a small SSD this has the potential to litter the HDD.
It would help, if cleanup would try to delete older versions (or a full fledged upgrade)

No longer relevant: #13201.


Changing the max_queue_size directive

A little patch to use the configuration directive max_queue_size from file instead the default 16K

If you wouldn't mind making that minor change and squashing, that would be awesome. Thanks.

Closing in favor of https://github.com/grepory/wizardvan/pull/2 -- thank you, though.


AllCops "Exclude" directory is not excluding .irbrc or .pryrc files

Expected behavior
Excluding directory like this:
AllCops:
  Exclude:
    - 'vendor/bundle/**/*'

I expect it to exclude all files in this directory.
Actual behavior
I have errors on two files within this directory: .irbrc and .pryrc
vendor/bundle/ruby/2.4.0/gems/backports-3.6.8/.irbrc:1:1: C: Style/SpecialGlobalVars: Prefer $LOAD_PATH over $:.
$:.unshift "./lib"
^^
vendor/bundle/ruby/2.4.0/gems/backports-3.6.8/.irbrc:1:12: C: Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.
$:.unshift "./lib"
           ^^^^^^^
vendor/bundle/ruby/2.4.0/gems/sidekiq-throttler-0.5.1/.pryrc:1:1: W: Lint/ScriptPermission: Script file .pryrc doesn't have execute permission.
#!/usr/bin/env ruby
^^^^^^^^^^^^^^^^^^^

All other files are correctly excluded.
RuboCop version
$ rubocop -V
0.51.0

Hm. Some problem with globbing and dot-files, I presume. 🤔

It seems so. Chasing it down, I believe the issue is in the match_path? method. In particular, I see the following.
irb(main):033:0> match_path?('vendor/bundle/**/*', 'vendor/bundle/some_subdir/some_file.rb')
=> true
irb(main):034:0> match_path?('vendor/bundle/**/*', 'vendor/bundle/some_subdir/.irbrc.rb')
=> false

Looking into a fix.

Hmm, the existing spec (see here and here) seems to indicate that match_path? is working as intended.
It thus isn't immediately obvious how this should go about getting fixed. Suggestions?

You are correct, the existing spec is working as intended in that it does not match against hidden files by default. From the File class documentation, here's one example:
File.fnmatch('*',   '.profile') #=> false # wildcard doesn't match leading period by default

See: https://ruby-doc.org/core-2.4.0/File.html#method-c-fnmatch-3F
The way to include hidden files is to append the "dotmatch" flag to the fnmatch? call, similar to how it already passes FNM::PATHNAME:
[1] pry(main)> File.fnmatch?('vendor/bundle/**/*', 'vendor/bundle/some_subdir/.irbrc.rb', File::FNM_PATHNAME | File::FNM_DOTMATCH)
=> true

However, I don't know everything about it so am unsure if there are side effects (for example, if it starts matching against other things that aren't expected).
The current RuboCop code only passes the FNM::PATHNAME flag at the moment.
(https://github.com/bbatsov/rubocop/blob/94f55e7c70bdb70fd9ed89f5c5fc70727cd69d1d/lib/rubocop/path_util.rb#L35). I'm new to RuboCop's source code, so I am also unsure if it is intended that the logic doesn't get matched to hidden files. That's up to the more experienced contributors to decide! If it's a desired feature, I can push a pull request up.


bug: mi_heap_contains_block is not consistent with mi_heap_malloc_aligned

to reproduce:
void* res = mi_heap_malloc_aligned(heap_, 33554426, 8);
assert(mi_heap_contains_block(heap_, res));

for sizes smaller than 33554426 this passes. For this size the assertion fails.
tested on v2.0.5

@daanx hello. did you have a chance to look at this bug?

Looks like related to  #570

This is fixed now in the latest release where huge blocks are correctly owned by a heap like all other blocks.


Moved 'Build Hygieia' section

@satishc1  - Moved section to test changes on capitalone.io

@tabladrum @ufx849 LGTM


Widgets html

First and basic structure for new editor HTML.
CR: @javierarce.
cc @viddo

:+1: thanks!


tests/transform: Update version numbers

These tests require an 8.0.x branch
Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket:

Addressed in #1471


Add tests

Either unit tests or integration tests, but we need tests to verify the ArtifactController class

@famartinrh
In my helm chart i've implemented basic e2e test using k3d cluster.
Please use it if you find it helpful.
https://github.com/eshepelyuk/apicurio-registry-helm

Tests were added some time ago.


feat: use next-auth for authentication (#395)

Associated Findable UI pull request: databiosphere/findable-ui#168


docs: add api handler docs

Codecov Report

Merging #1727 (cfea35a) into main (3ba2398) will decrease coverage by 52.71%.
The diff coverage is n/a.

: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
@@             Coverage Diff             @@
##             main    #1727       +/-   ##
===========================================
- Coverage   73.10%   20.40%   -52.71%
===========================================
  Files         389      389
  Lines       46524    46524
===========================================
- Hits        34013     9491    -24522
- Misses      12511    37033    +24522

Flag
Coverage Δ

integration-tests
20.40% <ø> (-0.03%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/rpc/rpc/src/trace.rs
93.33% <ø> (ø)

... and 260 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add Uint reflexion on Oracle & PostgreSQL dialects

In both Oracle and PostgreSQL dialects, it seems that ToSqlType is missing uint handling.
This PR adds reflect.Uint to the types mapped to either integer or serial.

Looking good! Thanks!


ie11 support

Seems that svgs won't render in ie11.  The svg element is empty if inspected.

After dicking around, found out ie11 doesn't support .innerHTML on svg elements.  This is the first google hit polyfill.  Including that, then modify svgicon.vue:

remove v-html directive from template svg element
<svg version="1.1" :class="clazz" :viewBox="box" ref="svg" :style="style"></svg>

inject path on mount

mounted () {
      this.$refs.svg.innerHTML = '\n' + this.path
}

There are definitely more elegant solutions that involve more thought/work, but this will do for me at the moment.  Hope this helps!

another option that doesn't require a polyfill is to wrap around the svg.
template:
<div v-html="svgString" :class="clazz" :style="style">
</div>

computed property:
      svgString () {
        let styleString = ''
        for (let property in this.style)
          styleString += `${ property }: ${ this.style[property] }; `
        return `<svg version="1.1" viewBox="${ this.box }" style="${ styleString }"> ${ this.path } </svg>`
      }

Good work with your investigation @mahlm !
I hope only the README is updated to warn a polyfill is needed for IE11 support.  Many using Vue do not need any IE support (mobile, Electron).  IE11 has only 3.4% global usage, so baking in IE11 support is unneeded IMHO.

I will try to fix it when I get a windows machine. @mahlm

@tomByrer I think we should support IE, because It has many user in my country.

Personally not interested in any extra bloat from polyfills if it added much of anything, I don't even allow logins from older browsers. Totally understand the broader use case for many others though, possibly an opt-in or opt-out feature?
As for IE testing, Microsoft has actually made some official virtual machine images for that exact purpose. Should be free and no signup even needed. Make note of the images expiring though, they suggest just setting a snapshot to roll back.
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

README file is updated. Use  https://github.com/dnozay/innersvg-polyfill to make IE work.

v1.2.0: https://github.com/MMF-FE/vue-svgicon#work-on-ie-and-old-browser


Dependency Conflicts while running run_acme_agent.py

Hey, first of all thank you for the detailed documentation and all the effort you put into this project. Unfortunately the installation for the required libraries for running run_acme_agent.py seems so be quite difficult and I don't find any solution or workaround to deal with all the dependency conflicts.
Do you have a list of all required packages with the corresponding version numbers + the Python version you need to run the code and that does not have any issues? That would be great because from my point of view this script seems to be not usable which is  quite sad. The problems mostly come from the interaction between android_env, acme (including jax/tf), reverb and gym.
I'm working with Linux and also tried It with Mac-ARM system.
Thank you in advance.

Hi @mj-support, what command did you use and do you have logs?
Our pip package is old, but the version at head works. You can install install it with something like pip install .[acme].
Cheers,
Daniel


Refactor: Split core make into multiple functions

Seperate the core factory make method into multiple parts to improve readability, reusability and mainainability.
Verified to work as expected on miob hardware.
In addition, #783 will implement features which require the seperation of parsing and initialization.

The e41651e commit isnt supposed to be in this PR, i will remove it tomorrow

please fix DCOs and I would also like a review from @stv0g. I'm not sure if the logger use is correct.


[FLINK-24373][docs] Remove BETA Tag from FLIP-27 Source Docs

What is the purpose of the change
Remove BETA Tag from FLIP-27 Source Docs. We will backport this to 1.14 release branch.
Does this pull request potentially affect one of the following parts:
Not Relevant
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @fapaul
@wuchong or @leonardBang I feel pretty confident I deleted the relevant section from the translated page but would either of you mind double checking 😅

Thanks @sjwiesman for the contribution, looks good to me both English and Chinese parts.

@fapaul yes sir
Thank you both for the review! Merging into 1.14 and master


[Application Bug] Update the ShowMandatory expression on the No. field on sales / purchase subforms

The "Sales Line Type" field is an extensible enum, allowing us to add new options such as "Internal Comment". Via the OnAfterHasTypeToFillMandatoryFields on table "Sales Line", we're able to bypass the FillMandatoryFields check.
However, on the sales/purchase subforms, the ShowMandatory property of the No. field does not use this function.
We'd like BC to replace the condition (Type <> Type::" ";) by the HasTypeToFillMandatoryFields return value instead (which is already available on most pages via the IsCommentLine variable.)

So can you please review below pages ...

... and change the property to
ShowMandatory = not IsCommentLine;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 53916.


[Feature Request]: Gentoo Ebuild

I would like to ask for permission to develop and later on add an ebuild for Gentoo users to install this fetching app. This would allow Gentoo users to install this fetching package from their portage package manager instead of building it from source by themselves.

@ThamognyaKodi Sure, go ahead.
Don't forget to update the README with instructions to install on Gentoo.

Thank you for the confirmation @deepjyoti30 .


Layer: calculate node_and_value_count non-recursive

Calculate the node_and_value count in a more imperative way for better performance and a smaller stack.

Codecov Report

Merging #20 into master will decrease coverage by 0.04%.
The diff coverage is 56.25%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
- Coverage   73.66%   73.62%   -0.05%
==========================================
  Files          20       20
  Lines        6240     6271      +31
  Branches      904      906       +2
==========================================
+ Hits         4597     4617      +20
- Misses        747      756       +9
- Partials      896      898       +2

Impacted Files
Coverage Δ

src/layer/layer.rs
57.69% <ø> (ø)
:arrow_up:

src/store/mod.rs
50.53% <0%> (-1.12%)
:arrow_down:

src/store/sync.rs
36.79% <0%> (-1.08%)
:arrow_down:

src/layer/base.rs
81.21% <100%> (+0.61%)
:arrow_up:

src/layer/child.rs
77.11% <85.71%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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