Warning and possible issues

ISSUE
I deployed Tailwind CSS Starter to Vercel and locally I ran into several warnings that I would really appreciate if you could review. I am wondering if there are some workspace, node version, config or other issues that need to be addressed.
Next.js v13.0.1
react-native v8.0.6
The following is the Vercel build log and Terminal log.
VERCEL BUILD LOG
[16:30:00.401] Running build in San Francisco, USA (West) – sfo1
[16:30:00.446] Cloning github.com/ (Branch: main, Commit: 0ed575f)
[16:30:00.586] Previous build cache not available
[16:30:01.829] Cloning completed: 1.382s
[16:30:01.992] Running "vercel build"
[16:30:02.561] Vercel CLI 28.16.2
[16:30:02.736] > Automatically detected Turbo monorepo manager. Attempting to assign default settings.
[16:30:02.736] WARN! Cannot automatically assign buildCommand as it is already set via project settings or configuration overrides.
[16:30:02.871] Warning: Due to "engines": { "node": "^16" } in your package.json file, the Node.js Version defined in your Project Settings ("18.x") will not apply. Learn More: http://vercel.link/node-version
[16:30:02.880] Running "install" command: yarn install...
[16:30:03.248] yarn install v1.22.17
[16:30:03.369] [1/5] Validating package.json...
[16:30:03.378] [2/5] Resolving packages...
[16:30:04.144] [3/5] Fetching packages...
[16:30:40.077] warning<EMAIL_ADDRESS>Invalid bin field for "mini-css-extract-plugin".
[16:30:54.748] [4/5] Linking dependencies...
[16:30:54.751] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[16:30:54.752] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.752] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has incorrect peer dependency "next@^11".
[16:30:54.752] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency "react@^17".
[16:30:54.753] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.754] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react@".
[16:30:54.754] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
[16:30:54.754] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react@".
[16:30:54.754] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
[16:30:54.754] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
[16:30:54.755] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native-screens@>= 3.0.0".
[16:30:54.755] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app ><EMAIL_ADDRESS>has unmet peer dependency "tailwindcss@~3".
[16:30:54.755] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app > expo-splash-screen ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.755] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app > react-native-screens ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[16:30:54.756] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app > next ><EMAIL_ADDRESS>has unmet peer dependency "react@>= 16.8.0 || 17.x.x || ^18.0.0-0".
[16:30:54.757] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app > next-fonts ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.757] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app > next-fonts ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.757] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > @react-navigation/native ><EMAIL_ADDRESS>has unmet peer dependency "react@".
[16:30:54.758] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react@".
[16:30:54.758] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
[16:30:54.759] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
[16:30:54.759] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > moti ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
[16:30:54.759] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > moti ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
[16:30:54.760] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app > react-native > react-native-codegen ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[16:30:54.760] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app > @expo/next-adapter > @expo/webpack-config ><EMAIL_ADDRESS>has unmet peer dependency "expo@".
[16:30:54.761] warning "workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app > @expo/next-adapter > babel-preset-expo ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@*".
[16:31:27.531] [5/5] Building fresh packages...
[16:31:28.206] Done in 84.97s.
[16:31:28.255] Detected Next.js version: 13.0.1
[16:31:28.257] Running "cd ../..;npx turbo run build --filter=next-app"
[16:31:29.211] • Packages in scope: next-app
[16:31:29.211] • Running build in 1 packages
[16:31:29.212] • Remote computation caching enabled
[16:31:30.450] next-app:build: cache hit, replaying output 41a3a4091fe004cd
[16:31:30.450] next-app:build: yarn run v1.22.17
[16:31:30.450] next-app:build: $ next build
[16:31:30.450] next-app:build: warn  - Invalid next.config.js options detected:
[16:31:30.450] next-app:build:   - The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build:   - The root value has an unexpected property, configOrigin, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build:   - The root value has an unexpected property, target, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build:   - The root value has an unexpected property, webpack5, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build:   - The value at .amp.canonicalBase must be 1 character or more but it was 0 characters.
[16:31:30.451] next-app:build:   - The value at .assetPrefix must be 1 character or more but it was 0 characters.
[16:31:30.451] next-app:build:   - The value at .i18n must be an object but it was null.
[16:31:30.451] next-app:build:   - The value at .images.loaderFile must be 1 character or more but it was 0 characters.
[16:31:30.451] next-app:build:
[16:31:30.451] next-app:build: See more info here: https://nextjs.org/docs/messages/invalid-next-config
[16:31:30.452] next-app:build: warn  - You have enabled experimental features (forceSwcTransforms, swcPlugins) in next.config.js.
[16:31:30.452] next-app:build: warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
[16:31:30.452] next-app:build:
[16:31:30.452] next-app:build: Attention: Next.js now collects completely anonymous telemetry regarding usage.
[16:31:30.452] next-app:build: This information is used to shape Next.js' roadmap and prioritize features.
[16:31:30.452] next-app:build: You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[16:31:30.452] next-app:build: https://nextjs.org/telemetry
[16:31:30.452] next-app:build:
[16:31:30.452] next-app:build: info  - Linting and checking validity of types...
[16:31:30.452] next-app:build: info  - Creating an optimized production build...
[16:31:30.452] next-app:build: Browserslist: caniuse-lite is outdated. Please run:
[16:31:30.452] next-app:build:   npx browserslist@latest --update-db
[16:31:30.453] next-app:build:   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
[16:31:30.453] next-app:build: info  - Compiled successfully
[16:31:30.453] next-app:build: info  - Collecting page data...
[16:31:30.453] next-app:build: info  - Generating static pages (1/4)
[16:31:30.453] next-app:build: info  - Generating static pages (2/4)
[16:31:30.453] next-app:build: info  - Generating static pages (3/4)
[16:31:30.453] next-app:build: info  - Generating static pages (4/4)
[16:31:30.453] next-app:build: info  - Finalizing page optimization...
[16:31:30.453] next-app:build:
[16:31:30.453] next-app:build: Route (pages)                              Size     First Load JS
[16:31:30.453] next-app:build: ┌ ○ /                                      85.6 kB         247 kB
[16:31:30.453] next-app:build: ├   /_app                                  0 B            73.8 kB
[16:31:30.454] next-app:build: ├ ○ /404                                   181 B            74 kB
[16:31:30.454] next-app:build: └ ○ /user/[id]                             1.58 kB         163 kB
[16:31:30.454] next-app:build: + First Load JS shared by all              75.8 kB
[16:31:30.454] next-app:build:   ├ chunks/framework-95e654c50294ba5f.js   45.4 kB
[16:31:30.454] next-app:build:   ├ chunks/main-b80439cc47e7a342.js        25.7 kB
[16:31:30.454] next-app:build:   ├ chunks/pages/_app-29f575fc754a80be.js  1.71 kB
[16:31:30.454] next-app:build:   ├ chunks/webpack-36d12a75f0098f30.js     1.04 kB
[16:31:30.454] next-app:build:   └ css/8c43602744541283.css               1.99 kB
[16:31:30.454] next-app:build:
[16:31:30.454] next-app:build: ○  (Static)  automatically rendered as static HTML (uses no initial props)
[16:31:30.454] next-app:build:
[16:31:30.454] next-app:build: Done in 47.89s.
[16:31:30.454]
[16:31:30.455]  Tasks:    1 successful, 1 total
[16:31:30.455] Cached:    1 cached, 1 total
[16:31:30.455]
[16:31:30.546] Collected static files (public/, static/, .next/static): 5.828ms
[16:31:30.593] Build Completed in /vercel/output [1m]
[16:31:31.496] Generated build outputs:
[16:31:31.497]  - Static files: 21
[16:31:31.497]  - Prerenders: 0
[16:31:31.497]  - Serverless Functions: 0
[16:31:31.497]  - Edge Functions: 0
[16:31:31.498] Deployed outputs in 1s
[16:31:31.867] Build completed. Populating build cache...
[16:31:55.153] Uploading build cache [234.43 MB]...
[16:31:59.343] Build cache uploaded: 4.190s
TERMINAL LOG
Now using node v16.19.1 (npm v8.19.3)
$ yarn web
yarn run v1.22.19
$ cd apps/next && yarn next
error Command "next" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
$ yarn
yarn install v1.22.19
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has incorrect peer dependency "next@^11".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency "react@^17".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "react-native-screens@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app ><EMAIL_ADDRESS>has unmet peer dependency "tailwindcss@~3".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app > expo-splash-screen ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app > react-native-screens ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app > next ><EMAIL_ADDRESS>has unmet peer dependency "react@>= 16.8.0 || 17.x.x || ^18.0.0-0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app > next-fonts ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app > next-fonts ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > @react-navigation/native ><EMAIL_ADDRESS>has unmet peer dependency "react@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react-native@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > @react-navigation/native-stack ><EMAIL_ADDRESS>has unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > moti ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > moti ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app > react-native > react-native-codegen ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app > @expo/next-adapter > @expo/webpack-config ><EMAIL_ADDRESS>has unmet peer dependency "expo@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app > @expo/next-adapter > babel-preset-expo ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@*".
[5/5] 🔨  Building fresh packages...
✨  Done in 55.86s.
Computer:$ yarn web
yarn run v1.22.19
$ cd apps/next && yarn next
$ /node_modules/.bin/next
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
warn  - Invalid next.config.js options detected:

