chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
d1bcbc8 -> c87742a

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.41.2 -> v1.41.3

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.41.3
Compare Source
Bug Fixes

deps: update gomod (#890) (ef2e183)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

4 additional dependencies were updated

Details:

Package
Change

github.com/IBM/platform-services-go-sdk
v0.70.0 -> v0.71.0

github.com/hashicorp/go-version
v1.6.0 -> v1.7.0

github.com/hashicorp/terraform-json
v0.22.1 -> v0.23.0

github.com/zclconf/go-cty
v1.14.4 -> v1.15.0

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

4 additional dependencies were updated

Details:

Package
Change

github.com/IBM/platform-services-go-sdk
v0.70.0 -> v0.71.0

github.com/hashicorp/go-version
v1.6.0 -> v1.7.0

github.com/hashicorp/terraform-json
v0.22.1 -> v0.23.0

github.com/zclconf/go-cty
v1.14.4 -> v1.15.0

/run pipeline

:tada: This PR is included in version 4.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unable to build production version

I am using version 0.40.2, After upgrading from version 0.38.2.
This is the error:
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@angular-mdc/web/app-bar' in 'XXX/node_modules/@angular-mdc/web/esm5'
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@angular-mdc/web/shape' in 'XXX/node_modules/@angular-mdc/web/esm5'
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@angular-mdc/web/theme' in 'XXX/node_modules/@angular-mdc/web/esm5'

@ofekashery Looks like you may need to manually remove node_modules folder, and re-run either npm i or yarn. Those 3 errors are folders that no longer exist.

Yep. It works


chore: replaces connection driver postgres with pgx

This patch replaces the connection driver postgres with pgx to avoid some of the limitations in the future that we encountered while developing #569.
Most of the code still relies on the simple protocol connection, further work will be needed to use the advanced protocol.
Closes #667
Signed-off-by: Armando Ruocco<EMAIL_ADDRESS>

/test

/test

/test

/test test_level=4

/test depth=main


Allow takeoffs to be aborted.

oh! could the "v status" replace knots on tag on takeoff? then we could see if it's too late to abort! once a craft hits, say..1000 ft then the knots would replace v staus.

Takeoffs can be aborted, yet I do like the V status. Opened a new issue (#268) for this and I think this one can be closed now, @zlsa


pods scheduled on different node cannot communicate with each other on kubernetes cluster using calico network

I am facing  this issue troubleshooting long time issue is  I have create Kubernetes cluster with calico network in my on premises server the **pods scheduled  on  different node on this Kubernetes cluster not able to communicate to each other **  . please chcek below scenarios.
There are two worker node server9 and server10
Two PODS are created on server 9 and  one pod created on server 10 as u can see below.
pods wit same node are bale to communicate with each other but pod on another node is not able to communicate with each other.
Can you please   help me to resolve this as there is no communication between this pods which is issue for application level cluster

/remove-kind bug
/kind support
This doesn't smell like a documentation issue. Please try other channels for tech support.

Please use https://github.com/kubernetes/kubernetes.
/close


Add sign_in_method Setting

Context
The sign in method is currently determined by two bools: use_dfe_sign_in and use_otp_sign_in to decide which buttons and routes to expose. This is confusing for development as there is a 3rd sign in persona which is exposed dependent on the use_dfe_sign_in bool.
Changes proposed in this pull request
Use a new setting sign_in_method to determine which buttons and routes to expose.
Guidance to review
make sure sign in works as expected using: otp, dfe and persona

 Define sign in method


Add initial action to create preview environments from PR builds

Add initial Action to create preview environments from PR builds. Note that these features are in internal/beta state at this stage, hence are not exposed in the public docs of this Action.
The PR adds a new preview/action.yml file with an input parameter preview-cmd, which can be used to define the build steps for the preview environment, using the value in AWS_ENDPOINT_URL as the target endpoint to deploy against.
Demo repo here: https://github.com/whummer/bref-localstack-sample/pull/3
See here for the deployment steps in the demo app: https://github.com/whummer/bref-localstack-sample/blob/main/.github/workflows/ci-preview.yml#L21-L33
Side note: Based on these changes, we can further iterate on the functionality, and further streamline this Action in the future. 👍 For example, the Start LocalStack build step is still the main step, but may not be required in all cases. See also the TODO comment in the main action.yml file in the repo
/cc @lukqw @HarshCasper

FYI - build error unrelated to this PR, currently being fixed in the context of https://github.com/localstack/localstack/issues/9253 👍


Paloalto fwaas integration

@ashutosh-mishra @njagadish ashutosh has reviewed this comments on different pull request and accepted this PR, had to create a new one because that branch was already merged. @njagadish can you review this pull request .

@njagadish what is the updated on merging this branch ??

@rayalaman - We are merging few changes now. I will let you know the branch into which this needs to be rebased after addressing the review comments.

Closing this as it is re-based to 03 June branch


Should featureName be in LayerFeature/PlotFeature interfaces?

It's not used now.

Could you please provide explanations for this issue?

Need to discuss if featureName  property is needed in LayerFeature/PlotFeature interfaces.


Add card item

Convert favorite button into a component to be reused

Codecov Report
Attention: Patch coverage is 0% with 119 lines in your changes missing coverage. Please review.

Project coverage is 1.53%. Comparing base (c787d49) to head (d7098c3).

Files with missing lines
Patch %
Lines

src/components/CardItem.tsx
0.00%
66 Missing and 1 partial :warning:

src/components/FavoriteFab.tsx
0.00%
30 Missing and 1 partial :warning:

src/components/SearchBar.tsx
0.00%
10 Missing :warning:

src/pages/SingleItem.tsx
0.00%
6 Missing :warning:

src/pages/Home.tsx
0.00%
4 Missing and 1 partial :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #11      +/-   ##
========================================
- Coverage   1.69%   1.53%   -0.17%
========================================
  Files         15      17       +2
  Lines        886     980      +94
  Branches      16      18       +2
========================================
  Hits          15      15
- Misses       857     949      +92
- Partials      14      16       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


nixos/k3s: start after network-online.target

nixos/k3s: start after network-online.target
Fixes #103158
Wants network.service does not exist:

Thought of network.target. But Arch Wiki says it is not necessary:

https://wiki.archlinux.org/title/Systemd#Targets

Will remove wants = [ "network.target" ] then.

Can this be backported to 22.11 as well?

Just add the tag and follow up on it...


added one logo and one animated logo

#56
Hey @avinashkranjan  I have added two logos in Friday/assets/icons/
Kindly, accept my pull request.

@avinashkranjan please review my pr

Do you have any other iterations for the Same. this does look app like icon
I didn't get it
can you please elaborate on what changes, I will design another?

@avinashkranjan
added some more logos (created other new pr for that)
in pr#100
please review and if required some other please let me know what changes you want I will make some more


[compiler] Implement compileCallExpression

Subject
compiler
Detail
Implement compileCallExpression() in translate/compiler.go.
If you meet call expression, push the next pc and compile call expression.

Some policy is changed!
If the heap tracer is implemented, I'll notify about this!


Contrast Tensor implementation on host and hip

Adds rpp support for contrast tensor on hip and host.
Support for U8/F32/F16/I8, NCHW/NHWC/toggle is added.
Adds corresponding unit tests and performance tests.

@r-abishek @paveltc Works only with this docker
docker pull abishekr/rocm4.5.2_ubuntu18.04_rpp_mivisionx:v0.1

On my dev system, with rocm 5.1 and opencv 4.5, imwrite fails
On the rocm5.1 you provided, it fails with
[3:00 PM] Ramasubramanian, Abishek
docker pull abishekr/rocm5.1_ubuntu18.04_rpp_mivisionx:v0.1.0
"hipErrorNoBinaryForGpu: Unable to find code object for all current devices!"

@r-abishek @rrawther I ran all of the tests and everything looks correct but there seems to be an extra test running for each collection of tests, contrast_u8_BatchPD. All the rest are labeled contrast_*_Tensor.
The BatchPD tests give different outputs than the Tensor ones, they all darken the image and seem to run some other augmentation.

@LakshmiKumar23 @rrawther @r-abishek I ran the unit tests on this PR using abishekr/rocm5.1.1_ubuntu18.04_opencv4.5.5_rpp_mivisionx:v0.1.0
Everything looks the same as with the previous run. As I understand it, the BatchPD is supposed to run for now.


🐞 Action not waiting until dependency is complete (in Github Actions)

What is the issue?
I have an action that builds a docker image and then one that pushes that image to AWS ECR. This works fine when I run this locally. This even works fine in a different Github Pipeline that I have. This isn't working when I setup an action that uses the install-only option. What seems to happen is the action that is pushing the image isn't waiting for the build step to complete, resulting in an error.
Log output
I turned on debug logging and have pasted some relevant info below. What I find interesting is that the dependency on the build step is recognized:
actions.deploy.push.ecr._push | dependency detected    dependency=actions.build._build

However, it seems to continue on anyway.
12:02AM INFO  actions.deploy.push.ecr._push | computing
12:02AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=actions.password.trim
12:02AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=client.env
12:02AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=actions.build._build
12:02AM DEBUG actions.deploy.push.ecr._push | add target credentials    target=632701593773.dkr.ecr.us-west-2.amazonaws.com
12:02AM DEBUG actions.deploy.push.ecr._push | export image    dest=632701593773.dkr.ecr.us-west-2.amazonaws.com/[project]-server:latest
12:02AM INFO  actions.build._build | #16 6.875
12:02AM INFO  actions.build._build | #16 6.875 33 packages are looking for funding
12:02AM INFO  actions.build._build | #16 6.875   run `npm fund` for details
12:02AM INFO  actions.build._build | #16 6.878
12:02AM INFO  actions.build._build | #16 6.878 found 0 vulnerabilities
12:02AM DEBUG actions.build._build | #16 DONE 6.9s
12:02AM DEBUG client.filesystem.".".read |
12:02AM DEBUG client.filesystem.".".read | #1 Local /home/runner/work/[project]/[project]
12:02AM DEBUG client.filesystem.".".read | #1 sha256:64cb5a46ba05438d800452909fd7086fe4ad782f00b337fcccd1d1e44149f2b6
12:02AM DEBUG client.filesystem.".".read | #1 transferring /home/runner/work/[project]/[project]: 1.51MB 0.2s done
12:02AM DEBUG client.filesystem.".".read | #1 DONE 0.2s
12:02AM DEBUG client.filesystem.".".read |
12:02AM DEBUG client.filesystem.".".read | #2 Local /home/runner/work/[project]/[project] [copy]
12:02AM DEBUG client.filesystem.".".read | #2 sha256:9500bb8befa94903b0bebff325e84090cac8e3b9f7c8556767a7d53e96a60967
12:02AM DEBUG client.filesystem.".".read | #2 DONE 0.2s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #7 [ 1/10] FROM docker.io/library/node:18-alpine@sha256:828424b660b8274e7dcf6c7447f014406610facf663f38df92c3162a3d29a1db
12:02AM DEBUG actions.build._build | #7 sha256:0f0400d1e280f0e4ecf72edb6f3ad29b04fd540e0bb6eaa68ec59afaa32c9d15
12:02AM DEBUG actions.build._build | #7 resolve docker.io/library/node:18-alpine@sha256:828424b660b8274e7dcf6c7447f014406610facf663f38df92c3162a3d29a1db 0.0s done
12:02AM DEBUG actions.build._build | #7 sha256:8d429ea46e68519681477903b59ecc86e81d89dc04db49144b15d6f451d83c75 450B / 450B 0.1s done
12:02AM DEBUG actions.build._build | #7 sha256:bb15f8897be610a73e89a8b77dc761efc8ff2c7da44e7b79d4a2d29bdc2c1f8f 2.35MB / 2.35MB 0.2s done
12:02AM DEBUG actions.build._build | #7 sha256:4cf055c4567149f7ce7599546e8e8b68ae6516da5e982a64aa304d91d5d88f07 46.35MB / 46.35MB 0.7s done
12:02AM DEBUG actions.build._build | #7 sha256:213ec9aee27d8be045c6a92b7eac22c9a64b44558193775a1a7f626352392b49 2.81MB / 2.81MB 0.2s done
12:02AM DEBUG actions.build._build | #7 extracting sha256:213ec9aee27d8be045c6a92b7eac22c9a64b44558193775a1a7f626352392b49 0.3s done
12:02AM DEBUG actions.build._build | #7 extracting sha256:4cf055c4567149f7ce7599546e8e8b68ae6516da5e982a64aa304d91d5d88f07 3.1s done
12:02AM DEBUG actions.build._build | #7 extracting sha256:bb15f8897be610a73e89a8b77dc761efc8ff2c7da44e7b79d4a2d29bdc2c1f8f 0.1s done
12:02AM DEBUG actions.build._build | #7 extracting sha256:8d429ea46e68519681477903b59ecc86e81d89dc04db49144b15d6f451d83c75 0.0s done
12:02AM DEBUG actions.build._build | #7 DONE 0.0s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #8 [ 2/10] RUN mkdir -p /usr/src/app
12:02AM DEBUG actions.build._build | #8 sha256:4aa30b924e0e37884771caf3892afc67f3da30ed82df652baf87e75de3c6816e
12:02AM DEBUG actions.build._build | #8 DONE 2.6s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #9 [ 3/10] WORKDIR /usr/src/app
12:02AM DEBUG actions.build._build | #9 sha256:1999039f25e5b0c813d6907c8217a74b53317049a88d43e7c0f1fd5720ad4289
12:02AM DEBUG actions.build._build | #9 DONE 0.1s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #10 [ 4/10] COPY package.json package.json
12:02AM DEBUG actions.build._build | #10 sha256:14c3ad925563611fb5c44173d2868355b1b4be8ff667281d934189e4a532ee6a
12:02AM DEBUG actions.build._build | #10 DONE 0.0s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #11 [ 5/10] COPY package-lock.json package-lock.json
12:02AM DEBUG actions.build._build | #11 sha256:7e0e8e1f8d47395614a8d114067cb5cfce7cbba080696160058b12751b992dcf
12:02AM DEBUG actions.build._build | #11 DONE 0.0s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #12 [ 6/10] COPY apps/server apps/server
12:02AM DEBUG actions.build._build | #12 sha256:5032adce0fe7555b1a1c22f9444caa001e3f301391849b596e0113bd4661ed4f
12:02AM DEBUG actions.build._build | #12 DONE 0.0s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #13 [ 7/10] COPY packages packages
12:02AM DEBUG actions.build._build | #13 sha256:929dbe7e69d4e8338b15b17e2ad88cb9c2d19f674addd567bd815d90ce319f3d
12:02AM DEBUG actions.build._build | #13 DONE 0.0s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #14 [ 8/10] RUN npm install --omit=optional
12:02AM DEBUG actions.build._build | #14 sha256:319126e6ebfde6802f5b0d1e0f63ec5f813630ef15f3087ae9e6e4e80de1bf49
12:02AM DEBUG actions.build._build | #14 DONE 57.7s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #15 [ 9/10] RUN npm run build -w @[org]/[project]-server
12:02AM DEBUG actions.build._build | #15 sha256:53c7e0bdce5e4f26b61b2925dd6ab60ea2db3b12437e6743e46b2b640955f361
12:02AM DEBUG actions.build._build | #15 DONE 34.8s
12:02AM DEBUG actions.build._build |
12:02AM DEBUG actions.build._build | #16 [10/10] RUN npm prune --omit dev --workspaces
12:02AM DEBUG actions.build._build | #16 sha256:1e6696c02b36f39b0ada36ee8cba58f1f1a991220cd0ea95b63666ef46fd361c
12:02AM DEBUG actions.build._build | #16 DONE 6.9s
12:02AM DEBUG system |
12:02AM DEBUG system | #22 exporting to image
12:02AM DEBUG system | #22 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
12:02AM DEBUG system | #22 exporting layers
12:02AM DEBUG system | #22 exporting layers 20.6s done
12:02AM DEBUG system | #22 exporting manifest sha256:d2468313f6331f1f5c9d63cd935983e876cc21bc50d0785c9e048dcb67d458fe done
12:02AM DEBUG system | #22 exporting config sha256:382d0c814dc9c11ec9b26bb3e716785db2d47ae3c6f36f86261dbb1588b65d6f done
12:02AM DEBUG system | #22 pushing layers
12:03AM DEBUG system | #22 pushing layers 8.0s done
12:03AM ERROR actions.deploy.push.ecr._push | failed: failed to solve: failed to do request: Post "https://632701593773.dkr.ecr.us-west-2.amazonaws.com/v2/[project]-server/blobs/uploads/": EOF
    duration=28.7s
12:03AM DEBUG system | #22 ERROR: failed to do request: Post "https://632701593773.dkr.ecr.***.amazonaws.com/v2/[project]-server/blobs/uploads/": EOF
12:03AM DEBUG system | ------
12:03AM DEBUG system | > exporting to image:
12:03AM DEBUG system | ------
12:03AM FATAL system | failed to execute plan: task failed: actions.deploy.push.ecr._push: failed to do request: Post "https://632701593773.dkr.ecr.us-west-2.amazonaws.com/v2/[project]-server/blobs/uploads/": EOF

Steps to reproduce
I don't know that I can create a simple reproducible example, honestly. My complete CUE file and github workflow are below
package [project]

import (
    "dagger.io/dagger"
    "dagger.io/dagger/core"
    "universe.dagger.io/aws"
    "universe.dagger.io/docker"
)

dagger.#Plan & {
    client: {
        env: {
            AWS_ACCESS_KEY_ID?: dagger.#Secret
            AWS_SECRET_ACCESS_KEY?: dagger.#Secret
            AWS_REGION?: dagger.#Secret
            ECS_CLUSTER: string | *""
            ECS_SERVICE: string | *""
            ECR_REPO: string | *""
            IMAGE_NAME: string | *""
            NODE_AUTH_TOKEN?: dagger.#Secret
            BUILD_VERSION: string | *""
        }
        filesystem: ".": read: {
            contents: dagger.#FS
            exclude: [
                "**/node_modules",
                "**/dist",
                "**/.vscode",
                "**/test",
                "cue.mod",
                ".git",
                ".github",
                "*.cue",
                "**/.DS_Store"
            ]
        }
    }

    actions: {
        // Build a docker image with aws cli preinstalled
        prepare: aws.#Build

        // Get a temporary password for the ecr registry
        password: {
            get: aws.#Container & {
                input: prepare.output
                credentials: aws.#Credentials & {
                    accessKeyId: client.env.AWS_ACCESS_KEY_ID
                    secretAccessKey: client.env.AWS_SECRET_ACCESS_KEY
                }
                env: {
                    AWS_REGION: client.env.AWS_REGION
                }
                command: {
                    name: "sh"
                    flags: "-c": "aws ecr get-login-password --region $AWS_REGION >> /output.txt"
                }
            }
            read: core.#NewSecret & {
                input: get.output.rootfs
                path: "/output.txt"
            }
            trim: core.#TrimSecret & {
                input: read.output
            }
            result: trim.output
        }
        // Build the server docker image
        build: docker.#Dockerfile & {
            source: client.filesystem.".".read.contents
            dockerfile: path: "./apps/server/Dockerfile"
            platforms: [ "linux/amd64" ]
        }
        deploy: {
            // Push the new image to ECR
            push: {
                ecr: docker.#Push & {
                    image: build.output
                    dest: "\(client.env.ECR_REPO)/\(client.env.IMAGE_NAME):latest"
                    auth: {
                        username: "AWS"
                        secret: password.result
                    }
                }
                output: prepare.output
            }
            // Force the ECS service to use the new image
            update: aws.#Container & {
                input: push.output
                credentials: aws.#Credentials & {
                    accessKeyId: client.env.AWS_ACCESS_KEY_ID
                    secretAccessKey: client.env.AWS_SECRET_ACCESS_KEY
                }
                env: {
                    AWS_REGION: client.env.AWS_REGION
                    ECS_CLUSTER: client.env.ECS_CLUSTER
                    ECS_SERVICE: client.env.ECS_SERVICE
                }
                command: {
                    name: "sh"
                    flags: "-c": "aws ecs update-service --cluster $ECS_CLUSTER --service $ECS_SERVICE --force-new-deployment"
                }
            }
        }
        publish: {
            // Push with version tag
            version: docker.#Push & {
                image: build.output
                dest: "ghcr.io/[org]/" + client.env.IMAGE_NAME + ":" + client.env.BUILD_VERSION
                auth: {
                    username: "USERNAME"
                    secret: client.env.NODE_AUTH_TOKEN
                }
            }
            // Push with latest tag
            latest: docker.#Push & {
                image: build.output
                dest: "ghcr.io/[org]/" + client.env.IMAGE_NAME + ":latest"
                auth: {
                    username: "USERNAME"
                    secret: client.env.NODE_AUTH_TOKEN
                }
            }
        }
    }
}

