Change T2/T3 unlimited

Hi,
Is there a way to enable/disable the unlimited feature for T2/T3 instances via the cloud-config? If not, is it possible to get this feature implemented ?
Thank you.
Greetings,
Benjamin

+1
Our T2 instances are also experiencing performance issue without unlimited feature disabled. Currently, we have to manually enable the feature on aws console after deploying the servers with bosh.


[bug]: TypeError: n.color.replace is not a function

Config file of your workflow
name: Label Syncer

on:
  push:
    branches:
      - main
    paths:
      - .github/labels.yml
      - .github/workflows/label-syncer.yml
  workflow_dispatch:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  sync-labels:
    runs-on: ubuntu-latest
    permissions:
      pull-requests: write
      issues: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Label Sync
        uses: srealmoreno/label-sync-action@v1
        with:
          token: ${{ secrets.LABEL_SYNC_TOKEN }}
          auto-discover-repos: true
          exclude-repos: |
            .github
          account-type: org
          exclude-forked-repos: true
          exclude-archived-repos: true
          exclude-private-repos: true
          exclude-disabled-repos: true

Describe the bug
When the action runs, it prints an error and cancels the workflow:

Expected behavior
It should pass and sync labels.
Current behavior
It cancels the workflow with an error.
Logs of the workflow
https://github.com/AlmostReliable/.github/actions/runs/8112547736/
Aditional information
No response
Self-service

[ ] I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines.

Are you familiar with Contributor Covenant Code of Conduct?

[X] I have read the Contributor Covenant Code of Conduct.

Contact Details
No response

There is no newer version and the problem still occurs.

@rlnt Please check your labels specification file, the key color must be a string.
https://github.com/AlmostReliable/.github/blob/aeb2397298d1630a4354f610144fd94b5d4327fc/.github/labels.yml#L26


tf slim, default initializers for relu

The defaults in layers such as conv and conv_transpose have the default activations as relu and the default initializer as xavier. From the paper https://arxiv.org/pdf/1502.01852v1.pdf, would this be the time to change the default initializer to use tf.contrib.layers.variance_scaling_initializer to account for the variance of the distributions being halved at each layer of activation?
Andrej Karpathy has a lecture which shows the effects of this https://youtu.be/gYpoJMlgyXA?t=47m6s
edit:forgot to add time in the video

@nathansilberman @sguada is that something we'd want to do? (change the default)

@martinwicke could you comment?

Due to backwards compatibility guarantees, we will not be able to change anything under core.
Therefore, we are not going to be able to change this for most of TF.


llama3.2:latest not running and giving Error: llama runner process no longer running: -1

What is the issue?
I have been using Ollama for a while and have never encountered this error while running any other llms (including llama3.1).
Below is the snapshot of server log with error:

Key issue seems to be related to wrong number of tensors. Any help? I have a 3070Ti GPU with 8 GB VRAM.
OS
WSL2
GPU
Nvidia
CPU
Intel
Ollama version
0.1.32

Upgrade ollama, 0.1.32 is too old to run llama3.2.


Added tojson writer and from_dict and from_json readers.

Added to_dict and to_json readers to the graphframe. Added a from_json reader.
Added tests to verify that these readers and writers work in addition to a thicket generated json file to verify backwards compatibility.
Added json files for tests.

@cscully-allison Can you look into why the test failed?


Gradle Enterprise Trial

This PR is a live branch to bookkeep all Gradle enterprise fixes to facilitate the before-and-after evaluation for Gradle enterprise.
Gradle Enterprise Trial Navigator for Gradle.pdf

On moving the test out of the resources folder - what do you think about future functional test for multiplatform and Android projects? Those could have cases that require multiple modules, each with violations that we would test that detekt picks up, and I feel that generating all of these files by placing the file content in a test script instead of a self-contained project can get quite confusing. IMHO it's easier to reason about a test project if it's files on the system instead of source in strings in a test script.
I was inspired by SQLDelight when setting up the self-contained project. SQLDelight has many Gradle projects which are used for functional testing: https://github.com/cashapp/sqldelight/tree/master/sqldelight-gradle-plugin/src/test
There are pros and cons with each approach of course - the Gradle project itself tends to setup tests in code, as a counter-example to SQLDelight.

I agreed that it would be easier to explore and review if we hold these test fixtures in resources in an organized way.
The only cons from my exploration in the checkstyle repo are that, when we want to start to test variants, we either need to copy-paste test fixtures or define some template within the test fixtures, the readability, in the end, would be jeopardized.

One problem with the tests right now (which I'm actually working on over the next few days as time allows) is that many functional tests can be rewritten to use ProjectBuilder (#3778) which makes testing different use cases simpler, as less setup code is required for each one. I think that's where majority of repetition for different test cases will end up (e.g. checking that task creation and wiring dependencies are as expected for different Kotlin plugins), with the functional tests only testing a few specific cases.
That might tip the balance in favour of keeping test fixtures as self-contained projects.

Should we convert this to a Draft PR?

One problem with the tests right now (which I'm actually working on over the next few days as time allows) is that many functional tests can be rewritten to use ProjectBuilder (#3778) which makes testing different use cases simpler, as less setup code is required for each one. I think that's where majority of repetition for different test cases will end up (e.g. checking that task creation and wiring dependencies are as expected for different Kotlin plugins), with the functional tests only testing a few specific cases.
That might tip the balance in favour of keeping test fixtures as self-contained projects.

I see your point - Totally agreed upon simplifying functional tests and using unit test with ProjectBuiilder to cover the varieties.
I am going to base my change on https://github.com/detekt/detekt/pull/4761/files to simplify the resource copy in a more organized way (mostly directory structure and naming).

This PR should be ready for review as we went through all 5 experiments in the Gradle enterprise trial.
Once merged into main, we will verify the scenario of CI build-cache + anonymous local checkout.

I am merging this PR for the meeting with Gradle folks tomorrow. I will monitor the trunk status closely.

https://github.com/gradle/gradle-enterprise-oss-projects/blob/main/.github/workflows/run-experiments-detekt.yml is where the previous GE experiments are being tracked.


Question about Get-ip site

How does this feature work?
She gets the site's ip and tries to connect to it.
or
She gets the ip from the site, tries to connect and then gets the ip from the site again and tries to connect.
P.S.
How do you like the idea of adding a backup ip / site address?
How do you like the idea of adding a watchdog?

second one
---Original---
From: @.>
Date: Tue, Jul 20, 2021 23:21 PM
To: @.>;
Cc: @.***>;
Subject: [qwqdanchun/DcRat]  Question about Get-ip site (#40)
How does this feature work?
She gets the site's ip and tries to connect to it.
or
She gets the ip from the site, tries to connect and then gets the ip from the site again and tries to connect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

How do you like the idea of adding a backup ip / site address?
How do you like the idea of adding a watchdog?

this is easy to add
---Original---
From: @.>
Date: Wed, Jul 21, 2021 00:10 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [qwqdanchun/DcRat]  Question about Get-ip site (#40)
How do you like the idea of adding a backup ip / site address?
How do you like the idea of adding a watchdog?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

ok


filter JS from job openings

currently it's possible to put JS into the tinyMCE inline Editor
http://www.karriere24.com/jobs/de/jobs/view?id=5494bb61d464a3de42dedae8
JS has to be filtered.

Some notes to clearify the linked diagrams:
These steps has to be done:

Create a XSS Filter class (implemening \Zend\Filter\FilterInterface)
Register this filter in the Filter Plugin Manager.
This is done by configuring the mapping in the filter plugin manager config, which is found in the main application config under the key "filters" (which is a service manager configuration array)
e.g.
"filters" => array(
"invokables" => array(
"Core/Xss" => "\Core\Filter\XssFilter",
)
)
Attach this filter to the elements which should be using it.
in the case of jobs, the only element currently is "\Core\Form\Element\Editor"

Make the element an input provider for \Zend\InputFilter by implementing "\Zend\InputFilter\InputProviderInterface"
In the "getInputSpecification()" method, configure the use of the Xss filter

    return array(
         ...
        "filters" => array(
               "Core/XssFilter"
        )

(Maybe the syntax is slightly different, I'm not sure at the moment.)

https://github.com/cross-solution/YAWIK/commit/4d79d2e5be90096d2d45c13e64f4d880ff11dc4f


[NPM-3357] Handle netlink not permitted when checking connection existence

What does this PR do?
Fixes a persistent warning log on platforms that don't support netlink conntracker, when querying for a connection (to check if it still exists). We now check if conntrack is supported (i.e. has permissions) in this code, and skip the existence check for the connection if it is not.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


PKS on GCP - riff function create fails on build-step-build-and-push stage in pushing image to gcr.io

Hi, I am following the Getting Started on GKE guide, but I am using PKS 1.2 deployed on GCP. I am following the instructions but getting this error while trying to create function:
riff function create node square --git-repo https://github.com/projectriff-samples/node-square --artifact package.json --image gcr.io/$GCP_PROJECT/square --wait -v
Waiting for LatestCreatedRevisionName:. square-00001
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0000] Downloading base image projectriff/node-function-invoker:0.0.8
default/square-00001-c4s2w[build-step-build-and-push]: ERROR: logging before flag.Parse: E1014 15:55:13.287695       1 metadata.go:142] while reading 'google-dockercfg' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg
default/square-00001-c4s2w[build-step-build-and-push]: ERROR: logging before flag.Parse: E1014 15:55:13.290958       1 metadata.go:159] while reading 'google-dockercfg-url' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg-url
default/square-00001-c4s2w[build-step-build-and-push]: 2018/10/14 15:55:13 No matching credentials were found, falling back on anonymous
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0000] Executing 0 build triggers
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0000] Extracting layer 0
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0001] Extracting layer 1
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0002] Extracting layer 2
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0003] Extracting layer 3
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0003] Extracting layer 4
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0003] Extracting layer 5
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0005] Taking snapshot of full filesystem...
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] ENV FUNCTION_URI /functions/
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] COPY . ${FUNCTION_URI}
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] Taking snapshot of files...
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] RUN (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] cmd: /bin/sh
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0008] args: [-c (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)]
default/square-00001-c4s2w[build-step-build-and-push]: npm notice created a lockfile as package-lock.json. You should commit this file.
default/square-00001-c4s2w[build-step-build-and-push]: up to date in 0.102s
default/square-00001-c4s2w[build-step-build-and-push]: INFO[0009] Taking snapshot of full filesystem...
default/square-00001-c4s2w[build-step-build-and-push]: error pushing image: failed to push to destination gcr.io/fe-shgpupta/square:latest: no token in bearer response:
default/square-00001-c4s2w[build-step-build-and-push]: {"errors":[{"code":"DENIED","message":"Token exchange failed for project 'fe-shgpupta'. Please enable Google Container Registry API in Cloud Console at https://console.cloud.google.com/apis/api/containerregistry.googleapis.com/overview?project=fe-shgpupta before performing this operation."}]}

