RISC-V - Kendryte K210 Support

Since the RISC-V platform is a rising star, support for chips available in the real world are important.
One of the available chips is the Kendryte K210 it is quite powerful for its price/size and even has an AI unit integrated. There are also modules already available which integrate the K210 on a module which can be handled more easily (e.g. https://www.seeedstudio.com/Sipeed-MAIX-I-module-WiFi-version-1st-RISC-V-64-AI-Module-K210-inside-p-3206.html).
The good thing is there already exists an initial port to FreeRTOS available at https://github.com/kendryte/kendryte-freertos-sdk
But I get the feeling the port is not complete and I think it would be a good choice to officially add this platform here to Amazon FreeRTOS.
Anyone interested in working together on this?
Preferable someone who has already experience with porting platforms to FreeRTOS?
I already got a bunch of the modules and kits available on the market with and K210 to try things out and test stuff (e.g. https://www.seeedstudio.com/Sipeed-Maixduino-Kit-for-RISC-V-AI-IoT-p-4047.html).

Normally, the boards that end up in amazon-freertos are qualified under the AWS Partner Device Catalog. However, if you'd like to implement and share a port for FreeRTOS, you are always welcome to submit a pull request under the FreeRTOS/FreeRTOS repository.

@yourslab Is a complete port necessary to be accepted or is a basic version enough to get started, and then add modules step by step? So the procedure would be to follow https://github.com/awsdocs/aws-freertos-docs/blob/master/doc_source/portingguide/index.md correct?

A basic port should be enough so that it ends up in https://github.com/FreeRTOS/FreeRTOS/tree/master/FreeRTOS/Demo
The porting guide you sent me is for vendors to qualify their boards with Amazon.

For the basic kernel port, you can follow the guide here:
https://www.freertos.org/FreeRTOS-porting-guide.html

The port you linked is for the standard FreeRTOS tough. This was already done (at least partially) in  https://github.com/kendryte/kendryte-freertos-sdk I need a port to the Amazon FreeRTOS variant.
So do I need to get the already existing port into the standard FreeRTOS port first or can I just focus on the Amazon FreeRTOS port?

Yes, you cannot have the Amazon FreeRTOS port without doing the standard port first. An Amazon FreeRTOS port is normally done by the vendor and will require a lot more work and testing than the standard port.

Also keep in mind that the work required for making a standard port is a subset of the work required for making an Amazon FreeRTOS port

Yes, correct I had a deeper look into the standard FreeRTOS porting guide and the existing K210 FreeRTOS SDK after our conversation here and noticed it myself that the standard FreeRTOS port from FreeRTOS/FreeRTOS-Kernel is linked to from Amazon FreeRTOS aws/amazon-freertos/freertos_kernel.
So the next steps are:

getting the existing K210 FreeRTOS SDK implementation
moving all the platform depended files heap_4.c, port.c and portmacro.h to there correct place
`FreeRTOS/FreeRTOS-Kernel/FreeRTOS-Kernel/portable/GCC/platform_name
check if there are impacts because of different FreeRTOS versions used in the K210 FreeRTOS SDK and the current master branch
implement the basic example

Am I correct so far?
When I looked into this a few questions came up:

The files in the K210 FreeRTOS SDK implementation use the Apache License, Version 2.0. Is this an issue as the FreeRTOS-Kernel repository uses the MIT License? I think not, since both are permissive licenses and work together so if it is not a problem to keep the original copyright information in the files this shouldn't be a problem. Am I correct on this?
Normally I would use RISC-V_K210 or just K210 (are there any preferences on this?) for platform_name but I noticed there is already a RISC-V directory which hosts the common part of "RISC-V port is split between the the code that is common across all currently supported RISC-V chips". But this generates a few questions.
2a.  So I presume this directory was once called RISC-V-RV32 and the documentation just didn't get updated!? Which brings up the next question.
2b. If the directory was once called RISC-V-RV32 is the code in it still just for 32-bit platforms? A quick look into FreeRTOS-Kernel/portable/GCC/RISC-V/portASM.S revealed that there are references to 64-bit platforms (__riscv_xlen == 64). So from my understanding this should be OK, correct? But then again a FreeRTOS-Kernel/portable/GCC/RISC-V/chip_specific_extensions/RV64I_CLINT_no_extensions/freertos_risc_v_chip_specific_extensions.h or something more special for the K210 (I need to check this out.) is needed, correct?

Sorry the list got long, but there are a bunch of different things to look at and I think it is better to discuss this prior to porting, and getting it right the first time than having a discussion afterwards in the code review when submitting the pull request. ;-)

The next steps you provided look to be in the right direction. It is likely though that changes need to be made to the existing port you linked me since it is using a much older version of the kernel.
I also personally don't think that the Apache License will be a problem. However, you had other great questions that will require more feedback from the kernel team. I will reach out to you again once we have clear answers to the points you brought up.

THX, great!
Yes, these where the possible needed modifications I ment with "check if there are impacts because of different FreeRTOS versions used in the K210 FreeRTOS SDK and the current master branch" any particular major things that come into your mind since you know the project much better than me? Or just start out with a diff and look where it goes? ;-)

I would suggest taking a look at the changelog here from V10.0.1 onwards:
https://www.freertos.org/History.txt
For example, you will see that in V10.2.1, the RISC-V port now automatically switches between 32-bit and 64-bit cores. You probably won't have to make any major changes but just have to keep it up to speed with the existing RISC-V ports.
One thing you will have to do is implement 'ParTest.c`. I noticed that a lot of the drivers (including GPIO) were ported from C to CPP in the Kendryte FreeRTOS SDK:
https://github.com/kendryte/kendryte-freertos-sdk/commit/bba479fb45603d9344c73fb588506a683500ff80
I'm not quite sure why this was done. If you take a look at the standalone SDK, the drivers are still written in C:
https://github.com/kendryte/kendryte-standalone-sdk/tree/develop/lib/drivers
For now, I believe we only allow ports that are written in C. It would be interesting to know why Kendryte decided to make the switch to CPP in the deprecated FreeRTOS SDK.

Also, I think you will find more people interested to help you with porting this board in the FreeRTOS forums
https://forums.freertos.org

I'll close this now and hope to hear more about it in the FreeRTOS forums.


Host it on a CDN

It would be great to have this hosted on a CDN. I suggest both CDNJS and JsDeliver:

https://github.com/cdnjs/cdnjs#adding-a-new-or-updating-an-existing-library
https://github.com/jsdelivr/jsdelivr#how-to-submit-or-update-projects

We need to send PRs to both CDN repos as per their requirements...
Cheers

:+1:

@SiamKreative, it is hosted on cdnjs. https://cdnjs.com/libraries/sanitize.css
And I’ve pushed an update for the current 3.1.1 branch. https://github.com/cdnjs/cdnjs/pull/6894


Multiple versions of nixpkgs

Currently we use multiple versions of nixpkgs. There are some issues that prevents us from using only the newest nixpkgs.
https://github.com/supabase/pg_net/blob/9d3f5be9b90663fb1a6ba92df61698236e399363/shell.nix#L4-L18
Tasks

[x] newest nixpkgs is only python3

many tests give the sqlalchemy.exc.ArgumentError: Textual SQL expression error
cleared on https://github.com/supabase/pg_net/pull/107

[ ] pathod command no longer exists https://github.com/mitmproxy/mitmproxy/issues/4273#issuecomment-1724490887. Ideally the maintainers reply with a way forward using mitmproxy.
[x] newest openresty doesn't have a prefix option: https://github.com/supabase/pg_net/blob/9d3f5be9b90663fb1a6ba92df61698236e399363/shell.nix#L2-L3

This is not a big problem since we can keep using multiple versions. It only adds some extra time for building/testing - not too much time (only download time, not compile time) because https://cache.nixos.org/  is already populated.

pathod command no longer exists https://github.com/mitmproxy/mitmproxy/issues/4273#issuecomment-1724490887. Ideally the maintainers reply with a way forward using mitmproxy.

For the above the way forward is to have the same functionality on https://github.com/steve-chavez/ngx_pathological, then we can just use Nginx for the tests.


ASL | Transfer Learning and Fine-tuning for Sign Language

Is your feature request related to a problem? Please describe.
Effective communication with the deaf community is crucial for inclusivity, but traditional methods often present barriers.  This project aims to bridge this communication gap by developing a robust American Sign Language (ASL) recognition system using deep learning. The challenge lies in accurately classifying diverse ASL expressions from images to enable real-time translation and facilitate seamless communication.

Describe the solution you'd like
This project demonstrates the application of transfer learning to classify American Sign Language (ASL) expressions. Two popular CNN architectures, InceptionV3 and ResNet50, are employed as base models with pre-trained weights from ImageNet.  The models are fine-tuned on an ASL dataset, leveraging their learned feature representations for improved accuracy.  The training process includes data augmentation and employs the Adam optimizer with a categorical cross-entropy loss function. The performance of both models is evaluated and compared, showcasing the effectiveness of transfer learning for ASL classification and its potential for communication support applications.

**Kindly, Assign me this Issue Under:

Gssoc🌸
hacktoberfest☘
Level-3✨

Additional context

@Neilblaze @SaiNivedh26 Kindly Assign me this Issue under Level - 3 , Gssoc-ext , hacktoberfest

@Varunshiyam wait till I told you to do it
And don't raise already existed issues it's already done btw.


[14.0] ISPN-15014 CVE fix netty and jackson upgrade

https://issues.redhat.com/browse/ISPN-15014
https://issues.redhat.com/browse/ISPN-15013

Thanks @pminz


Adde Hanif's changes

Added the Koleo loss
Added the weighted sup t con
Switched Batchnorm from layernorm

thanks! runs with following changes: https://github.com/tbenst/silent_speech/compare/f88716...tbenst:silent_speech:tb/hanif#diff-afab5b47f3c9255cc34937f181df1eefac20a9e304f1c8756a37666cf1c8d1d9L862


Some much needed spring cleaning

Remove the .idea file from the vc tracked files, and make sure that the project builds, compiles and runs a simple JavaFX application.

I had already removed the .idea directory whilst addressing the #4 issue.


Added welcome page and fixes minor tutorial issues

feat: added a welcome page to the docs, as well as helpful navigation. #151 ninjamike Review
fix: fixed incorrect deceleration of rendertargets as drawbuffer. #339  jbritain Review
Other minor spelling fixes and minor changes to formatting of the home and welcome pages

Thank you for all your feedback. I will work on rewriting the DH shaders thing soon.

Changed DH link to the uniforms overview (which makes more sense)


Add owner flag

Proposed Changes

Add a owner flag

Types of Changes

Command line

Testing
How to test:
1 - You can create a backport using the new flag -o
./backport -r k3s -o k3s-io -b 'release-1.21,release-1.22' -i 123

Linked Issues
User-Facing Change
Further Comments
I'm sending this PR because when I was trying to do backports this morning I was receiving a 404 when requesting the repo and it was missing the repo owner

@briandowns I tried using this command here
./backport-linux-amd64 -r k3s-io/k3s -i 8033 -r 'release-1.25
and I received
GET https://api.github.com/repos//k3s-io/k3s/issues/8033: 404 Not Found []
We could remove a / in the
func (s *IssuesService) Get(ctx context.Context, owner string, repo string, number int) (*Issue, *Response, error) {
	u := fmt.Sprintf("repos/%v/%v/issues/%d", owner, repo, number)
	req, err := s.client.NewRequest("GET", u, nil)
	if err != nil {
		return nil, nil, err
	}

	// TODO: remove custom Accept header when this API fully launch.
	req.Header.Set("Accept", mediaTypeReactionsPreview)

	issue := new(Issue)
	resp, err := s.client.Do(ctx, req, issue)
	if err != nil {
		return nil, resp, err
	}

	return issue, resp, nil
}

Removing the slash is preferred. Should be done in the lib and not the binary. I can do this today if you want.


feat: Update istio codebase

Ⅰ. Describe what this PR did
Update istio codebase to integrate changes from https://github.com/higress-group/istio/pull/16 .
Ⅱ. Does this pull request fix one issue?

related to https://github.com/alibaba/higress/issues/1478
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

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

Project coverage is 43.52%. Comparing base (ef31e09) to head (4ab818c).
Report is 183 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1485      +/-   ##
==========================================
+ Coverage   35.91%   43.52%   +7.61%
==========================================
  Files          69       76       +7
  Lines       11576    12320     +744
==========================================
+ Hits         4157     5362    +1205
+ Misses       7104     6622     -482
- Partials      315      336      +21

see 69 files with indirect coverage changes


Build script try to search mingw directory on MSVC toolchain

Operating system is Windows 10
The way you installed OpenCV: vcpkg
OpenCV version: last from vcpkg
Attach the full output of the following command from your project directory:

 cargo_metadata: [
        "cargo:rustc-link-search=native=C:/msys64/mingw64/lib",
        "cargo:rustc-link-lib=opencv_gapi",
        "cargo:rustc-link-lib=opencv_stitching",
        "cargo:rustc-link-lib=opencv_alphamat",
        "cargo:rustc-link-lib=opencv_aruco",
        "cargo:rustc-link-lib=opencv_bgsegm",
        "cargo:rustc-link-lib=opencv_ccalib",
        "cargo:rustc-link-lib=opencv_dnn_objdetect",
        "cargo:rustc-link-lib=opencv_dnn_superres",
        "cargo:rustc-link-lib=opencv_dpm",
        "cargo:rustc-link-lib=opencv_highgui",
        "cargo:rustc-link-lib=opencv_face",
        "cargo:rustc-link-lib=opencv_fuzzy",
        "cargo:rustc-link-lib=opencv_hdf",
        "cargo:rustc-link-lib=opencv_hfs",
        "cargo:rustc-link-lib=opencv_img_hash",
        "cargo:rustc-link-lib=opencv_intensity_transform",
        "cargo:rustc-link-lib=opencv_line_descriptor",
        "cargo:rustc-link-lib=opencv_ovis",
        "cargo:rustc-link-lib=opencv_quality",
        "cargo:rustc-link-lib=opencv_rapid",
        "cargo:rustc-link-lib=opencv_reg",
        "cargo:rustc-link-lib=opencv_rgbd",
        "cargo:rustc-link-lib=opencv_saliency",
        "cargo:rustc-link-lib=opencv_sfm",
        "cargo:rustc-link-lib=opencv_stereo",
        "cargo:rustc-link-lib=opencv_structured_light",
        "cargo:rustc-link-lib=opencv_phase_unwrapping",
        "cargo:rustc-link-lib=opencv_superres",
        "cargo:rustc-link-lib=opencv_optflow",
        "cargo:rustc-link-lib=opencv_surface_matching",
        "cargo:rustc-link-lib=opencv_tracking",
        "cargo:rustc-link-lib=opencv_datasets",
        "cargo:rustc-link-lib=opencv_text",
        "cargo:rustc-link-lib=opencv_dnn",
        "cargo:rustc-link-lib=opencv_plot",
        "cargo:rustc-link-lib=opencv_videostab",
        "cargo:rustc-link-lib=opencv_videoio",
        "cargo:rustc-link-lib=opencv_xfeatures2d",
        "cargo:rustc-link-lib=opencv_shape",
        "cargo:rustc-link-lib=opencv_ml",
        "cargo:rustc-link-lib=opencv_ximgproc",
        "cargo:rustc-link-lib=opencv_video",
        "cargo:rustc-link-lib=opencv_xobjdetect",
        "cargo:rustc-link-lib=opencv_objdetect",
        "cargo:rustc-link-lib=opencv_calib3d",
        "cargo:rustc-link-lib=opencv_imgcodecs",
        "cargo:rustc-link-lib=opencv_features2d",
        "cargo:rustc-link-lib=opencv_flann",
        "cargo:rustc-link-lib=opencv_xphoto",
        "cargo:rustc-link-lib=opencv_photo",
        "cargo:rustc-link-lib=opencv_imgproc",
        "cargo:rustc-link-lib=opencv_core",
    ],
}
=== Found OpenCV library version: 4.1.1 in headers located at: C:\vcpkg\installed\x64-windows\include

error occurred: Command "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.25.28610\\bin\\HostX64\\x64\\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "C:\\Users\\DuckerMan\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\opencv-0.36.0\\src_cpp" "-I" "C:\\vcpkg\\installed\\x64-windows\\include" "-I" "C:\\Users\\DuckerMan\\Desktop\\RUST\\opencv\\target\\debug\\build\\opencv-eb1d5fe6da326751\\out"
"-I" "." "-W4" "-std:c++latest" "-wd4996" "-wd5054" "-wd4190" "-EHsc" "-FoC:\\Users\\DuckerMan\\Desktop\\RUST\\opencv\\target\\debug\\build\\opencv-eb1d5fe6da326751\\out\\calib3d.o" "-c" "C:\\Users\\DuckerMan\\Desktop\\RUST\\opencv\\target\\debug\\build\\opencv-eb1d5fe6da326751\\out\\calib3d.cpp" with args "cl.exe" did not execute successfully (status code exit code: 2).

PS C:\Users\DuckerMan\Desktop\RUST\opencv>

Hi, unfortunately the output you provided is not sufficient to debug the issue, please attach the full build log as produced by the cargo -vv build after doing cargo clean.

Log

OPENCV_DIR                     C:\opencv\cv-rs\artifacts\vc15\install\opencv
What is OPENCV_DIR is supposed to be? Because I dont have opencv directory in C:\

That log is also not enough. I would need the full build log starting right after you issued the cargo build -vv command until it stopped with the error. One potential problem I already see though, are you building with feature buildtime-bindgen enabled? If not please enabled it for the crate before trying to build.

What is OPENCV_DIR is supposed to be? Because I dont have opencv directory in C:\

What is OPENCV_DIR in this context? An environment variable? If so the crate is not affected by this particular environment var so please clarify the question.

Another log without buildtime-bindgen

Ah, the crate does cmake library discovery first and that actually succeeds. So for it to pick up OpenCV from vcpkg add the following environment variable:
OPENCV_DISABLE_PROBES=cmake

And do build with buildtime-bindgen feature enabled, otherwise the build will fail.

Still error(another)
error occurred: Command "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.25.28610\\bin\\HostX64\\x64\\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "C:\\Users\\DuckerMan\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\opencv-0.38.0\\src_cpp" "-I" "C:\\vcpkg\\installed\\x64-windows\\include" "-I" "C:\\Users\\DuckerMan\\Desktop\\RUST\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out"

Can you please try with OPENCV_DISABLE_PROBES=cmake,pkg_config? pkg_config seems to also direct the build to mingw directories.

error: failed to run custom build command for `opencv v0.38.0`

Caused by:
  process didn't exit successfully: `C:\Users\DuckerMan\desktop\rust\opencv\target\debug\build\opencv-751ff83b900150e4\build-script-build` (exit code: 1)
--- stderr
=== Environment configuration:
===   OPENCV_HEADER_DIR = Some("C:\\vcpkg\\installed\\x64-windows\\include")
===   OPENCV_PACKAGE_NAME = None
===   OPENCV_PKGCONFIG_NAME = None
===   OPENCV_CMAKE_NAME = None
===   OPENCV_CMAKE_BIN = None
===   OPENCV_VCPKG_NAME = None
===   OPENCV_LINK_LIBS = None
===   OPENCV_LINK_PATHS = None
===   OPENCV_INCLUDE_PATHS = None
===   OPENCV_DISABLE_PROBES = Some("cmake,pkg_config")
===   OPENCV_CLANG_STDLIB_PATH = None
===   CMAKE_PREFIX_PATH = None
===   OpenCV_DIR = None
===   PKG_CONFIG_PATH = None
===   VCPKG_ROOT = None
=== Enabled features:
===   BINDING_GENERATOR
===   BUILDTIME_BINDGEN
===   CLANG
===   DEFAULT
===   OPENCV_4
=== Skipping probe pkg_config because of the environment configuration
=== Skipping probe cmake because of the environment configuration
=== Probing OpenCV library using vcpkg
=== OpenCV library configuration: Library {
    include_paths: [
        "C:\\vcpkg\\installed\\x64-windows\\include",
    ],
    version: "4.1.1",
    cargo_metadata: [
        "cargo:rustc-link-search=native=C:\\vcpkg\\installed\\x64-windows\\lib",
        "cargo:rustc-link-search=native=C:\\vcpkg\\installed\\x64-windows\\bin",
        "cargo:rustc-link-lib=opencv_aruco",
        "cargo:rustc-link-lib=opencv_bgsegm",
        "cargo:rustc-link-lib=opencv_bioinspired",
        "cargo:rustc-link-lib=opencv_calib3d",
        "cargo:rustc-link-lib=opencv_ccalib",
        "cargo:rustc-link-lib=opencv_core",
        "cargo:rustc-link-lib=opencv_datasets",
        "cargo:rustc-link-lib=opencv_dnn",
        "cargo:rustc-link-lib=opencv_dnn_objdetect",
        "cargo:rustc-link-lib=opencv_dpm",
        "cargo:rustc-link-lib=opencv_face",
        "cargo:rustc-link-lib=opencv_features2d",
        "cargo:rustc-link-lib=opencv_flann",
        "cargo:rustc-link-lib=opencv_fuzzy",
        "cargo:rustc-link-lib=opencv_hdf",
        "cargo:rustc-link-lib=opencv_hfs",
        "cargo:rustc-link-lib=opencv_highgui",
        "cargo:rustc-link-lib=opencv_img_hash",
        "cargo:rustc-link-lib=opencv_imgcodecs",
        "cargo:rustc-link-lib=opencv_imgproc",
        "cargo:rustc-link-lib=opencv_line_descriptor",
        "cargo:rustc-link-lib=opencv_ml",
        "cargo:rustc-link-lib=opencv_objdetect",
        "cargo:rustc-link-lib=opencv_optflow",
        "cargo:rustc-link-lib=opencv_phase_unwrapping",
        "cargo:rustc-link-lib=opencv_photo",
        "cargo:rustc-link-lib=opencv_plot",
        "cargo:rustc-link-lib=opencv_quality",
        "cargo:rustc-link-lib=opencv_reg",
        "cargo:rustc-link-lib=opencv_rgbd",
        "cargo:rustc-link-lib=opencv_saliency",
        "cargo:rustc-link-lib=opencv_shape",
        "cargo:rustc-link-lib=opencv_stereo",
        "cargo:rustc-link-lib=opencv_stitching",
        "cargo:rustc-link-lib=opencv_structured_light",
        "cargo:rustc-link-lib=opencv_superres",
        "cargo:rustc-link-lib=opencv_surface_matching",
        "cargo:rustc-link-lib=opencv_text",
        "cargo:rustc-link-lib=opencv_tracking",
        "cargo:rustc-link-lib=opencv_video",
        "cargo:rustc-link-lib=opencv_videoio",
        "cargo:rustc-link-lib=opencv_videostab",
        "cargo:rustc-link-lib=opencv_xfeatures2d",
        "cargo:rustc-link-lib=opencv_ximgproc",
        "cargo:rustc-link-lib=opencv_xobjdetect",
        "cargo:rustc-link-lib=opencv_xphoto",
        "cargo:rustc-link-lib=webp",
        "cargo:rustc-link-lib=webpdecoder",
        "cargo:rustc-link-lib=webpdemux",
        "cargo:rustc-link-lib=tiff",
        "cargo:rustc-link-lib=tiffxx",
        "cargo:rustc-link-lib=lzma",
        "cargo:rustc-link-lib=jpeg",
        "cargo:rustc-link-lib=turbojpeg",
        "cargo:rustc-link-lib=zlib",
        "cargo:rustc-link-lib=libpng16",
        "cargo:rustc-link-lib=hdf5",
        "cargo:rustc-link-lib=hdf5_hl",
        "cargo:rustc-link-lib=libhdf5",
        "cargo:rustc-link-lib=libhdf5_hl",
        "cargo:rustc-link-lib=libszip",
        "cargo:rustc-link-lib=szip",
        "cargo:rustc-link-lib=libprotobuf-lite",
        "cargo:rustc-link-lib=libprotobuf",
        "cargo:rustc-link-lib=libprotoc",
        "cargo:rustc-link-search=native=C:\\Users\\DuckerMan\\desktop\\rust\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out",
        "cargo:rustc-link-search=C:\\Users\\DuckerMan\\desktop\\rust\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out",
    ],
}
=== Found OpenCV library version: 4.1.1 in headers located at: C:\vcpkg\installed\x64-windows\include
=== Using OpenCV headers from: C:\vcpkg\installed\x64-windows\include\opencv2
=== Generating code in: C:\Users\DuckerMan\desktop\rust\opencv\target\debug\build\opencv-e72d2d0b2ff1bb06\out
=== Placing generated bindings into: C:\Users\DuckerMan\.cargo\registry\src\github.com-1ecc6299db9ec823\opencv-0.38.0\bindings\rust\opencv_4
=== Clang command line args: [
    "-isystemC:\\Program Files\\LLVM\\lib\\clang\\10.0.0\\include",
    "-isystemC:\\vcpkg\\installed\\x64-windows\\include",
    "-IC:\\vcpkg\\installed\\x64-windows\\include",
    "-IC:\\Users\\DuckerMan\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\opencv-0.38.0\\src_cpp",
    "-DOCVRS_PARSING_HEADERS",
    "-includeocvrs_resolve_types.hpp",
]

error occurred: Command "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.25.28610\\bin\\HostX64\\x64\\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "C:\\Users\\DuckerMan\\.cargo\\registry\\src\\github.com-1ecc6299db9ec823\\opencv-0.38.0\\src_cpp" "-I" "C:\\vcpkg\\installed\\x64-windows\\include" "-I" "C:\\Users\\DuckerMan\\desktop\\rust\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out" "-I" "." "-W4" "-std:c++latest" "-wd4996" "-wd5054" "-wd4190" "-EHsc" "-bigobj" "-FoC:\\Users\\DuckerMan\\desktop\\rust\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out\\core.o" "-c" "C:\\Users\\DuckerMan\\desktop\\rust\\opencv\\target\\debug\\build\\opencv-e72d2d0b2ff1bb06\\out\\core.cpp" with args "cl.exe" did not execute successfully (status code exit code: 2).

Now it doesnt try to search mingw but is doesn't compile

Can you please attach the full build log starting right after you issued cargo -vv build?

Have you had any success with that issue? Will you be able to share the log in case you haven’t?

Hi! I've fixed it.
Solution: Remove INCLUDE and LIB envs


Move Locale middleware into package

Q
A

Is bugfix?
✔/❌

New feature?
✔/❌

Breaks BC?
✔/❌

Fixed issues

[ ] Tests

This package already has many dependencies.
Suggest create separate package for Locale middleware. For example, yiisoft/yii-locale-middleware.

👍


Alternate Values for People

The author search does not correctly find the alternate name I need to find.
When I add an alternative value for a Chinese name, for example, it can be written with or without "-". eg Zhang, Dao-Chuan or Zhang, Daochuan.
I go to Alternative Values to add the name Daochuan instead of Dao-Chuan in the Alternative Spelling section.

And click SAVE

But then, for example, in the New Source task, when I type Zhang Daochuan in the Author search, it doesn't find anything.

If I search for just Daochuan, without typing the last name, it takes me to the person I'm looking for.

It doesn't associate it to the last name as it should.

I would need it to show me that this alternate spelling is for the same person. Here at OSF is an example of the information I get from searching for people in Species Files.

If you search for "Zhang, Da" in TW, you should get right result (same as in OSF example). If you search for "Daochuan, Za" - probably not. All search terms are treated as ordered. So the search assumes that Daochuan is the last name. Alternative searches are linked to Last name field only. I can check if the first name could be added to the search criteria, but the real chalenge is that more options you add, less precise results you get. Partial searches work for me best. The last name an first inicial or last name an both inicials works best for me.

do we index all these values? could there be one box to search any part of the string instead? (Note I'm trying to follow what is possible, what we know won't work). @mabecabrera thank you for this entry. We need to work on documentation that explains what to expect and what we know will not work.

Previous one was for the last name, This one is for the first name.

Radial annotator for Person is designed for adding alternative values (when you uniquify people, it is also done automatically).

@mabecabrera, did you try the alternative spellings? Did it work for you? Should the issue be closed?

Yes! @dimus! It works fine! Thank you! I didn't want to close the issue myself. I'll do it now! 👍


How to hide the midValue on yLabel

I had asked the question on stackoverflow,
but seems no one know the answer.
Defaults always have the maxValue , midValue(and Line) and the minValue on yLabe,
now I can use yLabels to set highest and lowest ,but the middle Line still here,
is there any method to hide the middle Line?
Thanks!

The answer provided on stack overflow is correct (and you marked it as well 🤔 - do you still some help @SuYungCheng ?

It's helpful, thanks!


Support the three/four/six-value syntax variants of

This PR adds support for the following syntax variants of  (see the docs):
#RGB        // The three-value syntax
#RGBA       // The four-value syntax
#RRGGBB     // The six-value syntax
#RRGGBBAA   // The eight-value syntax (we already support this)

It turned out that we have quite a few redundant lines of code around the color prop. I decided to address this problem in a different PR (to keep things clean): https://github.com/theatre-js/theatre/pull/201


quadratic_linear_attn implementation

I think you should put an epsilon in denominator of output of quadratic_linear_attn function to prevent NaN value when training HedgeHog MLP.
qk / (qk.sum(dim=-1, keepdim=True) +epsilon)

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@Kiet0712 if you could open up a pr that would be nice :)


Window doesn't get any inputs

Steps to reproduce:

Run mvn install in root folder
Open Intellij and choose the pom.xml file in root
Edit the pom.xml file to include the examples module
Resync IDE with maven
Right click on main method in SimpleShm.java and choose run application
Try to click, right click, drag.

What happens:

Nothing, clicks goes through the window to app below

What should happen:

Window should swallow the clicks? I should be able to resize the surface?

I'm running Fedora 22 which have Wayland 1.7 installed and I'm running a wayland session.

Fix pushed. Tested on Weston. Can you confirm it works on gnome wayland (I assume that's what you are using)?

Yes it works in gnome now :)


Suppress lint warning.

This patch is to suppress the lint warnings for missing density folder
and unused resources.
The exactly way is to add the ignore path to specified list, e.g.

but this way does not work all the time, I have tracked the command line,
python code and config xml, there is no difference.
Ignore all the warnings for missing density folder and unused resources
as a temporary solution.
BUG=XWALK-6276

LGTM, this seems better than introduces dependence with xwalk/app/android/...

Can you paste the build error you're getting with master? Since this is Chromium code I'd expect it to be working fine, otherwise it would have failed before in Chromium's own bots.

For IconMissingDensityFolder, the error is

FAILED: cd ../../xwalk; python ../build/android/gyp/lint.py "--lint-path=/home/whz/project/crosswalk/crosswalk2/src/third_party/android_tools/sdk//tools/lint" "--config-path=../build/android/lint/suppressions.xml" "--processed-config-path=../out/Release/xwalk_app_hello_world_apk/lint_config.xml" "--manifest-path=app/android/app_hello_world/AndroidManifest.xml" "--result-path=../out/Release/xwalk_app_hello_world_apk/lint_result.xml" "--resource-dir=app/android/app_hello_world/res" "--product-dir=../out/Release" "--src-dirs=app/android/app_hello_world/src" "--jar-path=../out/Release/lib.java/chromium_apk_xwalk_app_hello_world_apk.jar" --can-fail-build "--stamp=../out/Release/xwalk_app_hello_world_apk/lint.stamp" --enable
res Missing density variation folders in res: drawable-xxhdpi, drawable-xxxhdpi: IconMissingDensityFolder [warning]
Lint found 1 new issues.

For full explanation refer to out/Release/xwalk_app_hello_world_apk/lint_result.xml
Wanna suppress these issues?

Read comment in build/android/lint/suppressions.xml
Run "python build/android/lint/suppress.py out/Release/xwalk_app_hello_world_apk/lint_result.xml"

For UnusedResources, the error is

FAILED: cd ../../xwalk; python ../build/android/gyp/lint.py "--lint-path=/home/buildbot-slave/build-infrastructure/slave/crosswalk-android-x86/build/src/third_party/android_tools/sdk//tools/lint" "--config-path=../build/android/lint/suppressions.xml" "--processed-config-path=../out/Release/xwalk_app_hello_world_apk/lint_config.xml" "--manifest-path=app/android/app_hello_world/AndroidManifest.xml" "--result-path=../out/Release/xwalk_app_hello_world_apk/lint_result.xml" "--resource-dir=app/android/app_hello_world/res" "--product-dir=../out/Release" "--src-dirs=app/android/app_hello_world/src" "--jar-path=../out/Release/lib.java/chromium_apk_xwalk_app_hello_world_apk.jar" --can-fail-build "--stamp=../out/Release/xwalk_app_hello_world_apk/lint.stamp" --enable
res/values/strings.xml:10 The resource R.string.download_from_url appears to be unused: UnusedResources [warning]
Direct Download
~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:11 The resource R.string.download_from_store appears to be unused: UnusedResources [warning]
Install From Store
~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:12 The resource R.string.dialog_title_update_runtime_lib appears to be unused: UnusedResources [warning]
Update for Crosswalk Runtime Library is required
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:13 The resource R.string.dialog_message_update_runtime_lib appears to be unused: UnusedResources [warning]
Please update "Crosswalk Runtime Library" first.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:14 The resource R.string.dialog_title_update_runtime_lib_warning appears to be unused: UnusedResources [warning]
Update for Crosswalk Runtime Library is available
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:15 The resource R.string.dialog_message_update_runtime_lib_warning appears to be unused: UnusedResources [warning]
An update is recommended for "Crosswalk Runtime Library".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:16 The resource R.string.dialog_title_install_runtime_lib appears to be unused: UnusedResources [warning]
Crosswalk Runtime Library not found
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res/values/strings.xml:17 The resource R.string.dialog_message_install_runtime_lib appears to be unused: UnusedResources [warning]
Please install "Crosswalk Runtime Library" first.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
res Missing density variation folders in res: drawable-xxhdpi, drawable-xxxhdpi: IconMissingDensityFolder [warning]
Lint found 9 new issues.

For full explanation refer to out/Release/xwalk_app_hello_world_apk/lint_result.xml
Wanna suppress these issues?

Read comment in build/android/lint/suppressions.xml
Run "python build/android/lint/suppress.py out/Release/xwalk_app_hello_world_apk/lint_result.xml"


ENOTFOUND alpha.elm-lang.org

What worked
git clone https://github.com/avh4/elm-upgrade.git
npm install -g `pwd` # install `elm-upgrade` from local git repo, master branch
npm install -g elm-format@rc
cd path/to/my/elm/project
elm-upgrade

What didn't work
Instructions at https://github.com/avh4/elm-upgrade/tree/rc#how-to-use-it

npm install -g elm-format@rc  # Elm 0.19 alpha version of elm-format
npm install -g elm-upgrade@rc
cd path/to/my/elm/project
elm-upgrade

**NOT FOR SHARING.** Do not post about the alpha/rc version of elm-upgrade on reddit, twitter, HN, discourse, etc.
**NOT FOR SHARING.** Learn why here: <https://www.deconstructconf.com/2017/evan-czaplicki-on-storytelling>

{ RequestError: getaddrinfo ENOTFOUND alpha.elm-lang.org alpha.elm-lang.org:443
    at ClientRequest.req.once.err ($HOME/.nvm/versions/node/v8.11.2/lib/node_modules/elm-upgrade/node_modules/got/index.js:73:21)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  code: 'ENOTFOUND',
  message: 'getaddrinfo ENOTFOUND alpha.elm-lang.org alpha.elm-lang.org:443',
  host: 'alpha.elm-lang.org',
  hostname: 'alpha.elm-lang.org',
  method: 'GET',
  path: '/search.json' }
ERROR: Unable to connect to https://alpha.elm-lang.org.  Please try again later.

I suspect all can be fixed by updating npm?

The rc package server has been shut down now that Elm 0.19 has been release.  The 0.19 version of elm-upgrde hasn't been published yet, but I'm hoping to have it published in a few hours.


Az.Network module version

What version of Az.Network does the above script require?

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

ID: a9906cba-acc2-5978-1380-2b2f445a00da
Version Independent ID: a547cc17-92ce-e889-ed78-8fc294cca01b
Content: Migrate WAF policies for Azure Application Gateway
Content Source: articles/web-application-firewall/ag/migrate-policy.md
Service: web-application-firewall
GitHub Login: @vhorne
Microsoft Alias: ant

@jkeane Thanks for the feedback! We are currently investigating and will update you shortly.

Found it, v3.1.0 of Az (v2.1.0 of Az.Network)

@jkeane , Glad that you found the solution and thanks for sharing it in the community platform.
We are closing this issue for now.If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Issue while running OpenVino application on network edge openness 20.06

HI @amr-mokhtar
I have deployed openvino application on openness network edge and client-sim is running on a separate machine.
client-sim sending the traffic to the openvino consumer application but window pop-up is not coming up (it was came for 1 second and then lost).
please refer screenshot for reference
note that I have x11 window terminal but due to blur screen, i am sending the container logs from terminal.

consumer application logs:

HI @amr-mokhtar
application onboarding is successfully working on network-edge openness environment.
pop-up window is coming up and working fine.
thanks for all your support !!!

i am closing this issue.
@amr-mokhtar

I found display variable and xterm issue and resolved so, closing this issue.


[Refactor] Move RPCServer behavior into RPCServer.swift. Localising to 1 file

@hboon can you please wait for https://github.com/AlphaWallet/alpha-wallet-ios/pull/5246 first

Made PR a draft just in case.

Force-pushed after rebase master


Multiplayer sync - Player Actions

Apologies there are so many files changed!  The majority of that was because I deleted the Photon demos.  All the changes related to multiplayer sync can be seen under the single commit, https://github.com/PubNubDevelopers/unity-multiplayer-shooter/pull/1/commits/92c301c36b6a058aa71e0daae5e776363dc57fa8
I removed the Grenades as we discussed.  Rather than remove them entirely from the application, I just removed them from the UI as well as the critical areas of code - this was so we could easily add them back later if we wanted to.

Thanks @olivercarson-pubnub , I won't merge this request until we can discuss.  I also create my own PubNub instance at https://github.com/PubNubDevelopers/unity-multiplayer-shooter/commit/92c301c36b6a058aa71e0daae5e776363dc57fa8#diff-22ccb17a2db96e3479f458f599dd684780f8f0edd5622ee341edc9d17fc634c4R158 which I use for all my player actions logic and data


EU868 TxPower

This comment is a bit confusing to me when read with the one above.
Most of the RSSI's in the tests are changing to 30.
These two are the outliers, and I don't understand from the comments why they're both changing to 20 under opposite circumstances.
Above comment from L315
%% RSSI act as power here we are and based on UPLINK RSSI > -80 we should power downlink at 20

vs. this comment L457
%% RSSI act as power here we are and based on UPLINK RSSI < -80 we should power downlink at 20

Originally posted by @michaeldjeffrey in https://github.com/helium/router/pull/710#discussion_r865475100
We need to revisit the EU868 maximum tx_power setting in the LoRaWAN library.  Historically it has been set to 20, but the maximum allowed is actually 16.  Also double-check other Region maximums in the new Regional spec.
Related Issues:
https://www.etsi.org/deliver/etsi_en/300200_300299/30022002/03.02.01_60/en_30022002v030201p.pdf
https://github.com/helium/router/pull/304
https://github.com/helium/router/pull/355
We noticed while reviewing that this unit test sets packet Region to EU868, but Gateway processing packet is US915 causing confusion.

Fixed in LoRaWAN library
https://github.com/helium/erlang-lorawan/pull/13/commits/fa7b6fb30888e358671d66747091c05f507c9006

You had a bad reading of the etsi:

16dbm is EIRP not DBm.
regulation is 14dBM for RX 1
Regulation is 27dBm for RX 2

https://www.disk91.com/2017/technology/sigfox/all-what-you-need-to-know-about-regulation-on-rf-868mhz-for-lpwan/

@disk91 - Can you find the exact spec which advises 14dBm for RX 1 and 27dBm for RX 2?  The only value in the spec I can find is a max value of 16dBm.

@disk91 We have reviewed the evidence and you are right.
Nevertheless, the regional spec makes no mention of this so we had to dig into the actual EU standard  that you provided to see that RX2 is allowed to broadcast at 27dBM.
As we re-wrote the regional code to  improve it, we got confused because of some previously file tickets that seemed to tell us otherwise.

https://github.com/helium/router/issues/363
https://github.com/helium/router/issues/364
https://github.com/helium/router/issues/365

So we really want to make sure that: RX1 = 14dBM  and  RX2 = 27dBM.
Please confirm that this is the intended behavior and will will fix it.

Check the regulation spec : http://www.arcep.fr/fileadmin/reprise/dossiers/frequences/ERC-REC-70-03E-version02.PDF
Annex 1, Page 6 You will find the band G3 corresponding to the 869.4 to 869.65 where the RX2 windows is. This band is 10% duty cycle and 500mW e.r.p. eq 27dBm
In the LoRaWan Regional settings (RP002-1*.0.3-Final-1.pdf) you can see :
The RX2 receive window uses a fixed frequency and data rate. The default parameters are
869.525 MHz / DR0 (SF12, 125 kHz)
This frequency is inside the band G3

Fix to LoRaWAN library
https://github.com/helium/erlang-lorawan/pull/14/files

Fix to Router
https://github.com/helium/router/pull/793


warmup cache for cypress tests

I think the cache-warmup is not running on jenkins because government field tests are still failing.
Adding the env properties to CI docker-compose override

ignore this, I commited the change in the wrong docker compose file


Support Project-Based (application) Units

Allow for project-specific units, where the cards are ordered to support project based learning

Closing in favor of https://github.com/sagefy/sagefy/issues/378


Attempt to fix reflective access error

Codecov Report

Merging #180 (6bc6e20) into master (fa7c408) will increase coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #180      +/-   ##
============================================
+ Coverage     75.48%   75.70%   +0.22%
- Complexity      715      729      +14
============================================
  Files            95       95
  Lines          2166     2198      +32
  Branches        258      274      +16
============================================
+ Hits           1635     1664      +29
- Misses          403      406       +3
  Partials        128      128

Impacted Files
Coverage Δ

src/main/java/socialite/model/person/Dates.java
64.28% <0.00%> (-7.15%)
:arrow_down:

...n/java/socialite/logic/commands/RemarkCommand.java
100.00% <0.00%> (ø)

src/main/java/socialite/model/person/Person.java
85.12% <0.00%> (+1.12%)
:arrow_up:

Continue to review full report at Codecov.

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

I gave up LOL have no idea why it only fails on Ubuntu.


Resizing TextureBuffer

Concerning GLMakie. Dynamically changing the number of particles in a meshscatter does not work, because resizing of TextureBuffers is not implemented. E.g
using Makie

pos = Node(rand(Point3f0, 10))
meshscatter(pos)

pos[] = rand(Point3f0, 5)

fails. This is a bit disappointing, because I frequently want to visualize simulations with an ever-changing number of agents, and sprites often don't look good enough for my taste.
So, with great naivete, I went ahead and digged through the source of GLMakie, and made the following trivial amendment https://github.com/JuliaPlots/GLMakie.jl/pull/109
which makes the above example work.
Could it really be this simple? Or rather, what still needs to be done?
Happy about any input!

Hm, it might just work :D But I'm not 100% sure anymore, why I implemented it and disabled it later on... -.-

This can be closed now that https://github.com/JuliaPlots/GLMakie.jl/pull/110 has been merged.


[T3A3][T09-A4]Zhang Yunxuan

Ready for review

most things have been discussed in class. Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Allowing template owner to download template

Description
Removed the download icon when a template is not extractable.
Modified the api to allow a user from the same account as the template, to change the extractable attribute on the template.

Fixes: #3400
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

Tested using the UI.
Create a user, then login with that user. Navigate to templates, add a template.
Edit the template, click on the extractable checkbox. Save changes.
At this point, there is no error.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-96

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-109)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31175 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3475-t109-kvm-centos7.zip
Smoke tests completed. 71 look OK, 1 have error(s)
Only failed tests results shown below:

