Create new layout for /livepeer page

Maybe make the topbar a side bar? find a way to make the feed taller at least
Would also make scaling for mobile easier if all components are less wide
Think making events 3 lines tall and very narrow?

Currently reworking the Orchviewer and Event viewer to allow for vertical viewing
Also moving the top meta bar to the left and make it tall instead of wide


[Emergency]Change cheerio version

This sentence generates errors. (cheerio/index.js)
'exports.version = require('./package').version;'
and This sentence should be change to 'exports.version =
require('./package,json').version;'

Fixed in #80


Add support for Windows systems.

Currently the logger only works for UNIX based systems. For a better user experience, Windows systems should have the support added too.

I would like to help with Windows computers.

Sure, take it on yourself, make a pull request once you're done and I'll review it. Thanks for considering it!

Can u give me an idea as to where I can start from  ?

I'd suggest trying to make a Windows version, maybe in Visual Studio and see if it works like in Linux. Basically what I'd like to see is a structure as follows when doing debugging:
Current time (hours, mins, seconds) followed by debug level (DEBUG, INFO, WARNING, ERROR, FATAL), followed by the class name and line where the log was used, and followed by the debug message.
I'll attach a print screen to show how I'd like it to be written code-wise and what output to expect:

It works fine on a Windows PC

Judging from the screenshot, I guess you are using VS Code. I specified Visual Studio (I tested it on that and it failed, so it's guaranteed not to work on that). in the comment. I'll be a bit more clear this time: Visual Studio (2019 - Community Edition) doesn't compile and run this, so we should have support for the VS compiler too.

Here's what I am getting when using Visual Studio 2019:

This is the result for (_MSC_VER) version 1928 when running the above code.

Could you try uninstalling VS and downloading it again?

Could you try uninstalling VS and downloading it again?

I kindly hope this is not an official suggestion you propose. Also, I did update Visual Studio (I'm not going to uninstall 80 GB and reinstall it just to "Seem to fix the issue") and it is still NOT working. I believe our compilers differ and that's why in your case it may work and mine not. (or you had added the option to disable certain warnings, which I do NOT recommend!)
Anyways I found a fix, to check platform specifically if we use Windows or not and I'll add the required changes in the next commit.


Build failed on RHEL9 with OpenSSL 3

I was building the main branch with:
cmake -DBUILD_ONLY="sns" -DBUILD_SHARED_LIBS=OFF ../
But at the make-run I get Segmentation Faults on sns-gen-tests so I tried to build with:
cmake -DBUILD_ONLY="sns" ../
then on "make -j 4 VERBOSE=1"    I get this output:
cd /home/someuser/aws-sdk-cpp/build/generated/tests/sns-gen-tests && /usr/bin/cmake -E cmake_link_script CMakeFiles/sns-gen-tests.dir/link.txt --verbose=1

/usr/bin/c++ -O3 -DNDEBUG @CMakeFiles/sns-gen-tests.dir/objects1.rsp -o sns-gen-tests  -Wl,-rpath,/home/someuser/aws-sdk-cpp/build/tests/testing-resources:/home/someuser/aws-sdk-cpp/build/generated/src/aws-cpp-sdk-sns:/home/someuser/aws-sdk-cpp/build/src/aws-cpp-sdk-core ../../../tests/testing-resources/libtesting-resources.so ../../src/aws-cpp-sdk-sns/libaws-cpp-sdk-sns.so ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so ../../../crt/aws-crt-cpp/libaws-crt-cpp.a ../../../crt/aws-crt-cpp/crt/aws-c-mqtt/libaws-c-mqtt.a ../../../lib/libaws-c-event-stream.a ../../../crt/aws-crt-cpp/crt/aws-c-s3/libaws-c-s3.a ../../../crt/aws-crt-cpp/crt/aws-c-auth/libaws-c-auth.a ../../../crt/aws-crt-cpp/crt/aws-c-http/libaws-c-http.a ../../../crt/aws-crt-cpp/crt/aws-c-io/libaws-c-io.a ../../../lib/libs2n.a /usr/lib64/libcrypto.so ../../../crt/aws-crt-cpp/crt/aws-c-compression/libaws-c-compression.a ../../../crt/aws-crt-cpp/crt/aws-c-cal/libaws-c-cal.a /usr/lib64/libcrypto.so ../../../crt/aws-crt-cpp/crt/aws-c-sdkutils/libaws-c-sdkutils.a ../../../crt/aws-crt-cpp/crt/aws-checksums/libaws-checksums.a ../../../crt/aws-crt-cpp/crt/aws-c-common/libaws-c-common.a -lpthread -ldl -lm -lrt
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `OPENSSL_free'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_CIPHER_CTX_key_length'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_pop_free_ex'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `SSLeay'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `X509_NAME_hash'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_CIPHER_CTX_cleanup'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_256_gcm_tls13'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `AWSLC_thread_local_clear'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_seal'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_new_null'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `BN_num_bytes'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_open'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_128_gcm'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_cleanup'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_MD_CTX_destroy'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_chacha20_poly1305'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_PKEY_get1_tls_encodedpoint'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `OPENSSL_malloc'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `AWSLC_thread_local_shutdown'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_num'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_free'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_value'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_MD_CTX_create'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_free'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `FIPS_mode'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_PKEY_base_id'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_256_gcm'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_init'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_CIPHER_CTX_init'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `sk_push'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_AEAD_CTX_zero'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_256_gcm_tls12'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_128_gcm_tls13'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `SSLeay_version'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_MD_size'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_aead_aes_128_gcm_tls12'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_PKEY_size'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `CRYPTO_tls1_prf'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_PKEY_set1_tls_encodedpoint'
/usr/bin/ld: ../../../src/aws-cpp-sdk-core/libaws-cpp-sdk-core.so: undefined reference to `EVP_MD_CTX_size'
collect2: error: ld returned 1 exit status
make[2]: *** [generated/tests/sns-gen-tests/CMakeFiles/sns-gen-tests.dir/build.make:134: generated/tests/sns-gen-tests/sns-gen-tests] Error 1
make[2]: Leaving directory '/home/someuser/aws-sdk-cpp/build'
make[1]: *** [CMakeFiles/Makefile2:939: generated/tests/sns-gen-tests/CMakeFiles/sns-gen-tests.dir/all] Error 2
make[1]: Leaving directory '/home/someuser/aws-sdk-cpp/build'
make: *** [Makefile:156: all] Error 2

Expected Behavior
build should finish and tests should pass
Current Behavior
failed on build - see description
Reproduction Steps
RHEL 9.2 (Plow)
gcc 11.3.1
openssl 1.3.0
git clone --recurse-submodules https://github.com/aws/aws-sdk-cpp
cd aws-sdk-cpp
mkdir build;cd build
cmake -DBUILD_ONLY="sns" -DBUILD_SHARED_LIBS=OFF ../
or
cmake -DBUILD_ONLY="sns" ../
make -j 4
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.11.137
Compiler and Version used
gcc 11.3.1
Operating System and version
RHEL 9.2

Hi @majestix508 ,
Thank you for posting this issue.
We are using a custom FindCrypto cmake module which might give some issues. It seems that crypto lib headers found do not match crypto lib binaries found.
Could you please also post the output of the cmake configure stage i.e. cmake -DBUILD_ONLY="sns" ../?
Best regards,
Sergey

`cmake -DBUILD_ONLY="sns" ../
CMake Warning at CMakeLists.txt:9 (message):
In 1.11 releases, we are releasing experimental alternative building
mode.By setting -DLEGACY_MODE=OFF you can test our advances in modern CMake
building and provide early feedback.  The legacy support is set by default
in 1.11, when you complete build updating scripts please update the build
flags as mentioned in README.md and set -DLEGACY_BUILD=OFF.  The legacy
support will be removed at 1.12.0 release.
-- TARGET_ARCH not specified; inferring host OS to be platform compilation target
-- Building AWS libraries as shared objects
-- Generating linux build config
-- Building project version: 1.11.137
-- The CXX compiler identification is GNU 11.3.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /usr/bin/python3.9 (found version "3.9.16")
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.11")
--   Zlib library: /usr/lib64/libz.so
-- Encryption: LibCrypto
-- Found crypto: /usr/lib64/libcrypto.so
-- LibCrypto Include Dir: /usr/local/include
-- LibCrypto Shared Lib:  /usr/lib64/libcrypto.so
-- LibCrypto Static Lib:  /usr/local/lib64/libcrypto.a
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Http client: Curl
-- Found CURL: /usr/lib64/libcurl.so (found version "7.76.1")
--   Curl include directory: /usr/include
--   Curl library: /usr/lib64/libcurl.so
-- Performing Test HAVE_ATOMICS_WITHOUT_LIBATOMIC
-- Performing Test HAVE_ATOMICS_WITHOUT_LIBATOMIC - Success
-- AWS CRT C++ 0.21.0
-- The C compiler identification is GNU 11.3.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Warning (dev) at crt/aws-crt-cpp/crt/aws-c-common/CMakeLists.txt:5 (option):
Policy CMP0077 is not set: option() honors normal variables.  Run "cmake
--help-policy CMP0077" for policy details.  Use the cmake_policy command to
set the policy and suppress this warning.
For compatibility with older versions of CMake, option is clearing the
normal variable 'STATIC_CRT'.
This warning is for project developers.  Use -Wno-dev to suppress it.
-- CMake 3.20.2
-- Performing Test AWS_HAVE_GCC_OVERFLOW_MATH_EXTENSIONS
-- Performing Test AWS_HAVE_GCC_OVERFLOW_MATH_EXTENSIONS - Success
-- Performing Test AWS_HAVE_WINAPI_DESKTOP
-- Performing Test AWS_HAVE_WINAPI_DESKTOP - Failed
-- Performing Test AWS_ARCH_INTEL
-- Performing Test AWS_ARCH_INTEL - Success
-- Performing Test AWS_ARCH_ARM64
-- Performing Test AWS_ARCH_ARM64 - Failed
-- Performing Test AWS_ARCH_ARM32
-- Performing Test AWS_ARCH_ARM32 - Failed
-- Performing Test AWS_HAVE_GCC_INLINE_ASM
-- Performing Test AWS_HAVE_GCC_INLINE_ASM - Success
-- Performing Test AWS_HAVE_AUXV
-- Performing Test AWS_HAVE_AUXV - Success
-- Performing Test AWS_HAVE_EXECINFO
-- Performing Test AWS_HAVE_EXECINFO - Success
-- Performing Test AWS_HAVE_LINUX_IF_LINK_H
-- Performing Test AWS_HAVE_LINUX_IF_LINK_H - Success
-- Performing Test HAVE_M_AVX2_FLAG
-- Performing Test HAVE_M_AVX2_FLAG - Success
-- Performing Test HAVE_AVX2_INTRINSICS
-- Performing Test HAVE_AVX2_INTRINSICS - Success
-- Performing Test HAVE_MM256_EXTRACT_EPI64
-- Performing Test HAVE_MM256_EXTRACT_EPI64 - Success
-- Looking for pthread_mutexattr_init
-- Looking for pthread_mutexattr_init - not found
-- Performing Test HAS_FPIC_FLAG
-- Performing Test HAS_FPIC_FLAG - Success
-- Performing Test HAS_64BIT_FILE_OFFSET_BY_DEFAULT
-- Performing Test HAS_64BIT_FILE_OFFSET_BY_DEFAULT - Success
-- Looking for fseeko
-- Looking for fseeko - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stdbool.h
-- Looking for stdbool.h - found
-- Performing Test HAS_WGNU
-- Performing Test HAS_WGNU - Failed
-- Performing Test HAVE_SYSCONF
-- Performing Test HAVE_SYSCONF - Success
-- Looking for pthread_attr_setaffinity_np
-- Looking for pthread_attr_setaffinity_np - found
-- Performing Test PTHREAD_SETNAME_TAKES_2ARGS
-- Performing Test PTHREAD_SETNAME_TAKES_2ARGS - Success
-- Performing Test PTHREAD_GETNAME_TAKES_2ARGS
-- Performing Test PTHREAD_GETNAME_TAKES_2ARGS - Failed
-- Performing Test PTHREAD_GET_NAME_TAKES_2ARGS
-- Performing Test PTHREAD_GET_NAME_TAKES_2ARGS - Failed
-- Performing Test PTHREAD_GETNAME_TAKES_3ARGS
-- Performing Test PTHREAD_GETNAME_TAKES_3ARGS - Success
-- Building SIMD base64 decoder
-- Detected CMAKE_SYSTEM_PROCESSOR as x86_64
-- Detected 64-Bit system
-- Using libcrypto from the cmake path
-- CMAKE_AR found: /usr/bin/ar
-- CMAKE_RANLIB found: /usr/bin/ranlib
-- CMAKE_OBJCOPY found: /usr/bin/objcopy
-- feature S2N_ATOMIC_SUPPORTED: TRUE
-- feature S2N_CLONE_SUPPORTED: TRUE
-- feature S2N_CPUID_AVAILABLE: TRUE
-- feature S2N_DIAGNOSTICS_POP_SUPPORTED: TRUE
-- feature S2N_DIAGNOSTICS_PUSH_SUPPORTED: TRUE
-- feature S2N_EXECINFO_AVAILABLE: TRUE
-- feature S2N_FALL_THROUGH_SUPPORTED: TRUE
-- feature S2N_FEATURES_AVAILABLE: TRUE
-- feature S2N_KYBER512R3_AVX2_BMI2_SUPPORTED: TRUE
-- feature S2N_KYBER512R3_M256_INTRINSICS_SUPPORTED: TRUE
-- feature S2N_LIBCRYPTO_SUPPORTS_EVP_MD5_SHA1_HASH: TRUE
-- feature S2N_LIBCRYPTO_SUPPORTS_EVP_MD_CTX_SET_PKEY_CTX: TRUE
-- feature S2N_LIBCRYPTO_SUPPORTS_EVP_RC4: TRUE
-- feature S2N_LIBCRYPTO_SUPPORTS_HKDF: FALSE
-- feature S2N_LIBCRYPTO_SUPPORTS_KYBER: FALSE
-- feature S2N_MADVISE_SUPPORTED: TRUE
-- feature S2N_MINHERIT_SUPPORTED: FALSE
-- feature S2N___RESTRICT__SUPPORTED: TRUE
-- feature S2N_STACKTRACE: TRUE
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- feature S2N_KYBER512R3_AVX2_BMI2: TRUE
-- Found OpenSSL: /usr/lib64/libcrypto.so (found version "3.0.7")
-- Using libcrypto from system: /usr/lib64/libcrypto.so
-- Add s3-crt:s3 to C2J_SPECIAL_NAME_LIST
-- Considering sns
-- Looking for pathconf
-- Looking for pathconf - found
-- Looking for umask
-- Looking for umask - found
-- Adding sns to SDK build
-- Adding core to SDK build
-- Updating version info to 1.11.137
-- Custom memory management disabled
-- Performing Test CURL_HAS_H2
-- Performing Test CURL_HAS_H2 - Success
-- Performing Test CURL_HAS_TLS_PROXY
-- Performing Test CURL_HAS_TLS_PROXY - Success
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- SKIPPING:Threads::Threads
-- Configuring done
-- Generating done
-- Build files have been written to: /home/apatecstockinger/aws-sdk-cpp/build
`

Found by cmake -> openssl 3.0.7
-- Encryption: LibCrypto
-- Found crypto: /usr/lib64/libcrypto.so
-- LibCrypto Include Dir: /usr/local/include
-- LibCrypto Shared Lib: /usr/lib64/libcrypto.so
-- LibCrypto Static Lib: /usr/local/lib64/libcrypto.a

on RHEL9 these Packages from the standard repo are installed:
sudo dnf list installed|grep ssl
compat-openssl11.x86_64                       1:1.1.1k-4.el9_0                 @rhel-9-for-x86_64-appstream-rpms
openssl.x86_64                                1:3.0.7-17.el9_2                 @rhel-9-for-x86_64-baseos-rpms
openssl-devel.x86_64                          1:3.0.7-17.el9_2                 @rhel-9-for-x86_64-appstream-rpms
openssl-libs.x86_64                           1:3.0.7-17.el9_2                 @rhel-9-for-x86_64-baseos-rpms
openssl-pkcs11.x86_64                         0.4.11-7.el9                     @anaconda

@majestix508 did you have any other problems building this sdk?

Is it possible to compile with static lib on RHEL9?

I'm not sure why it wouldn't be possible. Just use the -DBUILD_SHARED_LIBS=OFF flag and let me know if you have any problems with that.


Add awsm.fish abbreviations to README.md

I feel like abbreviations is an awesome Fish feature that needs to be pushed more in front. I hope it fits the expectation of this awsm repo :).

@jorgebucaran What do you think of adding interesting abbreviations to the repo as well ˆˆ? Reading Fish Shell doc, looks like abbreviation would me a better alternative to aliases, and supports functions also.

Hey, thanks and sorry for the delay. The problem with abbreviations is that they are largely personal. For example, some might prefer "make-dir" (who knows?), others might use "md" like in your repo, or something else entirely—it's all up to them, right? Without a way to customize these, I find it less convenient for the general public. Clearly, having this as a plugin is beneficial since you can install it with Fisher, and there might be others who prefer your abbreviations over creating their own from scratch too. However, if someone wants their abbreviations merged here, how do we sort them out? How do we choose? There doesn't seem to be an objective way to decide, which is why I prefer not to have them here.
Well, an exception would be if certain abbreviations become so widely used that they are almost the de facto standard.

I also noticed that some of your abbreviations, like "ll," "/", and "~," are already supported out of the box in Fish. You might want to double-check those, as there's no point in reinventing them.

They are not my abbreviations, it's just several repos here and here. I use some, and wish to see more like we already find for ZSH. Some repos did not receive an update since a while :/.
It's definitively personal preference, that's why you can choose to add them or not, using fisher for example 8-). Like any plugin at the end of the day.
I get the point that this part may need more advanced / maintained abbreviations. Maybe we can trim? You noticed some duplicate from Fish, so I guess we can just remove this one at least. On my side I mainly use the one for Kubernetes, and I have my own.

Ah, got it, you're not the author—no worries. 👌
Just to clarify: I avoid adding abbreviations here because they vary so much based on personal taste, which is why you won't find many prompts in this repo either. It's all about quality curation, not just compiling everything and anything for Fish. While I'm not against abbreviations, I'd consider including an abbreviations plugin if it's well-supported, and thoughtfully presented, explaining why some abbreviations were chosen instead of others. It also needs to show some engagement, like users, stars, and issues.
I aim to feature only the best of the best here. I admit that this approach is not perfect since I authored many of the included plugins, like Fisher. But, that's precisely why this is a curated list—it adds a personal touch, making it my exotic collection of Fish curiosities.

Ah, yes, you make a good point about Kubernetes; those abbreviations might be more useful given the nature of Kubernetes. However, I still find them arbitrary—it's essentially just a list of abbreviations. Might as well wrap kubectl at this point (maybe, not sure). Frankly, I'm quite torn on this, and my default policy is to err on the side of exclusion, which I admit has its downsides, but that's my approach.

My request was inspired by this: https://github.com/unixorn/awesome-zsh-plugins#completions
I was not into abbreviations / aliases sharing in the past. Abbreviations / aliases lists are just some helper, for sure they are related to their owner or team. But it's like anything we add to our shell: just some add-ons we may not need that add to cover something we see as an addition. If it's ok to have several plugins, several prompts, etc. It should be ok to have abbreviations as well as it's today also part of Fish like functions. I often see central points like this repo as a major opportunity to share passion, to educate and to guide users where what they try to reach.
I'm coming from ZSH, on Fish since maybe 6 months. I love Fish + Tide, and feel like Fish is still a small community. As said in another post, your repo is actually the first one we find to extend our Fish. Maybe it could be interesting to continue to centralize all relevant information for Fish. But I understand, chosen abbreviations may lack some quality (excluding the Kubernetes one which I use every days). I was not aware of abbreviations before I've seen the plugin fish-abbreviation-tips in your list. But where are abbreviations to take advantage of it?
I hope we will see interesting repositories in the future with useful abbreviations we can all benefit from as a community :).
At the end of the day, it's your repo, and I totally respect your choice.
Thanks for answering my request Jorge :).


Read a product from the Shopcart

As a costomer
I need to read a product from my shopcart
So that I can know details of this product
Details & Assumptions:

the product exists in the shopcart

Acceptance Criteria:
Given [a product]
When [the customer need more detailed information]
Then [the customer can read a product form the shopcart]

GET /shopcarts/<customer_id>/products/<product_id>


:book: add release 0.2.1 blog post

LGTM

/hold
Waiting on https://issues.redhat.com/browse/ISV-3797

Thank you all for your reviews. Merging this PR now.


defect/VCMS65 - [Code refactor] Remove unnecessary duplicate views in the project

Removed unnecessary files in the project folder

Done


Vue Router (router-link) does not update properly if using tag

Vue.js version
<EMAIL_ADDRESS>version "2.0.3"
<EMAIL_ADDRESS>version "2.0.0"
<EMAIL_ADDRESS>version "2.0.1"
Reproduction Link
https://jsfiddle.net/b40xckws/
Steps to reproduce
Hover over link : you should see
https://fiddle.jshell.net/site/1
click on button
you will see the that the site id has changed but the link does not
What is Expected?
You should click the button and see
https://fiddle.jshell.net/site/4
What is actually happening?
You see https://fiddle.jshell.net/site/1
how to fix
Remove tag on router-link
https://jsfiddle.net/vLvvjk2p/

I took the freedom to make your example readable:
https://jsfiddle.net/Linusborg/b40xckws/2/

This is the wrong repository, please open it in the vue-router repository.
Thanks.

@LinusBorg thanks, ill do that ~

@LinusBorg should we repopen this one per response of : vuejs/vue-router#810


Add pagination to user/id/ratings

Hi!
As the title says it would be nice with pagination to users/{id}/ratings 🚀

Optional pagination will be available on /sync/ratings and /users/:id/ratings later this week. By default, all ratings will be returned, but if you send the pagination parameters, it will filter the results accordingly.


pull fails on program using ddic referencing class or interface

To reproduce

new online

repository: https://github.com/sandraros/test-abapgit
branch: ddic-ref-to-objecttype-prog-using-ddic-object

pull

Reason

abapGit first pulls DDIC then programs
While pulling DDIC objects with reference to class or interface, abapGit replaces the class or interface with generic OBJECT
When activating programs, use of class or interface members from DDIC objects does a syntax error because DDIC objects refer to generic OBJECT which doesn't have any member.
Workaround: rewrite ABAP programs so that to upcast references of DDIC objects (?=) then abapGit can pull

true. but as long as there's a separation between DDIC and other objects, there's no way to avoid this issue within abapGit (since it's a circular dependency).
Other solution that should avoid the problem: Put the code referencing the DDIC object into a class (and not a program/include).
Q: Does the issue also happen if you turn off the activation popup (https://docs.abapgit.org/guide-settings-personal.html)?

I agree that replacing the DDIC objects with types in a class or interface would definitely solve the problem (and I think I will propose a PR in abap2xlsx soon).
A: If I don't use the activation popup, it fails, and if use the activation popup I can force the activation and it's fine.
I propose also this solution in the PR above:

New activation step PRE_DDIC before DDIC: if class or interface doesn't exist, then it's created empty. It considers all classes in the repository, it doesn't check if the class or interface is used by DDIC objects.
DDIC objects which reference a class or interface don't need anymore to refer to generic OBJECT during DDIC step, and LATE step to revert back to original class or interface is not needed anymore.

Notes:

In this PR, I didn't test special types of classes like persistency classes, etc. maybe creating them empty will fail.
To risk less collateral effects, maybe we could have in the PRE_DDIC step only the classes/interfaces which are used by DDIC objects.

what if the prog uses an attribute or method of the class? creating an empty class won't work. you would still get syntax errors in the prog
Replacing the DDIC with class-types is another option but not what I meant. You should be able to refer to the DDIC object within classes since the classes are created in active version and not syntax checked (unlike progs).

The program in the test case uses a method of the class and interface. The empty class is created so that the DDIC objects can activate with the class, and during the ABAP step the class is changed with all its attributes and methods, so the program activates successfully.
OK, now I understand what you meant. Concerning the pull of abap2xlsx, 50 demo programs fail, versus 4 DDIC objects with reference to a class. I'll check what is best.

Not a fan of adding steps (a rather contemplate getting rid of all steps) but this could work for ddic with ref.

I updated #5393 so it's ready for some good testing. I will run the CI suite for a start.
abap2xlsx does not have the problem anymore after split of demos to another repo, but can you please it with #5393, please, @sandraros?

As you say, now it's solved with abap2xlsx, not sure if it's worth risking issues with the many types of classes like persistency, proxy... But at least I can help by testing it with abap2xlsx (tonight).

Test is done: latest #5393 works fine when pulling latest version of abap2xlsx (whatever abapGit setting with or without the activation popup)

Thanks. I will check other scenarios


Debian 11 & chef 18 compatibility

Description
Describe what this change achieves
Issues Resolved
List any existing issues this PR resolves
Check List

[ ] A summary of changes made is included in the CHANGELOG under ## Unreleased
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

Released as: 12.2.5


Moving window does not work in version 1903

Hi,
I read (https://github.com/sdias/win-10-virtual-desktop-enhancer/issues/131 and https://github.com/Ciantic/VirtualDesktopAccessor/issues/21) that the latest version of the DLL should resolve the problem that moving a windows doesn't work with newer builds of Windows 10. I just installed Windows 10, Version 1903 (OS Build 18362.175) and found there problem is back again. I downloaded win-10-virtual-desktop-enhancer, changed "MoveWindowToDesktop" to "Win, Alt", downloaded your latest DLL and replaced Windows.10.Virtual.Desktop.Enhancer.0.11.2/libraries/virtual-desktop-accessor.dll with your DLL. Generally win-10-virtual-desktop-enhancer works fine, but moving windows doesn't work.
Did I miss anything?
Michael.

Yeah, you missed something. I'm running: 1903 (OS Build 18362.239), moving windows between desktops works just fine. Make sure you have downloaded the latests one from the repo: https://github.com/Ciantic/VirtualDesktopAccessor/raw/master/x64/Release/VirtualDesktopAccessor.dll
(Not the releases part, I haven't updated that)
I have also tested this with the older .175 you seem to have)


Improve antichain inclusion and refactor code (renaming, suggestions)

actualised antichain_inclusion to use sync. iterator for computing post,
renamed few things, mainly incl -> inclusion
some TODO comments in the code (maybe not needed to merge all of them)

Firstly, we should do reviews, fix the arised conflict and fix python-binding.

reviewer pleaseing done

@tfiedor are you satisfied with changes?

@tfiedor are you satisfied with changes?

I trust you and Mr. L. that all that needed to be done was done.


Streaming and Asynchronous operation

This is a pretty rough example. I didn't write out a real full example. Instead, i'm highlighting sections to show async processing.
Also, I tried to use some ES6 style even tho I normally write everything in CoffeeScript. So, if you see some typos, it's because I don't normally use ES6, or even ES5, syntax.
And there are lots of variations on this. I basically wanted to show how callbacks allow asynchronous operation through all the processing and each thing handles its part.
This is also a string to string parsing, like a transpiler, instead of producing objects.
It is basically reading input from one file, sending it through a Transform which uses a Parser/Lexer, and then out to a new file. It would process data in chunks asynchronously and be good on memory.
var input = fs.createReadStream('some/input/file.blah', 'utf8')
  , target = fs.createWriteStream('some/output/file.bleh', 'utf8')
  , transform = new Transform({
      parser: buildParser()
      // if the parser is outputting objects then do the below setting.
      // in this example, we're writing out to another file, so, results are strings.
      // readableObjectMode: true
      transform: (data, encoding, done) => {
        if (Buffer.isBuffer(data) {
            data = data.toString('utf8')
        }
        // give the parser the callback to call when its done with data
        this.parser.process(data, done)
      }
  })

// and, when the parser emits a string, push it. this will only occur
// after transform() provides data and before the next() is called.
transform.parser.on('string', (string) => transform.push(string))

input.pipe(transform).pipe(target)

// each time parser.process() is called with new input, we feed it to the lexer like:
this.lexer.tokenize(data, callbackToParserWithEachToken);
// it adds `data` to any leftover data from before and then begins lexing again.
// when it has a token it gives it to the Parser's callback to process.
// if it can't produce a token from the data it has, then, it calls that callback
// without a token telling the Parser it's all done tokenizing the data it has so far.

// that callback to the parser then drives the parsing.
thatCallback: (token) => {
    if (!token) {
        // when we've received all the tokens we're going to get,
        // then tell the transform we're done with the input data we received.
        this.theTransformDoneCallback()
        return;
    }

    // otherwise, process this next token...

    // if the token leads us to a point where we now have a result to pass on,
    // some string content in this example, then emit it.
   this.emit('string', someString)

   // instead of an EventEmitter style, it could instead be a function given to the parser
   // to call when it has partial results.
   // basically, a way for the outside to use the partial result.
   // The transform would push() it.
   this.partialResult(someString);

    // then, return something back to the Lexer which called this function telling them to
    // continue, or stop, or whatever. If it provided no token then it's already stopped.
    return true
}

// as more data is given to the Transform it provides it to the Parser with its callback.
// The parser then provides the data to the Lexer with its callback.
// The callback the parser provides could change based on its current state.
// The lexer uses the callback to both provide tokens as it finds them and notify
// the parser it can't produce any more tokens from the current data.
// The parser processes a token and then returns something back to the lexer.
// When the parser is told there are no more tokens coming from the current data then
// it can call the transform's next() callback to ask for more input data.

// lastly, some flush() function is likely a good idea to tell the Parser/Lexer they have
// to finish up with what they have left.

Thanks @elidoran I will use this as a reference as I am attempting to create an example
of using Chevrotain for Async Parsing.

I Played around with creating Async APIs without much success
As I wanted to keep the Async parts in the lexer only and keep the parser as is.
The problem is that JavaScript has no mechanisms to SYNC halt execution until an async process finishes.
So once something becomes ASync the whole flow must become Async too...

I think I will revisit Async APIS after #480  (Declarative APIs) is implemented.

I appreciate you trying to figure this out and thank you for the update.
It's a difficult problem for sure. I like your idea of trying to contain it in the lexer.
It doesn't all have to be async to work with chunks of input, but, it changes how the rest works. It needs a way to hold the current state while waiting for another chunk, and, a way to restart where it left off.
The normal sync execution flow holds the state info in each called function in the call stack.  Without that, a whole different state holder is needed.
If a function doesn't have enough data to complete it must return in a way which tells the whole sync operation to return all the way back instead of moving on, and remember where it left off.
To take care of the async/streaming stuff I've been using stating (which is not a lexer/parser/grammar thing) to build a processor for my streams of structured info. It's more like building a weird state machine with functions as nodes. I used it in another package to help with the stream processing: @endeo/decoder. The sync style processor, debyte uses straight sync calls as usual expecting all the input to be available.
So, yeah, it's a lot more work supporting chunks of data instead of having it all at once and I think it makes lexer/parser stuff a whole lot more complicated when it's already complicated enough.
I do a lot of analyzing streaming data which must be processed in chunks and so far, the stating package has been helping me out immensely. I still keep an eye on parser generators tho. I checked out Myna as well.
Anyway, thank you for the update.

I appreciate you trying to figure this out and thank you for the update.

I actually investigated this months ago, but forgot to update the issue. 😢

I like your idea of trying to contain it in the lexer.

I was hoping there was a way to block until an async task finished executing and
have the Lexer asynchronously fetch more chunks when needed and the parser
to block waiting for the extra data and continue in sync execution once that data arrived.
But that does not seem to be available in JavaScript, Will need a stronger VM for that (JVM/Dot.net/...) with multi threading support.

If a function doesn't have enough data to complete it must return in a way which tells the whole sync operation to return all the way back instead of moving on, and remember where it left off.

I was thinking of using higher level abstractions for that.
Specifically Async/Await of ecmascript 2017.
    $.RULE("object", async function () {
        await $.CONSUME(LCurly);
        await $.OPTION(function () {
            await $.SUBRULE($.objectItem);
            await $.MANY(function () {
                await $.CONSUME(Comma);
                await $.SUBRULE2($.objectItem);
            });
        });
        await $.CONSUME(RCurly);
    });

This capability is available in Node.js 8.
And is short-hand syntax for wrapping everything in promises.
So if everything (Lexer  + Parser) is wrapped in promises and the lexer is "taught" to
work with chunks (it is currently stateless) than we will have a streaming parser.
The problem is that this results is quite verbose code (Chevrotain is already a little verbose)...
So I thought it would be easier to implement this using declarative APIs + code generation.
In which case a streaming parser would be (for the user) as simple as modifying a flag in the configuration.

But that does not seem to be available in JavaScript, Will need a stronger VM for that (JVM/Dot.net/...) with multi threading support.

Actually apparently JavaScript is getting some support for parallelism with sharedArrayBuffer and Atomics.wait.
And this is even supported in V8 version 6.0.
https://v8project.blogspot.co.il/2017/06/v8-release-60.html
This seems to allow blocking and resuming during a function without
using callbacks/promises. (Atomics.wait, Atomics.wake)
This still seems limited:

as it only allows sharing TypedArrays So the only data that can be communicated this way (without callbacks) are 32bit integers.

Atomics.wait is disallowed on the main thread of some(all?) browsers.

This may suffice for "pure" parsing as the Token types are already represented as positive integers.
This means:

One Webworker can stream the input text, and filled up a sharedArrayBuffer of ints that represents
The token vector.
Another Web parses the token vector synchronously and uses Atomics.wait if it runs out of input.

However users normally want to access the contents of their tokens (text,position, ect...)
But our tokens would not have this info, only an Int32 representing Type and another integer representing their position in the token vector.
So those actions would still have to be asynchronous as they will be accessing data
contained in a different process via webworker messages.
While this is not prefect it is a step forward. 😄

However users normally want to access the contents of their tokens (text,position, ect...)
But our tokens would not have this info, only an Int32 representing Type and another integer representing their position in the token vector.

This is actually not necessarily true.
Most of the information carried on a Token are 32bit integers (offset,line,column).
The only information that is harder to encode is the "image" (the text of the token).
But this too can be encoded with int32 using unicode values (4 bytes === int32).

I think that if I finish the support for custom lexer adapters (which is mostly done but was neglected)
https://github.com/SAP/chevrotain/pull/306
Then this may (???) be implemented at the lexer only level as initially intended.
The Chevrotain RegExp Lexer itself is not completely suitable for streaming because
as it is based on RegExps it can be difficult to determine how big a chunk of input is required
to ensure a match.
But there is nothing preventing end users from creating their own custom (by char) lexers.

I'm closing this for now.
Will re-visit in the future


Add revapi plugin to check public API in jbpm-services-api module

Hi, @mswiderski,
here is the revapi plugin configured for jbpm-services-api module. Thanks for justifications you made. Please wait for this PR droolsjbpm/droolsjbpm-build-bootstrap#303 to be merged, so we have the most up-to-date version tested.
Marian

jenkins retest this

jenkins retest this

jenkins retest this

jenkins retest this

I think that this can be merged now.

It would be great if someone could review this. @mswiderski could you please take a look?

@mswiderski has already provided justifications for it in my fork, so he knows about that.

@psiroky if you don't mind could you please merge when all dependencies are merged?


change api of the fucntions class

The signature of the get method does not require a
function ident as an argument any longer. The new signature:
get(schemaName, functionName, argumentTypes)

The new signature will prevent from instantiating a
function ident object upon the getting an implementation
of a fucntion.

ack


tasks: review file integrity scheduler

Review the task integrity scheduler

the scheduler might have a problem when two tasks run and use the same last_checked_date timestamp


Mess Detector configuration

Hello!

Type: code quality

In raising this pull request, I confirm the following:

[x] I have checked that another pull request for this purpose does not exist
[ ] I wrote some tests for this PR
[ ] I updated the CHANGELOG

Small description of change:

Added explicit rules for phpmd
Configured Codacy to use phpmd.xml.dist rules for analyzing project
Small php variable names refactoring
Fixed Windows CI workflow (added sqlite php extension)

Thanks

Thank you


Fix undefined function xml_convert at Database\BaseUtils

by add xml helper ported from CI3 source

It looks like this one was missed. Did you want to add the docs page for it, and add it to the helpers/index.rst in the user guide?

@jim-parry I've added documentation for it, and add MySQLi util class for class driver for it when using MySQL. It was only for PostgreSQL.


#142: Add broadcast channel

As proposed in #142 , I added a broadcast channel.
Sample implementation is at https://github.com/euphi/ESP_Heizungscontroller . (It does not make real use of it, it just logs the received message to Serial and back to MQTT).

When I'm back, I'll merge your changes and create a new pull request

Nevermind, I just fixed your PR. Thanks! 👍


what is this "PMS" does?

PMS | +++++ | - (_/) gabening intensifies..
and can you list the options that help increase fps and the one that don't, thank you

(\_/) it's an EasterEgg ;).
the more options used, the more potential for fps gain


Remove accidental configaration.rst lines

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Wrong fix, actual fix in #1089.  Closing.


Pop to specific View

View1 -> View2 -> View3 -> View4 How can I pop from View4 directly to View2 considering that we do not have control over the navigation stack ?

This framework is very use full for navigation. But I am also looking for above issue. I also want to navigate back to some specific screen

The way to do it currently would be to keep the reference to the router for each view. If you call "dismissScreen" on View3's Router, it should dismiss both View3 and View4.
The recommended approach would be to display View3 as a .sheet or .fullScreenCover, so that you could call "dismissEnvironment" to dismiss View3 and View4 (see Enter Screen Flows in the ReadMe: https://github.com/SwiftfulThinking/SwiftfulRouting).
In regards to pop to a specific view, this seems doable but it's quite difficult to implement - this isn't in the native SwiftUI framework either. I attempted it a few weeks ago and got pretty close but I need more time to implement it fully.

Thanks a lot @SwiftfulThinking

Please take care of this in ur future releases as it will be very helpful to the developers.

The way to do it currently would be to keep the reference to the router for each view. If you call "dismissScreen" on View3's Router, it should dismiss both View3 and View4.

I tried this, but it didn't seems to work for me. View1 -> View2 -> View3 -> View4. When I call dismissScreen in View4 with the router of View3, nothing happens. Is that correct?

Please take care of this in ur future releases as it will be very helpful to the developers.


What about create a PR to the dark SDK including this?

I mean, instead of having this cli to create AngularDart apps, why not forking the Dart SDK and adding an option to its dart create -t command?
like dart create -t angular myapp
what do you guys think?

Forking sounds fine for me, but I doubt upstream is going to accept this change though.


Update compatibility for ultraliser v0.4.0

This makes the necessary changes for placement-hints' mesh creation to use the current version of Ultraliser, v0.4.0

I tried beginning to run the tests, and unfortunately updating the tests for ultraliser v0.4.0 will likely be a significant pain: it seems the tests are hardcoded to use ultraliser v0.1.0 ( https://github.com/BlueBrain/atlas-placement-hints/blob/main/tests/distances/test_create_watertight_mesh.py#L19 ), and I know for a fact that ultraliser has gone through breaking changes across its versions.

The tests begin to fail when transitioning from ultraliser v0.3.0 (available in archive/2022-05, among others) to ultraliser v0.4.0. Simply changing the location of the executable causes the tests to fail. One cause of this is almost certainly because the filenames/formats that ultraVolume2Mesh expects seem to have changed when moving to v0.4.0, which is part of what I had to change in the commit in this PR.

Don't worry about this PR for now -- see https://github.com/BlueBrain/atlas-placement-hints/pull/11#issuecomment-1717238503

I've done it in #18

I guess we can close this one then?

yup, fine on my end, @asoplata?

Sure


[local_auth] throw error on LockedOut case when useErrorDialogs false

Hi, found that when useErrorDialogs: false iOS still shows the platform specific dialog on handling errors, instead of throwing an exception into the application. Should i do something more for this PR? Thanks in advance!
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[ ] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@googlebot I signed it!


Track down score_matching.py slowdown issue

What's the new feature?
Changing how enforce 2-dimensionality in the score_matching.py code slows down SteinThinning very significantly. Track down this bug. (See https://github.com/gchq/coreax/pull/746#issuecomment-2321449604)
What value does this add?
Consistent dimensionality handling without slowdown!
Is there an alternative you've considered?
No response
Additional context
No response

Was this resolved when #746 was merged?

We reverted the line of code that caused the issue. It is not resolved.


Continue button not showing up on linux build.

Continue icon not visible in the listing elements.
Might be connected to some plugins not being properly included. SVG plugin for example

works in master


deplicate code extract common method

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[x] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Welcome to contribute. Notice, please don't use Chinese to write commit message. In the Apache, English is always expected for more people readable. Thanks. @aderm

@wu-sheng ok


Persist brush size between sessions

Feature/enhancement description:

I'd like for Lorien to remeber the last brush size selected when I launch it.

You can set the default size you prefer from the settings


Add option to only scrap website if rules are available

#140

Is it worse the work to add a testcase for this?


wrong length with datasets

Hi
I have a MRPC dataset which I convert it to seq2seq format, then this is of this format:
Dataset(features: {'src_texts': Value(dtype='string', id=None), 'tgt_texts': Value(dtype='string', id=None)}, num_rows: 10)
I feed it to a dataloader:
dataloader = DataLoader(
            train_dataset,
            batch_size=self.args.train_batch_size,
            sampler=train_sampler,
            collate_fn=self.data_collator,
            drop_last=self.args.dataloader_drop_last,
            num_workers=self.args.dataloader_num_workers,
        )

now if I type len(dataloader) this is 1, which is wrong, and this needs to be 10. could you assist me please? thanks

Also, I cannot first convert it to torch format, since huggingface codes process the datasets afterwards during datacollector function to make it optimize for TPUs.

sorry I misunderstood length of dataset with dataloader, closed. thanks


add trailer video

Please add this part

Hi @KarimQaderi ,
The new parser already supports this as getPreviewVideoUrl on the anime model.
The rest api should get this in v3 soon when it is released.
Should maybe rename it to getTrailer though :)

tnx

Added! Key is trailer_url


Save and revert only if there areremapped datablocks from make_paths_absolute

Changelog Description

make_paths_absolute from openpype.hosts.blender.api.utils return remapped datablocks set
make_paths_absolute script save and revert only if there are remapped datablocks

parse_known_args return a tuple ! code fixed.


ccbuilder does not print any output

When run as a command line tool we don't see any output on the build progress. The default should be to print ninjas/make's output

Closed with https://github.com/DeadCodeProductions/ccbuilder/commit/275a05011d8f7a20bf7c21ea81ae78be100715ac


Unable to upgrade to latest version of Gatsby

Hello,
I've used this starter to learn Gatsby and develop my own site. In order to use the continuous build feature with contentful, Gatsby needs to be at the latest version. When that happens, it breaks the site and throws and error code that it Fails to Compile. Curious if you've looked into this and have any tips or tricks of what needs to change to be compatible with the latest version of Gatsby?
There was an error in your GraphQL query:

Cannot query field "contentfulAbout" on type "Query".

If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "contentfulAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/components/Footer.js

There was an error in your GraphQL query:

Cannot query field "contentfulAbout" on type "Query".

If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "contentfulAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/components/Helmet.js

There was an error in your GraphQL query:

Cannot query field "contentfulAbout" on type "Query".

If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "contentfulAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/About.js

There was an error in your GraphQL query:

Cannot query field "contentfulAbout" on type "Query".

If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "contentfulAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Landing.js

There was an error in your GraphQL query:

Cannot query field "siteMetadata" on type "Site".

If you don't expect "siteMetadata" to exist on the type "Site" it is most likely a typo.
However, if you expect "siteMetadata" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "siteMetadata" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Site":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Landing.js

There was an error in your GraphQL query:

Cannot query field "contentfulAbout" on type "Query".

If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "contentfulAbout" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Projects.js

There was an error in your GraphQL query:

Cannot query field "siteMetadata" on type "Site".

If you don't expect "siteMetadata" to exist on the type "Site" it is most likely a typo.
However, if you expect "siteMetadata" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "siteMetadata" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Site":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Writing.js

There was an error in your GraphQL query:

Cannot query field "allMediumPost" on type "Query".

If you don't expect "allMediumPost" to exist on the type "Query" it is most likely a typo.
However, if you expect "allMediumPost" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "allMediumPost" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Writing.js

There was an error in your GraphQL query:

Cannot query field "mediumUser" on type "Query".

If you don't expect "mediumUser" to exist on the type "Query" it is most likely a typo.
However, if you expect "mediumUser" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "mediumUser" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions

File: /home/alyssa/Documents/GitHub/ss-site/src/sections/Writing.js

Fixed in the latest release! #376


use getDerivedStateFromProps in vx/text to stop strict warnings

:rocket: Enhancements
vx/text gives the following warning when running in a strict react 16 build:

main.js:10481 Warning: Unsafe lifecycle methods were found within a strict-mode tree:
in StrictMode
in Unknown

componentWillMount: Please update the following components to use componentDidMount instead: Text

componentWillReceiveProps: Please update the following components to use static getDerivedStateFromProps instead: Text

Learn more about this warning here:

I've moved the initial call to updateWordsByLines into the constructor and used getDerivedStateFromProps instead of componentWillReceiveProps

Currently vx supports React 15 and 16. Updating these lifecycle methods is something that needs to happen for React 17 support and I was waiting for a React 17 release candidate to start work on upgrading all lifecycle methods.
If we landed this update in @vx/text it would me setting React peerDep to >=16.3.0 for @vx/text in the next release which would be inconsistent with the other packages. So I want to hold off on making these changes until ready to do it all at once.

@sto3psl you are absolutely right, terrible oversight from me.  I opened this PR originally but nobody responded.
I did notice the instance this first time round.  Out of curiosity, is that PR any better?

@dagda1 I'm not quite sure just from looking at it. As @hshoff already mentioned, these lifecycles won't go anywhere in a reasonable timeframe. React 17 isn't coming soon and there have been no mentions from the React team.
I'm not entirely sure if this will help with the warnings but you could try renaming the unsafe lifecycles to UNSAFE_componentWillReceiveProps and UNSAFE_componentWillUpdate.
https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops

@hshoff With the the latest release of React 16.9 is it still the plan to wait for React 17? The lifecycle methods have been renamed and will continue to work in 17 whenever it comes, which seems to be a long time away.

@denkristoffer now that 16.9 is out and folks are starting to see the warnings, I think it's time. In an upcoming release vx will have a react & react-dom peerDep of 16.3<= & =<16.9
Likely plan is to rename deprecated lifecycle methods to UNSAFE_* which will remove the warnings then follow up with migrating away from the unsafe methods.

@hshoff I'm not sure if it makes sense to use the prefixed methods. Those warnings are there for a reason.
When there are no errors I assume that I can update react without major issues
It could happen that someone hasn't upgraded VX to the newest version but upgrades react once it's released
I would just leave them and replace them as you go


ERROR: (localhost:2000) failed to read data: timed out

Hello,
When I try to run both server and client, I get few errors:

In client side is "ERROR: (localhost:2000) failed to read data: timed out".
In server side is "ERROR: tcpserver 0 : error reading message: Operation canceled" and "ERROR: tcpserver 2000 : error reading message: End of file".

I have tried to change the port, but I got the same error. Have you ever faced this problem or you know how to solve it?
Thanks in advance.

Are you executing them on the Colab remote desktop?
If you follow the tutorial until "Run Carla", does the snippet ! sudo -u colab DISPLAY=:1 vglrun /home/colab/carla/CarlaUE4.sh show any error? If not, you should see the Carla server running on the VNC desktop.
By opening a terminal in the VNC desktop, you can run a test client with:
pip install pygame
cd /home/colab/carla/PythonAPI/examples
python manual_control.py


Release v0.9.13

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/approve


Add property in service bus

[QUERY]
The 'partitionKeyExpression configuration in spring cloud stream does not work in azure-spring-cloud-stream-binder-servicebus

/azp run java - spring - tests

Please provide more info about this PR, what is this for? is there a github issue or what?

/azp run java - spring - tests

Hi, @lzc-1997-abel , please resolve the conflicts.

@chenrujun resolved

Closing this PR. Please create a new one if necessary.


LIbrary package says concretesolutions

This is using the br.com.concretesolutions package. So, I'd like to discuss two points here:

Move the library to github.com/concretesolutions
Update the package to br.com.concrete (much like we are trying to do with canarinho and next is requestmatcher).

I'd like to know what are your thoughts on these points.

I think we can update the package to br.com.concrete

Hey @cs-bruno-silva, are we already changed the package name?


Add additional info to asser for test 4135

What this PR does
Failures in unmarshal might give meaningless
messages without full context.
Example
Unexpected error:
    <*json.SyntaxError | 0xc007ee5920>:
    invalid character 'F' looking for beginning of value
    {
        msg: "invalid character 'F' looking for beginning of value",
        Offset: 1,
    }
occurred

Fixes #
Special notes for your reviewer

Release note

NONE

/cc @0xFelix

/cherry-pick release-1.3


fix: master borked arithmetic tests

dirty merge ye haw

When in doubt, change the 3's to 0's!

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit f5592b82 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,956
181,604
724,196

l1_rollup_calldata_gas
227,072
888,824
3,535,892

l1_rollup_execution_gas
320,263
1,007,272
3,756,270

l2_block_processing_time_in_ms
1,223 (+2%)
4,461
17,756

note_successful_decrypting_time_in_ms
313 (-1%)
970 (-1%)
3,626 (-1%)

note_trial_decrypting_time_in_ms
23.8 (-7%)
100 (-15%)
175 (-1%)

l2_block_building_time_in_ms
18,130 (-1%)
71,843
288,661

l2_block_rollup_simulation_time_in_ms
13,453 (-1%)
53,297
214,684

l2_block_public_tx_process_time_in_ms
4,646 (-1%)
18,469 (-1%)
73,726 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,425 (+3%)
28,970

note_history_successful_decrypting_time_in_ms
2,430 (-5%)
4,738 (-2%)

note_history_trial_decrypting_time_in_ms
92.3 (-44%)
165 (-16%)

node_database_size_in_bytes
17,285,200
33,226,832

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
327 (-1%)
44,528
25,313

private-kernel-ordering
196
43,633
16,193

base-rollup
1,455
129,774
933

root-rollup
84.2 (-2%)
4,192
729

private-kernel-inner
436
70,819
25,313

public-kernel-private-input
241
33,663
26,945

public-kernel-non-first-iteration
238
33,705
26,945

merge-rollup
8.05 (+1%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
16,859
35,484

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
549
1,439

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.495 (-3%)
574 (-1%)


evaluate.py produces different results for demo.py?

Why does running demo. py and evalevaluate. py with the same data set produce different results?
could you explain it, thanks

Hi, thanks for pointing out the issue. I also noticed that there is minor difference between bounding boxes produced by evaluate.py and demo.py.
# OTB Man sequence 0002 result
69.457,46.669,26.011,39.444  # demo.py
69.459,46.294,26.026,39.786  # evaluate.py

I recently digged into this issue and found out that got10k toolkit (evaluate.py) uses PIL to read images. On the other hand, my demo.py script reads images using opencv. This causes slight difference between pixel values of opencv and PIL images, which leads to different results. The following script reproduces this fact:
import numpy as np
import cv2
from PIL import Image
path = '../data/OTB/Man/img/0001.jpg'
cv2_img = cv2.imread(path)
cv2_img = cv2.cvtColor(cv2_img, cv2.COLOR_BGR2RGB)
pil_img = Image.open(path)
pil_img = np.array(pil_img)
print((cv2_img == pil_img).all())  # returns False

demo.py yields exactly same results as evaluate.py if you replace these lines with:
img_prev = np.array(Image.open(frames[i]))
img_curr = np.array(Image.open(frames[i+1]))

very nice, thank you very much for detailed explanation


[Controller/recorder] fix event bug

This PR is for:

Server

Fixes event bug
Steps to reproduce the bug

learn a host ip

Changes to fix the bug
Affected branches

main

Checklist

[ ] Added unit test to verify the fix.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Sprint: 47] XD-2572 Fixing configuration handling for SqoopTasklet

adding hadoop.properties settings to the configuration used by SqoopRunner

adding config properties needed for kerberos secured cluster to SqoopRunner

adding hadoop-mapreduce-client-app.jar to build for each Hadoop distro (needed for secured cluster jobhistory)

removing default connection properties when --options-file is used

Other than that played using listings and imports with kerberized and non-kerberized hadoop and it was all right. Merging...

Merged, closing.


Mac M2 Compatibility

Would it be an easy update to release a version for Mac? pip installing says it's only compatible with x86/x64 architectures. Thanks!

Thanks for the feature request! The current C code was written (by @jonashaag) with SIMD instructions that are specific to the x86-64 CPU architecture. Adding a scalar implementation and/or NEON implementation with ARM compatibility would be feasible. Once that is in place, it's mostly a matter of updating the Github Actions config file, so it builds for MacOS ARM.
I currently cannot make any promises on when or if I will make this happen. If you want to give it a stab yourself, here are some examples of changes that are similar to what would need to be done in fast-align-audio:
https://github.com/nomonosound/numpy-rms/pull/4/files
https://github.com/nomonosound/numpy-rms/pull/5/files
https://github.com/nomonosound/numpy-rms/pull/7/files

It should be relatively easy to switch to a library like https://github.com/google/highway

Thanks for the info! I'm also not sure if I have the capacity to get to this right now as it's not critical to what I'm working on. I was just hoping to find something that could efficiently time align signals when a dry signal is mixed with itself that was convolved with an IR. If the IR creates a delay, it would be nice to be able to account for this without adding much overhead.

That is indeed the use case Jonas had in mind when he originally made this


GET Route Exists returns no content

This endpoint should return some content, anything to indicate if the route exists. If that information is coming back in a header, it's not documented. If that information is in the response code, please document the response code used for false.
http://apidocs.cloudfoundry.org/226/routes/check_a_route_exists.html

Added a description section to describe the expected response codes.
http://apidocs.cloudfoundry.org/release-candidate/routes/check_a_route_exists.html


Segmentation fault in CP-SAT

What version of OR-Tools and what language are you using?
Version: v9.9.3963
Language: Python 12.1
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
I am using CP-SAT
What operating system (Linux, Windows, ...) and version?
Reproduced on Linux Mint 21, and on Linux Fedora 39 (two different computers).
What did you do?
What I did / what I am doing:
I create and solve many small-ish Cp Models in 2D packing context, and I have found at least one instance which >>sometimes<< causes a segfault.
In the terminal, the segfault just looks like this:
#14      0.03s best:17    next:[6,16]     no_lp (fixed_bools=46/189)
#15      0.03s best:16    next:[6,15]     no_lp (fixed_bools=49/189)
#16      0.04s best:15    next:[6,14]     no_lp (fixed_bools=50/191)
#17      0.04s best:14    next:[6,13]     no_lp (fixed_bools=52/193)
#Bound   0.36s best:14    next:[7,13]     max_lp
#Bound   0.37s best:14    next:[8,13]     max_lp
#Model   6.65s var:125/126 constraints:161/162
#Model   7.42s var:124/126 constraints:160/162
#Model   8.21s var:123/126 constraints:159/162
#Model   8.35s var:122/126 constraints:158/162
#Model   8.52s var:121/126 constraints:157/162
#Model   8.60s var:120/126 constraints:156/162
#Bound   8.66s best:14    next:[10,13]    no_lp
#Bound   8.69s best:14    next:[11,13]    no_lp
#Bound   8.73s best:14    next:[12,13]    no_lp
Speicherzugriffsfehler (Speicherabzug geschrieben)

To trigger this bug, the instance must be solved repeatedly, as it does not occur on every run. So, I believe it might be a race condition or similar timing-related bug.
I wrote a small script that loads the exported model proto and solves it repeatedly. The script and the model (in txt form) are appended to this issue.
model.txt
trigger_segfault.py.txt

Do you have rectangles that can have zero area ?

I ran it 50 times on main. It did not crash.

Do you have rectangles that can have zero area ?

No, this is not possible.

I ran it 50 times on main. It did not crash.

It is very unfortunate to me that you cannot reproduce the bug. As I said, I was able to reproduce this bug on two separate machines, so I am confident that this is a real issue. For me, the segfault usually occurs in the first five iterations.
Is there anything else I could provide you with to enable finding the root cause of the issue?
Maybe some information about my environments:

On both PCs I use Python 12.1
On both PCs I use conda to create and manage Python environments

I am on the main branch where I fixed some crash in the 2d packing
constraint.
Laurent Perron | Operations Research | @.*** | (33) 1 42 68 53
00
Le jeu. 21 mars 2024 à 11:10, Gabriel Gehrke @.***> a
écrit :

Do you have rectangles that can have zero area ?
No, this is not possible.
I ran it 50 times on main. It did not crash.
It is very unfortunate to me that you cannot reproduce the bug. As I said,
I was able to reproduce this bug on two separate machines, so I am
confident that this is a real issue. For me, the segfault usually occurs in
the first five iterations.
Is there anything else I could provide you with to enable finding the root
cause of the issue?
Maybe some information about my environments:

On both PCs I use Python 12.1
On both PCs I use conda to create and manage Python environments

—
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/4144#issuecomment-2011819416,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3MNSLRI6FYYUCW3IVLYZKWYJAVCNFSM6AAAAABFALKW22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJRHAYTSNBRGY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


dagger: 0.4.0 -> 0.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dagger/dagger/releases.
meta.description for dagger is: A portable devkit for CICD pipelines
meta.homepage for dagger is: https://dagger.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.1 with grep in /nix/store/zghaj7j35fm5xg814jrc36b4b873y3sj-dagger-0.4.1
found 0.4.1 in filename of file in /nix/store/zghaj7j35fm5xg814jrc36b4b873y3sj-dagger-0.4.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
dagger

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zghaj7j35fm5xg814jrc36b4b873y3sj-dagger-0.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dagger https://github.com/r-ryantm/nixpkgs/archive/8627e9d521a46539f7c7c3f557c28923b15e7dd9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zghaj7j35fm5xg814jrc36b4b873y3sj-dagger-0.4.1
ls -la /nix/store/zghaj7j35fm5xg814jrc36b4b873y3sj-dagger-0.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dagger

Maintainer pings
cc @jfroche @sagikazarmark for testing.

Result of nixpkgs-review pr 222328 run on aarch64-darwin 1

1 package built:

dagger


Update 5 modules

Update iproute2.git to 6.8.0
Update kolibri-0.16.0-py2.py3-none-any.whl to 0.16.1
Update setuptools-69.1.0-py3-none-any.whl to 69.2.0
Update wheel-0.42.0-py3-none-any.whl to 0.43.0
Update pillow-10.2.0.tar.gz to 10.3.0
🤖 This pull request was automatically generated by flathub-infra/flatpak-external-data-checker. Please open an issue if you have any questions or complaints. 🤖

Suppressed by #180


Feature Request: Display a throbber while image loads

Problem
I'm using two different source files for the smallImage and largeImage. Before an image loads, the enlargedImageContainer is just an empty transparent container.
As is, the empty container looks like a bug, and depending on the image size and connection speed it can take a second or two from mouseOver to fully load and display the image.
It'd be nice to show an indicator that the image is loading so people stick around and wait those one~two seconds.

@evannoronha - Thanks for opening this issue! I think you make a good case for your feature request. I will prioritize support for a loading animation. It will likely be in the next minor release.


Problem with RSS template

While RSS now loads in the editor, when you create a new item there is no way to add the title, link, description or pubDate fields and when you duplicate one containing these fields then they are not copied over to the duplicate.

Closing as this template is now deprecated now flash isn't supported


Change save_path when sending a torrent

When sending a torrent you should be able to change the saving path. Now this is possible using the API as explained here https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation#download-torrent-from-url
Requested via Google Play Console

Done!


Property 'viewLoaded' not found on object of type 'LTHPasscodeViewController *';

In "setDigitsCount" method Xcode warns about this error:
Property 'viewLoaded' not found on object of type 'LTHPasscodeViewController *'; did you mean 'viewIfLoaded'?

No, viewLoaded, but its getter is isViewLoaded. My mistake, but for me it works without errors or warnings. Does it work properly, though?
Will fix in next version, anyway.

Fixed in 3.8.2, e23049b2.


[cmake-user] Fix libraries check

What does your PR fix?
Amends last minutes changes in #21641:
Fixes the detection of the relevant <Pkg>_LIBRARIES variable, thus actually restoring the validation of debug vs. release configurations. (Found during work on wxwidgets.)

Which triplets are supported/not supported?

Oops, thanks @dg0yt


[Backend] error when receiving an empty string

Endpoint: api/posts/get_post
Error when receiving an empty string in query parameters.

Solved


change the permissions for /var/lib/leapp directory from '755' to '700'

The nature of the content stored in the /var/lib/leapp directory requires stricter permissions.

/rerun

/rerun


Add safeTxHash in Txs queue & history

Closes #1641.
Add safeTxHash in transaction details for queue and history.

@francovenica  @dasanra @nicosampler

[ ] Crash in PR ( not sure is it because of the current PR or something else- no such issue on staging)

rinkeby network
add safe = 0x1230B3d59858296A31053C1b8562Ecf89A2f888b
Go to the Queue
Expane tx with nonce = 540 to see details
( details about tx: it was created as contract interaction -> contract address=0x283Af0B28c62C092C9727F1Ee09c02CA627EB7F5 -> function = commit, commitment(bytes32):
0xab1247907991dd7348dbd241d1ccaca8c713e48e91175bc7398489e1628d5063 )
Current result: The app is crashed

Question
Let me know ow if it should be reported to separate issue

@francovenica @dasanra @nicosampler @katspaugh
* [x]  Crash in PR ( not sure is it because of the current PR or something else- no such issue on staging)

1. rinkeby network

2. add safe = 0x1230B3d59858296A31053C1b8562Ecf89A2f888b

3. Go to the Queue

4. Expane tx with nonce = 540 to see details
   ( details about tx: it was created as contract interaction -> contract address=0x283Af0B28c62C092C9727F1Ee09c02CA627EB7F5 -> function = commit, commitment(bytes32):
   0xab1247907991dd7348dbd241d1ccaca8c713e48e91175bc7398489e1628d5063 )
   Current result: The app is crashed
   ![image.png](https://camo.githubusercontent.com/1ecb34b61f8ce9941c02079317a32126be2bc8ca0ec27f837ca49afaa2c0f32d/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3565643735376332393435396262333662616364346262612f66646435306561622d376434622d346464612d613039342d393032356162333632613838)
   Question
   Let me know ow if it should be reported to separate issue

@liliya-soroka this was solved for the release v3.4.0 but the changes weren't in this PR yet (it wasn't updated with latest development changes)
Now it is and should be working as expected. Please remember to do a full reload of the app if you still have the issue

The issue reported is the same as this one #2136. where tx labeled as "Contract interaction" would crash upon open its details. It was fixed in version 3.4.0. Since this ticket is on the 3.3.1 version it still has that issue present.
Regarding the SafeTxHash. It works fine
The tx hash is shown in the tx details, in the queue and history tabs as well.
Tried using a SafeTxHash to execute an ApproveHash and it worked fine (just to validate the hash given)
Looks good to me


Failed to run a swarm as the generated server.pem don't have 'Client' extended key usage

Originally, I raised an issue, docker/docker#24982, as I could not follow the documentation, "Evaluate Swarm in a sandbox", https://docs.docker.com/swarm/install-w-machine/.
I created a script to follow the document to create a swarm. And the script works before, but not anymore.
Here is the script:
#!/bin/bash

function create() {
    echo "Create 3 machines"
    docker-machine create -d virtualbox --engine-opt debug manager
    docker-machine create -d virtualbox --engine-opt debug agent1
    docker-machine create -d virtualbox --engine-opt debug agent2
    docker-machine ls

    echo "Create Discovery token"
    eval "$(docker-machine env manager)"
    Token=`docker run --rm swarm create`
    echo "Service Discovery Token is ${Token}"

    echo "Create Swarm Manager"
    docker run -dt \
        --name manager \
        -p 3376:3376 \
        -v /var/lib/boot2docker:/certs:ro \
        swarm \
            -l "debug" --debug \
            manage \
                -H <IP_ADDRESS>:3376 \
                --tlsverify \
                --tlscacert=/certs/ca.pem \
                --tlscert=/certs/server.pem \
                --tlskey=/certs/server-key.pem \
                token://${Token}

    Size=2
    for i in $(seq 1 ${Size})
    do
        echo "Create Swarm Node ${i}"
        eval "$(docker-machine env agent${i})"
        docker run -d \
            --name agent \
            swarm \
                -l "debug" --debug \
                join \
                --addr="$(docker-machine ip agent${i}):2376" \
                token://${Token}
    done
}

function remove() {
    docker-machine rm -y manager agent1 agent2
}

function swarm_env() {
    echo "export DOCKER_TLS_VERIFY=1"
    echo "export DOCKER_CERT_PATH=~/.docker/machine/machines/manager"
    echo "export DOCKER_HOST=$(docker-machine ip manager):3376"
}

function main() {
    Command="$1"
    shift
    case "${Command}" in
        create) create ;;
        env)    swarm_env ;;
        remove) remove ;;
        *)      echo "Usage: $0 <create|env|remove>" ;;
    esac
}

main "$@"

My current docker-machine version is 0.8.2:
$ docker-machine -v
docker-machine version 0.8.2, build e18a919

After the swarm was created, the docker info showed me the swarm nodes are not working:
$ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: swarm/1.2.5
Role: primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint
Nodes: 2
 (unknown): <IP_ADDRESS>:2376
  └ ID:
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels:
  └ UpdatedAt: 2016-12-03T01:17:41Z
  └ ServerVersion:
 (unknown): <IP_ADDRESS>:2376
  └ ID:
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels:
  └ UpdatedAt: 2016-12-03T01:17:41Z
  └ ServerVersion:
Plugins:
 Volume:
 Network:
Swarm:
 NodeID:
 Is Manager: false
 Node Address:
Security Options:
Kernel Version: 4.4.27-boot2docker
Operating System: linux
Architecture: amd64
CPUs: 0
Total Memory: 0 B
Name: 5454869d197e
Docker Root Dir:
Debug Mode (client): false
Debug Mode (server): false
WARNING: No kernel memory limit support

And the logs of swarm container on the manager node shows following errors:
DEBU[1900] Failed to validate pending node: The server probably has client authentication (--tlsverify) enabled. Please check your TLS client certification settings: Get https://<IP_ADDRESS>:2376/info: remote error: bad certificate  Addr=<IP_ADDRESS>:2376
DEBU[1900] Failed to validate pending node: The server probably has client authentication (--tlsverify) enabled. Please check your TLS client certification settings: Get https://<IP_ADDRESS>:2376/info: remote error: bad certificate  Addr=<IP_ADDRESS>:2376

@dongluochen decided to change the swarm documentation instead (docker/swarm#2442), by using docker-machine's --swarm option, so the issue was closed.
But I still don't think that is a fix for the original problem, the original document worked fine just months ago, and had more details of how the swarm was created without hiding too much details in --swarm option.
So, I'm not giving up, after I understand more about docker-machine, I gave it another try. then I found out the commit c0b721b in docker machine, which is "Disable extended key usage as a client for non-Swarm-master server certs", caused the problem.
-		template.ExtKeyUsage = []x509.ExtKeyUsage{x509.ExtKeyUsageClientAuth, x509.ExtKeyUsageServerAuth}
 -		for _, h := range hosts {
 +		template.ExtKeyUsage = []x509.ExtKeyUsage{x509.ExtKeyUsageServerAuth}
 +		if opts.SwarmMaster {
 +			// Extend the Swarm master's server certificate
 +			// permissions to also be able to connect to downstream
 +			// nodes as a client.
 +			template.ExtKeyUsage = append(template.ExtKeyUsage, x509.ExtKeyUsageClientAuth)
 +		}

So, if I followed the documentation, create a docker host without using --swarm-master option, the generated server.pem will not have TLS Web Client Authentication.
Here is the difference in the server.pem between normal docker-machine create and docker-machine create --swarm-master:
         X509v3 extensions:
             X509v3 Key Usage: critical
                 Digital Signature, Key Encipherment, Key Agreement
             X509v3 Extended Key Usage:
-                TLS Web Server Authentication
+                TLS Web Server Authentication, TLS Web Client Authentication
             X509v3 Basic Constraints: critical
                 CA:FALSE
             X509v3 Subject Alternative Name:

That's the reason why it works before, as it used to generate both extended usage, but now it only generate TLS Web Server Authentication unless --swarm-master is specified.
Without having TLS Web Client Authentication extended usage, there is no easy way to create a working swarm, unless I regenerated the certs by myself.
So, please enable the TLS Web Client Authentication for server.pem.

what about a patch? could you write one?

@tronicum Sure, I just created a PR #3938 for this issue.

This also happens if you regenerate certs on an existing cluster, is there no way to pass something like --swarm-master when regenerating the certs?


[BugFix] replace comment to a space when remove it

Signed-off-by: packy<EMAIL_ADDRESS>What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

We should replace the comment to a space when we remove it. If not, sql like
select * from-- comments
t1

will transform to wrong sql like
select * fromt1

The 2.5 or latest version use new parser to process the comment and don't have this problem.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_fe_unittest

run starrocks_fe_unittest

@mergify backport branch-2.3


Adding the feature to "tag" a user or a message

Users, in order to continue a conversation on a particular topic or with a particular person, can tag that message or the person's username. I would like to work on this feature.

Sure! Assigned it to you


CI should not run on draft PRs

@dkarnikis, @nvasilakis I think that CI should not be invoked in draft PRs, since they are supposed to be volatile, therefore leading to too many CI invocations. The DCO should probably be run though.

Agreed!

Thanks for the feedback! CI now does not execute on draft PR's unless they are ready for review! DCO runs regardless of the CI.