name: Update QA

# This is triggered manually
on:
  workflow_dispatch:

jobs:
  release:
    runs-on: ubuntu-latest
    env:
      # Removed
    defaults:
      run:
        working-directory: ./
    permissions:
      contents: read
      packages: write
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: Install dagger
        uses: dagger/dagger-for-github@v3
        with:
          install-only: true
          version: 0.2.35
      - name: Update Version
        run: |
            dagger project update
            dagger do push -p dagger/update-version.cue
            git pull
        env:
          # Removed
      - name: Deploy Server
        run: |
            export BUILD_VERSION=$(cat VERSION)
            dagger do deploy -p dagger/server.cue
        env:
          # Removed

Dagger version
0.2.35
OS version
Github Actions

I kept messing with this some more and ruled out that install-only in the Github workflow was the issue.
Turning on debug locally, I see almost the same logging I posted above. However, I don't see the build action logs mingled in with the push logs at the end:
11:52AM INFO  actions.deploy.push.ecr._push | computing
11:52AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=actions.password.trim
11:52AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=client.env
11:52AM DEBUG actions.deploy.push.ecr._push | dependency detected    dependency=actions.build._build
11:52AM DEBUG actions.deploy.push.ecr._push | add target credentials    target=632701593773.dkr.ecr.us-west-2.amazonaws.com
11:52AM DEBUG actions.deploy.push.ecr._push | export image    dest=632701593773.dkr.ecr.us-west-2.amazonaws.com/tf-[project]-qa:latest
11:52AM INFO  actions.build._build | #18 22.16
11:52AM INFO  actions.build._build | #18 22.16 33 packages are looking for funding
11:52AM INFO  actions.build._build | #18 22.16   run `npm fund` for details
11:52AM INFO  actions.build._build | #18 22.17
11:52AM INFO  actions.build._build | #18 22.17 found 0 vulnerabilities
11:52AM DEBUG actions.build._build | #18 DONE 22.3s
11:52AM DEBUG client.filesystem.".".read |
11:52AM DEBUG client.filesystem.".".read | #4 Local /Users/noahtroncoso/projects/work/[project]
11:52AM DEBUG client.filesystem.".".read | #4 sha256:84b8c13ccf93d1f65b8304730a6435b9a7344339a124144e109c6c5ae3d86ea8
11:52AM DEBUG client.filesystem.".".read | #4 transferring /Users/noahtroncoso/projects/work/[project]: 39.18kB 0.0s done
11:52AM DEBUG client.filesystem.".".read | #4 DONE 0.1s
11:52AM DEBUG client.filesystem.".".read |
11:52AM DEBUG client.filesystem.".".read | #5 Local /Users/noahtroncoso/projects/work/[project] [copy]
11:52AM DEBUG client.filesystem.".".read | #5 sha256:0f76a11f21ba049b0958d2affa9646ccad93e48ff90d79785baf9011d45f10cb
11:52AM DEBUG client.filesystem.".".read | #5 DONE 0.3s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #9 [ 1/10] FROM docker.io/library/node:18-alpine@sha256:828424b660b8274e7dcf6c7447f014406610facf663f38df92c3162a3d29a1db
11:52AM DEBUG actions.build._build | #9 sha256:0f0400d1e280f0e4ecf72edb6f3ad29b04fd540e0bb6eaa68ec59afaa32c9d15
11:52AM DEBUG actions.build._build | #9 resolve docker.io/library/node:18-alpine@sha256:828424b660b8274e7dcf6c7447f014406610facf663f38df92c3162a3d29a1db 0.0s done
11:52AM DEBUG actions.build._build | #9 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #10 [ 2/10] RUN mkdir -p /usr/src/app
11:52AM DEBUG actions.build._build | #10 sha256:4aa30b924e0e37884771caf3892afc67f3da30ed82df652baf87e75de3c6816e
11:52AM DEBUG actions.build._build | #10 DONE 0.2s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #11 [ 3/10] WORKDIR /usr/src/app
11:52AM DEBUG actions.build._build | #11 sha256:1999039f25e5b0c813d6907c8217a74b53317049a88d43e7c0f1fd5720ad4289
11:52AM DEBUG actions.build._build | #11 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #12 [ 4/10] COPY package.json package.json
11:52AM DEBUG actions.build._build | #12 sha256:26a9396e4a2ef675ea9ab17aaf09a4872cf576bd14aa10a89011f571280f5532
11:52AM DEBUG actions.build._build | #12 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #13 [ 5/10] COPY package-lock.json package-lock.json
11:52AM DEBUG actions.build._build | #13 sha256:24442879a04cf02f2e666e2ae3adbc91e6af2c26e83908484dcfce05ef12e0d1
11:52AM DEBUG actions.build._build | #13 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #14 [ 6/10] COPY apps/server apps/server
11:52AM DEBUG actions.build._build | #14 sha256:d54a0243331050a99e3631577dc1e328f2b3786af306f73ab48eddcd13e6e9e7
11:52AM DEBUG actions.build._build | #14 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #15 [ 7/10] COPY packages packages
11:52AM DEBUG actions.build._build | #15 sha256:017e50bebfb0cfc6e38bcff447159c491051bf3ebff3bb5829001dd1733973b7
11:52AM DEBUG actions.build._build | #15 DONE 0.0s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #16 [ 8/10] RUN npm install --omit=optional
11:52AM DEBUG actions.build._build | #16 sha256:3a69a6ee48a37f4714c7c14e9c9c3425c02656ba9b68a79e5b3033c09948c7be
11:52AM DEBUG actions.build._build | #16 DONE 159.7s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #17 [ 9/10] RUN npm run build -w @[org]/[project]-server
11:52AM DEBUG actions.build._build | #17 sha256:b919a81833d5c80b2267b89237a63f156d12ba7a8628e15dfdddba37e92c9764
11:52AM DEBUG actions.build._build | #17 DONE 116.3s
11:52AM DEBUG actions.build._build |
11:52AM DEBUG actions.build._build | #18 [10/10] RUN npm prune --omit dev --workspaces
11:52AM DEBUG actions.build._build | #18 sha256:d5d935e4aa9da513f5b9deef37cc57798de8eeffc4e4ae67d06eee44ab53cee4
11:52AM DEBUG actions.build._build | #18 DONE 22.3s
11:52AM DEBUG system |
11:52AM DEBUG system | #22 exporting to image
11:52AM DEBUG system | #22 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00
11:52AM DEBUG system | #22 exporting layers
11:52AM DEBUG system | #22 exporting layers 9.8s done
11:52AM DEBUG system | #22 exporting manifest sha256:47aa9bc657e6f143da21962d8acdbbe8341f063c3456c8c3fd3811297d06fd34 done
11:52AM DEBUG system | #22 exporting config sha256:124b621589fce9f4680f73b7fa2590039daa15102ff936f43efe0b6e03861ee7 done
11:52AM DEBUG system | #22 pushing layers
11:52AM DEBUG system | #22 pushing layers 8.1s done
11:52AM DEBUG system | #22 pushing manifest for<PHONE_NUMBER>73.dkr.ecr.***.amazonaws.com/tf-[project]-qa:latest@sha256:47aa9bc657e6f143da21962d8acdbbe8341f063c3456c8c3fd3811297d06fd34
11:52AM DEBUG system | #22 pushing manifest for<PHONE_NUMBER>73.dkr.ecr.***.amazonaws.com/tf-[project]-qa:latest@sha256:47aa9bc657e6f143da21962d8acdbbe8341f063c3456c8c3fd3811297d06fd34 0.5s done
11:52AM INFO  actions.deploy.push.ecr._push | completed    duration=18.5s
11:52AM DEBUG actions.deploy.push.ecr._push | merging task result    result={

More notes: It looks like locally I was using version 0.2.28. After updating it to 0.2.36, this error occurs locally, too. So something seems to have happened between those 2 versions. It's kind of hard to navigate the "changelogs" because they are literally just a git diff between versions. Is there a proper changelog anywhere that lists issues fixed?

Nevermind... the error "EOF" made it seem like it was trying to upload the image before it was done building. The actual issue was just using the wrong image name altogether. In the original logging, it tried to push to https://632701593773.dkr.ecr.***.amazonaws.com/v2/[project]-server, which doesn't exist


update the mm dump relative, add orphan & biggest dump feature.

Summary
As we add lot of feature in the memory dump, the help prompt is not  exactly same as expected.
It make confuze to user when use memdump help, also make it difficult to add more feature here.
Make a patch in memdump help prompt work as expect.
Then add two feature in memdump

dump the orphan nodes(neighbor of free node) ,to help locate the memory nodes who more possible case the memory fragments.
dump the biggest nodes in already allocated nodes. to help locate the problem who used too much memory.

Impact
The usage no difference, and no compatible issues.
The macro more compatible with different kind of defconfig.
The memdump help more clear, and if not able to use, do not show help prompt..
Testing
CI-test & qemu-armv8a & cortex-a7 smp board.

[Experimental Bot, please feedback here]
The PR summary is missing some key information:

What functional part of the code is being changed?  Be specific.  E.g., "The memdump command within the NuttX kernel", or even better, a link to the specific code section.
How does the change exactly work? Briefly explain the technical approach to fixing the help prompt and adding the new features.

The Impact section is vague:

Is new feature added?  You say "add two features" - explicitly state this is YES.
Impact on user: While usage may not differ significantly, new features always have an impact.  Describe the new commands users can now use.
Impact on documentation:  New features require documentation updates. State YES and briefly describe what needs updating.

The Testing section is insufficient:

Build Host(s): Be specific about your development environment.
Target(s):  "qemu-armv8a & cortex-a7 smp board" is not enough detail.  Provide the exact board configurations used.
  Include actual log snippets demonstrating the issue before and the improvement after your changes.

In conclusion, this PR does NOT meet NuttX requirements in its current form.  You need to provide more specific and detailed information in all sections for it to be considered.


Datrie causing installation failures

When running pip3 install snakemake using python3.7 or python3.8, the installation fails with an error relating to datrie.
This is not a bug with snakemake, but a known issue with datrie. There is a PR currently open which solves this problem, but until it is merged, the following solutions should work.
A previous issue on bitbucket has dealt with this for python3.7.
https://github.com/snakemake/snakemake/issues/130 may be caused by the same problem, although the log in that error does not seem to mention datrie.
Workaround
Python3.7
pip3 install git+https://github.com/pytries/datrie.git
pip3 install snakemake

Python3.8
pip3 install<EMAIL_ADDRESS>pip3 install snakemake

EDIT: https://github.com/pytries/datrie/pull/78 seems to supersede the Python3.8 branch above.
Python3.8
pip3 install<EMAIL_ADDRESS>pip3 install snakemake

This is really a pity. Any suggestion for a stable package we could use instead?

Yeah, it is unfortunate. I do feel sorry for the maintainers though, they're getting some very unwarranted abuse.
The only other thing I could find that seems to be maintained is https://github.com/mina86/pygtrie which is a fork of Google's repo. They're pushing to the pypi releases, but I'm not sure if it is comparable to datrie.

datrie 0.8.2 should support py38 and was just pushed to pypi.

they're getting some very unwarranted abuse.

I agree and left comments to that effect.

Thanks a lot to everybody looking into this!


added mofdscribe

Love the repo!
I added mofdscribe which makes it really easy to use RASPA and Zeo++ for MOFs (also lots of other features).
Hopefully this section works!

Hi @FMcil, thanks for the suggestion, it is appreciated.
Nevertheless, my feeling is that it doesn't mesh fully with the aim of this list, sorption. It is more related to structure featurization rather than generating, fitting and further processing sorption data.


Added Toleration mechanism for worker node taint

Zun now takes a worker node taint into its conf and will proceed to set a toleration for it in k8s deployments. The worker node taint to be tolerated should be specified in CONF in the following format: worker_node_taint: "worker-node=true:NoSchedule"

 When deploying K3S. taint device nodes to only tolerate non-control plane services and add tolerations for device plugins and other device specifics.


Can we add configuration of r.Shadow.Virtual.Enable=1?

There's a community shadow fix to use the UE5 Virtual Shadowmap instead of the in-game shabby shadow maps.
Another great fix BMWK - SPF is incompatible with engine.ini tweaks but is compatible with your work.
Could you consider adding an option to adjust the 'r.Shadow.Virtual.Enable' setting to benefit from yours and the mods mentioned above?

Added in v0.8.2


Water Audio is a bit quiet?

It doesn't feel "sloshy" if that makes sense? wading through it, the sound is nice, but for jumping in it feels odd.
More an observation than anything else.

Hi RosinRush!
The water audio being quiet is a creative choice I made while working out the kinks in the water. It seemed that the noise the water made was obtrusively loud and needed to be turned down a bit. That being said, I will test a few different audio levels and make sure that the current level is/n't the best audio for it and adjust as needed.
Thank you,
Drako

Sounds good!

Fixed on release of v1.0.7


Revert the Travis workaround.

The issue has been fixed.
DO NOT MERGE
@Johann-S Please approve and I'll rebase to see when this passes again.

OK, so it seems they indeed fixed the issue.


0.73: Allow fractional zoom stopping with Map.TouchZoom and fix CRS.scale calc with fractional zoom

Hi.
I believe that I have found a fix to allow touch/pinch fractional zoom support (when using plain Leaflet object and or GeoJson objects). But I could not comment as to if this will break any map with tiles. We currently don't use tiles, so I don't have expertise.
This Pull is for stable (sorry if this is the wrong destination), I will create a second for master https://github.com/Leaflet/Leaflet/pull/3326 (as the code is different). I believe work has been done in master for version 1.0 to support better zooming so if this Pull is ignored in favour of the master pull then at least this code might serve as a reference for others using 0.7.
The underlying issue being solved is the "jump" in the map when stopping a touch/pinch zoom whilst the map snaps to a whole number zoom level. Our users on iPad's and Android were finding this very obvious and it was very hard for them to zoom in/out to the level of detail that they wanted.
Changes to Map.TouchZoom support stopping the zoom level exactly where the user has stopped the pinch.
The secondary issue uncovered is that the built in CRS.scale calculation also does not support fractional zoom. The side-affect of this is that when touch/pinch zooming, the percent with which the map is grown or shrunk does not reflect the final size that the map will be drawn at. Thus this means that there is still a "jump" in the map when stopping a touch/pinch zoom, even with the first fix in place.
The commit to CRS.js supports Scale calculation for fractional zoom levels.
Please refer to these related issues:
https://github.com/kartena/Proj4Leaflet/issues/57
https://github.com/kartena/Proj4Leaflet/pull/73
https://github.com/Leaflet/Leaflet/issues/426
https://github.com/Leaflet/Leaflet/pull/1309
http://stackoverflow.com/questions/24151177/fractional-zoom-levels
https://github.com/Leaflet/Leaflet/pull/2382
https://github.com/Leaflet/Leaflet/issues/2558

This will break a lot of apps, especially ones that use tiles (which is 99% of Leaflet apps). So I don't want to merge it into stable — lets continue discussion on the master changes.


Support of Detectron2 models

For now Detectron2 models don't work out of the box because of the different input format.
It would be nice to have an example on how to fix that.
Thanks!

Hello @justlike-prog!
I gave a look at the Detectron2 source code and I found an easy way to implement a workaround for optimizing it. In Detectron2 the whole computation is made by the Resnet-based backbone, so we can simply optimize the backbone for already getting good results.
The problem was that the backbone gives as output a dictionary and we need to map it to a tuple for being consistent with the Nebullvm API. I suggest defining two "wrapper" classes (one for the non-optimized and one for the optimized model) and then using them for running the Detectron2 optimized model.
Let's define the classes as
class BaseModelWrapper(torch.nn.Module):
    def __init__(self, core_model, output_dict):
        super().__init__()
        self.core_model = core_model
        self.output_names = [key for key in output_dict.keys()]

    def forward(self, *args, **kwargs):
        res = self.core_model(*args, **kwargs)
        return tuple(res[key] for key in self.output_names)

class OptimizedWrapper(torch.nn.Module):
    def __init__(self, optimized_model, output_keys):
        super().__init__()
        self.optimized_model = optimized_model
        self.output_keys = output_keys

    def forward(self, *args):
        res = self.optimized_model(*args)
        return {key: value for key, value in zip(self.output_keys, res)}

Then you can simply run the following code
import copy
from detectron2 import model_zoo
from nebullvm import optimize_torch_model

config_path = "COCO-InstanceSegmentation/mask_rcnn_R_50_FPN_3x.yaml"
model = model_zoo.get(config_path, trained=True)
model.eval()
model_backbone = copy.deepcopy(model.backbone)
res = model_backbone(torch.randn(1, 3, 256, 256))  # needed for getting the output_keys
backbone_wrapper = BaseModelWrapper(model_backbone, res)
optimized_model = optimize_torch_model(backbone_wrapper, batch_size=1, input_sizes=[(3, 256, 256)], save_dir="./")
optimized_backbone = OptimizedWrapper(optimized_model, backbone_wrapper.output_names)
# finally replace the old backbone with the optimised one
model.backbone = optimized_backbone

If you need dynamic input shapes you'd need to add a few more arguments to the optimize_torch_model function. Please give a look at issue #26 for further info.


Incompatibility with React 16.3.0 and up

Invariant Violation: Element ref was specified as a string (kronos) but no owner was set.
When react-dom and react are past version 16.2.0, this package breaks. I believe this error is in reference to line 49 of src/styled-component.js. According the documentation, you can not use refs on function components. In version 16.3.0, a couple of new APIs handling this were introduced so I believe the error was just suppressed until then.
I imagine it's pretty simple to fix this and update the package - until then, react-kronos doesn't work with any version of react or react-dom past 16.2.0.

@xenophilicibex Hey there! I just wanted to check in and see if this is still being updated?

Updated!


Upgrade to terraform-redhat/rhcs 1.6.0

@ahus1 I messed up the .gitignore  on the initial PR, so the *.hcl files weren't included as I thought. This PR addresses that and also upgrades the rhcs provider to the final 1.6.0 version.
Workflow run: https://github.com/ryanemerson/keycloak-benchmark/actions/runs/8540043303

Thank you for this update!


TP profile name not accepting dot (.)

When we name a new profile in TP, it's not accepting dot (.) which is useful to manage versions.
Example, 7.41.0 and 7.4.1 written as 741 can be differentiated better with decimal or dot.

CDN-3151

@tyagian - seems fine


there is a grey line in csv data window where the window normally ends (platform or ERC issue)

It was a mistake on the platform. This was fixed.


[CAP-223] Update to use the new properties pattern defined in uPortal 5.

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change
Update properties to use the new pattern defined for uPortal 5.
https://issues.jasig.org/browse/NOTIFPLT-86

LGTM too :+1:


Releases shall contain amd64 binaries at least for Dockerfile

In order to make sure that the Dockerfile can actually be made based on your release lifecycle, I need that you actually build up the binary and attach them to the releases ( either also as .tar.gz or direct binaries ) so I could update then the Dockerfile.
Ping me back when you started to do that. For eg. see https://github.com/bcicen/ctop/releases

Can it be directly from goaccess' download page? Right now you can find the tar.gz from  github's releases page, but I'd prefer if it's directly from goaccess' site.

Sorry, I forgot about it :) I'll try to take a look later then. Thank you!