@anuragaw @shwstppr can you review this PR?
@Spaceman1984 can you address review comments.
Thanks.

@borisstoyanov @shwstppr @anuragaw can you review and test. I've not tested it. Few cases; what happens to template wrt edit, download button for template registered by normal users under a domain, wrt root domain, domain admin, other accounts in the sub-domain etc.

Smoketests LGTM.

This is a known issue @shwstppr to go back and refresh the page. This is a general limitation of the UI.


Support array aggregation

e.g. array_agg, see https://www.postgresqltutorial.com/postgresql-aggregate-functions/postgresql-array_agg-function/

Is there any difference between ARRAY_AGG and our current LIST aggregate, or would an alias be sufficient?

Would you be open to adding a group_concat alias as well, or is the behavior different? It would help migration from SQLite!

GROUP_CONCAT seems to be equivalent to STRING_AGG, not to ARRAY_AGG. ARRAY_AGG returns a list, whereas GROUP_CONCAT returns a string. As far as I know SQLite does not have support for nested types.
I can add the alias for string_agg.

Ah, I see! Thank you!
On Tue, Sep 8, 2020, 2:23 PM Mark<EMAIL_ADDRESS>wrote:

GROUP_CONCAT seems to be equivalent to STRING_AGG, not to ARRAY_AGG.
ARRAY_AGG returns a list, whereas GROUP_CONCAT returns a string. As far
as I know SQLite does not have support for nested types.
I can add the alias for string_agg.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cwida/duckdb/issues/851#issuecomment-689054685, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOORAMI44I4DSFYUMGMOR3SEZZDRANCNFSM4QEWCKNA
.

