Add to favourites option shown on files

Description
When opening the context menu on a file there's an Add to favourites option witch doesn't work
Steps To Reproduce

Right click on a file

Steps to fix

Remove Add to favourites option on files

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.1194
Log file

It works but we don't display them in Files (you can check File Explorer), it's currently limited to the preview builds of Windows so we're waiting for it to be released before creating a widget.


Adjust min,max times for dumps after job finishes

Summary
We need to adjust dump interval with the actual timestamps we read from meta files.

Curious, what happens if we don't do this?

It can mislead the user if there is let's say no data. It's an edge case, or rather unexpected scenario. But we should have the best possible data on those times.


fix: Issues and Enhancements in the camera widget

Description
1): Fix on various issues on a camera widget

Stretching of images after click.
Camera controls not visible when placed on a white background
When you drag the camera widget for the first time and grant access, it doesn't show the devices
list in the dropdown. It works after you delete and add it again.

2): Enhance UX/Feature

Action should be updated to onImageSave than onImageCapture. We will retain the onImageCapture functionality in our code so that if users need it we can enable it.
For video also we need an action for onVideoSave so that user can confirm the video they want to send. We CAN retain the onVideoStart and onVideoStop functionality but let's not expose the controls right now.
Change the mode name to "Image" instead of "Camera" in the dropdown.
Always keep the camera dimensions intact on resize
@dilippitchika , @Pranay105 , You guys can find the PR for documentation change here : https://github.com/appsmithorg/appsmith-docs/pull/335

Fixes #10077 #10126
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
This change requires a documentation update

How Has This Been Tested?

Test A
Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/10077-camera-issue-enhance

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.44 (0.01)
37 (0.01)
35.29 (-0.01)
55.81 (0)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

:green_circle:
app/client/src/widgets/CameraWidget/component/index.tsx
11.01 (0.24)
15.09 (0.37)
0 (0)
12.87 (0.19)

:red_circle:
app/client/src/widgets/CameraWidget/widget/index.tsx
28.92 (-3.08)
0 (0)
33.33 (-9.53)
28.4 (-3.11)

@wmdev0808 please make some efforts towards making the PR description better along with the title, Making it descriptive for the reviewer is important

@wmdev0808 have you made the changes in the documentation? Can you link it here and tag @dilippitchika & @Pranay105

@wmdev0808 have you made the changes in the documentation? Can you link it here and tag @dilippitchika & @Pranay105

done

@wmdev0808 great work with the PR description. ❤

/ok-to-test sha=a0b37bc

@wmdev0808 Tested this PR and the issue #10126 and #10077 are working as expected

/ok-to-test sha=efa7b07

@wmdev0808 related test is failing. Please check.

@wmdev0808 related test is failing. Please check.

It is not specific to this test case

/ok-to-test sha=92ee419

/ok-to-test sha=0bd157e

/ok-to-test sha=dd4c8ff

/ok-to-test sha=aee92b6


[HW]

Name: DEEPAK RS
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/deepak-rs-03706abb/
Attach the homework step I screenshots below:

![Uploading Capture-9.PNG…]()
Attach the homework step II screenshots below:

Hey DEEPAK RS, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/264zz_DFRsWL7z9RUzAGWA

😁


Menu provides no way of going back

The menu on HGVS-nomenclature.org provides no way of going back.
E.g.,

Open HGVS-nomenclature.org,
Open the menu,
Click on "Recommendations",
You can now not go back to the main menu, you'll need to reload the page.
Click an item, e.g., "DNA" -> "deletion".
You can not use the menu to navigate to other parts of the site; you can only use it to navigate within the "DNA" menu tree.

Tested on FF 110 @ Ubuntu 22.04

(we might need a new label for website fixes; for now, I used "documentation fix")

This was fixed in 3fca4b7ca3bd9a0d75d7393ec4c0c676a2d53277


Why does the textile.jsonml function prepend the syntax tree with an "html" node?

Output then looks something like ["html", ["p", "hello world"]], which represents an HTML tree like

hello world

But this isn't valid HTML, you'd need a  tag and a  tag to contain all the other parse results. This is easy enough to correct by calling shift() on the output array, but I'm curious to understand why it prepends this html container in the first place.

JsonML has the limitation that it requires a single root node as a container†. Textile syntax, however, is not limited in this way.
Consider this Textile markup:
h1. heading

p. paragraph

Which should really translate to:
[ "h1", "heading" ],
[ "p", "paragraph" ]

But since the root needs to be a valid element, all the "block level" textile elements are wrapped in a container tag:
[ "html",
  [ "h1", "heading" ],
  [ "p", "paragraph" ]
]

The selection of html is completely arbitrary. Textile-js ignores this internally so there might be a case for changing it to something like a div to remove processing work for anyone using the .jsonml() function.

† At least, it was that way back when I originally wrote the library.

Thanks for the explanation!


Global average pooling fails if the Operator name has "Pool" inside

I ran into this issue when I was testing a converted model from ONNX. Since ONNX allows a node to have any name, if a GlobalAveragePool node's name contains the word "Pool", caffe2 checks for a kernel size parameter and fails.
The code which seems to be doing something wrong is here:
https://github.com/caffe2/caffe2/blob/master/caffe2/operators/conv_pool_op_base.h#L167
Reproducing code
import numpy as np
import os
import shutil
import onnx
import onnx_caffe2.frontend
from caffe2.proto import caffe2_pb2
from caffe2.python import model_helper, workspace, brew, utils

IN_DATA_NAME = "in_data"
OUT_DATA_NAME = "out_data"

model = model_helper.ModelHelper(name="gap_net")
# The following results in an error because the node name has the word "Pool" in it
brew.average_pool(model, IN_DATA_NAME, OUT_DATA_NAME, global_pooling=True, name="PoolPoolPool")
# The following works
#brew.average_pool(model, IN_DATA_NAME, OUT_DATA_NAME, global_pooling=True)

model.param_init_net.UniformFill([], IN_DATA_NAME, shape=(1,3,3,3), min=-2.0, max=2.0)
workspace.RunNetOnce(model.param_init_net)
id = workspace.FetchBlob(IN_DATA_NAME)
print(IN_DATA_NAME, id)
workspace.CreateNet(model.net)
workspace.RunNet(model.net)
b = workspace.FetchBlob(OUT_DATA_NAME)
print(OUT_DATA_NAME, b)
print("out shape", b.shape)
for c in id[0]:
    print(np.mean(c))

Results
When operator is named "PoolPoolPool"
$ python caffe2_bug.py
in_data [[[[-1.4755055   0.8291166   1.8095036 ]
   [-0.772043    0.8637898   1.1757474 ]
   [-0.07659233  0.74965596 -1.4103965 ]]

  [[ 1.4675004  -0.39934552 -1.7228949 ]
   [-1.3966541  -0.40833402 -0.9643401 ]
   [ 1.5508156  -1.6803277   0.6537442 ]]

  [[-0.15532112 -0.2408135  -1.3010323 ]
   [-1.0444076  -0.1672839   0.7210665 ]
   [-0.68532014  1.5852299   1.0893228 ]]]]
Traceback for operator 0 in network gap_net
/usr/local/caffe2/python/helpers/pooling.py:42
/usr/local/caffe2/python/brew.py:119
caffe2_bug.py:14
Traceback (most recent call last):
  File "caffe2_bug.py", line 22, in <module>
    workspace.CreateNet(model.net)
  File "/usr/local/caffe2/python/workspace.py", line 167, in CreateNet
    StringifyProto(net), overwrite,
  File "/usr/local/caffe2/python/workspace.py", line 193, in CallWithExceptionIntercept
    return func(*args, **kwargs)
RuntimeError: [enforce fail at conv_pool_op_base.h:176] kernel_[dim]. If you are doing convolution or pooling, you will need to set explicitly the kernel size.

When operator is not named
$ python caffe2_bug.py
in_data [[[[ 1.8542964   1.317266    0.935776  ]
   [-1.9163942  -0.15530694  1.7955503 ]
   [-0.70009923  1.8828702  -0.90508103]]

  [[-1.5479324  -0.69316816 -1.8525925 ]
   [ 1.2535133   0.6431527   0.5932145 ]
   [-0.76321626 -1.0862188  -0.8733362 ]]

  [[ 0.8466208  -0.04586458  0.4006784 ]
   [-0.4090197   1.4020386  -0.26248538]
   [-1.9751848   1.8272867  -1.7275488 ]]]]
out_data [[[[ 0.45654202]]

  [[-0.4807315 ]]

  [[ 0.00628013]]]]
out shape (1, 3, 1, 1)
0.4565419
-0.48073155
0.0062801307

It seems there are several tangled bug here. The code in conv_pool_op_base.h checks for operator_def.name() while it should be checking for operator_def.type(). We usually name our operators in lowercase, so the code that checks padding and access kernel size never ran. When it does run, it doesn't check if the pooling is global (and thus doesn't need kernel size). cc @Yangqing to decide how to deal with this code.

