text:
scaling issue when metric and threshold result in floating point, no recovery from that point onwards

Report
Consider below scaledobject, and a dummy k8s deployment called "demo"
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: demo-scaledobject
  namespace: default
spec:
  scaleTargetRef:
    name: demo
  minReplicaCount: 0
  cooldownPeriod:  30
  triggers:
  - type: prometheus
    metadata:
      serverAddress: http://192.168.1.165:9090
      metricName: visit_counter_total
      threshold: '2'
      query: visit_counter_total
      disableScaleToZero: 'true'

Issue:
Prometheus reported visit_counter_total=38, everything good 19 pods got created.
Prometheus reported visit_counter_total=39, pods stayed 19 (which is fine)
Prometheus reported visit_counter_total=40, ISSUE: NUMBER OF PODS STUCK AT 19

% k get pods --no-headers | wc -l
      19

LOGS: WHEN I INCREASED visit_counter_total FROM 38 TO 39 (WAITED FOR 3 MINS) TO 40 (WAITED FOR 10 MINS)
1.6563435558217254e+09	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435558218324e+09	DEBUG	controller.scaledobject	Parsed Group, Version, Kind, Resource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default", "GVK": "apps/v1.Deployment", "Resource": "deployments"}
1.656343555832207e+09	DEBUG	controller.scaledobject	ScaledObject is defined correctly and is ready for scaling	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435708244784e+09	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435708245707e+09	DEBUG	controller.scaledobject	Parsed Group, Version, Kind, Resource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default", "GVK": "apps/v1.Deployment", "Resource": "deployments"}
1.6563435708350515e+09	DEBUG	controller.scaledobject	ScaledObject is defined correctly and is ready for scaling	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435791322286e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436090996041e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436390634325e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.65634366903128e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436989966836e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563437289631693e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563437589283757e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563

Expected Behavior
POD COUNT SHOULD HAVE GONE UP TO 20.
Actual Behavior
POD COUNT STUCK AT 19
Steps to Reproduce the Problem

INSTALL PROMETHEUS LOCALLY
RUN THIS SAMPLE MICROSERVICE https://tanzu.vmware.com/developer/guides/spring-prometheus/
INCREASE visit_counter_total FROM 38 TO 39 (WAITED FOR 3 MINS) TO 40 (WAITED FOR 10 MINS)

