AutoEquatable generates definitions for Sourcery classes

When using Sourcery 0.5.5 with the following input:
https://gist.github.com/mindz-eye/a0160791349760b1245a4419c4aa6cc9
I get the following result:
https://gist.github.com/mindz-eye/04850b90572b45a95b34248dd8625021
Obviously, it generates definitions for some Sourcery runtime classes.
Not sure what version introduced this behavior, but in 0.4.9 it definitely worked correctly.
Sourcery is installed via CocoaPods

How does your build script look like?
Can you remove the cache folder from ~/Library/Caches/Sourcery

echo "Generating code from Sourcery templates..."
sourcery_path=${PROJECT_DIR}/${PROJECT}/Sourcery
templates_path=${PROJECT_DIR}/${PROJECT}/Templates
output_path=${PROJECT_DIR}/${PROJECT}/Gen
${sourcery_path}/bin/sourcery ${PROJECT_DIR} ${templates_path} ${output_path} --verbose

I switched from using CocoaPods to manually downloaded binary.
Deleting ~/Library/Caches/Sourcery doesn't help.

Your copy of Sourcery is inside PROJECT_DIR, which you ask it to scan, so it's scans it's own sources. So you either need to remove Sourcery sources (you only need binary any way), or you need to put it somewhere else, or pass it a directory which only contains your own project files.

Oh, my fault. Thanks a lot!


About Image Demosaicking

hi, In the source code, DMNet is used to convert input like 1144 RGGB to 1344 RGB, but when I test, it seem not like this, the output is still 1* 1* 4*4，is there something wrong with my understanding

Sorry for the inconvenience, the current code is not ready for other tasks. To construct a demosaicing network, the out_c parameter should be multiplied in the configuration out_channel of the laster conv layer before pixelshuffle (this line in MuLUTUnit).


Update setup.py

Updated for geoocation lookup

@lukedoyle7  - will this break anything? If not, can you please merge.


eas build -p ios  | Fastlane build failed with unknown error

Build/Submit details page URL
No response
Summary
I was able to properly create .ipa until last week, but now I get this error in FastLane during linking:
❌  ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.3_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

I tried to compile it with image="latest" with no luck.
Android build is working properly.
I also tried to archive the project locally with XCode13.3 after "expo prebuild --clean -p ios" and it worked.
Managed or bare?
Managed
Environment
expo-env-info 1.0.2 environment info:
System:
OS: macOS 12.2.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3/13E113 - /usr/bin/xcodebuild
npmPackages:
babel-preset-expo: 9.0.2 => 9.0.2
expo: ^44.0.6 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
eas-cli: 0.51.0
expo-cli: 5.3.2
Expo Workflow: bare
Error output
No response
Reproducible demo or steps to reproduce from a blank project
This is my eas.json:
{
  "cli": {
    "version": ">= 0.47.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal"
    },
    "production-ios": {
      "ios": {
        "image": "latest"
      },
      "distribution": "store",
      "releaseChannel": "production.ios-1.7.1"
    }
  },
  "submit": {
    "production": {}
  }
}

I queued the build with:
eas build -p ios --profile production-ios

Same issue here with same troubleshooting. It was working not long ago for me too. I assume it's Expo's build servers then?

You are depending on some third-party library that provides prebuild binaries build on a newer version xcode than expo servers have. The only option is to downgrade those libraries.
closing issue for now
it should not happen, but if the issue is caused by an expo package please reopen this issue

It looks like we will need new code for next SDK, so we will probably update latest image next week

Thanks!
Does anyone know how to easy detect the third-party lib compiled with the newest XCode?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Wojciech Kozyra @.>
Sent: Friday, April 22, 2022 1:37:48 PM
To: expo/eas-cli @.>
Cc: Luca Agostini @.>; Author @.>
Subject: Re: [expo/eas-cli] eas build -p ios | Fastlane build failed with unknown error (Issue #1079)
It looks like we will need new code for next SDK, so we will probably update latest image next week
—
Reply to this email directly, view it on GitHubhttps://github.com/expo/eas-cli/issues/1079#issuecomment-1106428406, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXEMV5IXN77AGVMQSTOHOYTVGKFQZANCNFSM5T7VESWQ.
You are receiving this because you authored the thread.Message ID: @.***>

For anyone to not to go trouble going through all third-party library, I raised the  macos image on azure pipeline to macos-12 and it was solved.

the latest image is now using xcode13.3

I'm a beginner and tried to compile the HelloWorld demo sample but no success to publish to apple store.
Expo says :
🍎 iOS build failed:
Fastlane build failed with unknown error. Please refer to the "Run fastlane" and "Xcode Logs" phases.
Fastlane errors in most cases are not printed at the end of the output, so you may not find any useful information in the last lines of output when looking for an error message.
And the ios Xcode log (lasts lines because its 10k lines !! Not succees to find which library was in cause) :
Ld /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/InstallationBuildProductsLocation/Applications/allomonde.app/allomonde normal (in target 'allomonde' from project 'allomonde')
    cd /Users/expo/workingdir/build/ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -target arm64-apple-ios12.0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/DoubleConversion -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/EXApplication -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/EXConstants -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/EXErrorRecovery -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/EXFont -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/Expo -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/ExpoKeepAwake -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/ExpoModulesCore -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/RCT-Folly -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/RCTTypeSafety -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-Codegen -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-Core -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-CoreModules -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTAnimation -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTBlob -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTImage -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTLinking -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTNetwork -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTSettings -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTText -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-RCTVibration -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-cxxreact -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-jsi -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-jsiexecutor -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-jsinspector -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-logger -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/React-perflogger -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/ReactCommon -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/Yoga -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/fmt -L/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/glog -F/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos -F/Users/expo/workingdir/build/ios/Pods/../../node_modules/expo-file-system/ios -F/Users/expo/workingdir/build/ios/Pods/../../node_modules/expo-splash-screen/ios -F/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/XCFrameworkIntermediates/EXFileSystem -F/Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos/XCFrameworkIntermediates/EXSplashScreen -filelist /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/IntermediateBuildFilesPath/allomonde.build/Release-iphoneos/allomonde.build/Objects-normal/arm64/allomonde.LinkFileList -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker @executable_path/Frameworks -dead_strip -Xlinker -object_path_lto -Xlinker /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/IntermediateBuildFilesPath/allomonde.build/Release-iphoneos/allomonde.build/Objects-normal/arm64/allomonde_lto.o -fembed-bitcode -Xlinker -bitcode_verify -Xlinker -bitcode_hide_symbols -Xlinker -bitcode_symbol_map -Xlinker /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/BuildProductsPath/Release-iphoneos -Xlinker -final_output -Xlinker /Applications/allomonde.app/allomonde -stdlib\=libc++ -fobjc-arc -fobjc-link-runtime -L/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/IntermediateBuildFilesPath/allomonde.build/Release-iphoneos/allomonde.build/Objects-normal/arm64/allomonde.swiftmodule -ObjC -lDoubleConversion -lEXApplication -lEXConstants -lEXErrorRecovery -lEXFont -lExpo -lExpoKeepAwake -lExpoModulesCore -lRCT-Folly -lRCTTypeSafety -lReact-Codegen -lReact-Core -lReact-CoreModules -lReact-RCTAnimation -lReact-RCTBlob -lReact-RCTImage -lReact-RCTLinking -lReact-RCTNetwork -lReact-RCTSettings -lReact-RCTText -lReact-RCTVibration -lReact-cxxreact -lReact-jsi -lReact-jsiexecutor -lReact-jsinspector -lReact-logger -lReact-perflogger -lReactCommon -lYoga -lc++ -lc++abi -lfmt -lglog -framework AudioToolbox -framework EXFileSystem -framework EXSplashScreen -framework JavaScriptCore -framework MobileCoreServices -ObjC -lc++ -lPods-allomonde -Xlinker -no_adhoc_codesign -Xlinker -dependency_info -Xlinker /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/IntermediateBuildFilesPath/allomonde.build/Release-iphoneos/allomonde.build/Objects-normal/arm64/allomonde_dependency_info.dat -o /Users/expo/Library/Developer/Xcode/DerivedData/allomonde-cxhqiciqscpymuclrzeeapjqoodr/Build/Intermediates.noindex/ArchiveIntermediates/allomonde/InstallationBuildProductsLocation/Applications/allomonde.app/allomonde
ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.3_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

and package.json :
{
  "name": "allo-monde",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web"
  },
  "dependencies": {
    "expo": "~45.0.0",
    "expo-splash-screen": "~0.15.1",
    "expo-status-bar": "~1.3.0",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-native": "0.68.1",
    "react-native-web": "0.17.7",
    "webpack-dev-server": "~3.11.0",
    "@expo/webpack-config": "~0.16.2"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9"
  },
  "private": true,
  "start": "react-scripts --openssl-legacy-provider start"
}