Error: function creation failed: RevisionMissing: Configuration "square" does not have any ready Revision.; Revision "square-00001" failed with message: "build step \"build-step-build-and-push\" exited with code 1 (image: \"docker-pullable://gcr.io/kaniko-project/executor@sha256:f6e586c4687e2669c610a0ad46d0cca780a140d2b7ed32008e690486f5cd8a02\"); for logs run: kubectl -n default logs square-00001-c4s2w -c build-step-build-and-push".

I did initialize by using:
riff namespace init default --gcr gcr-storage-admin.json
and I can see the service account being created but push-credentials don't look right?
$ kubectl get sa riff-build -o yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  creationTimestamp: 2018-10-14T03:32:45Z
  name: riff-build
  namespace: default
  resourceVersion: "9019"
  selfLink: /api/v1/namespaces/default/serviceaccounts/riff-build
  uid: d0a7afbb-cf61-11e8-beeb-42010a000b0a
secrets:
- name: push-credentials
- name: riff-build-token-47mj8

$ kubectl get secrets push-credentials -o json
{
    "apiVersion": "v1",
    "data": {
        "password": "--snipped--",
        "username": "X2pzb25fa2V5"
    },
    "kind": "Secret",
    "metadata": {
        "annotations": {
            "build.knative.dev/docker-0": "https://gcr.io"
        },
        "creationTimestamp": "2018-10-14T15:08:03Z",
        "name": "push-credentials",
        "namespace": "default",
        "resourceVersion": "71480",
        "selfLink": "/api/v1/namespaces/default/secrets/push-credentials",
        "uid": "f2bc6311-cfc2-11e8-beeb-42010a000b0a"
    },
    "type": "kubernetes.io/basic-auth"
}

My theory is that the most probable root cause is a missing "storage.admin" role binding on the service account.
Unfortunately I was unable to repro that this would cause the failure above on our team GCP project - even when i initialize the namespace using a secret for a serviceaccount with no bindings at all.
@trisberg perhaps you could confirm that a missing role binding would indeed cause the failure.

Do you have the Google Container Registry enabled?
Error says
Please enable Google Container Registry API in Cloud Console at https://console.cloud.google.com/apis/api/containerregistry.googleapis.com/overview?project=fe-shgpupta before performing this operation.

You could try something like the following:

enable GCR:

gcloud services enable containerregistry.googleapis.com

create service account with storage.admin role:

gcloud iam service-accounts create push-image
export GCP_PROJECT=$(gcloud config get-value core/project)
gcloud projects add-iam-policy-binding $GCP_PROJECT \
  --member<EMAIL_ADDRESS>\
  --role roles/storage.admin

create JSON key for the service account:

export GCP_PROJECT=$(gcloud config get-value core/project)
gcloud iam service-accounts keys create \
  --iam-account<EMAIL_ADDRESS>\
  $HOME/push-image.json

initialize the default namespace with the push credentials you created:

riff namespace init default --gcr $HOME/push-image.json

So, I made little progress (by the way of cloud services enable step)… but it fails at a different error this time:
riff function create node square --git-repo https://github.com/projectriff-samples/node-square --artifact package.json --image gcr.io/$GCP_PROJECT/square --wait -v
Waiting for LatestCreatedRevisionName:. square-00001
default/square-00001-ngljj[build-step-riff-init]: Initializing with node invoker
default/square-00001-ngljj[build-step-riff-init]: Initializing /workspace/Dockerfile
default/square-00001-ngljj[build-step-riff-init]: Initializing /workspace/.dockerignore
default/square-00001-ngljj[build-step-build-and-push]: INFO[0000] Downloading base image projectriff/node-function-invoker:0.0.8
default/square-00001-ngljj[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 14:23:53.696991       1 metadata.go:142] while reading 'google-dockercfg' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg
default/square-00001-ngljj[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 14:23:53.699961       1 metadata.go:159] while reading 'google-dockercfg-url' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg-url
default/square-00001-ngljj[build-step-build-and-push]: 2018/10/15 14:23:53 No matching credentials were found, falling back on anonymous
default/square-00001-ngljj[build-step-build-and-push]: INFO[0000] Executing 0 build triggers
default/square-00001-ngljj[build-step-build-and-push]: INFO[0000] Extracting layer 0
default/square-00001-ngljj[build-step-build-and-push]: INFO[0001] Extracting layer 1
default/square-00001-ngljj[build-step-build-and-push]: INFO[0003] Extracting layer 2
default/square-00001-ngljj[build-step-build-and-push]: INFO[0004] Extracting layer 3
default/square-00001-ngljj[build-step-build-and-push]: INFO[0004] Extracting layer 4
default/square-00001-ngljj[build-step-build-and-push]: INFO[0004] Extracting layer 5
default/square-00001-ngljj[build-step-build-and-push]: INFO[0006] Taking snapshot of full filesystem...
default/square-00001-ngljj[build-step-build-and-push]: INFO[0011] ENV FUNCTION_URI /functions/
default/square-00001-ngljj[build-step-build-and-push]: INFO[0011] Using files from context: [/workspace]
default/square-00001-ngljj[build-step-build-and-push]: INFO[0011] COPY . ${FUNCTION_URI}
default/square-00001-ngljj[build-step-build-and-push]: INFO[0011] Taking snapshot of files...
default/square-00001-ngljj[build-step-build-and-push]: INFO[0012] RUN (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)
default/square-00001-ngljj[build-step-build-and-push]: INFO[0012] cmd: /bin/sh
default/square-00001-ngljj[build-step-build-and-push]: INFO[0012] args: [-c (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)]
default/square-00001-ngljj[build-step-build-and-push]: npm notice created a lockfile as package-lock.json. You should commit this file.
default/square-00001-ngljj[build-step-build-and-push]: up to date in 0.1s
default/square-00001-ngljj[build-step-build-and-push]: INFO[0012] Taking snapshot of full filesystem...
default/square-00001-ngljj[build-step-build-and-push]: error pushing image: failed to push to destination gcr.io/fe-shgupta/square:latest: no token in bearer response:
default/square-00001-ngljj[build-step-build-and-push]: {"errors":[{"code":"DENIED","message":"Token exchange failed for project 'fe-shgupta'. Caller does not have permission 'storage.buckets.get'. To configure permissions, follow instructions at: https://cloud.google.com/container-registry/docs/access-control"}]}

Error: function creation failed: RevisionMissing: Configuration "square" does not have any ready Revision.; Revision "square-00001" failed with message: "build step \"build-step-build-and-push\" exited with code 1 (image: \"docker-pullable://gcr.io/kaniko-project/executor@sha256:a59007aa409ea7734107e31e7ee323a4a8bd85f863de59fdd7018e85ed3c2b5a\"); for logs run: kubectl -n default logs square-00001-ngljj -c build-step-build-and-push".

I do have "Storage Admin" on the service account

did you re-initialize the namespace with the new push-image.json file created from the new service account?

I did. How can I confirm that all the pre-reqs are in place? Tried again:
riff function create node square --git-repo https://github.com/projectriff-samples/node-square --artifact package.json --image gcr.io/$GCP_PROJECT/square --wait -v
Waiting for LatestCreatedRevisionName:. square-00001
default/square-00001-s5zlp[build-step-credential-initializer]: {"level":"info","ts":1539615012.912515,"logger":"fallback-logger","caller":"creds-init/main.go:40","msg":"Credentials initialized."}
default/square-00001-s5zlp[build-step-git-source]: {"level":"info","ts":1539615017.0998971,"logger":"fallback-logger","caller":"git-init/main.go:74","msg":"Successfully cloned \"https://github.com/projectriff-samples/node-square\" @ \"master\""}
default/square-00001-s5zlp[build-step-riff-init]: Initializing with node invoker
default/square-00001-s5zlp[build-step-riff-init]: Initializing /workspace/Dockerfile
default/square-00001-s5zlp[build-step-riff-init]: Initializing /workspace/.dockerignore
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0000] Downloading base image projectriff/node-function-invoker:0.0.8
default/square-00001-s5zlp[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 14:50:26.408557       1 metadata.go:142] while reading 'google-dockercfg' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg
default/square-00001-s5zlp[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 14:50:26.411219       1 metadata.go:159] while reading 'google-dockercfg-url' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg-url
default/square-00001-s5zlp[build-step-build-and-push]: 2018/10/15 14:50:26 No matching credentials were found, falling back on anonymous
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0000] Executing 0 build triggers
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0000] Extracting layer 0
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0001] Extracting layer 1
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0003] Extracting layer 2
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0003] Extracting layer 3
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0003] Extracting layer 4
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0003] Extracting layer 5
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0005] Taking snapshot of full filesystem...
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] ENV FUNCTION_URI /functions/
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] Using files from context: [/workspace]
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] COPY . ${FUNCTION_URI}
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] Taking snapshot of files...
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] RUN (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] cmd: /bin/sh
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0010] args: [-c (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)]
default/square-00001-s5zlp[build-step-build-and-push]: npm notice created a lockfile as package-lock.json. You should commit this file.
default/square-00001-s5zlp[build-step-build-and-push]: up to date in 0.104s
default/square-00001-s5zlp[build-step-build-and-push]: INFO[0011] Taking snapshot of full filesystem...
default/square-00001-s5zlp[build-step-build-and-push]: error pushing image: failed to push to destination gcr.io/fe-shgupta/square:latest: no token in bearer response:
default/square-00001-s5zlp[build-step-build-and-push]: {"errors":[{"code":"DENIED","message":"Token exchange failed for project 'fe-shgupta'. Caller does not have permission 'storage.buckets.get'. To configure permissions, follow instructions at: https://cloud.google.com/container-registry/docs/access-control"}]}

