proposals/app-level-api: add rkt app init subcommand

This adds a new subcommand app init to create an initial empty pod.
Follows #2932

The current proposal does not really specify how an empty pod has to be created. It vaguely suggests to start en empty pod "specified via an option that allows empty pods to stay alive" probably reflecting   https://github.com/coreos/rkt/pull/2932#discussion_r71244791.
Having a rkt run --empty-pod, or rkt run --mutable (without specifying any image) currently has no guarantee on the output format though.
I therefore suggest to add an explicit subcommand to initialize an empty pod (referred to as an empty Sandbox in CRI) which has a guaranteed/specified output format, namely the generated pod-uuid.

Since it's an empty pod creation app init feels strange.
Additionally there already is rkt rm to delete a pod.
May I suggest to add a new rkt pod command with init, rm, list etc... pod related commands (keeping the current ones for backward compatibility)?

@sgotti you have a fair point. Maybe we can find some alternative which is not as intrusive?

@s-urbaniak maybe we can use rkt pod init and then migrate others using an API deprecation process without making any intrusive changes
Another option is to add a command-line option to the current pod creation commands so that it allows an pod

I agree that app init may feel strange but at this point we are mostly moving our first steps in the CRI implementation so I would prefer to keep it self-contained under rkt app and gain experience from there.
I agree with @sgotti and @tmrts, in the long term I think we should try to re-use existing run/rm/list or consolidate them under pod xxx, in order to avoid having another duplicate parsing logic. But I prefer doing that UX rework once we have gained more insights from the implementation.
I'd say +1 for now on keeping it under app for now, calling it app init or app sandbox or something that doesn't look too weird, and revisit UX once we have all the elements. @sgotti @tmrts sounds fair?

@lucab seems good butq only if we are not going to create two different kind of pods (immutable and mutable) but just improve (the implementation and at the end also the UX ) the current pod model to also fit these new requirements. In addiition, perhaps the 'app' commands should be kept experimental so they could be changed/moved without the need to keep backward compatibility.

:+1: on app sandbox

@lucab SGTM :+1:

For a while I've been musing about adding a top-level pod subcommand and
keeping the top-level {run,kill,list,..} as aliases to subcommands. This
would make things more consistent with rkt image and rkt app etc. In
this context, rkt pod create or rkt pod init wouldn't be crazy.
On 31 August 2016 at 17:48, Luca Bruno<EMAIL_ADDRESS>wrote:

I agree that app init may feel strange but at this point we are mostly
moving our first steps in the CRI implementation so I would prefer to keep
it self-contained under rkt app and gain experience from there.
I agree with @sgotti https://github.com/sgotti and @tmrts
https://github.com/tmrts, in the long term I think we should try to
re-use existing run/rm/list or consolidate them under pod xxx, in order
to avoid having another duplicate parsing logic. But I prefer doing that UX
rework once we have gained more insights from the implementation.
I'd say +1 for now on keeping it under app for now, calling it app init
or app sandbox or something that doesn't look too weird, and revisit UX
once we have all the elements. @sgotti https://github.com/sgotti @tmrts
https://github.com/tmrts sounds fair?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/pull/3147#issuecomment-243808222, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN0yTTdIVj6kCBjYNa9zQXQY35DvNks5qlaJagaJpZM4JxnA0
.

@yifan-gu @euank PTAL, if it looks good to you, I'll merge this proposal.

@sgotti sure, it is experimental (not sure how to signal this). Regarding a single kind of pod, I'd like that to be the long-term form, but at the moment a mutable pod has many drawback (it is basically a privileged one by default) that I'd like to see how this whole CRI thing goes before adopting it as the default environment.
@jonboulle I think it makes sense, see my comment above, perhaps at a later stage?
@s-urbaniak fine on sandbox. This will be effectively the long-running pod-sandbox parent.

@sgotti sure, it is experimental (not sure how to signal this). Regarding a single kind of pod, I'd like that to be the long-term form, but at the moment a mutable pod has many drawback (it is basically a privileged one by default) that I'd like to see how this whole CRI thing goes before adopting it as the default environment.

