text:
[stable/hlf-couchdb] Update owners

What this PR does / why we need it:
Update hlf-couchdb owners
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/chart])

@nicolapaoli, pre-approving, but @dbandin and @inzamam-iqbal need to be member of the Helm organisation to be added as Owners

/verify-owners

authors: alexvicegrab nicolapaoli


text:
[incubator/kafka]. Add ability to set ServiceMonitor namespace to realese namespace

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @benjigoldberg

/ok-to-test
/lgtm

source: gharchive/pull-request

authors: benjigoldberg vkropotko

repo: helm/charts

license_type: permissive

license_source: github-api


text:
[stable/spring-cloud-data-flow] Add task scheduler launcher url

What this PR does / why we need it:

add SPRING_CLOUD_DATAFLOW_TASK_SCHEDULER_TASK_LAUNCHER_URL to server env vars

Signed-off-by: Chris Schaefer cschaefer@pivotal.io
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @sabbyanandan

/lgtm

authors: chrisjs sabbyanandan


text:
[stable/datalog] Do not enable the cri check when running on a docker setup

What this PR does / why we need it:
Make a clear distinction between the docker and the CRI setup so that only one of docker or cri check is scheduled by the agent.
Which issue this PR fixes
With the current chart, datadog.criSocketPath defaults to /var/run/docker.sock.
As datadog.criSocketPath is always setup, the Helm chart defines the environment variable DD_CRI_SOCKET_PATH which makes the datadog agent initialisation scripts setup the cri check.
But the docker socket doesn’t implement the CRI API so that, the cri check is always setup and fails.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/lgtm


text:
[stable/minio] corrected syntax error in statefulset

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Syntax error in Statefulset prevented installation from working.
Which issue this PR fixes
Syntax error
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Signed-off-by: Thomas Wilkinson thomas@capnajax.com

/assign @krisis

/lgtm

This PR reverts the fix I had submitted previously,
FYI:
https://stackoverflow.com/questions/17891226/difference-between-and-operators-in-go
The := operator is an assignment and declaration in one. Therefore:
{{ $scheme := "http" }}
 {{- if .Values.tls.enabled }}
 {{ $scheme := "https" }}
 {{ end }}

If tls is enabled, this will simply declare and assign a new variable "scheme" that only exists until the {{ end }}. ie, it will have zero effect on actually enabling https for minio.
Effectively, scheme is now always "http". If the previous fix broke anything, it is probably because you have enabled tls and there are issues with your certificates. Rather than revert the fix you could simply set tls to disabled or figure out the issues with the certs.

@krisis the PR @briend is referencing is #21373, which fixed the scoping issue that this PR reintroduced

Why it was merged? It seems wrong, and I can't enable TLS successfully.


text:
[stable/sentry] add custom labels for ingress

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

I create new one properly


text:
cleanup-on-fail ineffective for subcharts

helm upgrade fails for upgrading the Prometheus Helm chart (v14.1.3 to v15.3.0) with an field is immutable error message on label selectors. The Deployment affected comes from the kube-state-metrics subchart that extends the selectors. As per the description, Helm’s --cleanup-on-fail should resolve this issue but it does not seem to have any effect on a subchart.
Bug or misunderstanding?
Error message:
rollback.go:171: [debug] warning: Rollback "prometheus" failed: cannot patch "prometheus-kube-state-metrics" with kind Deployment: Deployment.apps "prometheus-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"prometheus", "app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
Error: UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: cannot patch "prometheus-kube-state-metrics" with kind Deployment: Deployment.apps "prometheus-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"prometheus", "app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable: cannot patch "prometheus-kube-state-metrics" with kind Deployment: Deployment.apps "prometheus-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"prometheus", "app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
helm.go:84: [debug] cannot patch "prometheus-kube-state-metrics" with kind Deployment: Deployment.apps "prometheus-kube-state-metrics" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"prometheus", "app.kubernetes.io/name":"kube-state-metrics"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

Output of helm version: version.BuildInfo{Version:"v3.8.0", GitCommit:"d14138609b01886f544b2025f5000351c9eb092e", GitTreeState:"clean", GoVersion:"go1.17.5"}
Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.6", GitCommit:"f59f5c2fda36e4036b49ec027e556a15456108f0", GitTreeState:"clean", BuildDate:"2022-01-19T17:33:06Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): kubeadm

Still an issue …

source: gharchive/issue

repo: helm/helm


text:
helm package should produce bitwise-deterministic tar files

We have a CI process for publishing charts where we try to determine if pushed repository needs to have it's charts built and published. We would like to do this with a bitwise comparison of the generated tgz files. This works for charts without dependencies, but it is inconsistent for charts with dependencies.
For the setup (Using v2.8.1):
charts
├── child1
│   └── Chart.yaml
├── child2
│   └── Chart.yaml
├── child3
│   └── Chart.yaml
└── parent
    ├── Chart.yaml
    └── requirements.yaml

With charts:
# child{1..3}/Chart.yaml
name: child{1..3}
version: 1.0.0

# parent/Chart.yaml
name: parent
version: 1.0.0

# parent/requirements.yaml
dependencies:
- name: child1
  repository: file://../child1
  version: "*"
- name: child2
  repository: file://../child2
  version: "*"
- name: child3
  repository: file://../child3
  version: "*"

Running:
# working dir: parent
$ helm dep update
$ for i in {1..1000}; do helm package . && sha256sum parent-1.0.0.tgz && rm parent-1.0.0.tgz; done

produces several (3, after a significant number of iterations) different shas. The shas also appear to be non-uniformly distributed (e.g. 1 sha appears 70% of the time).
My guess is that https://github.com/kubernetes/helm/blob/master/pkg/chartutil/save.go#L160 is iterating over dependencies in a non-deterministic order, thus producing different tar files.

I think this is actually due to gzip. Part of the gzip header has a mod time for whatever is compressed in the file, so by calling helm package multiple times, each one creates their own tarball which is then packaged by gzip and given a unique shasum because the modtime differed.
If you gunzip the .tgz, is the shasum identical between tarballs?

gunziping the tars still produces different tarballs. There still appear to be 3 different shasums.

Following up on my previous comment, you can even reproduce this yourself at home:
><> helm fetch stable/traefik
><> gunzip traefik-1.24.1.tgz
><> helm fetch stable/traefik
><> shasum -a 256 *
a032f1eba2c54b76d8de38d3763bab5ca5a6383af1156f30caf4595adaec67a0  traefik-1.24.1.tar
ebd78bdbbf63f557db8646c6351bfeeac849951334d4cbfc103ecc6bb1b170c5  traefik-1.24.1.tgz

So in this example, I've shown that I've got stable/traefik, both in compressed and decompressed versions from the official stable/traefik chart. If I gzip this up, we should be able to assert that we come up with the same shasum because the contents are the same, right?
Wrongo.
><> gzip traefik-1.24.1.tar
><> shasum -a 256 *
144eaa108aff820dd754e16732bbacd29accb41954d6249b4111623587fae415  traefik-1.24.1.tar.gz
ebd78bdbbf63f557db8646c6351bfeeac849951334d4cbfc103ecc6bb1b170c5  traefik-1.24.1.tgz

But the shasums of both the recently-gzipped tarball and the old shasum are still identical.
><> gunzip traefik-1.24.1.tar.gz
><> mv traefik-1.24.1.tar traefik-1.24.1.tar.1
><> gunzip traefik-1.24.1.tgz
><> mv traefik-1.24.1.tar traefik-1.24.1.tar.2
><> shasum -a 256 *
a032f1eba2c54b76d8de38d3763bab5ca5a6383af1156f30caf4595adaec67a0  traefik-1.24.1.tar.1
a032f1eba2c54b76d8de38d3763bab5ca5a6383af1156f30caf4595adaec67a0  traefik-1.24.1.tar.2

So in other words, if you want a deterministic shasum of the contents of the chart, I'd suggest decompressing the packages first before checking the shasum.
Would that work for you?

The timestamp issue in the default gzip settings appears to be irrelevant since there are only a few unique shas that appear in thousands of tests on helm package (whereas the shas from the gzip example appear to be purely random). It looks like writeToTar in pkg/chartutil/save.go specifies its own header here:  https://github.com/kubernetes/helm/blob/master/pkg/chartutil/save.go#L205.
Perhaps sorting the dependencies in a deterministic manner before serialization is all that is needed, but any help on where to put the sort would be appreciated.
For now a workaround is to do a file diff on the decompressed packages after removing the dependency tars. This won't catch differences in dependencies except version differences (which can happen for local dependencies, e.g.), but will catch most differences until this can be patched.

I was unable to reproduce this behaviour using a stable chart. Can you provide a sample chart that produces this behaviour?
My steps to test this:
$ helm fetch --untar stable/traefik
$ for i in {1..1000}; do helm package traefik/ && mv traefik-1.24.1.tgz traefik-1.24.1.tgz.$i; done
$ shasum -a 256 *.tgz* | awk '{print $1}' | uniq
ebd78bdbbf63f557db8646c6351bfeeac849951334d4cbfc103ecc6bb1b170c5

Every invocation of helm package returned a consistent shasum.
/shrug

https://github.com/cmaher/nondeterministic-charts demonstrates this using Client: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}

I found out a way to reproduce this. One thing that seems to be helpful in reproducing is having more than one dependency in the requirements file. Also, the large the values.yaml file  the easier it is to reproduce as well.
spinnaker is an example stable chart to reproduce:
mkdir pkgs
cd spinnaker
helm dep up
for i in {1..30}; do helm package . && mv spinnaker-0.5.0.tgz ../pkgs/spinnaker-0.5.0.tgz.$i; done
cd ../pkgs
shasum -a 256 *.tgz* | awk '{print $1}' | uniq

/remove-lifecycle rotten

We have been able to reproduce this issue with some of our local charts as well.

The problem definitely manifests itself on macOS. None of the suggestions mentioned in this tread solve the issues. I've created a repo to demonstrate the problem and a workaround: https://github.com/adrian-gierakowski/helm-package-sha-test.

Is this related to dependencies, or is the issue just increasingly more likely to occur the more files a chart contains?