Ah this is probably because ConvPoolOpBase is a huge base class that is not that well tested...
We should probably monkey patch it (credit goes to @Maratyszcza ) - by fixing the name() calls to type() calls, and also check that global_pooling_ is not true (in which case we don't check the kernel size).


Achieve high accuracy for OTT-QA

jaydesen created the following on Jan 25:
OTT-QA leaderboard accuracy now is in the range of 20-35%. We need to have a table+text QA system that achieves an product level ready accuracy (>70%) for OTT-QA
Original issue: https://github.ibm.com/ai-foundation/PrimeQA/issues/13

@vishwajeetkumar93 : please update the status for this.


Need more explaination about the canary strategy

I tried create a new fresh github actions with deploy snippet like below
- name: "Deploy azure vote front"
  uses: Azure/k8s-deploy@v1
  timeout-minutes: 5
  with:
    namespace: ${{env.NAMESPACE}}
    manifests: |
      manifests/front.yml
      manifests/service.yml
    images: |
      ${{secrets.REGISTRY_URL}}/${{env.IMAGE_NAME}}:${{ github.sha }}
    imagepullsecrets: |
      acr-secret
    strategy: canary
    percentage: 50

front.yml already set replica to 2, but the result I get from AKS cluster only shows on I have canary deployment, no baseline deployment
k get pod -n=github
NAME                                       READY   STATUS    RESTARTS   AGE
azure-vote-back-7d6d77f4ff-c8zf2           1/1     Running   0          48s
azure-vote-front-canary-7ffd6884cd-nnq7j   1/1     Running   0          39s
Is it an expected behavior?

@sundargs2000 given that you've been working on the strategies part recently.. could you address this question?

@huangyingting if this is the first time you are deploying (ie. there are no azure-vote-front-* pods already), then you would only get '-canary' pods as there are no existing pods to make '-stable' pods to compare canary pods with. after you promote once and there are pods without any suffix, in the next run you would get both canary and stable pods.


add option to apply softmax to classifier score

Coverage increased (+0.03%) to 92.649% when pulling 025adffffaa9679d0d63306a6cc2d836d33a4e0c on softmax into c3ec456034fc02c453ad1c9df33c0caf5b6779da on develop.

Coverage increased (+0.04%) to 92.656% when pulling 025adffffaa9679d0d63306a6cc2d836d33a4e0c on softmax into c3ec456034fc02c453ad1c9df33c0caf5b6779da on develop.

LGTM :+1:


Fail reading svg file

Hello, I am trying to convert to png the attached SVG file with the following code :
const img = sharp("file.svg");
console.log(img);
img
.png()
.toFile("out/svg/test.png")
.then(function(info) {
console.log(info);
})
.catch(function(err) {
console.log(err);
})
It doesn't work, it seems to be an error when I inspect the sharp object :
input: {
failOnError: true,
limitInputPixels: 268402689,
sequentialRead: false,
file: 'out/svg/aleacity_fixed_fixed.svg'
}
FYI, I was used to doing this conversion with inkscape in command line.
This svg file is generated by a node program.
Thanks
Regards
file.zip

Hi, the sample SVG image renders as a PNG for me using sharp v0.28.3 on Linux:

What error are you seeing passed to the catch handler?

Hi, thanks for your reply.
Absolutely nothing is printed to the console in the catch handler.
Windows 10
node --version

v14.16.1

npm version

npm: '6.14.12',
node: '14.16.1',

Is there any trick to increase the verbosity ?
Thanks

@quiz7 Are you still experiencing this behaviour with the latest v0.29.0 release?

Works for me on OSX with sharp 0.29.1.

Closing due to inactivity but please feel free to reopen with more details if further help is required.


GSF IEF Meeting Agenda 2023-10-12

Time 11:30am (GMT) / 4:00pm (IST) - See the time in your timezone

Lead – @srini1978 (Microsoft)
Co-Lead @navveenb (Accenture)
PM – @jawache (GSF)

Antitrust Policy
Joint Development Foundation meetings may involve participation by industry competitors, and it is the intention of the Joint Development Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.
Roll Call
Please add 'Attended' to this issue during the meeting to denote attendance.
Any untracked attendees will be added by the GSF team below:
Agenda

[x] Press Record!

PRs

[ ] https://github.com/Green-Software-Foundation/ief/pull/190
[ ] https://github.com/Green-Software-Foundation/ief/pull/174
[ ] https://github.com/Green-Software-Foundation/ief/pull/191

Discussions

[ ] https://github.com/Green-Software-Foundation/ief/issues/171
[ ] https://github.com/Green-Software-Foundation/ief/issues/177
[ ] https://github.com/Green-Software-Foundation/ief/issues/149
[ ] https://github.com/Green-Software-Foundation/ief/issues/197

Issues

[ ] Discuss in-progress/blocked issues on project board: https://github.com/orgs/Green-Software-Foundation/projects/26/views/1
[ ] AOB

Attended

Attended

Attended

Attended

Attended

Attended

Srini:

Let's have this clearly as part of the spec, so people understand what to expect.
Standardized model documentation
cpu-util <-- this is in units.yaml
cpu-util-idle
cpu-util-dynamic

Gadhu:

If we are mandating units what if someone wants different units they can use a non-standard field name (but not have any guarantee of any protection from other people using the same name)

attended

closing as completed


Rejected errors fix links

PTAL

@thompiler I tried that and I get a 404. Just double checked. Am I doing something wrong?

@thompiler I tried that and I get a 404. Just double checked. Am I doing something wrong?

Oh hmm I'm sure I tested it. What exactly did you do to get the 404?

I left the change in place. You can test it.

@stuartmoore1023 I am not seeing a 404 in development. Can you check again?
 It's up to you since it's your PR.

@stuartmoore1023 I am not seeing anything odd. Can you please check again?


Fix to allow kubectl list CRDs

What this PR does / why we need it:
Changes CRD name from route-rules.config.istio.io to routerules.config.istio.io
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1107
Special notes for your reviewer:
Release note:

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Are you hesitant to touch istio/istio ? Is that why you are holding off on
going to the non dashed version?
On Wed, Aug 30, 2017 at 1:05 PM Kuat<EMAIL_ADDRESS>wrote:

/retest
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/pilot/pull/1144#issuecomment-326055863, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd9Rlhaffcto_hexUVS302AW94cDFks5sdZY9gaJpZM4PHoE4
.

--
~shriram

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f781d166d7159de4a3b00b7fe3f9865d09fbe232
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Abandoned


Post https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s: service "cert-manager-webhook" not found

Describe the bug:
I installed cert-manager in the kube-system namespace with this command helm install cert-manager jetstack/cert-manager --namespace kube-system -f values.yaml --wait and everything seemed fine. During the installation of Prometheus on the same cluster, I had problems in generating certificates for alert-manager inputs.
Here is the error I found in the cert-manager logs. I only changed the alertmanager domain for security.
kubectl get certificates le-prometheus-alertmanager-tls -o json Error from server: conversion webhook for &{map[apiVersion:cert-manager.io/v1alpha2 kind:Certificate metadata:map[creationTimestamp:2020-03-25T16:18:11Z generation:1 labels:map[app:prometheus chart:prometheus-11.0.3 component:alertmanager heritage:Helm release:prometheus] name:le-prometheus-alertmanager-tls namespace:kube-system ownerReferences:[map[apiVersion:extensions/v1beta1 blockOwnerDeletion:true controller:true kind:Ingress name:prometheus-alertmanager uid:a225d045-1e39-4238-9352-06af00638c87]] uid:e73287ca-6db4-4e74-8e93-675eebfc8dcb] spec:map[dnsNames:[alertmanager.example.com] issuerRef:map[group:cert-manager.io kind:ClusterIssuer name:letsencrypt-production] secretName:le-prometheus-alertmanager-tls] status:map[conditions:[map[lastTransitionTime:2020-03-25T16:18:12Z message:Waiting for CertificateRequest "le-prometheus-alertmanager-tls-1268665689" to complete reason:InProgress status:False type:Ready]]]]} failed: Post https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s: service "cert-manager-webhook" not found
From what I understand the problem is that the cert-manager tries to connect to webhook in the default namespace (cert-manager) instead of the one in which it was installed (kube-system).
Expected behavior:
I expect cert-manager to call the webhook in the correct namespace.
Steps to reproduce the bug:

Install cert-manager in kube-system with this command:
helm install cert-manager jetstack/cert-manager --namespace kube-system -f values.yaml --wait

Changed conf for values.yaml
extraArgs: --cluster-resource-namespace=kube-system ingressShim:   defaultIssuerName: "letsencrypt-production"   defaultIssuerKind: "ClusterIssuer"

Install Prometheus in kube-system with this command:
helm install prometheus stable/prometheus --namespace=kube-system -f values.yaml

Changed conf for values.yaml: all ingress to true with tls
Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.15.10-eks-bac369):
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): EKS
cert-manager version (e.g. v0.4.0): v0.14.1
Install method (e.g. helm or static manifests): helm

/kind bug

I found other people with the same problem
https://github.com/jetstack/cert-manager/issues/2732
https://github.com/jetstack/cert-manager/issues/2602

same

Currently this problem is because the namespace is hardcoded in the chart. Currently it is possible when you get the yaml and manually change all the namespaces to the namespace you want. It would be nice if the chart will support it.

The chart is actually okay, and does not hardcode the namespace. The issue here is that the CRD manifests also have to hardcode a namespace name, and the CRDs are not managed by the Helm chart and thus cannot be templated.
There's a number of places in the CRDs that make reference to the namespace cert-manager, including in spec.conversion as well as metadata.annotations - you'll need to make sure to adjust all of these in order to have this work. Alternatively, just deploying into the cert-manager namespace works easiest 😅
We're hoping to be able to improve this in future, but we require https://github.com/helm/helm/issues/7735 to be addressed before we can.