This is implemented now


Testing: Move secret travis env vars to the travis account

It is possible to store travis environment variables in travis itself rather than the .travis.yml file.
This has several advantages:

We don't run the risk of losing or overriding key variables when merging up from old branches - as has happened repeatedly, often at my fault
Private vars aren't available on PRs or forks so provide little value to others
Currently some sensitive vars are published in plain text in our projects to allow this to work - we can keep these secret if we remove them from the public.
Forks can run against travis and provide their own variables for greater flexibility.

I'm in favour, after thinking about it. We should move the ARTIFACTS_KEY / ARTIFACTS_SECRET for each repo.

Happy with doing so for the secrets, but not for things like DB

Secret vars are already moved for most repos. Can we close this?


Last Accessed header now only appears on Course Outline screen

I've added a new function named isOnCourseOutline in CourseVideoListActivity, which allow us to determine if a user is on Course Outline screen or Course Detail screen.
p.s. we are using the same activity for both screens i.e. CourseOutlineActivity\
@aleffert plz review

:+1:


Correct typo in rules documentation

Summary
Add missing "is":
- The 🧪 emoji indicates that a rule in "preview".
+ The 🧪 emoji indicates that a rule is in "preview".

Test Plan
N/A

Thanks!


UIManager warning when using seekTo method