@allinurl I had a chance to see your download page but you're just giving away the source code to be built, where I am talking about an already built binary. This is neither available on your website ( versioned if possible ), neither from the releases page here.
Any idea when one of the two will be available?

@julianxhokaxhiu, thanks for looking into this. I'm curious why #311 used v1.1.1, it seems Alpine has v1.2 already, shouldn't that solve the issue in 311?

It may be that the docker was built before Alpine having the package updated.
Check the docker logs on Docker hub, otherwise just retrigger another build, ai'm pretty sure it will be solved automatically :)

Checking at the Docker status page, of your latest build, it seems that Alpine is still loading 1.1.1 version. I highly suggest to start releasing binaries ( at least amd64 ) in order to include them in your Docker, so you can align releases with Docker instances.

I can certainly start releasing binaries, but before doing (and to avoid having an extra layer of stuff to maintain), I wondering if it's possible to use the official goaccess' repo and extract the binaries from there? Not sure, but logstash appears to be using their own repo?

Well I have to be honest: we could use even the source to run it like in interpretation way, but I think to make the docker smaller we could also go for just including the binary without even using any base go docker image.
We are talking about a couple of MB ( or even less ) vs about 20MB between toolchain, basic distro packages, etc. which in the end will not also provide a fully performance enhanced binary.
Also, the interpretation way should just be used for development and not production. You source package delivered through the website is just the source code, not the binary output of it.
How much overhead would this add to you? We can also think about using travis to do this for you, and letting him trigger the docker hub repository for doing the build on top of the binary.
Really long shot, but it's fully automated.