and eas.json :
{
  "cli": {
    "version": ">= 0.52.0"
  },
  "build": {
    "development": {
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {}
  },
  "submit": {
    "production": {}
  }
}

No, not locally, I don't have a mac and this is why I tried this ReactNative/Expo/Eas thing.
I run :
npm install -g eas-cli
eas login
eas build:configure

I waited and after minutes the console said:
🍎 iOS build - status: waiting to enter the queue (concurrency limit reached)
Glad to know there is a local way to compile if I buy a mac.
Thank for you supoport !

Answered myself, with a little help from this thread  somehow related.
So you just have to add "image": "latest" to the "ios" element in eas.json in  the right profile.
ex. :
{
  "cli": {
    "version": ">= 0.52.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug",
		"image": "latest"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {}
  },
  "submit": {
    "production": {}
  }
}

And build with :
eas build --platform ios --profile development
(just to do the same with "production" profile (probably))
And the reason is here Latest = 13.3 default = 13.0 !!!

How to fix it on BigSur 11.6.7 + Xcode Version 13.2.1 (13C100) ?

I'm getting this error as well on Expo's build servers
❌  ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.3_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64
I copied the eas.json above
{
  "cli": {
    "version": ">= 0.53.1",
    "requireCommit": true
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug",
        "image": "latest"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {}
  },
  "submit": {
    "production": {}
  }
}

and my package.json is
  "dependencies": {
    "app": "*",
    "expo": "^44.0.0",
    "expo-dev-client": "~0.8.6",
    "expo-linear-gradient": "~11.0.3",
    "expo-splash-screen": "~0.14.1",
    "expo-status-bar": "~1.2.0",
    "react": "17.0.1",
    "react-dom": "17.0.1",
    "react-native": "0.64.3",
    "react-native-gesture-handler": "~2.1.0",
    "react-native-reanimated": "~2.3.1",
    "react-native-safe-area-context": "3.3.2",
    "react-native-screens": "~3.10.1",
    "react-native-web": "0.17.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@types/react": "~17.0.21",
    "@types/react-native": "~0.64.12",
    "typescript": "~4.3.5"
  },
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web"
  },

I'm using Expo Bared Project, facing the same issue
ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.3_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@xubmuajkub me, too.
Using Expo 46, bare project, MacBook M1, Xcode

Same issue here. Using expo sdk 46 and running eas build with --local flag on Azure pipeline using 'macos-latest' image.
could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.5_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64
+-------------+--------------------------------+
|              Build environment               |
+-------------+--------------------------------+
| xcode_path  | /Applications/Xcode_13.2.1.app |
| gym_version | 2.209.1                        |
| sdk         | iPhoneOS15.2.sdk               |
+-------------+--------------------------------+

@PingvinB That means that the Xcode version is too old.

Oh. I will try to make it use a newer version then. Thank you!

Oh. I will try to make it use a newer version then. Thank you!
Edit: What is the minimum required version of Xcode for sdk 46?
Edit 2: I changed the image in the pipeline from 'macOS-latest' (which apparently is macOS 11) to 'macOS-12'. This uses /Applications/Xcode_13.4.1.app  by default and the build was successful now 👍 Thanks again @wkozyra95

Do you have an example of how to change the image pipline in the configuration settings?

I'm experiencing this today, we haven't added any non-Expo dependencies since the last successful build.

Dependencies added (confirmed via Git diff):
    "expo-image-picker": "~13.3.1",
    "expo-camera": "~12.3.0",
    "expo-screen-orientation": "~4.3.0",
    "expo-image-manipulator": "~10.4.0"

We did another build without making any changes at all and it worked, so maybe an intermittent issue somewhere/somehow?  Do not know enough about EAS's architecture to say.

Hi everyone!
I come accross this error too and change the image used to build the application.
But once build, the IOS application systematically crashed.
Here is the log, maybe someone may have an idea
Last Exception Backtrace:
0   CoreFoundation                	0x1cbaed288 __exceptionPreprocess + 220 (NSException.m:200)
1   libobjc.A.dylib               	0x1e481d744 objc_exception_throw + 60 (objc-exception.mm:565)
2   UMJ                           	0x105070f8c RCTFatal + 668 (RCTAssert.m:146)
3   UMJ                           	0x1050efc14 -[RCTExceptionsManager reportFatal:stack:exceptionId:] + 488 (RCTExceptionsManager.mm:68)
4   UMJ                           	0x1050f04f8 -[RCTExceptionsManager reportException:] + 1412 (RCTExceptionsManager.mm:135)
5   CoreFoundation                	0x1cba75b24 __invoking___ + 148 (:-1)
6   CoreFoundation                	0x1cba93610 -[NSInvocation invoke] + 468 (NSForwarding.m:3378)
7   CoreFoundation                	0x1cbaca5fc -[NSInvocation invokeWithTarget:] + 80 (NSForwarding.m:3475)
8   UMJ                           	0x1050a381c -[RCTModuleMethod invokeWithBridge:module:arguments:] + 460 (RCTModuleMethod.mm:584)
9   UMJ                           	0x1050a5e08 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 536 (RCTNativeModule.mm:183)
10  UMJ                           	0x1050a5a3c operator() + 68 (RCTNativeModule.mm:104)
11  UMJ                           	0x1050a5a3c invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 112 (RCTNativeModule.mm:95)
12  libdispatch.dylib             	0x1cb752e6c _dispatch_call_block_and_release + 32 (init.c:1517)
13  libdispatch.dylib             	0x1cb754a30 _dispatch_client_callout + 20 (object.m:560)
14  libdispatch.dylib             	0x1cb75c124 _dispatch_lane_serial_drain + 668 (inline_internal.h:2622)
15  libdispatch.dylib             	0x1cb75cc80 _dispatch_lane_invoke + 392 (queue.c:3944)
16  libdispatch.dylib             	0x1cb767500 _dispatch_workloop_worker_thread + 648 (queue.c:6732)
17  libsystem_pthread.dylib       	0x23ccad0bc _pthread_wqthread + 288 (pthread.c:2599)
18  libsystem_pthread.dylib       	0x23ccace5c start_wqthread + 8 (:-1)

I just move to Expo 45 and here is my package.json
"dependencies": {
    "@react-native-async-storage/async-storage": "~1.17.3",
    "@react-native-masked-view/masked-view": "0.2.6",
    "@react-navigation/drawer": "^5.12.5",
    "@react-navigation/native": "^5.9.4",
    "@react-navigation/stack": "^5.14.5",
    "@types/react": "~17.0.21",
    "axios": "^0.24.0",
    "dayjs": "^1.10.5",
    "expo": "^45.0.0",
    "expo-application": "~4.1.0",
    "expo-blur": "~11.1.0",
    "expo-constants": "~13.1.1",
    "expo-device": "~4.2.0",
    "expo-document-picker": "~10.2.1",
    "expo-haptics": "~11.2.0",
    "expo-image-picker": "~13.1.1",
    "expo-linear-gradient": "~11.3.0",
    "expo-localization": "~13.0.0",
    "expo-notifications": "~0.15.4",
    "expo-sharing": "~10.2.0",
    "expo-splash-screen": "~0.15.1",
    "expo-status-bar": "~1.3.0",
    "i18n-js": "^3.8.0",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-native": "0.68.2",
    "react-native-calendars": "^1.1263.0",
    "react-native-floating-action": "^1.22.0",
    "react-native-gesture-handler": "~2.2.1",
    "react-native-keyboard-aware-scroll-view": "^0.9.4",
    "react-native-mask-text": "^0.7.0",
    "react-native-pager-view": "5.4.15",
    "react-native-reanimated": "~2.8.0",
    "react-native-safe-area-context": "4.2.4",
    "react-native-screens": "~3.11.1",
    "react-native-web": "0.17.7",
    "react-native-webview": "11.18.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@react-native-community/eslint-config": "^2.0.0",
    "@types/i18n-js": "^3.8.1",
    "@types/react-native": "~0.67.6",
    "@types/react-native-calendars": "^1.1264.3",
    "eslint": "^7.28.0",
    "jest-expo": "^45.0.0",
    "typescript": "~4.3.5"
  },
  "resolutions": {
    "@types/**/@types/react-native": "~0.67.6"
  },
  "jest": {
    "preset": "jest-expo",
    "transformIgnorePatterns": [
      "node_modules/(?!(jest-)?react-native|react-clone-referenced-element|@react-native-community|expo(nent)?|@expo(nent)?/.*|react-navigation|@react-navigation/.*|@unimodules/.*|unimodules|sentry-expo|native-base|@sentry/.*)"
    ]
  }

The error was thrown by incompatibility with a non expo-managed javascript library. In my case it was react-native-keyboard-aware-scroll-view.

