fail to build using docker

Description
Tried building library using docker through the command: python3 ci/build.py -p armv7 but compilation failed because it seems docker is pulling some binaries from and old repository (jessie). Tried running the same code with --force-yes with the same result.
Also tried to compile directly on Raspberry pi, but it fails because of insufficient VM, even after I increased it to 4096M. I'll move to cross-compilation next.
Error Message
WARNING: The following packages cannot be authenticated!
autoconf
E: There are problems and -y was used without --force-yes
The command '/bin/sh -c /work/deb_ubuntu_ccache.sh' returned a non-zero code: 100
Traceback (most recent call last):
File "ci/build.py", line 454, in
sys.exit(main())
File "ci/build.py", line 364, in main
num_retries=args.docker_build_retries, no_cache=args.no_cache)
File "ci/build.py", line 116, in build_docker
run_cmd()
File "/Volumes/External/mxnet/ci/util.py", line 81, in f_retry
return f(*args, **kwargs)
File "ci/build.py", line 114, in run_cmd
check_call(cmd)
File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 363, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['docker', 'build', '-f', 'docker/Dockerfile.build.armv7', '--build-arg', 'USER_ID=501', '--build-arg', 'GROUP_ID=20', '--cache-from', 'mxnetci/build.armv7', '-t', 'mxnetci/build.armv7', 'docker']' returned non-zero exit status 100.
To Reproduce
Just run python3 ci/build.py -p armv7
Steps to reproduce
(Paste the commands you ran that produced the error.)

Just run python3 ci/build.py -p armv7

What have you tried to solve it?

Added --force-yes when installing autoconf
Added https package just in case authentication was due to https site
Realized that autoconf may not be available because jessie distribution may be too old?

Environment
We recommend using our script for collecting the diagnositc information. Run the following command and paste the outputs below:
curl --retry 10 -s https://raw.githubusercontent.com/dmlc/gluon-nlp/master/tools/diagnose.py | python

# paste outputs here

----------Python Info----------
Version      : 3.7.5
Compiler     : Clang 11.0.0 (clang-1<IP_ADDRESS>)
Build        : ('default', 'Nov  2 2019 10:02:20')
Arch         : ('64bit', '')
------------Pip Info-----------
Version      : 19.3.1
Directory    : /Volumes/External/pyenv/tvmenv/lib/python3.7/site-packages/pip
----------MXNet Info-----------
Version      : 1.4.1
Directory    : /Volumes/External/pyenv/tvmenv/lib/python3.7/site-packages/mxnet
An error occured trying to import mxnet.
This is very likely due to missing missing or incompatible library files.
Traceback (most recent call last):
File "", line 122, in check_mxnet
AttributeError: module 'mxnet.util' has no attribute 'get_gpu_count'
----------System Info----------
Platform     : Darwin-19.0.0-x86_64-i386-64bit
system       : Darwin
node         : Catalyst-RD.local
release      : 19.0.0
version      : Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64
----------Hardware Info----------
machine      : x86_64
processor    : i386
b'machdep.cpu.brand_string: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz'
b'machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C'
b'machdep.cpu.leaf7_features: RDWRFSGS TSC_THREAD_OFFSET BMI1 AVX2 SMEP BMI2 ERMS INVPCID FPU_CSDS MDCLEAR IBRS STIBP L1DF SSBD'
b'machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT RDTSCP TSCI'
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0310 sec, LOAD: 0.4920 sec.
Timing for GluonNLP GitHub: https://github.com/dmlc/gluon-nlp, DNS: 0.0005 sec, LOAD: 0.5698 sec.
Timing for GluonNLP: http://gluon-nlp.mxnet.io, DNS: 0.0007 sec, LOAD: 0.0289 sec.
Timing for D2L: http://d2l.ai, DNS: 0.0008 sec, LOAD: 0.3076 sec.
Timing for D2L (zh-cn): http://zh.d2l.ai, DNS: 0.0006 sec, LOAD: 0.1726 sec.
Timing for FashionMNIST: https://repo.mxnet.io/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0007 sec, LOAD: 0.3055 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0089 sec, LOAD: 1.1580 sec.
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0005 sec, LOAD: 0.1895 sec.

Tried to fix the error by adding:
apt update && apt-key update && apt install -y --no-install-recommends
to deb.ubuntu.ccache.sh before autoconf is installed. That sort of worked but now it seems that asciidoc was not installed because:
/usr/bin/gcc -std=gnu99 -g -O2 -Wall -W -Werror -o ccache src/main.o src/args.o src/ccache.o src/cleanup.o src/compopt.o src/conf.o src/counters.o src/execute.o src/exitfn.o src/hash.o src/hashutil.o src/language.o src/lockfile.o src/manifest.o src/mdfour.o src/stats.o src/unify.o src/util.o src/version.o src/getopt_long.o src/hashtable.o src/hashtable_itr.o src/murmurhashneutral2.o src/snprintf.o   -lm  -lz

make install
asciidoc -a revnumber=3.4.2 -d manpage -b docbook -o - doc/MANUAL.adoc |
perl -pe 's!(.*?)!\1!g' >doc/MANUAL.xml
/bin/sh: 1: asciidoc: not found
a2x --doctype manpage --format manpage doc/MANUAL.xml
make: a2x: Command not found
dev.mk:175: recipe for target 'doc/ccache.1' failed
make: *** [doc/ccache.1] Error 127
The command '/bin/sh -c /work/deb_ubuntu_ccache.sh' returned a non-zero code: 2
Traceback (most recent call last):
File "ci/build.py", line 454, in
sys.exit(main())
File "ci/build.py", line 364, in main
num_retries=args.docker_build_retries, no_cache=args.no_cache)
File "ci/build.py", line 116, in build_docker
run_cmd()
File "/Volumes/External/mxnet/ci/util.py", line 81, in f_retry
return f(*args, **kwargs)
File "ci/build.py", line 114, in run_cmd
check_call(cmd)
File "/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 363, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['docker', 'build', '-f', 'docker/Dockerfile.build.armv7', '--build-arg', 'USER_ID=501', '--build-arg', 'GROUP_ID=20', '--cache-from', 'mxnetci/build.armv7', '-t', 'mxnetci/build.armv7', 'docker']' returned non-zero exit status 2.
(docker) alopez@Catalyst-RD>

I believe ci/build.py is not suppported outside of the CI environment. So I'm closing the issue.
Do you have any issues with cross-compile?

Its just that from some of the discussions in the forum it was suggested to use this CI capability to build a library for the raspberry Pi. Cross compilation will take me a bit longer to do and since currently the documentation is missing from the master branch I was not sure which was the sanctioned way of generating the library for the Pi.
I did try to use the precompiled version (mxnet-1.5.0-py2.py3-none-any.whl) of the library but it does not support OpenCV.
Ill try cross-compilation then.
Thanks!

@alopez1327 can you link the relevant discussion. Maybe @marcoabreu can clarify how to use the Docker container build setup

We used to show build.py as preferred build method on the devices-installation-dialog, but now it seems like it's gone.
Generally, the script should also work locally since it's dockerize. Especially considering that we're actively running it in CI, the error seems worth investigating. One thing I'm thinking of is that we're not running into it due to our caching, but once our cache breaks, we'll face the same error. Thus, I'd recommend to look into this error since otherwise it could knock off CI if the cache gets invalidated.

@zachgk assign @larroy

@larroy Please comment if you want to take this issue.

I'm quite short with time but I can try to chime in.

I built the latest from master without any problems, did you update submodules?
time ci/build.py -p armv7
...
2019-11-21 22:04:06,620 - root - INFO - Waiting for status of container 8ff0cb9f431b for 600 s.
2019-11-21 22:04:07,090 - root - INFO - Container exit status: {'Error': None, 'StatusCode': 0}
2019-11-21 22:04:07,091 - root - INFO - Container exited with success 👍
2019-11-21 22:04:07,091 - root - INFO - Stopping container: 8ff0cb9f431b
2019-11-21 22:04:07,092 - root - INFO - Removing container: 8ff0cb9f431b
0.71user 0.22system 3:34.27elapsed 0%CPU (0avgtext+0avgdata 65920maxresident)

I checked out master and updated the submodules, and encountered the same error originally reported by alopez1327. My steps:
git clone https://github.com/apache/incubator-mxnet
cd incubator-mxnet/
git submodule update --init --recursive
time ci/build.py -p armv7
...
The following packages will be upgraded:
  autoconf
1 upgraded, 1 newly installed, 0 to remove and 84 not upgraded.
Need to get 1169 kB of archives.
After this operation, 2502 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  autoconf
E: There are problems and -y was used without --force-yes
The command '/bin/sh -c /work/deb_ubuntu_ccache.sh' returned a non-zero code: 100
Traceback (most recent call last):
  File "ci/build.py", line 454, in <module>
    sys.exit(main())
  File "ci/build.py", line 364, in main
    num_retries=args.docker_build_retries, no_cache=args.no_cache)
  File "ci/build.py", line 116, in build_docker
    run_cmd()
  File "/Users/[NAME]/dev/incubator-mxnet/ci/util.py", line 81, in f_retry
    return f(*args, **kwargs)
  File "ci/build.py", line 114, in run_cmd
    check_call(cmd)
  File "/Users/[NAME]/anaconda3/envs/heard/lib/python3.7/subprocess.py", line 347, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['docker', 'build', '-f', 'docker/Dockerfile.build.armv7', '--build-arg', 'USER_ID=501', '--build-arg', 'GROUP_ID=20', '--cache-from', 'mxnetci/build.armv7', '-t', 'mxnetci/build.armv7', 'docker']' returned non-zero exit status 100.
      395.68 real         1.28 user         0.96 sys

This also affects the CI.
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-17031/13/pipeline/
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-17031/14/pipeline/
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-17031/15/pipeline/
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-17031/16/pipeline/