Why CRD can not use helm templates? Basically helm template | kubectl apply -f - where we could provide namespace?

It's made slightly trickier because we also generate the OpenAPI schema for the CRDs, which is patched in automatically by the controllergen tool from controller-tools: https://github.com/jetstack/cert-manager/blob/fbf2b3073da9622d30362fd054f9acd7a2dbb18f/hack/update-crds.sh#L42-L45
@meyskens worked on trying to get this generator to work against a CRD that includes Helm templating directives, and unfortunately it does not work (as it sees the YAML as misconfigured).
Either way, this is going to be an issue for us even if https://github.com/helm/helm/issues/7735 is addressed so we should come up with some solution to it. Potentially we could use Kustomize to 'overlay' the OpenAPI schema on top, as then the controller-gen tool could be pointed at an overlay that wouldn't contain any chart templating directives.
That would then mean part of the project is deployed with Kustomize and the other with Helm/kubectl, which is also not ideal. The other option would be to switch everything to a purely Kustomize based approach, but that's definitely a more drastic change and will probably cause quite a lot of pain for people, as there's a lot of Helm users out there 😅

Does anyone know any potential work around, or resolution for this error?

@holdenkilbride the only workaround that I can see is to manually edit the CRD before applying it to match your desidered namespace (ref: https://github.com/jetstack/cert-manager/issues/2752#issuecomment-605883456)

We're running into the same issue. If cert-manager is deployed to a different namespace the CRDs are not being deployed by the helm chart and the namespace is hardcoded. This is a real problem for CI/CD.

I have cert manager deployed to the "cert-manager" namespace and this issue still exists. I am unable to delete and describe resources.

Same issue. Installed to kube-system and cant use kubectl describe or get.

I was never trying to deploy to the kube-system namespace; just the default cert-manager namespace.

I want to install cert-manager to
namespace cert-manager-stage,
namespace cert-manager-prod, and so on.
I think you should fix this quickly.

I want to install cert-manager to
namespace cert-manager-stage,
namespace cert-manager-prod, and so on.
I think you should fix this quickly.

There should be only one cert manager per cluster. You can however install multiple Issuers in different namespaces

@boris-savic
one cert-manager per one cluster : is restriction and should be documented.
and anyway user can choose their namespace easily.

@Hokwang just read the documentation

Warning: You should not install multiple instances of cert-manager on a single cluster. This will lead to undefined behavior and you may be banned from providers such as Let’s Encrypt.

Ref: https://cert-manager.io/docs/installation/kubernetes/

Thanks @boris-savic, updating the CRDs like this allowed a stuck namespace deletion to finally terminate in my case.

I have cert manager deployed to the "cert-manager" namespace and this issue still exists. I am unable to delete and describe resources.

I am having similar problem ... using v0.14.2 ...
i.e. deploying cert-manager in the "cert-manager" namespace,
Using airship armada to helm install which forces use of "--name xyz" to helm,
Used 'Values.webhook.serviceName = xyz-cert-manager-webhook' to correct the dns names in certificate,
...
I can create issuer ... but on get, describe, etc. of issuer get the following error:
Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=Issuer failed: Post https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s: service "cert-manager-webhook" not found
Why is the wrong web hook dns name being used here ?
( the correct one is used when the issuer is created )

I have cert manager deployed to the "cert-manager" namespace and this issue still exists. I am unable to delete and describe resources.

I am having similar problem ... using v0.14.2 ...
i.e. deploying cert-manager in the "cert-manager" namespace,
Using airship armada to helm install which forces use of "--name xyz" to helm,
Used 'Values.webhook.serviceName = xyz-cert-manager-webhook' to correct the dns names in certificate,
...
I can create issuer ... but on get, describe, etc. of issuer get the following error:
Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=Issuer failed: Post https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s: service "cert-manager-webhook" not found
Why is the wrong web hook dns name being used here ?
( the correct one is used when the issuer is created )

FYI ... 0.15-alpha.0 fixed my problem

This has now been resolved with the new --set installCRDs=true option that can be used when installing the Helm chart in the latest (v0.15.0-alpha.X) versions. We are still in the processing of writing new installation docs to include info on this feature, but if you'd like to give it a go it should clear all this up 😄

Thank you @munnerz

vinay@pramukha:~$ kubectl get namespace
NAME                 STATUS   AGE
cert-manager         Active   9h
cert-manager-test    Active   2d1h
container-registry   Active   2d10h
default              Active   2d10h
ingress              Active   2d10h
kube-node-lease      Active   2d10h
kube-public          Active   2d10h
kube-system          Active   2d10h
kube-verify          Active   2d10h
kube-verify1         Active   2d5h
metallb-system       Active   2d10h
monitoring           Active   2d10h
nextcloud            Active   2d1h
vinay@pramukha:~$
vinay@pramukha:~$ kubectl get pods -A
NAMESPACE            NAME                                        READY   STATUS             RESTARTS   AGE
cert-manager         cert-manager-66bbb47c56-lh229               1/1     Running            0          9h
cert-manager         cert-manager-cainjector-5579468649-8jwvg    1/1     Running            0          9h
cert-manager         cert-manager-webhook-746cf468-xzb24         1/1     Running            0          9h
container-registry   registry-5d5b754549-m8zl6                   1/1     Running            2          2d10h
default              echo1-bfb568c8b-7fchh                       0/1     CrashLoopBackOff   575        2d
default              echo1-bfb568c8b-phc29                       0/1     CrashLoopBackOff   575        2d
default              echo2-5f44d9d965-hznqh                      0/1     ImagePullBackOff   0          2d
default              microbot-65bc8bdd7c-sgrd6                   1/1     Running            0          8h
default              microbot-65bc8bdd7c-zzdqt                   1/1     Running            0          8h
default              nginx-deployment-6b474476c4-5sm7t           1/1     Running            1          2d
default              nginx-deployment-6b474476c4-btzdq           1/1     Running            1          2d
ingress              nginx-ingress-microk8s-controller-247ws     1/1     Running            6          2d10h
ingress              nginx-ingress-microk8s-controller-8gzgf     1/1     Running            1          2d3h
ingress              nginx-ingress-microk8s-controller-qwtxr     1/1     Running            1          2d5h
kube-system          coredns-588fd544bf-9nmds                    1/1     Running            2          2d10h
kube-system          dashboard-metrics-scraper-59f5574d4-wcrll   1/1     Running            1          2d1h
kube-system          hostpath-provisioner-9b7695c6b-x5p27        1/1     Running            2          2d10h
kube-system          kubernetes-dashboard-6d97855997-tmqmf       1/1     Running            1          2d1h
kube-system          metrics-server-79749d858b-bhzl6             1/1     Running            2          2d10h
kube-verify          kube-verify-5f976b5474-4vz5s                1/1     Running            2          2d10h
kube-verify          kube-verify-5f976b5474-7fg52                1/1     Running            2          2d10h
kube-verify          kube-verify-5f976b5474-tjl5v                1/1     Running            2          2d10h
kube-verify1         kube-verify-5f976b5474-6t7pv                1/1     Running            1          2d5h
kube-verify1         kube-verify-5f976b5474-7blz8                1/1     Running            1          2d5h
kube-verify1         kube-verify-5f976b5474-mprc4                1/1     Running            1          2d5h
metallb-system       controller-5f98465b6b-gd82s                 1/1     Running            2          2d10h
metallb-system       speaker-6gs2w                               1/1     Running            1          2d5h
metallb-system       speaker-cml76                               1/1     Running            1          2d3h
metallb-system       speaker-ncs2p                               1/1     Running            2          2d10h
monitoring           alertmanager-main-0                         2/2     Running            4          2d10h
monitoring           arm-exporter-522xf                          2/2     Running            2          2d3h
monitoring           arm-exporter-mcw44                          2/2     Running            4          2d10h
monitoring           arm-exporter-ptshf                          2/2     Running            2          2d5h
monitoring           grafana-676bcb5687-d6hl2                    1/1     Running            1          2d7h
monitoring           kube-state-metrics-96bf99844-6tlrq          3/3     Running            6          2d10h
monitoring           node-exporter-9gkhm                         2/2     Running            4          2d10h
monitoring           node-exporter-cjjgs                         2/2     Running            2          2d5h
monitoring           node-exporter-hbg8s                         2/2     Running            2          2d3h
monitoring           prometheus-adapter-f78c4f4ff-zvcr7          1/1     Running            2          2d10h
monitoring           prometheus-k8s-0                            3/3     Running            4          2d7h
monitoring           prometheus-operator-6b8868d698-pt9rw        2/2     Running            4          2d10h
monitoring           smtp-server-5c7c8d77f8-q592k                1/1     Running            2          2d10h
nextcloud            nextcloud-857cd47bdf-xrnm4                  0/1     Running            2          2d1h
vinay@pramukha:~$ cat <<EOF | kubectl apply -f -

apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
name: letsencrypt-staging
spec:
acme:
email<EMAIL_ADDRESS>server: https://acme-staging-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt-staging
solvers:
- http01:
ingress:
class: nginx
EOF
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s": x509: certificate is valid for k8s-pi-master, not cert-manager-webhook.cert-manager.svc
vinay@pramukha:~$

Issue still persists even after with dedicated namespace "cert-manager"

`ubuntu@k8s-pi-master:~$ kubectl get namespace
NAME STATUS AGE
cert-manager Active 18h
cert-manager-test Active 2d10h
container-registry Active 2d19h
default Active 2d20h
ingress Active 2d19h
kube-node-lease Active 2d20h
kube-public Active 2d20h
kube-system Active 2d20h
kube-verify Active 2d19h
kube-verify1 Active 2d15h
metallb-system Active 2d19h
monitoring Active 2d19h
nextcloud Active 2d11h

ubuntu@k8s-pi-master:~$ kubectl get certificate -o wide --namespace cert-manager
No resources found in cert-manager namespace.
ubuntu@k8s-pi-master:~$ kubectl get certificate -o wide --namespace kube-system
No resources found in kube-system namespace.
ubuntu@k8s-pi-master:~$ kubectl get certificate -o wide -A
No resources found

ubuntu@k8s-pi-master:~$
`
There are no certificates in cert-manager and all other namespaces.

Same issue. Installed to kube-system and cant use kubectl describe or get.
Edit:
I've manually changed the CRD YAML config as follows:
Download file https://github.com/jetstack/cert-manager/releases/download/v0.14.1/cert-manager.crds.yaml and manually replace:

Annotations

Replace all occurances (should be 6 of them):
cert-manager.io/inject-ca-from-secret: cert-manager/cert-manager-webhook-tls

With:
cert-manager.io/inject-ca-from-secret: kube-system/cert-manager-webhook-tls

Namespace definitions

Replace all occurances (should be 6 of them):
namespace: cert-manager

With:
namespace: kube-system

and then apply kubectl apply --validate=false -f cert-manager.crds.yaml (cert-manager.crds.yaml being the local file you just edited) instead of the command provided in the official docs.
After applying everything works as expected.

Hi there,
I have tried your solution. Implementation went OK, but after when i try
kubectl get clusterissuers
that I'm receiving
Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=ClusterIssuer failed: Post https://cert-manager-webhook.kube-system.svc:443/convert?timeout=30s: x509: certificate signed by unknown authority
I'm wondering if it was also your case

Interestingly I'm getting the same error but having installed it in cert-manager namespace.

For the ones struggling, it seems that if you generate a name on the helm that is different from cert-manager, then the service will be named after your name (something like service/cert-manager-1595315110-webhook). Since the service is expected to be named cert-manager-webhook then it can't be found. This can be solved by using cert-manager as the name of the release when installing the chart (probably cert-manager as the namespace too).
Anyway, that still didn't solve the problem for me, so what I did was:

Removed the chart: helm uninstall <release_name>
Removed the custom resource definitions: kubectl delete -f https://github.com/jetstack/cert-manager/releases/download/v0.16.0-alpha.1/cert-manager.crds.yaml
Installed the chart again with: helm install jetstack/cert-manager --generate-name --set installCRDs=true

I hit to the same problem. But I have k8s by kubespray, on managed by GCP, DO etc works without problem.

For the ones struggling, it seems that if you generate a name on the helm that is different from cert-manager, then the service will be named after your name (something like service/cert-manager-1595315110-webhook). Since the service is expected to be named cert-manager-webhook then it can't be found. This can be solved by using cert-manager as the name of the release when installing the chart (probably cert-manager as the namespace too).
Anyway, that still didn't solve the problem for me, so what I did was:

Removed the chart: helm uninstall <release_name>
Removed the custom resource definitions: kubectl delete -f https://github.com/jetstack/cert-manager/releases/download/v0.16.0-alpha.1/cert-manager.crds.yaml
Installed the chart again with: helm install jetstack/cert-manager --generate-name --set installCRDs=true

yep,
helm install jetstack/cert-manager --generate-name --set installCRDs=true
worked for me as well
I did use a small modif though, included the version parametere
helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--version v0.15.2 \
--set installCRDs=true

--set installCRDs=true worked out for me as well!

@munnerz
Problem is with configmaps generated in kube-system namespace by previous installation ( you can have same helm release name btw )...
Try to remove them:
kubectl delete cm cert-manager-cainjector-leader-election cert-manager-cainjector-leader-election-core cert-manager-controller -n kube-system

Or use:
--set global.leaderElection.namespace=cert-manager and always delete cert-manager namespace
And redeploy cert-manager...

quicker startup times
no Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s: x509: certificate signed by unknown authority
no Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s: dial tcp <IP_ADDRESS>:443: connect: connection refused

But this should be handled by Readiness and Liveness probes I guess ...

When using helm upgrade --install rather than helm install for the intiial deployment we're seeing this error in any subsuquent deployments
Error: failed to create resource: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s: x509: certificate signed by unknown authority

AKS 1.16.10
cert-manager v0.15.2
helm/tiller v2.16.9

When using helm upgrade --install rather than helm install for the intiial deployment we're seeing this error in any subsuquent deployments
Error: failed to create resource: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s: x509: certificate signed by unknown authority
AKS 1.16.10
cert-manager v0.15.2
helm/tiller v2.16.9

Try removing the secret cert-manager-webhook-ca. It will be regenerated and the restart the cert-manager-webhook pod.

这个问题可能是cni导致的，我修改了calico的mtu后这个问题解决了(This problem may be caused by cni. After I modified the mtu of calico, the problem was solved.)
{
  "name": "k8s-pod-network",
  "cniVersion": "0.3.1",
  "plugins": [
    {
      "type": "calico",
      "log_level": "info",
      "log_file_path": "/var/log/calico/cni/cni.log",
      "datastore_type": "kubernetes",
      "nodename": "k3s-operator-1",
      "mtu": 1420,
      "ipam": {
          "type": "calico-ipam"
      },
      "policy": {
          "type": "k8s"
      },
      "kubernetes": {
          "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"
      }
    },
    {
      "type": "portmap",
      "snat": true,
      "capabilities": {"portMappings": true}
    },
    {
      "type": "bandwidth",
      "capabilities": {"bandwidth": true}
    }
  ]
}

Just had a an issue with certmanager deploy using installCRDs but via pulumi where the resource name was different to the chart name resulting in the service being called: resource-name-cert-manager-webhook, but cert manager contuning to look for cert-manager-webhook without the resource name prefix.
    new k8s.helm.v3.Chart(
      "cert-manager",
      {
        chart: "cert-manager",
        version: "1.2.0",
        namespace: namespace,
        fetchOpts:{
          repo: "https://charts.jetstack.io",
        },
        values: {
          installCRDs: true,
        },
      },
    )

I'm not sure if this is an issue with Cert manager or Pulumi, but I thought I'd post it here in case others run into the issue. In my case it was quite difficult to spot as I thought I had used cert-manager for the resource name but had in fact made a typo cert-manger (missing the "a").
The magic that leads to this prefix when you make a typo: https://github.com/jetstack/cert-manager/blob/master/deploy/charts/cert-manager/templates/_helpers.tpl#L18-L21

@gerrywastaken I think it's not related to Pulumi, as I just ran into the same issue without Pulumi.
I had to downgrade to https://github.com/jetstack/cert-manager/releases/tag/v1.1.1 to make it work. There is also some comment regading the installCRDs flag in the release notes

Also be sure to update the --dynamic-serving-dns-names flag in the cert-manager-webhook deployment which contains cert-manager as a namespace if you are changing the namespace name.

I am already using:
helm install cert-manager jetstack/cert-manager --namespace $NAME_SPACE --create-namespace --version v1.3.1 --set installCRDs=true
So installCRDs=true in my case does not make any difference.
I get error like :
Error from server (InternalError): error when creating "output/zero_ssl.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": dial tcp <IP_ADDRESS>:443: i/o timeout

For other poor souls like me who have been surfing the Internet for several days and have NOT customized the cert-manager namespace, please try restarting your webhook pod :man_facepalming:
In our case we were having the dreadful remote error: tls: bad certificate errors and they are gone after a restart.
We're using an old version of cert-manager (0.8.0) which worked just fine for a long time until this. My guess is that one of the secrets it's using was replaced but there is no logic to re-read them. I don't know what it was, but after contemplating a re-install in production, finding it apparently solved like this was worth sharing with others.

Hello, I have the same problem when I made this request :
kubectl get clusterissuers

I have this error :
Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=ClusterIssuer failed: Post https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s: service "cert-manager-webhook" not found

And 1 year ago, at the cluster configuration, I first install cert-manager in wrong namespace, uninstall it and reinstall in kube-system namespace. It seems may artifacts are here. How to juste uninstall them (and don't uninstall/reinstall cert-manager)


chore(client): Fix register pre-commit hook

Summary
Fix register pre-commit hook
Related links

Closes #134

CLA

[x] I have signed the individual contributor's license agreement and sent it to the board of the WüSpace e. V. organization.

Tested and verified under Win10.


[Improve][SourceConnector] Unifie InfluxDB source fields to schema

Purpose of this pull request
fix #3821
Unifie InfluxDB source fields to schema
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

cc @Hisoka-X @liugddx , could you help me review this PR?

cc @Hisoka-X @liugddx , could you help me review this PR?
Let's wait for CI.

cc @Hisoka-X @liugddx , could you help me review this PR?
Let's wait for CI.
I have resolved e2e module CI error , could you please restart CI ？thx

cc @Hisoka-X @liugddx , could you help me review this PR?
Let's wait for CI.
I have resolved e2e module CI error , could you please restart CI ？thx

Hi, seem like you not update your code after resolved e2e module CI error. If you update the code, the ci will auto restart

#3896 is duplicate with this. In chronological order #3896 is valid, could you please try another task? @wfrong

Let's waiting CI process. Thanks, if CI passed this pull request can be merged.


Update cats-effect, cats-effect-laws to 2.3.1

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 2.1.4 to 2.3.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-minor

Superseded by #184.


DRAFT: Component Library Proof of Concept

The Problem
We want a way to quickly implement UI changes without some of the complexity that can exist in implementing those changes. We also want to make sure that our UI has a consistent look and feel across the application, providing a nice user experience throughout.
Context
I explored several options for how to make general UI improvements in the CIAB site. I looked at the following options:

Google's Material Design - this would still be a solid choice for us, however we do not use a build process (yet) which would make this a little more challenging. It makes use of Web Components, which are generally supported by all browsers.
Briefly considered Material UI, but it is React only so that was a no-go.
Bootstrap - has a lot of things that work nicely out of the box. Styling is applied through using typical HTML practices such as defining something like <div class="the-style"> so it still requires some effort. It's also incompatible with Vue, so it's a no-go.
Tailwind CSS - this is only CSS and also generally recommends use with a build process. Since we are looking for quick implementation for consistent look and feel, this could help in solving some of the issues around theming and consistent look and feel. However, if we wanted to build something like a date picker or color picker, we're still on our own for this.
Vuetify - provides nice, out of the box components for us to leverage, similar to Material Design. This framework is built to work specifically with Vue and gives us the Material Design look and feel, allows theme customization, and more.

Vuetify seems to satisfy several requirements:

Allows us to quickly implement UI changes through pre-built components
Allows us to quickly define styles in an application-wide theme.
All components are rendered in the same way and can be individually customized, or inherit from the application-wide theme.
Can be used further through our own custom component definitions.
Can work well with build processes if we leverage that in the future.

For the purposes of this proof of concept I chose Vuetify.
Scope
This PR includes an example implementation of some changes to our UI using Vuetify.
I chose to implement a very simple theme based on the colors on the Convergence Con site. If desired, we can also somewhat easily incorporate Material UI based Icons, and while I explored this during the example implementation, I noticed that the icons seemed to load in after the page had loaded. With additional effort we may be able to leverage these.
In this example implementation, I chose to define a thing specifically for the Staff Module, because I wanted to limit any visual changes to the ConCom List section of the site only. Including the CSS at the root level of the application was causing some unintended visual updates on other parts of the site.
In practice, it is likely that we will define the theme once, in a single place and then reference that theme when we are applying the Vuetify framework into the application rather than what I have done here as an example.
Changes Made

Converted buttons for adding and editing to use Vuetify provided buttons.
Converted select dropdown for position choices on the sidebar to use Vuetify provided select dropdown

I am including screenshots showing what this looked like before and how it will look after.
As you can see, there was not much that needed to be changed, we were able to simplify the code a little bit and removed some styles that were no longer needed.
This is just a simple example and does not represent fully how we can break out components our own components for further customization and re-use.
PLEASE DO NOT MERGE THIS MR. It would be nice to explore this further and convert more of this to use Vuetify if we feel this is the right path for us.
Original Buttons and Select Style

Vuetify-ed Buttons and Select Style

We will need to use or replace the scss/event.scss functionality.  This is the ability to set the colors based on event.  It is the beginning of a way to skin the site.
This skinning from a user side occurs in index.php?Function=admin and index.php?Function=admin/asset
The scss defines things like the Primary and secondary event colors that are used on headers and buttons and such.
I love the idea of this framework, but wonder why you went from red oval buttons to purple square buttons, unless it was just to show what changed.

We will need to use or replace the scss/event.scss functionality. This is the ability to set the colors based on event. It is the beginning of a way to skin the site.

If we want to hook it into the pre-configured primary/secondary color scheme from the database we certainly could. I went for simple in this example. So long as we can get the color scheme from an API call, it would be easy to configure.

I love the idea of this framework, but wonder why you went from red oval buttons to purple square buttons, unless it was just to show what changed.

There were a couple of reasons.

Demonstrate what we can do with very little configuration on our side. This is the default styling with no additional changes.
Simplify the color scheme. Our pages are way too noisy and distracting.

Overall, a few small changes can make the site look and feel a whole lot better. We can keep oval buttons if we really want to do that, with minimal effort, but I would advise simplifying the color scheme in general and being consistent with it.

Closing since this has served its purpose for now. Thanks for the feedback!


Removing settings

I selected too many folders and now lrcget is stuck with the 'Loading library...' message. Left it on overnight, no change.
Uninstalled and re-installed, and again the Loading library message. How can i reset or delete the settings? Devuan Daedalus.

If you're on Windows try deleting the files in the path: %appdata%/net.lrclib.lrcget

Solved. I installed lrcget_0.2.1_amd64_ubuntu_22.04.deb. After uninstall the leftover files can be found with locate.
So i can't recommend selecting an external drive with 2000+ folders.


Threat Dragon 2.0 - Breaking Changes in Drawing Package

Hello!
I'm one of the Threat Dragon maintainers, and  just learned of this awesome tool through an OWASP Kyiv video on YouTube.  Threat Dragon is ramping up for it's 2.0 release, which will be using an entirely different drawing package (moving from JoinJS to Antv/x6).  To date, we've been working hard to ensure that there aren't breaking changes in the JSON models, except for the drawing parts.  Unfortunately, this looks like it will be a breaking change for this project.  We do not have an exact ETA for the version 2 release at this time, but development has been underway for a while.  The exact schema for the 2.0 models isn't finalized yet, however, they will likely have a version tag at the top level to help identify them from the 1.x versions.
My goal is to start a conversation and see if there's anything we can do to help the transition to 2.0 models.  There will be a couple new shapes introduced in 2.0, possibly more in the future.  The first thing that comes to mind as far as things we could do that might be helpful is possibly publishing Threat Dragon's shape definitions as a separate NPM package?
I'm very open to discussion and am here to help!  Cheers!

Hi @lreading
thank you very much for letting us know about the breaking changes. This is a great service of you as we haven't been aware of this! :heart:
I believe it would help us most if we could get an example JSON (and maybe a list of the changes) as soon as the schema is somehow stable.
I am not sure whether I understand the part about the new drawing package: Is the new JSON schema coupled to the drawing package? I.e. do we have to change to x6 as well?
Thank you very much!

The new JSON schema will be tightly coupled to the drawing package.  (It currently is tightly coupled to JointJS).  I think the easiest path forward would be using X6 as well, as the properties are just slightly different.
We don't have an example quite yet though, but I will be sure to post one when we have it, along with some specific references to how we're handling the conversion of v1 -> v2 models.  V2 is still in development, so we will be sure to stay in contact.
Thanks again!

Hey everyone, is there anything going on here? Threat Dragon 2.0.0 was released a few months ago :+1: :grin:

2.X got rid of the diagramJSON attribute, seems to have moved  "data" seems to be the new attrs and  attrs has been made to reflected what looks like visualization attributes for the element.
Ive been trying to figure out how to edit the client code to parse the new JSON format for TD 2.X but its a lot of eye-bleeding debugs. dia doesnt like that my cell types arent strings

Just wanted to check if there is any progress on this issue or if maybe help in testing is needed?
Unfortunately, we have a bunch of models in threat dragon 2 format and using images as a basis for EoP is not nearly as nice as having the models directly in the game.
And thank you for making this awesome digital version of EoP!

Hi @gh0st42
@ChristophNiehoff and the folks at TNG maintain a fork with additional features at https://github.com/TNG/elevation-of-privilege. I haven't been actively involved in the development/maintenance lately, but I can spare some time to add support for it if needed.


e2e test for Pause Feature

Summary
We will want to confirm that:

updating a Pipeline causes Pipeline to follow this sequence of events: pause, update, run
updating an ISBService causes all Pipelines using it to follow this sequence of events: pause all pipelines, wait for them to be paused, ISBService updated, ISBService completely reconciled (i.e. StatefulSet has been updated with all new Pods), pipelines running
updating a Numaflow Controller causes all Pipelines on namespace to follow this sequence of events: pause all pipelines, wait for them to be paused, Numaflow Controller Deployment updated and reconciled (created a new ReplicaSet which has created new Pods which are running), pipelines running

We need to see if it is a challenge to check Pipeline Phase for "Paused" quickly enough before it becomes running. That could happen if we are simply doing a "Get" periodically on the Pipeline - we could miss it. Best approach is probably to do a Watch and receive an update that we can check every time. If that approach doesn't work for some reason, we can use "kubernetes events" to check.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

I'm torn between having a separate test for this vs just taking our existing test and adding a few if ${DATA_LOSS_PREVENTION} env var set type steps. I don't want to have a bunch of redundant code in 2 places after all.
It kind of sounds like in the future we may not even support the case of basic CRUD, so perhaps we do for now add if ${DATA_LOSS_PREVENTION} env var set steps to check for pausing to the existing test?


State saved in 'hash' should take precedence over 'local_storage'

When state saving is enabled using hash and local_storage filter states should be restored from hash (if present), and then local_storage should be used,
This scenario applies to situations when one person send the URL to the table to the other people.
The person assumes all people will get the same result in the table, as all the filters are in the link.
Example config:
            state: {
                types: ['hash', 'local_storage'],
                filters: true,
                page_number: true,
                page_length: true,
                sort: true,
                columns_visibility: true,
                filters_visibility: true
            },

Reproduction steps:
I'll describe here how to reproduce the situation on one PC using two different browsers. But this happens between different systems also.
This is easily reproducible using one browser, but with different profiles (or Private Mode could be used).

Using browser 1 (Firefox) set filter on column 1 to "AAAA"
Using browser 2 (Chrome) set filter on column 2 to "BBBB"
Copy and open the link from browser 1 (Firefox) to browser 2 (Chrome)

Expected behavior:
Browser 2 (Chrome) should show the same filters applied as in browser 1 (Firefox).
Column 1 filter is set to "AAAA"
Observed behavior:
Browser 2 (Chrome) shows locally saved filters.
Column 1 filter is set to "BBBB"
TableFilter version: v0.6.9
Browser and version: Firefox 57.0.2
OS and version: Fedora 27
Additional information:

Problem started happening recently, didn't happen in an older version of TableFilter:
I don't know
Problem can be reliably reproduced, doesn't happen randomly: Yes

tx @maciex for pointing this out. I will try to include a fix in the next releases.

@maciex are you noticing behaviour you described above with multiple selection filters (multiple, checklist)?
I am seeing expected behaviour for input and select types.

I checked this behaviour on input, select and checklist and all of them seem to behave the same, every time there's something saved in local_storage it takes precedence over hash.


Crash when excute json_decref

Hi,
I'm working on a project using Jansson to send http request.And crash happened when build request
JanssonTest(84916,0x1003ac380) malloc: *** error for object 0x102858928: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug

Code are as the following
json_t *methodParaJson = json_object();

tmp = request.displayName;
json_object_set_new(methodParaJson, "displayName", json_string(tmp.c_str()));

json_t *requestJson = wrapper(methodParaJson, "initConnection");

char *requestStr = json_dumps(requestJson, 0);
requestBody = std::string(requestStr);

free(requestStr);
json_decref(requestJson);

json_decref(methodParaJson);// The code cause crash

json_t *ProximityRequestBodyBuilder::wrapper(json_t *parameterJson, const std::string &methodName)
{
    json_t *root = json_object();

    //wrap token
    json_object_set_new(root, "token", json_string("ed2f"));

    //wrap method
    json_t *methodPara = json_object();
    json_object_set_new(methodPara, methodName.c_str(), parameterJson);

    //wrap request
    json_object_set_new(root, "request", methodPara);

    return root;
}

And the reason of the crash is json_decref(requestJson) not only decrease the reference of requestJson but also decrease the reference of methodParaJson, So when I attemp to execute json_decref(methodParaJson) after excute  json_decref(requestJson);, crash happened frequently.
And the reason why json_decref(requestJson) also excute json_decref(methodParaJson) is the methodParaJson is wrapped by requestJson.
But I think who is responsible for increase reference, and he also responsible for decrease reference.
So maybe the implementation of function json_object_set_new should increase reference?

You should use json_object_set if you want to use the reference to added value later. json_object_set_new "steals" the reference to the added value.
So the correct fix for you is to use json_object_set(methodPara, methodName.c_str(), parameterJson) instead of json_object_set_new(...).

It worked. Thanks a lot @akheron


chore: Add an internal request ID for logging

/ok-to-test<EMAIL_ADDRESS>

[!CAUTION]
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8911411758
Commit: e97e64b3ef09688488753434c61217ac17e07b5c
Cypress dashboard:  Click here!
The following are new failures, please fix them before merging the PR:
cypress/e2e/Sanity/Datasources/AuthenticatedApiWithOAuth_spec.ts
cypress/e2e/Sanity/Datasources/MySQLNoiseTest_spec.js
cypress/e2e/Sanity/Datasources/RestApiOAuth2Validation_spec.ts
cypress/e2e/Sanity/Datasources/SMTPDatasource_spec.js
To know the list of identified flaky tests - Refer here

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true


expired tokens

I noticed when endpoint is issued with expired token then before action oauth server validates this token in CompositeAuth class. It ignores result from Server::verifyResourceRequest() which causes running actions using expired tokens. After action is performed then afterActio  handler ErrorToException is triggered and returns 401 response which is ok.
I think this class ErrorToException should be removed and code from it should be moved to CompositeAuth to verify tokens and throw proper exception before action instead of after action.

i didn't have an idea to fix this in library as this fix would need to introduce some BC and changing lot of internals. So as a workaround I made own CompositeAuth class as this:
<?php

namespace api\oauth;

use Exception;
use filsh\yii2\oauth2server\exceptions\HttpException;
use filsh\yii2\oauth2server\Module;
use Yii;

final class CompositeAuth extends \yii\filters\auth\CompositeAuth
{
    /**
     * @inheritdoc
     *
     * @throws HttpException
     * @throws \Exception
     * @throws \yii\base\InvalidConfigException
     */
    public function beforeAction($action)
    {
        /**
         * @var \yii\web\Application $app
         */
        $app = Yii::$app;
        /**
         * @var Module|null $server
         */
        $server = $app->getModule('oauth2');
        if ($server === null) {
            throw new Exception('An internal server error has occurred (could not load the OAuth2 Module)');
        }
        $server = $server->getServer();
        $server->verifyResourceRequest();

        $response = $server->getResponse();
        $isValid = true;
        if ($response !== null) {
            $isValid = $response->isInformational() || $response->isSuccessful() || $response->isRedirection();
        }
        if (!$isValid) {
            throw new HttpException($response->getStatusCode(), $this->getErrorMessage($response), $response->getParameter('error_uri'));
        }

        return parent::beforeAction($action);
    }

    /**
     * @param \OAuth2\Response $response
     * @return string
     */
    private function getErrorMessage(\OAuth2\Response $response)
    {
        return Yii::t('common', $response->getParameter('error_description'));
    }
}

and using it in controller like this:
    public function behaviors()
    {
        return [
            ...
            'authenticator'     => [
                'class'       => CompositeAuth::class,
                'authMethods' => [
                    ['class' => HttpBearerAuth::class],
                    ['class' => QueryParamAuth::class, 'tokenParam' => 'accessToken'],
                ],
            ],
            ...
        ];
    }

Nice, thanks for sharing!

@mozarcik thank you for noticing that.
I will find time and see if I can do anything for 1.x version with breaking BC.
If I can't I will branch into 2.x-dev which will end up as version 2.x with no BC


Can't reeanble disabled date.

https://jsfiddle.net/wcq5txx4/
Am i doing something wrong? I have a bunch of date whitelists, that i need to toggle.

This does what i'm expecting
https://github.com/amsul/pickadate.js/issues/364#issuecomment-116980300


fix github_repo config

change incubator-hugegraph to incubator-hugegraph-doc

Thanks, and seems we need a script / plugin to auto generate new pages?
Now we can't see the diff after we merged PR


Move bulk of homepage "Instantly containerizable and production-ready" section to new "Containerization" doc

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2263
Originally created by @DouweM on 2020-08-12 16:13:57

[x] Simplify example code
[x] Move GitLab instructions to doc
[x] Leave at most 3 paragraphs and a button

View 6 previous comments from the original issue on GitLab


[AutoPR web/resource-manager] Fix network trace API REST format

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4295

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/324


use parent code title for better readability

A picture tells a thousand words
Before this PR

After this PR

Coverage increased (+0.2%) to 43.99% when pulling b6cb392c09bc77880275185c1a6c1dbdf79633b9 on useParentCodeTitle into 3665f8a2a40dd04d3f4aa7c663c27e053b61da8b on master.


docs: new tutorial "validate asyncapi documents using studio"

Description

NEW tutorial, "How to Validate AsyncAPI documents using studio"

Related issue(s)

#872

@alequetzalli this is up for suggestions and reviews

📝  Hey @starlightknown, a few feedback notes:

This tutorial had a lot of unnecessary content that was directly copied over from the 'guide' PR. This should have been re-written entirely and edited to be much more succinct. (Ex: mention of diff ways to validate, writing a description of an AsyncAPI document and it's sections (we already have a Quickstart), and even talking about parsers).
This tutorial was not written in only sequential format, guiding us from step 1-10. I re-wrote this content to show how tutorials steps should be written.

At this point it would be great to have @derberg review it from a technical perspective and provide his feedback too on how to further improve this tutorial.
Thank you for all your work so far ✨✨✨✨

Oh and we need add the Prev/Next steps buttons to this doc page too :)

Oh and we need add the Prev/Next steps buttons to this doc page too :)

would that lead to my next tutorial?

Oh and we need add the Prev/Next steps buttons to this doc page too :)