Logs from KEDA operator
1.6563435558217254e+09	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435558218324e+09	DEBUG	controller.scaledobject	Parsed Group, Version, Kind, Resource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default", "GVK": "apps/v1.Deployment", "Resource": "deployments"}
1.656343555832207e+09	DEBUG	controller.scaledobject	ScaledObject is defined correctly and is ready for scaling	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435708244784e+09	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435708245707e+09	DEBUG	controller.scaledobject	Parsed Group, Version, Kind, Resource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default", "GVK": "apps/v1.Deployment", "Resource": "deployments"}
1.6563435708350515e+09	DEBUG	controller.scaledobject	ScaledObject is defined correctly and is ready for scaling	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "demo-scaledobject", "namespace": "default"}
1.6563435791322286e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436090996041e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436390634325e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.65634366903128e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563436989966836e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563437289631693e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563437589283757e+09	DEBUG	scalehandler	Scaler for scaledObject is active	{"scaledobject.Name": "demo-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "demo", "Metrics Name": "s0-prometheus-visit_counter_total"}
1.6563

KEDA Version
2.7.1
Kubernetes Version
1.23
Platform
Other
Scaler Details
Prometheus
Anything else?
ALL THIS IN THE LOCAL ENVIRONMENT USING KIND

I tried it again today, and found that it might take time to reproduce but it does happen, that after a point scaling pauses
% k get hpa
NAME                         REFERENCE         TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
keda-hpa-demo-scaledobject   Deployment/demo   2154m/2 (avg)   1         100       13         33m

I was working perfectly fine till I hit visit_counter_total=28

Hey,
I'd say that having that small difference between the target value and the current value, you could need a lot of time more. I suggest taking a look at HPA documentation and how to configure these advanced  behaviours.
In the docs they also say:
The control plane skips any scaling action if the ratio is sufficiently close to 1.0 (within a globally-configurable tolerance, 0.1 by default). Maybe this is your case

BTW, where have you found the parameter disableScaleToZero? I think that it's not used anywhere

Can you give me a debug binary to get more informed logs?
--zap-log-level=debug is really not enough to nail down on this one.

What do you mean? You can use the source code and troubleshoot your case with it

Hey, I'd say that having that small difference between the target value and the current value, you could need a lot of time more. I suggest taking a look at HPA documentation and how to configure these advanced behaviours. In the docs they also say: The control plane skips any scaling action if the ratio is sufficiently close to 1.0 (within a globally-configurable tolerance, 0.1 by default). Maybe this is your case

This was the issue. But now I am completely trapped. Because I have no way to configure this in my AKS clusters. I checked with Azure AKS teams, they are unable to help.
@JorTurFer
Do you know a workaround?

the only workaround is setting the targetValue smaller, the problem is that in v2.7.1, the target value and the metrics have to be integers, so you need to have 1 instead of 2 and I guess that it's too much overscaling.
In main there is a commit merged to support float values for target and metrics, and using it you could set the threshold to 1.8 or 1.9 but next release will be in a month. You could use main tag but we discourage it because it's not a stable version

FYI: https://github.com/Azure/AKS/issues/3068

This is not on KEDA but AKS

hi @tomkerkhove instead of the customized fix, do we have a solution for this issue now?

authors: JorTurFer bjethwan jcQuartic

repo: kedacore/keda


text:
fix: apply semgrep suggestions

Signed-off-by: Jorge Turrado jorge_turrado@hotmail.es

Fix some code alerts generated by semgrep
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to https://github.com/kedacore/keda/issues/3961

/run-e2e

/run-e2e

/run-e2e

LGTM

I have to add a lot of extra changes for the rule [Semgrep found a possible error wrong wrapped](https://github.com/kedacore/keda/security/code-scanning/534). If you agree, I'll merge the PR once I have done them and e2e tests pass

LGTM

I have to add a lot of extra changes for the rule [Semgrep found a possible error wrong wrapped](https://github.com/kedacore/keda/security/code-scanning/534). If you agree, I'll merge the PR once I have done them and e2e tests pass

yeah :)

/run-e2e

/run-e2e

/run-e2e

source: gharchive/pull-request

authors: JorTurFer zroubalik

license_type: permissive

license_source: github-api


text:
Validate declared group member index against group selection result

Closes #484
Closes #834
This work is still in progress.

The group selection protocol outcome is an array of values uniquely identifying clients selected to the group. Index of a client in that array is an index used for DKG protocol. During DKG protocol execution we need to validate those indexes - check if all members we cooperate with, use the correct ones. If not, the message from the given sender should be rejected.

The main component is group.MembershipValidator implemented by groupselection.MembershipValidator and passed to DKG executor. For every received message it checks the public key of the sender and its declared index against group selection result - ordered array of staker addresses. This component replaced createGroupMemberFilter in node.go as it offers the same functionality.
TODO:

[ ] validation of sender index during relay entry signing
[ ] this validation - although seems to be pretty lightweight - causes problems in commitment verification state; a lot of members is marked as inactive
[ ] we are currently dropping message - should we consider disqualifying member?

Closed in favor of #1534

Closed in favor of #1534

authors: lukasz-zimnoch pdyraga

repo: keep-network/keep-core

license: MIT


text:
Dependency bumps: all in one batch

All old and recent dependabot updates gathered into one PR to avoid having to rebase constantly. Also, the change from https://github.com/keep-network/keep-core/commit/fd6dd1908741acc8be8bf7e514a8ea30bae4f4ab required special attention. I reverted it and updated go-ethereum to v1.10.15 in https://github.com/keep-network/keep-core/pull/2817/commits/132ecaee8986d09c55a6244b6210e53297efa966. The change in go.sum removing golang.org/x/mod from there introduced in https://github.com/keep-network/keep-core/commit/fd6dd1908741acc8be8bf7e514a8ea30bae4f4ab  made our build fail with:

[gobuild 23/24] RUN go generate ./pkg/gen:
#30 0.506 /go/pkg/mod/golang.org/x/tools@v0.1.1/internal/imports/mod.go:21:2: missing go.sum entry for module providing package golang.org/x/mod/module (imported by golang.org/x/tools/internal/imports); to add:
#30 0.506 	go get golang.org/x/tools/internal/imports@v0.1.1
#30 0.506 /go/pkg/mod/golang.org/x/tools@v0.1.1/internal/gocommand/vendor.go:17:2: missing go.sum entry for module providing package golang.org/x/mod/semver (imported by golang.org/x/tools/internal/gocommand); to add:
#30 0.506 	go get golang.org/x/tools/internal/gocommand@v0.1.1
#30 0.511 pkg/gen/async.go:3: running "sh": exit status 1

Revert helped with this problem and I upgraded to the most recent version to keep the dependency still secure.
60fade7 replaces #2463
e187c98 replaces #2465
5c99ffa replaces #2495
3e9ea91 replaces #2565
c967059 replaces #2566
b0b6272 replaces #2567
80c14e4 replaces #2568
2651908 replaces #2586
a3cd12d replaces #2587
f334b7b replaces #2588
c11910d replaces #2589 and #2688
fd6dd19 and later https://github.com/keep-network/keep-core/pull/2817/commits/132ecaee8986d09c55a6244b6210e53297efa966 replaces #2678
21f6fab replaces #2687
9f6c8be replaces #2689
759bfda replaces #2702
3948917 replaces #2717
f0d568a replaces #2785
f48f33a replaces #2787
52dc368 replaces #2788
6e4cd29 replaces #2789
e9d22d5 replaces #2790
5671531 replaces #2808
c3fcee4 replaces #2809
30e7f74 replaces #2810
cea23c1 replaces #2811
8665483 replaces #2812
919734b replaced #2813
4896502 replaces #2814

Checked:

build and tests /solidity/random-beacon
build won't work for /solidity/ecdsa but we don't have any contracts here, so I think it's fine
go get produces the following:

# github.com/benbjohnson/clock
/Users/dp/go/pkg/mod/github.com/benbjohnson/clock@v1.1.0/clock.go:323:11: t.ticker.Reset undefined (type *time.Ticker has no field or method Reset)
note: module requires Go 1.15
# github.com/keep-network/keep-common/pkg/chain/ethereum/ethutil
/Users/dp/go/pkg/mod/github.com/keep-network/keep-common@v1.7.1-0.20211012131917-7102d7b9c6a0/pkg/chain/ethereum/ethutil/ethutil.go:30:2: duplicate method HeaderByNumber
/Users/dp/go/pkg/mod/github.com/keep-network/keep-common@v1.7.1-0.20211012131917-7102d7b9c6a0/pkg/chain/ethereum/ethutil/logging_wrapper.go:51:33: loggingWrapper.HeaderByNumber is ambiguous
/Users/dp/go/pkg/mod/github.com/keep-network/keep-common@v1.7.1-0.20211012131917-7102d7b9c6a0/pkg/chain/ethereum/ethutil/logging_wrapper.go:51:33: cannot use &loggingWrapper literal (type *loggingWrapper) as type EthereumClient in return argument:
        *loggingWrapper does not implement EthereumClient (missing HeaderByNumber method)
/Users/dp/go/pkg/mod/github.com/keep-network/keep-common@v1.7.1-0.20211012131917-7102d7b9c6a0/pkg/chain/ethereum/ethutil/rate_limiter.go:214:2: not enough arguments to return
/Users/dp/go/pkg/mod/github.com/keep-network/keep-common@v1.7.1-0.20211012131917-7102d7b9c6a0/pkg/chain/ethereum/ethutil/rate_limiter.go:214:26: ambiguous selector rl.EthereumClient.HeaderByNumber

go generate ./... worked

All the changed files look good to me.

authors: dimpar pdyraga


text:
spike: Experiment Candidate for Leader Elections ♠

For reference:
Starknet Decentralized Protocol I - Introduction
Starknet Decentralized Protocol II - Candidate for Leader Elections
Starknet Decentralized Protocol III - Consensus
Starknet Decentralized Protocol IV - Proofs in the Protocol
Starknet Decentralized Protocol V - Checkpoints for Fast Finality
Starknet Decentralized Protocol VI - The Buffer Problem
Starknet Decentralized Protocol VII - Chained Proof Protocols & Braiding

Madara Consensus Spike:
TASKS

Sync on outer node storage & "mapping-sync" on node init(extend for consensus data ref moonbeam 'relay_chain_state_proof')
Create "bookie" solidity contract/and $fSTARK(contact Ilia to see what's been done)
Create "bookie" block author pallet
Create "quorum" finalization pallet
Benchmark/Integration tests
Evaluate usage of HotStuff pallet when available

Architecture
Substrate Consensus done in 2 phases:

Block Authoring process nodes use to create new blocks
Block Finalization process used to handle forks and choose canonical chain

Block Authoring:
Aura and Babe require a known set of validators or "authorities" as block producers, time is divided into discrete slots and during each slot authority can propose block.
Bookie(StarkNet Proposal) - epoch based stake weighted scheduling
- epoch(5m)/slot(15s) public lottery based on L1 timestamps
- leader_election(epoch randomness, stake distribution) - can be calculated offchain
- state update of the L1 core contract ensures via proof that L2 block authorship follows schedule
alts/refs
Aura - Authority Based Round Robin Scheudling
- rotating list of authorities takee turns creating blocks
- majority of online authorities are assumed to be honest
- used in combo w/ GRNADPA where Aura = block production and short term finality and GRANDPA deterministic finality provided by GRANDPA
Babe - Blind assignment of blockchain extention slot-based scheduling
- authorities win slots based on a verifiable random function as opposed to round-robin
- winning authority can select a chain and submit new block
Block Finalization:
Substrate exposes the fork choice rule implementation via the "SelectChain" trait and you can use custom or GRANDPA. Substrate exposes "LongestChain" for chain selection rule.
Deterministic finality can be reached with a set of fixed authorities casting "finality" votes. When enough(2/3) votes have been cast block is deemed final. Blocks that have been finalized can't be reverted w/o external coordination such as hard fork. If your blockchain has a finality mechanism, must be modified wthe fork choise rule to consider the finality vote.
Quorum(StarkNet Proposal) - dual ledger finality via quorum certs
- Periodic L1 checkpointing of state update
- Quorum checkpoints supported by majority of stake
- Conflicting checkpoints can't exist
alts/refs
GRANDPA - deterministic finality mechanism for blockchains
- longest chain rule = best chain is the longest chain
GHOST - greediest heaviest observed subtree
- the correct fork is the one that has the most blocks built on it
HotStuff - 3 phase view-change w/ quorum certs message exchange
- Random/Fair/Rotating primary(no need for seperate block authoring pallet, can use randomness)
- Quorum Certificates consist of unique node and view number
- (prepare)Leader extends branch with the highest QC view and broadcasts replica accepts/responds w/ portion of threshold signature -> (pre-commit) Leader combines in a "prepare QC" and broadcasts prepare message and replicas vote on pre-commit -> (commit) Leader combines votes in "pre-commit QC" and broadcasts commit message, replica votes on commit and locks "pre-commit QC" ->  (decide) leader combines in "commit QC" broadcast decision, replica execute command, increase view number,start new view
- Substrate(madara) impl https://github.com/keep-starknet-strange/madara/issues/180

project repo for PoC solidity contracts:
https://github.com/keep-starknet-strange/zaun

source: gharchive/issue

authors: abdelhamidbakhta drspacemn

repo: keep-starknet-strange/madara


text:
Still in being maintained ?

Is there a roadmap for the plugin ?

I'm still struggling to find a reasonable goal. It's hard to provide an optimal solution for SDI with this plugin due to the limitation of DeckLink products. I have to find a middle ground.
How do you want to use the plugin? What features do you want in the plugin? Any input is welcomed.

Hello Keijiro! Thank you for amazing stuff you make for unity community!
But a want ask a question - is there any chance to make this plugin for "Decklink"
capture work on osx ?

@keijiro I'm use external Intensity Shuttle device (usb3/thunderbolt2) and looks like it works thru the same DeckLink library as PCI capture cards.  Already tested my devices in openframeworks with  this addon [https://github.com/hanasaan/ofxDeckLink].

@grigM Thanks for the response. Yes, it would work with Intensity. It's a little bit troublesome to add macOS support though.

Hi @keijiro, is the new version of the desktop video 11 SDK supported?

@Filmengineers Currently I'm not working on this project, so there is no update for the new SDK.

authors: Filmengineers grigM keijiro whitespeed

repo: keijiro/Klinker

license: Unlicense


text:
Help wanted for AR Foundation integration

I would like a to integrate this amazing tool into AR Foundation.
How can I use the AR camera stream to track the tags; being able to trace images in a unity scene instead of a webcam would probably also be a useful advance/hint,
thank you.

The tag detector processes an image, not a webcam. The webcam support is implemented in the sample program.
So, I think you can do it in the current implementation.

I'm closing this issue now. Please feel free to reopen it for further problems.

I'm not so smart yet and i have not found any solution to modify and take advantage of the webcam sample to work with an image or a render texture instead. I tried to set up Render Texture or a Texture2D instead of the WebCamTexture but this doesn't make sense. Could you help me to implement this?
thank you.

I have managed to crash unity instantly with this :) PictureTest.cs

Is the dimensions of sourceImage correct? My wild guess is that the texture importer changed the dimensions to a power-of-two square.

After changing the read/write parameter = true and set the Non-Power of 2 to none in the sourceImage importer it just works!
Thank you.

Thanks Keijiro for pointing me in the right direction, i have learned a lot...
https://user-images.githubusercontent.com/49713529/140614561-d452d7f0-9f22-4e0e-ae2d-acc2d763ec8a.mov


text:
Register/unregister cluster with Keiko-manager

close https://github.com/keikoproj/manager/issues/5 & https://github.com/keikoproj/manager/issues/7
Could you share the solution in high level?
For managed cluster registration,
Assumption:

CLI register/unregister commands must be run by cluster administrator who has kubeconfig downloaded in their local machine.
User can also create service account, cluster role(with * access) and cluster role binding to service account by themself and just pass service account name to the cli command.
If the service account is not provided, cli creates all the necessary RBAC resources including sa, cluster role and cluster role binding.

Could you share the test results?
Registration:
mtvl15367e28a:manager nmogulla$ go run cli/manager/main.go cluster register -c admins@iksm-ppd-usw2-k8s
token received successfully
mtvl15367e28a:manager nmogulla$

mtvl15367e28a:manager nmogulla$ k get sa keiko-manager-sa -o yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  creationTimestamp: "2020-03-13T22:31:35Z"
  name: keiko-manager-sa
  namespace: kube-system
  resourceVersion: "19728716"
  selfLink: /api/v1/namespaces/kube-system/serviceaccounts/keiko-manager-sa
  uid: 65d282ee-657a-11ea-adfa-0290a4e7fa7c
secrets:
- name: keiko-manager-sa-token-9q28c
mtvl15367e28a:manager nmogulla$

Unregister the cluster: This will remove the service account, cluster role and rolebinding from the target cluster
mtvl15367e28a:manager nmogulla$ go run cli/manager/main.go cluster unregister -c admins@iksm-ppd-usw2-k8s
mtvl15367e28a:manager nmogulla$
mtvl15367e28a:manager nmogulla$
mtvl15367e28a:manager nmogulla$ k get secrets keiko-manager-sa-token-9q28c -o yaml|base64
Error from server (NotFound): secrets "keiko-manager-sa-token-9q28c" not found

mtvl15367e28a:manager nmogulla$
mtvl15367e28a:manager nmogulla$ k get sa keiko-manager-sa -o yaml
Error from server (NotFound): serviceaccounts "keiko-manager-sa" not found
mtvl15367e28a:manager nmogulla$

This is just CLI part. Server and Controller is in work in progress

i will overwrite that but i'd see if i can include cluster_types.go too as i'm currently working on server part and include that also in the same PR so i'm not blocked.

Cluster registration from server:
2020-03-25T01:36:50.426Z	INFO	server.cluster.RegisterCluster	Request received
2020-03-25T01:36:50.427Z	INFO	server.cluster.RegisterCluster	cluster name from the request	{"name": "ops-prim-ppd.cluster.k8s.local"}
2020-03-25T01:36:50.427Z	DEBUG	server.cluster.RegisterCluster	cluster name after sanitizing	{"name": "ops-prim-ppd-cluster-k8s-local"}
2020-03-25T01:36:50.444Z	INFO	pkg.k8s.resources.CreateNamespace	Successfully created namespace	{"name": "ops-prim-ppd-cluster-k8s-local"}
2020-03-25T01:36:50.470Z	INFO	pkg.k8s.rbac.CreateK8sSecret	Successfully created/updated secret	{"secret_name": "ops-prim-ppd-cluster-k8s-local-secrets", "namespace": "ops-prim-ppd-cluster-k8s-local"}
2020-03-25T01:36:50.505Z	INFO	pkg.k8s.resources.CreateNamespace	Successfully cluster CR created/updated

2020-03-25T01:40:23.331Z	INFO	server.cluster.RegisterCluster	Request received
2020-03-25T01:40:23.331Z	INFO	server.cluster.RegisterCluster	cluster name from the request	{"name": "docker-desktop"}
2020-03-25T01:40:23.331Z	DEBUG	server.cluster.RegisterCluster	cluster name after sanitizing	{"name": "docker-desktop"}
2020-03-25T01:40:23.371Z	INFO	pkg.k8s.resources.CreateNamespace	Successfully created namespace	{"name": "docker-desktop"}
2020-03-25T01:40:23.388Z	INFO	pkg.k8s.rbac.CreateK8sSecret	Successfully created/updated secret	{"secret_name": "docker-desktop-secrets", "namespace": "docker-desktop"}
2020-03-25T01:40:23.419Z	INFO	pkg.k8s.resources.CreateNamespace	Successfully cluster CR created/updated

Cluster Registration from controller:
2020-03-25T01:40:23.462Z	INFO	controllers.cluster_controller.Reconcile	Start of the request	{"request_id": "019144c9-808a-4950-b678-1bfd49dc0faf"}
2020-03-25T01:40:23.471Z	INFO	pkg.k8s.rbac.GetK8sSecret	secret found	{"request_id": "019144c9-808a-4950-b678-1bfd49dc0faf", "secret_name": "docker-desktop-secrets"}
2020-03-25T01:40:23.471Z	INFO	controllers.cluster_controller.Reconcile	New cluster resource. Adding the finalizer	{"request_id": "019144c9-808a-4950-b678-1bfd49dc0faf", "finalizer": "cluster.finalizers.manager.keikoproj.io"}
2020-03-25T01:40:23.483Z	INFO	controllers.cluster_controller.HandleReconcile	state of the custom resource 	{"request_id": "019144c9-808a-4950-b678-1bfd49dc0faf", "state": ""}
I0325 01:40:23.578652       1 event.go:281] Event(v1.ObjectReference{Kind:"Cluster", Namespace:"docker-desktop", Name:"docker-desktop", UID:"98352719-6e39-11ea-bfe9-025000000001", APIVersion:"manager.keikoproj.io/v1alpha1", ResourceVersion:"5173538", FieldPath:""}): type: 'Normal' reason: 'Ready' Successfully validated the target cluster
2020-03-25T01:40:23.663Z	INFO	controllers.cluster_controller.HandleReconcile	SUCCESSFUL	{"request_id": "019144c9-808a-4950-b678-1bfd49dc0faf", "version": "1.14"}

Cluster unregistration from controller:
2020-03-25T01:41:29.266Z	INFO	controllers.cluster_controller.Reconcile	Start of the request	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3"}
2020-03-25T01:41:29.279Z	INFO	pkg.k8s.rbac.GetK8sSecret	secret found	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3", "secret_name": "ops-prim-ppd-cluster-k8s-local-secrets"}
2020-03-25T01:41:29.279Z	INFO	controllers.cluster_controller.Reconcile	Cluster delete request	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3"}
2020-03-25T01:41:29.359Z	INFO	pkg.k8s.client.DeleteServiceAccount	Service account removed successfully	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3", "serviceAccount": "keiko-manager-sa", "namespace": "kube-system"}
2020-03-25T01:41:29.359Z	INFO	controllers.cluster_controller.Reconcile	Removing finalizer from Cluster	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3"}
2020-03-25T01:41:29.395Z	INFO	controllers.cluster_controller.Reconcile	Successfully deleted cluster	{"request_id": "916cac56-f90f-4372-bcaa-0b200d7e22e3"}
2020-03-25T01:41:29.395Z	DEBUG	controller-runtime.controller	Successfully Reconciled	{"controller": "cluster", "request": "ops-prim-ppd-cluster-k8s-local/ops-prim-ppd-cluster-k8s-local"}
I0325 01:41:29.395996       1 event.go:281] Event(v1.ObjectReference{Kind:"Cluster", Namespace:"ops-prim-ppd-cluster-k8s-local", Name:"ops-prim-ppd-cluster-k8s-local", UID:"194ba969-6e39-11ea-bfe9-025000000001", APIVersion:"manager.keikoproj.io/v1alpha1", ResourceVersion:"5173630", FieldPath:""}): type: 'Normal' reason: 'Deleted' Successfully deleted cluster

