Added output at startup about address and port

I had to read the source code to figure out where the server was listening, and I thought this was a nice addition (and I've seen it done this way with quite a few server frameworks in the past).
Just a suggestion.

Looks good :star:
Thanks for submitting this


Need to Work on Prompts.

Need a better way to approach prompt windows for users.  They should not be able to enter anything.

Had to use while loops for each for would not working

Had to use while loops for each for would not working


histogram_quantile error result

prometheus 1.7.1
my query is:histogram_quantile(0.95, rate(http_server_requests_bucket{app="puhui-decision-server"}[30m]))
the result is:

it is obvious that "/prometheus" can not be 0.95
when i use 0.90  query :histogram_quantile(0.90, rate(http_server_requests_bucket{app="puhui-decision-server"}[30m]))

the result is 0.90 ,why is that the result is decided by φ-quantile? so weird

sorry ,little busy

Those are different queries for different jobs and instances, different results are to be expected.

they are not different jobs,job is all the same("all"),i can not find out why

can you show me how to use histogram_quantile correctly? it seems as if my query is wrong @brian-brazil


Add integration test for node draining and deactivation.

High-level description
This PR adds two minimal integration tests which verify that node draining and deactivation work correctly.
Corresponding DC/OS tickets (required)

DCOS-56345 DC/OS integration test for node draining

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot label Ready For Review


Return type error with useTweaks

When using the useTweaks hook, I'm getting an error about the return types. The return type looks to be an object with a single key that is an empty string?
const {
    numCirclesPerGroup,
    circleGap,
    innerCircleRadius,
    numGroups,
  } = useTweaks({
    numCirclesPerGroup: { value: 12, min: 1, max: 40, step: 1 },
    circleGap: { value: 2, min: 0, max: 100, step: 1 },
    innerCircleRadius: { value: 20, min: 1, max: 100, step: 1 },
    numGroups: { value: 6, min: 2, max: 90, step: 1 },
  })
// Property 'innerCircleRadius' does not exist on type '{ "": { numCirclesPerGroup: ....

See this sandbox https://codesandbox.io/s/jovial-lamport-8c4u3?file=/src/App.tsx

Pretty sure now that if you revert your project to react 16 this will go away.

Fixed in 0.3.2-alpha.0.


[WIP]<EMAIL_ADDRESS>

Hello @loosebazooka, @thesayyn, modules you maintain (rules_distroless) have been updated in this PR. Please review the changes.

This seems odd. Only the bcr app should be making these prs


Compatibility with BiomesOPlenty <IP_ADDRESS>

No Ores are generated by CustomOreGen   (Vanilla and Mods) when world type is BiomesOPlenty. Neither in new nor in vanilla biomes.

@reteo I think we should use the dimension property to decide on the dimension type. In 1.10, there is a formal notion of dimension type (Overworld, Nether, End by default) and that is now mapped to dimension since dimension-specific names have apparently gone away. In other words, use dimension="Nether" instead of dimension.generator.class="ChunkProviderHell".

Thank you. That helped!

At this point, I'm going to have to drop the configuration work.  I'm making configurations for a version of Minecraft that I don't play (not that I'm even playing Minecraft much anymore), which makes the whole project feel like an unpaid job, and I'm getting burned out.  Feel free to fork (or remake) the Sprocket toolkit for your own use if it helps; it's open to everyone's use and modification (GPL License).

Ok, thanks all of your contributions. I don't play Minecraft anymore either, so I understand your perspective.


Stanza check hangs when TLS is enabled

Same as https://github.com/canonical/postgresql-k8s-operator/issues/238
Steps to reproduce
Deploy multiple units and enable TLS, relate to s3
Expected behavior
Pgbackrest to initialise successfully
Actual behavior
Check stanza hangs, because TLS servers aren't started on secondary units.
Versions

Operating system:

Juju CLI:

Juju agent:

Charm revision:

LXD:
Log output

Juju debug log:

Additional context

Fixed in edge (rev. 326).