would that lead to my next tutorial?

Yes @starlightknown, remember we're ordering the 4 new tutorials in the following order:

Create AsyncAPI document
Validate AsyncAPI document
Generate Code
Validate Events/Messages

Oh and we need add the Prev/Next steps buttons to this doc page too :)

would that lead to my next tutorial?

Yes @starlightknown, remember we're ordering the 4 new tutorials in the following order:

Create AsyncAPI document
Validate AsyncAPI document
Generate Code
Validate Events/Messages

added the buttons

@starlightknown Is this PR still in progress for development or completed? Because I can still see that the routes you added in the Prev and UpNext buttons are missing. Are you working on those pages in this PR only?

@starlightknown Is this PR still in progress for development or completed? Because I can still see that the routes you added in the Prev and UpNext buttons are missing. Are you working on those pages in this PR only?

Hey, I added the routes too but it doesn't work maybe because we don't have other PR merged yet.

Hey, I added the routes too but it doesn't work maybe because we don't have other PR merged yet.

@starlightknown We actually can't merge this PR with undefined routes right now. If the other PRs are taking time to get merged, I'll suggest making the routes of the buttons according to the current scenario of the Docs tree. If you want to wait for other PRs, just we should make sure we don't merge this PR first.
Also, please list down the PRs that are linked to this so that I could have a check on that also.