Yeah, for the implementation I was just suggesting (perhaps it's obvious) to not reinvent the wheel (creating two different implementations) but extend the current one (as an example https://github.com/coreos/rkt/issues/3153#issuecomment-244202734).

ok, self-merging, since no opposition was stated.


Installing sharp with yarn causes "Could not load the "sharp" module using the linuxmusl-x64 runtime"

Possible install-time or require-time problem

[x] I have read and understood all of the documentation relating to installation.
[x] I have searched for known bugs relating to this problem in my choice of package manager.

You must confirm both of these before continuing.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.
0.33.3
If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.

If you are using another package which depends on a version of sharp that is not the latest,
please open an issue against that package instead.

[x] I am using Node.js with a version that satisfies ^18.17.0 || ^20.3.0 || >=21.0.0
20.9.0
[ ] I am using Deno
[ ] I am using Bun

If you cannot confirm any of these,
please upgrade to the latest version
and try again before opening an issue.
Are you using a supported package manager and installing optional dependencies?

[ ] I am using npm >= 9.6.5 with --include=optional
[x] I am using yarn >= 3.2.0
[ ] I am using pnpm >= 7.1.0 with --no-optional=false
[ ] I am using Deno
[ ] I am using Bun

If you cannot confirm any of these, please upgrade to the latest version of your chosen package manager
and ensure you are allowing the installation of optional or multi-platform dependencies before opening an issue.
What is the complete error message, including the full stack trace?
[TypeScript] 1:39:13 PM - Found 0 errors. Watching for file changes.
[Node] /admin-be/node_modules/sharp/lib/sharp.js:114
[Node]   throw new Error(help.join('\n'));
[Node]   ^
[Node]
[Node] Error: Could not load the "sharp" module using the linuxmusl-x64 runtime
[Node] Possible solutions:
[Node] - Ensure optional dependencies can be installed:
[Node]     npm install --include=optional sharp
[Node]     yarn add sharp --ignore-engines
[Node] - Ensure your package manager supports multi-platform installation:
[Node]     See https://sharp.pixelplumbing.com/install#cross-platform
[Node] - Add platform-specific dependencies:
[Node]     npm install --os=linux --libc=musl --cpu=x64 sharp
[Node] - Consult the installation documentation:
[Node]     See https://sharp.pixelplumbing.com/install
[Node]     at Object.<anonymous> (/admin-be/node_modules/sharp/lib/sharp.js:114:9)
[Node]     at Module._compile (node:internal/modules/cjs/loader:1241:14)
[Node]     at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
[Node]     at Module.load (node:internal/modules/cjs/loader:1091:32)
[Node]     at Module._load (node:internal/modules/cjs/loader:938:12)
[Node]     at Module.require (node:internal/modules/cjs/loader:1115:19)
[Node]     at require (node:internal/modules/helpers:130:18)
[Node]     at Object.<anonymous> (/admin-be/node_modules/sharp/lib/constructor.js:10:1)
[Node]     at Module._compile (node:internal/modules/cjs/loader:1241:14)
[Node]     at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
[Node]
[Node] Node.js v20.9.0
[Node] [nodemon] app crashed - waiting for file changes before starting...

What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?

npm verb cli [
npm verb cli   '/home/roman/.nvm/versions/node/v16.14.0/bin/node',
npm verb cli   '/home/roman/.nvm/versions/node/v16.14.0/bin/npm',
npm verb cli   'install',
npm verb cli   '--verbose',
npm verb cli   '--foreground-scripts',
npm verb cli   'sharp'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/home/roman/.nvm/versions/node/v16.14.0/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 1ms
npm timing config:load:env Completed in 1ms
npm timing config:load:file:/home/roman/Documents/test/.npmrc Completed in 1ms
npm timing config:load:project Completed in 2ms
npm timing config:load:file:/home/roman/.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:/home/roman/.nvm/versions/node/v16.14.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 8ms
npm timing npm:load:configload Completed in 8ms
npm timing npm:load:setTitle Completed in 1ms
npm timing config:load:flatten Completed in 2ms
npm timing npm:load:display Completed in 5ms
npm verb logfile /home/roman/.npm/_logs/2024-04-03T13_40_56_076Z-debug-0.log
npm timing npm:load:logFile Completed in 3ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 19ms
npm timing arborist:ctor Completed in 1ms
npm timing arborist:ctor Completed in 0ms
npm timing idealTree:init Completed in 8ms
npm timing idealTree:userRequests Completed in 2ms
npm http fetch GET 200 https://registry.npmjs.org/sharp 1073ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/detect-libc 273ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linuxmusl-arm64 542ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linux-x64 739ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linux-arm 744ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linuxmusl-arm64 744ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linux-x64 744ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-darwin-arm64 747ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-darwin-arm64 747ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linuxmusl-x64 746ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linux-arm 745ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linux-s390x 746ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linux-s390x 748ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-linux-arm64 749ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-darwin-x64 750ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linuxmusl-x64 788ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-linux-arm64 828ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/color 880ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/semver 901ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-win32-x64 948ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-wasm32 950ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-win32-ia32 953ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@img%2Fsharp-libvips-darwin-x64 2003ms (cache miss)
npm timing idealTree:#root Completed in 3092ms
npm http fetch GET 200 https://registry.npmjs.org/color-convert 182ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/lru-cache 186ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-string 205ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/@emnapi%2Fruntime 277ms (cache miss)
npm timing idealTree:node_modules/sharp Completed in 328ms
npm timing idealTree:node_modules/@img/sharp-darwin-arm64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-darwin-x64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-darwin-arm64 Completed in 1ms
npm timing idealTree:node_modules/@img/sharp-libvips-darwin-x64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linux-arm Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linux-arm64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linux-s390x Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linux-x64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linuxmusl-arm64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-libvips-linuxmusl-x64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-linux-arm Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-linux-arm64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-linux-s390x Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-linux-x64 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-linuxmusl-arm64 Completed in 1ms
npm timing idealTree:node_modules/@img/sharp-linuxmusl-x64 Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/tslib 172ms (cache revalidated)
npm timing idealTree:node_modules/@img/sharp-wasm32 Completed in 179ms
npm timing idealTree:node_modules/@emnapi/runtime Completed in 4ms
npm timing idealTree:node_modules/@img/sharp-win32-ia32 Completed in 0ms
npm timing idealTree:node_modules/@img/sharp-win32-x64 Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 165ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-name 170ms (cache revalidated)
npm timing idealTree:node_modules/color Completed in 180ms
npm timing idealTree:node_modules/color-convert Completed in 1ms
npm timing idealTree:node_modules/color-name Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 186ms (cache revalidated)
npm timing idealTree:node_modules/color-string Completed in 188ms
npm timing idealTree:node_modules/detect-libc Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/yallist 179ms (cache revalidated)
npm timing idealTree:node_modules/semver Completed in 183ms
npm timing idealTree:node_modules/lru-cache Completed in 3ms
npm timing idealTree:node_modules/simple-swizzle Completed in 3ms
npm timing idealTree:node_modules/is-arrayish Completed in 0ms
npm timing idealTree:node_modules/tslib Completed in 0ms
npm timing idealTree:node_modules/yallist Completed in 0ms
npm timing idealTree:buildDeps Completed in 4177ms
npm timing idealTree:fixDepFlags Completed in 3ms
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^18.17.0 || ^20.3.0 || >=21.0.0', libvips: '>=8.15.2' },
npm WARN EBADENGINE   current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm timing idealTree Completed in 4195ms
npm timing reify:loadTrees Completed in 4197ms
npm timing reify:diffTrees Completed in 5ms
npm timing reify:retireShallow Completed in 1ms
npm timing reify:createSparse Completed in 10ms
npm timing reify:loadBundles Completed in 0ms
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-win32-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-win32-ia32
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-wasm32
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@emnapi/runtime
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/tslib
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linuxmusl-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linuxmusl-arm64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linux-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linux-s390x
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linux-arm64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-linux-arm
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linuxmusl-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linuxmusl-arm64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linux-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linux-s390x
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linux-arm64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-linux-arm
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-darwin-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-libvips-darwin-arm64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-darwin-x64
npm verb reify failed optional dependency /home/roman/Documents/test/node_modules/@img/sharp-darwin-arm64
npm timing reifyNode:node_modules/@img/sharp-win32-x64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-win32-ia32 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-wasm32 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-linuxmusl-x64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-linuxmusl-arm64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-linux-x64 Completed in 10ms
npm timing reifyNode:node_modules/@img/sharp-linux-s390x Completed in 10ms
npm timing reifyNode:node_modules/@img/sharp-linux-arm64 Completed in 10ms
npm timing reifyNode:node_modules/@img/sharp-linux-arm Completed in 10ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linuxmusl-x64 Completed in 10ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linuxmusl-arm64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linux-x64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linux-s390x Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linux-arm64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-linux-arm Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-darwin-x64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-libvips-darwin-arm64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-darwin-x64 Completed in 11ms
npm timing reifyNode:node_modules/@img/sharp-darwin-arm64 Completed in 11ms
npm timing reifyNode:node_modules/color-name Completed in 76ms
npm timing reifyNode:node_modules/lru-cache Completed in 76ms
npm timing reifyNode:node_modules/yallist Completed in 77ms
npm timing reifyNode:node_modules/color-convert Completed in 77ms
npm timing reifyNode:node_modules/tslib Completed in 79ms
npm timing reifyNode:node_modules/semver Completed in 83ms
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.3.2.tgz 308ms (cache miss)
npm timing reifyNode:node_modules/is-arrayish Completed in 328ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 332ms
npm timing auditReport:getReport Completed in 336ms
npm timing auditReport:init Completed in 0ms
npm timing reify:audit Completed in 338ms
npm http fetch GET 200 https://registry.npmjs.org/sharp/-/sharp-0.33.3.tgz 541ms (cache miss)
npm timing reifyNode:node_modules/sharp Completed in 579ms
npm http fetch GET 200<EMAIL_ADDRESS>570ms (cache miss)
npm timing reifyNode:node_modules/@emnapi/runtime Completed in 594ms
npm http fetch GET 200 https://registry.npmjs.org/color/-/color-4.2.3.tgz 1133ms (cache miss)
npm timing reifyNode:node_modules/color Completed in 1175ms
npm http fetch GET 200 https://registry.npmjs.org/color-string/-/color-string-1.9.1.tgz 1322ms (cache miss)
npm timing reifyNode:node_modules/color-string Completed in 1350ms
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle/-/simple-swizzle-0.2.2.tgz 1342ms (cache miss)
npm timing reifyNode:node_modules/simple-swizzle Completed in 1365ms
npm http fetch GET 200 https://registry.npmjs.org/detect-libc/-/detect-libc-2.0.3.tgz 1423ms (cache miss)
npm timing reifyNode:node_modules/detect-libc Completed in 1454ms
npm timing reify:unpack Completed in 1455ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 4ms
npm timing build:link:node_modules/semver Completed in 2ms
npm timing build:link Completed in 3ms
npm info run<EMAIL_ADDRESS>install node_modules/sharp node install/check

<EMAIL_ADDRESS>install
node install/check

npm info run<EMAIL_ADDRESS>install { code: 0, signal: null }
npm timing build:run:install:node_modules/sharp Completed in 83ms
npm timing build:run:install Completed in 83ms
npm timing build:deps Completed in 91ms
npm timing build Completed in 91ms
npm timing reify:build Completed in 92ms
npm timing reify:trash Completed in 7ms
npm timing reify:save Completed in 9ms
npm timing reify Completed in 5796ms
added 11 packages, and audited 12 packages in 6s
1 package is looking for funding
run npm fund for details
found 0 vulnerabilities
npm timing command:install Completed in 5801ms
npm verb exit 0
npm timing npm Completed in 5980ms
npm info ok

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Memory: 4.77 GB / 15.28 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
Yarn: 3.2.0 - ~/.nvm/versions/node/v20.9.0/bin/yarn
npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
npmPackages:
sharp: ^0.33.3 => 0.33.3

npm info using<EMAIL_ADDRESS>Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node

It looks like you have multiple, possibly conflicting versions of Node.js on this machine.

[Node] Error: Could not load the "sharp" module using the linuxmusl-x64 runtime
OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)

Additionally, it looks like you're using multiple Linux OS with different libc implementations. For yarn you'll need to configure its supportedArchitectures feature - please see https://sharp.pixelplumbing.com/install#cross-platform

Well the different version of node issue is because i have one node installed globally, and then I use nvm per project to manage different version, which is a pretty standard practice , in this case the project where im trying to install sharp is 20.9.0
But apparently the root of the issue was not having this file
.yarmc.yml
yarnPath: .yarn/releases/yarn-3.2.0.cjs
nodeLinker: node-modules
supportedArchitectures: {
  os: [
    "current",
    "darwin",
    "linux",
    "win32",
  ],
  cpu: [
    "current",
    "x64",
    "ia32",
    "arm64",
  ],
  libc: [
    "current",
    "glibc",
    "musl",
  ],
}

What i did is have that file in the root folder, and then when building the docker dev container
# build commands
FROM node:20.9-alpine

WORKDIR /workdir
COPY ./package.json .
COPY ./.yarn/releases/yarn-3.2.0.cjs .yarn/releases/yarn-3.2.0.cjs #new
COPY ./.yarnrc.yml .yarnrc.yml #new
RUN yarn install

# run command
CMD yarn run watch

This fixed the issue for me


Make "Video" lowercase in workbook title

In the following notebook:
https://github.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/model_evaluation/automl_video_classification_model_evaluation.ipynb
In the notebook title, lowercase "video" so that it's:
Vertex AI Pipelines: Evaluating batch prediction results from AutoML video classification model

Made "Video" lowercase in the notebook title


feat: Drop log body after record successfully parsed

Description
Changes proposed in this pull request (what was done and why):

Added new attribute keepRawBody to the application input section of Logpipeline
The default value of the new attribute is true
If the keepRawBody is false and the original log content is JSON payload and parsing was successful the log attribute of the log record dropped.

Changes refer to particular issues, PRs or documents:

https://github.com/kyma-project/telemetry-manager/issues/551

Traceability

[x] The PR is linked to a GitHub issue.
[x] The PR has a milestone set.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[x] If the change is user-facing, the documentation has been adjusted.
[x] The feature is unit-tested.
[ ] The feature is e2e-tested.

/test pull-telemetry-manager-build


(SERVER-2895) Symlink to old cadir when setting up with the new default

This commit adds a method to symlink the new default cadir to the old default
cadir location when running the setup and import commands. This ensures
that, even on new installs, we can access the cadir from the old location
because there are still tools in the ecosystem that expect the old location.

I did a manual test of puppetserver ca setup on a FOSS install and it created the cadir in the right place and symlinked to the old place.

Will merge after squash.

Did another manual test for good measure and it still looks good.
Just gonna think on the testing stuff over night, probs.

I think we should be setting the "default_{new,old}_cadir" to be relative to $confdir. That would let us test this easier and be consistent with the work we just landed.

@justinstoller relative to the actual confdir, as opposed to the defaults? I agree that would be easier to test, but then my question is: if someone is using a non-default confdir, do we still want to create the symlink? My understanding was that the point of this symlink is so tools that hard-code the (default) cadir will continue to work. If we symlink to a cadir under a non-default confdir, won't those tools still be broken?

Wouldn't those tools already be broken if someone was using a non-default confdir then? Seems like that's not a case that actually happens in production (i.e. the confdir is expected to be default in that environment), so we can safely parameterize it without risking real use cases, but also allow easier testing.

So my understanding of the use cases for this tool are that 99% of it is for bootstrapping a new install with 0 custom configuration. There exists the ability to do custom configuration and some advanced users may do so. I expect those that have changed any of the defaults to "know what they're doing" and not need a symlink. However, if someone has set a $confdir to a custom value, but are otherwise expecting $cadir to be rooted in the same place as usual our new move could be disruptive.
Basically, I don't think users who are setting custom values (anywhere) when they use this command need this symlink. However, I also don't think it's incorrect behavior to create the symlink in the case of a custom $confdir case. I do think it is incorrect to link a custom $cadir to the old cadir.


Wifi instead of Ethernet Cable?

Hi there,
I am currently running a raspiblitz with wifi and would like to switch to Umbrel to try it out. But before I kill my current node, I 'd like to know if it supports wifi. If yes, are there any insturctions on how to do the installation with wifi?
If no, I'd like to see that feature added.
Thanks for the great work you are doing!

You can indeed use WiFi with Umbrel OS.
After flashing the SD card, remove it and then plug it back in to your computer. Should see it show up in your file manager with the name "boot".
You need to create a file called wpa_supplicant.conf with the following contents:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=<Insert 2 letter ISO 3166-1 country code here>

network={
 ssid="<Name of your wireless LAN>"
 psk="<Password for your wireless LAN>"
}

Then unmount the SD card, put it in your Pi, and it should automatically conned to your WiFi when it boots.
Let us know how you get on!

You need to manually put a file onto the boot partition called "wpa_supplicant.conf" with an adjusted version of this as content:
country=us
update_config=1
ctrl_interface=/var/run/wpa_supplicant

network={
 scan_ssid=1
 ssid="MyNetworkSSID"
 psk="Pa55w0rd1234"
}

You can remove the scan_ssid if your network SSID isn't hidden.

You can basically use the file from RaspiBlitz, they recommend doing it the same way.

Awesome, thanks for the info!

You can indeed use WiFi with Umbrel OS.
After flashing the SD card, remove it and then plug it back in to your computer. You should see it show up in your file manager with the name "boot".
You need to create a file called wpa_supplicant.conf with the following contents:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=<Insert 2 letter ISO 3166-1 country code here>

network={
 ssid="<Name of your wireless LAN>"
 psk="<Password for your wireless LAN>"
}

Then unmount the SD card, put it in your Pi, and it should automatically conned to your WiFi when it boots.
Let us know how you get on!

I followed all of these steps and I cannot get my Node to work on WIFI. Any assistance is greatly appreciated:
I am running a Rasp pi4 with the latest Umbrel OS. I used TextEdit (this could be the problem but I don't know what I am doing)to creat the file above, copied into the Boot SD and it still doesn't work. Please let me know what other information you may need to help troubleshoot. Again, thanks for any assistance, its greatly appreciated.

How to connect to WiFi with Captive portals?

Will I be able to do this retrospectively? i.e take the SD card out of a Pi that's already set up with umbrel and add the file afterwards..?

What are the contents of the file if the wifi network requires a username and password?


Is atrules option still relevant ?

Now that the module uses browserslist, is atrules option to force fallbacks in at-rules still relevant ?
Reminder:

if you target IE8, IE9 or IE10, rem fallbacks in at-rules are only needed in font shorthand and pseudo-element.
all other browsers support rem

Anyone has a use-case ?

Hi @iamvdo ,
Forgive me if I'm being ignorant, but if I'm using respond.js for IE8 that will allow the use of media-queries, and therefore the px rules inside them are still relevant. Also, I am using rem for all my font-sizes too so I would still require atrules for IE9/10.
Thanks,
Rob

I still require them for the reason @robzor mentioned, and there's also another use case. Opera has supported CSS3 media queries for years now, many years before any other browser supported them (so long in fact media queries back in the day were used as a CSS hack to supply styles just to Opera) and therefore long before rem was supported which arrived in Opera in version 12. IMO because of this pixrem should do fallbacks in atrules by default.


dbjobqueue: acquire a new connection for each listen query

This fixes a bug where the listen function would keep trying to use a
closed, unrecoverable connection to listen for a notification. This
continued failing, which essentially made the queue instance useless.

Out of curiosity, how did this manifest in practice? Were we seeing failures in prod due to this? Were they captured by out SLOs?

Not really, there were generally enough pods available to keep it going.

Not really, there were generally enough pods available to keep it going. Just a lot of logging statements.

Thanks for your attention to detail and looking at all the things!


x/tools/cmd/fiximports: don't use .biz extension in testdata

What version of Go are you using (go version)?

go version go1.14.2 windows/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\bert.hooyman\AppData\Local\go-build
set GOENV=C:\Users\bert.hooyman\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\bert.hooyman\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\BERT~1.HOO\AppData\Local\Temp\go-build874685950=/tmp/go-build -gno-record-gcc-switches

What did you do?

go get -v golang.org/x/tools/gopls
What did you expect to see?
successful tool install
What did you see instead?
go: downloading golang.org/x/tools v0.0.0-20200408132156-9ee5ef7a2c0d
-> unzip<EMAIL_ADDRESS>mkdir<EMAIL_ADDRESS>Access is denied.
go: golang.org/x/tools/gopls upgrade => v0.3.4
-> unzip<EMAIL_ADDRESS>mkdir<EMAIL_ADDRESS>Access is denied.
go get golang.org/x/tools/gopls: unzip<EMAIL_ADDRESS>mkdir<EMAIL_ADDRESS>Access is denied.
The problem I am seeing is essentially: mkdir titanic.biz
.biz is a ransomware extension Symantec will block it.
My system has Symantec Enpoint Protection, and my employer won't let me switch it off.
.biz is a bad choice for a testdata folder name suffix.

Probably the same issue described in #36568 and partially fixed in 1.14.2.

Update: I was able to convince SysAdmin to suspend my Symantec Endpoint Protection for an hour. I could do "Go: Install/Update Tools" in VS Code and get all tools installed flawlessly at the first try.
The single problem was the .biz foldername extension.

/cc @heschik

@bcmills @jayconrod is this a dupe of #36568? This is an error on directory creation rather than rename.

No, it doesn't look like a duplicate of #36568. In the error log here's it's failing while extracting the x/tools module zip, not when renaming the directory.
@BertHooyman So it sounds like your organization has a policy against creating files that end with .biz? I'm not sure how we can anticipate that kind of thing.

These files are years old and we've never had a problem before AFAIK. I can review a change to rename them but I don't think I'm going to do it myself.

@jayconrod  I'm not sure whether my company has 'special' rules or these rules come with Symantec Endpoint Protection. It's an edge condition for sure. Either way, having the scenario mentioned here might be sufficient for others experiencing the exact same error message "Access is denied" on a mkdir. It took me quite a while to weed through all the seemingly related mentions (not just in x/tools), so having it here might help people. I understand if the issue is not 'resolved'.

It doesn't seem plausible for us to work around every IT department's arbitrary restrictions on filenames.
I agree with @heschik: we can review a change to work around this restriction, but we shouldn't do it proactively. I would add to that that the commit message should include a reference to some specific documentation about why (and, ideally, under what conditions) those names are disallowed.

@bcmills thats perfectly understandable. I would suggest to make the root cause discoverable by those who suffer from it. So that users understand that when a mkdir leads to an Access Denied (on Windows), they understand it's not Go Tools' fault, but their endpoint protection.


[network] [small] Use HashMap::entry in PeerManager::add_peer

Instead of removing and adding the current connection to check if there is a simultaneous dial, we use HashMap::entry API.

@bors-libra r+

:pushpin: Commit 6230754 has been approved by davidiw

:hourglass: Testing commit 623075477ef54b9f4298b69f258c9f496d65749d with merge 12e5a317763be8183a9ee4703c89934ce82090d7...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit 623075477ef54b9f4298b69f258c9f496d65749d with merge 286c1b2431d48de3758a09104355b1ae7aff7fc7...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing 286c1b2431d48de3758a09104355b1ae7aff7fc7 to master...


docs(status page): release 5.4 updated to add Migration Options

Mike asked to wait until the status page was merged in release 5.4  Adding Migration Option to status page.

Could you open a PR against the gh-pages branch?


i18n(zh-cn): update error-reference

Description (required)
update error-reference
Related issues & labels (optional)

https://github.com/withastro/docs/pull/9081

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
reference/error-reference.mdx
Localization changed, will be marked as complete.

zh-cn
reference/errors/get-entry-deprecation-error.mdx
Localization added, will be marked as complete.

zh-cn
reference/errors/unknown-filesystem-error.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Getting errors on run.

I get this error when I run my code
I've used quick.db before and everything has gone fine I don't know what the issue is now

C:\node_modules\quick.db\bin\handler.js:240
db.prepare(CREATE TABLE IF NOT EXISTS ${options.table} (ID TEXT, json TEXT)).run();
^
SqliteError: file is not a database

Can you paste your code please?

sorry I don't comment much
`
//Startup stuff
console.log("loading...")
const Discord = require('discord.js');
const client = new Discord.Client();
const db = require('quick.db');
client.once('ready', () => {
let allUsers = client.users.array();
for(let i = 0; i < allUsers.length; i++){
if(!(db.get(allUsers[i].id))){
db.set(allUsers[i].id, {insurancePremium: null})
	}

}
console.log('Ready!');

});
client.login('NjI4MzM3NTQ3NzYzNzc3NTc0.XZOSbg.SyhCynaHoOrTrJhGeJz6DnOhtUk');
console.log("almost there...")
var active = false
var questionsAsked = null
//Start of message parsing
client.on("message", message =>{
if (message.author.id === "628337547763777574") return;
const server = message.guild
const iChannel = server.channels.find('name', 'insurance-calculator')
if (message.channel.id === "637748327550681119"){
if (message.content.startsWith("!ICalcPremium")){
if (active === false){
console.log(message.author.id + " is calculating his insurance premiums")
active = true
var calculatorID = message.author.id
db.set(calculatorID, {insurancePremium: 0})
			message.member.addRole('649718621852925983')
			iChannel.send(`${message.member} Please respond correctly to all of the questions correctly.`)
			iChannel.send("If any questions are answered incorrectly then Baos reserves the right to refuse to pay any payouts you may be otherwise entitled to.")
			iChannel.send("question 1:")
			iChannel.send("How many times have you lost a lawsuit?")
			console.log("{-_-} Debug: Calc Channel Roadmark 0 reached")
			console.log(calculatorID)
			questionsAsked = 1
			console.log("{-_-} Debug: Asked Questions: " + questionsAsked)
		};
	};
};

if (message.channel.id === "649718622108778525")	{
	var ans = message.content
	console.log("{-_-} Debug: logged Answer: " + ans)
	console.log("{-_-} Debug: Calc Channel Roadmark 1 reached")
	console.log("{-_-} Debug: Asked Questions: " + questionsAsked)
	if (questionsAsked == 1){
		console.log("{-_-} Debug: Calc Channel Roadmark 2 reached")
		ans = parseInt(ans)
		console.log("{-_-} Debug: ans is now equal to: " + ans)
		var currentPrem = db.get(`${calculatorID}.insurancePremium`)
		console.log("{-_-} Debug: currentPrem is now equal to: " + currentPrem)
		var insuranceMod = ans * 15
		console.log("{-_-} Debug: insuranceMod is now equal to: " + insuranceMod)
		var newPrem = currentPrem - insuranceMod
		console.log("{-_-} Debug: newPrem is now equal to: " + newPrem)
		db.set(`${calculatorID}`, {insurancePremium: newPrem, lostLawsuits: ans})
		iChannel.send("Answer has been noted.")
		iChannel.send("Question 2:")
		iChannel.send("How many times has somebody attempted but failed to sue you?")
		questionsAsked = 2
		}else if (questionsAsked == 2){
		console.log("{-_-} Debug: Calc Channel Roadmark 3 reached")
		ans = parseInt(ans)
		console.log("{-_-} Debug: ans is now equal to: " + ans)
		var currentPrem = db.get(`${calculatorID}.insurancePremium`)
		console.log("{-_-} Debug: currentPrem is now equal to: " + currentPrem)
		var insuranceMod = ans * 5
		console.log("{-_-} Debug: insuranceMod is now equal to: " + insuranceMod)
		var newPrem = currentPrem - insuranceMod
		console.log("{-_-} Debug: newPrem is now equal to: " + newPrem)
		db.set(`${calculatorID}`, {insurancePremium: newPrem, WonLawsuits: ans})
		iChannel.send("Answer has been noted.")
		iChannel.send("Question 3: ")
		iChannel.send("")
		questionsAsked = 3

	};
};

//start of admin commands
if (!message.guild) return;

//end of admin commands

});
//end of message Parsing
`

Ok, I will look into it. Warning, you have sent your token.

oops

it turns out I corrupted the sqlite file so alls good.


Server crash

I am getting a server crash with the following console error:
/var/nodeapps/isforms/bundle/programs/server/node_modules/fibers/future.js:245
						throw(ex);
						      ^
TypeError: Cannot read property 'keys' of undefined
    at packages/cfs:tempstore/tempStore.js:297:1
    at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108:1)
error: Forever detected script exited with code: 8

I believe it is caused by file uploads. Any ideas on how to determine what causes it? Servers bouncing and being off-line for some period of time is no good at all...

Help anyone? please...

same here. any ideas @raix, @aldeed or @rhyslbw?

Same here.
/opt/meteor/app/programs/server/node_modules/fibers/future.js:24
5
throw(ex);
^
TypeError: Cannot read property 'keys' of undefined
at packages/cfs:tempstore/tempStore.js:297:1
at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108:1)
error: Forever detected script exited with code: 8
error: Script restart attempt #3
Would anyone be able to point me in the right direction?
Thank you,

