Add Android community CI

The previous Android CI has been offline for nearly a year. We'd like to volunteer to take on the community CI builds for Android.

@marcprux Email sent for additional information. Thanks

The main issue with the current setup is that it was using the bootstrap build, so once that broke, it no longer built the compiler. If you simply use the same build preset but provide an OS environment with a prebuilt Swift toolchain and Android NDK 26d available, it should work.

Btw, I updated trunk to work with NDK 27, so the latest NDK 27c should work now.

Node: https://ci-external.swift.org/computer/ubuntu-24.04-android-arm64/
Job: https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-arm64/
Job: https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-build/

The NDK 27c installation is at ANDROID_NDK. It is also set to SWIFT_ANDROID_NDK_PATH, which build-script-impl script suggests should be automatically used, but it appears not:
$  ./swift/utils/build-script --preset buildbot_linux_crosscompile_android,tools=RA,stdlib=RD,build install_destdir=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install installable_package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz

[./swift/utils/build-script] ERROR: no value found for ndk_path in "%(ndk_path)s"

Tacking it onto the end of the command with ndk_path=${ANDROID_NDK} does successfully kick off the build, though.
Should I make a PR for build-presets.ini with this flag, or should be added by the Jenkins controller?

Manually running the Android build with:
./swift/utils/build-script --preset buildbot_linux_crosscompile_android,tools=RA,stdlib=RD,build install_destdir=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install installable_package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz ndk_path=${ANDROID_NDK} --reconfigure

eventually errors out with:
+ /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/cmake-linux-x86_64/bin/cmake --build /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/swift-linux-x86_64 -- -j4 all swift-stdlib-linux-x86_64 swift-stdlib-android-aarch64 swift-libexec-linux-x86_64 swift-libexec-android-aarch64
ninja: error: 'stdlib/public/core/SwiftMacros', needed by 'stdlib/public/core/LINUX/x86_64/Swift.o', missing and no known rule to make it

This is the same error cited by https://github.com/swiftlang/swift/pull/77795, so I'm wondering if https://github.com/swiftlang/swift/pull/77815 will fix it.

Should I make a PR for build-presets.ini with this flag, or should be added by the Jenkins controller?

The latter, Swift build presets are customizable with such declared command-line flags, though I believe it ignores the --reconfigure you added, certainly other undeclared customizations. The Android build presets expect the NDK path to be passed in by this ndk_path flag and will not work without it.

This is the same error cited by https://github.com/swiftlang/swift/pull/77795, so I'm wondering if https://github.com/swiftlang/swift/pull/77815 will fix it.

That shouldn't be necessary: if you simply install a prebuilt Swift toolchain for the host and add it to the PATH, as I noted a couple weeks ago, the CMake build automatically picks it up and uses it to build the Swift portions of the trunk compiler.
There is no reason to bootstrap the trunk compiler on this CI when there are already prebuilt host toolchains available for linux.

if you simply install a prebuilt Swift toolchain for the host and add it to the PATH, as I noted a couple weeks ago, the CMake build automatically picks it up and uses it to build the Swift portions of the trunk compiler.

That seems to not be the case:
swiftci@skipbox:~$ which swift
/home/swiftci/swift/swift-current/usr/bin/swift

swiftci@skipbox:~$ swift --version
Swift version 6.0.2 (swift-6.0.2-RELEASE)
Target: x86_64-unknown-linux-gnu

swiftci@skipbox:~$  ~/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script --preset buildbot_linux_crosscompile_android,tools=RA,stdlib=RD,build install_destdir=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install installable_package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz ndk_path=${ANDROID_NDK}

[/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script] NOTE: using preset "buildbot_linux_crosscompile_android,tools=RA,stdlib=RD,build", which expands to

/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script --assertions --swift-enable-ast-verifier=0 --no-swift-stdlib-assertions '--swift-install-components=autolink-driver;compiler;clang-resource-dir-symlink;libexec;stdlib;swift-remote-mirror;sdk-overlay;static-mirror-lib;toolchain-tools;license;sourcekit-inproc' '--llvm-install-components=llvm-ar;llvm-ranlib;llvm-cov;llvm-profdata;IndexStore;clang;clang-resource-headers;compiler-rt;clangd;lld;LTO;clang-features-file' --build-subdir=buildbot_linux --release --test --validation-test --long-test --stress-test --test-optimized '--lit-args=-v --time-tests' --build-ninja --android --android-ndk=/home/swiftci/android/ndk/android-ndk --android-api-level=21 --build-swift-static-stdlib --build-swift-static-sdk-overlay --build-swift-stdlib-unittest-extra --install-destdir=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install --installable-package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz --host-test --install-prefix=/usr --install-llvm --install-static-linux-config --install-swift --install-swiftsyntax --skip-test-linux --skip-build-benchmarks --skip-early-swiftsyntax --reconfigure

[/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script] NOTE: Using toolchain default

…

-- Build files have been written to: /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/swift-linux-x86_64
+ popd
~
+ /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/cmake-linux-x86_64/bin/cmake --build /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/swift-linux-x86_64 -- -j4 all swift-stdlib-linux-x86_64 swift-stdlib-android-aarch64 swift-libexec-linux-x86_64 swift-libexec-android-aarch64
ninja: error: 'stdlib/public/core/SwiftMacros', needed by 'stdlib/public/core/LINUX/x86_64/Swift.o', missing and no known rule to make it
ERROR: command `['/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script-impl', '--workspace', '/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build', '--build-dir', '/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux', '--install-prefix', '/usr', '--host-target', 'linux-x86_64', '--stdlib-deployment-targets=linux-x86_64 android-aarch64', '--host-cc', '/usr/bin/clang', '--host-cxx', '/usr/bin/clang++', '--darwin-xcrun-toolchain', 'default', '--darwin-deployment-version-osx=13.0', '--darwin-deployment-version-ios=16.0', '--darwin-deployment-version-tvos=16.0', '--darwin-deployment-version-watchos=6.0', '--darwin-deployment-version-xros=1.0', '--cmake', '/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/cmake-linux-x86_64/bin/cmake', '--llvm-build-type', 'Release', '--swift-build-type', 'Release', '--swift-stdlib-build-type', 'Release', '--lldb-build-type', 'Release', '--foundation-build-type', 'Release', '--libdispatch-build-type', 'Release', '--xctest-build-type', 'Release', '--llbuild-build-type', 'Release', '--swift-enable-assertions', 'true', '--swift-stdlib-enable-assertions', 'false', '--swift-analyze-code-coverage', 'false', '--llbuild-enable-assertions', 'true', '--lldb-assertions', 'true', '--cmake-generator', 'Ninja', '--cross-compile-append-host-target-to-destdir', 'true', '--build-jobs', '4', '--lit-jobs', '4', '--common-cmake-options=-G Ninja -DCMAKE_C_COMPILER:PATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:PATH=/usr/bin/clang++ -DCMAKE_Swift_COMPILER:PATH=/home/swiftci/swift/swift-current/usr/bin/swiftc -DCMAKE_LIBTOOL:PATH= -DCMAKE_AR:PATH=/usr/bin/ar -DCMAKE_RANLIB:PATH=/usr/bin/ranlib -DLLVM_VERSION_MAJOR:STRING=17 -DLLVM_VERSION_MINOR:STRING=0 -DLLVM_VERSION_PATCH:STRING=0 -DCLANG_VERSION_MAJOR:STRING=17 -DCLANG_VERSION_MINOR:STRING=0 -DCLANG_VERSION_PATCH:STRING=0 -DCMAKE_MAKE_PROGRAM=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/ninja-build/ninja', '--build-args=-j4', '--dsymutil-jobs', '1', '--build-swift-libexec', 'true', '--swift-enable-backtracing', 'true', '--build-swift-clang-overlays', 'true', '--build-swift-remote-mirror', 'true', '--swift-cmake-options=-DCMAKE_EXPORT_COMPILE_COMMANDS=TRUE -DSWIFT_FORCE_OPTIMIZED_TYPECHECKER:BOOL=FALSE -DSWIFT_STDLIB_ENABLE_STDLIBCORE_EXCLUSIVITY_CHECKING:BOOL=FALSE -DSWIFT_ENABLE_EXPERIMENTAL_DIFFERENTIABLE_PROGRAMMING:BOOL=TRUE -DSWIFT_ENABLE_EXPERIMENTAL_CONCURRENCY:BOOL=TRUE -DSWIFT_ENABLE_EXPERIMENTAL_CXX_INTEROP:BOOL=TRUE -DSWIFT_ENABLE_CXX_INTEROP_SWIFT_BRIDGING_HEADER:BOOL=TRUE -DSWIFT_ENABLE_EXPERIMENTAL_POINTER_BOUNDS:BOOL=FALSE -DSWIFT_ENABLE_EXPERIMENTAL_DISTRIBUTED:BOOL=TRUE -DSWIFT_ENABLE_BACKTRACING:BOOL=TRUE -DSWIFT_ENABLE_EXPERIMENTAL_OBSERVATION:BOOL=TRUE -DSWIFT_ENABLE_SYNCHRONIZATION:BOOL=TRUE -DSWIFT_ENABLE_VOLATILE:BOOL=TRUE -DSWIFT_STDLIB_STATIC_PRINT=FALSE -DSWIFT_FREESTANDING_IS_DARWIN:BOOL=FALSE -DSWIFT_STDLIB_BUILD_PRIVATE:BOOL=TRUE -DSWIFT_STDLIB_ENABLE_UNICODE_DATA=TRUE -DSWIFT_SHOULD_BUILD_EMBEDDED_STDLIB=TRUE -DSWIFT_SHOULD_BUILD_EMBEDDED_STDLIB_CROSS_COMPILING=FALSE -DSWIFT_STDLIB_BUILD_SYMBOL_GRAPHS:BOOL=FALSE -DSWIFT_TOOLS_LD64_LTO_CODEGEN_ONLY_FOR_SUPPORTING_TARGETS:BOOL=FALSE -DSWIFT_ENABLE_EXPERIMENTAL_PARSER_VALIDATION:BOOL=TRUE -USWIFT_DEBUGINFO_NON_LTO_ARGS', '--build-stdlib-deployment-targets', 'all', '--ninja-bin=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/ninja-build/ninja', '--install-destdir', '/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install', '--skip-build-benchmarks', '--skip-build-foundation', '--skip-build-xctest', '--skip-build-lldb', '--skip-build-llbuild', '--skip-build-libcxx', '--skip-build-libdispatch', '--skip-build-libxml2', '--skip-build-zlib', '--skip-build-curl', '--build-swift-dynamic-stdlib', '--build-swift-static-stdlib', '--build-swift-stdlib-unittest-extra', '--build-swift-dynamic-sdk-overlay', '--build-swift-static-sdk-overlay', '--validation-test', '--long-test', '--stress-test', '--skip-test-benchmarks', '--android-arch', 'aarch64', '--android-ndk', '/home/swiftci/android/ndk/android-ndk', '--android-api-level', '21', '--android-deploy-device-path', '/data/local/tmp', '--extra-cmake-options=-USWIFT_DARWIN_SUPPORTED_ARCHS -DSWIFT_EARLY_SWIFT_DRIVER_BUILD=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/earlyswiftdriver-linux-x86_64/release/bin', '--swift-enable-ast-verifier=0', '--swift-install-components=autolink-driver;compiler;clang-resource-dir-symlink;libexec;stdlib;swift-remote-mirror;sdk-overlay;static-mirror-lib;toolchain-tools;license;sourcekit-inproc', '--installable-package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz', '--install-swift', '--reconfigure', '--llvm-lit-args=-v --time-tests --param color_output', '--llvm-install-components=llvm-ar;llvm-ranlib;llvm-cov;llvm-profdata;IndexStore;clang;clang-resource-headers;compiler-rt;clangd;lld;LTO;clang-features-file', '--musl-path=/usr/local/musl', '--linux-static-archs=x86_64;aarch64', '--only-execute', 'linux-x86_64-swift-build']` terminated with a non-zero exit status 1, aborting