The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, configOrigin, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, target, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, webpack5, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash, typescript, useFileSystemPublicRoutes, webpack).
The value at .amp.canonicalBase must be 1 character or more but it was 0 characters.
The value at .assetPrefix must be 1 character or more but it was 0 characters.
The value at .i18n must be an object but it was null.
The value at .images.loaderFile must be 1 character or more but it was 0 characters.

See more info here: https://nextjs.org/docs/messages/invalid-next-config
warn  - You have enabled experimental features (forceSwcTransforms, swcPlugins) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
info  - automatically enabled Fast Refresh for 1 custom loader
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
event - compiled client and server successfully in 9.6s (262 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 33.2s (1938 modules)
^Z
[2]+  Stopped                 yarn web
Computer: $ yarn native
yarn run v1.22.19
$ cd apps/expo && expo start
Starting project at /apps/expo
Some dependencies are incompatible with the installed expo version:
<EMAIL_ADDRESS>- expected version: ~3.2.4
<EMAIL_ADDRESS>- expected version: 18.0.0
<EMAIL_ADDRESS>- expected version: 18.0.0
<EMAIL_ADDRESS>- expected version: 0.69.6
Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Starting Metro Bundler
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
› Metro waiting on exp://<IP_ADDRESS>:19000
› Scan the QR code above with Expo Go (Android) or the Camera app (iOS)
› Press a │ open Android
› Press i │ open iOS simulator
› Press w │ open web
› Press r │ reload app
› Press m │ toggle menu
› Press ? │ show all commands
Logs for your project will appear below. Press Ctrl+C to exit.
transform[stderr]:
transform[stderr]: warn - No utility classes were detected in your source files. If this is unexpected, double-check the content option in your Tailwind CSS configuration.
transform[stderr]: warn - https://tailwindcss.com/docs/content-configuration
transform[stderr]:
transform[stderr]: warn - No utility classes were detected in your source files. If this is unexpected, double-check the content option in your Tailwind CSS configuration.
transform[stderr]: warn - https://tailwindcss.com/docs/content-configuration
iOS Bundling complete 66929ms

these are all annoying warnings, but it’s actually not a real issue. some
of the tools are just outdated etc. they might go away in the future
On Mon, Feb 20, 2023 at 12:23 PM EA @.***> wrote:

ISSUE
I deployed Tailwind CSS Starter to Vercel and locally I ran into several
warnings that I would really appreciate if you could review. I am wondering
if there are some workspace, node version, config or other issues that need
to be addressed.
Next.js v13.0.1
react-native v8.0.6
The following is the Vercel build log and Terminal log.
VERCEL BUILD LOG
[16:30:00.401] Running build in San Francisco, USA (West) – sfo1
[16:30:00.446] Cloning github.com/ (Branch: main, Commit: 0ed575f)
[16:30:00.586] Previous build cache not available
[16:30:01.829] Cloning completed: 1.382s
[16:30:01.992] Running "vercel build"
[16:30:02.561] Vercel CLI 28.16.2
[16:30:02.736] > Automatically detected Turbo monorepo manager. Attempting
to assign default settings.
[16:30:02.736] WARN! Cannot automatically assign buildCommand as it is
already set via project settings or configuration overrides.
[16:30:02.871] Warning: Due to "engines": { "node": "^16" } in your
package.json file, the Node.js Version defined in your Project Settings
("18.x") will not apply. Learn More: http://vercel.link/node-version
https://urldefense.com/v3/__http://vercel.link/node-version__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0aQej4xE$
[16:30:02.880] Running "install" command: yarn install...
[16:30:03.248] yarn install v1.22.17
[16:30:03.369] [1/5] Validating package.json...
[16:30:03.378] [2/5] Resolving packages...
[16:30:04.144] [3/5] Fetching packages...
[16:30:40.077] warning @.: Invalid bin field
for "mini-css-extract-plugin".
[16:30:54.748] [4/5] Linking dependencies...
[16:30:54.751] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app >
@." has incorrect peer dependency @.".
[16:30:54.752] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app >
@." has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.752] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@@." has incorrect peer dependency "next@^11".
[16:30:54.752] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@@." has unmet peer dependency "react@^17".
[16:30:54.753] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@@." has unmet peer dependency "react-native-web@
^0.17.0".
[16:30:54.753] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@." has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@." has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@." has unmet peer dependency<EMAIL_ADDRESS>[16:30:54.753] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@." has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.754] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency "react@
". [16:30:54.754] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency "react-native@
".
[16:30:54.754] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency "react@
". [16:30:54.754] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency
"react-native@".
[16:30:54.754] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency
"react-native-safe-area-context@>= 3.0.0".
[16:30:54.755] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@@." has unmet peer dependency
"react-native-screens@>= 3.0.0".
[16:30:54.755] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@." has unmet peer dependency "tailwindcss@~3".
[16:30:54.755] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app >
expo-splash-screen > @@." has unmet peer
dependency<EMAIL_ADDRESS>[16:30:54.755] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app >
react-native-screens > @." has incorrect peer dependency
<EMAIL_ADDRESS>[16:30:54.756] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
next > @." has unmet peer dependency "react@>= 16.8.0 ||
17.x.x || ^18.0.0-0".
[16:30:54.757] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
next-fonts > @." has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.757] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
next-fonts > @." has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[16:30:54.757] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@react-navigation/native > @@." has unmet peer
dependency "react@
". [16:30:54.758] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@react-navigation/native-stack > @@." has
unmet peer dependency "react@".
[16:30:54.758] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@react-navigation/native-stack > @@.**" has
unmet peer dependency "react-native@
". [16:30:54.759] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app >
@react-navigation/native-stack > @@." has
unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
[16:30:54.759] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > moti >
@." has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 ||
^18.0.0". [16:30:54.759] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > app > moti >
@." has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0
|| ^18.0.0". [16:30:54.760] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > expo-app >
react-native > react-native-codegen > @." has unmet peer
dependency<EMAIL_ADDRESS>[16:30:54.760] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@expo/next-adapter > @expo/webpack-config > @." has unmet
peer dependency "expo@".
[16:30:54.761] warning
"workspace-aggregator-1b92d6cd-27b6-48c1-b10f-b1b022314686 > next-app >
@expo/next-adapter > babel-preset-expo >
@." has unmet peer dependency
@./core@".
[16:31:27.531] [5/5] Building fresh packages...
[16:31:28.206] Done in 84.97s.
[16:31:28.255] Detected Next.js version: 13.0.1
[16:31:28.257] Running "cd ../..;npx turbo run build --filter=next-app"
[16:31:29.211] • Packages in scope: next-app
[16:31:29.211] • Running build in 1 packages
[16:31:29.212] • Remote computation caching enabled
[16:31:30.450] next-app:build: cache hit, replaying output 41a3a4091fe004cd
[16:31:30.450] next-app:build: yarn run v1.22.17
[16:31:30.450] next-app:build: $ next build
[16:31:30.450] next-app:build: warn - Invalid next.config.js options
detected:
[16:31:30.450] next-app:build: - The root value has an unexpected
property, webpackDevMiddleware, which is not in the list of allowed
properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir,
compiler, compress, crossOrigin, devIndicators, distDir, env, eslint,
excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId,
generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries,
optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader,
productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode,
redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build: - The root value has an unexpected
property, configOrigin, which is not in the list of allowed properties
(amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress,
crossOrigin, devIndicators, distDir, env, eslint,
excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId,
generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries,
optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader,
productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode,
redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build: - The root value has an unexpected
property, target, which is not in the list of allowed properties (amp,
analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress,
crossOrigin, devIndicators, distDir, env, eslint,
excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId,
generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries,
optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader,
productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode,
redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build: - The root value has an unexpected
property, webpack5, which is not in the list of allowed properties (amp,
analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress,
crossOrigin, devIndicators, distDir, env, eslint,
excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId,
generateEtags, headers, httpAgentOptions, i18n, images, onDemandEntries,
optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader,
productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode,
redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
[16:31:30.451] next-app:build: - The value at .amp.canonicalBase must be 1
character or more but it was 0 characters.
[16:31:30.451] next-app:build: - The value at .assetPrefix must be 1
character or more but it was 0 characters.
[16:31:30.451] next-app:build: - The value at .i18n must be an object but
it was null.
[16:31:30.451] next-app:build: - The value at .images.loaderFile must be 1
character or more but it was 0 characters.
[16:31:30.451] next-app:build:
[16:31:30.451] next-app:build: See more info here:
https://nextjs.org/docs/messages/invalid-next-config
https://urldefense.com/v3/__https://nextjs.org/docs/messages/invalid-next-config__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0fDsTqsw$
[16:31:30.452] next-app:build: warn - You have enabled experimental
features (forceSwcTransforms, swcPlugins) in next.config.js.
[16:31:30.452] next-app:build: warn - Experimental features are not
covered by semver, and may cause unexpected or broken application behavior.
Use at your own risk.
[16:31:30.452] next-app:build:
[16:31:30.452] next-app:build: Attention: Next.js now collects completely
anonymous telemetry regarding usage.
[16:31:30.452] next-app:build: This information is used to shape Next.js'
roadmap and prioritize features.
[16:31:30.452] next-app:build: You can learn more, including how to
opt-out if you'd not like to participate in this anonymous program, by
visiting the following URL:
[16:31:30.452] next-app:build: https://nextjs.org/telemetry
https://urldefense.com/v3/__https://nextjs.org/telemetry__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0CMwIUTk$
[16:31:30.452] next-app:build:
[16:31:30.452] next-app:build: info - Linting and checking validity of
types...
[16:31:30.452] next-app:build: info - Creating an optimized production
build...
[16:31:30.452] next-app:build: Browserslist: caniuse-lite is outdated.
Please run:
[16:31:30.452] next-app:build: npx @.** --update-db
[16:31:30.453] next-app:build: Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
https://urldefense.com/v3/__https://github.com/browserslist/browserslist*browsers-data-updating__;Iw!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0qJ-NO2g$
[16:31:30.453] next-app:build: info - Compiled successfully
[16:31:30.453] next-app:build: info - Collecting page data...
[16:31:30.453] next-app:build: info - Generating static pages (1/4)
[16:31:30.453] next-app:build: info - Generating static pages (2/4)
[16:31:30.453] next-app:build: info - Generating static pages (3/4)
[16:31:30.453] next-app:build: info - Generating static pages (4/4)
[16:31:30.453] next-app:build: info - Finalizing page optimization...
[16:31:30.453] next-app:build:
[16:31:30.453] next-app:build: Route (pages) Size First Load JS
[16:31:30.453] next-app:build: ┌ ○ / 85.6 kB 247 kB
[16:31:30.453] next-app:build: ├ /_app 0 B 73.8 kB
[16:31:30.454] next-app:build: ├ ○ /404 181 B 74 kB
[16:31:30.454] next-app:build: └ ○ /user/[id] 1.58 kB 163 kB
[16:31:30.454] next-app:build: + First Load JS shared by all 75.8 kB
[16:31:30.454] next-app:build: ├ chunks/framework-95e654c50294ba5f.js 45.4
kB
[16:31:30.454] next-app:build: ├ chunks/main-b80439cc47e7a342.js 25.7 kB
[16:31:30.454] next-app:build: ├ chunks/pages/_app-29f575fc754a80be.js
1.71 kB
[16:31:30.454] next-app:build: ├ chunks/webpack-36d12a75f0098f30.js 1.04 kB
[16:31:30.454] next-app:build: └ css/8c43602744541283.css 1.99 kB
[16:31:30.454] next-app:build:
[16:31:30.454] next-app:build: ○ (Static) automatically rendered as static
HTML (uses no initial props)
[16:31:30.454] next-app:build:
[16:31:30.454] next-app:build: Done in 47.89s.
[16:31:30.454]
[16:31:30.455] Tasks: 1 successful, 1 total
[16:31:30.455] Cached: 1 cached, 1 total
[16:31:30.455]
[16:31:30.546] Collected static files (public/, static/, .next/static):
5.828ms
[16:31:30.593] Build Completed in /vercel/output [1m]
[16:31:31.496] Generated build outputs:
[16:31:31.497] - Static files: 21
[16:31:31.497] - Prerenders: 0
[16:31:31.497] - Serverless Functions: 0
[16:31:31.497] - Edge Functions: 0
[16:31:31.498] Deployed outputs in 1s
[16:31:31.867] Build completed. Populating build cache...
[16:31:55.153] Uploading build cache [234.43 MB]...
[16:31:59.343] Build cache uploaded: 4.190s
TERMINAL LOG
Now using node v16.19.1 (npm v8.19.3)
$ yarn web
yarn run v1.22.19
$ cd apps/next && yarn next
error Command "next" not found.
info Visit https://yarnpkg.com/en/docs/cli/run
https://urldefense.com/v3/__https://yarnpkg.com/en/docs/cli/run__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0JQgbUSo$
for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run
https://urldefense.com/v3/__https://yarnpkg.com/en/docs/cli/run__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0JQgbUSo$
for documentation about this command.
$ yarn
yarn install v1.22.19
[1/5] 🔍 Validating package.json...
[2/5] 🔍 Resolving packages...
[3/5] 🚚 Fetching packages...
[4/5] 🔗 Linking dependencies...
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
expo-app > @." has incorrect peer dependency
@.".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
expo-app > @." has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @@." has incorrect peer dependency "next@
^11".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @@." has unmet peer dependency "react@
^17".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @@." has unmet peer dependency
<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @." has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @." has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @." has unmet peer dependency "postcss@
^8.1.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @." has unmet peer dependency<EMAIL_ADDRESS>||
^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @." has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@@." has unmet peer dependency "react@
". warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
app > @@." has unmet peer dependency
"react-native@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@@." has unmet peer dependency "react@
". warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
app > @@." has unmet peer dependency
"react-native@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@@." has unmet peer dependency
"react-native-safe-area-context@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@@." has unmet peer dependency
"react-native-screens@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@." has unmet peer dependency "tailwindcss@~3".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
expo-app > expo-splash-screen > @@." has unmet
peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
expo-app > react-native-screens > @." has incorrect peer
dependency<EMAIL_ADDRESS>warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > next > @." has unmet peer dependency "react@>=
16.8.0 || 17.x.x || ^18.0.0-0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > next-fonts > @." has unmet peer dependency
<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > next-fonts > @." has unmet peer dependency
<EMAIL_ADDRESS>|| ^5.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@react-navigation/native > @@." has unmet peer
dependency "react@
". warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
app > @react-navigation/native-stack > @@."
has unmet peer dependency "react@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
@react-navigation/native-stack > @@.**" has
unmet peer dependency "react-native@
". warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
app > @react-navigation/native-stack > @@."
has unmet peer dependency "react-native-safe-area-context@>= 3.0.0".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app >
moti > @." has unmet peer dependency<EMAIL_ADDRESS>||
^17.0.0 || ^18.0.0". warning
"workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > app > moti >
@." has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0
|| ^18.0.0". warning
"workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > expo-app >
react-native > react-native-codegen > @." has unmet peer
dependency<EMAIL_ADDRESS>warning
"workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 > next-app >
@expo/next-adapter > @expo/webpack-config > @." has unmet
peer dependency "expo@".
warning "workspace-aggregator-32d596d7-5c83-49ed-ab74-6a68ad83f761 >
next-app > @expo/next-adapter > babel-preset-expo >
@." has unmet peer dependency
@./core@*".
[5/5] 🔨 Building fresh packages...
✨ Done in 55.86s.
Computer:$ yarn web
yarn run v1.22.19
$ cd apps/next && yarn next
$ /node_modules/.bin/next
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
https://urldefense.com/v3/__http://localhost:3000__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0JwSa_Pg$
warn - Invalid next.config.js options detected:

The root value has an unexpected property, webpackDevMiddleware,
which is not in the list of allowed properties (amp, analyticsId,
assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin,
devIndicators, distDir, env, eslint, excludeDefaultMomentLocales,
experimental, exportPathMap, generateBuildId, generateEtags, headers,
httpAgentOptions, i18n, images, onDemandEntries, optimizeFonts, output,
outputFileTracing, pageExtensions, poweredByHeader,
productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode,
redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, configOrigin, which is
not in the list of allowed properties (amp, analyticsId, assetPrefix,
basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators,
distDir, env, eslint, excludeDefaultMomentLocales, experimental,
exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions,
i18n, images, onDemandEntries, optimizeFonts, output, outputFileTracing,
pageExtensions, poweredByHeader, productionBrowserSourceMaps,
publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions,
serverRuntimeConfig, staticPageGenerationTimeout, swcMinify, trailingSlash,
typescript, useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, target, which is not in
the list of allowed properties (amp, analyticsId, assetPrefix, basePath,
cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env,
eslint, excludeDefaultMomentLocales, experimental, exportPathMap,
generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images,
onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions,
poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig,
reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
The root value has an unexpected property, webpack5, which is not in
the list of allowed properties (amp, analyticsId, assetPrefix, basePath,
cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env,
eslint, excludeDefaultMomentLocales, experimental, exportPathMap,
generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images,
onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions,
poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig,
reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig,
staticPageGenerationTimeout, swcMinify, trailingSlash, typescript,
useFileSystemPublicRoutes, webpack).
The value at .amp.canonicalBase must be 1 character or more but it
was 0 characters.
The value at .assetPrefix must be 1 character or more but it was 0
characters.
The value at .i18n must be an object but it was null.
The value at .images.loaderFile must be 1 character or more but it
was 0 characters.

See more info here: https://nextjs.org/docs/messages/invalid-next-config
https://urldefense.com/v3/__https://nextjs.org/docs/messages/invalid-next-config__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0fDsTqsw$
warn - You have enabled experimental features (forceSwcTransforms,
swcPlugins) in next.config.js.
warn - Experimental features are not covered by semver, and may cause
unexpected or broken application behavior. Use at your own risk.
info - automatically enabled Fast Refresh for 1 custom loader
Browserslist: caniuse-lite is outdated. Please run:
npx @.*** --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
https://urldefense.com/v3/__https://github.com/browserslist/browserslist*browsers-data-updating__;Iw!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0qJ-NO2g$
event - compiled client and server successfully in 9.6s (262 modules)
wait - compiling / (client and server)...
event - compiled client and server successfully in 33.2s (1938 modules)
^Z
[2]+ Stopped yarn web
Computer: $ yarn native
yarn run v1.22.19
$ cd apps/expo && expo start
Starting project at /apps/expo
Some dependencies are incompatible with the installed expo version:
@.*** - expected version: ~3.2.4
@.*** - expected version: 18.0.0
@.*** - expected version: 18.0.0
@.*** - expected version: 0.69.6
Your project may not work correctly until you install the correct versions
of the packages.
Install individual packages by running npx expo install<EMAIL_ADDRESS>@.*** @.*** @.***
Starting Metro Bundler
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
› Metro waiting on exp://<IP_ADDRESS>:19000
› Scan the QR code above with Expo Go (Android) or the Camera app (iOS)
› Press a │ open Android
› Press i │ open iOS simulator
› Press w │ open web
› Press r │ reload app
› Press m │ toggle menu
› Press ? │ show all commands
Logs for your project will appear below. Press Ctrl+C to exit.
transform[stderr]:
transform[stderr]: warn - No utility classes were detected in your source
files. If this is unexpected, double-check the content option in your
Tailwind CSS configuration.
transform[stderr]: warn -
https://tailwindcss.com/docs/content-configuration
https://urldefense.com/v3/__https://tailwindcss.com/docs/content-configuration__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0uv2hbwc$
transform[stderr]:
transform[stderr]: warn - No utility classes were detected in your source
files. If this is unexpected, double-check the content option in your
Tailwind CSS configuration.
transform[stderr]: warn -
https://tailwindcss.com/docs/content-configuration
https://urldefense.com/v3/__https://tailwindcss.com/docs/content-configuration__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0uv2hbwc$
iOS Bundling complete 66929ms
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/nandorojo/solito/issues/332__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0upZ6RDE$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADEP4S6KDJW5LPBBR5ZKWDDWYOSB5ANCNFSM6AAAAAAVCEBR6Q__;!!IBzWLUs!TrILlFvx_CuAYXTpBajMVcgTYTYxboy010ZNrHJVzhcTd8v_CnXnIWYL0JaMkqt73WJifoLBXsmExmiGeKE0PYMTyCc$
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Fernando Rojo
University of Pennsylvania, Class of 2019
Candidate for Bachelor of Arts in Economics and Mathematics
Founder at PATOS http://wearpatos.com
734.645.4666
Forbes http://bit.ly/PATOSforbes, Business Insider http://bit.ly/PATOSbi
, NBC
https://www.nbcnews.com/feature/college-game-plan/patos-aims-make-positive-impact-peru-through-sneakers-n730846

Yeah. Worth a shot reaching out. I will close the issue and update the project on my side.


remove_powershell_action_and_operation

Fixes #102
Signed-off-by: Claudiu Ban<EMAIL_ADDRESS>

:+1:


Update License Year

Need some PRs for hacktoberfest.digitalocean.com :D

Lol Gilboy?

haha yeah, I'm still lurking from Seattle. I found out about Hacktoberfest yesterday which gave me just enough time to put in PRs for updating copyright dates 😁 .  I'm just waiting for SignalR to be released for .NET Core and then this project will see some updates from me. Its been a while since I've booted into Windows to do dev work.
How are things with you all?

Mostly the same as when you left. Acquired a company out of Boston/Dallas/Atlanta. That's about it.


[C++][Parquet] Add cmake options for various dependency-linking scenarios

Unless libparquet is being built as part of a statically-linked application toolchain, it may be preferable in a lot of cases to use dynamic linking with its dependencies, rather than statically linking everything as it does now.
I envision several distinct use cases we should support

libparquet.so, with no dependencies statically linked that have shared libraries available
libparquet.so, with all dependencies statically linked (this is what we are doing now)
libparquet.a, with all dependencies statically linked
libparquet.a, without any unnecessary static linking

Having these options accessible through cmake flags will help users of parquet-cpp avoid dependency hell in some cases, and incorporate libparquet in the desired way into a 3rd-party build toolchain
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-487. Please see the migration documentation for further details.

Blake Ryan:
How will this work with upstream dependencies? When I build thrift and parquet today, I get the following failure:
/usr/bin/ld: /usr/local/lib/libthrift.a(TProtocol.o): relocation R_X86_64_32S against `_ZTVN6apache6thrift8protocol16TProtocolFactoryE' can not be used when making a shared object; recompile with -fPIC
I can work around this by configuring parquet-cpp to build statically.
Do you build thrift with -fPIC?

Wes McKinney / @wesm:
Yep: https://github.com/apache/parquet-cpp/blob/master/thirdparty/build_thirdparty.sh#L100

Wes McKinney / @wesm:
I think this is done to our satisfaction as of 1.0.0


Main action should link to IQX rather than qiskit install instructions

What is the expected behavior?
The main "Welcome to Quantum" action should link to the IQX rather than the Qiskit install instructions.

The link to IQX exists in the 2nd section after the main header. Right?

Correct. But there is a logical disconnect here.  We state that the IQX is the place to get started, no installation required, and thus motivate the fact that it is easy to get setup and running, but then direct users to a page that starts talking about creating virtual envs and VC++ runtime components.  It does not make sense to direct new users there to begin with.
Ideally we would have two things, an action to go to IQX, and a little code snippet that is just pip install qiskit.


Send Email to Collective Admins when Expense Moves from Incomplete to Pending

This is discussed in https://opencollective.slack.com/archives/C0429NTTABF/p1678134125648479
Currently when a collective admin marks an expense as incomplete the user gets an email notifying them to update the expense.

However when the user edits this expense we move the expense back to pending state and there's no notification for the collective admins. Suggesting that we send a email to the collective admins with the expense link to re-approve the expense.

[ ] Add email template in templates/emails for notifying collective admins that the expense has been edited by the user.
[ ] Add case in server/lib/notifications/email.ts to check if expense moved from incomplete to edited and send emails to collective admins.

cc: @Betree Hope I covered everything here?

FYI, a more general discussion on the whole workflow related to expense incomplete status is discussed here; https://github.com/opencollective/opencollective/issues/6492.

Better cc @kewitz, he has more context on incomplete expenses


events.list not executing properly

When trying to execute:
response = client.events.list(event_values= "[EventAlarmType.MOTION]")
I'm getting this error:
    kwargs.update({"event_value_list": [code for code in event_values.codes]}) AttributeError: 'str' object has no attribute 'codes'

Hi @liamhoganson, this isn't the correct syntax for the command you're trying to execute. You have the quotes in the wrong place. It should be:
from wyze_sdk.models.events import EventAlarmType
...
response = client.events.list(event_values= [EventAlarmType.MOTION])


exit 1

see:
https://github.com/wkhtmltopdf/wkhtmltopdf/issues/4659
Hi at the pdfkit.
The problem hit me.
workaround: specify margins expilcitely:
{{{
kit   = PDFKit.new(
html,
margin_top:'19.05mm',
margin_bottom:'0mm',
margin_left:'0mm',
margin_right:'0mm',
)
}}}

Looks like wkhtmltopdf does not understand inches (aka --margin-top 0.75in)
But it works like expected if you use mm units.

Please fix:
https://github.com/pdfkit/pdfkit/blob/master/lib/pdfkit/configuration.rb
please replace '0.75in' by '19.05mm'
(that should be compatible and make things work again)
~eike

Space is not measured in meters or in inches


Updated the logging settings in settings.py to be compatible with Django 1.9+

The build process with the makefile fails with Django==1.9.10
according to http://stackoverflow.com/questions/34348360/cannot-resolve-django-utils-log-nullhandler-in-django-1-9
django.utils.log.NullHandler is an alias to logging.NullHandler.
django.utils.log.NullHandler seems to have been removed in Django 1.9
when trying to build the project with the makefile (make sandbox) the process fails when this command is called:
sandbox/manage.py migrate --noinput
this command raises the following Exception:
ValueError: Unable to configure handler 'null': Cannot resolve 'django.utils.log.NullHandler': No module named NullHandler
Updating the logger settings in settings.py to use logging.NullHandler instead of django.utils.log.NullHandler resolved the issue and the build completes.

I will add it in my fork, thanks.

I've addressed this and other issues in #159.


fix(setup): enable init-projection by default

Introduced as optional flag starting from versions 2.44.0, 2.43.6 and  2.42.12, the init-projections allows to pre-fill newly created projection tables during the setup phase. (Tech Advisory 10008)
The flag was initially provided as optional / not enabled by default to prevent breaking (behaviour) changes and test out the option. Since then it solved the desired problem of moving the heavy load of recomputing projections from the runtime phase to the setup phase.
To mitigate problems if the flag was not enabled, we will switch to enable it by default.
Definition of Ready

[x] I am happy with the code
[x] Short description of the feature/issue is added in the pr description
[ ] PR is linked to the corresponding user story
[ ] Acceptance criteria are met
[ ] All open todos and follow ups are defined in a new ticket and justified
[ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[ ] No debug or dead code
[ ] My code has no repetitions
[ ] Critical parts are tested automatically
[ ] Where possible E2E tests are implemented
[ ] Documentation/examples are up-to-date
[ ] All non-functional requirements are met
[ ] Functionality of the acceptance criteria is checked manually on the dev system.

add comment in mitigation of tech advisory


Gradle 7 deprecation warnings

plugins {
	id 'java'
	id 'antlr'
	id 'com.github.spotbugs' version '4.7.1'
}

repositories {
	mavenCentral()
}

sourceSets {
	web {
		java.srcDir "${buildDir}/generated-src"
	}
}

dependencies {
	spotbugs 'com.github.spotbugs:spotbugs:4.2.3'
}

Run gradle clean check --warning-mode all on this. Using Gradle 7.0.2. I get:
> Task :clean
> Task :generateGrammarSource NO-SOURCE
> Task :compileJava NO-SOURCE
> Task :processResources NO-SOURCE
> Task :classes UP-TO-DATE
> Task :spotbugsMain NO-SOURCE
> Task :generateTestGrammarSource NO-SOURCE
> Task :compileTestJava NO-SOURCE
> Task :processTestResources NO-SOURCE
> Task :testClasses UP-TO-DATE
> Task :spotbugsTest NO-SOURCE
> Task :generateWebGrammarSource NO-SOURCE

> Task :compileWebJava
Execution optimizations have been disabled for task ':compileWebJava' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':compileWebJava' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':compileWebJava' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':compileWebJava' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.0.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':compileWebJava' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.0.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

> Task :processWebResources NO-SOURCE
> Task :webClasses
> Task :test NO-SOURCE

> Task :spotbugsWeb
Execution optimizations have been disabled for task ':spotbugsWeb' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.0.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/home/boris/code/spotbugs-plugin-bug/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.0.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

> Task :check

Execution optimizations have been disabled for 2 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD SUCCESSFUL in 596ms
3 actionable tasks: 3 executed

You can see there are some deprecation warnings. I'm actually not sure this is a SpotBugs problem or somewhere else... seems to happen only with ANTLR. Any ideas?
P.S. Sorry, there also should be a src/web/java/com/company/Test.java file with this inside:
package com.company;

public class Test {
}

So if you remove the ANTLR plugin do you still get the warnings?

Well, no, but that's normal - as you see in the log, the deprecation warning is that the SpotBugs task uses the output of an ANTLR task. Not sure how/why.

If there are not warnings when you remove ANTLR, it is probably in their plugin. Has it been updated to work with gradle 7 as there were lots of changes with that release. I would go ask on their repo.
It isn't about the Spotbugs task but generateGrammarSource which is ANTLR.

Well, the ANTLR plugin is built-in in Gradle. I would guess it's updated. As you see in the warning:
Task ':spotbugsWeb' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency

The problem, at least according to Gradle, is in SpotBugs.

Reading their documentation I'm not sure how we are introducing that implicit dependency as we only use java src and we specifically apply the java plugin. If you have any insight or know how to fix pull requests are welcome

I am also unsure. Changing:
sourceSets {
	web {
		java.srcDir "${buildDir}/generated-src"
	}
}

To:
sourceSets {
	web
}

Removes the warning. I'm not exactly sure why. It may also be a Gradle bug...

I would ask for help in their forums as that way of setting up a sourceset is non-standard.

What do you mean non-standard? As far as I can see that's the way to add an additional source directory.

You are referencing a source from the build directory. When you do gradle clean that directory is wiped out, so it is just weird that you are declaring it as a source when it could not exist. Typically you declare sources that always exist like src\main\java

I cannot reproduce this issue in my local, you can clone the project at https://github.com/KengoTODA/reproduce-506
In my understanding, spotbugs-gradle-plugin uses SourceSet's source directory as its input, and it should be enough in major cases.
https://github.com/spotbugs/spotbugs-gradle-plugin/blob/efaad9a3eabee92f0c0b9c2c1883e2fea495ac32/src/main/groovy/com/github/spotbugs/snom/internal/SpotBugsTaskFactory.java#L61-L62
The ANTLR plugin adds generated source directory to existing SourceSet, it is also valid and expected:
https://github.com/gradle/gradle/blob/cde2eecea2f66a45a8444870df7923e9e8998275/subprojects/antlr/src/main/java/org/gradle/api/plugins/antlr/AntlrPlugin.java#L83
So I think the problem comes from users' build script.
@boris-petrov if possible, share a mcve project then it'll help us to debug the problem.

@KengoTODA - did you try the example in my original post? I just tried it and I get the warning using Gradle 7.2. Just put this in a build.gradle file:
plugins {
	id 'java'
	id 'antlr'
	id 'com.github.spotbugs' version '4.7.1'
}

repositories {
	mavenCentral()
}

sourceSets {
	web {
		java.srcDir "${buildDir}/generated-src"
	}
}

dependencies {
	spotbugs 'com.github.spotbugs:spotbugs:4.2.3'
}

And in src/web/java/com/company/Test.java:
package com.company;

public class Test {
}

Running gradle --no-daemon clean check --warning-mode all leads to:
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.2/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
> Task :clean UP-TO-DATE
> Task :generateGrammarSource NO-SOURCE
> Task :compileJava NO-SOURCE
> Task :processResources NO-SOURCE
> Task :classes UP-TO-DATE
> Task :spotbugsMain NO-SOURCE
> Task :generateTestGrammarSource NO-SOURCE
> Task :compileTestJava NO-SOURCE
> Task :processTestResources NO-SOURCE
> Task :testClasses UP-TO-DATE
> Task :spotbugsTest NO-SOURCE
> Task :generateWebGrammarSource NO-SOURCE
> Task :compileWebJava
> Task :processWebResources NO-SOURCE
> Task :webClasses

> Task :spotbugsWeb
Execution optimizations have been disabled for task ':spotbugsWeb' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/home/boris/code/test/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/home/boris/code/test/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/boris/code/test/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/home/boris/code/test/build/generated-src'. Reason: Task ':spotbugsWeb' uses this output of task ':generateTestGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

> Task :test NO-SOURCE
> Task :check

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD SUCCESSFUL in 11s
3 actionable tasks: 2 executed, 1 up-to-date

It could be reproduced in my local, thanks. I'm sure that the problem is here:

  java.srcDir "${buildDir}/generated-src"

Simply remove this line then you can solve this problem. The ANTLR plugin configure the srcDir ./build/generated-src/antlr/web automatic, so you do not have to config manually.

I'll close this issue to clean up unclosed PRs/issues.
Feel free to reopen this issue if more discussion is needed. Thanks!

@KengoTODA - thanks for the time! Note that I can't reopen the issue.
Here is a new example, a little bit expanded:
build.gradle:
plugins {
	id 'java'
	id 'antlr'
	id 'com.github.spotbugs' version '4.7.1'
}

repositories {
	mavenCentral()
}

sourceSets {
	web {
		java.srcDir "${buildDir}/generated-src"
	}
}

configurations.webImplementation.extendsFrom configurations.antlr

tasks.named('generateWebGrammarSource').configure {
	outputDirectory = file("${buildDir}/generated-src/com/company")
	arguments = ['-visitor', '-no-listener', '-package', 'com.company']
}

dependencies {
	antlr 'org.antlr:antlr4:4.9.2'
	spotbugs 'com.github.spotbugs:spotbugs:4.2.3'
}

src/web/java/com/company/Test.java:
package com.company;

public class Test {
	SearchLexer x;
}

src/web/antlr/SearchParser.g4:
parser grammar SearchParser ;

options { tokenVocab=SearchLexer; }

expression : L_PAREN ;

src/web/antlr/SearchLexer.g4:
lexer grammar SearchLexer ;

L_PAREN : '(' ;

Run again gradle --no-daemon clean check --warning-mode all. You will see the warnings.
If you remove the java.srcDir "${buildDir}/generated-src" line as you mention, the code doesn't compile. Perhaps I'm doing something strange or not using the ANTLR plugin correctly?

Yes I think so. I guess you don't need  to configure not only sourceSets but also configurations. I'll confirm it in my local first.

I solve compilation problem with a help from https://github.com/antlr/antlr4/issues/2335#issuecomment-886043863 , here is the updated build.gradle:
plugins {
    id 'java'
    id 'antlr'
    id 'com.github.spotbugs' version '4.7.1'
}

repositories {
    mavenCentral()
}

sourceSets {
    web
}

configurations {
    webImplementation.extendsFrom antlr
}

tasks.named('generateWebGrammarSource').configure {
    def file = file("$buildDir/generated-src/antlr/web/com/company")
    arguments += ['-visitor', '-no-listener', '-package', 'com.company', '-lib', file.absolutePath]

    doFirst {
        file.mkdirs()
    }
}

dependencies {
    antlr 'org.antlr:antlr4:4.9.2'
    spotbugs 'com.github.spotbugs:spotbugs:4.2.3'
}

In this way, we can run ANTLR before the java compilation process and spotbugs. It also has no Gradle 7 deprecation warning. :+1:

Yes, that seems to do the job! Thank you very much for the time and the support!
Just a last question:

The ANTLR plugin configure the srcDir ./build/generated-src/antlr/web automatic, so you do not have to config manually.

How does the ANTLR plugin do that? Where did you see it? Can you send me a link to the source-code?
Thanks again!

https://github.com/gradle/gradle/blob/cde2eecea2f66a45a8444870df7923e9e8998275/subprojects/antlr/src/main/java/org/gradle/api/plugins/antlr/AntlrPlugin.java#L93
here it is. 👍

Thank you very much again!


[RFE]Add instructions about ansible relate tasks in CloudForms after running 'ansible-playbook unconfigure.yml' for 'Infrastructure Migration 1.1 Deployment Guide'

Done!
#2bb620


About the real-time nature of the network

Hello!
I read your paper and I think your work is really great!
I have a question, your input in the paper is 5000 x 3, but in reality the number of point clouds is unknown. Can this network be used to identify obstacles in real time? Can you easily reveal the real-time nature of this network?
Looking forward to your reply!

Thanks for your interest.
We fix the number of input points in our paper so that we can fully utilize the computational power and memory of the GPU. In practice, the number of points may vary from time-to-time. In this case, we have a few choices:

Perform downsampling or upsampling of the points, so that the input to the network remain the same, and we can perform batch processing.
Process one point cloud in each forward computing. That is, each forward computing can take different number of input points.
This is the most complicated one: re-implement the network so that it takes a batch of point clouds as input, and each point cloud can have different number of points. This is possible, but requires a lot of work.

For real-time implementation:

The deep network itself is very fast. It contains around 10 layers. For example, for a batch of 8 point clouds (each point cloud contains 1024 points), it takes around 20ms for our network to perform classification with 1080ti.
However, training the Self-Organizing Map is time consuming. The SOM serves as an input to the deep network in our SO-Net.
The good news is that, the network is still performing well with Farthest Point Sampling (FPS) instead of SOM. That is, we can replace the SOM nodes with the FPS, and the performance of the network decrease a little, but still satisfying.
To achieve best efficiency, you may consider re-implementing deep networks with TensorRT. Deep learning frameworks like PyTorch and TensorFlow trades convenience with performance. The performance of network forwarding can be improved by maybe 10 times if implemented with TensorRT.


feat(operations): Implements Serializer and Deserializer interface

Features:

Resolves deserialisation issues with previously implemented interface
Implements serialize and deserialize methods for all node types
Unit tests for the serialization and deserialization interface

close #12

Codecov Report

Merging #17 (8f22c3f) into main (b6e1e37) will increase coverage by 6.55%.
The diff coverage is 90.19%.

@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
+ Coverage   77.56%   84.11%   +6.55%
==========================================
  Files           7        7
  Lines         205      214       +9
==========================================
+ Hits          159      180      +21
+ Misses         39       27      -12
  Partials        7        7

Impacted Files
Coverage Δ

operations/defs/list_node.go
75.47% <83.87%> (+9.47%)
:arrow_up:

operations/defs/deepcopy_util.go
69.56% <85.71%> (ø)

operations/defs/json_node.go
93.10% <91.42%> (ø)

operations/defs/register_node.go
80.00% <93.75%> (+17.03%)
:arrow_up:

operations/defs/map_node.go
78.94% <100.00%> (+28.94%)
:arrow_up:

operations/serializer/serializer.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Support output for JS API

Hello again! 👋
Would you accept a PR to add output as an option to the findLeaks options similarly to what the CLI supports today, so I as a user wouldn't have to handle dumping the output to a JSON file?

@andreasvirkus Can you explain more what the value of the explicit output API would be? I figured it's pretty easy right now to dump to a JSON file:
import { appendFileSync } from 'node:fs';
for await (const result of results) {
  appendFileSync('out.json', JSON.stringify(result, null, 2), 'utf-8')
}

Closing, please reopen if this is still an issue for you!


Refactor SAT stuff

Cleaning up a few things:

[x] Make naming of satellites consistent (use LoTW names where assigned)
[x] Rename SAT_NAME in log table where non-LoTW names were stored
[x] Add column to satellite table showing if LoTW accepted or not
[x] Ignore non-LoTW accepted satellites in LoTW upload

This is now brushed up and imho ready to test. Would like at least @int2001 to give it a go :)


ESP32 Support

Hi, im Matias from Argentina,
first, i need to say that you make an incredible work here.
Can you port your library to use in the powerfull ESP32??
would be great....
Amazing work

+++
That would be great, I use Esp32 only nowdays.
Also is there a way to set I2C_SDA  I2C_SCL pins ?
Thank you


Add support for pytest-rerunfailures plugin

Is your feature request related to a problem? Please describe.
when using both the syrupy-project and pytest-rerunfailures plugin, I get an internal error: "ValueError: 'rerun' is not a valid ItemStatus"
Describe the solution you'd like
either add "rerun" to the enum that will have a similar behavior to failure or have a fallback behavior for unsupported test run results
Describe alternatives you've considered
not using the plugin
Additional context
python version 3.11.9
syrupy==4.6.4
pytest-rerunfailures==14.0
Windows 11

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

This is fixed in https://github.com/syrupy-project/syrupy/releases/tag/v4.7.1


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

@changeworld @Mikejo5000 - The commits in this PR were moved to the private repo (PR #3869) for validation and staging. We'll close this PR now.


Update abilities.csv

Sombra's abilities

For the rewards/achievements I'll do it when she'll be released


Adding common root domain limitation for v2 apps

@henrymbuguakiarie
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hello @jsoveral,
Thanks for your contribution!
We are currently reviewing the proposed changes.

#please-close


Finalizers in PVCs

Several PVC objects have a finalizer included in the object.  Generally I keep all finalizers out of the object defenition and only allow k8s to apply the appropriate finalizers in order to prevent a finalizer that doesn't exist from preventing the deletion of the object.
Is there any advantage to keeping the finalizer in the object definition?
finalizers:
    - kubernetes.io/pvc-protection

These aren't required and should be removed.

Provided a fix


Set BALLERINA_HOME from vscode for Darwin

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #17466 into master will decrease coverage by 59.16%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #17466       +/-   ##
===========================================
- Coverage   68.85%    9.68%   -59.17%
===========================================
  Files           5       46       +41
  Lines         122     1476     +1354
  Branches       21      239      +218
===========================================
+ Hits           84      143       +59
- Misses         38     1320     +1282
- Partials        0       13       +13

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx

composer/packages/tracing/src/TraceList.tsx

composer/packages/tracing/src/DetailView.tsx

composer/packages/tracing/src/TraceLogs.tsx

composer/packages/tracing/src/index.ts

tool-plugins/vscode/src/utils/logger.ts
52.63% <0%> (ø)

tool-plugins/vscode/src/core/index.ts
100% <0%> (ø)

tool-plugins/vscode/src/utils/rpc/handler.ts
5.88% <0%> (ø)

tool-plugins/vscode/src/debugger/index.ts
0% <0%> (ø)

tool-plugins/vscode/src/debugger/manager.ts
0% <0%> (ø)

... and 41 more

Continue to review full report at Codecov.

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


BUG: instanceof connection returns false in next-js

const { connection } = useConnection();
const socean = useMemo(() => new Socean(network, connection), [network, connection]);

since connectionOption instanceof Connection returns false from this line^, the constructor interprets the connection object as a string instead, and throws TypeError [ERR_INVALID_URL]: Invalid URL

How would I replicate this? I tried using the useSocean() hook and it seemed to be working fine

change line 14 of SoceanProvider from
const socean = useMemo(() => new Socean(cluster.network), [cluster.network]);
to
const socean = useMemo(() => new Socean(network, connection), [network, connection]);

This is pretty weird, the only way I've been able to correctly check if its a Connection instance is using connection.constructor.name === "Connection". But I guess that would validate any class named Connection.
Even this returns false,
// eslint-disable-next-line no-prototype-builtins
console.log(Connection.prototype.isPrototypeOf(connection));

Reference:
https://stackoverflow.com/questions/1249531/how-to-get-a-javascript-objects-class


Better callback traits in basic_parser_v1

basic_parser_v1 traits check for a function signature with an exact match. If a programmer gets a parameter type wrong, the program will still compile but fail to behave correctly. The traits should be relaxed to only check that a member with the given name exists. Then, in the invoking function, a static_assert can check that the argument types are correct, giving better diagnostics.

Merged in b16


Fix value_type and key_type for Tuple

@kalmarek Are you still ok now ?
For consistency with key_type, I changed everything to value_type. It also avoids having a code using valtype that works for everything except tuples as it forces people to use value_type otherwise it won't work for much.

We could also require using StaticArrays.SVector instead of tuples


ArtworkDownload

Version: 2.9.13
Build: 2018-07-23 18:42
OS: Windows 10 10.0
JDK: 1.8.0_181 amd64 Oracle Corporation
What is the actual behaviour?
Error at downloading Artwork : Error accessing url: Internal Server Error
tmm_logs.zip
What is the expected behaviour?
Steps to reproduce:
Additional
Have you attached the logfile from the day it happened?
tmm_logs.zip

Well, some of the Fanart.tv downloadservers have expired HTTPS SSL certificates.

CertificateExpiredException: NotAfter: Tue Jun 12 12:25:05 CEST 2018
There's nothing we can do about - we're already retrying 5 times...

duplicate of #373


Mock API result is different than result on AppSync console

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
Npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.0.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
I am creating a custom resolver to extend my automatic generated mutationCreate resolvers.
The custom extension queries a dynamodb table and evaluates the result based on the result the update is executed or a error is raised.
The logic works correctly while running some tests via the AWS console but when running amplify mock api I get wrong results.
Based on my analysis so far the result of the following line of code is different via the AppSync and mock.
$ctx.result.items.size() == 0
AppSync returns [] for $ctx.result.items
While mock returns null for $ctx.result.items
Expected behavior
Results are consistent between mock and AppSync to allow local testing
Reproduction steps

Run test via AppSync console
Run test via mock api

GraphQL schema(s)
No response
Project Identifier
No response
Log output
No response
Additional information
No response

Hey @tb102122 :wave: thanks for raising this! To better understand the context of your issue would you mind sending the project identifier output from amplify diagnose --send-report?

@josefaidt Sure no problem here you go Project Identifier: 51a20327a332cd6417119f4d26ea6cdd

Hey @tb102122 apologies for the delay here. Would you mind providing an example of an app where you're experiencing this issue? I'm seeing $ctx.result.items return [] in an error message, using the following resolver to test (Query.listTodos.res.vtl):
## [Start] ResponseTemplate. **
#if( $ctx.error )
  $util.error($ctx.error.message, $ctx.error.type)
#else
  $util.error($ctx.result.items)
#end
## [End] ResponseTemplate. **

Hey @josefaidt these are the following steps to reproduce.

create schema as below
update resolves based on definition attached backupResolvers.zip
run amplify mock
run below query and mutation

'''type Class @model {
id: ID!
Name: String! @index(name: "byClassName", queryField: "classByName", sortKeyFields: ["id"])
Note: String
}
query MyQuery {
listClasses {
items {
Name
id
}
}
}
mutation MyMutation {
createClass(input: {Name: "Heron"}) {
Name
id
}
}```
Expected result first mutation createClass runs successful the 2nd mutation createClass with the same name should raise an error.
When I run the setup via the APPSync console it works but in the mock API it does not work.
For the update process nothing works and there is no update done of the record.

Hey @tb102122 I was able to reproduce the issue using the provided steps and sample files, schema. Thank you for clarifying! Additionally, I am only able to receive the error after restarting the mock server, otherwise I am allowed to create as many records as I want.
"Name already existing please pick a different name."

After pushing to AWS and navigating to the AppSync console I am not able to create a record, receiving the following:
{
  "data": {
    "createClass": null
  },
  "errors": [
    {
      "path": [
        "createClass"
      ],
      "data": null,
      "errorType": "MappingTemplate",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "Unsupported element '$[operation]'."
    }
  ]
}

I also noticed a separate issue when reproducing this, which I've documented here https://github.com/aws-amplify/amplify-category-api/issues/849

@josefaidt thanks for the update and the other finding did you also try the update why it is not working?
I also realized that the naming's in AppSync are not consistent:
AWS AppSync > XXX > Schema > Mutation > CreateClass > PipelineResolver
[MutationcreateStartSequenceinit0Function]
[MutationcreateClassauth0Function]
[QuerygetStartSequencepostAuth0Function]
[MutationCreateClassDataResolverFn]
The StartSequence is another table in my schema linked to the table Class.

Hey @tb102122 :wave: after discussing with the team, the inconsistent naming you are seeing for the pipeline resolver is coming from an effort to re-use pipeline resolvers and reduce the number of resources we need to push. I'm still investigating the $[operation] issue, though

thanks for the updated

Is there any update on the investigation? @josefaidt

Do you have any update on the progress?


Made score persistent across levels

My attempt at helping with Issue #62. Essentially the fix is to make score persistent across levels. This was done by making score a global variable, and introducing a time variable that would trigger level changes in the way that score used to.
The fix has been tested on Chrome, Firefox, and Edge, and appears to work on all three. Hope this helps!

@Germlord Thanks for your contribution.
You have implemented the change perfectly, however on playing the game I think it has made the scoring system confusing for people new to the game.
Do you think it would be better if the score only incremented on coin collection and enemy kill, and a second count down timer added to the screen to show time left for each level?

Hmmmm. Yeah, that's a good point--it's difficult to tell that you're getting bonus score. Your idea seems solid, so if you'd like I could probably rework the existing code to do what you're describing pretty easily. I'm going to hold off till tomorrow to start, though.

@Germlord That would be great!


[FLINK-29339][runtime] JobMasterPartitionTracker returns future to avoid blocking main thread

What is the purpose of the change
JobMasterPartitionTracker#getClusterPartitionShuffleDescriptors returns future to avoid blocking the main thread.
Brief change log

JobMasterPartitionTracker#getClusterPartitionShuffleDescriptors returns future to avoid blocking the main thread.
Adjust TaskDeploymentDescriptorFactory so that createDeploymentDescriptor returns a future of DeploymentDescriptor.

Verifying this change
This change is already covered by existing tests, such as (please describe tests).
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializer: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@Sxnan Could you have a look at the above issue first ?

@gaoyunhaii Thanks for your review and sorry for the late update. I updated the PR accordingly. Could you please take another look?


Add danielbeck to matrix-auth

Description
https://github.com/jenkinsci/matrix-auth-plugin/
I'd like to merge and release https://github.com/jenkinsci/matrix-auth-plugin/pull/18 and https://github.com/jenkinsci/matrix-auth-plugin/pull/20 and, if I find the time, ideally take over some maintainership duties to ensure the plugin isn't terrible.
As existing uploaders I need your approval @jglick @mathias-nyman
Submitter checklist for changing permissions
Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

LGTM

@mathias-nyman thanks


Proposal: Drop support for normalize, parse and format

I don't think these are useful methods as they are implemented.
There are better places to handle this type of concern:

in the Field.component for handling user input,
in the initialValues for transforming values from external state,
onSubmit handler for transforming form values to external state

We already expect that the Form's state may be invalid, and, as far as I can see, restricting user input is outside of the scope of this library too.
Transforming the inputted text messes for the Form's state also messes around with the caret position on text inputs.
I'm not say there shouldn't be hooks to handle form value changes (which can happen in the validation or in the Field.component), but I would suggest that these three methods are unnecessary on a library that allows users to inject their own components.

Format seems to work the same as normalize now, unless I misunderstand: I still see the "formatted" values showing up in the redux store instead of the raw values.

I've used <Field> to wrap Material UI's <DatePicker>, the input.value is a Date object.
I used parse() and format() to convert the Date object to format I want ("YYYY-MM-DD").
Yet my first thought was to use a pre-submit function to convert the "native" input values (including the Date object for <DatePicker>) to the model of the API. However there's no pre-submit hook in redux-form so I resorted to parse() and format().

It seems that there are more people against this idea than people in favor of dropping such props.
Therefore, I'm closing this issue.

@leesei typically you would parse the values in the function you pass to handleSubmit.
Are there really common cases where parse and format don't cause annoying behavior?  For example if you parse values in a text field into a Date and then format them back to a string, the text field will be irritatingly contrary, resetting the cursor position anytime the re-formatted value ends up being different.
Thus far I always end up parsing values in my submit handler and formatting them before I initialize the form.  Which is much less convenient than if I could define such logic on the fields themselves, without making the fields behave in a contrary way.
I think it would be better for redux-form to:

store both raw and parsed values separately in redux store
have an option to validate parsed values rather than raw values
always pass the raw value to field components (if storing a special value in the redux store is necessary, it should be the component's responsibility to do parsing and formatting)
have the ability to pass raw and/or parsed values to initialize
pass raw and parsed values to the submit handler

@leesei that logic is better put in a wrapper component anyway so that you don't have to pass parse and format props to every date field you make.