Thanks. I'll add the binaries over the weekend. Would it work to have them under https://goaccess.io?

Sure, would be even better! Ping me when it's done :)

Binaries can be found here. Let me know if that works. Thanks!

Is the url still working? I've tried to access it now, and it seems it doesn't work.

It's no longer active. Since Alpine now uses v1.2 (edge), then I don't think we need the binaries anymore, but thanks for all the work though :)

Fine then :D If you think we need to improve the Docker then, feel free to reopen this issue :)
Best regards!


Legion Prof throws away information about multiple points in a single region

The Python implementation of Legion Prof seems to blindly overwrite the index space bounds information when a region contains multiple points (or rects):
https://github.com/StanfordLegion/legion/blob/d47b4fa50bd2cf7c8673c338e86ee6797e714d22/tools/legion_prof.py#L2925-L2926
If you look at what this does on tests like tests/regent/run_pass/region_partition_by_preimage_multiregion.rg, it seems clear to me that this is throwing away information in cases where the region does not consist of a single dense rectangle/point.
Not an issue for Rust yet, but will be since I need to match Python's behavior.

Digging into this further showed that we were getting the following logger messages (on the relevant index space):
record IndexSpacePointDesc { ispace_id: ISpaceID(8), dim: 1, rem: Point([0, 0, 0]) }
record IndexSpacePointDesc { ispace_id: ISpaceID(8), dim: 1, rem: Point([2, 0, 0]) }
record IndexSpaceSizeDesc { ispace_id: ISpaceID(8), dense_size: 3, sparse_size: 2, is_sparse: true }