Error: function creation failed: RevisionMissing: Configuration "square" does not have any ready Revision.; Revision "square-00001" failed with message: "build step \"build-step-build-and-push\" exited with code 1 (image: \"docker-pullable://gcr.io/kaniko-project/executor@sha256:a59007aa409ea7734107e31e7ee323a4a8bd85f863de59fdd7018e85ed3c2b5a\"); for logs run: kubectl -n default logs square-00001-s5zlp -c build-step-build-and-push".

You could run something like:
kubectl get secret push-credentials -o "jsonpath={.data.password}" | base64 -D

and verify you have the right JSON credentials in the secret you are using

Confirmed that the JSON is exactly the same as was uploaded from $HOME/push-image.json...
Questions:

Does this line of output mean anything default/square-00001-s5zlp[build-step-build-and-push]: 2018/10/15 14:50:26 No matching credentials were found, falling back on anonymous
default/square-00001-s5zlp[build-step-build-and-push]: error pushing image: failed to push to destination gcr.io/fe-shgupta/square:latest: no token in bearer response this tells me that authentication hasn't happened with container registry to have a bearer token?

Exact same setup, but on GKE works perfectly fine.
riff function create node square --git-repo https://github.com/projectriff-samples/node-square --artifact package.json --image gcr.io/$GCP_PROJECT/square --wait -v
Waiting for LatestCreatedRevisionName:. square-00001
default/square-00001-4gh45[build-step-build-and-push]: INFO[0000] Downloading base image projectriff/node-function-invoker:0.0.8
default/square-00001-4gh45[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 18:20:55.047820       1 metadata.go:142] while reading 'google-dockercfg' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg
default/square-00001-4gh45[build-step-build-and-push]: ERROR: logging before flag.Parse: E1015 18:20:55.050255       1 metadata.go:159] while reading 'google-dockercfg-url' metadata: http status code: 404 while fetching url http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg-url
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:20:55 No matching credentials were found, falling back on anonymous
default/square-00001-4gh45[build-step-build-and-push]: INFO[0000] Executing 0 build triggers
default/square-00001-4gh45[build-step-build-and-push]: INFO[0000] Extracting layer 0
default/square-00001-4gh45[build-step-build-and-push]: INFO[0001] Extracting layer 1
default/square-00001-4gh45[build-step-build-and-push]: INFO[0002] Extracting layer 2
default/square-00001-4gh45[build-step-build-and-push]: INFO[0003] Extracting layer 3
default/square-00001-4gh45[build-step-build-and-push]: INFO[0003] Extracting layer 4
default/square-00001-4gh45[build-step-build-and-push]: INFO[0003] Extracting layer 5
default/square-00001-4gh45[build-step-build-and-push]: INFO[0004] Taking snapshot of full filesystem...
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] ENV FUNCTION_URI /functions/
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] Using files from context: [/workspace]
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] COPY . ${FUNCTION_URI}
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] Taking snapshot of files...
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] RUN (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] cmd: /bin/sh
default/square-00001-4gh45[build-step-build-and-push]: INFO[0007] args: [-c (cd ${FUNCTION_URI} && npm install --production  --unsafe-perm)]
default/square-00001-4gh45[build-step-build-and-push]: npm notice created a lockfile as package-lock.json. You should commit this file.
default/square-00001-4gh45[build-step-build-and-push]: up to date in 0.088s
default/square-00001-4gh45[build-step-build-and-push]: INFO[0008] Taking snapshot of full filesystem...
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:05 existing blob: sha256:605ce1bd3f3164f2949a30501cc596f52a72de05da1306ab360055f0d7130c32
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:98cfc19c2da6c1afc0b7de59ed7d351fd4939561387057b5128a52fefbd27ffa
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:3f0ff71f6ba10ec6ba666d261c4794b81d2ce0ef92b7e01cf806a3ced5a1e8d6
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:b9120239cfdf2d1f88c148a98c9867a8f7d6261e770554d5de4e4382abea905d
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:793b21730bffa835e14b49234d5e0cf637d3af96b5d01bb1c2b8e1f04efc7163
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:343e34c41f87fd40fa77e38946458ec27e88aedd8607f8a60e1c92c0bb25e123
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:07 pushed blob sha256:1467c8ee45df61e24a02ca3de448e45a287485f3bfd700b7b52462b70eabc101
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:08 pushed blob sha256:e727997e671263b3e33f36f22e96ed5ce246a2314ea28bfd7008e6593cb6e6b3
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:08 pushed blob sha256:0511902e1bcd00eb5002093590197ce40e984c181e63719167e393b6a06cf944
default/square-00001-4gh45[build-step-build-and-push]: 2018/10/15 18:21:08 gcr.io/fe-shgupta/square:latest: digest: sha256:afa9704fab47c8cae57501e63f3ff1d54092eb23ec59d5c67350a2405a47c0a0 size: 1566
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: Node started in 90ms
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: Server starting with undefined interaction model and undefined argument type
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: gRPC loaded in 153ms
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: HTTP loaded in 95ms
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: gRPC running on localhost:10382
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: HTTP running on localhost:8080
default/square-00001-deployment-547dc6bcdc-2bdww[user-container]: Function invoker started in 343ms
riff function create completed successfully

Interesting, I'll see if I can find someone who is more familiar with Knative builds on PKS to take a look.

If it helps, the other difference is the GKE installation is 1.10.7 and PKS is 1.11.2 for K8s.

That version should be fine, I run with 11.x on minikube without problems

I am also having this issue. Let me know if you need any additional information to help resolve.

Also, similar problem on minikube - https://github.com/projectriff/riff/issues/723

I created an issue in knative/build for similar issue on GKE pushing to GCR running in a different GCP project - https://github.com/knative/build/issues/450

Please document how to allow PKS to push images to GCR (running on google cloud).

Now that riff use the Cloud Native Buildpacks v3 and no longer uses Kaniko, this is not a problem any more.
You need to initialize the namespace with proper credentials for pushing images using riff namespace init default --gcr <path-to-json-key-with-image-push-credentials>
You also need to add imagePullSecret with image-pull credentials for the namespace. That can be done using:
export PULL_IMAGE_JSON_KEY=<path-to-json-key-with-image-pull-credentials>
kubectl create secret docker-registry "gcr" \
  --docker-server=gcr.io \
  --docker-username=_json_key \
  --docker-password="$(cat $PULL_IMAGE_JSON_KEY)" \
  --docker-email=$(gcloud config get-value core/account) \
  --namesapace "default"
kubectl patch serviceaccount "default" \
  --patch '{"imagePullSecrets": [{"name": "gcr"}]}' \
  --namesapace "default"

We can close this issue once riff 0.2.0 is released

Thanks @trisberg - just one question:
Could you clarify if the image pull secret is required for builds when riff itself has been installed on PKS from images on public OSS repos?  -- i.o.w Do builds required both pull and push credentials?

the pull secret would still be required since you are pushing the function image to private GCR repo

closing per https://github.com/projectriff/riff/issues/879#issuecomment-439450739 now that v0.2.0 has been released.


Refactor weight generation code to use a templating language

Refactor the weight file generation code to use a templating language and allow people to pass a custom template.
This will allow people to customize header, footer, spacing, format etc.
https://github.com/paritytech/substrate/blob/master/utils/frame/benchmarking-cli/src/writer.rs
handlebars will be a good templating language to use.

completed with https://github.com/paritytech/substrate/pull/7390
Thanks again @zadmarbella


Segmentation fault while testing detector with pytest

I am using:
-Python 3.6.0
-pytest 3.9.1
-tensorflow-gpu 1.11.0
-ubuntu 16.04
My error:
(anonymizer) uidn4908@frd87sju:~/anonymizer$ pytest
================= test session starts ============================
platform linux -- Python 3.6.0, pytest-3.9.1, py-1.8.1, pluggy-0.13.1
rootdir: /home/uidn4908/anonymizer, inifile: pytest.ini
collected 6 items
test/anonymization/anonymizer_test.py .. [ 33%]
test/detection/detector_test.py Speicherzugriffsfehler
After some debugging i narrowed it down to line 50 in detector.py:
num_boxes, scores, boxes = self.session.run(
[num_detections, detection_scores, detection_boxes],
feed_dict={image_tensor: np_images})
Anybody a similar issue? Or an idea how to solve this ?

After some further investigation i still could not find the issue that caused this error.
So i finally tried it by upgrading tensorflow-gpu to version 1.12.0 and this resolves the error.


AWSLOGS

Relevant information
Adding AWSLogs
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Monitoring-CloudWatch-Metrics.html
Checklist

[x] I've read the guidelines and understand the acceptance criteria.
[x] The value of the attribute marked as identifier will be unique and valid.
[x] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

@entityBot deploy


are file extensions required or should there be a default?

When running PyFr we get the log:
[13:42:42.870] INFO: Downloading input mesh.
[13:42:42.870] INFO: Downloading complete.
[13:42:42.870] ERROR: Exception raise by task: list index out of range