My PR updates ubuntu_arm.sh script (https://github.com/apache/incubator-mxnet/pull/17031/commits/dc4e18a61d6c30b80f4265686f7f740aa8182973), thus the cached Docker container can't be reused and is rebuilt. The build fails due to this issue.
CC @larroy

@larroy the reason that ci/build.py -p armv7 works is that it uses the cache.
Would there be any problem to switch to the updated dockcross images? They recently moved to debian stretch: https://github.com/dockcross/dockcross/commit/aae501313ef206b769b0204067cebd1604029fcd
Why do we need mxnetcipinned and where is it maintained? I couldn't find it at https://github.com/apache/incubator-mxnet-ci/search?q=mxnetcipinned&unscoped_q=mxnetcipinned

when we tracked dockcross directly it was breaking CI randomly. That's why it's pinned. Anyone can update this via PR.

This is correct, to reproduce container rebuild:
piotr@44-229-42-241:0: ~/mxnet [upstream_master]> time ci/build.py -p armv7 --no-cache 2>&1 | tee armv7.log

As part of https://github.com/apache/incubator-mxnet/issues/16753, the docker containers have been updated and switched to the upstream version. Thus this issue can be closed.
I opened https://github.com/apache/incubator-mxnet/issues/17151 to track pinning the upstream containers again @larroy


Forward-merge branch-23.04 to branch-23.06

Forward-merge triggered by push to branch-23.04 that creates a PR to keep branch-23.06 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.

SUCCESS - forward-merge complete.


Show free memory with and without buffer/cache

The  live pie charts was showing free memory based on buffer/cache after you changed it in #908. You then changed it back so it won't include the buffer/cache in free memory but sometimes it would be nice to know how much the buffer/cache are using.
How about a second indicator inside the memory pie chart that will show how much free memory i have without including the buffer/cache as you do now?

Hi,
Happy New Year!
I'll have to check if WebminCore supplies this data. In case it does, I would be able to make it displayed somehow with the future Dashboard update.

Ref.: Todo #2 https://github.com/qooob/authentic-theme/issues/896


K-Means - Base

Solution for issue#10 and issue#6 (partially).

@ashwani-rathee is it good now?

@SatYu26 It's clear from my side,let's wait for a update from our admin@geekquad

@SatYu26 It's clear from my side,let's wait for a update from our admin @geekquad

Sure sir. Thank you!

Amazing work @SatYu26. Keep coding :)

Thank you sir.!!


Felix supports authenticating with user/password etcd

Description

Calico-Felix does not support authenticating username and password with etcd. As the result, the Etcd cluster can not be enabled in authenticated mode. we can't set role base access to every Felix agent. When Felix agent is hacked, a hacker can change rules and execute more actions.

Todos

[x] Add configuration username password to felix agent
[x] example /etc/calico/felix.cfg file

DatastoreType=etcdv3
EtcdEndpoints=https://<IP_ADDRESS>:2379
EtcdCertFile=/home/bienkma/tmp/server.crt
EtcdCaFile=/home/bienkma/tmp/ca.pem
EtcdKeyFile=/home/bienkma/tmp/server.pem
LogPrefix=/var/log/calico/felix.log
EtcdUsername=calico-ro
EtcdPassword=change_me

 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.bienkma 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.

Hey @bienkma ! Sorry for the delay. We'll need to look at this PR.
I don't recall how etcd auth is handled in the other Calico components but is the approach in this PR the same?
I wonder if we'll need to update the calico-etcd manifest as well (https://projectcalico.docs.tigera.io/manifests/calico-etcd.yaml)

Hi @lmm
I have not just seen what you mention. I created the PR when setup calico-Felix on VM/Physical server for hostEndpoint and grant policy. I didn't test with Kubernetes and other components

@bienkma We definitely already have that support, because it is used when Felix is run with OpenStack.  I will try to find a pointer for you...

@bienkma You should be able to specify an etcd username and password with these environment variables:
CALICO_ETCD_USERNAME or ETCD_USERNAME
CALICO_ETCD_PASSWORD or ETCD_PASSWORD
Please give those a try.

@bienkma You should be able to specify an etcd username and password with these environment variables: CALICO_ETCD_USERNAME or ETCD_USERNAME CALICO_ETCD_PASSWORD or ETCD_PASSWORD Please give those a try.

I don't remember exactly the calico-felix version which I did on 04/2022 but I tried those environment and not work. Note: I only use calico-felix to manage iptables policy on VM/Physical server.

Yep, I believe these are the config values that we would expect to work:  https://github.com/projectcalico/calico/blob/177db3b4babbbfe0a027d9770c1deb6af65fec42/libcalico-go/lib/apiconfig/apiconfig.go#L54-L55
Should work for VM / physical server use-case. I think we'll need to dig into why those didn't work for you before we merge any changes here.

@bienkma , If you're still seeing issues with this, would you mind opening an issue so we can follow up with it there? I think in light of the changes we already have, these might not be the right changes so I'll close this, but we can always reopen this if needed.


⚡ Write a deepgramTopicDetection() Function using node #4455

A Node Cloud Function that detect list of topic from spoken audio using Deepgram API.
https://github.com/appwrite/appwrite/issues/4455

Thank you so much for the PR 🤩. We're adding the hacktoberfest-accepted label to ensure this PR counts towards your Hacktoberfest contributions count. With that said, please stay active on this PR to address any comments once you receive a review. Happy Hacktoberfest! 🎃

Thanks for adding 🎃.
I am active on this PR

@stnguyen90
✅Fixed the compatibility issues with Appwrite.
One issue is related to deepgram sdk as it does not providing the proper error message if the fileUrl is incorrect or the API key.
IF required the it can be fixed by removing the sdk and using the fetch API directly.

Thanks  🎉🎉


Remove Papr - it's no longer functional on this repo

Necessary to land further commits in this branch

We need to land this prior to #2890

LGTM, assuming happy tests

Is the integration failure a known issue or a flake?

Rerunning. This branch is months old, so I'm no longer sure what flakes to expect on it.

All green here now :)

/lgtm


Remove the CFE package opt-out whitelist

"/sdk/pkg/front_end/lib/src/fasta/source/source_library_builder.dart" currently has a whitelist of packages that live in the SDK in order to opt them out of NNBD. I think this was set up before CFE had support for the package_config.json file.
It does support that now, I believe, and there is a package_config.json file checked in for the repo that sets every package to a language version that matches what its pubspec requests. Can we remove this whitelist? We are starting to trial migrate packages to null-safety, and right now we have to comment them out in CFE in order to get it to treat them as opted in.
cc @stereotype441

Duplicate of #40775


[AGE-274] Evaluation: Rerun a cancelled job

Is your feature request related to a problem? Please describe.
We want to be able to rerun a cancelled evaluation job by specifying the evaluation ID and job ID.
Describe the solution you'd like

Add a meta (of type Dict) in the Evaluation db model to store store extra backend-specific information
When retrieving the created evaluation from the database, include the Job ID in the return
Implement a POST endpoint for rerunning the evaluation job

AGE-274

Closing this issue as completed will resolve the second issue addressed https://github.com/Agenta-AI/agenta/issues/1196.

Done


ACME doesnt work with http_proxy

Installation
Netflow
Inbound
Request --> EIP-A --> ELB --> Ingress --> Container
Outbound
Container (Cert-Manager) --> ECS (proxy) --> EIP-B --> requested URL
Environment details
Docker Network: <IP_ADDRESS>/16
Cluster Network: <IP_ADDRESS>/16
Outbound traffic is disabled and only possible through the proxy: http://proxy.frontend.example.com:8080
SHARED_SNAT is disabled
example.com is just a replacement for our TLD
values.yaml
installCRDs: true
rbac:
  create: true
global:
  imagePullSecrets:
    - name: default-secret
http_proxy: http://proxy.frontend.example.com:8080
https_proxy: http://proxy.frontend.example.com:8080
no_proxy: <IP_ADDRESS>,localhost,<IP_ADDRESS>/16,<IP_ADDRESS>/16
startupapicheck:
  enabled: true
  serviceAccount:
    create: true
  image:
    pullPolicy: Always
  securityContext:
    runAsNonRoot: true
  timeout: 1m
  backoffLimit: 4
  jobAnnotations:
    helm.sh/hook: post-install
    helm.sh/hook-weight: "1"
    helm.sh/hook-delete-policy: hook-succeeded
cainjector:
  image:
    pullPolicy: Always
prometheus:
  enabled: true
  servicemonitor:
    enabled: true
resources:
  requests:
    cpu: 10m
    memory: 32Mi

Kubernetes Resources
Cluster-/Issuer
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  labels:
    name: letsencrypt-staging
  name: letsencrypt-staging
spec:
  acme:
    email<EMAIL_ADDRESS>    preferredChain: ''
    privateKeySecretRef:
      name: letsencrypt-staging
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    solvers:
      - http01:
          ingress:
            class: nginx

Ingress
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-staging
  labels:
    name: anyservice
  name: anyservice
  namespace: auth
spec:
  rules:
    - host: idms.example.com
      http:
        paths:
          - backend:
              service:
                name: anyservice
                port:
                  number: 8080
            path: /
            pathType: Prefix
  tls:
    - hosts:
        - idms.example.com
      secretName: idms.example.com-cert

Error
Kube resources
$ kubectl get challenges,orders,certificaterequests,certificates,clusterissuers,issuers,certificatesigningrequests
NAME                                                               STATE   AGE
order.acme.cert-manager.io/idms.example.com-cert-b8x2j-824733948           15m

NAME                                                             APPROVED   DENIED   READY   ISSUER                REQUESTOR                                         AGE
certificaterequest.cert-manager.io/idms.example.com-cert-b8x2j   True                False   letsencrypt-staging   system:serviceaccount:cert-manager:cert-manager   15m

NAME                                                READY   SECRET                  AGE
certificate.cert-manager.io/idms.example.com-cert   False   idms.example.com-cert   77m

NAME                                                READY   AGE
clusterissuer.cert-manager.io/letsencrypt-staging           15m

$ kubectl describe clusterissuer
Name:         letsencrypt-staging
Namespace:
Labels:       name=letsencrypt-staging
Annotations:  <none>
API Version:  cert-manager.io/v1
Kind:         ClusterIssuer
Metadata:
  Creation Timestamp:  2021-09-14T16:00:34Z
  Generation:          1
  Managed Fields:
    API Version:  cert-manager.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .:
          f:name:
      f:spec:
        .:
        f:acme:
          .:
          f:email:
          f:preferredChain:
          f:privateKeySecretRef:
            .:
            f:name:
          f:server:
          f:solvers:
    Manager:         kubectl-replace
    Operation:       Update
    Time:            2021-09-14T16:00:34Z
  Resource Version:  3091502
  Self Link:         /apis/cert-manager.io/v1/clusterissuers/letsencrypt-staging
  UID:               ce0050ac-9c51-4883-9b81-2d143f01bffc