if i recall correctly, we were trying to read a key (cookie name) that didnt exist from meteor-server-cookies. it was happening around the same time that this was fixed, but i dont think they were related: https://github.com/gfk-ba/meteor-server-cookies/pull/3

I see it too. This crash our server =/
Not sure what happened here: https://github.com/CollectionFS/Meteor-CollectionFS/blob/b46cb20d2d86a806e19e9ffbd72955c2a4ae37e7/packages/tempstore/tempStore.js#L297

@aldeed Any idea what can cause this?

This is obviously related with #619

same for me. Critical

Who is supposed to solve this? Or can somebody give us a hint?

https://forums.meteor.com/t/deprecating-collectionfs/16921

@hluz, @nathantsoi and @migloo
Did you ever solve this?

I moved away from CollectionFS to vsivsi:file-collection (I only needed GridFS support)

It happend to me when I add-remove-add-remove fastly an image that have multiple storages and transformations, and because there are no way to stop uploading when removing, the best idea is to say goodbye to CollectionFS

I guess I have to agree with @Buom01 , Aside from this issue, there are some other issues and it seems like they don't have the time to do fix it anymore as some of them were still hanging for 1 year now.


Extension causes high cpu load with large numbers of variables/parameters/resources

Issue Type: Performance
Extension Name: azurerm-vscode-tools
Extension Version: 0.13.0
OS Version: Windows_NT x64 10.0.19041
VSCode version: 1.50.0

