[Bug]: serverless function using "sharp" cannot find "sharp" module

Summary
If you include "sharp" as a dependency in your package.json in a Next.js serverless function, it will not be bundled into your deployed functions and you will get an error:

Error: Cannot find module 'sharp'

I believe this is because of the DEFAULT_EXCLUDED_MODULES declaration in src/helpers/config.ts.
Steps to reproduce
I ran this on Typescript, but I assume the same problem holds for Javascript repos. Note, I am also using Yarn as a multi-package monorepo, if it's relevant. sharp is installed in one of the subpackages, not at the monorepo root.
npm install sharp

Make a file in src/pages/api/myfail.ts:
import sharp from 'sharp';

export default function () {
   ...
}

A link to a reproduction repository
No response
Plugin version
4.2.4
More information about your build

[ ] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
Linux
Your netlify.toml file

`netlify.toml`
[build]
# postinstall package.json scripts don't run when the dependency is cached, so
# we need to manually call those commands when we build in Netlify.
command = "yarn hardhat:compile && yarn components:build && yarn pixel:build && yarn frontend:build"
publish = "packages/frontend/.next"

[build.environment]
# Do not use this mnemonic for anything real. This is a shared mnemonic used by
# Hardhat.
MNEMONIC = "test test test test test test test test test test test junk"
NEXT_PUBLIC_APP_URL_SCHEME = "https"
NEXT_PUBLIC_APP_HOST = "app.supercool.xyz"

[[plugins]]
package = "@netlify/plugin-nextjs"

[functions]
node_bundler = "esbuild"
external_node_modules = ["sharp"]

# staging branch
[context.staging]
[context.staging.environment]
NEXT_PUBLIC_SHOW_CONNECTED_ADDRESS = "false"

# dev branch
[context.dev]
[context.dev.environment]
NEXT_PUBLIC_SHOW_CONNECTED_ADDRESS = "true"

Your public/_redirects file

`_redirects`
# Paste content of your `_redirects` file here

Your next.config.js file

`next.config.js`
# Paste content of your `next.config.js` file here. Check there is no private info in there.

Builds logs (or link to your logs)