Due to #131, I decided to hide the default controls and create my own using slider, like this:

But, when I change the slider value and set the video position using `seekTo()`, it generates the warning, **Accessing view manager configs directly off UIManager via UIManager['ReactYouTube'] is no longer supported. Use UIManager.getViewManagerConfig('ReactYouTube') instead.**
Here is the screenshot of the error:

After Googling, I found two similar issues with other components - here and here

Facing the same issue!

@manzoorwanijk 56c037c15813976f86f225c1ec669e192af33185


Couldn't download the entire gallery from Deviantart

Some galleries have hundreds of images but RipMe downloaded only the first 24 or 48 or 96 images, and says that it's completed.

Is this problem still alive ?

Is this problem still alive ? Cuz I left a fresh installation of Win7 Ultimate SP1 x64, Oracle Java SE 8 Update 131 x64 and RipMe 1.5.2 get 3 galleries (2 were 99.999% ripped already, though) having well over 100 uploads each over night and got them no problem.
Next time fill out the template as instructed.

just tried it again today and it's working just fine. not sure what was the problem back then.


Code Formatting Cleanup

[x] removed extra semi-colons
[x] uniform indents across files
[x] convert double quotes to single
[x] fixed space around equal sign on JSX propery

addressed in https://github.com/DarkFlorist/TheInterceptor/pull/1228