msazurermtools.azurerm-vscode-tools-unresponsive.cpuprofile.txt

https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

Hmmm, perf tools don't seem to like this file, although I don't see anything obviously wrong with it.  Will have to try on another computer.

Taking a long time in visitAllReachableStringValues
@konopkap Did this happen one time, or does it happen frequently?  Is it a particularly large file?  Is it possible to get a copy of it or at least a description (how many lines, resources, etc.)?  You can mail me directly if you'd like @ my first name then a period then my last name then at microsoft of course dot com.  Thanks!

~180KB, ~4,3k lines
400 variables
One of the resources has 4K lines

@konopkap If you'd like, you can try out the fix here: https://github.com/microsoft/vscode-azurearmtools/releases/tag/v0.14.0-alpha.  Download the VSIX, then use F1 -> Install from VSIX... inside vscode to install the new version.  While you're at it, feel free to give feedback on the preview "Extract to variable/parameter" functionality!
Thanks!
Stephen

@StephenWeatherford Now it works without any lags. Big thank you! To be honest I don't know how to use this new functionality. Could you tell me how can I use it?

@konopkap Sorry, was out yesterday.  I would start with our Getting Started info at https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools, then feel free to ask additional questions.


bpf: lb: fix L3 pseudo-hdr csum update for SCTP in __lb6_rev_nat()

Same as in commit 9f27973a1052 ("bpf: lb: fix check for L3 pseudo-hdr csum update in lb6_xlate()"), only update the L3 pseudo-hdr component in the L4 csum when the L4 protocol requires it (ie. for TCP/UDP, but not for SCTP).

Same as in https://github.com/cilium/cilium/pull/22953. I checked all csum_l4_replace() call sites, this should be it.

/test