A more precise error in command.log leading to this line
[2016-03-02 23:54:30,136: ERROR/Worker-3] Exception raise by task: list index out of range
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 240, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 438, in __protected_call__
    return self.run(*args, **kwargs)
  File "cumulus/taskflow/__init__.py", line 118, in wrapped
    return func(celery_task, *args, **kwargs)
  File "/opt/hpccloud/hpccloud/server/taskflows/hpccloud/taskflow/pyfr.py", line 159, in import_mesh
    extn = file['exts'][0]
IndexError: list index out of range
[2016-03-02 23:54:30,182: ERROR/MainProcess] Task hpccloud.taskflow.pyfr.import_mesh[f276c2b0-f20f-4b39-85c9-e1be1ac8a111] raised unexpected: IndexError('list index out of range',)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 240, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 438, in __protected_call__
    return self.run(*args, **kwargs)
  File "cumulus/taskflow/__init__.py", line 118, in wrapped
    return func(celery_task, *args, **kwargs)
  File "/opt/hpccloud/hpccloud/server/taskflows/hpccloud/taskflow/pyfr.py", line 159, in import_mesh
    extn = file['exts'][0]
IndexError: list index out of range

Fetching the file from the API however exts has no content:

A file extension is required at the moment as that is how we ( PyFR )
determines the mesh type
On Wed, Mar 2, 2016 at 7:16 PM, TristanWright<EMAIL_ADDRESS>wrote:

When running PyFr we get the log:
[13:42:42.870] INFO: Downloading input mesh.
[13:42:42.870] INFO: Downloading complete.
[13:42:42.870] ERROR: Exception raise by task: list index out of range
A more precise error in command.log leading to this line
https://github.com/Kitware/HPCCloud/blob/dev-v2/server/taskflows/hpccloud/taskflow/pyfr.py#L159
[2016-03-02 23:54:30,136: ERROR/Worker-3] Exception raise by task: list index out of range
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 240, in trace_task
R = retval = fun(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 438, in protected_call
return self.run(*args, **kwargs)
File "cumulus/taskflow/init.py", line 118, in wrapped
return func(celery_task, *args, **kwargs)
File "/opt/hpccloud/hpccloud/server/taskflows/hpccloud/taskflow/pyfr.py", line 159, in import_mesh
extn = file['exts'][0]
IndexError: list index out of range
[2016-03-02 23:54:30,182: ERROR/MainProcess] Task hpccloud.taskflow.pyfr.import_mesh[f276c2b0-f20f-4b39-85c9-e1be1ac8a111] raised unexpected: IndexError('list index out of range',)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 240, in trace_task
R = retval = fun(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 438, in protected_call
return self.run(*args, **kwargs)
File "cumulus/taskflow/init.py", line 118, in wrapped
return func(celery_task, *args, **kwargs)
File "/opt/hpccloud/hpccloud/server/taskflows/hpccloud/taskflow/pyfr.py", line 159, in import_mesh
extn = file['exts'][0]
IndexError: list index out of range
Fetching the file from the API however exts has no content:
[image: screen shot 2016-03-02 at 17 12 59]
https://cloud.githubusercontent.com/assets/13318121/13480300/1b6be752-e09a-11e5-9e4b-0dce656049e0.png
—
Reply to this email directly or view it on GitHub
https://github.com/Kitware/HPCCloud/issues/201.

got this sorted out in 81ee5a9ef887807430ead9ee5ee4ad26ad37c5a4, thanks.


Prototyping connection state

This PR prototypes the concept of connection state.
I am introducing an ``EventEmitter` to schema poller class that consumers may subscribe to to be notified of connection events. Currently there are 2.. Connected and Reconnecting.. Connected is fired when a driver is initialized and passes auth/connectivity checks. Reconnecting is fired when a driver fails to pass auth and connectivity checks. I've gone with Reconnecting since the schema poller will retry every 30 seconds until it succeeds or the driver is closed.
In the extension UI, when you connect to a connection you are first presented with a "Connecting" state.. the label next to the connection will briefly read connecting... until the Connected event fires and we can update state, at which point we switch the label to connected and show a success info message. For connections that are unhealthy we will show a reconnecting... label and an accompanying error message.
This state will automatically update itself when the schema next polls.. i.e. if a connection becomes unhealthy, the UI will receive an update.

 [VSCode Extension] Synchronicity between DBMS connection and extension


Canceling animation doesn't clear nested effect with zero duration

See the test case: http://jsbin.com/tahafemoso/1/edit?html,js,output
The red background is expected to be reverted to the initial value once the animation has finished. Giving fx1 a duration of 1 fixes the problem.

Can reproduce when web-animations-1 polyfill is active, it doesn't occur when native backed.


Docker image build can't find deltalake-core dependency

Following the set up instructions from main and docker build -t kdi:0.1 . -f Dockerfile.Debian fails to resolve deltalake-core dependency:
> [builder 4/4] RUN cargo install --path .:
0.200   Installing kafka-delta-ingest v0.2.0 (/usr/src/kafka-delta-ingest)
0.328     Updating crates.io index
20.97     Updating git repository `https://github.com/delta-io/delta-rs`
22.61 error: failed to compile `kafka-delta-ingest v0.2.0 (/usr/src/kafka-delta-ingest)`, intermediate artifacts can be found at `/usr/src/kafka-delta-ingest/target`
22.61
22.61 Caused by:
22.61   no matching package named `deltalake-core` found
22.61   location searched: https://github.com/delta-io/delta-rs?branch=main
22.61   required by package `kafka-delta-ingest v0.2.0 (/usr/src/kafka-delta-ingest)`
------
Dockerfile.Debian:4
--------------------
   2 |     WORKDIR /usr/src/kafka-delta-ingest
   3 |     COPY . .
   4 | >>> RUN cargo install --path .
   5 |
   6 |     FROM debian:bullseye
--------------------
ERROR: failed to solve: process "/bin/sh -c cargo install --path ." did not complete successfully: exit code: 101

@beanscouts I have some local changes I had been meaning to push which update the main Dockerfile. I was intending to just delete Dockerfile.debian Do you have a strong reason for that, or would me cleaning up the main Dockerfile be sufficient

@rtyler No strong reason, no. Just following the README.md instructions to get running with this software. I'll hold out for the stashed changes - thanks!


Trouble understanding

I am a complete newbie for flat databases and PHP. I have trouble creating database and inserting record in it.I get a lot of errors thrown..........I'm not sure what is the path i must give for 'path/for/storage/dir'. I'm having trouble running it in console too.
I find flatbase easy to relate with sql queries and easy to understand the code,but a simple example or pointing out where I'm going wrong would be of great help.
I am planning on using this flatbase flat file database for storing the users who change password. It's like log to my page. Any suggestions are welcome.
Thank You.
I use PHP 7.2
Code :
`

use Flatbase\Exception\Exception;
use Flatbase\Handler\DeleteQueryHandler;
use Flatbase\Handler\InsertQueryHandler;
use Flatbase\Handler\ReadQueryHandler;
use Flatbase\Handler\UpdateQueryHandler;
use Flatbase\Query\DeleteQuery;
use Flatbase\Query\InsertQuery;
use Flatbase\Query\Query;
use Flatbase\Query\ReadQuery;
use Flatbase\Query\UpdateQuery;
use Flatbase\Storage\Filesystem;
use Flatbase\Storage\Storage;
use Flatbase\Flatbase;
use Flatbase\Collection;

$storage = new Flatbase\Storage\Filesystem('/home/user/Flatdb/Logs/users');
$flatbase = new Flatbase\Flatbase($storage);

$flatbase->insert()->in('users')->set(['name' => 'Adam', 'height' => "6'4"])->execute();

$flatbase->read()->in('users')->where('name', '=', 'Adam')->first();
?>

`

I get these Errors:
`PHP Fatal error:  Uncaught Exception: Stream contents is corrupt in /home/ldap/ChangePassword/vendor/php-serializer/php-serializer/src/SerializedArray.php:135
Stack trace:
#0 /home/ldap/ChangePassword/vendor/php-serializer/php-serializer/src/SerializedArray.php(21): PHPSerializer\SerializedArray->rewind()
#1 /home/ldap/ChangePassword/vendor/flatbase/flatbase/src/Handler/QueryHandler.php(120): PHPSerializer\SerializedArray->__construct(Object(SplFileObject))
#2 /home/ldap/ChangePassword/vendor/flatbase/flatbase/src/Handler/InsertQueryHandler.php(15): Flatbase\Handler\QueryHandler->getIterator('users')
#3 /home/ldap/ChangePassword/vendor/flatbase/flatbase/src/Flatbase.php(40): Flatbase\Handler\InsertQueryHandler->handle(Object(Flatbase\Query\InsertQuery))
#4 /home/ldap/ChangePassword/vendor/flatbase/flatbase/src/Query/Query.php(119): Flatbase\Flatbase->execute(Object(Flatbase\Query\InsertQuery))
#5 /home/ldap/ChangePassword/try.php(15): Flatbase\Query\Query->execute()
#6 {main}
thrown in /home/ldap/ChangePassword/vendor/php-serializer/php-serializer/src/SerializedArray.php on line 135
`

Are you sure flatbase is correctly installed? If yes, make sure to add the Composer autoload thing at the top of your file, like so :
require __DIR__ . '/vendor/autoload.php';

More on this here.
@Jeya27

Thank you for your help @locness3

I think you should close this issue now ;)


Update documentation to make it more clear to use match

          1 Warning

:warning:
Please provide a changelog summary in the Pull Request description @KrauseFx

  Generated by :no_entry_sign: Danger


error: ‘class jwt::decoded_jwtjwt::traits::nlohmann_json’ has no member named ‘get_payload_json’;

What happened?
Tried to follow the example in Getting Started section of README with slight modifications.
It threw a compiler error stating a method was not found which is weird.
I think the issue can be fixed by using decoded_jwt::get_payload_claims() function. The README code may need to be changed.
I also noticed that this issue in README is there in the master branch. When I check README of v0.6.0 release artifacts, I see get_payload_claims() mentioned correctly there.
How To Reproduce?
#include "jwt-cpp/traits/nlohmann-json/traits.h"
#include <iostream>

int main()
{
    std::string token = "eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.VFb0qJ1LRg_4ujbZoRMXnVkUgiuKq5KxWqNdbKq_G9Vvz-S1zZa9LPxtHWKa64zDl2ofkT8F6jBt_K4riU-fPg";
    auto decoded = jwt::decode<jwt::traits::nlohmann_json>(token);
    for (auto& [k, v] : decoded.get_payload_json())
        std::cout << k << '=' << v << '\n';
}

Run with: g++ main.cpp -I /path/to/jwt-cpp-0.6.0/include/
Version
0.6.0
What OS are you seeing the problem on?
Linux
What compiler are you seeing the problem on?
GCC
Relevant log output
main.cpp: In function ‘int main()’:
main.cpp:8:33: error: ‘class jwt::decoded_jwt<jwt::traits::nlohmann_json>’ has no member named ‘get_payload_json’; did you mean ‘get_payload’?
    8 |     for (auto& [k, v] : decoded.get_payload_json())
      |                                 ^~~~~~~~~~~~~~~~
      |                                 get_payload

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

I am not sure what the issue is 🤔
0.6.0 matches the readme and master matches? The code in question is unreleased https://github.com/Thalhammer/jwt-cpp/commit/cba92ab173f45bb028f287b4acdbdb9d06352499 is that what might have tripped you up?
The releases are infrequent since it's very stable but I dont think it's an issue for master docs to match the master code. Thats very common.

@prince-chrismc Yes it seems I got confused because I downloaded the release artifacts but kept the repo's URL open in the browser which showed the master branch README which had a new API in the example.
I see you mentioned the exact commit (cba92ab) where this API was changed. I think it would be better to keep the older API but with some deprecation warning in the new release. Else, it can completely break some code that used the old API and now wants to migrate to a new version due to some reasons.

I think it would be better to keep the older API but with some deprecation warning in the new release.

I generally agree, but jwt-cpp had way more impactful API breaks in the past. In this case for most codebases it will boil down to replacing all occurrences of get_payload_claims with get_payload_json. We'd like to adopt semver eventually, but I'd like to make sure its actually usable before, so we don't end up with a version 200.1.1.

We do try to avoid breaking the API, there are most often aliases left to avoid any impact. It's a hardline to balance improvements and not changing.
Ticked this as closed since the docs for that release were correct :)