This is a sparse instance. We see it's correctly tracked as such in the logs. Right now, detailed bounds information doesn't make it into the profiler output anyway, so this is a bit of a moot point.
I'll document this in the Rust code and plan to leave it as-is.


link goes down

in doc "addon"
Community training projects
Chinese simplefied: see issue 296; download http://ubuntuone.com/p/3Yw/

fixed (moved because of broken link)


Fix a mistake in the documentation

I'm not 100% certain about this, so this PR is also a request for clarification.

You are absolutely correct !
Thanks !


do peg-in in two steps and add some helper fns

added a few helper functions which can be used in the future.
fixed a small bug in the sat to btc calculation (amounts > 100.000.000 sat would not work because there is a 0 in front of it)
provide a quick way to peg-in manually (or do whatever with the TXOUTPROOF and TRANSACTION)

I just noticed I cant use it in my clientd-tests.sh (without weired workourounds) because pegin.sh uses the other client and they cant run at the same time (DB access). So if you think this is still useful for later I'll leave the PR open but can just close it too..

I'm not sure I fully understand what this is doing. Maybe having a separate script/shell function that just gives you the proof and transaction and another that uses these to do the peg-in would be more useful? As it is the peg-in happens and then you get the exported proof+tx, idk how that would help?

I'm not sure I fully understand what this is doing. Maybe having a separate script/shell function that just gives you the proof and transaction and another that uses these to do the peg-in would be more useful? As it is the peg-in happens and then you get the exported proof+tx, idk how that would help?

if you set the -e flag it dosn't peg-in but only exports the txoutproof, transaction. But yes just splitting this up in functions makes way more sense

Codecov Report

Merging #350 (a0423d8) into master (66519d5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #350   +/-   ##
=======================================
  Coverage   75.29%   75.29%
=======================================
  Files          83       83
  Lines       10391    10391
=======================================
  Hits         7824     7824
  Misses       2567     2567

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


LAN addrs for services initially resolving Embassy UI

Reproduction steps:

Install service
Configure and start
Visit LAN address

If you visit the address quickly enough (no idea how quick is quick enough) Embassy UI will load instead of the service UI. This is not an acceptable experience and will likely result in added support load. Either we need to fix this behavior on the BE, or we need to message for it or black against it on the FE.

@dr-bonez you had said that one of the ways for this to be resolved is that there is a "starting" status for when the container has been started but the net controller hasn't yet been updated?

I would have to create one. It doesn't exist yet

Is that the approach we are going with though? I'm trying to clean out all the scoping requirements here.

yeah a starting state seems like the correct route to go here.

OK should this still be a joint assignment or is the entirety of the work on embassyd?

@DrewAns The FE component that needs to be handled by this ticket is as follows.

A new status will be introduced: starting
If an app is currently in the starting state, then the launch UI button should be greyed out or otherwise unclickable.

@dr-bonez
is "starting" a package status in the installed object, or a state at the top level of the package?

This should not be closed until the full fix is in. So far only the FE portion has been merged


UI enhancement request: Indicate completed orders in Account Orders History

Currently, in the Account Orders History UI, there is a listing of the orders made, both completed and unfulfilled.  It would be helpful to visually indicate which orders there have be filled/completed, and which are still Open. (display completed ones with a green or orange font, perhaps?)

Moved: https://github.com/BitShares/web_wallet/issues/629


Release spark 1.1.1-2.2.0 (automated commit)

Release spark 1.1.1-2.2.0 (automated commit)
Changes since revision 26:
0 files added: []
0 files removed: []
4 files changed:
--- 26/command.json
+++ 27/command.json
@@ -1,5 +1,5 @@
 {
   "pip": [
-    "https://downloads.mesosphere.com/spark/assets/1.1.0-2.1.1/dcos_spark-0.5.19-py2.py3-none-any.whl"
+    "https://downloads.mesosphere.com/spark/assets/1.1.1-2.2.0/dcos_spark-0.5.19-py2.py3-none-any.whl"
   ]
 }
--- 26/config.json
+++ 27/config.json
@@ -45,12 +45,12 @@
         "spark-dist-uri": {
           "type": "string",
           "description": "Spark distribution URI.  This is only used to run spark-submit on your local machine.  The DCOS Spark CLI will fetch this Spark distribution.  This variable has no effect on the Spark distribution running the dispatcher, drivers, nor executors.  If you want to customize the Spark build used in the jobs themselves, configure service.docker-image.",
-          "default": "https://downloads.mesosphere.com/spark/assets/spark-2.1.1-bin-2.6.tgz"
+          "default": "https://downloads.mesosphere.com/spark/assets/spark-2.2.0-bin-2.6.tgz"
         },
         "docker-image": {
           "type": "string",
           "description": "The docker image used to run the dispatcher, drivers, and executors.  If, for example, you need a Spark built with a specific Hadoop version, set this variable to one of the images here: https://hub.docker.com/r/mesosphere/spark/tags/",
-          "default": "mesosphere/spark:1.1.0-2.1.1-hadoop-2.6"
+          "default": "mesosphere/spark:1.1.1-2.2.0-hadoop-2.6"
         },
         "log-level": {
           "type": "string",
--- 26/package.json
+++ 27/package.json
@@ -20,6 +20,6 @@
     "batch",
     "analytics"
   ],
-  "version": "1.1.0-2.1.1",
+  "version": "1.1.1-2.2.0",
   "website": "https://docs.mesosphere.com/service-docs/spark/"
 }
--- 26/resource.json
+++ 27/resource.json
@@ -2,7 +2,7 @@
   "assets": {
     "container": {
       "docker": {
-        "spark_docker": "mesosphere/spark:1.1.0-2.1.1-hadoop-2.6"
+        "spark_docker": "mesosphere/spark:1.1.1-2.2.0-hadoop-2.6"
       }
     }
   },

I will create a new PR after back porting a change to 2.2.0.


Moved functions in the cpp file

Removed the #define for VC6

Yeah... as I said, that will break the Dos build :-/

Why?

Let me hunt for a compiler option. I would like that best, because only one compiler is concerned anyway....

Uhm, I'd prefer to move the inline functions to a cpp file.

Usually inline is only because of my laziness :)

But there's also that there are some platforms that are easy to forget and hard / impossible for us to test.
Perhaps it would be a good idea to create an issue for everything that involves adding / removing / renaming files, and then do them all at once (like with the splitting of mock tests).
My bad not to have proposed a separate source to begin with.

Yeah, perhaps...


Update tool to allow direct args or update docs

Silly me, just realized that all of our docs saying to use logpipe --port <number> were wrong.
Right now node swallows these args, so we need to do logpipe -- --port <number> which looks pretty annoying.
There should be a way to get around this. One way is to capture the arguments before passing it to node through bash.

Ended up just being a bug in my argument parsing. Not an actual issue with node swallowing arguments.


Forked Network Tests

Having tests against a forked network would be very helpful for ensuring that any spell is correct.
The forge scripting framework that we are using has a convenience _postCheck method that can be implemented with assertions about the upgrade. Each script should implement the _postCheck method with application specific assertions and should be ran before performing an upgrade.
There are 2 options for how these tests can be implemented:

Spin up anvil and run the script exactly as is against a forked network. This may not work ideally with multisigs unless coupled with the RPC hardhat_setStorageAt (there is also an anvil prefixed alias) to overwrite the signer threshold.
Do all of the execution in memory as a simulation, so call the forge script without the --broadcast flag, pin the command to a particular blocknumber and pass a URL to fork state from. We would want to make a solidity library that can be used for overwriting the signer threshold, this is easy to do with the cheatcode vm.store.

The second option seems a bit easier to me.
The justfile could be updated with a test command that CI can consume. We could choose to stop running tests for upgrades that we have already performed after some time if we wanted to.
We may also want to consider if we want to have a _preCheck function that can be implemented as well.

@tynes What exactly did you have in mind for this issue's scope? Should this be closed because we do implement the postCheck hooks now, or did you mean running the standard monorepo test suite against the state resulting from a task?

Good to close this based on the post hooks existing


[Bug] Any button on the form triggers a save action

Bug report
What I did
I added a button to a CRUD edit form
What I expected to happen
the button to work by itself, to start some javascript action
What happened
the button triggers a save action
What I've already tried to fix it
stopImmediatePropagation/return false
Is it a bug in the latest version of Backpack? yes
After I run composer update backpack/crud the bug... is it still there?
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
the last version