K8sKafkaPolicyTest flaked (https://github.com/cilium/cilium/issues/22021 ?), and brought down the k8s-1.25-kernel-4.19 run. Rerunning.

/test-1.25-4.19


Test for classical explainer

simple test for classicalExplainer explain_local()

@janhavi13 hmm it looks like the builds are failing on this PR due to flake8 errors

it looks like the build is hitting the time limit:
timeoutInMinutes: 40 # how long to run the job before automatically cancelling

it looks like the build is hitting the time limit:
timeoutInMinutes: 40 # how long to run the job before automatically cancelling

What's the max we should set it ? The unified_information takes ~50 minutes to run

@janhavi13 sounds reasonable to use 60 or even 120 for now


Turn action tuples into its own type

As raised in #42, we should probably not be passing around unspecific Tuple[int,int,int] when passing around graph action indices.
To improve the situation, we should create a new class for this data type and refactor the code to use it.

Fixed by #129


Servo on DFRobot Edison shield

var five = require("johnny-five");
var Edison = require("galileo-io");
var board = new five.Board({
io: new Edison()
});
board.on("ready", function() {
console.log("board ready");
var servPan = new five.Servo(5);
Results in this...
1450680905444 Device(s) Intel Edison
1450680905453 Connected Intel Edison
1450680905470 Repl Initialized

board ready

ERROR: TypeError: Cannot read property '0' of undefined
at ToPinIndex (/home/root/.node_app_slot/node_modules/galileo-io/lib/galileo.js:304:19)
at Galileo.pinMode (/home/root/.node_app_slot/node_modules/galileo-io/lib/galileo.js:357:14)
at Servo.Controllers.Standard.initialize.value (/home/root/.node_app_slot/node_modules/johnny-five/lib/servo.js:59:19)
at new Servo (/home/root/.node_app_slot/node_modules/johnny-five/lib/servo.js:189:8)
at Board. (/home/root/.node_app_slot/main.js:46:19)
at Board.emit (events.js:92:17)
at process._tickCallback (node.js:448:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)
at node.js:935:3
I remembering someone saying the DFRobot board acts like the Intel Mini Breakout Board.  So my assumption is that one may not address the pins in the same way for the DFRobot board as they would for the Intel Adruino Breakout Board.  Would this be correct?  If so, is there a way to make it so one may address things the same way as on the Intel board?  If not, how does one address the pins on the DFRobot board?

Are you referring to the DFRobot IO Expansion board? I have a WIP branch that does a bunch of pin mapping to make this is all nicer—I'll get that finished and landed

Luckily I have both boards from them.  I would be able to test either.
On Mon, Dec 21, 2015 at 7:36 AM, Rick Waldron<EMAIL_ADDRESS>wrote:

Are you referring to the DFRobot IO Expansion board? I have a WIP branch
that does a bunch of pin mapping to make this is all nicer—I'll get that
finished and landed
—
Reply to this email directly or view it on GitHub
https://github.com/rwaldron/galileo-io/issues/44#issuecomment-166318955.

I've been working on this all day. One major issue I've come across is that PWM doesn't seem to actually function correctly on this board. I even tried controlling it with a sketch uploaded via Arduino IDE and it did not work.

Also, this board crashes a lot :\

And gets very hot

Ok, strike all that, I tried with external power plugged in and it works "ok-ish". I think this is a poorly assembled board.

I noticed a squirrelly response from the servos when I used GPIO pins such
as GP44 (I think).  I did not use external power.
On Mon, Dec 21, 2015 at 1:37 PM, Rick Waldron<EMAIL_ADDRESS>wrote:

Ok, strike all that, I tried with external power plugged in and it works
"ok-ish". I think this is a poorly assembled board.
—
Reply to this email directly or view it on GitHub
https://github.com/rwaldron/galileo-io/issues/44#issuecomment-166410776.

I always use external power for servos, otherwise the resulting behavior is unreliable


CSS link href is unknown

I have installed sixpack using pip and I'm running the latest version.  I can create experiments with the API, but my CSS isn't loading for the dashboard.  It says "(unknown)" for the href.  I can see the dashboard's HTML.  It just appears ASSET_URL isn't defined.
I checked to see if the bundled CSS and JS were getting created.  They are being generated in the correct folder from the config.yml file.  I can also access them from the web if I navigate to the CSS file directly.
So as far as I can tell, everything is working, but the URL for the CSS isn't being added in the dashboard template.  Do you have any ideas on why that would be?
I am using gunicorn, but I got the same results when running it with the "sixpack-web" command.  And I'm not getting any errors. I also have a secret key.

I ran it from source and it worked.  I'm not sure what wasn't working when installing with pip.  I'll close this.  Thanks.

@ShaneBurkhart can this be reopened please? Latest version from PIP is still broken


Introduce option for high volume request tracking

Beyla tracks the full request completion time, this typically means we look to see if the application is responding with more data after the first HTTP response. One example would be a large file download, where the majority of the time is actually serializing the data on the wire. When the client uses keep-alive, we don't necessarily see the connection close event, but we tell by new pushed requests that we should terminate an earlier request.
This approach doesn't work well in when there's high volume of requests, e.g. beyond our current map sizing. The delayed requests will likely be booted out of the map before we have a chance to complete them. The ideal fix is to provide an option to resize the maps to match the volume of requests, but we need to finish the work of the tracer code restructuring for this to happen.
I'm adding an option to force Beyla to complete the request as soon as the response is finished. It will produce less accurate accounting for large file downlaods, but it will avoid no data for high volume of requests. We can also use this option to unblock clients if there are bugs in the delayed request accounting.
This PR is partial, since I accidentally pushed to main. Please review the following commits too:
https://github.com/grafana/beyla/commit/7be9c33fc08aa825f275213d3418f4c7a5b3440d
and
https://github.com/grafana/beyla/commit/bd3e5f4c3b9e30bf10ab0839ed4c344b83cb3c56
(Original PR: https://github.com/grafana/beyla/pull/1192)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 53.30%. Comparing base (c3901b2) to head (dc5fba1).

:exclamation:  There is a different number of reports uploaded between BASE (c3901b2) and HEAD (dc5fba1). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (c3901b2)
HEAD (dc5fba1)

oats-test
1
0

k8s-integration-test
1
0

integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1196       +/-   ##
===========================================
- Coverage   81.03%   53.30%   -27.73%
===========================================
  Files         136      136
  Lines       11501    11501
===========================================
- Hits         9320     6131     -3189
- Misses       1647     4967     +3320
+ Partials      534      403      -131

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
53.30% <ø> (-0.04%)
:arrow_down:

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

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


MIG Mongo Queue

Description
MIG is currently using Mongo for persistence but it is also using it for resiliency. This caused an issue in SIT when we rebuilt the environment because as MIG started it started to read from an internal Mongo queue for data which no longer existed in minio. This caused errors in the logs but from a users perspective they would never know as MIG was still able to process incoming associations and added them to the bottom of its internal queue.
Suggestion is that moving the internal queue to rabbit is a better solution and provides more resiliency and observability to this issue making it easier to maintain.
Additional Information

@JoeBatt1989 have you tested the latest release https://github.com/Project-MONAI/monai-deploy-informatics-gateway/releases/tag/0.3.8?

@JoeBatt1989 are we okay closing this issue?

@mocsharp we were still seeing the issue on GSTT prod, I will gather some details and make sure we have the right deployment etc


Populatedb randomly crashes if some already existing users don't have a billing address

Steps to reproduce the problem

Create some or a user having no default billing address
Optionally remove other users to have more chance of crashing
Run populatedb
It might crash when trying to create a fake payment

What Happened
The following code snippet will select a user randomly which might not have an existing billing address:
https://github.com/mirumee/saleor/blob/61b3a62988599d76184955663f89e8892b92b6e4/saleor/core/utils/random_data.py#L507-L510
  File "/app/saleor/core/utils/random_data.py", line 387, in create_fake_payment
    billing_address=order.billing_address,
  File "/app/saleor/payment/utils.py", line 82, in create_payment
    "billing_first_name": billing_address.first_name,
AttributeError: 'NoneType' object has no attribute 'first_name'

is this bug still relevant now ?

This is now fixed.


hello brother

i wnt help

hi, What help do you need?

you have any instagram account brother

give me i wnt help

https://www.instagram.com/___anson____/
On Mon, Sep 18, 2023 at 10:33 AM zackworld @.***> wrote:

give me i wnt help
—
Reply to this email directly, view it on GitHub
https://github.com/ansonbenny/ChatGPT/issues/3#issuecomment-1722760455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNWLFHJDFII4SSFAGJRACTX27IZHANCNFSM6AAAAAA44D2SBM
.
You are receiving this because you commented.Message ID:
@.***>

please accept request

ok

where we get
SITE_URL & JWT_PRIVATE_KEY

SITE_URL = react local url [http://localhost:5173] or hosted url
On Mon, Sep 18, 2023 at 10:44 AM zackworld @.***> wrote:

where we get
SITE_URL & JWT_PRIVATE_KEY
—
Reply to this email directly, view it on GitHub
https://github.com/ansonbenny/ChatGPT/issues/3#issuecomment-1722766864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNWLFFPJC4BNTT5JRJFTWLX27KCRANCNFSM6AAAAAA44D2SBM
.
You are receiving this because you commented.Message ID:
@.***>

JWT_PRIVATE_KEY = you can add any keywords
On Mon, Sep 18, 2023 at 10:50 AM Anson Benny @.***>
wrote:

SITE_URL = react local url [http://localhost:5173] or hosted url
On Mon, Sep 18, 2023 at 10:44 AM zackworld @.***>
wrote:

where we get
SITE_URL & JWT_PRIVATE_KEY
—
Reply to this email directly, view it on GitHub
https://github.com/ansonbenny/ChatGPT/issues/3#issuecomment-1722766864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNWLFFPJC4BNTT5JRJFTWLX27KCRANCNFSM6AAAAAA44D2SBM
.
You are receiving this because you commented.Message ID:
@.***>


Running $validator.reset() does not correctly clear validation hidden file input.

Versions

vee-validate: ^2.1.0-beta.7
vue: ^2.5.16

Describe the bug
When using a hidden input with a custom button for file input, I am attempting to add a remove button the clear the file. When using $validator.reset() on the file input I can see that it's properties in the error bag get reset, but upon submit they are set to passing again.
To reproduce
Steps to reproduce the behavior:
Press submit to see file input error, input a file, press submit to clear error, remove file, press submit again and you will see in the console that validation is passing even though the file has been removed and errors reset.
Expected behavior
I expected that the file error would appear as the input has been reset.
Demo link
https://codesandbox.io/s/2p36w7x3pj
Desktop (please complete the following information):

OS: MacOS High Sierra 10.13.6
Browser Firefox Dev Edition
Version 65.0b4

Additional context
In my application I am using provide inject as my forms are built up in templates, so the submit button and the input itself are in different components. However local testing shows the same behavior.

My mistake, this was easily solved by manually clearing the input.


PropGroup component should implement table with dragging option

linked to #609
At this moment, PropGroup component is based on a simple grid-based table and used within editor and detail. Following the best practice within actant /action table, we should use the react-table with dragging function here (instead of buttons for moving things up and down)

Would be nice to somehow solve it with grid because of better styling options, but I try to solve style deficit in table. There is problem with full length dynamic tags width now.

Closing as it's implemented in #769 (duplicity)


Use const syntax in init to declare const variables

They will then be interpreted as lets, and passed over to the UGen object.

Const are now declared with full capital letters
init:
    MYCONST = 0.5


Feat (LASC) Merge LASC branch into master

LASC branch supports LA Superior court data collection and parsing for Juriscraper.

I haven't had time to really dig into this, but thought it worth commenting that any tests that hit the network (if there are any) should be identified and isolated under `tests/network/' before merging

Thanks Philip. I'm merging this one today so I'll make sure it's OK.
On Tue, Sep 10, 2019 at 7:36 AM Philip Ardery<EMAIL_ADDRESS>wrote:

I haven't had time to really dig into this, but thought it worth
commenting that any tests that hit the network (if there are any) should be
identified and isolated under `tests/network/' before merging
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/freelawproject/juriscraper/pull/273?email_source=notifications&email_token=AABZ3KR3QXQVTH25XIMHPQLQI6WF5A5CNFSM4IUK473KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6LKEUQ#issuecomment-529965650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABZ3KU625X2RTJPBRBJFX3QI6WF5ANCNFSM4IUK473A
.

--
Mike Lissner
Executive Director
Free Law Project
https://free.law

Awesome, thanks!
[sent from a phone]
On Tue, Sep 10, 2019 at 9:44 AM, Mike Lissner<EMAIL_ADDRESS>wrote:

Thanks Philip. I'm merging this one today so I'll make sure it's OK.
On Tue, Sep 10, 2019 at 7:36 AM Philip Ardery<EMAIL_ADDRESS>wrote:

I haven't had time to really dig into this, but thought it worth
commenting that any tests that hit the network (if there are any) should be
identified and isolated under `tests/network/' before merging
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/freelawproject/juriscraper/pull/273?email_source=notifications&email_token=AABZ3KR3QXQVTH25XIMHPQLQI6WF5A5CNFSM4IUK473KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6LKEUQ#issuecomment-529965650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABZ3KU625X2RTJPBRBJFX3QI6WF5ANCNFSM4IUK473A
.

--
Mike Lissner
Executive Director
Free Law Project
https://free.law
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: Pmcrypto Golang 0.0.1 (ddacebe0)
Comment: https://protonmail.com

xsBNBFbzO7YBCADGzq8Iw0brBGgIZajm2CpZndKCsb20AwHcFEqVxDfOH93ivf0b
RJL2BHrZANUqi1L6vGrd4HmF7leA4eAyuexpMLjV8vRmlaKm4jMs9xY1VDDyCqbU
09UDxcMQ91Q5kKmz537DYmaR11gsUwFJrgFCso/fbt8HTXqpn6xklj6Lp27ehNp6
fezgKGI0VzEPSsZYN+1lD2RgrAQ1kdxBJRQUfvL+OvAi0UyM9Vkw+Afr9XlzVnEM
xjWhAg/lrY8DIYFkpULmNBKaQcQxpRQ7/c1xHIgId3uUnyTAGsRiIcSrypEtNcBt
EouwXZO1uEZmXBeVKhzz1mGsH+SKMGIoMuMdABEBAAHNL2FyZGVyeXBAcHJvdG9u
bWFpbC5jb20gPGFyZGVyeXBAcHJvdG9ubWFpbC5jb20+wsB1BBABCAApBQJY4B4s
BgsJBwgDAgkQ0/rhfw45OSAEFQgKAgMWAgECGQECGwMCHgEAALvkCACpjDFIJxUG
qqW9gJSz/PJtJogVdNLLUpkqwmnhOodfpKBaQL0WWf1iCm4wYsg5+/3Ah5Ab4rae
gSAhsy7/vSinW4Jqvu/8wPgrvDJVC1nH+wTPV2sd/AgWjUKtw0TvFyagBchLy0N+
rdJBo8zZSbAq9vpYbZDXFMksN96oPGCapd73TLv7+lX9NRc1LoQOpyZyGQPeyp6a
NWb2GEuv+u6Sm/b/fGeX0qfQQXcZli2Cqa/cmvRZ3jHlVfzIE+hCZyCtFlB8Vo/0
PAFNCEL+yMK4jBWpuJWPAFTlRPkZxuuEroNWGDxLZ1fz7CdZIgBpl9ZhUfhKrA2A
RoZdGB5q2snEzsBNBFbzO7YBCADKTtMWGfV4di5fz94qQFUG/CUfrxGkUuHmp8Cq
w/OU394cYgSEBPu0gdH02xrD3td1vmMOWlwpMeZMkOlHN1/UHslc7igzgTUfhCcR
5VMKvPFmWzC0W6M3vY7jGrSjMnPjf4L1FlBJ44aaKZwu1uos75yj8jbPblTAx9LF
hqlhXOTZuVtmrnxAJqS0tux2Eg7l4jNUZWMVVQ+411y3WMy6L6WDPnyhC2GScyG8
irzvQN5kGCcQPOMh4FvKcAmTjAAFnGPc6yAVe2NwgFqJsy7GETj3Z/1DjMPBnW+8
AJlQZebIT/lELI9+DUyTOn4IcOGxr/O6rFQwVfctEkBYssKlABEBAAHCwF8EGAEI
ABMFAljgHiwJENP64X8OOTkgAhsMAACEigf+KXMc9zoQRLJAbO2cDq47LdmWShb+
1+NyOhvrh/idpQueU/IWAOsqhnXdpRmu+bUuI/jqYb4fdkP6nTXUNLtUYTxs8srm
ag1GeUJa+DJKjijgi0LlHdvFlk7EGeMcAEB7B/rWI0NvM3e+t4HeQK21W1/bjvir
TzgBHPZYsheutwYeQ+nf3mVSFVrIBAB8W65gv2HdYGV9Jw46YS/PbrPAi5yAvdhs
BckmxpPnGybby/TvOX5BZWxkWkmPveDQFgmzmCFRQSbtVDIDVGK2w8TkgmfVk7/8
flwtxGO5z25sam8j/Xm/9zt74Dr1HKkmB1+iBls9REgT4pBO4cmZvv/6/w==
=aQR4
-----END PGP PUBLIC KEY BLOCK-----


Integrate special matching codes (eg frank) into ms2ldavis somehow

Justin said this will greatly improve his productivity.

Do you mean spectral matching?
On the spectra, or the motifs, or both?

Autocorrect.. Yes, I meant spectral matching, on the spectra and perhaps the motifs too. This will save the time that Justin has to spend on manual validation work. Not sure what the best approach is, what do you think? Easiest is to simply copy and paste the entire Frank codes and put them into ms2ldavis, but we end up with duplicates codes in pimp too.

Impossible to do given the time.


Added twitter to contact info

Purpose
I wanted to add my twitter information to the contact page of my hugo website.
Screenshots
See e.g., https://andrewfowlie.github.io/#contact
Documentation
I don't see explicit documentation for the contact widget at https://sourcethemes.com/academic/docs/get-started/, so I haven't added a corresponding PR there.

Thanks for putting together this contribution!
If we go down this route, we'll end up with requests to put all the other social links in the contact widget too - which is something we have already implemented locally (similar to how the social links in the About widget are processed) and considering releasing to the public. Hence, I'll close this for now, but appreciate the effort!
Feel free to submit PRs for any of the open issues, especially those with the help wanted tag :)

That's great that it's being developed.

which is something we have already implemented locally (similar to how the social links in the About widget are processed) and we are considering releasing it to the public

I see - I didn't realize that not all the development was here on github.
best,


If partial re-deploy in node-red, connection to slack hangs

It appears that whenever a partial deploy is made in node-red (only deploying modified flows or nodes), sometimes connection hangs and message are not received until a full re-deploy is made.
Thanks!

Closing this issue as it is resolved in version 2.0.0


Re-set osc.spec.criconfig on re-deploy

How to categorize this PR?

/area os
/kind bug
What this PR does / why we need it:
Re-set osc.spec.criconfig on re-deploy
Now that it is possible to modify the CRI for existing worker pools, the osc needs to take into account that a worker pool formerly set to containerd is reconfigured with worker.CRI==nil. The OSC object is only re-created when k8s major or minor version is changed or the worker name is updated and therefore needs to take this update path into account.
Which issue(s) this PR fixes:
Fixes #4254
Special notes for your reviewer:
Release note:

Switching an existing worker pool from `containerd` to `docker` no longer starts `containerd` on the new node

This doesn't work the way I'd want it to work, see https://github.com/gardener/gardener/issues/4254#issuecomment-871226538


[ETHOSN] Add support for Ethos(TM)-N 21.08 driver stack release.

Co-authored-by: Tristan O'Connor<EMAIL_ADDRESS>

@mbaret @leandron


Added prefix variable for the formatted title.

Some schools allow personal appointments. These appointments don't have to follow the regular schoolhour scheme. Instead of showing 'null' in Google Calendar, it will show a 'P' in front.

Thanks for the contributions! Please do not hesitate to open a new PR if you think of  a new improvement.


Misspelled reference to conda environment

Looking at the section: https://docs.microsoft.com/en-us/azure/machine-learning/tutorial-1st-experiment-sdk-setup-local#workspace
In this section is this line:
In the window that has the activated tutorial1 conda environment, run this code from the tutorial directory.
It refers to tutorial1, but the conda env created above was named tutorial (without the 1)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 93ab763e-565b-17d9-744f-4efbdc73b3d9
Version Independent ID: 2d591a5a-80a9-74a8-7876-aecf59bfbf17
Content: Tutorial: Get started with machine learning - Python - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-1st-experiment-sdk-setup-local.md
Service: machine-learning
Sub-service: core
GitHub Login: @aminsaied
Microsoft Alias: amsaied

@dipankar-ray Thanks for the feedback! We will review and update accordingly.

@dipankar-ray Thanks for the feedback! We will review and update accordingly.

Thanks, Raised the PR #https://github.com/MicrosoftDocs/azure-docs-pr/pull/145042 for the update.

Thanks, Raised the PR #https://github.com/MicrosoftDocs/azure-docs-pr/pull/145042 for the update.

@dipankar-ray We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Hide resources on demand.

Is your feature request related to a problem? Please describe.
I'm using ash_paper_trail for my resources, and since all resources in the API are included, Version resources make the list too messy.
Describe the solution you'd like
In the resource, I can set it to be hidden.
Express the feature either with a change to resource syntax, or with a change to the resource interface
use Ash.Resource, extensions: [AshAdmin.Resource]

admin do
  show? false
end

You can do this with the mixing: https://hexdocs.pm/ash_paper_trail/0.1.0/get-started-with-paper-trail.html#enriching-the-versions-resource

@zachdaniel
I don't understand, could you provide more information?
As far as I know, there's no show? option in admin section of AshAdmin.Resource.

Oh, wow. I didn't realize we only had it for apis :(


remove the parameter is not used in func

Signed-off-by: Xiaoyang Zhu<EMAIL_ADDRESS>
Changes
remove the parameter is not used in the taskrun reconcile function.

/ok-to-test

/kind cleanup

hi, @sbwsg  please look at this pr, thanks.

@soulseen tried to add the release note label using /release-note-none prow command but didn't seem to work, but you should be able to add the required release note label by following the instructions in the pull request template

/release-note-none

@jerop looks like get some wrong with prow

/lgtm

/test pull-tekton-pipeline-integration-tests


Ability to generate date with a specific format and add more attribute to person class

I found this useful,

Ability to generate date with a specific format
Adding more attributes to a person which includes (Date of birth, Phone Number etc)
Was using date and person to generate some data and i found out this is missing

Thanks for the great library.

DateFormat('yyyy-MM-dd HH:mm:ss').format(faker.date.dateTime(minYear: 2021, maxYear: 2022));
You could format your date like this

Wow thats a great work around but i just think it should be there instead of going through the route of adding another library


Modify keyword to fetch the name and added retrun to the notification…

This PR has fixed for ODS-673 which was getting failed in Tier2
Signed-off-by: Tarun Kumar<EMAIL_ADDRESS>

Jenkins job: 381


Update deps

Update all dependencies (most are at least 2 years old).

I'll gladly merge this as soon as the macos tests pass.

How can I test on macos, without such a machine?

With a freshly compiled darling (github.com/darlinghq/darling), it passes:
Darling [/Volumes/SystemRoot/tmp]$ ./search.test -test.run=Alloc -test.v
=== RUN   TestGetPermanodeLocationAllocs
    handler_test.go:1020: explicit location from attrs: 0 allocations (max 0)
    handler_test.go:1020: referenced permanode location: 1 allocations (max 1)
    handler_test.go:1020: location from exif photo: 1 allocations (max 1)
--- PASS: TestGetPermanodeLocationAllocs (0.52s)
PASS

So, I don't know what happens in GitHub's test machine.

Maybe try disabling cache in the macos build? I've had similar issues in the past. We can remove cache from the macos workflow and never put it back...

How can I remove the cache?

By removing these lines:
https://github.com/perkeep/perkeep/blob/8171ea5b511bb969590f4439b8726b9e76c6499a/.github/workflows/tests-macos.yml#L18-L22

I know this sucks but the other option for debugging this quickly without access to macos would be to update ~50% of the libs and see if the build passes, then the other 50%.
You can test multiple setups in parallel by pushing to different branches and github will build them all in parallel.

This looks good to me @tgulacsi.
Are you done? I can merge whenever.

Yes, I am. Please merge it.

Done! thanks :))


Typescript support

Any chances to add Typescript definitions to the project?

@marcelowa, that would be an awesome addition. I don’t know much about typescript, is that something but I’d be willing to do it especially if I can get some help.
Maybe there is a tool that can convert flow to TS?

I looked a bit for such a tool, but I couldn't find any (there's flowgen that does the opposite), but doing some reading it shouldn't be too hard to add this support
Do you mind if I take it?

Would love the contribution, you'd be my first contributor! Would be awesome if it could be automated, would be super hard to keep both up to date and in sync.

Unfortunately I can't find an existing tool to automate this

Thats a bummer @marcelowa. I'll leave the ticket open. I'd say someone can make external typings for it but it would be a large project and hard to keep up to date.

Hi there, FYI I've started some definitions (https://github.com/ncknt/rmwc-typed). It's very much a work in progress.

Sidenote @jamesmfriedman, if you replace react-scripts with react-script-ts, you can use CRA with typescript. No need to eject.

I think he's saying he would prefer Flow anyway. :)
For what it's worth, I was the same way until I got sick of Flow's RAM usage and lack of good editor tooling. You don't have to use the object-oriented aspects of Typescript, you can use it almost exactly like Flow, and it's nearly equivalent in static analysis these days. (You can also even use it with babel now in babel 7, no need to use its compiler.)

It's less preference and more toolchain. It was INCREDIBLY hard to put together something that would auto-document directly from the built in types. I went with Flow because React Docgen supported it and it seemed like the best way to make sure the code and docs stayed 100% in sync.

I think that's a good reason to choose your typing on; in the end you want the work to become less -- not more.
For anyone browsing this issue: https://github.com/styleguidist/react-docgen-typescript is promising but really not ready for production use.

I'm still hoping for TS bindings... Is this ded?

Not dead at all, I'm interesting in finding a first class way to support this. I was just looking at the shape of typescript definitions tonight and I'm convinced that an automated process can be built into the RMWC build to spit out the definition files. Can't promise anything in the near term, but definitely not falling off the radar.

@marcelowa flow-to-typescript could be the tool you're searching for: https://github.com/bcherny/flow-to-typescript/issues/4

#159 has been fixed and has paved the way for this. Is there anyone available to help me work on this one?

Generating ts type definition files at transpile time could be a little finicky. Would you have any interest in a refactor from flow to typescript? Converting from flow to typescript isn't too painful and you've already done a lot of the hard work by defining types.

If we did that, then we’d have to find a way to create flow definitions at transpile time ;). I’ve been exploring this, it’s very doable and I’ll be doing a POC soon.

Welp, it's definitely possible! :). POC of automatically converting the FlowTyped javascript files to Typescript. Take a look at the Typescript branch if you're interested in whats going on. More updates soon!

I'll give it a try this weekend, and report back.

How are the TS files being generated? They're ignored in git, but published on npm (see https://unpkg.com/rmwc@1.7.2/). If they're not directly based on stable definitions like some fully compatible Flow or JSDoc types, they should be committed to the repository so they can be improved manually.

@nickmccurdy you are correct that they are ignored. They are based completely on the stable flow definitions.

The library is built in flow
The tests fail on any flow failure
The build generates tsx files from the flow typed ones and then uses the tsx files to generate the declarations
The typescript compiler will error out if there are any Typescript errors causing the build to fail

So basically, there is a test / build safe way to generate these things without error. The things I'm unsure of are peoples different typescript configurations and how those might play, as well as conflicts with @types/react versions (should I make it a peer dependency?). I'm sure those things will be cleared up relatively quick.

I am using the onClick handler on an ListItem (as is done in /src/docs/Submenu.js). But it seems that the TS definitions do not include the onClick attribute for the ListItem. I assume it should get all of the React HTMLAttributes?

Correct. All of the components in RMWC handle spread props, so all of the appropriate react ones should be passed on through ...rest. This allows you to pass anything React accepts without having it explicitly typed.

That's what is actually happening at run-time, yes, but the current typing definitions are not reflecting this.
So for example when I use TextField since the type tag is not in the TextFieldPropsT, typescript complains that I'm passing a prop that isn't matching what the component accepts.
I'm not sure how to get this to work with the automated build you have from Flow to TSX though.

That's what is happening during run-time yes. But TypeScript isn't properly typing RMWC components to support prop types from HTMLInputElement. So the compiler is complaining about fields that are supported at run-time but not supported at compile type because they're missing.
E.g. Cannot add prop type on TextField

I was just doing some reading and it appears it’s a simple as adding a Union with React.HTMLAttributes. I take a look.

I think that should do it, yes :) Thanks you!

