feat: initialize projenrc.js with commented options

Issue #, if available: Closes #168
Description of changes: Updated default rendering function for .projenrc.js config file so that it gets initialize with a list of all options available based on the project type.
Also updated the docstrings of several props so that the "default" field would be a proper value.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This feature was easier than expected to implement. The only issue right now not all props seem to show up, and I'm honestly not sure why... For example if I run npx projen new typescript, around 50 or so of the possible config options all appear in alphabetical order (like shown below), but all of the TypeScript-specific options don't seem to appear. I might have to dig a little deeper into how JSII picks up these labels (because these properties are still appearing correctly in API.md).
const project = new NodeProject({
  // allowLibraryDependencies: true,                                           /** Allow the project to include `peerDependencies` and `bundledDependencies`. */
  // antitamper: true,                                                         /** Checks that after build there are no modified files on git. */
  // authorEmail: undefined,                                                   /** Author's e-mail. */
  ...

looking forward for another iteration

Here's what .projenrc.js looks like after creating a new jsii project with the features on this PR:
const { JsiiProject } = require('projen');

const project = new JsiiProject({
  // allowLibraryDependencies: true,                                           /** Allow the project to include `peerDependencies` and `bundledDependencies`. */
  // antitamper: true,                                                         /** Checks that after build there are no modified files on git. */
  authorAddress<EMAIL_ADDRESS>                                       /** Email or URL of the library author. */
  // authorEmail: undefined,                                                   /** undefined */
  authorName: "Chriscbr",                                                      /** The name of the library author. */
  // authorOrganization: undefined,                                            /** undefined */
  // authorUrl: undefined,                                                     /** undefined */
  // autoDetectBin: true,                                                      /** Automatically add all executables under the `bin` directory to your `package.json` file under the `bin` section. */
  // bin: undefined,                                                           /** Binary programs vended with your module. */
  // buildWorkflow: true,                                                      /** Define a GitHub workflow for building PRs. */
  // bundledDependencies: undefined,                                           /** undefined */
  // bundledDeps: undefined,                                                   /** List of dependencies to bundle into this module. */
  // compat: false,                                                            /** Automatically run API compatibility test against the latest version published to npm after compilation. */
  // compatIgnore: ".compatignore",                                            /** Name of the ignore file for API compatibility tests. */
  // copyrightOwner: undefined,                                                /** License copyright owner. */
  // copyrightPeriod: undefined,                                               /** The copyright years to put in the LICENSE file. */
  // defaultReleaseBranch: "master",                                           /** The name of the main release branch. */
  // dependabot: true,                                                         /** Include dependabot configuration. */
  // dependabotOptions: undefined,                                             /** Options for dependabot. */
  // dependencies: undefined,                                                  /** undefined */
  // deps: [],                                                                 /** Runtime dependencies of this module. */
  // description: undefined,                                                   /** Library description. */
  // devDependencies: undefined,                                               /** undefined */
  // devDeps: [],                                                              /** Build dependencies for this module. */
  // docgen: true,                                                             /** Automatically generate API.md from jsii. */
  // dotnet: undefined,                                                        /** undefined */
  // entrypoint: "lib/index.js",                                               /** Module entrypoint (`main` in `package.json`). */
  // eslint: true,                                                             /** Install eslint. */
  // java: undefined,                                                          /** undefined */
  // jest: true,                                                               /** Use jest for unit tests. */
  // jestOptions: undefined,                                                   /** Jest options. */
  // jsiiVersion: undefined,                                                   /** undefined */
  // keywords: undefined,                                                      /** Keywords to include in `package.json`. */
  // libdir: "lib",                                                            /** Compiler artifacts output directory. */
  // license: undefined,                                                       /** undefined */
  // maxNodeVersion: undefined,                                                /** Minimum node.js version to require via `engines` (inclusive). */
  // mergify: true,                                                            /** Adds mergify configuration. */
  // mergifyAutoMergeLabel: "auto-merge",                                      /** Automatically merge PRs that build successfully and have this label. */
  // mergifyOptions: undefined,                                                /** Options for mergify. */
  // minNodeVersion: undefined,                                                /** Minimum Node.js version to require via package.json `engines` (inclusive). */
  name: "projen-test",                                                         /** The name of the library. */
  // npmDistTag: "latest",                                                     /** The dist-tag to use when releasing to npm. */
  // npmignore: undefined,                                                     /** Additional entries to .npmignore. */
  // npmignoreEnabled: true,                                                   /** Defines an .npmignore file. Normally this is only needed for libraries that are packaged as tarballs. */
  // npmRegistry: "registry.npmjs.org",                                        /** The registry url to use when releasing packages. */
  // packageManager: NodePackageManager.YARN,                                  /** The Node Package Manager used to execute scripts. */
  // peerDependencies: undefined,                                              /** undefined */
  // peerDependencyOptions: undefined,                                         /** Options for `peerDeps`. */
  // peerDeps: [],                                                             /** Peer dependencies for this module. */
  // projenDevDependency: true,                                                /** Indicates of "projen" should be installed as a devDependency. */
  // projenUpgradeAutoMerge: undefined,                                        /** Automatically merge projen upgrade PRs when build passes. */
  // projenUpgradeSchedule: [ "0 6 * * *" ],                                   /** Customize the projenUpgrade schedule in cron expression. */
  // projenUpgradeSecret: undefined,                                           /** Periodically submits a pull request for projen upgrades (executes `yarn projen:upgrade`). */
  // projenVersion: Semver.latest(),                                           /** Version of projen to install. */
  // pullRequestTemplate: true,                                                /** Include a GitHub pull request template. */
  // pullRequestTemplateContents: undefined,                                   /** The contents of the pull request template. */
  // python: undefined,                                                        /** undefined */
  // releaseBranches: [ "master" ],                                            /** Branches which trigger a release. */
  // releaseEveryCommit: true,                                                 /** Automatically release new versions every commit to one of branches in `releaseBranches`. */
  // releaseSchedule: undefined,                                               /** CRON schedule to trigger new releases. */
  // releaseToNpm: false,                                                      /** Automatically release to npm when new versions are introduced. */
  // releaseWorkflow: true,                                                    /** Define a GitHub workflow for releasing from "master" when new versions are bumped. */
  repository: "https://github.com/Chriscbr/projen-test.git",                   /** Git repository URL. */
  // rootdir: ".",                                                             /** undefined */
  // scripts: {},                                                              /** npm scripts to include. */
  // srcdir: "src",                                                            /** Typescript sources directory. */
  // stability: undefined,                                                     /** undefined */
  // start: true,                                                              /** Defines a `yarn start` interactive experience. */
  // startOptions: undefined,                                                  /** Options for `yarn start`. */
  // testdir: "test",                                                          /** Tests directory. */
  // workflowBootstrapSteps: "yarn install --frozen-lockfile && yarn projen",  /** Workflow steps to use in order to bootstrap this repo. */
  // workflowContainerImage: undefined,                                        /** Container image to use for GitHub workflows. */
  // workflowNodeVersion: undefined,                                           /** The node version to use in GitHub workflows. */
});

project.synth();

Note how there is // projenVersion: Semver.latest() which corresponds to @default Semver.latest() from its docstring, and // copyrightPeriod: undefined which corresponds to @default - current year from its docstring.

Can we put this behind a cli flag or at least add a flag to disable this?
I think this is pretty unreadable for some project types with tens of options.
We have auto-completion to know what possible options we can set imho.

Great idea - I've gone ahead and added a CLI flag, --removeComments. I've opted to have the comments show by default since it's most helpful for new users, and it only gets generated once.
I've also added a minor quality of life improvement by organizing the options according to the interface they are from, to break down the big list a little bit. (For example, in a ReactProject, there a section appears for NodeProjectCommonOptions, a section for NodeProjectOptions, a section for TypeScript options, and if there were custom react options, then ReactTypeScriptProjectOptions). Here is how it looks with jsii:
const { JsiiProject } = require('projen');

const project = new JsiiProject({
  /* NodeProjectCommonOptions */
  // allowLibraryDependencies: true,                                           /* Allow the project to include `peerDependencies` and `bundledDependencies`. */
  // antitamper: true,                                                         /* Checks that after build there are no modified files on git. */
  // autoDetectBin: true,                                                      /* Automatically add all executables under the `bin` directory to your `package.json` file under the `bin` section. */
  // bin: undefined,                                                           /* Binary programs vended with your module. */
  // buildWorkflow: true,                                                      /* Define a GitHub workflow for building PRs. */
  // bundledDependencies: undefined,                                           /* undefined */
  // bundledDeps: undefined,                                                   /* List of dependencies to bundle into this module. */
  // copyrightOwner: undefined,                                                /* License copyright owner. */
  // copyrightPeriod: undefined,                                               /* The copyright years to put in the LICENSE file. */
  // defaultReleaseBranch: "master",                                           /* The name of the main release branch. */
  // dependabot: true,                                                         /* Include dependabot configuration. */
  // dependabotOptions: undefined,                                             /* Options for dependabot. */
  // dependencies: undefined,                                                  /* undefined */
  // deps: [],                                                                 /* Runtime dependencies of this module. */
  // devDependencies: undefined,                                               /* undefined */
  // devDeps: [],                                                              /* Build dependencies for this module. */
  // entrypoint: "lib/index.js",                                               /* Module entrypoint (`main` in `package.json`). */
  // keywords: undefined,                                                      /* Keywords to include in `package.json`. */
  // libdir: "lib",                                                            /* Compiler artifacts output directory. */
  // maxNodeVersion: undefined,                                                /* Minimum node.js version to require via `engines` (inclusive). */
  // mergify: true,                                                            /* Adds mergify configuration. */
  // mergifyAutoMergeLabel: "auto-merge",                                      /* Automatically merge PRs that build successfully and have this label. */
  // mergifyOptions: undefined,                                                /* Options for mergify. */
  // minNodeVersion: undefined,                                                /* Minimum Node.js version to require via package.json `engines` (inclusive). */
  // npmDistTag: "latest",                                                     /* The dist-tag to use when releasing to npm. */
  // npmignore: undefined,                                                     /* Additional entries to .npmignore. */
  // npmignoreEnabled: true,                                                   /* Defines an .npmignore file. Normally this is only needed for libraries that are packaged as tarballs. */
  // npmRegistry: "registry.npmjs.org",                                        /* The registry url to use when releasing packages. */
  // packageManager: NodePackageManager.YARN,                                  /* The Node Package Manager used to execute scripts. */
  // peerDependencies: undefined,                                              /* undefined */
  // peerDependencyOptions: undefined,                                         /* Options for `peerDeps`. */
  // peerDeps: [],                                                             /* Peer dependencies for this module. */
  // projenDevDependency: true,                                                /* Indicates of "projen" should be installed as a devDependency. */
  // projenUpgradeAutoMerge: undefined,                                        /* Automatically merge projen upgrade PRs when build passes. */
  // projenUpgradeSchedule: [ "0 6 * * *" ],                                   /* Customize the projenUpgrade schedule in cron expression. */
  // projenUpgradeSecret: undefined,                                           /* Periodically submits a pull request for projen upgrades (executes `yarn projen:upgrade`). */
  // projenVersion: Semver.latest(),                                           /* Version of projen to install. */
  // pullRequestTemplate: true,                                                /* Include a GitHub pull request template. */
  // pullRequestTemplateContents: undefined,                                   /* The contents of the pull request template. */
  // releaseBranches: [ "master" ],                                            /* Branches which trigger a release. */
  // releaseEveryCommit: true,                                                 /* Automatically release new versions every commit to one of branches in `releaseBranches`. */
  // releaseSchedule: undefined,                                               /* CRON schedule to trigger new releases. */
  // releaseToNpm: false,                                                      /* Automatically release to npm when new versions are introduced. */
  // releaseWorkflow: true,                                                    /* Define a GitHub workflow for releasing from "master" when new versions are bumped. */
  // scripts: {},                                                              /* npm scripts to include. */
  // srcdir: "src",                                                            /* Typescript sources directory. */
  // start: true,                                                              /* Defines a `yarn start` interactive experience. */
  // startOptions: undefined,                                                  /* Options for `yarn start`. */
  // testdir: "test",                                                          /* Tests directory. */
  // workflowBootstrapSteps: "yarn install --frozen-lockfile && yarn projen",  /* Workflow steps to use in order to bootstrap this repo. */
  // workflowContainerImage: undefined,                                        /* Container image to use for GitHub workflows. */
  // workflowNodeVersion: undefined,                                           /* The node version to use in GitHub workflows. */

  /* JsiiProjectOptions */
  authorAddress<EMAIL_ADDRESS>                                      /* Email or URL of the library author. */
  // authorEmail: undefined,                                                   /* undefined */
  authorName: "Chriscbr",                                                      /* The name of the library author. */
  // authorOrganization: undefined,                                            /* undefined */
  // authorUrl: undefined,                                                     /* undefined */
  // compat: false,                                                            /* Automatically run API compatibility test against the latest version published to npm after compilation. */
  // compatIgnore: ".compatignore",                                            /* Name of the ignore file for API compatibility tests. */
  // description: undefined,                                                   /* Library description. */
  // docgen: true,                                                             /* Automatically generate API.md from jsii. */
  // dotnet: undefined,                                                        /* undefined */
  // eslint: true,                                                             /* Install eslint. */
  // java: undefined,                                                          /* undefined */
  // jest: true,                                                               /* Use jest for unit tests. */
  // jestOptions: undefined,                                                   /* Jest options. */
  // jsiiVersion: undefined,                                                   /* undefined */
  // license: undefined,                                                       /* undefined */
  name: "projen-test",                                                         /* The name of the library. */
  // python: undefined,                                                        /* undefined */
  repository: "https://github.com/Chriscbr/projen-test.git",                   /* Git repository URL. */
  // rootdir: ".",                                                             /* undefined */
  // stability: undefined,                                                     /* undefined */
});

project.synth();

Looks good! A few more ergonomics suggestions:

Hoist all the assigned options to the top (so it's easy to just remove the comments)
Remove the deprecated options
Alpha sort

Agree. This is cool!

Updated with all three suggestions:
const { JsiiProject } = require('projen');

const project = new JsiiProject({
  authorAddress<EMAIL_ADDRESS>  authorName: "Chriscbr",
  name: "projen-test",
  repository: "https://github.com/Chriscbr/projen-test.git",

  /* JsiiProjectOptions */
  // authorOrganization: undefined,                                            /* undefined */
  // compat: false,                                                            /* Automatically run API compatibility test against the latest version published to npm after compilation. */
  // compatIgnore: ".compatignore",                                            /* Name of the ignore file for API compatibility tests. */
  // description: undefined,                                                   /* Library description. */
  // docgen: true,                                                             /* Automatically generate API.md from jsii. */
  // dotnet: undefined,                                                        /* undefined */
  // eslint: true,                                                             /* Install eslint. */
  // java: undefined,                                                          /* undefined */
  // jest: true,                                                               /* Use jest for unit tests. */
  // jestOptions: undefined,                                                   /* Jest options. */
  // jsiiVersion: undefined,                                                   /* undefined */
  // license: undefined,                                                       /* undefined */
  // python: undefined,                                                        /* undefined */
  // rootdir: ".",                                                             /* undefined */
  // stability: undefined,                                                     /* undefined */

  /* NodeProjectCommonOptions */
  // allowLibraryDependencies: true,                                           /* Allow the project to include `peerDependencies` and `bundledDependencies`. */
  // antitamper: true,                                                         /* Checks that after build there are no modified files on git. */
  // autoDetectBin: true,                                                      /* Automatically add all executables under the `bin` directory to your `package.json` file under the `bin` section. */
  // bin: undefined,                                                           /* Binary programs vended with your module. */
  // buildWorkflow: true,                                                      /* Define a GitHub workflow for building PRs. */
  // bundledDeps: undefined,                                                   /* List of dependencies to bundle into this module. */
  // copyrightOwner: undefined,                                                /* License copyright owner. */
  // copyrightPeriod: undefined,                                               /* The copyright years to put in the LICENSE file. */
  // defaultReleaseBranch: "master",                                           /* The name of the main release branch. */
  // dependabot: true,                                                         /* Include dependabot configuration. */
  // dependabotOptions: undefined,                                             /* Options for dependabot. */
  // deps: [],                                                                 /* Runtime dependencies of this module. */
  // devDeps: [],                                                              /* Build dependencies for this module. */
  // entrypoint: "lib/index.js",                                               /* Module entrypoint (`main` in `package.json`). */
  // keywords: undefined,                                                      /* Keywords to include in `package.json`. */
  // libdir: "lib",                                                            /* Compiler artifacts output directory. */
  // maxNodeVersion: undefined,                                                /* Minimum node.js version to require via `engines` (inclusive). */
  // mergify: true,                                                            /* Adds mergify configuration. */
  // mergifyAutoMergeLabel: "auto-merge",                                      /* Automatically merge PRs that build successfully and have this label. */
  // mergifyOptions: undefined,                                                /* Options for mergify. */
  // minNodeVersion: undefined,                                                /* Minimum Node.js version to require via package.json `engines` (inclusive). */
  // npmDistTag: "latest",                                                     /* The dist-tag to use when releasing to npm. */
  // npmignore: undefined,                                                     /* Additional entries to .npmignore. */
  // npmignoreEnabled: true,                                                   /* Defines an .npmignore file. Normally this is only needed for libraries that are packaged as tarballs. */
  // npmRegistry: "registry.npmjs.org",                                        /* The registry url to use when releasing packages. */
  // packageManager: NodePackageManager.YARN,                                  /* The Node Package Manager used to execute scripts. */
  // peerDependencyOptions: undefined,                                         /* Options for `peerDeps`. */
  // peerDeps: [],                                                             /* Peer dependencies for this module. */
  // projenDevDependency: true,                                                /* Indicates of "projen" should be installed as a devDependency. */
  // projenUpgradeAutoMerge: undefined,                                        /* Automatically merge projen upgrade PRs when build passes. */
  // projenUpgradeSchedule: [ "0 6 * * *" ],                                   /* Customize the projenUpgrade schedule in cron expression. */
  // projenUpgradeSecret: undefined,                                           /* Periodically submits a pull request for projen upgrades (executes `yarn projen:upgrade`). */
  // projenVersion: Semver.latest(),                                           /* Version of projen to install. */
  // pullRequestTemplate: true,                                                /* Include a GitHub pull request template. */
  // pullRequestTemplateContents: undefined,                                   /* The contents of the pull request template. */
  // releaseBranches: [ "master" ],                                            /* Branches which trigger a release. */
  // releaseEveryCommit: true,                                                 /* Automatically release new versions every commit to one of branches in `releaseBranches`. */
  // releaseSchedule: undefined,                                               /* CRON schedule to trigger new releases. */
  // releaseToNpm: false,                                                      /* Automatically release to npm when new versions are introduced. */
  // releaseWorkflow: true,                                                    /* Define a GitHub workflow for releasing from "master" when new versions are bumped. */
  // scripts: {},                                                              /* npm scripts to include. */
  // srcdir: "src",                                                            /* Typescript sources directory. */
  // start: true,                                                              /* Defines a `yarn start` interactive experience. */
  // startOptions: undefined,                                                  /* Options for `yarn start`. */
  // testdir: "test",                                                          /* Tests directory. */
  // workflowBootstrapSteps: "yarn install --frozen-lockfile && yarn projen",  /* Workflow steps to use in order to bootstrap this repo. */
  // workflowContainerImage: undefined,                                        /* Container image to use for GitHub workflows. */
  // workflowNodeVersion: undefined,                                           /* The node version to use in GitHub workflows. */
});

project.synth();

Was a little bit surprised to see all the comments when I run npx projen new today.
It's a nice feature but I personally prefer to disable by default and opt-in with the CLI argument(--comment).


Can't create Challenge pods on Openshift 4.1.4

Describe the bug:
Using ingress-shim, the cert-manager pod picks up the requested certificate but is unable to schedule the solver pods with the following error:
controller.go:131] cert-manager/controller/challenges "msg"="re-queuing item  due to error processing" "error"="[pods \"cm-acme-http-solver-9gfqp\" is forbidden: cannot set blockOwnerDeletion in this case because cannot find RESTMapping for APIVersion cert-manager.io/v1alpha2 Kind Challenge: no matches for kind \"Challenge\" in version \"cert-manager.io/v1alpha2\", services \"cm-acme-http-solver-rtttj\" is forbidden: cannot set blockOwnerDeletion in this case because cannot find RESTMapping for APIVersion cert-manager.io/v1alpha2 Kind Challenge: no matches for kind \"Challenge\" in version \"cert-manager.io/v1alpha2\"]" "key"="my-namespace/my-certificate-1785202477-1642064916-2652506774"

Expected behaviour:
Challenge solver pods are deployed, able to solve the ACME HTTP01 challenge, and issue a certificate.
Steps to reproduce the bug:
On an Openshift 4.1.4 cluster:

Deploy cert-manager 0.12.0
Deploy an ACME cluster issuer
Deploy an Ingress resource with the following annotations:  acme.cert-manager.io/http01-edit-in-place: true
  cert-manager.io/cluster-issuer: name-of-issuer-from-step-2

Check cert-manager pod logs

Anything else we need to know?:
I noticed issue #2308 with the same error was opened and marked as resolved. That issue was running cert-manager 0.11.0. We deployed cert-manager 0.12.0 and experienced the same issue. I tried changing the cert-manager deployment to use the quay.io/jetstack/cert-manager-controller:v0.13.0-alpha.0 image as well and had the same error.
The CRD for Challenge exists in the cluster with the API version acme.cert-manager.io/v1alpha2 instead of cert-manager.io/v1alpha2. It seems like #2324 implemented the fix to use the correct API version but it's either not working or not present in quay.io/jetstack/cert-manager-controller:0.12.0 and quay.io/jetstack/cert-manager-controller:v0.13.0-alpha.0
Environment details::

Kubernetes version (e.g. v1.10.2): v1.14.6+76aeb0c, Openshift v4.1.4
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): on premises Openshift
cert-manager version (e.g. v0.4.0): 0.12.0
Install method (e.g. helm or static manifests): helm

/kind bug

@CoaxVex could you please give some insights how to workaround this issue on cert-manager v0.12.0 ?

Challenges are using  acme.cert-manager.io/v1alpha2 (oc explain challenge), and not cert-manager.io/v1alpha2, so this does look very similar to #2308, but that one was on orders, not challenges.
It looks like the http solver tries to create a pod that has an owner reference to the challenge but gets it wrong.
I would start looking here: https://github.com/jetstack/cert-manager/blob/7f317469f36f4b15b21393b6fd85cbacb2c2b60e/pkg/issuer/acme/http/pod.go#L166

This is very weird..
Is there any details we can provide to help debugging this issue ?

Would I have to set any values in the helm chart when I install cert-manager? The only value I set at the moment is global.isOpenshift = true

@danielrudn not sure if this helps but in Openshift, if you leave the issuer ingress class blank, then it will use the default, which is the openshift ingress.
apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata:   name: letsencrypt-staging-cluster-issuer spec:   acme:     email<EMAIL_ADDRESS>   server: https://acme-staging-v02.api.letsencrypt.org/directory     privateKeySecretRef:       name: letsencrypt-staging-cluster-issuer-account-key     solvers:     - http01:         ingress:           serviceType: ClusterIP


[stable/neo4j] minor improvements to charts

-Changed the empty values in values.yaml to arrays instead of dicts.  This prevents following error when overriding them from a values parent chart:
warning: cannot overwrite table with non table for sidecarContainers (map[])
warning: cannot overwrite table with non table for initContainers (map[])

-Added variable for sidecarContainers for replicas as well

maintainer: @mneedham
/assign @linki

/cc @mneedham

LGTM

/assign

/retest

/ok-to-test

/lgtm


process registry should be in the type system

process registry is now a mapping between keys and addresses. An address contains the protocol : data the protocol needs to find and operate the process


Module does not work: "Unable to resolve module react-dom/server"

Expected Behavior

'react-native-avataaars' module should work out-of-the-box.

Actual Behavior

Metro builder generating an error upon importing the module and the app crashing

Steps to Reproduce the Problem

Create a new react-native project via expo CLI / RN CLI
Add 'react-native-avataaars' package to the project.
Import the package to App.js
Run 'npm run dev' on the terminal.

Try npm install react-dom --save or yarn add react-dom.


Supprot ES vector search（WIP）

Description
Supprot ES vector search
How Has This Been Tested?
unit test
Snapshots:
Include snapshots for easier review.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have already rebased the commits and make the commit message conform to the project standard.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] Any dependent changes have been merged and published in downstream modules