Spec:
  Acme:
    Email<EMAIL_ADDRESS>    Preferred Chain:
    Private Key Secret Ref:
      Name:  letsencrypt-staging
    Server:  https://acme-staging-v02.api.letsencrypt.org/directory
    Solvers:
      http01:
        Ingress:
          Class:  nginx
Events:
  Type     Reason         Age                  From          Message
  ----     ------         ----                 ----          -------
  Warning  ErrInitIssuer  4m45s (x8 over 16m)  cert-manager  Error initializing issuer: context deadline exceeded

Cert-Manager logs
E0914 16:06:59.180314       1 controller.go:163] cert-manager/controller/clusterissuers "msg"="re-queuing item due to error processing" "error"="context deadline exceeded" "key"="letsencrypt-staging"
E0914 16:11:12.101063       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="auth/idms.example.com-cert-b8x2j-824733948"
I0914 16:11:59.180801       1 setup.go:219] cert-manager/controller/clusterissuers "msg"="ACME server URL host and ACME private key registration host differ. Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="cert-manager" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
E0914 16:12:09.181147       1 setup.go:259] cert-manager/controller/clusterissuers "msg"="failed to register an ACME account" "error"="context deadline exceeded" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="cert-manager" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
I0914 16:12:09.181172       1 conditions.go:95] Setting lastTransitionTime for Issuer "letsencrypt-staging" condition "Ready" to 2021-09-14 16:12:09.181166651 +0000 UTC m=+4716.830433333
E0914 16:12:09.181200       1 sync.go:60] cert-manager/controller/clusterissuers "msg"="error setting up issuer" "error"="context deadline exceeded" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
E0914 16:12:09.181348       1 controller.go:163] cert-manager/controller/clusterissuers "msg"="re-queuing item due to error processing" "error"="context deadline exceeded" "key"="letsencrypt-staging"

Proxy logs
{
  "time": "2021-09-14T14:32:02+0000",
  "client_ip": "<IP_ADDRESS>",
  "Method": "CONNECT",
  "Request_URL": "acme-staging-v02.api.letsencrypt.org:443",
  "HTTP_Version": "1.1",
  "HTTP_Code": "503",
  "Request_Header": "User-Agent: Go-http-client/1.1\r\nHost: acme-staging-v02.api.letsencrypt.org:443\r\n",
  "Response_Header": "-"
}

Expected behaviour

Cert-Manager outbound traffic uses the proxy (issuer, certificate request etc)
issuer could be created

Steps to reproduce the bug

Remove proxy variables
enable shared-SNAT (unblocked outbound traffic)
valid certificate got succesfully created
Disable SNAT
add proxy variables to cert-manager again
delete  tls-secret containing the valid certificate
error as described

Anything else we need to know?

same issue when using letsencrypt-prod
ingress-nginx

app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/version: 0.44.0
helm.sh/chart: ingress-nginx-3.25.0

Error looks similar to #4452

Environment details

Kubernetes version: v1.19.8
Cloud-provider/provisioner: OpenTelekomCloud
cert-manager version: v1.5.3
Install method: helm through Kapitan

/kind bug

stupid me. Everything works as expected.
Issue was to missread the proxy logs. The 503 was from the proxy itself.

Hi! I was able to run cert-manager-controller with https_proxy turned using mitmproxy. The "new account" succeeds on my side:
POST https://acme-v02.api.letsencrypt.org/acme/new-acct HTTP/1.1
...

HTTP/1.1 200 OK
Server: nginx
Content-Type: application/json
Boulder-Requester: 189994420

{
  "contact": [
<EMAIL_ADDRESS>  ],
  "status": "valid"
}

I noticed from the proxy logs
{
  "HTTP_Code": "503",
}

Is that expected?

Context could mean your not connected to the internet in any means. This has nothing to do with cert-manager. Please ask your Cloud Provider.

It's fully connected everything is working fine I have other setups too
which I run on my cluster.
I just need to connect them to valid ssl.
On Sun, 17 Oct, 2021, 9:56 pm Danny, @.***> wrote:

Context could mean your not connected to the internet in any means. This
has nothing to do with cert-manager. Please ask your Cloud Provider.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/4455#issuecomment-945154012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAFREB2BINJC45H574XEFTUHL2LHANCNFSM5EARLQAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Add ability to change nonce while transaction is pending

Similar to increasing fee, could users change their nonces while a transaction is pending?

I'm pretty sure this isn't possible. Replace-by-fee works by nonce, and only non-nonce values can be updated post-broadcast.
cc/ @kantai @lgalabru to confirm


chore: bump SAST to 0.0.52

This PR also updates the test to make them compatible with Mariana Trench.

@edoardopirovano , @linpengzhang , I don't understand why we get the failure ERROR unable to check updates: 403 Forbidden here. Could this be related to the Lacework CLI?

@jeremydubreil Looks like there's a failure in SAST now: https://github.com/lacework/code-security-action/actions/runs/5798923878/job/15720824962?pr=88#step:5:554

Thanks! I will investigate.


Target federated_proto is not installed, resulting in missing library dependency missing

When PLUGIN_FEDERATED is set to ON, target federated_proto is built and linked to the main xgboost target. However, no installation rule is specified for federated_proto. Thus, on a Linux platform, when BUILD_SHARED_LIBS is set to ON, the installed libxgboost.so will link with libfederated_proto.so but cannot find it in its installation path.
Steps to reproduce:
cd xgboost && mkdir build && cd build
cmake -DPLUGIN_FEDERATED=ON -DBUILD_WITH_CUDA_CUB=ON -DUSE_CUDA=ON -DUSE_NCCL=ON \
    -DCMAKE_INSTALL_PREFIX=install -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Release ..
cmake --build . --config Release
cmake --install . --config Release
ldd install/lib/libxgboost.so | grep federated

The output for the last command will then be
        libfederated_proto.so => not found

which is not expected.
This issue can be constantly reproduced with current master(8e76f5f). My environment is Archlinux, with all packages installed from official repository and having version as of date 2022-11-07. Required packages are installed using pacman -S base-devel cmake cuda nccl grpc. CUDA version is 11.8 and GCC version is 12.2.

@rongou Could you please help take a look when you are available?

In my environment I'm seeing both libdmlc.so and libfederated_proto.so as not found.

Never mind, libdmlc.so is indeed copied, just need to run ldconfig for it to show up. I think I have a fix for libfederated_proto.so, sending a PR.


Ensure scanner last err is checked

A scanner's last error should always be checked.  This ensures a proper scan completes successfully.

Can one of the admins verify this patch?

@jhendrixMSFT - hmm not clear what you mean? I opened this against master which I figured was latest? Which branch do you want it against?

@deckarep We have a branch called latest which is where we stage changes before merging them into master.  Looks like our CONTRIBUTING file is missing this bit of info, sorry for the confusion we'll get that fixed.

@jhendrixMSFT - ah ok got it....I’ll get it done at some point this evening.

Closing this PR in favor of: https://github.com/Azure/azure-sdk-for-go/pull/3154 which is based off the latest branch.


Participants of the Channel are not able to join the Meeting

I created an online meeting using graph API in my one of the channel in the Teams.
I am following the example given here. Create Online Meeting in the channel of the team
Below are the API request and its body.
Request: https://graph.microsoft.com/beta/me/onlineMeetings/
Body:
{
  "startDateTime":"2019-10-30T06:45:00Z",
  "endDateTime":"2019-10-30T06:50:00Z",
  "subject":"Test Meeting",
  "chatInfo": {
<EMAIL_ADDRESS>  },
  "accessLevel":"everyone"
}

The meeting is created successfully and it is also shown on the channel. However, users are not able to join the meeting by clicking on it as nothing happens when the user clicks on the meeting.

Can anyone let me know what am I missing here?

Could you please try to set your AcceeLevel  parameter to SameEnterprise and test the same?

Hi @Trinetra-MSFT , Tried as per your feedback but still facing the same issue.

@dhruvp29 , Thanks for trying out, We are looking into the issue.

@dhruvp29 Participants joining depends on the policy of the channel. Could you please tell us if it was a private channel or a public channel?
Also what was the message that was shown to the participant who was trying to join? Like were they in lobby?

Hi @Gousia-MSFT  It is a public channel.
Participants are not getting any error messages. as they are not able to click the meeting. If we create any meeting from teams UI,  we are able to see the view meeting details option as per the below screenshot.

the above option is not available when the meeting is created using GRAPH API.
Kindly let me know if you require more information from my end.

@dhruvp29 This is a known client issue. You can only join such created meeting using the join url.

@Gousia-MSFT Thanks for the update. Is there any API using which we can achieve the Meet Now functionality available in teams UI?
OR
we can initiate a call in teams channel?

@dhruvp29 , You can use meetNow a MeetingType. Please see the request body here:

POST https://graph.microsoft.com/beta/app/onlineMeetings

{
  "meetingType": "meetNow",
  "participants": {
    "organizer": {
      "identity": {
        "user": {
          "id": "[myUserId-Guid]"
        }
      }
    }
  },
  "subject": "MeetNow from Graph API"
}

From the response you can isolate easily the most important information

joinURL

Send that joinURl into participants you want to add into a meeting. But there is more in that meeting.

@Trinetra-MSFT Thanks for the answer but, in my case, I do not want to send the meeting URL separate.
I want that, it should send the notification in the channel similarly it is being sent when we perform Meet Now using Teams UI.

@dhruvp29 , Please take a look at Create an online meeting in a Microsoft Teams Channel with a user token.

@Trinetra-MSFT I am already using that API and getting the issue.
Please check the question again.


pull-cert-manager-website-verify is pulling stale data from other branches.

Reference: https://github.com/cert-manager/website/pull/272#issuecomment-667080023
It seems that the pull-cert-manager-website-verify job, when trying to verify a PR against the master branch, is seeing a not-the-most-recent commit on the release-next branch, and failing the build because of it.
Specifically, I'm seeing this failure report in the logs:
+++ Running spell check
    content/en/next-docs/installation/compatibility.md
       36 | n a custom CNI on EKS, so the CNIs differ between control
       43 | Note that since kubelet uses port `10250` by default