feat: Node.removeUIEvent [Fixes: #95873004]

@alexanderGugel @DnMllr @michaelobriena

@redwoodfavorite Looks good, just some small bits

Addressed your earlier comment.  Good catch.

OK @alexanderGugel I pushed that change thx for the review.

landed as fe2d1e6


NTR: somatodendritic dopamine secretion

I could do with some new GO terms to annotate the role of Synaptobrevins in PMID:21576241:
somatodendritic dopamine secretion ; GO:NEW
is_a: dopamine secretion ; GO:0014046
suggested intersection: dopamine secretion ; GO:0014046 that occurs_in: somatodendritic compartment ; GO:0036477
The regulated release of dopamine from the somatodendritic compartment (cell body or dendrites) of a neuron [GOC:bf, GOC:PARL, PMID: 21576241]
synonym: somatodendritic dopamine release [PMID: 21576241]
synonym: STD dopamine release [PMID: 21576241]
synonym: STD DA release [PMID: 21576241]
axonal dopamine secretion ; GO:NEW
is_a: dopamine secretion ; GO:0014046
suggested intersection: dopamine secretion ; GO:0014046 which occurs_in axon ; GO:0030424
The regulated release of dopamine from the axon of a neuron [[GOC:bf, GOC:PARL, PMID: 21576241]
synonym: axonal dopamine release [PMID: 21576241]
synonym: axonal DA release [PMID: 21576241]
I'll need to add 'regulation' terms in through TG for both.
Given that the end of the process ends with the protein being extracellular, would 'has_target_start_location/has_start_location' be better relations for the intersections?
Thanks!

Hi @dosumis - any comments on these?

I am "lurking" here, after Rebecca @rebeccafoulger leaves UCL

Hi @dosumis - any update on these?

GO_0099123

GO_0099124

Decided to stick with 'occurs in' as this is used for neurotransmission secretion terms.  This at least reflects the location of the secretory machinery.


Error: context deadline exceeded

I tried to install latest Helm (v2.4.1) on my fresh created GKE cluster (with k8s 1.5.7). and it give out error whenever I install any chart. Attached are the logging of my previous command execution.
~ gcloud container clusters get-credentials minidock --zone xxxxxx --project xxxxxx
Fetching cluster endpoint and auth data.
kubeconfig entry generated for minidock.
~ helm init
$HELM_HOME has been configured at /home/dick/.helm.

Tiller (the helm server side component) has been installed into your Kubernetes Cluster.
Happy Helming!
~ kubectl get po --namespace kube-system
NAME                                                            READY     STATUS    RESTARTS   AGE
fluentd-cloud-logging-gke-minidock-default-pool-9b0813ac-3zdz   1/1       Running   0          21m
heapster-v<IP_ADDRESS>-1244163626-jmtpv                              2/2       Running   0          21m
kube-dns-3475745875-ngw5q                                       4/4       Running   0          22m
kube-dns-autoscaler-2835134359-1z3hg                            1/1       Running   0          22m
kube-proxy-gke-minidock-default-pool-9b0813ac-3zdz              1/1       Running   0          22m
kubernetes-dashboard-3968242289-t3gpk                           1/1       Running   0          22m
l7-default-backend-2001230086-vt3n0                             1/1       Running   0          22m
tiller-deploy-3210876050-4p7sx                                  1/1       Running   0          20m
~ kubectl --namespace kube-system logs tiller-deploy-3210876050-4p7sx
Starting Tiller v2.4.1 (tls=false)
GRPC listening on :44134
Probes listening on :44135
Storage driver is ConfigMap
~ helm install --debug stable/wordpress
[debug] Created tunnel using local port: '34772'

[debug] SERVER: "localhost:34772"

[debug] Fetched stable/wordpress to wordpress-0.6.0.tgz

[debug] CHART PATH: /home/dick/wordpress-0.6.0.tgz

Error: context deadline exceeded

Could you get us the tiller logs for when this happened?

I'm also seeing exactly the same issue -
no logs at all from tiller, except the standard start up logs:
Starting Tiller v2.4.2 (tls=false)
GRPC listening on :44134
Probes listening on :44135
Storage driver is ConfigMap

I'm also seeing this with Tiller v2.4.2 with Helm v2.4.2. Let me know if there's any other info you need...

Full logs attached - note: I'm running 1.6.2 not 1.5.x here and getting the same issue. Issue also occurs with Tiller 2.4.2 with Helm 2.3.1.

bash-4.3# kubectl get no
NAME                                            STATUS    AGE       VERSION
gke-gs-staging-gke-default-pool-8a9f998e-ghwc   Ready     2d        v1.6.2
bash-4.3# kubectl get po -n kube-system
NAME                                                       READY     STATUS    RESTARTS   AGE
fluentd-gcp-v2.0-j2xff                                     1/1       Running   0          2d
heapster-v1.3.0-3440173064-bz5jr                           2/2       Running   0          2d
kube-dns-3263495268-0hn0m                                  3/3       Running   0          2d
kube-dns-autoscaler-2362253537-dv7d7                       1/1       Running   0          2d
kube-proxy-gke-gs-staging-gke-default-pool-8a9f998e-ghwc   1/1       Running   0          2d
kubernetes-dashboard-490794276-9ddww                       1/1       Running   0          2d
l7-default-backend-3574702981-dhj0x                        1/1       Running   0          2d
tiller-deploy-1651596238-v57zs                             1/1       Running   0          9m
bash-4.3# kubectl logs -n kube-system tiller-deploy-1651596238-v57zs
Starting Tiller v2.4.2 (tls=false)
GRPC listening on :44134
Probes listening on :44135
Storage driver is ConfigMap
bash-4.3# helm version --debug
[debug] Created tunnel using local port: '36495'
[debug] SERVER: "localhost:36495"
Client: &version.Version{SemVer:"v2.4.2", GitCommit:"82d8e9498d96535cc6787a6a9194a76161d29b4c", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller
bash-4.3# kubectl logs -n kube-system tiller-deploy-1651596238-v57zs
Starting Tiller v2.4.2 (tls=false)
GRPC listening on :44134
Probes listening on :44135
Storage driver is ConfigMap

I'm actually seeing this with all clusters, not just GKE.
I've also noticed Helm works fine from my OS X box to the same cluster. It seems to not work when in an alpine docker container. If I try the same process with a Debian container, it seems to work fine. The dockerfile in question that produces a Helm that doesn't work:
FROM alpine:3.5

RUN apk add --no-cache \
        openssl \
        curl \
        bash \
        python2 \
        make \
        graphviz \
        jq \
        ttf-ubuntu-font-family

# Install gcloud SDK
ENV GCLOUD_VERSION 153.0.0
ENV GCLOUD_HASH ade29e765f7847bf6081affb6eada69b45138d4abb443b1484e891312990e958
RUN cd /tmp && \
    curl -L https://dl.google.com/dl/cloudsdk/channels/rapid/downloads/google-cloud-sdk-${GCLOUD_VERSION}-linux-x86_64.tar.gz > /tmp/gcloud.tar.gz && \
    echo "${GCLOUD_HASH}  /tmp/gcloud.tar.gz" | sha256sum -c && \
    tar xvf /tmp/gcloud.tar.gz && \
    /tmp/google-cloud-sdk/install.sh && \
    rm -v /tmp/gcloud*

# Add gcloud binaries to PATH
ENV PATH /tmp/google-cloud-sdk/bin:$PATH

RUN gcloud components install -q kubectl

# Install terraform
ENV TERRAFORM_VERSION 0.9.4
ENV TERRAFORM_HASH cc1cffee3b82820b7f049bb290b841762ee920aef3cf4d95382cc7ea01135707
RUN cd /tmp && \
    curl -L https://releases.hashicorp.com/terraform/${TERRAFORM_VERSION}/terraform_${TERRAFORM_VERSION}_linux_amd64.zip > /tmp/terraform.zip && \
    echo "${TERRAFORM_HASH}  /tmp/terraform.zip" | sha256sum -c && \
    unzip /tmp/terraform.zip && \
    mv terraform /usr/local/bin && \
    rm -v /tmp/terraform*

# Install helm
ENV HELM_VERSION v2.4.1
RUN cd /tmp && \
    curl -L https://storage.googleapis.com/kubernetes-helm/helm-${HELM_VERSION}-linux-amd64.tar.gz > /tmp/helm.tar.gz && \
    tar xvf /tmp/helm.tar.gz && \
    mv linux-amd64/helm /usr/local/bin && \
    rm -rf /tmp/linux-amd64*

ENV HOME /root
# copy contents of the git
WORKDIR /terraform
ADD . /terraform

Can anyone else replicate this using the above image? The tiller server itself is not receiving any requests at all, however the local port does seem to be forwarded fine as I'm able to make a request using curl (to be presented with unreadable characters, presumably because curl isn't speaking gRPC).

@munnerz I am seeing a few related issues in Kubernetes that appears to be related to Docker, possibly due to the number of pods running.

In this case, one is a brand new 4 node GKE cluster (n1-standard-1) and
another single node bare metal cluster with about 40 pods (where tiller is
running).
Tiller itself isn't receive a request at all when helm is run in an alpine
container, but works fine on macOS and within a debian container.
Those issues appear unrelated except for the reference to "context deadline
exceeded", which is a common error message in Go coming from the context
package https://godoc.org/context#DeadlineExceeded
On Fri, 19 May 2017 at 00:16, Taylor Thomas<EMAIL_ADDRESS>wrote:

@munnerz https://github.com/munnerz I am seeing a few
https://github.com/kubernetes/kubernetes/issues/27388 related
https://github.com/kubernetes/kubernetes/issues/39028 issues
https://github.com/kubernetes/kubernetes/issues/42164 in Kubernetes
that appears to be related to Docker, possibly due to the number of pods
running.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/helm/issues/2409#issuecomment-302566717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbPwkjDrtZyEz8k4C_vIb8wSe12nXyks5r7NFbgaJpZM4NSp7R
.

Ok, I'll dig in to this bug next after I finish the one I am working on

@munnerz I tried this with a non-GKE k8s and didn't have a problem. I don't have a GKE cluster to test against right now though

Same error here on GKE:
[0] ~ >> helm version
Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
[0] ~ >> helm list thevotingapp
NAME        	REVISION	UPDATED                 	STATUS  	CHART             	NAMESPACE
thevotingapp	6       	Wed Jun 28 12:38:44 2017	DEPLOYED	thevotingapp-0.1.0	thevotingapp
[0] ~ >> helm get values thevotingapp
Error: context deadline exceeded

I'm seeing the same issue on Azure. helm list and helm get work just fine, but I hit the context deadline as soon as I try helm get manifest/values.
output:
><> helm list
NAME       	REVISION	UPDATED                 	STATUS  	CHART              	NAMESPACE
draft      	2       	Fri Jul  7 09:27:58 2017	FAILED  	draftd-canary      	kube-system
ingressctl 	1       	Thu Jul  6 15:16:48 2017	DEPLOYED	nginx-ingress-0.6.0	kube-system
><> helm get draft
REVISION: 2
RELEASED: Fri Jul  7 09:27:58 2017
CHART: draftd-canary
[...]
><> helm get manifest draft
Error: context deadline exceeded

No tiller logs were available after the call to helm get manifest, but helm list and helm get shows regular logs:
[storage] 2017/07/07 18:46:54 listing all releases with filter
[storage] 2017/07/07 18:47:07 getting last revision of "draft"
[storage] 2017/07/07 18:47:07 getting release history for "draft"

This is just on a 2-node cluster (one master, one node). I'll see if restarting the docker daemon on the node or just nuking the node from orbit will fix this issue.

I met this error in my cluster too, non-GKE.
This is my Environment:
Host:
   Linux node01 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux

docker Version:
Client:
Version:      1.13.1
API version:  1.26
Go version:   go1.7.5
Git commit:   092cba3
Built:        Wed Feb  8 06:50:14 2017
OS/Arch:      linux/amd64

Server:
Version:      1.13.1
API version:  1.26 (minimum version 1.12)
Go version:   go1.7.5
Git commit:   092cba3
Built:        Wed Feb  8 06:50:14 2017
OS/Arch:      linux/amd64
Experimental: false

Error:
root@node01:~# helm version --debug
[debug] SERVER: "localhost:44134"

Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

K8s Env:
root@node01:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.0", GitCommit:"58b7c16a52c03e4a849874602be42ee71afdcab1", GitTreeState:"clean", BuildDate:"2016-12-12T23:35:54Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:52:01Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

Same!
-> % helm get values excited-bison -a Error: context deadline exceeded

Encountering the same problems on AWS with a kops-1.6.2 install using RBACs
helm get works, can install charts, but get manifest doesn't work
$ helm version --debug
[debug] Created tunnel using local port: '1474'

[debug] SERVER: "localhost:1474"

Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.7", GitCommit:"095136c3078ccf887b9034b7ce598a0a1faff769", GitTreeState:"clean", BuildDate:"2017-07-05T16:40:42Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}

$ helm get manifest dunking-echidna
Error: context deadline exceeded

This issue was fixed in https://github.com/kubernetes/helm/pull/2664 and is being shipped in v2.5.1.

I'm still having this issue even when using the latest canary release, which also seems to have some argument parsing errors.
Here's my kubectl output
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.7+coreos.0", GitCommit:"c8c505ee26ac3ab4d1dff506c46bc5538bc66733", GitTreeState:"clean", BuildDate:"2017-07-06T17:38:33Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}

Helm output from latest canary release:
$ helm version --debug
unknown flag: --debug
Usage of homer:
      --home string   location of your Helm config. Overrides $HELM_HOME (default "$HOME/.helm")