Cluster unregistration from server:
2020-03-25T01:41:29.243Z	INFO	server.cluster.UnregisterCluster	cluster name from the request	{"name": "ops-prim-ppd.cluster.k8s.local"}
2020-03-25T01:41:29.243Z	DEBUG	server.cluster.UnregisterCluster	cluster name after sanitizing	{"name": "ops-prim-ppd-cluster-k8s-local"}
2020-03-25T01:41:29.304Z	INFO	pkg.k8s.resources.DeleteNamespace	Successfully deleted namespace	{"name": "ops-prim-ppd-cluster-k8s-local"}

To list the clusters:
mtvl15367e28a:manager nmogulla$ k get clusters --all-namespaces
NAMESPACE                        NAME                             STATE   RETRYCOUNT   AGE
docker-desktop                   docker-desktop                   Ready   0            20s
ops-prim-ppd-cluster-k8s-local   ops-prim-ppd-cluster-k8s-local   Ready   0            3m53s

repo: keikoproj/manager


text:
gRPCで相互通信出来る最小構成のサンプルコードを追加する

Doneの定義

2つのgRPCサーバーが構築され、その2つが相互通信出来る状態になっている事

補足情報
Dockerfileの https://github.com/keitakn/golang-grpc-server/blob/046c8ca56fcd1f4a38b54749cf711e8fc1720e9c/Dockerfile#L25 の部分が間違っているのでついでに修正する。

README.mdもこの課題の中で書けるだけ書く。

repo: keitakn/golang-grpc-server


text:
Problemas na lura toon

Source information
Lura toon
Source language
Português brasil
Steps to reproduce
As imagens não carregam eu já resolvi o cloudflare no capitulo mais continua a mesma coisa
Expected behavior
Quando resolvesse o cloudflare as imagens deveriam carregar
Actual behavior
Mais elas não estão carregando
Mihon/Tachiyomi version
0.16.5
Android version
Android 10
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

seems like a site issue

Chapters are being blocked as soon as they are opened

It seems that now Cloudflare verification is only present when accessing chapters

What is your extension version of Lura toon?