Adjust read timeout

@arturantonnikau Please also provide a description to the MR about what we are doing and why we are doing it. 🙇

Can we add some tests for the new method?


Fix to the holy grail code in the inspector

I'm sorry about the whitespace, it's all spaces at my side.

Don't know what I m doing


Reuse LeafReader where possible in StoredRowLookup

Currently StoredRowLookup will pull new iterators on every new document,
but this will quite often not be necessary.  Instead, we compare the previously
cached reader and document id against the new lookup request, and if the
reader is the same and the document id is higher, we don't reset readers on
any internal expressions so that iterators are re-used.

Benchmarks are happy:
compare_run.py --v1 branch:master --v2 branch:aw/storage/stored-row-always-in-order --spec specs/queries.toml

# Results (server side duration in ms)
V1: 5.10.0-a779810d48892a6ad0f5a5b86ae7f69717c42f52
V2: 5.10.0-c107c6204382a29cee78024ea14c49ffd8a7643b

Q: select * from uservisits limit 10
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.515 ±    0.899 |      0.304 |      0.435 |      0.555 |     28.371 |
|   V2    |        0.505 ±    0.895 |      0.290 |      0.421 |      0.550 |     28.204 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   1.88%                           -   3.24%
There is a 18.93% probability that the observed difference is not random, and the best estimate of that difference is 1.88%
The test has no statistical significance

Q: select * from uservisits limit 100
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.605 ±    0.121 |      0.501 |      0.581 |      0.624 |      2.144 |
|   V2    |        0.489 ±    0.098 |      0.372 |      0.475 |      0.516 |      1.994 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  21.17%                           -  20.20%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 21.17%
The test has statistical significance

Q: select * from uservisits limit 100
C: 20
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.989 ±    0.954 |      0.527 |      0.804 |      1.012 |     12.520 |
|   V2    |        0.571 ±    0.602 |      0.364 |      0.416 |      0.571 |      8.498 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  53.58%                           -  63.50%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 53.58%
The test has statistical significance

Q: select * from uservisits limit 1000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        3.979 ±    0.597 |      3.690 |      3.902 |      3.974 |     13.498 |
|   V2    |        2.629 ±    0.254 |      2.434 |      2.602 |      2.651 |      6.945 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  40.86%                           -  39.95%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 40.86%
The test has statistical significance

Q: select * from uservisits limit 10000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       38.254 ±    1.123 |     37.454 |     37.960 |     38.194 |     50.537 |
|   V2    |       25.374 ±    1.740 |     24.680 |     25.109 |     25.266 |     49.915 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  40.49%                           -  40.75%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 40.49%
The test has statistical significance

Q: select * from uservisits limit 100000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |      424.161 ±   18.115 |    378.174 |    423.107 |    436.444 |    503.178 |
|   V2    |      269.404 ±   12.998 |    244.273 |    272.976 |    278.115 |    328.567 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  44.63%                           -  43.14%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 44.63%
The test has statistical significance

Q: select * from uservisits order by "adRevenue" limit 10
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        6.756 ±    1.617 |      6.339 |      6.563 |      6.654 |     53.688 |
|   V2    |        7.023 ±    1.840 |      6.395 |      6.847 |      6.997 |     61.084 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               +   3.88%                           +   4.24%
There is a 99.94% probability that the observed difference is not random, and the best estimate of that difference is 3.88%
The test has statistical significance

Q: select * from uservisits order by "adRevenue" limit 10
C: 20
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       57.438 ±   21.885 |     15.535 |     54.861 |     73.634 |    157.223 |
|   V2    |       55.448 ±   20.829 |      9.656 |     51.668 |     70.342 |    125.894 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   3.53%                           -   5.99%
There is a 96.26% probability that the observed difference is not random, and the best estimate of that difference is 3.53%
The test has no statistical significance

Q: select "cCode", count(*) from uservisits group by 1 order by 2 desc limit 20
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        8.842 ±    8.796 |      7.820 |      7.952 |      8.098 |    177.243 |
|   V2    |        8.912 ±   11.515 |      7.847 |      8.001 |      8.107 |    225.726 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               +   0.79%                           +   0.62%
There is a 8.60% probability that the observed difference is not random, and the best estimate of that difference is 0.79%
The test has no statistical significance

Q: select extract(day from "visitDate"), count(*) from uservisits group by 1 order by 2 desc limit 20
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       50.235 ±    6.515 |     48.851 |     49.839 |     50.050 |    193.140 |
|   V2    |       47.707 ±    5.782 |     44.665 |     47.364 |     48.922 |    163.839 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   5.16%                           -   5.09%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 5.16%
The test has statistical significance

System/JVM Metrics (durations in ms, byte-values in MB)
    |    YOUNG GC            |       OLD GC           |      HEAP         |     ALLOC
    |  cnt      avg      max |  cnt      avg      max |  initial     used |     rate      total
 V1 | 1771     1.76     1.11 |  534    15.57    40.32 |      268       53 |  2526.58     326513
 V2 |  631     3.06     1.68 |  204    19.24    16.11 |      268       61 |   837.43     120240

Top allocation frames
  V1
    Unsafe.allocateUninitializedArray(Class, int) total=109412645112, count=7095
    MappedMemorySegmentImpl.dup(...) total=41035588086, count=2816
    MemorySegmentIndexInput.buildSlice(...) total=27629841896, count=2050
    Arrays.copyOf(...) total=26546001616, count=1189
    Array.newInstance(Class, int) total=12810080623, count=799
    MemorySegmentIndexInput$SingleSegmentImpl.<init>(...) total=11663191456, count=711
    DirectMonotonicReader.getInstance(...) total=11532352313, count=782
    StringConcatHelper.newString(...) total=10967720064, count=785
    CustomLucene90DocValuesProducer$BaseSortedDocValues.termsEnum() total=8713653080, count=447
    StringUTF16.compress(...) total=7818580552, count=475
  V2
    Arrays.copyOf(...) total=27520270048, count=2840
    StringUTF16.compress(...) total=14740106096, count=2122
    BytesRef.utf8ToString() total=9791344432, count=1772
    ArrayList.iterator() total=7376982696, count=278
    HashMap.newNode(...) total=7132887640, count=1325
    AbstractBigArray.newBytePage(int) total=6178410736, count=1037
    CharsRef.toString() total=5222230864, count=763
    DirectMethodHandle.allocateInstance(Object) total=4952664880, count=3144
    FetchCollector.collect(...) total=4138346804, count=9
    IndexSearcher.getNumClausesCheckVisitor() total=3535350808, count=132