Moe Sync

Commits:

 Hello
World
5c3759c36debd899431f95199c3bd9f1717c365d

 Second
Commit backticks
94feb2a27d2050fa8ba615b3694d329e988fcf9c

Jeez your markdown skills look terrible :trollface:


Fix some typos and minor issues generating fresh data for a new database

Hi @ivyleavedtoadflax,
I made a few changes to run this locally and thought it might be useful to push back up to the repo.

I had to generate fake data in a particular order, so I've made it work if you follow the README steps
I had an issue with the priority view using postgres
There were a few typos in the README.

Thanks,
Mat

Thanks for this @MatMoore. Travis is not finding the test db for some reason, so tests are failing.

Moved to #96 to fix failing tests.


Fix React dependency so XCode 12 can compile

Summary
Fixes issue described in https://github.com/facebook/react-native/issues/29633

Test Plan

What's required for testing (prerequisites)?
No tests needed, it was a wrong dependency.
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

@harunsmrkovic I tried applying this locally and got an error during pod install.
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `lottie-react-native-iOS` depends upon `React-Core-iOS`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

can you share how you have your Podfile setup to make this work?

Hm, it could be that use_frameworks! gets rids of this error for me... Not sure, haven't seen that error in awhile...

lottie-react-native is a Swift module, if we merge this PR we will start having this issue: https://github.com/facebook/react-native/issues/29633#issuecomment-694700346
We are waiting for a change in React Core's podspec to fix the issue: https://github.com/facebook/react-native/pull/29995

Looks like the change in React Core is already merged. Can anybody help me here testing this before merging?

This has been resolved on https://github.com/lottie-react-native/lottie-react-native/pull/738


NO-JIRA: chore(gha): fix poetry install in GitHub Actions

Description
Currently, pip install refuses to install outside of a virtual env without --break-system-packages.
To fix this, let's install with pipx and let's configure pipx for GHA caching.
How Has This Been Tested?
GHA
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/cc @jstourac

/lgtm

/override ci/prow/images
/approve


Add failing test for SSH clone

Cloning with an ssh URL results in error Unsupported URL protocol which is the result of a libgit2 check if SSH is enabled. It seems that SSH is not enabled for objective-git, although the GIT_SSH flag is set.
Is this the expected behaviour?

SSH used to work, so this is a regression :frowning:
While I like the idea of having a test like this, there are several reasons it could fail which have nothing to do with the framework. Also, the build server may not even be set up with an SSH key. Perhaps this test could be disabled by default and then manually enabled - or perhaps the logic depends on an environment variable to be present.
I think a better permanent test would be to assert that git_libgit2_features returns with the GIT_FEATURE_SSH bit set.

:+1: Will rewrite it then and find a test file where it suites in.

You can disable the test with xdescribe or xit. That test will be a great help in verifying a fix for the SSH functionality (which I suspect is build related).

Yeah, it seems that GIT_SSH is not set when script/update_libgit2 is being built. Too I am lacking a ton of cmake knowledge.

I've worked with the build scripts and cmake a bit so I can look into this issue.

I would also love to work on this but have little hope. I tried adding -DCMAKE_C_FLAGS="${CMAKE_C_FLAGS} -DGIT_SSH" but that did not help.

The libgit2 cmake build will disable SSH support if it doesn't find the libraries, which may be what's going on here. Are you seeing this when building for Mac, iOS or both?

Both as Mac is the test target and my iOS app also fails. Afaik the Mac build uses system OpenSSH and the iOS app depends on the OpenSSH iOS build.

@phatblat I fixed the build and enabled SSH support. I also refactored the test to test for the correct error (SSH credentials not there).

Fantastic! :balloon: I'll test this out later this evening. I have an idea for getting those SSH credentials working.

Superb!! 🎉
On Tuesday, July 7, 2015, Ben Chatelain<EMAIL_ADDRESS>wrote:

Fantastic! [image: :balloon:] I'll test this out later this evening. I
have an idea for getting those SSH credentials working.
—
Reply to this email directly or view it on GitHub
https://github.com/libgit2/objective-git/pull/478#issuecomment-119266271
.