I'm getting this error as well on Expo's build servers
❌  ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '13<IP_ADDRESS>.3_0' Reader: '13<IP_ADDRESS>_0')', using libLTO version 'LLVM version 13.0.0, (clang-13<IP_ADDRESS>)' for architecture arm64

I copied the eas.json above with a newer cli version
{
  "cli": {
    "version": ">= 0.53.1",
    "requireCommit": true
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug",
        "image": "latest"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {}
  },
  "submit": {
    "production": {}
  }
}

and my package.json is
  "dependencies": {
    "app": "*",
    "expo": "^44.0.0",
    "expo-dev-client": "~0.8.6",
    "expo-linear-gradient": "~11.0.3",
    "expo-splash-screen": "~0.14.1",
    "expo-status-bar": "~1.2.0",
    "react": "17.0.1",
    "react-dom": "17.0.1",
    "react-native": "0.64.3",
    "react-native-gesture-handler": "~2.1.0",
    "react-native-reanimated": "~2.3.1",
    "react-native-safe-area-context": "3.3.2",
    "react-native-screens": "~3.10.1",
    "react-native-web": "0.17.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@types/react": "~17.0.21",
    "@types/react-native": "~0.64.12",
    "typescript": "~4.3.5"
  },
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web"
  },

The eas build --platform ios --profile development command sort of builds (builds but doesn't run). I'm stumped as I can run the app locally no problem.

This causes apple to flag our code because adds development API calls it seems?
The app references non-public selectors in YOUR_APP: _isKeyDown, _modifiedInput, _modifierFlags. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app.

I had the same problem, do a general cleanup in the credentials section of your project in your expo.dev account and then do a rebuild.

Removing accent on name in app.json solved it for me
{   "expo": {     "name": "withoutAccent" ...

I am getting this issue on SDK 51. Everything worked fine using SDK 49.


Pip install permission error

pip install git+https instead of git+ssh

Thanks! Fixed in the readme in most recent committ


Add rule to upgrade type alias annotations to keyword (UP040)

Adds rule to convert type aliases defined with annotations i.e. x: TypeAlias = int to the new PEP-695 syntax e.g. type x = int.
Does not support using new generic syntax for type variables, will be addressed in a follow-up.
Added as part of pyupgrade — ~the code 100 as chosen to avoid collision with real pyupgrade codes~.
Part of #4617
Builds on #5062

FYI, this was not added to PyUpgrade because the new syntax is not valid at runtime. For example:
# file1.py
type newint = int

# file2.py
from file1 import newint
isinstance(3, newint) # Doesn't work!

This "upgrade" is only valid if you never use the TypeAlias at runtime. Which you can't tell statically (as shown above).
This is a bit safer than PyUpgrade, since you can disable it by code, but it's not a 1:1 upgrade like all the other upgrades.
Standalone example:
$ docker run --rm -it python:3.12-rc
Python 3.12.0b4 (main, Jul 28 2023, 04:24:27) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

>>> type newint = int
>>> isinstance(3, newint)

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: isinstance() arg 2 must be a type, a tuple of types, or a union

Thanks! We can just limit this to .pyi files for now to be safe while we figure out more nuanced detection. (We can certainly detect whether an annotation is used at runtime within a file, so we could always apply this to private type variables as a suggested fix.) Wdyt @zanieb?

Created https://github.com/astral-sh/ruff/issues/6434 to track modifications.


Fix carousel after aspect ratio change

Bug Description
Looks like #872 broke the responsive layout for the carousel, as numbers in assets/src/edit-story/components/canvas/layout.js were not updated.
I suggest moving those constants to assets/src/edit-story/constants.js so they don't get missed next time.
Screenshots
On a 15 inch screen:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

The layout.js has been updated. Probably something is off with the math there.

@swissspidy also, can you please send your current innerWidth/Height - I'm not seeing this layout. The carousel goes into a compact mode for 15" screen for me.

window.innerWidth x window.innerHeight is 1680x916 for me

I can repro. Looking.


Added display:block to svg logo element to fix alignment issue

This fixes bug #1032

@jrbarnes9 spotted another bug, so going to resolve this in this PR.

@jrbarnes9 image scales correctly now as you would expect.

 Issue #1032: Alignment of logo and menu button in the header is incorrect


[HIP] HIP has conflicts with nvcc.

Since f19e7c29dfcef3d0c941c977ce6d1448ad4e288a commit hipcc cannot compile CUDA codes
on Nvidia machines, the compilation fails with this error:
$ pwd
/home/kaveh/source/HIP/samples/0_Intro/square

$   hipcc square.cu
In file included from /usr/local/cuda-10.1//include/driver_types.h:78:0,
                 from /usr/local/cuda-10.1//include/builtin_types.h:59,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:91,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:18:19: error: missing binary operator before token "("
 #if !__has_feature(modules)
                   ^
/home/kaveh/software/hip/include/stddef.h:30:42: error: missing binary operator before token "("
 #if !defined(_PTRDIFF_T) || __has_feature(modules)
                                          ^
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
/home/kaveh/software/hip/include/stddef.h:55:42: error: missing binary operator before token "("
      !defined(_RSIZE_T)) || __has_feature(modules)
                                          ^
In file included from /usr/include/string.h:33:0,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:77,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/strings.h:23:0,
                 from /usr/include/string.h:431,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:77,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/time.h:29:0,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:78,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/c++/7/bits/cxxabi_init_exception.h:38:0,
                 from /usr/include/c++/7/bits/exception_ptr.h:38,
                 from /usr/include/c++/7/exception:142,
                 from /usr/include/c++/7/new:40,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:103,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:18:19: error: missing binary operator before token "("
 #if !__has_feature(modules)
                   ^
/home/kaveh/software/hip/include/stddef.h:30:42: error: missing binary operator before token "("
 #if !defined(_PTRDIFF_T) || __has_feature(modules)
                                          ^
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
/home/kaveh/software/hip/include/stddef.h:55:42: error: missing binary operator before token "("
      !defined(_RSIZE_T)) || __has_feature(modules)
                                          ^
In file included from /usr/include/stdio.h:33:0,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:128,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/x86_64-linux-gnu/bits/_G_config.h:19:0,
                 from /usr/include/x86_64-linux-gnu/bits/libio.h:35,
                 from /usr/include/stdio.h:41,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:128,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/stdlib.h:31:0,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:145:0,
                 from /usr/include/stdlib.h:394,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/alloca.h:24:0,
                 from /usr/include/stdlib.h:566,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)

I see same error with nvcc if I add HIP's include path to my CPATH:

$ nvcc square.cu  ### works fine!
$ export CPATH=$CPATH:/home/kaveh/software/hip/include/
$ nvcc square.cu
In file included from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/driver_types.h:78:0,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/builtin_types.h:59,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:91,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:18:19: error: missing binary operator before token "("
 #if !__has_feature(modules)
                   ^
/home/kaveh/software/hip/include/stddef.h:30:42: error: missing binary operator before token "("
 #if !defined(_PTRDIFF_T) || __has_feature(modules)
                                          ^
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
/home/kaveh/software/hip/include/stddef.h:55:42: error: missing binary operator before token "("
      !defined(_RSIZE_T)) || __has_feature(modules)
                                          ^
In file included from /usr/include/string.h:33:0,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:77,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/strings.h:23:0,
                 from /usr/include/string.h:431,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:77,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/time.h:29:0,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:78,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/c++/7/bits/cxxabi_init_exception.h:38:0,
                 from /usr/include/c++/7/bits/exception_ptr.h:38,
                 from /usr/include/c++/7/exception:142,
                 from /usr/include/c++/7/new:40,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:103,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:18:19: error: missing binary operator before token "("
 #if !__has_feature(modules)
                   ^
/home/kaveh/software/hip/include/stddef.h:30:42: error: missing binary operator before token "("
 #if !defined(_PTRDIFF_T) || __has_feature(modules)
                                          ^
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
/home/kaveh/software/hip/include/stddef.h:55:42: error: missing binary operator before token "("
      !defined(_RSIZE_T)) || __has_feature(modules)
                                          ^
In file included from /usr/include/stdio.h:33:0,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:128,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/x86_64-linux-gnu/bits/_G_config.h:19:0,
                 from /usr/include/x86_64-linux-gnu/bits/libio.h:35,
                 from /usr/include/stdio.h:41,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:128,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/stdlib.h:31:0,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:145:0,
                 from /usr/include/stdlib.h:394,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)
                                       ^
In file included from /usr/include/alloca.h:24:0,
                 from /usr/include/stdlib.h:566,
                 from /usr/include/c++/7/cstdlib:75,
                 from /usr/include/c++/7/stdlib.h:36,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/crt/common_functions.h:129,
                 from /usr/local/cuda-10.1//bin/../targets/x86_64-linux/include/cuda_runtime.h:115,
                 from <command-line>:0:
/home/kaveh/software/hip/include/stddef.h:41:39: error: missing binary operator before token "("
 #if !defined(_SIZE_T) || __has_feature(modules)

It seems nvcc is using HIP's stddef.h which leads to this problem. The lastes working commit is  e1aac060da864beb2afbf29d39566546c8195e9a .

kaveh@hostname:~/source/HIP/samples/0_Intro/square$ hipconfig -f
HIP version  : 2.10.19425-954d1847

== hipconfig
HIP_PATH     : /home/kaveh/software/hip
HIP_PLATFORM : nvcc
CPP_CONFIG   :  -D__HIP_PLATFORM_NVCC__=  -I/home/kaveh/software/hip/include -I/usr/local/cuda-10.1//include

== nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243

=== Environment Variables
PATH=/opt/nvidia/nsight-systems/2019.5.1/bin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/bin/intel64:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/libfabric/bin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/bin:/home/kaveh/software/intel/debugger_2019/gdb/intel64/bin:/home/kaveh/software/pgi/18.10/linux86-64/18.10/bin:/usr/local/cuda-10.1//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/kaveh/software/llvm/9.0.0//bin:/home/kaveh/software/hip/bin:/usr/totalview/bin:/home/kaveh/software/cppp/bin/
CUDAROOT=/usr/local/cuda-10.1/
LD_LIBRARY_PATH=/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/compiler/lib/intel64_lin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/libfabric/lib:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/release:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/ipp/lib/intel64:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/compiler/lib/intel64_lin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/tbb/lib/intel64/gcc4.7:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/tbb/lib/intel64/gcc4.7:/home/kaveh/software/intel/debugger_2019/libipt/intel64/lib:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/daal/lib/intel64_lin:/home/kaveh/software/intel/compilers_and_libraries_2019.4.243/linux/daal/../tbb/lib/intel64_lin/gcc4.4:/usr/local/cuda-10.1//lib::/home/kaveh/software/pgi/18.10/linux86-64/18.10/lib:/home/kaveh/software/llvm/9.0.0//lib
HIP_PATH=/home/kaveh/software/hip
CUDA_ROOT=/usr/local/cuda-10.1/
CUDA_HOME=/usr/local/cuda-10.1/
CUDA_PATH=/usr/local/cuda-10.1/

== Linux Kernel
Hostname     : hostname
Linux hostname 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic

@Kaveh01,

I thought we've come to the conclusion that f19e7c2 is hipify-clang only related change and couldn't affect hipcc/nvcc compilation.

Please confirm that for hipcc compilation HIP's include path is added (or not) to CPATH as for nvcc compilation.

For e1aac060da864beb2afbf29d39566546c8195e9a we do not have stddef.h in HIP_INSTALL/include and f19e7c29dfcef3d0c941c977ce6d1448ad4e288a we have!

I agree with you that the commit seems irrelevant to the error but this is what I observe!

If the particular commit is provided for the bug, it means that triaging is done, and the bug appeared with that commit, so its author should fix the bug. But f19e7c2 is definitely unrelated, thus the triaging is wrong.

with "-DBUILD_HIPIFY_CLANG=OFF" error disappears.

with "-DBUILD_HIPIFY_CLANG=OFF" error disappears.

It doesn't prove that the bug in f19e7c2.
What happen if f19e7c2 is reverted? Does it eliminate the bug?

with "-DBUILD_HIPIFY_CLANG=OFF" error disappears.

It doesn't prove that the bug in f19e7c2.
What happen if f19e7c2 is reverted? Does it eliminate the bug?

The difference is the stddef.h in the HIP_INSTALL_PATH/include and it comes with f19e7c29dfcef3d0c941c977ce6d1448ad4e288a if you compile and install hipify-clang.

What happen if f19e7c2 is reverted? Does it eliminate the bug?

Yes. The difference is the stddef.h in the HIP_INSTALL_PATH/include and it comes with f19e7c2 if you compile and install hipify-clang.

The subfolder include with clang's distributive headers including stddef.h is installed with hipify-clang binary to bin folder. How is this include subfolder relevant to HIP_INSTALL_PATH/include?

What happen if f19e7c2 is reverted? Does it eliminate the bug?

Yes. The difference is the stddef.h in the HIP_INSTALL_PATH/include and it comes with f19e7c2 if you compile and install hipify-clang.

The subfolder include with clang's distributive headers including stddef.h is installed with hipify-clang binary to bin folder. How is this include subfolder relevant to HIP_INSTALL_PATH/include?

stddef.h is installed to HIP_INSTALL_PATH/include please look at the end of the log
(-- Installing: /home/kaveh/software/hip/include/stddef.h) :
~/source/HIP/build$ rm -rf ~/software/hip && rm -rf * && cmake  -DCMAKE_BUILD_TYPE=Release -DBUILD_HIPIFY_CLANG=ON -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DHIP_COMPILER=clang   -DCMAKE_INSTALL_PREFIX=/home/kaveh/software/hip ../ && make -j8 install
-- The C compiler identification is Clang 9.0.0
-- The CXX compiler identification is Clang 9.0.0
-- Check for working C compiler: /home/kaveh/software/llvm/9.0.0/bin/clang
-- Check for working C compiler: /home/kaveh/software/llvm/9.0.0/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /home/kaveh/software/llvm/9.0.0/bin/clang++
-- Check for working CXX compiler: /home/kaveh/software/llvm/9.0.0/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- HIP Platform: nvcc
-- HIP Compiler: clang
-- HIP will be installed in: /home/kaveh/software/hip
-- Generating profiling promitives: /home/kaveh/source/HIP/include/hip/hcc_detail/hip_prof_str.h
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipMemcpyToSymbolAsync
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipMemcpyFromSymbolAsync
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipMemcpyFromSymbol
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: __hipPushCallConfiguration
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipGetSymbolAddress
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipGetSymbolSize
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: hipMemcpyToSymbol
/home/kaveh/source/HIP/hip_prof_gen.py Warning: implementation not found: __hipPopCallConfiguration
/home/kaveh/source/HIP/hip_prof_gen.py Warning: 8 API calls missing in interception layer
CMake Warning (dev) at hipify-clang/CMakeLists.txt:10 (find_package):
  Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables.
  Run "cmake --help-policy CMP0074" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  Environment variable LLVM_ROOT is set to:

    /home/kaveh/software/llvm/9.0.0/

  For compatibility, CMake is ignoring the variable.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found LLVM 9.0.0:
--    - CMake module path: /home/kaveh/software/llvm/9.0.0/lib/cmake/llvm
--    - Include path     : /home/kaveh/software/llvm/9.0.0/include
--    - Binary path      : /home/kaveh/software/llvm/9.0.0/bin
-- Linker detection: GNU ld
CMake Deprecation Warning at CMakeLists.txt:486 (cmake_policy):
  The OLD behavior for policy CMP0037 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.

 It is all about #1571 - fix #1593 is under review, but you may check it.

Thanks @emankov
It fixed with<PHONE_NUMBER>a985660d367109dc53f84728b560cf .


tsp-openapi3: import examples

Clear and concise description of the problem
Now that #2700 is complete, the tsp-openapi tool should be updatet to do the reverse and add example(s) to the TypeSpec. (A single opExample/example if using example, multiple if using examples.)
Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@markcowl @timotheeguerin thanks for backlogging, hopefully it can at least be in beta by Hack


clang: Fix some compilation errors

Fix clang compilation issues when compiling firmware for STM32 with minimal libc.

I probably found regression here. I'm using STM32H5 mcu with zephyr-sdk-0.16.0.
In my application device states has the following location in RAM:
 *(SORT_BY_ALIGNMENT(.z_devstate))
 .z_devstate    0x0000000020000ee4        0x6 zephyr/subsys/retention/libsubsys__retention.a(retention.c.obj)
 .z_devstate    0x0000000020000eea        0x2 zephyr/drivers/interrupt_controller/libdrivers__interrupt_controller.a(intc_exti_stm32.c.obj)
 .z_devstate    0x0000000020000eec        0x2 zephyr/drivers/clock_control/libdrivers__clock_control.a(clock_stm32_ll_h5.c.obj)
 .z_devstate    0x0000000020000eee        0x4 zephyr/drivers/dma/libdrivers__dma.a(dma_stm32u5.c.obj)
 .z_devstate    0x0000000020000ef2        0x2 zephyr/drivers/entropy/libdrivers__entropy.a(entropy_stm32.c.obj)
 .z_devstate    0x0000000020000ef4        0x2 zephyr/drivers/flash/libdrivers__flash.a(flash_stm32_ospi.c.obj)
 .z_devstate    0x0000000020000ef6        0x2 zephyr/drivers/flash/libdrivers__flash.a(flash_stm32.c.obj)
 .z_devstate    0x0000000020000ef8       0x12 zephyr/drivers/gpio/libdrivers__gpio.a(gpio_stm32.c.obj)
 .z_devstate    0x0000000020000f0a        0x2 zephyr/drivers/reset/libdrivers__reset.a(reset_stm32.c.obj)
 .z_devstate    0x0000000020000f0c        0x2 zephyr/drivers/retained_mem/libdrivers__retained_mem.a(retained_mem_zephyr_ram.c.obj)
 .z_devstate    0x0000000020000f0e        0xa zephyr/drivers/serial/libdrivers__serial.a(uart_stm32.c.obj)
 .z_devstate    0x0000000020000f18        0x2 zephyr/drivers/watchdog/libdrivers__watchdog.a(wdt_iwdg_stm32.c.obj)