Top frames (by count)
  V1
    Unsafe.allocateUninitializedArray(Class, int) total=109412645112, count=7095
    GregorianChronology.isLeapYear(int) total=4860, count=4860
    MappedMemorySegmentImpl.dup(...) total=41035588086, count=2816
    MemorySegmentIndexInput.buildSlice(...) total=27629841896, count=2050
    TopFieldCollector$SimpleFieldCollector$1.collect(int) total=1985, count=1985
    Long.valueOf(long) total=810488436, count=1706
    Row.materialize() total=333482672, count=1295
    DirectMethodHandle.allocateInstance(Object) total=2207332881, count=1258
    IntObjectHashMap.allocateBuffers(int) total=676166968, count=1191
    Arrays.copyOf(...) total=26546001616, count=1189
  V2
    Long.valueOf(long) total=2171152282, count=3965
    GregorianChronology.isLeapYear(int) total=3443, count=3443
    Row.materialize() total=641548608, count=3292
    DirectMethodHandle.allocateInstance(Object) total=4952664880, count=3144
    Arrays.copyOf(...) total=27520270048, count=2840
    IntObjectHashMap.allocateBuffers(int) total=1015578131, count=2146
    StringUTF16.compress(...) total=14740106096, count=2122
    BytesRef.utf8ToString() total=9791344432, count=1772
    TopFieldCollector$SimpleFieldCollector$1.collect(int) total=1701, count=1701
    HashMap.newNode(...) total=7132887640, count=1325

Looks like we're back to where we were in 5.9, or even slightly ahead:
compare_run.py --v1 branch:5.9 --v2 branch:aw/storage/stored-row-always-in-order --spec specs/queries.toml

# Results (server side duration in ms)
V1: 5.9.3-c5619e50036acb5ef8b43c6b453f08d6480c4737
V2: 5.10.0-c107c6204382a29cee78024ea14c49ffd8a7643b

Q: select * from uservisits limit 10
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.587 ±    1.676 |      0.288 |      0.430 |      0.609 |     52.360 |
|   V2    |        0.515 ±    0.885 |      0.304 |      0.435 |      0.566 |     27.899 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  12.97%                           +   1.14%
There is a 76.71% probability that the observed difference is not random, and the best estimate of that difference is 12.97%
The test has no statistical significance

Q: select * from uservisits limit 100
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.522 ±    0.264 |      0.405 |      0.501 |      0.542 |      7.952 |
|   V2    |        0.488 ±    0.552 |      0.375 |      0.448 |      0.492 |     17.621 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   6.83%                           -  11.10%
There is a 92.50% probability that the observed difference is not random, and the best estimate of that difference is 6.83%
The test has no statistical significance

Q: select * from uservisits limit 100
C: 20
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        0.936 ±    1.009 |      0.387 |      0.710 |      0.948 |     12.995 |
|   V2    |        0.604 ±    0.674 |      0.380 |      0.480 |      0.613 |     12.658 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  43.16%                           -  38.53%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 43.16%
The test has statistical significance

Q: select * from uservisits limit 1000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        2.651 ±    0.169 |      2.489 |      2.628 |      2.679 |      5.345 |
|   V2    |        2.628 ±    0.280 |      2.442 |      2.602 |      2.661 |      9.356 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   0.86%                           -   0.98%
There is a 97.08% probability that the observed difference is not random, and the best estimate of that difference is 0.86%
The test has no statistical significance

Q: select * from uservisits limit 10000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       25.561 ±    0.845 |     25.123 |     25.396 |     25.492 |     34.402 |
|   V2    |       25.687 ±    0.740 |     25.091 |     25.586 |     25.721 |     35.797 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               +   0.49%                           +   0.75%
There is a 98.82% probability that the observed difference is not random, and the best estimate of that difference is 0.49%
The test has statistical significance

Q: select * from uservisits limit 100000
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |      277.212 ±   13.734 |    253.710 |    278.523 |    284.984 |    361.252 |
|   V2    |      274.203 ±   12.923 |    249.741 |    278.007 |    282.875 |    329.361 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   1.09%                           -   0.19%
There is a 98.80% probability that the observed difference is not random, and the best estimate of that difference is 1.09%
The test has statistical significance

Q: select * from uservisits order by "adRevenue" limit 10
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        7.877 ±    2.474 |      6.288 |      7.857 |      7.971 |     83.242 |
|   V2    |        6.827 ±    1.812 |      6.371 |      6.624 |      6.754 |     59.196 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  14.29%                           -  17.03%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 14.29%
The test has statistical significance

Q: select * from uservisits order by "adRevenue" limit 10
C: 20
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       61.017 ±   23.525 |     15.377 |     56.952 |     78.115 |    134.964 |
|   V2    |       57.197 ±   21.629 |     14.745 |     53.434 |     71.825 |    131.615 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -   6.46%                           -   6.37%
There is a 99.98% probability that the observed difference is not random, and the best estimate of that difference is 6.46%
The test has statistical significance

Q: select "cCode", count(*) from uservisits group by 1 order by 2 desc limit 20
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |        8.942 ±   13.555 |      7.600 |      7.857 |      7.993 |    255.504 |
|   V2    |        9.439 ±   13.541 |      7.998 |      8.167 |      8.278 |    266.831 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               +   5.41%                           +   3.87%
There is a 43.84% probability that the observed difference is not random, and the best estimate of that difference is 5.41%
The test has no statistical significance

Q: select extract(day from "visitDate"), count(*) from uservisits group by 1 order by 2 desc limit 20
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |       51.589 ±    5.976 |     47.553 |     51.071 |     52.275 |    178.037 |
|   V2    |       51.682 ±    5.290 |     50.220 |     51.249 |     51.703 |    164.981 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               +   0.18%                           +   0.35%
There is a 20.61% probability that the observed difference is not random, and the best estimate of that difference is 0.18%
The test has no statistical significance

System/JVM Metrics (durations in ms, byte-values in MB)
    |    YOUNG GC            |       OLD GC           |      HEAP         |     ALLOC
    |  cnt      avg      max |  cnt      avg      max |  initial     used |     rate      total
 V1 | 1005     2.35     0.62 |  264    18.32    15.92 |      268      204 |  1373.56     204327
 V2 |  631     3.15     1.37 |  200    20.02    21.60 |      268       61 |   802.63     117752

Top allocation frames
  V1
    Long.valueOf(long) total=48094539057, count=12303
    Arrays.copyOf(...) total=26802630712, count=2911
    StringUTF16.compress(...) total=19921801504, count=2035
    HashMap.newNode(...) total=14917003875, count=2056
    StoredFieldVisitor.binaryField(...) total=8462133789, count=822
    ArrayList.iterator() total=5963997200, count=153
    HashMap.resize() total=5891594830, count=731
    AbstractBigArray.newBytePage(int) total=5880782688, count=670
    CharsRef.toString() total=4874141433, count=543
    ByteSourceJsonBootstrapper.constructParser(...) total=4816119579, count=680
  V2
    Arrays.copyOf(...) total=25708140792, count=3142
    StringUTF16.compress(...) total=15191736936, count=2243
    BytesRef.utf8ToString() total=9964995000, count=1756
    HashMap.newNode(...) total=8485091936, count=1404
    ArrayList.iterator() total=6641830128, count=162
    CharsRef.toString() total=6607416568, count=754
    AbstractBigArray.newBytePage(int) total=5252192320, count=830
    DirectMethodHandle.allocateInstance(Object) total=3670970072, count=564
    FetchCollector.collect(...) total=3519795212, count=10
    Arrays.copyOfRange(...) total=3474241777, count=616

Top frames (by count)
  V1
    Long.valueOf(long) total=48094539057, count=12303
    Row.materialize() total=633068408, count=3701
    GregorianChronology.isLeapYear(int) total=3478, count=3478
    Arrays.copyOf(...) total=26802630712, count=2911
    TopFieldCollector$SimpleFieldCollector$1.collect(int) total=2582, count=2582
    IntObjectHashMap.allocateBuffers(int) total=1060584088, count=2297
    HashMap.newNode(...) total=14917003875, count=2056
    StringUTF16.compress(...) total=19921801504, count=2035
    GroupByOptimizedIterator.aggregateValues(...) total=869, count=869
    GroupingCollector.iter(Map, Row) total=861, count=861
  V2
    Long.valueOf(long) total=2210589905, count=5481
    Row.materialize() total=655268336, count=4325
    GregorianChronology.isLeapYear(int) total=4248, count=4248
    Arrays.copyOf(...) total=25708140792, count=3142
    IntObjectHashMap.allocateBuffers(int) total=994990536, count=2320
    StringUTF16.compress(...) total=15191736936, count=2243
    BytesRef.utf8ToString() total=9964995000, count=1756
    TopFieldCollector$SimpleFieldCollector$1.collect(int) total=1717, count=1717
    HashMap.newNode(...) total=8485091936, count=1404
    MemorySessionImpl.checkValidStateRaw() total=976, count=976


Snakemake spontaneously interrupts jobs when running singularity

Snakemake version
8.14
Describe the bug
I think this is the same as issue #434. Since the issue has gone cold and the minimal example was not as minimal as it could have been I think it deserves a new bug report. I am happy to move to a comment on this older bug report if you think that is more appropriate. Snakemake seems to sometimes spontaneously quit all running jobs. Nothing is written to the per-job log files suggesting that the error does not originate from the utility being run inside the rule. I have so far only observed this when using the 'container directive'. This has nothing obviously to do with the utilities being used in the workflow itself. I observe the behaviour when the rule simply waits for an hour and then exits (see the minimal example).
For me this usually happens at least once every 24 hours, but not reliably on the same job.
Logs
Building DAG of jobs...
Pulling singularity image docker://ubuntu:latest.
Using shell: /usr/bin/bash
Provided cores: 2
Rules claiming more threads will be scaled down.
Job stats:
job      count
-----  -------
all          1
wait        80
total       81

Select jobs to execute...
Execute 2 jobs...

[Tue Jul  9 12:15:23 2024]
localrule wait:
    output: output/15.txt
    log: logs/wait/15.log
    jobid: 16
    reason: Missing output files: output/15.txt
    wildcards: rep=15
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg

[Tue Jul  9 12:15:23 2024]
localrule wait:
    output: output/66.txt
    log: logs/wait/66.log
    jobid: 67
    reason: Missing output files: output/66.txt
    wildcards: rep=66
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg
[Tue Jul  9 13:15:23 2024]
Finished job 67.
1 of 81 steps (1%) done
Select jobs to execute...
Execute 1 jobs...