@phatblat Did you have any chance to get to the tests or maybe share your approach?

Sorry, got tied up the last couple evenings.
I started adding some logic to pick up the SSH keys from ~/.ssh, but then I noticed that there is already an SSH clone test. This test doesn't run unless you have the GTUserName, GTPublicKey, GTPrivateKey and GTPrivateKeyPassword defined in the current environment.

I presume these values are defined on the GitHub build server. I defined them as above and ran this test on my Mac. So, SSH is working fine on the Mac side - without these changes.

It's been challenging validating this change on iOS as my client app builds with Xcode 7 but I'm not able to build ObjectiveGit from source with 7. However, I built this branch with 6.4 and copied over the .framework and the GIT_FEATURE_SSH flag is coming back set from git_libgit2_features.
This looks like progress, but I'd like to do some deeper validation because this change forces GIT_SSH to be set, but that flag is supposed to automatically get set by cmake if it finds the SSH lib. I'm concerned about the lib not being found since that can cause issues when an app tries to actually use SSH.

I think this may be the real fix: phatblat@aed2cc39c831697102ac6aff317990729b55dd2c. I misspelled LIBSSH2_INCLUDE_DIRS when I added that to the libgit2 build scripts.

I can verify it, my app still runs on Xcode 6.4. Will try it out today. If it fixes the issue, I will cherry pick and rebase this branch.

Also check out #483 to see if that works for you.

Closing in favour of #483


Y24-030 [BUG] Limber not allowing plate creation on TCR chromium plate

When attempting to assign tags to a LBC TCR Post Lig 1xSPRI plate when 1 group of tags are selected there is the option to create the plate (This is the case regardless of whether it is the i7 or i5 tags that are selected)

When the second group of tags is selected creating a plate is no longer an option

RT Ticket Number
RT799378
To Reproduce
(nts) The previous plate to the LBC TCR Post Lig 1xSPRI is LBC TCR Dil 2 in training I found SQPP-50916-O could be used to reproduce this. If non chromium tag sets are selected (i.e pWGSD) then the create plate option remains
'Possible' additional info:
Was discussed and mentioned at stand up (19/3) that there were JS changes a few weeks ago. The contacts in the RT mention that this has been a noted issue for the "..past few weeks"
Contacts:
Jo (jc32) Team Lead - Chromium 10X
Steve (sw32) SSR PaM

See crossed through wells now we've fixed the other issue in Y24-029. Investigating.

resolved by https://github.com/sanger/limber/issues/1631


Want to Add JS Projects - Percentage Scored Issue No. - #2271

Title and Issue number
Want to Add JS Projects - Percentage Scored Issue No. - #2271
Close #<issue_no>
Want to Add JS Projects - Percentage Scored Issue No. - #2271
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

Pls add this PR I have joined the JS Project code - Percentage Scored.


Support mTLS connection-level capabilities and RPC access filtering in C++ [run-systemtest]

@havardpe @bjorncs please review
Adds the following:

Named capabilities and capability sets that represent (respectively)
a single Vespa access API (such as Document API, search API etc)
or a concrete subset of individual capabilities that make up a
particular Vespa service (such as a content node).
A new capabilities array field to the mTLS authorization policies
that allows for constraining what requests sent over a particular
connection are allowed to actually do. Capabilities are referenced
by name and may include any combination of capability sets and
individual capabilities. If multiple capabilities/sets are configured,
the resulting set of capabilities is the union set of all of them.
An FRT RPC-level access filter that can be set up as part of RPC
method definitions. If set, filters are invoked prior to RPC methods.
A new PERMISSION_DENIED error code to FRT RPC that is invoked if
an access filter denies a request.

This also GCs the unused AssumedRoles concept which is now deprecated
in favor of capabilities.
This PR does not wire access filtering to any existing RPC method definitions;
this will be added when the base functionality is in.
Note: this is not yet a public or stable API, and capability
names/semantics may change at any time!

@havardpe PTAL. Have refactored and moved Capability ID functionality around so that it is no longer exposed as part of the API. bit_id/as_bit_set is no longer available.


lv_gif_event_cb callback don't work

Hi.
I try to call a event after end the gif animation, but the callback don't work.
This is the code I use.
The GIF is showing corretly in the screen,
I use the "release/v7" branch.
What is wrong?
void TFT_ShowGIF()
{
	ESP_LOGD(TAG, "Showing GIF");

	extern const uint8_t img155_155_opt70_map[];  //Use the example gif
	lv_obj_t * gif1 = lv_gif_create_from_data(lv_scr_act(), img155_155_opt70_map);

	// Set Finish Event
	lv_obj_set_event_cb(gif1, lv_gif_event_cb);

	lv_obj_set_pos(gif1, 0, 0);         //Set its position
}

void lv_gif_event_cb(struct _lv_obj_t * obj, lv_event_t event)
{
	ESP_LOGD(TAG, "GIF Event");

        if (LV_EVENT_LEAVE != event)  {
              return;
        }

       lv_obj_del(obj);
  }

The event should be sent here but only if the gif is not looped infinitely.

Hi kisvegabor.
I change the GIF for a only one loop using a EZGif.
In a PC, the GIF show only a one loop, but in the application, the GIF is showing in a infinite loop.
I need to config something for a one loop??
Thank's a lot.

There can be something problem here. Can you debug it?


update description of Seata in README.md

Describe what this PR does / why we need it
update description of Seata in README.md
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Thanks for your contribution.


HA doesn't recognize fmf ic3 devices inside zones

Hi, good morning. The issue persists on beta 9...
Beta 9:

versus v2.4.7:

Originally posted by @marceloaf in https://github.com/gcobb321/icloud3_v3/issues/36#issuecomment-1400254485

Right now, I am using FamShr and ios app, My wife is using FmF and iOS App. We are both Home and it shows 2 people in the Home zone and lists them in the person attribute. She was out to lunch and in the Quail zone and it showed one person at home (me) and one at Quail (her). I could not tell if that was coming from FamShr, FmF or the iOS App.
I set up the persons for each of us and did have to go to the zone and update the quail zone, it was showing Quail but it didn't look like it was displaying it correctly (quail instead of Quail) so I set it as Quail. I went back to iC3 and saw I had the 'name' selected for the Event Log Zone format, I changed it to the HA Zone friendly name and then she showed up in the Quail zone person count. Changing the Zone Format may not have mattered.
I have not used the person.entity before and will see what happens if I do not associate the iOS App with it.

I fixed a problem where the non-numeric sensors were not showing in the History correctly (HA thought they were numbers instead of text because the unit_of_measurement for text sensors was wrong). I don't know if it has anything to do with the person issue but here it is just in case,
Unzip it into the /config/icloud3 directory and restart HA.
sensor.zip

Hi Gary, how are you? I still think there is a bug somewhere and, unfortunately, I’m not being able to explain/show it to you. Maybe because of the language barrier...
I noticed that, no matter which option you choose in the Zone Name Format, the zones are being shown the very same way.  In all the images below you can see that despite of the zone name format, the home zone is shown with capital (probably the friendly_name) and the other zones like the entity_ids. Between evey change on the zone name format I restarted icloud3 to make sure the change was being recognized:

Equivalent to fname in v2.4.7
[Graphical user interface, text, application, email  Description automatically generated]
[Graphical user interface, text, application  Description automatically generated]

Equivalent to zone in v2.4.7

[Timeline  Description automatically generated]
[Graphical user interface, text, application  Description automatically generated]

Equivalent to name in v2.4.7
[Graphical user interface, text, application, email  Description automatically generated]
[Graphical user interface, application  Description automatically generated]

Equivalent to title  in v2.4.7
[Timeline  Description automatically generated with medium confidence]
[Graphical user interface, text, application  Description automatically generated]

I chose one of the zones to make an experiment. I changed the zone entity id from zone.casa_da_lena to zone.lena and the Friendly Name from Casa da Lena to Lena. This was the only way HA could  “recognize” fmf ic3 devices inside the zone. See below:
[A picture containing graphical user interface  Description automatically generated]
If I change the zone name OR the zone entity_id back to more than 1 word, it doesn’t recgonize it as inside the zone.... ☹
[A picture containing graphical user interface  Description automatically generated]
In v2.4.7 if I play around with the zone_display_name the results are consistent as shown below:
display_zone_format: fname
[Graphical user interface, text, application, chat or text message  Description automatically generated]
display_zone_format: zone
@.***
display_zone_format: name
[Graphical user interface, text, application, chat or text message  Description automatically generated]
display_zone_format: title
[Graphical user interface, text, application, chat or text message, Teams  Description automatically generated]
In version 2.4.7 if I use the zone_friendly_name as fname or title the devices are correctly recognized inside the zone. The image below I’m using as title
@.***
Thanks in advance
Marcelo
From: Gary Cobb @.>
Sent: Tuesday, January 24, 2023 7:56 PM
To: gcobb321/icloud3_v3 @.>
Cc: marceloaf @.>; Author @.>
Subject: Re: [gcobb321/icloud3_v3] HA doesn't recognize fmf ic3 devices inside zones (Issue #50)
Right now, I am using FamShr and ios app, My wife is using FmF and iOS App. We are both Home and it shows 2 people in the Home zone and lists them in thperson attribute. She was out to lunch and in the Quail zone and it showed one person at home (me) and one at Quail (her). I could not tell if that was coming from FamShr, FmF or the iOS App.
I set up the persons for each of us and did have to go to the zone and update the quail zone, it was showing Quail but it didn't look like it was displaying it correctly (quail instead of Quail) so I set it as Quail. I went back to iC3 and saw I had the 'name' selected for the Event Log Zone format, I changed it to the HA Zone friendly name and then she showed up in the Quail zone person count. Changing the Zone Format may not have mattered.
I have not used the person.entity before and will see what happens if I do not associate the iOS App with it.
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F50%23issuecomment-1402796247&data=05|01||d583d7ed7fab436faaae08dafe5e18a9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638101977338605278|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=I5NeYXZiGx4Mas%2FHOkc4BeoV3wQuVmBTpo0e6HOemSo%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS74X2BLJ4EX4WDQU3DWUBMWHANCNFSM6AAAAAAUFD2ARY&data=05|01||d583d7ed7fab436faaae08dafe5e18a9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638101977338605278|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=s7NdVcvz21BpmtXSWuFI5aIYHy84z%2F2fOyZ7z8ZHpX4%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hi Gary, how are you? I still think there is a bug somewhere and, unfortunately, I’m not being able to explain/show it to you. Maybe because of the language barrier...
I noticed that, no matter which option you choose in the Zone Name Format, the zones are being shown the very same way.  In all the images below you can see that despite of the zone name format, the home zone is shown with capital (probably the friendly_name) and the other zones like the entity_ids. Between evey change on the zone name format I restarted icloud3 to make sure the change was being recognized:

Equivalent to fname in v2.4.7

Equivalent to zone in v2.4.7

Equivalent to name in v2.4.7

Equivalent to title  in v2.4.7

I chose one of the zones to make an experiment. I changed the zone entity id from zone.casa_da_lena to zone.lena and the Friendly Name from Casa da Lena to Lena. This was the only way HA could  “recognize” fmf ic3 devices inside the zone. See below:

If I change the zone name OR the zone entity_id back to more than 1 word, it doesn’t recgonize it as inside the zone.... ☹

In v2.4.7 if I play around with the zone_display_name the results are consistent as shown below:
display_zone_format: fname

display_zone_format: zone

display_zone_format: name

display_zone_format: title

In version 2.4.7 if I use the zone_friendly_name as fname or title the devices are correctly recognized inside the zone. The image below I’m using as title

Thanks in advance
Marcelo

OK. I set up everything like you . Even moved my home zone and set up a Casa de Test. Yes, there was a bug. It was in v2.4.7, not v3. It is recommended by HA that all state values be lower case with underscores ('_') for spaces, just like entity names. v2.4.7 did not follow this standard, v3 does, or there is a new option to follow it or not follow it. You can now decide.
I added an option on the Event Log Parameters screen to use the Zone format selected for the Event Log or to follow the HA standard. It is in b10 which I am going to upload tomorrow.

Ok, thanks for taking a look into this. So, if I understand correctly, now v3 will honor the Zone Name Format, right?
Best regards,
Marcelo
From: Gary Cobb @.>
Sent: Friday, January 27, 2023 8:46 PM
To: gcobb321/icloud3_v3 @.>
Cc: marceloaf @.>; Author @.>
Subject: Re: [gcobb321/icloud3_v3] HA doesn't recognize fmf ic3 devices inside zones (Issue #50)
OK. I set up everything like you . Even moved my home zone and set up a Casa de Test. Yes, there was a bug. It was in v2.4.7, not v3. It is recommended by HA that all state values be lower case with underscores ('_') for spaces, just like entity names. v2.4.7 did not follow this standard, v3 does, or there is a new option to follow it or not follow it. You can now decide.
I added an option on the Event Log Parameters screen to use the Zone format selected for the Event Log or to follow the HA standard. It is in b10 which I am going to upload tomorrow.

Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F50%23issuecomment-1407195977&data=05|01||3ab0644d50824cc5b59b08db00c0970d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104599384650249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Z%2FUSa5osM7GAJKfXlyG%2BTyhVMJ0B5LO5eeOfoklkRkY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS523Z6PT7DEGO37HFTWURM2BANCNFSM6AAAAAAUFD2ARY&data=05|01||3ab0644d50824cc5b59b08db00c0970d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104599384650249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=1sKxN1eeGzG20ObeDBCIFWB9jwmotWRRedxCmOZ21EM%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Yes. There is new option on the Event Log Parameter screen. You can select to override the HA format and use the zone name format you are using on the Event Log. I hope to have it out later today.
On Jan 28, 2023 at 7:54 AM -0500, marceloaf @.***>, wrote:

Ok, thanks for taking a look into this. So, if I understand correctly, now v3 will honor the Zone Name Format, right?
Best regards,
Marcelo
From: Gary Cobb @.>
Sent: Friday, January 27, 2023 8:46 PM
To: gcobb321/icloud3_v3 @.>
Cc: marceloaf @.>; Author @.>
Subject: Re: [gcobb321/icloud3_v3] HA doesn't recognize fmf ic3 devices inside zones (Issue #50)
OK. I set up everything like you . Even moved my home zone and set up a Casa de Test. Yes, there was a bug. It was in v2.4.7, not v3. It is recommended by HA that all state values be lower case with underscores ('_') for spaces, just like entity names. v2.4.7 did not follow this standard, v3 does, or there is a new option to follow it or not follow it. You can now decide.
I added an option on the Event Log Parameters screen to use the Zone format selected for the Event Log or to follow the HA standard. It is in b10 which I am going to upload tomorrow.

Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F50%23issuecomment-1407195977&data=05|01||3ab0644d50824cc5b59b08db00c0970d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104599384650249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Z%2FUSa5osM7GAJKfXlyG%2BTyhVMJ0B5LO5eeOfoklkRkY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS523Z6PT7DEGO37HFTWURM2BANCNFSM6AAAAAAUFD2ARY&data=05|01||3ab0644d50824cc5b59b08db00c0970d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638104599384650249|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=1sKxN1eeGzG20ObeDBCIFWB9jwmotWRRedxCmOZ21EM%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Working now! Thanks!!


Add a script to monitor unicornherder reloads

Trello: https://trello.com/c/oPNhsGl3/536-investigate-delaying-an-app-deployment-until-the-app-has-restarted-to-avoid-false-smokey-builds
We reload Ruby apps, following a deployment, by using upstart to reload
a unicornherder 1 process. This reload creates a new unicorn process
with new workers initialised, after a period of overlap - where the old
and new unicorn processes serve requests - the old process is
terminated.
The problem with this functionality is that we lack visibility of when
a new version of an app is available. We know that we told it to
reload and we expect that some point in the next couple of minutes the
app will be available. This has led to incidents where we've triggered
smoke tests following the deploy of a broken app, but we've been unaware
the app was broken because the smoke tests ran against the old,
non-broken, version of the app.
To counter this problem this commit introduces a wrapper script for
unicornherder reloading. This script monitors whether a new process is
created and when the old one is removed. This was done as a separate
script to unicornherder as there didn't seem a simple synchronous way
to communicate with the process (our existing communication is via signals
which are an asynchronous medium).
The script is expected to be run by a superuser as per the existing reload
commands 2. To support this I've added in permissions for the deploy user
to be able to run this script with sudo.
There's a couple of parts to the script that we may consider needing to
parameterise should a need arise. It expects the pid file to be in a
consistent location matching the name of the service and it expects the
restarts to complete within 3 minutes.
I wrote this in bash as it seemed to be the most common approach we have
for wrapper scripts and this avoids the dependency version/concerns that
would be the case in Ruby.
Trying this out on a deploy you get the following output:
18:03:30   * executing `deploy:restart'
18:03:30   * executing "sudo initctl start email-alert-api 2>/dev/null || sudo govuk_unicorn_reload email-alert-api"
18:03:30     servers: ["ip-10-1-5-9.eu-west-1.compute.internal", "ip-10-1-6-234.eu-west-1.compute.internal"]
18:03:30     [ip-10-1-5-9.eu-west-1.compute.internal] executing command
18:03:30 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Checking email-alert-api is running
18:03:30 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> email-alert-api is running with process 26011. Reloading...
18:03:40 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> New process 26718 started
18:03:40 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:03:50 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:04:00 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:04:10 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Process 26011 has exited
18:04:10 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Successfully reloaded email-alert-api
18:04:10     command finished in 40145ms
18:04:10     [ip-10-1-6-234.eu-west-1.compute.internal] executing command
18:04:10 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Checking email-alert-api is running
18:04:10 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> email-alert-api is running with process 29454. Reloading...
18:04:20 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> New process 30188 started
18:04:20 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:04:30 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:04:40 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
18:04:50 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Process 29454 has exited
18:04:50 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Successfully reloaded email-alert-api
18:04:50     command finished in 40112ms

We can also configure the task to run in parallel to speed up the
process:
19:14:16   * executing `deploy:restart'
19:14:16   * executing "sudo initctl start email-alert-api 2>/dev/null || sudo govuk_unicorn_reload email-alert-api"
19:14:16     servers: ["ip-10-1-5-9.eu-west-1.compute.internal", "ip-10-1-6-234.eu-west-1.compute.internal"]
19:14:16     [ip-10-1-6-234.eu-west-1.compute.internal] executing command
19:14:16     [ip-10-1-5-9.eu-west-1.compute.internal] executing command
19:14:16 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Checking email-alert-api is running
19:14:16 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Checking email-alert-api is running
19:14:16 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> email-alert-api is running with process 30188. Reloading...
19:14:16 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> email-alert-api is running with process 26718. Reloading...
19:14:26 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> New process 533 started
19:14:26 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> New process 4064 started
19:14:26 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:26 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:36 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:36 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:46 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:46 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Waiting for processes to swap over
19:14:56 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Process 26718 has exited
19:14:56 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Process 30188 has exited
19:14:56 *** [err :: ip-10-1-5-9.eu-west-1.compute.internal] ---> Successfully reloaded email-alert-api
19:14:56 *** [err :: ip-10-1-6-234.eu-west-1.compute.internal] ---> Successfully reloaded email-alert-api
19:14:56     command finished in 40172ms

Nice bash! Despite what people say, I found it easy to follow 💯.
Aside from a couple of minor comments, I was thinking about the ways the assumptions of the script might break. I could only think of one: if a previous deployment is in a constant state of restarting, then a subsequent deploy may have a race condition:

service <app> start may fail if the app is briefly up
pid_running may then fail if the app falls over (again)

In this scenario, we'd abort the reload incorrectly. On the positive side, upstart would then start the app by itself, anyway. This seems like a reasonable risk, since it's easy enough to re-run the deploy and watch it succeed next time round.

Yup, that sounds correct - it seems better to claim the deploy failed when it's ambiguous than to deem it successful.
It can behave rather oddly is if anything is also talking to upstart. For example, if while we were waiting for the app to reload something else triggered an upstart restart of an app then we'd find the pid we were expecting would never be running and the old pid would terminate quickly.
It's worth bearing in mind that a failed deploy at this point though is rather special as it's past the point where capybara can rollback. This means that you'll just get told of an error and could be left in an inconsistent state if deploys succeeded on some boxes but not others - though this seems the same as the current situation this just makes it more visible.

we'd find the pid we were expecting would never be running and the old pid would terminate quickly.

Ah, interesting. This is a similar outcome to the scenario I mentioned, but also for the new process. Do you know of any predictable ways a restart command could be issued around a deployment?

as it's past the point where capybara can rollback

This seems like a positive thing to me - if we're failing to roll forward, then trying to roll back automatically could make it worse!

we'd find the pid we were expecting would never be running and the old pid would terminate quickly.

Ah, interesting. This is a similar outcome to the scenario I mentioned, but also for the new process. Do you know of any predictable ways a restart command could be issued around a deployment?

Hmm, I guess if puppet runs at the same time as a deploy and there is a change to an app that triggers an app restart. Otherwise it'd be someone manual. Seems very edge case.