What @nichgalea reported, was what I tried to say. I just was not very clear about that. And I couldn't help on this since I have no idea how flow and the ts conversion process works.

Can we commit the TypeScript types to make this fix, or is this also an issue with the Flow types?

Just published 1.7.4 which fixes the DomAttribute issue being described.
Unfortunately, Circle CI appears to be down so it says the build is failing, which it is not. Either way, the code should be working as expected

Just a headsup: a union with React.HTMLAttributes works, but doesn't make the type complete. Because in the underlying MDC you can use tag to change the HTML tag, you oughta match the tag value to the correct html attributes.
I'm just mentioning this so you know why it's not recognised correctly if you use a field on React.SpecificAttribute which is not present on the base attributes.
As far as I know there is currently no good way to solve this in either flow or TS, without making all the calls generic and have you put in the html attributes type which defaults to the base attributes.

@SleeplessByte You're absolutely right. I did think of this, but came to the same conclusion. I'm not really sure how this can be done, even with generics since tag can be manipulated at runtime. Thats why I defaulted to using any with the HTML props.
Definitely open to any help on this.

DrawerHeader seems to still miss the HTMLAttributes.

If you have the HTML Attributes type as the default generic type, you can
leave it up to the user. Just keep all you have right now, but replace the
exact type by a default type with Type Parameter.
BaseComponent<A = React.HTMLAttributes>

