Updated copyright to 2016

It's better to update in all files, not only the license.
Em qui, 31 de dez de 2015 23:23, AQNOUCH Mohammed<EMAIL_ADDRESS>escreveu:

You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/3180
Commit Summary

Updated copyright to 2016

File Changes

M LICENSE.md
https://github.com/godotengine/godot/pull/3180/files#diff-0 (2)

Patch Links:

https://github.com/godotengine/godot/pull/3180.patch
https://github.com/godotengine/godot/pull/3180.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180.

It's better to update in all files, not only the license.
Em qui, 31 de dez de 2015 23:23, AQNOUCH Mohammed<EMAIL_ADDRESS>escreveu:

You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/3180
Commit Summary

Updated copyright to 2016

File Changes

M LICENSE.md
https://github.com/godotengine/godot/pull/3180/files#diff-0 (2)

Patch Links:

https://github.com/godotengine/godot/pull/3180.patch
https://github.com/godotengine/godot/pull/3180.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180.

Still in 2015 over here.. 23:00 Will merge in an hour!
On Dec 31, 2015 22:43, "George Marques"<EMAIL_ADDRESS>wrote:

It's better to update in all files, not only the license.
Em qui, 31 de dez de 2015 23:23, AQNOUCH Mohammed <
<EMAIL_ADDRESS>escreveu:

You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/3180
Commit Summary

Updated copyright to 2016

File Changes

M LICENSE.md
https://github.com/godotengine/godot/pull/3180/files#diff-0 (2)

Patch Links:

https://github.com/godotengine/godot/pull/3180.patch
https://github.com/godotengine/godot/pull/3180.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180.

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180#issuecomment-168273498.

Still in 2015 over here.. 23:00 Will merge in an hour!
On Dec 31, 2015 22:43, "George Marques"<EMAIL_ADDRESS>wrote:

It's better to update in all files, not only the license.
Em qui, 31 de dez de 2015 23:23, AQNOUCH Mohammed <
<EMAIL_ADDRESS>escreveu:

You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/3180
Commit Summary

Updated copyright to 2016

File Changes

M LICENSE.md
https://github.com/godotengine/godot/pull/3180/files#diff-0 (2)

Patch Links:

https://github.com/godotengine/godot/pull/3180.patch
https://github.com/godotengine/godot/pull/3180.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180.

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/3180#issuecomment-168273498.

@reduz  thanks and happy new year

@reduz  thanks and happy new year


Add a link to the DevByte video in the README.md

Added a link to the DevByte video https://www.youtube.com/watch?v=HxbidYYAek8 in the prereqs section.

I signed it!


Preprosessed vtab-1k zip file is broken

Hi authors,
Thank you for sharing the source code for you inspirational work! I wanted to mention to you that the vtab-1k dataset you shared on onedrive seems broken. The error message I got when I tried to unzip the file is "Error 79 - Inappropriate file type or format". Could you kindly help to look into the issue?
Update:
I figured out the correct way to unzip the five split .tar.gz files. The following command works for me
cat filename.tar.gz.* | tar -zxv

Hi authors,
Thank you for sharing the source code for you inspirational work! I wanted to mention to you that the vtab-1k dataset you shared on onedrive seems broken. The error message I got when I tried to unzip the file is "Error 79 - Inappropriate file type or format". Could you kindly help to look into the issue?
Update: I figured out the correct way to unzip the five split .tar.gz files. The following command works for me
cat filename.tar.gz.* | tar -zxv

have you deal with this problem @yushuinanrong


Not able to get correct ouput for tables

Hi,
I am currently using tesseract version 3.05 with leptonica version 1.73.
I want to get the ouput from an image which consists of tables of numerical data.
But  the output which I am getting after the processing of tesseract is way different than the original image.
Should I modify anything in the config file or the code to make it work?
A reference  is attached which is similar to the original image.
https://www.google.com/search?q=sensex+data&espv=2&biw=1280&bih=914&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjaxcG9oZbSAhXDVyYKHXKjBnIQ_AUICCgD#imgrc=REJCkEnS1S-bLM:
Thank You.

You need to pre process your image.
Convert to black and white and 300 dpi.
See attached files for image converted using Irfanview, processed using --oem 0 (legacy tesseract ocr engine) and --oem 1 (new lstm engine).
#!/bin/bash
export TESSDATA_PREFIX=/mnt/c/Users/User/shree/tesseract-ocr

    img_files=$(ls ./Sen*bw.png)
    for img_file in ${img_files}; do
        ls ${img_file}
        filename=$(basename "${img_file##*/}" .png)
        echo ${filename} "oem 1"
        time tesseract ${img_file} ${filename}-eng-oem1  --oem 1 --psm 6 -l eng   logfile
        cp tesseract.log ${filename}-eng-oem1-log.txt
        echo ${filename} "oem 0"
        time tesseract ${img_file} ${filename}-eng-oem0  --oem 0 --psm 6 -l eng   logfile
        cp tesseract.log ${filename}-eng-oem0-log.txt
    done

./SensexMonthly-bw.png
SensexMonthly-bw oem 1

real    2m19.615s
user    4m52.203s
sys     0m7.031s

SensexMonthly-bw oem 0

real    0m30.366s
user    0m27.828s
sys     0m0.781s

SensexMonthly-bw-eng-oem0.txt
SensexMonthly-bw-eng-oem1.txt

Hi Shreeshrii,
Thanks for your reply.
I am able to get the desired output with the preprocessing of the images.
Cheers!

Another option:
https://github.com/tesseract-ocr/tesseract/issues/736#issuecomment-381418910
Should be tested on all supported platforms.
You can replace putenv with _putenv
https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/putenv-wputenv?view=vs-2017


Decide on a common format for the documents to be collected in the language specific corpora

The first documents we have collected show already a diversity of formats: from plain text files to XML files embedding some metadata.
We should enumerate what common formats are generally used to share corpora (document content + metadata) and then decide on the format to adopt for the Odeuropa corpora.

This corpus is not the benchmark, and therefore we aim at having as many documents as possible (possibly with little effort). To me the simplest way to store these data would be a plain text + separate metadata (tsv or excel) with basic information. It will not always be possible to have metadata at document level, so we have to allow having metadata at repository level. This corpus is meant to be processed with NLP tools, which require plain text in input in most of the cases. So if we opted for any other format (TEI or similar) we would need to clean them of all tags anyway.


Kubernetes Ingress: Buffering annotation is not recognised.

Do you want to request a feature or report a bug?
(Potential) Bug
What did you do?
I tried to configure buffering for an Kubernetes Ingress.
What did you expect to see?
The buffering annotation getting recognised and applied.
What did you see instead?
Nothing, no error in the log, nothing in the dashboard.
I tried removing "traefik" from the annotation. I added it back, tried different things I found online.
Traefik does not seem to notice the annotation at all.
And the documentation was not very percise how it should be configured correctly, it only dokuments that the annotation exists.
Output of traefik version: (What version of Traefik are you using?)
Traefik docker container 1.7.1
What is your environment & configuration (arguments, toml, provider, platform, ...)?
# (paste your configuration here)

Kubernetes Ingress Annotation
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    traefik.ingress.kubernetes.io/buffering: |
      maxrequestbodybytes: 10485760
      memrequestbodybytes: 2097153
      maxresponsebodybytes: 10485761
      memresponsebodybytes: 2097152
      retryexpression: IsNetworkError() && Attempts() <= 2
    kubernetes.io/ingress.class: traefik

If applicable, please paste the log output in DEBUG level (--logLevel=DEBUG switch)

Hi @Flyffies ,
We think that your problem is in your yaml configuration file because we tested this option here https://github.com/containous/traefik/blob/v1.7/provider/kubernetes/kubernetes_test.go#L908
Could you use https://yaml-multiline.info/ and double check your configuration?

Hi @jbdoumenjou,
I put my YAML through a yaml validator, and it is valid. The multiline part gets read correct.
However, the newlines get converted into '\n's. Maybe they dont get read correctly when inside the annotation? I extracted the annottion and ran it through the validator as well. When replacing the \n with a newline it was also valid...
I just get it to work and the log contains nothing...

could try:
    traefik.ingress.kubernetes.io/buffering: |-
      maxrequestbodybytes: 10485760
      memrequestbodybytes: 2097153
      maxresponsebodybytes: 10485761
      memresponsebodybytes: 2097152
      retryexpression: IsNetworkError() && Attempts() <= 2

Sorry for getting back so late... I tried it, and it does not work... Traefik is still not able to pick the annotation up.
Here is my complete Ingress:
`apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: traefik
traefik.ingress.kubernetes.io/buffering: |-
maxrequestbodybytes: 10485760
memrequestbodybytes: 2097153
maxresponsebodybytes: 10485761
memresponsebodybytes: 2097152
retryexpression: IsNetworkError() && Attempts() <= 2
name: demo-app
namespace: default
spec:
rules:

host: demo.
http:
paths:

backend:
serviceName: demo-app
servicePort: 80
`

In fact, the annotation must be set on the service not on the ingress.
I updated the documentation https://github.com/containous/traefik/pull/3991

Thanks, yes. Now it works.


feat: prepare for release v0.2

update the fuseml-core deployment to use the release fuseml-core
image tag instead of the dev tag

Please add this change https://github.com/jsuchome/fuseml/commit/790f4f24bf76fd952ff42d1a50092199ce061cba

Please add this change jsuchome@790f4f2