>> 2 spelling errors found in 536 files

which was caused by 9d485d0a4cdf263add370542c68cd3bc93c65ee9 (same errors appear in the build log for this commit) and fixed by a6c70fa59b05b8500391823e073051dac18dd4ec 10 hours later, both on release-next, both part of the same PR (#268), which was merged four hours ago, and itself passed the same job.
The pull-cert-manager-website-verify jobs doesn't appear to log the hash it found on the branches it pulls, so it's not clear what's going on here.
I retried the job an hour later, with the same result.
It looks like this is the first run of this job since #268 was merged, in case somehow #268 left the tree in a bad state, despite passing its own builds...

It took me a morning coffee to understand but the issue here is not stale data it is that we take the .spell from master merged with the PR branch. But since we added new correct words to release-next we never added them on master.
Is fixed in https://github.com/cert-manager/website/pull/274


Online scores in index never load

Describe the bug
Online scores never load
Console error
I think it dont says the problem, sorry
Desktop (please complete the following information):

OS: Windows 7 Professional
Browser Chrome
Version 96.0.4664.45 (Build oficial) (32 bits)

Can't confirm the issue here. Do other things work? Also can you please check the "network" tab of your inspector (press F12, then go to the network tab to see if anything goes wrong. You should see periodical requests. Click on them to see details.)

Can't confirm the issue here. Do other things work? Also can you please check the "network" tab of your inspector (press F12, then go to the network tab to see if anything goes wrong. You should see periodical requests. Click on them to see details.)

this?

btw in that spanish text says basically It cant load the reply data

Make sure the URL says http:// not https://

Oh yeah, he's right. btw @BlaNKtext your version looks really cool!

Make sure the URL says http:// not https://
Edit: I host a https version

Ye it says https://

Make sure the URL says http:// not https://
Edit: I host a https version

Ye it says https://

Live plays only work on http://osugame.online

Make sure the URL says http:// not https://
Edit: I host a https version

Oh i read it wrong


joss reviewer #2 comment: manuscript

I am another reviewer on JOSS submission (see https://github.com/openjournals/joss-reviews/issues/2166). In the course of the coinstac (not manuscript content) review, I have filed other issues pertinent to the JOSS review checklist. Here I would like to provide a summary of the paper (from Mon Mar 30 10:19:56 2020 EDT, md5sum 84b7642d511894822a63769fff13525e).
First of all let me state that COINSTAC seems (have not used it personally yet to provide empirical support, but have heard many great things) indeed to be a great and needed to the ecosystem platform, which is a result of great work of the project's "scientific advisory board" and the developers!   Well done!  With that in mind, I feel that JOSS submission and some parts of the documentation could be improved to make it more accessible.
Decentralized
"decentralized" should be explained and comparison to other platforms need to be adjusted:

"decentralized": I think the reader would benefit from a brief summary of "decentralized". Moreover, the first use of the word is not really accenting on the right application per se: "can build ... models ... collaboratively in a decentralized fashion". COINSTAC enables decentralized computation, orchestrated via a central service. So I would argue that if anything, models are actually built centrally, where individual computations are decentralized.
Picture is worth a thousand words, and I think that is the case here. Please add a figure which could help reader to understand the flow and the aspect of the decentralization of computation
Re "the first ... platform enabling decentralized analysis": Might be worth referencing ENIGMA study as one of the early examples (https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4008818/) and then guide comparison with other platforms (not tools!) while accenting on the fact that COINSTAC was designed specifically to support such decentralized computation, unlike those other platforms platforms (which as @gkiar points out in #849 with CBRAIN) might already support it.

Data Protection
Wording should be adjusted to possibly avoid making false claims

Even the statement of the need for "enhanced protection" (via differential privacy) undermines the not really described claim that COINSTAC "preserves the privacy".  Since results of computation are transferred back to the central node, and they could potentially incorporate sensitive data, there is a possibility of leaking sensitive information.  So wording should be adjusted to not "over-promise".

Similarly fuzzy wording in the "keep your data safely ... untouched" in the  features.  "untouched" here means that data is not modified, but it is "looked at", thus there is a possibility of leakage.

Summarizing: nothing is stated about mechanisms to protect against malicious "apps/computations" which might send "interesting" private data back. Re "untouched" - is there a guarantee that the app does not actually modify the data?  Is there any process in place for curating the "analyses/pipelines/etc" as to what "bits and pieces" would be sent to central node?

Is it a singleton?
From my limited experience with running 'coinstac' -- there is only one central node is out there and I was not sure if it could be configurable, i.e. that I could have my own COINSTAC instance/network with coinstac client connecting to it instead of the default one.  Is COINSTAC like COINS in being "the one and only" instance?  Please clarify in the text (and/or README.md) on how to deploy/work with an independent COINSTAC deployment.
"Conclusions"
"... central compute nodes ... attempt to draw conclusions"  sounds "too AI". Nodes are not attempting to draw conclusions I hope, but rather follow some prescribed procedures to establish the overall result based on some coded logic/stats/etc.  Please adjust wording avoiding the notion of an AI being in charge of the main node ;)
"Example usage"
I think paper (see above recommendation about Figure) could be greatly improved with some real-world'ish example.  It would not need to be detailed, but could have references to all the details (full pipeline on github, sample data somewhere) while depicting the apps/data (as results) flow.
It then also would allow to mention that apps/pipelines are formalized in javascript (for better or for worse) which could orient a new reader better.
Differential privacy
Could benefit from a sentence summary + reference for more details.
"Community guidelines:"
Nothing in the paper.  At least a brief summary of what you would expect community to do (or not to do ;)) besides using (singleton?) COINSTAC, would be valuable to the reader.
Minor typos
in the paper (as well as in other documents within repository, see #880 ) there is some minor inconsistency in opening sentences word casing.  ". we also", ". bits and pieces", ". instead" - please fixup

I am another reviewer on JOSS submission (see openjournals/joss-reviews#2166). In the course of the coinstac (not manuscript content) review, I have filed other issues pertinent to the JOSS review checklist. Here I would like to provide a summary of the paper (from Mon Mar 30 10:19:56 2020 EDT, md5sum 84b7642d511894822a63769fff13525e).
First of all let me state that COINSTAC seems (have not used it personally yet to provide empirical support, but have heard many great things) indeed to be a great and needed to the ecosystem platform, which is a result of great work of the project's "scientific advisory board" and the developers! Well done! With that in mind, I feel that JOSS submission and some parts of the documentation could be improved to make it more accessible.
Decentralized
"decentralized" should be explained and comparison to other platforms need to be adjusted:

"decentralized": I think the reader would benefit from a brief summary of "decentralized". Moreover, the first use of the word is not really accenting on the right application per se: "can build ... models ... collaboratively in a decentralized fashion". COINSTAC enables decentralized computation, orchestrated via a central service. So I would argue that if anything, models are actually built centrally, where individual computations are decentralized.
Thank you very much for the comment. I added ‘aka decentralization’ in the text. We don’t disagree with your interpretation but at the same time, we reckon, the sentence ‘can build...models...collaboratively in a decentralized fashion‘ can also be interpreted as the decentralized computations collaborating to build a model. Think of a team of players playing a game. The result of the game (here model) is not decentralized but a result of the individuals playing (decentralized computations).

Picture is worth a thousand words, and I think that is the case here. Please add a figure which could help reader to understand the flow and the aspect of the decentralization of computation
We concur with you about the suitability of a pictorial representation of the decentralization of computation but unfortunately such a representation is tied to the specific algorithm and might not necessarily do complete justice. However, we added a figure to depict the overall structure of the coinstac framework with local computer nodes (where the computations happen) and a central node (where the model is built).

Re "the first ... platform enabling decentralized analysis": Might be worth referencing ENIGMA study as one of the early examples (https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4008818/) and then guide comparison with other platforms (not tools!) while accenting on the fact that COINSTAC was designed specifically to support such decentralized computation, unlike those other platforms platforms (which as @gkiar points out in #849 with CBRAIN) might already support it.
Thank you very much for pointing out the need for comparing with existing frameworks. We’ve added a ‘Related work’ section where ENIGMA, ViPAR are discussed. We would also like to bring to your attention that in your understanding CBRAIN does not necessarily support decentralization but supports distributed computation. The distinction has been clarified in a response to @gkiar.

Data Protection
Wording should be adjusted to possibly avoid making false claims

Even the statement of the need for "enhanced protection" (via differential privacy) undermines the not really described claim that COINSTAC "preserves the privacy".  Since results of computation are transferred back to the central node, and they could potentially incorporate sensitive data, there is a possibility of leaking sensitive information.  So wording should be adjusted to not "over-promise".
Thanks for pointing it out. The sentence has been rephrased as follows: Because there is no pooling of data it can technically guarantee the privacy of individual datasets. However, we also offer differentially private algorithms for enhanced protection.

Similarly fuzzy wording in the "keep your data safely ... untouched" in the  features.  "untouched" here means that data is not modified, but it is "looked at", thus there is a possibility of leakage.
Modified to ‘technically untouched’‘. However, the following point ‘Applying differential privacy strategies to further enhance anonymization of private data, whilst still permitting collaboration.’ should clarify it further.

Summarizing: nothing is stated about mechanisms to protect against malicious "apps/computations" which might send "interesting" private data back. Re "untouched" - is there a guarantee that the app does not actually modify the data?  Is there any process in place for curating the "analyses/pipelines/etc" as to what "bits and pieces" would be sent to central node?
Please see the bullet point at the bottom of the paper under (3).

Is it a singleton?
From my limited experience with running 'coinstac' -- there is only one central node is out there and I was not sure if it could be configurable, i.e. that I could have my own COINSTAC instance/network with coinstac client connecting to it instead of the default one. Is COINSTAC like COINS in being "the one and only" instance? Please clarify in the text (and/or README.md) on how to deploy/work with an independent COINSTAC deployment.
Anyone can set up their own COINSTAC server. We already provide instructions at https://github.com/trendscenter/coinstac/blob/master/SETUP.md, and have linked to them on the main README.md page.

"Conclusions"
"... central compute nodes ... attempt to draw conclusions" sounds "too AI". Nodes are not attempting to draw conclusions I hope, but rather follow some prescribed procedures to establish the overall result based on some coded logic/stats/etc. Please adjust wording avoiding the notion of an AI being in charge of the main node ;)
Changed to “...central compute nodes … help the user draw conclusions”

"Example usage"
I think paper (see above recommendation about Figure) could be greatly improved with some real-world'ish example. It would not need to be detailed, but could have references to all the details (full pipeline on github, sample data somewhere) while depicting the apps/data (as results) flow.
It then also would allow to mention that apps/pipelines are formalized in javascript (for better or for worse) which could orient a new reader better.
Please see the section entitled Example usage.

Differential privacy
Could benefit from a sentence summary + reference for more details.
Added a citation describing differential privacy
"Community guidelines:"
Nothing in the paper. At least a brief summary of what you would expect community to do (or not to do ;)) besides using (singleton?) COINSTAC, would be valuable to the reader.
Please see the last section entitled Community Guidelines.
Minor typos
in the paper (as well as in other documents within repository, see #880 ) there is some minor inconsistency in opening sentences word casing. ". we also", ". bits and pieces", ". instead" - please fixup
The paper has been edited for grammar.

@yarikoptic Thanks for reviewing this work. I've added responses to your comments. I hope you will be able to take some time off your schedule to take a look and we will be happy to address any further concerns you may have. Thanks again for your time.


[monorepo-builder] github http error

Split seemed to stop working, here's the github action log

Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   composer.json
	modified:   src/SurvosDocBundle.php

no changes added to commit (use "git add" and/or "git commit -a")

[NOTE] Adding git commit

[NOTE] Pushing git commit with "why isnt split working" message to "main"

fatal: could not read Password for<EMAIL_ADDRESS>No such device or address

[NOTE] Changing directory from "/tmp/monorepo_split/build_directory" to "/github/workspace"

Where is that password error coming from?  The composer file is pretty straightforward.
https://github.com/survos/survos/blob/main/packages/doc-bundle/composer.json

I'm wondering if a token expired, but I can't figure out what to do.
Or if it's something else that's wrong.  All of a sudden, my bundles stopped splitting.


west.yaml: update hal_espressif after SDHC porting

Update revision reference for PR #71165 as needed.
Fix #72196

How could the PR introducing the wrong revision get merged, though?

Is the root cause a merge on the Zephyr side or a git "push force" that removes the targetted commit on the Espressif side?

In fact it does seem like the issue is caused by a force push on the hal_espressif repo. Shouldn't be allowed, right?
I believe the issue is that the Zephyr PR referenced the commit of the unmerged HAL PR and was merge before the HAL PR.

I believe the issue is that the Zephyr PR referenced the commit of the unmerged HAL PR and was merge before the HAL PR.

You are correct: https://github.com/zephyrproject-rtos/hal_espressif/pull/276/commits/e554857b07d54e2152c6f1a9b39da6d6c13fe7f7

I seems to not break CI yet, but should be tag it as trivial such that it it will be merged sooner?

Merged, could have used a better commit message though, something describing what was incorrect with the previous hash.

I believe the issue is that the Zephyr PR referenced the commit of the unmerged HAL PR and was merge before the HAL PR.

You are correct: https://github.com/zephyrproject-rtos/hal_espressif/pull/276/commits

Sorry for this. Indeed that hal PR should have been merged before its counterpart in Zephyr.

Sorry for this. Indeed that hal PR should have been merged before its counterpart in Zephyr.

Yeah, and the commit hash referenced should have been the one in the repo after the PR was merged instead of the one in the PR.
Could we have an automatic check to detect this before PRs are merged into main in the future ?

Could we have an automatic check to detect this before PRs are merged into main in the future ?

That would be ideal but unfortunately the way modules are managed is not quite uniform enough to allow writing such a check in a reliable way (not that I can think of anyway), specifically the "main" branch of modules can have different names.

@sylvioalves please:

In the HAL module repo create a branch or tag the commit to ensure it is not garbage collected, and name it something that makes it very evident that it should not be deleted. And protect that branch in github.
Send a hotfix PR to Zephyr to correct the west manifest to point to the merged commit sha.
(Without 1. we will end up quite soon with this commits in Zephyr being unfetchable by west)

@aescolar We usually make sure to update west.yaml only after having it merged into default/protected hal_espressif repo.  This was really a mistake that has never happened before and I will, of course, pay more attention to it. Thanks for the recommendation.


Unstable note playing when scheduling at time 0

I noticed that when starting the measure index at 0 the first measure is often, but not always, skipped, and the notes start playing only from the second measure.
But when starting the measure index at 1 then the first measure is always played and no notes are ever missed.
It took me a little while to notice this instability.
Tone.Transport.scheduleOnce((measureStartTime: any) => {
}, measureCounter + 'm');

Could you post a jsfiddle or a way to reproduce this issue? I am unable to reproduce the issue with your above code.
There is usually instability with the AudioContext as soon as the page loads, it's always best to start the Transport from a button click (which also solves common Autoplay pitfalls and will work more consistently across browsers) instead of just on page load.

I experience the issue, even long after the page has loaded, even after multiple play and stop of the soundtrack.
I will now try to create a live example and come back with it.

Hello, I have now made a live example.

Looks like your example is using<EMAIL_ADDRESS>Could you update to tone@latest or tone@next? It's possible this issue has already been fixed in subsequent versions

I upgraded the tone dependency of the example to ^13.8.25 and still observed the exact same issue after reloading the example.
I have the same dependency on my project.
I then tried to do an npm i tone@latest and it updated a dependency;
+<EMAIL_ADDRESS>updated 1 package and audited 30268 packages in 67.818s

but my package.json file did not change as it already had that same dependency version.
I then tried to do an npm i tone@next and it updated a dependency, and my package.json file changed:

<EMAIL_ADDRESS>
I upgraded the example with the same version and the issue went away there.
On my app the issue also went away.
But there was some other issue showing up, the events seem to not be cancelled properly. On a replay the sound becomes garbled. I can see the error message in the console: Max polyphony exceeded. Note dropped. It's a show stopper. I have to revert to the previous stable version. No worries.

The max polyphony is initially set to 32 i think, but you can pass in an argument to the constructor to increase that. But if you're exceeding 32, it might be an issue that the notes aren't being released.
If the original issue is fixed in tone@next, i suggest we resolve the issue and create another issue if you're unable to solve the PolySynth max polyphony issue

I have used at most 4 voices in a poly synth, so I'm surprised it hit the 32 maximum. I have never been above 4 in my synth configurations. Let's see if tone@next fixes this.

@stephaneeybert any updates on the original issue?

I just installed the tone@ dependency again in my application.
The sound came out again poorly, with some clearly heard static, like some radio received audio. Stopping the play did not release all of the notes and some were left triggered. I had the same results with the following synths:
    const synth: any = new Tone.PolySynth(Tone.Synth, {
      "volume" : -8,
      "oscillator" : {
          "partials" : [1, 2, 5],
      },
      "portamento" : 0.005
    }).toMaster();

    const synth: any = new Tone.PolySynth(Tone.Synth, {
      oscillator: {
        type: 'sine',
      }
    }).toMaster();

The console had nothing to say. I had to reload the page to stop the sound.

would it be possible to create an example reproducing this issue? I'm unable to reproduce this issue on my side with that code.

Yes, such an example already exist, it is the one linked to above in the thread.
It has the tone@next version.
I played it on Chrome now and it showcased a failing sound, with some kind of static.
You can try to play it and you should not hear any real playing, but only some static sound.

your example doesn't make any sound for me no matter which buttons i click on. Looks like you're triggering the attack and decay at the same time. If i update line 81 to this: this.synth.triggerRelease(placedChord.renderAbc(), triggerTime + 0.1); then i can hear the notes, but am not getting the distortion you mentioned.

My example had some fault. I fixed it. It now plays and shows the behaviour explained in it. It does so even on the next release of Tone 14.6.0 and no garbled sound nor static is heard. I will see if I can replicate in this example the issue I see in my project.

Seems like the original issue is fixed. If you're able to create a test case for the issue you're having with the PolySynth, please open a new issue for that


Fix KeyError when accessing content in messages with function calls

End-user friendly description of the problem this fixes or functionality that this introduces

[x] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Fixes a "message['content'] key" error

Give a summary of what the PR does, explaining any non-trivial design decisions
Fixes #5142
The error occurs when a message in the messages list doesn't have a 'content' key. This can happen with OpenRouter when using function calls, as some messages might only have function call information without content.
Let me summarize what OpenHands did to fix the issue ("I" = OpenHands):
I identified that the error was occurring in the convert_fncall_messages_to_non_fncall_messages function when trying to access the 'content' key from messages that only had function calls.
I wrote a test case to reproduce the issue, which showed that messages with function calls but no content were causing a KeyError.
I fixed the issue by modifying the code to use message.get('content') instead of message['content'] in three places:
In the main message processing loop
In the system message handling
In the assistant message handling
The fix ensures that messages without a 'content' key are handled gracefully, which is important when dealing with function calls from OpenRouter or other providers that might not include content in their function call messages.

Just to note, also fixed here: https://github.com/All-Hands-AI/OpenHands/pull/5026
Along with a couple of other conversion issues.

Oh, thanks a lot @enyst , I didn't see it mentioned in the issue. I'll close this in favor of yours.

My bad, thank you. I'm working on a refactoring that will hopefully make these stop cropping up.


fix(board-item): add styles to board-item and board

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[X] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[X] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[X] Updated Storybook documents for component
[X] Wrote test codes for composable, utils and etc.
[X] Tested with console(if usages are changed)

Description

Fix border and background-color of selected <p-border-item/>

Add box-shadow and border-radius to <p-border/>

board-item & board Component Figma

Things to Talk About

:tada: This PR is included in version 2.0.0-beta.73 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Split overloaded 'use' method into multiple methods.

Per the September 2022 plenary discussion, the DisposableStack.prototype.use method should not be overloaded and instead split into multiple methods:

use(disposable) to add a disposable resource to be disposed when the stack is disposed.
adopt(value, onDispose) to add a non-disposable resource (value), such that onDispose(value) is called when the stack is disposed.
defer(onDispose) to add a callback to execute when the stack is disposed.

so "adopt" is like "use and defer"?

hmm - so is adopt(x, y) just defer(y => x(y))?

Not quite: adopt returns its first argument.
I had the same question on Wednesday, and if I understood @rbuckton correctly, it's intended for cases like this
let resource = stack.adopt(getResource(), handleResourceDisposal);

Rewriting that to use defer would require
let resource = getResource();
stack.defer(() => handleResourceDisposal(resource));

which has the problem that there is now a place you can insert code between where the resource is acquired and the place where it is registered for disposal (i.e. between the first and the second lines). Using adopt avoids that risk.

defer(y => { x(y); return y; }) then?

The argument to defer isn't invoked until scope exit, so no, not like that.

ahhh i see, because it allows "defer" but with eager evaluation of the expression. thanks.

Yeah.
Also, to be clear, the function passed to defer isn't passed any arguments: in your defer(y => x(y)) , snippet, y is always going to be undefined.

use(value) registers a disposable and returns value.
adopt(value, onDispose) registers something like { [Symbol.dispose]() { onDispose(value); } }, and returns value.
defer(onDispose) registers something like { [Symbol.dispose]() { onDispose(); } }, and returns undefined.

Ok, so why isn’t defer and adopt the same method, with the value as a second optional argument?

Ok, so why isn’t defer and adopt the same method, with the value as a second optional argument?

For several reasons:

defer(onDispose, value?) feels too reminiscent of filter(callback, thisArg?), and I'd rather not confuse users.
Having the callback last is reminiscent of NodeJS's continuation-passing style.
adopt(value, v => v.close()) works better for type inference purposes since the type of v can be determined from the type of value; the other way around requires you to write defer(v => |, value) first and then jump back to | to get completions.

I don't agree with the first point at all - there's tons of APIs, array or not, that aren't filter that don't take an optional thisArg (reduce, split, join, etc), nor do I see a problem with the second - this isn't a continuation, it's basically an event handler. I'm also not persuaded by type inference arguments.
It seems silly to me to have two separate methods (even if they had names that actually seemed related, and that actually conveyed what they do, which "defer" kind of does but "adopt" doesn't at all) when the only difference is the value argument's presence.

It seems silly to me to have two separate methods (even if they had names that actually seemed related, and that actually conveyed what they do, which "defer" kind of does but "adopt" doesn't at all) when the only difference is the value argument's presence.

It seemed silly to me to have three, which is why they were overloaded. Regardless, I'm not in favor of (callback, value?) because of the mess it causes for inference when using an editor with type information (be that TS or JSDoc types). reduce is a perfect example of the issue with inference:
["a", "b", "c"].reduce((memo, value) => ¦

As you type and reach the ¦ a type system would infer memo to be a string. But if you're planning to aggregate it into a Map it won't infer that type until you write the rest of the call:
["a", "b", "c"].reduce((memo, value) => ¦, new Map())

split and join are poor examples as they don't accept callbacks. There are many built-ins that do take callbacks, and the majority take the callback last:

new Proxy(obj, handlers) (the handlers are essentially a collection of callbacks)
JSON.parse(text, reviver)
JSON.stringify(value, replacer)
Array.from(items, mapfn) (if you ignore the thisArg)

Aside from reduce/reduceRight, the only other functions in the standard library that take a value following the callback take a thisArg (map, filter, find, etc.).

If you're making a consistency argument, then the thisArg pattern is exactly what you'd want to follow. I don't think a type inference argument should be valid since ecmascript doesn't have types in that sense - if that mattered, the order of import/from would have been reversed, and a precedent might have existed to follow. I understand the issue with inference, I'm saying that may be an unavoidable cost.

I don't think a type inference argument should be valid since ecmascript doesn't have types in that sense

I think it's important to consider the effects on tooling, given that many people are using tools. We absolutely should not assume everyone is using a tool, but we also shouldn't give considerations about tooling literally zero weight.

that's fair that we should give it nonzero weight. However, I think defer/adopt are confusing names, and it took a lot of questioning before i realized that they're actually the same method with an optional value argument squished into the front. I think it would be very, very confusing unless we combine them into one (callback, value?) signature.

Honestly they don't really seem like the same method to me? One is "I wish to use this value, and here's the function used for disposing of the value's resources [because it doesn't implement @@dispose itself] once it goes out of scope"; the other is "here's a function to call at the end of this block, with no particular resource associated". They're not really that similar in intent, even if they do have similar underlying mechanics.

@ljharb:

[...] I don't think a type inference argument should be valid since ecmascript doesn't have types in that sense - if that mattered, the order of import/from would have been reversed, [...]

That has consistently been a pain, and a proposal to do just that was created and put on the agenda at one point, though it was withdrawn and wasn't presented.

However, I think defer/adopt are confusing names [...]

I'm more than happy to consider alternatives. I chose defer since it is reminiscent of Go's defer, though Python's ExitStack just uses callback. I chose adopt since its purpose is interoperability, to "use something that isn't disposable as if it was disposable". I considered "adapt", but that doesn't imply a containment/ownership relationship. I was leaning towards a short single-word function name, but we could also consider something like useNonDisposable, etc.

I think it would be very, very confusing unless we combine them into one (callback, value?) signature.

But what would you call that? defer doesn't seem like the right term for something that takes a value, and if we were to use that signature I'd find it confusing unless it was (callback, thisArg?), necessitating the use of a function expression rather than an arrow function so that you can access this.
I personally like the idea that the subject of the operation is the first argument and the return value, hence why the signature for use is <T>(value: T) => T, and the signature for adopt is <T>(value: T, onDispose: (value: T) => void) => T.
@bakkot:

(That said, I don't feel that strongly that those two operations need to be separate methods; I see the type inference concern but don't know if it warrants having an extra method. I am fine either way.)

I still prefer the overloaded use I presented:
class DisposableStack {
  use<T extends Disposable>(value: T): T;
  use<T>(value: T, onDispose: (value: T) => void): T;
  use(onDispose: () => void): void;
}

But if we were to break this into two methods instead of three, I'd prefer this breakdown:
class DisposableStack {
  use<T extends Disposable>(value: T): T;
  use<T>(value: T, onDispose: (value: T) => void): T;

  defer(onDispose: () => void): void;
}

Where the use and adopt methods are merged, with the 2nd argument existing as a way to override any potential [Symbol.dispose]() method on value.

I still prefer the overloaded use I presented:

There's two bad things about that overload (to my eyes):

f(x) branches on x being disposable vs callable
f(x, y) treats x as a different kind of thing than f(x)

These are both bad, but the first one is more serious.
The three-method form eliminates both of these problems.
Having use plus an overloaded defer which is either defer(() => void) or defer<T>(T => void, T), as Jordan suggests, also eliminates both of these problems (but has the type inference problem you point out).
Having use plus an overloaded defer which is either defer(() => void) or defer<T>(T, T => void) only eliminates the first problem.
Having defer plus an overloaded use which is either use<T extends Disposable>(T) or use<T>(T, T => void) only eliminates the first problem.
I would be happiest if we eliminate both of the problems with the originally proposed overload. I can live with only eliminating the first problem. I would be unhappy if we don't eliminate either problem.

I haven't thought all the way through this yet, but I'm very interested in how incremental migrations would work here.  Specifically, what does it look like when a pre-disposable API updates to become an actual disposable?  Relatedly, what might it look like if anybody is polyfilling or ponyfilling disposable or DisposableStack?
For the former question, I imagine you'd start with code that looks like stack.adopt(resource, r => r.close()).  If resource grew a Symbol.dispose method then you could continue using it with adopt, but could then switch to use(resource) or using resource at any time.  I could imagine a possibility where adopt was actually useOrDefer or some such, so that it would switch to using the symbol method if it existed, and otherwise it would use the given callback - this would give it some distinction from both use and defer.  But I can also imagine plenty of arguments against that design.

Aside about polyfills/ponyfills (tl;dr: I think it's not an issue)
I have a harder time reasoning about polyfills/ponyfills, since I'm not quite sure what they might look like.  Presumably a polyfill would actually define Symbol.dispose, which downstream disposables would then depend on.  A transpiler would probably change using into a for-of loop, and there would be an actual DisposableStack implementation that could be used as well.  What happens when the latter is replaced with the real thing?  I assume the symbol would drop in correctly and there's no problems?

[...] I could imagine a possibility where adopt was actually useOrDefer or some such, so that it would switch to using the symbol method if it existed, and otherwise it would use the given callback - this would give it some distinction from both use and defer. But I can also imagine plenty of arguments against that design.

Aside from just adopting non-disposables, adopt is also able to use custom dispose semantics for actual disposables:
using stack = new DisposableStack();
const res = stack.adopt(getResource(), res => {
  disposeCounter++; // some extra work we want to do.
  res[Symbol.dispose]();
});

As such, I wouldn't want adopt to conditionally use the callback based on the presence of Symbol.dispose, but to always use the callback. Even with the overloaded use version proposed currently, the presence of a callback would always outweigh whether the object itself was disposable.

I could imagine a possibility where adopt was actually useOrDefer or some such, so that it would switch to using the symbol method if it existed, and otherwise it would use the given callback

I'm strongly opposed to doing this kind of switching. It's harder to read, and it makes it a lot more likely that adding the Symbol.dispose will be a breaking change (in particular if it's not just an alias for the thing the user was doing previously).

[...] A transpiler would probably change using into a for-of loop [...]

Actually, my plan for TypeScript is to implement with nested try..finally, per the example transposed representations in the explainer. Transpiling to a for..of would require a much more complex transform since you would need to also transform any containing iteration statements and nested continue or break statements to work around the introduction of an additional loop (something also mentioned in the explainer).

Regarding naming, use(disposable) makes sense to me, altho i'd mildly prefer using(disposable) precisely because it mirrors the keyword.
defer(callback) also makes sense to me, not because i think any notable percentage JS programmers will have ever seen go or be familiar with it, but because it accurately describes what it's doing.
adopt(value, nonDisposable) is the one I'm not comfortable with. One because value is optional, and it should be adopt(nonDisposable[, value ]), but also the name - it's just a really weird pattern imo, and something like .defer((x => { x.close(); return x; }).bind(null, value)) or similar doesn't seem sufficiently unergonomic to me to warrant adding this method now (iow, it seems better for a followup proposal).

something like .defer((x => { x.close(); return x; }).bind(null, value)) or similar doesn't seem sufficiently unergonomic to me to warrant adding this method now

The implementation of adopt is something like
class DisposableStack {
  // ...
  adopt(resource, callback) {
    this.defer(() => callback(resource));
    return resource;
  }
}

So your snippet doesn't do the same thing as adopt - in particular, it doesn't evaluate to value. Did you mean (x => { stack.defer(() => x.close()); return x; })(value)? Personally that absolutely seems sufficiently unergonomic to warrant adding this method now. No one is going to write that; they're just going to mention the resource twice and risk not cleaning it up.

I'm not sure why it needs to be chained - stack.defer(() => callback(resource)); resource then?

adopt(value, nonDisposable) is the one I'm not comfortable with. One because value is optional, and it should be adopt(nonDisposable[, value ]), but also the name [...]

I'm open to suggestions for an alternative name, but I strongly disagree with having the value as the 2nd argument. It's not that it's optional, per se, but that it passes through the argument (including null and undefined). As I've said before, the pattern to emulate here is JSON.parse(text, reviver), JSON.stringify(obj, replacer), Array.from(obj, mapper), fs.readFile(filename, callback), not array.map(callback, thisArg). If it came down to it, I would rather ban null and undefined as the first argument to adopt than to change the argument order.

That you can insert code doesn't mean you will; this seems like a very unnecessary guardrail/convenience to me compared to the cost of an entirely distinct API method.

That you can insert code doesn't mean you will; this seems like a very unnecessary guardrail/convenience to me compared to the cost of an entirely distinct API method.

I'm not sure I understand what you mean by "can insert code"? The point of adopt is that you want to both use a resource and provide custom disposal behavior (primarily to interop with a non-Disposable resource), meaning that you will want to run code that is associated with that resource. use is convenient for Disposables, defer is convenient for callbacks, neither are convenient for interop, hence the third method.

That you can do it in two lines seems perfectly acceptable to me.

I strongly disagree. There are other APIs for which "just do it in two steps" is totally fine, but not this one.

That you can do it in two lines seems perfectly acceptable to me.

It isn't to me. When this ships, there will be a long tail of APIs between the DOM, NodeJS, Electron, third-party packages, etc. that will not yet support Symbol.dispose, meaning that for several years its likely adopt would see more use than use. It is a matter of convenience that, to me, trumps having both .then and .catch on Promise (for example).

I'm going to go ahead and merge #103 and we can discuss this again in plenary.

If you're making a consistency argument, then the thisArg pattern is exactly what you'd want to follow.

I really hope we won't repeat thisArg pattern in any other place except Array methods. thisArg pattern IMO have big ergonomics issues, not only type infer, but also error-prone. As I understand, the only reason we have thisArg pattern is because we didn't have arrow functions and creating new functions may still have big cost in some engines in JavaScript 1.7 era. Even that, the API could have been designed like arr.forEach([thisArg, method]) which avoid the issues.


Some doubts for WebSocket Server...

Hello guy's I have some doubts regarding the creation of my WebSocket Server and i wanns ask something to you :)
I'm creating an Server for Mobile application for write topics and comments (into mysql). Before i ask something i'll show toy my code /logic

This is my start_server.php. This is like "main" function and i use this for launch my server.
http://pastebin.com/kvcx8NzD

I realize an XML file for server settings and i load them with loadSettings. Now i think here it's all correct (i hope). Now i wanna try to use the IP Blacklist but i can't recognize how can i use it in this script :( and if you have some suggestion for improve this initial code please tell me.

The start_server create and lunch my server.php:
http://pastebin.com/nT3swRa5

Now in my server i have some objects:
clients: is original dataobject from test server (i think it will be removed)
router: is my special object, with this i route the request from client (i'll show after)
loop: is the main object loop, with this i send PINGs and prevent the connection close
users: is an array[email] dataset of clients object. with this i can reference the clients into my another classes
In the construnct i add an periodic function where i send PINGs and refresh the setting of server (min version for clients and another)
in onOpen event function i send an ACK to client ("Connected") and recognize (from IP for now) their location
in onMessage i decode the request from client exec the request (with data if the client send) with router (i'll show you after)
after exec the request i send the response (or ack) to the client.
in onClose i check if the client was logged in or not (in my $users)
if is logged i UNSET the position of my array (and i hope this free the memory)
else i remove only from clients and close connection (it's right?)
now it's correct for now or can i improve my script? (like memory usage or other)
NOW i'll show you my idea for manage the request of client, i created the MRC like pattern (Model Router Controller).
The logic is:   Client send Request (with controller, function and data if requested) ---> pass all to an Router Object ---> this check if exist that class of controller and that function, if exist create a new object of controller and run that function ----> this function comunicate with model for update data in database -----> return the response to router -----> router return response to client
Now this is my Router Class:
http://pastebin.com/GuQcaFkC
In the construct i add ONLY public controllers (i have some controllers only for server)
But this object it's really simply, now my doubt is on my Controller - Model logic.. Every time a client request something, the Router create a new Controller and every time a new Controller wad created, it create a private Model. Every time the model need to connect to Database, it create a new DB object for comunicate with DB (i'm using Medoo lib) and after all i REALLY HOPE the server release the memory and close all DB connection in auto. i tried to make an singleton DB object but i think isn't a good idea... so can you tell me (or teach _) some improvements ? thx a lot and sorry for my bad english
Another problem is when Linux kill my php process after some days.. so i have edited the NICE value to 19 but when i run hTop and MySQLTuner i see this:

i see some mysqld process and i don't know if it's right or not

I would highly recommend against connecting to the database for each new connection. You should only need one connection for the lifetime of your application to speak to the database.
Also, any I/O that is not tied to the React EventLoop will block.

Also if you want to do blocking things with the event loop take a look at react/child-process. It's my to go package to do blocking tasks with in the event loop.

As cboden said:

I would highly recommend against connecting to the database for each new connection. You should only need one connection for the lifetime of your application to speak to the database.

Also, any I/O that is not tied to the React EventLoop will block.

but one connection for each client or only one for the server?  (and the clietns use the same Singleton connection for query)

One connection for the server. You can run as many queries as you'd like on behalf of any client.


Pipeline Caching blocked on "Artifact cannot be uploaded because max quantity has been exceeded"

https://github.com/microsoft/azure-pipelines-yaml/pull/113#issuecomment-514165261

Log from @mastfissh
Upload statistics:
Total Content: 2,576.7 MB
Physical Content Uploaded: 87.3 MB
Logical Content Uploaded: 174.4 MB
Compression Saved: 87.1 MB
Deduplication Saved: 2,402.2 MB
Number of Chunks Uploaded: 2,113

Information, Using the following fingerprint argument (Linux_target) as a string value.
Information, Generated fingerprint: E13D931D320D947A5E1528BBD52E398E2BA9141204D8D1EE07CB290AF38889EA00
Information, Creating a pipeline cache artifact with the following fingerprint: E13D931D320D947A5E1528BBD52E398E2BA9141204D8D1EE07CB290AF38889EA00
##[error]Artifact cannot be uploaded because max quantity has been exceeded or the payment instrument is invalid. https://aka.ms/artbilling for details.
##[section]Finishing: Cache target

Team is rolling out a fix here.

Should I re-test this?

@owenhuynMSFT and @fadnavistanmay - Please ping this thread when the rollout of the billing change has happened.

@mastfissh - This should be fixed. Can you please confirm. Thanks.

@fadnavistanmay working perfectly now, cheers! 👌

@mastfissh - Awesome. Closing the issue.


TypeError

Hi. First, I tested mono .wav files which resulted in an error.
Now I'm using stereo .wav files which results in another error.
stefan@stefan-quadcore ~/dev/sound-cnn-master $ ./doit.sh
Traceback (most recent call last):
  File "train.py", line 20, in <module>
    classes,trainX,trainYa,valX,valY,testX,testY = util.processAudio(bpm,samplingRate,mypath)
  File "/home/stefan/dev/sound-cnn-master/utilities.py", line 24, in processAudio
    audData = np.reshape(audData[1][:,1][0:samples*((seconds*samplingRate)/samples)],[samples,(seconds*samplingRate)/samples])
TypeError: slice indices must be integers or None or have an __index__ method
stefan@stefan-quadcore ~/dev/sound-cnn-master $ cat doit.sh
python3 train.py 240 44100 ../sounds-stereo/ 1000 100

Why does stuff not work in this world?
Cheers

Any luck? @stefan-reich

I don't know, what do you mean?

I think you're running the code with python3 but it was clearly written in python2.
A major difference between the two is that / operator gives you float output in the former and integers in the latter.
Try using // operator instead, or running the code using python2, because the calculated values are used as slices index and need to be integers.


fix runAsUser for kubescape deployment

PR Type:
Bug fix

PR Description:
This PR addresses a security issue in the Kubescape deployment by modifying the security context of the deployment. It enables the runAsUser and fsGroup settings, and sets them to a non-root user (65532). Additionally, the readOnlyRootFilesystem setting is enabled and runAsNonRoot is set to true. The version of the application is also updated from 1.15.3 to 1.15.4.

PR Main Files Walkthrough:
charts/kubescape-operator/Chart.yaml: The version and appVersion are updated from 1.15.3 to 1.15.4.
charts/kubescape-operator/README.md: The version and appVersion displayed in the README are updated from 1.15.3 to 1.15.4.
charts/kubescape-operator/templates/kubescape/deployment.yaml: The security context of the deployment is updated. The runAsUser and fsGroup settings are enabled and set to 65532. The readOnlyRootFilesystem setting is enabled and runAsNonRoot is set to true.

seems to work on GKE and kind

might need to check the cache location:
{"level":"warn","ts":"2023-09-18T13:33:27Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/security.json","error":"open /home/nonroot/.kubescape/security.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:27Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/nsa.json","error":"open /home/nonroot/.kubescape/nsa.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:27Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/DevOpsBest.json","error":"open /home/nonroot/.kubescape/DevOpsBest.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:28Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/cis-aks-t1.2.0.json","error":"open /home/nonroot/.kubescape/cis-aks-t1.2.0.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:28Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/cis-eks-t1.2.0.json","error":"open /home/nonroot/.kubescape/cis-eks-t1.2.0.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:28Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/allcontrols.json","error":"open /home/nonroot/.kubescape/allcontrols.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:28Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/ArmoBest.json","error":"open /home/nonroot/.kubescape/ArmoBest.json: read-only file system"}
{"level":"warn","ts":"2023-09-18T13:33:28Z","msg":"failed to cache file","file":"/home/nonroot/.kubescape/cis-v1.23-t1.0.1.json","error":"open /home/nonroot/.kubescape/cis-v1.23-t1.0.1.json: read-only file system"}


Does redisclient support Redis transactions?

Hi,
Does the RedisSyncClient support Redis transactions and execute the WATCH/MULTI/EXEC commands? Can the command() be used for that purpose?
Thank you in advance,
George

Yes, RedisSyncClient supports transaction commands.


Add tests for Worker template

#7974

Blocked on getting a new SDK. https://github.com/aspnet/AspNetCore/pull/8670

Is more work needed here beyond just getting the new SDK? I want to know if we should move this over to someone else or punt it in order to make space for Kerberos :)

Hard to tell until we get the SDK update. Need to rebase and see if the existing tests work.

This should now be unblocked.

@Tratcher is the next step here as simple as rebasing/retriggering?

Rebased, but there's something wrong with my test that's causing a hang on all platforms.

@ryanbrandenburg already did most of this in https://github.com/aspnet/AspNetCore/pull/8628. I just need to re-enable the test. Closing this PR.


VA Profile Sync: Plan Seeding Production

As VA Notify
I want to populate existing opt-in selections in Production
So that our local cache is accurate
Briefly, the Comp and Pen preference was turned on in Production. About 16,000 selections were made before it was disabled behind a feature flag.
The file will be in the existing BIO JSON format and will be sent via encrypted VA.gov email to Kyle/Dave. See example format in the VA Profile Sync Technical Doc.

[ ] Determine and document the method of loading the data into our production local cache table
[ ] Update the work ticket: https://github.com/department-of-veterans-affairs/notification-api/issues/869

Hey team! Please add your planning poker estimate with Zenhub @kalbfled @EvanParish @trevor2718 @k-macmillan

Please add your planning poker estimate with Zenhub @ianperera

Here are a couple of options:

Importing data from Amazon S3 into an Aurora PostgreSQL DB cluster
psql \copy command (search for "\copy")

Either approach probably requires me to write a short script to put the data in CSV format.  The data, as provided by VA Profile, is a JSON export.

Just so it's stated here too. The s3 extension is not an option without thorough testing in dev first. We would need to deploy a migration, downgrade, and push Terraform to ensure no issues within the extension being in the DB. We would also have to be able to remove it without issue.

I used the \copy method.


Improve builtin build backend errors

This improves errors in two cases:

When a file name for a module doesn't have an extension: currently .o is shown in the error message instead of actual name.
When a file for a Lua module doesn't exist: currently failure cause isn't displayed.

To be merged after 2.3.0 is released, I suppose.

:+1: good to merge I think?


Encode Redirect URI

This is a fix for #113
As the title says, encoded redirect url for all providers. Tested with facebook and linkedin and seems to be working well.

@msalman86 Awesome! Thanks a lot.
@doktordirk Looking at this... Perhaps we should put this in a variable somewhere? I think it's sort of off that we have so many copies of the same thing.

@RWOverdijk  https://github.com/SpoonX/aurelia-authentication/issues/119
@msalman86 can you rephrase your commit message to
fix(BaseConfig): bla bla .. . better for our changelog (see contributong.md)

Updated commit comment and also rebased

@msalman86 tx again. and merged it is :smile:


Large SQL lines are not visible on SQL error panel

Version: 1.0.10
Laravel: 9.5

I have some SQL queries with large table names and columns and when a error occurs, the SQL is not fully visible on the right.

Maybe adding a overflow: auto to layer?
Thanks!

Hi @eusonlito, are you talking about not being able to horizontally scroll to the right, or is the end of the string getting hidden behind the fade-out?

@AlexVanderbist yes, there aren't horizontal scroll, then large SQL lines are hidden behind the fade out :)

I finally removed all solution providers and all my problems gone away 😅

bad bot


LUCENE-9999: CombinedFieldQuery can fail with an exception when document is missing fields

This change fixes a bug in MultiNormsLeafSimScorer that assumes that each field should have a norm for every term/document.

@jimczi asked if I could finish the PR -- I pushed some changes:

Add a check that either all fields or no fields have norms enabled
Rework the testing strategy

Let me know if it still looks okay or if you have other comments.

@jpountz would you be able to take another look?

I tried out your idea. I opted to do it on a global basis in createWeight to ensure we always validate this, even when the query is rewritten.
I'm going to merge, but feel free to give post merge feedback if anything seems off.


Audible book seekbar on web app problem.

Briefly summarize your issue:

When my device is playing audible book then I seek (or rewind 30s , forward 30s) on web app page(https://alexa.amazon.com/spa/index.html#player), The seekbar has strange behavior.
What is the expected behavior?
The seekbar behavior should be like echo dot.
What behavior are you observing?
https://www.youtube.com/watch?v=JAABe0l00ZY
Everything is fine include audible book audio but the seekbar issue.
Tell us about your environment:
What version of the AVS Device SDK are you using?
AVS SDK 1.6
Tell us what hardware you're using:
ARM
Tell us about your OS (Type & version):
embedded linux
I got these logs when I use seekbar.
2018-08-03 03:06:17.560 [  4] I DirectiveSequencer:onDirective:directive={"namespace:"System",name:"ResetUserInactivity",messageId:"06b45b2c-a8c7-4650-94a9-3b3c891cdda9",dialogRequestId:""}
2018-08-03 03:06:17.560 [  5] I DirectiveRouter:preHandleDirective:messageId=06b45b2c-a8c7-4650-94a9-3b3c891cdda9,action=calling
2018-08-03 03:06:17.560 [  6] I DirectiveRouter:handleDirective:messageId=06b45b2c-a8c7-4650-94a9-3b3c891cdda9,action=calling
2018-08-03 03:06:17.931 [  4] I DirectiveSequencer:onDirective:directive={"namespace:"AudioPlayer",name:"Play",messageId:"d5843a88-ab09-4c46-9047-6067c4b4d4e9",dialogRequestId:""}
2018-08-03 03:06:17.931 [  5] I DirectiveRouter:preHandleDirective:messageId=d5843a88-ab09-4c46-9047-6067c4b4d4e9,action=calling
2018-08-03 03:06:17.931 [  6] I DirectiveRouter:handleDirective:messageId=d5843a88-ab09-4c46-9047-6067c4b4d4e9,action=calling
2018-08-03 03:06:17.931 [  6] E JsonUtils:findNodeFailed:reason=missingDirectChild,child=streamFormat
2018-08-03 03:06:17.932 [  6] E JsonUtils:findNodeFailed:reason=missingDirectChild,child=expectedPreviousToken
2018-08-03 03:06:17.978 [  2] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-08-03 03:06:17.994 [  2] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2018-08-03 03:06:17.994 [  2] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
onStateChanged
2018-08-03 03:06:17.994 [  2] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
###########################
Finished...
###########################
########################################
Alexa is currently idle!
########################################
2018-08-03 03:06:17.997 [  2] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2018-08-03 03:06:17.998 [  2] E MediaPlayer:validateSourceAndIdFailed:reason=sourceNotSet
2018-08-03 03:06:18.000 [  2] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-08-03 03:06:18.004 [  2] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-08-03 03:06:18.966 [  a] I InProcessAttachmentReader:readFailed:reason=SDS is closed
2018-08-03 03:06:19.873 [  a] I InProcessAttachmentReader:readFailed:reason=SDS is closed
0:02:05.097352381   455   0x5e46c0 WARN                    alsa conf.c:4817:snd_config_expand: alsalib error: Unknown parameters {AES0 0x02 AES1 0x82 AES2 0x00 AES3 0x02}
0:02:05.097613423   455   0x5e46c0 WARN                    alsa pcm.c:2450:snd_pcm_open_noupdate: alsalib error: Unknown PCM default:{AES0 0x02 AES1 0x82 AES2 0x00 AES3 0x02}
0:02:05.158098562   455   0x5cbcf0 WARN                    alsa pcm_hw.c:1250:snd_pcm_hw_get_chmap: alsalib error: Cannot read Channel Map ctl
: No such file or directory
0:02:10.307268547   455 0x7474de00 WARN        mpegtspacketizer mpegtspacketizer.c:359:mpegts_packetizer_parse_adaptation_field_control: PID 0x0100 afc == 0x30 and length 183 > 182
0:02:10.307428381   455 0x7474de00 WARN        mpegtspacketizer mpegtspacketizer.c:359:mpegts_packetizer_parse_adaptation_field_control: PID 0x0100 afc == 0x30 and length 183 > 182
0:02:10.307489867   455 0x7474de00 WARN        mpegtspacketizer mpegtspacketizer.c:359:mpegts_packetizer_parse_adaptation_field_control: PID 0x0100 afc == 0x30 and length 183 > 182
0:02:10.307545631   455 0x7474de00 WARN        mpegtspacketizer mpegtspacketizer.c:359:mpegts_packetizer_parse_adaptation_field_control: PID 0x0100 afc == 0x30 and length 183 > 182
0:02:10.307599020   455 0x7474de00 WARN        mpegtspacketizer mpegtspacketizer.c:359:mpegts_packetizer_parse_adaptation_field_control: PID 0x0100 afc == 0x30 and length 183 > 182
0:02:10.307667867   455 0x7474de00 WARN                 tsdemux tsdemux.c:2255:gst_ts_demux_queue_data: CONTINUITY: Mismatch packet 0, stream 10

Hi hauhan ,
Progress bar in the Alexa companion app not syncing properly during playback is a known issue. This is not really anSDK issue. We are working with the companion app team to get this fixed and will update on the progress.
Thanks
Priya

Hi priyagsenthil,
Thanks about your reply, Ihave no other problem, thanks again. :)

I just stumbled across the same issue. Is it a known issue in the 1.9 sdk as well?


Enter first 100 data rows

Try entering 100 NGO campaigns mapped to SDGs

GlobalGiving 1000 Sample rows can be downloaded here.
Here is a video of how this mapping can be attempted that helps us explore information architecture:
Sample Row mapping video