Build logs
6:31:07 PM: Build ready to start
6:31:11 PM: build-image version: 122b31996ccaffd45d820a452d6227f8312110cc (focal)
6:31:11 PM: build-image tag: v4.5.3
6:31:11 PM: buildbot version: 0854df8549ceb2ae5c3f0bb7326040a5c2ced0c5
6:31:11 PM: Fetching cached dependencies
6:31:11 PM: Starting to download cache of 1.0GB
6:31:16 PM: Finished downloading cache in 4.795906935s
6:31:16 PM: Starting to extract cache
6:31:54 PM: Finished extracting cache in 38.56656924s
6:31:54 PM: Finished fetching cache in 43.556708242s
6:31:54 PM: Starting to prepare the repo for build
6:31:55 PM: Preparing Git Reference refs/heads/beta
6:31:56 PM: Parsing package.json dependencies
6:31:58 PM: Starting build script
6:31:58 PM: Installing dependencies
6:31:58 PM: Python version set to 2.7
6:31:58 PM: Started restoring cached node version
6:32:00 PM: Finished restoring cached node version
6:32:01 PM: v16.13.2 is already installed.
6:32:01 PM: Now using node v16.13.2 (npm v8.1.2)
6:32:01 PM: Started restoring cached build plugins
6:32:01 PM: Finished restoring cached build plugins
6:32:01 PM: Attempting ruby version 2.7.2, read from environment
6:32:03 PM: Using ruby version 2.7.2
6:32:03 PM: Using PHP version 8.0
6:32:03 PM: Started restoring cached yarn cache
6:32:19 PM: Finished restoring cached yarn cache
6:32:19 PM: Yarn workspaces detected
6:32:19 PM: Started restoring workspace packages/frontend node modules
6:32:19 PM: Finished restoring workspace packages/frontend node modules
6:32:19 PM: Started restoring workspace packages/hardhat node modules
6:32:19 PM: Finished restoring workspace packages/hardhat node modules
6:32:19 PM: Started restoring workspace packages/pixel-art-react node modules
6:32:19 PM: Finished restoring workspace packages/pixel-art-react node modules
6:32:19 PM: Started restoring workspace packages/ui-components node modules
6:32:19 PM: Finished restoring workspace packages/ui-components node modules
6:32:19 PM: Started restoring workspace root node modules
6:32:19 PM: Finished restoring workspace root node modules
6:32:20 PM: Installing NPM modules using Yarn version 1.22.10
6:32:20 PM: yarn install v1.22.10
6:32:20 PM: [1/4] Resolving packages...
6:32:22 PM: [2/4] Fetching packages...
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
6:32:24 PM: info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
6:32:24 PM: [3/4] Linking dependencies...
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^16.0.0".
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^16.0.0".
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency "@types/styled-components@>= 5".
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency "@types/styled-theming@>= 2".
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency "styled-components@>= 5".
6:32:24 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency "styled-theming@>= 2".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend ><EMAIL_ADDRESS>has unmet peer dependency "react-is@>= 16.8.0".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/hardhat ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/hardhat ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/hardhat ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/hardhat ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency "react@*".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16 || ^17".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16 || ^17".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/ui-components ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > @chakra-ui/icons ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > @emotion/styled ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > babel-jest ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react > react-beautiful-dnd ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/pixel-art-react > react-color ><EMAIL_ADDRESS>has unmet peer dependency "react@*".
6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/ui-components > @babel/preset-typescript ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > @emotion/styled > @emotion/babel-plugin ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > babel-jest > babel-preset-jest ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/ui-components > next > styled-jsx ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/ui-components > @babel/preset-typescript > @babel/plugin-transform-typescript ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > babel-jest > babel-preset-jest > babel-preset-current-node-syntax ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:24 PM: warning "workspace-aggregator-a54b629a-142b-42aa-a7b0-f24dfe161ad6 > @pixly/frontend > babel-jest > babel-preset-jest > babel-preset-current-node-syntax ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>6:32:42 PM: [4/4] Building fresh packages...
6:33:05 PM: Done in 44.53s.
6:33:05 PM: NPM modules installed using Yarn
6:33:05 PM: Started restoring cached go cache
6:33:05 PM: Finished restoring cached go cache
6:33:05 PM: go version go1.16.5 linux/amd64
6:33:05 PM: go version go1.16.5 linux/amd64
6:33:05 PM: Installing missing commands
6:33:05 PM: Verify run directory
6:33:07 PM:
6:33:07 PM: ────────────────────────────────────────────────────────────────
6:33:07 PM:   Netlify Build
6:33:07 PM: ────────────────────────────────────────────────────────────────
6:33:07 PM:
6:33:07 PM: ❯ Version
6:33:07 PM:   @netlify/build 26.2.3
6:33:07 PM:
6:33:07 PM: ❯ Flags
6:33:07 PM:   baseRelDir: true
6:33:07 PM:   buildId: 61fde16b24b9c40007750f08
6:33:07 PM:   deployId: 61fde16b24b9c40007750f0a
6:33:07 PM:
6:33:07 PM: ❯ Current directory
6:33:07 PM:   /opt/build/repo
6:33:07 PM:
6:33:07 PM: ❯ Config file
6:33:07 PM:   /opt/build/repo/netlify.toml
6:33:07 PM:
6:33:07 PM: ❯ Context
6:33:07 PM:   production
6:33:07 PM:
6:33:07 PM: ❯ Loading plugins
6:33:07 PM:    -<EMAIL_ADDRESS>from netlify.toml and package.json
6:33:09 PM:
6:33:09 PM: ────────────────────────────────────────────────────────────────
6:33:09 PM:   1. @netlify/plugin-nextjs (onPreBuild event)
6:33:09 PM: ────────────────────────────────────────────────────────────────
6:33:09 PM:
6:33:10 PM: Next.js cache restored.
6:33:10 PM: Netlify configuration property "build.environment.NEXT_PRIVATE_TARGET" value changed.
6:33:10 PM:
6:33:10 PM: (@netlify/plugin-nextjs onPreBuild completed in 651ms)
6:33:10 PM:
6:33:10 PM: ────────────────────────────────────────────────────────────────
6:33:10 PM:   2. build.command from netlify.toml
6:33:10 PM: ────────────────────────────────────────────────────────────────
6:33:10 PM:
6:33:10 PM: $ yarn hardhat:compile && yarn components:build && yarn pixel:build && yarn frontend:build
6:33:10 PM: yarn run v1.22.10
6:33:10 PM: $ yarn workspace @pixly/hardhat compile
6:33:11 PM: $ npx hardhat compile
6:33:19 PM: Solidity 0.8.11 is not fully supported yet. You can still use Hardhat, but some features, like stack traces, might not work correctly.
6:33:19 PM:
6:33:19 PM: Learn more at https://hardhat.org/reference/solidity-support
6:33:19 PM:
6:33:22 PM: Downloading compiler 0.8.11
6:33:23 PM: Compiling 28 files with 0.8.11
6:33:28 PM: Warning: Visibility for constructor is ignored. If you want the contract to be non-deployable, making it "abstract" is sufficient.
6:33:28 PM:   --> contracts/RleRendererV3.sol:10:5:
6:33:28 PM:    |
6:33:28 PM: 10 |     constructor () public {
6:33:28 PM:    |     ^ (Relevant source part starts here and spans across multiple lines).
6:33:28 PM:
6:33:28 PM:
6:33:28 PM: Warning: Unnamed return variable can remain unassigned. Add an explicit return with value to all non-reverting code paths or name the variable.
6:33:28 PM:   --> contracts/Frames.sol:14:13:
6:33:28 PM:    |
6:33:28 PM: 14 |             string memory,
6:33:28 PM:    |             ^^^^^^^^^^^^^
6:33:28 PM:
6:33:28 PM:
6:33:28 PM: Warning: Unnamed return variable can remain unassigned. Add an explicit return with value to all non-reverting code paths or name the variable.
6:33:28 PM:   --> contracts/Frames.sol:15:13:
6:33:28 PM:    |
6:33:28 PM: 15 |             uint256,
6:33:28 PM:    |             ^^^^^^^
6:33:28 PM:
6:33:28 PM:
6:33:28 PM: Warning: Unnamed return variable can remain unassigned. Add an explicit return with value to all non-reverting code paths or name the variable.
6:33:28 PM:   --> contracts/Frames.sol:16:13:
6:33:28 PM:    |
6:33:28 PM: 16 |             string[] memory
6:33:28 PM:    |             ^^^^^^^^^^^^^^^
6:33:28 PM:
6:33:28 PM:
6:33:28 PM: Warning: Unnamed return variable can remain unassigned. Add an explicit return with value to all non-reverting code paths or name the variable.
6:33:28 PM:    --> contracts/Frames.sol:148:30:
6:33:28 PM:     |
6:33:28 PM: 148 |     ) internal pure returns (uint256) {
6:33:28 PM:     |                              ^^^^^^^
6:33:28 PM:
6:33:28 PM:
6:33:29 PM: Warning: SPDX license identifier not provided in source file. Before publishing, consider adding a comment containing "SPDX-License-Identifier: <SPDX-License>" to each source file. Use "SPDX-License-Identifier: UNLICENSED" for non-open-source code. Please see https://spdx.org/ for more information.
6:33:29 PM: --> contracts/Multicall.sol
6:33:29 PM:
6:33:29 PM:
6:33:29 PM: Generating typings for: 28 artifacts in dir: ../frontend/types/typechain for target: ethers-v5
6:33:32 PM: Successfully generated 45 typings!
6:33:32 PM: Compilation finished successfully
6:33:32 PM: Done in 21.83s.
6:33:32 PM: yarn run v1.22.10
6:33:32 PM: $ yarn workspace @pixly/ui-components build
6:33:33 PM: warning package.json: No license field
6:33:33 PM: $ tsc --build
6:33:33 PM: Done in 1.09s.
6:33:34 PM: yarn run v1.22.10
6:33:34 PM: $ yarn workspace @pixly/pixel-art-react build
6:33:34 PM: $ NODE_ENV=production webpack -p --config webpack.production.config.js
6:33:45 PM: Done in 11.24s.
6:33:45 PM: yarn run v1.22.10
6:33:45 PM: $ yarn workspace @pixly/frontend build
6:33:46 PM: warning package.json: "dependencies" has dependency "eslint-config-next" with range "^12.0.0" that collides with a dependency in "devDependencies" of the same name with version "^11.0.1"
6:33:46 PM: $ next build
6:33:47 PM: info  - Checking validity of types...
6:34:00 PM: warn  - The Next.js plugin was not detected in your ESLint configuration.  Functions bundling
6:34:22 PM: ────────────────────────────────────────────────────────────────
6:34:22 PM:
6:34:22 PM: Packaging Functions from .netlify/functions-internal directory:
6:34:22 PM:  - ___netlify-handler/___netlify-handler.js
6:34:22 PM:  - ___netlify-odb-handler/___netlify-odb-handler.js
6:34:22 PM:  - _ipx/_ipx.js
6:34:22 PM:
6:34:59 PM:
6:34:59 PM: (Functions bundling completed in 36.8s)
6:34:59 PM:
6:34:59 PM: ────────────────────────────────────────────────────────────────
6:34:59 PM:   5. @netlify/plugin-nextjs (onPostBuild event)
6:34:59 PM: ────────────────────────────────────────────────────────────────
6:34:59 PM:
6:34:59 PM: Next.js cache saved.
6:34:59 PM:
6:34:59 PM: (@netlify/plugin-nextjs onPostBuild completed in 362ms)
6:34:59 PM:
6:34:59 PM: ────────────────────────────────────────────────────────────────
6:34:59 PM:   6. Deploy site
6:34:59 PM: ────────────────────────────────────────────────────────────────
6:34:59 PM:
6:34:59 PM: Starting to deploy site from 'packages/frontend/.next'
6:35:00 PM: Creating deploy tree
6:35:00 PM: Creating deploy upload records
6:35:00 PM: 19 new files to upload
6:35:00 PM: 3 new functions to upload
6:35:09 PM: Site deploy was successfully initiated
6:35:09 PM:
6:35:09 PM: (Deploy site completed in 9.3s)
6:35:09 PM:
6:35:09 PM: ────────────────────────────────────────────────────────────────
6:35:09 PM:   Netlify Build Complete
6:35:09 PM: ────────────────────────────────────────────────────────────────
6:35:09 PM:
6:35:09 PM: (Netlify Build completed in 2m 1.5s)
6:35:09 PM: Starting post processing
6:35:09 PM: Post processing - HTML
6:35:09 PM: Caching artifacts
6:35:09 PM: Started saving workspace packages/frontend node modules
6:35:09 PM: Finished saving workspace packages/frontend node modules
6:35:09 PM: Started saving workspace packages/hardhat node modules
6:35:09 PM: Finished saving workspace packages/hardhat node modules
6:35:09 PM: Started saving workspace packages/pixel-art-react node modules
6:35:09 PM: Finished saving workspace packages/pixel-art-react node modules
6:35:09 PM: Started saving workspace packages/ui-components node modules
6:35:09 PM: Finished saving workspace packages/ui-components node modules
6:35:09 PM: Started saving workspace root node modules
6:35:09 PM: Finished saving workspace root node modules
6:35:09 PM: Started saving build plugins
6:35:09 PM: Finished saving build plugins
6:35:09 PM: Started saving yarn cache
6:35:09 PM: Post processing - header rules
6:35:09 PM: Post processing - redirect rules
6:35:10 PM: Post processing done
6:35:11 PM: Site is live ✨
6:35:24 PM: Finished saving yarn cache
6:35:24 PM: Started saving pip cache
6:35:24 PM: Finished saving pip cache
6:35:24 PM: Started saving emacs cask dependencies
6:35:24 PM: Finished saving emacs cask dependencies
6:35:24 PM: Started saving maven dependencies
6:35:24 PM: Finished saving maven dependencies
6:35:24 PM: Started saving boot dependencies
6:35:25 PM: Finished saving boot dependencies
6:35:25 PM: Started saving rust rustup cache
6:35:25 PM: Finished saving rust rustup cache
6:35:25 PM: Started saving go dependencies
6:35:25 PM: Finished saving go dependencies
6:35:25 PM: Build script success
6:38:13 PM: Finished processing build request in 7m2.047346671s```

</details>

### Function logs

<details>
  <summary>Function logs</summary>

01:54:15 PM: c9f3c7a0 INFO   [GET] /pixlies/17?chainId=80001 (SSR)
01:54:15 PM: c9f3c7a0 Duration: 41.14 ms	Memory Usage: 145 MB	01:54:16 PM: 62255a1a ERROR  Error: Cannot find module 'sharp'
Require stack:

/var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js
/var/task/node_modules/next/dist/server/next-server.js
/var/task/.netlify/functions-internal/___netlify-handler/handlerUtils.js
/var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.js
/var/task/___netlify-handler.js
/var/runtime/UserFunction.js
/var/runtime/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:93:18)
at Module.9359 (/var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js:20:40)
at webpack_require (/var/task/packages/frontend/.next/server/webpack-runtime.js:25:43)
at webpack_exec (/var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js:126:39)
at /var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js:127:78
at Function.webpack_require.X (/var/task/packages/frontend/.next/server/webpack-runtime.js:108:21)
at /var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js:127:47 {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/var/task/packages/frontend/.next/server/pages/api/pixlies/[tokenId]/png.js',
'/var/task/node_modules/next/dist/server/next-server.js',
'/var/task/.netlify/functions-internal/___netlify-handler/handlerUtils.js',
'/var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.js',
'/var/task/___netlify-handler.js',
'/var/runtime/UserFunction.js',
'/var/runtime/index.js'
]
}

</details>

### .next JSON files

<details>
  <summary>generated .next JSON files</summary>

Paste file contents here. Please check there isn't any private info in them
You can either build locally, or download the deploy from Netlify by clicking the arrow next to the deploy time.

</details>

I was able to fix my issue by using yarn package aliases, like
yarn workspace @pixly/frontend add mysharp@npm:sharp

and then importing mysharp instead of sharp.

are there any better ideas on how to fix it?

So the issue is that sharp is excluded from the bundle to keep the size reasonable. For our project we created a custom netlify build plugin that removes the exclusion.
What we did:

We have a plugin folder include_sharp/ in our project with a package.json:

{
  "name": "include_sharp",
  "version": "1.0.0",
  "main": "index.js"
}

We have a plugin manifest manifest.yml:

name: include_sharp

And the plugin code itself in the index.js:

module.exports = {
  async onBuild({ netlifyConfig }) {
    const fn = netlifyConfig.functions['___netlify-handler'];

    fn.included_files = fn.included_files.filter(
      (f) => f !== '!node_modules/sharp/**/*'
    );
  },
};

In the end we reference the plugin in our netlify.toml, after the netlify-plugin-nextjs plugin:

[[plugins]]
  package = "@netlify/plugin-nextjs"

[[plugins]]
  package = "./include_sharp"

This way the sharp module is not excluded from the bundle anymore. This is kind of a hack, but works without additional external packages.

I was able to fix my issue by using yarn package aliases, like
yarn workspace @pixly/frontend add mysharp@npm:sharp

 Save
and then importing mysharp instead of sharp.

I tried a variety of things including the include_sharp suggestion above, but setting a package alias was the only thing that worked for me. Thank you.

https://github.com/netlify/next-runtime/pull/1745
This issue has been solved here. To include sharp, add it to included_files in your netlify.toml


Try again to preserve undo history

Closes #15.

It seems that undo-amalgamate-change-group is not available prior to Emacs 26. Should we just paste in the source? Or should we simply drop support for 25?

Emacs 25 is still used enough that I think I'd prefer to continue supporting it. In particular it's shipped with the second-to-latest Ubuntu LTS which most people are probably still on who run Ubuntu LTS.
Pasting in the definition is fine, here is an example of how to do that.

I closed the PR since it didn't seem to do anything to alleviate the problem of large entries in buffer-undo-list.
Tha markers generated within apheleia--apply-rcs-patch seem to be accounting for much of the size of each entry within buffer-undo-list. But from a glance at the code, the markers look pretty important, so I'm not sure how the space usage of this function can be cut down.

Oh, huh. I didn't realize markers got recorded in the undo history. I guess that makes sense though. Do we clean them up properly? I don't see anything for that in the code. Perhaps they are accumulating over time and the undo history is getting exponentially bigger because of all the markers getting moved around.


Add atexit handler

This will pause the app before exit in a portable manner

I think it's no necessary to put atexit() in public area of main function,because application can disable all console output by NO_CUI macro in my design.Put it into NO_CUI macro area will be better.


Indexing plain objects without entitymanager

Description
I've been briefly looking through the Wiki and I cannot find an example that shows if it's possible to use plain objects/models/DTOs and index them with this bundle. I've found in the code that the SearchService can perform rawSearch, which I assume works for any non-entities as well (?), but I don't see a similar indexing method for this kind of "raw" indexing.
So my question follows: is indexing of plain objects supported?
Basic example

If it's already possible with the SearchService to index plain objects, I'd appreciate an example (and update the Wiki accordingly).
If this is not possible, maybe I'm better of with using meilisearch-php directly?

Other
I'm new to Meilisearch 🙂

Currently not, but I've plans to implement this in future

Hey @norkunas 👋
Thanks for the quick response. I'll be eagerly waiting until then 👌

I, too, would like to see this bundle de-coupled from the EntityManager.  I use the meilisearch-php library to index plain objects, as I'm working on a project to index csv files and it bypasses doctrine altogether.

https://symfony.com/blog/migrating-symfony-com-search-engine-to-meilisearch

There is a Meilisearch Symfony bundle, but we don't use it because ... it's mainly focused on indexing Doctrine entities/documents.

Symfony documentation is built with the symfony-tools/docs-builder, which parses RST documents and outputs JSON files with a certain structure (title, body, TOC, pagination, etc.) That's why we used instead the Meilisearch PHP integration [instead of the bundle]

I think this situation is very common, to want to index data without using Doctrine.  While it's a cool feature of the bundle to have a listener and updating the meili index in the background when a doctrine entity has been changed, I don't think is should be the only way to update an index.
In fact, I would use this bundle just for the still-unmerged debug toolbar.  Currently I use the Symfony HTTP client to update meili, so I can debug the HTTP requests, but a dedicated toolbar would rock.

I still pursue it, just need more time

@ToshY Cool, thanks, I'll check it out.
I have a meilisearch service in a bundle that integrates datatables.net with api-platform, it works great but I now need the same functionality in another bundle.  So I'm trying to extract my service which has no application-specific logic, just a wrapper around creating indexes including some async stuff.  Like getting stats for the index, which obviously can't be done until the index is finished.
    public function waitUntilFinished(Indexes $index, SymfonyStyle $io = null): array
    {
        do {
            $index->fetchInfo();
            $info = $index->fetchInfo();
            $stats = $index->stats();
            $isIndexing = $stats['isIndexing'];
            $indexName = $index->getUid();
            if ($this->logger) {
                $this->logger->info(sprintf("\n%s is %s with %d documents",
                    $indexName, $isIndexing ? 'indexing' : 'ready', $stats['numberOfDocuments']));
            }
            if ($isIndexing) {
                sleep(1);
            }
        } while ($isIndexing);
        return $stats;
    }

Anyway, just brainstorming, I'd love to drop my service and use this bundle or the package you recommended.


Store run-time property lists in scalar arrays

This stores the HDF5 property lists that are created during module initialization using a scalar array for each property, which avoids the use of hard-coded indices.

Julia nightly appears to fail on import Blosc:
Julia Version 0.4.0-dev+6531
Commit e6180f0 (2015-08-07 23:10 UTC)

ERROR: LoadError: LoadError: LoadError: LoadError: __precompile__(true) but require failed to create a precompiled cache file
 in require at ./loading.jl:211
 in include at ./boot.jl:254
 in include_from_node1 at ./loading.jl:263
 in include at ./boot.jl:254
 in include_from_node1 at ./loading.jl:263
 in include at ./boot.jl:254
 in include_from_node1 at ./loading.jl:263
 in require at ./loading.jl:202
 in include at ./boot.jl:254
 in include_from_node1 at ./loading.jl:263
 in process_options at ./client.jl:308
 in _start at ./client.jl:411
while loading /home/travis/.julia/v0.4/HDF5/src/blosc_filter.jl, in expression starting on line 1
while loading /home/travis/.julia/v0.4/HDF5/src/plain.jl, in expression starting on line 509
while loading /home/travis/.julia/v0.4/HDF5/src/HDF5.jl, in expression starting on line 1
while loading /home/travis/.julia/v0.4/HDF5/test/runtests.jl, in expression starting on line 1

This looks like a nice change, :+1:. Once we require julia 0.4, we'll probably want to switch to a Ref.
Re the Blosc/precompilation failure: CC @stevengj. Blosc works fine for me locally. A couple of lines above that Travis error are interesting, too:
INFO: Recompiling stale cache file /home/travis/.julia/lib/v0.4/Blosc.ji for module Blosc.
WARNING: Module Compat uuid did not match cache file
ERROR: LoadError: LoadError: LoadError: LoadError: __precompile__(true) but require failed to create a precompiled cache file
...

@petercolberg, that is JuliaLang/julia#12508.   It will go away once a new Compat is tagged, but for now you can just quit Julia and try again and it will work the second time.

I just tagged a new version of Compat (https://github.com/JuliaLang/METADATA.jl/pull/3042), since all HDF5/JLD PRs are failing Travis tests.

Thanks, @petercolberg.


double publish attempt for io.js

One travis build is harmlessly failing since it looks like a double publish is being attempted: https://travis-ci.org/mapbox/node-sqlite3/jobs/50288165

looks like the 32 bit version failed (perhaps the 32 bit is being built as 64)

fixed by 131a8f9f9551c813fa44cf1ae, refs https://github.com/iojs/build/issues/45


blank custom_schemas after user creation

I am creating a new user and inserting some custom data in custom_schemas property of a AdminDirectoryV1 :: User object :
new_user = Google::Apis::AdminDirectoryV1::User.new
new_user.primary_email =<EMAIL_ADDRESS>new_user.password ='teste'
new_user.org_unit_path = '/Test'
new_user.custom_schemas = {"test" => "my custom value"}

name = Google::Apis::AdminDirectoryV1::UserName.new
name.given_name = "Test"
name.family_name = "Google API Test"

new_user.name = name
service.insert_user(new_user)

This way I'm able to register the user normally. But I am not able to retrieve the information you have saved custom_schemas.
I am seeking users like this:
response = service.list_users(customer: 'my_customer',
                              max_results: 500,
                              projection: 'full',
                              query: 'orgUnitPath=/Test',
                              order_by: 'email')

When I try to access the property this way:
response.users.each { |user|

puts user.custom_schemas

}

It returns me just an empty line in the console (empty hash).
I have looked in the documentation and examples and apparently I'm not doing anything wrong , at least not in the user creation time .
Somebody else had this problem ?

You're using the wrong value for custom schema. As in the docs, it's not a flat hash of key/value pairs. Instead, it's a set of nested hashes. The top is a hash of schema names -> hash. The nested hashes contain the actual key/value pairs for your specific schema.
I don't know your specific schema name, but should be something like:
new_user.custom_schemas = {
  "my_schema_name" => { "test" => "my custom value"}
}

If the schema is not defined you'll get an error. You can call insert_schema to create the schema if needed.
Interestingly, looks like a minor bug on the server -- it should have rejected your request with a 40x error.

Thanks for the help Steve .
It is now giving error as expected because not yet created the scheme .
In fact I had already seen this error I'm getting now . But as he was taking the wrong way I was doing, just ignored .


Is it possible to save the potts params used for sequence sampling?

Is it possible to save the potts params (L,A) and (L,A,L,A) given structure, used for sequence sampling at the design stage?

nvm found it!


Create a ValidatingAdmissionPolicy for MeshConfig

For CRDs, we are largely moving away from webhook to native validation (https://github.com/istio/istio/issues/46151) (not really away for awhile, but augment it).
For MeshConfig, its a configmap so we don't have the same choice. We could add a webhook for that, but doesn't seem great since webhooks are kind of problematic, and has a somewhat circular dependency on Istio
https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy fix all of these problems. They are beta in 1.28. We should make a VAP for MeshConfig. It may not be ready for inclusion in core yet, but it can be a standalone yaml folks can apply

For complex validation, it seems webhook can not easily be replaced by Validating Admission Policy.

doesn't seem great since webhooks are kind of problematic, and has a somewhat circular dependency on Istio

CM validation is similar as other Istio APIs, is there any diff.  validation is part of istiod,, so what circular dependency?

For complex validation, it seems webhook can not easily be replaced by Validating Admission Policy.

doesn't seem great since webhooks are kind of problematic, and has a somewhat circular dependency on Istio

CM validation is similar as other Istio APIs, is there any diff. validation is part of istiod,, so what circular dependency?

Istiod needs the config map to start with correct config, but istiod needs to be started to write the config map.
Probably we could workaround it but still a bit risky

IC, this is something that can fail startup.

Hello. I would like to work on this :)

Not stale
On Wed, Jan 24, 2024, 10:34 AM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2023-10-26.
It will be closed on 2024-02-08 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/47593#issuecomment-1907384866, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCAXD23OQLMORP6XAWMRSLYQCI4LAVCNFSM6AAAAAA6QAL5BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBXGM4DIOBWGY
.
You are receiving this because you were assigned.Message ID:
@.***>

not stale

Just a bit caught up. Will be spending time on it this week.

Since writing this I think there is an issue. MeshConfig is really 1 key and a big string. CEL cannot really parse that

I don't have enough knowledge on it to comment but will changing the parsing logic help?

CEL is a limited language, it cannot parse YAML at all

I see. So what do you suggest?

https://github.com/istio/istio/issues/48991#issuecomment-1922660112

in Bootstrap stop loading the meshConfiguration if it is invalid, and using the default meshConfig.
Adding we validating webhook for meshConfig, and prevent updating invalid config.

It is to validate in two places, both webhook and istiod startup. I believe it works

Ok, I guess according to @hzxuzhonghu we can make it work. I can start with the implementation.


First attempt to add WEB client to the streaming emformer.

It supports reading a wav file from the client and sends it to the server for recognition at present.
Note: Even though we send all the samples at once, the server supports accepting samples coming in a streaming fashion.
Example screen recording:
https://user-images.githubusercontent.com/5284924/167114390-de28e2c7-4f97-4641-b5ff-bfe71f0554e8.mov

I also use websocket, it is in python. I think they are similar, but mine is very simple, I implement it in case we will need a demo for speechhome meeting. @csukuangfj  you can go ahead, I have not done much survey about the server framework.

The following is a demo for streaming recognition from real-time recordings.
https://user-images.githubusercontent.com/5284924/167253183-7115a96e-1095-4145-969b-69d72079e043.mov

wow, nice!! Does this actually reflect when it is doing the recognition?

Do you mean the tail padding issue? I think this PR is using a version of beam search before we fix the padding issue.

I meant the video plays audio and shows recognition, I wonder if this is somehow "real" and reflects how fast you could recognize real live audio.

It looks like it has sth around 200-300ms latency between the time I hear a word and it appears in the recognition, I'd that's easily representative of actual live performance.

I meant the video plays audio and shows recognition, I wonder if this is somehow "real" and reflects how fast you could recognize real live audio.

Yes, I replayed two test waves from the test-clean dataset from my phone.


Change the banner "General banner level" input from text to a drop down menu

The "General banner level" has four parameters that change the color of the banner.  The four parameters must be typed in.  Instead of typing the values into a text box, the four values should be displayed in a drop down menu.
Instead of displaying the four parameter values of "Error," "Notice" etc, just display the banner color (i.e. red, blue, green and yellow) as drop down values.
The "General banner level" only affects the banner color.  It does not change the banner's default wording.  The banner's default wording is "Announcement:"

Added to #1965


Identity providing for users with multiple MSISDNs

Hello,
Reviewing the minutes of the meeting I have noticed that maybe there is a bit of misunderstanding within the client identity providing process. @deepakjaiswal1  commented that the current version of the API does not support choosing the line to be used for registration. It retrieves the MSISDN based on the deviceid provided by the client.
Our vision is that, in cases where the user possesses multiple MSISDNs, the selection of the desired MSISDN does not depend on the API but rather on the IdP from the Telco. As the basic scenario for which this BYON API is intended is a device without a simcard or a webbrowser. The deviceId stands for the device where the BYON feature is being deployed. Then we consider that no further development of the API might be needed regarding this topic.
Are we all alligned on this?

There are two topics here for discussion,
1 – Identity to be used for authentication and user profile retrieval from IDP.
The RACM Request API has defined “userid” and “deviceId”. The deviceid is the unique device id while userid could be any Operator provided identity. Mavenir implementation previously used msisdn as userid, but we are ok to change this, if msisdn can be retrieved from the IDP. The key to be used for user profile retrieval from the IDP would be the SSO Access Token included in the RACM Request API (included as part of the Authorization header).
We are aligned in principle for not sending MSISDN in the RACM API, but it would be good to discuss and align how this work end to end.
2 – Line (aka MSISDN or Phone number) selection to be used for network registration.
In line with my response to #1 above, our opinion here is to keep Line/MSISDN selection outside the communication API. The client must first be made aware of all the lines available for selection, and this comes under the provisioning scope. This should be done as part of the overall device management procedure, which can be separate API outside of the scope of comms API. From the dependency on IMS Registration, the WebRTC GW should support implicit registration of all the provisioned lines retrieved from the IDP. This avoids the client complexity for the Line to be explicitly registered and keeps the UX simple. Line selection will be required for call origination, and for this the existing Call API already has the parameter defined for capturing Originator’s address. In summary, our response is not to take this up into the RACM API.

Aligned with both cases.

We dont see the necessity to handle the MSISDN within the RACM API as long as you have the IdP Token. This way, maybe we need to figure out which parameter should be used instead or even whether it is not necessary to have the userID param and can be deleted. I also have a question regarding why is it important to have the deviceID param. I assume it is because there could be multiple webRTC devices that can be registered for the same user but if you can please clarify this...
Agree. This should be done outside the API scope

I am in agreement with both cases and would like to offer a probable end to end flow for better clarity. In the context of the login process (following the login itself), there will be a user experience provided for selecting a line on a specific device, referred to as device-X. The user's selection will be stored in their user profile within the identity provider (iDP). The WebRTC Gateway will register lines that are designated as active or provisioned for device-X. It's important to note that the UserID can be omitted, but the device ID is essential. Our objective is to support a single registration for each device associated with a specific MSISDN. In the event of multiple registration requests from the same device, the previous registration should be cleared to enable re-login without a clean logout.

We should also clarify what we understand for "deviceID", specially when the users are using a browser where several tabs can be open at the same time. We can still provide "single registration" if we consider that each tab is a new deviceID (if this is a use case that we can to consider).

If we treat each browser tab as a distinct device, it could potentially lead to multiple registrations for the same browser. In such a scenario, if a user registers the same line on multiple tabs, it would result in multiple simultaneous rings for a single incoming call, causing confusion. To enhance the user experience, we've chosen to use the same deviceID for each tab when providing a similar service. This approach ensures that registration is limited to a single instance per browser, avoiding any such confusion.


Can O' Spam: Watch kisankalyanfoundation.com

Can O' Spam requests the watch of the watch_keyword kisankalyanfoundation\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

kisankalyanfoundation\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


[BUG] - Type instantiation is excessively deep and possibly infinite.

Describe the bug
Not sure if a bug, but when I tried to use the toFormikValidationSchema(Schema), I get a warning saying Type instantiation is excessively deep and possibly infinite.. This seems to stress the typescript server in vs code. If I comment out this line validationSchema={toFormikValidationSchema(Schema)} then VS Code works as expected. Not sure why this is. I have not had this problem in the past. I just updated to version 1.2.0.
To Reproduce
Steps to reproduce the behavior:

Update to version 1.2.0
Add validationSchema={toFormikValidationSchema(Schema)} to your Formik component
It should give a warning about Type instantiation is excessively deep and possibly infinite

Expected behavior
I expect the code to not give errors and validate my form as expected
Screenshots

Desktop (please complete the following information):

MacOS Ventura 13.1

Node version:
Zod, Formik and zod-formik-adapter versions:
zod: "^3.20.2",
zod-formik-adapter: "^1.2.0",
formik: "^2.2.9"
Additional context
I have tried to turn my computer on and off, restarted the ts server in vs code, and restarted vs code. It only seems to be working correctly if I do not include the validationSchema.
import { BodyLong, Heading, TextField } from "@navikt/ds-react";
import { FieldHookConfig, Form, Formik, useField } from "formik";
import { z } from "zod";
import { toFormikValidationSchema } from "zod-formik-adapter";
import styles from "../tiltaksgjennomforinger/Oversikt.module.scss";

const Schema = z.object({
  tiltakstypenavn: z.string({ required_error: "Tiltakstypen må ha et navn" }),
});

type SchemaValues = z.infer<typeof Schema>;

function Tekstfelt({
  label,
  name,
  ...props
}: { name: keyof SchemaValues; label: string } & FieldHookConfig<any>) {
  const [field, meta] = useField({ name, ...props });
  return <TextField label={label} {...field} error={meta.error} />;
}

export function OpprettTiltakstype() {
  const initialValues = { tiltakstypenavn: "" };
  return (
    <>
      <Heading className={styles.overskrift} size="large">
        Opprett ny tiltakstype
      </Heading>
      <BodyLong className={styles.body} size="small">
        Her kan du opprette eller redigere en tiltakstype
      </BodyLong>
      <Formik<SchemaValues>
        initialValues={initialValues}
        validationSchema={toFormikValidationSchema(Schema)} // TODO Se på toFormikValidationSchema og hvorfor den kneler Typescript-serveren
        onSubmit={(values, actions) => {
          setTimeout(() => {
            alert(JSON.stringify(values, null, 2));
            actions.setSubmitting(false);
          }, 1000);
        }}
      >
        {() => (
          <Form>
            <Tekstfelt name="tiltakstypenavn" label="Navn" />
            <button type="submit">Opprett</button>
          </Form>
        )}
      </Formik>
    </>
  );
}

If i downgrade to 1.1.1 then everything works as expected

Can you also provide the Typescript version that your TS server is using?

4.9.4 is the typescript version being used. I have updated my original question as well.

FWIW, I'm also seeing this error on 1.2.0 with TypeScript 4.7.4
Best I can tell, the only change since 1.1.1 that could possibly impact toFormikValidationSchema behavior would be the change from Zod ~3.14.4 to ^3.14.4, since Zod is up to 3.20.2 now. 🤔
Unfortunately, if I downgrade my project to exactly Zod 3.14.4 while remaining on Zod Formik Adapter 1.2.0, then restart my TS server in VS Code, the error still occurs! 😖 NPM dependency hell is "fun" to troubleshoot when project behavior can differ by when dependencies were frozen in lockfile.
For now, downgrading both zod & zod-formik-adapter is the only thing that provides relief:
"zod": "~3.14.4",
"zod-formik-adapter": "~1.1.1"

This issue happens to me, as well 😦
"typescript": "5.1.6",
(...)
"zod": "^3.22.4",
"zod-formik-adapter": "^1.2.0",

I'm getting this error as well, has there been any fix ?

Same here on 1.3.0. The only solution I could find for now is either to @ts-ignore it or downgrade to 1.1.1 as per @sndrem's answer.


Newbodies added to bodies module

Addresses #234
I have added class for moon and other planets of solar system + Pluto to bodies.py .I have used all data from NASA JPL.
@shreyasbapat @ritzvik please review it

Should I write tests for it too before merging?

@abhijeetmanhas indeed. Tests are important. :)

@shreyasbapat
I've not developed the bodies module, but still, here's my two cents.

It wasn't a wise design decision to have BlahBlahBody = _BlahBlahBody() because each time we import anything from bodies module, all 11 __init__() in all predefined bodies are getting executed, making the module slow!
Further, we are not giving user the freedom to make different instances of the same class. We are giving them predefined instances. Now it may be possible that the user might want 2 different instances of _Sun(), one with a slight change in it, but he won't be able to do that easily.

Well, it was never intended to have solar system bodies

It was mentioned in comments of bodies.py that it was supposed to have predefined bodies, I added those. I also thought that writing body = _body will make it slow, but I found it was done for sun and earth, so I followed same format.
So should I remove all lines containing body = _body even for earth and sun? Or should I not create different classes for other planets, but store their attributes in some dictionary and  create 3 parent classes: star, planet & satellite?


feat: Add secrecy crate feature

Hey 👋
This PR adds the ability to use secrecy::Secret<T> from the secrecy crate as an sqlx::Type.
Example:
#[derive(Debug, FromRow)]
pub struct User {
    pub id: i32,
    pub email_address: String,
    pub password_hash: secrecy::Secret<String>,
}

I'm personally not inclined to merge this because I still stand by what I stated in #613. Using secrecy is just plugging one hole in a very leaky dam and I'm worried about luring people into a false sense of security.
If you really care about security then using secrecy should be only one small part of a comprehensive hardening effort. Until such effort materializes I feel like using secrecy is just security theater.

@abonander Your concerns are fair and I didn't notice #613 before making this PR.
I'll close this for now.


Constrain dependency according to Rails' shifted semver

Per @rafaelfranca's (a member of the Rails core team) comment[1]:

I'd not do this. 5.2 may contains breaking changes, usually for gems of this size it works, but the Rails team doesn't recommend to use the same rules as the semver since we use shifted semver.

1: https://github.com/activemerchant/offsite_payments/commit/cc772fdf6115ce2a4bbc73c99b58a70f60908a28#commitcomment-22021971

Ah, I see here and here that there was some discussion about the reasons to go with 6.x. Nonetheless, I think @rafaelfranca's comment should be taken into consideration.
Either way, I'd like Rails 5.1 support! Thanks!

Thanks!


Measure use of unlisted_choice in LEAP hub to see if anyone is actually using it.

@jmunroe this is probably tied into talking to the community champion as well. https://jupyterhub-grafana.readthedocs.io/en/latest/ has some info on how to use the dashboard to see this.


Keyword-only arguments

Keyword-only arguments are described in a Python PEP: https://www.python.org/dev/peps/pep-3102/
Examples:
def compare(a, b, *, key=None): ...

def sortwords(*wordlist, case_sensitive=False): ...

It is supported in the Java implementation. There was a desire to remove this feature, to keep Starlark a subset of Python 2 and Python 3 syntax. However, this feature is useful and often requested:

Many builtins use it
Documentation in Bazel uses that syntax
Macros in Bazel shouldn't allow positional arguments, for maintenance reasons

This doesn't conflict with https://github.com/bazelbuild/starlark/issues/13#issuecomment-433995990, because #13 concerns only the call sites. The current issue concerns only the definition sites.

I'm not averse to it; the ability to require named arguments at call sites does improve maintainability.
I have an implementation for Starlark-go in https://github.com/google/starlark-go/pull/62.

Let's add keyword-only arguments to the specification.

Sounds good to me. I'll dust off that implementation.

Can we also have support for required keyword-only parameters? Currently required parameters must be positional, which makes it easy for calling code to accidentally forget to use kwarg style. Python 3 supports the notion of "this parameter is required, and must be named".
def foo(ctx, *, source, options = []):
  print("source: {}, options: {}".format(source, options))

>>> foo(ctx)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: foo() missing 1 required keyword-only argument: 'source'

>>> foo(ctx, ctx.file.src)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: foo() takes 1 positional argument but 2 were given

>>> foo(ctx, source = ctx.file.src)
source: <generated file>, options: []
>>>

Yes, we can we also have support for required keyword-only parameters. It's a nice feature and it's not hard to implement. It's already done in Starlark-in-Java,  and I just mailed out a CL for it in Go.

It's disabled in Starlark-in-Java at the moment (for no good reason), but I can re-enable it.

https://github.com/google/starlark-go/pull/151 added this feature to the Go implementation and its documentation.

Hi, does Starlark support keyword-only arguments that aren't optional?
For optional keyword-only arguments Bazel seems to work fine, but for required ones I get Keyword-only argument is forbidden.

It's disabled in Starlark-in-Java at the moment (for no good reason), but I can re-enable it.

I've filed https://github.com/bazelbuild/bazel/issues/10416 to request re-enabling mandatory keyword parameters in Java Starlark.

Since https://github.com/bazelbuild/bazel/issues/10416 is now fixed, could this please be documented in the spec?


Fine-tune PR titles in Renovate PRs

I was too fast merging https://github.com/statnett/image-scanner-operator/pull/171, as this should have been classified as a user-facing change and appeared in the changelog.
Can Renovate be configured to use a different PR title depending on the suggested change? As we can do with Dependabot, ref.
https://github.com/statnett/image-scanner-operator/blob/main/.github/dependabot.yml#L9-L11

That is possible, more fine-grained than I initially thought (by using semanticCommitType in a packageRule with a matcher). We can set PR title based on many attributes of a dependency, e.g. what type of dependency it is (docker, golang etc.), name of the dependency (either perfect match or regex match), pattern of package path (e.g. everything in test/ folder should have a specific PR title).
Trivy (ghcr.io/aquasecurity/trivy) is a candidate, it is a docker dependency so we can match it on either docker or name. But we don't want docker dependencies like https://github.com/statnett/image-scanner-operator/pull/158 to be build, so maybe not based docker?


Feat/clean import

This pull request addresses the messy import issue.
Now there is no from x import * in main_eval.py.
However, absolute path is needed in the configuration file if a class is defined locally by ourselves.


Latest version of Xcode is too outdated (Macos)

==> Installing tetris from samtay/tui
Error: Your Xcode (14.0.1) is too outdated.
Please update to Xcode 14.1 (or delete it).
Xcode can be updated from the App Store.

Looks like you need to update Xcode. This is unrelated to this project.

Well at that point 14.0.1 was the latest version for we. But 14.1 is now available, so I'll try with that


Still showing sent NFT when using 2 different browser

Description of the bug
Still showing sent NFT when using 2 different browser
To reproduce the bug
Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-build-1.0.2-1-2023-04-17T07-59-29UTC.zip
Pre-condition: Open 2 different browsers A & B and use the same account
Steps:

In browser A, send NFT successfully
In browser B, observe the information displayed

Actual: Still showing sent NFT
Expect: Do not show sent NFT

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1271-build-1.0.2-1-2023-04-21T12-01-24UTC.zip
Validation passed!


Synthesis failed for Google.Cloud.Asset.V1Beta1

Hello! Autosynth couldn't regenerate Google.Cloud.Asset.V1Beta1. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-Google.Cloud.Asset.V1Beta1'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
    last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
    text=True,
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

Google internal developers can see the full log here.

Autosynth is still having trouble generating Google.Cloud.Asset.V1Beta1. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-Google.Cloud.Asset.V1Beta1'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
    last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
    text=True,
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


UcscTrack() not recognizing some tracks

Hi there,
What a fantastic package! Really intuitive and flexible; exactly what I've been looking for. That said, I don't seem to be able to access the UCSC nuclei tracks through the UcscTrack() function.
Specifically, the hub_400557_human_microglia_H3K27ac_exvivo_pooled_hg19 table within the nuclei_h3k27ac_hg19_pooled track (though I plan to query the other nuclei tracks as well).
Thanks in advance!,
Brian
Input
  # UCSC Tracks
  conservation <- UcscTrack(genome="hg19",
                            chromosome="chr12",
                            from = "40590585", to = "40763013",
                            width=1,
                            trackType="DataTrack",

                            track="nuclei_h3k27ac_hg19_pooled",
                            name="nuclei_h3k27ac_hg19_pooled",
                            table="hub_400557_human_microglia_H3K27ac_exvivo_pooled_hg19"
                            )

Output
rror in match.arg(track, sort(c(availTracks, names(availTracks)))) :
  'arg' should be one of "1000G Ph1 Accsbl", "1000G Ph1 Vars", "1000G Ph3 Accsbl", "1000G Ph3 Vars", "5% Lowest S", "acembly", "AceView Genes", "Affy Exon Array", "Affy GNF1H", "Affy RNA Loc", "Affy U133", "Affy U133Plus2", "Affy U95", "affyExonArray", "affyGnf1h", "affyU133", "affyU133Plus2", "affyU95", "All SNPs(138)", "All SNPs(141)", "All SNPs(142)", "All SNPs(144)", "All SNPs(146)", "All SNPs(147)", "All SNPs(150)", "All SNPs(151)", "Allen Brain", "allenBrainAli", "allHg19RS_BW", "Alt Haplotypes", "altLocations", "Assembly", "AUGUSTUS", "augustusGene", "BAC End Pairs", "bacEndPairs", "Broad ChromHMM", "Broad Histone", "BU ORChID", "Burge RNA-seq", "burgeRnaSeqGemMapperAlign", "Caltech RNA-seq", "Cand. Gene Flow", "CCDS", "ccdsGene", "CD34 DnaseI", "CGAP SAGE", "cgapSage", "chainSelf", "Chromosome Band", "Chromosome Band (Ideogram)", "ClinGen CNVs", "clinvar", "ClinVar Variants", "cnvDevDelay", "Common SNPs(138)", "Common SNPs(141)", "Common SNPs(142)", "Common SNPs(144)",

Version
R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Mojave 10.14.5
[1] Gviz_1.28.3

Hi @bschilder,
I am happy that you like Gviz.
I am afraid that the UCSCTrack cannot work here as the table itself is essentially a link to external bigWig file. You can still plot it with Gviz, however you need to create a DataTrack out of it:
library(Gviz)

bigWigFile <- "http://homer.ucsd.edu/hubs//nuclei_h3k27ac_hg19_pooled/hg19/human_microglia_H3K27ac_exvivo_pooled_hg19.ucsc.bigWig"

conservation <- DataTrack(bigWigFile,
                          from=40590585,
                          to=40763013,
                          genome="hg19",
                          type="histogram",
                          chromosome="chr12",
                          name="nuclei_h3k27ac_hg19_pooled",
                          importFunction=Gviz:::.import.bw)
# command above takes some time to fetch the data...

plotTracks(conservation, from=40590585, to=40763013, genome="hg19", chromosome="chr12")

Hope that helps.
Best
Robert
P.S. I believe this type of question should rather go to Bioconductor support channel.

This works perfectly, thank you very much!


CNF-14660: Remove timeout from ProvisioningRequest spec

Removed the timeout field from the ProvisioningRequest spec.
Timeouts for hardware provisioning, cluster provisioning, and configuration are now configured in their respective ConfigMaps, referenced in ClusterTemplate.spec.templates. These timeouts are optional.
- Config keys hardwareProvisioningTimeout, clusterProvisioningTimeout, clusterConfigurationTimeout
If a timeout is not specified in the ConfigMap, the default timeout values will be used, consistent with previous behavior:
- Default for hardware provisioning: 90 minutes
- Default for cluster provisioning: 90 minutes
- Default for cluster configuration: 30 minutes
Added sample ConfigMaps for clusterInstance and policyTemplate.

/lgtm

Looks good - my only real comment is that it would be better to use durations (e.g. 10s, 30m, 5h) instead of having all the timeouts in seconds. I know it was like this already, so don't feel you need to change it now.

Added a new commit for this change. Have tested in the real env.

/lgtm

/approve


Upgrade com.uber.nullaway:nullaway 0.10.7 -> 0.10.8

This PR contains the following updates:

Package
Type
Update
Change

com.uber.nullaway:nullaway

patch
0.10.7 -> 0.10.8

com.uber.nullaway:nullaway
compile
patch
0.10.7 -> 0.10.8

Release Notes

uber/NullAway
v0.10.8
Compare Source

Don't do checks for type casts and parameterized trees in unannotated code (#712)
Add an initial nullaway:nullaway-annotations artifact. (#709)

Contains only an implementation of @Initializer for now.

NullAwayInfer/Annotator data serialization support [experimental]

Update region selection for initialization errors. (#713)
Update path serialization for reported errors and fixes. (#714)

Build / CI tooling for NullAway itself:

Turn up various Error Prone checks (#710)

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

Suggested commit message:
Upgrade NullAway 0.10.7 -> 0.10.8

See:
- https://github.com/uber/NullAway/blob/master/CHANGELOG.md
- https://github.com/uber/NullAway/compare/v0.10.7...v0.10.8


Icons disappear on tmux

I'm not sure if here is the right place to ask
The icon are fine

but when I use tmux, those icons disappear

My font is SourceCodePro+Powerline+Awesome
Any body knows the solution?

Hi @agungsetiawan !
Is the line where you define the mode (POWERLEVEL9K_MODE) on the top of your ~/.zshrc?

No, I have this line on third line from bottom
POWERLEVEL9K_MODE='awesome-patched'
Should I place it on the very first line?

Yes, try that! ;)

Ah yes, after move it to the up, now it's working
thank you @dritter what a wonderful clue 🤝

Awesome! And apologies for that confusion. We are working on that, so that the position where you place that line gets irrelevant..

It's okay :)
Cool!
I'm looking forward for the update


 Note that symbolic links to directories are skipped.
2022-11-23 15:20:26.803 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 15:20:26.849 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 15:20:26.925 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 15:20:27.055 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:20:27.150 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:20:27.379 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:20:27.465 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 15:20:27.502 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 15:20:27.514 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 15:20:27.531 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 15:20:27.542 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 15:20:27.557 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 15:20:27.569 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 15:20:27.580 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 15:20:29.853 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 15:20:29.907 +0900 [INFO] (main): Committed.
2022-11-23 15:20:29.908 +0900 [INFO] (main): Next config diff: {"in":{"last_path":"/tmp/example/data.csv"},"out":{}}

profile
out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: trocco-test-giwa
  auth_method: profile
  profile_name: pn-s3-test
  formatter:
    type: csv

ken@Kens-MacBook-Air embulk-output-s3 % embulk run -I build/gemContents/lib config.yml

2022-11-23 15:27:10.186 +0900: Embulk v0.9.24
2022-11-23 15:27:11.014 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-23 15:27:14.697 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-23 15:27:16.621 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-23 15:27:16.840 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-23 15:27:16.899 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-23 15:27:16.900 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-23 15:27:16.901 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 15:27:16.956 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 15:27:17.021 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 15:27:17.156 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:27:17.255 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:27:17.500 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:27:17.585 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 15:27:17.626 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 15:27:17.645 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 15:27:17.659 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 15:27:17.676 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 15:27:17.694 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 15:27:17.709 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 15:27:17.724 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 15:27:20.061 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 15:27:20.119 +0900 [INFO] (main): Committed.
2022-11-23 15:27:20.119 +0900 [INFO] (main): Next config diff: {"in":{"last_path":"/tmp/example/data.csv"},"out":{}}

env
out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: trocco-test-giwa
  auth_method: env
  formatter:
    type: csv

embulk run -I build/gemContents/lib config.yml

2022-11-23 15:39:13.718 +0900: Embulk v0.9.24
2022-11-23 15:39:14.545 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-23 15:39:17.555 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-23 15:39:19.436 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-23 15:39:19.709 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-23 15:39:19.829 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-23 15:39:19.831 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-23 15:39:19.833 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 15:39:19.877 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 15:39:19.949 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 15:39:20.074 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:39:20.192 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:39:20.419 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:39:20.508 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 15:39:20.545 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 15:39:20.556 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 15:39:20.571 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 15:39:20.584 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 15:39:20.594 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 15:39:20.605 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 15:39:20.615 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 15:39:22.980 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 15:39:23.032 +0900 [INFO] (main): Committed.
2022-11-23 15:39:23.033 +0900 [INFO] (main): Next config diff: {"in":{"last_path":"/tmp/example/data.csv"},"out":{}}

http_proxy
out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: trocco-test-giwa
  http_proxy:
    host: <IP_ADDRESS>
    port: 8899
  auth_method: env
  formatter:
    type: csv

embulk run -I build/gemContents/lib config.yml
2022-11-23 15:46:53.424 +0900: Embulk v0.9.24
2022-11-23 15:46:54.214 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-23 15:46:57.222 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-23 15:46:59.128 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-23 15:46:59.339 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-23 15:46:59.447 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-23 15:46:59.448 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-23 15:46:59.449 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 15:46:59.501 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 15:46:59.584 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 15:46:59.723 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:46:59.815 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:47:00.004 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.039 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 15:47:00.131 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 15:47:00.157 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.166 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 15:47:00.175 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.178 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 15:47:00.189 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.195 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 15:47:00.209 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.212 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 15:47:00.224 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.225 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 15:47:00.240 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.242 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 15:47:00.251 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 15:47:00.255 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 15:47:03.327 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 15:47:03.384 +0900 [INFO] (main): Committed.

deprecated configs
out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: trocco-test-giwa
  proxy_host: <IP_ADDRESS>
  proxy_port: 8899
  auth_method: env
  formatter:
    type: csv

embulk run -I build/gemContents/lib config.yml

2022-11-23 16:29:49.700 +0900: Embulk v0.9.24
2022-11-23 16:29:50.524 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-23 16:29:53.637 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-23 16:29:55.528 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-23 16:29:55.844 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-23 16:29:55.955 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-23 16:29:55.956 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-23 16:29:55.958 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 16:29:56.010 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 16:29:56.087 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 16:29:56.215 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:29:56.320 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:29:56.509 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.546 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:29:56.640 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 16:29:56.671 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.683 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 16:29:56.692 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.694 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 16:29:56.718 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.721 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 16:29:56.734 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.736 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 16:29:56.754 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.756 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 16:29:56.767 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.768 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 16:29:56.778 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:29:56.781 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 16:29:59.675 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 16:29:59.737 +0900 [INFO] (main): Committed.

http_proxy has priority
out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: trocco-test-giwa
  proxy_host: <IP_ADDRESS>
  proxy_port: 9000
  http_proxy:
    host: <IP_ADDRESS>
    port: 8899
  auth_method: env
  formatter:
    type: csv

embulk run -I build/gemContents/lib config.yml

2022-11-23 16:31:50.199 +0900: Embulk v0.9.24
2022-11-23 16:31:51.004 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-23 16:31:53.945 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-23 16:31:55.892 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-23 16:31:56.172 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-23 16:31:56.273 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-23 16:31:56.274 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-23 16:31:56.276 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-23 16:31:56.323 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-23 16:31:56.407 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-23 16:31:56.548 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:31:56.629 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:31:56.820 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:56.863 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-23 16:31:56.950 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-23 16:31:56.973 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:56.985 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-23 16:31:56.996 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.003 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-23 16:31:57.013 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.018 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-23 16:31:57.033 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.036 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-23 16:31:57.045 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.048 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-23 16:31:57.066 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.068 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-23 16:31:57.076 +0900 [INFO] (0015:task-0000): Configuring Proxy. Proxy Host: <IP_ADDRESS> Proxy Port: 8899
2022-11-23 16:31:57.082 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-23 16:32:00.029 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-23 16:32:00.089 +0900 [INFO] (main): Committed.
2022-11-23 16:32:00.089 +0900 [INFO] (main): Next config diff: {"in":{"last_path":"/tmp/example/data.csv"},"out":{}}

out:
  type: s3
  path_prefix: logs/out
  file_ext: .csv
  bucket: test-by-giwa
  auth_method: assume_role
  account_id: ********
  role_name: **********
  external_id: **********
  formatter:
    type: csv

embulk run -I build/gemContents/lib config.yml

2022-11-25 12:08:50.280 +0900: Embulk v0.9.24
2022-11-25 12:08:51.146 +0900 [WARN] (main): DEPRECATION: JRuby org.jruby.embed.ScriptingContainer is directly injected.
2022-11-25 12:08:54.186 +0900 [INFO] (main): Gem's home and path are set by default: "/Users/ken/.embulk/lib/gems"
2022-11-25 12:08:56.253 +0900 [INFO] (main): Started Embulk v0.9.24
2022-11-25 12:08:56.437 +0900 [INFO] (0001:transaction): Loaded plugin embulk/output/s3 from a load path
2022-11-25 12:08:56.507 +0900 [INFO] (0001:transaction): Listing local files at directory '/tmp/example' filtering filename by prefix ''
2022-11-25 12:08:56.508 +0900 [INFO] (0001:transaction): "follow_symlinks" is set false. Note that symbolic links to directories are skipped.
2022-11-25 12:08:56.510 +0900 [INFO] (0001:transaction): Loading files [/tmp/example/data.csv]
2022-11-25 12:08:56.564 +0900 [INFO] (0001:transaction): Using local thread executor with max_threads=16 / output tasks 8 = input tasks 1 * 8
2022-11-25 12:08:56.635 +0900 [INFO] (0001:transaction): {done:  0 / 1, running: 0}
2022-11-25 12:08:56.804 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-25 12:08:57.120 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-25 12:08:57.203 +0900 [WARN] (0015:task-0000): Your profile name includes a 'profile ' prefix. This is considered part of the profile name in the Java SDK, so you will need to include this prefix in your profile name when you reference this profile from your Java code.
2022-11-25 12:08:57.313 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.000.00.csv'
2022-11-25 12:08:57.356 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.001.00.csv'
2022-11-25 12:08:57.374 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.002.00.csv'
2022-11-25 12:08:57.396 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.003.00.csv'
2022-11-25 12:08:57.407 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.004.00.csv'
2022-11-25 12:08:57.420 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.005.00.csv'
2022-11-25 12:08:57.432 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.006.00.csv'
2022-11-25 12:08:57.446 +0900 [INFO] (0015:task-0000): Writing S3 file 'logs/out.007.00.csv'
2022-11-25 12:09:06.714 +0900 [INFO] (0001:transaction): {done:  1 / 1, running: 0}
2022-11-25 12:09:06.771 +0900 [INFO] (main): Committed.
2022-11-25 12:09:06.771 +0900 [INFO] (main): Next config diff: {"in":{"last_path":"/tmp/example/data.csv"},"out":{}}


GPU and CPU inference are inconsistent

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): centos
TensorFlow version and how it was installed (source or binary): 2.8.3, pip install
TensorFlow-Recommenders-Addons version and how it was installed (source or binary): 0.5.1
Python version:  3.7.16
Is GPU used? (yes/no): yes

Describe the bug
A clear and concise description of what the bug is.
When using the Keras model  for inference, the results of GPU and CPU inference are inconsistent
This model train on gpu, and the graph rebuild by de.enable_inference_mode().

Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
import os;os.environ['CUDA_VISIBLE_DEVICES'] = '-1'
import tensorflow as tf
import tensorflow_recommenders_addons.dynamic_embedding as de
func = tf.saved_model.load('model_path').signatures['serving_default']
func(**tensors)
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

I'm not sure if this is a problem caused by TFRA, as even the TF itself can have issues with inconsistent CPU and GPU inference results.


Human in the loop and design a social media game?

Can we increase the frequency of human participation in the OASIS interaction? As users, humans can interact with agents in the simulation. We could add a visual interface to observe how the content we share and the action we make influences the entire agent society.

Welcome to discuss here


Did you already have Tep Oceus before he gave it to you ? Does the debug window show any errors ?

Try pressing F2 after defeating him to open the doors.

TO was one of my starting items. Nothing strange in the debug window.
F2 did the trick.

Okay yeah my current script for preventing the boss softlocks only detects the shard if it's one you don't already have. In the opposite case press F2 to end the boss manually. Same goes for Glutton Train and IGA.


✨ Uplift CAPI to v0.4.4 and align other deps with CAPI release-0.4

This patch:

uplifts capi to v0.4.4
downgrades kube-api/machinery/apiserver and client-go to v0.21.4
downgrades controller runtime to v0.9.7

follows: CAPI release-0.4
Note: we will uplift downgraded modules again while uplifting to CAPI v1beta1.

/approve

Humm it seems they are keeping the CR to 0.9.7 in release-0.4 branch , I think we shall also downgrade it since we are referencing v0.4.x currently. Would you please also check what else is downgraded?

Done

/lgtm


Added Socket.io

Resolves #[Issue Number if there]
PR Fixes:

1 Integrated Socket.io
2

Checklist before requesting a review

[ ] I have pull latest changes from main branch
[ ] I have tested the changes locally
[ ] I have run npm run lint:fix locally
[ ] I have performed a self-review of my code
[ ] I assure there is no similar/duplicate pull request regarding same issue

Hello @DhanushNehru  Backend is being hosted on render it is running on a free version that is after a period of inactivity the server goes down and takes time to restart once a request is made . So either if you have other plans to host you can host on other platform too i have added server folder within the root directory of your project you could look into it.

Hi @TheAdich please mention the issue number properly in the PR

Hello @DhanushNehru Backend is being hosted on render it is running on a free version that is after a period of inactivity the server goes down and takes time to restart once a request is made . So either if you have other plans to host you can host on other platform too i have added server folder within the root directory of your project you could look into it.

To keep your backend alive every time, you can create a job in cron-job.org which will send a request to the backend every 1 min, solving the server going down issue.

Like video in the readme or here to show how i have implemented it ?

screen-capture.webm

On render you just need to choose web service and choose the repo where your backend is located in my case i had created a seperate repo and on render selected that repo

Yo

in the build command just write npm install
and in the start command write node index.js and choose the free plan and click on deploy
However if you are locally setting up the project you don;t need to configure the render


Document process of configuring the YARP server in the iCub setup?

While debugging the iCubNancy01, I noticed that in our documentation it is not documented anywhere the fact that a single machine in the system should be designated to host the yarpserver, and all the other machines should be configured, first aligning the yarp namespace, and then setting the server address via yarp detect --write or yarp conf ip sockerport. Not sure if this should be added.

It would be a good addition indeed.

fyi @Uboldi80


Refactoring Redis OM Python to use pydantic 2.0 types and validators

With #533 it became possible to use Redis OM Python in an environment where pydantic 2.0 was installed, however this leaned completely on the pydantic v1 shim, consequentially this meant that if you tried to use any of the pydantic 2.0 types or validators produce errors-a-plenty, see: #602, #601, #590, #572, #571, #546, and many more
Pydantic V1 -> Pydantic V2 was described as a "ground up rewrite" by the pydantic team, and it's apparent that it was, however they have also stated that while they will be shipping major versions every year going forward that future migrations should not be nearly as painful
the tact projects like FastAPI took was to use the shim in the inverse (import v1 types from their old places if your pydantic version is V1, use v2 types if pydantic version is v2), which this PR adapts us towards.
If you only use pydantic 1.x, there should be no breaking changes in here, the shim should include the correct fields for you and the code should  be backwards compatible, however if you are using pydantic 2.0 in your app, there will be breaks going from redis om python 0.2.x -> 0.3.x. namely. In short, anything that comes up in the pydantic 2.0 migration guide is liable to be an issue for someone migrating. Some highlights:

The way the validators work in pydantic has changed, previously, in pydantic 1.0, if a field was declared as Optional, pydantic would infer that it should not produce a validation error if the field was not set, in pydantic 2.0, optionals must be explicitly set on the model, or must be provided a default value.
There will also be type-changes in the types of error's that are thrown during validation, namely moving from the pydantic 1.x ValidationError to the pydantic 2.x ValidationError.
Only Validators from 2.x will work

Would like some eyes from our end (namely @banker, @bsbodden, @tylerhutcherson). As well as feedback from anyone in the community who might have interest.

This would be great to have soon, given pydantic recently released 2.7.0 few days ago :) would make this library a lot more useful in projects where I can't downgrade pydantic.


domain split: parser

parse the results of domain split

No longer applicable, once we have the new split_sequence script.