[RELEASE] 1.4.3

What's the task? Please describe.
Action items for releasing v1.4.3
Describe the items of the task (DoD, definition of done) you'd like.

Pre-Release

[x] Regression test plan (manual) - @khushboo-rancher
[x] Run e2e regression for pre-GA milestones (install, upgrade) - @yangchiu
[x] Run security testing of container images for pre-GA milestones - @roger-ryao
[x] Verify longhorn chart PR to ensure all artifacts are ready for GA (install, upgrade)  @chriscchien
[ ] Run core testing (install, upgrade) for GA build from the previous patch and the last patch of the previous feature release (1.4.2 & 1.3.3). - @chriscchien

Release

[ ] Release longhorn/chart from the release branch to publish to ArtifactHub
[ ] Release note

[ ] Deprecation note
[ ] Upgrade notes including highlighted notes, deprecation, compatible changes, and others impacting the current users

Post-Release

[ ] ~Create a new release branch of manager/ui/tests/engine/longhorn instance-manager/share-manager/backing-image-manager when creating the RC1~
[ ] Update https://github.com/longhorn/longhorn/blob/master/deploy/upgrade_responder_server/chart-values.yaml @PhanLe1010
[ ] Add another request for the rancher charts for the next patch release (1.4.3) @rebeccazzzz

Rancher charts: verify the chart is able to install & upgrade - @khushboo-rancher

[ ] rancher/image-mirrors update @weizhe0422 (@PhanLe1010 )
[ ] rancher/charts 2.7 branches for rancher marketplace @weizhe0422 (@PhanLe1010)

dev-2.7: https://github.com/rancher/charts/pull/2622

cc @longhorn/qa @longhorn/dev

Run security testing of container images for pre-GA milestones:
v1.4.3-rc1: 71 HIGH, 0 CRITICAL

Run e2e regression for pre-GA milestones (install, upgrade):
v1.4.3-rc1:
amd64: 4 failures
arm64: 3 failures
amd64 upgrade: 4 failures
arm64 upgrade: 4 failures

Run security testing of container images for pre-GA milestones:
v1.4.3-rc2: 67 HIGH, 0 CRITICAL

Run core testing (install, upgrade) for GA build from the previous patch and the last patch of the previous feature release (1.4.2):
amd64:
arm64:
amd64 upgrade from v1.4.2:
arm64 upgrade from v1.4.2:

Verify longhorn chart PR to ensure all artifacts are ready for GA (install, upgrade) @chriscchien - passed

Test result for /longhorn/chart PR
Test result for /charts PR

@PhanLe1010 @rebeccazzzz @weizhe0422 @khushboo-rancher Please help with post-release items. Thanks.