[Tue Jul  9 13:15:23 2024]
localrule wait:
    output: output/26.txt
    log: logs/wait/26.log
    jobid: 27
    reason: Missing output files: output/26.txt
    wildcards: rep=26
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg
[Tue Jul  9 13:15:23 2024]
Finished job 16.
2 of 81 steps (2%) done
Select jobs to execute...
Execute 1 jobs...

[Tue Jul  9 13:15:23 2024]
localrule wait:
    output: output/39.txt
    log: logs/wait/39.log
    jobid: 40
    reason: Missing output files: output/39.txt
    wildcards: rep=39
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg
[Tue Jul  9 14:15:24 2024]
Finished job 27.
3 of 81 steps (4%) done
Select jobs to execute...
Execute 1 jobs...

[Tue Jul  9 14:15:24 2024]
localrule wait:
    output: output/41.txt
    log: logs/wait/41.log
    jobid: 42
    reason: Missing output files: output/41.txt
    wildcards: rep=41
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg
[Tue Jul  9 14:15:24 2024]
Finished job 40.
4 of 81 steps (5%) done
Select jobs to execute...
Execute 1 jobs...

[Tue Jul  9 14:15:24 2024]
localrule wait:
    output: output/56.txt
    log: logs/wait/56.log
    jobid: 57
    reason: Missing output files: output/56.txt
    wildcards: rep=56
    resources: tmpdir=/tmp

Activating singularity image /mnt/local_data/test_snakemake_interruption/exp2/rep1/url/.snakemake/singularity/2e5bd6a5c85d5bc8bd68ce85ad7310d4.simg
[Tue Jul  9 14:16:06 2024]
Error in rule wait:
    jobid: 42
    output: output/41.txt
    log: logs/wait/41.log (check log file(s) for error details)
    shell:

        sleep 3600s > output/41.txt 2>logs/wait/41.log
        echo "Done" >> output/41.txt 2>logs/wait/41.log

        (one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)

Removing output files of failed job wait since they might be corrupted:
output/41.txt
[Tue Jul  9 14:16:06 2024]
Error in rule wait:
    jobid: 57
    output: output/56.txt
    log: logs/wait/56.log (check log file(s) for error details)
    shell:

        sleep 3600s > output/56.txt 2>logs/wait/56.log
        echo "Done" >> output/56.txt 2>logs/wait/56.log

        (one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)

Removing output files of failed job wait since they might be corrupted:
output/56.txt
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: .snakemake/log/2024-07-09T121514.438965.snakemake.log
WorkflowError:
At least one job did not complete successfully.

Minimal example
reps=[i for i in range(80)]
rule all:
    input:
        expand("output/{rep}.txt", rep=reps)

rule wait:
    output:
        "output/{rep}.txt"
    threads: 1
    log: "logs/wait/{rep}.log"
    container:
        "docker://ubuntu:latest"
    shell:
        """
        sleep 3600s > {output} 2>{log}
        echo "Done" >> {output} 2>{log}
        """

Additional context
I run the workflow with:
nohup snakemake  --use-singularity --singularity-args '-B /mnt' --cores 2 >url/terminal_output.txt &
I run snakemake locally on an OpenStack VM running Ubuntu-22.04.
As part of investigating this bug I once had two instances of snakemake running in two separate folders. All jobs of both instances quit at the same moment. This is not always the case that all snakemake jobs quit at once. It seems to occur when both workflows are started at the same time.

The bug seems to be avoided if I do not use nohup ... & to launch snakemake in the background. If I instead run snakemake in a detached terminal with screen the issue seems to not occur.


Cannot control fire tv and see status changes

IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
<Unable to control Fire TV from the alexa_media_player device list, but all the echo devices can be controlled>
To Reproduce

Go to 'Integrations'
Click on 'Alexa Media Player.'
Click on 'devices'
Select any 'Fire TV device'.
In the Controls section, Fire TV status is shown as standby even though the TV is ON and doesn't change when you click on it.

Expected behavior
Fire TV status should be updated to reflect current status and should change when clicked on from Controls section
Screenshots
See attached image

System details

Home-assistant (version): 2023.8
alexa_media (version from const.py or HA startup): 4.6.5
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). <!---We will not debug login issues if unanswered--->: y

Logs
Please provide logs.
Additional context
Echo devices behave as expected. Only Fire TV couldn't be controlled.

Can you control it via the Alexa app?

I cannot use Fire TV as a trigger for my routines in the alexa app. But I was able to switch on/off fire tv based on some other triggers. So yes, I was able to control it.

Does it show up as a media player in the app with controls? I'm not talking about triggers. We can only emulate the app so if it's not supported in the app we can't do more.

Oh, now i understand. No, I don't see it as a media player.  For example, see if it's off/on? I only want to use the status of Fire tv as a trigger in my HA automations.

So yah, probably can't determine it's status. The status for the device comes from the media player which is whether it's playing etc. We may need to specifically exclude fire tv devices from populating the media player. I just don't recall if other functionality works for them like notifications. If they do get those, then perhaps we leave them in for those purposes. I'll leave this open as an enhancement request because maybe someone can find some other way the app reports the actual status and can do a PR, but otherwise I won't be doing anything else on it.

Same issue, can't control anything and the reporting is stuck.

@alandtse , Alright. Thanks for the quick response. I ended up using the Android debug bridge integration for getting the Fire TV status.

I'got the same issue. Can't control the Fire TV Stick via this integration. But with Android debug bridge it works.


Props get stuck somtimes

Sometimes, seemingly at random, props will get stuck and be unable to be grabbed or despawned by turning off the toggle. The only way to fix this is to reset the avatar. I'd give some more details if I could, but I can't seem to find any pattern to the issue occuring. I'll update this if I notice any patterns.

Definitely odd... could potentially be a low frame rate issue skipping over keys. If it happens again, I would look at the position of where the physbone is located and if its stretched at all. The off animation is supposed to act as a hard reset for anything that may have gone wrong but there may be something I overlooked.

I'll do some testing later and may actually just update some animations regardless to ensure that isn't the case because I felt like it may be slightly under what I needed it to be in order to work 100% of the time.

I think there's also a related bug where sometimes other people will see the prop stuck in place and not deactivating with the toggle, but the user of the avatar doesn't. Not sure if you can fix sync issues like that but I thought I'd bring it up.

I've found the issue and it is in fact frame rate dependent. I'm updating the package now. Thank you for bringing this up. The issue was what I mentioned above where keys were skipped and I was only able to reproduce at a less than 10 fps. Ill be making it less likely for this to occur and if it does happen to still occur after updating the package it should at least fix it self when turning the system on and off for sure. It will only require you to update the avatar prop logic layer if you update it.


add back nox

Adding back nox per https://github.com/iterative/dvclive/pull/749#issuecomment-1857226519. Looks like it was removed in https://github.com/iterative/dvclive/pull/527 without too much thought beyond one user running into an issue with it.

See https://github.com/iterative/dvclive/pull/756#issuecomment-1858793979 for why a test is failing - it's unrelated to this PR.


(maint) Add --trace option

Adds a --trace option that prints error backtraces.

CLA signed by all contributors.


Feature/test spec against generated

With this test, an open API spec will be generated, and some aspects are compared to our manual spec to ensure completeness.

this looks great. Let's talk about that git dependency tomorrow!


Added Single occurring element in an array by bitwise operation

Have you read the Contributing Guidelines on Pull Requests?
YES.
Description
Given an array of N elements, where each element occurs twice except one.
we can found that element with the help of Bitwise XOR operator.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
fixed #3815

@iamrajiv @ankitaggarwal23  kindly review

@iamrajiv @ankitaggarwal23 kindly review.

@iamrajiv  I guess , he is  busy. whom should I request  for review?

@iamrajiv  Thanks <3


Domain is not a valid unfurl domain claimed by your app

Description
Error: An API error occurred: invalid_blocks
    at platformErrorFromResult (/Users/kenshin/codes/lunapark/slack-demo/node_modules/@slack/web-api/dist/errors.js:51:33)
    at WebClient.apiCall (/Users/kenshin/codes/lunapark/slack-demo/node_modules/@slack/web-api/dist/WebClient.js:171:56)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async postRichContent (/Users/kenshin/codes/lunapark/slack-demo/index.js:38:5) {
  code: 'slack_webapi_platform_error',
  data: {
    ok: false,
    error: 'invalid_blocks',
    errors: [
      'Video validation failed: Domain is not a valid unfurl domain claimed by your app [json-pointer:/blocks/1]'
    ],
    response_metadata: {
      messages: [
        '[ERROR] Video validation failed: Domain is not a valid unfurl domain claimed by your app [json-pointer:/blocks/1]'
      ],
      scopes: [
        'app_mentions:read', 'channels:history',
        'groups:history',    'im:history',
        'mpim:history',      'channels:read',
        'groups:read',       'im:read',
        'mpim:read',         'users:read',
        'users:read.email',  'team:read',
        'im:write',          'chat:write',
        'channels:join',     'channels:manage',
        'chat:write.public', 'commands',
        'groups:write',      'mpim:write',
        'reactions:read',    'links.embed:write',
        'links:read',        'chat:write.customize'
      ],
      acceptedScopes: [ 'chat:write' ]
    }
  }
}

I have two apps (one for local testing & one for dev) and two testing workspaces (A and B). Both two apps have same domain list.
✅Send message to workspace A via local testing app
✅Send message to workspace B via local testing app
✅Send message to workspace A via dev app
❌Send message to workspace B via dev app
The fist three cases are working fine, but I keep get the error for the last case even if I confirmed,

The domain has been added to the unfurl domain list and it's valid.
The app has been installed to the workspace B. (I at least tried 10+ times)

Does anyone know the cause?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Hi @kenshin54 thank for writing in!
I would tend to say that this issue is environment related and not Bolt related, but would you be able to log the message request before it is sent to Slack and share it here?