I chose A for attributes here instead of T for type.
And yeah you can change tag at runtime, but that becomes the user's issue
hehe. They would use a or (type | other type) in their type and decide with
casting which one is being used.
On a sidenote, somewhere in the react definitions there is a giant map from
type to attributes. Theoretically you can capture tag not as a string but
as a enum value. You then map the enum value to a type. Or I think that
could work. Or maybe not. :P
On Mon, 25 Jun 2018, 23:29 James Friedman<EMAIL_ADDRESS>wrote:

@SleeplessByte https://github.com/SleeplessByte You're absolutely
right. I did think of this, but came to the same conclusion. I'm not really
sure how this can be done, even with generics since tag can be manipulated
at runtime. Thats why I defaulted to using any with the HTML props.
Definitely open to any help on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/40#issuecomment-400101898,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB35WJbjj_ZO7D4egyiSLOYVq4VXTtiKks5uAVYrgaJpZM4QwOjC
.

@lal12 fixed and published with 1.7.5

It seems like the way this package bundles TypeScript types is broken. Any typing packages for dependencies must be included in rmwc's dependencies (see https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html).
Currently I'm stuck on this error, even after installing @types/material__snackbar:
/Users/nick/Repos/stackselect/node_modules/rmwc/Snackbar/index.d.ts
(6,29): Could not find a declaration file for module<EMAIL_ADDRESS><EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm install @types/material__snackbar` if it exists or add a new declaration (.d.ts) file containing `declare module 'material__snackbar';`

I use "strict": true, which includes noImplicitAny.

@nickmccurdy could you do me a favor and post your tsconfig? That will definitely help troubleshooting.

https://github.com/nickmccurdy/stackselect/blob/master/tsconfig.json

@nickmccurdy I've gone ahead and added the most recent version of @types/material-components-web to rmwc. It's published in 1.7.6
Even before installing the additional types, I was unable to create any compile errors using your exact config, everything just worked as expected. I to am using react-scripts-ts with create-react-app. Even though I can't repro your error, I'm inclined to believe you since I still don't know much about TS :). Let me know if this fixes the problems you were hitting.

Thanks for the quick response. Unfortunately, I still get the same error on 1.7.6. Would it help if I pushed this code and linked to it?

Steps to reproduce:
npm create react-app my-app --scripts-version=react-scripts-ts
cd my-app
npm install rmwc @types/prop-types
# add "import 'rmwc';" to src/index.tsx
npm start

Hey @jamesmfriedman.
So I started to dig in and have run into a couple of roadblocks. (It's important to note that we are working from a custom Webpack config and not create-react-app.)
First, compilation is successful but results in these warnings
Second, including the Button component results in this error:
withFoundation.js?6da3:231 Uncaught TypeError: Cannot read property 'prototype' of undefined
    at withFoundation (withFoundation.js?6da3:231)
    at eval (index.js?0bf1:103)
    at Object../node_modules/rmwc/Ripple/index.js (main.js:12651)
    at __webpack_require__ (main.js:64)
    at eval (withRipple.js?6c9d:14)
    at Object../node_modules/rmwc/Base/withRipple.js (main.js:12591)
    at __webpack_require__ (main.js:64)
    at eval (index.js?3c4e:16)
    at Object../node_modules/rmwc/Base/index.js (main.js:12531)
    at __webpack_require__ (main.js:64)
    at eval (index.js?23a1:20)
    at Object../node_modules/rmwc/Button/index.js (main.js:12615)
    at __webpack_require__ (main.js:64)
    at eval (AppLayout.tsx?8f50:1)
    at Module../src/layouts/AppLayout/AppLayout.tsx (main.js:13633)
    at __webpack_require__ (main.js:64)

And lastly, attempts to use the Provider results in this TS error:
JSX element type 'RMWCProvider' is not a constructor function for JSX elements.

It's quite possible that the issues are unique to our implementation - our version of @types/react ("15.6.2") is not consistent with our version of react (16.4.1) and I have a hunch that this is fallout from that.
But just wanted to make some progress in getting this into our app.
Keep up the good work man!

Hi ya!
The first error is a postcss issue with root element properties, from the
base MDC library. I think they have an issue in their repo.
When your types don't match your base react, you'll implement calls
wrongly. Don't know if that is the issue here, but I'd start with
normalising that :)
On Fri, 6 Jul 2018, 19:20 Shawn Rice<EMAIL_ADDRESS>wrote:

Hey @jamesmfriedman https://github.com/jamesmfriedman.
So I started to dig in and have run into a couple of roadblocks. (It's
important to note that we are working from a custom Webpack config and not
create-react-app.)
First, compilation is successful but results in these warnings
https://gist.github.com/shawnatxapp/e27ddd0436270286cf1db88227325b7f
Second, including the Button component results in this error:
withFoundation.js?6da3:231 Uncaught TypeError: Cannot read property 'prototype' of undefined
at withFoundation (withFoundation.js?6da3:231)
at eval (index.js?0bf1:103)
at Object../node_modules/rmwc/Ripple/index.js (main.js:12651)
at webpack_require (main.js:64)
at eval (withRipple.js?6c9d:14)
at Object../node_modules/rmwc/Base/withRipple.js (main.js:12591)
at webpack_require (main.js:64)
at eval (index.js?3c4e:16)
at Object../node_modules/rmwc/Base/index.js (main.js:12531)
at webpack_require (main.js:64)
at eval (index.js?23a1:20)
at Object../node_modules/rmwc/Button/index.js (main.js:12615)
at webpack_require (main.js:64)
at eval (AppLayout.tsx?8f50:1)
at Module../src/layouts/AppLayout/AppLayout.tsx (main.js:13633)
at webpack_require (main.js:64)
And lastly, attempts to use the Provider results in this TS error:
JSX element type 'RMWCProvider' is not a constructor function for JSX elements.
It's quite possible that the issues are unique to our implementation - our
version of @types/react ("15.6.2") is not consistent with our version
of react (16.4.1) and I have a hunch that this is fallout from that.
But just wanted to make some progress in getting this into our app.
Keep up the good work man!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/40#issuecomment-403096408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB35WOJpsC76ziloDqsgSrmYNF4FeeRvks5uD5xSgaJpZM4QwOjC
.

Just wanted to follow up on my comment above
The runtime error was happening because of a weakness in our webpack config. The resolve.extenstions array looked like this:
extensions: [".css", ".sass", ".scss", ".ts", ".tsx", ".js"],

Which was pulling in Ripple.css instead of the Ripple.js file and wreaking havoc. Reordering the array to look for the ts/js files first seemed to do the trick:
extensions: [".ts", ".tsx", ".js", ".css", ".sass", ".scss", ],

So lesson learned- order matters.
The Provider issue mentioned above still stands, but we can live without that so I'm not concerned with  fixing it at this time.

A good time to follow up, 1.8 has some good TS updates thanks to @mutsys. Please report and failures (or successes) for validation.
Also, could definitely use some guidances on how to create tests to validate TS is working. Right now, the test is just that it compiles successfully, I'm not sure if anything more than that needs to be done.

It looks like the Snackbar type declaration in DefinitelyTyped is for @material/snackbar/index.js, but rmwc/Snackbar/index.d.ts is importing it as @material/snackbar/dist/mdc.snackbar', so it has an implicit any type.

@nickmccurdy
This is a great question, how do we handle conflicts like that? This example brings up one of the reasons I wanted to bake TS definitions directly into this codebase since some of the packages on definitely typed can be wrong.

Is it possible for you to declare that module yourself as any so at least it's not implicit?
MDC is on version 0.37.1 but the stuff of definitely typed is only on version 0.35.0. I don't think this will be a huge problem since MDC isn't exposed directly to the consumer through RMWC, but I'm expecting at some point I'll hit compilation errors if that stuffs not up to date.
Should we just declare all of those modules manually as any and avoid using definitely typed for material all together?

@nickmccurdy maybe I did a bad job explaining
Currently the types are being pulled from definitely typed. My issue is, definitely typed is behind MDC and not often correct.
Also, what you brought up about the Snackbar should technically impact everything in RMWC, but it sounds like that problem is isolated to Snackbar?

If types for a dependency package are incorrect, we should fix it in the
appropriate types package. DefinitelyTyped is pretty quick to review
contributions. However I'm not sure if the dependency path issue is with
rmwc or DefinitelyTyped, we should probably figure it out first.
On Fri, Jul 20, 2018, 5:48 PM James Friedman<EMAIL_ADDRESS>wrote:

@nickmccurdy https://github.com/nickmccurdy maybe I did a bad job
explaining
Currently the types are being pulled from definitely typed. My issue is,
definitely typed is behind MDC and not often correct.
Also, what you brought up about the Snackbar should technically impact
everything in RMWC, but it sounds like that problem is isolated to Snackbar?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jamesmfriedman/rmwc/issues/40#issuecomment-406735428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4l9Me166a_X67ZqmcX6GUdz02N3F0_ks5uIlArgaJpZM4QwOjC
.

I can confirm that Snackbar support is broken.
import { Snackbar } from "rmwc/Snackbar";

**/node_modules/rmwc/Snackbar/index.d.ts
(6,29): Could not find a declaration file for module<EMAIL_ADDRESS><EMAIL_ADDRESS>implicitly has an 'any' type.
  If the 'material__snackbar' package actually exposes this module, consider sending a pull request to amend 'https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/material__snackbar`