Hey, I added the routes too but it doesn't work maybe because we don't have other PR merged yet.

@starlightknown We actually can't merge this PR with undefined routes right now. If the other PRs are taking time to get merged, I'll suggest making the routes of the buttons according to the current scenario of the Docs tree. If you want to wait for other PRs, just we should make sure we don't merge this PR first.
Also, please list down the PRs that are linked to this so that I could have a check on that also.

Those are #1025 and #1023

yes, definitely
but please align with @alequetzalli and @Annysah
because looks like now we will have the following tutorial flow:

create AsyncAPI document
validate document
generate code
validate messages

for generate code CLI is also needed. So I'm not 100% sure, but I think it doesn't make sense to have CLI installation instruction in both, validate document and generate code

Point 1: Prev/Next buttons
@starlightknown, @akshatnema is 100% right here. Adding next/prev buttons without routes or routes that don't exist yet is not what you should do. We've talked about this offline and in our GSoD calls, but there are 2 ways you can handle this:

Include the routes of ONLY content currently LIVE and get your PR merged. Moving forward, as new content is merged, we will update the routes in those buttons. (not necessarily you, but whoever creates a PR that would require updating those buttons)
WAIT to merge this PR until ALL 4 NEW gsod tutorials are ready to merge. In this case, it would be ok to use routes for content that is not yet LIVE because you're waiting to merge it.