Client: &version.Version{SemVer:"v2.5+unreleased", GitCommit:"1261f71faf1aa8b9a127a6e1759fd799a51d9528", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

Can you open a new issue for that, please?
You might also want to test https://github.com/kubernetes/helm/pull/2682. It sounds like this issue's already being fixed for v2.5.1.

this issue was fixed in v2.5.1. Closing!

I can confirm that this is an issue in helm 2.5.0
$ helm list --kube-context xyz.k8s.domain.net --host domain-helm-charts.s3-website-eu-west-1.amazonaws.com --all
Error: context deadline exceeded

Looks like we need to upgrade

I can reproduce this with 2.5.1 too :(

The issues I had above were caused by not having registered the node names in local DNS. The fix was to add --kubelet-preferred-address-types=InternalIP to the apiserver manifest.

I can confirm that this is a issue in helm 2.6.0
[root@k8s-master ~]# helm install -f config.yaml stable/redis --tiller-namespace default --host <IP_ADDRESS>:44134   --debug
[debug] SERVER: "<IP_ADDRESS>:44134"
[debug] Original chart version: ""
[debug] Fetched stable/redis to /root/.helm/cache/archive/redis-0.9.0.tgz
[debug] CHART PATH: /root/.helm/cache/archive/redis-0.9.0.tgz
Error: context deadline exceeded
k8s version is :
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:48:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:30:51Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Still an issue for me in 2.6.1 as well.

I'm also having this problem. I have a bare-metal three (1 master + 2 minions) nodes Kubernetes cluster up and running on Cent OS 7.
Kubernetes Version: v1.5.2
Kubernetes Config :

# kubectl config view
apiVersion: v1
clusters: []
contexts: []
current-context: ""
kind: Config
preferences: {}
users: []

Kubernetes Cluster Info :

# kubectl cluster-info
Kubernetes master is running at http://localhost:8080
KubeDNS is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kube-dns
kubernetes-dashboard is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard

I've just followed the Helm installation steps from the documentation. After downloading the "helm" binary to the system path I did : # helm init

Creating /root/.helm
Creating /root/.helm/repository
Creating /root/.helm/repository/cache
Creating /root/.helm/repository/local
Creating /root/.helm/plugins
Creating /root/.helm/starters
Creating /root/.helm/cache/archive
Creating /root/.helm/repository/repositories.yaml
$HELM_HOME has been configured at /root/.helm.
Happy Helming!

I can see Tiller pod is running : # kubectl get pods -o wide --all-namespaces
NAMESPACE     NAME                                    READY     STATUS    RESTARTS   AGE       IP            NODE
default       nginx-ingress-rc-s83kb                  1/1       Running   0          6d        <IP_ADDRESS>   minion03
kube-system   kube-dns-v20-z8lnd                      3/3       Running   0          21d       <IP_ADDRESS>   minion03
kube-system   kubernetes-dashboard-3543765157-tmmb8   1/1       Running   1          21d       <IP_ADDRESS>   minion02
kube-system   tiller-deploy-833363792-5v0gk           1/1       Running   0          10m       <IP_ADDRESS>   minion03

But, when I issue the version command : helm version --debug

Client: &version.Version{SemVer:"v2.6.1", GitCommit:"bbc1f71dc03afc5f00c6ac84b9308f8ecb4f39ac", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

^ Couldn't connect to helm server pod.

Hi All, I am facing this issue on v2.6.2 and I am running my local kubernetes using minikube.
Has anyone been able to resolve this error ?

+1

From looking at kubernetes' issue queue, one possible reason why this error comes up is due to a bug with the docker daemon running on the node hosting tiller.
It might be good to see the docker daemon logs from the host running tiller, if anyone has those available.

Is anyone experiencing this error after installing Helm with HomeBrew? I'm seeing success when installing directly with the "From Script" method in the wiki.

FYI @onlydole I made a comment above that might help give you more insight into the error.
I don't think the difference between the CLI installed with homebrew and with the install script method will matter too much but it's definitely an interesting data point since homebrew builds from source whereas the install script uses the pre-built binary CircleCI releases every tag.
If anyone is able to check and verify if homebrew vs. install script makes any difference, that would be helpful to know!

I get this error too. My configuration is below
K8s version: 1.7.7
helm version --host <IP_ADDRESS> --debug
[debug] SERVER: "<IP_ADDRESS>"
Client: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

@veeresh1982 can you check the tiller pod’s status using kubectl?

@veeresh1982 - If you installed via Homebrew, can you try deleting and installing directly like this? https://github.com/kubernetes/helm/blob/master/docs/install.md#from-script
Curious to see if that binary is the issue.

Ok I did below to resolve : I am going to try @philchristensen solution too and update.
PREP on all master nodes:
On all master nodes following link: https://github.com/kubernetes/helm/issues/1455, updated /etc/hosts
<IP_ADDRESS>   cbu-dev-k8s-node0
<IP_ADDRESS>   cbu-dev-k8s-node1
<IP_ADDRESS>   cbu-dev-k8s-node2
A) On each master nodes: try below
cbu-dev-k8s-master0 core # ./helm ls
NAME            REVISION        UPDATED                         STATUS          CHART                   NAMESPACE
knobby-donkey   1               Mon Nov 13 21:12:42 2017        DEPLOYED        hello-world-1.0.0       kube-system
cbu-dev-k8s-master1 core # ./helm ls
NAME            REVISION        UPDATED                         STATUS          CHART                   NAMESPACE
knobby-donkey   1               Mon Nov 13 21:12:42 2017        DEPLOYED        hello-world-1.0.0       kube-system
cbu-dev-k8s-master2 core # ./helm ls
NAME            REVISION        UPDATED                         STATUS          CHART                   NAMESPACE
knobby-donkey   1               Mon Nov 13 21:12:42 2017        DEPLOYED        hello-world-1.0.0       kube-system
B)From my another remote ubuntu machine:<IP_ADDRESS>
1)
Logged in as root:
export KUBECONFIG=/root/.kube/config
rm -rf /root/.helm
./helm init -c --debug
root@veeresh-spinnakerbuild:/home/ubuntu# helm ls --debug
[debug] Created tunnel using local port: '46624'
[debug] SERVER: "localhost:46624"
root@veeresh-spinnakerbuild:/home/ubuntu# helm version --debug
[debug] Created tunnel using local port: '44653'
[debug] SERVER: "localhost:44653"
Client: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}

Followed this link: https://hackernoon.com/the-missing-ci-cd-kubernetes-component-helm-package-manager-1fe002aac680
to install a sample hello-world app using helm.

cd /home/ubuntu/hello-world
helm install . --debug
root@veeresh-spinnakerbuild:/home/ubuntu/hello-world# helm list --debug
[debug] Created tunnel using local port: '35190'
[debug] SERVER: "localhost:35190"
NAME            REVISION        UPDATED                         STATUS          CHART                   NAMESPACE
knobby-donkey   1               Mon Nov 13 21:12:42 2017        DEPLOYED        hello-world-1.0.0       kube-system
3)Logged into cbu-dev master0 node
cbu-dev-k8s-master0 core # ./kubectl get po --all-namespaces
NAMESPACE     NAME                                                              READY     STATUS    RESTARTS   AGE
kube-system   fluentd-23hk7                                                     1/1       Running   0          4d
kube-system   fluentd-5t7rh                                                     1/1       Running   0          4d
kube-system   fluentd-jr22g                                                     1/1       Running   0          4d
kube-system   hello-world-2541921211-vfzxt                                      1/1       Running   0          1m

NAMESPACE     NAME                                                              READY     STATUS    RESTARTS   AG
kube-system   tiller-deploy-2318886584-1km4j                                    1/1       Running   0          41m

Tested @philchristensen solution. It works too and with this no need to update /etc/hosts file on the master side.

Just as another input to this: I was experiencing this issue intermittently when deploying. Whenever the context deadline error appeared, I could try again and usually by the second or third try it would work. We have a VPN directly into our cluster, so I tried adding the --host flag to helm upgrade and I haven't ever gotten the error since.

I was running into this issue as well running Helm from Ubuntu 16.04LTS outside of a bare-metal cluster.  I'm running Calico for networking and am exporting the svc cluster IPs so I can reach those directly.  I wasn't seeing any kind of network connection created at all.  Turns out, I had to add a port to HELM_HOST, e.g. export HELM_HOST=<IP_ADDRESS>:44134.
Now I'm up and running.
$ helm version
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}

This didn't work for me.
$ helm version --debug --host <IP_ADDRESS>
[debug] SERVER: "<IP_ADDRESS>"

Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
[debug] context deadline exceeded
Error: cannot connect to Tiller

This works:
$ helm version --debug --host <IP_ADDRESS>:44134
[debug] SERVER: "<IP_ADDRESS>:44134"

Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}

Still seeing the original issue with v2.8.2 running kubernetes in docker-for-mac edge.
$ helm version
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

$ helm get manifest curatrix-int-tests --debug
[debug] Created tunnel using local port: '54054'

[debug] SERVER: "<IP_ADDRESS>:54054"

Error: context deadline exceeded

Regular helm get, helm get values, and helm get hooks all work just fine.
Nothing exceptional in the tiller logs:
[main] 2018/03/17 15:52:02 Starting Tiller v2.8.2 (tls=false)
[main] 2018/03/17 15:52:02 GRPC listening on :44134
[main] 2018/03/17 15:52:02 Probes listening on :44135
[main] 2018/03/17 15:52:02 Storage driver is ConfigMap
[main] 2018/03/17 15:52:02 Max history per release is 0

Facing this with 2.8.2 as well.
root@ubuntu:/home# helm get manifest vigilant-tapir
Error: context deadline exceeded

root@ubuntu:/home# helm version
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

No related logs within tiller container.
cc @bacongobbler  Thanks!

Same issue here, with helm 2.8.2 both using a brew installation and "from script"

https://github.com/kubernetes/helm/pull/3715 is the fix for this. Could one of you please try that branch and see if it works for you? Thanks!

