Error initializing datadog on ios (expo eject project) TypeError: null is not an object (evaluating '_$$_REQUIRE(_dependencyMap[13], "./sdk/DdSdk").DdSdk.initialize')

Describe what happened
TypeError: null is not an object (evaluating '_$$_REQUIRE(_dependencyMap[13], "./sdk/DdSdk").DdSdk.initialize')

import {
  BatchSize,
  DatadogProvider,
  DatadogProviderConfiguration,
  SdkVerbosity,
  UploadFrequency,
} from '@datadog/mobile-react-native';

const datadogConfiguration = new DatadogProviderConfiguration(
  'client id',
  ENV,
  'app id',
  true, // track User interactions (e.g.: Tap on buttons. You can use 'accessibilityLabel' element property to give tap action the name, otherwise element type will be reported)
  true, // track XHR Resources
  true, // track Errors
);

   <DatadogProvider configuration={datadogConfiguration}>

        <AppNavigator />

    </DatadogProvider>

Additional context

Version of the SDK: 2.1.0
Version of React Native: 0.69.4

Hi @lurdharry, thanks for reaching out!
To help us troubleshoot your case, could you specify which steps you ran as part when installing @datadog/mobile-react-native? Specifically, did you run (cd ios && pod install) and re-built your application?
Thanks!

Yes, I did!
I even add to install expo-datadog  because it’s an expo eject project but
I still get the same error
On Tue, Feb 13, 2024 at 2:04 PM Louis Zawadzki @.***>
wrote:

Hi @lurdharry https://github.com/lurdharry, thanks for reaching out!
To help us troubleshoot your case, could you specify which steps you ran
as part when installing @datadog/mobile-react-native? Specifically, did
you run (cd ios && pod install) and re-built your application?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/DataDog/dd-sdk-reactnative/issues/610#issuecomment-1941473563,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL54N6T5ZV77ILAP5EVSCOLYTNQGJAVCNFSM6AAAAABDGMNTOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRGQ3TGNJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @lurdharry, thanks for coming back with this information!
Could you share how you ejected the expo app and how you build your application?
If you could include a copy of your ios/Podfile.lock file that would help as well.
Thanks a lot!