And now macro DT_FOREACH_PROP_ELEM(DT_NODELABEL(exti), is writing some values there.
After RCC init and before calling exti init:

And now after the call of stm32_exti_init

Data in ranges 0x20000eec to 0x20000efc are set to 0x1a00.

Yes! https://github.com/zephyrproject-rtos/zephyr/pull/58421/commits/ba5e50c20006677788ac3a839227c09a10eaec88 introduces a bug. I mentioned that in my previous comment, but @nashif decided to merge it :shrug:.
I'm working on fix right now. Sorry for the problem.


Migrate Jenkinsfile to GH Actions Workflow

Summary
Migrate Jenkinsfile to GH Actions Workflow
Tasks

[x] Migrate Jenkinsfile
[x] Delete Jenkins Job config
[ ] Delete Jenkins Job
[ ] Update sheet

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-21T11:20:53.361+0000

Duration: 5 min 27 sec

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Hi @trentm!
I need your help here. I'm currently migrating the Jenkinsfile to a GH Actions Workflow.
As you can see in the status checks, the test for node 17 is failing, but only in GH Actions. The Jenkins stage is still successful. The main difference seems to be that Jenkins is utilising docker, while GH Actions seems to be using a native node version.
While I was trying to debug the issue, I found that both actions/setup-node@v3 and docker are using node 17.9.1.
Interestingly, I was able to reproduce the same behaviour locally. When running the install and test script in the node:17 docker container, the tests succeeded.
But running it with node 17 while utilising nvm, the tests are failing the same way as is in the GH Action workflow.
I will take any hint, advice, opinion, suggestion or help!
Thank you.
cc @cachedout

@reakaleek Can you cherry-pick this commit to your branch? https://github.com/elastic/ecs-logging-nodejs/commit/afcba058271c0c345684619b0600b8d4e1dde31e   This should fix the tests for node >=v17.

@reakaleek Can you cherry-pick this commit to your branch? afcba05 This should fix the tests for node >=v17.

HI @trentm,
Thank you for the help. Unfortunately, the test for for node 19 is now failing with a different error. It seems to be related to https://nodejs.org/en/blog/announcements/v19-release-announce/#http-s-1-1-keepalive-by-default

@trentm I was able to make the tests green with https://github.com/elastic/ecs-logging-nodejs/pull/132/commits/54426d985613c50ae72dcaaed376f65b076afbb6.
Let me know what you think and if this patch is sufficient for your use case. Otherwise, please propose a change request.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-22T08:46:58.357+0000

Duration: 8 min 49 sec

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@reakaleek This looks fine but I am curious why you made the changes from localhost -> <IP_ADDRESS>? Was this just for syntactic consistency or was there a functional reason for these changes?

This change was actually cherry-picked by the suggestion here: https://github.com/elastic/ecs-logging-nodejs/pull/132#issuecomment-1362182198


Examples not working

I find a lot of these examples give me the following error - "....is currently not available in location 'EastUS'
zones '' for subscription <my subscription"
Please try another size or deploy to a different location or zones. See
https://aka.ms/azureskunotavailable for details.
Is this because of my subscription or where I am located - tried a few things like different vm sizes etc but no joy.

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

ID: f7a34cbb-1a9d-6192-ed0b-2570e1bdbd0a
Version Independent ID: 0558114d-2381-45e4-61bf-cb078e906518
Content: Create a Virtual Machine Scale Set with Azure PowerShell | Microsoft Docs
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-create-powershell.md
Service: virtual-machine-scale-sets
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@gsuttie Sorry about that experience. Without knowing the location/zone its hard to say, but the best bet would be to follow the guidance at https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-sku-not-available-errors. Once you have walked through it, the issue might just be that the regions in this document aren't available to your subscription and at the bottom of the page their is a link that walks you through opening a support case to get that region enabled in your subscription.


172.3 compatibility

I cannot install the plugin into the 2017.3 EAP. Could you please bump up the version?

I think @dschulten  means 173.* compatibility. I have to revert back to 172.* to get this plugin back

Exactly :)

Yes, as soon as I test the compatibility thoroughly


[Test] permutation factor

The claim is
h_ls^{k1,k2} = (-1)^{l+s-j1-j2} h_ls^{k2,k1}

it can be checked numerically

The difference only appears in interference, therefore the test should be checking the interference of the reference chain with that test chain that is being permuted.
I = |A1(ref) + A3|ˆ2

check that interference is not zero, e.g, #64 setup
Computed the intensity with the permuted chain3

I' = |A1(ref) + c * permute(A3)|ˆ2

where c is the symmetry factor from the header. Is I equal to I'?

modify spin, quantum numbers, make sure that both c positive and negative are covered. See if the identity always true.

There is a chance that it works :-)
I've looked at the same exercise with DPD. It's a but tricky to figure out either pi, or -pi appears for the aligned confuguration if one starts messing up with the order.
for the records, what I get is
(-1)^{j-l-s} * # from Clebsch
 (-1)^{j-lambda}*(-1)^{lambda} * # from D(theta_12)
 (-1)^{j1-lambda1}*(-1)^{lambda1} * # from WignerD: I did not get exactly this, because of +- pi complications
 (-1)^{j2-lambda2}*(-1)^{lambda2} * # from WignerD: I guess this

If I guess right, the product gives exactly (-1)^{l+s-j1-j2}

Im working on it, but cant quite show the desired result yet.
The interference does not properly match yet


Modify setup.py to include python version requirement

Issue 160 noted that Medspacy release 1.0.0 works in python 3.8 and later. Consider adding version requirement in setup.py file.

This looks like a good change.  Thank you for making this since we should have added this in 1.0. Since we do not typically merge directly into master, I've set up a new PR here where this and other PRs can be checked and tested ahead of a next release:
https://github.com/medspacy/medspacy/pull/170