The problem is happening in the latest version of the extension, the same one that was updated yesterday (The problem is happening in the latest version of the extension, the same one that was updated yesterday (1.4.46)

Qual é a sua versão de extensão do Lura toon?

1.4.46

Os capítulos estão sendo bloqueados assim que são abertos Parece que agora a verificação Cloudflare só está presente ao acessar os capítulos

Sim isso mesmo

Tem algum geito de resolver

Qual é a sua versão de extensão do Lura toon?

O problema está acontecendo na última versão da extensão, a mesma que foi atualizada ontem (O problema está acontecendo na última versão da extensão, a mesma que foi atualizada ontem (1.4.46)

Sim

Sim é na versão mais recentes 1.4.46 como posso resolver é uma das
extensões que mais uso
Em sex, 17 de mai de 2024 16:38, DollynDeveloper @.***>
escreveu:

What is your extension version of Lura toon?
The problem is happening in the latest version of the extension, the same
one that was updated yesterday (The problem is happening in the latest
version of the extension, the same one that was updated yesterday (1.4.46)
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/3088#issuecomment-2118259687,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUAKVFKLD53HVBSJRS6N6LZCZMEPAVCNFSM6AAAAABH4RSEOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGI2TSNRYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Chapters are being blocked as soon as they are opened  It seems that now Cloudflare verification is only present when accessing chapters

Usa o app na playstore chamado: "1.1.1.1" da cloudfare, depois de iniciar reiniciar o app e pronto.

Ok obrigado
Em sex, 17 de mai de 2024 20:53, nomaxsnx @.***>
escreveu:

Chapters are being blocked as soon as they are opened [image:
Screenshot_20240517-163430_Kuukiyomi]
https://private-user-images.githubusercontent.com/72720834/331713073-1148f9c0-bed6-4697-bf8d-ebe8ae4dd8a1.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU5OTAyMzksIm5iZiI6MTcxNTk4OTkzOSwicGF0aCI6Ii83MjcyMDgzNC8zMzE3MTMwNzMtMTE0OGY5YzAtYmVkNi00Njk3LWJmOGQtZWJlOGFlNGRkOGExLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTE3VDIzNTIxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlZGYyNjJhMGY5MDQ1YjNkMzYwNzgxODU2ZjNkZTZkMzUwN2EzNDg5ZGYxYTEyZmZiMzI0ODExZDExMTQzZWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.JtO3VV0OhCdIVFjq-5P3ilIi9lnwFtYud37IGtebEVI
It seems that now Cloudflare verification is only present when accessing
chapters
Usa o app na playstore chamado: "1.1.1.1" da cloudfare, depois de iniciar
reiniciar o app e pronto.
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/3088#issuecomment-2118501035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUAKVFCKFHCHPAWZINEIK3ZC2KBDAVCNFSM6AAAAABH4RSEOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGUYDCMBTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Eu fiz como vc disse mais não funcionou
Em sex, 17 de mai de 2024 21:33, Pedro Paulo Pereira Da Costa <
@.***> escreveu:

Ok obrigado
Em sex, 17 de mai de 2024 20:53, nomaxsnx @.***>
escreveu:

Chapters are being blocked as soon as they are opened [image:
Screenshot_20240517-163430_Kuukiyomi]
https://private-user-images.githubusercontent.com/72720834/331713073-1148f9c0-bed6-4697-bf8d-ebe8ae4dd8a1.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU5OTAyMzksIm5iZiI6MTcxNTk4OTkzOSwicGF0aCI6Ii83MjcyMDgzNC8zMzE3MTMwNzMtMTE0OGY5YzAtYmVkNi00Njk3LWJmOGQtZWJlOGFlNGRkOGExLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTE3VDIzNTIxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlZGYyNjJhMGY5MDQ1YjNkMzYwNzgxODU2ZjNkZTZkMzUwN2EzNDg5ZGYxYTEyZmZiMzI0ODExZDExMTQzZWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.JtO3VV0OhCdIVFjq-5P3ilIi9lnwFtYud37IGtebEVI
It seems that now Cloudflare verification is only present when accessing
chapters
Usa o app na playstore chamado: "1.1.1.1" da cloudfare, depois de iniciar
reiniciar o app e pronto.
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/3088#issuecomment-2118501035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUAKVFCKFHCHPAWZINEIK3ZC2KBDAVCNFSM6AAAAABH4RSEOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGUYDCMBTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Continuou com o mesmo problema
Em sex, 17 de mai de 2024 21:49, Pedro Paulo Pereira Da Costa <
@.***> escreveu:

Eu fiz como vc disse mais não funcionou
Em sex, 17 de mai de 2024 21:33, Pedro Paulo Pereira Da Costa <
@.***> escreveu:

Ok obrigado
Em sex, 17 de mai de 2024 20:53, nomaxsnx @.***>
escreveu:

Chapters are being blocked as soon as they are opened [image:
Screenshot_20240517-163430_Kuukiyomi]
https://private-user-images.githubusercontent.com/72720834/331713073-1148f9c0-bed6-4697-bf8d-ebe8ae4dd8a1.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU5OTAyMzksIm5iZiI6MTcxNTk4OTkzOSwicGF0aCI6Ii83MjcyMDgzNC8zMzE3MTMwNzMtMTE0OGY5YzAtYmVkNi00Njk3LWJmOGQtZWJlOGFlNGRkOGExLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTE3VDIzNTIxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlZGYyNjJhMGY5MDQ1YjNkMzYwNzgxODU2ZjNkZTZkMzUwN2EzNDg5ZGYxYTEyZmZiMzI0ODExZDExMTQzZWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.JtO3VV0OhCdIVFjq-5P3ilIi9lnwFtYud37IGtebEVI
It seems that now Cloudflare verification is only present when accessing
chapters
Usa o app na playstore chamado: "1.1.1.1" da cloudfare, depois de
iniciar reiniciar o app e pronto.
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/3088#issuecomment-2118501035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUAKVFCKFHCHPAWZINEIK3ZC2KBDAVCNFSM6AAAAABH4RSEOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGUYDCMBTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Versão 1.4.46
Em sáb, 18 de mai de 2024 11:45, AwkwardPeak7 @.***>
escreveu:

Closed #3088 https://github.com/keiyoushi/extensions-source/issues/3088
as completed via #3090
https://github.com/keiyoushi/extensions-source/pull/3090.
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/3088#event-12856058904,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUAKVFJAEDVAM5DA3EGCADZC5SPFAVCNFSM6AAAAABH4RSEOWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSHA2TMMBVHA4TANA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

authors: DollynDeveloper Pedropaulo015 bapeey nomaxsnx

repo: keiyoushi/extensions-source


text:
Add EternalMangas

Closes #2104
HeanCMS copycat theme (already two sources using this)
Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[x] Have removed web_hi_res_512.png when adding a new extension

mangaesp is using same code?
make multisrc thanks


text:
proxying only some versions of crates from crates.io

Hi,
I'm trying to setup kellnr 5.1.1 to use as a proxy for crates.io, however, when I try to run cargo fetch I get the following error:
$ cargo fetch
    Updating `kellnr-cratesio` index
error: failed to select a version for the requirement `ahash = "^0.8"`
candidate versions found which didn't match: 0.4.0, 0.3.8, 0.3.7, ...
location searched: `kellnr-cratesio` index (which is replacing registry `crates-io`)
required by package `sqlx-core v0.7.0`
    ... which satisfies dependency `sqlx-core = "=0.7.0"` of package `sqlx v0.7.0`
    ... which satisfies dependency `sqlx = "^0.7"` of package `config-rest-service v2024.1.28 (/home/pcampbell/projects/tasyn/main/crates/services/config-rest-service)`
    ... which satisfies path dependency `config-rest-service` of package `tasyn v2024.1.28 (/home/pcampbell/projects/tasyn/main/crates/main)`
perhaps a crate was updated and forgotten to be re-vendored?

This works when my ~/.cargo/config is unmodified and is contacting crates.io directly.
When I add the following to ~/.cargo/config I get the error as above:
[registries]
kellnr = { index = "sparse+https://********:443/api/v1/crates/", token = "***" }
[source.crates-io]
replace-with = "kellnr-cratesio"
[source.kellnr-cratesio]
registry = "sparse+https://********:443/api/v1/cratesio/"

When I inspect the cratesio_index table within the sqlite database, I can see that only the first ~49 versions of the ahash crate have been added to the database.

Hi @kemitix!
I tried to reproduce the issue but failed, as ahash is correctly pulled on my machine. Can you describe your setup of kellnr for me, such that I can replicate it?
Do you use Kellnr on bare metal or as a container? Do you use the sqlite or postgresdb backend?

Hi @secana
Here is my docker-compose.yml:
version: "3.3"
services:
  kellnr:
    image: ghcr.io/kellnr/kellnr:5.1.1@sha256:50ed600736e1b561eaf2c1bf960f7d320e5d4525ae0c6574d380f8d033526f8a
    restart: unless-stopped
    volumes:
      - ./data:/opt/kdata
    ports:
      - 8089:8000
    environment:
      KELLNR_ORIGIN__PROTOCOL: https
      KELLNR_ORIGIN__HOSTNAME: crates.***.net
      KELLNR_ORIGIN__PORT: 443
      # KELLNR_LOG__LEVEL: trace
      KELLNR_REGISTRY__MAX_CRATE_SIZE: 1000
      KELLNR_PROXY__ENABLED: true
      KELLNR_DOCS__ENABLED: true
      KELLNR_DOCS__MAX_SIZE: 1000

It is hosted behind Caddy as a reverse proxy:
https://crates.***.net:443 {
    reverse_proxy :8089
}

@kemitix I still fail to reproduce the issue. Can you please run kellnr with the log level "trace" and provide the logs? Maybe there is a hint, why not all versions are pulled from crates.io

@secana I believe I've found the problem. I have a squid proxy that I use with HTTPS_PROXY and HTTP_PROXY environment variables. I suspect my proxy isn't resolving my kellnr instance's hostname. I can look into that myself. :)
The logs that led me that that were these, when I tried a cargo build from a shell that we using the squid proxy:
crates-kellnr-1  | 2024-02-04T18:08:34.460860Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/num-traits
/num-traits-0.2.16.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.492042Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/utf8parse/
utf8parse-0.2.1.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.492020Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/taglib/tag
lib-1.0.0.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.493168Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/taglib-sys
/taglib-sys-1.0.0.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)
crates-kellnr-1  | 2024-02-04T18:08:34.496635Z ERROR registry::cratesio_api: Failed to download crate from crates.io: error sending request for url (https://static.crates.io/crates/quote/quot
e-1.0.33.crate): error trying to connect: tcp connect error: Cannot assign requested address (os error 99)

I unset HTTPS_PROXY and unset HTTP_PROXY, then tried cargo build again, and this time it worked.
Thanks for you help, but the problem does appear to be with my own networking.

authors: kemitix secana

repo: kellnr/kellnr


text:
Sensor data doesn't update after set time

I am using a TI gas-gauge which is a battery sensor, as in, it reports battery voltage, current, temp etc. The sensor works fine, as I have a working C code. Trying to port it to nodejs. An initial run with node-i2c gives me the results I am hoping for. Although, I haven't been able to update the results continuously.
I even tried modifying the accel.coffee example for my sensor, which now looks like this: https://gist.github.com/chintanp/c8e1ad362eb9d99c30c7
As you can see in the code, it has a this.wire.read ... inside a setTimeout which should get me the sensor readings every 100 ms, or atleast this is what I am trying to achieve. What happens right now, is the code prints the sensor value correctly, once, and then just sits there without exiting, or re-printing etc. I have tried putting the wire.read code in a while(true) , for(;;) to create an infinite loop type call, but to no avail. This may not be a node-i2c issue, just my bad nodejs.
Anyway, how can I get this working ?

Closed without a comment ? Hey, some love would go a long way.

Project issues aren't for debugging you code. Please use stackoverflow or other services for code help.

authors: chintanp kelly

license_source: bigquery


text:
Added "New Branch" command

I think having a "New Branch" command is helpful, especially when paired up with the existing "Change Branch" command.

+1 Works like a charm.

authors: fesplugas joshuacc


text:
installed failed

i used package manager to install. but the file is not lastest. so i git clone the project. and put it to packages fold. but it not work.

i changed the sublime-package file to zip file. and update the code to lastest (because chinese char problem). then chaged it to sublime-package file. but it still not work

I'd hypothesize that you might be placing things in the wrong folder. Check out http://sublimetext.info/docs/en/extensibility/packages.html for more details, there.

authors: ckrad kemayo

repo: kemayo/sublime-text-git

license: mit


text:
Denoland deploy

Would it be possible to have this added to the denoland registry?
This would involve adding a webhook to this module, which would then publish the typescript source.
Details are listed here: https://deno.land/x

Using an import map, this polyfill can be utilised directly through GitHub:
{
  "imports": {
    "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern.ts",
    "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-utils": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-utils.ts",
    "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern.interfaces": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern.interfaces.ts",
    "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/path-to-regex-modified": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/path-to-regex-modified.ts",
    "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern-parser": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/url-pattern-parser.ts",
    "urlpattern-polyfill": "https://raw.githubusercontent.com/kenchris/urlpattern-polyfill/main/src/index.ts",
  }
}

This would be similar if it was deployed to deno.land unless these typescript files were process further to include extensions for deployment.

Ignoring the later failing jobs in these actions, we can see this code running across deno, node, webkit, chrome, and firefox:
https://github.com/virtualstate/app-history/blob/7171f6aea0e26847525ff65796b96447a52e4169/src/tests/examples/url-pattern.ts#L12-L21
appHistory.addEventListener("navigate", ({ destination }) => {
        const identifiedTest = new URLPattern({
            pathname: "/test/:id"
        });
        if (identifiedTest.test({ pathname: destination.url })) {
            body.innerHTML = destination.getState<{ innerHTML: string }>().innerHTML;
        } else {
            throw new Error(unexpectedPage);
        }
    });

Running the tests we can see the matcher is working:
START  urlPatternExample
Updated window pathname to /test/1
Updated window pathname to /test/2
PASS   urlPatternExample

Node Test - Uses native node.js resolution + yarn/npm
Deno Test - Uses the above import map
Chrome Test - Uses skypack CDN variant of package)
WebKit Test - Uses rollup, no import map support
Firefox Test  - Uses rollup, no import map support