as it's past the point where capybara can rollback

This seems like a positive thing to me - if we're failing to roll forward, then trying to roll back automatically could make it worse!

Yeah just a nuance that a failed deploy may actually mean a partial deploy - I guess that has always been the case though.


[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.64-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to Account settings > Workspaces > any workspace
Go to Members
Invite +252 3 234211 which will cause an error
Return to workspace list
Click on the X button to dismiss the error

Expected Result:
The error is dimissed
Actual Result:
The error is not dismissed when clicking on X button in the workspace list
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/e7d367ca-0a07-4aa0-bd73-d6cc16840db5
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0186e1563827cf6717
Upwork Job ID:<PHONE_NUMBER>343851008
Last Price Increase: 2024-04-23
Automatic offers:

akinwale | Contributor | 0
bernhardoj | Contributor | 0

Issue OwnerCurrent Issue Owner: @joekaufmanexpensify

this def seems like a bug.

Proposal
Please re-state the problem that we are trying to solve in this issue.
There are 3 issues here, first, the failed member and its error message don't show like before. Second, when we close the invite error message, the policy is removed and we are navigated back to the workspace list. Last, we can't clear the error from workspace list page/
What is the root cause of that problem?
For the first problem, we get the member data from getMemberAccountIDsForWorkspace
https://github.com/Expensify/App/blob/d296ef806743f7bdf40d8c8d243d95771996d33d/src/pages/workspace/WorkspaceMembersPage.tsx#L75
However, getMemberAccountIDsForWorkspace ignores member that has an error.
https://github.com/Expensify/App/blob/d296ef806743f7bdf40d8c8d243d95771996d33d/src/libs/PolicyUtils.ts#L157-L159
For the second problem, when closing the error message, we call dismissError which will navigate the user back to the workspace list page and remove the workspace.
https://github.com/Expensify/App/blob/d296ef806743f7bdf40d8c8d243d95771996d33d/src/pages/workspace/WorkspaceInitialPage.tsx#L74-L77
For the 3rd problem, if there is no pending action, which is true for our case, we just do nothing.
https://github.com/Expensify/App/blob/792459706d4e1e5cbedaf334900f5ce388649a10/src/pages/workspace/WorkspacesListPage.tsx#L339-L344
What changes do you think we should make in order to solve the problem?

For the first problem, we can add a new param to getMemberAccountIDsForWorkspace to include members with errors.
In 3rd problem, we already handle the case for add/delete pending action.
https://github.com/Expensify/App/blob/792459706d4e1e5cbedaf334900f5ce388649a10/src/pages/workspace/WorkspacesListPage.tsx#L105-L116
To solve the 3rd problem, we will remove the pending action check from the code below.
https://github.com/Expensify/App/blob/792459706d4e1e5cbedaf334900f5ce388649a10/src/pages/workspace/WorkspacesListPage.tsx#L340-L343
In dismissWorkspaceError, if the pending action is empty, then we just want to clear the error. We have Policy.clearErrors,
https://github.com/Expensify/App/blob/a852ea7a4d3707bc4ed9eb87e38ff01536a7805f/src/libs/actions/Policy.ts#L2503-L2506
but it doesn't work because we access the key wrongly, it should be
if (!allPolicies?.[`${ONYXKEYS.COLLECTION.POLICY}${policyID}`])

but even if we fix this one, looks like the double merge with a null and empty object doesn't work at all.
https://github.com/Expensify/App/blob/a852ea7a4d3707bc4ed9eb87e38ff01536a7805f/src/libs/actions/Policy.ts#L1789-L1796
To simplify it, we can just update Policy.clearErrors to replace setWorkspaceErrors with
Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors: null});

To solve the 2nd problem, we will update the onClose code of the error to be like this. We check !policyID for invalid policy ID error. I don't think we need to add for delete case like in above, but if we want to add it, we can just add it to follow the similar pattern in dismissWorkspaceError above.
onClose={() => {
    if (!policyID || policy?.pendingAction == 'add') {
        dismissError(policyID)
    } else {
        Policy.clearErrors(policyID);
    }
}}

Updated proposal to include more fix

Proposals pending review

Sorry this one, skipped my list will get to it later today!

TY!

Pending review from @Santhosh-Sellavel

Sorry for the back and forth. I'm Just gonna unassign this as my bandwidth is too low. Asked here for volunteers

@arosiclair Will takeover this as C+!

Looks like an auto complete error above. Taking over here as C+.

After reviewing the proposals, I believe @bernhardoj's proposal is the best one which contains a comprehensive fix for the issue and its related quirks.
@bernhardoj Please also verify and ensure that the member count for the workspace is correctly updated when the invite fails.
🎀 👀 🎀 C+ reviewed.

PR is ready
cc: @akinwale

@akinwale could you please handle the BZ checklist this week so we can prep for payment?

bump @akinwale could you please handle BZ here so we can issue payment?

[x]  [@akinwale] The PR that introduced the bug has been identified. Link to the PR:
[x]  [@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[x]  [@akinwale] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Not a regression. This was not being specifically handled.

[x]  [@akinwale] Determine if we should create a regression test for this bug.
[x]  [@akinwale] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Steps

Launch Expensify.
Open the workspace members as a workspace admin.
Invite +252 3 234211.
Verify that the invited member is displayed with an error message.
Clear the displayed error message.
On the workspace settings page, clear the error message.
Verify that the error message is cleared.
Repeat steps 2 through 4.
Navigate back to the workspace list page.
Clear the error message displayed below the list of workspace items.
Verify that the error message is cleared.

Do we agree 👍 or 👎?

Hmm, I feel like this is a pretty niche issue. I feel like it's fine to have no regression test for this.

Checklist is complete!

All set to issue payment. We need to pay:

@bernhardoj - $250 for PR via upwork.
@akinwale - $250 for C+ via upwork.

@bernhardoj $250 sent and contract ended!

@akinwale $250 sent and contract ended!

Upwork job closed.

All set, TY everyone!


Dependancy Issue

Hi @hoangtien2k3 @hoangchungk53qx1
The repo is really great and good and i would like to contribute as well,But i couldnt do an initial setUp
when i run the mvn clean install i see a quite a few dependancy conflicts especially the spring-web and boot version
Here it uses 2.7.16
org.springframework.boot
spring-boot-starter-parent
2.7.16

but the web version

org.springframework
spring-web
6.1.11

    and in most of the modules spring-web  uses the spring base version which is supposed to be 5.x series

    <dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-webflux</artifactId>
		</dependency>

		Even excluding it

		<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-webflux</artifactId>
		<exclusions>
			<exclusion>
				<groupId>org.springframework</groupId>
				<artifactId>spring-web</artifactId>
			</exclusion>
		</exclusions>
	</dependency>

	dosent fix the issue

Hi @smfaizalkhan
Thanks for the kind words! It looks like there are some dependency version mismatches causing issues with your setup. The project is using Spring Boot 2.7.16, but Spring Web version 6.1.11, which is part of Spring Framework 6.x series, might not be compatible with the 2.x Spring Boot version.
To resolve this, you could try aligning both Spring Boot and Spring Web versions. Either downgrade spring-web to a version compatible with 2.7.16 or upgrade the Spring Boot version to 3.x, which supports Spring Framework 6.x.
Let me know if you need further assistance!

@smfaizalkhan
Contributing
Thank you for considering contributing to our project! Follow these steps to set up the project and resolve common issues before making contributions:
1. Resolve Spring Dependency Conflicts
The project uses Spring Boot 2.7.16, which is compatible with Spring Framework 5.x. If you encounter dependency conflicts like seeing spring-web 6.1.11 (from Spring Framework 6.x), here’s how to resolve it:

Option 1: Downgrade spring-web to a version compatible with Spring Boot 2.7.16, such as 5.3.x.
Option 2: Alternatively, you can upgrade the project to Spring Boot 3.x, which is compatible with Spring Framework 6.x. Note that this will require additional refactoring to handle breaking changes.

2. Fork the Repository

Fork the repository to your own GitHub account to make changes safely.
Clone the forked repository to your local machine using:

  git clone https://github.com/your-username/repo-name.git

3. Set Up the Project Locally

After cloning, navigate to the project directory and ensure all dependencies are properly installed by running:

mvn clean install

4. Create a Branch for Your Changes

Always create a new branch for the feature or fix you want to contribute:

git checkout -b fix-version-conflict

5. Make the Necessary Adjustments

Resolve any dependency conflicts, make your changes, and test your setup.
Run tests to ensure everything is working correctly:

mvn test

6. Submit a Pull Request

Push your branch to your forked repository:

git push origin fix-version-conflict

If you need help at any step or have questions, feel free to reach out! We're happy to assist.


Front - V1 - iOS - Create the folder

• Create the project folder in the github project (title : "SwiftUI")

Might be useful to follow this kudoleh/iOS-Clean-Architecture-MVVM repo for a structure template

[ ] Make a new xcode swiftui project

use the swift package manager for dependency management
make a first build (Xcode build docs)

[ ] Create the simplest page

A good candidate can be the list of newsletters


Add support for Rollouts resource

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I agree to follow the Code of Conduct.

Problem Description
Hello! Please add support for the Rollouts resource, which replaces Deployment when using the Argo Rollouts utility. In general, this resource has the same structure as Deployment (except for some additional fields)
Proposed Solution
Add support for Rollouts resource
Alternatives Considered
No response
Additional Information
No response

Hey @ykizin,
This sounds like a great and easy-to-add enhancement. I'm unsure if we will have time for this in the future, but contributions are always welcome!


episode 7: GPU programming options

low-level, directive-based, kernel-based, ... options.
low-level: CUDA, HIP
directive-based: OpenMP, OpenACC (incremental approach)
language-based: Python-numba, Julia-GPU, SYCL, TensorFlow/Pytorch

this is all done, resolving


windows10:V0.1.35 -The API interface of openai faill! but V0.1.34 is ok!

What is the issue?
V0.1.35: windows10,openai api fail!
Version 0.1.35: The API interface of openai cannot be used.
It is OK to return to 0.1.34.
Now using version 0.1.34, the openai interface can be used normally.

OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.35

ok   https://github.com/ollama/ollama/releases/download/v0.1.34/OllamaSetup.exe
fail  https://github.com/ollama/ollama/releases/download/v0.1.35/OllamaSetup.exe

Hi @808cn would it be possible to share the error you're seeing?

@808cn maybe it’s related to the #4357 about incorrect finish_reason value in openai response.
If so you can test with the new release v0.1.37 to see if it fixes the problem.

Thank you!
new release v0.1.37  windows10,openai is good!

@jmorganca I think you can close the issue 🙂