thanks for your pr, we will test and then will merge it.

Could you please provide additional documentation and include some examples of how to use it?

we need add elasticsearch package requirements I wonder

thanks for your pr, we will test and then will merge it.

It is very necessary to support ES

Already support at PR #1500


feat(validation): support for doc gen

What this PR does
Make definition.Operator an interface.
Add validator.Infoer for doc gen.
why we need it
doc gen need it.
Special notes for your reviewer:
https://github.com/caicloud/nirvana/issues/68
@liubog2008 @kdada @ddysher

The pr can be merged now. I'll refactor it later.


fix: set relative path to production /static/ path correctly

Fixes production images that isn't showing correctly, with this fix the relatives paths are setted correctly.

@liyasthomas this fix is urgent because its affecting the rendering of content bellow images
https://docs.hoppscotch.io/features/collections


Z-index issues when combining Dialog.Portal with Popover, Dropdown, etc.

Bug report
Current Behavior
After switching over to the new <Dialog.Portal>, I'm having issues maintaining a proper z-index order for dialogs that are initiated from Popovers or Dropdown menus.
A use case for this might be a "Delete" option in a DropdownMenu. The user opens a dropdown, clicks "Delete", and then a Dialog prompts them to confirm. We choose to keep the dropdown list open while the dialog is on screen.
With the current behavior, the dropdown list renders above the dialog's overlay because the dialog's portal seems to be using a new system that doesn't set a value for "z-index", but Popovers and DropdownMenus are using radix-portal, which sets<PHONE_NUMBER>.