I don't know much about deno land or how to publish it there. Could you share instructions?

Now that your module that is published to npm with exports, it is also directly compatible with skypack (maybe it was before too?)
I found that I can now just use the import map:
{
  "imports": {
    "urlpattern-polyfill": "https://cdn.skypack.dev/urlpattern-polyfill"
  }
}

However some might still want to access from deno.land, here are steps to publish to the deno.land registry:

Go to https://deno.land/x
Click "Publish Module"

Add a module name

Add a subdirectory, src/ here is usable because your source is typescript, deno can directly utilise it

Follow these steps to add the webhook to this repository:

I think the problem here would be though... the import map still will be a bit messy because of deno's requirement for extensions to be present for exports, while this isn't common practice when writing typescript
Once deployed the import map would probably look something like:
{
  "imports": {
    "https://deno.land/x/urlpattern_polyfill/url-pattern": "https://deno.land/x/urlpattern_polyfill/url-pattern.ts",
    "https://deno.land/x/urlpattern_polyfill/url-utils": "https://deno.land/x/urlpattern_polyfill/url-utils.ts",
    "https://deno.land/x/urlpattern_polyfill/url-pattern.interfaces": "https://deno.land/x/urlpattern_polyfill/url-pattern.interfaces.ts",
    "https://deno.land/x/urlpattern_polyfill/path-to-regex-modified": "https://deno.land/x/urlpattern_polyfill/path-to-regex-modified.ts",
    "https://deno.land/x/urlpattern_polyfill/url-pattern-parser": "https://deno.land/x/urlpattern_polyfill/url-pattern-parser.ts",
    "urlpattern-polyfill": "https://deno.land/x/urlpattern_polyfill"
  }
}

Even then, I'm not sure how deno's resolution exactly works, and it might rely on the redirected to url for this individual mapping, meaning possibly this is the required import map with version pinning included:
{
  "imports": {
    "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern.ts",
    "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-utils": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-utils.ts",
    "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern.interfaces": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern.interfaces.ts",
    "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/path-to-regex-modified": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/path-to-regex-modified.ts",
    "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern-parser": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2/url-pattern-parser.ts",
    "urlpattern-polyfill": "https://deno.land/x/urlpattern_polyfill@v1.0.0-rc2"
  }
}

TLDR seems like skypack is a better goto here, no additional steps required there.

Why do you need it in Deno? Deno supports URLPattern natively now

Ha! Well, I guess I could work a local polyfill file to detect globalThis.URLPattern exists!
I'm writing code that is compatible across all platforms, so using the polyfill is a must for others like node or the browser. I would have expected this polyfill to eventually provide the global where it is present.

I see. That is tracked in https://github.com/kenchris/urlpattern-polyfill/issues/47 so closing this one

authors: fabiancook kenchris

repo: kenchris/urlpattern-polyfill


text:
Slicer doesn't handle folder structure good

With OctoPrint 1.3.0 a possibility to create folders inside the upload folder was introduced.
When you create a folder and and enter it, then upload a .stl, the slicer plugin gives you a wrong output path. It shows something like "Vases/Vase_1.gco". This will  result in the creation of a file called "VasesVase_1.gco" in the currently active folder.
Side effect of this problem is that the Alalysis is not performed afterwards. I think this is related to the wrong creation path/filename.
This will result in a gcode file which has no proper metadata and is missing filament/volume properties. Plugins which depend on this information like the History plugin and the Costs plugin will fail.

Darn, directly after opening this issue I see that my plugin is still at 0.8.1, not at 0.8.3. I will check back later when I get it updated.

Darn, directly after opening this issue I see that my plugin is still at 0.8.1, not at 0.8.3. I will check back later when I get it updated.

Solved, sorry for the confusion :)

Solved, sorry for the confusion :)

Glad that you figured this out!

Glad that you figured this out!

authors: bizziebis kennethjiang

repo: kennethjiang/OctoPrint-Slicer


text:
pipfile importing (work in progress)

#327

will merge once tests pass

repo: kennethreitz/pipenv


text:
utils: let select_proxy not raise an exception when url has no hostname

Fixes #3131.

While we're here, we should probably also handle the possibility that there's no scheme in the URL as well.

scheme defaults to '', though. Well, more or less:
The scheme argument gives the default addressing scheme, to be used only if the URL does not specify one. It should be the same type (text or bytes) as urlstring, except that the default value '' is always allowed, and is automatically converted to b'' if appropriate.

Urgh, urlparse is such an inconsistent function. Good spot.

Thanks! :sparkles: :cake: :sparkles:

authors: Lukasa chipaca

repo: kennethreitz/requests


text:
Test that the readme renders in CI.

Resolves #4030.

Codecov Report

Merging #4033 into master will decrease coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4033      +/-   ##
==========================================
- Coverage   89.74%   89.53%   -0.21%
==========================================
  Files          15       15
  Lines        1940     1940
==========================================
- Hits         1741     1737       -4
- Misses        199      203       +4

Impacted Files
Coverage Δ

...es/urllib3/packages/ssl_match_hostname/__init__.py
83.33% <0%> (-10%)
:arrow_down:

requests/sessions.py
93.59% <0%> (-0.36%)
:arrow_down:

Continue to review full report at Codecov.

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

Merge this when everything else is ✔

authors: Lukasa codecov-io sigmavirus24


text:
lt, gt chars parsing inside a tag

Is it correct that when using sanitize.HTML the HTML like
1 < 2
 won't be parsed accurately?

What is accurately? What do you see, and what do you expect to see?

Sanitizing
1 < 2
 I'm getting 1  (with a space after the number) and I want to get 1 < 2. That's because the parser ignores everything after the < char even if it's not a HTML-tag.

I'm not sure that's valid html, you're supposed to escape less than signs (in html 5 at least). If you try validating this html here:
<!DOCTYPE html>

<title>asdf</title>

1 < 2

https://validator.w3.org/#validate_by_input
It will fail. It's hard for the parser to know if this is the start of a tag, or a less than sign, so the entity would be better. Browsers may try to work around it as they're used to broken html, but I would try to fix the html.
You could pre-process it by searching for ' < ' and replacing with ' < ', but I think I'd rather not do that in sanitize.

authors: iharsuvorau kennygrant

repo: kennygrant/sanitize


text:
[Bug] Cisco Nexus profile CPU oid erratic and does not match up to other tools

Currently polling against 1.3.6.1.4.1.9.9.305.1.1.1.0, consensus on various forums and data collected in NR shows this oid is very erratic as it is the point in time value with no time averaging.
Suggesting we remove this from the nexus profiles and fall back to the more typical 1.3.6.1.4.1.9.9.109.1.1.1.1.10

addressed in PR #128

authors: Mesverrum thezackm

repo: kentik/snmp-profiles


text:
APC PDU 7800/8800 Temperature and Humidity Sensor OID's missing