UPDATE: Two PRs have been created covering generating mirrors (https://github.com/rancher/image-mirror/pull/416) and Rancher charts files (https://github.com/rancher/charts/pull/2780), I will follow PR comments. Also, I update the task status.


Text from feeds can set the mode (and give errors)

One of my feeds contains the text "Easy way to add -- mode: org; -- to my notes files?"
This gives an error message upon starting elfeed, because set-auto-mode() is called after loading the database, which tries to activate org-mode, leading to a 'stack overflow in regexp' error.
elfeed_bug.txt

Very interesting bug! I hadn't expected this behavior from Emacs, though it makes sense. I imagine the scan for local variables was slowing down Elfeed's startup, too. I believe 40d892c fixes it.
Fortunately this isn't a security issue since Emacs is (rightfully) very conservative about local variables in files. I'm considering opening the index file differently to prevent any other sort of Emacs magic from happening.

It's working working fine with the new version, thanks!


completion fails with ValueError

Hi,
thx for your work on the server. I really appreciate it.
I am using the server with neovim. Unfortunately the completion does not properly work. Most of the time the log has the following errors:
ValueError: too many values to unpack (expected 2)

salt-server.log

Could you also upload the file that you were editing?

I made a simple top.sls file and post the log here. There are multiple errors in the log. I am not sure which one messes up the completions.
salt-server.log
base:
  '*':
    - pkg.installed:

Hi @benatouba,
is the code block the whole top.sls file you have? As far as I know you need two files, the top.sls which contains a mapping of minions to SLS files and (at least) one SLS file itself.
For example:
# /srv/salt/top.sls
base:
  '*':                     # matches all minions
    - test                 # matches test.sls, assigned to all matched minions

# /srv/salt/test.sls
vim:
  pkg.installed

Do you get the same error with a SLS file setup like I described?

I think both the ValueError: too many values to unpack (expected 2) and many of the yaml.scanner.ScannerError are fixed with #20

@benatouba Could you recheck with the latest state from main?

As it looks to me right now, the updates solved this issue. I still get no completion but that might have a different source.
The log does only show "yaml.scan.errrors" with jinja templates (%). But that is not yet implemented, right?

Benjamin Schmidt @.***> writes:

As it looks to me right now, the updates solved this issue. I still get no completion but that might have a different source.
The log does only show "yaml.scan.errrors" with jinja templates (%). But that is not yet implemented, right?

You are (unfortunately) correct, we did not get around to implement yaml
templates yet.

Thx for the work so far. There still seem to be some problems with getting completion but I need to find out whether they might just be on my end.

Now I get completion for submodules, some time after I open the file. It seems to take some time. Here is the log file for the test.sls suggested by @agraul . As you can see there are no errors in the log. Maybe there is still helpful stuff for you in there.
salt-server.log


Fix NodeJS DEVELOPER.md

DEVELOPER.md instructions for new linux env are prone to errors, since apt install node v12 OOB, we need to fix the instructions by adding node -v step after installation and add handling instructions for version lower than v16

https://github.com/aws/glide-for-redis/pull/1321
Fixed


BAEL-7775 mybatis-plus module added with CRUD and other features

BAEL-7775 - Introduction to MyBatis-Plus, mybatis-plus module added

retest this please

retest this please

@theangrydev It looks good now.


modctl failed to handle repository path with ports

$modctl build -t example.com:5000/library/llama3:v1.0.0 -f Modelfile .
Built blob      =>  (0 B)
Built blob      =>  (0 B)
Built blob      =>  (0 B)
Error: faile to build image config: failed to push config to storage: filesystem: invalid path: /docker/registry/v2/repositories/example.com:5000/library/llama3/_uploads/919a8686-88f0-48d7-9b12-a8f104a9b7c5/startedat

Close as resolved.


Fix binary classification bug #7

I've also encountered the problem in #7 and tracked it down to first to the same line as @pgagarinov, then I digged a bit more. It seems the issue was that when num_classes=2 the num_classes should not be passed into XGBoost. That fixes the problem in the issue but brought up another one, namely that when silent = false, then XGBoost evaluates the wrong metric resulting again in a different error:
Check failed: preds.Size() == info.labels_.Size() (2000 vs. 1000) :  labels are not correctly providedpreds.size=2000, label.size=1000, Loss: binary:logistic
This can be fixed by noticing that eval_metric is corrected, but not passed into the function, so I've changed kwargs(model, silent, seed, objective) to kwargs(model, silent, seed, objective,eval_metric) and using the appropriate values.
I'm not sure where these changes would break other codes, but I've added a test (and bumped the verbosity for all the others to check it this will occur again) and they seem to run (both for silent = true and silent = false, even though the previously set misclassification_rate check in some tests do error, I guess they were chosen arbitrarily?) and now it is possible to use XGBoost in MLJ pipelines for binary classifications.

I also ran into #7 and can confirm that this PR solves it for me.

label must be in [0, num_class), num_class=1 but found 1 in label

hitting this now, can we merge this maybe?


OOV FID calculate questions

I have read your article GANwriting: Content-Conditioned Generation of Styled Handwritten Word Images and your code, and I am confused about how to calculate the FID of the OOV words.
I noticed that in your article you mentioned that you prepared 400 unique words to test the OOV performance, but there are only 80 words in your file corpora_english/oov.common_words , I have a few questions:

If it is actually 400 words, could you please give me the word list?
Is the OOV FID calculated by averaging of the FID scores of each handwriting style or directly performing evaluation on randomly sampled generated images?

Thank you for your amazing work.  I have the same question about the file "oov.common_words".  Could you share the complete list of 400 oov words？

I have read your article GANwriting: Content-Conditioned Generation of Styled Handwritten Word Images and your code, and I am confused about how to calculate the FID of the OOV words. I noticed that in your article you mentioned that you prepared 400 unique words to test the OOV performance, but there are only 80 words in your file corpora_english/oov.common_words , I have a few questions:

If it is actually 400 words, could you please give me the word list?
Is the OOV FID calculated by averaging of the FID scores of each handwriting style or directly performing evaluation on randomly sampled generated images?

Hello, Can you tell me  how to use OOV_word.text to calculate the FID value of OOV.  I hope I can get your guidance and help

Hello, Can you tell me how to use OOV_word.text to calculate the FID value of OOV. I hope I can get your guidance and help

Hello, Could you tell me how to use OOV_word.text to calculate the FID value of OOV. I hope I can get your guidance and help

I have read your article GANwriting: Content-Conditioned Generation of Styled Handwritten Word Images and your code, and I am confused about how to calculate the FID of the OOV words. I noticed that in your article you mentioned that you prepared 400 unique words to test the OOV performance, but there are only 80 words in your file corpora_english/oov.common_words , I have a few questions:

If it is actually 400 words, could you please give me the word list?
Is the OOV FID calculated by averaging of the FID scores of each handwriting style or directly performing evaluation on randomly sampled generated images?

Hello, Could you tell me how to use OOV_word.text to calculate the FID value of OOV. I hope I can get your guidance and help

Thank you for your amazing work. I have the same question about the file "oov.common_words". Could you share the complete list of 400 oov words？

Hello, Could you tell me how to use OOV_word.text to calculate the FID value of OOV. I hope I can get your guidance and help


Serialization issue in withItems leading to duplicate tasks

Summary
With argo version 3.2.6, when submitting workflows that use withItems where the value has double quotes inside of single quotes (ie: value: '"foo"') then each task is doubled where the duplicate task contains a different quote-escape of the parameters.
Note that this single-double quoting is a result of hera-workflows sending json blobs back and forth.
Name:                test9ckrq
Namespace:           etl
ServiceAccount:      default
Status:              Running
Created:             Wed Feb 16 19:15:48 +0100 (1 second ago)
Started:             Wed Feb 16 19:15:48 +0100 (1 second ago)
Duration:            1 second
Progress:            0/1

STEP                          TEMPLATE       PODNAME               DURATION  MESSAGE
 ● test9ckrq                  test-workflow
 ├─◷ test-task(0:a:\"test\")  test-task      test9ckrq-2427085523  1s
 └─◷ test-task(0:a:"test")    test-task      test9ckrq-3392308087  1s

Interestingly, once the jobs complete, argo watch doesn't show the duplicate for successful tasks but if we look at the logs we can see both runs.
$ argo -n etl watch @latest
Name:                test9ckrq
Namespace:           etl
ServiceAccount:      default
Status:              Succeeded
Conditions:
 PodRunning          False
 Completed           True
Created:             Wed Feb 16 19:15:48 +0100 (16 seconds ago)
Started:             Wed Feb 16 19:15:48 +0100 (16 seconds ago)
Finished:            Wed Feb 16 19:15:58 +0100 (6 seconds ago)
Duration:            10 seconds
Progress:            1/1
ResourcesDuration:   1s*(1 cpu),1s*(100Mi memory)

STEP                          TEMPLATE       PODNAME               DURATION  MESSAGE
 ✔ test9ckrq                  test-workflow
 └─✔ test-task(0:a:\"test\")  test-task      test9ckrq-2427085523  4s

$ argo -n etl logs @latest
test9ckrq-3392308087: test
test9ckrq-2427085523: test

Diagnostics
This is the simplest workflow that reproduces the issue. Simply changing a: '"test"' to a: "test" solves the issue of the duplicate tasks, however this isn't a reasonable solution since it means we can't send json in this field.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: test
spec:
  entrypoint: test-workflow
  templates:
    - name: test-workflow
      dag:
        tasks:
          - name: test-task
            template: test-task
            arguments:
              parameters:
                - name: a
                  value: '{{item.a}}'
            withItems:
              - a: '"test"'
    - name: test-task
      inputs:
        parameters:
          - name: a
            value: '{{item.a}}'
      script:
        name: test-task
        image: 'python:3.7'
        command:
          - python
        source: |
          import json
          a = json.loads('{{inputs.parameters.a}}')

          print(a)

Interestingly, the duplicate task doesn't show up in the controller logs.
$ kubectl logs -n etl-argo-v3 deploy/argo-argo-workflows-workflow-controller | grep test9ckrq
time="2022-02-16T18:15:48.788Z" level=info msg="Processing workflow" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.793Z" level=info msg="Updated phase  -> Running" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.793Z" level=info msg="DAG node test9ckrq initialized Running" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.793Z" level=info msg="TaskGroup node test9ckrq-4247033023 initialized Running (message: )" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.793Z" level=info msg="All of node test9ckrq.test-task(0:a:\\\"test\\\") dependencies [] completed" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.794Z" level=info msg="Pod node test9ckrq-2427085523 initialized Pending" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.820Z" level=info msg="Created pod: test9ckrq.test-task(0:a:\\\"test\\\") (test9ckrq-2427085523)" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.821Z" level=info msg="TaskSet Reconciliation" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.821Z" level=info msg=reconcileAgentPod namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.832Z" level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"test9ckrq\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.832Z" level=info msg="Re-applying updates on latest version and retrying update" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.846Z" level=info msg="Update retry attempt 1 successful" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:48.846Z" level=info msg="Workflow update successful" namespace=etl-argo-v3 phase=Running resourceVersion=997292078 workflow=test9ckrq
time="2022-02-16T18:15:58.817Z" level=info msg="Processing workflow" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.817Z" level=info msg="Updating node test9ckrq-2427085523 exit code 0" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="Updating node test9ckrq-2427085523 status Pending -> Succeeded" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="node test9ckrq-4247033023 phase Running -> Succeeded" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="node test9ckrq-4247033023 finished: 2022-02-16 18:15:58.818693885 +0000 UTC" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="Outbound nodes of test9ckrq set to [test9ckrq-2427085523]" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="node test9ckrq phase Running -> Succeeded" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.818Z" level=info msg="node test9ckrq finished: 2022-02-16 18:15:58.81895713 +0000 UTC" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg="Checking daemoned children of test9ckrq" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg="TaskSet Reconciliation" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg=reconcileAgentPod namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg="Updated phase Running -> Succeeded" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg="Marking workflow completed" namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.819Z" level=info msg="Checking daemoned children of " namespace=etl-argo-v3 workflow=test9ckrq
time="2022-02-16T18:15:58.831Z" level=info msg="Workflow update successful" namespace=etl-argo-v3 phase=Succeeded resourceVersion=997292181 workflow=test9ckrq
time="2022-02-16T18:15:58.838Z" level=info msg="cleaning up pod" action=labelPodCompleted key=etl-argo-v3/test9ckrq-2427085523/labelPodCompleted

Some information about my argo install,
$ kubectl -n etl get configmap argo-argo-workflows-workflow-controller-configmap -o yaml
apiVersion: v1
data:
  config: |
    containerRuntimeExecutor: docker
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: argo
    meta.helm.sh/release-namespace: etl
  creationTimestamp: "2022-02-09T05:56:51Z"
  labels:
    app.kubernetes.io/component: workflow-controller
    app.kubernetes.io/instance: argo
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: argo-workflows-cm
    app.kubernetes.io/part-of: argo-workflows
    helm.sh/chart: argo-workflows-0.10.0
  name: argo-argo-workflows-workflow-controller-configmap
  namespace: etl-argo-v3

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Poking around, it seems like this may be part of the issue: https://github.com/argoproj/argo-workflows/blob/master/pkg/apis/workflow/v1alpha1/item.go#L67-L71

I knew that code would cause problem. I'm not sure this is fixable due to inherent problems with the design of Item.
Instead, I think we need #7801

I take this back. I think this is just a bug.

@alexec thanks so much for looking into this!

I've run latest and I do not see this behaviour:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"argoproj.io/v1alpha1","kind":"Workflow","metadata":{"annotations":{},"name":"test","namespace":"argo"},"spec":{"entrypoint":"test-workflow","templates":[{"dag":{"tasks":[{"arguments":{"parameters":[{"name":"a","value":"{{item.a}}"}]},"name":"test-task","template":"test-task","withItems":[{"a":"\"test\""}]}]},"name":"test-workflow"},{"inputs":{"parameters":[{"name":"a","value":"{{item.a}}"}]},"name":"test-task","script":{"command":["python"],"image":"python:3.7","name":"test-task","source":"import json\na = json.loads('{{inputs.parameters.a}}')\n\nprint(a)\n"}}]}}
    workflows.argoproj.io/pod-name-format: v1
  creationTimestamp: "2022-02-17T17:28:29Z"
  generation: 4
  labels:
    workflows.argoproj.io/phase: Running
  name: test
  namespace: argo
  resourceVersion: "21187"
  uid: 41cae1f0-8d59-440f-a0a3-7855d0acfa94
spec:
  activeDeadlineSeconds: 300
  arguments: {}
  entrypoint: test-workflow
  podSpecPatch: |
    terminationGracePeriodSeconds: 3
  templates:
    - dag:
        tasks:
          - arguments:
              parameters:
                - name: a
                  value: '{{item.a}}'
            name: test-task
            template: test-task
            withItems:
              - a: '"test"'
      inputs: {}
      metadata: {}
      name: test-workflow
      outputs: {}
    - inputs:
        parameters:
          - name: a
            value: '{{item.a}}'
      metadata: {}
      name: test-task
      outputs: {}
      script:
        command:
          - python
        image: python:3.7
        name: test-task
        resources: {}
        source: |
          import json
          a = json.loads('{{inputs.parameters.a}}')

          print(a)
  ttlStrategy:
    secondsAfterCompletion: 600
status:
  artifactRepositoryRef:
    artifactRepository:
      archiveLogs: true
      s3:
        accessKeySecret:
          key: accesskey
          name: my-minio-cred
        bucket: my-bucket
        endpoint: minio:9000
        insecure: true
        secretKeySecret:
          key: secretkey
          name: my-minio-cred
    configMap: artifact-repositories
    key: default-v1
    namespace: argo
  conditions:
    - status: "False"
      type: PodRunning
  finishedAt: null
  nodes:
    test:
      children:
        - test-2744414361
      displayName: test
      finishedAt: null
      id: test
      name: test
      phase: Running
      progress: 0/1
      startedAt: "2022-02-17T17:28:29Z"
      templateName: test-workflow
      templateScope: local/test
      type: DAG
    test-2560562737:
      boundaryID: test
      displayName: test-task(0:a:\"test\")
      finishedAt: null
      hostNodeName: minikube
      id: test-2560562737
      inputs:
        parameters:
          - name: a
            value: \"test\"
      message: PodInitializing
      name: test.test-task(0:a:\"test\")
      phase: Pending
      progress: 0/1
      startedAt: "2022-02-17T17:28:29Z"
      templateName: test-task
      templateScope: local/test
      type: Pod
    test-2744414361:
      boundaryID: test
      children:
        - test-2560562737
      displayName: test-task
      finishedAt: null
      id: test-2744414361
      name: test.test-task
      phase: Running
      progress: 0/1
      startedAt: "2022-02-17T17:28:29Z"
      templateName: test-task
      templateScope: local/test
      type: TaskGroup
  phase: Running
  progress: 0/1
  startedAt: "2022-02-17T17:28:29Z"

@alexec Strange! Oddly enough I get the same type of output as you... no reference to the test9ckrq-2427085523 node which was alive before the job was finished and which added to the logs (from argo -n etl logs @latest).
I've got v3.2.6 client and controller. Here is the output for the workflow from my first post:
$ kubectl get wf -o yaml test9ckrq -n etl-argo-v3
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  annotations:
    workflows.argoproj.io/pod-name-format: v1
  creationTimestamp: "2022-02-16T18:15:48Z"
  generateName: test
  generation: 4
  labels:
    workflows.argoproj.io/completed: "true"
    workflows.argoproj.io/phase: Succeeded
  name: test9ckrq
  namespace: etl-argo-v3
  resourceVersion: "997292181"
  uid: 74cfe0a4-0cbf-49f2-8289-415d20173259
spec:
  arguments: {}
  entrypoint: test-workflow
  templates:
  - dag:
      tasks:
      - arguments:
          parameters:
          - name: a
            value: '{{item.a}}'
        name: test-task
        template: test-task
        withItems:
        - a: '"test"'
    inputs: {}
    metadata: {}
    name: test-workflow
    outputs: {}
  - inputs:
      parameters:
      - name: a
        value: '{{item.a}}'
    metadata: {}
    name: test-task
    outputs: {}
    script:
      command:
      - python
      image: python:3.7
      name: test-task
      resources: {}
      source: |
        import json
        a = json.loads('{{inputs.parameters.a}}')

        print(a)
status:
  artifactRepositoryRef:
    artifactRepository: {}
    default: true
  conditions:
  - status: "False"
    type: PodRunning
  - status: "True"
    type: Completed
  finishedAt: "2022-02-16T18:15:58Z"
  nodes:
    test9ckrq:
      children:
      - test9ckrq-4247033023
      displayName: test9ckrq
      finishedAt: "2022-02-16T18:15:58Z"
      id: test9ckrq
      name: test9ckrq
      outboundNodes:
      - test9ckrq-2427085523
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2022-02-16T18:15:48Z"
      templateName: test-workflow
      templateScope: local/test9ckrq
      type: DAG
    test9ckrq-2427085523:
      boundaryID: test9ckrq
      displayName: test-task(0:a:\"test\")
      finishedAt: "2022-02-16T18:15:52Z"
      hostNodeName: gke-production-generic-68da36a8-8btm
      id: test9ckrq-2427085523
      inputs:
        parameters:
        - name: a
          value: \"test\"
      name: test9ckrq.test-task(0:a:\"test\")
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2022-02-16T18:15:48Z"
      templateName: test-task
      templateScope: local/test9ckrq
      type: Pod
    test9ckrq-4247033023:
      boundaryID: test9ckrq
      children:
      - test9ckrq-2427085523
      displayName: test-task
      finishedAt: "2022-02-16T18:15:58Z"
      id: test9ckrq-4247033023
      name: test9ckrq.test-task
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2022-02-16T18:15:48Z"
      templateName: test-task
      templateScope: local/test9ckrq
      type: TaskGroup
  phase: Succeeded
  progress: 1/1
  resourcesDuration:
    cpu: 1
    memory: 1
  startedAt: "2022-02-16T18:15:48Z"

In your YAML I do not see the duplicated node under spec.nodes. I hypothesies that this this is a CLI only issue. That then makes me wonder if it has been fixed in a more recent version.
To test this hypothesis, could you do either of the following

Confirm that a second pod was created, e.g. starting kubectl get pods -w while running the workflow.
Upgrade your CLI to the latest version and run the test again.

Confirm that a second pod was created, e.g. starting kubectl get pods -w while running the workflow.

@alexec I'd also like to confirm there are no duplicate pods created. I tested this when @mynameisfiber first reported this on Hera.

Unless this can be reproduced, we cannot fix this. I’m not sure how to proceed.

@alexec do you not see the duplicate log entries when running the test workflow? So far the outputs we've both shared are consistent with one-another and the logs are the only place, once the workflow is finished, where this duplicate task is recorded.
Running kubectl get pods -w doesn't show the duplicate tasks either. All this seems to be pointing to the fact that these duplicate tasks are just in the CLI. However, this issue first came up because I was getting race-conditions in some sql table being updated by a task... this could only have happened if this phantom task actually does run.

Actually, I do see them both starting in the PodInitializing phase!
$ argo watch @latest -n etl-argo-v3
Name:                test48tlp
Namespace:           etl-argo-v3
ServiceAccount:      default
Status:              Succeeded
Conditions:
 PodRunning          False
 Completed           True
Created:             Mon Feb 21 19:04:31 +0100 (1 minute ago)
Started:             Mon Feb 21 19:04:31 +0100 (1 minute ago)
Finished:            Mon Feb 21 19:05:39 +0100 (now)
Duration:            1 minute 8 seconds
Progress:            2/2
ResourcesDuration:   2m13s*(1 cpu),2m13s*(100Mi memory)

STEP                          TEMPLATE       PODNAME               DURATION  MESSAGE
 ✔ test48tlp                  test-workflow
 ├─✔ test-task(0:a:\"test\")  test-task      test48tlp-4057174963  57s
 └─✔ test-task(0:a:"test")    test-task      test48tlp-3851843159  51s

Meanwhile:
$ kubectl get pods -n etl-argo-v3
...
test48tlp-3851843159                                       0/2     PodInitializing      0          20s
test48tlp-4057174963                                       0/2     PodInitializing      0          20s

... later ...
$ kubectl get pods -n etl-argo-v3
...
test48tlp-3851843159                                       0/2     Completed            0          2m30s
test48tlp-4057174963                                       0/2     Completed            0          2m30s
...

This is with:
$ argo version
argo: v3.2.6
  BuildDate: 2021-12-17T20:59:31Z
  GitCommit: db7d90a1f609685cfda73644155854b06fa5d28b
  GitTreeState: clean
  GitTag: v3.2.6
  GoVersion: go1.16.12
  Compiler: gc
  Platform: linux/amd64

Upgraded CLI leads to the same behavior :
$ argo watch @latest -n etl-argo-v3
...
 ✔ testcnmrx                  test-workflow
 ├─✔ test-task(0:a:"test")    test-task      testcnmrx-1857363345  23s
 └─✔ test-task(0:a:\"test\")  test-task      testcnmrx-620009245   24s

$ argo version
argo: v3.2.8
  BuildDate: 2022-02-04T20:06:09Z
  GitCommit: 8de5416ac6b8f5640a8603e374d99a18a04b5c8d
  GitTreeState: clean
  GitTag: v3.2.8
  GoVersion: go1.16.13
  Compiler: gc
  Platform: linux/amd64

There is some inconsistencies with some of the data here. For example, you should never two pods unless you have two pod nodes with in your YAML - you do not have these.
Your log file shows a conflict error. This can occur when there are two workflow controllers running in a single cluster, both trying to update the same workflow. Could you check to make sure this is not the case so that we can remove that as a potential cause?

@alexec we indeed have two controllers running, but they are in different namespaces. I take it that this is a mistake? We have the etl namespace which is running argo <v3 and etl-argo-v3 where we are testing argo v3.2.6.

Here are the controllers... both namespaces installed with the argo helm charts.
$ kubectl get deploy -n etl-argo-v3
NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
argo-argo-workflows-server                1/1     1            1           13d
argo-argo-workflows-workflow-controller   1/1     1            1           13d

$ kubectl get deploy -n etl
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
argo-server                1/1     1            1           328d
argo-workflow-controller   1/1     1            1           328d

Are they different versions? Are they configured with --managed-namespace?

@alexec sorry for the long delay in response... I was off of this project for a little bit. So it turns out that --managed-namespace wasn't configured for the argo instances. I do think, however, that this should be addressed because it is quite confusing undefined behavior. I think at the least a warning that the user may be encountering this behavior would be useful for debugging purposes.


Added the option to add aes256 sse

My org, and I would imagine others, prefers to encrypt s3 buckets even when not entirely necessary just for uniformity in our internal security audits.
This fixes https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/issues/54

Thanks for the review @aknysh, I changed the names, rebuilt the README.md, and formatted the code

@dmattia  please rebase

@dmattia please rebase

Just rebased @aknysh, thanks!

/codefresh run test

@aknysh Readme has been updated

/codefresh run test


Wait for leadership finish and exclude new topics

ARUHA-3130: Bubuku may hang up on start
Bubuku may hang up on start for new topics being under creation. For example:
  WARNING:bubuku.broker:Leadership is not transferred for 769c2845-4aee-4b38-8b80-087cc08817e4 2 ({"controller_epoch": 61, "leader": -1, "version": 1, "leader_epoch": 110, "isr": [67123066]}, brokers: ['67123027', '67123028', '67123033', '67123034', '67123035', '67123036', '67123037', '67123038', '67123039', '67123040', '67123041', '67123044', '67123046', '67123047', '67123048', '67123049', '67123050', '67123051', '67123052', '67123053', '67123055', '67123056', '67123057', '67123058', '67123059', '67123060', '67123061', '67123062', '67123063', '67123064', '67123065', '67123066', '67123427'])

In this pull request, I change the code to wait indefinitely for leadership transfer to complete since we start brokers sequentially during a rolling restart and none of the brokers would start if any leadership transfer is in progress.
Since leadership transfer check is done for both starting and stopping of brokers, also added a check to remove topics of certain age from the check. That is implemented by querying zookeeper for created_at time.

I was thinking about the case when such a situation with restart of controller would arise when topic-partition leader would be =1, considering a newly created topic. Even with restarts/switch of the controller, eventually a leader should be successfully elected eventually.
In the case which is presented in the ticket, I think the issue was actually with a topic being deleted. A deleted topic is still part of /broker/topics children, and is apparently not cleaned up from there until the log cleaner deletes the data from the brokers. Please find an example case produced locally for this case:
[zk: localhost:2181(CONNECTED) 11] ls /admin/delete_topics
[test]
[zk: localhost:2181(CONNECTED) 12] ls /brokers/topics
[party1, party2, party3, test, party4]
[zk: localhost:2181(CONNECTED) 13] get /brokers/topics/test/partitions/0/state
{"controller_epoch":14,"leader":-1,"version":1,"leader_epoch":17,"isr":[67108865]}
cZxid = 0xc5
ctime = Wed Oct 21 00:29:11 UTC 2020
mZxid = 0x21ad
mtime = Wed Oct 21 22:05:12 UTC 2020
pZxid = 0xc5
cversion = 0
dataVersion = 18
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 82
numChildren = 0
[zk: localhost:2181(CONNECTED) 14]

In the bug happening on live, Kafka was taking a long time (~30 minutes), possibly due to broker restarts to delete the topic partitions logs and the log trail can be found here.
Initially, considering leader election for a topic, I've added code to filter out topics by creation time and age. However, now I've modified it to exclude deleted topics while considering leader election.

👍

:+1:


ansible-galaxy install throws error

I'm getting the error in #158 and have tried the "sudo ansible-galaxy install ..." solution, which installs lots of useful looking roles, but then bombs out with:
- downloading role 'php', owned by geerlingguy
https://galaxy.ansible.com/roles/432/versions/?page=2&page_size=50
Traceback (most recent call last):
  File "/usr/local/bin/ansible-galaxy", line 959, in <module>
    main()
  File "/usr/local/bin/ansible-galaxy", line 953, in main
    fn(args, options, parser)
  File "/usr/local/bin/ansible-galaxy", line 819, in execute_install
    if len(role_versions) > 0:
TypeError: object of type 'NoneType' has no len()

Any idea what's going wrong with this?

What version of Ansible are you using (you can check by typing ansible --version into your Terminal)?
If it's less than 2.0, you'll need to update it.

OK, it's ansible 1.9.4

Yeah, update it so that it's 2.0 or greater. I'm currently running <IP_ADDRESS> that I've installed via pip.
Then try the ansible-galaxy command again. :)

Thanks - this seems to have cleaned everything up:
sudo pip install --upgrade pip
sudo pip install --upgrade ansible
sudo ansible-galaxy install -r provisioning/requirements.yml --force

There was just one warning between drupal console and php.  Not sure which it was referring to:
[DEPRECATION WARNING]: The comma separated role spec format, use the yaml/explicit format instead.. This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

That deprecation notice will be fixed after the next drupal-console release. Just some old YAML syntax hanging around in the meta file in that role :)

Unfortunately I'm still seeing the same error reported above (TypeError: object of type 'NoneType' has no len() for the php package), on Ansible <IP_ADDRESS>.

Hmm, not sure why it's happening. I'll have to try to test as well—can you let me know what system/environment you're running the command on?


ci: Spin-up new server for each test run

As discussed, all tests are now wired up to run against localhost:3000.
CI config now spins up a new speckle server in the same way we're doing so for .Net
Python tests should be run against your own local server if needed.

Tests are not passing but it appears to be unrelated to this change. Will open new issue.


Handle reset vector not pointing to ELF symbol

Closes #391

Output of running probe-run --chip RP2040 target/thumbv6m-none-eabi/debug/rp2040-project-template -v and then aborting with CTRL-C, with the fixed binary:
probe-run.log

Merge conflict.

I'll have a look.

bors retry
Thank you for your work @jannic


Add circular Progress Component

Current Behavior

Desired Behavior

Screenshots / Mockups

@thekavikumar i also want to contribute to this issue please assign me as well

Please assign it to me under gssoc'23. I would like to work upon this issue.


Not able to connect my Bot from skype and Webchat.

Bot Info

Bot handle: QnA_Moz
App ID: b2bc75ea-2a39-4263-89bc-ec62804ff18f
SDK Platform: .NET
SDK Version:
Active Channels: <!-- Skype, WebChat>
Deployment Environment: Azure Web App

Issue Description
Not able to connect my Bot from skype and Webchat.
The bot is to Skype and in My Client application for Webchat. But not receiving any Greeting message
from bot.which is not received in Skype and Webchat.
Please help me to get this sorted

There is some sort of error with your bot, have you tried debugging locally with ngrok? https://docs.microsoft.com/en-us/bot-framework/debug-bots-emulator

Already done testing my hosted API with Emulator and ngrok. It works perfectly fine here. Is this something to do something with AI integrationg with Skype?

What version of the botbuilder SDK are you using?

Closing the issue assuming it as resolved. Feel free to reopen if you questions or comments.


fix(monitor,suggestion): order commonalert metric and modify alertresoruce type value and add suggestion models climc

这个 PR 实现什么功能/修复什么问题:
1.修改监控metric排序
2.统一报警资源type和监控报警中res_type 进行统一，前端可以统一展示
3.增加suggestion服务相关climc
是否需要 backport 到之前的 release 分支:

release/3.6
release/3.7

/cc @zexi
/area monitor

Codecov Report

Merging #9782 (b23519b) into master (5d6ffa1) will increase coverage by 2.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9782       +/-   ##
==========================================
+ Coverage    5.98%   8.06%    +2.07%
==========================================
  Files         848     107      -741
  Lines      131744   12978   -118766
==========================================
- Hits         7889    1047     -6842
+ Misses     123154   11811   -111343
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.06% <ø> (+2.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/multicloud/aws/dnsrecordset.go

pkg/mcclient/options/dnszone_recordsets.go

pkg/monitor/alerting/conditions/evaluator.go

pkg/util/qemuimg/init.go

pkg/multicloud/aws/aws.go

pkg/multicloud/aws/dnstrafficpolicy.go

pkg/baremetal/utils/ipmitool/ipmitool.go

pkg/mcclient/options/servers.go

pkg/baremetal/tasks/basedeploy.go

pkg/util/httputils/error.go

... and 729 more

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 5d6ffa1...b23519b. Read the comment docs.

Codecov Report

Merging #9782 (b23519b) into master (5d6ffa1) will increase coverage by 2.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9782       +/-   ##
==========================================
+ Coverage    5.98%   8.06%    +2.07%
==========================================
  Files         848     107      -741
  Lines      131744   12978   -118766
==========================================
- Hits         7889    1047     -6842
+ Misses     123154   11811   -111343
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.06% <ø> (+2.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/multicloud/aws/dnsrecordset.go

pkg/mcclient/options/dnszone_recordsets.go

pkg/monitor/alerting/conditions/evaluator.go

pkg/util/qemuimg/init.go

pkg/multicloud/aws/aws.go

pkg/multicloud/aws/dnstrafficpolicy.go

pkg/baremetal/utils/ipmitool/ipmitool.go

pkg/mcclient/options/servers.go

pkg/baremetal/tasks/basedeploy.go

pkg/util/httputils/error.go

... and 729 more

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 5d6ffa1...b23519b. Read the comment docs.


Use correct audit log configuration in proxy

What changes are proposed in this pull request?
The v1 and v2 versions of proxy use uniform judgment conditions.

also suggest updating the PR title to be Use correct audit log configuration in proxy. thanks

could you also fix the same problem in https://github.com/Alluxio/alluxio/blob/master-2.x/core/server/proxy/src/main/java/alluxio/proxy/s3/S3RestServiceHandler.java#L1521

Done.

alluxio-bot, merge this please


problem while excute winpayloads

Hi,
When i finished install winpayloads this error come out and i search many times but i couldn't fix it the error is :
root@kali:~/Desktop/Winpayloads# ./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 5, in
from lib.menu import *
File "/root/Desktop/Winpayloads/lib/menu.py", line 4, in
from generatepayload import *
File "/root/Desktop/Winpayloads/lib/generatepayload.py", line 3, in
from psexecspray import *
File "/root/Desktop/Winpayloads/lib/psexecspray.py", line 4, in
import blessings
ImportError: No module named blessings
Please Help Me Soon As possible With my regards .

Hi please rerun the setup as it will fix the issue.
Thanks

I Will do it THANKS FOR your attention .

Hi,
i re-setup it  again but it steal have same error

Did you do a got pull first?

No i don't know how please help .

Hi
I Search for git pull and i understand what is and do what you say and it's Working
Thanks For Your Help.


Medium PartialSimpleMedium  and TransportDelay model

Hi,
In the model Processes.TransportDelay, the final equation h_out = u_out + p_out * v_out is not true for the PartialSimpleMedium Interface (Ex : SimpleLiquiWater and ...) . The outlet state is evaluated using h_out and propagate an error on the the outlet temperature due to the term p_out * v_out.
I think the best way to resolve this problem will be to use a function of the Medium package or the model BaseProperties .
u_out=Medium.specificInternalEnergy(Medium.setState_phX(p_out, h_out, Xi_out));
Or
Medium.BaseProperties medium_out;
And then
medium_out.p=p_out;
medium_out.Xi=Xi_out;
medium_out.u=u_out;
medium_out.u=h_out;
An other possibility will be to use a delay directly on the specific enthalpy and not on the specific internal energy. But is this true for a compressible fluid?
What is your feeling ?
Best regards,
François

Yes we might consider using a different approach, i didnt build the model, so i have no idea why they picked internal energy.
However h = u + p*v is the definition of specific enthalpy, and i wouldn't recommond neglecting p*v like PartialSimpleMedium does, and therefor i actually wouldn't recommend using PartialSimpleMedium. This will always yield errors, it just seems like people dont care about it most of the time, e.g. assuming a flow resistance to be isenthalpic (no heat flow, no work) h_in = h_out, yields for PartialSimpleMedium u_in = u_out, which yields T_in = T_out, which yields s_in = s_out, which is not what you would expect for the obviously irreversible process of a flow resistance. For the same reason one can not consider entropy to calculate the outlet state for PartialSimpleMedium, e.g. one can not use h_out = specificEnthalpy_psX(p_out, s_in, X) to calculate the outlet specific enthalpy for an ideal compressor/turbine/pump for PartialSimpleMedium, however for all other media this works, which is another example which shows that PartialSimpleMedium is not useful in my opinion.


Update README.md Test

GitHub practice by Addi

Code is review

Looks good to me. Let's merge the code


Cocoapods1 1 1

Coverage increased (+0.05%) to 83.086% when pulling 91a1751b0b92a3acb68df878ddd86bd263edd545 on cocoapods1-1-1 into e4f82b07dd71d528ad19c55cc9af68d222ce2472 on master.

Coverage increased (+0.05%) to 83.086% when pulling<PHONE_NUMBER>52eda67b7a653621a63d30dddaf89a on cocoapods1-1-1 into e4f82b07dd71d528ad19c55cc9af68d222ce2472 on master.


Error message upon unsupported values for max_execution_time

Summary
Added error message when max_execution_time is outside the allowed range. Previously, this gave an error on the server side.
Details and comments
Related to  #851.
Should actually have been part of #781.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 67.217%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
3420

Relevant Lines:
5088

💛  - Coveralls


FR: Tailwind CSS

Is a tailwind exporter planned?

Not currently; I’m not a Tailwind user myself. But I’d love to support a Tailwind export plugin be created in any capacity (whether that’s helping the author, or improving docs, etc.). Cobalt is designed to be pluggable, so anyone can make a custom plugin for their needs without too much hassle.

For future readers, here's the tailwind plugin we wrote. It's highly specific to our tokens and what we have defined (and what we don't yet), so it will require some tweaking.
In general, I'm not sure how generic a tailwind plugin could be. It would either need a specific token structure or a lot of options to be passed in.
import setWith from 'lodash.setwith';
import util from 'node:util';

/**
 * @param {import('@cobalt-ui/core').ParsedToken[]} tokens
 * @param {Record<string, any>} initial
 * @returns {Record<string, any>}
 */
function expandThemeGroup(tokens, initial) {
	return tokens.reduce((acc, token) => {
		let path = token.id;
		let value = token._original.$value;

		// Default value, capitalize for tailwind
		if (path.endsWith('default')) {
			path = path.replace('default', 'DEFAULT');
		}

		setWith(
			acc,
			path.split('.').map((v) => v.replace('_', '.')),
			value,
			Object,
		);

		return acc;
	}, initial);
}

/**
 * @param {Record<string, any>} tokens
 * @param {number} depth
 * @returns {string}
 */
function printThemeGroup(tokens, depth) {
	let keys = Object.keys(tokens);
	let padding = new Array(depth).fill('\t').join('');
	let lines = keys.map((key) => {
		let val = tokens[key];
		let unsafeKey = /[ .,-]/g.test(key);
		let paddedKey = `${padding}${unsafeKey === true ? "'" : ''}${key}${unsafeKey === true ? "'" : ''}`;

		if (Array.isArray(val)) {
			return `${paddedKey}: ${util.inspect(val, { compact: true, showHidden: false })},`;
		} else if (typeof val === 'object') {
			return `${paddedKey}: {
${printThemeGroup(val, depth + 1)}
${padding}},`;
		} else if (typeof val === 'string') {
			// Aliased value, transform it into a `theme()` call
			if (val.startsWith('{')) {
				return `${paddedKey}: theme('${val.slice(1, -1)}'),`;
			}

			return `${paddedKey}: '${val}',`;
		} else {
			return `${paddedKey}: ${val},`;
		}
	});

	return lines.join('\n');
}

/** @returns {import('@cobalt-ui/core').Plugin} */
export default function pluginTailwind() {
	return {
		name: 'tailwind',
		async build({ tokens }) {
			let colors = tokens.filter((token) => token.id.startsWith('colors.'));
			let aliasedColors = tokens.filter((token) => token.$type === 'color' && !token.id.startsWith('colors.'));
			let spacing = tokens.filter((token) => token.id.startsWith('spacing.'));
			let fontWeights = tokens.filter((token) => token.$type === 'fontWeight');
			let borderRadii = tokens.filter((token) => token.id.startsWith('radius.'));
			let fontSizes = tokens.filter((token) => token.id.startsWith('fontSize.'));
			let nestedColors = expandThemeGroup(colors, { colors: { transparent: 'transparent', current: 'currentColor' } });
			let nestedAliasColors = expandThemeGroup(aliasedColors, {});
			let nestedSpacing = expandThemeGroup(spacing, { spacing: { px: '1px' } });
			let nestedFontWeights = expandThemeGroup(fontWeights, {});
			let nestedBorderRadii = expandThemeGroup(borderRadii, { radius: { none: '0', full: '100%' } });
			let nestedFontSizes = expandThemeGroup(fontSizes, {});

			return [
				{
					filename: 'tailwind.config.js',
					contents: `/**
 * Design Tokens
 * Autogenerated from tokens.json.
 * DO NOT EDIT!
 */

module.exports = {
	theme: {
		colors: (theme) => ({
${printThemeGroup(nestedColors.colors, 3)}
${printThemeGroup(nestedAliasColors, 3)}
		}),
		spacing: {
${printThemeGroup(nestedSpacing.spacing, 3)}
		},
		fontWeight: (theme) => ({
${printThemeGroup(nestedFontWeights.fontWeight, 3)}
		}),
		borderRadius: {
${printThemeGroup(nestedBorderRadii.radius, 3)}
		},
		fontSize: (theme) => ({
${printThemeGroup(nestedFontSizes.fontSize, 3)}
		}),
	},
}`,
				},
			];
		},
	};
}

@mike-engel ah that’s interesting—so you’re generating the configuration that Tailwind is then picking up.
I had been mulling around a similar idea in #129, but I do like the idea of just generating a Tailwind config automatically. Then you’re using Tailwind and not “we have Tailwind at home.”
I like this approach more than trying to create some competitor to Tailwind that frankly I have no interest in trying to get people to use.

Absolutely! We're so far on the tailwind train (for better or worse) that the approach we took was way simpler 😂

Just published @cobalt-ui/plugin-tailwind to hopefully provide a sane-ish DX (docs). It taps into Tailwind’s presets so people can still keep their current setup, basically just provide tokens as a base.
I’m not the biggest fan of having to manually run a command for Tailwind (I wish it would just “pick up on changes”), but I guess it‘s consistent with how the other Cobalt plugins work currently.
Anyway, it’s version 0.0.1 so would love feedback if anyone has any 🙏


[NOT AN ISSUE] Simple questions

Hi,
Thank you for your add-on/extension.
Please if possible, allow me few simple questions:

When one group "A" switches to another group "B", tabs in group "A" are closed? Or tabs are hidden? Please I want to know which process your add-on uses: It closes tabs, or it hides tabs?

If your answer to my previous question is "tabs are hidden", then my second question is: These hidden tabs are discarded (hibernated) when group "A" is closed? Or these hidden tabs remain active?

When user is at group "B", and a tab is reopened, the tab is refreshed and tab content is updated? Or the tab is just reloaded with the old content?

It seems you updated your add-on recently, after a long pause of time. Do you plan to be more active with this your add-on? I hope so! I ask you only because I'm interested on your add-on.

Thank you in advance!

@EstherMoellman, sorry for late response,

Tabs are closed, no way for now to safely switch between browsing sessions
Closed, and each tab's URL is stored
Fully re-loaded
Hope to be more active, have a lot of things to do yet

You welcome :)

Hi @lambidu , thank you for your answer. Please, if possible, allow me some requests:

User tab order per group, always should be remembered.
Last active tab always remembered per group.
Option to ignore (or not ignore) pinned tabs per group.
Option to unload tabs until selected/active, saving RAM, CPU etc.
"Select-tab-after-closing" function, allowing to choose which tab will be open (last, right, left, pinned).
Menu at icon pop-up bar and tab context menu, allowing multiple functions with just mouse-right-click.
Option for “Temporary Container”: If this option is selected, every new tab will be open in a separate container, reducing tracking. And when the tab is closed, everything inside the temporary container will be deleted, just the url will be saved as a bookmark (allowing to reuse the tab again).
Password protection group option.
Dark theme.

Thanks in advance again!


Browser files open twice

Hello,
I have implemented this code in my project, but when I click browse it open the dialog box and after selecting the image or after pressing cancel the dialog box open again. It open twice in short.
This is how I am implementing the code in my html.
Can you please tell what wrong I am doing.
Drop pdfs or images here or click to upload

What version of the plugin are you using? Try using the latest version.

The latest one which is in Github repository.

Then you gotta change the directive name, the prefixes are now ngf-*.
Create a jsfiddle to reproduce the problem if you can.

Ok I'll try n update u
-Best Regards
Mateen Kadwaikar
On 30-Apr-2015 11:17 pm, "Danial Farid"<EMAIL_ADDRESS>wrote:

Then you gotta change the directive name, the prefixes are now ngf-*.
Create a jsfiddle to reproduce the problem if you can.
—
Reply to this email directly or view it on GitHub
https://github.com/danialfarid/ng-file-upload/issues/709#issuecomment-97895909
.

Its working fine now. Thank you,.

i have same problem with new version.


Incompatible detection for Intel Compiler on windows

Hedley correctly detects Intel compiler and version, but then uses it to enable usage of GCC dialects like attribute(foo) which is not supported on windows, where the compiler is going for MSVC compatibility instead of GCC. Likewise it is not making use of the parts of the MSVC dialect which are supported by Intel on that platform.

Interesting, thanks for the report. I thought ICC just supported both versions everywhere; IIRC you can use several MSVC-style things on Linux.  I'll try to get a copy of ICC installed on a Windows VM over the weekend, and hopefully make a new release early next week.

I installed Intel oneAPI on a Windows VM, and I'm unable to reproduce this.  Just like on Linux, it supports both attribute and declspec syntaxes.
Can you please provide a reproducible test case, including the exact command you're using to invoke the compiler?  If it helps, there are lots of tests in the test/ subdirectory.

Hello, I can try to make a reproducible test case for you. But what I have exactly now is that I discovered this problem when using the nlohmann/json project, which bundles the latest version (13) of hedley.
This is the error I had:
C:\PROGRA~2\INTELS~1\SW_DEV~1\COMPIL~1.218\windows\bin\intel64\icl.exe  /nologo /TP /DWIN32 /D_WINDOWS /D_CRT_SECURE_NO_WARNINGS /W3 /Zi /bigobj /Oi /MP /GF /Gy /permissive- /EHsc /WX- /wd1292 /Ox /Ob2 /DNDEBUG /Ot /GS- /fp:fast -MT   -Qstd=c++20 /showIncludes /Fomain.cc.obj -c main.cc
nlohmann\detail\exceptions.hpp(60): error : expected a type specifier
        JSON_HEDLEY_NON_NULL(3)
        ^

nlohmann\detail\exceptions.hpp(60): error #303: explicit type is missing ("int" assumed)
        JSON_HEDLEY_NON_NULL(3)
        ^

nlohmann\detail\exceptions.hpp(61): error : expected a ";"
        exception(int id_, const char* what_arg) : id(id_), m(what_arg) {}

And that investigating this, hedley was providing this definition based on the fact it detected an Intel C++ compiler:
#define JSON_HEDLEY_NON_NULL(...) __attribute__((__nonnull__(__VA_ARGS__)))

Which the compiler was not accepting.
Testing the following snippet:
static void* test(void* in) __attribute__((__nonnull__));

in another part of my project, which does not use hedley, I got the following error:
r3k.cc(947): error : expected a "{"
    static void* test(void* in) __attribute__((__nonnull__));

Patching hedley to short circuit the intel compiler detection was my temporary way around the problem.
Have you tested the compiler yourself through the icl frontend (which mimics MSVC's cl) ?

I realized you might be testing a different C++ compiler than I am.
I am testing Intel C++ compiler 19.1 for windows (which is included in System Studio):
https://software.intel.com/content/www/us/en/develop/tools/system-studio/choose-download.html
You can get this with a free renewable one year license .
This intel oneAPI DPC++ is something I didn't know and  I just heard about from yourself.

As soon as I saw the command you're using I saw the problem; I was using icx not icc.  AFAICT icx is basically their next-generation clang-based compiler, which looks like it will support both attribute and declspec just like icc does.
You can get icc through oneAPI (it's in the HPC add-ons); DPC++ is something else.
I'm going to need to think about the API a bit.  I'm leaning towards HEDLEY_INTEL_* basically being icc-only, and adding a separate HEDLEY_ICL_* group for icl.  Interestingly, neither icc -qnext-gen nor icx define __INTEL_COMPILER, so icc -qnext-gen will use the clang paths.  The biggest question is whether HEDLEY_ICL_* should apply to icx…

I have added full support for icl, sorry about the delay. It's in the dev branch now, and I'm planning on putting out a release in the next day or two.

@nemequ Do you have a rough idea when the next release will be published?

@nlohmann, I can do it today if you want.  I was kind of hoping to get a better idea of how an issue with warning numbers on PGI will be resolved, but the code I have in place right now will just disable both warning numbers which should be stable going forward, and I can always tweak it in the next release to only disable one if PGI fixes it.

I did not mean to rush you. It's just that I have nlohmann/json#2346 which depends on this fix, and I would rather not make a release with the develop version of Hedley.

No worries, I understand.  If you want to make a release I can go ahead and put one out first; I've done pretty much all of the necessary testing already, so it's really not a big deal.
Waiting on PGI is probably a bit silly; it's not exactly a popular compiler, and the only disadvantage to putting out a release now is that future versions of the compiler will disable one more diagnostic then they have to (i.e., using HEDLEY_DIAGNOSTIC_DISABLE_UNKNOWN_CPP_ATTRIBUTES will disable diagnostics 1097 and 1098, when in reality we only want to disable one of them, I'm just not sure which one we want to disable until I find out if PGI is going to go back to the old diagnostic numbers or proceed with the new ones.
I'll go ahead and finish up my testing with the current dev branch this afternoon. Then if you can just give me a little warning before you want to make a new release I'll make sure to put out a new version of Hedley (which is trivial once the testing is done).

@nlohmann, I just release v14, it's exactly the same as what has been in dev for a while.


Person card

Describe Changes
Related Issue (Optional)

Hey, @Rishika-S-V you can't be copying over files for each PR.
Also, I don't see when this component would be used on a website, care to give some examples?


send media

How can i send any media? so as image or docuement?

Please read the API documentation


Memory leak: scene->clear(true)

scene->clear(true) seems not release all required memory.
Test scenario posted below result in 24,099 definitely lost bytes (456,099 bytes for j<20).
void tvgDrawCmds(tvg::Canvas* canvas)
{
    if (!canvas) return;

    auto scene = tvg::Scene::gen();

    for (int j=0; j<2; j++) {
        scene->clear(true);
        for (int i=0; i<1000; i++) {
            auto shape = tvg::Shape::gen();
            shape->appendRect(10, 10, 100, 100, 20, 20);
            shape->fill(255,0,0, 255);
            scene->push(move(shape));
        }
    }

    canvas->push(move(scene));
}

Hello Michal. I think this example is not correct. 1000 objects will always remain unreleased and same results show asan report. After canvas->push there is no command to clear scene or canvas.  Correct way is always:

Create scene
Create shapes and push it to scene
Push scene to canvas
Draw and sync canvas
Cleanup

So above sequence is a one frame rendering process. You cleanup code at point 5. could looks like this:
canvas->clear(true);

or
scene->clear(true);

If you notice memory leak after cleanup then we can check memory leak issue.

Last 1000 were correctly removed deleting the scene on finish, but the problem was scene->clear(true) function itself that didn't remove paints on particular case. I already created patch https://github.com/Samsung/thorvg/pull/446 It fixes memory leak on this snippet

@mmaciola Ok I got your point. It will not be removed correctly because internal issue


Stopped working in Chrome due to crypto.randomUUID error

Current version: 4.0.0
Chrome version: 124.0.6367.118
It suddenly stopped working today, at least on Google Chrome. I also get this error on console: "Uncaught TypeError: crypto.randomUUID is not a function". Already tried using the default settings so it's not a configuration issue.

Fixed. Waiting for the Chrome team to publish the extension.


Allow disabling HTTP TRACE/TRACK verbs

Motivation
Pulsar broker's embedded Jetty client does not disable HTTP TRACE and TRACK by default which causes the application to be flagged as insecure in certain corporate environments
Modifications
Created a new servlet filter: DisableDebugHttpMethodFilter that is attached to the servlets as they are added at startup. I used this StackOverflow answer for reference.
Verifying this change
This change added tests and can be verified as follows:
(example:)

Added test case testDisableHttpTraceAndTrackMethods in WebServiceTest class

Does this pull request potentially affect one of the following parts:

The rest endpoints: (yes) -- the property is set to false by default in broker.conf so it should not introduce any ill side effects in existing environments

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (comment in broker.conf)

@wmccarley  can you please rebase the PR.

@wmccarley Could you please resolve the conflicts?

move to 2.8.0 first


rerender

Issue:
@conda-forge-admin please rerender

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/cmrt-feedstock#4.


Build(deps-dev): Bump eslint-import-resolver-typescript from 2.5.0 to 2.7.0 (#3177)

Pull request opened by the merge tool on behalf of #3177

Merged in 93e5d061a9b9125ed23f5fe9a6813833d18db621


add redux to workspaces List

This is a canonical use of Redux in the workspaces List component. Highlights described here, and in code comments.
Code separation
The List component has been simplified, and no longer contains state, state transition logic, or asynchronous ajax logic. Its only concerns are display, and responding to interaction. This has several benefits, including ease of refactoring and ease of testing.
Logging and instrumentation
Because all state transitions are done via actions (which are just data), it is trivial to provide a real-time log of everything that happens.

Relatedly, it is possible to simulate events by constructing and dispatching them directly.

The store state is also available for direct inspection.

Testing
Since the component no longer directly manages state or makes ajax calls, it is much more amenable to testing using e.g. a mocked store Provider. Also, the reducer is a pure function and therefore can be tested directly.
Immutable.js
The store state is using Immutable.js, which provides clojure-inspired immutable data structures, including structural sharing, etc.
Tradeoffs
Redux code will usually be slightly larger than the non-Redux equivalent. Reducers and connect calls constitute the bulk of it. The code tends to be simple and flat, and doesn't add to overall complexity.

We decided not to implement redux at this time


Show matrix file count in data columns

Item 4 in https://github.com/HumanCellAtlas/data-browser/issues/303#issuecomment-433857799

Show Matrix file count in "Processed" files tool tip.


Don't allow continuous polygons to collapse into dust

With the --no-simplification-of-shared-nodes option, shard gaps could still be introduced between polygons through interaction with the collapse of tiny polygons into polygon dust. This PR prevents polygons that have been determined to share a border with another polygon from collapsing into dust.
Affected test
tests/ne_110m_admin_0_countries/out/-D8_-d8_-z1_-yname_--no-simplification-of-shared-nodes.json:
Before:

After:

For manual testing, my plan is to test within Felt on the matched Felt PR, rather than testing directly with tippecanoe.


Downloading wrong (my) playlists after logging in.

I was downloading all the playlists from  https://www.youtube.com/user/SingingMadeSimple/playlists and everything was working well until it hit upon a age restricted video and stopped. To work around it I decided to provide my login credentials. This is the code I typed with my username :: (password I typed later)
youtube-dl -o "%(uploader)s/%(playlist)s/%(playlist_index)s - %(title)s.%(ext)s" -f 18 -u
shrinidhi111 https://www.youtube.com/user/SingingMadeSimple/playlists

But to my astonishment it's downloading all my playlists instead of what's given. I don't know what's going on.

For the time being I removed my username and added  -i tag to ignore the age restricted videos to continue downloading rest of the playlists. Here's part of output ::
[download] 100% of 24.18MiB
[download] Finished downloading playlist: Voice Lessons (Series 4)
[download] Downloading video 6 of 10
[youtube:playlist] PLDAJtJ3ZoFS9ychzOXgQb1k6W4dBuhO48: Downloading webpage
[download] Downloading playlist: Voice Lessons with Celebrities
[youtube:playlist] playlist Voice Lessons with Celebrities: Downloading 5 videos
[download] Downloading video 1 of 5
[youtube] X_m-rEiLqeQ: Downloading webpage
[youtube] X_m-rEiLqeQ: Downloading embed webpage
[youtube] X_m-rEiLqeQ: Refetching age-gated info webpage
ERROR: X_m-rEiLqeQ: YouTube said: Please sign in to view this video.
[download] Downloading video 2 of 5
[youtube] bPugcGqimG4: Downloading webpage
[youtube] bPugcGqimG4: Downloading embed webpage
[youtube] bPugcGqimG4: Refetching age-gated info webpage
ERROR: bPugcGqimG4: YouTube said: Please sign in to view this video.
[download] Downloading video 3 of 5
[youtube] Gn0PAEXswG8: Downloading webpage
[youtube] Gn0PAEXswG8: Downloading embed webpage
[youtube] Gn0PAEXswG8: Refetching age-gated info webpage
ERROR: Gn0PAEXswG8: YouTube said: Please sign in to view this video.
[download] Downloading video 4 of 5
[youtube] E_hME11cslM: Downloading webpage
[youtube] E_hME11cslM: Downloading embed webpage
[youtube] E_hME11cslM: Refetching age-gated info webpage
ERROR: E_hME11cslM: YouTube said: Please sign in to view this video.
[download] Downloading video 5 of 5
[youtube] XwHNv9Js1-o: Downloading webpage
[youtube] XwHNv9Js1-o: Downloading embed webpage
[youtube] XwHNv9Js1-o: Refetching age-gated info webpage
ERROR: XwHNv9Js1-o: YouTube said: Please sign in to view this video.
[download] Finished downloading playlist: Voice Lessons with Celebrities
[download] Downloading video 7 of 10
[youtube:playlist] PLDAJtJ3ZoFS-EdfM6n7wa8HOwLjIyocP4: Downloading webpage
[download] Downloading playlist: Voice Lessons (Series 5)
[youtube:playlist] playlist Voice Lessons (Series 5): Downloading 9 videos


Agent: add testing mode

Previously, we didn't run agent tests in CI because they relied on a live Sourcegraph server running in the background to respond to HTTP requests. This PR adds support for a new testing mode that records HTTP requests into a directory and replays from that directory. This new testing mode makes it possible to enable the agent tests in CI because they run entirely from the HTTP recording avoiding the need for a sourcegraph access token or a live sourcegraph server. The HTTP recorder has been customized to automatically redact the Sourcegraph access token so that we don't commit the token into the git repository.
This PR also enables BFG tests, which send an HTTP requests to fetch the BFG binary but are otherwise offline.
Test plan
Green CI with agent tests enabled!

I have a local branch that fixes a lot of things, will push later today

I will fix the Windows failures on Monday. Would be good to get the Windows build green with this enabled instead of disabling it on Windows


Bug in the hash implementation?

This doesn't look right - I mean the 0: https://github.com/whitfin/siphash-c/blob/master/src/siphash.c#L62

I second that it looks wrong. If it turns out right, I could use an in-code comment.

I don't have time to jump into this right now, but afaict it's correct. If you can give me a case where the output is incorrect, I can work on it.

I have used this function to hash text strings, and I had A LOT of colliding strings of length 3. Just 3! I then used this implementation and it works fine: https://github.com/veorq/SipHash
Try these two strings: 3Ct and 3CD


[Fix] install from src should do "nvm use" before npm detection

The origin logic didn't noticed that the new installed nodejs will not be in the PATH, so if you don't have any installed npm, no matter if you installed nodejs succeed or failed this time, you'll never detect it, so should try to activate the version and then do the npm detection.

Wouldn't this mean that anyone installing node from source for the first time, when they don't have a system node, would attempt to install npm?
That seems like the sort of thing I'd have gotten bug reports on years ago.

Actually the npm was installed together, just because the PATH was not updated then caused it can't be detected, so nvm try to install it from script again.

Sorry that I just put it in the wrong place when I commit it, fixed as what I tested.

@ljharb I think the problem is fixed now, would you please help confirm this? Many thanks!

Now after nvm deactivate && nvm uninstall 0.10.10 && nvm install -s 0.10.10 i get at the end:
Now using node v0.10.10 (npm v1.2.25)
Now using node v0.10.10 (npm v1.2.25)

@ljharb would you mind me just hide(using redirect) the previous one?

It seems silly to double-use - we shouldn't need to run nvm use twice.

hmmm ... but the process will need to be refactored, right? Any suggestion on the refactoring? Don't want do refactor something will be dropped directly haha. Thanks!

I think maybe it would be better to move the "install npm" code into a separate method - and do it directly inside nvm install instead of inside nvm_install_source?

hmmm ... let me try :) Will update here :D

but don't we need to test it after PATH updated? I think we can just use a subshell to test it?

Yes, that's what I'm saying - nvm install itself runs nvm use- I'm suggesting to ensure npm is installed after the top-level nvm use.

@ljharb can we have workaround here first? To help we migrate the CI test on to Ubuntu 14.04, and at least make it works properly first, thanks.

k, I ended up implementing https://github.com/creationix/nvm/pull/1334#issuecomment-264727900, which should fix this.

Closed by b9f9977cdd9d14a501a619fe5e0e578328ec0f64

oh okay ...


Add details on how to specify memory and other settings

Check in with Michael about how to set memory higher? And resolve some other questions

Had a nice chat with Michael about this today:
Indeed, the sbatch --mem option does not guarantee memory allocation, and SciComp recommends requesting cores as a proxy for memory allocation:

If you think your job will need more than 4GB of memory, request one CPU for every 4GB required.

Why does requesting more CPU help with allocating more memory?
FH Gizmo has class J nodes which each have 24 cores and 384GB of memory, and class K nodes which each have 36 cores and 768GB of memory. So, if you think you will need 100GB of memory for your job, by this rule of thumb you would request 25 cores. You would be assigned to a class K node, and you would occupy 25/36 cores on that node. On this node, other users can use the remaining 11 cores. You would share the 768GB of memory all together and hope that the other users don't take up more memory than you need: the more cores you occupy on a node, less users will compete for memory. It's an imprecise system and SciComp has interest to make memory allocation more precise in the future.
Note: on other SLURM systems, sbatch --mem does have implications about memory allocation.

awesome recon, thank you!


Algolia logo added twice.

Hi @teamkogg can you please remove the old Algolia logos from your website.
I just uploaded the new Algolia logo on your website, use this one please.


feat(cli): lock project to prevent simultaneous builds

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

This pr adds a lock method for nuxt cli commands. The lock is used to prevent simultaneous builds for a project, so only one build can run at once.
The locking also helps automation, if you develop a long running nuxt command which is triggered by a cronjob you can rely on locking to prevent running that command more then once.
To make sure that the locking doesnt cause problems on exotic filesystems (CI's?), I have added a common --no-lock cli option to disable the locking.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Did not write tests yet, will do after initial approval

@pi0 You probably wont like this implementation either, but I wanted to show it before we move the lock to core or common. If we move it, I think we should add build.lock and generate.lock properties so you can differentiate between those.

I will close this so you dont have to, feel free to take any idea/implementation of this pr you like :+1:


fix: ami family conversion

Fixes the following issues with AMI conversion:

Fail closed when the AMI family we're convering from is Ubuntu
Don't create an alias when the AMI family is non-custom but selector terms are specified

Fixes #N/A
Description
This PR fixes two issues with the conversion webhooks for AMI family and selector terms:

Fail closed when the AMI family is Ubuntu
Don't create an alias when the AMI family is non-custom but AMISelectorTerms are defined

How was this change tested?
make test
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 79.113%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
5939

Relevant Lines:
7507

💛  - Coveralls


Support custom chunks for webpack / separate chunks for in-house libraries

🚀 Feature request
Command (mark with an x)

[ ] new
[x] build
[x] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
 A clear and concise description of the problem or missing capability...
We do most of our component development in an Angular library. That library is linked via package.json (local file reference as it is in a mono-repo style git repository). This library is quite large and it takes time for webpack to re-pack it. The contents get put into vendor.js as we have vendorChunk set to true. It would be nice to be able to have our library be able to be put in its own chunk file so that the vendor chunk rarely ever changes during a release (it is uncommon for us to change other packages during a release).
While this may be possibly using tools like @angular-builders/custom-webpack:browser it would be nice to have greater customization of the chunks that are created via the core builder and angular.json.
Describe the solution you'd like
 If you have a solution in mind, please describe it.
New additionalChunks section of angular.json configuration for the @angular-devkit/build-angular:browser builder.
It would allow glob matching to customize the chunks.
"additionalChunks": {
    "myLib": [ "node_modules/myLib/**" ]
}

This would package the "myLib" Angular library as "myLib.[hash].js" in the output of ng build (and a separate file for serve)
Describe alternatives you've considered
 Have you considered any alternative solutions or workarounds?
@angular-builders/custom-webpack:browser

Hi @arobinson,
Thanks for this feature request. That said in this case using 3rd party extension that enhances the Angular CLI seems to be the reasonable thing to do.
It's also important to highlight that vendorChunk is meant to be used only during development, as using this for production build will cause optimization bailouts especially when using lazy-loading.
Thanks.

Hi @arobinson,
Thanks for this feature request. That said in this case using 3rd party extension that enhances the Angular CLI seems to be the reasonable thing to do.
It's also important to highlight that vendorChunk is meant to be used only during development, as using this for production build will cause optimization bailouts especially when using lazy-loading.
Thanks.


⚠ Bofrost.be has degraded performance

In 4df3f91, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1855 ms

Resolved: Bofrost.be performance has improved in 474e3cb.


Isolate demo project from template project.

We need new demo projects, and keep the default project alongside with template project currently.


Convert hard-coded version to regex to appease MegaLinter

to avoid using the exact version string b/c it changes from time to time
Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1417 (30830c0) into dev (d9373cd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1417   +/-   ##
=======================================
  Coverage   26.97%   26.97%
=======================================
  Files          31       31
  Lines        1001     1001
  Branches      128      128
=======================================
  Hits          270      270
  Misses        721      721
  Partials       10       10

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


net: http: switch to zsock_ for http_client

Using zsock_ in http_client instead of the POSIX API versions of the
functions allows the usage of http_client in combination with
CONFIG_POSIX_API.
Signed-off-by: Benedikt Schmidt<EMAIL_ADDRESS>

@mniestroj FYI, with regards to shutdown()

I'm uncertain if this is a desired patch, but it would resolve #38414. As the POSIX-thingie seems to be some sort of an issue (e.g. reading a bunch of comments by @pfalcon) I considered it might be easier to just avoid it internally, as it is not really necessary in this case.

The changes in the library look fine, as they make the library independentof the configuration, we do this in other libraries as well (not all though yet).
I'm not conviced about the sample though, it explicitly enables CONFIG_NET_SOCKETS_POSIX_NAMES=y to use POSIX apis, I don't think we should change that.

Okay, I will revert the changes in the sample.


Stopped connecting

I've been using RDP Wrapper for years now. Every time after Windows 10 update new ini file worked for me. This time it's different. Although it says that everything is OK, I can't connect. Last week I had this problem, I changed port number and it was working few days without restarting. But during weekend I had to restart and again it's not connecting and changing port this time doesn't help. What can I do?

i tried this one and its working for me https://github.com/stascorp/rdpwrap/issues/781
can you try and let us know

Yes, it's working now, thank you. Earlier I was trying this INI https://github.com/stascorp/rdpwrap/issues/744 and it wasn't working.


Protocol documentation

Hi, thanks for providing this code. I was wondering if you reverse engineered the protocol using a BLE sniffer or alike (like nRF tools) and implemented it in Python, or if there is a protocol specification somewhere. Thanks.

Hi, https://github.com/cdump/radiacode/issues/4#issuecomment-1003606860

Ok, this is great. Please in the case I would like to write a documentation for the protocol, could I send you questions in this issue to get your help? Thanks.

I can’t guarantee 24/7 support for all questions, but I’ll try to answer here occasionally

Also, the free Microsoft developer VMs running under qemu on a Linux host work for capturing USB traffic with Wireshark. You can run the app with debug turned on, and see what goes on the wire.

Thank you

@cdump if you have any notes to share, even if messy, feel free to share please, I'd be happy to start jotting down an initial document.

@RamonBeast I don't have any notes, sorry. All the knowledge I have is already in the code (variable names, a few comments)

Noted then, thank you!


Linkedin is not validating

When I call the linkedInTrack method on events I get window error: lintrk is not defined

Old issue, you probably figured it out but just in case...
Did you use <LinkedInInsightTag /> somewhere in your code? (in your App or a layout)? If so, when loading your page, can you see loads from domain snap.licdn.com when looking at the network activity?

I close this issue. Please reopen it if you have any news about it.


CB-18420 Set property nifi.nar.hotfix.provider.enabled=true via clust…

…er template. Set this property with true value, enables resource fetcher functionality. We need that for 7.2.16.
See detailed description in the commit message.

@doktoric could you please clarify, is it enough to commit this change into master branch to make it available in 7.2.16? Thanks.

@vbrodetskyi CB releases are not tied to runtime versions. master branch is 2.63 at the moment. Given that 2.62 was just got branched last week prior to the unplug and its QE verification has not yet started, it will likely take 2-3 weeks to have 2.62 promoted to Prod, and another similar 2-3 weeks for 2.63. So the present change will likely land in Prod around the end of September / early October. I do not know how this compares to the 7.2.16 release schedule, though.

@lajosrodek got it, thank you. For me, it's important to have this change available for 7.2.16, because we will have related CFM change for Flow Datahub cluster on 7.2.16. Do you know who can clarify on that?

@TheTinkerDad Do you possibly know if 7.2.16 is targeting CB 2.63? (It is definitely not available for 2.61, but I have not checked 2.62 TBH.)


Update download URL to pyvistaqt main branch

Follows https://github.com/mne-tools/mne-python/pull/9497/files and https://github.com/pyvista/pyvistaqt/pull/120, the PR updates the branch name of pyvistaqt.

Please merge once CIs come back happy!

I manually downloaded the file so I'll try to save the CIs some cycles here


Update updates page for dcp27

New projects (16):

Benchmarking Single-Cell RNA Sequencing Protocols for Cell Atlas Projects
Cell Atlas of The Human Fovea and Peripheral Retina.
Construction of A Human Cell Landscape by Single-cell mRNA-seq
Cross-tissue immune cell analysis reveals tissue-specific features in humans
Differential pre-malignant programs and microenvironment chart distinct paths to malignancy in human colorectal polyps
Identification of a unique subset of tissue-resident memory CD4+ T cells in Crohn’s disease
Integration of eQTL and a Single-Cell Atlas in the Human Eye Identifies Causal Genes for Age-Related Macular Degeneration
Intrarenal Single-Cell Sequencing of Hepatitis B Virus Associated Membranous Nephropathy.
Pathogen-induced tissue-resident memory TH17 (TRM17) cells amplify autoimmune kidney disease
Single cell RNA sequencing to dissect the molecular heterogeneity in lupus nephritis
Single-cell analyses of Crohn's disease tissues reveal intestinal intraepithelial T cells heterogeneity and altered subset distributions
Single-cell analyses of renal cell cancers reveal insights into tumor microenvironment, cell of origin, and therapy response
Single-cell multiome of the human retina and deep learning nominate causal variants in complex eye diseases
Single-cell profiling of healthy human kidney reveals features of sex-based transcriptional programs and tissue-specific immunity
Single-cell sequencing reveals novel cellular heterogeneity in uterine leiomyomas.
Single-cell transcriptomic atlas of the human retina identifies cell types associated with age-related macular degeneration

Updated Projects (4):

Single cell sequencing identifies novel sub-populations of breast cancer cells selected under hypoxia
Single-cell RNA sequencing identifies cell type-specific cis-eQTLs and co-expression QTLs
A single-cell transcriptomic atlas of the human ciliary body
Integrated analysis of multimodal single-cell data

PR is here: https://github.com/DataBiosphere/data-portal/pull/2135

Complete


Dist version doesn't work in a web server

Thanks for this project, is very helpful.
After i build your code with yarn build or npm run build  I see the creation of the dist/ directory with all the files minified.
If I serve that directory with a webserver using:
docker run -p 80:80 -v $(pwd):/usr/share/nginx/html nginx

or the  instant web server with:
instant 8800

The app won't work and in the console I see this error:
09:58:05.732 angular.js:15570 Error: [$injector:unpr] Unknown provider: iProvider <- i
https://errors.angularjs.org/1.7.9/$injector/unpr?p0=iProvider%20%3C-%20i
    at angular.js:138
    at angular.js:4926
    at Object.u [as get] (angular.js:5086)
    at angular.js:4931
    at u (angular.js:5086)
    at c (angular.js:5111)
    at Object.invoke (angular.js:5135)
    at M.instance (angular.js:11707)
    at ot (angular.js:10520)
    at angular.js:9835
(anonymous) @ angular.js:15570

To me looks like there's a problem with the minification.

Thanks for reporting, @atropo, I'll get into it 👌

@atropo, can you provide your docker config please so that I could reproduce the issue in a more specific environment and make sure other types of environments are OK after that?

@atropo I'd tested the fix at different environments, please confirm that it works for you, in opposite case feel free to ping me to reopen the issue

For the sake of documenting the issue for others, though it's a rather unusual case these days - combining AngularJS applications with Parcel bundler and specific Babel plugins 🤷♂
It was caused by failing minification resulting in Unknown provider: iProvider <- i console error. The reason for that is that babel-plugin-angularjs-annotate babel plugin doesn't work with Parcel bundler with implicit dependency injection annotations, you need to make them explicit by putting /* @ngInject */ where needed and setting "explicitOnly": true option for the plugin.
Alternatively, you can use Webpack to make annotations implicit, but for this oppinionated starter I prefer Parcel, because it's faster, cleaner and allow to avoid the Webpack's configuration hell.


Fixed "Create New..."

Removed angle brackets so "Create New" renders correctly instead of being turned into an HTML element.

Hi @cilynx, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


feat: add sp1 verifier

This PR adds ffi bindings for sp1 proof verification and the embedding in the operator.
The anvil gas_limit parameter was set to a high value so that transactions with sp1 proofs can be effectively made without being revoked.

Add a reference to Succint Labs and Polygon (valida and plonky3) thanking them. Do the same for each verifier. We need to add everyone.


Curl filter doesn't work

Hi. I tried to use RetrySubscriber::createCurlFilter. But seems it doesn't work.
Created filter - checks curl_result in transferInfo:
return isset($errorCodes[(int) $e->getTransferInfo('curl_result')]);

Response looks like:
(dump from ./vendor/guzzlehttp/guzzle/src/RequestFsm.php)
=> <GuzzleHttp\Transaction #000000000f5e91f8000000004289c9b4> {
       client: <GuzzleHttp\Client #000000000f5e911e000000004289c9b4> {},
       request: <GuzzleHttp\Message\Request #000000000f5e91f3000000004289c9b4> {},
       response: <GuzzleHttp\Message\Response #000000000f5e90cc000000004289c9b4> {},
       exception: <GuzzleHttp\Ring\Exception\RingException #000000000f5e904100000000428b51b4> {
           message: "cURL error 60: SSL certificate problem: self signed certificate in certificate chain",
           file: "/var/www/analytics/vendor/guzzlehttp/ringphp/src/Client/CurlFactory.php",
           line: 126
       },
       transferInfo: [
           "url"                     => "https://some_url.domain/",
           "content_type"            => null,
           "http_code"               => 0,
           "header_size"             => 39,
           "request_size"            => 150,
           "filetime"                => -1,
           "ssl_verify_result"       => 0,
           "redirect_count"          => 0,
           "total_time"              => 0.960707,
           "namelookup_time"         => 0.004378,
           "connect_time"            => 0.004543,
           "pretransfer_time"        => 0.0,
           "size_upload"             => 0.0,
           "size_download"           => 0.0,
           "speed_download"          => 0.0,
           "speed_upload"            => 0.0,
           "download_content_length" => -1.0,
           "upload_content_length"   => -1.0,
           "starttransfer_time"      => 0.0,
           "redirect_time"           => 0.0,
           "redirect_url"            => "",
           "primary_ip"              => "<IP_ADDRESS>",
           "certinfo"                => [],
           "primary_port"            => 8888,
           "local_ip"                => "<IP_ADDRESS>",
           "local_port"              => 58707
       ],
       retries: 0,
       state: "error",
       future: null,
       _transitionCount: 0,
       _future: null
   }

I didn't find any mentions of curl_result in transferInfo.
In tests also wasn't checked this case.
I suggest merge curl_getinfo with curl_error and curl_errno, in ./vendor/guzzlehttp/ringphp/src/Client/CurlHandler.php

I was also trying to use createCurlFilter but could not seem to get it work. After I while I also realized I could not find a mention of curl_result anywhere and starting to search the web was what in fact lead me to this open issue. So it seems this method does not work?

Yep. It doesn't work. I forked RingPHP and this subscriber to fix it. I still waiting response about suggested fix from maintainers or something.

PR was merged.


Delay before able to click Accept camera in flash

There is a delay around a second or two, between the time I see the Accept prompt, and the time that the  Accept button is clickable. Its very annoying, I am clicking it and nothing happens.  I can submit a video, if required.

That's not a bug in WebcamJS.  It's a Flash thing.  Also, it's not a delay, it's the mouse position.  Adobe is reading the mouse cursor at a slight Y offset.  Try clicking at the very "top" of the Accept button, and you'll see what I mean.
I have no idea how to fix this.  I think it's a bug in Flash.


improved mainview and added notification options

change to ObjectListView (nuget) for:
-- grouping
-- sorting
-- ability to hide columns
-- restore previous state
added "Show Status Window" to tray context menu
added options to enable/disable specific messages
added optional speech notification (used some code from http://www.gooteck.com/tutorials/dotnet/text-speech-using-c-net-speech/ but changed/simplified to suit the need)
added posiblity to disable build icon annimation (some find it attracting attention while they only want to see the notification/status)

Could you use the standard ListView or find an alternative to ObjectListView that is not GPL?

That's possible, however that would result in loss of a lot of options,
i'm pretty new to it but as far as I can see according to
http://www.gnu.org/licenses/license-list.html#X11License
the X11 License (also called MIT license) is compatible with GPL.
(its in the green section above which is called "Free licenses, compatible
with the GNU GPL")
So nothing has to change, right?
2016-05-23 5:07 GMT+02:00 Kevin Ortman<EMAIL_ADDRESS>
Could you use the standard ListView or find an alternative to
ObjectListView that is not GPL?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/KevinOrtman/bambootray/pull/9#issuecomment-220878639

Compatible doesn't always mean 2-ways.
I understand that there is a lot of confusion/debate around this.  But at the end of the day, I will not link GPL libs to a MIT licensed project nor accept a pull request that do so.
I appreciate your improvements and I'm happy to accept changes, but I won't budge on that.  If you feel the library is needed, it is okay for you to continue to maintain your fork.


Display the reason why the download failed

(Split from #1208, particularly this comment.)
If Podboat fails to write the file, e.g. because the filepath is too long, Podboat should display an error message explaining what went wrong.

Hey, I was thinking about this one. This one doesn't seem too difficult (I hope, lol).
Do you have a particular way you would want this implemented?

Hey, cool! The message should be put into "msg" field of the dllist — see src/pbview.cpp. That field is displayed at the bottom of Podboat's window.
Other than that, I can't think of any other requirements.


nixos/zabbix: overhaul package & module

Motivation for this change
Team effort between @mmahut and myself to cleanup Zabbix in NixOS as the module & packages have become fairly unmaintained.
Things not yet done

[ ] Write some release notes (@aanderse)
[ ] Add a NixOS test which tests all of the server, proxy, and agent (@mmahut)
[ ] test zabbixProxy module in a real environment (@aanderse)

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@PsyanticY Well I didn't notice https://github.com/NixOS/nixpkgs/pull/63581... Can you please review this and provide feedback?

Sorry for missing this! Had not realized there were multiple zabbix prs, but this one certainly looks to handle things well. Feel free to revert the other PR (or base on top of it).

@matthewbauer No problem, it happens. My fault as well. I had started this branch before the other was publish so when I checked it wasn't there... but then when I actually pushed and made a PR I didn't check again. Oops.
This PR has now been based on top of master after the other PR was merged. As mentioned I have been running this for roughly a month now. Mostly compatible with the merged PR, just a few tiny naming differences. Care to merge?

@aanderse, as @matthewbauer  said this one handle thing way better then the other pr so please revert the other or base on top of it.

@PsyanticY Thanks for your approval on this. I regret that our work clashed so I'll double check open PRs more than once next time I work on something like this! Already rebased and briefly tested so I'm going ahead and merging this. Thank you for your support and listing yourself as a maintainer. I hope to hear from you again on the topic of zabbix on NixOS :smile:

Thanks, no problem, it is all for the grater nix good :p  :)


fix: Modify v1 UpgradeHandler to correctly execute migration [DEV-1973]

Fixes ICA module store key initialisation.

Task linked: DEV-1973 Fix upgrade handler for v1.0.0 migrations


Updates theme to fork of original and changes color for 2024

Type of Contribution
Check the item(s) that applies.

[ ] :zap: HOWTO Content update
[x] 📃 Hugo static site update
[ ] :icecream: README or site documentation update

Is this pull request related to an existing issue? If so, which one is it?

[x] :white_check_mark: Yes! - Issue number: #45
[ ] :x: No, sorry.

Description

I've updated the site color to green to match the vibe of this year, and I've updated the hugo theme to refer to the organization's fork of the theme because the original theme has been archived.

Closes #45


error 0x80070002 on admin launch (Command Prompt)

When doing a shift + right click in a directory, going into 'Windows Terminal (Admin) here' -> Command Prompt or Windows Azure Shell, I get the following error:

[error 0x80070002 when launching `Prompt -d C:\Users\abarranco\Downloads.']

[error 0x80070002 when launching `Cloud Shell']

Powershell appears to function properly in admin though.
So does non-admin across all 3.

Thanks. Will fix it soon.

All except Azure Cloud Shell have been fixed, but the root cause for Azure Cloud Shell is miserable. So will leave this issue open for a while.