I'm glad that @akshatnema noticed this because we need to ensure each new doc page has working routes in the prev/next buttons. Please let us know if this still doesn't make sense, and I can totally hop on a call if that helps. 😄
Point 2: Adding CLI commands to this tutorial
@derberg No, the purpose of this tutorial from the beginning has always been how to validate AsyncAPI documents with the Studio tool specifically. This does not mean we don't need a validation tutorial with CLI commands, it just means that is another topic. This tutorial is to showcase Studio validation, it should not go outside of the topic and discuss CLI commands. Each validation method requires its dedicated tutorial, focused and succinct to one scenario.
At this point, it is too late to ask the GSoD project ALSO to add a 'CLI validation' tutorial, so you should consider that work for me (Alejandra) that I pick up independently of GSoD. 😄✌🏽
Let's keep this tutorial focused on Studio validation example and I will create a NEW Docs issue outside of GSoD scope for a NEW tutorial on AsyncAPI document validation via CLI commands.
Something I will also point out is that creating a 2nd tutorial on the topic of validation methods opens the door for a new Tutorials sub-section on validation. Personally, I have been looking forward to doing this for a while, and now that we have more content its a great time to make these improvements.
Does this mean we need a NEW tutorial for Generate code w/ CLI? YES 🙌
Same reason as explained above for having a NEW "validation w/ CLI" tutorial. I will also take responsibility to create new Docs issue for this, as this too is outside of GSoD scope.
Point 3: Not including CLI installation information in individual tutorials
@derberg I see you asked: "So I'm not 100% sure, but I think it doesn't make sense to have CLI installation instruction in both, validate document and generate code"
So to answer that question, YES, each individual tutorial will always include required installation items. It doesn't matter if one or more tutorials end up needing the same items installed. It only matters that any tutorial can stand on it's own, and include any and all info needed to install for that tutorial.
Never assume a user knows what to install or has already completed a previous tutorial with same installation items. 😜