here is the request,
{
  "channel": "MY_CHANNEL_ID",
  "text": "hello",
  "blocks": [
    {
      "type": "video",
      "video_url": "https://assets.gadder.live/videos/19325/6f00545907a44e47ae04e840f9632fe3_hd.mp4",
      "thumbnail_url": "https://assets.gadder.live/thumbnails/19325/6f00545907a44e47ae04e840f9632fe3.0000000.jpg",
      "alt_text": "big buck bunny",
      "title": {
        "type": "plain_text",
        "text": "big buck bunny"
      }
    }
  ]
}

This is a part of the app manifest (exclude some unrelated entries)
{
    "features": {
        "unfurl_domains": [
            "assets.gadder.live"
        ]
    },
    "oauth_config": {
        "scopes": {
            "bot": [
                "channels:join",
                "channels:manage",
                "channels:read",
                "channels:history",
                "chat:write",
                "chat:write.customize",
                "im:write",
                "im:history",
                "mpim:write",
                "mpim:history",
                "team:read",
                "users:read",
                "users:read.email",
                "links.embed:write",
                "links:read",
                "reactions:read",
                "groups:read",
                "mpim:read"
            ]
        }
    },
    "settings": {
        "event_subscriptions": {
            "bot_events": [
                "app_home_opened",
                "app_uninstalled",
                "link_shared",
                "member_joined_channel",
                "member_left_channel",
                "message.im",
                "user_profile_changed"
            ]
        }
    }
}

This is the app detail page,
Authorizations
...
Embed assets.gadder.live video player URLs in messages and app surfaces
View assets.gadder.live URLs in messages

I also tested it with raw HTTP request and I got the same error.
@WilliamBergamin You are right, this is not a problem of Bolt SDK. Is https://api.slack.com/support the right place to get the support?

I'm unable to reproduce this error on my local, Since the unfurl_domains in your manifest matches the one in your request and this works on other workspace and I'm unable to figure out what is wrong.
I feel like this is an environment Issue, reaching out to https://api.slack.com/support could allow you to rule out that this is a Slack issue.
It would be great if you could report back here once the issue is solved in order to provide a solution to anyone who encounters a similar problem

@WilliamBergamin I got the help from Slack support. Basically I have two apps installed in the same workspace, but two apps have the same unfurl domain registered. It seems only the first app installation is the one that will have these registered for it. That's why I got the error for the second app. I think the error message can be optimized to something like "This domain has been registered by another app", this will be much easier to catch the problem.
Anyway, thanks for the help. I will follow up with the support team and close this issue.


More details about the clip separation for training

Hi,
Recently I'm trying to repeat the training part of audio2feature, could u please share more details about the dataset construction, e.g., the duration of each clip, and the overlap of two clips?
Thanks and looking for your reply😊.
Yunfei

There're no overlaps between the two clips. I just use one clip for training. Check issue #27.

Thanks! This helps me a lot.

Hi, Recently I'm trying to repeat the training part of audio2feature, could u please share more details about the dataset construction, e.g., the duration of each clip, and the overlap of two clips?
Thanks and looking for your reply😊.
Yunfei

hello, 复现训练代码能分享下？


Impossible to separate the middleman?

I'm trying to fork a repo in a way which doesn't seem to be allowed.
What I did first which worked was fork a fork and adding both upstreams. However, only one branch of the first fork was relevent, and I would have rather had the rest be pure upstream. So I tried forking the upstream, then adding upstream as a remote, then adding the fork as another remote and only pulling the unique branch from the first fork. I get a
"remote: Permission to Fork1/program.git denied to Danfun64.
fatal: unable to access 'https://github.com/Fork1/program.git/': The requested URL returned error: 403"
error. Is there a way to make the way I'm trying to set things up (only use Fork1 for a branch upstream lacks)?

I think I see what I did wrong. I forgot to make a local version of the branch.


feat(client): adds HttpInfo to responses when HttpConnector is used

Adds client::connect::Connected::extra(), which allows connectors to
specify arbitrary custom information about a connected transport.

If a connector provides this extra value, it will be set in the
Response extensions.
Closes #1402

This is an alternative to #1592

Anything blocking this?

@sfackler I'd been waiting on the work in Linkerd to test it out before merging, in case there were any changes needed. It also allows for people to tell me it's a good or stupid idea :D

@seanmonstar how long do you think it'll be for this to steep? I want to take a crack at https://github.com/seanmonstar/warp/issues/9 which I believe is ultimately blocked on this.

This is a PR for the client, so I don't think it will help with that feature in warp...

Serves me right for the very quick search and glance...


Many any types in the FuseBox constructor options

Playing recently with Fusebox I encountered the problem with available types in the FuseBox constructor
Especially the sourceMaps part is at least confusing and I had to read a few tickets to get everything in my project working.
The proper type definitions may help people to work with this bundle meanwhile the any type steps us back to the normal JavaScript world.

Maybe it should be converted to vanilla JavaScript!

Yeah we have this problem, but we are solving it step by step. 1.4.1 has many fixes already

FuseBox v4 Major Upgrade
As of today, the latest major version of FuseBox v4 is available in fuse-box@next. FuseBox has undergone a full re-write from scratch, learning from its mistakes in the previous versions.
There are a lot of improvements, speed and config wise.
Get started here
We are still working on the documentation and polishing before the major release. We are getting very close. And we need help testing.
npm install fuse-box@next

Most of the issues that I am closing have been resolved, however, if you find that your issue is still relevant in v4 don't hesitate to re-open or (better) create a new one with v4 configuration.


[Error Analysis] Left alignment of all interpretML tabs

They are left-aligned. Please refer to the fluent style for the margin between tabs

fixed with PR https://github.com/microsoft/responsible-ai-widgets/pull/342


Add new CAI resources (compute)

CAI has announced these new resources, and these should be added to Forseti inventory.
compute.googleapis.com/GlobalForwardingRule | 4/22/2019
compute.googleapis.com/RegionBackendService | 4/22/2019

#2778 adds support for GlobalForwardingRule
#2791 adds support for RegionBackendService


Offer a bundled iOS 11 style large-title pull-to-refresh

iOS 11 has a pull-to-refresh between the persistent nav bar and its scrollable large title instead of below the nav bar in the scrollable list itself.
Offer a default built-in equivalent.

CupertinoRefreshControl reuses some of the subcomponents of BouncingScrollPhysics (to deal with snap back etc) which are not the default behavior on Android. If you want to pull them in, see the ScrollConfiguration widget.

Thank you for you reply. I will have a try.

We are investigating this as part of https://github.com/flutter/flutter/issues/124330 and see https://github.com/flutter/uxr/discussions/93


(packaging) Add beaker-abs dependency for CI

This adds a dependency on our beaker-abs hypervisor when running beaker
acceptance tests. This will cause the gem to be installed in production
CI pipelines (the gem has already been mirrored internally), but the gem
will not be used until we switch to CI.next.

current gem is mirrored here http://rubygems.delivery.puppetlabs.net/gems/beaker-abs-0.1.3.gem and released to rubygems.org too

:+1:

Sounds good, I'm excited for Facter to be one of the guinea pigs for this! 👍


⚠ GitLab Server has degraded performance

In f1b0155, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 13636 ms

Resolved: GitLab Server performance has improved in b468c21.


Add support for getting unsized CNG properties and make the property API more ergonomic

This PR enables us to fetch dynamically-sized properties such as strings or structs with VLAs/trailing bytes and introduces a safe way to inspect such data in a type-safe way via new TypedBlob struct.
This unblocks further work on ergonomically handling structs like BCRYPT_RSAKEY_BLOB or fetching string properties like BCRYPT_ALGORITHM_NAME.

@emgre do you have any opinions on this? Is this something you'd consider merging and have bandwidth to review?


Shuffle coalesce read supports split-and-retry

close #11584
This PR adds in the split-and-retry support when reading buffers from Shuffle for GpuShuffleCoalesceExec and sized hash joins.
When OOM happens, the retry will reduce the target size by half,  re-collect buffers from the cache with total size up to the new target batch size, then concatenate the collected buffers and move the concatenated result to GPU. Since the concatenated buffer can not be split, we have to re-collect the buffers and concatenate them again with this new smaller target size.
The new target size will be used by all the following read in this task. The more split-and-retry it gets, the smaller the target size will be.  This is just a choice. We prefer to believe that the GPU is busy with high memory pressure when getting an OOM. And more OOMs will possibly occur if using the original target batch size.
This PR also covers some code refactor in the shuffle hash join for the coming Kudo support. See https://github.com/NVIDIA/spark-rapids/issues/11590. It tries to move all the code pieces handling serialized tables into GpuShuffleCoalesceExec for esier code maintenance.

build

This is a lot of code, and I have not even really started to dig into it. I am concerned about how much is being changed here. From the description it looks like someone has misconfigured the target batch size, so this is going to try and adjust that target size, but just for shuffle coalesce? I am really confused about the goals of this and would like to see examples of when this helps and what the performance impact is to the happy path.

Yes, this only adjusts the target size only for shuffle coalesce. And the whole task will be affected only when no other operators will concatenate or split the batches for the output.
This is mainly to improve the stability. It can possibly get better performance only when the time cost of this split retry is lesss than a Spark task retry and the task retry can really happen without this change.
I rememer the target size was well tuned. Changing it will lead to longer operation time for some operators in the query. @winningsix  may know more context.


Add license declaration for this project

Please add the license declaration by either a explicit LICENSE file or a license section in the package.json.

fixed


Gitlab Enterprise documentation

Fleshes out Gitlab OAuth documentation

documents the Gitlab callback URL but also the various scopes that seem appropriate.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

I would appreciate confirmation that the scopes I've documented are all required. I'm not sure if they are all necessary. I have just begun experimenting with backstage and haven't done anything with git yet.