In working through the migration if our devices into New Relic we are finding that APC PDU Sensor OID's are missing from the profile(s).
Here are the OID's that we are specifically looking for:
PowerNet-MIB::rPDU2SensorTempHumidityStatusRelativeHumidity
PowerNet-MIB::rPDU2SensorTempHumidityStatusTempF

1.3.6.1.4.1.318.1.1.26.10 PowerNet-MIB (rPDU2)

resolved with #196

authors: araddas thezackm travisroberts-sf


text:
Update fortinet-fortigate.yml

Added SLA OID for fortigate

updated new file.


text:
Autoplay stops when touched on mobile/ipad

Hi folks, I have an issue I hope you can help me with.
I have a slider set to autoplay, and both pauseOnHover and pauseOnFocus set to false.
Here is my code:
$('.cc-slider-container').slick({
infinite: true,
slidesToShow: 1,
slidesToScroll: 1,
autoplay:true,
autoplaySpeed:5000,
pauseOnHover:false,
pauseOnFocus:false
});
This works as expected on desktop with autoplay even if its hovered. However on mobile (android) and ipad when I touch the slider to scroll the page the autoplay stops and never resumes.
anyone have any advice?
I am using slick version 1.8.0,
Thanks!

Same problem and same version!!
I've to set swipe to false to avoid this. Please fix this bug.
This is my code:
$('.slideshow').slick({
  autoplay: true,
  pauseOnHover: false,
  pauseOnFocus: false,
  prevArrow: '',
  nextArrow: ''
});

Looks to me more like a Feature than a bug. The user should have the ability to pause the autoplay by i.e. touching a slide. The autoplay should resume some time after. This seems to work.
Gesendet von Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 für Windows 10
Von: Francesco Giorgiomailto:notifications@github.com
Gesendet: Freitag, 2. Februar 2018 12:39
An: kenwheeler/slickmailto:slick@noreply.github.com
Cc: Subscribedmailto:subscribed@noreply.github.com
Betreff: Re: [kenwheeler/slick] Autoplay stops when touched on mobile/ipad (#3306)
Same problem and same version!!
I've to set swipe to false to avoid this. Please fix this bug.
This is my code:
$('.slideshow').slick({
autoplay: true,
pauseOnHover: false,
pauseOnFocus: false,
prevArrow: '',
nextArrow: ''
});
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kenwheeler/slick/issues/3306#issuecomment-362564026, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFmRU-V-jaIniqdI31OiGfUmnP5116DVks5tQvQHgaJpZM4RpjMs.

Looks to me more like a Feature than a bug. The user should have the ability to pause the autoplay by i.e. touching a slide. The autoplay should resume some time after. This seems to work.

No, you are confusing the pauseOnFocus and pauseOnHover property that do what you say.
Read carefully.
I've disabled both pauseOnFocus and pauseOnHover, and when I use Slick by touchscreen, like a smartphone, and I scroll the page touching the plugin (a vertical swipe), It stops and never restart. Not only It stops despite the two properties above disabled, but the autoplay doesn't work anymore.
I've to disable the swipe property to solve this, but I want to swipe my slideshow horizontally too so I need this property to be true.

Plus one. Having the same issue.

Can reproduce in Firefox with mobile emulation and touch simulation enabled. Unfortunately the slick swipe event does not handle vertical swipe (get “undefined” for direction the first time, then nothing thereafter) so it is not possible to manually restart the autoplay.
Gesendet von Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 für Windows 10
Von: Francesco Giorgiomailto:notifications@github.com
Gesendet: Montag, 5. Februar 2018 10:12
An: kenwheeler/slickmailto:slick@noreply.github.com
Cc: Dodd, Paul Sutton (UB)mailto:paul.dodd@ub.unibe.ch; Commentmailto:comment@noreply.github.com
Betreff: Re: [kenwheeler/slick] Autoplay stops when touched on mobile/ipad (#3306)
Looks to me more like a Feature than a bug. The user should have the ability to pause the autoplay by i.e. touching a slide. The autoplay should resume some time after. This seems to work.
No, you are confusing the pauseOnFocus and pauseOnHover property that do what you say.
Read carefully.
I've disabled both pauseOnFocus and pauseOnHover, and when I use Slick by touchscreen, like a smartphone, and I scroll the page touching the plugin (a vertical swipe), It stops and never restart. Not only It stops despite the two properties above disabled, but the autoplay doesn't work anymore.
I've to disable the swipe property to solve this, but I want to swipe my slideshow horizontally too so I need this property to be true.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/kenwheeler/slick/issues/3306#issuecomment-363023423, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFmRUx_-ywM5isjfVNAAfalGFQhCA5gKks5tRsX2gaJpZM4RpjMs.

I can't replicate this on FF up to date.

I'm having the same problem. When scroll vertically in that area

It seems to be reproduced in iOS UIWebView & WKWebView.

you have to add responsive params to your slider setup,
it works for me:
            responsive: [               {                 breakpoint: 960,                 settings: {                     waitForAnimate : false,                     pauseOnFocus   : false,                     pauseOnHover   : false,                     swipe : false                                   }               },             ]

@vol4ikman Your solution worked because of the swipe:false option, but if you set it to true (because you want the swipe to slide ability) the slider stops when you scroll the page vertically on touchscreen devices.
I'm trying with with the 1.8.1 version and the bug is still present ... and it's frustrating because the swipe option is totally useless.
@kenwheeler please fix this!!! Thank you

I have the same problem at my sliders on every page...
I have at config:
pauseOnHover: false,
pauseOnFocus: false,
pauseOnDotsHover: false,
But at safari on iPhone 5 when you are moving through slider it stops. autoplay is being off... When I swipe (swipe must be enabled! Disable it is not an option) then autoplay is working, again. But after a few movements with a finger at slick problems backs...
@kenwheeler +1 to fix that in next release :) Thanks! :)

+1 Same Problem here with android chrome and ios11.4.1 safari. Would be fantastic if it will be fixed.

Is there any fix for this?

+1 Android

Found this site
https://stackoverflow.com/questions/48402481/slick-slider-autoplay-stops-when-touched-on-mobile-tablet
With a snippet of code that fixed it for me:
$('.cc-slider-container').on('touchstart', e => {
$('.cc-slider-container').slick('slickPlay');
});
Changing cc-slide-container to your slick slider container

I had same problem. Some solution below but it is not perfectly works (through time)
$('slider').on(             'touchend touchcancel touchmove',             function() {                 $(this).slick('slickPlay');             }         );

+1 Android. I'm having the same issues. Samsung Galaxy S9, Android version 9, chrome latest public build.  As described above I turned off the pauseOn* settings leaving the touch swipe enabled.  Vertical swiping over the slick area pauses the autoplay and it never restarts.
Using the workaround that @mawkleonite mentioned works for me.  I registered the event handler after the slick initialization and it takes care of restarting the autoplay after I release from vertical touch swiping.
+1 to add a similar fix to an upcoming build.  Thanks for the nice carousel control. I was using bxslider before and was having issues with it.

I had the same issue, there's a workaround to it.
set autoplay to true and then listening to the scroll event, it will trigger once when the page scrolls and calls the next slide. This was a term solution until I find a better solution.
listenScrollEvent = () => {
if (this.props.autoplay) {
this.slideTime && clearTimeout(this.slideTime);
this.slideTime = setTimeout(() => {
if (window.pageYOffset < 100) {
this.slide(this.slideIndex + 1);
}
}, 3000);
}
};

Just use these extra hacky code to get it work again ;
// $('.images').slick({....});

$('.images').on('touchcancel touchmove', e => {
      $('.images').slick('slickPlay');
});

I had the same problem but It got fixed.
Here is my code:

  $(".fade").slick({
    dots: false,
    infinite: true,
    speed: 500,
    fade: true,
    cssEase: "linear",
    autoplay: true,
    autoplaySpeed: 1000,
    pauseOnHover: false,
    pauseOnFocus: false,
  });

I've added pauseOnHover & pauseOnFocus and now it's working fine on desktop, chrome inspect mobile view, and on the actual mobile device.

I made a not very good, but working solution:

First of all, we have to set next properties

var self = this
this.slides = this.$('.js-clients-slider__slides') // Slider
this.delay = 10 // Time per slide
this.slides.slick({
            autoplay: false,
            pauseOnFocus: false,
            pauseOnHover: false,
            speed: 400,
            infinite: true,
        });

Then we need to add a timer function

refresh: function () {
        this.delay-- // -1sec
        this.timer = setTimeout(this.refresh.bind(this), 1000)
        if (this.delay <= 0) {
            this.slides.slick('slickNext')
        }
    },

Next, start the timer
this.timer = setTimeout(this.refresh.bind(this), 1000)

Also, you need to reset the timer if you swipe manually

this.slides.on('afterChange', function(){
            self.delay = 10
        });

repo: kenwheeler/slick


text:
Checked List Items

I would like to switch the style of checked list items (text after a checkbox). On default the text of checked items doesn't changed. I would like to grey out the text and line-through.
Another style option is to disable small-caps on smaller headings.

This is not currently on my roadmap, but the quick (and fairly simple) solution is to use a CSS snippet. See forum post for instructions..

To grey out checked tasks in preview mode, the following snippet can be used:
https://forum.obsidian.md/t/dont-strike-through-nested-checkboxes-when-outer-checkbox-is-checked/8389/3
To strike through checked tasks, one can change text-decoration: none; to text-decoration: line-through;. I am not sure how to achieve both at the same time, though.
To disable small-caps on headers, the following can be used:
https://gist.github.com/wenlzhang/e80b53869c01a96659cee67b736e423d

Both options are now available in Style Settings as of 4.2.9

authors: 702573n kepano wenlzhang

repo: kepano/obsidian-minimal


text:
Init container not starting for blue/green deployments