ERROR: command `['/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift/utils/build-script', '--assertions', '--swift-enable-ast-verifier=0', '--no-swift-stdlib-assertions', '--swift-install-components=autolink-driver;compiler;clang-resource-dir-symlink;libexec;stdlib;swift-remote-mirror;sdk-overlay;static-mirror-lib;toolchain-tools;license;sourcekit-inproc', '--llvm-install-components=llvm-ar;llvm-ranlib;llvm-cov;llvm-profdata;IndexStore;clang;clang-resource-headers;compiler-rt;clangd;lld;LTO;clang-features-file', '--build-subdir=buildbot_linux', '--release', '--test', '--validation-test', '--long-test', '--stress-test', '--test-optimized', '--lit-args=-v --time-tests', '--build-ninja', '--android', '--android-ndk=/home/swiftci/android/ndk/android-ndk', '--android-api-level=21', '--build-swift-static-stdlib', '--build-swift-static-sdk-overlay', '--build-swift-stdlib-unittest-extra', '--install-destdir=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/swift-nightly-install', '--installable-package=/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/2-android.tar.gz', '--host-test', '--install-prefix=/usr', '--install-llvm', '--install-static-linux-config', '--install-swift', '--install-swiftsyntax', '--skip-test-linux', '--skip-build-benchmarks', '--skip-early-swiftsyntax', '--reconfigure']` terminated with a non-zero exit status 1, aborting

You snipped out the relevant portion where the CMake config for the trunk Swift compiler is supposed to find it:
-- Found assembler: /opt/swift/5.8.1/usr/bin/clang
CMake Warning (dev) at CMakeLists.txt:108 (enable_language):
  project() should be called prior to this enable_language() call.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- The Swift compiler identification is Apple 5.8.1
-- Check for working Swift compiler: /opt/swift/5.8.1/usr/bin/swiftc
-- Check for working Swift compiler: /opt/swift/5.8.1/usr/bin/swiftc - works
-- CMake (/home/build-user/build/cmake-linux-x86_64/bin/cmake) Version: 3.30.2
-- CMake Make Program (/home/build-user/build/buildbot_linux/ninja-build/ninja) Version: 1.11.1                                                                    -- C Compiler (/opt/swift/5.8.1/usr/bin/clang) Version: 13.0.0
-- C++ Compiler (/opt/swift/5.8.1/usr/bin/clang++) Version: 13.0.0                                                                                -- Assembler (/opt/swift/5.8.1/usr/bin/clang) Version:                                                                                -- Swift Compiler (/opt/swift/5.8.1/usr/bin/swiftc) Version: 5.8.1
--   Implicit 'string-processing' import: TRUE
--   Implicit 'backtracing' import: FALSE
--   Package CMO: NO
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed

That log snippet shows how the linux CI has CMake find the prebuilt Swift 5.8.1 toolchain used from its PATH.
Is it possible your PATH is different in the CI environment where build-script is actually run somehow? Take a look at that log output to see what CMake is finding.

The Jenkins-submitted build is still failing immediately due to the missing ndk_path (https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-build/lastBuild/consoleFull). But when I manually add it to the PATH and run the build manually, it does seem to pick up the compiler:
-- The Swift compiler identification is Apple 6.0.2
-- Check for working Swift compiler: /home/swiftci/swift/swift-current/usr/bin/swiftc
-- Check for working Swift compiler: /home/swiftci/swift/swift-current/usr/bin/swiftc - works
CMake Warning at CMakeLists.txt:820 (message):
  Force setting SWIFT_BUILD_REGEX_PARSER_IN_COMPILER=OFF because Swift parser
  integration is disabled

-- CMake (/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/cmake-linux-x86_64/bin/cmake) Version: 3.30.2
-- CMake Make Program (/home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-build/build/buildbot_linux/ninja-build/ninja) Version: 1.11.1
-- C Compiler (/usr/bin/clang) Version: 18.1.3
-- C++ Compiler (/usr/bin/clang++) Version: 18.1.3

@shahmishal, can you configure Jenkins for the Android CI to:

Set ndk_path to /home/swiftci/android/ndk/android-ndk
Set the PATH environment to include /home/swiftci/swift/swift-current/usr/bin to pick up the Swift compiler (I had added it to ~/.profile, but it doesn't looks like the Jenkins agent pick up the environment from there)

@shahmishal, can you configure Jenkins for the Android CI to:

@shahmishal, should I be requesting this through some other forum?

@marcprux Sorry, I was out last week. Let me look into this later today.

Both jobs are now updated:

[Build 67 or newer] https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-build/67/console
[Build 64 or newer] https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-24.04-android-arm64/

OK, it finds the prebuilt Swift compiler now, so you can start updating the presets. You'll want to start building the swift-syntax parser again, add android-arch=armv7 to the base preset (I switched the Android default arch to AArch64 earlier this year), and while you're at it, fix the CMake log output to remove the incorrect ENV portion.
@drodriguez, is it okay if we modify the README to remove the links to your old community CI, which it looks like stopped running a couple months ago?

@drodriguez, is it okay if we modify the README to remove the links to your old community CI, which it looks like stopped running a couple months ago?

Yes, we should update the README.

add android-arch=armv7 to the base preset

Oh wait, you are proposing CI for aarch64 and x86_64 instead. In that case, maybe just leave the base preset alone for that variable, so it defaults to aarch64, then add a new x86_64 preset and update this pull to explicitly list that new x86_64 preset instead.

That shouldn't be necessary: if you simply install a prebuilt Swift toolchain for the host and add it to the PATH, as I noted a couple weeks ago, the CMake build automatically picks it up and uses it to build the Swift portions of the trunk compiler.

Even though the build is now finding the host toolchain:
-- Check for working Swift compiler: /home/swiftci/swift/swift-current/usr/bin/swiftc
-- Check for working Swift compiler: /home/swiftci/swift/swift-current/usr/bin/swiftc - works

It is still ultimately failing with the same error:
+ /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-arm64/cmake-linux-x86_64/bin/cmake --build /home/swiftci/jenkins/workspace/oss-swift-RA-linux-ubuntu-24.04-android-arm64/buildbot_linux/swift-linux-x86_64 -- -j4 all swift-stdlib-linux-x86_64 swift-stdlib-android-aarch64 swift-libexec-linux-x86_64 swift-libexec-android-aarch64
ninja: error: 'stdlib/public/core/SwiftMacros', needed by 'stdlib/public/core/LINUX/x86_64/Swift.o', missing and no known rule to make it

Should we be adding build-llvm=0 to build-presets.ini?
I almost wonder if we should add a new Android preset that exactly mirrors your working build script:
./swift/utils/build-script -RA --skip-build-cmark --build-llvm=0 --android --android-ndk $ANDROID_NDK_LATEST_HOME --android-arch ${{ matrix.arch }} --android-api-level $ANDROID_API_LEVEL --build-swift-tools=0 --native-swift-tools-path=${TOOLCHAIN}/bin --native-clang-tools-path=${TOOLCHAIN}/bin --cross-compile-hosts=android-${{ matrix.arch }} --cross-compile-deps-path=$SDK --skip-local-build --build-swift-static-stdlib --xctest --skip-early-swift-driver --install-swift --install-libdispatch --install-foundation --install-xctest --install-destdir=$SDK --swift-install-components='compiler;clang-resource-dir-symlink;license;stdlib;sdk-overlay' --cross-compile-append-host-target-to-destdir=False -b -p --install-llbuild --sourcekit-lsp --skip-early-swiftsyntax

It is still ultimately failing with the same error:

That is most likely related to the now incorrect skip-early-swiftsyntax flag in the preset that I linked to above. Try it out locally and see.

Should we be adding build-llvm=0 to build-presets.ini?

The point of this community CI is to regularly build the trunk compiler and test it for Android, so that wouldn't make sense. I do think the official CI rebuilds way too much code, and told Mishal years ago that it should employ some build caching, so that a recently built compiler build directory for a certain compiler commit can be reused between, let's say, swift-foundation builds.
Some of that has been done, eg SwiftPM "self-hosted" smoke tests now use the prebuilt nightly snapshot compiler instead of building the latest trunk compiler commit from source each time, but not nearly enough build caching on the CI has been added.
The problem is that you'd have to clearly state the build dependency tree first to know what repo depends on what, eg the compiler build also builds libdispatch so that's a circular dependency of sorts, and that work likely hasn't been done.
I hope Mishal gets some help with his official CI work- I thought I saw on Mastodon that Apple was hiring build engineers for Swift- and they can get that implemented some day.

I almost wonder if we should add a new Android preset that exactly mirrors your working build script

That's the plan for the official CI at some point, which is moving up to the top of my task queue, though it would have to build the trunk compiler also, unlike my Android CI which just uses the prebuilt compiler snapshots.
If you find setting this up too much of a hassle, we could just wait for that official Android CI instead. This preset will only really help keep the compiler validation suite up to date for Android, which has little to no effect on my Android CI and its SDK bundles. You mentioned some failed trunk runs on my Android CI in asking for this community CI, but that's mostly related to my upstreaming Android patches for other repos like SwiftPM, which aren't even built by this preset.
And considering I expect to get the official Android CI submitted in the next couple months, this community CI would only be useful for those few prior months.
Your call: there is some value in fixing the last tests in the compiler validation suite for Android, and getting this preset working isn't much effort. But this community CI will have basically no effect on my own Android CI and the trunk SDK bundles it generates.

@marcprux the existing Android presets were the presets used by the community CI which was disconnected at the end of September. Feel free to repourpose those presets for the new community CI. No need to create new ones (well, if you want to modernize to skip armv7 and do something more meaningful that should be fine). If a Swift toolchain is present in the new CI machines, the changes from swift#68895 should not be necessary anymore.

What form will this take? Will it be just another preset that is built using the same Jenkins process, or a whole separate CI mechanism?

It would be part of the official CI, which are Docker images that run a build preset through Jenkins, similar to this community CI.

how do you envision it integrating with PRs and the like?

Initially, it would be another post-commit CI, like the couple dozen that run now. Maybe it would graduate to a pre-commit CI at some point, as Alex discussed on the forum earlier this year.

I certainly don't want to duplicate work.

You wouldn't, I haven't done anything about the official Android CI yet. If you want to spearhead this, whether with the community or official CI, go for it, and I will assist when I can.

My goal was to first get the current preset working, and then start proposing additions to it like building SwiftPM, Foundation, and other essential packages that frequently need to be patched due to breakage.

I agree about the corelibs, as I wrote up in my plan for the official CI when discussing it with Alex on the forum.
As for building SwiftPM and other outside packages for Android, I don't know if the official CI does that type of extra validation, particularly for platforms for which it does not distribute an official native toolchain, only a cross-compilation SDK. Building the compiler and corelibs and running their tests is mostly what I see it doing for other platforms now.
Also, in my experience, everything has been pretty stable and I see almost no breakage with most of the Swift repos. If you're referring to the sometimes failing builds on my Android CI, that's usually because I'm still upstreaming patches for the new Android overlay and Foundation rewrite from earlier this year and I don't know when those will be included in a new snapshot tag. So when one of my patches makes it into a snapshot tag, my CI will try to apply the same patch and fail.
That's not a big deal and is quickly fixed, plus it's just a temporary situation after all the Android overlay/rewrite changes earlier this year.

Alright, changing the base preset and adding one for x86_64 shows that this CI works, as it now builds the Swift compiler and fails when cross-compiling the stdlib for Android, because the passed-in path to the Android NDK on this CI doesn't have the NDK version.
That's fine: I'll update the stdlib CMake config to check the NDK's source.properties instead, which is a more reliable way to check the NDK version that I need on my Android CI also.
So keep this NDK path the way it is, but update this pull to use the right aarch64 and new x86_64 presets now.
@shahmishal, I don't know if you need to change any other internal config to use the new x86_64 preset also, but once those last changes are in, we can get this merged and Marc and I can then iterate on the presets and fixing tests for Android.

If we need to change the preset, please update the nodes/aarch64_ubuntu_22_04_android.json and nodes/x86_64_ubuntu_22_04_android.json in this PR.

@shahmishal, we got the compiler validation suite running on this new CI finally, so once you adjust the CI jobs to these two presets, this is ready for merging.

Oh, one discrepancy I noticed is that this pull says 22.04, but the CI jobs are named and seem to run 24.04.

Oh, one discrepancy I noticed is that this pull says 22.04, but the CI jobs are named and seem to run 24.04.

Fixed in edcc8e3 and c7c1865


Strange behaviour while locking and unlocking a list

Hi,
I have a variable that is controlling if the list is locked or not.
It works well before any change in the ordering.
But as soon as I change the order of an item, and then lock the list again it behaves in an incorrect way.
Now the component is allowing me to reorder the items, which is good but I can still drag the items.
Check it here https://codepen.io/hugomau/pen/WGNrbJ
Any ideia if this a bug or is there something I can do so that if a list is locked the item are not draggable.
Thank you,
Hugo Maurício

Sorry for not replying in a sensible timeframe. I will do my best to investigate in the coming weekend.

Hi there. I'm answering this at last...
This is a jQuery-UI issue, where changing the items options after the initialization causes this issue.
This has been reported before and is related to several issues.
Duplicate of #268, #456, #379.
As noted in the codeped that you forked, you might be able to use the cancel option for your use case.
// The `cancel` option is preferable,
// in case that you are
// updating the item classes on runtime
// eg: adding/removing the `not-sortable` class
// cancel: ".not-sortable"
// The `items` works in case that
// you are not manipulating the items.
// It also prevents us from placing an item
// above "Item 1" or below "Item 6"
items: "li:not(.not-sortable)"

Also, take a look at the alternative approach suggested at #225.


VM diagnostics

By following the article below, i am trying to enable the diagnostics settings using Azure CLI instead of manually for my Azure VM. however the script runs fine but it is not enabling the diagnostics setting and also no error message. please help me out with the solution. https://docs.microsoft.com/en-us/cli/azure/vm/diagnostics?view=azure-cli-latest&viewFallbackFrom=azure-cli-latest.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
Add any other context about the problem here.

Hello @prafulbusa, what does the cli return when you run the command and what did you expect. As much information as possible / reasonable would be helpful. Thanks!

Unable to set guest-level monitoring disagnostic from azure cli.
Cx is automating the creation of VMs using azure cli and one of the things that he was trying to do is set the diagnostics as shown below.  When he look at the result from the Azure portal, it shows the diagnostic being set but the the save button is enabled meaning the diagnostic setting has not been saved and has to be done manually.  I am not clear as to why this is occurring and what should be done to not end up in such a state.

This syntax {foo} was not used to imply it was a shell variable. It is the standard placeholder syntax we use in examples. However, since the entire example presents itself as a script, it would make sense to use bash variable syntax.

I have the same issue - az cli setting of diagnostics does not work for windows unless the save is performed in the portal for that vm's diagnostic setting. (BTW, not an issue with Linux VMs.).
my_vm_resource_id=$(az vm show -g $my_resource_group -n $my_win_vm --query "id" -o tsv)
protected_settings="{'storageAccountName': '${my_diagnostic_storage_account}',
'storageAccountSasToken': '${storage_sastoken}'}"
default_config=$(az vm diagnostics get-default-config --is-windows-os
| sed "s#DIAGNOSTIC_STORAGE_ACCOUNT#$my_diagnostic_storage_account#g"
| sed "s#VM_OR_VMSS_RESOURCE_ID#$my_vm_resource_id#g")
storage_sastoken=$(az storage account generate-sas
--account-name $my_diagnostic_storage_account --expiry 2037-12-31T23:59:00Z
--permissions wlacu --resource-types co --services bt -o tsv)
az vm extension set --publisher Microsoft.Azure.Diagnostics
--name IaaSDiagnostics
--protected-settings "${protected_settings}"
--settings "${default_config}"
--version "1.5"
--resource-group $my_resource_group --vm-name $my_win_vm