I'll close this PR now that I've merged this one into develop (https://github.com/medspacy/medspacy/pull/170).
Thank you again @andyjessen  for this contribution!


Update README.md

Hello @pr0d33p!
Thank you for your contribution! I appreciate your PR, and would love to merge it into the main repository.
Thanks,
Binit Ghimire (@TheBinitGhimire)


Unit test

Codecov Report

Merging #9 (31fc3c7) into main (6bfb54e) will decrease coverage by 0.14%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
- Coverage   83.30%   83.15%   -0.15%
==========================================
  Files          15       15
  Lines         527      564      +37
==========================================
+ Hits          439      469      +30
- Misses         88       95       +7

Impacted Files
Coverage Δ

OktaPosh/public/Invoke-OktaApi.ps1
76.08% <36.36%> (-0.23%)
:arrow_down:

OktaPosh/public/User.ps1
83.09% <67.85%> (-10.24%)
:arrow_down:

OktaPosh/public/Export-OktaAuthorizationServer.ps1
82.75% <82.14%> (-13.67%)
:arrow_down:

OktaPosh/public/Set-OktaOption.ps1
92.00% <100.00%> (+13.73%)
:arrow_up:

OktaPosh/public/AuthorizationClaim.ps1
93.33% <0.00%> (+16.66%)
:arrow_up:

Continue to review full report at Codecov.

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


Example analysis of LFQ MS/MS data

Do you have example analysis of LFQ MS/MS data?

Hi Javan,
I seemed to have missed your question. No, I do not have any MaxQuant MS1 feature intensity quantitative examples. I have made some progress off and on, but have not set aside the time to finish it up. I do not really like the whole LFQ normalization scheme. It seems wacky to me. I have been working on an "evidence.txt" file parser so that I can take the MQ PSMs through my protein inference algorithm and compute feature sums. Then I could start playing with notebooks and seeing how normalization methods compare, what the summarized data looks like (intensity distributions, CV distributions, etc.), and statistical testing sensitivity, etc. It takes a lot of hours of focused effort to make these pipelines and analyses.
Cheers,
Phil


Enable memory barrier on s390

when I try to compile on s390, error says: #error Please implement AtomicPointer for this platform.
I am not sure how to enable this. Is there any clue on this?

Here is how you find the error in the code:
https://github.com/google/leveldb/search?q=Please+implement+AtomicPointer+for+this+platform
If your compiler is compatible with C++11,  should provide an implementation that AtomicPointer would pick up.

@pwnall emm， actually I have read the source code you in your link. Just have no idea how to implement it.  I will have an deeper look at this.
BTW, can I just replace the leveldb with other one? If I can, could you please give some advice on this? thanks

I don't know how the S390 works, sorry. You either need a compiler with C++11 support, or a very good knowledge of the hardware.
Linux seems to have some code for atomic ops on Z390 that you can use as inspiration:
https://github.com/torvalds/linux/blob/master/arch/s390/include/asm/atomic.h
https://github.com/torvalds/linux/blob/master/arch/s390/include/asm/atomic_ops.h
As for LevelDB alternatives, the benchmarks for alternative databases show how to get operations similar to LevelDB with 2 alternatives:
https://github.com/google/leveldb/tree/master/doc/bench
Compare the code against:
https://github.com/google/leveldb/blob/master/db/db_bench.cc

I have enable memory barrier. I will send the patch.

@pwnall I have pushed the patch, please help review it. Thanks.

How can I push my patch to this repo? I have no access to this origin. So I wonder how can I push my patch?


[C++] S3 Finalization functions need to exist even when S3 isn't enabled.

Describe the bug, including details regarding any error messages, version, and platform.
Before Arrow 12 you could have c++ consumers of Arrow conditional use S3 without knowing if the Arrow they are linking to has S3 support enabled.
 std::string s3_uri = "s3://.....?region=us-east-1";
 auto const no_s3_support = arrow::fs::FileSystemFromUri(s3_uri).status().IsNotImplemented();
 ....

But with Arrow 12 due to AWS SDK issues ( https://github.com/apache/arrow/pull/33858 ) creation of an S3 filesystem
now requires an explicit call to fs::FinalizeS3() during shutdown of the application.  Since the FinalizeS3 function is in the optionally compiled cpp/src/arrow/filesystem/s3fs.cc there is no easy way for a C++ user to determine if they can call FinalizeS3.
I believe that the correct solution is that Arrow needs some generalized shutdown API that is always provided. This API would be aware if S3 support is enabled and call the function when needed. Currently this can't be done by consumers since S3 support can't be safely determined by consumers:
The current solution to work around this, is that every C++ user/consumer needs to use dlopen ( or equivalant on windows ) on either libArrow or the root executable for static builds ( dlopen(NULL)  ) and check if the FinalizeS3 functions exists.
Component(s)
C++

I agree with a finalization API that can be called with/without S3 makes user codes simpler.
We can use the following code for now:
#include <arrow/util/config.h>
#ifdef ARROW_S3
#  include <arrow/filesystem/s3fs.h>
#endif

// ...
#ifdef ARROW_S3
  arrow::fs::EnsureS3Finalized();
#endif

You don't need to use dlopen().

A compile time check is insufficient since it binds our application to a given build of Arrow. The FileSystemFromUri allows us to have runtime support checks since that ensure that we fail gracefully when the user / env has an Arrow build with different build options.
E.g. We build on machines without S3, but run on machines with S3 support.

Does this mean that you build your module's binary with S3 disabled Apache Arrow C++ and your user uses your built-binary with S3 enabled Apache Arrow C++ (that may be built by your user not you)?
Why do you build your module with S3 disabled Apache Arrow C++?

Why do you build your module with S3 disabled Apache Arrow C++?
Because it dramatically simplifies the build env requirements.

We should also remember that the ARROW_S3 is only exposed to CMake downstream users. Anyone that is using package config will not know if the Arrow they are consuming has S3 enabled or not.

We don't support the build style. (We don't guarantee ABI for different build options binaries.)
If you use the build style, it's "use it at your own risk". (Tricky dlopen() may be needed like you for the case.)

We should also remember that the ARROW_S3 is only exposed to CMake downstream users. Anyone that is using package config will not know if the Arrow they are consuming has S3 enabled or not.

Does the "package config" means pkg-config/pkgconf command? If so, we can add support for it by providing arrow-filesystem-s3.pc like we did for JSON module (arrow-json.pc) or adding a s3 variable to arrow-filesystem.pc like *_version in arrow.pc. If you need it, please open a new issue for it.
Note: In C++ level, we can use ARROW_S3  by #include <arrow/util/config.h> as I mentioned at https://github.com/apache/arrow/issues/36974#issuecomment-1661127660 . It doesn't depend on CMake nor pkg-config/pkgconf.

Does the "package config" means pkg-config/pkgconf command? If so, we can add support for it by providing arrow-filesystem-s3.pc like we did for JSON module (arrow-json.pc) or adding a s3 variable to arrow-filesystem.pc like *_version in arrow.pc. If you need it, please open a new issue for it.

Yes I meant the pkg-config files. But I missed in your first explanation that ARROW_S3 is provided via arrow/util/config.h. Since that is build system independent I don't think anything changes are needed.
The entire situtation around the AWS SDK requiring an explicit end of program shutdown call is rather unforunate. I wish we had a cleaner approach but that is best discussed in another issue.
Thank you for the help.


Centralize the configuration for each topic

Right now topics such crime, property, development must be configured in a bunch of different places.
Topics can be configured in the following places

app/adapters/simplicity.arcgis.rest.api.adapter.js : the queries for search method for each topic are defined here
app/simplicity.backend.config.js : the REST endpoints for each topic are defined here as well as the search (geocoder) url
app/components/topics/topic-components/{{topic}}/{{topic}}.factory.js : how to render the topic and default values are defined for each topic in their respective factories, and each topic has custom views

I think these all should be moved to one file, or at least one file for each topic, or something.

:+1:

Created the branch issue-6 for this. Thinking about make a config directory in the root of the app with a bunch of JSON files. Right now,  I just want to duplicate all of the existing configuration, move it to the config directory, and transfer it out of Angular constants and factories and into raw JSON.

Maybe uses something like gulp-ng-config to pull all the JSON config files into the angular app.

So here's what I got going on so far...
I created app/config and app/config/topics directories.
Inside of app/config will be a few json files to config things like search and some ui stuff.
Inside of app/config/topics there will be a separate json file for each topic (including an example.json). Just copy the example json and then fill out the json when adding a new topic.
I'm then using  gulp-jsoncombine and gulp-ng-config to pipe the json to angular constants
So for example if you create a crimes.json and a trash.json in app/config/topics you get a angular constant that looks like
{
 simplicityTopics :
 {
   crimes : {...}
 },
 {
   trash: {...}
 }
}

I'll have some commits tomorrow


[Performance Test] Create Service Invocation test case

The service invocation test case includes a load test tool that is injected as the application next to a Dapr sidecar.
A configuration file for the test will include the following parameters:

qps
client connections
duration

It is important that the deployment config yamls contain taints and tolerations that prevent the test app  pod and the load tester pod from being scheduled on the same node.
The measurements of this test include:

added latency in ms with dapr compared to baseline

The test results will be stored on a local file and/or configurable cloud blob, or returned from an API.
The test case will perform the following flow:
Baseline
Load tester --> [Out of Pod] --> Test App
Dapr
Load tester --> Sidecar --> [Out of Pod] --> Sidecar --> Test App

Closed by #1428


Remove hardcoded values in estimate_fee test

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

Testing

What is the current behavior?

Resolves: #1368
What is the new behavior?

Replace hardcoded value in estimate_fee test with actual fee
Does this introduce a breaking change?

Other information

blocked by #1573
We are going to wait a bit before rebasing and merging this one, okay?

@apoorvsadana Could you help to review this PR? Thanks

repository archived in favor of https://github.com/madara-alliance/madara


A Patch from Randomness CEO (For July (August?) 2021)

Contains 9 patches and optimizations:
Some of the algorithms have been updated, mostly for documentation, but a few small changes here and there.
 It will be closed until a later date, when we feel like we can review it.

OK, I'll reduce the size of the commit

Can I open another one?

Open it to the all-sorts branch.

Why?


[Feature]: Make /tmp folder writable

Is there an existing issue already for this feature request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?
Some of my stored procedures are running plpython3u code, which creates temporary files. Because /tmp is not writable, those are currently created in the pgdata directory (the current working directory).
Describe the solution you'd like
Make /tmp writable.
Describe alternatives you've considered
I found #681, which was turned into a discussion. However, I think this should not need to be worked around.
Additional context
No response
Backport?
N/A
Are you willing to actively contribute to this feature?
No
Code of Conduct

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

I see. That may well be the case. The remainder of the filesystem outside /tmp isn't writable by the postgres user in the container while /tmp is, but the pod configuration may be created in such a way that /tmp also becomes read-only.


Issue with reopening Websocket after Idle 10m

There is no need for these lines as they also prevent the Observable from subscribing again which means the websocket is reopened but the frontend does not process it no more, there might be a better way of doing , I am no Angular expert, but removing these lines worked fine in my deployment here
https://eu-west-3-amer-demo.auth.eu-west-3.amazoncognito.com/login?client_id=3uouf490c5u4mfej54igv25am9&response_type=token&redirect_uri=https://d17sdmhwxn0gs2.cloudfront.net/callback
closeSubscriber.next();
closeSubscriber.complete();
observer.complete();

only removing observer.complete(); would solve the issue


RailsCop detects variable to_time as method when used in a range

In my code, I have
foo(resource_id: rid, range: from_time..to_time) and I get this:
Convention: Do not use to_time on Date objects,because it knows nothing about time zone in use.
While it could be argued that to_time is somewhat ill-conceived name for a variable, it should not be reported as an error.

That's definitely a bug. //cc @palkan


Explain how to use stac_extensions

We need to clarify how to use stac_extensions. Especially with the Commons extension (see #665) it is not so clear where to put what.
Here's an example how it should work for an Item that and a Collection, which both use the Commons extension and the Item shares EO fields also in the Collection:
Collections stac_extension would be: ["commons"]
Items stac_extension would be: ["commons", "eo"]
The reason for having commons in both is that it influences and "extends" both Item and Collection, but the reason for not having eo in Collections ist that eo doesn't extend Collections, but only Items. We should clarify/explain both of these issues in general in the documentation.

Has been solved with PR #677.


Toggle preview functionality?

Can we have the toggle preview functionality? Sometimes, you have to play with the generated html.
Thanks for this great package :)

Thank you for your suggestions, more functions will be updated in the future.

Ok, great :)