@bacongobbler awesome! The patch works for me!
root@ubuntu:/home/cloud/helmtmp# ./helm version
Client: &version.Version{SemVer:"v2.8+unreleased", GitCommit:"87c64e7987f348c0a99a4f6e12d6ec187723b7cc", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8+unreleased", GitCommit:"87c64e7987f348c0a99a4f6e12d6ec187723b7cc", GitTreeState:"clean"}

root@ubuntu:/home/cloud/helmtmp# ./helm install stable/linkerd
NAME:   existing-bison
LAST DEPLOYED: Tue Mar 20 11:15:34 2018
.......

root@ubuntu:/home/cloud/helmtmp# ./helm get manifest existing-bison

---
# Source: linkerd/templates/config.yaml
apiVersion: v1
kind: ConfigMap
metadata:
......

Reproduce:
/scripts/helm_mac get manifest cf.20180507.130920 --debug
[debug] Created tunnel using local port: '58010'

[debug] SERVER: "<IP_ADDRESS>:58010"

Error: context deadline exceeded
IBMMasterMBP:bcf-deployer bjxzi$ ./scripts/helm_mac version --debug
[debug] Created tunnel using local port: '58046'

[debug] SERVER: "<IP_ADDRESS>:58046"

Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Kubernetes: &version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.11-2+fa6873d3e386d7", GitCommit:"fa6873d3e386d7ead42923b24aea3b76e74395a3", GitTreeState:"clean", BuildDate:"2018-04-17T08:10:40Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

@rabbitfang Hi, I upgraded helm but got same error:
bjxzi$ ./scripts/helm_mac get  manifest cf.20180516.143139 --debug
[debug] Created tunnel using local port: '49509'

[debug] SERVER: "<IP_ADDRESS>:49509"

Error: context deadline exceeded
bjxzi$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Is it possible ./scripts/helm_mac is using a different client? You call both that script and helm directly in that example.

That makes sense then... As it's been mentioned a few times in this thread now, the Helm 2.8.2 client does not have this fix. You need to use the 2.9 client if you want to use helm get manifest. The fix was purely client-side.

@bacongobbler Sorry, I missed that get manifest command was using v2.8.2.


B 18737 int

B-18737
Summary
The primary goal of this ticket is to add move-level service items to a new section in the Office MTO page, accessible by TXO and SC roles. Here, they will be displayed as read-only.
Some time was taken to research the feasibility of including dollar amount prices to this page for just these items, but after some technical discovery it was decided that this change will be made as part of another future story which will affect all service items, not just those at the move level.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the customer app. Some existing test data will not have the move-level service items created, so we will create our own.
Create and submit a move.
Log in as a service counselor, approve the move.
Log in as a TOO, approve the move. Then, view the MTO Page for the move, and scroll down. You should see the Move Management fee approved in it's own section. See the below screenshot for an example.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against 88b991b6f2ab4f8b4439af663df74cdc9f1a5e8a


.Net BCL implementation through Proxies

I'd like to discuss wich option of implementation BCL classes through JSIL proxies will be best.
Right now I have small number of classes taken from Mono, that support all .Net formatting for numbers (they are implemented in external native code in .Net).
Right now I see only next option:

Create new project in JSIL solution - let it be JSIL.mscorlib.
Put all logic there.
Add JSIL translation as a compilation step for this project. Put translation output to Libraies\ folder
Include translation result loading in JSIL.js
Write proxies that will call translated classes.

@kg, what do you think about it? Do you have better options?

Probably we need introduce additional meta attribute, something like:
[assembly: JSInclude(typeof(System.Globalization.NumberFormatInfo)], that will include target type from some other assembly in translation of current assembly.
I really don't want implement a lot of really simple logic of NumberFormatInfo in JS files :)

It is impossible to reuse current proxies infrastructure for it fully - as JSIL don't translate types in ignored libraries/dependent libraries (with some configs) - and here we want be able translate types always to prepare minimal Bootstrap for JSIL.

Will describe on real example. Let's say that we need always have NumberFormatInfo in our bootstrap.
This type is easy enough to just translate it without any changes. In this case we would add to JSIL.mscorlib project next class:
[JSReuse(typeof(System.Globalization.NumberFormatInfo, JSMemberReusePolicy.ReuseAll))]
public static class NumberFormatInfoExternal {}

When JSIL will translate this assembly, it will include NumberFormatInfo instead of NumberFormatInfoExternal.
Later we could add something like
[JSReuse(typeof(System.Globalization.NumberFormatInfo, JSMemberReusePolicy.ReuseAll))]
public static class NumberFormatInfoExternal {

public static NumberFormatInfo ReadOnly(NumberFormatInfo nfi) {
  return false
  }
}

In this case, JSIL will translate NumberFormatInfo, but will replace ReadOnly(..) method.
So, it should really work very similar to JSProxy,  but it additionally include type from external assembly in current assembly.


24.1 plug-ins

Plugins are restricted to 24.1.4?
GOT REQUEST TO INSTALL
Currently running OPNsense 24.1 at Sun Mar 31 14:17:44 AWST 2024
Installation out of date. The update to opnsense-24.1.4 is required.
DONE

I haven't built 24.1.4 yet. The latest version I have built is 24.1. Therefore, currently, you can only get OPNsense 24.1 pkgs from my site.

ah yeah i see, i had the wrong url by accident, it is working now thanks


Stacks / Ways to break up your deployments?

Our current project is quite big and we break it up into multiple stacks.
I'm wondering if there are still ways to break up the deployment into multiple stacks, to isolate the surface area from anything that can go wrong.

Or if there are plans to support this in the future?

Do you mean Pulumi's stacks or do you just mean organizing resources separately? https://github.com/sst/ion/tree/dev/examples/aws-monorepo/infra

breaking up into stacks in v2 didn't really provide any benefits - they still all get deployed together and we only had to break things up for arbitrary cfn limits
breaking your code up makes sense for organization purposes and we have an example in aws-monorepo
is there any specific problem you're looking to solve?

The benefit would be that you can have multiple teams take responsibility for parts of the code base and deploy it independently without worrying that you will break some other part of the total project.

breaking up into stacks in v2 didn't really provide any benefits - they still all get deployed together and we only had to break things up for arbitrary cfn limits
breaking your code up makes sense for organization purposes and we have an example in aws-monorepo
is there any specific problem you're looking to solve

Ok, let me explain one of the downsides.
I work on the same project with a team.
For development, you sometimes need to deploy stuff to staging to debug/test your code.
When working in different stacks, one person can simply deploy their own stack without worrying that they will change anything in the rest of the project.
We also have a project where you can only deploy the whole project.
And we have to communicate constantly to not break anything someone else is working on.

ok so i have some ideas here that may help

we do support sst deploy <target> but it's pretty primitive right now. if we supported wildcards and stuff that might be usable to achieve what you want?
we could introduce an sst.Group("mygroup", () => { ..resources }) concept which would just prefix all the resources created inside, then deploying a single group is just deploying everything with that prefix

So, what you're saying is it would still be possible to deploy only a subset of the resources inside your project by prefixing it with a sst.Group ?
And if so, how does it resolve dependencies outside the group?

@jayair I mean real deployment isolation. Just like AWS stacks.

Yeah something like that.
We'll need to give it some thought on our side.

My current usecase involves a separate Backend and Frontend in a monorepo, both sharing a linked resource for a DynamoDB-based cache which they communciate over (Mainly so the frontend lambdas don't need to invoke the backend lambda for changed data).
Right now, each change causes both the backend and frontend to be rebuild and redeployed.
It would either help to have some filter functionality to only trigger rebuilds for certain parts of the stack, or to allow sharing resources across stacks.
Another usecase is directly conntected(not linked in SST terminolog) stacks, in this case I'd like to pass env urls to both backend and frontend (currently, this only works one-way only AFAIK), mainly to allow 1-Click-Deployments instead of manually needing to configure envs for both how they could reach each other.
For an initial deployment there's some chicken & egg kind of problem here which could be solved by reapplying e.g. env-vars which have outstanding dependencies like an url only known after deployment, but subsequent deployments should be able to rely on the pulumi state. For my specific usecase where the deployments are Sites, it would also help to make the creation of the Cloudfront Distribution more flexible so these could be created beforehand and urls would be known and could be passed to the functions. I guess for that to work properly the respective Stack components like e.g. Nextjs would need to export a function to create the Distribution with all the framework-specific config, and then the Stack should be able to accept these as optional input and skip creation.


fix enable_unicode_name_support need forward to master

Proposed changes
Session variable enable_unicode_name_support is used to enable using unicode for table/column names.
And it should be forward to master when executing create table stmt on non-master FE.
Otherwise, even if we set enable_unicode_name_support to true on non-master FE,
we can create table with unicode name.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Partial loading replaces whole Body instead of RenderBody() location

As title, would love ajax-loaded content to replace an appropriate location instead of the whole body.
Happens for component updates and Location calls.
This makes it impossible to have _Layout=null for ajax-calls to achieve faster rendering.
Solved in my fork, will make a PR.

Agree very much!
Expecting!

The only issue I see with current code is when you go back in history. In your changes I see:
window.addEventListener('popstate', async function () {
  await loadPageContent(window.location.href, findLocationTarget(), false);
});

function findLocationTarget() {
  let hydro = document.querySelector('#hydro-location');
  if (hydro) {
      return `#hydro-location`;
  }
  return `body`;
}

But if a user chooses another target in one of the requests, we won't know it, and by default refresh possibly wrong region. That's why the target selector can't be any selector, but it only can be either #hydro-location or body. I will include these changes in a new PR.

Actually I think the target selector should be specified by the target page:
@{
  if (HttpContext.IsHydro())
  {
    Layout = null;
    this.HydroTarget("#main");
  }
}

It makes sense, since the target page "knows" the best what element can be replaced in case of Hydro request.


Consider an exercise for working with excel speadsheets

I don't think I'll add this for the first cohort, but it may be something we come back to.

Would this be for a generic CSV or for a more spreadsheet specific format like OpenXML( .xlsx )?

I was thinking a generic CSV file.
On Tue, Jan 24, 2023, 10:31 a.m. Stephen Fowler @.***>
wrote:

Would this be for a generic CSV or for a more spreadsheet specific format
like OpenXML( .xlsx )?
—
Reply to this email directly, view it on GitHub
https://github.com/DockYard-Academy/curriculum/issues/709#issuecomment-1402404320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRQG7GMIAIWZRXHFGPNZK3WUANYPANCNFSM6AAAAAAUCWBVCY
.
You are receiving this because you were assigned.Message ID:
@.***>


Incorrect null handling in DownloadActionWrapper.execut

In the DownloadActionWrapper.execute method, the dest property is read and tested for being null. If the dest property is null, it will cause an NPE on line 18 where it is dereferenced to obtain the absolute path.

A followup observation is that the code would be simpler if you made the class a utility class (e.g. Download) with a single method (e.g. get, download). That way you do not need the setting and re-setting of dest. You only appear to use the class as a utility (i.e. new DownloadActionWrapper(...).execute()).

would be simpler if you made the class a utility class

it was a copy-paste from IntelliJ so the idea was not to change it to grab changes from there if needed.
And.. it hasn't been needed for couple years already :)
Thanks!


Dataset Viewer not showing Previews for Private Datasets

Dataset viewer issue for 'abidlabs/test-audio-13'
It seems that the dataset viewer does not show previews for private datasets, even for the user who's private dataset it is. See [1] for example. If I change the visibility to public, then it does show, but it would be useful to have the viewer even for private datasets.

Link:
[1] https://huggingface.co/datasets/abidlabs/test-audio-13
Am I the one who added this dataset?
Yes

Sure, it's on the roadmap.

Closing in favor of https://github.com/huggingface/datasets-server/issues/39.


Add new collector to expose Cluster creation time

It exposes cluster creation time only when the Creating condition is false, meaning that the cluster has already been created.

Tested on ghost, it works. Merging.


ARM64 VM does not boot because EFI NVRAM is not persisted

After installing the os the virtual machine reboots into the os menu and allows the use of operating system. Upon subsequent reboots you are dropped into a UEFI shell. And every time after the first reboot this happens.

I have tested an AARCH64 Kali Linux VM in UTM using the "UTM Logo EFI" from here and it exhibits a similar problem. After the VM is powered off after installation, and then powered back on later, it doesn't detect the installed grub boot loader, and sits at a screen asking if you want to enter the boot menu.

To get it to boot, I have to manually use the Boot Maintenance Manager to Boot From File: /No Volume Label/EFI/kali/grubaa64.efi.

Should be implemented in https://github.com/utmapp/UTM/commit/d5600010064e3e7f0faf06e5632d167c9dea7519


feat(stepper): add the ability to cancel step changes programmatically

Adds a new output event named beforeSelectionChange to be able to programmatically cancel a step selection, or implement any needed custom logic before the change is executed.
Expected Usage: Handle beforeSelectionChange output event, set preventStepChange to false and this will prevent the selectedIndex from being changed.
Closes https://github.com/angular/material2/issues/9733

What is the status of this feature?

Any new status on this functionality? Any workaround (e.g. able to cancel a step navigation if data is not saved or invalid).

status? more than one year...

In this angular version, it will available.

This style of API is not used in any of our other components. For API consistency, I don't think we want to make these changes. However, I'm leaving the associated issue open because we do need some solution for it.


v0.13

🤖 Generated by Copilot at 7926b37
Summary
🌎♿🗑

This pull request adds several features and improvements to the Homarr app, such as accessibility settings, location selection for widgets, config copying and deletion, and icon selection for dashboards. It also refactors some components to use custom React Query hooks and the api utility, and removes some unused files and code.

This pull request has many changes
To improve the app for all ranges
It adds location selection
And accessibility protection
And some hooks and icons for the pages

Walkthrough

Delete files related to code formatting and linting (F2,F5,F0,F1)

In my opinion it should still be 1.12.4. Whats your opinion @manuel-rw ?

I don't mind either version - maybe .12 is slightly better, as it corresponds with the roadmap. I think we should release soon , regardless what version it will be :)

@ajnart what is blocking this? Would be awesome if we could start working on the next step on the roadmap.

@ajnart what is blocking this? Would be awesome if we could start working on the next step on the roadmap.

It’s not I just need to write the release notes and I’ve been quite lazy. I was also looking to do some small fixes before that and add a new language. I think we can merge it today

Okay. Just note that I won't be able to help, as I'm in holydays.

@Meierschlumpf we usually merge the crowdin PR with the squash strategy to avoid so many commits aha. But it’s ok.

@Meierschlumpf we usually merge the crowdin PR with the squash strategy to avoid so many commits aha. But it’s ok.

Oh oops :joy:
I didn't know that


Don't add null dependencies non existing names

In case of optionnal dependencies, the param value can be null.
Thus, there is no name property and the following error is thrown :
Uncaught TypeError: Cannot read property 'name' of undefined

@Riron @sumitarora LGTM :shipit:


Add default jsdoc tag for ShadowMap size property

Thanks @fredj, the change looks good. Do we have a CLA from you? Just send one over so we can merge this.

Also once that is sent over feel free to add yourself to CONTRIBUTORS.md.

we (camptocamp) have a corporate CLA. I should be included, see https://github.com/AnalyticalGraphicsInc/cesium/pull/2932#issuecomment-130127548

Ah I see, thanks!


FSharp.Core can require minimum version of 4.7 instead of 4.7.1

FSharp.Core guidelines recommend setting lowest possible minimum version for libraries (https://fsharp.github.io/2015/04/18/fsharp-core-notes.html).
The lowest version of FSharp.Core that targets .NET Standard 2.0 is 4.7, so it would be great if Quibble referenced that version.

https://github.com/nrkno/json-quibble/commit/fbece753214b3d81e5df16e15c459d7881ebbcb3


make wzdx spec conform to geojson

Proposal
I'm working with road closures data @sharedstreets and want to expand on the suggestion in #21 to use GeoJSON for WZDx.  GeoJSON is based on JSON (making it very human-readable) and around it is a healthy open source ecosystem. GeoJSON is a geospatial data standard that data consumers are familiar with. GeoJSON can be easily translated into formats like CIFS (#25) as well.
The main idea here is that anything related to the work zone location can be a concern of the GeoJSON Feature's geometry field (a well-defined standard for geospatial data), and anything else (aka the WorkZoneActivity/the Common Core Data Dictionary) can be a concern of the GeoJSON Feature's properties field.
Example GeoJSON WZDx shape
For WZDx:

at the top level there will be a metadata object that contains the fields in File Header Information
each item in the features array will have a geometry type of LineString representing the location of the work zone
each item in the features array will have a properties value that will be contain WorkZoneActivity object—this will be an object with all the properties defined in the Common Core Data Dictionary

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "geometry": {
                "type": "LineString",
                "coordinates": [
                    [100.0, 0.0],
                    [101.0, 1.0],
                    [102.0, 2.0]
                ]
            },
            "properties": { WorkZoneActivity }
        }
    ],
    "metadata": { File Header Information }
}

In this pull request:
This pull requests modifies the spec to:

add a section on what GeoJSON is

add a section on how the WorkZoneActivity object relates to GeoJSON (each Feature has a properties object that will be a WorkZoneActivity object)

remove latitude/longitude from the BeginLocation and EndLocation DataFrames

[x] edit full-spec/full-spec.md

[x] add sample WZDx typescript classes w/ GeoJSON support

[ ] update data-tables/*.md

[ ] update sample-files/

[ ] update images/

This change is backwards-incompatible, so closing in favor of #40 that is backwards-compatible.

@indraneel why is there a requirement to make this backwards compatible? didn't think this spec was widely adopted yet, and that we are here to help shape this to be the most useful spec possible. I think GeoJSON would be the natural choice for simplicity and wide adoption.

@mikelmaron from the SharedStreets side we're fully in support of GeoJSON as the path forward as but had heard from WZDx team during previous working group meeting that there was a preference for PRs that were backwards compatible, hence adding #40 as an alternative.  Just to be clear our preference would be to stick with GeoJSON,  as that mirrors how we've handled this in our SharedStreets closures tooling.


[BUG] Typo in agent delete popup

Describe the bug
Delete Agent poup has some typos. It displays "Target" instead of "Agent". The same happens in multiple agents delete popup
To Reproduce
Steps to reproduce the behavior:

Go to Agent list
Click on Delete button, to delete an agent
It displays "target" instead of "agent"
The same happens in multiple agents delete popup

Expected behavior
Rename "target" word for "agent"
Screenshots

@YanetABUC  I think this is done


Removing myself from TSC

Signed-off-by: Olaf Flebbe<EMAIL_ADDRESS>

Sad to see you go @oflebbe -- until next time then!


fix: correctly show error response text

Description
JSON call can fail

Ah, this is actually a duplicate of #14, which is a bit more comprehensive. Maybe take a look at that?


In which case Location.route can be null?

In which case Location.route can be null?
https://github.com/vaadin/vaadin-router/blob/47e5a2633395fea191982c80052006ae1623761f/interfaces.d.ts#L108
Thanks in advance!

This is the case when a router instance is created, but no navigation has happened yet:
const router = new Router(document.querySelector("#outlet"));
console.log(`router.location.route = ${router.location.route}`);
// outputs 'router.location.route = null'

Thanks @vlukashov!


Help and documentation

Create a proper help system, write a proper manual for users/lexicographers.

Iztok is writing something up. I will then find a good way to include that in Lexonomy.

This should be now combined with the curriculum material preparation for WP5.


Add favicon and title in HTML template

Corrected the icon and title in html

This configuration does not work, because when running examples, vite searches for favicon in the public folder relative to the root directory (for example, 01_example...). It is necessary to change the configuration.


hackEarlySend is incompatible with Cardboard

Enabling hackEarlySend - because I am using LuckPerms - causes all players to connect as "offline" players.
(When hackEarlySend is set to false (only possible without LuckPerms) everyone is in normal online mode as usual, this is why I think that enabling hackEarlySend is the cause.)
Am I overseeing something here, or is this a bug?
The config:
hackOnlineMode = true
hackEarlySend = true
secret = "secret"

Update: This mod seems to be incompatible with Cardboard.

For a fix, you might have a look at these Mixins from Cardboard:
ServerLoginNetworkHandler (the class where the mixin for hackEarlySend is applied):
https://github.com/CardboardPowered/cardboard/blob/master/src/main/java/org/cardboardpowered/mixin/network/MixinServerLoginNetworkHandler.java
and possibly any of these other network mixins is related aswell:
https://github.com/CardboardPowered/cardboard/tree/master/src/main/java/org/cardboardpowered/mixin/network

Even more specific: I think this mixin causes the issue.
Is it possible to fix this incompatibility?

Even more specific: I think this mixin causes the issue.
Is it possible to fix this incompatibility? (Or is this maybe an issue which has to be fixed by Cardboard?)

Yes it need fixed by Cardboard, it skip FabricProxy auth progress.
I think this mixin is not necessary, maybe Cardboard can add config to allow disable it.

cardboard issue:
https://github.com/CardboardPowered/cardboard/issues/209

Mh just a guess: Couldn't you remove this cancel call, and then I will create a PR to Cardboard to execute cardboards logic AFTER the logic of FabricProxy-Lite (only possible if FabricProxy-Lite does not cancel immediately)?


Add workaround for action mishandling of draft: true -> false transition

This works around softprops/action-gh-release not being able to properly "publish" a release by changing draft: true to draft: false.
The intention is that the step with draft: false would find the existing draft release and update it, but, previously, the action would fail to find the existing draft release and instead create a duplicate one. The old behaviour is visible (to people who can see draft releases) with v0.12.3-beta.0 and -beta.1:

The particular new version of the action is:

changes: https://github.com/softprops/action-gh-release/compare/master...huonw:action-gh-release:huonw/pantsbuild-fix-see-scie-pants-439 (specifically commit https://github.com/huonw/action-gh-release/commit/55ec297e11bf84ff0f5893a84ea987d93489920c from branch https://github.com/huonw/action-gh-release/commits/huonw/pantsbuild-fix-see-scie-pants-439 )
this is just the latest code (v2.2.0) with https://github.com/softprops/action-gh-release/pull/316 merged in

Ah, gonna do this with a branch in this repo, to be able test from the branch.


Apply client proxy in online upgrade

This PR applied client proxy in online upgrade. The session transfer should be done through client proxy if proxy annotation is enabled, and all types of Vertica clients can utilize session transfer.
TODO: wait for #980 to be merged and add e2e tests.

@qindotguan You need to update the operator in realdb using this branch for the demo. This branch can perform online upgrade successfully.
The commit 65d9a42 is a temporary solution for removing old proxy pods after online upgrade is done. You should remove that commit and use Hao's changes in #980 when #980 is merged.
You should add a test suite for proxy online upgrade, and update the tests in e2e-leg-11/client-proxy suite(we need to verify config file is updated when we add/remove nodes from a subcluster).
@roypaulin should know the context and you can ask him for help.

@qindotguan you can work on this once #980 is merged.

@qindotguan Before you rebase on main, you should revert the commit "temporary fix for removing old proxy pod 65d9a42"


[Identity] Upgrade to core-tracing 1.0

Relative to #21204

API change check for @azure/identity
API changes are not detected in this pull request for @azure/identity

After a couple of weird git-history turns, it is back to something reasonable 🙂

API change check for @azure/identity-cache-persistence
API changes are not detected in this pull request for @azure/identity-cache-persistence

API change check for @azure/identity-vscode
API changes are not detected in this pull request for @azure/identity-vscode


Update README.md test for CLA Assistant

Test opening a PR as an org member to ensure we aren't prompted for the CLA Assistant

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


AB#5016

Proposed changes

Related issues

Checklist

[x] I consider the submitted work as finished
[x] I tested the code for its functionality
[ ] I wrote test cases for the relevant uses case
[ ] I added/update the relevant documentation (either on github or on notion)
[ ] Where necessary I refactored code to improve the overall quality

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

This has been tested with the local build and appears to be working as designed, @DallasP9124 @r-joyce please review and merge.


Avoid force-unwrapping

The bindings currently use force unwraps (! / !!) in various places. If they fail they crash the app. Ideally we'd convert failures into promise rejections or NOOPs with error logs.

This is obsolete now that we're using uniffi-bindgen-react-native.


'The "Print Spooler" service was removed from the OS'

Prerequisites

[ ] Verify that this is not a Windows issue;
[X] Refer to the System requirements;
[X] I do not use a homebrew Windows image;
[ ] I did not tweak Windows before that could cause system instability;
[X] Attach a created log. You may find it in the Logs folder.

Steps To Reproduce

Have already messed around with Windows to try to improve performance (One of the things I did was disable Print Spooler since I don't have a printer and have no need of any printing-based functionality)
Open SophiApp
Error

Expected behavior
It doesn't give an error because the service is only used for printing as far as I know.
Actual behaviour
It gives an error and I can't click on anything.
Windows Version
Windows 11 Home 21H2 Build 22000.739
SophiApp version
<IP_ADDRESS>
SophiApp release type
SophiApp
Logs
Windows 11 Home 21H2 build 22000.739
Computer name: MICHAELWIN11PC
User: micha
User domain: MICHAELWIN11PC
User culture: English (United States)
User region: United States
App version: <IP_ADDRESS>
App is release: True
App folder: "C:\Users\micha\Downloads\SophiApp"
App localization: EN
App theme: DARK
Antivirus: Malwarebytes
05.07.2022 20:33:12 Debug mode is: False
05.07.2022 20:33:12 Active view is: Loading
05.07.2022 20:33:12 Advanced settings is visible: False
05.07.2022 20:33:12 The "UWP for all users" switch state is: UNCHECKED
05.07.2022 20:33:12 The OS conditions checkings started
05.07.2022 20:33:12 OsVersionCondition run result: True
05.07.2022 20:33:12 The next condition to be run: OsBuildVersionCondition
05.07.2022 20:33:12 OsBuildVersionCondition run result: True
05.07.2022 20:33:12 The next condition to be run: OsFilesNotCorruptedCondition
05.07.2022 20:33:12 OsFilesNotCorruptedCondition run result: True
05.07.2022 20:33:12 The next condition to be run: RebootRequiredCondition
05.07.2022 20:33:12 RebootRequiredCondition run result: True
05.07.2022 20:33:12 The next condition to be run: SingleInstanceCondition
05.07.2022 20:33:12 SingleInstanceCondition run result: True
05.07.2022 20:33:12 The next condition to be run: SingleAdminSessionCondition
05.07.2022 20:33:12 SingleAdminSessionCondition run result: True
05.07.2022 20:33:12 The next condition to be run: Win10TweakerCondition
05.07.2022 20:33:12 Win10TweakerCondition run result: True
05.07.2022 20:33:12 The next condition to be run: SycnexScriptCondition
05.07.2022 20:33:12 SycnexScriptCondition run result: True
05.07.2022 20:33:12 The next condition to be run: DefenderWarningCondition
05.07.2022 20:33:12 DefenderWarningCondition run result: True
05.07.2022 20:33:12 The next condition to be run: DefenderNotCorruptedCondition
05.07.2022 20:33:13 DefenderNotCorruptedCondition run result: True
05.07.2022 20:33:13 The next condition to be run: SpoolerNotCorruptedCondition
05.07.2022 20:33:13 SpoolerNotCorruptedCondition run result: False
05.07.2022 20:33:13 The next condition to be run: NewVersionCondition
05.07.2022 20:33:13 Active view is: SpoolerCorrupted
05.07.2022 20:33:13 It took 1 second(s) to check the OS conditions

Hi! Actually, this is not an issue. This is by design. And it won't be fixed neither for you, nor for anyone.
Your problem is that all of you think that removing any service (not disabling it or setting a manual type of start) may result in speeding up OS. This is a myth! you cannot speed it up at all. All you do is making harm to the OS. But I may compile a special version for you with this checking disabled.


Release

Hey, it would be nice to have a release off your fork, for the not that tech savy people.

Yeah, you're right! I'll look into it!


Added uri construction for queryParameters

This PR intends to help avoid replicating code when using the beamer package and URI's with query parameters. While refactoring my code I came across multiple navigation calls where I could avoid manually constructing the URI if the beamer package accepted query parameters as an input.
I've made the following changes:

added Map<String, dynamic>? queryParameters as an optional input parameter for: beamToNamed, beamToReplacementNamed and popToNamed
added the private function String constructUri(String uri, Map<String, dynamic>? queryParameters) that return the URI with the formatted query parameters appended at the end.
added unit tests for the new function.

@slovnicki feel free to request any additional changes to my code or discard the pull request if you don't consider the changes relevant/useful.

@Lorenzohidalgo Thanks for the PR! :blue_heart:
This is definitely a useful feature, but now that I think of it... Maybe we should switch to Uri altogether instead of String for named beaming :thinking: Sure, this will be a breaking change, but this is expected for the v2 we're working on. Let me know what you think about that. The only thing that concerns me is that it is a significant breaking change and a bit of a hassle for apps that really use only path. I wish we could take the best of both worlds without over-complicating the API.
We should also update all the functions in BeamerDelegate to make use of this new feature, be it your constructUri helper or complete switch to Uri. And if we stay with the constructUri option, maybe a better place for it would be utils.dart.

Hi @slovnicki, Thanks for your feedback! I also agree that maybe switching to Uri altogether would resolve the issue, but as you mentioned it would be a breaking change and more complex/cumbersome for users with more straightforward implementations. To avoid creating a breaking change or making it more complicated for other users I went with the constructUri approach.
Either way, I would be happy to help with implementing this further. Just let me know If I should make the complete change to Uri or just continue updating the functions to use constructUri as mentioned in your last paragraph.

@Lorenzohidalgo Yeah, it might be best if we don't do the full transition to Uri yet. Let's complete your constructUri proposal and maybe we can discuss the transition to Uri after, in some other PR.

Perfect @slovnicki , I'll implement the requested changes and let you know once it's ready for the next review 😉

Hey there @slovnicki ,
I've finally had a moment to fix the requested changes:

We should also update all the functions in BeamerDelegate to make use of this new feature, be it your constructUri helper or complete switch to Uri. And if we stay with the constructUri option, maybe a better place for it would be utils.dart.

Let me know if anything else should be updated 😉


Add support for HANA connector.

@johannesroesch Does this PR contain functionality that isn't already available in the Spring Cloud SAP HANA extension project?
In general, it's preferred that support for new clouds, service types, etc is done in separate extension projects like those listed at the bottom of the project site instead of adding to the core project.


Syntax error when line starts with commas

Hello, firstly I'd like to thank you for writing this extension!
Anyways, my small problem is as follows. The CryptoZombies tutorial includes a line which interacts the CryptoKitties getKitty function. Because we only want the last variable, the rest are left empty and we just have commas.
(,,,,,,,,, kittyDna) = kittyContract.getKitty(_kittyId);
Now, as far as I can tell this is perfectly valid Solidity code and I can even compile it with the vscode-solidity extension. However, I'm getting a rather irritating error message from the linter

Syntax error: Expected "!", "!=", "(", "+", "++", "-", "--", "0", "<", "<=", "==", ">", ">=", "[", "^", "delete", "false", "hex", "mapping", "new", "this", "true", "v", "~", [1-9], comment, end of line, identifier, number, string, or whitespace but "," found.

I could just ignore this when I was on vscode 1.19, but as of 1.20 the error is very prominent, so I'd like to find a solution.

My apologies, I've been reading up and figured out that this really isn't the fault of the Solidity extension – it's an issue with the linter. Changing the linter to solhint and playing with the setting has solved my problems.


CLOUDP-244156: enable race detector in ginkgo tests

All Submissions:

[ ] Have you signed our CLA?
[ ] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if there is one).
[ ] Update docs/release-notes/release-notes.md if your changes should be included in the release notes for the next release.

e2e fails with data race warnings. We have more fixes to do. Adding those on top of this PR.


Gas estimation failed

Hi! Everything works fine in mainnet-fork, but when I try to execute in Kovan I get this error:
You have 0.102528088850729021 worth of ETH deposited
You have 9.876093905E-9 worth of ETH already borrowed
You have 0.082022461204489312 ETH available to borrow
Lets borrow some DAI!
El precio DAI/ETH es 0.000956734067650536
Puedo pedir prestado hasta 81.44513797404251 DAI
Borrowing DAI!
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie_cli\run.py", line 49, in main
return_value, frame = run(
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\project\scripts.py", line 103, in run
return_value = f_locals[method_name](*args, **kwargs)
File ".\scripts\aave_borrow.py", line 48, in main
tx2 = lending_pool.borrow(
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\network\contract.py", line 1693, in call
return self.transact(*args)
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\network\contract.py", line 1566, in transact
return tx["from"].transfer(
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\network\account.py", line 642, in transfer
receipt, exc = self._make_transaction(
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\network\account.py", line 725, in _make_transaction
raise VirtualMachineError(e) from None
File "C:\Users\teres\AppData\Roaming\Python\Python310\site-packages\brownie\exceptions.py", line 121, in init
raise ValueError(str(exc)) from None
ValueError: Gas estimation failed: 'The execution failed due to an exception.'. This transaction will likely revert. If you wish to broadcast, you must set the gas limit manually.
Any suggestion? Thanks

The kovan addresses have changed a lot... It's likely due to a new address. Maybe we should update the repo to stick to mainnet-forks and not testnets?
What do you think?


fix: corner-radius-1000 type should be borderRadius

Description
corner-radius-1000 was introduced with type "number" instead of type "borderRadius", which other corner-radius tokens use.
Motivation and context
Consistency and accuracy.
Related issue

Types of changes

[ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
[ ] Minor (add a new token, changing a value; non-breaking change which adds functionality)
[ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
SPECTRUM SYNC SUMMARY
CHANGED SCHEMAS: (1) corner-radius-1000

TEST COMPLETE


Modify DictionaryMatcher's logic with incoming dataReader chagnes

Modify dictionaryMatcher's logic to be consistent with the new dataReader design. Similar changes are made to Regex( #197 ), Keyword( #193 ), and Fuzzy( #194 ).

LGTM.


Fixed issue #30

Fixed according to Issue #30, I also renamed arg to id, to make it more similar to the one used in mongo-db, a slight performance impact might be noted as the ID doesnt return in certain cases.
Bounty URL: https://www.huntr.dev/app/bounties/open/1-npm-bson-objectid
Implemented the fix described in Issue #30
PoF
All tests pass

Sorry @benkyd, we enjoyed reviewing your fix but it has not been selected this time. If this bounty has not been closed, please feel free to try again with a new pull request!
We appreciate your effort and look forward to reviewing more of your fixes in the future! 🔨😎


How to avoid updating a field, but keep creating it. (filter field in PUT / POST operation)

It's a real question and maybe the "Hydra vocab" is the reason that block this feature.
My problem is simple :
I want create a resource with two fields, but one of this two field cannot be updatable. (authorize two field on POST but one field on PUT operation).
Actually Normalization/Denormalization is shared between operation because the vocabulary is shared between operations and a property is only : read or write (not read, write-in-creation, write-in-update)
So, how to deal with this problem ?
Maybe ask this question on Hydra ML ?

Here is a thread speaking about that: https://lists.w3.org/Archives/Public/public-hydra/2015Jun/0018.html
You can still do what you want with a custom normalizer or a custom controller.


Add support for puzzle notes

This change checks if the puzzle contains any solving notes, and adds them to the output's 'notes' field.
Solving notes are not uncommon in themed puzzles. Example:
nyt.py Chrome https://www.nytimes.com/crosswords/game/daily/2008/09/11 Sep1108.puz
Note about notes: When the NYT was publishing in .puz format, they would often put notes into the puzzle title. For example here is their own published version of the above Sep 11, 2008 puzzle. (In the JSON version this actually contains two notes; in the published .puz file one ended up in the title and the other in the notes field.) I'm guessing they did this for compatibility in case software ignored the notes field. However the solvers I've tested (macOS Black Ink and downforacross.com) both handle notes properly so I'm disinclined to put them in the title.

So I wanted to take a quick moment to mention a big thanks to @jkboyce and @edsantiago .  This marks the end of the items I wanted to get to in my personal todo list, which you two have managed to intuit.
I'm going to call this v1, and opened a couple of bugs for bigger items I have left on my list as bugs for anyone to tackle, or for me to get to one day.
Of course, feel free to keep adding whatever features you come up with!


哪里可以找到离线安装的文档？

/invite

CloudImage is already offline, just sealer save xxx, and load it in your offline cluster.

thank


Instance: Murat's demo to Evolution

Cloud Computing Instance Flavor
g3.xl - GPU instance (32 CPUs, 125 GB RAM and A100 GPU)
Description
I would like to use 3D Slicer on the cloud to process large datasets from MorphoSource for my dissertation.
ORCID
0000-0002-7921-9018
Email
<EMAIL_ADDRESS>

/email


Refactor chain-specific database location code

Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes #1580
Other information and links

Code looks good. Could you add a summary of the changes to the PR?


Best practice with multi page PDF?

Process each page or merge pages into one large image and process the large image?

I've made a solution that works. Loop each image and then have a pageOffset that increase every page.
pageOffset = index * images[i].Height;  //Works


TextBox Attribute Trim=true or TextBoxHelper.Trim=true

What steps will reproduce this issue?
TextBox has the Trim = true attribute, the Trim = true attribute would implement the Changed event by doing a TrimStart () and would implement LostFocus that would do the Trim
or helper TextoBoxHelper.Trim=true
Expected outcome
The text would have no spaces at the beginning or end
Code example
trimtextbox.txt

@punker76 @robertorp I like the idea, perhaps something along the lines of TextBoxHelper.Trimming with options for TrimBeginning, TrimEnd, or None?  I know that @thoemmi has concerns with the TextBox style becoming too bloated - any thoughts?

I think IMO this should not be added to MahApps. I know MahApps has a lot of other attached properties, but this functionality has nothing to do with the styling itself...
/cc @thoemmi

@amkuchta caught me 😉 I agree with @punker76, it's out of MahApps.Metro's scope.
(BTW, I would make it a behaviour, not an attached dependency property)


Map coordinates not working properly when placing a point depending on which way you move the map

I noticed that when I place a point in Cambodia going from left to right in the map as opposed to going from right to left, it results in different coordinates (for the same point). The longitude when you toggle to Cambodia from right to left and place a point is negative 200 something (supposed to be 160 something). Not sure if this is a bug or just a limitation of the map ui.

What is happening is that ipyleaflet creates a new map view when the map is panned out of the world bounds, it would be easily corrected using the worlCopyJump attribute to the map.


Score outline

As with the others - fit this into the scoring prompt.
Story Outline: An ideal outline:

Is well-organized, with clear beginning, middle, and end
Follows a logical progression, free of plot holes, non sequitors, or unfulfilled promises
Is concise and precisely targeted, free of extraneous events or characters
Maintains an engaging pace without rushing or dragging in spots
Has a clear and compelling central conflict that creates tension
Resolves its central conflict in a satisfying and logical manner

Scoring prompt:
Critique this story's outline based on this rubric describing an ideal outline:

- Conflict and tension: Has a clear and compelling central conflict that creates tension
- Resolution: Resolves its central conflict in a satisfying and logical manner that does not feel abrupt or unjustified
- Editing: Is ruthlessly edited and engagingly paced; every event is critical to the story
- Narrative consistency: Follows a logical progression, with no plot holes, non sequitors, or unfulfilled promises
- Character-driven: Drives plot by the actions decisions of characters, not external events or coincidences

Follow the list structure of the rubric. For each item, discuss how well the outline does, identify specific ways the outline falls short of the ideal, and finally score that item out of 5. Be as harsh as possible!

End your review with "Overall Score: <sum of item scores>/<best possible score>".

Recommendation generation prompt:
Excellent feedback, thank you! Based on your feedback, give three concrete recommendations for how to improve the outline. Each recommendation should solve a problem highlighted above and specify every detail on what should be changed and how. Multiple recommendations can target one problem.

Remember that eliminating or combining redundant events, refocusing on the central conflict, and simplifying concepts for the target audience are often important too, not only adding more things. Don't be afraid to recommend big changes. Finally, remember that this is just an outline, so focus on the core elements of the plot, NOT language and NOT imagery.

Give your recommendations in a numbered list format. Omit preface, omit a summary, and omit other notes; include only the list itself.


Implement new NATS message for edit functionality

Story
As a developer, I would like the new "edit" message to be sent as needed
Description
The NATS message redesigned as part of this ticket (see dependencies) will require either two separate message or one message with a type to indicate if it's for an "edit" or "new project set". This story is to implement the message sent when "edit".
Done When
A properly formated message is sent to NATS when a project "edit" is being requested.

If we want to include audit we can include the ID in the NATS message and it will get recorded in the PR.

**released on the registry-web-platform-registry-prod silver cluster: Dec 03, 2020


docs: add new but forgetten Linux dep: libvirt-dev

This is required for the
 libvirt-python = {version = "^7.10.0", platform = 'linux'}

line on the toml file.

 Will wait until it settles upstream

Can we get the doc change merged firstly?

The doc is updated in another PR.


route: use reference wrapper for get all filter config

Commit Message: route: use reference wrapper for get all filter config
Additional Description:
@alyssawilk I think we have a information gap at #36028. The pointer is better for the perFilterConfigs() because we always need to do a dynamic_cast. pointer is simpler and won't result in potential exception throwing.
But the Utility::getAllPerFilterConfigs() could use the reference wrapper because it take a template parameter and will return the typed configs.
Risk Level: low.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.

/retest

cc @alyssawilk I will defer this to you to merge in case you have other questions. :)


Poetry problems

Any attempt at using poetry add, causes a The lock file is not compatible with the current version of Poetry error when building docker.
I'm using poetry 1.4.0

I didn't edit pyproject.toml manually, I used poetry add, but since my poetry is 1.4.0 and container's is 1.1, it's probably incompatible.
I fixed it by adding RUN pipx upgrade poetry to backend docker file, right before it executes poetry install
By the way, deleting lock file doesn't fix the problem. If it stays deleted, then docker complains about not finding dependencies for pytest-cov and if I regenerate the lock, I end up where I started.

I didn't edit pyproject.toml manually, I used poetry add, but since my poetry is 1.4.0 and container's is 1.1, it's probably incompatible.
I fixed it by adding RUN pipx upgrade poetry to backend docker file, right before it executes poetry install
By the way, deleting lock file doesn't fix the problem. If it stays deleted, then docker complains about not finding dependencies for pytest-cov and if I regenerate the lock, I end up where I started.

Yeah, if you delete the lock file you need to re-run poetry install to regenerate it. The version mismatch may have caused your problems, though.

Just to add a reference to this issue for future search: https://inboard.bws.bio/docker#docker-and-poetry

Inboard now uses Hatch for Python dependency management and packaging. Poetry 1.1 was used before Hatch, and Poetry 1.1 is still included in the Docker images for backwards compatibility. If you have a downstream project using the inboard Docker images with a newer version of Poetry, you can add RUN pipx upgrade poetry or RUN pipx install poetry>1.2 --force to your Dockerfile to upgrade Poetry for your project.


Multi-GPU support

New Text Classification can efficiently use GPU, almost 100% according to task manager. Need for CPU is also quite high, so it probably would be the next bottleneck, but multi-gpu support would be nice to lower temperatures and at least some speed up.

@luisquintanilla Is this an ask for the framework?

@beccamc It does sound to me like a framework ask. I know that currently you are able to set which GPU you want to use but I believe you're limited to only one. In any case, let's transfer to the dotnet/machinelearning repo.

@beccamc On the Model Builder front though, I could see an "Advanced environment" option similar to data / training where we could let users choose which GPU to use in case they have multiple.

@luisquintanilla  ATM I am unable to select which card I want to use. Not really important for me, just FYI. In task manager I can see both. Only difference in views is PCI channel is different 11 vs 12.
Nvidia Game-Ready Driver 526.86, Windows 11

In GPU-Z the only difference is BIOS version (I wonder why) and Device ID

No errors in Device manager

That is about as much I know where to look for more info.

Since we have some Model Builder context in this issue I've copied the information into a new issue in ML.NET repo. This can now be used to track selection of GPU from Model Builder.


Remove core-data test #27 issue #187

#187
Signed-off-by: Trevor Conn<EMAIL_ADDRESS>

https://github.com/edgexfoundry/edgex-go/pull/1209 has been merged. This test will now fail until it is removed.


update docs to explain proxy configuration

@chuckbutler @mbruzek @Cynerva
#39 #61 #63

I approve of this message 👍

Words, you have the best words! +1


retriable: Nonce provider

Coverage increased (+0.07%) to 87.078% when pulling 2bba92c967ab66ee0a35139410eec39403e91d6f on dissoupov into d5e2aaf018bd8a2c48c69cdc49cfb634fc6b7134 on main.


iOS Arguments on Launch not working

Steps to Reproduce
Add some Arguments on Launch to your Schema in iOS for example -FIRAnalyticsDebugEnabled
Run your application trough flutter run or Android Studio.
This is not working at all.
To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled
If I run the project directly from Xcode it works.
Logs
To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled
Flutter Doctor
[✓] Flutter (Channel beta, v0.3.1, on Mac OS X 10.13.4 17E199, locale en-DE)
    • Flutter version 0.3.1 at /Users/eikebartels/Applications/flutter
    • Framework revision 12bbaba9ae (7 days ago), 2018-04-19 23:36:15 -0700
    • Engine revision 09d05a3891
    • Dart version 2.0.0-dev.48.0.flutter-fe606f890b

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/eikebartels/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.3, Build version 9E145
    • ios-deploy 1.9.2
    • CocoaPods version 1.4.0

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 24.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

Sorry for the late response.
Is this still an issue with recent Flutter versions?

Yes it is

Where do you add these parameters (I haven't done much iOS stuff yet).

Is there any workaround for now?

The workaround I used is to run the app from XCode.

One place where users might need it is the Firebase Analytics event debugging.  (see iOS steps)

Another place it would be helpful is for dynamic links diagnostics:
https://firebase.google.com/docs/dynamic-links/debug#ios_self-diagnostic_tool
It should be possible to call using a platform channel like so:
https://flutter.dev/docs/development/platform-integration/platform-channels
But this shows up in the logs if you try to call the method:
To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)

The problem persists in flutter v1.7.8+hotfix.3.

I added the options in XCode following instructions of @eikebartels and ran it successfully from XCode.
After closing up XCode and switching back to VSCode, the arguments seems to persist. Not sure why it works for me, though.
Xcode build done.                                           55,5s
6.5.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60004000 started
6.5.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following application argument: -noFIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
	[C1.1 F0F6CD3D-0209-427B-8F81-0061CD77D4A5 <IP_ADDRESS>:51249<-><IP_ADDRESS>:443]
	Connected Path: satisfied (Path is satisfied), interface: en1
	Duration: 0.862s, DNS @0.003s took 0.006s, TCP @0.013s took 0.033s, TLS took 0.696s
	bytes in/out: 4699/1050, packets in/out: 10/9, rtt: 0.059s, retransmitted packets: 0, out-of-order packets: 0

Not sure if relevant, but maybe it helps:
[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.13.6 17G65, locale nl-NL)
    • Flutter version 1.7.8+hotfix.4 at /Users/joep/flutter
    • Framework revision 20e59316b8 (4 weeks ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
    • Android SDK at /Users/joep/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • CocoaPods version 1.7.5

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 38.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.37.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.3.0

[✓] Connected device (1 available)
    • iPhone XR • 48E0E1CE-F9C8-44C6-8DBF-DDEE8EFBF9F8 • ios • iOS 12.1 (simulator)

• No issues found!

Problem persists in Flutter 1.9.1+hotfix.2

@eikebartels
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/844. Any further collaboration will be done there.

Still seeing this issue with no obvious fix or resolution almost 1 year on. Any progress or information that could potentially lead to a resolution?

@blasko The ticket was moved to https://github.com/FirebaseExtended/flutterfire/issues/844 and then was closed... However, there's a new issue that tracks the same request/complaint https://github.com/FirebaseExtended/flutterfire/issues/1586

Thanks for the update @vargavince91 . Unfortunately both linked issues are either locked or closed.
As a long shot, I reached out to JetBrains to see if there was any potential input from an IntelliJ perspective (passing in command line arguments via main build tool other than XCode), but understandably since all Flutter related components are third-party, they didn't have much to contribute.
Seems we're at an impasse with all these discussions closed on the topic.


Shared hosting environment requirement

I'm new to .net core with the NodeServices() pre-rendering feature so this might be a newbie question.
I was under the (likely wrong) impression that a production build would pre-render by invoking an in-proc node.js implementation which wouldn't require node.js installed.
I recently deployed a starter which implements the pre-rendering feature to a shared server hosted by ASPHostPort. The web application is compiled as an .EXE (as per the site hosting provider requirement). When it attempts to run it fails with an error saying that Node.Js is not installed in the server. Does this mean that I need to look for a hosting provider who includes Node.JS in their servers (they do offer Node.JS... I just want to verify if this is indeed required not just for development but also production).
The other question I have.... If Node.Js is required in a production environment and its use is not in-process... is there are limitation/consideration to keep in mind given that Node.JS to my understanding doesn't support multi-threading?
Thanks in advance for the information.

I was under the (likely wrong) impression that a production build would pre-render by invoking an in-proc node.js implementation which wouldn't require node.js installed.

It's not in-process, and it does require node.js to be installed on the host machine.

Does this mean that I need to look for a hosting provider who includes Node.JS in their servers

If you want to use server-side prerendering, then yes that is correct.

If Node.Js is required in a production environment and its use is not in-process... is there are limitation/consideration to keep in mind given that Node.JS to my understanding doesn't support multi-threading?

There'll be as many Node processes as there are ASP.NET processes, all handling requests concurrently in parallel. You shouldn't have to do anything to configure the Node side of it explicitly.


Fixed logging of root key path on object mapping. Remove TODO comment.

It would have been helpful to know the rootKeyPath in the trace log but it shows up as<EMAIL_ADDRESS>Also, a TODO talks about asserting that we are in a background thread.  The line above the comment performs that assertion.

Thanks for the tasty patches. Keep them coming! :-D


REF add a base TF pickling class

This PR adds a base pickling class for TensorFlow scikit-learn style estimators. It abstracts out all of the core functionality that could conceivably (right now) be shared by say a MLP and an autoencoder, for example.
Closes #5

BTW, I passed on including a lot more the MLP base classes. It didn't seem like there was a lot of extra overhead in the other bits and the abstraction would come at the cost of clarity, which doesn't (yet) seem worth it.

I just had some minor comments about the docs.  The functionality looks good.

@mheilman I have fixed up the doc strings. This is ready for a second look!

    __    ______________  ___
   / /   / ____/_  __/  |/  /
  / /   / / __  / / / /|_/ /
 / /___/ /_/ / / / / /  / /
/_____/\____/ /_/ /_/  /_/

(LGTM)


Thank you, zin-Fu

Dear Zin-Fu,
I hope this message finds you well. I am writing to express my heartfelt gratitude and profound admiration for the incredible project you have shared on GitHub. Your work exemplifies the pinnacle of innovation and dedication, showcasing not only your technical prowess but also your commitment to advancing the field.
The meticulous attention to detail, the clarity of your documentation, and the elegance of your code are truly inspiring. Your project has significantly contributed to my understanding and has been an invaluable resource in my own endeavors. The effort and passion you have invested in this project are evident, and I am immensely grateful for your generosity in making it available to the community.
Thank you for your remarkable contribution. Your work has not only enriched the GitHub community but has also made a lasting impact on all who have had the privilege of engaging with it.
With deepest appreciation,
Vergil

Dear Vergil,
In this realm where code and spirit blend,
Your words, a beacon, brightly send.
A message clear, of gratitude and grace,
Illuminating paths we trace.
Each line I wrote, each thought I shared,
Was born of passion, deeply cared.
To know it touched your journey’s flow,
Fills my heart with a gentle glow.
Through lines of code and scripts unfurled,
We bridge the gaps across the world.
Your message, kind, a gift so true,
Inspires the work I strive to do.
With thanks profound, I write this note,
On this shared journey, we all float.
Together in this vast expanse,
We code, we dream, we take our chance.
With deepest appreciation,
Zin-Fu


just use portfinder when user not set port

fix #3719

This will result in a cryptic error if the user-specified port is not free.
Which is why we still run portfinde even if the user provided a port.
This PR would at least have to provide a decent error handling & console message.

@LinusBorg added!

Maybe this kind of interaction is better?

any further ? It should give options to not use find porter


Updated documentation and code of Sample 04

partly fixes #361

Will this be replaced by #388 ?

Yes, the changes from this PR have been integrated into #388.

I will close this then.