PODS:
  - appcenter-analytics (4.4.5):
    - AppCenter/Analytics (~> 4.0)
    - AppCenterReactNativeShared (~> 4.0)
    - React-Core
  - appcenter-core (4.4.5):
    - AppCenterReactNativeShared (~> 4.0)
    - React-Core
  - appcenter-crashes (4.4.5):
    - AppCenter/Crashes (~> 4.0)
    - AppCenterReactNativeShared (~> 4.0)
    - React-Core
  - AppCenter/Analytics (4.4.3):
    - AppCenter/Core
  - AppCenter/Core (4.4.3)
  - AppCenter/Crashes (4.4.3):
    - AppCenter/Core
  - AppCenterReactNativeShared (4.4.5):
    - AppCenter/Core (= 4.4.3)
  - Base64 (1.1.2)
  - boost (1.76.0)
  - BVLinearGradient (2.6.2):
    - React-Core
  - CodePush (7.0.5):
    - Base64 (~> 1.1)
    - JWT (~> 3.0.0-beta.12)
    - React-Core
    - SSZipArchive (~> 2.2.2)
  - DoubleConversion (1.1.6)
  - EXApplication (4.2.2):
    - ExpoModulesCore
  - EXConstants (13.2.4):
    - ExpoModulesCore
  - EXErrorRecovery (3.2.0):
    - ExpoModulesCore
  - EXFileSystem (14.1.0):
    - ExpoModulesCore
  - EXFont (10.2.0):
    - ExpoModulesCore
  - Expo (46.0.10):
    - ExpoModulesCore
  - ExpoKeepAwake (10.2.0):
    - ExpoModulesCore
  - ExpoModulesCore (0.11.5):
    - React-Core
    - ReactCommon/turbomodule/core
  - EXSplashScreen (0.16.2):
    - ExpoModulesCore
    - React-Core
  - FBLazyVector (0.69.4)
  - FBReactNativeSpec (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTRequired (= 0.69.4)
    - RCTTypeSafety (= 0.69.4)
    - React-Core (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - Firebase/Analytics (9.4.0):
    - Firebase/Core
  - Firebase/Core (9.4.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (~> 9.4.0)
  - Firebase/CoreOnly (9.4.0):
    - FirebaseCore (= 9.4.0)
  - Firebase/Crashlytics (9.4.0):
    - Firebase/CoreOnly
    - FirebaseCrashlytics (~> 9.4.0)
  - Firebase/Messaging (9.4.0):
    - Firebase/CoreOnly
    - FirebaseMessaging (~> 9.4.0)
  - FirebaseAnalytics (9.4.0):
    - FirebaseAnalytics/AdIdSupport (= 9.4.0)
    - FirebaseCore (~> 9.0)
    - FirebaseInstallations (~> 9.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - FirebaseAnalytics/AdIdSupport (9.4.0):
    - FirebaseCore (~> 9.0)
    - FirebaseInstallations (~> 9.0)
    - GoogleAppMeasurement (= 9.4.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - FirebaseCore (9.4.0):
    - FirebaseCoreDiagnostics (~> 9.0)
    - FirebaseCoreInternal (~> 9.0)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Logger (~> 7.7)
  - FirebaseCoreDiagnostics (9.6.0):
    - GoogleDataTransport (< 10.0.0, >= 9.1.4)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Logger (~> 7.7)
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - FirebaseCoreExtension (9.4.0):
    - FirebaseCore (~> 9.0)
  - FirebaseCoreInternal (9.6.0):
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
  - FirebaseCrashlytics (9.4.0):
    - FirebaseCore (~> 9.0)
    - FirebaseInstallations (~> 9.0)
    - GoogleDataTransport (< 10.0.0, >= 9.1.4)
    - GoogleUtilities/Environment (~> 7.7)
    - nanopb (< 2.30910.0, >= 2.30908.0)
    - PromisesObjC (~> 2.1)
  - FirebaseInstallations (9.6.0):
    - FirebaseCore (~> 9.0)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/UserDefaults (~> 7.7)
    - PromisesObjC (~> 2.1)
  - FirebaseMessaging (9.4.0):
    - FirebaseCore (~> 9.0)
    - FirebaseInstallations (~> 9.0)
    - GoogleDataTransport (< 10.0.0, >= 9.1.4)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/Environment (~> 7.7)
    - GoogleUtilities/Reachability (~> 7.7)
    - GoogleUtilities/UserDefaults (~> 7.7)
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - fmt (6.2.1)
  - glog (0.3.5)
  - GoogleAppMeasurement (9.4.0):
    - GoogleAppMeasurement/AdIdSupport (= 9.4.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleAppMeasurement/AdIdSupport (9.4.0):
    - GoogleAppMeasurement/WithoutAdIdSupport (= 9.4.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleAppMeasurement/WithoutAdIdSupport (9.4.0):
    - GoogleUtilities/AppDelegateSwizzler (~> 7.7)
    - GoogleUtilities/MethodSwizzler (~> 7.7)
    - GoogleUtilities/Network (~> 7.7)
    - "GoogleUtilities/NSData+zlib (~> 7.7)"
    - nanopb (< 2.30910.0, >= 2.30908.0)
  - GoogleDataTransport (9.3.0):
    - GoogleUtilities/Environment (~> 7.7)
    - nanopb (< 2.30910.0, >= 2.30908.0)
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/AppDelegateSwizzler (7.12.0):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
  - GoogleUtilities/Environment (7.12.0):
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/Logger (7.12.0):
    - GoogleUtilities/Environment
  - GoogleUtilities/MethodSwizzler (7.12.0):
    - GoogleUtilities/Logger
  - GoogleUtilities/Network (7.12.0):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.12.0)"
  - GoogleUtilities/Reachability (7.12.0):
    - GoogleUtilities/Logger
  - GoogleUtilities/UserDefaults (7.12.0):
    - GoogleUtilities/Logger
  - Intercom (12.4.3)
  - intercom-react-native (3.0.5):
    - Intercom (~> 12.4.3)
    - React-Core
  - JWT (3.0.0-beta.14):
    - Base64 (~> 1.1.2)
  - lottie-ios (3.4.0)
  - lottie-react-native (5.1.4):
    - lottie-ios (~> 3.4.0)
    - React-Core
  - nanopb (2.30909.1):
    - nanopb/decode (= 2.30909.1)
    - nanopb/encode (= 2.30909.1)
  - nanopb/decode (2.30909.1)
  - nanopb/encode (2.30909.1)
  - PromisesObjC (2.3.1)
  - RCT-Folly (2<IP_ADDRESS>-v2):
    - boost
    - DoubleConversion
    - fmt (~> 6.2.1)
    - glog
    - RCT-Folly/Default (= 2<IP_ADDRESS>-v2)
  - RCT-Folly/Default (2<IP_ADDRESS>-v2):
    - boost
    - DoubleConversion
    - fmt (~> 6.2.1)
    - glog
  - RCTRequired (0.69.4)
  - RCTTypeSafety (0.69.4):
    - FBLazyVector (= 0.69.4)
    - RCTRequired (= 0.69.4)
    - React-Core (= 0.69.4)
  - React (0.69.4):
    - React-Core (= 0.69.4)
    - React-Core/DevSupport (= 0.69.4)
    - React-Core/RCTWebSocket (= 0.69.4)
    - React-RCTActionSheet (= 0.69.4)
    - React-RCTAnimation (= 0.69.4)
    - React-RCTBlob (= 0.69.4)
    - React-RCTImage (= 0.69.4)
    - React-RCTLinking (= 0.69.4)
    - React-RCTNetwork (= 0.69.4)
    - React-RCTSettings (= 0.69.4)
    - React-RCTText (= 0.69.4)
    - React-RCTVibration (= 0.69.4)
  - React-bridging (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-jsi (= 0.69.4)
  - React-callinvoker (0.69.4)
  - React-Codegen (0.69.4):
    - FBReactNativeSpec (= 0.69.4)
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTRequired (= 0.69.4)
    - RCTTypeSafety (= 0.69.4)
    - React-Core (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-Core (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.69.4)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/CoreModulesHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/Default (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/DevSupport (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.69.4)
    - React-Core/RCTWebSocket (= 0.69.4)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-jsinspector (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTActionSheetHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTAnimationHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTBlobHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTImageHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTLinkingHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTNetworkHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTSettingsHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTTextHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTVibrationHeaders (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-Core/RCTWebSocket (0.69.4):
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Core/Default (= 0.69.4)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsiexecutor (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - Yoga
  - React-CoreModules (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.69.4)
    - React-Codegen (= 0.69.4)
    - React-Core/CoreModulesHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-RCTImage (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-cxxreact (0.69.4):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-callinvoker (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-jsinspector (= 0.69.4)
    - React-logger (= 0.69.4)
    - React-perflogger (= 0.69.4)
    - React-runtimeexecutor (= 0.69.4)
  - React-jsi (0.69.4):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-jsi/Default (= 0.69.4)
  - React-jsi/Default (0.69.4):
    - boost (= 1.76.0)
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
  - React-jsiexecutor (0.69.4):
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-perflogger (= 0.69.4)
  - React-jsinspector (0.69.4)
  - React-logger (0.69.4):
    - glog
  - react-native-config (1.4.6):
    - react-native-config/App (= 1.4.6)
  - react-native-config/App (1.4.6):
    - React-Core
  - react-native-netinfo (9.3.0):
    - React-Core
  - react-native-pager-view (5.4.25):
    - React-Core
  - react-native-safe-area-context (4.3.3):
    - RCT-Folly
    - RCTRequired
    - RCTTypeSafety
    - React-Core
    - ReactCommon/turbomodule/core
  - react-native-sensitive-info (6.0.0-alpha.9):
    - React-Core
  - React-perflogger (0.69.4)
  - React-RCTActionSheet (0.69.4):
    - React-Core/RCTActionSheetHeaders (= 0.69.4)
  - React-RCTAnimation (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.69.4)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTAnimationHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTBlob (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTBlobHeaders (= 0.69.4)
    - React-Core/RCTWebSocket (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-RCTNetwork (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTImage (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.69.4)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTImageHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-RCTNetwork (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTLinking (0.69.4):
    - React-Codegen (= 0.69.4)
    - React-Core/RCTLinkingHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTNetwork (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.69.4)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTNetworkHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTSettings (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - RCTTypeSafety (= 0.69.4)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTSettingsHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-RCTText (0.69.4):
    - React-Core/RCTTextHeaders (= 0.69.4)
  - React-RCTVibration (0.69.4):
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-Codegen (= 0.69.4)
    - React-Core/RCTVibrationHeaders (= 0.69.4)
    - React-jsi (= 0.69.4)
    - ReactCommon/turbomodule/core (= 0.69.4)
  - React-runtimeexecutor (0.69.4):
    - React-jsi (= 0.69.4)
  - ReactCommon/turbomodule/core (0.69.4):
    - DoubleConversion
    - glog
    - RCT-Folly (= 2<IP_ADDRESS>-v2)
    - React-bridging (= 0.69.4)
    - React-callinvoker (= 0.69.4)
    - React-Core (= 0.69.4)
    - React-cxxreact (= 0.69.4)
    - React-jsi (= 0.69.4)
    - React-logger (= 0.69.4)
    - React-perflogger (= 0.69.4)
  - RNCAsyncStorage (1.17.9):
    - React-Core
  - RNCClipboard (1.11.2):
    - React-Core
  - RNCMaskedView (0.2.7):
    - React-Core
  - RNDeviceInfo (10.0.2):
    - React-Core
  - RNFBAnalytics (15.3.0):
    - Firebase/Analytics (= 9.4.0)
    - React-Core
    - RNFBApp
  - RNFBApp (15.3.0):
    - Firebase/CoreOnly (= 9.4.0)
    - React-Core
  - RNFBCrashlytics (15.3.0):
    - Firebase/Crashlytics (= 9.4.0)
    - FirebaseCoreExtension (= 9.4.0)
    - React-Core
    - RNFBApp
  - RNFBMessaging (15.3.0):
    - Firebase/Messaging (= 9.4.0)
    - FirebaseCoreExtension (= 9.4.0)
    - React-Core
    - RNFBApp
  - RNGestureHandler (2.5.0):
    - React-Core
  - RNInAppBrowser (3.7.0):
    - React-Core
  - RNLocalize (3.0.2):
    - React-Core
  - RNNotifee (5.7.0):
    - React-Core
    - RNNotifee/NotifeeCore (= 5.7.0)
  - RNNotifee/NotifeeCore (5.7.0):
    - React-Core
  - RNReanimated (2.10.0):
    - DoubleConversion
    - FBLazyVector
    - FBReactNativeSpec
    - glog
    - RCT-Folly
    - RCTRequired
    - RCTTypeSafety
    - React-callinvoker
    - React-Core
    - React-Core/DevSupport
    - React-Core/RCTWebSocket
    - React-CoreModules
    - React-cxxreact
    - React-jsi
    - React-jsiexecutor
    - React-jsinspector
    - React-RCTActionSheet
    - React-RCTAnimation
    - React-RCTBlob
    - React-RCTImage
    - React-RCTLinking
    - React-RCTNetwork
    - React-RCTSettings
    - React-RCTText
    - ReactCommon/turbomodule/core
    - Yoga
  - RNScreens (3.16.0):
    - React-Core
    - React-RCTImage
  - RNSVG (13.0.0):
    - React-Core
  - SSZipArchive (2.2.3)
  - Yoga (1.14.0)

DEPENDENCIES:
  - appcenter-analytics (from `../node_modules/appcenter-analytics`)
  - appcenter-core (from `../node_modules/appcenter`)
  - appcenter-crashes (from `../node_modules/appcenter-crashes`)
  - boost (from `../node_modules/react-native/third-party-podspecs/boost.podspec`)
  - BVLinearGradient (from `../node_modules/react-native-linear-gradient`)
  - CodePush (from `../node_modules/react-native-code-push`)
  - DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)
  - EXApplication (from `../node_modules/expo-application/ios`)
  - EXConstants (from `../node_modules/expo-constants/ios`)
  - EXErrorRecovery (from `../node_modules/expo-error-recovery/ios`)
  - EXFileSystem (from `../node_modules/expo-file-system/ios`)
  - EXFont (from `../node_modules/expo-font/ios`)
  - Expo (from `../node_modules/expo`)
  - ExpoKeepAwake (from `../node_modules/expo-keep-awake/ios`)
  - ExpoModulesCore (from `../node_modules/expo-modules-core/ios`)
  - EXSplashScreen (from `../node_modules/expo-splash-screen/ios`)
  - FBLazyVector (from `../node_modules/react-native/Libraries/FBLazyVector`)
  - FBReactNativeSpec (from `../node_modules/react-native/React/FBReactNativeSpec`)
  - glog (from `../node_modules/react-native/third-party-podspecs/glog.podspec`)
  - "intercom-react-native (from `../node_modules/@intercom/intercom-react-native`)"
  - lottie-ios (from `../node_modules/lottie-ios`)
  - lottie-react-native (from `../node_modules/lottie-react-native`)
  - RCT-Folly (from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`)
  - RCTRequired (from `../node_modules/react-native/Libraries/RCTRequired`)
  - RCTTypeSafety (from `../node_modules/react-native/Libraries/TypeSafety`)
  - React (from `../node_modules/react-native/`)
  - React-bridging (from `../node_modules/react-native/ReactCommon`)
  - React-callinvoker (from `../node_modules/react-native/ReactCommon/callinvoker`)
  - React-Codegen (from `build/generated/ios`)
  - React-Core (from `../node_modules/react-native/`)
  - React-Core/RCTWebSocket (from `../node_modules/react-native/`)
  - React-CoreModules (from `../node_modules/react-native/React/CoreModules`)
  - React-cxxreact (from `../node_modules/react-native/ReactCommon/cxxreact`)
  - React-jsi (from `../node_modules/react-native/ReactCommon/jsi`)
  - React-jsiexecutor (from `../node_modules/react-native/ReactCommon/jsiexecutor`)
  - React-jsinspector (from `../node_modules/react-native/ReactCommon/jsinspector`)
  - React-logger (from `../node_modules/react-native/ReactCommon/logger`)
  - react-native-config (from `../node_modules/react-native-config`)
  - "react-native-netinfo (from `../node_modules/@react-native-community/netinfo`)"
  - react-native-pager-view (from `../node_modules/react-native-pager-view`)
  - react-native-safe-area-context (from `../node_modules/react-native-safe-area-context`)
  - react-native-sensitive-info (from `../node_modules/react-native-sensitive-info`)
  - React-perflogger (from `../node_modules/react-native/ReactCommon/reactperflogger`)
  - React-RCTActionSheet (from `../node_modules/react-native/Libraries/ActionSheetIOS`)
  - React-RCTAnimation (from `../node_modules/react-native/Libraries/NativeAnimation`)
  - React-RCTBlob (from `../node_modules/react-native/Libraries/Blob`)
  - React-RCTImage (from `../node_modules/react-native/Libraries/Image`)
  - React-RCTLinking (from `../node_modules/react-native/Libraries/LinkingIOS`)
  - React-RCTNetwork (from `../node_modules/react-native/Libraries/Network`)
  - React-RCTSettings (from `../node_modules/react-native/Libraries/Settings`)
  - React-RCTText (from `../node_modules/react-native/Libraries/Text`)
  - React-RCTVibration (from `../node_modules/react-native/Libraries/Vibration`)
  - React-runtimeexecutor (from `../node_modules/react-native/ReactCommon/runtimeexecutor`)
  - ReactCommon/turbomodule/core (from `../node_modules/react-native/ReactCommon`)
  - "RNCAsyncStorage (from `../node_modules/@react-native-async-storage/async-storage`)"
  - "RNCClipboard (from `../node_modules/@react-native-clipboard/clipboard`)"
  - "RNCMaskedView (from `../node_modules/@react-native-masked-view/masked-view`)"
  - RNDeviceInfo (from `../node_modules/react-native-device-info`)
  - "RNFBAnalytics (from `../node_modules/@react-native-firebase/analytics`)"
  - "RNFBApp (from `../node_modules/@react-native-firebase/app`)"
  - "RNFBCrashlytics (from `../node_modules/@react-native-firebase/crashlytics`)"
  - "RNFBMessaging (from `../node_modules/@react-native-firebase/messaging`)"
  - RNGestureHandler (from `../node_modules/react-native-gesture-handler`)
  - RNInAppBrowser (from `../node_modules/react-native-inappbrowser-reborn`)
  - RNLocalize (from `../node_modules/react-native-localize`)
  - "RNNotifee (from `../node_modules/@notifee/react-native`)"
  - RNReanimated (from `../node_modules/react-native-reanimated`)
  - RNScreens (from `../node_modules/react-native-screens`)
  - RNSVG (from `../node_modules/react-native-svg`)
  - Yoga (from `../node_modules/react-native/ReactCommon/yoga`)

SPEC REPOS:
  trunk:
    - AppCenter
    - AppCenterReactNativeShared
    - Base64
    - Firebase
    - FirebaseAnalytics
    - FirebaseCore
    - FirebaseCoreDiagnostics
    - FirebaseCoreExtension
    - FirebaseCoreInternal
    - FirebaseCrashlytics
    - FirebaseInstallations
    - FirebaseMessaging
    - fmt
    - GoogleAppMeasurement
    - GoogleDataTransport
    - GoogleUtilities
    - Intercom
    - JWT
    - nanopb
    - PromisesObjC
    - SSZipArchive

EXTERNAL SOURCES:
  appcenter-analytics:
    :path: "../node_modules/appcenter-analytics"
  appcenter-core:
    :path: "../node_modules/appcenter"
  appcenter-crashes:
    :path: "../node_modules/appcenter-crashes"
  boost:
    :podspec: "../node_modules/react-native/third-party-podspecs/boost.podspec"
  BVLinearGradient:
    :path: "../node_modules/react-native-linear-gradient"
  CodePush:
    :path: "../node_modules/react-native-code-push"
  DoubleConversion:
    :podspec: "../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec"
  EXApplication:
    :path: "../node_modules/expo-application/ios"
  EXConstants:
    :path: "../node_modules/expo-constants/ios"
  EXErrorRecovery:
    :path: "../node_modules/expo-error-recovery/ios"
  EXFileSystem:
    :path: "../node_modules/expo-file-system/ios"
  EXFont:
    :path: "../node_modules/expo-font/ios"
  Expo:
    :path: "../node_modules/expo"
  ExpoKeepAwake:
    :path: "../node_modules/expo-keep-awake/ios"
  ExpoModulesCore:
    :path: "../node_modules/expo-modules-core/ios"
  EXSplashScreen:
    :path: "../node_modules/expo-splash-screen/ios"
  FBLazyVector:
    :path: "../node_modules/react-native/Libraries/FBLazyVector"
  FBReactNativeSpec:
    :path: "../node_modules/react-native/React/FBReactNativeSpec"
  glog:
    :podspec: "../node_modules/react-native/third-party-podspecs/glog.podspec"
  intercom-react-native:
    :path: "../node_modules/@intercom/intercom-react-native"
  lottie-ios:
    :path: "../node_modules/lottie-ios"
  lottie-react-native:
    :path: "../node_modules/lottie-react-native"
  RCT-Folly:
    :podspec: "../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec"
  RCTRequired:
    :path: "../node_modules/react-native/Libraries/RCTRequired"
  RCTTypeSafety:
    :path: "../node_modules/react-native/Libraries/TypeSafety"
  React:
    :path: "../node_modules/react-native/"
  React-bridging:
    :path: "../node_modules/react-native/ReactCommon"
  React-callinvoker:
    :path: "../node_modules/react-native/ReactCommon/callinvoker"
  React-Codegen:
    :path: build/generated/ios
  React-Core:
    :path: "../node_modules/react-native/"
  React-CoreModules:
    :path: "../node_modules/react-native/React/CoreModules"
  React-cxxreact:
    :path: "../node_modules/react-native/ReactCommon/cxxreact"
  React-jsi:
    :path: "../node_modules/react-native/ReactCommon/jsi"
  React-jsiexecutor:
    :path: "../node_modules/react-native/ReactCommon/jsiexecutor"
  React-jsinspector:
    :path: "../node_modules/react-native/ReactCommon/jsinspector"
  React-logger:
    :path: "../node_modules/react-native/ReactCommon/logger"
  react-native-config:
    :path: "../node_modules/react-native-config"
  react-native-netinfo:
    :path: "../node_modules/@react-native-community/netinfo"
  react-native-pager-view:
    :path: "../node_modules/react-native-pager-view"
  react-native-safe-area-context:
    :path: "../node_modules/react-native-safe-area-context"
  react-native-sensitive-info:
    :path: "../node_modules/react-native-sensitive-info"
  React-perflogger:
    :path: "../node_modules/react-native/ReactCommon/reactperflogger"
  React-RCTActionSheet:
    :path: "../node_modules/react-native/Libraries/ActionSheetIOS"
  React-RCTAnimation:
    :path: "../node_modules/react-native/Libraries/NativeAnimation"
  React-RCTBlob:
    :path: "../node_modules/react-native/Libraries/Blob"
  React-RCTImage:
    :path: "../node_modules/react-native/Libraries/Image"
  React-RCTLinking:
    :path: "../node_modules/react-native/Libraries/LinkingIOS"
  React-RCTNetwork:
    :path: "../node_modules/react-native/Libraries/Network"
  React-RCTSettings:
    :path: "../node_modules/react-native/Libraries/Settings"
  React-RCTText:
    :path: "../node_modules/react-native/Libraries/Text"
  React-RCTVibration:
    :path: "../node_modules/react-native/Libraries/Vibration"
  React-runtimeexecutor:
    :path: "../node_modules/react-native/ReactCommon/runtimeexecutor"
  ReactCommon:
    :path: "../node_modules/react-native/ReactCommon"
  RNCAsyncStorage:
    :path: "../node_modules/@react-native-async-storage/async-storage"
  RNCClipboard:
    :path: "../node_modules/@react-native-clipboard/clipboard"
  RNCMaskedView:
    :path: "../node_modules/@react-native-masked-view/masked-view"
  RNDeviceInfo:
    :path: "../node_modules/react-native-device-info"
  RNFBAnalytics:
    :path: "../node_modules/@react-native-firebase/analytics"
  RNFBApp:
    :path: "../node_modules/@react-native-firebase/app"
  RNFBCrashlytics:
    :path: "../node_modules/@react-native-firebase/crashlytics"
  RNFBMessaging:
    :path: "../node_modules/@react-native-firebase/messaging"
  RNGestureHandler:
    :path: "../node_modules/react-native-gesture-handler"
  RNInAppBrowser:
    :path: "../node_modules/react-native-inappbrowser-reborn"
  RNLocalize:
    :path: "../node_modules/react-native-localize"
  RNNotifee:
    :path: "../node_modules/@notifee/react-native"
  RNReanimated:
    :path: "../node_modules/react-native-reanimated"
  RNScreens:
    :path: "../node_modules/react-native-screens"
  RNSVG:
    :path: "../node_modules/react-native-svg"
  Yoga:
    :path: "../node_modules/react-native/ReactCommon/yoga"

SPEC CHECKSUMS:
  AppCenter: 3fd04aa1b166e16fdb03ec81dabe488aece83fbd
  appcenter-analytics: 1aea9ada8922d2e2df3e069a28eda21157c9d30d
  appcenter-core: c593b2e4ac28d6a21b6a217c4a5e6b3de7b0b00f
  appcenter-crashes: d9ae1c9296974c1c433600fa2f320e0ba1f12bdf
  AppCenterReactNativeShared: f395caeabde0dc3a11609dbcb737d0f14cd40e79
  Base64: cecfb41a004124895a7bcee567a89bae5a89d49b
  boost: a7c83b31436843459a1961bfd74b96033dc77234
  BVLinearGradient: 34a999fda29036898a09c6a6b728b0b4189e1a44
  CodePush: ef496b6fd053012e985e3d4a0ab9f9dbf2739eac
  DoubleConversion: 5189b271737e1565bdce30deb4a08d647e3f5f54
  EXApplication: e418d737a036e788510f2c4ad6c10a7d54d18586
  EXConstants: 7c44785d41d8e959d527d23d29444277a4d1ee73
  EXErrorRecovery: 74d71ee59f6814315457b09d68e86aa95cc7d05d
  EXFileSystem: 927e0a8885aa9c49e50fc38eaba2c2389f2f1019
  EXFont: a5d80bd9b3452b2d5abbce2487da89b0150e6487
  Expo: fcdb32274e2ca9c7638d3b21b30fb665c6869219
  ExpoKeepAwake: 0e8f18142e71bbf2c7f6aa66ebed249ba1420320
  ExpoModulesCore: 5a973701f4400d70254bc836305228731c829010
  EXSplashScreen: 799bece80089219b2c989c1082d70f3b00995cda
  FBLazyVector: c71b8c429a8af2aff1013934a7152e9d9d0c937d
  FBReactNativeSpec: cb0df4f0084281b394f76bb9b4d1d9540f35963f
  Firebase: 7703fc4022824b6d6db1bf7bea58d13b8e17ec46
  FirebaseAnalytics: a1a24e72b7ba7f47045a4633f1abb545c07bd29c
  FirebaseCore: 9a2b10270a854731c4d4d8a97d0aa8380ec3458d
  FirebaseCoreDiagnostics: 99a495094b10a57eeb3ae8efa1665700ad0bdaa6
  FirebaseCoreExtension: 2cf8c542b54ad3c2d4b746c22e8828b670dcd9b0
  FirebaseCoreInternal: bca76517fe1ed381e989f5e7d8abb0da8d85bed3
  FirebaseCrashlytics: 121ea1d37f4906c94c4c9307297af5121b98b789
  FirebaseInstallations: 0a115432c4e223c5ab20b0dbbe4cbefa793a0e8e
  FirebaseMessaging: 4e220eddd356181469ba2ec5f7d5fafbc2312841
  fmt: ff9d55029c625d3757ed641535fd4a75fedc7ce9
  glog: 3d02b25ca00c2d456734d0bcff864cbc62f6ae1a
  GoogleAppMeasurement: 5d69e04287fc2c10cc43724bfa4bf31fc12c3dff
  GoogleDataTransport: 57c22343ab29bc686febbf7cbb13bad167c2d8fe
  GoogleUtilities: 0759d1a57ebb953965c2dfe0ba4c82e95ccc2e34
  Intercom: 43bfacc55b1c93cce9ec569833696d3f15678430
  intercom-react-native: b2a48297f0ed988970c819133cabe8c965080003
  JWT: ef71dfb03e1f842081e64dc42eef0e164f35d251
  lottie-ios:<PHONE_NUMBER>1a378fdc7d1bb4c5930347e37baf1f
  lottie-react-native: b702fab740cdb952a8e2354713d3beda63ff97b0
  nanopb: d4d75c12cd1316f4a64e3c6963f879ecd4b5e0d5
  PromisesObjC: c50d2056b5253dadbd6c2bea79b0674bd5a52fa4
  RCT-Folly: b9d9fe1fc70114b751c076104e52f3b1b5e5a95a
  RCTRequired: bd9d2ab0fda10171fcbcf9ba61a7df4dc15a28f4
  RCTTypeSafety: e44e139bf6ec8042db396201834fc2372f6a21cd
  React: 482cd1ba23c471be1aed3800180be2427418d7be
  React-bridging: c2ea4fed6fe4ed27c12fd71e88b5d5d3da107fde
  React-callinvoker: d4d1f98163fb5e35545e910415ef6c04796bb188
  React-Codegen: ff35fb9c7f6ec2ed34fb6de2e1099d88dfb25f2f
  React-Core: 4d3443a45b67c71d74d7243ddde9569d1e4f4fad
  React-CoreModules: 70be25399366b5632ab18ecf6fe444a8165a7bea
  React-cxxreact: 822d3794fc0bf206f4691592f90e086dd4f92228
  React-jsi: ffa51cbc9a78cc156cf61f79ed52ecb76dc6013b
  React-jsiexecutor: a27badbbdbc0ff781813370736a2d1c7261181d4
  React-jsinspector: 8a3d3f5dcd23a91e8c80b1bf0e96902cd1dca999
  React-logger: 1088859f145b8f6dd0d3ed051a647ef0e3e80fad
  react-native-config: 7cd105e71d903104e8919261480858940a6b9c0e
  react-native-netinfo: 129bd99f607a2dc5bb096168f3e5c150fd1f1c95
  react-native-pager-view: da490aa1f902c9a5aeecf0909cc975ad0e92e53e
  react-native-safe-area-context: b456e1c40ec86f5593d58b275bd0e9603169daca
  react-native-sensitive-info: d44e909d065f9c0e15734245e5dd6a24b82e3dcd
  React-perflogger: cb386fd44c97ec7f8199c04c12b22066b0f2e1e0
  React-RCTActionSheet: f803a85e46cf5b4066c2ac5e122447f918e9c6e5
  React-RCTAnimation: 19c80fa950ccce7f4db76a2a7f2cf79baae07fc7
  React-RCTBlob: f36ab97e2d515c36df14a1571e50056be80413d5
  React-RCTImage: 2c8f0a329a116248e82f8972ffe806e47c6d1cfa
  React-RCTLinking: 670f0223075aff33be3b89714f1da4f5343fc4af
  React-RCTNetwork: 09385b73f4ff1f46bd5d749540fb33f69a7e5908
  React-RCTSettings: 33b12d3ac7a1f2eba069ec7bd1b84345263b3bbe
  React-RCTText: a1a3ea902403bd9ae4cf6f7960551dc1d25711b5
  React-RCTVibration: 9adb4a3cbb598d1bbd46a05256f445e4b8c70603
  React-runtimeexecutor: 61ee22a8cdf8b6bb2a7fb7b4ba2cc763e5285196
  ReactCommon: 8f67bd7e0a6afade0f20718f859dc8c2275f2e83
  RNCAsyncStorage: b2489b49e38c85e10ed45a888d13a2a4c7b32ea1
  RNCClipboard: 3f0451a8100393908bea5c5c5b16f96d45f30bfc
  RNCMaskedView: cb9670ea9239998340eaab21df13fa12a1f9de15
  RNDeviceInfo: 0a7c1d2532aa7691f9b9925a27e43af006db4dae
  RNFBAnalytics: dae2f8d9eff3c51e982bb7af3b734e0cd7a8a7de
  RNFBApp: 0db41be0ca09ec0828164f16cd36732c0df8dabb
  RNFBCrashlytics: c09c159648f509a8a70b35a874c73e3f8e147ccf
  RNFBMessaging: b75bbb60959cd67302b78e198b92b34a331843fb
  RNGestureHandler: bad495418bcbd3ab47017a38d93d290ebd406f50
  RNInAppBrowser: e36d6935517101ccba0e875bac8ad7b0cb655364
  RNLocalize: dbea38dcb344bf80ff18a1757b1becf11f70cae4
  RNNotifee: 5155e0a5e0a97d0c839030d8192783cd63053999
  RNReanimated: 7faa787e8d4493fbc95fab2ad331fa7625828cfa
  RNScreens: ee31ecdf23fe81e93c74feaa086cf173d758ab58
  RNSVG: 42a0c731b11179ebbd27a3eeeafa7201ebb476ff
  SSZipArchive: 62d4947b08730e4cda640473b0066d209ff033c9
  Yoga: ff994563b2fd98c982ca58e8cd9db2cdaf4dda74

PODFILE CHECKSUM: 056f3cbc094e74bc418e6f11024858977b8ce0ce

COCOAPODS: 1.14.3

Thanks for sharing this @lurdharry!
Indeed it looks like the DatadogSDKReactNative pod is not present in your Podfile.lock.
Could you check that the file located at<EMAIL_ADDRESS>exists?
If so, can you share the output of pod install when you run it?

yes, the file is there.
this is the output of pod install
Installing DatadogCore (2.6.0)
Installing DatadogCrashReporting (2.6.0)
Installing DatadogInternal (2.6.0)
Installing DatadogLogs (2.6.0)
Installing DatadogRUM (2.6.0)
Installing DatadogSDKReactNative (2.1.0)
Installing DatadogTrace (2.6.0)
Installing DatadogWebViewTracking (2.6.0)
Installing GoogleDataTransport 9.3.0 (was 9.2.0)
Installing GoogleUtilities 7.12.0 (was 7.10.0)
Installing PLCrashReporter (1.11.1)
Installing PromisesObjC 2.3.1 (was 2.1.1)
Installing nanopb 2.30909.1 (was 2.30909.0)
[!] The 'Pods-AwakeLabsMobile' target has transitive dependencies that include statically linked binaries: (DatadogCrashReporting)

Thanks so much.
the solution works 🤩.


Pointer Compression to enable 8G Loom

Description
Resolves #163
In fulfillment of https://urbit.org/grants/loom-pointer-compression
Benchmark
Basic brass pill fakezod boot benchmark - x86_64 linux
Pay primary attention to Elapsed (wall clock) time, Maximum resident set size (kbytes) and Major (requiring I/O) page faults
Takeaway
We expected increased memory usage because this is naturally a tradeoff of
alignment. Do note, that runs (2) and (3) included changes to align the stack
as well as the heap. In the run without stack alignment (4) you can see that
stack alignment has no effect on max RSS -- at least when booting from a
pill. From some basic evaluation in gdb I've done in the past, I expect stack
usage when DWORD-aligned to increase by ~50% (rather than a theoretical
100%). Stack usage is quite small compared to heap usage however, so you
shouldn't expect to see this reflected in maximum RSS. Overall maximum resident
memory increased by about ~33%.
The number of major pagefaults encountered during a brass boot is roughly equal
to prior.
The elapsed (wall clock) time difference between (2) and (3) is essentially
zero. There is essentially no performance gained by the virtual bit size being a
compile-time constant.
There is a small latency cost in the current DWORD-aligned heap allocation
implementation as compared to a runtime that doesn't require allocations to be
aligned. Compare the elapsed times of (1) -- 2:21.09 or 141.09 s -- and (2) --
2:23.50 or 143.50 s -- result: ~1.7% increased latency. If you look at run (4)
however, which excluded stack alignment changes -- 2:22.55 or 142.55 s --, we
split the difference at ~1.0% increased latency. Note, this is repeatable and
the 1% difference isn't random. Running the same program over again on the same
system exhibits tiny variance.
1) -O3 no pointer compression vere/develop
A run from the HEAD of vere/develop
commit 7c890c3350e3b10e918ea04b92a34dc25af1552d
Command being timed: "./urbit -t -q -F zod -B brass.pill -c zod"
User time (seconds): 1.25
System time (seconds): 0.03
Percent of CPU this job got: 0%
Elapsed (wall clock) time (h:mm:ss or m:ss): 2:21.09
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 148036
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3492
Minor (reclaiming a frame) page faults: 6188
Voluntary context switches: 68
Involuntary context switches: 5
Swaps: 0
File system inputs: 14866
File system outputs: 21544
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0

2) -O3 compiletime determined virtual bit size i/163/pointer-compression
State of pointer compression work prior to migration (where concessions to
runtime determined virtual bit size were made)
commit 4083f1c660c1db682516b57e32780fd59bff7eaf
Command being timed: "./urbit -t -q -F zod -B brass.pill -c zod"
User time (seconds): 1.39
System time (seconds): 0.04
Percent of CPU this job got: 1%
Elapsed (wall clock) time (h:mm:ss or m:ss): 2:23.50
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 197176
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3487
Minor (reclaiming a frame) page faults: 6219
Voluntary context switches: 68
Involuntary context switches: 2
Swaps: 0
File system inputs: 14866
File system outputs: 21544
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0

3) -O3 runtime determined virtual bit size i/163/pointer-compression
Current state of pointer compression work -- after implementation of migration
and runtime determined virtual bit size concession
commit 8dffe067e133ac895a5f8befb67762b58116ae75:
Command being timed: "./urbit -t -q -F zod -B brass.pill -c zod"
User time (seconds): 1.40
System time (seconds): 0.06
Percent of CPU this job got: 1%
Elapsed (wall clock) time (h:mm:ss or m:ss): 2:23.52
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 197200
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3489
Minor (reclaiming a frame) page faults: 7242
Voluntary context switches: 69
Involuntary context switches: 4
Swaps: 0
File system inputs: 14866
File system outputs: 21544
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0

4) -O3 runtime determined virtual bit size WITHOUT stack alignment barter-simsum/pointer-compression-no-align-stack
commit 8b0438ab3bb00cf662c7cef6128f441210728f85
Command being timed: "./urbit -t -q -F zod -B brass.pill -c zod"
User time (seconds): 1.42
System time (seconds): 0.06
Percent of CPU this job got: 1%
Elapsed (wall clock) time (h:mm:ss or m:ss): 2:22.55
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 197204
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3492
Minor (reclaiming a frame) page faults: 6221
Voluntary context switches: 68
Involuntary context switches: 3
Swaps: 0
File system inputs: 14866
File system outputs: 21544
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0

Worst case scenario is we use a directory prefix for include paths, so #include "noun.h" becomes #include "noun/noun.h" and similar, allowing us to have "vere/version.h" and "noun/version.h".
#142 is relevant here. You'd only need to add build --copt='-DC3DBG' to .bazelrc.

Don't merge yet doing a few more tests on live ships.

Ran into some weird behavior on a comet when running the migration. Indicates free list corruption. Can't repro now and unfortunately didn't have a debugger attached. Assuming the free list corruption is a false positive, though don't know what could put the ship into that state and also what between 5 and 6 could magically resolve it.

Create comet with urbit-v1.13

echo edge > testcomet/.bin/pace

prep and next -> version incremented to 1.16. Run on that version

next again and now on version 1.22-f2df391. Run on that version

Run with pointer compression enabled binary

Get the following error repeatedly:
live: loaded: MB/264.437.760
loom: migration running. This may take several minutes to perform.
loom: have version: 1 migrating to version: 2
Assertion '!"loom: corrupt"' failed in pkg/noun/allocate.c:192
Assertion failed: !"loom: corrupt" (pkg/noun/allocate.c: _box_detach: 192)
                                                                          pier: serf unexpectedly shut down

Run pointer compression binary with -L, suddenly the migration works.

Between 5 and 6, I also ran one more time following the free list corruption messages on 1.22-f2df391. Unsure if that could have had any effect and can't repro at all now. Nothing special about this comet. It was freshly booted.

Seeing corruption like that certainly gives me pause.  I feel like it would be worth writing a function that sanity checks the snapshot (free list at minimum, could also traverse the nouns) and keeping it running so that we'll detect more corruption (the worst is when the corruption lasts so long that you write another snapshot before it triggers anything).  If it's fast enough, it should run every time before we write a snapshot, but at the least it will be useful for debugging.

@philipcmonk Sorry should have clarified. This is actually happening in |pack which is called prior to starting the migration. This would be the equivalent of detecting corruption when issuing pack as a subcommand.
Here's the gist of what happened. Only reproed once on a fresh comet. Hasn't since. Unsure of root cause

Briefly ran pier on 1.22-f2df391. Exited.
Ran on binary containing compression/migration code. Pack fails with freelist corruption.
Repeat (2) multiple times. Same result.
Rerun briefly on 1.22-f2df391.
Repeat (2). Works fine this time.

So apparently the corrupted image changed between (2) and (5) -- I suppose with the rerun of (4).

|pack will obliterate all free lists, so I'm not sure how it was noticing free list corruption.  Maybe in the initial "clear some caches" step?  I would want to know more specifically when it encountered corruption and ideally how long it had been there.

Snapshots can be corrupted for a long time without us noticing, which is why a checkpoint-is-sane function would be informative.

I agree adding a loom sanity check prior to writing the snapshot would be useful in tracking down the cause of this, even if it's somewhere else in vere and not in this PR.
And yes, the free list corruption must have been detected as part of the u3m_reclaim call in |pack. The migration has enough logging to tell it definitely occurred in pack though.

@philipcmonk @belisarius222
I found the issue. It was introduced in an unrelated refactor of _box_slot 1c43861d5a9ce6cd8667d10be755c13f5c217bf5. It ultimately led to an OBO for certain siz_ws. The siz_w is repeatedly divided by 2 (because our freelists size by powers of two). We add one though before right shifting so odd siz_ws round up once. Since all boxes on the migrated loom are DWORD multiples (even), it wouldn't matter. But when freeing boxes as part of the pack/migration on the old loom, if we attempt to detach a head box from a freelist and it happens to have a siz_w equal to (2^n)-1 for n=5..u3a_fbox_no-1, we'll get an incorrect box slot which is caught by the last assert in _box_detach.
So not exactly heap corruption. If the assert weren't there, we would have simply had the chance of moving a freelist matching the criteria above one slot lower than it should be -- which is fine because the pack immediately following would have cleared all that freespace anyway.

Added u3a_loom_sane. Currently gets called after the image is loaded, after the migration, and every time u3e_save is called before we write to disk. Don't have a an easy way to profile the bazel-built vere though. Maybe a brass pill boot time would do -- or will that not invoke u3e_save?

Nice!  We basically just want u3a_loom_sane to not add a ton of time to u3e_save, so I'd be inclined to just print out the time before/after u3e_save overall and u3a_loom_sane specifically, and the run that on (-L copies of) some large, infrequently packed ships and see if anything bad happens.  My guess is it takes a lot less time than writing to disk.

Benchmarked a fresh comet. Increased u3e_save latency by about 1%. Can't just run on any old freelist fragmented pier though, because the migration will of course clear all the fragmentation. Going to just use the comet and let it run for a while to try to increase fragmentation.

On a pretty fragmented ship like mine, the freelist traversal increased u3e_save latency by 20%! Maybe doing this is still worth it, but I'm surprised by the latency difference.

What are the absolute numbers for how long it took u3e_save() to run on your fragmented ship?  My guess is the 20% doesn't matter, but if it's starting to get really slow, we should be careful.

@belisarius222
Apologies, was calculating the time diff wrong. It looks like on the fairly fragmented pier of ~barter-simsum, u3a_loom_sane takes only about 60ms. The amount of time that u3e_save takes varies of course by how much data it has to write. If you don't do any allocation following the last snapshot, it's roughly 3 seconds on my x86 linux machine. If you do a bit of allocation, possibly up to 10 seconds.
The longest runtime for u3e_save is going to be following a migration where we have to write the entire filled amount to disc. On a 700MB pier, this took about 30 seconds on my machine. Piers approaching 4G might take multiple minutes.
Anyway, given the average of 60 milliseconds to validate the freelist, I say we keep this in.

rebased _box_slot fix into bcac1d6d2475550d734cc47c2dca900a32b49112 where the regression was originally introduced.
Please read "FINAL BENCHMARK BEFORE MERGE" section in PR description.
This is ready to merge into develop. Whoever makes the merge commit, please keep the default merge commit description which should be prepopulated with the PR description.

Just fixing -Wformat complaint when printing u3a_bits_max


Update GHCJS conditions to also support the GHC JavaScript backend

This MR is to update CPP and cabal file conditions to support the GHC JavaScript backend.
Because the JavaScript backend uses a different FFI syntax than GHCJS, the initialSeedJS function now has two versions of the import string.
The main motivation for this change is the use of this function in ghcjs-base's testsuite.

My opinion is same as in https://github.com/haskellari/splitmix/pull/73
Add a CI job to simple.yml. I'll merge faster if there is a bindist installable with ghcup.
The #73 is not merged, because we apparently need some GHC specifc WASI toolchain, and I'm not gonna bother with something like that. I cannot easily debug if there is a problem, I don't care about accepting the patch (and taking maintenance burden).

This patch doesn't appear to be in head.hackage?


Fix vint warning

Fixed the following warnings presented by vint.

Prefer single quoted strings (see Google VimScript Style Guide (Strings))
Use scriptencoding when multibyte char exists (see :help :scriptencoding)
Make the scope explicit like v:version (or possibly be unexpected builtin?) (see :help local-variable)

Didn't know about vint, sweet!


Add a guide to deploy Semaphore contracts on other networks

Hi!!!.. I am Rocio from PSE Core Program Ecuador group. Can I colaborate with this issue?


Adding multiplication using FFT

Could you add some description like in algorithms from pull requests 23, 24, 25? Description of algorithm (maybe with link to external description) and some in-code comments? Because I can't uderstand this algorithm.

I agree with @arytmetyk, I'm looking through the code and it could use some more back-ground. Class header comments with links are helpful to the reader/user.

@mciancia I have pulled in the FFT code. I have slightly changed the layout of the class and added some header comments. Thanks for the code!


remove of agent does not reset task in queue

woodpecker version: v2.2.2
if the autoscaler just cancled an agent who just managed to mark an task as started ... we will wait without any chance of success.
so i propose on agent removal, (and if agent heartbet do timeout) to "reset" all running tasks in queue, so healthy agents can pick them up again

I still think it should land in server itselve

fixed by https://github.com/woodpecker-ci/woodpecker/pull/3377


Add support for filling subjects with mocks

Codecov Report

Merging #19 (98eb9b4) into gomock-integration (ffa7040) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@                  Coverage Diff                   @@
##           gomock-integration      #19      +/-   ##
======================================================
+ Coverage               98.81%   98.93%   +0.12%
======================================================
  Files                       5        5
  Lines                     253      282      +29
======================================================
+ Hits                      250      279      +29
  Misses                      2        2
  Partials                    1        1

Impacted Files
Coverage Δ

ensurepkg/run_table.go
100.00% <100.00%> (ø)

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 ffa7040...98eb9b4. Read the comment docs.

Codecov Report

Merging #19 (98eb9b4) into gomock-integration (ffa7040) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@                  Coverage Diff                   @@
##           gomock-integration      #19      +/-   ##
======================================================
+ Coverage               98.81%   98.93%   +0.12%
======================================================
  Files                       5        5
  Lines                     253      282      +29
======================================================
+ Hits                      250      279      +29
  Misses                      2        2
  Partials                    1        1

Impacted Files
Coverage Δ

ensurepkg/run_table.go
100.00% <100.00%> (ø)

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 ffa7040...98eb9b4. Read the comment docs.


Postgres  'CURRENT_TIMESTAMP' parsed as a sring.

I have got current_timestamp  as string after insert query. How to handle this.

Could you give me the query you're trying to run please.

@sreeharicubet not sure what are you doing but i kind of think that squel.rstr will solve your problem. It avoids squel to add quotes to the parameter
log(
  squel.update()
  .table('students')
  .set('modified', squel.rstr('NOW()'))
  .toString()
);
/*  UPDATE students SET modified = NOW()  */

Thanks @psypersky , that's exactly what rstr() is for

Thanks @psypersky . This saved me today lol


Migrate Argument Handling for wipac-rest-tools v1.6.0

Currently, we're locked into wipac-rest-tools==1.5.2 because kubernetes==28.1.0 has urllib3 [required: >=1.24.2,<2.0, installed: 1.26.17] and wipac-rest-tools==1.6.0 has urllib3>=2.0.4 (https://github.com/WIPACrepo/rest-tools/pull/137)
This is not pinned by skydriver

as seen in https://github.com/WIPACrepo/SkyDriver/pull/80


chore: automated PR to update ReleaseNotes for 202305.23.0 VHD

This is an automated PR to bump ReleaseNotes for the VHD release with image version 202305.23.0

closing since mariner kata vhd's are fubar


[Question]: Freezing and crashing the program due to getSystemMemoryInMegabytes() error

Hi,
When running the program on some Windows operating systems, we encounter the following error. Currently, this error message occurred on a virtual machine with 8 GB of memory.
Edition	Windows 10 Home
Version	21H2
OS build	19044.1620

Checklist before submitting a question

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I am using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

WindowsException: Error 0x00000000: A operação foi concluída com êxito.
  File "device_info_plus_windows.dart", line 127, in DeviceInfoPlusWindowsPlugin.getSystemMemoryInMegabytes
  File "device_info_plus_windows.dart", line 87, in DeviceInfoPlusWindowsPlugin.getInfo
  File "device_info_plus_windows.dart", line 40, in DeviceInfoPlusWindowsPlugin.deviceInfo
  File "device_info_plus.dart", line 93, in DeviceInfoPlugin.windowsInfo
...
(5 additional frame(s) were not displayed)

I encountered the same problem and it was automatically collected by sentry.


Change request

First of all, I like to state that I highly respect the time and effort which has flown into this integration.
I personally think it is 100%, very good, and I am aware that this request is pretty cheeky, but never the less I think plenty of people will benefit from the following changes, and as I cannot do them myself, I am asking a lot here. :-(
I am not a Python Developer, but I can read and write code...
When I read your code it states that the refresh interval is 15 Minutes, which is 100% correct for "the blank case",
But looking at the Opensky website: https://openskynetwork.github.io/opensky-api/rest.html#api-credit-usage
It states that for requests under 500km radius, they only charge 1 credit (Interval=216 seconds only).
Could we make the scan interval dependant on the radius, or enter the scan interval as a parameter that can be user defined?
Next thing:
If the user has a name and password with opensky, she or he can get 4000 to 8000 credits.
Could we integrate something, so we are able to pass username and password as a parameter and based on that change the scan interval is recalculated, or as stated above add a paramter scan_interval, so that the admin can define the interval in the HA config?
I am not expecting anything here, I am just asking, if you could look into this?

Thanks for the message! I first need to add a config flow, after which I can check if we can (and are allowed to) use dynamic timing (so if someone has a really big radius, it wouldn't update as often as a smaller radius). I am not sure if this fits into the HA architecture. I think it's also a discussion to see if we still allow unauthenticated users to use it, or that we force everyone to use authentication.
But I know for sure, a scan interval set by config (via options or something) is unwanted, so we can't do that

To give an update on this. Next HA release will feature the config flow for OpenSky, so we're a step further!

Hi,
I modified a bit my local version of Opensky integration, to add you upcoming authentication code in init.py with my Opensky's user and password in it and I am able to refresh each 25s, without reaching the limit, which is awesome!

You're welcome :)


json_encode

From /countries/index.php I just receive [{"id":"1","name":"espana"},{"id":"2","name":"francia"}]. What about jsgrid functions? What I am doing wrong? Thanks for your help.

Not sure I understand the issue. Could you describe it in more details?
What jsgrid function? What result do you get, and what do you expect?

I have had problems with sample.js paths as I´m using Fedora, and I just could see the result for clients.php, without jsgrid table formatting.
I have achieved that now. However, I have a doubt, maybe you can solve me. What do I have to do to call two foreign key tables, instead of just one like countries with clients in your example, I need to do the same, something like continents, countries, and clients. Thanks in advance, great job!

See my comment to another issue https://github.com/tabalinas/jsgrid-php/issues/1#issuecomment-143893459


[1.0] Removing Eventbrite support and adding link in readme to new package

As referenced in #213, the Eventbrite support was in need of a new maintainer and support migrated to new package.
Find a maintainer - me!
Link in the README - in this PR
Remove from league/oauth2-client - in this PR

Coverage decreased (-0.01%) to 99.74% when pulling 62a9feaa7fadd62351139152da404b144a479c5e on stevenmaguire:migrate-eventbrite into f2224668d2b644ad1eee14b7428ac98c9f385fe0 on thephpleague:1.0.

Thanks!


Using Query Filter with left join generated by navigation property

Query filter configured for parent entity producing query which selects primary key value even if row was filtered out.
public class BloggingContext : DbContext
{
	public DbSet<Blog> Blogs { get; set; }
	public DbSet<Post> Posts { get; set; }

	protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
//		=> optionsBuilder.UseInMemoryDatabase()
		=> optionsBuilder.UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=LeftJoinQueryFilter;Trusted_Connection=True;")
//			.UseLoggerFactory(Logger.MyLoggerFactory)
			;

	protected override void OnModelCreating(ModelBuilder modelBuilder)
	{
		modelBuilder.Entity<Blog>().HasQueryFilter(p => !p.IsDeleted);
	}
}

public class Blog
{
	public int Id { get; set; }
	public string Title { get; set; }
	public bool IsDeleted { get; set; }

	public ICollection<Post> Posts { get; set; }
}

public class Post
{
	public int Id { get; set; }
	public string Title { get; set; }

	public int? BlogId { get; set; }
	public Blog Blog { get; set; }
}

public class PostDTO
{
	public int Id { get; set; }
	public string Title { get; set; }
	public BlogDTO Blog { get; set; }
}

public class BlogDTO
{
	public int? Id { get; set; }
	public string Title { get; set; }
}

void Main()
{
	using (var context = new BloggingContext())
	{
		context.Database.EnsureDeleted();
		context.Database.EnsureCreated();

		context.Add(new Post
		{
			Title = "Post 1"
		});

		context.AddRange(new[]
		{
			new Blog {
				Title = "Blog 1",
				Posts = new[]
				{
					new Post { Title = "Post 2" },
					new Post { Title = "Post 3" },
				}
			},
			new Blog {
				Title = "Blog 2",
				IsDeleted = true,
				Posts = new[]
				{
					new Post { Title = "Post 4" },
					new Post { Title = "Post 5" }
				}
			}
		});

		context.SaveChanges();
	}

	using (var context = new BloggingContext())
	{
		var list = context.Posts.Select(p => new PostDTO
		{
			Id = p.Id,
			Title = p.Title,
			Blog = new BlogDTO
			{
				Id = p.Blog.Id,
				Title = p.Blog.Title
			}
		})
		.ToList();

		foreach (var post in list)
		{
			Console.WriteLine($"Post.Id: {post.Id}, Post.Title: {post.Title}, Blod.Id: {post.Blog.Id?.ToString() ?? "(null)"}, Blog.Title: {post.Blog.Title ?? "(null)"}");
		}
	}
}

Output:
Post.Id: 1, Post.Title: Post 1, Blod.Id: (null), Blog.Title: (null)
Post.Id: 2, Post.Title: Post 2, Blod.Id: 1, Blog.Title: Blog 1
Post.Id: 3, Post.Title: Post 3, Blod.Id: 1, Blog.Title: Blog 1
Post.Id: 4, Post.Title: Post 4, Blod.Id: 2, Blog.Title: (null)
Post.Id: 5, Post.Title: Post 5, Blod.Id: 2, Blog.Title: (null)

Notice the difference between Post with Id 1 (has no Blog initially) and those with Id 4, 5 (Blog filtered by query filter) - no way to determine if parent entity was filtered out by filter (for example, checking Blog.Id for null).
Generated Sql:
SELECT [p].[Id], [p].[Title], [p].[BlogId] AS [Id0], [t].[Title] AS [Title0]
FROM [Posts] AS [p]
LEFT JOIN (
    SELECT [p0].*
    FROM [Blogs] AS [p0]
    WHERE [p0].[IsDeleted] = 0
) AS [t] ON [p].[BlogId] = [t].[Id]

Generated Sql query result:
Id	Title	Id0	Title0
1	Post 1	NULL	NULL
2	Post 2	1	Blog 1
3	Post 3	1	Blog 1
4	Post 4	2	NULL
5	Post 5	2	NULL

So the problem is query filter applied to subquery before left join, but not as left join condition and value of PK for select is mapped from left side of resulted join, not the right side (which is NULL for filtered rows).
Expected query and result:
SELECT [p].[Id], [p].[Title], [t].[Id] AS [Id0], [t].[Title] AS [Title0]
FROM [Posts] AS [p]
LEFT JOIN (
    SELECT [p0].*
    FROM [Blogs] AS [p0]
) AS [t] ON [p].[BlogId] = [t].[Id] AND [t].[IsDeleted] = 0

Id	Title	Id0	Title0
1	Post 1	NULL	NULL
2	Post 2	1	Blog 1
3	Post 3	1	Blog 1
4	Post 4	NULL	NULL
5	Post 5	NULL	NULL

Further technical details
EF Core version: 2.2.4
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: (e.g. Visual Studio 2017 15.9.12)

Duplicate of #13517


Support cached data clean up for published names

This probably needs the following

Support protocol api that will indicate to caches that publisher explicitly closes the connection
Have such indicate to cleanup names and associated cached data in the relay

From a media perspective, we run into many challenges with IP mobility, where both producer (sender) and subscriber (receiver) are changing networks. Media today handles this via RTP and IP mobility (handled by the client and servers at the app level). IMO, we need something to resume an existing session (subscriber and/or producer) via a different IP/port/etc. flows.  For example, switching from Verizon 5g to WIFI.  Normally this involves auth and a session ID to facilitate transitioning to different IP flows.  A connection level FIN will likely be after the network change (e.g., Verizon 5g --> Wifi).  The client (producer or subscriber) may not be aware of the change till it's already happened.  A graceful FIN may not be seen.  Instead, it'll be a reconnect to resume, if at all. If we don't have a session ID, the reconnect will result in an additional cache and/or conflict with previous flow(s).
I'm leaning towards producer cache expiring purely based on TTL of messages or just FIFO and queue length. The caches can be updated real-time with the active session ID that has been authorized.  A producer on reconnect would of course have to authz before it can send anything, otherwise hello DoS.  Circular buffer queues are great here because it reduces the requirement to have garbage maintenance to purge out old data in cache.
Subscribers are a bit different. Subscriptions could be enhanced to be faster with cached data based on previous session.  For example, subscriber changes network providers. It reconnects and authorizes its flow via the same session id.  That session then inherits all previous subscriptions and resumes where it left off, unless it's greater than subscription max replay messages value (e.g., tail number).  This will directly improve mobility by not requiring re-subscription while also keeping track of session ID cache position.   Again, if the cache position for a subscriber is larger than subscribed tail back value, it would be moved forwarded and messages between disconnect and reconnect will be dropped to that subscriber.  For example, say I'm on Verizon 5g and then lose signal for 5 minutes and reconnect using Comcast.  I can resume my session, but the replay of 5 minutes is too great for some of the cached named flows. The flows that are too great will simply replay up to tail number. Not all names/queues/streams are equal, so some will still be able to resume the past 5 minutes. This is a bit tricky where time-sync between names/flows are not maintained. Many folks are of the opinion that it's too much for the relay to be involved with application time-sync between flows.. Instead leave it to the apps to deal with it and have the relays be super high performing with shallow cache.
Deep cache, or even persistent cache, can be offloaded.

@TimEvens the prototype pretty much manages the cache based on TTL. Group of blocks are removed from the cache some time T after they were received. That time was set to 2 minutes in the previous builds, but we just changed that to 10 seconds, which should improve the memory footprint a bit.
The decision to purge the cache or not is per media source -- a flag set when publishing the media. This is clearly a prototype thing: we want to be able to experiment with a variety of options. In "production", I would expect that to have a different effect:

if a media is "real time", purge media frames based on TTL
if a media is streaming, purge only if the memory is running short. In that case, keep a short cache for serving current connections, but stop advertising that cache as available for new connections. We might consider a second level persistent cache, but for a prototype that's complicated.

The cache purge is per-GOB. That may mean keeping several seconds of video, which requires memory. We do that because if we restart video from arbitrary points, users will likely see a mosaic of squares until the next GOB. We may want to purge all frames based on a shorter TTL, but if we want to avoid the mosaics of squares that requires changing the logic so that new client can only start at the next GOB, which may mean waiting a couple seconds. Or maybe we introduce an end-to-end signal to ask for "please rev a new GOB asap".
On the reconnect issue, we need to develop scenarios and test them. We have a subscribe intent option to "reconnect at GOB X, Object Y", which would do pretty much what you describe. But until we have tested it, we won't know whether it works as expected.

PR #112 set the cache clean up timer to 10 seconds. This appear to have fixed the original issue.


#525: 30 min booking restriction and #532 default review page for approvers

Added a 30 minute minimun requirement to each booking to ensure that a room isn't booked for less than 30 min. Also, added that approvers now have a their default booking page to be the review booking page.
Test plan (required)
30 min restriction :

Closing issues

closes #525
closes #532

Pre-Merge checklist
Complete these items before requesting reviews

[X] Static Analysis Rules Validated
[X] All commits follow naming conventions

Sub-tasks Checklist

[ ] UI Implementation
[ ] UI Test
[X] Backend Implementation
[X] Backend Tests
[ ] Integration Tests
[ ] System Tests
[ ] Documentation

Converted to draft pending resolution of the merge conflicts @joeyabou

Do the tests still pass after the feature of bookings being in increments of 30 minutes was added?
The tests are making bookings with non-standard increments, but we might not be verifying the booking time specifically.

it did not I changed it for the test to work

PR Has merge conflicts and is marked as draft until they have been resolvled by @joeyabou (in progress)

Superseded by #638


[DateRangePicker] Static mode to choose which date is selected first

Hello. Maybe somebody know, is it possible for a static mode to choose which date is selected first "Check-in"(start) or "Check-out"(end)?
https://next--material-ui.netlify.app/ru/components/date-range-picker/#static-mode
Thank for  answer. sorry for issue

Sorry, my english is not good. I can try again.
I'm sure @dmtrKovalenko understand what I mean.
SO. We have a basic component view
https://next--material-ui.netlify.app/ru/components/date-range-picker/#basic-usage

If you try to click on "Check-in" field and select some date (for example December 16) then focus will move to "Check-out" field
and we can select the end of range.
Otherwise, if you first click on the "Check-out" field and also select December 16, then focus will move to "Check-in" field and we can select start of date range.
But in static mode
https://next--material-ui.netlify.app/ru/components/date-range-picker/#static-mode

Clicking first on the same December 16, then we can choose the second date - the end of range.
And the sense of the question - is it possible for a static mode to indicate which date is selected first "Check-in"(start) or "Check-out"(end)

@Krasnopir Thanks for the extra details, it's easier to grasp now. This state is hosted under "currentlySelectingRangeEnd". We don't provide a way or at least an easy way to control this state. I guess we could.

thank a lot


[Feature Request] File nesting for filename patterns

In some languages, for example in go identifying a test or other related file might use a different filename pattern e.g. a go file ends with file.go and its test will end with file_test.go I believe this is also a pattern used in several other languages e.g. _spec.blah etc. I see from the original issue/PR that the decision was to go with the simplest solution, however I think there are a bunch of use cases in other languages that would be served by allowing nesting based on filename patterns.
Any thoughts on having file nesting work for these use cases as well?

I've got an another face to this issue, I couldn't nest the file pattern below as
js = { 'js.map', 'd.ts' }

I just want to add another example:
["package.json"] = { "package-lock.json", "yarn.lock" }

which would nest package-lock.json and yarn.lock below/inside a package.json ;-)


Update readme.

I like it, lgtm, thought about specifying default values but that's already in the action.yml so i don't think it's needed


Fix problems when user changes parameter(s)

Currently if the user changes a parameter (eg cell size), the data is reloaded and table is recalculated. Change this to:

[x] not reload data
[ ] not recalculate table

Change that behavior so that when the user changes sig2obs, t max, cell size and/or buffer parameters, the rasters are re-calculated by calling calculateRaster2D() and then replot the new rasters by calling plotMKDE().  Iif the user changes only the probabilities, rasters don't need to be recalculated, just replot by calling plotMKDE()
Calls that are impacted by the user parameters:
calculateRaster2D (data, id, input$sig2obs, input$tmax, input$cellsize, xmin, xmax, ymin, ymax)

plotMKDE (raster, probs = probs, asp = rasters[[1]]$ny/rasters[[1]]$nx, xlab='', ylab='')

animalAttributes(data, input$cellsize)

For the All and Summary tables:

table_all data comes from gps$original which comes from preprocessDataframe() which comes from loadDataframeFrom*()
table_summary data comes from gps$summary which comes from animalAttributes(...,input$cellsize) which comes from preprocessDataframe() which comes from loadDataframeFrom*()

Order of processing:

loadDataframeFrom*()
preprocessDataframe() -> gps$data, gps$original
animalAttributes(..., input$cellsize) -> gps$summary


Volume fade in / fade out

There is no volume fade in / out when press play/pause on the track.
It would be great to see this options in raspotify.

Any ideas about this feature?


Generated rust bindings fail to compile with missing rinf::SharedCell

Report
cargo b -p hub

--> native/hub/src/messages/brongnal.rs:7:5
use rinf::SharedCell;
  |     ^^^^^^^^^^^^^^^^ no `SharedCell` in the root

Steps to Reproduce
No idea
System Information
rustc --version
flutter doctor

flutter doctor
rustc 1.82.0-nightly (2c93fabd9 2024-08-15)
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel , 3.22.3, on Arch Linux 6.10.3-zen1-1-zen, locale en_US.UTF-8)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ✗ Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] Connected device (2 available)
[✓] Network resources

! Doctor found issues in 2 categories

I believe I fixed this with:
cargo update
cargo install rinf
flutter pub upgrade
rinf message

Is it documented anywhere that the rinf cli must be kept up to date with the rust library?

Hi, Brongan :)
This isn’t documented yet. As you mentioned, the Rinf version in pubspec.yaml and Cargo.toml should be the same. I agree it would be helpful to add this information to the documentation. Thanks for pointing out the issue!


Bitfields don't always respect default values

I just realized that default values for bitfields don't always make sense if adding a new bitfield to the packet doesn't increase the size. Example:
<Packet name="test" ID="0">
    <Data name="Field0" inMemoryType="bitfield1" />
    <Data name="Field1" inMemoryType="bitfield1" default="1" />
</Packet>

In this case, if an older version of the protocol that only knows about Field0 sends a packet with Field0 = 1, the packet data will consist of one byte, 0x80. The problem is that the newer protocol version will infer from the one-byte size that it has a valid Field1 value and read it out as zero, overwriting the default of 1.
My suggestion would be to throw a warning for any bitfields with default values. One could argue that the default could be forced to zero, but I think there may be valid usecases for non-zero defaults.
In addition if you have multiple default bitfields in the same byte the size check is unnecessarily repeated.

Fixed in 2.9.a


Update python/curl_json dependencies and explicitly enable plugins.

While using this cookbook, I noticed that the curl_json and python plugins did not work "out of the box." I used the collectd source to diagnose the problem and figure out the fix.
It appears to me that many of the plugins for collectd don't come via default installation. I have not investigated more than curl_json or python, but I they are some examples of plugins that are not included with the base installation, i.e. configure && make all install.
Essentially, this pull request takes the keys from the plugins hash and explicitly enable plugins in the configuration stage. I had to add curl_json and python dependencies to enable these plugins.
I'm willing to investigate the other plugins that are not being included by default and if they need dependencies resolved, but I wanted to get the ball rolling on this issue.
Feedback welcome!

Looks good to me.


Not able to register /install new driver and app in dev mode.

No error on CM logs. After uploading manifest, UI shows the new driver  but shows disabled " install" button.

@pooyadav can you provide the manifest so we can reproduce the error.


can i play the audio of my phone on my computer ?

and i hope to improve the sharpness of the video so that the letter are more able to read

And it will be better if could set the windows on the toppest

Forward audio please refer #14 .
And there is an option called --always-on-top so that scrcpy can always be above others.

Forward audio please refer #14 .
And there is an option called --always-on-top so that scrcpy can always be above others.

sorry i don't know whats wrong,the shortcut works but command didn't

https://github.com/Genymobile/scrcpy/issues/385#issuecomment-451895997

#385 (comment)

thank you so much,now i got it.


Thorntail

Moved to Thorntail to fix Issue #5.
Work around for Thorntail/WF Swarm bug https://issues.jboss.org/browse/THORN-2015

very cool, @sjwoodman  - let's do that for the other swarm things too!
:tada:


inputButtonConfig was removed, but not update in docs

Hi, I use latest version of your package(7.0.4), in this version, there is no inputButtonConfig property and InputButtonConfig class, but you don't include this in your documents, there is no migration guide for this, and you use this property in the last example in you docs, please update your docs

sorry about that!
7.0.1 was actually a breaking change and I replaced InputButtonConfig with KeyPadConfig.
I have added this to the migration guide in the readme.
#89 should fix the docs accordingly!


Custom styles not applied to Numbered List

Describe the bug
I tried to add custom styles to Numbered list, but its not been added.
To Reproduce
Steps to reproduce the behavior:
  NumberedList.extend({     options: {       HTMLAttributes: {         spellCheck: false,         className: 'numberedStyle',       },     },   }),
and style
 .numberedStyle {   color: slateblue; }
Expected behavior
Should apple the styles
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS:  Windows 11 22621.1702
Browser: Chrome 113.0.5672.93
Version :     "@stripe/react-stripe-js": "^2.1.0",
"@stripe/stripe-js": "^1.52.1",
"@yoopta/action-menu-list": "^1.9.3-rc",
"@yoopta/blockquote": "^1.9.4-rc",
"@yoopta/callout": "^1.9.3-rc",
"@yoopta/code": "^1.9.3-rc",
"@yoopta/editor": "1.9.5-rc",
"@yoopta/embed": "^1.9.3-rc",
"@yoopta/headings": "^1.9.3-rc",
"@yoopta/image": "^1.9.3-rc",
"@yoopta/link": "^1.9.3-rc",
"@yoopta/lists": "^1.9.3-rc",
"@yoopta/marks": "^1.9.3-rc",
"@yoopta/paragraph": "^1.9.5-rc",
"@yoopta/renderer": "^1.9.3-rc",
"@yoopta/toolbar": "^1.9.3-rc",
"@yoopta/video": "^1.9.3-rc",

This is partially fixed in the latest version, the styles are initially applied, but when we create new numbered list or bulleted list, or while clicking the pre rendered list from the initial state, it goes back to default font.

Fixed in latest version


fix: prevent generation of backup poms

Based on the discussion here, it seems that workflow is not allowed to push to a branch with protection rules. We require test check before a commit can be pushed to master.
Hence, I am disabling it to see if I can release it.


functionapp: Remove support to create PowerShell 6.2 function apps

Description
Remove support to create PowerShell 6.2 function apps
cc: @gzuber @eamonoreilly @anirudhgarg @anthonychu @stefanushinardi

functionapp

@gzuber - any update on this?

Closing as this is no longer relevant since we rely on the stacks API to determine if a runtime is still supported and do not allow customers to create the function app if that is not the case.


Upload not working on 0KB files

Hi,
Why when I try to upload empty file the upload not working?
Thanks.

+1


Picking up from "Electrum" to "Electron Cash" BitcoinCash will not work

Hello,
I just wanted to pick up my BitcoinCash, created by the hard fork, via the Wallet Electron Cash.
Now I have the extent that I entered the private key during installation and it works so far.
But I do not get the BitcoinCash !? I synced already but nothing comes.
Can you help me please!??
best regards
Freini

Did you have bitcoin in that wallet before the fork (before block 478558)?

make sure its not a 2fa wallet and that the same addresses are created.  check the block explorer.

hi there, - i am attempting to claim bitcoin cash using electron cash wallet- i tried to enter the 12 word seed from my electrum bitcoin (BTC) wallet but the next button did not activate- is there a reason for this? am i doing something wrong? any help would be appreciated- thanks

@gravityguide typo or extra whitespace

yeah- i have done this - (re: a space inbetween each word- and double checked for typos) the 'next' button only seems to activate roughly half way through typing the 12 word seed (on the 39th character- including spaces), when i finish entering the 12 word seed - the next button does not activate- which is weird...

means one of the words is wrong then.

Or it could be a BIP39 key, are you sure it's an electrum key?

yeah -my electrum seed from the electrum BTC wallet is a 12 word seed (total 76 characters)- this is the seed i had my BTC before the fork in august 2017-  this is the seed i am attempting to input into the electron- cash  (BCC) wallet to claim my bitcoin cash

Was it generated by electrum? You're 100% positive it isn't a BIP39 seed :stuck_out_tongue:?
If it is an electrum key, jonald is right. Typos/bad spacing is likely the issue. Have you tried importing the wallet file directly (obviously make a backup)

yeah- dont think it is a BIP39 seed- how do i import the wallet file directly- i have the .csv file and json files backed up already- but cant see an option to do this when opening the electron cash wallet- thanks

double check if all the words on are on the seed list.

Get the seed words directly from the dialog box in Electrum :  Wallet | Seed menu

ok - so update:)
managed to download electron cash - an earlier version  2.9.2
i inputted the electrum (btc) seed ok and it accepted it:) and the (bcc) balance is displayed to claim
however now i cant connect to a server and server not syncing to network
any ideas how i resolve this? thanks

open the wallet file in 3.2

ok- i downloaded electron cash 3.2
and opened it using the wallet file from (/.electron-cash), however the wallet is still showing 2.9.2 version, but the light in the right corner is showing green and i am now automatically connected to the network (ELECASH.BCC.NUMMI.IT)
so i then attempted to send a transaction to my trezor (BCH) wallet
and got the following error
"error: the transaction was rejected by network rules.
16: mandatory-script-verify-flag-failed(signature must use SIGHASH_FORKID)
still not able to send anything out of my electron cash wallet

What do you mean the wallet is showing 2.9.2 version?

@gravityguide, unless you want more help, I am going to close this issue as resolved.  Please respond if you are not sorted out yet.

still need to look into this further- but thanks for getting back to me...

The 2.9.2 version and FORKID error indicates that something is really broken on your end, beyond anything possible from a properly installed Electron Cash.  As such, I am going to close this.
Feel free to reopen it when you've investigated, if you think the problem lies with Electron Cash, but given the facts on hand this is very unlikely.


Export isBeforeDay/isAfterDay

Both isBeforeDay and isAfterDay are quite useful utlities but are not included in index.js exports. Is there a reason behind this? If not, would you accept a PR to export those?

They're already exposed - react-dates/lib/utils/isBeforeDay, etc. There's no real need imo to add to the already too-massive manifest export in the "main".
Everything reachable is part of the public API.

import isBeforeDay from "react-dates/lib/utils/isBeforeDay";
import isAfterDay from "react-dates/lib/utils/isAfterDay";


How to writing warning or error to console in OnImport

We are developing an Powershell module. We want to present some warning messages to users in IModuleAssemblyInitializer::OnImport method. However, in this stage, both commandRuntime and host are not available. And so how to present message to console in OnImport? And what is the best way to do that?

@stoneiii  In general it's best to avoid writing messages on import as a module import doesn't necessarily indicate a cmdlet is being invoked.  For instance, it's possible for the module to imported during tab completion, even if the subject command is completely unrelated.
Instead, messages should be queued until the first command is invoked and displayed then.  For cmdlets, this is pretty easy to set up with a common base cmdlet class that implements BeginProcessing.
If you absolutely need to write a message for some reason, you would need to use the PowerShell class to invoke the corresponding Write-* cmdlet.

@stoneiii In general it's best to avoid writing messages on import as a module import doesn't necessarily indicate a cmdlet is being invoked. For instance, it's possible for the module to imported during tab completion, even if the subject command is completely unrelated.
Instead, messages should be queued until the first command is invoked and displayed then. For cmdlets, this is pretty easy to set up with a common base cmdlet class that implements BeginProcessing.
If you absolutely need to write a message for some reason, you would need to use the PowerShell class to invoke the corresponding Write-* cmdlet.

Thanks for your answer!
And would you please tell me which queue I shall use for caching my message?

There's nothing really built in since it isn't a particularly common thing to need. I would do something like this:
using System;
using System.Collections.Generic;
using System.Management.Automation;
using System.Management.Automation.Runspaces;
using System.Runtime.CompilerServices;

namespace MessageQueueExample
{
    public static class InitializationMessageQueue
    {
        private static readonly ConditionalWeakTable<Runspace, List<object>>.CreateValueCallback s_creator
            = _ => new List<object>();

        private static readonly ConditionalWeakTable<Runspace, List<object>> s_storage
            = new ConditionalWeakTable<Runspace, List<object>>();

        public static List<object> GetQueueFromTLS()
        {
            Runspace runspace = Runspace.DefaultRunspace;
            if (runspace == null)
            {
                throw new PSInvalidOperationException(
                    "There is no Runspace available to run scripts in this thread. You can "
                    + "provide one in the DefaultRunspace property of the System.Management"
                    + ".Automation.Runspaces.Runspace type.");
            }

            return s_storage.GetValue(runspace, s_creator);
        }

        public static void DisplayPendingMessages(PSCmdlet context)
        {
            List<object> messages = GetQueueFromTLS();
            if (messages.Count == 0)
            {
                return;
            }

            object[] messagesCopy = messages.ToArray();
            messages.Clear();
            foreach (object message in messagesCopy)
            {
                switch (message)
                {
                    case ErrorRecord error: context.WriteError(error); break;
                    case WarningRecord warning: context.WriteWarning(warning.Message); break;
                    case VerboseRecord verbose: context.WriteVerbose(verbose.Message); break;
                    case DebugRecord debug: context.WriteDebug(debug.Message); break;
                    case InformationRecord info: context.WriteInformation(info); break;
                    default: context.WriteInformation(message, Array.Empty<string>()); break;
                }
            }
        }
    }

    public class ModuleInit : IModuleAssemblyInitializer
    {
        public void OnImport()
        {
            try
            {
                // do a thing
            }
            catch (Exception e)
            {
                InitializationMessageQueue.GetQueueFromTLS().Add(
                    new ErrorRecord(
                        e,
                        "my error",
                        ErrorCategory.NotSpecified,
                        targetObject: null));
            }
        }
    }

    public abstract class MyModuleBaseCommand : PSCmdlet
    {
        protected sealed override void BeginProcessing()
        {
            InitializationMessageQueue.DisplayPendingMessages(this);
            BeginProcessingInternal();
        }

        protected virtual void BeginProcessingInternal()
        {
        }
    }

    [Cmdlet(VerbsDiagnostic.Test, "MessageQueueThing")]
    public class TestMessageQueueThingCommand : MyModuleBaseCommand
    {
        protected override void BeginProcessingInternal()
        {
            // Override this instead of BeginProcessing. Everything else would be
            // the same. You could also remove sealed from BeginProcessing and just
            // ensure that you always call base.BeginProcessing when overriding it.
        }
    }
}

@SeeminglyScience Really helpful! Thank you very much!


[Insight] Commented code should not be committed - in zzcleanurls.php, line 22

in zzcleanurls.php, line 22

Commented out code reduces readability and lowers the code confidence for other developers. If it's common usage for debug, it should not be committed. Using a version control system, such code can be safely removed.

if (!defined('_PS_VERSION_')) {
    return;
}

// Uncomment to enable debugging
// define('ZZ_DEBUG', true);

if (defined('ZZ_DEBUG') && ZZ_DEBUG && is_readable(__DIR__.'/vendor/autoload.php')) {
    require __DIR__.'/vendor/autoload.php';
    Symfony\Component\Debug\Debug::enable();
}

Posted from SensioLabsInsight

already fixed in dev


.csproj Assets not copied to output in dev builds

When doing full desktop builds, items listed in the .csproj as <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> are copied into the built app's folder hierarchy but when doing dev builds the developer needs to manually copy the files into the destination directory.
For example, if you've included files from the Assets folder in your .csproj, those files need to be copied into obj/Host/node_modules/electron/dist/resources/app/bin/Assets (on a PC) or obj/Host/node_modules/electron/dist/Electron.app/Contents/Resources/app/bin/Assets (on a Mac). I suspect the same issue is present on Linux machines and I'm guessing the destination path matches the PC path but I've not been able to confirm for Linux.

you could setup webpack to copy the file for you.

Unfortunately webpack can't see inside the .csproj file so it can't easily understand or correctly predict what assets need to be copied, making it viable as a hard-coded temporary workaround but definitely not a real solution (I've got a similar manual work-around I'm doing at the moment).

but you can easily tell webpack to copy all files in Asset to the wwwroot folder and that will get published

@yoDon Do you mean the "electronize start" command creates a different folder on other platforms?!
And the assets folder is not in the correct path?

@GregorBiswanger This is a dev vs. production build issue not an OS platform issue. Dev builds and production builds act differently with respect to assets listed in the .csproj. Production builds copy assets listed in .csproj to the expected output folder. Dev builds don't work because the dev server expects to find the assets under obj/Host/..... as described in the initial bug report here and the dev build process doesn't copy them there.


Poor use of Issue Tracker: This.

A beautiful mod @theoriginalbit !!
Excitedly adds to own server

Most people report issues either directly to me, or via the forums. Though I have started using this more.


modules: interface: return None if speed not defined

On Linux, some interfaces don't have a speed attribute, such as lo for
instance. In that case, cat /sys/class/net/lo/speed returns:
cat: /sys/class/net/lo/speed: Invalid argument
which causes Interface.speed to throw an exception.
This commit makes Interface.speed return None in those cases, instead of
throwing an AssertionError.

Hi, thanks for contributing !
If the interface name does not exists it will return None as well and I think it's better to raise an error in this case.
% cat /sys/class/net/doesnotexist/speed
cat: /sys/class/net/doesnotexist/speed: No such file or directory
% echo $?
1

Maybe we should keep the current behavior and assume we can't test speed of such interfaces.

You're right, I didn't think about that. It still seems counter-intuitive to me to throw an assertion error when the speed is undefined though.
How about checking whether the interface exists or not during __init__(), since the interface properties (speed, address) don't make sense if it doesn't; the exception could be thrown there.
Otherwise, I would do assert self.exists at the beginning of speed, and then use the same logic as proposed in this PR; but it seems like we'd end up having that assertion on every single property, so having it in __init__() would be more straightforward.
Let me know what you think.

It seems to me that an except in __init__() if the interface does not exist breaks workflows that want to assert that an interface does not exist, i.e. assert not interface.exists(). Also one might use the same interface object to assert that an interface does not exist, create it externally and then assert that does exists now or the other way around.


basic fix command

Fixes #74,

There's also this issue where ruff returns a non-zero exit code upon auto-fixing the lint errors, which throws an error in our case(after fixing lints), Any idea how to deal with this, should we modify our error message?
No pyproject.toml found.
Falling back to default configuration...
Found 0 error(s) (65 fixed).
hauk exited with code ExitCode(unix_exit_status(1)): An unknown error occurred: . Please file a bug report at https://github.com/cnpryer/huak/issues/new?assignees=&labels=bug&template=BUG_REPORT.md&title=

Hey so I'm checking this out now, but I'm trying to give it a spin and realized that instead of doing that we could probably just add a test for this. Would you be able to add that to the PR?

yeah sure, will do that.

Blocker: https://github.com/charliermarsh/ruff/issues/341
also tagging #286

I'll just merge as is and add. Thanks for the PR!


Review Kanban Board

Review of kanban board - Final Capstone
Back-end
Front-end
We are a team of 5 members:

@fibini
@franclobo
@Gopxfs
@Draxeytina
@waqaskanju

Kanban board screenshot:

Hi Team,
Great work so far👏
However, there are some issues preventing me from giving the 👍

I am not seeing the link to the kanban board, I do see issues that are great, but I do not see a project board in either of the repos linked. (One board is fine)

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Please, do not open a new Issue for re-reviews. You should use the same Issue submitted for the first review, either valid or invalid unless it is requested otherwise.

done.

Sorry, don't know how I missed that, apologies - This is what I see:

Have not submitted review yet, but that's what I see

Sorry, don't know how I missed that, apologies - This is what I see:
Have not submitted review yet, but that's what I see

Hello @mcrd25 , can you check it again? We made it private, sorry for the inconvenient 😅

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.

Thanks for your patience!