just keep in mind that if we split these, have separate Studio and separate CLI tutorial, we will repeat a lot of content, about 80%, intro, summary and background will be almost the same. AsyncAPI file the same. The only difference will in direct instructions on how to check stuff in Studio and how to do it with CLI, which is just asyncapi validate <FILE_NAME>
and again, how is this PR related to https://github.com/asyncapi/website/pull/971 as I keep getting confused reviewing all these different PRs and sometimes seeing they overlapping each other 😅

just keep in mind that if we split these, have separate Studio and separate CLI tutorial, we will repeat a lot of content, about 80%, intro, summary and background will be almost the same. AsyncAPI file the same. The only difference will in direct instructions on how to check stuff in Studio and how to do it with CLI, which is just asyncapi validate <FILE_NAME>

That is fine, and having a short CLI tutorial is fine. Again, it's about keeping the separation of scenarios (tools).

and again, how is this PR related to #971 as I keep getting confused reviewing all these different PRs and sometimes seeing they overlapping each other 😅

hahaha yeah they got confused and opened an extra PR.. not a big deal but I can see why you got confused 😄

left some comments
please also fix section's headings

The headings used are # for introduction and other main sections, ## for sub sections and ### for examples in every tutorial till now, if I change it here then we'll lose the consistency plus others have to change too

Notes (just for me)
Validation keywords

type( string, integer, boolean, number, object, array)
constant values
objects (properties, additional properties)
arrays (items, additional items)
numbers (multipleOf, minimum, maximum)
string (minlength, maxlenght, email)

@magicmatatjahu you know studio and new layout the best, please do the technical review if all steps are accurate and all is properly explained 🙏🏼

technically all good, we just need to incorporate of course the new fragment with CLI installation
@alequetzalli leaving this one to you
@Annysah well done 👏🏼

Hehe it's me tho 😝

ups @starlightknown I was suppose to comment it here https://github.com/asyncapi/website/pull/1025#pullrequestreview-1201090665 😄
for this PR:

just left one suggestion
all good from my side, leaving it to @alequetzalli and also @magicmatatjahu in case of template in studio (not sure if @starlightknown what to try to contribute or not

anyway, my approval is not needed 👍

@magicmatatjahu I would like to add the template, could you please let me know what and where to do that?

@starlightknown
You should create (exactly copy and paste) your invalid AsyncAPI file to this location https://github.com/asyncapi/studio/tree/master/src/examples - please create tutorials folder and there paste that document.
Next thing is to create new example type in this file https://github.com/asyncapi/studio/blob/master/src/examples/index.tsx as tutorials. You should know what I mean - if not, let me know :)
And at the end you should update that file https://github.com/asyncapi/studio/blob/master/src/components/Modals/NewFileModal.tsx to render the category, Tutorials - again, if you will have problems, let me know :)

@starlightknown
You should create (exactly copy and paste) your invalid AsyncAPI file to this location https://github.com/asyncapi/studio/tree/master/src/examples - please create tutorials folder and there paste that document.
Next thing is to create new example type in this file https://github.com/asyncapi/studio/blob/master/src/examples/index.tsx as tutorials. You should know what I mean - if not, let me know :)
And at the end you should update that file https://github.com/asyncapi/studio/blob/master/src/components/Modals/NewFileModal.tsx to render the new category, Tutorials - again, if you will have problems, let me know :)

Done!

@magicmatatjahu helped me and we did it! Thank you

@starlightknown @derberg Let me know when you wanna merge that PR, I will merge PR in the Studio before this one.

I suggested that we have a valid example, and that the flow of tutorial says, "you choose valid example and then just break it to get errors"
https://github.com/asyncapi/website/pull/1022#discussion_r1037156926

having an invalid example is weird to me. This is why we also have a valid tutorial.yml in CLI. But if I'm the only one thinking it is weird, let's go with invalid. Thoughts?

having an invalid example is weird to me. This is why we also have a valid tutorial.yml in CLI. But if I'm the only one thinking it is weird, let's go with invalid. Thoughts?

If there's already valid and we break it then the user already knows which parts they broke, it'll be a whole cycle again and they won't try to fix coz they know. if they have to do this in real life then they might not know as they did not actually fix an invalid file?
Idk just my thought

as @starlightknown wrote. The user will start breaking down the specifications which is correct and do the tutorial backwards - why a tutorial then?

I suggested that we have a valid example, and that the flow of tutorial says, "you choose valid example and then just break it to get errors"
#1022 (comment)

ya @derberg  you keep trying to do that but I keep telling you that is missing the point of the tutorial 😄😂😜

my own two cents...

The flow of this tutorial was always planned to begin with a BROKEN document that the user must learn how to debug by troubleshooting via console errors. The goal is to learn how to troubleshoot when your code (document) is broken and you only have console errors to help guide you along the way. (It is pointless to begin with a CORRECT file that the user can easily know what section they broke. That is not how you manage these situations in the wild; the point of this tutorial is to replicate a real bug scenario in Studio and show users how to use the tool to debug documents.)
Originally...I'm not sure if I'd have wanted to recommend having the sample buggy (broken) document in Studio, but the nice thing about this idea is that we could add a comment within the template that links to the tutorial. That way, users who accidentally run into this while using the Studio tool can immediately see we have a tutorial for learning how to debug their documents. If we do it this way, I think it's actually a neat idea from Macief. So I guess I like it? 😄

Shall I go ahead and add that comment?

@alequetzalli

Shall I go ahead and add that comment?

@starlightknown oui sparklessparklessparklessparklessparkles

added, I guess this is good now?

hey @starlightknown, where is that comment added to the Studio invalid template example? can you please show me link to that

hey @starlightknown, where is that comment added to the Studio invalid template example? can you please show me link to that

https://github.com/asyncapi/studio/pull/536 it's not merged yet

@starlightknown @alequetzalli Should I merge the PR in Studio first or I should wait for this PR?

@starlightknown @alequetzalli Should I merge the PR in Studio first or I should wait for this PR?

@magicmatatjahu I recommend we wait to merge https://github.com/asyncapi/studio/pull/536 at the same time as this tutorial PR; otherwise, it will confuse users since the tutorial won't be live yet.

@alequetzalli Mentioned PR is already merged 😅 You can merge this one with one problem.

@alequetzalli Mentioned PR is already merged 😅 You can merge this one with one problem.

LOL !! yeah I see fran got excited and jumped the gun  to merge...
So you say "You can merge this one with one problem." Sorry, what problem is that? 🧐

/rtm


Add d3.linspace.

Related #90.

Maybe worth adding logspace and geomspace too, while we’re here?

I can see how it would be useful, esp. if it returned a Float64Array (or had some option like dtype), and satisfy #90 at the same time.
Not sure about floor(n), since it could be nice to continuously change n (in the case where * endpoint* is false).
For logspace and geomspace it looks like there is no particular algorithmic challenge and not much use. I wouldn't want to add weight (bytes and documentation and cognitive load) just for the sake of it :)

Very nice!

This looks like a nice PR. Could be merged I suppose.

I don’t think the positional arguments with defaults are appropriate here because they aren’t analogous to Python’s named arguments. For example in Python you would say stuff like
np.linspace(2.0, 3.0, 5)
np.linspace(2.0, 3.0, num=5)
np.linspace(2.0, 3.0, num=5, endpoint=False)
np.linspace(2.0, 3.0, endpoint=False)

and the meaning is fairly clear. However in JavaScript it would be
d3.linspace(2, 3, 5)
d3.linspace(2, 3, 5)
d3.linspace(2, 3, 5, false)
d3.linspace(2, 3, undefined, false)

which I think is much less obvious. So I wonder if instead we should do something like:
d3.linspace(2, 3, 5)
d3.linspace(2, 3, {num: 5})
d3.linspace(2, 3, {num: 5, endpoint: false})
d3.linspace(2, 3, {endpoint: false})

This would also allow us to create typed arrays:
d3.linspace(2, 3, {num: 5, type: Float64Array})

I also don’t really like feeling stuck with Python’s names for these options. I think I’d prefer n or length instead of num. I’m using type instead of dtype because in JavaScript it would be the type of the array rather than the type of the value. (And I thought about inclusive or exclusive instead of endpoint but I couldn’t make up my mind.)
And lastly I wonder if there should be more symmetry between d3.range and d3.linspace. Like, what about:
d3.range(2, 3, {length: 5, inclusive: true})

Also this feels fairly low priority and ambiguous so I’m not very motivated to think about this too much. 🤷 Sorry!


Added new guide 'data_engineering_CDC_SnowpipeStreaming_DynamicTables' (status hidden)

Created new Virtual Hands-on Lab, showing 2 new preview features (Snowpipe Streaming and Dynamic Tables).  Set to hidden initially, to enable feedback and previewing.

More edits coming


Add Notebook Completion Item Provider Unit Tests

Add unit tests for the notebook completion item provider.
Since we're interrogating Jupyter here to populate Intellisense completion items, mocking out the kernel/session, since not every environment will have Jupyter/python installed.

Coverage increased (+0.2%) to 36.325% when pulling e0644adb134091890db2094954d22ac5caacb89c on chlafren/moartestss into ac78822d90358059b5a781a0abffb111e6637a67 on main.


Windows: correctly set notifications name - not electron.app.YOURAPPNAME

this helps with setting the the name correctly for windows notifications
currently it shows as electron.app.YOURAPPNAME
you need to run this command aswell as starting the app from the start menu or shortcut
https://www.electronjs.org/docs/latest/tutorial/notifications#windows

Neat, thanks! Just two nits and I'll merge this.

I think I've done it correctly if you can verify please?

Neat, thanks! Just two nits and I'll merge this.

I think I've done it correctly if you can verify please?

@si458 perfect. Merging, will ship with the next release, in a few days/weeks. Thanks!

Is there any way to fix https://github.com/nativefier/nativefier/issues/1253 like this PR does?


Usage with npm

Are you planning on publishing this to npm ? I'd like to use URL in a node bundle but wasn't able to find any other polyfills.
Thanks,
Dave

nevermind! found https://github.com/defunctzombie/node-url#readme


Top priority - Restrict basic sku on these regions when creating/updating a firewall

Related command
az network firewall create, az network firewall update
Is your feature request related to a problem? Please describe.
Can you please block creating/updating a firewall on these regions since basic sku firewall is not available in these regions yet? Taiwan North, Canada East, Jlo India West, Poland Central, Spain Central, USSec West Central, Belgium Central, Germany North, Sweden South, China East 3
Describe the solution you'd like

Describe alternatives you've considered

Additional context

network feature

should be handled by the server side


ODPI-109 - Output bash and java version in test runners

Someone smarter than me test this ( i.e. @alanfgates, @rvs, or @c0s )

Looks about right. Please merge in.


Default partitioning not respected with StreamBridge

Describe the issue
After upgrading to version 4.0.4 we noticed that default partitioning is not working as expected (key.hashCode() % partitionCount) when using StreamBridge. It can be possibly associated with this commented block: https://github.com/spring-cloud/spring-cloud-stream/blob/e06d4eedfd70302f0ba7241adb3e3e3d8d8b00d5/core/spring-cloud-stream/src/main/java/org/springframework/cloud/stream/function/StreamBridge.java#L263. Before, if condition is met, DefaultPartitionInterceptor was added and partitionHandler.determinePartition(message) was called, which is not the case now in version 4.0.4.
To Reproduce
We are using Spring Cloud Stream functions. The message key is a very simple record schema.
Steps to reproduce the behavior:

Set the configuration properties

spring.cloud.stream:
  default:
    producer:
      useNativeEncoding: true
      partition-key-expression: headers['kafka_messageKey'].id
    consumer.useNativeDecoding: true
  function.autodetect: false
  bindings:
    testEventSource-out-0:
      destination: test-event
  kafka:
    binder:
      auto-create-topics: false
      producer-properties:
        key.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
        value.serializer: io.confluent.kafka.serializers.KafkaAvroSerializer
        key.subject.name.strategy: io.confluent.kafka.serializers.subject.TopicRecordNameStrategy
        value.subject.name.strategy: io.confluent.kafka.serializers.subject.TopicRecordNameStrategy

Run the following integration test

void sendEvent_whenUsingStreamBridge_shouldRespectPartitioningScheme() {
        final int numberOfPartitions = 6;

        final Message<KafkaNull> outgoingMessage = MessageBuilder.withPayload(KafkaNull.INSTANCE)
                .setHeader(KafkaHeaders.KEY, TestEventKey.newBuilder().setId(1001L).build())
                .build();

        streamBridge.send("testEventSource-out-0", outgoingMessage);

        final ConsumerRecords<Object, Object> records = testConsumer.poll(Duration.ofSeconds(5L));
        assertThat(records.iterator().next().partition()).isEqualTo(eventId % numberOfPartitions);
    }

We have used KafkaNull.INSTANCE but it's the same behaviour with the regular message.
4. See the failed assertion
Version of the framework
SpringBoot 3.1.2
SpringCloudStream 4.0.4
Expected behavior
When using defaults partition should be selected based on the following function: (key.hashCode() % partitionCount).

I literally just cut/paste your code and i get
Invalid value io.confluent.kafka.serializers.KafkaAvroSerializer for configuration key.serializer: Class io.confluent.kafka.serializers.KafkaAvroSerializer could not be found.
	at org.apache.kafka.common.config.ConfigDef.parseType(ConfigDef.java:744) ~[kafka-clients-3.5.1.jar:na]
	at org.apache.kafka.common.config.ConfigDef.parseValue(ConfigDef.java:490) ~[kafka-clients-3.5.1.jar:na]
. . . .

If you want as to look at the issue please provide a way to reproduce it. The best thing you can do is create a small project with reproducible code an push it to github so we can take a look.


How do I use this module in Rasspberry Pi

I can use this module to establish a wifi connection in Windows, my code is as follows：
wifi=PyWiFi()
ifaces=wifi.interfaces()[0]
print(ifaces.name())
print(const.IFACE_CONNECTED)
print(const.IFACE_INACTIVE)
profile = pywifi.Profile()
profile.ssid = ""
profile.auth = const.AUTH_ALG_OPEN
profile.akm.append(const.AKM_TYPE_WPA2PSK)
profile.cipher = const.CIPHER_TYPE_CCMP
profile.key = "**"
tmp_profile = ifaces.add_network_profile(profile)
ifaces.connect(tmp_profile)
time.sleep(5)
if ifaces.status() == const.IFACE_CONNECTED:
print("OK")
else:
print("ERROR")`
Now I wann make a wifi connection on Raspberry pi，using this code not succeed.
The "Prerequisites" : "On Linux, you will need to run wpa_supplicant to manipulate the wifi devices, and then pywifi can communicate with wpa_supplicant through socket." I think I should start here, but I don't know how to do it in particular. could you give me some advice？ Thanks

I use this module on Raspberry pi and it do not succeed either. However it works on Windows.

Having the same issue. The iface.status() is always 0, but I am sure it already connected to the Network.

Having the same issue~  Anyone can fix it?


GDAES-960 - update uwsgi to support alternate install locations, spec…

… tests, various cleanup

Tons of work here, nice job