done


Tracking: deprecate sha256 attribute in fetchers in favor of hash = ""

When we did not support SRI hash, we wrote a lot of sha256 = "...", and some of new PRs are still written with this attribute. However, when using an empty string to obtain the correct hash from the error, the SRI hash is obtained, which causes some confusion.
Let's move on from this old attribute. I don't expect to remove it within a certain period of time, but we can throw a warning to prevent this type of writing from continuing to appear in nixpkgs.
I did an experiment last time with cargoHash in https://github.com/NixOS/nixpkgs/pull/323983. I wrote the following script for this:
#!/usr/bin/env bash

process_line() {
    local filename=${1%:}
    if [[ $4 =~ \"(.*)\"\; ]]; then
      local sha256="${BASH_REMATCH[1]}"
    fi

    [[ -z $sha256 ]] && return 0

    local hash=$(nix hash to-sri --type sha256 $sha256)

    echo "Processing: $filename"
    echo "  $sha256 => $hash"

    sed -i "s|sha256 = \"$sha256\"|hash = \"$hash\"|" $filename
}

# split output by line
grep -r 'sha256 = ' . | while IFS= read -r line; do
    # split them further by space
    read -r -a parts <<< "$line"
    process_line "${parts[@]}"
done

We can deprecate each fetcher's sha256 separately, instead of the entire hash, to avoid the burden of review:

[ ] fetch-scm
[ ] fetchCrate
[ ] fetchDebianPatch
[ ] fetchDockerConfig
[ ] fetchDockerLayer
[ ] fetchFirefoxAddon
[ ] fetchFrom9Front
[ ] fetchFromBitbucket
[ ] fetchFromGitHub
[ ] fetchFromGitLab
[ ] fetchFromGitea
[ ] fetchFromGithub
[ ] fetchFromGitiles
[ ] fetchFromRepoOrCz
[ ] fetchFromSavannah
[ ] fetchFromSourcehut
[ ] fetchHex
[ ] fetchMavenArtifact
[ ] fetchNextcloudApp
[ ] fetchNpmDeps
[ ] fetchNuGet
[ ] fetchPypi
[ ] fetchPypiLegacy
[ ] fetchRepoProject
[ ] fetchTarball
[ ] fetchYarnDeps
[ ] fetchbower
[ ] fetchbzr
[ ] fetchcvs
[ ] fetchdarcs
[ ] fetchdocker
[ ] fetchegg
[ ] fetchfossil
[ ] fetchgit
[ ] fetchgitLocal
[ ] fetchgx
[ ] fetchhg
[ ] fetchipfs
[ ] fetchit
[ ] fetchmail
[ ] fetchmail_7
[ ] fetchmtn
[ ] fetchpatch
[ ] fetchpatch2
[ ] fetchpijul
[ ] fetchs3
[ ] fetchsvn
[ ] fetchsvnrevision
[ ] fetchsvnssh
[x] fetchtorrent (Looks like there is no support for sha256 attribute?)
[ ] fetchurl
[ ] fetchutils
[ ] fetchzip

the SRI hash is obtained, which causes some confusion.

You can still use the SRI sha256 hash in the sha256 attr.
(Not disagreeing with the deprecation though.)

(Taking the opportunity to plug the related lib.fakeHash, which maybe only I use, because it lets you avoid remembering how many As you need.)

You can still use the SRI sha256 hash in the sha256 attr.

Yes, it's like sha256 = "sha256-...", if after some day we decide to use sha512 by default, it will become sha256 = "sha512-"

@emilazy I usually just use "" honestly, as Aleksanaa mentioned.
Anyway, discussing strategy: should we remove the usages first for a given fetcher, before we add the warnings?
And your example bash script, it may work safely for something like cargoHash as you did in https://github.com/NixOS/nixpkgs/pull/323983, because we know it will only affect the rust builder/fetcher. But sometimes people use custom builders and scripts (especially update scripts) that may break with this. I will try to come up with a more robust script that only touches one fetcher at a time.

Anyway, discussing strategy: should we remove the usages first for a given fetcher, before we add the warnings?

Yes, otherwise ofBorg will fail?

I will try to come up with a more robust script that only touches one fetcher at a time.

I'm adding one more grep like grep -rl "fetchFromBitbucket" . | xargs grep -r 'sha256 = ' | while IFS= read -r line; do and it turned out well. But update script is indeed a problem and it is not within the scope of our scan.

(Thank you, I had no idea "" works! I could swear it didn’t in the past. Sorry for the tangent.)

Yes, otherwise ofBorg will fail?

I didn't know borgo fails on warnings. But anyway I meant, keeping the 0-rebuild treewide in a separate PR would make it easier to avoid merge conflicts and mixing of logical changes.

I'm adding one more grep like grep -rl "fetchFromBitbucket" . | xargs grep -r 'sha256 = ' | while IFS= read -r line; do

Some packages have multiple fetcher or people doing some custom constructs in the same file, which is why I'll try to avoid grep in this way if possible.

There are many fetchers that are based on others(fetchFromOrCz is based on fetchzip, fetchFrom9Front is based on either fetchurl or fetchgit, etc). Will the sha256 attribute have to be deprecated in those fetchers first, or in the underlying ones?

So I wrote this script:

my script
#!/usr/bin/env bash

EDITED_LOG=./edited-log
PROBLEM_LOG=./problem-log
SEARCH_CACHE=./search-cache

mkfifo nix_repl_in
mkfifo nix_repl_out

trap "rm -f nix_repl_in nix_repl_out" EXIT

# if replacing more files we can remove 2>/dev/null
nix repl < nix_repl_in > nix_repl_out 2>/dev/null &
NIX_REPL_PID=$!

sleep 2

exec 13>nix_repl_in
exec 14< nix_repl_out

extract_output() {
  output=$(echo $1 | ansi2txt)
  if [[ $output == "\"\"" ]]; then
    return 1
  elif [[ $output =~ ^\"([^\"]+)\"$ ]]; then
    echo "${BASH_REMATCH[1]}"
  elif [[ $output == "null" ]]; then
    echo "null"
  else
    return 1
  fi
}

send_repl() {
  local cmd=$1
  echo "$cmd" >&13
  echo "$cmd" > ./repl_in
  while IFS= read -r -d $'\n' line <&14; do
    if [[ -z "$line" ]]; then
      return 1
    else
      echo "$(extract_output $line)"
      echo "$line" > ./repl_out
    fi
  done
}

replace_hash() {
  local attr_name=$1

  local hashAlgo=$(send_repl "${attr_name}.src.outputHashAlgo") || return 1
  # Only to limit scope here, can be adjusted
  local hashHomepage=$(send_repl "${attr_name}.src.meta.homepage") || return 1

  if [[ "$hashAlgo" == "sha256" ]] && [[ "$hashHomepage" == "https://gitlab.com/"* ]]; then
    local hash=$(send_repl "${attr_name}.src.outputHash") || return 1
    # echo "$attr_name hash"
    if [[ "$hash" == "sha256"* ]]; then
      local position=$(send_repl "${attr_name}.meta.position") || return 1

      [[ $position == "null" ]] && return 1

      local position_file=${position%%:*}

      grep -q "sha256 = \"$hash\"" $position_file
      if [ $? -eq 0 ]; then
        local outPath=$(send_repl "${attr_name}.outPath") || return 1
        echo "editing: ${attr_name}:${position_file}"
        sed -i "s|sha256 = \"$hash\"|hash = \"$hash\"|" $position_file
        echo "${attr_name}:${position_file}:${outPath}" >> $EDITED_LOG
      fi
    fi
  fi
}

verify_hash() {
  local attr_name=$1
  local position_file=$2
  local outPath=$3

  local new_outPath=$(send_repl "${attr_name}.outPath")
  if [ $? -ne 0 ] || [[ "$outPath" != "$new_outPath" ]]; then
    echo "problem: ${attr_name}:${position_file}"
    # echo "'$outPath' != '$new_outPath'"
    echo "${attr_name}:${position_file}:${outPath}" >> $PROBLEM_LOG
  fi
}

[[ -f "$SEARCH_CACHE" ]] || nix search . ^ --json > $SEARCH_CACHE

pkg_list=($(cat $SEARCH_CACHE | jq --raw-output 'keys_unsorted | @sh'))

send_repl ":l ./."

sleep 1

echo "starting to replace"

for pkg_raw in ${pkg_list[@]}; do
  pkg=${pkg_raw#*.*.}
  pkg=${pkg%\'}
  replace_hash $pkg
done

send_repl ":r"

sleep 1

echo "starting to examine"

while IFS= read -r line; do
  IFS=':' read -r -a parts <<< "$line"
  verify_hash ${parts[@]}
done < "$EDITED_LOG"

It depends on jq and ansi2txt. Currently, because it is single-threaded logic, a treewide operation takes about 10 minutes. Feel free to modify it according to your ideas.

Just noticed in the list, but fetchit is not a fetcher, it's a podman tool. Should probably be removed.

I tried GitHub (only editing sha256 = "sha256-), and there are 3000+ direct editions, including 1000+ objections (we can modify the check to revert changes directly, using sed or git, depending on the speed). We can still edit 2000+ files painlessly after all. Might be related to https://github.com/NixOS/nixpkgs/issues/301014

Just noticed in the list, but fetchit is not a fetcher, it's a podman tool. Should probably be removed.

I've given up that list, because we cannot actually determine which fetcher it is (except for those that only serve specific sites)


Video_Player plugin issue in iOS

Hello,
Video_player plugin cannot play video streams from servers which does not support HTTP range header. In logs appear message "flutter: Failed to load video: Operation Stopped". This issue is only in iOS, in Android it play this stream without problem.
Example url stream: "https://stream.dpsu.gov.ua:5101/publicLive/194/mainStream"

@kaiv2000
There's already a similar open issue describing your case, https://github.com/flutter/flutter/issues/56665
Follow-up there for updates.
Closing this as duplicate.


[FLINK-29432][flink-connector-hive]Replace GenericUDFNvl with UDFCoalesce

What is the purpose of the change
hive nvl function have known problem
Brief change log
flink-connector-hive
Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)
no

Documentation

Does this pull request introduce a new feature? (yes / no)  no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@y0908105023 did you get any chance to look at the failure ?
it would be great if you can
thank you

@flinkbot run azure

@Samrat002  the failure had resolved


[Windows] Update VCTools v143 to 14.35

Description
Update Visual Studio VCTools v143 individual components from 14.34 to latest 14.35.
Related issue: #7487
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run windows2022


Default PropTypes in nested object

Nested default props are not merged. (Editor::language) Solve defaults other way.

#84


Fix/DEV-8433: Fix sequential slicing of images

Replaces Promise.all with an anonymous async function with a for loop that awaits each image slice command's completion before proceeding to the next. Previously, I was using an await inside a .map which does not wait for the function to resolve before moving to the next item... all it does is allow you to execute a callback after that item has completed.

@hbalenda this is working for me now!

Agreed. I updated DEV-8601 (Refactor imageslice) with a note to replace the self-invoked function with a task queue.


Sortable table header row buttons mis-aligned, missing role and incorrectly styled

Sortable table header row buttons mis-aligned, missing role and incorrectly styled
Header row buttons should be:

inheriting link style text-underline-position
accessible with role=link attribute
left-aligned with column cells content

Originally posted by @jrbarnes9 in https://github.com/ONSdigital/design-system/discussions/102#discussioncomment-1430774

Resolved in #1744


feat: overwrite task url and url meta

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

Overwrite task url and url meta.

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1740 (b4333c6) into main (3f9309c) will increase coverage by 0.27%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1740      +/-   ##
==========================================
+ Coverage   43.59%   43.87%   +0.27%
==========================================
  Files         128      128
  Lines       15863    15874      +11
==========================================
+ Hits         6916     6965      +49
+ Misses       8421     8384      -37
+ Partials      526      525       -1

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
43.87% <100.00%> (+0.27%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

scheduler/service/service.go
76.68% <100.00%> (+0.38%)
:arrow_up:

client/daemon/peer/peertask_conductor.go
57.01% <0.00%> (+0.65%)
:arrow_up:

...ent/daemon/peer/peertask_piecetask_synchronizer.go
51.09% <0.00%> (+0.93%)
:arrow_up:

client/daemon/peer/peertask_piecetask_poller.go
48.63% <0.00%> (+14.20%)
:arrow_up:


Pubs 1439

I had to remove the the json keyfile from this repo and the command I used apparently recomitted every file. Look for anything under the pubs_ui/metrics directory. Also worth looking at is config.py, assets.py and pubs_ui/init.py. Sorry about that

I borked this badly that I'm closing it.


Add Utils library project

Open source SDKUtils source code from the private Windows repo to MSIX SDK repo so that it is available for the Windows community to collaborate/contribute to. This supports our org-wide goal to open source as much of our code as we can. This will also enable us to take other services open source.

I am kind of worry that the main directory is called SDKUtils. I think that seeing SDKUtils in a repository where people finds the MSIX SDK will make them think that it is related to it, even though it is not and we are sticking here because reasons...
We already have an #350 that says that the structure of the repo is confusing

Understood. Do you have any suggestions for the name? Given the contents of this library I can't think of a better description than utils/utilities. Maybe simply "Utils" so that it doesn't seem as related to the MSIX SDK?

agreed about naming as per thread. Something like Tools could also work.

In reply to: 662024211 [](ancestors = 662024211)

ah. luis too fast and github->codeflow intergration is pain

In reply to: 662089037 [](ancestors = 662089037,662024211)

Ping?

//-----------------------------------------------------------------------

Is the PR history public?  You may need to purge that... for reasons...

Refers to: tools/utils/Utils/Telemetry/Telemetry.cs:1 in 042e244. [](commit_id = 042e244a3a818b6337828f18765c0fc9d4420981, deletion_comment = False)

Consider modifying the CODEOWNERS file. As it is right now, Ran, John and I will show as the required reviewers.


Disable (Previous / Next) buttons when there is no previous / next page

Should not be able to interact with the previous / next buttons when the page does not exist!

Grey out the button and make it none intractable in the case it doesn't have a page to go to

Hi
This issue has been fixed alongside this issue here.
Thank you for your feedback!


Instrumenting Apache Kafka clients with OpenTelemetry

To observe the full trace on the backend, is it necessary to keep the producer's service name as same as the consumer's service name in the environment variables?

@ppatierno can you help with that? Thanks.

@sweetxiaodai I guess your question is related to the one you opened on my own repo here https://github.com/ppatierno/kafka-opentelemetry/issues/10, let's keep the discussion in one place. I think the OpenTelemetry repo is the best place to discuss.
So, in general having the same service name on both side, helps for sure having all the spans to be in the same place on the Jaeger UI (not needed to jump across services). I have never tried if Jaeger UI is able to correlate if service names are different.
Said that, are you using the Java agent to instrument your producer and consumer? In this case, producing and consuming are correctly on different traces but they are referenced so that you can jump from receiving to producing. This is why in a messaging system like Kafka, everything happens async. You can read more about this in this blog post: https://opentelemetry.io/blog/2022/instrument-kafka-clients/ . See more detailed comments in the https://opentelemetry.io/blog/2022/instrument-kafka-clients/#instrumentation-in-action section.

Thanks @ppatierno
I've read the blog and keep the service name of producer and consumer as one. But how ever I still got a broke span.
I put my code in the two repositories, it will help you reproduce the issue. I don't think the issue could be closed. Sorry.
https://github.com/sweetxiaodai/kafka-otel-producer.git
https://github.com/sweetxiaodai/kafka-otel-consumer.git
Would you mind kindly use the code reproduce the issue or let me know where is the incorrect part of the configuration?
I also put my environment variables here to help you to identify the issue.
producer env:
jvm options:
-javaagent:/Users/genesis/otel/opentelemetry-javaagent.jar -Dotel.service.name=kafka-trace
'''
OTEL_TRACES_EXPORTER=jaeger;
OTEL_EXPORTER_JAEGER_ENDPOINT=http://localhost:14250;
OTEL_SERVICE_NAME=kafka-trace`
'''
consumer env:
jvm options:
-Dotel.service.name=kafka-trace -javaagent:/Users/genesis/otel/opentelemetry-javaagent.jar -Dotel.instrumentation.messaging.experimental.receive-telemetry.enabled=true
'''
OTEL_TRACES_EXPORTER=jaeger;
OTEL_EXPORTER_JAEGER_ENDPOINT=http://localhost:14250;
OTEL_SERVICE_NAME=kafka-trace
'''

What do you mean by broken trace?
Using my project at https://github.com/ppatierno/kafka-opentelemetry I was able to run a producer and consumer together with the opentelemetry agent. I get what I explained in the blog post.

one producer span in its own trace
two consumer span (receive and process) in its own trace but with ...

"operationName": "my-topic process",
                    "references": [
                        {
                            "refType": "FOLLOWS_FROM",
                            "traceID": "506ab16d27fe0cdca459e90238096755",
                            "spanID": "15abd6951658f94e"
                        },
                        {
                            "refType": "CHILD_OF",
                            "traceID": "940a5b7ae354b0eaa0b3ab478fd76f4c",
                            "spanID": "cadbe6a14b07a315"
                        }
                    ],

... where the process span is CHILD_OF receive in the same consumer trace but it FOLLOWS_FROM the send in the producer trace.

Hi @ppatierno
Sorry to make you confused. I attached the screen shot in jaeger. The send and receive span are in different trace looks like. Is there any way to link it together? I just developed two application, one is the consumer and the other one is the producer, but looks like the spans of sending and receiving cannot combine as a whole trace.
I will try to use your code to verify again. I have same problem when I tested the Rocket MQ. Some incompatible dependencies's version caused the issue. Then I use lower version of the driver, then it works fine. I guess this time it was the similar problem.

As I mentioned in the blog post but even in my previous comment, as OpenTelemetry works with messaging is about having them leaving in two different traces but they are linked together (see my JSON above). Can you provide the JSON representation of your spans and traces to see that?
I also think this discussion could clarify your doubts https://github.com/open-telemetry/opentelemetry-specification/discussions/2695

Ok, finally, I got your point. But it is different with otel rocketMQ. otel RocketMQ could put all spans in one trace.
I attached two json.
I do find the follows_from's traceID is as same as the producer traceID. I will try to read your post to understand the mechanism. How did you figured out the produced trace and consumed trace belongs one message?
Thanks so much for your patient. It is really helpful.
producer
{
    "data": [
        {
            "traceID": "aff05b721bafcae46cca80290db1d9a6",
            "spans": [
                {
                    "traceID": "aff05b721bafcae46cca80290db1d9a6",
                    "spanID": "d4ddb09c305eef71",
                    "operationName": "KafkaController.publish",
                    "references": [
                        {
                            "refType": "CHILD_OF",
                            "traceID": "aff05b721bafcae46cca80290db1d9a6",
                            "spanID": "a9407380777c3dff"
                        }
                    ],

consumer
    "data": [
        {
            "traceID": "9ad022e836cea34c065bafeaae86bb90",
            "spans": [
                {
                    "traceID": "9ad022e836cea34c065bafeaae86bb90",
                    "spanID": "5ad0544c9856e92c",
                    "operationName": "topic1 process",
                    "references": [
                        {
                            "refType": "FOLLOWS_FROM",
                            "traceID": "aff05b721bafcae46cca80290db1d9a6",
                            "spanID": "708058c7be78e595"
                        },
                        {
                            "refType": "CHILD_OF",
                            "traceID": "9ad022e836cea34c065bafeaae86bb90",
                            "spanID": "66397c1cf6b115cc"
                        }

I have never used RocketMQ, but I would expect to have the spans in the same trace when we are talking about a queue messaging pattern. Producer sends, just one consumer will get the message, process and delete it. Just one trace.
With Kafka, you can have consumers in different consumer groups getting the same message from the topic and also you could re-read the entire stream of events, so re-read the messages. Using one trace will make a mess in this scenarios. Better is having multiple traces (representing the send and receive on their own) but linked together.
I could expect the same if using a messaging system with pub-sub pattern.

Thanks and close the issue.


fix: fix out-of-sync logger type definition

Logger now extends from EventEmitter
(sidenote: apologies for not following the commit guidelines before, I wasn't thinking)

Thanks, @relative.  We need to do a better job of validating this file.  We don't use Typescript and are providing this as a courtesy, but seems like our test suite needs to incorporate a use of it so we can verify it.  I'll look into that.

@relative we're changing our CI process to build on fork PRs.  Make sure that if you're "following" a project, make sure it's not your fork.  CI will fire once this is merged, so I think it's ok for now to proceed.
https://circleci.com/docs/2.0/oss/#build-pull-requests-from-forked-repositories


Fix crash due to not defined enum bit flag option

We observed crashes like these for two users:
Exception name=RCTFatalException: Exception '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil' was thrown while invoking getAssets on target CameraRollRNPhotosFrameworkManager with params (
        {
        endIndex = 60;
        fetchOptions =         {
            mediaTypes =             (
                image
            );
            sortDescriptors =             (
                                {
                    ascending = 0;
                    key = creationDate;
                }
            );
        };
        includeMetaData = 1;
        prepareForSizeDisplay =         {
            height = "131.3333333333333";
            width = "131.3333333333333";
        };
        startIndex = 0;
    },
    164,
    165
)

...

After much digging through the code I am quite certain the problem is in RNPFHelpers. nsOptionsToArray. iOS 10.2 introduced PHAssetMediaSubtypePhotoDepthEffect (for iPhone 7+ and these two users both have it) which is not defined in RCTConvert+RNPhotosFramework.m. https://developer.apple.com/reference/photos/phassetmediasubtype?changes=latest_minor&language=objc
This PR just fixes testing that the option has a value, so that this doesn't crash for this one nor when when Apple adds new flags.
It doesn't add definition for PHAssetMediaSubtypePhotoDepthEffect because it is specified under "Type Properties" where the others are specified under "Constants" and I don't know what the difference is, plus I don't know if defining it would means that the library depends on iOS 10.2? I guess not but maybe just the most recent version of the SDK...

Ah!
Had missed that one. I had already added PHAssetCollectionSubtypeSmartAlbumDepthEffect but not this option. But your absolutely right, when should have a guard here if new values arrive.
I Think we should add this new type. If anyone have problems with SDK-compatibility down the line, we look at it then. I will add the value. and merge this.

👍


[SPARK-34504][SQL] Avoid unnecessary resolving of SQL temp views for DDL commands

What changes were proposed in this pull request?

For DDL commands like DROP VIEW, they don't really need to resolve the view (parse and analyze the view SQL text), they just need to get the view metadata.
This PR fixes the rule ResolveTempViews to only resolve the temp view for UnresolvedRelation. This also fixes a bug for DROP VIEW, as previously it tried to resolve the view and failed to drop invalid views.
Why are the changes needed?

bug fix
Does this PR introduce any user-facing change?

no
How was this patch tested?

new test

cc @linhongliu-db @imback82 @maropu

Test build #136119 has started for PR 31853 at commit 5bcb9b5.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40701/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136122/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40704/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40704/

Test build #136119 has finished for PR 31853 at commit 5bcb9b5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136119/

Hm, the scala-2.13 build failure seems to be not related to this PR and it is reported in https://issues.apache.org/jira/browse/SPARK-34762.

yea the scala 2.13 issue is not related, I'm merging it, thanks for the review!

late LGTM


build: propagate ASAN/TSAN flags down to cmake_external deps.

While we await a solution for bazelbuild/rules_foreign_cc#154 (comment), this PR provides a
temporary workaround to get full ASAN/TSAN propagation as needed.
This continues https://github.com/envoyproxy/envoy/pull/6061, which had accumulated too much
complicated merge history to work with after the recent gperftools/LuaJIT migration to
rules_foreign_cc.
Risk level: Low
Testing: --config=clang-{tsan,asan}. This is broken in the latest CI images due to the mismatched
linker/compiler flags we previously had been sending to cmake_external builds.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

OK, this is great, we don't need the gperftools patch after moving over to rules_foreign_cc 👍

It looks that the Lua tests are failing with ASan/TSan, could you investigate? Though, the issue is most likely with Lua itself, and not with your changes, which only uncovered it.

@PiotrSikora I know, I'm digging into this now. I'm hoping I can figure out a way to workaround these Envoy side, if not upstream, in a timely way, this is blocker for the coverage work atm.

@htuch another way to approach this, assuming Lua issues are going to take more than a day or two to resolve, is to temporarily exclude Lua tests from ASan and TSan runs, since this PR is an improvement, all things considered, and it's not the reason for the breakage.

or blacklist Lua itself from being instrumented by ASAN? https://github.com/google/sanitizers/wiki/AddressSanitizer#turning-off-instrumentation

@lizan I think I'll blacklist, I've been looking at these errors and there are a few different varieties. We need someone to spend some serious time looking at this, it's not a high priority right now for us though.

Sigh, now we have some unrelated LSAN issue with host protoc, I guess we can disable LSAN but not sure why it started happening now..

@htuch I see that on some other PRs as well, so it might not directly related to this PR. Could be some docker capabilities issue with Circle.
/retest

@lizan I think I have a fix based on what you did for LuaJIT. This should hopefully help other PRs.

@htuch seems it didn't help, LeakSanitizer has encountered a fatal error is probably something that LSAN bug or LSAN itself couldn't recover... I'm not sure why protoc is build with ASAN, as the flags are not set to host_cflags, no?

@lizan I don't think there is a clear split of host/target in https://github.com/protocolbuffers/protobuf/blob/master/BUILD. I will continue to investigate in this PR.


fix: Allow dns_name for vpces to be optional

What type of PR is this? (check all applicable)

fix: A bug fix

Description
Allows private dns name for VPCES to be optional

This PR is included in version 1.6.6 :tada:


Hugo arguments as sub directives

Instead of writing args "--buildFuture true"  we could write: buildFuture true, and so on.

If you do this, then drop "true", since if the term appears, we assume that means "turn it on"


Proposal
I would like to customize the validation hint "Please enter valid url.".
Willing to submit a PR?
None

You can configure via
NgxEditorModule.forRoot({
  locals: {
    enterValidUrl: "Please enter a valid URL",
  },
});


Auto formatting

Automatically assign a geometry format based on the filename (e.g. .xyz, .zmt). Alternatively, attempt to parse the input with different formats. Can set fmt='auto' as the default.
Output should be similar: based on the provided filename (or on the format of the input?).

Input auto formatting: Is there an 'natm' line? Is there a comment line? Where are the strings located? How many elements per line? Need to distinguish int vs. float vs. str for each item to recognize pattern.
Output auto formatting: By filename extension (.xyz, .col, .columbus, .zmt, .zmat, .dat; default: xyz).


Add extra params support

Prosed fix for #2

Hey! Thanks for the PR, it looks like a great way to do this is to raise a pr at https://github.com/ateodorescu/home-assistant-ipmi, given that it's the source for this repo and I'm not necessarily the person to review changes to that core PHP server and don't have a good enough grasp on it to evaluate the PRs, I'm sure you understand!


Avatar

Everything looks good . just use rems instead of px

Thanks, Lomesh and Arsalan. Merging now :)


how to notification message on  "onSubmit" hook?

I would like alert message when onSubmit hook successful:
onSubmit: function (insertDoc, updateDoc, currentDoc) {
            // Do any thing here
            Notifications.success('User', 'User is inserted successfully.');
        }

but don't show `alert'.

This seems like a notifications issue, not autoform.

but now i chage to alert('Hi');, It don't work too.


fix: issue in google module when creating a fresh cluster in 1.27

fix: issue in google module when creating a fresh cluster in 1.27
Description
The purpose of this PR is to apply some patches in the google module:

replace deprecated gavinbunney/kubectl which is not working since 1.27 by alekc/kubectl.
fix iam permissions by removing the usage of module when the resources cannot be known in advance.
fix dependencies

Please explain the changes you made here and link to any relevant issues.
Checklist

[x] CI tests are passing
[x] README.md has been updated after any changes to variables and outputs. See https://github.com/particuleio/terraform-kubernetes-addons/#doc-generation

@ArchiFleKs @rguichard My previous PR: #2481 was closed


License

Hey, this slider looks great. Any chance a license could be specified? https://choosealicense.com/

Here you go: https://github.com/mhkeller/svelte-double-range-slider/commit/0eda0d4d8a9a4350ddba87b423a1565dd1e8f9b7


Structure application architecture as a pipeline

First off: awesome project! I've been using an ad-hoc process to study chess with anki but I've never been totally happy with it. I think this utility has a lot of potential so thanks for putting it together!
My suggestion is to rework the architecture and move to a pipeline-style application with a controller and three distinct phases:

sources - build a pgn file with games
transformers - take a pgn file of games and build a pgn of "snippets" (pgn syntax but with a SetUp tag of 1, a FEN starting position and a few moves played out. I put an example at the bottom of this comment)
ankifier - take a pgn file of "snippets" and build anki cards

The lichess integration would be a "source"; integrations with chess.com, chessgames or chess24 could be other sources. Maybe interfacing with a Chessbase install could be another etc.
The mistakes/openings/tactics functionality would all be examples of various types of "transformers".
The ankifier would simply take these generated snippets and create anki cards.
Then the controller would be responsible for parsing the command line, handling all the state/config (eg api credentials and last downloaded game timestamp for a source), and gluing it all together so the user only has to type something like:

chessli lichess mistakes

to get their recent games from lichess downloaded/analyzed/ankified, instead of running each component in the pipeline on its own.
Or maybe

chessli chessgames:tid=54397 openings

to get cards on the openings used in the Fischer/Spassky match ankified from https://www.chessgames.com/perl/chess.pl?tid=54397
My reasoning for all this is that separating the full program into distinct pipeline phases with no shared state would allow easier contributions and extensions in the future. For instance, I could imagine writing up another transformer for memorizing games. It could take a pgn file and split it up into overlapping, 4-move snippets (moves 1-4 in the first pgn snippet, 3-6 on the next etc.) and with this architecture I could plug it right in and immediately be able to pull games from any of the included sources and make anki cards with zero additional effort. Likewise, if I want to add a source I don't have to build the entire pipeline, just getting a pgn with games is enough. I would also have the option to skip phases as needed, like if I already have a database of endgame positions as pgn "snippets" I can just plug it directly into the ankifier.
Anyways, this is just a thought, I don't know how far you want to take the utility or what use-cases you want to support, or if you even want to support it long-term lol. I just saw this and got excited for what it could be x). Feel free to delete/ignore this.
An example of a snippet might be: (Note, Lichess uses the [Variant] tag instead of the [SetUp] and [FEN] tags, maybe both styles should be supported)

[Event "F/S Return Match"]
[Site "Belgrade, Serbia JUG"]
[Date "1992.11.04"]
[Round "29"]
[White "Fischer, Robert J."]
[Black "Spassky, Boris V."]
[Result "1/2-1/2"]
[Variant "From Position"]
[FEN "rnbqkbnr/pp2pppp/3p4/2p5/4P3/5N2/PPPP1PPP/RNBQKB1R w KQkq - 0 3"]

d4 cxd4 4. Nxd4 Nf6 5. Nc3

Hey, thank you for your helpful input! I very much like your ideas!  :)
I agree that the current architecture isn't optimal. Part of the reason is that the codebase originated from a collection of hacky scripts. I did some refactoring when I open-sourced the project, but only as much as needed to make it work in this first iteration.
I will follow up in the next days on your ideas!
I think I it would be a good idea for a version 0.3. So the second next version update.

Hey, thank you for your helpful input! I very much like your ideas!  :)
I agree that the current architecture isn't optimal. Part of the reason is that the codebase originated from a collection of hacky scripts. I did some refactoring when I open-sourced the project, but only as much as needed to make it work in this first iteration.
I will follow up in the next days on your ideas!
I think I it would be a good idea for a version 0.3. So the second next version update.

Hey, while I appreciate your ideas, I decided after some deliberation that I won't (at least in the near future) support other backends than lichess.
The reason is that I don't know of any features that lichess doesn't have (especially as it is now really polishing up its tactics features) and I want to limit the feature-set to the minimally required in order to reduce maintenance and development efforts.
I'm open to any other ideas that require less heavy refactoring, however!

Yeah that's completely understandable. I just wanted to clarify real quick though that I didn't mean to suggest that you be the one to create all those sources/transformers, just that there be a strictly-defined data interface between the various stages of the "pipeline". If you do that and provide a reference implementation using Lichess then it would make it easier for other people to come along and contribute their own sources (or transformers) while still being able to leverage everything that's already been built.
ie If the Lichess source is only responsible for returning PGNs then all I have to do to contribute my own chess.com source is write a function that returns PGNs from chess.com. Everything else from that point on will be handled since the later stages of the pipeline would already know how to process those PGNs.
Same thing with transformers. If transformers are only responsible for taking in PGNs and returning PGN snippets then contributing transformers would be a lot easier. I don't have to have special logic for each source, or a special ankify function for my transformer. The sources already return PGNs and the ankifier already processes PGN snippets, so I only have to care about my specific PGN->PGN snippet transformation.
Still understandable if it's not something you want to take on; I just wanted to clarify because I think it would make it easier for outsiders to contribute functionality and easier to maintain long-term for you as well.

Thanks for the clarifications! That makes sense! I reopen this here and return to my initial answer that I want to tackle this with version 0.3 :D

Sorry for closing the issue again @jonprairie , but in the last month I realized that I won't be able to find the time for a larger rewrite of this project. Thank you again for the time you took to formulate and share your great ideas and I hope you still can find some value in this project even if I won't be able to remodularize it into your suggested pipeline structure.


Revive silk-testnode

Codecov Report

Merging #75 into master will increase coverage by 0.16%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
+ Coverage   93.36%   93.52%   +0.16%
==========================================
  Files          15       15
  Lines        1130     1128       -2
==========================================
  Hits         1055     1055
+ Misses         75       73       -2

Impacted Files
Coverage Δ

src/accountant_skel.rs
91.34% <100%> (ø)
:arrow_up:

src/accountant_stub.rs
96.03% <100%> (+0.89%)
:arrow_up:

src/historian.rs
100% <0%> (+1.31%)
:arrow_up:

Continue to review full report at Codecov.

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


Issue #128 (1st stage): Added drag&drop of input records on the allocation page.

Added drag&drop of input records, 1st approximation: only one-by-one, without multiple selection, no next phase.
Next tasks:

Correct comments on the current implementation.
Make multiple selection/dragging.
Start next stage ('allocation phase').

@lilliputten This is amazing work! There is some polish needed, but I am very, very impressed and happy.


fix(tests): suppress deprecation error of event_loop

The event_loop of pytest-asyncio should be closed explicitly, as shown in the following document.
https://github.com/pytest-dev/pytest-asyncio/tree/v0.18.3#event_loop
As of 0.18.3, which is fixed in pyproject.toml, it closes automatically, but as of 0.21.0, it throws an error.
It would be good to fix this for future updates.

Thanks for reporting! We'll take a look at this tomorrow.

Thanks for the fix @natsukium! We've pushed a fix separately that includes your changes and also bumps pytest-asyncio to the latest version in #114.

thanks!


the label helper method does not remove :as from the label_html

The label helper correctly changes the class from "string required" to "boolean required", but it adds as="boolean" to html output.
<% f.label, :name, {:as => :boolean} %>

* Name

:heart:

sorry, forgot to add "closes #472" to commit message. Close it somebody please

@nashby thanks again mate!! :heart:


documentation - patterns - larger applications - add link to explain why "Python does not want modules in packages to be the startup file"

This paragraph:

But how do you run your application now? The naive python yourapplication/__init__.py will not work. Let’s just say that Python does not want modules in packages to be the startup file.

could be summarized as:

You can't do that, and we won't explain why; just trust us.

In lieu of actually explaining, a link to the Python docs that actually do explain what's going on here seems in order.

A much more charitable and less snarky summary would be "plenty of our developers over years have experienced weird behavior when trying to run packages directly like that, but there's no straightforward documentation of all Python's weird behaviors; just trust us."
I'm not sure where that reference is, if it exists. I guess pallets/werkzeug#1416 is a good writeup of some of the the behavior I've encountered recently, but it's not something I want to subject most users to reading. If you have a reference to add, I'm happy to consider a PR, but I'm going to close this for now.

Your summary works for me. Having it footnoted, with a link to the Werkzeug ticket you mentioned, is a solution I like. If that makes since to you, would be happy to open PR.
Sorry if the ticket came off snarky. What I'm getting at here is that this section of the docs proposes a big leap for someone with a basic Flask app:

refactoring project directory structure
moving the app obj to __init__.py (a non-trivial piece of Python import's system to understand)
adding setup.py (which a newer developer might typically hear about in the context of distribution and distutils)

Given the big leap, felt like the existing explanation didn't sufficiently sell the necessity of making such changes.
I realize the Flask docs have been trying to walk the line between friendly-for-newcomers and scalable project structure since the rewrite for 1.0. My bias is friendly-for-newcomers; I realize it's a bias and hopefully am not being dismissive of other perspectives here.
Either way, thanks for responding, and thanks for passing along that Werkzeug ticket; really shows how hairy the problem can get :)


linuxKernel.packages.linux_6_1.zfs: unreproducible kernel modules

Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible-builds.org/ .
Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems.
Steps To Reproduce
nix-build '<nixpkgs>' -A linuxKernel.packages.linux_6_1.zfs --check --keep-failed

You can use diffoscope to analyze the differences in the output of the two builds.
To view the build log of the build that produced the artifact in the binary cache:
nix-store --read-log $(nix-instantiate '<nixpkgs>' -A linuxKernel.packages.linux_6_1.zfs)

Additional context
There seem to be different symbols included - perhaps some architecture/feature sniffing leaking through?

Please do not hesitate to assign me or ping me (as I am maintainer of ZFS now. True for any package which I am maintainer of which is not reproducible.)

Prior art:
https://github.com/NixOS/nixpkgs/issues/220662
https://github.com/NixOS/nixpkgs/pull/181456

I have what I think is a fix in #231768. Please let me know if you still encounter unreproducibility with this patch applied -- in my (limited) testing this issue is fixed.

Have we verified this works for everything and not just zfs?

I think it was a generic pahole patch for BTF generation, but this issue is about ZFS anyway, there's other issues for the general kernel unreproducibility.


update(doc, {$set: {object_field: {...}}}) doesn't work with type Object

When I attach a schema to a Collection with field of type: Object, and I update doc like this:
Coll.update(doc, {$set: {object_field: {test: "test value"}}})

I'm expecting to get this:
{"_id":"Zw7gEH2JkuaSAnwJr","title":"Introducing Telescope","object_field":{"test":"test value"}}
But I get this:
{"_id":"Zw7gEH2JkuaSAnwJr","title":"Introducing Telescope","object_field":{}}
This behavior seems wrong (otherwise, what's the correct way to specify schema?).
Here is my full test case.
Coll = new Mongo.Collection('coll');
Coll.attachSchema(new SimpleSchema({
  title: {
    type: String
  },
  object_field: {
    type: Object,
    optional: true
  }
}));

Meteor.methods({
  updateTest: function() {
    var doc = Coll.findOne({}, { sort: { title: -1 }});
    Coll.update(doc, {$set: {object_field: {test: "test value"}}})
  }
})

I may have a related bug except with a nested array. And when I try to do a $push operation
Meteor.users.update({_id: Meteor.userId()}, {$push: {'nestArray.0': 'test'}})
I get the error: Uncaught TypeError: Cannot read property 'blackbox' of undefined triggered by the line if (self.schema(schemaKey).blackbox === true) { in SimpleSchema.prototype.allowsKey
Here is my abridged schema
NestArray = new SimpleSchema({
  0: {
    type: [String],
    defaultValue: [],
  },
  '0.$': {
    type: String,
    regEx: SimpleSchema.RegEx.Id,
  },
  ...
});

User = new SimpleSchema({
  nestArray: {
    type: NestArray,
  },
  ...
});

So after digging into the code further, my issue is that any numeric object keys get auto converted into $ signs. Is there any way around this without changing to a 2D array?

@vonwao Add blackbox: true to object_field schema, or define test property in the schema.
@merlinpatt I don't think number keys are currently supported. 2d array or use zero.$ or something


Include an attribute for result generation timestamp

The date/time of result generation (or analysis result program execution) is usually needed for auditing purposes and may be included in, for example, display footers.
This also raises the question of whether it should be possible represent results from multiple executions of the analysis result programs.  If this is necessary (e.g., so that it's possible to compare results from separate executions of the the same version of the analysis), then it may be necessary to introduce to introduce something like "result sets" as timestamped sets of results, e.g.:

This was discussed on 2024-03-13 and it was agreed that this change should be considered for a future version of ARS because additional consideration is required. For example, while the proposal above suggests creating resultSets within the Analysis class, it's unclear whether it might be better to allow "result sets" to include results from more than one analysis.  One option for consideration could be to move results out of analyses (e.g., to be a separate component of the reporting event itself).  These results would need to retain a reference to the analysis that generated them (e.g., via analysisId), but could possibly be grouped in different ways.


UI needs an API explaining why a function isn't indexed or is returning 404

Currently the UI queries a function's keys. If that fails for any reason, we query the function status, if that also fails, we query the host status.
However we still have cases where keys is 404, status is 404, and host status is 200 no errors. More logs and analysis are included in an email with subject [Azure/Azure-Functions] Getting error: "We are not able to retrieve the keys for function "
Of course part of the problem stems from having 2 parts interpreting what a function is (kudu and the runtime)

This is a very generic issue. If there is a specific repro, we can make specific improvements, but otherwise this is a general feature request to give better e2e information on the state and errors wrong with a given Function.
This could also be related to "host-disabled" flavored issue and better handling those states: https://github.com/Azure/azure-webjobs-sdk-script/issues/950

check email with subject "[Azure/Azure-Functions] Getting error: "We are not able to retrieve the keys for function " for specific repro.

Would love to know what's wrong with my function then as I have no idea what's wrong with it currently.  Any feedback I'm being given from functions isn't giving me anything actionable.

@atrauzzi can you share your function.json and function code so that I can try to repro? If you prefer, send me an email at<EMAIL_ADDRESS>if you pref

@atrauzzi: @mamaso investigated and found that you are setting the functions property in your host.json, which causes all other functions to be ignored (see https://github.com/Azure/azure-webjobs-sdk-script/wiki/host.json). Do you remember doing that, or did that somehow get set by some tool or something else?

https://github.com/atrauzzi/anecdote-azure/blob/master/functions/host.json
Would appear as though I only have QueueScans listed here.  I remember adding that file a while back as it seemed important to me at the time, although I haven't revisited it.
Should I be ensuring every function gets an entry in that array, and is there anything else I have to cross off to coerce Functions into working?
@davidebbo - This must be another one of those "How many yaks do I have to shave before this just works(tm)?" 😉
So far, I've been interrupted by six different things before I can get beyond stage demos with Functions: Resource structure, artifact deployment, magical app service variables, special key files in storage, host.json, function.json.
I'm closer now than I have ever been, but I will admit I'm far above the norm for patience with these kinds of things.
I'd like to very affectionately and respectfully think the Azure team needs to take a good hard look at the developer joy story with Functions (and inevitably a few things before it).  I've had discussions with people in private who may never come back to functions because their experiences have been so bad.
cc. @lindydonna

That settings is actually some advanced thing that very few people are using. If you don't have it at all, then all your functions are enabled. Do you recall what caused you to add it in the first place?
About the rest of issues you are running into, I think the best we can do is take them one by one and try to improve. We do realize that we are still a long way from perfection :)

Totall, and I should definitely take the time to note that while what I'm saying seems quite critical, it's in the hopes of helping improve the platform.  It's no good if everyone just walks away without offering input.

@atrauzzi Can you provide info on why you were using the functions property in the first place?  It's an advanced feature.

Ah gosh, I wish I could remember now.  You know it might be that I copied the host.json prior to committing to deleting and redeploying the project.  I think it's part of a default setup?  How individual functions got listed in there though...  If your main concern is about any official documentation, I don't think it was from MS that I got the advice.  Likely someone's blog post.

clearing milestone to discuss again in triage

We should do some tactical fixes to provide more detail in the host endpoint, otherwise the UI just displays useless information. Ahmed has already investigated some common cases where we have poor error messages.
We could do some queries on the most common cases for 404 and prioritize error messages for those cases.

@christopheranderson @lindydonna should this move from May milestone?

Root cause could be #2530


Orbs address scheme next version: network ID, virtual chain ID, encoding in parts

This PR implements the next Orbs address scheme, combining the spec from architecture.
For example:
Public Key: 8d41d055d00459be37f749da2caf87bd4ced6fafa335b1f2142e0f44501b2c65
Virtual Chain ID: 640ed3
Network ID: 14 (M)

SHA256: 40784b5b15e6bb364263dbb598f262bc5c5b4c18a34806ca70be180c3d995e0d
Account ID: RIPEMD160 of SHA256: c13052d8208230a58ab363708c08e78f1125f488
Network ID + Version + Virtual Chain + Account ID: 1400640ed3c13052d8208230a58ab363708c08e78f1125f488
Checksum: 61f04bfc
Raw public address: 1400640ed3c13052d8208230a58ab363708c08e78f1125f48861f04bfc

BASE58 (in parts): M1EXMPnnaWFqRyVxWdhYCgGzpnaL4qBy4QFsJu1

@idandash @netoneko this PR is good to go.

@idandash I've addressed your comments. I've noted of the extra encoding and perhaps change it in the future, once the mobile integration is complete (since it required to regenerate the addresses).

@idandash please approve and let's merge.


Cannot log screen view event when the app is not active

[REQUIRED] Step 1: Describe your environment

Xcode version: Xcode 12.4
Firebase SDK version: 7.3.1
Installation method: Swift Package Manager
Firebase Component: Analytics, Crashlytics

[REQUIRED] Step 2: Describe the problem
It appears that the system FaceID/TouchID authentication prompt is putting the app into a resigned/non-active state. And sending screen_view event during the prompt is ignored by Firebase SDK due to the limitation that no screen_view events are allowed when the app is not active.
The console printed out the error: Cannot log screen view event when the app is not active.
I'm not sure what's the best way to solve this to be honest. Not sure if it's fair to assume Firebase SDK would take care of this situation.
Steps to reproduce:
Perform a FaceID/TouchID authentication as soon as the app is coming back from background while sending out a screen_view event.
Relevant Code:
LAContext().evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, localizedReason: "some reason") { }
Analytics.logEvent(AnalyticsEventScreenView, [
AnalyticsParameterScreenName: "MyView",
AnalyticsParameterScreenClass: "MyViewClass"
])

Hey @KelvinJin, sorry for the trouble you're seeing. This may be a silly suggestion, but does moving the logEvent call before the call to bring up the FaceID prompt work in your case? I'm not sure off the top of my head if we can detect the FaceID prompt showing in the app or not.

@ryanwilson Hey Ryan, thanks for the reply. I tried both order but it won't work unless I add some sort of delay by using for instance DispatchQueue.main.asyncAfter. This issue also applies to the case if we're to show a view right after success of the FaceID authentication. That view's screen view event won't get sent unless we add some sort of delay.
I think the underlying problem is that Firebase is observing applicationWillResignActive to disable screen view tracking but sometimes when this happens, the app is actually visible and screens are being updated. One example being when you receive a phone call and that iOS phone call banner will show up from the top of your device which will put the app into non-active state. If we send screen view events during this period, it won't be captured.
I couldn't really provide any constructive advice other than maybe instead of observing applicationWillResignActive, Firebase should observe applicationDidEnterBackground?
It's not a big big deal for me to add some delay in order to workaround this issue but I'm worried that a random delay might cause further issues. For instance, if I delay the screen view event by 2 seconds but don't delay the following interactive events. Then the interactive events might be associated with a wrong firebase_screen.
Let me know if you have any other ideas! Thanks.

Thanks for the detailed reply! I'm not sure all the considerations made here so I'll defer to someone who knows more than I do. @htcgh any ideas if this is working as intended or there's a way we can determine the type of non-active state here?

Just to add to this... I'm seeing the same. My case is a bit different. I ask notification permission and as soon as the user respond, we show a new screen and this screen is not tracked
Cannot log screen view event when the app is not active

Any updates on this one? , we are having the same issues


Profile Icon does not respond to user click

The profile icon should be clickable to show the sign out option on all pages, the fix can be that the javascript file is not called right in the html in the handlebars files.

Fixed the Issue by reproducing the problem and then added some of the dashboard.js code to all the other pages like tasks and team pages. The eventListener code has the same id as the static file in main handlebars.


Dockerfile

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...
- [x] bug report

[x] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Impossible to build Dockerfile

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue

Docker version 19.03.8, build afacb8b
MacOS Catalina 10.15.3 (19D76)
Visual Studio Code
Version: 1.43.1
Commit: fe22a9645b44368865c0ba92e2fb881ff1afce94
Date: 2020-03-18T07:01:41.240Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

install Vuestic installer

npm install -g vuestic-installer

Vuestic a new project

XXX % vuestic vuestic
 __     __          ____  _   _
 \ \   / /   _  ___/ ___|| |_(_) ___
  \ \ / / | | |/ _ \___ \| __| |/ __|
   \ V /| |_| |  __/___) | |_| | (__
    \_/  \__,_|\___|____/ \__|_|\___|

vuestic has been successfully created.

Modify .dockerignore to add .git into docker (Because of git rev-parse HEAD)

node_modules/
dist/
# .git/
.dockerignore
.gitattributes
.gitignore
Dockerfile
README.md

build Dockerfile

docker build --rm -f "Dockerfile" -t vuestic:latest "vuestic"

What is the expected behavior?
A Docker image

What is the motivation / use case for changing the behavior?
Would like to run project into the Dockerfile provided

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Seems to be here:
const getLastCommitHash = () => {
  const hash = require('child_process').execSync('git rev-parse HEAD')
    .toString()

  return hash.slice(0, 6)
}

and here
new webpack.DefinePlugin({
        VERSION: JSON.stringify(version),
        TIMESTAMP: JSON.stringify(timeStamp),
        COMMIT: JSON.stringify(getLastCommitHash()),
      }),

XXX % docker build --rm -f "Dockerfile" -t vuestic:latest "vuestic"
Sending build context to Docker daemon  5.779MB
Step 1/7 : FROM node:8
 ---> 8eeadf3757f4
Step 2/7 : WORKDIR /app
 ---> Using cache
 ---> ae53738b9d7a
Step 3/7 : COPY . /app
 ---> 1602768e7d08
Step 4/7 : EXPOSE 8082
 ---> Running in 7c02792ba6d0
Removing intermediate container 7c02792ba6d0
 ---> 88e58b684741
Step 5/7 : RUN npm install http-server -g
 ---> Running in 0e80aabe2224
/usr/local/bin/http-server -> /usr/local/lib/node_modules/http-server/bin/http-server
/usr/local/bin/hs -> /usr/local/lib/node_modules/http-server/bin/http-server
+<EMAIL_ADDRESS>added 26 packages from 35 contributors in 7.255s
Removing intermediate container 0e80aabe2224
 ---> 74d8c3fcf86d
Step 6/7 : RUN npm install && npm run build
 ---> Running in a07a73acdbc2

><EMAIL_ADDRESS>install /app/node_modules/yorkie
> node bin/install.js

setting up Git hooks
done

><EMAIL_ADDRESS>install /app/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.0/linux-x64-57_binding.node
Download complete
Binary saved to /app/node_modules/node-sass/vendor/linux-x64-57/binding.node
Caching binary to /root/.npm/node-sass/4.13.0/linux-x64-57_binding.node

><EMAIL_ADDRESS>postinstall /app/node_modules/babel-polyfill/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /app/node_modules/babel-runtime/node_modules/core-js
> node postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /app/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /app/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)

><EMAIL_ADDRESS>postinstall /app/node_modules/vuestic-ui/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /app/node_modules/flag-icon-css
> opencollective-postinstall || true

Thank you for using flag-icon-css!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/lipis/donate

><EMAIL_ADDRESS>postinstall /app/node_modules/node-sass
> node scripts/build.js

Binary found at /app/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1872 packages from 1185 contributors and audited 935248 packages in 183.315s

24 packages are looking for funding
  run `npm fund` for details

found 40071 vulnerabilities (40063 low, 8 moderate)
  run `npm audit fix` to fix them, or `npm audit` for details

><EMAIL_ADDRESS>build /app
> vue-cli-service build

 ERROR  TypeError: Function.prototype.toString requires that 'this' be a Function
TypeError: Function.prototype.toString requires that 'this' be a Function
    at Proxy.toString (<anonymous>)
    at foldValue (/app/node_modules/hash-sum/hash-sum.js:47:27)
    at foldKey (/app/node_modules/hash-sum/hash-sum.js:28:12)
    at Array.reduce (<anonymous>)
    at foldObject (/app/node_modules/hash-sum/hash-sum.js:26:32)
    at foldValue (/app/node_modules/hash-sum/hash-sum.js:45:12)
    at foldKey (/app/node_modules/hash-sum/hash-sum.js:28:12)
    at Array.reduce (<anonymous>)
    at foldObject (/app/node_modules/hash-sum/hash-sum.js:26:32)
    at foldValue (/app/node_modules/hash-sum/hash-sum.js:45:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Thanks for informing.


Update alfons

This should use InputSource move-data constructor on ios

@hjanetzek this is good. Can you first make a PR in alfons and bring it in alfons:master before we update submodule in tangram-es?

@tallytalwar I've pushed the commit to alfons master - so the submodule ref is still valid. It just seems not to be possible in github gui ;)

We should also think about updating harfbuzz, I looked at it last year, and there were a few goodies added to it which could simplify some of alfons code. Something to think about.


Method signature issue in keys function in maps package

keys function lookup has multiple return types.

Duplicate of #605 .


[Snyk] Upgrade esbuild from 0.16.17 to 0.17.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade esbuild from 0.16.17 to 0.17.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-01-14.

Release notes

Package name: esbuild

0.17.0 - 2023-01-14 Read more

0.16.17 - 2023-01-11

Fix additional comment-related regressions (#2814)
This release fixes more edge cases where the new comment preservation behavior that was added in 0.16.14 could introduce syntax errors. Specifically:
x = () => (/* comment */ {})
for ((/* comment */ let).x of y) ;
function *f() { yield (/* comment */class {}) }
These cases caused esbuild to generate code with a syntax error in version 0.16.14 or above. These bugs have now been fixed.

    from esbuild GitHub release notes

Commit messages

Package name: esbuild

2a18b3d publish 0.17.0 to npm
60ba46a test coverage for build merging
3153032 Version 0.17.0: rewrite the incremental build apis (#2816)
5579b0f change wordmark text
fa27e29 fix link to go docs
e72962f Update README.md
5d80704 new year new changelog
9cc2b84 add more info to `exports` errors in package.json

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #272 (22e87d8) into master (4b8b1e1) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##            master      #272   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          222       222
  Branches        30        30
=========================================
  Hits           222       222

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


latest version suggestion

anton as you have done latest version might be other users could be problem
case you are inserting 0 value during heartbit ? or sleeping mode ? as latest version ?
so all time but problem is solved from xml  as i did ignore 0 and seems working fine and great
so may be this sample config files users can use it and problem solved ? as 0 filtering so will have great working this last version for all people really
case they people can get consider as status of device
i  have done other class customized and working fine according my need  :)

I don't quite understand what you are talking about. Heartbeat messages are not saved in the database and they won't be.

heartbeat mean device sleeping then just send details without gps lat long got it ?

The idea is that on heartbeat message server would just update device status and timestamp.

yes true and it's working fine great work it could be stable version i have tested more time


After deconnection, variable delays to reconnect via Call Home observed on v2

I switched recently to the following software version from the devel branch(v2) : Netopeer2 v2.0.35
Scenario : In CLI, alternative listen/disconnect cmd leads to the following logs at Server level.
Observation : listen cmd is stuck for an randomize time linked to the time xyz displayed in following Server logs :
==> [INF]: LN: Call Home client "default-client" reconnecting in xyz seconds.
This behavior was not observed in Netopeer2 v1
Full logs below with several trials of sequence listen/disconnect at CLI level along with the Call Hom configuration in place in the datastore.
Time to time, we can see that xyz is different.
[INF]: SR: Successful processing of "rpc" event with ID 2 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 2 priority 0 succeeded.
===> Disconnect Call Home from CLI
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: NP: Session 2: thread 3 event new RPC.
[INF]: NP: Session 2: thread 3 event session terminated.
[INF]: SR: Published event "notif" "ietf-netconf-notifications" with ID 10 priority 0 for 2 subscribers.
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 10.
[INF]: SR: Successful processing of "notif" event with ID 10 priority 0 (remaining 0 subscribers).
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Call Home client "default-client" session terminated.
[INF]: LN: Call Home client "default-client" reconnecting in 117 seconds.
[ERR]: LN: Session 2: Waiting for Call Home thread failed (Connection timed out).
[2021/11/28 07:25:58.583001, 1] ssh_socket_exception_callback:  Socket exception callback: 1 (0)
[2021/11/28 07:25:58.583032, 1] ssh_socket_exception_callback:  Socket error: disconnected
===> reconnection with Call Home frozen during the 117 seconds timeout ....
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 11.
[INF]: SR: Successful processing of "notif" event with ID 11 priority 0 (remaining 1 subscribers).
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 12.
[INF]: SR: Successful processing of "notif" event with ID 12 priority 0 (remaining 1 subscribers).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
[INF]: LN: Successfully connected to <IP_ADDRESS>:4334 over IPv4.
[INF]: SR: Session 177 (user "root", CID 3) created.
===> Disconnect Call Home from CLI
[INF]: NP: Session 4: thread 3 event new RPC.
[INF]: NP: Session 4: thread 3 event session terminated.
[INF]: SR: Published event "notif" "ietf-netconf-notifications" with ID 16 priority 0 for 2 subscribers.
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 16.
[INF]: SR: Successful processing of "notif" event with ID 16 priority 0 (remaining 0 subscribers).
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Call Home client "default-client" session terminated.
[INF]: LN: Call Home client "default-client" reconnecting in 26 seconds.
[ERR]: LN: Session 4: Waiting for Call Home thread failed (Connection timed out).
[2021/11/28 07:32:27.152690, 1] ssh_socket_exception_callback:  Socket exception callback: 1 (0)
[2021/11/28 07:32:27.152716, 1] ssh_socket_exception_callback:  Socket error: disconnected
====> reconnection with Call Home frozen during the 26 seconds timeout ....
[ERR]: SR: Internal error (/opt/dev/sysrepo/src/common.c:3886).
[ERR]: SR: Internal error (/opt/dev/sysrepo/src/common.c:3886).
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 17.
[INF]: SR: Successful processing of "notif" event with ID 17 priority 0 (remaining 0 subscribers).
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 18.
[INF]: SR: Successful processing of "notif" event with ID 18 priority 0 (remaining 1 subscribers).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
[INF]: LN: Successfully connected to <IP_ADDRESS>:4334 over IPv4.
[INF]: SR: Session 210 (user "root", CID 3) created.
====> Disconnect Call Home from CLI
[INF]: NP: Session 5: thread 1 event new RPC.
[INF]: NP: Session 5: thread 1 event session terminated.
[INF]: SR: Published event "notif" "ietf-netconf-notifications" with ID 20 priority 0 for 2 subscribers.
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 20.
[INF]: SR: Successful processing of "notif" event with ID 20 priority 0 (remaining 1 subscribers).
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Call Home client "default-client" session terminated.
[INF]: LN: Call Home client "default-client" reconnecting in 3 seconds.
[ERR]: LN: Session 5: Waiting for Call Home thread failed (Connection timed out).
[2021/11/28 07:34:04.743739, 1] ssh_socket_exception_callback:  Socket exception callback: 1 (0)
[2021/11/28 07:34:04.743766, 1] ssh_socket_exception_callback:  Socket error: disconnected
====> reconnection with Call Home frozen during the 3 seconds timeout ....
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
[INF]: LN: getsockopt() error (Connection refused).
=====> Disconnect Call Home from CLI
[INF]: NP: Session 6: thread 1 event new RPC.
[INF]: NP: Session 6: thread 1 event session terminated.
[INF]: SR: Published event "notif" "ietf-netconf-notifications" with ID 24 priority 0 for 2 subscribers.
[INF]: SR: Processing "notif" "ietf-netconf-notifications" event with ID 24.
[INF]: SR: Successful processing of "notif" event with ID 24 priority 0 (remaining 0 subscribers).
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Call Home client "default-client" session terminated.
[INF]: LN: Call Home client "default-client" reconnecting in 115 seconds.
[ERR]: LN: Session 6: Waiting for Call Home thread failed (Connection timed out).
[2021/11/28 07:35:56.927858, 1] ssh_socket_exception_callback:  Socket exception callback: 1 (0)
[2021/11/28 07:35:56.927885, 1] ssh_socket_exception_callback:  Socket error: disconnected
======> reconnection with Call Home frozen during the 115 seconds timeout ....
> get --defaults report-all --filter-xpath  /netconf-server/call-home
DATA
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <netconf-server xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-server">
    <call-home>
      <netconf-client>
        <name>default-client</name>
        <endpoints>
          <endpoint>
            <name>default-tls</name>
            <tls>
              <tcp-client-parameters>
                <remote-address><IP_ADDRESS></remote-address>
                <remote-port>4335</remote-port>
                <keepalives>
                  <idle-time>1</idle-time>
                  <max-probes>10</max-probes>
                  <probe-interval>5</probe-interval>
                </keepalives>
              </tcp-client-parameters>
              <tls-server-parameters>
                <server-identity>
                  <keystore-reference>
                    <asymmetric-key>serverkey</asymmetric-key>
                    <certificate>servercert</certificate>
                  </keystore-reference>
                </server-identity>
                <client-authentication>
                  <cert-maps>
                    <cert-to-name>
                      <id>1</id>
                      <fingerprint>02:E9:38:1F:F6:8B:62:DE:0A:0B:C5:03:81:A8:03:49:A0:00:7F:8B:F3</fingerprint>
                      <map-type xmlns:x509c2n="urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name">x509c2n:specified</map-type>
                      <name>tls-test</name>
                    </cert-to-name>
                  </cert-maps>
                  <required/>
                  <ca-certs>cacerts</ca-certs>
                  <client-certs>clientcerts</client-certs>
                </client-authentication>
              </tls-server-parameters>
            </tls>
          </endpoint>
          <endpoint>
            <name>default-ssh</name>
            <ssh>
              <tcp-client-parameters>
                <remote-address><IP_ADDRESS></remote-address>
                <remote-port>4334</remote-port>
                <keepalives>
                  <idle-time>1</idle-time>
                  <max-probes>10</max-probes>
                  <probe-interval>5</probe-interval>
                </keepalives>
              </tcp-client-parameters>
              <ssh-server-parameters>
                <server-identity>
                  <host-key>
                    <name>default-key</name>
                    <public-key>
                      <keystore-reference>genkey</keystore-reference>
                    </public-key>
                  </host-key>
                </server-identity>
                <client-authentication>
                  <supported-authentication-methods>
                    <publickey/>
                    <passsword/>
                    <other>interactive</other>
                  </supported-authentication-methods>
                </client-authentication>
              </ssh-server-parameters>
            </ssh>
          </endpoint>
        </endpoints>
        <connection-type>
          <periodic>
            <period>2</period>
            <idle-timeout>0</idle-timeout>
          </periodic>
        </connection-type>
        <reconnect-strategy>
          <start-with>first-listed</start-with>
          <max-attempts>3</max-attempts>
        </reconnect-strategy>
      </netconf-client>
    </call-home>
  </netconf-server>
</data>

Okay, the timeout was being anchor when it should not have been, fixed in the latest libnetconf2. But I am more interested in the errors so please include the exact steps you took when connecting to/disconnecting from the server because from logs it seems you have also subscribed to notifications by some client, which I think may be the root of the problem.


Promises exceptions suppressed in Chrome

Current Chrome version throws a lot of exceptions on pages with heavy use of sounds:
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
As this library uses events for asynchronous handling, it should be okay to just ignore promise exceptions.

Thanks a lot!


feat(linter) deepscan: bad char at compaison

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1747

PR #1748

PR #1749

PR #1750   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 19, 11:24 PM: @@Boshen started a stack merge that includes this pull request via Graphite.


example(serverless functions): Stripe Webhooks

Codecov Report

Merging #1311 (c59f622) into main (b8b4e36) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1311   +/-   ##
=======================================
  Coverage   94.74%   94.74%
=======================================
  Files          48       48
  Lines        6931     6931
  Branches      450      450
=======================================
  Hits         6567     6567
  Misses        364      364

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.