#279 Fixes click outside on header items

Added global click outside directive
Fixed hide dropdown menu on header
Fixed hide notification menu on header
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the dev branch. Also you should start your branch off dev branch.
[ ] Check you have added tests that prove your fix is effective or that your feature works.
[ ] Check your code additions will fail neither code linting checks nor unit test.
[ ] Check you added any notable changes to the CHANGELOG.md file.

Description
Please describe your pull request.
💔Thank you!

Codecov Report

Merging #286 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #286   +/-   ##
=========================================
  Coverage     78.85%   78.85%
  Complexity      232      232
=========================================
  Files            82       82
  Lines           752      752
=========================================
  Hits            593      593
  Misses          159      159

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 f13c963...cca4f8f. Read the comment docs.


React big calendar weekly view not working correctly

Hi guys,
I want to say that I love this component. It's very good. I have a problem with it though. In particular I can't make it work for the montly view (that I would actually be more keen to have in my calendar). It seems that all the heights and the rows are 0 and I have no idea why. I've loaded correctly the react-big-calendar css. and I'm using bootstrap 3.3.7 in the project.
Any ideas? here the image

Hi, you have to set an explicit height on your container, from docs:

note: The default styles use height: 100% which means your container must set an explicit height (feel free to adjust the styles to suit your specific needs).

Sorry, I hadn't realised that. my fault. Thanks a lot for the quick reply.


Idea: Show Nuxt tips randomly

Examples:

Do you know you can run npx nuxt build -a to analyze your bundles visually?

Nuxt.js uses [serve-placeholder](https://github.com/nuxt/serve-placeholder] to respond with smarter placeholder the 404 calls?

etc.

I really love this idea!

Comming soon :D

@pi0 is the idea still under implementation or has been scraped, just curious ?

Still in the todo list :)


Leverage WASI Preview2

I believe a lot could be simplified by leveraging the WASI preview2 + WIT work that is happening here. From the JavaScript binding generation perspective, you might have a look in this repo too: https://github.com/bytecodealliance/jco.

The JCO tool does what you are describing. It actually generates the binding for JavaScript (both js and d.ts files) from a WIT definition. You can find an example of usage here.

I started looking at jco and what I need to do for VS Code. Since things will be special in VS Code (it is not a pure browser nor a pure Node.js environment) I am currently exploring the following approach:

implement the canonical API (https://github.com/WebAssembly/component-model/blob/main/design/mvp/CanonicalABI.md) in a way that matches VS Code characteristics. Especially we need to support forwarding API implementation from the wasm worker thread to the extension host main thread.
Generate VS Code implementation from a wit file.

A first implementation cut is in branch dbaeumer/monetary-ox-cyan. Interesting might be:

https://github.com/microsoft/vscode-wasm/blob/b33d132e36e1f8021a6e9e9e41608ea77b2c8b30/wasm-wasi-core/src/common/preview2/wasi.ts#L1
and a WIT parser and AST based on Peggy (https://github.com/microsoft/vscode-wasm/blob/b33d132e36e1f8021a6e9e9e41608ea77b2c8b30/tools/src/wit.pegjs#L1)

Please note that this is all work in progress however I think that parts of the  canonical API implementation might be useful for projects that use TypeScript. It is very likely not useful for project that use pure JavaScript since I use some TS typing rules to make the usage side easier (see for example how Variants are handle using is statement (https://github.com/microsoft/vscode-wasm/blob/b33d132e36e1f8021a6e9e9e41608ea77b2c8b30/wasm-wasi-core/src/common/preview2/wasi.ts#L1203)


Updated support for App Proxy and RD Web Client

App Proxy now supports the RD Web Client. I'm requesting to update the note on this page to avoid customer confusion. A blog post announcing this support is planned for this week.

@briantaintor as FYI.

@Heidilohr  tagging you as well for help approving since this doc change is necessary. We've just released support for this functionality today.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/windowsserverdocs/blob/master/articles/windows-server-overview.md
Private repo URL: https://github.com/Microsoft/windowsserverdocs-pr/blob/master/articles/windows-server-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


CHEBI:61258, wrong structure

The structure of nickel-iron-sulfur cluster contains nitrogen (N) instead of nickel (Ni).

Thanks for letting us know. The structure has been updated.


Javascript error prevents some server consoles from working

I'm experiencing a strange behavior with the server consoles. When I open the server page where the console is at it stays blank for some servers. On these servers it non operational and even the Start/Stop/... buttons don't work. Upon closer inspection I noticed that the following error appears in the browser console: TypeError: data.line is undefined  console.js:200:9
However this error only appears on servers with a certain service. Namely the Waterfall service (Waterfall is an alternative BungeeCord) I created myself. It used to work before though. And since I haven't used the panel in a good month I can't exactly pinpoint when it stopped working. I also had a hard shutdown on the server during the period of no usage.
It is also very weird that when I start the server the console works while I stay on the page. As soons as I leave and come back to it it stops working.
I'll happily provide additional information when requested.
I'm using the panel version 0.6.4 and do not use any themes. Other versions below:
uname -a:
Linux BrainHost 4.12.0-1-amd64 #1 SMP Debian 4.12.6-1 (2017-08-12) x86_64 GNU/Linux

php -v:
PHP 7.1.8-1 (cli) (built: Aug  3 2017 18:35:23) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
    with Zend OPcache v7.1.8-1, Copyright (c) 1999-2017, by Zend Technologies

docker info:
Containers: 3
 Running: 3
 Paused: 0
 Stopped: 0
Images: 10
Server Version: 17.09.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.12.0-1-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.34GiB
Name: BrainHost
ID: BX5U:Q3RA:MQL6:GFJ5:PKCG:7YXX:APWL:DCLP:BMQW:OSRZ:ZSF3:54GA
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No swap limit support

According to https://github.com/Pterodactyl/Panel/blame/develop/public/themes/pterodactyl/js/frontend/console.js#L200 @DaneEveritt last changed that line.

Definitely having this issue too it's quite annoying.

After wrapping data.line with String() at https://github.com/Pterodactyl/Panel/blame/develop/public/themes/pterodactyl/js/frontend/console.js#L200 I was able to get everything working again but at the beginning of the console I see "undefined" what this means to me is that the initial log is not being loaded.
Recently waterfall a fork of Bungeecord made some changes to the way they handle and store log files. This is likely incompatible with the service configuration included with Pterodactyl, though it still shouldn't be crashing the console just because there is a missing log file.

Ok. After correcting the log path it is working again.
So I guess the base issue is that if the configured log file can't be found that the error appears. It should be handled and if possible an error message indicating that the log could not be found should appear.

Fixed with #710


Is Subsequence

Is your feature request related to a problem? Please describe.
It is a problem on Leetcode which can be solved using dynamic programming.
Describe the solution you'd like
I would like to solve it in Java
Additional context
Problem Link: https://leetcode.com/problems/is-subsequence/

I want to do this question in C++ if available.


Fatal: number of used blobs is larger than number of available blobs

hello,
It seems I have a problem:
$ restic prune -r $RESTIC_REPOSITORY
gives:

repository d923f435 opened successfully, password is correct
counting files in repo
building new index for repo
[12:53] 100.00%  54603 / 54603 packs
repository contains 54603 packs (731631 blobs) with 249.787 GiB
processed 731631 blobs: 0 duplicate blobs, 0 B duplicate
load all snapshots
find data that is still in use for 20 snapshots
[0:18] 100.00%  20 / 20 snapshots
Fatal: number of used blobs is larger than number of available blobs!
Please report this error (along with the output of the 'prune' run) at
https://github.com/restic/restic/issues/new

so what ?
cheers

possible precision: I'm not sure but this problem may have come after a bad 'restic forget...', during which the network was suddenly cut.

Please fill in the details asked for in the Bug template: https://github.com/restic/restic/issues/new?assignees=&labels=&template=Bug.md
Besides that, you're using a rather old restic version, please run restic check using restic 0.12.1 to provide more details on the current state of the repository.
restic forget ... cannot cause that problem at all unless you're using the --prune option. And even the latter case shouldn't be a problem. Please provide the full commands which you think could have been a problem.

sorry for the delay, it took me 3 days to gather the info...
-->
Output of restic version
ANSWER
$ restic version
restic 0.12.1 compiled with go1.16.6 on linux/amd64
How did you run restic exactly?
ANSWER
the problem appeared after the following cmd, during which the wifi was cut before the end:
$ restic forget -r $RESTIC_REPOSITORY --keep-hourly 12 --keep-daily 8 --keep-weekly 4 --keep-monthly 12 --keep-yearly 3 --prune

What backend/server/service did you use to store the repository?
ANSWER

I'm not sure I fully understand the question... I will try and give all the needed info, but please ask if anything is missing.

the problem appears at several levels, but may be summarised by a 'check':
$ restic check -r $RESTIC_REPOSITORY --read-data-subset="1/100"
using temporary cache in /tmp/restic-check-cache-208101817
repository d923f435 opened successfully, password is correct
created new cache in /tmp/restic-check-cache-208101817
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
error for tree 86f54bad:pshots
tree 86f54bad: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 89f68a0a:apshots
tree 89f68a0a: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 93065d78:apshots
tree 93065d78: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree e79be157:apshots
tree e79be157: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 3fe9e47b:
tree 3fe9e47b: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 93c10d5b:apshots
tree 93c10d5b: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 5e7fb310:napshots
tree 5e7fb310: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree d09b54bb:napshots
tree d09b54bb: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
error for tree 6206fce0:napshots
tree 6206fce0: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
[0:57] 100.00%  18 / 18 snapshots
error for tree 31492cd6:
tree 31492cd6: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index
read group #1 of 653 data packs (out of total 51768 packs in 100 groups)
[0:57] 16.23%  106 / 653 packs
[0:58] 16.69%  109 / 653 packs
[5:03] 100.00%  653 / 653 packs
Fatal: repository contains errors

the environment variable RESTIC_REPOSITORY is
$ echo $RESTIC_REPOSITORY
rest:https://<login, pw, address & port>

Expected behavior
ANSWER
check without error nor error message
..................................................
Do you have any idea what may have caused this?
ANSWER
I was using restic for months without any problems, until this time where the wifi was cut during the cmd 'retic forget ... --prune'. That's why I suspect this could be due to this wifi cut
Do you have an idea how to solve the issue?
ANSWER
actually I already had a similar problem a time ago and I think it can be solved by re-init the repository but then all the backups are lost... I was looking for something more "friendly".
Did restic help you today? Did it make you happy in any way?
ANSWER
wonderful tool...
 happy new year

tree 3fe9e47b: file "index" blob b6417b6b8781ea4144ef23f83ded09b5c2f98faf71bf68ff14f77560c245119d not found in index

I would try restic rebuild-index or if that doesn't help wird --read-all-packs, so restic rebuild-index --read-all-packs. If you have a copy of the repository I'd try that, otherwise I'd wait for @MichaelEischer to answer.

I would try restic rebuild-index or if that doesn't help wird --read-all-packs, so restic rebuild-index --read-all-packs.

I'm somewhat sure that won't help here, as restic does not complain about files that are not contained in the index. And check did not complain about a mismatch between the pack files and the index. On the other hand, that makes no sense at all, when prune was interrupted halfways. Which commands did you run after the failed forget --prune?
As the prune implementation has been completely rewritten since restic 0.9.6, and that or an older version was used for the interrupted forget --prune  command, there's not much use in investigating what went wrong in detail as it's quite likely already been fixed. If you still have to output of the interrupted forget --prune run, then it would nevertheless still be interesting to see it.
Otherwise, let's just jump to repairing the repository. Please follow the steps described in https://github.com/restic/restic/issues/828#issuecomment-706186047 as "Route 2".

sorry, I completely lost the logs. I followed route 2 of the link, 'restic finding' all the bad trees and 'restic forgetting'  the corresponding snapshots. Seems it works... but it remains only 4 snapshots... better than 0...
thank you for all

Closing as the problem has been resolved.


added es6 features.

@RonLek @djcruz93 Would like to get your inputs on it : )

@RonLek @djcruz93 Would like to get your inputs on it : )

@Sumitraj387 please resolve the due conflicts as well.

@Sumitraj387 please resolve the due conflicts as well.

@Sumitraj387 I am unable to understand why only some functions are made arrow functions?

@Sumitraj387 I am unable to understand why only some functions are made arrow functions?


Added Calendar.NOVEMBER instead of 10 Magic constant

Hi , I added Calendar.NOVEMBER instead of 10 Magic constant

Hi, @Lczajkowski  May you change the label hacktoberfest-accepted  instead of Hacktoberfest. Thanks :)


Broken link to download Deployment Checker for ASDK

The link with this name can't find the download for the ASDK pre-req checker script.
Deployment Checker for ASDK
https://go.microsoft.com/fwlink/?LinkId=828735&clcid=0x409
It now redirects to the TechNet Gallery script samples browser.

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

ID: 289cb46f-b173-0ec0-ace1-6e038f82c553
Version Independent ID: 8f72a4e5-fba9-6631-1924-3b649446bf18
Content: Download and extract the ASDK - Azure Stack Development Kit (ASDK)
Content Source: azure-stack/asdk/asdk-download.md
Service: azure-stack
Sub-service: azure-stack-hub-asdk
GitHub Login: @PatAltimore
Microsoft Alias: patricka

Hello @tysonflint , thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you soon.

@tysonflint, I verified that the script was hosted on the retired gallery.technet.microsoft.com. We are working on updating the new link on this page and will keep you posted. Thanks again for reporting this!

Hi @tysonflint,
Thanks for finding and reporting the issue. We've reviewed, updated, tested, and hosted the script on GitHub. The link has been updated to point to https://github.com/Azure/AzureStack-Tools/blob/master/Deployment/asdk-prechecker.ps1.
I'm going to close the issue.
Thanks,
Pat
#please-close


VMR Build Tagging is Failing

Example pipeline run (internal Microsoft link)
This is the commit that caused the failure: https://github.com/dotnet/sdk/commit/b66c80019ad5d67147186b97e66d59a5c23b28b3

This is the error I get when I try to run the darc command locally:
/dotnet/src/sdk# ../../.dotnet/dotnet darc vmr get-version --vmr /dotnet sdk
Unhandled exception encountered
System.InvalidOperationException: Unable to resolve service for type 'Microsoft.DotNet.DarcLib.VirtualMonoRepo.IVmrDependencyTracker' while attempting to activate 'Microsoft.DotNet.Darc.Operations.VirtualMonoRepo.GetRepoVersionOperation'.
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance[T](IServiceProvider provider, Object[] parameters)
   at Microsoft.DotNet.Darc.Options.CommandLineOptions`1.GetOperation(ServiceProvider sp) in /_/src/Microsoft.DotNet.Darc/Darc/Options/CommandLineOptions.cs:line 25
   at Microsoft.DotNet.Darc.Program.RunOperation(CommandLineOptions opts, ServiceProvider sp) in /_/src/Microsoft.DotNet.Darc/Darc/Program.cs:line 68

@premun - I believe that you merged https://github.com/dotnet/sdk/pull/44554 which updated darc in sdk. Can you please TAL? Thanks.

Will do! Sorry about this, I guess we don't have E2E tests for this command

Hi , this issue reoccurred with the same error, so I reopened it, example pipeline run (internal Microsoft link)
@premun @marcpopMSFT , this issue caused by https://github.com/dotnet/sdk/pull/44625, could you please TAL? Thanks.

Yeah, it's because we reverted an update but then it got merged again here which I didn't notice: https://github.com/dotnet/sdk/pull/44625
I will open a manual PR to bump to the correct version

Fix is here: https://github.com/dotnet/sdk/pull/44632

Okay, the pipeline is green after the update: https://dev.azure.com/dnceng/internal/_build/results?buildId=2575516&view=logs&j=fa5c2909-0e29-5671-d5eb-16d6c40e0c4a&t=22eb0279-f706-5157-2789-5196ba7b00a6&l=14