The issue is that the POSIX directory enumeration API does not define a specific order for file names to be returned. There may be a "common" order but since sorting/ordering is not something that can be done generically (it is locale/user specific), the core filesystems are not forced to provide a consistent order. Result orders may depend on available cache entries or order of data returned from elevator algorithms that read from the disk or a number of other out-of-order execution behaviors.

Is there really not a way enforce this order in Go? @Michael-Sinz

You can write your own code to take the enumeration and sort it.  Pick your sort to be consistent across all locales.
Unix/Posix does not push costly operations onto all use cases when most cases do not need that - it assumes that you would compose one operation with another to get the desired result.
__
Michael Sinz C Architect C http://midori/ v C Microsoft

From: Josh Dolitsky notifications@github.com
Sent: Wednesday, May 27, 2020 4:36 PM
To: helm/helm helm@noreply.github.com
Cc: Michael Sinz Michael.Sinz@microsoft.com; Mention mention@noreply.github.com
Subject: Re: [helm/helm] helm package should produce bitwise-deterministic tar files (#3612)
Is this related to dependencies, or is the issue just increasingly more likely to occur the more files a chart contains?
The issue is that the POSIX directory enumeration API does not define a specific order for file names to be returned. There may be a "common" order but since sorting/ordering is not something that can be done generically (it is locale/user specific), the core filesystems are not forced to provide a consistent order. Result orders may depend on available cache entries or order of data returned from elevator algorithms that read from the disk or a number of other out-of-order execution behaviors.
Is there really not a way enforce this order in Go? @Michael-Sinzhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMichael-Sinz&data=02|01|Michael.Sinz%40microsoft.com|7f787afb198646f162fc08d80296c2ef|72f988bf86f141af91ab2d7cd011db47|1|0|637262193827632571&sdata=5yvN1d7V5r1DYfxWZdVYeawCsSmPCOws73GJ68bY0m8%3D&reserved=0
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhelm%2Fhelm%2Fissues%2F3612%23issuecomment-634999466&data=02|01|Michael.Sinz%40microsoft.com|7f787afb198646f162fc08d80296c2ef|72f988bf86f141af91ab2d7cd011db47|1|0|637262193827632571&sdata=nE1BhhEAVlJaYWnLVFMs3dqW9sd89O%2Bw03m9jZi7IGE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIZINKSLFWKEXWDAUN3OGL3RTWPXJANCNFSM4ETXKHGQ&data=02|01|Michael.Sinz%40microsoft.com|7f787afb198646f162fc08d80296c2ef|72f988bf86f141af91ab2d7cd011db47|1|0|637262193827642528&sdata=9D784OITV0hBpmnLnLvUDIByZo%2FevAgnuYKA%2B5blDh4%3D&reserved=0.

Is there no progress on this issue.  The lack of deterministic output for constant input is a big problem.  It means that helm package is not deterministic and we can not depend on it producing the same results.  Imaging if a compiler could make different code for the same source code from run to run - how would you debug such a program?

Agreed. We've had to make clumsy workarounds to only package the chart if one of the source files changes. One issue is the embedded time stamps.

@Michael-Sinz I have not seen any activity from the community on this bug. Please feel free to work on a fix!

We still would like to have deterministic helm chart building.  The fact that the same helm chart from the same source tree from the same git hash with the same helm version does not produce deterministic hashes is concerning.

Deterministic output is the goal of the Reproducible builds  project.
It has a recommended tar example:
# requires GNU Tar 1.28+
$ tar --sort=name \
      --mtime="@${SOURCE_DATE_EPOCH}" \
      --owner=0 --group=0 --numeric-owner \
      --pax-option=exthdr.name=%d/PaxHeaders/%f,delete=atime,delete=ctime \
      -cf product.tar build

gz seems to produce reproducible output since 2018.
But as helm uses go libs, maybe the fix is around file order:
https://github.com/helm/helm/blob/f41f46c6c6a1fae459b51a110f76d60f33281f74/pkg/chartutil/save.go#L205-L228

Hi, we are really waiting for this issue to be fixed. Since real advantage of using OCI is that we make use of the delta changes in the chart that are only committed to the repository and this saves the space at the repository. We are leveraging this feature in OCI container images a lot. Without this feature, we cannot declare helm OCI support is moved to permanent from experimental.

/cc @jdolitsky @scottrigby

Any updates?

I can reproduce it like this:
$ helm version
version.BuildInfo{Version:"v3.10.0", GitCommit:"ce66412a723e4d89555dc67217607c6579ffcb21", GitTreeState:"clean", GoVersion:"go1.19.1"}
$ helm create foo
Creating foo
$ for i in {1..10}; do helm package foo >/dev/null; md5sum foo-0.1.0.tgz; sleep 0.5; done
39e2b6bff940ed840873926f271d72f8  foo-0.1.0.tgz
f34d771d8039d77c9b76340c7940ab55  foo-0.1.0.tgz
f34d771d8039d77c9b76340c7940ab55  foo-0.1.0.tgz
afe15ee8c34f069e967e88e70c7bbd29  foo-0.1.0.tgz
afe15ee8c34f069e967e88e70c7bbd29  foo-0.1.0.tgz
7c1b20acd7a9a73944af13fec2303cf0  foo-0.1.0.tgz
7c1b20acd7a9a73944af13fec2303cf0  foo-0.1.0.tgz
16cef47516265bed7f8dbd9ef145042c  foo-0.1.0.tgz
16cef47516265bed7f8dbd9ef145042c  foo-0.1.0.tgz
1532cb3b9a5d828e19d74b034caebace  foo-0.1.0.tgz

FWIW the example from reproducible builds worked well for me, but that obviously requires custom scripting, which is not ideal.

Fix for the above has been pending review/merge. Not sure what the blocker is TBH:
https://github.com/helm/helm/pull/10178

authors: FrenchBen Michael-Sinz adrian-gierakowski bacongobbler bmperrea cmaher diclophis dinvlad geowalrus4gh h0tbird hickeyma jdolitsky jeff-knurek rjeberhard sathieu


text:
Tune goreleaser config

Reduce permissions for github token
Use custom token only for homebrew tap updates
Group up commits in changelog
Automatically close milestones on release

Hmm maybe it should be in release-0.17.0?

Hmm maybe it should be in release-0.17.0?

@zhilyaev I want to create manually rc tag on main with this config before merging 0.17.0
  # If set to auto, will mark the release as not ready for production
  # in case there is an indicator for this in the tag e.g. v1.0.0-rc1
  # If set to true, will mark the release as not ready for production.
  # Default is false.
  prerelease: auto

@r3nic1e ping

repo: helmwave/helmwave

license: MIT


text:
Docker Kubernetes

Hi,
I had trouble finding information if the helpy docker instance can be ran in kubernetes.
The usual problem is that docker images encode passwords, url in the image.
Has anyone tried making helpy work in kubernetes?
I'm interested in contributing.

Hey @fire would be great!  I have not done it yet myself, but there have been some changes over the last months to move passwords and api keys to env. variables where possible.  This makes it easier to separate the app server from the filestore and db.  This has worked great for running Helpy in a cluster with ephemeral app servers, even auto scaling.
The one issue with Helpy is that it uses a cached settings plugin that stores key-value settings both in the database and on disk.  Thus, in a cluster of app servers, it becomes impossible to invalidate the disk cached items immediately.  The solution is run a cron that deletes the cache every 1-n minutes.  Luckily these settings don't change very often except when you are first getting things configured.
As far as k8s goes, I know one team worked on this about a year ago, but I have no idea how well they got it working.  It should be easier now because you can use S3 for file storage by using env. vars.

List of tasks:

move passwords and api keys to env. variables where possible

run a cron that deletes the cache every 1-n minutes

use S3 for file storage by using env. vars.

Create kubernetes docker image

Create statefulset

Pick a postgresql operator

Create a service

Create an ingress

See https://github.com/helpyio/helpy/blob/master/docker/.env.sample for the environmental variables.

postgres
rails secret
remote storage local
remote storage s3
transfer remote local to s3 to local?
Always prepare / run migrations

@scott is unicorn required, or can I use a loadbalance that roundrobins with affinity?

I think that the current docker container uses Unicorn, but you can use any Rails app server.  I mostly use Puma or Passenger with nginx on the front end.

Hey @fire were you able to get Helpy to work in Kubernetes?

Hey @dwene I am not sure about @fire, but I have been able to run it in Kubernetes and am almost finished with the PR and documentation

That's great to hear @scott ! Let me know if you need a guinea pig to try anything out, or if you need help getting it across the line. I'm definitely interested in trying it.

Ah, I was not able to get Kubernetes running. Other priorities got me.

Hi @dwene Here is what you will want to start with https://github.com/helpyio/helpy/tree/kubernetes/deploy

I should add I left the postgres deployment in there but have not tried to get it working.  I am only interested in using DBAAS for kubernetes myself.  If you can get it to work that would surely be helpful to others.

I'd do Helm chart if you guys create the deployment yaml files.

authors: dwene fire hadifarnoud scott

repo: helpyio/helpy

license: mit

license_source: bigquery


text:
当表头为多级表头时，数据渲染不出来

下图为正常情况：

下图为加入拖拽情况：

下图为Table组件的props参数：

请问作者大大 有遇到这种情况吗

可以给个复现吗

可以给个复现吗

我尝试在沙盒里复现，但没复现出来，只有本地存在这个问题，我明天调试一下源码

好的，辛苦了。如果还是有问题的话，可以把columns，table发出来我看看


text:
🛑 hentaiOS GitLab is down

In c0f68dc, hentaiOS GitLab (https://gitlab.hentaios.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hentaiOS GitLab is back up in 7ae31b5.


text:
Aloe doesn't work when use case has no authorization method

Describe the bug
I'm testing a usecase with no authorization and got an error because ALOE doesn't validate if the usecase has authorization.
To Reproduce
Steps to reproduce the behavior:

Create a usecase without authorization method
Create a test scenario without authorization

Expected behavior
Not authorized error.
Screenshots

Additional context
I have created an issue to request a creation of hasAuthorization method to validade if usecase has authorization before run.

@dalssoft

https://github.com/herbsjs/herbs/issues/46

repo: herbsjs/herbs


text:
move smoltcp to libhermit-rs

The main motivation to move the tcp stack to the kernel, is the easier handling of timing behavior of TCP.
This PR requires hermitcore/libhermit-rs#520

bors r+

bors r+

repo: hermitcore/rusty-hermit


text:
xtask: Add x86_64-uefi target

Replaces https://github.com/hermitcore/rusty-loader/pull/85.
Depends on https://github.com/hermitcore/rusty-loader/pull/86.

bors r+

authors: mkroening stlankes

repo: hermitcore/rusty-loader


text:
Remove x86 dependency

This is required for https://github.com/hermitcore/uhyve/issues/247.
The x86 crate does not provide a configuration which can be compiled on the stable toolchain channel. The rest of uhyve has already been migrated to x86_64. The constants imported from x86 have been inserted manually.

bors r+

repo: hermitcore/uhyve


text:
v0.20.40 looks is the wrong tag for latest release version

as title. should be 0.22.xx?

Yup, my bad, I'll fix.

authors: dcarroll redguardtoo

repo: heroku/force


text:
🛑 Software Center - Test 1 is down

In 4399097, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7abe1d6.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In 0d34306, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 61ce6f3.


text:
🛑 Software Center - Test 1 is down

In 49dcec9, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7516d88.


text:
🛑 Software Center - Test 1 is down

In f3cf805, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 83c2b01.


text:
🛑 Software Center - Test 1 is down

In 31685d5, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 6a63a3c after 17 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 0905eec, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 0fd8791 after 34 minutes.


text:
🛑 Software Center - Test 1 is down

In 3a052d4, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in ea62688 after 21 minutes.


text:
🛑 Software Center - Test 1 is down

In 3690df2, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in dc6e52b after 21 minutes.


text:
🛑 Software Center - Test 1 is down

In 484dd22, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in c1dbe15 after 39 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 397c0c0, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in e56d45c after 18 minutes.


text:
🛑 Software Center - Test 1 is down

In a51ccbf, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d8ad676 after 55 minutes.


text:
🛑 Software Center - Test 1 is down

In 535a397, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d389a4b after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 5ebc1ac, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 02ed9a4 after 51 minutes.


text:
🛑 Software Center - Test 1 is down

In 74f23ea, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 155c4f3 after 1 hour.


text:
🛑 Software Center - Test 1 is down

In 40e51d8, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 33e0189 after 45 minutes.


text:
🛑 Software Center - Test 1 is down

In 6a97938, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 06beac8 after 22 minutes.


text:
🛑 Software Center - Test 1 is down

In 06a6c47, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 01e0b20 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 5760a06, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d9952d1 after 41 minutes.


text:
🛑 Software Center - Test 1 is down

In 871d9ed, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in c0ec5ad.


text:
🛑 Software Center - Test 1 is down

In e2804b5, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in c9d3a27.


text:
🛑 Auth-Bridge - Test 1 is down

In b9b80fb, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in b783be2.


text:
Allow Python 3.8 - What do we need to do?

At the moment the only steps i can see should be:

Remove constraint in setup.py
Add Python 3.8 to travis

This list is not complete.

At the moment the only steps i can see should be:

Remove constraint in setup.py
Add Python 3.8 to travis

I think that is all

repo: hetznercloud/hcloud-python


text:
Fix wrong description for helpers

I found a misc mistake.
Thanks.

Ah yes you found a copy+paste typo! Thank you @tanakaworld

authors: tanakaworld tcrowe

repo: hexojs/site


text:
HHH-13244 test case

setting hibernate.jpa.compliance.proxy=true and org.hibernate debug level to DEBUG breaks hibernate

Superseded by https://github.com/hibernate/hibernate-orm/pull/2770

authors: gbadner stoty

repo: hibernate/hibernate-orm


text:
pessimistic locking

We've been ignoring LockModes and LockOptions, which is reasonable because we don't have transactions yet. However, most of the code to support them is already there, I think it just means adding some of the plumbing to let the user pass them in.

Now that we have a prototype for transactions, we can work on adding support for pessimistic locking.

This is now done, except for the Session.lock() method.

Shit, I didn't actually mean to push that to master. I meant to push it to the txns branch. Uff.
Well, OK, it's fine, no harm done, I guess.

I've opened #142 to cover the missing lock() method, which is much more work, and much less useful.
Since I accidently pushed this work already, I might as well close the issue.
Not my most competent moment.

No worries, it happens. I'm closing the issue.

ahaha, you should see Gavin's SVN history. It's full of ops, fixed now, damn now fix, shit I can't code today etc :D

@emmanuelbernard I'm trying to be a better person.

authors: DavideD emmanuelbernard gavinking

repo: hibernate/hibernate-reactive


text:
Extended output reading and writing

This PR adds additional output reading and writing so that a Booz_xform object can be initialized from netcdf for use with a BoozerRadialInterpolant in simsopt.

The toroidal and poloidal fluxes are read from vmec wout and saved to the booz_xform netcdf file.
G, I, and iota are also now read from the booz_xform netcdf file.

I fixed this issue and added to test_write_read.py to check things relevant to this PR.

The change to the signature of init_from_vmec would require a change to simsopt in https://github.com/hiddenSymmetries/simsopt/blob/master/src/simsopt/mhd/boozer.py#L210-L223. Even with that change, I bet some users will experience errors from using an updated version of simsopt with the pre-update booz_xform, or vice-versa. To avoid this and ease the transition, would it work to move phi0 and phip0 to the end of the argument list and make them optional arguments? E.g. https://en.cppreference.com/w/cpp/language/default_arguments (There might need to be some logic in init_from_vmec to check the length of phi0 and phip0, and if the length is ns, then use them, but if the length is 0 due to them being the default vectors, then set phi and phip to vectors of length ns full of 0s.) Other ideas?

The change to the signature of init_from_vmec would require a change to simsopt in https://github.com/hiddenSymmetries/simsopt/blob/master/src/simsopt/mhd/boozer.py#L210-L223. Even with that change, I bet some users will experience errors from using an updated version of simsopt with the pre-update booz_xform, or vice-versa. To avoid this and ease the transition, would it work to move phi0 and phip0 to the end of the argument list and make them optional arguments? E.g. https://en.cppreference.com/w/cpp/language/default_arguments (There might need to be some logic in init_from_vmec to check the length of phi0 and phip0, and if the length is ns, then use them, but if the length is 0 due to them being the default vectors, then set phi and phip to vectors of length ns full of 0s.) Other ideas?

Thanks for this suggestion. I have followed your advice and made a default argument for phip0 and eliminated the phi0 argument.

authors: ejpaul landreman


text:
fix #278: tracing.hpp does not find boost

This PR fixes #278 .

Thanks for merging this! :-)

repo: hiddenSymmetries/simsopt


text:
Where in: Operand should contain 2 column(s)

Hi, I've encountered this error:
sqlMessage: "Operand should contain 2 column(s)"

while trying to do a query like this:
var data = [ [1, 2] ];
squel.delete()
.from('table')
.where('(field1, field2) IN ?', data)
.toString();

// Produces
DELETE FROM table WHERE ( (field1, field2) IN (1,2) )

I made a couple of tests and seems that the query built from squel is wrongly formed:
// Squel
DELETE FROM table WHERE ( (field1, field2) IN (1,2) )

// Expected
DELETE FROM table WHERE ( (field1, field2) IN ((1,2)) )  <-- note the subgrouping

It seems when the array contains only one item is not grouping it in the right way, instead when you use an array of multiple arrays it's working:
var data = [ [1, 2], [3, 4] ];

squel.delete()
.from('table')
.where('(field1, field2) IN ?', data)
.toString();

// Produces
DELETE FROM table WHERE ((field1, field2) IN ((1,2), (3,4)))

I made a plunker if you want to check this code above.
I didn't look at the source code yet, but if I can find where the problems come from I'll link it too.
Update:
By the way this can be solved simply by surrounding the question mark with parenthesis: (?) but I think the expected beheviour for an array is to be expanded like this:
// normal values doesn't get grouped
[ a ]  -> ( a )
[ a, b ]  -> ( a, b )

// arrays are grouped
[ [a] ]  -> ( (a) )
[ [a, b] ]  -> ( (a, b) )
[ [a, b], [c, d] ]  -> ( (a, b), (c, d) )

// example
array = [
[1, 2, 3],
[4, 5, 6]
];

// When preparing query
WHERE (field1, field2, field3) IN ?

// Expanded query
WHERE (field1, field2, field3) IN ( (?, ?, ?), (?, ?, ?) )

So if the value is an array (even just one) is grouped into parentesis.

I wasn't aware that this was how it arrays out to be expanded. My feeling is that since adding parantheses makes this work ok, users should just do that since it seems simple enough. As otherwise, squel would need more logic to check when/how an array value is being included within the query - and the logic is already tricky.

I see your point and it's right.
But it will be great to introduce it in future, I'll try to contribute, but as you said the logic is already tricky and I had some trouble last time when I first attempted: :]

repo: hiddentao/squel


text:
switching between light and dark background

Hello,
First of all - love the tool, discovered it recently and really happy with the functionality.
Second of all, I need suggestions for my setup.
So I'm using the latest iTerm2 (v3.5) that supports switching color preset (including background) based on the system automatically enabled/disabled dark mode, e.g., if the system is set to light mode during the day, I have the light solarized background, if it's dark mode - I have dark solarized.
As per this suggestion, I'm using scripts and aliases to switch manually between kubecolor and kubecolor --light-background, but wonder if there is more automatic way to switch?

I will take a look into the solution, I think it's possible if the terminal background color can be determined from Go program. But I just don't know how...

authors: AndriiOmelianenko hidetatz

repo: hidetatz/kubecolor


text:
highlightjs-line-numbers support

highlightjs-line-numbers support

https://highlightjs.readthedocs.io/en/latest/line-numbers.html


text:
ISODate format or Epoch time

I am using jsonix to store data in nosql (mongodb). Problem is I cannot query data by date (less than or greater than). Is there a way to set a format to return date either in epoch time or ISODate format?
Disclaimer: I am new to nosql and and recently started using jsonix.

Yes, it is probably possible. I'll put an example together.
But first a question: what do you mean by epoch time and ISODate format, exactly?
My guesses are:

epoch time - a number (integer) of milliseconds after 1970-01-01 and so on.
ISODate format - a string like "2015-01-01T02:03:04"

Please confirm or give your examples.

Currently, the json for the date looks like {"year":2001,"month":10,"day":31,"hour":8,"minute":15,"second":0,"fractionalSecond":0,"timezone":0}
Instead, I wondering if I can get date in the epoch (integer) or ISODate format like your comment.

Yes, possible. I'm working on an example right now.
https://github.com/highsource/jsonix/wiki/Types#defining-custom-simple-types

Following tweak worked for me. In the js file which is generated from .xsd. I changed typeInfo from Calender to DateTime.
{
name: 'dateTimeCreation',
typeInfo: 'DateTime'
}, {
name: 'dateTimeChange',
typeInfo: 'DateTime'
}
Which returns the date in following format "2001-05-31T08:15:00.000Z". Which is queryable in MongoDB.

Documentation:
https://github.com/highsource/jsonix/wiki/Types#defining-custom-simple-types
Example:
https://github.com/highsource/jsonix/blob/master/nodejs/tests/basic/tests/gh48.js
var DateTimeTimestamp = new (Jsonix.Class(Jsonix.Schema.XSD.DateTime, {
	// Strictly speaking name and typeName are not necessary here as they're
	// inherited from Jsonix.Schema.XSD.DateTime
	name : 'DateTime',
	typeName : Jsonix.Schema.XSD.qname('dateTime'),
	parse : function(text, context, input, scope) {
		Jsonix.Util.Ensure.ensureString(text);
		var date = Jsonix.Schema.XSD.DateTime.prototype.parse.apply(this,
				arguments);
		return date.getTime();
	},
	print : function(value, context, output, scope) {
		Jsonix.Util.Ensure.ensureInteger(value);
		var date = new Date(value);
		var text = Jsonix.Schema.XSD.DateTime.prototype.print.apply(this, [
				date, context, output, scope ]);
		return text;
	},
	CLASS_NAME : 'Timestamp'
}))();
var Mapping = {
	name : "Mapping",
	typeInfos : [ DateTimeTimestamp ],
	elementInfos : [ {
		elementName : 'dateTime',
		typeInfo : 'DateTime'
	} ]
};

Continued in #49. You'll be able to use the DateTimeTimestamp and get an integer then.

authors: highsource imomin

repo: highsource/jsonix


text:
You should follow the trademark rules of Apache Software Foundation

I would suggest to change the name of the plugin to jaxb2-maven-plugin to better follow the naming trademarks.
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html

@highsource nice and extensive write-up. Thank you for the plugin BTW.

authors: LIttleAncientForestKami khmarbaise


text:
g++

g++ -shared -o ./davarocr/davar_det/datasets/pipelines/lib/tp_data.so -fPIC ./davarocr/davar_det/datasets/pipelines/lib/tp_data.cpp   -L/fast-drive/workspace/opencv-3.3.0/build/modules/cudabgsegm/CMakeFiles/ pkg-config --cflags --libs opencv
/usr/bin/ld: cannot find -lopencv_cudabgsegm
/usr/bin/ld: cannot find -lopencv_cudaobjdetect
/usr/bin/ld: cannot find -lopencv_cudastereo
/usr/bin/ld: cannot find -lopencv_cudafeatures2d
/usr/bin/ld: cannot find -lopencv_cudacodec
/usr/bin/ld: cannot find -lopencv_cudaoptflow
/usr/bin/ld: cannot find -lopencv_cudalegacy
/usr/bin/ld: cannot find -lopencv_cudawarping
/usr/bin/ld: cannot find -lopencv_cudaimgproc
/usr/bin/ld: cannot find -lopencv_cudafilters
/usr/bin/ld: cannot find -lopencv_cudaarithm
/usr/bin/ld: cannot find -lopencv_cudev
collect2: error: ld returned 1 exit status

I think it is because there is no opencv installed in your environment.

repo: hikopensource/DAVAR-Lab-OCR


text:
Made Site Responsive !!

Fixes #273
Just 2 pages are remaining KMP & Core team ! Please have a look at all pages and let me know if I missed any other than those two pages !!
https://rohank2502.github.io/SFC-foundations/     Deployment link !

@rohank2502 Good work, but still some changes are requested,

The dog div is broken in some pages.
The images with text in about us section needs increment of font size.

Please Have a look at the changes made @himanshu007-creator

All sorted,  just change the font size here in mobile view, and increase the image size

This issue still exist,


text:
🛑 Birthdays is down

In 580c86d, Birthdays (https://m.hinzwifi.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Birthdays is back up in bb145c2 after 16 minutes.

repo: hinzwifi/uptime-hinz


text:
Implement landing page for docs.hiro.so

Figma file: https://www.figma.com/design/WYxzBZubEGwbbzFq79eNim/Docs-Working-File?node-id=1005-728&t=M2Q9MWX8ben3D798-1

@ryanwaits are you working on this ?

merged in with https://github.com/hirosystems/docs/pull/795

authors: ginny-d rehan-adi ryanwaits

repo: hirosystems/docs


text:
Faucet

Describe the bug
A clear and concise description of what the bug is.
Transaction ID
Address
Block#
Time stamp
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots or consol.log to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here:

We're seeing issues with faucet transactions stuck in pending and address balances displaying incorrect numbers.
We need to resync from Genesis to repopulate the missing data, including any other missing data that may not be immediately noticed today.  This is the best way to ensure the data is clean and consistent moving forward.
Unfortunately, this might take a couple of days. Please follow the updates here:
https://status.hiro.so/incidents/psgbfczfcc6c

repo: hirosystems/explorer


text:
start chainhook questions?

chainhook start command:
chainhook service start --start-http-api --no-hord --config-path=/root/config.toml
chainhook-node  | {"msg":"Starting service...","level":"INFO","ts":"2023-07-10T03:18:58.888867375Z"}
chainhook-node  | {"msg":"Listening on port 20456 for chainhook predicate registrations","level":"INFO","ts":"2023-07-10T03:18:58.890419958Z"}
chainhook-node  | {"msg":"Listening on port 20455 for Stacks chain events","level":"INFO","ts":"2023-07-10T03:18:58.890693167Z"}
chainhook-node  | {"msg":"Observing Bitcoin chain events via Stacks node","level":"INFO","ts":"2023-07-10T03:18:58.890708667Z"}
chainhook-node  | Shield:
chainhook-node  | {"msg":"Handling HTTP GET /ping","level":"INFO","ts":"2023-07-10T03:19:06.394931045Z"}
chainhook-node  | {"msg":"Handling HTTP POST /v1/chainhooks","level":"INFO","ts":"2023-07-10T03:19:06.43797417Z"}
chainhook-node  | {"msg":"Handling RegisterPredicate command","level":"INFO","ts":"2023-07-10T03:19:06.438946004Z"}
chainhook-node  | {"msg":"Registering chainhook eebcdfcc-49a3-4bb5-96e3-5cef98d353da","level":"INFO","ts":"2023-07-10T03:19:06.439063712Z"}
chainhook-node  | {"msg":"Updating predicate predicate:eebcdfcc-49a3-4bb5-96e3-5cef98d353da with spec: {"bitcoin":{"action":{"http_post":{"authorization_header":"Bearer cn389ncoiwuencr","url":"http://172.20.0.6:3099/chainhook/inscription_feed\"}},\"enabled\":false,\"include_inputs\":false,\"include_outputs\":false,\"include_proof\":false,\"include_witness\":false,\"name\":\"inscription_feed\",\"network\":\"mainnet\",\"predicate\":{\"operation\":\"inscription_feed\",\"scope\":\"ordinals_protocol\"},\"start_block\":767430,\"uuid\":\"eebcdfcc-49a3-4bb5-96e3-5cef98d353da\",\"version\":1}}","level":"INFO","ts":"2023-07-10T03:19:06.43971942Z"}
chainhook-node  | {"msg":"Updating predicate predicate:eebcdfcc-49a3-4bb5-96e3-5cef98d353da status: "disabled"","level":"INFO","ts":"2023-07-10T03:19:06.439923004Z"}
chainhook-node  | {"msg":"Streaming blocks from bitcoind ","level":"INFO","ts":"2023-07-10T03:19:06.440624379Z"}
chainhook-node  | {"msg":"Starting predicate evaluation on Bitcoin blocks","level":"INFO","ts":"2023-07-10T03:19:08.35585238Z"}
chainhook-node  | {"msg":"30622 blocks scanned, 0 actions triggered","level":"INFO","ts":"2023-07-10T03:19:26.310252013Z"}
chainhook-node  | {"msg":"Updating predicate predicate:eebcdfcc-49a3-4bb5-96e3-5cef98d353da status: {"scanning":{"cursor":798051,"end_block":798050,"occurrences_found":0,"start_block":767430}}","level":"INFO","ts":"2023-07-10T03:19:26.31200693Z"}
chainhook-node  | {"msg":"Enabling Predicate eebcdfcc-49a3-4bb5-96e3-5cef98d353da","level":"INFO","ts":"2023-07-10T03:19:26.313299055Z"}
chainhook-node  | {"msg":"Updating predicate predicate:eebcdfcc-49a3-4bb5-96e3-5cef98d353da with spec: {"bitcoin":{"action":{"http_post":{"authorization_header":"Bearer cn389ncoiwuencr","url":"http://172.20.0.6:3099/chainhook/inscription_feed\"}},\"enabled\":true,\"include_inputs\":false,\"include_outputs\":false,\"include_proof\":false,\"include_witness\":false,\"name\":\"inscription_feed\",\"network\":\"mainnet\",\"predicate\":{\"operation\":\"inscription_feed\",\"scope\":\"ordinals_protocol\"},\"start_block\":767430,\"uuid\":\"eebcdfcc-49a3-4bb5-96e3-5cef98d353da\",\"version\":1}}","level":"INFO","ts":"2023-07-10T03:19:26.31423293Z"}
chainhook-node  | {"msg":"Updating predicate predicate:eebcdfcc-49a3-4bb5-96e3-5cef98d353da status: "initial_scan_completed"","level":"INFO","ts":"2023-07-10T03:19:26.314372013Z"}
After the ordinals started, the chainhook log stopped and did not continue to scan the index

@pupudaye I've moved your issue to our new repo https://github.com/hirosystems/hord - dedicated to ordinals indexing.
I invite you to follow the steps from the README, this new tool is way easier to approach and use, while providing the same features from an ordinal point of view.
Feel free to re-open issues if you're having some troubles getting started with hord.

authors: lgalabru pupudaye

repo: hirosystems/hord


text:
feat: bnsx query contract

Try out this version of the Hiro Wallet - download extension builds.

Clone of @hstove's PR

Making note of this open PR to fix a validation bug involving the current recipient field handling with a bns address: https://github.com/hirosystems/stacks-wallet-web/pull/3359
Prob need to rethink the relationship b/w these two fields and how they are validated?

authors: fbwoolf kyranjamie

repo: hirosystems/stacks-wallet-web


text:
feat: Strict ECDSA Signatures

Strict signatures contain the following properties:

Signatures encoded as (R,S), S is always smaller than the group order.
The signature is calculated over the hash of the public key and the message

This second property satisfies the requirements for Universal Exclusive Ownership, as defined in this paper (section 3.3).
Strict signatures are more suitable in applications where it's undesirable for s1 = s2 given s1 = sign(k1, msg1) and s2 = sign(k2, msg2). Direct ECDSA permits this condition (even if msg1 = msg2).
Description
Breaking change?
No, it's a new feature.
Example

Checklist

[x] Unit tested updated code paths
[x] Tagged 1 of @janniks or @zone117x for review

Thanks, great change. Maybe we should mention the currently implemented SIP-018 somewhere, this will stay unstrict 🤔

Added some test cases

@fpbgg I notice this PR is in draft. Is it intended for merge?

authors: fpbgg janniks smcclellan


text:
fix: not close tooltip on click

Closes #603
Description

Fix bug . Tooltip should be not closed when click on trigger element.

Current behavior (updates)

Currently, when click on trigger element the tooltip will be hidden

New behavior

Tooltip not being hidden when click trigger element.

Is this a breaking change (Yes/No):

no

Additional Information
https://github.com/hirotomoyamada/yamada-ui/assets/78476413/1704638a-18f1-4543-91ea-1807967f4c7a

@quangnmwork
Hey! thanks for the PR.
Please also change JSDocs.
  /**
   * If `true`, the tooltip will hide on click.
   *
   * @default false
   */
  closeOnClick?: boolean

@quangnmwork
Hey! thanks for the PR.
Please also change JSDocs.
  /**
   * If `true`, the tooltip will hide on click.
   *
   * @default false
   */
  closeOnClick?: boolean

Thanks . I have changed the JSDoc !

authors: hirotomoyamada quangnmwork

repo: hirotomoyamada/yamada-ui


text:
[SmartContracts.js] Line needs to be evaluated for null before calling 'Object.keys'

https://github.com/hive-engine/steemsmartcontracts/blob/0bb3c76955a1cda0636f6716ff31a2a847f42c1f/libs/SmartContracts.js#L543
Not yet known, but in some conditions, the VM is null and the following error could appear on the log:
2022-07-18 03:52:57 error: [Blockchain] ERROR DURING CONTRACT EXECUTION:  TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at Function.getJSVM (/home/user/steemsmartcontracts/libs/SmartContracts.js:543:14)
    at /home/user/steemsmartcontracts/libs/SmartContracts.js:558:33
    at new Promise (<anonymous>)
    at Function.runContractCode (/home/user/steemsmartcontracts/libs/SmartContracts.js:557:12)
    at Function.executeSmartContract (/home/user/steemsmartcontracts/libs/SmartContracts.js:493:42)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Block.processTransaction (/home/user/steemsmartcontracts/libs/Block.js:263:19)
    at async Block.produceBlock (/home/user/steemsmartcontracts/libs/Block.js:132:7)
    at async /home/user/steemsmartcontracts/plugins/Blockchain.js:92:9

2022-07-18 03:52:57 error: [Blockchain] {
  refHiveBlockNumber: 66190261,
  transactionId: '64471f5b09ac71815bdc6a601282df22f83df6a2',
  sender: 'ricksens85',
  contract: 'market',
  action: 'sell',
  payload: '{"symbol":"SPS","quantity":"274.29500000","price":"0.11095121","isSignedWithActiveKey":true}',
  executedCodeHash: '5e327ab66bc4bc780892b2c80856b3b595b792ac31ab0c0c4eb1498e51550e08815ad74975ef2099fb0d332f42eb5503e27c52c78002f3d408fb0ca67bc37edb',
  hash: '413868a1198a7b8074da6aa4400c8245a341da0c8c63feafd56629ea626dceaf',
  databaseHash: 'c542f6f0b54578e6a316a5af915d161a7f974293b4269a04f8266bd5d752e10f',
  logs: '{"events":[{"contract":"tokens","event":"transferToContract","data":{"from":"ricksens85","to":"market","symbol":"SPS","quantity":"274.29500000"}}]}'
}

2022-07-18 03:52:57 error: [Blockchain] Transaction {
  refHiveBlockNumber: 66190261,
  transactionId: '64471f5b09ac71815bdc6a601282df22f83df6a2',
  sender: 'ricksens85',
  contract: 'market',
  action: 'sell',
  payload: '{"symbol":"SPS","quantity":"274.29500000","price":"0.11095121","isSignedWithActiveKey":true}',
  executedCodeHash: '',
  hash: '383bc011e2f8e4e21ee16918f17dbc29715add27286db07b12515a0f3486270c',
  databaseHash: '7ad7fddacff80400efee6f04b4b6fbb71b00d10447d748fd75d2001c386992f5',
  logs: '{"errors":["TypeError: Cannot convert undefined or null to object"]}'
}

2022-07-18 03:52:57 error: [Blockchain] Error: tx hash mismatch with api
    at Block.produceBlock (/home/user/steemsmartcontracts/libs/Block.js:140:17)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async /home/user/steemsmartcontracts/plugins/Blockchain.js:92:9
    at async producePendingTransactions (/home/user/steemsmartcontracts/plugins/Blockchain.js:91:7)
    at async produceNewBlockSync (/home/user/steemsmartcontracts/plugins/Blockchain.js:144:5)

2022-07-18 03:52:57 error: [Blockchain] (node:3040128) UnhandledPromiseRejectionWarning: Error: tx hash mismatch with api
    at Block.produceBlock (/home/user/steemsmartcontracts/libs/Block.js:140:17)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async /home/user/steemsmartcontracts/plugins/Blockchain.js:92:9
    at async producePendingTransactions (/home/user/steemsmartcontracts/plugins/Blockchain.js:91:7)
    at async produceNewBlockSync (/home/user/steemsmartcontracts/plugins/Blockchain.js:144:5)

This happens with higher versions of vm2.

repo: hive-engine/steemsmartcontracts


text:
🛑 Reime ohne Sinn und Verstand is down

In eb89c4a, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in afba554 after 8 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 Griffo is down

In a6b0201, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 96a11f6 after 13 minutes.


text:
🛑 Griffo is down

In 0f99506, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 70389a6 after 8 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In 182487e, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in 6ab1697 after 8 minutes.


text:
🛑 Opa Hansi is down

In e3f26ab, Opa Hansi (https://www.opahansi.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Opa Hansi is back up in 79a3421 after 7 minutes.


text:
🛑 HJStrauss is down

In d2a6faa, HJStrauss (https://www.hjstrauss.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in b8e97be after 9 minutes.


text:
SSR / Next.js example

Hi there!
What you are doing is amazing and you are solving a very big problem for apps that have a lot of strings. I'm really glad this exists now!
However, from the current examples it's not immediately obvious how this would work with isomorphic apps, using Next.js for example.
So if you could provide some pointers or maybe create a Next.js example, you'd save someone's life :)
Thanks!

Thanks for the idea! You're right, a Next.js example would be helpful.
I'm not super familiar with nextjs but I'll give it a shot. In the meantime, if you get an example working can you make a pull request! :)
Let me know if you have any other questions getting set up

@willross Let me know if this helps https://github.com/hjylewis/babel-plugin-inline-i18n-messages/tree/master/examples/nextjs-example

@hjylewis, thanks for the quick response!
Your Next.js example has some issues from the Next.js project logic point of view, but they are easily fixed.
The main problem is that en locale is hardcoded in the .babelrc, therefore the locale doesn't change even when you provide a different locale prop to IntlProvider.
I see that in your react-intl-example you are exporting a dedicated webpack config for each locale to solve that. To be honest, I don't really understand your approach to configuring webpack like that, but I'm not very good with webpack/babel magic.
So far I'm unable to successfully reproduce this approach in next.config.js, which is where webpack is configured in Next. I'm not sure if it even is possible to export multiple webpack configs in Next.
Here's my repo, hope you'll have an opportunity to take a look: https://github.com/willross/nextjs-example. In it's current state it's working with the hardcoded locale, but doesn't allow changing languages.

Apparently, currently you can't return an array of webpack configs in Next.js (https://github.com/zeit/next.js/issues/1306). Do you think there's a way to achieve multi-locale functionality some other way?

Hmm, that's what I was worried about.

Your Next.js example has some issues from the Next.js project structure logic point of view, but they are easily fixed.

PRs are welcome :)

Apparently, currently you can't return an array of webpack configs in Next.js (zeit/next.js#1306)

Yeah, that's how the other examples work. You are basically building a version of your application for each locale.

Do you think there's a way to achieve multi-locale functionality some other way?

You could set it up so that all locales are loaded. This would be suboptimal since it would increase bundle size but works with Next.js. It would also have the added benefit of allowing locale switching without a refresh
To get that to work, your getMessage function should ignore the locale argument and return an object containing the message in every locale (instead of just a string). Then you'll want to modify your addMessages function to accept these objects.
// getMessage

const fs = require("fs");
const path = require("path");

module.exports = function getMessage(key, locale, defaultMessage) {
  const en = JSON.parse(fs.readFileSync(
    path.resolve(process.cwd(), `./i18n/messages/en.json`)
  ));
  const es = JSON.parse(fs.readFileSync(
    path.resolve(process.cwd(), `./i18n/messages/es.json`)
  ));

  return {
    en: en[key] || defaultMessage,
    es: es[key] || defaultMessage,
  }
};

// addMessages
const messages = {
  en: {},
  es: {},
};

export function getMessages(locale) {
  return messages[locale];
}

export function addMessages(idAndMessages) {
  idAndMessages.forEach(([id, messageObject]) => {
    Object.keys(messageObject).forEach(locale => {
      messages[locale][id] = messageObject[locale];
    });
  });
}

// App.js

...

<IntlProvider locale={locale} messages={getMessages(locale)}/>

...

Unfortunately, since Nextjs doesn't make it easy to build multiple outputs there isn't a way to build per-locale bundles without ditching Nextjs. That said, you should be able to SSR per-locale bundles, just not with Nextjs.
Does that help? Let me know if you have any questions

Yup, this approach works!

authors: hjylewis willross


text:
Issue #42 Add lasteRefreshedOn variable

Description
This adds the lastRefreshedOn variable to fix issue #42

LGTM


text:
🛑 eService-HK.com is down

In fbe77f3, eService-HK.com (https://eservice-hk.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: eService-HK.com is back up in 022de20 after 42 minutes.

repo: hklcf/upptime


text:
Home (Gabriel Hess, BFH I4MI)

ch.fhir.ig.ch-etoc#2.0.0-ballot /
Die Links zu den Composition Sections funktionieren nicht.
Ausserdem zahlreiche Typos:
Kapitel 1.1

[ ] „hispital“ statt „hospital“
[ ] my be implemented“ statt „may be implemented

Kapitel 1.2

[ ] Überflüssiges „>“ nach dem FHIR R4 Link
[ ] „the the HL7 Switzerland Technical Committee“ (doppeltes the)
[ ] „disccussed“ statt „discussed“
[ ]  „questionnaie“ statt „Questionnaire“
[ ] generell Questionnaire und QuestionnaireResponse nicht einheitlich, z.T. gross geschrieben, z.T. klein, Questionnaire Response zum Teil auseinander
[ ] „Swiss Core“ statt „CH Core“
[ ] „secctions“ statt „sections“
[ ] „condsidered“ statt „considered“
[ ] „Copy receiver is ment“ statt „… is meant“

Gabriel Hess, BFH I4MI

Various typos on the home page corrected
See Home
Update changelog

authors: ig-feedback pjolo


text:
use directory local variable change module load behavior

Hi, @hlissner
I have add gtags to doom-emacs. Now I want to implement some feature as description below:

when open a project, detect whether gtags-enable-for-this-project is defined.
if it is not defined, ask user "whether use gtags", then write user's option to directory local variable
gtags-enable-for-this-project
if gtags-enable-for-this-project is t, enable gtags and disable lsp

my question is how I could make gtags-enable-for-this-project available before related module is loaded. e.g. change the cc module load behavior due to gtags-enable-for-this-project.

Sorry for the late response. Perhaps something like this?
(defun check-gtags ()
  (when (memq major-mode '(c-mode c++-mode objc-mode))
    (unless (bound-and-true-p gtags-enable-for-this-project)
      (setq gtags-enable-for-this-project
            (y-or-n-p "Enable gtags?")))
    (when gtags-enable-for-this-project
      (gtags-mode +1)
      (lsp-mode -1))))
(add-hook 'hack-local-variables-hook #'check-gtags)

Using hack-local-variables-hook means the function is a) after changing a major-mode and b) after file/dir-local variables are read.

@hlissner thanks for you help. doom-emacs is the best emacs config that I ever used.

authors: chengyi hlissner

repo: hlissner/doom-emacs


text:
Set locate-command in tools macos

It should be mdfind since spot light is on by default.
I think you could still improve things further by not making users that prefer locate on a mac to override two options, but this is better already.

Thanks for the help!

authors: hlissner rgrinberg


text:
Package hls4ml with setuptools

Create a single user-facing tool and package the project with setuptools so it can be installed with pip in the future. More details here:
https://gist.github.com/vloncar/f149c7a0dba34d51e0d9c6d3cb17b12a
(sans the model zoo part for now)
Noah Paladino (@ngpaladi) will work on this.

https://github.com/vloncar/hls4ml/tree/intel

I have created a branch with some initial support for setuptools:
https://github.com/vloncar/hls4ml/tree/packaging
Includes a major restructuring of the project packages and introduces a new tool (located in scripts/hls4ml) that, when installed, will be available from the command line. A lot of things still need to be done to support running the included hls4ml from any location. @nhanvtran @ejk43 comments on the project structure and setuptools are welcome.
Brief example on how to build and install the wheel:
python setup.py sdist bdist_wheel
pip install dist/HLS4ML-0.2.0-py3-none-any.whl

@ngpaladi If you have any questions, feel free to ask me.

Nice! Installation worked for me in a clean conda environment and I could access the hls4ml script on my path. Also, if you're in the hls4ml repo, you can just do pip install . which saves a line of typing.
I tried running hls4ml convert -c <config> in a out-of-tree test directory but had a few failures, mostly related to typos and not installing the hls-templates package_data. Some minor updates here seemed to fix stuff: https://github.com/ejk43/hls4ml/tree/packaging
I was able to create a project from the example config in a new directory and run through simulation/synthesis! Pretty cool! Very useable.
One odd thing is that the include file for the nnet_utils folder ends up referencing the files inside the conda environment (or wherever hls4ml is installed). Maybe it would make sense to optionally copy the nnet_utils library into some source code directory? Or inside the generated project?

Hi @ejk43, thanks for the fixes. I thought that include_package_data=True in setup.py should be enough, but the files weren't there.
BTW, is pip install . always reinstalling all files of a package? I had issues when using that command to switch between different (major) versions of onnx development branch. Apparently not all files got rebuilt and replaced and that led to many problems, I hope that in our project we can't get into that situation.
Regarding the nnet_utils, my preference is to bundle these files with the generated project. That is how I did it for the intel branch. I thought it was a simpler solution as it can save us from users complaining that something broke when they upgrade hls4ml (or conda).

Regarding the nnet_utils, my preference is to bundle these files with the generated project. That is how I did it for the intel branch. I thought it was a simpler solution as it can save us from users complaining that something broke when they upgrade hls4ml (or conda).

Yeah, thats a really good point. I completely agree. My branch refers to the nnet_utils in the conda env but packaging with the generated project is definitely a better approach.

BTW, is pip install . always reinstalling all files of a package? I had issues when using that command to switch between different (major) versions of onnx development branch.

Aha, gotcha, pip is sometimes weird. I usually do pip install -U . which makes it upgrade the package if you've incremented the version. If that still doesn't work: pip install -U --force-reinstall .

@ngpaladi I've merged EJ changes and added a fix for nnet_utils. You can take over from here.

authors: ejk43 nhanvtran vloncar


text:
feat: add article cards block

This is the first pass at adding a cards block. There are several cards described in the ticket, this one is specifically for articles. I renamed the existing card block to article-cards and added a "Lead-Article" variant.
The default block accepts a list of article URLs:

It will convert those into cards for the target articles:

The Lead-Article variant is similar when authored:

The main difference is it will emphasize the first bullet point and use a grid format:

There are some TODOs to figure out:

Right now it's using fetch to retrieve data from the query index. This approach won't scale, so we'll need to revisit when we have more data.
We'll need a way to determine an article's "category". Right now I've hard-coded one. We can derive the category's path from the article's URL, but we'll need some way to translate that into the category's display name.
We may need to revisit some minor padding/formatting in the cards as the site comes together more.

Fix #13
Test URLs:

Before: https://main--channelco-crn-com--hlxsites.hlx.page/drafts/frisbey/
After: https://issue-13--channelco-crn-com--hlxsites.hlx.page/drafts/frisbey/

The variant will disregard any bullets past the first 5.

I was hoping to be able to do the grid layout of the "Lead-Article" variant with pure CSS, but it seems that the number of articles in the grid can be more than 4. So I'll revisit this and come up with a different way.

@mfrisbey

We'll need a way to determine an article's "category". Right now I've hard-coded one. We can derive the category's path from the article's URL, but we'll need some way to translate that into the category's display name.

We have that field set as tag  on the article level ,see sample and should be indexed (can be renamed as 'category' if it makes more sense, just let @varunmitra know)

@kunwarsaluja  We have that field set as tag on the article level

Nice! Should we assume that matches 1:1 with the parent path of the URL? For example, the URL path of that article is:
/news/managed-services/painful-decision-slalom-consulting-layoffs-hit-900-workers

I could:

Display the Tag value from the metadata as the link's text.
Use the URL's parent path as the href (in this case /news/managed-services)

Does that sound ok?

@mfrisbey  That is valid for all news articles (of template=article) but when it comes to Company pages like this, we'll be relying on a different metadata (companynames set on the article level, was just added today to the live site, will update the content tomorrow)
can't we rely on the 'path' from the index to get the article url ?

@kunwarsaluja can't we rely on the 'path' from the index to get the article url ?

yes, that's what I meant - I misspoke by using URL.

@mfrisbey  I think 'category' as metadata makes more sense/intuitive here..'tag' is pretty generic. Can you use 'category'  for now ? ill update the  sample content with category in 5mins
@varunmitra Can you please adjust the migration script to make 'category' instead of 'tag'

@kunwarsaluja I think 'category' as metadata makes more sense/intuitive here

Sounds good!

@kunwarsaluja FYI, it's now using the category value from the index. I also added links to the article, and some aria/accessibility-related properties to the appropriate elements.

authors: kunwarsaluja mfrisbey

repo: hlxsites/channelco-crn-com


text:
feat: pdf viewer

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #28
Test URLs:

Before: https://main--mammotome--hlxsites.hlx.page/en/dj-test-pdf-viewer
After: https://28-pdf-flip-book--mammotome--hlxsites.hlx.page/en/dj-test-pdf-viewer

@Acidham this is a general issue with section styling and affects all blocks. i will open a follow-up issue to fix it for all.

@karlpauls PTAL

repo: hlxsites/mammotome


text:
Updated video player

Update video player id + some optimizations to lazy load videos until we need them
New player ID based on https://adobe-dx-support.slack.com/archives/C03GXBSC72T/p1667413712026009
Test URLs:

Before: https://main--theplayers--hlxsites.hlx.page/past-champions/archive/al-geiberger-1975
After: https://updated-video-player--theplayers--hlxsites.hlx.page/past-champions/archive/al-geiberger-1975

thank you for doing this!

authors: fkakatie shsteimer

repo: hlxsites/theplayers


text:
CIV-8582 MultiList

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Bundle defaults to an electronic bundle, regardless of option chosen on Disposal hearing DJ journey
Change description
Bundle defaults to an electronic bundle, regardless of option chosen on Disposal hearing DJ journey
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Will this require the change ın cıvıl-service data model to have List type for multiple values?

authors: sabahirfan suvarnathekkoot

repo: hmcts/civil-ccd-definition


text:
CIV-6683 Add Api Test

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-6683
Change description
Add API test for written rep without notice application to assert error
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

repo: hmcts/civil-general-apps-ccd-definition


text:
CIV-13408 notification for help with fees in review

JIRA link (if applicable)
CIV-13408
Change description
Add notification for claimant after requesting help with fees
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

https://build.hmcts.net/blue/organizations/jenkins/HMCTS_a_to_c%2Fcivil-service/detail/PR-4529/17/pipeline/ got green

repo: hmcts/civil-service


text:
scrape insecure not working

Hi,
nice work! But i got a little error, it seems the ssl-certificate of the scrape-target is checked anyway..?
/usr/local/bin/prometheus_nginx_exporter -insecure -nginx.scrape_uri https://localhost/nginx_status_vts
2017/10/27 11:35:22 Starting nginx_vts_exporter (version=0.6, branch=HEAD, revision=e48bd6899d8864b11b9f71f852b049ec3ad2ae26)
2017/10/27 11:35:22 Build context (go=go1.8.3, user=root@3b0fc1d0acb6, date=20170808-07:09:08)
2017/10/27 11:35:22 Starting Server at : :9913
2017/10/27 11:35:22 Metrics endpoint: /metrics
2017/10/27 11:35:22 Metrics namespace: nginx
2017/10/27 11:35:22 Scraping information from : https://localhost/nginx_status_vts
2017/10/27 11:35:23 fetchHTTP failed Get https://localhost/nginx_status_vts: x509: certificate is valid for *.xyz.de, not localhost

Accessing localhost over HTTPS doesn't make a ton of sense. I would access it over HTTP by running prometheus_nginx_exporter -insecure -nginx.scrape_uri http://localhost/nginx_status_vts.
Accessing a localhost endpoint never leaves the host, so you don't need to worry about unencrypted network traffic. If you're concerned about exposing an unencrypted endpoint on the nginx host, just make sure that the VTS module stats is only listening on localhost.

Of course you are correct, scraping localhost via ssl doesn't make much sense. I just assumed the error would be the same as scraping some self-signed ssl endpoint.

Maybe we could consider using -k like curl to do insecure https request?

yes, i thought thats what the -insecure was for... isn't it?

support -insecure now, please check the latest release.

authors: hnlq715 remeika strowi


text:
why I got so little metrics

[root@node1 export]# curl http://10.96.174.195:9913/metrics
HELP nginx_vts_exporter_build_info A metric with a constant '1' value labeled by version, revision, branch, and goversion from which nginx_vts_exporter was built.
TYPE nginx_vts_exporter_build_info gauge
nginx_vts_exporter_build_info{branch="HEAD",goversion="go1.9.4",revision="43b45563691a369b8fa12f7383d185a6b28d18ea",version="0.10.3"} 1

Please make sure your nginx is compiled with vts correctly.

+1
Any solutions?

+1 Any solution?
I have nginx 1.12 with module nginx-module-vts
http://domain.name/status/format/json
or
http://domain.name/status/format/prometheus
shows all metrics, but nginx-vts-exporter doesn`t
I tried different version (0.10.0, 0.10.3, 0.10.7)


text:
Add further packages

[ ] mne-rsa: will be added as soon as the conda-forge package is ready
[ ] mne-hfo: @adam2392 was unsure whether it's ready for inclusion yet (0.2)
[ ] mne-features: conda-forge package in PR
[ ] mne-microstates: there doesn't seem to be an officially tagged release. Are you planning on making a release sometime, @wmvanvliet?
[ ] I just came across MNE-ARI, it's super new. Should we get in touch with the author and include it?

cc @agramfort @larsoner

I could mint a release for mne-microstates. It was always intended as a simple script, but it actually has some users now that are not me :)

authors: hoechenberger wmvanvliet

repo: hoechenberger/mne-installers


text:
Fix: prevent logging base64 schema as static asset not found

Prevent logging "Asset not found" for css base64 references as filepath,
i.e. "background:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAAsCAYAA...);"

Fantastic :+1:

authors: hollandben lnfnunes

repo: hollandben/grunt-cache-bust


text:
init: ported Get_String_Encoder primitive function

Since level-2 libraries use certain string functions, we have to port their primitive functions into HestiaKERNEL. Hence, let's do this.
This patch ports Get_String_Encoder primitive function into init/ directory.

skip review since it's a port and is not affecting the production implementations.

repo: hollowaykeanho/Upscaler


text:
Provide functionality for subscribing to events

As far as I could see there is currently no functionality for subscribing to events.
Are there any plans to add this?

You subscribe to node events automatically. Note that currently we only forward urgent events

I was thinking about events like these:

HardwareFaultChange
NetworkFaultChange
BootReason

I guess a workaround now is to subscribe to the attributes that may change as a result of these events.

Yeah, that is better as the non-urgent events are very verbose

I'm a bit confused on how the "attribute_updated" events are currently working.
I found this in the code ():
        LOGGER.debug(             "The subscribe_attribute command has been deprecated and will be removed from"             " a future version. You no longer need to call this to subscribe to attribute changes."         )
How can I general subscribe to updates to cluster attributes if I'm not supposed to call the subscribe_attribute command?
I see that I get updates to an attribute that I subscribe to, but I don't see that I get events for other attributes.

the server now defaults to a wildcard so as soon as you send the "start_listening" command, you will from then on receive all attribute updates and urgent events, no longer needed to explicitly tell what attributes to subscribe. You can do filtering in your own implementation.

Ok, sounds good as a starting point.
What about attributes for clusters like Software Diagnostics Cluster? Doesn't the device periodically updates attributes like  ThreadMetrics,  CurrentHeapFree etc.? Shouldn't I get events for these? I get updated values if I request them with the "read_attribute" command. I just need to understand why I get events for some and not for others.

That is completely device dependent but I think you also want the non urgent device events.
I skipped those for now because they are verbose and cause a lot of traffic while we are already struggling with thread network stability.
Let's keep this open as feature request to add an additional/optional subscription to the non-urgent node events as well, maybe with a slow interval.

I'm not talking about events in general here, only attribute updates. Are you categorizing attributes into urgent / non-urgent ones? If I see that values have changed between calls to "read_attribute", I would have assumed that I should have received an "attribute_updated" in-between.
Ideally, I would have lefty more of the responsibility for managing this up to the caller and have a bit less stuff happen "automagically".

You get ALL attribute updates already.

Ok, then I need to understand why I'm getting "attribute_updated" events for carbonmonoxideconcentrationmeasurement measured-value, but not for softwarediagnostics current-heap-free.
Both are changing values over time.

I think that is device dependent. Are you sure the device should report that as attribute updated reports ?

According to the .zap file the attribute reporting are enabled for the softwarediagnostics attributes:

OK, then you should get them. If not, you have a device issue.
As I said, we're doing a wildcard sub to the device, all attributes updates are forwarded

@olavt make sure you run the latest Matter server version.

The device decides what to send with a wildcard sub

authors: balloob marcelveldt olavt


text:
Add support for new controller command

Adds support for this change: https://github.com/zwave-js/zwave-js-server/pull/666
Also bumping the schema version required because of this bug which is properly fixed here: https://github.com/zwave-js/zwave-js-server/pull/665 . It was technically fixed here: https://github.com/zwave-js/zwave-js-server/pull/662 but then the clients wouldn't have this node in their model so it would serve no utility

I swapped it around in preparation for schema 20. Dependent on upstream release


text:
Addon Samba unable to connect since 9.1.0

Hi,
I updated samba addon to 9.1.0 and then the backup job that uses smb share to copy /backup folder to my NAS failed.
I tried to remove the connected smb share from NAS to HASS, and add it back without luck. I looked to the changes from 9.0.0 to 9.1.0 but i can't see why it's not working anymore. Downgrade to 9.0.0 works good.
Unfortunately i have no logs on the NAS when it fails (just say connection to the share failed) and in addon log nothing interresting comes up on connection tries from the NAS (only that auth worked). From my windows 10 PC it's working good with 9.1.0...

I have the same issue.....it also nocks out smb on my other two computers stopping sharing. As soon as the addon is reverted back to 9.0.0 it works perfectly

I confirm the same issue, when I try to connect from my ubuntu18.04 pc the system say that it is not possible to create list of share folder and connection is refused. I've check the option.json file it seems ok. I tried different configuration with allow ip but nothing change. Please solve this issue as much as possible. My system is Hassio with HassOS on raspberry Pi4 4gb 32bit ver. Is it possible to downgrade the addon?

I confirm the same issue (I'm currently using VM Box with Hassio installed).
Thanks!

My Synology NAS says that it cannot mount my /backup directory because the addon doesn't support SMB1. I know SMB1 shouldn't be used anymore, due to security issues, but Synology only seems to support SMB1, and in a controlled network, it should be possible to choose SMB1.

I confirm the same issue, how do i revert back to 9.0.0 ? i did a lot of changes the same day and my snapshot is too old to go back. just for this. 9.0.2 please!

To revert to 9.0.0 i used a snapshot and only restore the addon (you can chose what you want to restore) so even it's an old one just restore only the addon !
Before restore anything, do a snapshot ;) I'm not responsible for any damage while downgrading this addonc via snapshots !

Same problem, I tried to revert to a 9.0 version snapshot but I get same error:
20-04-20 13:29:30 ERROR (SyncWorker_16) [supervisor.docker] Can't start addon_core_samba: 403 Client Error: Forbidden ("endpoint with name addon_core_samba already exists in network host")

In my case I reverted back to 9.0 by using an older snapshot and restoring the samba addon only.
It worked smoothly.
Before doing anything it is always recommended to do the snapshot, you know, just in case! ;-)

@pvizeli @tathamoddie any suggestion as you were both behind the wheel for the last update on this addon ?

I have no issue, maybe wrong credentials? Do you have something like an error on a log?

@pvizeli are you using SMB1 Sharing Protocol on Windows 10. As soon as the latest addon 9.1.0 is used. Everything drops off the network. As soon as 9.0.0 is restored its reappears.

Nothing happens when I select only "Samba Share" and click "Restore Selected". No idea why. My snapshots are password protected. Anyone who has managed to to a partial restore of the "Samba Share" add-on from a password protected snapshot?

I've solved with a partial restore from a snapshot. @olapettersson it's seem strange you couldn't restore, after restore your samba version is 9.0 or lower version? Anyway I haven't uderstood if samba is linked anyhow to appdeamon addon because after restore the old samba version I've found appdeamon addon activeted. Before I installed the addon but I never activated it in order to understand the best configuration. Good luck waitng for a new samba version

There were two changes from 9.0 to 9.1.0.

The default allow_hosts list had fe80::/10 added to it. This is covered in 8427d678ecd8d755c6c37eafa489b23fdcb0d3f5. You can revert this in your local environment by just removing that line from the runtime config of the extension; it's user-configurable, so you can add and remove this line to your heart's content. That changeset was the entire scope of pull request #1208 when I submitted it.

@pvizeli incorporated an extra change into the pull request before merging it, mainly with changeset e7877374b990f18f648b2846a4abea329a6f5b65. In this changset, "init": false was added to the extension's config.json. According to https://developers.home-assistant.io/docs/hassio_addon_config/#add-on-config, this would normally be defaulted to true, so this is a change in the configuration. It is not user-configurable, so you can't easily try toggling it back on. It relates to a Docker setting, so might indicate a link with the log event that @fudu shared in https://github.com/home-assistant/hassio-addons/issues/1224#issuecomment-616557967. I don't know why this non-IPv6-related change was added to pull request #1208.

@pvizeli no, unfortunately there's no log in addon nor in supervisor.
Here is a fresh log from upgrade from 9.0.0 to 9.0.1 + trying to connect from my NAS :
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:27:18] INFO: Hostname: hassio
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user snoof.
nmbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface ens18 ip=2a01:e0a:3a0:de50:341d:89ff:fe90:d77c bcast= netmask=ffff:ffff:ffff:ffff::
added interface ens18 ip=192.168.1.3 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.3 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0
create_subnets: ignoring non IPv4 interface.
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface ens18 ip=2a01:e0a:3a0:de50:341d:89ff:fe90:d77c bcast= netmask=ffff:ffff:ffff:ffff::
added interface ens18 ip=192.168.1.3 bcast=192.168.1.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
Closing idle connection
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
check_ntlm_password:  authentication for user [snoof] -> [snoof] -> [snoof] succeeded
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
check_ntlm_password:  authentication for user [snoof] -> [snoof] -> [snoof] succeeded

We can see the NAS connecting with correct credentials but on the other side, from the NAS : error connecting to the shared staorage.
@tathamoddie : thx for your answer, i was around the same point => init: false added to your PR. @pvizeli why this has been added ? Coult it be the problem ?

To compare : logs from 9.0.0 and a connection from the NAS :
[11:35:55] INFO: Hostname: hassio
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user snoof.
nmbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface ens18 ip=2a01:e0a:3a0:de50:341d:89ff:fe90:d77c bcast= netmask=ffff:ffff:ffff:ffff::
added interface ens18 ip=192.168.1.3 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.3 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0
create_subnets: ignoring non IPv4 interface.
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface ens18 ip=2a01:e0a:3a0:de50:341d:89ff:fe90:d77c bcast= netmask=ffff:ffff:ffff:ffff::
added interface ens18 ip=192.168.1.3 bcast=192.168.1.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
check_ntlm_password:  authentication for user [snoof] -> [snoof] -> [snoof] succeeded
idmap range not specified for domain '*'
192.168.1.5 (ipv4:192.168.1.5:52514) connect to service backup initially as user root (uid=0, gid=0) (pid 68)
192.168.1.5 (ipv4:192.168.1.5:52514) closed connection to service backup
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
check_ntlm_password:  authentication for user [snoof] -> [snoof] -> [snoof] succeeded
idmap range not specified for domain '*'
snoof-nas (ipv4:192.168.1.5:52538) connect to service backup initially as user root (uid=0, gid=0) (pid 69)

Considering both logs show a successful container start and script execution, I think we can park the idea that the init: false change is the issue.
That leaves us with no clear change causing an issue though...
I note that your 9.0 logs contain references to smbd version 4.10.8 started
Your 9.1 logs contain references to smbd version 4.11.5 started
The samba server version has changed.
This isn't referenced in the Hass.io Add-on config I don't believe, so I'm not sure where the version selection comes from. That is, it doesn't seem that the add-on is pinned to any particular samba-server version.
This might be a samba server version change that's causing a different compatibility issue, and it's not 9.1 of the add-on breaking it, but just the fact that the add-on was reinstalled as a result of the update and then picked up a newer dependency?

Yeah, samba-server 4.11 disables SMB1 by default now: https://www.samba.org/samba/history/samba-4.11.0.html
Something else has picked up that new version: not the code of the add-on v9.1 specifically, but maybe just the container being recreated or a HassOS update?
It seems that your challenge is now:

You're trying to use the insecure, outdated SMB1 protocol
The server component that the add-on uses now disables this version of SMB by default
The add-on does not expose a way to turn the insecure old protocol back on
That would be a new configuration flag that would have to be added

@tathamoddie Well done on your detective work....Guess we need a switch to be able to revert to SMB1 for the new Samba Addon to work as some of us old folk have NAS's that won't upgrade their firmware so the newer version of SMB isn't an option

I would think that people use the wrong credentials. "homeassistant" with here password. I think most is used the old "hassio" logging.

The samba version is pin to Alpine version. That was the move from 3.10 to 3.11

I'm fine to add a option to enable the old SMB1. But I currently focus to a new OS release, so I can't do that before next 2 weeks.

An SMB1-option would be lovely for us poor bastards stuck with Synology's archaic Samba/CIFS-mount implementation!

Yeah working on it already @olapettersson

Wow nice investigation work folks ! Thx :)
What's fun is that on my NAS i can use SMB 1 to 3 as server but only SMB 1 as client. QNAP you're doing it wrong...

authors: Lynnpaskett SNoof85 arripeo brinzlee frenck fudu gabeale olapettersson pvizeli tathamoddie

repo: home-assistant/hassio-addons


text:
implement request_location_update via push notifications

I was not able to test this yet, since it seems that I cannot send pull notifications from a development app? https://github.com/home-assistant/home-assistant-android#setup-development-environment

Fixed

All changes implemented.

@Mic92 Nice work! Looks like we can do like iOS and just send message: "request_location_update" for this?

After looking deeper, this is going to be affected by the same thing as https://github.com/home-assistant/home-assistant-android/issues/337.  I'll be making changes to fix both.

@JBassett did you ever do this fix?

Yes, this is working as expected.

authors: JBassett Mic92 mdrichardson

repo: home-assistant/home-assistant-android


text:
My log is full of this error multiple times a day

This message is owerflowing my log sometimes, does anyone know what it is related to?
I have done the basics thing. Restarted, rebooted, upgraded to 0.66.1 and so on.
regards
Richard
Error doing job: Exception in callback SendfileStreamWriter._sendfile_cb(<Future cancelled>, 53, 51, 26790, 55304, <_UnixSelecto...e debug=False>, True)

Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/events.py", line 126, in _run
    self._callback(*self._args)
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_fileresponse.py", line 36, in _sendfile_cb
    loop.remove_writer(out_fd)
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 351, in remove_writer
    self._ensure_fd_no_transport(fd)
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 258, in _ensure_fd_no_transport
    fd, transport))
RuntimeError: File descriptor 53 is used by transport <_SelectorSocketTransport fd=53 read=polling write=<polling, bufsize=0>>

I have the same problem. It seems to happen when a client goes into sleepmode, or disconnects without logging out.

+1
2018-04-26 15:53:34 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback SendfileStreamWriter._sendfile_cb(<Future cancelled>, 30, 29, 46138, 144388, <_UnixSelecto...e debug=False>, True)
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/events.py", line 127, in _run
    self._callback(*self._args)
  File "/srv/ha/lib/python3.6/site-packages/aiohttp/web_fileresponse.py", line 37, in _sendfile_cb
    loop.remove_writer(out_fd)
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 351, in remove_writer
    self._ensure_fd_no_transport(fd)
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 258, in _ensure_fd_no_transport
    fd, transport))
RuntimeError: File descriptor 30 is used by transport <_SelectorSocketTransport fd=30 read=polling write=<polling, bufsize=0>>

Same issue here:
raspberry Pi 3, Raspbian Stertch LITE Kernel 4.14.71-v7+
Home assistant 0.80.2. installed as official guide.
Moreover the HISTORY GRAPH doen't show the graph!

Duplicate as #12832

authors: Omdal VDRainer awarecan lumanga rich710se

repo: home-assistant/home-assistant