Outputs using
az vm show -n gr-sim-win -g gr-rg-westcentralus --query "resources[]"
presave.txt
postsave.txt

@jagan-at-vi, I will look into these. You can remove / update the txt files. They have your subscriptions ids in them.

@jagan-at-vi, I could reproduce this issue with windows VMs. I, too, couldn't set the extension. Even after fixing / altering the default config settings. It seems, this might be a service side issue.
I reached out to the extension's documentation authors for help.

The issue I see is that the agent does not seem to create any of the tables in the specified storage account that are needed for the APIs to retrieve rows relating to counter values.
…
________________________________ From: adewaleo<EMAIL_ADDRESS>Sent: Thursday, January 3, 2019 10:06:46 AM To: Azure/azure-cli Cc: Jagan Jagannathan; Mention Subject: Re: [Azure/azure-cli] DNM [vm] update diagnostics set example. Fix bug in diagnostics get-default-config --is-windows-os (#8117) Tried the latest default_config per above and not having success in seeing even tables being created in the storage account @jagan-at-vihttps://github.com/jagan-at-vi, what error did you get in the CLI. There seems to be an issue with setting the extension using the CLI. This is why I placed a do not merge label on the PR. I will at least try to find some work around and mention it in 8108. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8117 (comment)>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8dxmsWusSdcy3zhFBI77HyDmSctTks5u_ka2gaJpZM4ZfNRA.
________________________________ The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.

@jagan-at-vi. Yes, I understand the extension is not getting successfully provisioned. When I asked what error you got, I meant what the output / result of executing the diagnostics set / extensions set command was? I wanted to confirm that it is a similar error to what I was getting. I am sure if you run az vm show -n yourVMName -g yourRG you will see that the extension's provisioning state is "failed".

See attached for output of az vm show

From: adewaleo<EMAIL_ADDRESS>Sent: Thursday, January 3, 2019 1:05:24 PM
To: Azure/azure-cli
Cc: Jagan Jagannathan; Mention
Subject: Re: [Azure/azure-cli] VM diagnostics (#8108)
The issue I see is that the agent does not seem to create any of the tables in the specified storage account that are needed for the APIs to retrieve rows relating to counter values.
…
________________________________ From: adewaleo notifications<EMAIL_ADDRESS>Sent: Thursday, January 3, 2019 10:06:46 AM To: Azure/azure-cli Cc: Jagan Jagannathan; Mention Subject: Re: [Azure/azure-cli] DNM [vm] update diagnostics set example. Fix bug in diagnostics get-default-config --is-windows-os (#8117https://github.com/Azure/azure-cli/pull/8117) Tried the latest default_config per above and not having success in seeing even tables being created in the storage account @jagan-at-vihttps://github.com/jagan-at-vihttps://github.com/jagan-at-vi, what error did you get in the CLI. There seems to be an issue with setting the extension using the CLI. This is why I placed a do not merge label on the PR. I will at least try to find some work around and mention it in 8108. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#8117 (comment)https://github.com/Azure/azure-cli/pull/8117#issuecomment-451227328>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8dxmsWusSdcy3zhFBI77HyDmSctTks5u_ka2gaJpZM4ZfNRA.
________________________________ The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.
@jagan-at-vihttps://github.com/jagan-at-vi. Yes, I understand the extension is not getting successfully provisioned. When I asked what error you got, I meant what the output / result of executing the diagnostics set / extensions set command was? I wanted to confirm that it is a similar error to what I was getting. I am sure if you run az vm show -n yourVMName -g yourRG you will see that the extension's provisioning state is "failed".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/8108#issuecomment-451276824, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8U1ZgjIsWAz6U2JtjgK9OAP6qgDKks5u_nCUgaJpZM4ZbXa8.
--

The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.

@jagan-at-vi I don't see any attached output of vm show. What might be more helpful in this case is the error you get when you run the extension set / diagnostics set command.
Also, this issue appears to be a service side issue and a CLI issue. Hence, the updated labels. I have reached out to a member of the Windows Azure diagnostics team / owners.

az_vm_show.txt

The file you sent me shows that the extension was provisioned successfully. If this is truly the case, please make sure you are inspecting the correct storage account and that you are doing so properly.
As I have mentioned previously, there is an issue where attempting to set the diagnostics extension on a windows vm fails. I am waiting for feedback / help from @brahmnes who works on the extension, as this is beyond a CLI problem.

Ok - will wait for further word
(Looking at the correct storage account)
.........................................
Sent from mobile device

From: adewaleo<EMAIL_ADDRESS>Sent: Thursday, January 3, 2019 14:31
To: Azure/azure-cli
Cc: Jagan Jagannathan; Mention
Subject: Re: [Azure/azure-cli] VM diagnostics (#8108)
The file you sent me shows that the extension was provisioned successfully. If this is truly the case, please make sure you are inspecting the correct storage account and that you are doing so properly.
As I have mentioned previously, there is an issue where attempting to set the diagnostics extension on a windows vm fails. I am waiting for feedback / help from @brahmneshttps://github.com/brahmnes who works on the extension, as this is beyond a CLI problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/8108#issuecomment-451298515, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8exvjm38ar6QRhyGDbpLOr2c_ABNks5u_oTFgaJpZM4ZbXa8.
--

The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.

@jagan-at-vi, FYI, The work around that worked for me was to go on the portal and click save after the CLI diagnostics / extension command failed to successfully provision the extension. After clicking save, the extension was provisioned successfully and the storage account started receiving diagnostics data. I used a configuration identical to the config found in PR #8117 for the windows diagnostics extension.

Yes that works for me as well except I am trying to avoid any user intervention.  Thanks for your help
.........................................
Sent from mobile device

From: adewaleo<EMAIL_ADDRESS>Sent: Thursday, January 3, 2019 14:44
To: Azure/azure-cli
Cc: Jagan Jagannathan; Mention
Subject: Re: [Azure/azure-cli] VM diagnostics (#8108)
@jagan-at-vihttps://github.com/jagan-at-vi, FYI, The work around that worked for me was to go on the portal and click save after the CLI diagnostics / extension command failed to successfully provision the extension. After clicking save, the extension was provisioned successfully and the storage account started receiving diagnostics data. I used a configuration identical to the config found in PR #8117https://github.com/Azure/azure-cli/pull/8117 for the windows diagnostics extension.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/8108#issuecomment-451301499, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Amli8Xc-X2UrQL2bPk4OEkka0G_NWv14ks5u_oewgaJpZM4ZbXa8.
--

The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please contact the sender immediately and permanently delete or destroy the material/information.

@prafulbusa and @jagan-at-vi
The newly added windows diagnostics example and updated diagnostics config in pull request #8117 work work correctly for setting diagnostics on a vm. The example also shows how one can use a storage account key as an alternative to using a storage account sas token.
The issue is that the WAD extension has strict expectations of the sas token's format. Moreover, it gives poor errors if setting the diagnostics extension fails. The status logs on the VM were helpful in coming up with a solution (thanks @brahmnes).
For the vm diagnostics set command to work properly, the sas token should:

be enabled for the 'container (c)' and 'object (o)' resource type
be enabled for 'blob (b)' and 'table (t)' services. This means your storage account must support blobs and tables
be generated with 'acuw' permissions. i.e. 'add', 'create', 'update' and 'write'
permit only HTTPS

I did not try slight variations of this. Before using these settings I got cryptic warnings such as:
"The given key was not present in the dictionary." (likely due to a bug in the parsing logic of the sastoken) and "No primary storage account" (likely when the extension rejects the token for not having the desired attributes). @brahmnes, work should be done to give richer / clearer errors when sastoken parsing fails.
When the pr #8117 is merged, I will close this issue.
Please let me know if you have any more questions @jagan-at-vi and @prafulbusa. Thanks so much for your patience!
cc: @yugangw-msft

I just met alike issue when I enabled diagnostics agent with the cli command.
I let 2 windows vm enable diagnostics use the same storage account, they're enable succeed. but 2 vm display the same metric graph from metric of first VM.

I will follow up with this issue.

@qwordy please can you follow up with this when you have time?
@kingweo I am no longer on the CLI team.
What do you mean by the 2 vms display the same metric graph? My tip for now is to verify the settings for the two VMs are different even though they are targeting the same storage account. Did you try enabling diagnostics with the portal and compare the settings via portal with the settings you used in the CLI?
Also if the CLI is passing your diagnostics settings correctly, then it is not a CLI issue.

Thank you for quick reply.
I just found the reason of this issue. I used old version of az cli to set diagnostics.
As this example from az cli refrence as below:
default_config=$(az vm diagnostics get-default-config | sed "s#__DIAGNOSTIC_STORAGE_ACCOUNT__#$my_diagnostic_storage_account#g"  | sed "s#__VM_OR_VMSS_RESOURCE_ID__#$my_vm_resource_id#g")
You should be know it was not be found that the string "VM_OR_VMSS_RESOURCE_ID"  in parts of windows os from  _vm_diagnostics_templates.py with the old version.
I hope someone meet the same issue and he can upgrade his az cli to latest version for resolve it correctly.


aws-cdk-lib hardcoded to a specific version

Describe the bug
The version of the dependency aws-cdk-lib in cdk-eks-blueprints is hardcoded to a specific version. Therefore, if there is a mismatch with the version of aws-cdk-lib of your project you encounter a TypeScript complication error.
Expected Behavior
That I am able to upgrade the version of aws-cdk-lib in my package.json and I do not get a complication error.
Current Behavior
If I change aws-cdk-lib in my package.json to a version not matching what cdk-eks-blueprints wants I get a complication error.
Reproduction Steps
Use "@aws-quickstart/eks-blueprints": "^1.13.1 with "aws-cdk-lib": "2.97.0" defined in your package.json.
Possible Solution

https://github.com/aws-quickstart/cdk-eks-blueprints/pull/519

Additional Information/Context
No response
CDK CLI Version
N/A
EKS Blueprints Version
No response
Node.js Version
N/A
Environment details (OS name and version, etc.)
N/A
Other information
Related

https://github.com/aws-quickstart/cdk-eks-blueprints/issues/423
https://github.com/aws-quickstart/cdk-eks-blueprints/issues/468
https://github.com/aws-quickstart/cdk-eks-blueprints/issues/517

Thinking more about this, you actually do not even need to touch your package.json manually to get this complication errors. Your usage/installation commands will install @aws-quickstart/eks-blueprints with a caret(^) so it is not pinned. So if I do an npm update I could start getting complication errors.

I think an important thing to note about CDK users is that they may not come from a development background. Even with my development background, prior experience with CDK and basic Node/NPM knowledge this was still an hour of debugging for me to resolve it.

@DeveloperC286 thank you for your feedback.
You can upgrade the version of CDK to any version without issues if you use the override functionality as shown here. We should document it better for sure.
However, your feedback is spot-on. Many users don't have dev background or background in node/npm and it created more issues than we expected.
The pinned version was a conscious choice, as we observed cases when upgrading CDK version broke blueprints functionality. It is probably time to reevaluate this as it was more common in the past.

You can upgrade the version of CDK to any version without issues if you use the override functionality as shown here. We should document it better for sure.

Thank you for the link, I had found that solution from yourself in your replys to prior issues. Once I knew what the problem was it was simple to fix, but getting from a typescript error to the problem was the challenging part.

However, your feedback is spot-on. Many users don't have dev background or background in node/npm and it created more issues than we expected.

I was asked by someone without a development background for help, someone who is very proficient with AWS and CloudFormation and without my help this would have been a roadblocker for adopting cdk-eks-blueprints.

The pinned version was a conscious choice, as we observed cases when upgrading CDK version broke blueprints functionality. It is probably time to reevaluate this as it was more common in the past.

A combination to tackle both problems of making sure people do not use untested CDK versions and removing this dependency issue could be to use a version range e.g. accept 2.80 -> 2.110(or what ever versions you have tested).

@DeveloperC286 1.14.0 release is out and should have the fix to address this issue.
CDK depedency is moved to peerDependencies. You can read more on the behavior here.
This approach eliminates the situation when CDK version mismatch is causing a compile issue. It also makes it easier to change the version of CDK to the latest (with warning).
Please let me know if you have any feedback.

@DeveloperC286 1.14.0 release is out and should have the fix to address this issue. CDK depedency is moved to peerDependencies. You can read more on the behavior here.
This approach eliminates the situation when CDK version mismatch is causing a compile issue. It also makes it easier to change the version of CDK to the latest (with warning).
Please let me know if you have any feedback.

Thank you, this is far easier now to know about the missing/mismatched CDK version rather than a mysterious complication error :tada:
My only comment would be it would be great if the version wasn't pinned to a specific version. Even a range of versions it has been tested against would be better.

Atm, the pipeline is only testing against the version specified in the release. It seems that the peer dependency solution is a good indication of the version we tested against, but also allows setting any other CDK version if you need to.
I can relax the pinned version to a range, but atm the team is only equipped to accept issues against the tested version as testing gets more and more complex with the proliferation of options and addons.


wxpython inspection tools opened by default

windows 10
Python 3.6
Gooey Version 1.0.3 branch

Since  11a53edac1f980e0e847b260d0cbf9126b07690a  whenever running, a new window of wxpython inspection tools is opened.
is there a way to turn off this behavior?
it seems weird to me that by default this debug tool is opened.
it happens since adding line:
wx.lib.inspection.InspectionTool().Show()
to gooey/gui/application.py
Thanks! ^_^

it seems weird to me that by default this debug tool is opened.

Yeah, that's the branch on which I do all the active dev stuff ¯\(ツ)/¯ It's got a bit of cruft / debug noise floating around.
I'd say this isn't an issue, as it's a dev branch, but, just to make sure I don't forget, let's leave it open : )


[fix](case function) Applying for an array in the heap to avoid stack overflow

… overflow
Proposed changes
Issue Number: close #xxx
Applying for an array in the heap to avoid stack overflow.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.59 seconds
stream load tsv:          507 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>0 Bytes

run p0

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.74 seconds
stream load tsv:          507 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.1 seconds inserted 10000000 Rows, about 343K ops/s
storage size:<PHONE_NUMBER>0 Bytes


Updated actions version i.e checkout@4 and paths-filter@v3

This pull request:

Updates the checkout action from version 3 to version 4
Updates the paths-filter action from version 2 to version 3

Please ignore trimmed trailing whitespaces.

This pull request:

Updates the checkout action from version 3 to version 4
Updates the paths-filter action from version 2 to version 3

Please ignore trimmed trailing whitespaces.


Added i18n namespace for NRQL

Added a new i18n namespace 'NRQL' which allows for the translation of the warning about the fallback NRQL statement being used with each chart.

I'm closing this PR before merge due to some concerns about previously merged changes still showing. I will recreate my fork/branch from the dev branch and submit a new PR.


bg pattern added in all pages

Issue #546

@RavindraP04 Add green splash at home page open source program section behind the image
and i think in the about us page add the splash at the top and also in the team member section the green dots are more

In the About Us section I have added green splash but the it looks different in different browser like it looks bright in firefox but dull in chrome
Firefox

Chrome

@Debajyoti14 Updated with all the changes


Rasa Chat error

Chat window not responding the throws following error in the server backend
Got an action of utter type. Fetching info from db
Error occurred. Respond back with Rasa NLU only
Error occurred. Respond back with Rasa NLU only
ReferenceError: err is not defined
at /Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/mw_routes/core_router.js:249:20
at tryCatcher (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:693:18)
at Async._drainQueue (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:781:20)
at tryOnImmediate (timers.js:743:5)
at processImmediate [as _immediateCallback] (timers.js:714:5)
also below error
DB Error while getting agent details.
TypeError: Cannot read property 'rasa_core_enabled' of undefined
at routeRequest (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/middleware.js:43:16)
at /Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/middleware.js:32:7
at tryCatcher (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:693:18)
at Async._drainQueue (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:781:20)
at tryOnImmediate (timers.js:743:5)
at processImmediate [as _immediateCallback] (timers.js:714:5)

@karthikbalu , when rasaui app is loading, does it show a successfull connection to the DB?
example:
Postgres DB Connected
Using connection string from: package.json
Postgres Server: <IP_ADDRESS>:5432
Database:rasaui
Schema:public

yes
Rasa UI Server: http://localhost:5001
Express server listening on port 5001
Rasa NLU Connected
Using connection string from: package.json
Rasa NLU Server: http://localhost:5004
Rasa Core Connected
Using connection string from: package.json
Rasa Core Server: http://localhost:5005
Postgres DB Connected
Using connection string from: package.json
Postgres Server: <IP_ADDRESS>:5432
Database:rasaui
Schema:public

No Token, but got an Auth request. Allowing it
Authenticate User
Rasa NLU Status Request -> http://localhost:5004/status
Rasa NLU Version Request -> http://localhost:5004/version
settings.getSettings
Rasa NLU Status Request -> http://localhost:5004/status
Rasa NLU Config Request -> http://localhost:5004/config
Got to parse middleware
Cache Not Found for Agent. Making a DB call for: clofusbot
Agent Information: []
DB Error while getting agent details.
TypeError: Cannot read property 'rasa_core_enabled' of undefined
at routeRequest (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/middleware.js:43:16)
at /Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/middleware.js:32:7
at tryCatcher (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:693:18)
at Async._drainQueue (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:781:20)
at tryOnImmediate (timers.js:743:5)
at processImmediate [as _immediateCallback] (timers.js:714:5)
Got to parse middleware
Cache Not Found for Agent. Making a DB call for: clofus
Agent Information: [{"agent_id":1,"agent_name":"clofus","endpoint_enabled":false,"endpoint_url":null,"basic_auth_username":"admin","basic_auth_password":"admin","rasa_core_enabled":true}]
Rasa Core Parse Request -> http://localhost:5005/conversations/admin/parse
Create Initial cache for rasa Core Parse Request
After request:{"next_action": "utter_hi", "tracker": {"sender_id": "admin", "slots": {"cuisine": null, "matches": null}, "latest_message": {"intent": {"name": "greet", "confidence": 0.14112411263389862}, "entities": [], "intent_ranking": [{"name": "greet", "confidence": 0.14112411263389862}, {"name": "clofus_exclamation", "confidence": 0.07309127466825298}, {"name": "are_we_friends", "confidence": 0.0407103315283429}, {"name": "clofus_bye", "confidence": 0.03611548804431702}, {"name": "thank_you", "confidence": 0.03406156390588131}, {"name": "you_are_welcome", "confidence": 0.03301081745902056}, {"name": "you_are_bad", "confidence": 0.032712847530855675}, {"name": "confirmation", "confidence": 0.03065388490764292}, {"name": "dont_care", "confidence": 0.02443560822268291}, {"name": "answer_me", "confidence": 0.023677292022909118}], "text": "hi"}, "latest_event_time":<PHONE_NUMBER>.499337, "paused": false, "events": null}}
Rasa Core Resonse: {"next_action":"utter_hi","tracker":{"sender_id":"admin","slots":{"cuisine":null,"matches":null},"latest_message":{"intent":{"name":"greet","confidence":0.14112411263389862},"entities":[],"intent_ranking":[{"name":"greet","confidence":0.14112411263389862},{"name":"clofus_exclamation","confidence":0.07309127466825298},{"name":"are_we_friends","confidence":0.0407103315283429},{"name":"clofus_bye","confidence":0.03611548804431702},{"name":"thank_you","confidence":0.03406156390588131},{"name":"you_are_welcome","confidence":0.03301081745902056},{"name":"you_are_bad","confidence":0.032712847530855675},{"name":"confirmation","confidence":0.03065388490764292},{"name":"dont_care","confidence":0.02443560822268291},{"name":"answer_me","confidence":0.023677292022909118}],"text":"hi"},"latest_event_time":1525026779.499337,"paused":false,"events":null}}
Got an action of utter type. Fetching info from db
Error occurred. Respond back with Rasa NLU only
Error occurred. Respond back with Rasa NLU only
ReferenceError: err is not defined
at /Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/server/routes/mw_routes/core_router.js:249:20
at tryCatcher (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/promise.js:693:18)
at Async._drainQueue (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/Users/karthikbalu/MYDRIVE/DEVELOPMENT/PROTOTYPES/rasa-ui/rasaui/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:781:20)
at tryOnImmediate (timers.js:743:5)
at processImmediate [as _immediateCallback] (timers.js:714:5)
Rasa NLU Status Request -> http://localhost:5004/status
Rasa NLU Config Request -> http://localhost:5004/config

@karthikbalu

DB Error while getting agent details.

Is the Agent created in Postgres DB? Can you check that? It looks like there might have been an error when creating an agent it self

Hi All,
Can someone please help me figure out what can be possible reasons for the connection error in rasa_nlu and rasa_core. I'm getting the following result on executing npm start in rasaui folder.
<EMAIL_ADDRESS>start /home/praneesh/chatbot/rasa-ui
node server/server.js
Rasa UI Server: http://localhost:5001
Express server listening on port 5001
Rasa NLU Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5000
Using connection string from: package.json
Rasa Core Error: Error: connect ECONNREFUSED <IP_ADDRESS>:5005
Using connection string from: package.json
Postgres DB Connected
Using connection string from: package.json
Postgres Server: <IP_ADDRESS>:5432
Database:rasaui
Schema:public
I have updated the package.json file. Here is the configuration attribute of the file.
"config": {
"rasanluendpoint": "http://localhost:5000",
"rasacoreendpoint": "http://localhost:5005",
"coresecuritytoken": "",
"nlusecuritytoken": "",
"cacheagents": false,
"jwtsecret": "th1s1sn0t0nlyths3cr3tbutth3m0st1mp0rtAntp13c30f1nf0rmAt10nf0rth1sAppl1cAt10n",
"postgresserver": "postgres://:@localhost:5432/rasaui"
}
Please let me know how can I fix this issue.

@praneesh12 please check the configuration in package.json. That should be picked up at the startup of the server. Please open another issue if it still persists.


Add port to route uris if present

[#147569369]
Signed-off-by: Belinda Liu<EMAIL_ADDRESS>Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

Change the route model to return route port as part of it's URI, mainly to include it for tcp routes in VCAP_APPLICATION

An explanation of the use cases your change solves
For applications to register their uri for service discovery, the route port is necessary.

Links to any other associated PRs

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bundle exec rake

[x] I have run CF Acceptance Tests on bosh lite

Thanks,
CF Routing
@jberkhahn && @belinda-liu

Forgot to tag the commit with the PR : (
We merged this in with commit https://github.com/cloudfoundry/cloud_controller_ng/tree/4b0d2d33d35fe536e5ed0ab5b1d6ad0a3c6bdaf2


fix typo

typo means typographic error, here it fixes phpdoc annotation. title should reflect the changes to avoid clickbait merge requests


the exact behaviour of assignment semantics on callable types

hello
consider this: var pickyCallable: {(l: any): any, (): aType };
in the above example, only functions that have both (l: any): any and (): aType signatures could be assigned to this "pickyCallable" thing; is this the actual behaviour of the typecheckr?

No, that's not how it works. In an assignment f = g, where f and g are functions of type F and G, for each signature in F there must be at least one compatible signature in G, but F and G aren't required to be identical. So:
var x: { (x: any): any, (): aType };
var y: { (x: any): any };
var z: { (): aType };
x = y;  // Error
x = z;  // Ok

The x = y assignment is an error because x can be called with no arguments, but y always expects an argument. The x = z assignment is ok because y is free to ignore the argument possibly passed to x, and aDate is assignment compatible with any.
See also #4661.


Android build on Mac OS X - V2

Hey guys, i am having issues to build your starter cutePuppy app.
This is the error which i got in terminal.

Hello! Do you have the Android sdk installed on your mac? The easiest way to install it is to install Android studio. This will also give you an easy to keep the sdk updated. Thanks for using Ionic!

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


fix: RabbitMQ connection not closing

This pull request fixes issue #157

Good day, any chance we can get this approved? Let me know if you need more information.

Any idea when this is being merged?

Added comment to associate issue #157. Awaiting response.

Please see comment in #157. I still think this is a valid pull request

Any word on this issue?

Reopening the pull request so it stays visible. I had planned to get the issue reproduced, but haven't gotten much time out of other work.

Requesting to not spend time in editing the PR to restructured files unless I or someone verifies the issue and confirms here.

bump on closing this?


VSCode does not recognize tilde (~) for absolute file paths

VSCode Version: All
OS Version: OSX

Steps to Reproduce:

Press command-p to open a file
Paste in an absolute link to a file starting with tilde, as in ~/Desktop/some-file-that-exists.bmp

Expected result:
File path is found and openable
Actual result:
No file is found
Workaround:
Paste in the full expanded path, as in /Users/yourname/...
Reproduces without extensions: Yes

That would be nice 👍

Paste in the full expanded path, as in /Users/yourname/...

This doesn't work for me. Currently quickopen is only looking at the relative paths of files inside the open workspace. Do you expect to be able to open files outside the workspace with an absolute path? I think that makes sense.

Is anybody still working on this. If not, I would like to work on this, with some help.
Thank you.


abdlllll

abdll

@abdullahalo614 Thank you for the feedback, please leave additional comments below.

@abdullahalo614 Thank you for the feedback, please leave additional comments below.


Two T1w labels for some subjects

@NathanMolinier and I noticed that some subjects have duplicated T1w labels:
data-multi-subject/derivatives/labels/sub-amu02/anat$ ls -1 *T1w*labels*nii.gz
sub-amu02_T1w_RPI_r_labels-manual.nii.gz
sub-amu02_T1w_labels-disc-manual.nii.gz

T1w_RPI_r_labels-manual.nii.gz
These labels were created in the context of the spine-generic paper on the reoriented and resampled images (see lines here). These files contain only two labels at C3 and C5 mid-vertebral levels (because we used only two labels for the registration to the template), see lines here. These labels are available only for 31 subjects (those where the automatic labeling did not work).
T1w_labels-disc-manual.nii.gz
These labels were created manually by @NathanMolinier using the manual-correction.py script in the original images (i.e., no reorientation and resampling were applied). These files contain disc labels for all visible discs. These labels are available for all the subjects.

@NathanMolinier pointed out that it might be confusing to have two "labels" files.
Potential solutions:

clarify the difference between the label files in README.md
suggestion from @NathanMolinier: remove T1w_RPI_r_labels-manual.nii.gz files

Related to https://github.com/spine-generic/data-multi-subject/issues/95

It sounds like the two kinds of label files should be in two separate derivatives, each with their own README (which can just be your two paragraphs from this issue description!).

Yeah, this would make sense.

Maybe derivatives/vertebral-labels/ and derivatives/disc-labels/?

I initially thought that we could keep the T1w_RPI_r_labels-manual.nii.gz files under the current derivatives/labels/ folder to keep them together with other files created using the same analysis script process_data.sh and move the T1w_labels-disc-manual.nii.gz files created by @NathanMolinier to a new derivatives/disc-labels/ folder.
But the tricky thing is that Nathan just updated/corrected the T1w_labels-disc-manual.nii.gz files which already had been living beside T1w_RPI_r_labels-manual.nii.gz under derivatives/labels/ for a long time.

Sidenote: I will also upload soon spinal nerve rootlets segmentations created in the context of the model-spinal-rootlets project. I guess a good strategy would be to save them under a new folder like derivatives/spinal-rootlets-labels/.


:robot: Add vnc-viewer.vm

Automated PR from https://github.com/mandiant/VM-Packages/issues/514 :rocket:

Tested locally. Works. Very cool @Menn1s!


Protected Routes with Preact Router

Hey @developit,
I'm running into some issues trying to implement protected routes. I know react-router has the onEnter prop which helps implement protected routes basically admin pages, etc. How would one implemented this with preact-router.
This is my current approach
// Excerpt from Root Container
render (props) {
  return (
    <Router>
      <Home path='/' user={props.user}/>
      <Contact path='/contact' />
      <ProfileContainer path='/profile' />
      <LoginContainer path='/signin' />
      <PageError type='404' default />
    </Router>
  )
}

Then inside LoginContainer I'm checking if the session is valid, but componentWillMount is not being triggered.
...
componentWillMount () {
  if (isLoggedIn) {
    route('/profile')
  }
}

render (props) {
...

Not sure if this is the right approach. Any pointers will be greatly appreciated. Thanks

Hi @nishtacular - you're exactly right, just there's currently a tiny bug in preact-router for this exact use-case.  For now, please wrap your call to route() in a setTimeout:
...
componentWillMount () {
  if (isLoggedIn) {
    setTimeout( () => route('/profile') );
  }
}

render (props) {
...

If you want to avoid the few millisecond flash of your view, perform the same isLoggedIn check in render().
Hopefully I'll land a fix for this soon!

If you don't mind, I'm going to close this out as a duplicate since we're already tracking the same fix in #48. Cheers!


Locale priority issue

Suppose that

There is an app which supports only two locales, de_DE and en_US.
I have a device whose default locale has been set to ko_KR.

When I run this app on this device, the app's locale automatically falls back to de_DE, because ko_KR is not supported by the app and de_DE comes first in the engine's preferred locale list (as Tizen's i18n module resolves available locales alphabetically).

Should the engine resolve en_US first in this situation, just because it's more "natural" for general users?
Is there a way to list available locales in an order of preference?
How do other platforms or native/.NET apps deal with this situation?

Should the engine resolve en_US first in this situation, just because it's more "natural" for general users?

I like this solution. Because there is no priority of locales except for the locale that is set in tizen.
It is not strange that  we choose en first.

I'll prepare a patch for this issue. I think we should only pass ko_KR to the engine but not the whole list of 730 languages.

I'll prepare a patch for this issue. I think we should only pass ko_KR to the engine but not the whole list of 730 languages.

I'm not sure.. but I think it's a good solution. :+1:

https://flutter.dev/docs/development/accessibility-and-localization/internationalization
Internationalized apps can specify their supported languages using the supportedLocales parameter, and usually en (English) comes first in the list. Thus the solution will work exactly as you expect.


Avoid duplicate proposition in completion

This is a proposition to avoid having duplicate entries in completion menu.
For example, on my distribution, /bin is a symlink to /usr/bin adn both are in PATH.
So every entry in /usr/bin appear twice.

yeah it works, but I think it should use g_strcmp0 instead
gmrun should not add (process) duplicate directories. I'll see what I can do to make it recognize symlinks and duplicate dirs, the bug is easy to reproduce with something like this
# export PATH=/bin:/bin:/bin:${PATH}
gmrun


Pipelines: Update SDK references to point to the generated docs on Read The Docs

We now have auto-generated SDK ref docs on Read The Docs:
https://kubeflow-pipelines.readthedocs.io/en/latest/
We should search for all references in the pages on kubeflow.org that point to the GitHub repo for the SDK, and point to the relevant Read The Docs link instead.

I've marked this one for tackling during the doc sprint. It's a good one for a tech writer to tackle.

@sarahmaddox it looks this has been taken care of in some pull requests like https://github.com/kubeflow/website/pull/770/files. I did a search of the docs repo and couldn't find any other references of the SDK that pointed to Github. Let me know if I'm mistaken.

There are still some left. I haven't done an exhaustive search, but this search and this search pick up some occurrences (tho the later search contains non-relevant hits too). There may be more.

@sarahmaddox I was trying to help with this but I wasn't quite clear on the mapping. For instance, the first result from https://github.com/kubeflow/website/search?q="github.com%2Fkubeflow%2Fpipelines%2F"&unscoped_q="github.com%2Fkubeflow%2Fpipelines%2F", is content/docs/pipelines/sdk/reusable-components.md. Would I just replace the link for reusable components with https://kubeflow-pipelines.readthedocs.io/en/latest/source/kfp.components.html ? And what would I replace Cloud ML Engine model training with -- I couldn't find an equivalent link on https://kubeflow-pipelines.readthedocs.io.

/area docs
/priority p2


how to use with non-AWS s3 providers?

Many object storage services implement the S3 protocol without actually being AWS S3. For example, Wasabi and Open Storage Network (OSN). For these services, you define a custom endpoint URL for S3.
I would like to try cloud-files with OSN. For the AWS CLI, I would use this configuration
[plugins]
endpoint = awscli_plugin_endpoint

[profile osn]
aws_access_key_id=<key>
aws_secret_access_key=<secret>
s3 =
    endpoint_url = https://ncsa.osn.xsede.org
s3api =
    endpoint_url = https://ncsa.osn.xsede.org

However, I'm having trouble figuring out how to make this work. I read the wiki and looked at the code, but I couldn't figure it out. It is supported?
Thanks a lot for your help and for providing this useful package.

Hey Ryan! Glad you're finding this useful.
We use a kind of non-standard way of doing this, but I think it makes a lot of sense.
cf = CloudFiles("s3://https://ncsa.osn.xsede.org/BUCKET")

This functionality isn't super battle tested, so please report any issues or any apparent design flaws.

Awesome, will give it a try.

The thing that immediately occurs to me is that there isn't a great way to set a per-host secrets file. I think it will probably pick up your default aws-secret.json though.


Support for Clang 3.8 and above

These changes were necessary to get Chimera to build against Clang 4.0.0 on macOS. I believe this should: (1) not break backwards compatibility with Clang 3.6 and (2) should add support for the intermediate versions (i.e. 3.7, 3.8, and 3.9).
This may require some back-and-forth with Travis to make sure that it works on all those versions.

I tested this locally with brew install llvm, so I will merge this as it is. I'll address any issues that #125 uncovers in that pull request.


Rewrite netmask_vx function.

Excuse me, this is a little improvement.

I'm work on openSUSE and test it on Win8, cargo/rust not check  code for other platform, it is terrible..


⚠ SkipTheCommericals has degraded performance

In 9611d4f, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 1493 ms

Resolved: SkipTheCommericals performance has improved in 9769243.


Use an unsigned pointer compare, as the highest bit may sometimes be set.

This fixes intermittent connection issues on 32-bit Linux. Also related
to issues #2557 and #2600.

Can one of the admins verify this patch?

Test this please
On Tue, Aug 4, 2015, 4:22 AM gRPC Jenkins<EMAIL_ADDRESS>wrote:

Can one of the admins verify this patch?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2782#issuecomment-127568956.

Nice catch!
On Tue, Aug 4, 2015, 6:26 AM Craig Tiller<EMAIL_ADDRESS>wrote:

Test this please
On Tue, Aug 4, 2015, 4:22 AM gRPC Jenkins<EMAIL_ADDRESS>wrote:

Can one of the admins verify this patch?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2782#issuecomment-127568956.

This is ok to test.


Fix and improve TemporariesGraph

@mloubout : this should fix your issue in time-free-sparse. Pls let me know

Looks like it does yes, thanks.

OK, merging...


Input Decorator overflows the parent widget vertically

Steps to Reproduce

Run https://dartpad.dev/?id=60403a776f027d75ccd29aa2421342b7

Expected results:
The InputDecorator in red should be inside the parent widget without any overflow.
Actual results:
On web (screenshot) we can see on the top and bottom a small overflow. On android, this is slightly different but still buggy.

I have not find a workaround yet. Might be a similar issue with another approach https://github.com/flutter/flutter/issues/82709.

Hi @bsolca, Thanks for filing the issue. I am able to reproduce the issue on Desktop and it renders fine on mobile platforms (ios and Android). This is reproducible on latest stable and the master channel.

Desktop ❌
Web ❌

Android  ✅
IOS ✅

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 3.0.5, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.0.5 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f1875d570e (5 days ago), 2022-07-13 11:24:16 -0700
    • Engine revision e85ea0e79c
    • Dart version 2.17.6
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)              • chrome        • web-javascript • Google Chrome 103.0.5060.114

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.2009, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.1.0-0.0.pre.2009 on channel master at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9d96c7b8be (2 days ago), 2022-08-01 00:39:06 -0400
    • Engine revision cf0db3e546
    • Dart version 2.19.0 (build 2.19.0-49.0.dev)
    • DevTools version 2.16.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.69.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • C217DCBE-806E-4BC7-A952-61E4A647A7DA • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.4 21F79
      darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome
      104.0.5112.79

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Android
IOS
MacOs
Web

✅
✅
❌
❌

✅ : No Issue ❌: Issue reproduced

Hi @maheshmnj, thank you for your feedback. On Android and iOS this is less obvious but I made a new example to see and compare it better.
Comparing code with a normal Container:
https://dartpad.dev/?id=3a087243d1ccac042ee2e3eb6181b391
Tested on android (Nexus 7 API 30 and Pixel C API 30) and iOS (iPhone SE).

Android
iOS

Guessing this might be non-platform-specific but dependent on desktop-sized views. (Desktop triage)

This looks like it may be the same issue as https://github.com/flutter/flutter/issues/82709.
/cc @hangyujin I'll leave you to dedupe (or not). (Desktop triage)

Hi, I would like to solve this issue. Could you kindly assign this to me.

Hi @bsolca
A workaround If you need: Set visualDensity: VisualDensity.standard in ThemeData will solve the overflow problem.
The issue is caused because:
The Child property in InputDecorator is Typically an inputText and it uses densityOffset to adjust size.

Hello,
Good day to you. Sorry for the inconveniences. I was unable to solve the
issue as my team members and I were engaged in internal examinations that
were being conducted.
Could you kindly reassign the issue, we will get back to resolving it
as soon as possible.
Thanks and Regards,
Aakansha Ramesh
On Wed, Aug 17, 2022 at 9:44 PM hangyu @.***> wrote:

Assigned #108813 https://github.com/flutter/flutter/issues/108813 to
@aakansharamesh42 https://github.com/aakansharamesh42.
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/108813#event-7207464974, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQI33JDQVST3KWNYLZHAXLTVZUFU5ANCNFSM55LIID4Q
.
You are receiving this because you were assigned.Message ID:
@.***>

Hello @bsolca
Could you kindly reassign this issue to me.

Hello @bsolca Could you kindly reassign this issue to me.

I'm not sure I have the right for it.

Issues can only be reassigned by someone who's a member of the Flutter GitHub organisation.
It's currently assigned to @hangyujin on the Flutter team; they can confirm whether or not they plan to work on this and reassign if that makes sense.

Is there an update on the case assignment?

@aakansharamesh42 No one is assigned now, so if you still want to fix this, it's all yours 😁


Add dryRun option to goreleaser workflow

Having the workflow do a dryRun on any PR that modifies the workflow file would allow us to test those changes (such as renovate updates) automatically and enable automerge on them

Thank you!

@budimanjojo I think this should be as simple as adding the 'snapshot' flag like this:

https://github.com/mirceanton/reusable-workflows/blob/v1.0.0/.github/workflows/go-release.yaml#L55

You can see an example run of this here:

https://github.com/mirceanton/kube-switcher/actions/runs/10752026739/job/29819896577

What do you think?

Go ahead, I don't see there will be any problem having it. Thank you!


added lucy pet store ui

Description
I Created a ui for a pet store
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manual testing

Checklist:

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

please add screenshots

You need to add atleast 3-4 pages to be considered as proper ui.


Upgrade angular project to v6

What the program do ?
Hello World!
In what programming language it is written?
Typescript / Angular

This pull request exeeds the max additions limit. Please fix it and reopen


[nrf noup] fix: action: docs: fix cache and gh runner

squash! [nrf noup] action: docs: set checkout folder name to zephyr
Fixes used cache directory
Signed-off-by: Maciej Perkowski<EMAIL_ADDRESS>

N/A


use S3 bucket as the targets repository

This PR adds the S3 bucket as the targets' repository. It also specifies the default format for the targets as "rds" and the credentials profile as dev. The dev profile is what is produced (at least for me) when I use saml2aws to generate temporary AWS credentials.
This PR supersedes #119
closes #84 ; closes #152 ; closes #153; closes #154

With the old version of targets I read that the _targets/meta file should be committed in the git repo so that the S3 data version would be git tracked. That way, switching to a previous commit would pull the data for that commit. I also read that the targets not tracked in S3 should be git committed locally for the same reason. Is this handled differently in the new targets version?
I'm wondering what will happen if I run this pipeline. My local copy of the repo had some targets built, but with the previous version of targets. The previous targets version did not have the repository column in the meta file, so I got an error with tar_make. I decided to delete the _targets folder because the cause of the problem is clear. If I now try to run the repo, will I overwrite (create a new version) of the targets in our S3 bucket?

Thanks, Jeff! After the commit of the _targets/meta/meta file, many targets are skipped for me because they are already on S3, so that's great! I think the only new target builds are the ones specified as 'local', which makes sense because they don't exist in my local directories. I'm not sure if targets that depend on locally built targets are also getting rebuilt. That would be good to test.
The pipeline also rebuilt the first target I tried to build because I had not yet set up the AWS credentials and that gave an error message for that target (error message changed the meta file, so that target was triggered to rebuild). If that happens on a target that downloads data, then this method would not ensure the same data are used from one run to the next.
Notes
It is ~2x faster to run the pipeline off VPN for downloads. I had download targets time out when on VPN and they downloaded fine off of VPN. I also saw some S3 timeouts when on VPN. Messages like: could not check target p1_FORESCE_reclass_table. Timeout was reached: [drb-inland-salinity.s3.amazonaws.com] Connection timed out after 60000 milliseconds.
I needed to increase the AWS session duration from the default of 1 hr to finish all of the downloads in one run. I think using 4 hrs will work:
saml2aws configure --session-duration 14400
Questions:
Did you build all of the targets before? I think the bucket had less than 1000 items in it before I ran the pipeline (when it has more than 1000, the contents can't be sorted by name or date, and I was able to sort before running the pipeline).
Should I commit the updated targets/meta file so that it matches what is in the bucket?

Also noting some unexpected behavior for file targets. I noticed after I did a git diff that a file in 1_fetch/in and a log file in 3_visualize/log were deleted. These are both stored on S3, so I guess the locally stored files were deleted by running the pipeline. When I used tar_load(<target name>), that caused the csv files to appear in my local files. That was unexpected to me because I thought that file targets only save the file path to S3, but it looks like it also saves the file itself.

Should I commit the updated targets/meta file so that it matches what is in the bucket?

@jsadler2: Following up on this question, it would be interesting to know what happens for you now that some targets are newer on S3 than you have locally (they're newer because I built them when I ran the pipeline). Does targets pull the newer version on S3 or keep using the version you have locally?

We also have this question from our last meeting "Does switching from ‘local’ to ‘aws’ push locally built targets to aws? Or does it rebuild them?" We discussed using tar_cue to not rebuild when the repository source changes, but this may be a different problem. We would want the targets that are already built (e.g., during a PR) to be pushed from local to S3. Maybe using tar_cue = 'repository' would allow this to happen? Is this a good PR to figure out what happens when we switch the repository source, or should I open a new issue to investigate this?

@jds485  - I think this is ready to go now.


You have a paper wallet?

You have a paper wallet?
To import your paper wallet into the executable wallet, please do like so:

open .exe wallet.
Unzip the files and open the corresponding QT wallet for your computer's operating system (Windows, Apple or Linux)
Next click Window -> Console
enter: importprivkey your_private_key

This should import your wallet.
We are currently developing a user friendly wallet that will support the SCHO coin and eventually the Stable SCHO coin that is also in development.
Hope this helps. Let me know if this worked.
Cheers,

From: erichtimm0427<EMAIL_ADDRESS>Sent: Monday, February 1, 2021 11:12 AM
To: scholarshipcoin/scholarshipcoin<EMAIL_ADDRESS>Cc: Nicholas Dorion<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [scholarshipcoin/scholarshipcoin] isue whit chain (#1)
[image]https://user-images.githubusercontent.com/47291087/106484969-20919200-647e-11eb-8c92-1813078fd5fb.png
My payments are showing that they were payed out to my on the explorer but I have not received anything in my wallet
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/scholarshipcoin/scholarshipcoin/issues/1#issuecomment-770970795, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASRXNA2SSQEGGNPKTEOYIGTS43HGNANCNFSM4WT4RCLQ.
Originally posted by @scholarshipcoin in https://github.com/scholarshipcoin/scholarshipcoin/issues/1#issuecomment-770980104

This is for my Windows wallet not the paper wallet

What happens when you load the URI? scholarship:wallet address

From: erichtimm0427<EMAIL_ADDRESS>Sent: Monday, February 1, 2021 11:45 AM
To: scholarshipcoin/scholarshipcoin<EMAIL_ADDRESS>Cc: Nicholas Dorion<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [scholarshipcoin/scholarshipcoin] You have a paper wallet? (#3)
This is for my Windows wallet not the paper wallet
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/scholarshipcoin/scholarshipcoin/issues/3#issuecomment-770993314, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASRXNA4XTBOCSXDY5A2QNA3S43LBZANCNFSM4W5DL5TQ.

Still not working, it says requires a backup

I don't understand why I need to do all this for this wallet. I think this is a sign for me to cut my loses and go support a coin that has things more together. Good luck to everyone, but I am moving on

Oh you can do that no problem. See ya.
Get Outlook for Androidhttps://aka.ms/ghei36

From: erichtimm0427<EMAIL_ADDRESS>Sent: Monday, February 1, 2021 12:46:35 PM
To: scholarshipcoin/scholarshipcoin<EMAIL_ADDRESS>Cc: Nicholas Dorion<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [scholarshipcoin/scholarshipcoin] You have a paper wallet? (#3)
I don't understand why I need to do all this for this wallet. I think this is a sign for me to cut my loses and go support a coin that has things more together. Good luck to everyone, but I am moving on
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/scholarshipcoin/scholarshipcoin/issues/3#issuecomment-771034060, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASRXNA53MM2BIRJAN46LZZTS43SHXANCNFSM4W5DL5TQ.

Closing the issue since everything works now with the official mainnet release
Official paper wallet is at: https://paperwallet.scholarshipcoin.org