Expected behavior
I would expect portals to layer in the order in which they are made visible. So if a Popover opens a Dialog, the Dialog should layer on top. If a Dialog opens a Popover, the Popover should layer on top.
Reproducible example
https://codesandbox.io/s/dreamy-curie-1rc2tf?file=/src/App.tsx
Suggested solution
Add documentation about how we can achieve this with the new Dialog API, if it's possible.
Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-dialog, @radix-ui/react-popover
0.1.7, 0.1.6

React
n/a

Browser
Chrome
100

Assistive tech

Node
n/a

npm/yarn

Operating System

Hi @jgoz,
It seems the reproducible Sandbox isn't saved properly, there's nothing in there apart from a title.
That being said, I think I can shed some light already.
Historically, all the primitives you mentioned used Portal internally and it wasn't exposed.
We hardcoded the z-index on it to the maximum, to make it all work out of the box as you suggested here:

I would expect portals to layer in the order in which they are made visible.

Our users told us that they sometimes needed more control over the z-index when integrating with other libs, or inside apps where you do not necessarily have control over every aspect.
With that, we trialed the idea of exposing the portal part in Dialog which no longer sets any z-index so you have full control as a user. The reception has been good and so we will roll it out to all the other relevant components soon (#1302, #1303, #1304, #1305, #1306).
In the meantime, I can see how it might be a bit counter-intuitive when using a mixture of those.
I think for now, your best solution will be to manually set the old max z-index on the dialog ones, until we update all the components, at which point you will have full control to do whatever you want.
✌

Thanks for the detailed response @benoitgrelard and apologies about the sandbox.
I did actually try setting the maximum z-index on the Dialog portal but that doesn't apply it to the correct element, from what I can tell. If this is supposed to work, I can try to get a reproducible example of what it does instead.
I also tried rendering it in a portal imported from @radix-ui/react-portal but that didn't work reliably either.
My short term workaround is simply to downgrade and wait for the broader rollout of the other portals.

I believe it should work so if you could update the sandbox to reproduce it, we can then take a look for you.

OK, I reproduced it in a sandbox: https://codesandbox.io/s/1rc2tf?file=/src/App.tsx
I needed to add another element inside the portal that sets max z-index and expand it to fill the screen. It layers correctly when the elements are opened by user interaction, but when both are set to defaultOpen, the popover layers on top of the dialog.
I'm not sure if this would actually affect us though, so it might be a suitable workaround until the new portals are rolled out more broadly.

I see the confusion.
You don't need to add an extra element.
The way it works is that whatever is wrapped in Dialog.Portal (here Dialog.Overlay and Dialog.Content) gets portalled without the need to create an extra element for the portal.
This means you can apply the styles directly to those parts like this for example:
https://codesandbox.io/s/inspiring-cloud-9e58kr?file=/src/App.tsx

but when both are set to defaultOpen, the popover layers on top of the dialog.

This however was always present before or after that change, and is due to how React renders children first, so here the dialog being a child of the popover, it will be rendered first, hence its portal will be first in the DOM.
This is unlikely to be an issue in real life as you shouldn't auto-open popover/dialogs typically.
That being said, that is one of the reasons that pushed us to open up that portal part to give more control for z-index, as once again this is something you will be able to get around with once all primitives can be controlled via their own z-index.
Hope that makes sense.

Thanks, I will close this one then because we are tracking the others separately.
✌

@benoitgrelard
Hi. So what am I supposed to do to make the dialog on top of the popover?
Can they share the div[data-radix-portal]?
https://codesandbox.io/s/dialog-inside-popover-m09fmx?file=/src/App.tsx

Hey @mattp0123,

With that, we trialed the idea of exposing the portal part in Dialog which no longer sets any z-index so you have full control as a user. The reception has been good and so we will roll it out to all the other relevant components soon (https://github.com/radix-ui/primitives/issues/1302, https://github.com/radix-ui/primitives/issues/1303, https://github.com/radix-ui/primitives/issues/1304, https://github.com/radix-ui/primitives/issues/1305, https://github.com/radix-ui/primitives/issues/1306).

All the improvements suggested above have been made, they are available in the latest release candidates, not public yet.
But if you update your example to use the latest RCs for Popover and Dialog and add the new Popover.Portal part (just like the dialog one) then it should just work out of the box (and if you need more control, you can now set your own z-index as we don't set any).
Side node: I noticed you used asChild and then attached styles to divs, etc. You can pass your styles directly to the part, and not use asChild too. All the parts render an element by default. asChild is there mostly for composition or ability to change the tag types in some fringe cases.

Just so I'm understanding correctly, are portals still layering in the order made visible?
I've got a dialog which, on button click, renders a toast. This works great, the toast appears on top of the dialog as expected. However, if you then close the dialog (and don't close the toast) and then re-open the dialog, the toast stays visible but is un-interactive (can't click to close or swipe, etc.)
We have the toast z-index set to the maximum, so I would have thought ordering wouldn't be an issue


Testing the limits of performance on Android is displaying strange effects on overall animation fps.

Description
I'm currently in the process of optimizing my app's performance on Android, and I've run into a problem that I found most strange.
For some background: My app has a storefront that uses a horizontal page-style FlatList with 5 pages, each page has 3 parallax images that take up about half the screen and animate as you swipe through the pages.
On a mid to low range Android phone this really seems to challenge the device. Animation fps really takes a hit, dropping to a constant low of 15-20 fps.
Here's what's strange: If image view size is reduced by even as little as 5% that same device will happily chug along at a constant 60 fps. There almost seems to be some sort of invisible performance threshold on the device, and as soon as you approach it, the frame rate is absolutely destroyed.
A slightly faster Android device does not have this issue, suggesting that even if I optimized for the slowest device I own by keeping that view size change, the problem would just get kicked down the road to users with a slightly slower device.
Has anyone else experienced a similar issue, or have ideas on how to work around it?
P.S. This occurs using either the image component or react-native-fast-image with low resolution and highly compressed images. Image source weight and resolution seem to have have no effect on causing/mitigating this issue.
React Native version:
System:
OS: macOS 10.15.5
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 425.63 MB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.9.0 - /usr/local/bin/node
Yarn: 1.22.5 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 29, 30
Build Tools: 29.0.2, 30.0.2
System Images: android-29 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 11.7/11E801a - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_265 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
react-native: Not Found
Expected Results
I would expect performance to get affected much more gradually like it does on iOS, not for frame rate drop by >70% the moment the device gets challenged. Note that the issue described above does not present itself on an iPhone 6 which effortlessly maintains 60 fps, suggesting that the logic is fast enough to run on a very slow iOS device. Please let me know if this isn't the case, and the above issue is expected.
Thanks for reading.
Edit:
The problem can also be mitigated by removing a single image from the entire FlatList, it really puzzles me why this change would be enough for the app to go from sub 20 fps to stable 60.

The issue can be traced back to rendering too many large sized image views. In my scenario I am drawing around 20 of these images simultaneously, all taking up close to half the viewport or more, and all having gesture based animations attached to them.
It also seems that removeClippedSubviews have no effect on reducing processing required to render pages that are far from visible, at least on Android.
I managed to mitigate the issue by making tiny performance optimizations though-out the entire app until I was able to edge far enough away from the "invisible performance threshold" for image animations to run at 60 fps.
It is unfortunate that even brand-new high-end Android devices seem to get outperformed by almost obsolete iOS devices in this area, and a great deal of effort and care have to put into making the Android experience even close to as polished as on iOS.


'Invalid error' for lsr function

Cool project! I tried executing one of the example queries against a folder on my machine and am getting an error. Wondering if it's file permissions or something?
SELECT size, count, file_extension AS "type"
  FROM (
      SELECT SUM(file_size(path)) AS size_raw, hsize(size_raw) AS size, COUNT(*) AS count, file_extension(path) AS file_extension
      FROM lsr('/Users/myusername/Downloads', 10)
      GROUP BY file_extension(path)
  ) AS subquery
  ORDER BY size_raw DESC
  LIMIT 3;

The error I get is: Invalid Error: Operation not permitted: '/Users/myusername/Downloads'
Possibly a permissions issue?
I'm using MacOS Sequoia 15.0.1 and DuckDB 1.1.2.

Hi - thank you for checking out my project!
I think I fixed the issue, but not 100%. The default option for ls and lsr is to skip files that would cause anOperation not permitted error. This can be disabled with the last parameter of the function, e.g. ls(path, skip_permission_denied). I submitted an update to the duckdb community extension repository, but it could take a bit for the update to be installable via UPDATE EXTENSIONS.

 The new update should be out now; you can update the extensions using UPDATE EXTENSIONS.


Depends on "future"

pip installed untwisted  as dependency of "vy"

Error:
File "/home/eliot/.local/lib/python3.5/site-packages/untwisted/core.py", line 6, in
from future.utils import itervalues
ImportError: No module named 'future'

pip install future fixed this
So, untwisted should depend on 'future' ?

Yes, it works for both python2 and python3, i'm planning to get rid of python2 support soon, for now, it is necessary to have future package installed.

I haven't added that in the requeriments.txt file i'll be adding that soon.


Remove xDai transfer fee from "Max" helper button calculations

Currently, when you click "Max" to exit all the sunDai you have, it will put in the value 0.01 less (accounting for xDai fee). Let's remove that

obsolete. The helper is not used anymore (the code is here though)


update tabBarComponent to tabBar

tabBarComponent doesn't exist in the react-navigation props, it's tabBar only.
For now, it compile to this and it doesn't work:
return React.createElement($$Navigator.make, {
              children: children,
              tabBarComponent: CustomTopTabBar$TopTabBar,
              tabBarOptions: tabBarOptions
            });

Thank you!

No, thank YOU!


Issue: Unable to use USB A host port, Cannot enable USB Host 5V Power

Prerequisites
Please check the following before posting an issue / bug report.

[ ] I am running the latest version of the firmware found HERE
[x] I have checked the documentation HERE and found no answer
[x] I checked to make sure that this issue has not already been filed HERE
[x] I am reporting the issue to the correct repository

Context

Firmware Version: CMake #1063
Name of device: RP2040 Feather USB A Host
Link to where you purchased the device: https://www.adafruit.com/product/5302
Is this a custom build?: No
Operating System: 6.4.1-arch1-1
Browser: Chromium

Expected Behavior
Use the Keyboard Host Configuration Addon with the RP2040 Feather USB A Host. Plug a keyboard into the USB A host port, and use the keyboard as a controller.
Current Behavior
Keyboard is unable to receive power from the RP2040 Feather USB A Host and the controller does not respond to keyboard inputs. When board pins are shorted, it does respond appropriately.
Steps to Reproduce

Flash RP2040 Feather USB A Host with Pico .uf2 file from CMake #1063
Press and hold GPIO 17 (located on USB Host port) and reset to go into WebConfig
Disable addons and remap pins appropriately to free up GPIO 16, 17, and 18 for the USB A Host

Enable Keyboard Host Configuration
Set D+ to 16 (Automatically sets D- to 17)
Restart Controller
Plug in keyboard into USB A Host
Attempt to input using keyboard (fails)

Proposed Solution
Include a field under Keyboard Host Configuration labelled "USB Host 5V Power Enable" that is set to -1 by default (disabled). When set to an appropriate GPIO pin, it will pull the pin high, enabling the use of the USB A host port.
Screenshots & Files

Adafruit Feather RP2040 with USB Type A Host Pinouts

The USB host capability is controlled with the following pins:
USB Host Data Plus (D+) - GPIO 16. In Arduino, this pin can be accessed with PIN_USB_HOST_DP.
USB Host Data Minus (D-) - GPIO 17. In Arduino, this pin can be accessed with PIN_USB_HOST_DM.
USB Host 5V Power - GPIO 18. In Arduino, this pin can be accessed with PIN_5V_EN.

The 5V LED is a green LED, located directly below D6/GPIO6 next to the USB-A port. It indicates whether the USB host 5V power is enabled. The 5V output is provided by a 5V boost converter, based on the TPS61023, with up to 1 Amp peak output for USB peripheral power.

Current Workaround:

Enable the Extra Button Add On
Assign pin 18 to any button you would not use ("None" does not work)
Restart board


please publish new version of graphlib to npm

This fix for lodash was merged a while back but sadly has not yet been released to npm: https://github.com/cpettitt/graphlib/pull/59
@cpettitt think you could publish a new version? ❤
Related https://github.com/cpettitt/graphlib/issues/58

Should now be up as v2.1.1


Ability to hide tasks from dep list but still allow them to be run

Q
A

Issue Type
Feature Request

Deployer Version
6.3.0

Local Machine OS
Ubuntu 18

Remote Machine OS
Ubuntu 18

Similar to closed issued #212 it would be useful to hide tasks from the dep list but also be able to run them independently.
A typical scenario when this would be useful is when a deploy falls over because one of its sub tasks (set to private) fails to complete. I then need to complete the remaining tasks one by one and this currently involves removing setPrivate from each task, running them and then reinstating setPrivate.
This could be achieved by allowing tasks to be run irrespective of whether setPrivate is set or by providing a setHidden option instead.
Another alternative (though I have a feeling this won't technically be possible) would allow a task to be started from a particular sub task (skipping the ones already successfully completed) with a syntax like this:
dep task --start=sub-task
e.g. dep deploy --start=deploy:update_code
Great tool by the way.

Done in master!


IPv6 networking not working in Kubevirt VM

/kind bug

This is related to https://github.com/kubevirt/kubevirt/issues/1017
What happened:
# ping -6 google.com
ping: google.com: Name or service not known
# ping -6 2a00:1450:4009:809::200e
connect: Network is unreachable

Getting IPv6 Network unreachable
We have a IPv6 interface for Kubevirt VM but it's not working when we try to use IPv6 to reach out to other services in cluster or to the web.
What you expected to happen:
I would expect ping to work on IPv6 and resolve
How to reproduce it (as minimally and precisely as possible):
Followed this to get a basic interface setup: https://kubevirt.io/user-guide/docs/latest/creating-virtual-machines/interfaces-and-networks.html
cc: @fabiand

hey, thanks for reporting - but I think this is known, but:
Please share your VM definition.
Did oyu use a multus backed or pod-network?
In KubeVirt the pod network is known to not support IPv& (yet) - even if
the underlying Kubernetes is configured in a native IPv6 way.
All in all IPv6 support is something we want to add - no question.

Hi, thanks for a quick answer!
We're using a pod network, happy to change if there is a workaround.
VMIRS definition
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachineInstanceReplicaSet
metadata:
  name: agent-replica-set
  namespace: app-agents
  labels:
    app: app-agents
    role: replicaset
spec:
  replicas: 24
  selector:
    matchLabels:
      role: agent
  template:
    metadata:
      name: k8s-agent-
      namespace: app-agents
      labels:
        app: app-agents
        role: agent
    spec:
      domain:
        cpu:
          cores: 4
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          - name: emptydisk
            disk:
              bus: virtio
          - disk: {}
            name: agent-config-disk
            serial: CONFIGDISK
          interfaces:
          - name: default
            bridge: {}
        firmware:
          bootloader:
            efi: {}
        resources:
          requests:
            memory: 32Gi
      networks:
        - name: default
          pod: {}
      livenessProbe:
          initialDelaySeconds: 300
          tcpSocket:
            port: 8888
      terminationGracePeriodSeconds: 30
      volumes:
      - containerDisk:
          image: path_to_an_image
        name: containerdisk
      - name: emptydisk
        emptyDisk:
          capacity: 64Gi
      - configMap:
          name: agent-config
        name: agent-config-disk

Ah, pod network.
If you are flexible, then I'd recommend to use a multus backed L2 interface.
@phoracek might be able to help our here

@bharatnc first of all, I'd advise you  to change bridge: {} to masquerade: {} since there are known issues with the bridge binding. What network plugin are you using (Flannel/Calico/...)? That may have an affect on IPv6 for pods in general. I have to check what is the state of our IPv6 support with masquerade. As Fabian said, if you could, try to use Multus and L2. I can recommend Linux bridge CNI to you https://github.com/kubevirt/cluster-network-addons-operator#linux-bridge. Happy to discuss any details if you are interested.

@phoracek  thank you!
To answer your question: >  What network plugin are you using (Flannel/Calico/...)?
We use Calico as our Network CNI. I guess it would be interesting to use IPv6 with masquerade to check if that makes a difference. But, like you have mentioned, it would be great if you can check if this is possible at all.
It would be nice if we can have native support without additional plugins on the cluster, just from the operational perspective (upgrades, updates etc). With that being said, we would be happy to explore the possible options.
I also have a question for you:
Is there a major blocker that makes it difficult to add IPv6 support to Kubevirt. That would be something that we would wish to explore and contribute to!
Thank you!

@bharatnc IPv6 doesn't seem to be supported on masquerade at the moment https://github.com/kubevirt/kubevirt/blob/a523d9ad55fb1cd6145bd2dc49a94164f34a18a2/pkg/virt-launcher/virtwrap/network/podinterface.go#L606 (we don't setup anything in IPv6 tables) and neither it is on default pod interface with bridge https://github.com/kubevirt/kubevirt/blob/a523d9ad55fb1cd6145bd2dc49a94164f34a18a2/pkg/virt-launcher/virtwrap/network/podinterface.go#L168 (we don't pass IPv6 addresses from pod to VM).
The only option now seems to be use secondary interface with L2.
We can investigate possibility of enabling IPv6 on the default pod interface. @fabiand what do you think?

@phoracek AFAIR Kubernetes itself had issues with proper IPv6 support in the recent past. https://github.com/kubernetes/enhancements/issues/563 We can of course try and see whether it works but I expect the road to be bumpy.

@phoracek AFAIR Kubernetes itself had issues with proper IPv6 support in the recent past. kubernetes/enhancements#563 We can of course try and see whether it works but I expect the road to be bumpy.

@booxter I think that PR is for using dual stuck on a single cluster and not only ipv4 or ipv6.
ipv6 is supported by kubernetes you can use calico as the cni provider that support ipv6

/remove-lifecycle stale

@kacpercf  closing this issue out as this is no longer our priority I think. Pleas feel free to reopen if necessary.

@bharatnc IPv6 should be supported soon via https://github.com/kubevirt/kubevirt/pull/3112 in case somebody will need it.


Importing on the renderer breaks on Electron forge.

Describe the bug
It is mentioned once https://github.com/hardchor/electron-redux/issues/96, when using newer version of Electron or electron forge all import { ipcRenderer } from electron break whenever called from the renderer process.
To Reproduce
Set up readme example with Electron forge & create-react-app instead of manual webpack
Expected behavior
compile and run
Screenshots
see #96
Desktop (please complete the following information):

OS: MacOS 10.14.3
Browser: Chrome
Version: 1.4.0

Additional context
tried replacing all impport {ipcRenderer } from 'electron' calls to :
const _electron = window ? window.require("electron") : require("electron")

in all classes still somewhere the error persisted.

@adhambadr I just published 1.5.1. Could you check if that fixes your issue?

Feel free to reopen if problem persists


Use docker swarm/config as a kv-store

Do you want to request a feature or report a bug?
Feature
What did you expect to see?

One thing to note, this is only for storing the acme data.  Not the full config which should just be replicated as command parameters in the yml.
Rather than setting up another KV store inside docker swarm environment.  Why not just use docker config APIs to actually get and store configurations assuming the instance has /var/run/docker.sock mounted.
Using /proc/self/cgroup will allow you to get the ID of the container https://stackoverflow.com/questions/20995351/docker-how-to-get-container-information-from-within-the-container#25729598
then use service labels to update the "current config" to use.  Only service labels are mutable in Docker services.
So what I am thinking is one of the labels designates a node that is the "master" which is responsible for the updates.  If it detects that no node is the traefik master (i.e. the container ID designated is no longer running) it will elect another one automatically.
The update process does the following only on the master

let [config-uid] be a unique id for the configuration data
let [old-config-uid] be the ID for the current configuration data which is the label "config.uid".  Can be nil
create config [config-uid] with the acme data
set the label "config.uid" to [config-uid]
delete config [old-config-uid]
trigger a docker service update --force  for the nodes
once stable reelect the master (since all the containers are restarted).

Hi  @trajano,
First of all thanks for your interest in Træfik.
Unfortunately I will close this issue because this is something that we don't want to do due to a security concerns.
Today Træfik use the docker socket to watch events in read only. And we don't want to give write access to traefik on the docker socket.


Security armoured winter jackets

About the PR

Replaces instances of security winter jackets with armoured versions that use basic armour vest values (see media for values).
Replaces the security winter jacket in the uniform printer recipe with an unarmoured version.
Grammatical changes to descriptions of HoS, warden and security unarmoured winter jackets.

Why / Balance

Based on #18170 and addresses concerns from https://github.com/space-wizards/space-station-14/pull/18170#issuecomment-1685619800.
Although lizard security officers were already disadvantaged by cold temps, currently all races in security are affected by temperature slowdowns following #29692. Adding armour to security winter jackets brings them to parity with their warden and HoS counterparts.
Technical details

yml changes only

Resources/Prototypes/Entities/Clothing/OuterClothing/wintercoats.yml (adds new armour parent to security winter jacket, added security winter jacket without armour with new ID)
Resources/Prototypes/Entities/Structures/Machines/lathe.yml (changed uniform printer to only print unarmoured security jacket)
Resources/Prototypes/Recipes/Lathes/clothing.yml (changed recipe IDs to print unarmoured security jackets)

Media

Security armoured winter jacket and sources

Security (unarmoured) winter jacket and sources

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl:

tweak: Security winter jackets in SecDrobes and loadouts are now armoured with basic vest values.
tweak: Uniform printer now prints unarmoured security winter jackets.

Can we get armored berets too lol

isn't durathread only meant to be used for command's clothes?

isn't durathread only meant to be used for command's clothes?

Its just cloth with plastic, lots of stuff uses it in the fab I recall+ medibeds.

Can we get armored berets too lol

If you provide an armoured sprite then maybe (someone on Discord said they'd sprite an armoured winter jacket)

That would be me, still need em?

Jackets should not have the full protection of a bulletproof vest to give a jacket. If you want to increase the protection, then make it a little lower. Even a greatcoat or a hos/warden jacket do not have such protection

Jackets should not have the full protection of a bulletproof vest to give a jacket. If you want to increase the protection, then make it a little lower. Even a greatcoat or a hos/warden jacket do not have such protection

Their jackets very much have full protection, detective coat loses explosive protection though.

Pretty sure det coats provide insulation, as they are bane to my 5 second freeze cryopods otherwise. I think even non-winter warden/hos coats do but I might be stripping those out of muscle memory at this point.

I've been cryo tanked before with the detectives coat.
It didn't prevent my body temperature from dropping

I've been cryo tanked before with the detectives coat. It didn't prevent my body temperature from dropping

Non-EVA clothing won't stop you from dropping temperature in well set cryopod but insulation still can greatly increase time before medicine can work, especially boots and coats, scarfs and other clothing have minimal effect if theres any coefficient.

I should note my body temperature dropped extremely fast

this should be merged and then fix the issues tbh

Yeah I'm planning to make another PR that resolves most of these issues, as seen by all the commits that I had to revert

yeah good idea


How can i add headers

How can i add headers for the sheet

I think the headers generally take the shape of your data's Object keys


Duplicate keys, enigmatica 6

was hoping this would work with enigmatica 6, but it doesn't when I switch the controls to my preferences. This mod also won't let me remove the controller keybinds that I don't like.
crash-2021-10-15_21.58.55-client.txt
another log
crash-2021-10-17_11.59.48-client.txt
:

[crash-2021-11-01_08.52.24-client.txt](https://github.com/MrCrayfish/Controllable/files/7462728/crash-2021-11-01_08.52.24-client.txt
crash-2021-11-02_08.22.36-client.txt
)
Some more crash logs


Fix CI failures related to Ansible Galaxy

This PR bumps the minimum Python version to 3.8.

ah, seems like 2.16.6 requires a version newer than 3.9

Looks like according to the ansible-core lifecycle[1], we could use ansible-core 2.15 which supports python3.9-3.11 but it goes EOL in November 2024. Maybe ansible 2.16 and >=python 3.10 is a safer bet?
Also I think ansible collections need to be upgraded as well - https://github.com/ceph/teuthology/blob/main/requirements.yml
[1] https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix

Superseded by  #1939, which uses 3.10 instead of 3.9 at @VallariAg's suggestion


feat: add iTerm theme

Thanks for the great theme! It's been a while since I found something so pleasant and usable.
This PR adds a simple port of the Alacritty theme to iTerm.

Hey there, thanks for the pr and the kind words!
I think Alacritty is a bit of a special case since it seems to be a bit brighter than Kitty for example but let me know if it's different for you. I made the Kitty colors a bit brighter because of this so I would recommend following those.
One more thing is that I think the normal Nord theme for iTerm has some pretty nice defaults, so I would build off starting from that for some of the options like cursor guide and you can do so too if you'd like!

I'll also tag @shMorganson since they seemed to have an iTerm theme too and might have some suggestions!

Got it. I tweaked it to use the original Nord theme as a base and the colors from the Kitty theme instead. On my screen, Kitty and iTerm look identical.
I don't really use the cursor guide, so I'm not sure what it's supposed to look like, but I left it alone for now.

This looks great, thanks again!


Add documentation that input leaves should be strings?

I had an issue using merkletreejs on the frontend, as Webpack (a common dependency in React) has a latest version that is incompatible with Buffer.
It seems that this issue has been experienced by others.
https://stackoverflow.com/questions/70530052/keccak-js-uncaught-refereanceerror-buffer-is-not-defined

Closed - I misunderstood the library documentation. The leaves should be an array of strings!

I had an issue using merkletreejs on the frontend, as Webpack (a common dependency in React) has a latest version that is incompatible with Buffer.
It seems that this issue has been experienced by others. https://stackoverflow.com/questions/70530052/keccak-js-uncaught-refereanceerror-buffer-is-not-defined

There's a fix for this issue for those who stumble upon it later: https://stackoverflow.com/questions/68707553/uncaught-referenceerror-buffer-is-not-defined


New Contribution

Contributor: [woary]
SSH Public key: [SHA256:MSBCBkMq4o0OAYSDUmPQLLpUYgKRSQ219R780dKCFgk]
Attestation: [woary]

Hi Team, I am ready to contribute, let me know if I can start now


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.17 to before v5.14.15",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c3895391df385c6628638f014c87e16f5e2efd45",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ec93d4a439c3a619b6682ba5778dc885d1460d3e"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "c3895391df385c6628638f014c87e16f5e2efd45",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "ec93d4a439c3a619b6682ba5778dc885d1460d3e",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "mm, slub: fix mismatch between reconstructed freelist depth and cnt\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.14.15 by commit ec93d4a439c3a619b6682ba5778dc885d1460d3e, it was introduced in version v4.17 by commit c3895391df385c6628638f014c87e16f5e2efd45. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002110


Fix m_current_bytes accounting in DynamicPoolMap

Addresses an issue where the pool will never coalesce, since getCurrentSize will never return 0.

LGTM

Did we test that this really solves the issue? I can't remember, but did we use the replay file and the rounded_bytes fix to check? Also, would it be worth it to add a gtest case that checks for this?

Did we test that this really solves the issue? I can't remember, but did we use the replay file and the rounded_bytes fix to check? Also, would it be worth it to add a gtest case that checks for this?

Yup, I ran it against the replays and verified it fixed it. I'm not sure the best way to write a test. I think we eventually need a replay-based system for more complex issues like this.

This looks good. Does DynamicPoolList have the same problem?
We obviously don't seem to have a gtest for this particular failure since no tests were ever really failing. Should we create one?

I have added a test - verified that it failed for develop, and is fixed by this PR.

LGTM

LGTM


jetbrains: autocommit updates

Description of changes
With this PR, when the jetbrains IDEs are being updated, the update script will automatically commit the changes. This has the advantage of consistent commit messages.
If there is just a single Product update, the commit message looks like this:
jetbrains.phpstorm: 2023.1.4 -> 2023.2

If there are multiple Product updates, the commit message looks like this:
jetbrains: 2023.1.4 -> 2023.2

jetbrains.phpstorm: 2023.1.4 -> 2023.2
jetbrains.rider: 2023.1.4 -> 2023.2

The plugins.json file is committed separatly as
jetbrains.plugin: update

This was suggested here.
//cc @Janik-Haag
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Btw. @Janik-Haag I hope I cleared the confusion a bit. If not, here is a more high-level explanation:
The recent commits I did when updating the jetbrains IDEs followed the form:
<subject>

<list of updates>

This form is similar to the PRs, which have naturally a subject. See the Commits here, here as Examples. And even Commits from others seem to include just the Subject line: here and here.
The inconsistency in the commit messages is IMHO a good reason for this Change.
If we decide to drop the subject line and just list the updates, this PR would be much simpler (no need to calculate min/max Versions etc).
In this PR I went with the first approach. Thus the complexity.
Please let me know if there is anything unclear.

Result of nixpkgs-review pr 247240 run on x86_64-linux 1


Localization Auth.storyboard

Hi
I got 2 Errors when I Localization Auth.storyboard
IB Designables Group
1- /Scenes/Auth/Base.lproj/Auth.storyboard: error: IB Designables: Failed to render and update auto layout status for QMWelcomeScreenViewController (ncs-B4-uAJ): Failed to load designables from path (null)
2- /Scenes/Auth/Base.lproj/Auth.storyboard: error: IB Designables: Failed to update auto layout status: Failed to load designables from path (null)
Thanks for your support
Regards
Allan

@gbr33, This issue is not related to our SDK and Q-municate. This is a Xcode's bug.
Just

remove derived data.
restart the Xcode for now.
clean project
for now.


Support more wallet types

Maybe a continuation of https://github.com/GenesysGo/shadow-drive/issues/10
It would be useful if this library could support more wallet types, such as the ones in @solana/wallet-adapter-wallets:
BaseWalletAdapter, BaseSignerWalletAdapter, BaseMessageSignerWalletAdapter
At the moment the recommendation is to use useAnchorWallet from @solana/wallet-adapter-react which seems restrictive.

I'm using this TypeScript workaround for now:
const wallet = new PhantomWalletAdapter(); // BaseMessageSignerWalletAdapter
await wallet.connect();
const drive = await new ShdwDrive(connection, wallet as any).init();


Error is thrown when the example is run.

When running the example on Mac OSX High Sierra, it throws an error:

Kims-MacBook-Pro-401:example kimgysen$ npm start

<EMAIL_ADDRESS>start /Users/kimgysen/Documents/zwoop/website/history/webpack-hot-server-middleware/example
npm run start:express

<EMAIL_ADDRESS>start:express /Users/kimgysen/Documents/zwoop/website/history/webpack-hot-server-middleware/example
node express/index.js

internal/modules/cjs/loader.js:611
throw err;
^
Error: Cannot find module 'require-from-string'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:609:15)
at Function.Module._load (internal/modules/cjs/loader.js:535:25)
at Module.require (internal/modules/cjs/loader.js:663:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (/Users/kimgysen/Documents/zwoop/website/history/webpack-hot-server-middleware/src/index.js:5:27)
at Module._compile (internal/modules/cjs/loader.js:734:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:745:10)
at Module.load (internal/modules/cjs/loader.js:626:32)
at tryModuleLoad (internal/modules/cjs/loader.js:566:12)
at Function.Module._load (internal/modules/cjs/loader.js:558:3)

Node version: 11.9.0
I installed the packages using npm install (not using yarn).
I can see the npm package require-from-string in then node_modules folder though.
Note: if the project is not supported anymore, you should mark it as deprecated, as we don't want this to end up in production otherwise.

Issue is related to webpack-hot-sever-middleware. I mistakenly added the issue here; opened a ticket there now.


chore(avm): make stats thread safe

Needed because some things are calculated in parallel.

#7393  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @fcarreiro and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:mint_public): 73.2 (-79%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 92.0 (+132%)
avm_simulation_time_ms (Token:transfer_public): 48.4 (+32%)
avm_simulation_time_ms (Token:_increase_public_balance): 14.8 (-76%)
avm_simulation_time_ms (FPC:pay_refund_with_shielded_rebate): 163 (+44%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,728 (-1%)
1,547 (-1%)
708 (-1%)
764
769 (-1%)

proof_construction_time_sha256_30_ms
11,734 (-1%)
3,183
1,410 (+1%)
1,447
1,471

proof_construction_time_sha256_100_ms
43,830 (-1%)
11,789 (-2%)
5,583 (+2%)
5,432
5,364

proof_construction_time_poseidon_hash_ms
79.0 (+1%)
34.0
34.0
59.0
90.0 (+2%)

proof_construction_time_poseidon_hash_30_ms
1,520
417
201 (-1%)
227 (+2%)
268

proof_construction_time_poseidon_hash_100_ms
5,616 (-1%)
1,525
678
730
748 (-1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,452
9,466
9,452

l1_rollup_execution_gas
613,480
613,645
613,782

l2_block_processing_time_in_ms
757
1,416
2,726 (+1%)

l2_block_building_time_in_ms
12,870 (-1%)
25,429 (-1%)
49,558 (-1%)

l2_block_rollup_simulation_time_in_ms
12,870 (-1%)
25,429 (-1%)
49,558 (-1%)

l2_block_public_tx_process_time_in_ms
10,834 (-1%)
23,208 (-1%)
47,337 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,009
9,961

node_database_size_in_bytes
12,468,304
16,175,184

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
79.8
13,790

GasToken:set_portal
13.8 (-19%)
3,339

Token:constructor
100 (-4%)
23,692

FPC:constructor
73.4 (-1%)
13,592

GasToken:mint_public
61.0 (-3%)
10,158

Token:mint_public
:warning: 73.2 (-79%)
19,034

Token:assert_minter_and_mint
:warning: 92.0 (+132%)
12,925

AuthRegistry:set_authorized
33.3 (-2%)
7,812

FPC:prepare_fee
99.5
15,062

Token:transfer_public
:warning: 48.4 (+32%)
31,218

FPC:pay_refund
125 (-5%)
25,260

Benchmarking:increment_balance
1,309 (-1%)
15,267

Token:_increase_public_balance
:warning: 14.8 (-76%)
15,006

FPC:pay_refund_with_shielded_rebate
:warning: 163 (+44%)
26,347

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.155 (-1%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.601
0.513
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.0 (-1%)
75.9 (-1%)
131
245 (-2%)
472 (+1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.490 (-1%)
0.467 (-1%)
0.451
0.444 (-1%)
0.441 (+1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.6
111
183 (+1%)
353 (-1%)
695 (+1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.503
0.500
0.485 (+1%)
0.478
0.477

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
72.8
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.519
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
74,082
667,868

Transaction size based on fee payment method
| Metric |  |
| - |  |

Merge activity

Jul 9, 9:35 AM EDT: @fcarreiro merged this pull request with Graphite.


Accurately show status when downgrading dependencies

What does this PR try to resolve?
A few times now I've ran into issues where Cargo ends up downgrading a dependency in order to satisfy a pinned dependency somewhere in the dependency graph. Unfortunately this is not clear in the output of cargo update, which just shows all the changed dependencies as Updating.
References:

#5702
Finding a pinned dependency edge
https://github.com/tokio-rs/axum/issues/1814

How should we test and review this PR?
This is a small change that tries to make dependency downgrades stand out more in the output of cargo update. I have not added any new tests since the existing tests seem to cover this functionality.
Some tests still fail, these refer to Git dependencies. I'm honestly not sure how to handle these, so I'd like to get some feedback on this before I fix those tests up. Git commits form a DAG, so one option is to see if the new commit is an ancestor of the old one (mark as "updating"), if the old commit is an ancestor of the new one (mark as "downgrading"), or neither (could be from parallel branches) we could compare based on timestamp in that case.
To do

Fix up tests for Git dependency updates

Looks pretty good! I am totally fine with the yellow color. People usually bikeshed on UI-related stuff, so let's do a quick FCP here.
@rfcbot fcp merge
This is relatively small in terms of code changes, but a big help in console output. The graph below shows the UI change. Feel free to block this if you have any thought.

For reference, this is on a default color scheme:

Thanks. I forgot I use a customized one 😅.
Just saw the CI failure on the git dependencies. I think if a downgrade is not really meaningful to a source (e.g., git hash changed), we can just display the original “Updating” status.

I've updated the change to only use Downgrading when removed[0].version() is specifically larger than added[0].version(), this seems to keep the Updating behavior for the case where there is no clear distinction (such as git dependencies).

Thanks every for the review. Let's go forward!
@bors r+

:hourglass: Testing commit 20a5d2b82ff22221857d9b31e4886b8d68282b6e with merge 4e11cae55dfb829b6a82010e9cd6199852ab307e...

:broken_heart: Test failed - checks-actions

:hourglass: Testing commit 20a5d2b82ff22221857d9b31e4886b8d68282b6e with merge 9282cf74a38757c217d122bbf998afcda2626595...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 9282cf74a38757c217d122bbf998afcda2626595 to master...


Does $_FILES really need wp_unslash?

Bug Description
I'm using wp_handle_upload in one of my plugins. PHPCS complains about the $_FILES slice not being run through wp_unslash. However, wp_magic_quotes does not add slashes to $_FILES.
Running an apparently superfluous wp_unslash on $_FILES is harmless on POSIX platforms, but breaks file uploading on Windows.
Minimal Code Snippet
$mimetypes = [
	'jpg|jpeg|jpe' => 'image/jpeg',
	'gif'          => 'image/gif',
	'png'          => 'image/png',
];
$args = [
	'mimes'                    => $mimetypes,
	'test_form'                => false,
];
$avatar = \wp_handle_upload( \wp_unslash( $_FILES[ 'avatar' ], $args ) );

Error Code
WordPress.Security.ValidatedSanitizedInput.MissingUnslash
Environment

Question
Answer

PHP version
7.3.6

PHP_CodeSniffer version
3.4.2

WPCS version
2.1.1

WPCS install type
Composer project local

Tested Against develop branch?

[ ] I have verified the issue still exists in the develop branch of WPCS.

Seems legitimate. If WP doesn't touch the $_FILES superglobal to add slashes, then there shouldn't be a need to give a violation if it is accessed without unslashing.

Any update on this?

on a sidenote: $_FILES[...]['tmp_name'] should not require sanitizing nor unslashing either, as that's set by PHP internally with random alphanumeric characters.

on a sidenote: $_FILES[...]['tmp_name'] should not require sanitizing nor unslashing either, as that's set by PHP internally with random alphanumeric characters.

@kkmuffme  As all array entries in superglobals are mutable, it can be changed, so as far as I'm concerned, it should still be sanitized.


0.2.0 Release Candidate

This PR should not be merged yet, it's a review checklist.
This PR can now be merged.
This release adds/changes the following:

The fuzzer is now a SIMICS package with number 31337
There is no longer a frontend binary, SIMICS itself is the frontend
Added validated architecture support for x86 and RISC-V (32/64)
Added validated support for kernel and user-space fuzzing
Enhanced test infrastructure
Stability enhancements
Windows support
So much more!

This can be merged. There are still a couple things to do for docs and CI for the release (plus we need to manually trivy scan some too-large containers), but we can just tick the release once they're done instead of tacking even more minor fixups onto this PR.


Generate the Go datastructure

It would be good to be able to generate the Go struct from the Nix module to guarantee that they stay in sync.
The schema defined in mkDevShell/options.nix is the canonical version and devshell/config.go needs to be kept in sync with it. To avoid unnecessary discrepancy, it would be great if the latter could be derived from the former.

Breadcrumb:

https://github.com/dave/jennifer/
https://github.com/aloder/tojen

Another option to add here is rycee/nmd.
I'm using it to convert modules nix to markdown files and document some modules
Something like this:
# simplified from https://github.com/cruel-intentions/devshell-files/blob/master/modules/docs.nix
let
  modules = [
    ./myModulePath.nix
    {
      _module.check = false;
      _module.args.pkgs = lib.mkForce (nmd.scrubDerivations "pkgs" pkgs);
    }
  ];
  docs = mnd.buildModulesDocs {
    channelName     = "";
    docBook         = {};
    mkModuleUrl     = path: path;
    moduleRootPaths = [ ./. ];
    modules         = modules;
  };
in (import ./docs/markdown.nix) docs.optionsDocs

# simplified from https://github.com/cruel-intentions/devshell-files/blob/master/modules/docs/markdown.nix
moduleDocs:
let
  optionToMd = opt:
    ''
      ## ${opt.name}

      ${opt.description}
      #### type
      ${opt.type}

      ${opt.example}

      ${opt.default}
    '';
in builtins.concatStringsSep "\n" (builtins.map optionToMd moduleDocs)


Using actor report reminders error

I used actors, and when I set up the app in k8s, there were some errors about  reminders, like these:
error getting reminders for actor type ChatRoom: (Unauthorized) there are no users authenticated" app_id=chatroom instance=chatroom-b4dfcd6c-4r58r scope=dapr.runtime.actor type=log ver=1.3.0
error getting reminders for actor type User: (Unauthorized) there are no users authenticated" app_id=chatroom instance=chatroom-b4dfcd6c-4r58r scope=dapr.runtime.actor type=log ver=1.3.0
Since I didnt' use reminder, why this error could happen? What's the meaning and how to fix it ?
Thanks a lot.

@halspang - can you help investigate this?

@mjtansin - What statestore are you using in your application? Also, does the app continue to run afterwards? Or are all actor functions broken?
The error appears to be based on your statestore's authentication model. The reason you may be seeing it is hard to say at first, but when an actor runtime starts up, it tries to fetch all reminders for the actors. This is because reminders are persistent and must always be accounted for.

Hi!
I thank you are right. I use mongo replica set as statestore. When actors store state value, it will throw exception for authentication problem.  Usually, to login to a mongo db we need to set authentication db, like
mongo --authenticationDatabase  -u  -p
but it seems mongdb component dosen't offered the opportunity to set that db.
When I change statestore to redis, all errors will disppear, so it's not dapr's bug.
Best regards,

发件人: halspang @.>
发送时间: 2021年9月28日 18:48
收件人: dapr/dotnet-sdk @.>
抄送: mjtansin @.>; Mention @.>
主题: Re: [dapr/dotnet-sdk] Using actor report reminders error (#737)
@mjtansinhttps://github.com/mjtansin - What statestore are you using in your application? Also, does the app continue to run afterwards? Or are all actor functions broken?
The error appears to be based on your statestore's authentication model. The reason you may be seeing it is hard to say at first, but when an actor runtime starts up, it tries to fetch all reminders for the actors. This is because reminders are persistent and must always be accounted for.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dapr/dotnet-sdk/issues/737#issuecomment-929530060, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACN73NT7QPC4BTWSUIYZT43UEIEXRANCNFSM5CDIBBJQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@mjtansin - Gotcha, do you need anything else from this ticket then?
@rynowak, if they don't can you close it? I don't have permission yet.

No activity here for a while, and I have permission to close things now.


Fix CI to lint tests as well

See this comment by @CreepySkeleton:

cargo clippy --tests -- -D warnings

Be aware that --tests checks only the tests apparently, not the lib itself, so you're going to need two invocations:
cargo clippy -- -D warnings
cargo clippy --tests -- -D warnings

I had a bit of headache trying to figure it out four months ago. Maybe it has changed, don't know.

File to change is here: https://github.com/lambda-fairy/maud/blob/master/.travis.yml


How to delete voice signature?

Looking at the specs from https://signature.centralus.cts.speech.microsoft.com/UI/index.html#/Signature/Signature_GenerateVoiceSigatureFromByteArray
It looks like it only creates signature. How do I delete a voice signature? And do Microsoft store the audio forever? Where is the data privacy for this one?

Thanks for the questions. @sarahlume could you comment on this ?


debian packaging: Something is causing scripts to show up in /usr/local/bin too

These don't get overwritten by later updates which makes them a pain to deal with. Where are they coming from!?

This appears to be happening when setup.py develop is run on an application that depends on baseplate. It's also causing pshell and friends (from Pyramid) to be installed. Need to figure out why that is now.

develop appears to run through the install step on all the deps which results in the script installation in /usr/local/bin. I'm fixing this on the puppet side by adding --no-deps to the develop step because we have the deps installed already by dpkg.


skip or offset

I could not find offsets (skipping to list the first n items (as they may be rendered in full lengh just above the list).

You can use slice FQ operation to make an offset. Is this what you want or do you want something specific in the package itself?

Maybe it makes sense to make it part of the package itself, just for convenience?

Thanks for pointing me to slice. The linked doc mentions "offset" but gives me no idea how to use it.

So to get 10 items offsetting by 5, you'd write smth like .slice(5, 10)

I've added this feature, see linked commit. Is this the kind of thing which you wanted?

Thank you for the slice example.


Remove Reporter + Add browser/os detection + No longer import library everytime

Fixes:

https://github.com/ciena-blueplanet/ember-cli-visual-acceptance/issues/2

Approved - looks good.  Would you mind adding the README updates as well?

@sglanzer Whoops forgot branches were a thing. So also in this PR is the fix for container resizing since html2canvas just scales the image. And adding the container resolution to the image path

Approved with the new changes, nice work!


Link environment to existing Lakehouse in Fabric

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric#link-to-fabric-from-power-apps
May or may not need a resource.  Could be solution aware.  Related to https://github.com/microsoft/power-platform-terraform-quickstarts/issues/35

Maybe a relevant way to create the fabric capacity if we need to build a sample of this capability https://www.remcohooijer.nl/2024/03/11/deploying-fabric-capacity-with-terraform/


Docker environment for run tests + enhancement for ssl_handshake

I've prepared Dockerfile which enable to run tests in isolated environment with all needed tools. I hope it helps newbies like me to verify their PR.
While i was running
make longtest

i noticed some undeterministic behaviour (some tests ie. auth_https.tdir sometimes failed due to connection timeout to petal).
I found some problem in util/netevent.c which cause switching to reading phase before send http request due to incomplete ssl_handshake.

Hi, thanks for taking the time for this!
I have some comments for changes before being able to merge.
If something is not clear let me know.
I was hunting an ssl bug in windows and came to the same conclusion for the ssl handshake. May I ask how you stumbled upon this?

Thank You for review my PR. I observed problem with handshake while launching longtests in docker, i started digging and found ssl connection was waiting for response despite request wasn't send due to not finished handshake.
I merged actual master to my branch and verified that change ca67691 fixed also above problem - so i've reverted my changes in netevent.c. I've adjusted my code to other suggestions. Please let me know if i can improve something else.
Best regards.

Thanks, looks good to me!
Currently we are in code freeze for the upcoming release but I will merge this right after that.
Something that just came to mind, I am not sure about the portability of the -E option to grep. In most man pages I find online I see support for it but we will find out when testing on different platforms for the release. Worst case we convert it back to regular regular expression.

Thanks for information :)


Azure function concurrency

I'm working with Azure functions. I've got a function triggered by a storage queue, where I put a large number of messages (O(1000)) in bursts. I want them all to execute in parallel, but I'm currently throttled by the batch size of 32.

The HTTP trigger offers unbounded paralleism, but I want to be able to invoke functions asynchronously. That is, I want to be able to run some code that triggers a function and continue, without waiting for an HTTP response. Is there any way to achieve the best of both worlds? To be able to invoke a function asynchronously, and have an unbounded number run in parallel?
Thanks!

The answer here provides recommendations on the approaches you can follow: https://stackoverflow.com/questions/38123887/can-i-implement-async-fire-and-forget-http-triggers-in-azure-functions
You may also want to take a look at Durable Functions for async HTTP APIs: https://docs.microsoft.com/en-us/azure/azure-functions/durable-functions-overview#pattern-3-async-http-apis

Closing as answered.


Whenever a child process is spawned, we should log the PID

It seems that we do in lsyncmanager, but some logs have been seen without the line.  Needs some more investigation.