The init container is not starting when trying to do a service name resolution in the init script (only happens for me in a blue/green deployment scenario). My feeling is that it can not resolve the service name since the Istio sidecar is not available at this point in time. But the istio sidecar will only start once all other init containers have done their job.
Please also find some discussion on this issue here: https://discuss.istio.io/t/k8s-istio-sidecar-injection-with-other-init-containers/845
Environment

Keptn Version (keptn version): 0.6.2
Istio Version. 1.5 (installed with the experimental option keptn install --istio-install-option=Reuse (installed with 0.6.1 and then upgraded to 0.6.2 later)

Affected Component

[ ] Docs
[ ] CLI
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] Helm
[x] Istio
[ ] Bridge
[ ] Gatekeeper
[ ] Datastore
[ ] REST API
[ ] eventbroker / distributor
[ ] jmeter

Describe the bug

I am pasting a fragment of my helm chart here:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: loadgenerator
spec:
  replicas: {{ .Values.replicaCount }}
  selector:
    matchLabels:
      app: loadgenerator
  replicas: 1
  template:
    metadata:
      labels:
        app: loadgenerator
      annotations:
        sidecar.istio.io/inject: "true"
    spec:
      terminationGracePeriodSeconds: 5
      imagePullSecrets:
      - name: regcred
      restartPolicy: Always
      # initContainers:
      # - name: wait-frontend
      #   image: alpine:3.6
      #   command: ['sh', '-c', 'set -x;  apk add --no-cache curl &&
      #     until timeout -t 2 curl -f "http://${FRONTEND_ADDR}"; do
      #       echo "waiting for http://${FRONTEND_ADDR}";
      #       sleep 2;
      #     done;']
      #   env:
      #   - name: FRONTEND_ADDR
      #     value: "frontend:80"
      containers:
      - name: server
        image: "{{ .Values.image }}"
        env:
        - name: DT_CUSTOM_PROP
          value: "keptn_project={{ .Values.keptn.project }} keptn_service={{ .Values.keptn.service }} keptn_stage={{ .Values.keptn.stage }} keptn_deployment={{ .Values.keptn.deployment }}"
        - name: FRONTEND_ADDR
          value: "frontend:80"
        - name: USERS
          value: "10"
        resources:
          requests:
            cpu: 300m
            memory: 256Mi
          limits:
            cpu: 500m
            memory: 512Mi

The part that is commented out is the problematic one - it won't ever finish since the service can not be accessed. Once the part is removed (like it did in this example) the server container is working fine (please note that it uses the exact same FRONTEND_ADDR) but at this point istio is already available.

AFAIK this is a known issue of Istio.
Right now this prevents people from onboarding services that use init containers with Keptn. There is no work-around available.

This issue cannot be solved on the Keptn side. It is a problem of Istio.

repo: keptn/keptn


text:
go-utils: Deprecate event-broker, introduce better error handling for failed SendingCloudEvents

For Keptn 0.8.0, do we still need event-broker as a config option in go-utils (in keptnOptions)?
As far as I know we are not using event-broker anymore, but go-utils still refers to it as a Keptn Configuration Option and uses it somehow...
I just ran into the problem that my cloudevents would not appear in Keptn, and the reason was that I have set eventbroker in my service.yaml manifest to
          env:
            - name: EVENTBROKER
              value: 'http://event-broker/keptn'

Also, I did not get an error message when using keptnHandler.SendCloudEvent.

Clean-up task:

[ ] Please check the manifests of keptn/keptn whether there is an env for the event broker. If there is, please remove it.

Clean-up task:

[ ] Please check the manifests of keptn/keptn whether there is an env for the event broker. If there is, please remove it.

authors: christian-kreuzberger-dtx johannes-b


text:
The rollback of blue/green deployment following a pitometer 'fail' status fails to find the istio-virtual-service YAML file

Describe the bug
The rollback of blue/green deployment following a pitometer 'fail' status fails to find the istio-virtual-service YAML file, thus stopping the "evaluation_done" pipeline
To Reproduce
Failure is because the YAML files for the keptn project are in "camelCase" and the jenkins job is looking for actual name.  In my scenario the service names is "front-end".   Project Yaml his istio-virtual-service-frontEnd.yaml but Jenkins job looking for istio-virtual-service-front-end.yaml

run a build where the pitometer result is a fail.  Here is sample message.

{"keptnContext":"f5cddaf3-120b-4bd0-be4b-0e1b689ac704","logLevel":"INFO","message":"Sending event: {\"id\":\"e1fb220a-180a-46a3-af46-f0bbeb10e577\",\"specversion\":\"0.2\",\"time\":\"2019-04-26T12:58:57+00:00\",\"datacontenttype\":\"application/json\",\"shkeptncontext\":\"f5cddaf3-120b-4bd0-be4b-0e1b689ac704\",\"data\":{\"githuborg\":\"jahn-keptn-orders\",\"project\":\"orders-project\",\"deploymentstrategy\":\"blue_green_service\",\"stage\":\"staging\",\"service\":\"front-end\",\"image\":\"10.23.246.81:5000/orders-registry/front-end\",\"tag\":\"1-3\",\"evaluationpassed\":false},\"type\":\"sh.keptn.events.evaluation-done\"}","keptnService":"pitometer-service"}

the "evaluation_done" jenkins job runs.  It then attempts to update the manifest file and can't find it, thus failing the job.

+ git checkout staging
Branch 'staging' set up to track remote branch 'staging' from 'origin'.
Switched to a new branch 'staging'
[Pipeline] sh
+ cd orders-project
+ sed -i 's#weight: 0#weight: swap_100#' helm-chart/templates/istio-virtual-service-front-end.yaml
sed: helm-chart/templates/istio-virtual-service-front-end.yaml: No such file or directory

Expected behavior
Job will find the YAML file for the service.
Screenshots

Environment
Using git clone --branch release-0.2.x https://github.com/keptn/keptn as of 4-25-2019
Additional context
Add any other context about the problem here.

Before working on this issue, I will work on #295 since then it is easier to finish this one.

The upcoming release of the jenkins-service can deal with service names that contain a hyphen. For example, carts-service > Log file from "evaluation_done" pipeline:
Switched to a new branch 'staging'
[Pipeline] sh
+ cd sockshopxy
+ sed -i 's#weight: 0#weight: swap_100#' helm-chart/templates/carts-service-istio-virtual-service.yaml
[Pipeline] sh
+ cd sockshopxy
+ sed -i 's#weight: 100#weight: 0#' helm-chart/templates/carts-service-istio-virtual-service.yaml
[Pipeline] sh
+ cd sockshopxy
+ sed -i 's#weight: swap_100#weight: 100#' helm-chart/templates/carts-service-istio-virtual-service.yaml

authors: johannes-b robertjahn


text:
Release 0.8.4-hotfix1

Create a hotfix release for 0.8.4 that incorporates the following Issue:

#4476 (PR: https://github.com/keptn/keptn/pull/4481 )

Unfortunately the version 0.8.4-hotfix1 is a bad choice, as it suggests that it is a pre-release and that 0.8.4 is newer.
See this table for comparison:

Due to this, we are presenting the user a message when installing 0.8.4-hotfix1 in bridge:

Since there is no solution to this problem, the team decided to deliver the bugfix with version number 0.8.5 #4527

authors: christian-kreuzberger-dtx warber


text:
#957 add automated tests for pull requests

*Work in progress

Changed file permission of several shell scripts (chmod +x)
Restructured the way the travis pipeline works
Less code = better
$TRAVIS_COMMIT_RANGE does not work for git commit --amend and force pushing - had to adapt the git diff command for that
Less tags are now pushed to dockerhub (to prevent tag-spamming)
Some basic tests should now also work for external contributors

This PR is partially irrelevant now, as we have restructured tests within travis-ci. I will close this PR and create a new one once this is ready.

Closing this (stale PR)


text:
Contributing to Keras Core

Keras Core is a high-velocity open-source project. We welcome contributions! Here's what you can do:
Take up of these open items:
Add scan operation
Add scan op in keras_core/ops/core.py, following the same API as the JAX version.
Add solve operation
Add solve op in keras_core/ops/math.py, following the same API as this function.
[Assigned] Add erf operation
Add erf op in keras_core/ops/math.py.
We'd like to add it as a backend-agnostic op in Keras Core. Here's a draft PR you can use a starting point.
[Assigned] Convert TF Discretization preprocessing layer to a backend-agnostic implementation
Right now, the Discretization layer is implemented in TensorFlow. However, it can be implemented via a backend-native implementation.
Note: assigned to @divyashreepathihalli.
Check out TODOs
There are various TODOs in the codebase. You can do a quick search (e.g. grep "TODO" keras_core -r) and see if anything looks interesting to you. Make sure to ask in this thread before starting work on any item!
Increase test coverage
Keras Core doesn't have 100% code coverage in unit tests just yet. You can try to run a code coverage tool like codecov and see if there are any unit tests you could add to improve Keras Core.
Convert an example from keras.io to Keras Core
keras.io/examples offers many great tutorials, but they're based on tf.keras. We'd like to bring over in the shiny new world of multi-framework ML.
There are two stages of conversion: 1. Converting a tf.keras example so that it can run on Keras Core with the TF backend. 2. Converting a tf.keras example so that it can run on Keras Core with any backend.
See detailed instructions here to learn more about the process.
Bring new pretrained model implementations to KerasCV and KerasNLP
The Keras ecosystem packages KerasCV and KerasNLP are looking for contributors!
If you'd like to port a pretrained model implementation to the Keras Core ecosystem, these packages are great projects to join.

Taking up the Moving Dataset utils task as a priority! Should I make a draft PR?

Taking up the Moving Dataset utils task as a priority! Should I make a draft PR?

No need for a draft -- you can just send the PR when you have something you want a review on. Thank you!

Some repositories invite contributors as collaborators when they are firstly created, will this happen in keras-core?
cc: @fchollet