Hey @MeerKatDev
Any button inside the form, if you don't specify type="button" will be assumed to be a submit button.
That's general web rules, not backpack ones. I am pretty sure that you are missing that bit. https://www.w3.org/TR/2011/WD-html5-20110525/the-button-element.html#the-button-element
Let me know,
Pedro

didn't know that - thanks!


Migrate OpenVP-CANdy services to use the BC Endorser Service

Dev:

DID: Ui6HA36FvN83cEtmYYHxrn rooted on CANdy-Dev
[x] Update the DID with and Alias: CANdy - Unverified Person Issuer (Dev)
[x] Ensure the author's agent is configured to be an author on the ledger (role=null)
[x] Make sure all services connected to the author's agent, other than the wallet, are shutdown; controllers, apis, web interfaces.
[x] Ensure the author's agent configuration has been updated to support the endorser protocol settings.
[x] Update the author's agent settings to enable the endorser protocol.
[x] Ensure READ_ONLY_LEDGER=false on the author's agent.
[x] Accept TAA though the author's agent if needed.  Switching to multi-ledger breaks existing TAAs
[x] Ensure the author's public endpoint has been written to the ledger.
[x] Register the agent with the BC Endorser Service using the ./manage registerAuthor script.
[x] Restart all services connected to the author's agent.

Test:

Old DID: XZQpyaFa9hBUdJXfKHUvVg rooted on CANdy-Dev

[x] Demote

New DID: HTkhhCW1bAXWnxC1u3YVoa rooted on CANdy-Test
[x] Start out with ACAPY_READ_ONLY_LEDGER=true
[x] Migrate the OpenVP-CANdy DID to CANdy-Test.  Create a new DID, the existing one is on CANdy-Dev as it pre-dates the CANdy-Test ledger.  Use the CANdy-Test - Government of British Columbia - Endorser to write the new DID.
[x] Set the alias to CANdy - Unverified Person Issuer (Test)
[x] Ensure the author's agent is configured to be an author on the ledger (role=null)
[x] Make sure all services connected to the author's agent, other than the wallet, are shutdown; controllers, apis, web interfaces.
[x] Ensure the author's agent configuration has been updated to support the endorser protocol settings.
[x] Update the author's agent settings to enable the endorser protocol.
[x] Ensure READ_ONLY_LEDGER=false on the author's agent.
[x] Accept TAA though the author's agent if needed.  Switching to multi-ledger breaks existing TAAs
[x] Ensure the author's public endpoint has been written to the ledger.
[x] Register the agent with the BC Endorser Service using the ./manage registerAuthor script.
[x] Restart all services connected to the author's agent.
[x] Ensure Schemas and Cred-Defs get written to the ledger.

"Prod":

Old DID: 9wVuYYDEDtpZ6CYMqSiWop rooted on CANdy-Dev

[x] Demote

New DID: 4eCXHS79ykiMv2PoBxPK23 rooted on CANdy-Test
[x] Start out with ACAPY_READ_ONLY_LEDGER=true
[x] Migrate the OpenVP-CANdy DID to CANdy-Test (NOT CANdy-Prod).  Create a new DID, the existing one is on CANdy-Dev as it pre-dates the CANdy-Test ledger.  This VC is meant for testing purposes only.  Such DIDs do not get written to production ledgers.  Use the CANdy-Test - Government of British Columbia - Endorser to write the new DID.
[x] Set the alias to CANdy - Unverified Person Issuer (Prod)
[x] Ensure the author's agent is configured to be an author on the ledger (role=null)
[x] Make sure all services connected to the author's agent, other than the wallet, are shutdown; controllers, apis, web interfaces.
[x] Ensure the author's agent configuration has been updated to support the endorser protocol settings.
[x] Update the author's agent settings to enable the endorser protocol.
[x] Ensure READ_ONLY_LEDGER=false on the author's agent.
[x] Accept TAA though the author's agent if needed.  Switching to multi-ledger breaks existing TAAs
[x] Ensure the author's public endpoint has been written to the ledger.
[x] Register the agent with the BC Endorser Service using the ./manage registerAuthor script.
[x] Restart all services connected to the author's agent.
[x] Ensure Schemas and Cred-Defs get written to the ledger.

Update dependent services and references:
Test - XZQpyaFa9hBUdJXfKHUvVg => HTkhhCW1bAXWnxC1u3YVoa

[x] Code references: https://github.com/search?q=org%3Abcgov+XZQpyaFa9hBUdJXfKHUvVg&type=code

https://github.com/bcgov/bc-wallet-mobile/issues/806
https://github.com/bcgov/issuer-kit-demo-verifier-chat/issues/84
https://github.com/bcgov/trust-over-ip-configurations/issues/123
https://github.com/bcgov/essential-services-delivery/issues/125

[x] Discussions: https://github.com/search?q=org%3Abcgov+XZQpyaFa9hBUdJXfKHUvVg&type=discussions

"Prod" - 9wVuYYDEDtpZ6CYMqSiWop => 4eCXHS79ykiMv2PoBxPK23

[x] Code references: https://github.com/search?q=org%3Abcgov+9wVuYYDEDtpZ6CYMqSiWop&type=code

https://github.com/bcgov/bc-wallet-mobile/issues/806
https://github.com/bcgov/essential-services-delivery/issues/125

[x] Discussions: https://github.com/search?q=org%3Abcgov+XZQpyaFa9hBUdJXfKHUvVg&type=discussions

Update URL for "PROD" environment

[ ] https://openvp-candy-dev.vonx.io/ => https://openvp-candy.vonx.io/

[ ] Update Open Verified Person (OpenVP) Credential with new URL.

The issuer services have been migrated to the correct ledgers (now they are available) and wired to the BC Endorser services for those environments and tested.
Environment documentation has been updated with the new DIDs and ledger links.
Left to do - update the code references; proof configurations and credential branding in the wallet.

Tickets have been created for updating code references.  All but the BC Wallet ticket have been completed.
Left to so - Update the "Prod" URL.

Work here is complete.  There are separate PRs and issues in review for the various steps.  All work has been tested.


Fix Delphes non-'sm' execution