@nickmccurdy Any existing solution?

@mattferrin while RMWC ships with its own types, it relies on @types/material-components-web for the MDC typings. Unfortunately, the definitely typed typings haven't been getting any community love. My suggestion:

Contribute to @types/material-components-web and bring it up to speed. RMWC will pick up the latest minor release automatically when you install.
Declare the Snackbar module in your own project and cast it to any. Before you tell me that this is a terrible idea, your project will never be directly exposed to the library since it's obfuscated by RMWC. Declaring the module is just a formality to get your compiler to stop complaining about it.

Three troubles:

Could not find Snackbar declaration:
code as:
import { Snackbar } from "rmwc/Snackbar"

report from TypeScript compiler:
ERROR in [at-loader] ./node_modules/rmwc/Snackbar/index.d.ts:6:29
 TS7016: Could not find a declaration file for module<EMAIL_ADDRESS><EMAIL_ADDRESS>implicitly has an 'any' type.

Try npm install @types/material__snackbar if it exists or add a new declaration (.d.ts) file containing declare module 'material__snackbar';

resolved by:

rename<EMAIL_ADDRESS>to ``'material-components-web'

`` -- **node_modules/rmwc/Snackbar/index.d.ts** line 6

> module **@types/material-components-web** defines that terms.

2. Bad constructors definition

code as:

```ts
import { TextFiled } from "rmwc/TextFiled"

report from TypeScript compiler:
ERROR in [at-loader] ./node_modules/rmwc/TextField/index.d.ts:205:50
 TS2510: Base constructors must all have the same return type.

ERROR in [at-loader] ./node_modules/rmwc/TextField/index.d.ts:255:44
 TS2510: Base constructors must all have the same return type.
[12:12:39] webpack is watching for changes

resolved by:
delete new <P>(props: Readonly<any>) -- node_modules/rmwc/TextField/index.d.ts line 163
delete new <P>(props: Readonly<any>) -- node_modules/rmwc/TextField/index.d.ts line 213

duplicated definition

@tulayang thanks for digging into this some. If could could help provide a bit more guidance

The snackbar issue, these seems to be an issues with the definitely typed repo. I'd rather fix it there. Hoping the community will jump in and keep that up to date as I cannot take that on.
On the TextField issue, I finally managed to repro and have corrected it (as well as the same issue elsewhere) throughout. Interestingly enough, I use RMWC in a TS project of my own and never ran into this issue, I was just able to get my IDE to complain about it after running a build in RMWC.

For anyone following this issue, had a great tip off that the TS defs contained a lot of extra junk. I've been able to make some refinements to the build process to remove all of the garbage.
Would love some validation when someone gets a chance. 2.0.2.

The 5.x.x release has been completely re-written top to bottom in Typescript for React 16.3 and higher. For anyone that is using the current generated Typescript implementation, or anyone that wanted to try the library but found the old type system broken, now is the time to try out the 5.x.x-alpha branch and leave your feedback!

Very happy to close this issue and to fully support Typescript! Enjoy the V5 release.


fix: dynamic chart animation

Fixed work

plotLine animation of the dynamic chart does not work and blotband setting does not work. #81
(다이나믹 차트에 plotLine, plotBands설정시 애니메이션효과가 나타나지 않는 수정)

Demo

http://<IP_ADDRESS>:8082/examples/example12-01-dynamic-chart-append-and-shift-data-dynamically.html

[4/6] 리뷰 완료하였습니다~ 간단하군요ㅎㅎ


make hlut widget optional

would be nice to add an hlut button to the toolbar so it can be generated after imagewidget instantiation if a user wanted one for a specific subplot!

would be nice to add an hlut button to the toolbar so it can be generated after imagewidget instantiation if a user wanted one for a specific subplot!

I think this is feature creep, we they can create and add it programmatically if they need that level of customization?

Also add kwarg to specify subsample dims for HistogramLut widget?

Also add kwarg to specify subsample dims for HistogramLut widget?

@kushalkolar anything more than number of bins? or you want a dict that allows user to pass nbins and flank?

Just a tuple of its to specify the max size?

going to merge this, see #359 for the subsample


Profiler crashes with SIGSEGV on OpenJDK 11

Hey all!
The profiler occasionally causes a segmentation fault in our application with the following logs:
#
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007efea3292d5a, pid=1, tid=2563
# JRE version: OpenJDK Runtime Environment Temurin-11.0.24+8 (11.0.24+8) (build 11.0.24+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (11.0.24+8, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libasyncProfiler-linux-musl-x64-70e751fa84d39dcf2daa802a20d7378ca9c8f2.so+0xa2d5a]  Profiler::recordSample(void*, unsigned long long, EventType, Event*)+0x6a
#
# Core dump will be written. Default location: Core dumps may be processed with "/var/mnt/core-dump-handler/cdc -c=%c -e=%e -p=%p -s=%s -t=%t -d=/var/mnt/core-dump-handler/cores -h=%h -E=%E" (or dumping to //core.1)
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues

I've seen a few other issues (open and closed) about segmentation faults, but none of them matched our java version and the problematic frame Profiler::recordSample. If it is indeed a duplicate, please feel free to close and link to that 🙏
I unfortunately don't have the /tmp/hs_err_pid1.log anymore, but if it helps, I can try to reproduce the error and collect the logs.
Regarding the JDK version, we're running it in the metabase/metabase-enterprise image, so we unfortunately cannot influence it (in case the answer was "your JDK is too old").

Hey @Gerrit-K, thanks for the report.
Could you confirm what version of the profiler (pyroscope-java) you are using? I see a few related and fixed issues in the underlying profiling engine (https://github.com/async-profiler/async-profiler) so I want to see if we need to perform an update.

Ah sorry, missed that - it's the latest, v0.14.0, downloaded from the release


circlescan generate floats

The example in README.rst in not correct
My code is:
from pixelscan.pixelscan import *

for x, y in circlescan(0, 0, 0, 1):
   print (x, y)

What I expect:
(0,0), (0,1), (1,1), (1,0), (1,-1), (0,-1), (-1,-1), (-1,0), (-1,1)

What I got:
(0, 0)
(0, 1)
(0.707107, 0.707107)
(1, 0)
(0.707107, -0.707107)
(0, -1)
(-0.707107, -0.707107)
(-1, 0)
(-0.707107, 0.707107)

My python version is:
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
My pixelscan version is pixelscan==0.3.2

There was a snap transformation missing in the README example. Thanks. It's been fixed with aa67c30.