@fchollet regarding dataset utils, since all three frameworks tensorflow , torch and jax have their own data-loading modules or have specific classes to provide this utilities, so since it is relying on tf.keras can only accept either tf.Dataset or regular python structures as of now, so dropping it means that we either support similar logic for individual framework or we accept generic structures + framework specific data-holder and convert it to a unified keras data-holder and then perform similar operations.
since in first option we import framework specific modules and built on top but these will stay in keras.backend but in option two we we don't need to touch keras.backend' we only made changes to  keras.utils`. Can you please let me know your thoughts on this. 😊
@suvadityamuk can please also share your thoughts in which direction you are choosing. 😊

@asingh9530
I'm currently looking into trying to move the tf.keras-specific data utils from the original keras-team/keras space to this space, with all implementations intact. The only thing I'm adding is support to handle torch.utils.data.Dataset along with it, since that's a major focus.

@suvadityamuk Thanks for responding, since this will be a big change let's track it in a new issue with specific changes needed to be done since even in keras the utils are for tf.Dataset let's say Iterators, batched etc.  How about I'll add you there and work on this.

Hello,
I am rather new w.r.t contributions, so I may ask a rather silly question : are publicly exported functions those decorated with @keras_core_export ?

so I may ask a rather silly question : are publicly exported functions those decorated with @keras_core_export

Yes, that's right. The public API is programmatically generated using those decorators.

Hi @fchollet,
I checked some of the layer unit tests and have some questions. The data is generated randomly:
https://github.com/keras-team/keras-core/blob/b4e6aace85043de5f465d836ef131bca5edb636f/keras_core/layers/convolutional/depthwise_conv_test.py#L196-L213
Since the data is random, how one can hard-code the expected value? Is it OK to reproduce the expected result using for loops? I guess that will look very bad, too many nested loops for a convolution.

Can someone help me with keras_core/layers/layer.py:439:        # TODO: handle layout.What does it mean to handle the layout?

@fchollet bump

Can someone help me with keras_core/layers/layer.py:439: # TODO: handle layout.What does it mean to handle the layout?

This was referring to the implementation of a future distribution API -- but this has been handled since. Nothing to do here.

Hi,
I am willing to take a shot at the solve operation implementation, still setting up a development environment. One clarification question. What is the error value for a matrix input that is singular (i.e., no inverse matrix exists), not full rank, or not square? To be sure, I look forward to contributing as a hobby and will circle back when I have something satisfactory for review.
Thanks,
bf

Hello @fchollet,
I wanted to reach out and update you on the progress I've made with the ERF function. I've made significant changes to the code and have already uploaded them to my forked repository. I'm confident that these updates will improve the function's performance, but please take a look and let me know if there's anything else you'd like me to do.
1.) Changes to keras-core/ops/math.py
https://github.com/sqali/keras-core/blob/6485433201e8a935f462aca191bc37dd7cf00c30/keras_core/ops/math.py#L934-L966
2.) Changes to keras-core/ops/math_test.py
https://github.com/sqali/keras-core/blob/6485433201e8a935f462aca191bc37dd7cf00c30/keras_core/ops/math_test.py#L840-L868
3.) Changes to keras-core/backend/tensorflow/math.py
https://github.com/sqali/keras-core/blob/6485433201e8a935f462aca191bc37dd7cf00c30/keras_core/backend/tensorflow/math.py#L244-L245

I am willing to take a shot at the solve operation implementation, still setting up a development environment. One clarification question. What is the error value for a matrix input that is singular (i.e., no inverse matrix exists), not full rank, or not square? To be sure, I look forward to contributing as a hobby and will circle back when I have something satisfactory for review.

solve exists in all 3 backends, so most likely we just want to wrap it. You can check what the error is for a singular matrix for each backend. We should raise a similar error.

I wanted to reach out and update you on the progress I've made with the ERF function. I've made significant changes to the code and have already uploaded them to my forked repository. I'm confident that these updates will improve the function's performance, but please take a look and let me know if there's anything else you'd like me to do.

It will also need to be implemented for the JAX, torch, and numpy backends. Can you open a PR? We can carry on on the PR.

Sure, I will do that. Thanks.

@fchollet , I am interested in contributing to Keras Core.  I went through the description above and interested to work on this item "Convert an example from keras.io to Keras Core". Could you please guide me on the steps to follow . Do I need to raise a new pull request.
Thank you

@fchollet I can take up erf implementation, any specific condition you want in the implementation if not I will follow implementation guideline of rest of operations.

I can take up the scan op/operation in jax

Hi @asingh9530 ,
I have already opened a PR and working on it. Thanks.

Hi people,
I think I took care of most of the necessary changes. Still struggling on how to run a unit test locally with respect to my forked branch. Happy to open a PR if this is helpful. In addition, please advise on how to run a test, import a built whl binary into a Jupyter notebook, and next steps for agnostic solve.
Thanks,
bf

@fchollet I'm working on the keras_core/saving/saving_lib.py.   TODO: if h5 filepath is remote, create the file in a temporary directory     then upload it. Should I use the requests library to posts the file on the required remote filepath ?

I'm working on the keras_core/saving/saving_lib.py.   TODO: if h5 filepath is remote, create the file in a temporary directory then upload it. Should I use the requests library to posts the file on the required remote filepath ?

Please only use Python stdlib utilities for this. Thanks!

I am interested in contributing to Keras Core. I went through the description above and interested to work on this item "Convert an example from keras.io to Keras Core". Could you please guide me on the steps to follow . Do I need to raise a new pull request.

Here's the full context and the process to follow: https://github.com/keras-team/keras-core/issues/222

I can take up the scan op/operation in jax

Sure, sounds good! It will need to be implemented in all 4 backends though.

I think I took care of most of the necessary changes. Still struggling on how to run a unit test locally with respect to my forked branch. Happy to open a PR if this is helpful. In addition, please advise on how to run a test, import a built whl binary into a Jupyter notebook, and next steps for agnostic solve.

It will need much more extensive unit testing. You can run unit tests locally via pytest.

I'm working on the keras_core/saving/saving_lib.py.   TODO: if h5 filepath is remote, create the file in a temporary directory then upload it. Should I use the requests library to posts the file on the required remote filepath ?

Please only use Python stdlib utilities for this. Thanks!

thanks, last question what can be a good example for remote file path.

thanks, last question what can be a good example for remote file path.

Something like gcs://...

I am interested in contributing to Keras Core. I went through the description above and interested to work on this item "Convert an example from keras.io to Keras Core". Could you please guide me on the steps to follow . Do I need to raise a new pull request.

Here's the full context and the process to follow: #222

Thank you. I will check the link and start working

I could port some the listed examples from tf.keras to Keras Core. Out of the outstanding examples, are there any, in particular, you would first like to see ported to Keras Core?

Request to kindly create  an Excel/ some tracking  on the examples each of us are working on so that there is no repetition of tasks on example
Thank you

authors: BenjiFischman Frightera asingh9530 dranaivo fchollet jayaBalaR pranav-vempati pranavvp16 sqali suvadityamuk vulkomilev

repo: keras-team/keras-core


text:
TypeError: 'module' object is not callable

System information

Windows 10
TensorFlow backend (yes / no):  yes
TensorFlow version:  1.14.0
Keras version:  2.24
Python version:  3.6
CUDA/cuDNN version:  10
GPU model and memory:  gtx 1050 ti

Describe the current behavior
I installed tensoflow and keras via conda. Then i tried to run this code:
import tensorflow as tf
import keras
import numpy as np

model = keras.Sequential([keras.layers(units=1, input_shape=[1])])

model.compile(optimizer="sgd", loss="mean_squared_error")

x = np.array([-1, 0, 1, 2, 3, 4])
y = np.array([-3, -1, 1, 3, 5, 7])

model.fit(x, y, epochs=500)

print(model.predict([10]))`

When i run this code I get the error:
Using TensorFlow backend.
Traceback (most recent call last):
  File "C:/Users/xxx/PycharmProjects/Workspace/tensorflow/hello_world_of_nn.py", line 5, in <module>
    model = keras.Sequential([keras.layers(units=1, input_shape=[1])])
TypeError: 'module' object is not callable

When i try this:
python -c 'import keras as k; print(k.__version__)'
I get the error:
 C:\Users\xxx>python -c 'import keras as k; print(k.__version__)'   File "<string>", line 1     'import           ^ SyntaxError: EOL while scanning string literal

import tensorflow as tf
import keras
import numpy as np
model = keras.models.Sequential([keras.layers.Dense(units=1, input_shape=[1])])
model.compile(optimizer="sgd", loss="mean_squared_error")
x = np.array([-1, 0, 1, 2, 3, 4])
y = np.array([-3, -1, 1, 3, 5, 7])
model.fit(x, y, epochs=500)
print(model.predict([10]))

repo: keras-team/keras


text:
steps variable usage in lstm_text_generation.py file

`# cut the text in semi-redundant sequences of maxlen characters
maxlen = 40
step = 3
sentences = []
next_chars = []
for i in range(0, len(text) - maxlen, step):
sentences.append(text[i: i + maxlen])
next_chars.append(text[i + maxlen])
print('nb sequences:', len(sentences))
print('Vectorization...')
x = np.zeros((len(sentences), maxlen, len(chars)), dtype=np.bool)
y = np.zeros((len(sentences), len(chars)), dtype=np.bool)
for i, sentence in enumerate(sentences):
for t, char in enumerate(sentence):
x[i, t, char_indices[char]] = 1
y[i, char_indices[next_chars[i]]] = 1
`
why are we using steps =3 in above code

@RiyazAina-DeepML  Moving this issue to closed status as there has been no recent activity, in case you still face the error please create a new issue.Thanks!

authors: RiyazAina-DeepML sushreebarsa