This PR aims to continue the fixes from previous PR (https://github.com/scailfin/workflow-madminer/pull/15), that allowed all the Pyshics use-case steps to be run locally.
For now, the ROOT_INCLUDE_PATH Delphes run-time used environment variable has been added. When not defined, the beginning of the log file (log_delphes.log) that the 4th step of the Physics workflow creates, look like this:
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootTreeReader.h
   requested to autoload type ExRootTreeReader
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootTreeWriter.h
   requested to autoload type ExRootTreeWriter
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootTreeBranch.h
   requested to autoload type ExRootTreeBranch
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootResult.h
   requested to autoload type ExRootResult
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootClassifier.h
   requested to autoload type ExRootClassifier
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootFilter.h
   requested to autoload type ExRootFilter
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootProgressBar.h
   requested to autoload type ExRootProgressBar
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootConfReader.h
   requested to autoload type ExRootConfParam
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootConfReader.h
   requested to autoload type ExRootConfReader
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState:
   Missing FileEntry for ExRootAnalysis/ExRootTask.h
   requested to autoload type ExRootTask
** INFO: adding module        ParticlePropagator       ParticlePropagator
** INFO: adding module        Efficiency               ChargedHadronTrackingEfficiency
... From this point forward modules are loaded normally ...

The reference to solve this problem has been obtaine from this ROOT forum response.

~What is missing in this PR?~
~Last thing I would like to debug before merging, is the fact that the Physics 4th step (executable via the 4_delphes.sh script), only works when the provided benchmark is sm.~

Additional changes
In order to make the 4_delphes.sh script work with any benchmark, the /extract folder need to be cleanup after each run. This is an issue when running all the benchmark-dependent Delphes steps locally, but not when running them on completely isolated environments (REANA).
Furthermore, I have implemented a "events file discovery snippet" to work with different named output files from the previous step (step 3: Pythia simulation).
I could not figure out why this is happening, so event files will look like:

tag_1_pythia8_events.hepmc.gz
tag_2_pythia8_events.hepmc.gz
...

@irinaespejo this PR is not in "draft" stage anymore.
Changes to make it promote to production-ready PR can be checked in these commits:

Improve Physics step 4 operability
Impl. events file discovery function

Thank you @Sinclert the changes look great!


bat-into-tokyonight --clean

Why

When a user uninstalls the themes, this method is easier than manually deleting the directory by typing the full path.

About

remove the theme directory

remove tokyonight.nvim/ from $(command bat --config-dir)/themes/

remove the cache

If the cache remains, the deletion is not applied, which is contrary to user expectations.

It should be sufficient to introduce a snippet in the README without providing a cleanup script.


update does not reset popup to current date

Expected behaviour
I call .datepicker('update', '') and click on the input-addon.
When I click on a freshly created instance the current month is preselected.
I expect the current month to be displayed as popup.
Actual behaviour
The calendar pops up and displays the month that was previously selected.
Datepicker version used
ex. 1.7.1.

I setup a fiddle over at bootply; that works as expected

This is still true for version 1.9.
Calling .datepicker('clearDates'); doesn't improve the situation.


xGov-180: Thurstober Digital Studios - Open Source, No Code Tools

An overview of the xGov Proposal for Thurstober Digital Studios.

Seems like the proposal number should be 180

Hey @LoafPickleWW your proposal number should match the PR number. Would you please rename it (and on the forum as well if you've created your thread)? Thanks.

Hey @LoafPickleWW your proposal number should match the PR number. Would you please rename it (and on the forum as well if you've created your thread)? Thanks.

Done

Deliverables:
The Deliverables for this proposal are now complete, you can see them here:
Item 1: The Laboratory 1
Item 2: https://swapshop.thurstober.com/ 1
Item 3: The Laboratory 1 and The Laboratory 1
Item 4: The Laboratory 1
Item 5: Wallet Enhancer 1
Item 6: The Laboratory 1
Item 7: https://labs.thurstober.com/ 1
Repos:
Labs: GitHub - thurstober-digital/evil-tools
Wallet Enhancer: GitHub - algovado/wallet-enhancer: Make it easier to interact with the assets (or NFTs) of Algorand.
Swap Shop: GitHub - algovado/swap-shop 1

Please note that all of these sites have now moved to wen.tools. Redirects should work, but all the repos can be found here: https://github.com/LoafPickleWW

Fixed links:

https://www.wen.tools/vault-send
https://swap.wen.tools/
https://www.wen.tools/simple-mint and https://www.wen.tools/simple-update
https://www.wen.tools/multimint-asset-holders
https://wallet.wen.tools/asset/392891258
https://www.wen.tools/simple-batch-mint
https://www.wen.tools/ and https://wallet.wen.tools/ and https://swap.wen.tools/


Fix for choosing PnC and DIN removal when the connection is non-TLS

@anudeep-20 - I see the file formatting has failed (the comment has exceeded 88 chars limit per line). Could you run the following commands in the repo and fix any errors.
make flake8
make black
make reformat

Hi @anudeep-20 - merging this change. Thank you for the PR. :)


Fix Wrapping optimizers upon assignment

What does this PR do?

Fixes # (issue) <- this links related issue to this PR
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[ ] Check that target branch and milestone match!

Did you have fun?
Make sure you had fun coding 🙃

Hello @justusschock! Thanks for opening this PR.

In the file pytorch_lightning/trainer/properties.py:

Line 378:1: W293 blank line contains whitespace

Do see the Hitchhiker's guide to code style

@justusschock it seems that the GPU tests hanged...

@Borda That's strange because actually it should not change the behaviour of those tests at all.

@justusschock fixing GPU test now, so a sec...


Inquiry About Open Source Plans

Very interesting work! Could you kindly share if there are any plans to open source your AnomalyCLIP in the near future?

Very interesting work! Could you kindly share if there are any plans to open source your AnomalyCLIP in the near future?

Hi Our code has been released thanks for your interests.


Hello!

Hello!
Thank you for publishing this project.
If you're interested in this sort of thing, you may also be interested in https://github.com/Cyphrme/Coze.  Coze also performs JSON canonicalization.
I also had a question:
Why not require the minimal escaping, U+0000 to U+0019 / U+0022 / U+0056?
Thank you,
Zamicol

The escaping is minimal given that we require a valid Unicode document that can safely be interchanged between systems.
The U+D800 to U+DFFF range is used for surrogate pairs in UTF-16 to represent code points beyond U+FFFF, which require more than the 16 bits available in UTF-16 to specify. They are code-points but not characters. Hence, they do not appear in valid Unicode character stream. They should only appear in UTF-16 encodings. UTF-8 and UTF-32 should not use them. (Though in the real world, they do appear in "wobbly" UTF-8 encodings.)
If a system receives a document that contains a single code-point in the range U+D800 to U+DFFF, then it is certainly allowed to replace that character with a U+FFFD � replacement character as the single code point does not represent a character. Python has a system called "surrogate escapes" where invalid UTF-8 is replaced with isolated surrogate pairs to preserve the invalid bytes. Such a system would treat a UTF-8 input with an isolated surrogate pair as three invalid bytes and expand your single code point out to three.
Unicode also has non-characters and private-use characters. These are OK for interchange and hence we do not require them to be escaped.
I'm sure you will have noticed that the Coze canonicalization procedure specifies how fields in objects should be ordered, but not how they should be represented. Many systems lean on the IEEE algorithm for representing 64-bit floating point numbers, but this can lead to problems. For example, the "1000000000000000000" is a valid 64-bit integer, and as an integer would be displayed as that. However, if parsed as a IEEE 64-bit double, then it would be output as "1.0E18". This breaks digital signatures.

I guess the question is why escape and not error for the range U+D800 to U+DFFF?  Why not just leave them, or specify that they should be replacement characters?
Escaping the 34 required by the RFC is legitimate.  There's also another approach: OLPC escaped only the two characters absolutely required to be escaped, and does not escape anything else.  The appeal of this approach is that although that's out of alignment with the JSON RFC, it is in alignment with the original JSON.org spec, and also acknowledges that there was an oopsie with the RFC.  The RFC forgot about the other ASCII, and further still, Unicode control characters and non-printable characters.  There are 33 ASCII controls and 65 Unicode controls, not 32 as the RFC was originally written.

how fields in objects should be ordered, but not how they should be represented.

In Coze the digest is over bytes.  For JSON this is UTF-8 first and then JSON.  A message can be verified by Coze and be represented by various systems differently.  If fact, Coze signs and verifies digests, and that digest can be of anything.  Coze just has some addition rules for messages that are JSON.
I am thinking about adding a stricter JSON canonicalization to CozeX (Coze eXtended), which yes would address representation as well.  However, that's a rabbit hole I'm not confident anyone has resolved yet.  I'm currently researching that problem.  Coze chose its current canonicalization exactly because I wanted to avoid writing representation rules, which are much more extensive than what it currently requires.  Any stricter canonicalization would probably be added to CozeX, unless there was a really good reason to add it to core, the main Coze spec.

In my opinion, a canonical JSON format needs to meet at least these goals:

Be valid JSON (so not OLPC)
Allow all possible JSON data to be represented without loss so,
a) no forcing of IEEE floating point, like RFC-8785,
b) no changing string representation to replace characters, enforce normalization, or similar
c) no barring data, like lone surrogates, as RFC-8785 requires.
Be platform agnostic  (so no assuming ZMODEM is not being used, for example)
In some sense, be faithful to the concept of JSON.

The JSON standard does have quirks, such as why is U+007F (DEL) not escaped when all other 7-bit control codes are?
Escaping U+0000 to U+001F ensures the obvious high risk U+0000 (NUL) which can be interpretted as a text terminator, U+000A (LF) and U+000D (CR) which can be changed due to line end conversions such as between UNIX and Windows, U+0009 (TAB) which can be broken by auto-reformatting. Then there are less obvious cases such as use of the data separator characters U+001C to U+001F to seperate JSON records in a single file, and the fact some data transmission protocols use the control characters as actual control characters.
There are many other characters that could cause problems. Here are some examples:

The entire C1 control characters group (U+0080 to U+009F)
New line characters U+0085, U+2028, and U+2029 which could be broken by new line standardisation
The DEL character U+007F
Non-characters, which some implementations consider invalid in character streams, according to the unicode consortium
Private-use characters, which could interfere with another systems private use of the private use character
Unassigned characters, which could be replaced with the replacement character U+FFFD
Annotation markers, which could be stripped.
Explicit variant selectors which select undefined or default character variants.

All of these are valid JSON and valid unicode, so we allow them.
Unicode allows all code-points except the lone surrogates to appear in transmissions. Lone surrogates can be valid data though, such as Python's surrogate escapes. That leads us to escaping lone surrogates instead of barring them.
If we ever get a version 2 of this standard, I'd like to see the possibility for configration, where parties can agree additional escaping of characters to acknowledge the limits of their systems and working practices. I would add U+007F to U+009F, U+2028 and U+2029, but no more than that, in my own systems as those have all caused me concerns in real life. I'd also like a configurable limit on the number of trailing zeros on an integer, so values like 1.23E+2, and 1.23E+2000000000 can both be handled sensibly.
In a cryptographic secure system everyone has to agree on the "bytes that were signed", so the path from data to bytes must be precise.  Is 1E+1000 an integer, a floating point, or an invalid number because it doesn't fit in IEEE 64-bit number? Is 1.0000000000000001 the same as 1?  If all systems agree, you are good. If you control all systems, it is easy to make them agree. If you think people might be building their own systems to implement your standards you are the mercy of their assumptions about what you don't specify.
The key benefit of this Canonical JSON specification is that every JSON document has a canonical form. All the other specifications I am aware of limit the data that can be represented.

Thank you for your thoughtful reply!
My plan for this week is to play with control characters
in jq.  I'd like to better document particular issues with using non-escaped control characters.
Do you have any particular examples with non-escaped control characters,  especially those past 32?  I'm hoping tonight to start playing around with 'DEL'.  I'd suspect there's issues with that to start.

I'm writing this on my phone while waiting for an appointment.  I forgot to ask, why doesn't this spec require DEL and the Unicode range controls to be escaped?

The short answer is that if we escape the characters required by JSON, and escape the lone surrogates to respect Unicode, then everything else is technically allowed.
Everything else is trying to protect humans from theoretical confusion by strangely displayed data, or protecting systems from theoretical bugs. Such things are very hard to predict. For example, who would have thought mixing Telugu and Zero-Width-Non-Joiners would brick iPhones? If we try to identify every theoretical problem, we will end up with a lot of extra work for no certain benefit. Is the cost worth it? We cannot know.
However, I think there are grounds for systems to require additional escaping.

DEL can be used to hide data
U+0080 to U+009F are used to control things. You'd think one had to be mad to implement U+009D (Operating System Command), but according to Wikipedia it works in xterm.
Next line, line separator and paragraph separator could be messed up by text editors and break the expected flow of a JSON document.

I'd seriously consider proposing these as a potential variant to the standard as I can see specific clear risks, but I don't think they should be a required part of the standard as there is, technically, no problem with them.
If we are going to look at theoretical problems, we have a lot to consider:

Bidirectional text can confuse humans and hide the real meaning of text. They are known to be used in phishing attacks, so the bidirectional control codes could be risky but on the other hand are required for proper display of Right-To-Left text. If you ban them, humans could be confused by text that is supposed to be RTL but is displayed LTR.
Language Tags - Deprecated for a while and now un-deprecated but without meaning. This sounds like a ripe territory for bugs and so maybe we should protect systems from them?
Variant Selectors - Getting the right skin tone for your emoji is important, but what if you pick a variant that doesn't exist? That sounds like accessing an undefined memory address and that leads to bugs.
Interlinear annotations - affect text display so could hide data from humans.
Private use characters - what if the target system uses the private use character as a control code?
Unallocated code points - what if they are handled strangely?

They come down to two main areas of risk. The first is "humans might be confused". Why are humans looking at the JSON? Users should be looking at the user-interface and that needs to handle the weird characters. Developers, one hopes, know what they are doing.
The second risk area is "Sound like it might cause bugs". If my favourite editor strips language tags that's not the problem of the JSON. If my system uses private use characters as control codes, then that was something we should be predicting here. I would never have put "Telegu + ZWNJ" on my list of risks, and that just shows why this is an impossible task.
So:

If it is required to be escape by a standard, then we should escape it (Hence U+0000 to U+001F and isolated surrogates)
If it has a clearly defined risk, we should escape it as a well documented extension to the standard.
If it has a vague risk, we should keep things simple and do nothing.

Hope that helps.

I asked around to see if anyone knew of an example exploit using the "theoretically risky" characters. We didn't know of any, but the advice I got differed from my "what should the standard say" to be "what would a security professional recommend".
So, this was their response:

Precautionary Approach is the way to go. Experience and history repeatedly show that something that someone one day thinks is "overly cautious", becomes an exploit later.
The longer version is that the removal or escaping of potentially problematic characters, in any system, nearly always has the benefit of reducing the surface area for vulnerabilities, known and unknown. If you adopt this approach, you effectively lower the risk of unexpected behaviour or security issues at the expense of string veracity and processing speed, which aren't excuses not to do it. If there is a potential loss of information / change in meaning of the string, or if processing speed is an issue now, then remember hackers don't sit there and say "Oh, these guys have servers too slow and code that isn't secure, so we won't target them", on the contrary.
With your Standards Approach, as best as I can tell, in both JSON and Unicode standards these characters are "allowed". Relying solely on standards, however, assumes that all systems handling the data also strictly adhere to these standards, which is not always the case (now, or in the future), as again history and experience frequently shows.
So my recommendation would lean towards the precautionary approach.
Your list for the super-cautious approach seems well-considered. It addresses a range of potential issues, from data corruption to security vulnerabilities, and I can't think of anything to add there.
To answer your question, I have not personally come across any instances where language tags, annotations, or variant selectors have been used in successful hacking attempts. However, me being unaware of such cases should not imply the absence of risk. Basically you've jinxed this by discussing it, and you should now consider all of these a security risk, because if you can see a potential security risk, so might someone else.
So given the complexity of IT systems, unknown future changes to these systems, and the likelihood of encountering non-standard behaviours, I would recommend adopting the precautionary approach, which would include escaping the characters you've mentioned.

In the real world, the chosen solution generally becomes a compromise between what the standards guy (me) and the security guy (quoted) recommend.


Add sizing helpers for SVGs

Changes

Add sizing helpers for SVGs

Closes #64.

Are these style helpers also exported for users of the component library?

@mlent They are: https://github.com/sumup/circuit-ui/blob/master/src/styles/index.js#L4


Support for dotnet core

Investigate what's required.
Known issues:

We assume Windows style directory separators (C:\blah) - for this should be able to cherry-pick https://github.com/ComparetheMarket/fettle/commit/b7efed34e91b93d4b5be1d112d4b01fa77bd5285 from the mono branch

Known potential issues:

Relying on app-domains for isolation when running tests using NUnit Engine, not sure what happens when using the .NET Standard version?

@oliwennell do you want a hand with this? I was just thinking about it this morning....which is how I found this issue.

I'd welcome your help if you're up for it @dcook-net :)
I did some initial investigation but i was quite a while ago now.
Perhaps if you have an initial look and we can talk through what you find?

Cloning...

Just thought about creating a global tool for fettle, so we could simplify how the tool is run. And this is how I landed here.
@dcook-net how it went with conversion to the core? Can I help somehow?

Support for  Microsoft.CodeAnalysis.MSBuild.MSBuildWorkspace(https://github.com/dotnet/roslyn/issues/17974) is missing in core.

@robertlyson I didnt get very far, mostly due to other commitments tbh. I doesn't currently build.

Hey @robertlyson , thank you for offering to help :) 👍
Right now what would help is a list of "known issues" that we need to resolve before we can support dotnet core. I see that you've mentioned an issue with MSBuildWorkspace, if you're able to find out any others and list them here that's be great.
Alternatively, you could look into how we could get around the MSBuildWorkspace issue you mentioned.

Just thought about creating a global tool for fettle, so we could simplify how the tool is run. And this is how I landed here.

This is a good idea. Personally I think this combined with DotNetCliToolReference support would be fantastic (FYI - this is also how Stryker works). This would give users complete flexibility in how people consume fettle.
Global Tools are great on the command line, but are a little messy inside Docker.
Just thinking out load.


[SVS-36] Save (with prompt) before binding and after (without prompt)

#SVS-36
Misc: modified execution preference of one of the steps.

LGTM


WIP: Move to Dropwizard 2.0 series

Why:
1.3 branch was last released in 2020-12 making it pretty stale. Moving
off of this branch keeps us with the releases.
How:
This should remove all references to dropwizard 1.3.X releases and
should add the specific dependencies required for this
project. Specifically, with Dropwizard 2.X, Guardrail needs to include

hibernate-core
hibernate-validator

as they are no longer transitively pulled into the project via
Dropwizard dependencies.
Need Help:
I don't understand how the classpath for the tests is
constructed. This results in the classpath missing the hibernate
dependencies during test runs.

Alrighty, I've been sorta hands-off on this because I really don't know anything about this, but I was able to stumble through at least enough of the deprecation notes to get it to attempt the tests.
I had no idea what whatever Unwrapping is, so I commented it out. Presumably we'll end up with runtime errors, but it gets us closer to iterating

A problem here is that dropwizard-scala is discontinued and has no dropwizard 2.x support


Project Needs Automated Test Framework

The project should have an automated test framework that gives at least basic coverage, if if it can't be perfect. This will both help reduce tedious manual testing and make it easier for new developers to contribute.
As a side note, introducing automated testing in projects not originally designed for it typically introduces major structural changes to accommodate the extra functionality needed to support automated testing.

There's both a unit test and functional test framework in PR #28. It's mixed in with other changes, though; if you don't want them all you'll have to pick out the bits you want.


Fix the wrong nouns in plugin test doc

@dmsolr I need to head up for you. There is a ref check feature missing in the current version. We are checking the instance id != 0 today, which is helpful but not enough, we should add service name(entry/parent) translated from the instance id in the mock.
This is not urgent, but should be done.

Codecov Report

Merging #4459 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4459      +/-   ##
==========================================
- Coverage   24.94%   24.94%   -0.01%
==========================================
  Files        1230     1230
  Lines       28490    28490
  Branches     3906     3906
==========================================
- Hits         7108     7107       -1
  Misses      20725    20725
- Partials      657      658       +1

Impacted Files
Coverage Δ

...ache/skywalking/apm/agent/core/jvm/JVMService.java
55% <0%> (-1.67%)
:arrow_down:

Continue to review full report at Codecov.

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


Exception: build_media_tag: unable to find audio data with language: gl, channels: 2.0

Bug report
Your Environment

Netflix add-on version: 1.9.0
Operating system version/name: LibreElec 9.2.4
Device model: Raspberry Pi 3 B+

Used Operating system:

[ ] Android
[ ] iOS
[X] Linux
[ ] OSX
[ ] Raspberry-Pi
[ ] Windows

Describe the bug

Kodi pops up an error of an exception build_media_tag: unable to find audio data with language: gl, channels: 2.0. The error pops up at starting and along the video stream at random intervals of time. It needs user interaction to acknowledge (Accept) every time.
After troubleshooting, it looks as if the error happens only when the audio track es-Spain is selected. If the track is selected after the stream was started in a different language, the error comes out after quiting the pop up menu.
However, I tested with other stream that uses spa as the name of the audio track and it does not fail.
Expected behavior

No errors.
Actual behavior

Popping up the described error when audio track tagged as es-Spain is selected.
Steps to reproduce the behavior

Error message:

Start any Narcos episode.
Choose audio track es-Spain

No error message

Start any Narcos episode.
Choose any audo track different to es-Spain.

Possible fix

My Kodi baseline language is gl_ES (Galician) and that may conflict with es_ES (Spanish - Spain) if expected by the plugin.
Debug log

The debug log can be found from these links:

Logs with Netflix debug verbose only: short log of error.
Logs with Netflix debug verbose and Kodi debug: full log of error.
Logs with Netflix debug verbose only: short log - no error.
Logs with Netflix debug verbose and Kodi debug: full log - no error.

Additional context or screenshots (if appropriate)
Installation

[ ] I'm using other Netflix Repo
[ ] I'm using a different source

Other information

Screenshots

i need to know two more things
-what profile language is set to the netflix profile used
-if you are able, from the addon user-data folder get the file "manifest.json" after played the video (mandatory nf addon verbose debug enabled from expert setting)

Hi,
I also have RPi 3 B+ with LibreElec...no Errors at all, try setting default audio and subtitle languages, on KODI Settings,  Player,  Languages...I use my default to English or Spanish , even I use Spanish - Mexico (Latin).
Hope it helps.

Hello,
Thanks for your replies. Regarding Kodi player language, audio is already set to Media Default.
Regarding the questions:

Netflix user's profile language is set to Spanish. I see Netflix addon in English because there is no translation to Galician… yet (I will try).
manifest file taken with Kodi and Netflix verbose debugging.

Many thanks again.
Regards.

I think i have fould the problem, try update test and let me know:
plugin.video.netflix_1.9.1_20200926_t1.zip

Yes! It works smooth now!
Thank you very much.


choice + extensions not represented properly?

So if I have...
  <xs:complexType name="base">
    <xs:sequence>
      <xs:element ... />
    </xs:sequence>
  </xs:complexType>

  <xs:complexType name="child">
    <xs:complexContent>
      <xs:extension base="base">
        <xs:choice>
           ...

The current behavior adds the base elements directly to the XsdGroup in the child, which seems incorrect.
I would expect the child XsdComplexType.content_type to be an XsdGroup with a sequence model, that contains 2 elements, the single element from the base and an XsdGroup representing the choice element in the child.
I believe the issue is caused at https://github.com/brunato/xmlschema/blob/master/xmlschema/factories.py#L496

Please take a look at this issue with the new version 0.9.10.

Will do.


MultiSig

Does Dogecoin support multi-sig transactions? I tried to create one but the funds aren't showing up in my generated MultiSig address:
http://dogechain.info/address/A3YeGE1MCRfj7c8SFs7oAtKYDLzsTXX7GC
http://dogechain.info/tx/caa22d4321b5f4dfa5843ef994a3c241fc8836c24d65125b2c34632ac082dd7e
Thanks

As per last comment, this is now in general use in standard client

multisig works fine with 1.8, I use it every day.

Do we have any documentation to perform multisig transaction on dogecoin.
like any github repo etc.


Fix for non-routable IP regex

The 172.2 pattern has an extra \ causing the fallback to host ip not to occur

Thank you for spotting this!

Thank you for spotting this!

No probs, thanks for your quick look at this PR - do you have any plan when the next package will be pushed to nuget? We came across this bug connecting to a third-party system and have temporarily used our copy of FluentFTP with this fix to test it confirm it worked - which it did :) But this was just a quick hack and we'd want to use the actual nuget feed version of FluentFTP.