Build fails with error

After launching the db I'm trying to build calcom:
finkel@box:~/calcom-docker$ DOCKER_BUILDKIT=0 docker-compose build calcom
Building calcom
Sending build context to Docker daemon  73.43MB
Step 1/29 : FROM node:16 as builder
 ---> 9bf69dd73b08
Step 2/29 : WORKDIR /calcom
 ---> Using cache
 ---> 188dc2d8222f
Step 3/29 : ARG NEXT_PUBLIC_LICENSE_CONSENT
 ---> Using cache
 ---> d78a6966f2f4
Step 4/29 : ARG CALCOM_TELEMETRY_DISABLED
 ---> Using cache
 ---> 02a9b0e45346
Step 5/29 : ARG DATABASE_URL
 ---> Using cache
 ---> ea21c9428d0b
Step 6/29 : ARG NEXTAUTH_SECRET=secret
 ---> Using cache
 ---> e9151c897584
Step 7/29 : ARG CALENDSO_ENCRYPTION_KEY=secret
 ---> Using cache
 ---> 38f031a5cea3
Step 8/29 : ARG MAX_OLD_SPACE_SIZE=4096
 ---> Using cache
 ---> fbf917cc4e2a
Step 9/29 : ENV NEXT_PUBLIC_WEBAPP_URL=http://NEXT_PUBLIC_WEBAPP_URL_PLACEHOLDER     NEXT_PUBLIC_LICENSE_CONSENT=$NEXT_PUBLIC_LICENSE_CONSENT     CALCOM_TELEMETRY_DISABLED=$CALCOM_TELEMETRY_DISABLED     DATABASE_URL=$DATABASE_URL     NEXTAUTH_SECRET=${NEXTAUTH_SECRET}     CALENDSO_ENCRYPTION_KEY=${CALENDSO_ENCRYPTION_KEY}     NODE_OPTIONS=--max-old-space-size=${MAX_OLD_SPACE_SIZE}
 ---> Using cache
 ---> 9d6a99db244b
Step 10/29 : COPY calcom/package.json calcom/yarn.lock calcom/turbo.json ./
 ---> Using cache
 ---> 75ab07ce54cb
Step 11/29 : COPY calcom/apps/web ./apps/web
 ---> Using cache
 ---> c113666d68ea
Step 12/29 : COPY calcom/packages ./packages
 ---> Using cache
 ---> 8e4b9c076662
Step 13/29 : RUN yarn global add turbo &&     yarn config set network-timeout<PHONE_NUMBER> -g &&     turbo prune --scope=@calcom/web --docker &&     yarn install
 ---> Running in eb0c5cd65065
yarn global v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - turbo
Done in 5.37s.
yarn config v1.22.19
success Set "network-timeout" to "1000000000".
Done in 0.03s.
Generating pruned monorepo for @calcom/web in /calcom/out
 - Added @calcom/web
 - Added @calcom/lib
 - Added @calcom/tsconfig
 - Added @calcom/app-store
 - Added @calcom/office365video
 - Added @calcom/ui
 - Added @calcom/embed-snippet
 - Added @calcom/embed-react
 - Added @calcom/dayjs
 - Added @calcom/eslint-plugin-eslint
 - Added @calcom/dailyvideo
 - Added @calcom/zoomvideo
 - Added @calcom/trpc
 - Added @calcom/app-store-cli
 - Added @calcom/core
 - Added @calcom/prisma
 - Added @calcom/config
 - Added @calcom/embed-core
 - Added @calcom/types
 - Added @calcom/features
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0".
warning "jest-mock-extended ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| >=3".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0-alpha || ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0-alpha || ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/app-store-cli ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/app-store-cli ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/app-store-cli ><EMAIL_ADDRESS>has unmet peer dependency "eslint@^3 || ^4 || ^5 || ^6 || ^7 || ^8".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/app-store-cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/prisma ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc ><EMAIL_ADDRESS>has unmet peer dependency "next@*".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0 || ^18.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow ><EMAIL_ADDRESS>has unmet peer dependency "react@>=17".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow ><EMAIL_ADDRESS>has unmet peer dependency "react-dom@>=17".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.1".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.1".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > kbar ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 17.x".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > kbar ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 17.x".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > kbar ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > react-hot-toast ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > react-timezone-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > react-timezone-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/app-store-cli > ink ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/trpc > @trpc/next ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/routing-forms > react-awesome-query-builder ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17 || ^18".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > kbar > @reach/portal ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 17.x".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/web > kbar > @reach/portal ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 17.x".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > @radix-ui/react-collection ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > @radix-ui/react-dismissable-layer ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > @radix-ui/react-dismissable-layer ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > react-remove-scroll ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > react-remove-scroll ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > react-remove-scroll ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/ui > @radix-ui/react-select > react-remove-scroll ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > @solana/web3.js ><EMAIL_ADDRESS>has unmet peer dependency "react-native@*".
warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > eth-block-tracker ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > eth-block-tracker > @babel/plugin-transform-runtime ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > eth-block-tracker > @babel/plugin-transform-runtime ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > eth-block-tracker > @babel/plugin-transform-runtime ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-00eabc36-4551-4607-b016-12d664cbe9ba > @calcom/rainbow > wagmi > @coinbase/wallet-sdk > eth-block-tracker > @babel/plugin-transform-runtime > babel-plugin-polyfill-corejs2 ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning Workspaces can only be enabled in private projects.
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
success Saved lockfile.
$ turbo run post-install
 WARNING  cannot find a .git folder. Falling back to manual file hashing (which may be slower). If you are running this build in a pruned directory, you can ignore this message. Otherwise, please initialize a git repository in the root of your monorepo
• Packages in scope: @calcom/app-store, @calcom/app-store-cli, @calcom/applecalendar, @calcom/around, @calcom/caldavcalendar, @calcom/campfire, @calcom/cli_base__app_name, @calcom/closecom, @calcom/config, @calcom/core, @calcom/dailyvideo, @calcom/dayjs, @calcom/ee, @calcom/emails, @calcom/embed-core, @calcom/embed-react, @calcom/embed-snippet, @calcom/eslint-plugin-eslint, @calcom/example-app, @calcom/exchange2013calendar, @calcom/exchange2016calendar, @calcom/exchangecalendar, @calcom/fathom, @calcom/features, @calcom/ga4, @calcom/giphy, @calcom/googlecalendar, @calcom/googlevideo, @calcom/hubspotothercalendar, @calcom/huddle01video, @calcom/jitsivideo, @calcom/larkcalendar, @calcom/lib, @calcom/n8n, @calcom/office365calendar, @calcom/office365video, @calcom/ping, @calcom/pipedream, @calcom/prisma, @calcom/qr_code, @calcom/rainbow, @calcom/raycast, @calcom/riverside, @calcom/routing-forms, @calcom/sendgrid, @calcom/sirius_video, @calcom/stripepayment, @calcom/tandemvideo, @calcom/trpc, @calcom/tsconfig, @calcom/typeform, @calcom/types, @calcom/ui, @calcom/vital, @calcom/weather_in_your_calendar, @calcom/web, @calcom/whereby, @calcom/zapier, @calcom/zoomvideo, WipeMyCal
• Running post-install in 60 packages
@calcom/prisma:post-install: cache bypass, force executing f8aee5f84ec1ff36
@calcom/app-store-cli:post-install: cache miss, executing df0f69c858975b52
@calcom/prisma:post-install: yarn run v1.22.19
@calcom/app-store-cli:post-install: yarn run v1.22.19
@calcom/prisma:post-install: $ yarn generate-schemas
@calcom/app-store-cli:post-install: warning package.json: No license field
@calcom/app-store-cli:post-install: $ yarn build
@calcom/prisma:post-install: $ prisma generate && prisma format
@calcom/app-store-cli:post-install: warning package.json: No license field
@calcom/app-store-cli:post-install: $ ts-node --transpile-only src/app-store.ts
@calcom/prisma:post-install: Prisma schema loaded from schema.prisma
@calcom/prisma:post-install: Error: spawn ENOMEM
@calcom/prisma:post-install: error Command failed with exit code 1.
@calcom/prisma:post-install: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@calcom/app-store-cli:post-install: No parser and no filepath given, using 'babel' the parser now but this will throw an error in the future. Please specify a parser or a filepath so one can be inferred.
@calcom/prisma:post-install: error Command failed with exit code 1.
@calcom/prisma:post-install: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@calcom/prisma:post-install: ERROR: command finished with error: command (packages/prisma) yarn run post-install exited (1)
command (packages/prisma) yarn run post-install exited (1)

 Tasks:    0 successful, 1 total
Cached:    0 cached, 1 total
  Time:    28.437s

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
The command '/bin/sh -c yarn global add turbo &&     yarn config set network-timeout<PHONE_NUMBER> -g &&     turbo prune --scope=@calcom/web --docker &&     yarn install' returned a non-zero code: 1

I don't really understand why the build fails

@calcom/prisma:post-install: Error: spawn ENOMEM
It looks like your machine may have run out of memory

Apparently so. It turns out one needs a pretty hefty machine to build the service, not your usual small server.

I solved it by temporarily upscaling my VPS and the downscaling it. Patience truly is a virtue ;)

hi @asm0dey, I'm working on deployment options then will shift back to optimizing the image. You should be good to simply pull the image, using the latest instructions.
Is it ok if we close this for now?

@krumware yes it works, thank you!


problem with "dma-coherent" in the device tree

Hello,
I found that read access to the Rx memory allocated by the driver is slow too.I have already referred to the issue:https://github.com/bperez77/xilinx_axidma/issues/69
In my app,i dis like this:
uint8_t *dma_rx_buf; dma_rx_buf = axidma_malloc(axidma_dev, 32768); sendto(Socket_UDP,dma_rx_buf,16388,0,(struct sockaddr*)&UDP_addr_dst,sizeof(UDP_addr_dst));
When I use function sendto(), I read dma_rx_buf very slowly.I modify the DT with "dma-coherent" like this:
/include/ "system-conf.dtsi" / {       	axidma_chrdev: axidma_chrdev@0 { 	compatible = "xlnx,axidma-chrdev"; 	dmas = <&axi_dma_0 0 &axi_dma_0 1>; 	dma-names = "tx_channel", "rx_channel";         };         amba_pl: amba_pl { 		#address-cells = <1>; 		#size-cells = <1>; 		compatible = "simple-bus"; 		ranges ; 		axi_dma_0: dma@40400000 { 			#dma-cells = <1>; 			clock-names = "s_axi_lite_aclk", "m_axi_sg_aclk", "m_axi_mm2s_aclk", "m_axi_s2mm_aclk"; 			clocks = <&clkc 15>, <&clkc 15>, <&clkc 15>, <&clkc 15>; 			compatible = "xlnx,axi-dma-1.00.a"; 			interrupt-parent = <&intc>; 			interrupts = <0 29 4 0 30 4>; 			reg = <0x40400000 0x10000>; 			xlnx,addrwidth = <0x20>; 			dma-coherent; 			dma-channel@40400000 { 				compatible = "xlnx,axi-dma-mm2s-channel"; 				dma-channels = <0x1>; 				interrupts = <0 29 4>; 				xlnx,datawidth = <0x20>; 				xlnx,device-id = <0x0>; 			}; 			dma-channel@40400030 { 				compatible = "xlnx,axi-dma-s2mm-channel"; 				dma-channels = <0x1>; 				interrupts = <0 30 4>; 				xlnx,datawidth = <0x20>; 				xlnx,device-id = <0x1>; 			}; 		}; 	}; };
Then when I use the function axidma_oneway_transfer() to receive data,a mistake has occurred:
xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051500 tdr 3f051500 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051580 tdr 3f051580 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051600 tdr 3f051600 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051680 tdr 3f051680 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051700 tdr 3f051700 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051780 tdr 3f051780 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051800 tdr 3f051800 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051880 tdr 3f051880 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051900 tdr 3f051900 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051980 tdr 3f051980 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051a00 tdr 3f051a00 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051a80 tdr 3f051a80 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051b00 tdr 3f051b00 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051b80 tdr 3f051b80 xilinx-vdma 40400000.dma: Channel ef2edc10 has errors 10, cdr 3f051c00 tdr 3f051c00
If i do not use "dma-coherent;" in DT, there is no erro. How can i improve the speed that access to the Rx memory dma_rx_buf？
When i test like this:
char udp_tx_buf[65536]; udp_txSize = sendto(Socket_UDP,udp_tx_buf,16388,0,(struct sockaddr*)&UDP_addr_dst,sizeof(UDP_addr_dst));
The read speed is good.Is there any way to solve this problem?

Hi could you please provide more detail? and format your code...


Fix image links and other links in the test

@Erioldoesdesign What's the matter with them at the moment?


Move blockly XML definition out of index.html

It confuses crawlers who then consider the blockly terms (like PLUS, MINUS, ....) as keywords for the page.

The following code is dependent on that node being in index.html:

https://github.com/Microsoft/pxt/blob/master/pxtblocks/blocklyloader.ts#L505
https://github.com/Microsoft/pxt/blob/master/webapp/src/blocks.tsx#L59
https://github.com/Microsoft/pxt/blob/master/webapp/src/blocks.tsx#L190

First option would be to have toolbox.xml and lazily request it in these three places (with local caching). Second option would be to just include it as a string constant in a toolbox.ts file and import it. The former approach would be better if it is likely to get modified (I'm not sure if @sgk's work on localisation is likely to affect it) but the second would be easier.

I'm working on a PFR for the second approach mentioned (just putting it into a string constant)


Some of the events disappear on zooming in and out

Describe the bug
Some events that are being displayed at the hour timeline disappear when changed to the daily or weekly timeline
Screenshots
If applicable, add screenshots to help explain your problem.

Anyone else facing this issue

I believe some code example (especially data) would be useful to reproduce this, it's hard to figure out the issue from the screenshot


Filtered functools.wraps method to avoid missing attribute problem fo…

…r native methods.

looks fine is this the new code?
return functools.wraps(wrapped, assigned=filter(lambda a: hasattr(wrapped, a), assigned),
updated=filter(lambda a: hasattr(wrapped, a), updated))

merge it?

Yep
On Dec 3, 2015 7:31 PM, Bo Willyard<EMAIL_ADDRESS>wrote:
merge it?
—
Reply to this email directly or
view it on GitHub.


More flexible tick spacing

What can we do to make ScottPlot better?
Currently automatic tick spacing is based on "nice numbers". These numbers are defined as a literal here: https://github.com/swharden/ScottPlot/blob/f9b4b2ad5520610c1d8bce4bba8e33bf3e318876/src/ScottPlot/Config/TickCollection.cs#L203
These give nice numbers in decimal, but not any other base. When I worked on #475 I neglected to work on this and then I forgot about it for several months :/ This is theoretically a very easy change, perhaps add another parameter for radix? Then nice numbers in hex could be [2, 2, 2, 2], giving nice numbers of [16, 8, 4, 2, 1]. And mentions to Log10 would be replaced with a call to the log function with the appropriate base.
Admittedly this is a pretty niche feature and while a function to create "nice" numbers for any radix is possible I'm unsure that it would really be used. As it is the only commonly used radices are decimal, hex, and binary. You can't really create a nice looking number in binary anyways so there's probably not much downside to just hardcoding in nice numbers for hex like was done for decimal. Might get nicer results that way too if it's hand done for each radix. If there's a compelling case that other radices might be used then I may change my mind. Keep in mind that radices above 16 are not currently supported.

I implemented this on my branch https://github.com/Benny121221/ScottPlot/tree/nice-hexnumbers, however, I added some new tests and they didn't pass. I'll try and fix that or rewrite the offending code.

Hey @Benny121221, this is an interesting idea! I agree that on one hand this is a pretty obscure use case, but on the other hand it seems that supporting it looks to be pretty simple.
As you refine this you could add another optional argument at the end of the Plot.Ticks() list
https://github.com/swharden/ScottPlot/blob/f9b4b2ad5520610c1d8bce4bba8e33bf3e318876/src/ScottPlot/Plot/Plot.Ticks.cs#L40-L42
to store a feature toggle in the end of the ticks config module

Oops, I hit enter with the comment button selected and I guess I hit send too early. I pretty much captured all the technical details with the message above, but I wanted to follow-up with a "thanks for your effort on this one"!
I'm pretty deep working on #578 for at least the next few days (it's taking a lot longer than I expected) so no rush finishing this one, but I'm excited to see how it ends up!

As you refine this you could add another optional argument at the end of the Plot.Ticks() list ... to store a feature toggle in the end of the ticks config module

To toggle which feature? The radix and prefixes are already there:
https://github.com/swharden/ScottPlot/blob/f9b4b2ad5520610c1d8bce4bba8e33bf3e318876/src/ScottPlot/Plot/Plot.Ticks.cs#L36-L39
Perhaps the use of both base and radix here isn't a great plan, but currently base is the only word used for user-facing code. So at least the user isn't confused.

currently base is the only word used for user-facing code

I agree with your assessment - we can leave the method the way it is and use the word "base" in user-facing arguments and documentation. Thanks again for this @Benny121221!


Update Power Automate URL

Should the environment variable for Power Automate be updated to https://make.powerautomate.com/environments/

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

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up inventory components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @mscloud-pro. This issue has been assigned to the doc author for review.

Thank you! Made the change locally, ready for our next docs update later this week.

Fixed yesterday with our latest docs update!


Too much reactivity when passing in invalidCount to form content

In the following code, {{log "refreshing"}} is called once, as expected:
<template name="myFormBlock">
  <form>
    {{> UI.contentBlock
        data=data
        schema=schema
        schemaContext=__schemaContext__
        setValidatedValue=__setValidatedValue__
        submit=__submit__
        submitted=__submitted__
        loading=__loading__
        failed=__failed__
        success=__success__
    }}

	  <button type="submit">Submit</button>

  </form>
</template>

<template name="myForm">

    {{#myFormBlock schema=schema action=action data=data}}

	  {{log "refreshing"}}

      {{> myInput field='testField1'}}
      {{> myInput field='testField2'}}
      {{> myInput field='testField3'}}

    {{/myFormBlock}}

</template>

But suppose you want to pass in invalidCount as an argument to UI.contentBlock (see the use case in discussion https://github.com/meteortemplates/forms/issues/15), like this:
<template name="myFormBlock">
  <form>
    {{> UI.contentBlock
        data=data
        schema=schema
        schemaContext=__schemaContext__
        setValidatedValue=__setValidatedValue__
        submit=__submit__
        submitted=__submitted__
        loading=__loading__
        failed=__failed__
        success=__success__
		invalidCount=invalidCount
    }}

	  <button type="submit">Submit</button>

  </form>
</template>

Then {{log "refreshing"}} is called 4 times (once + once per input).

This works properly with 1.8.0 but you must use:
{{#with context}}
  {{#if submitted}} ... {{/if}}
  {{#if invalidCount}} ... {{/if}}
{{/with}}

I could conceivably make all these individual helpers (so context doesn't have to be used). But this was the simplest option for now.

Code is here:
https://github.com/meteortemplates/forms/blob/master/lib/helpers.coffee


Add support in pubsub for channel point redemptions

Feature Request
Twitch has added the ability to subscribe to channel point redemption: https://discuss.dev.twitch.tv/t/introducing-the-channel-points-redemption-pubsub-topic/23489?sf226250428=1

Added in 4.0.0-pre.7.


Confusing/new behavior/error with registered distribution

Here is a minimal version of an issue raised by a user. When attempting to clear the environment, the presence of a previously registered distribution internally causes an inscrutable error during the second round of compilation. The user reports that their code worked previously, so this problem may have been introduced in a recent version of nimble.
Cursory investigation did not reveal an obvious change that would have introduced this. There were (less obvious) changes for AD to check and utilize user-defined distributions, so that might be the source of the problem.
library(nimble)

dfoo <- nimbleFunction(
  run = function(x=double(), log=integer(0, default=0)) {
    return(0)
    returnType(double())
  }
)

m <- nimbleModel(
  nimbleCode({
    x ~ dfoo()
  })
)

cm <- compileNimble(m)

rm(list = ls())
# Then rerun from dfoo through through compileNimble to see the error

# The error does not happen if:
# rm(list=ls()) is not run, OR
# deregisterDistributions("dfoo") is run

The error occurs in 0.13.2, so probably not related to AD.
Here's the error:
Error: In sizeAssignAfterRecursing: 'rfoo' is not available or its output type is unknown.
 This occurred for: model_x[1] <<- rfoo(1)
 This was part of the call:  {
  model_x[1] <<- rfoo(1)

This is because we've created a dummy rfoo, which is registered, and then rm removes it "uncleanly".

I'm not inclined to "fix" this as I would argue this is not a bug. We told the user initially we are creating rfoo for them and that if they change the distribution they need to call deregisterDistributions. They then chose to blow away the environment's objects. And the error reasonably informative. It says that rfoo is not available, albeit the error is not trapped where we probably would want it to be.
We could trap this in  checkUserDefinedDistribution with some specific logic, but the code that would be involved feels clunky as it would duplicate some of what registerDistributions does.

Check in sizeASsignRecursing if the issue seems to relate to registered distributions.

I'm modifying the error trapping in sizeAssignAfterRecursing to give a more refined message in this case.


Unclear relationship between Lighthouse-managed AAD tenants and Microsoft Customer Agreements for Azure

The topology for the Tenant management architecture makes a lot of sense and could prove incredibly powerful; however, there seems to be an assumption baked into the architecture that all tenants involved are mature (or at least have their own MCAs).

Is there any possible way to go about starting this multi-tenancy management architecture from scratch?
What about cases where your organization is limited to a single MCA?

This architecture seems like a non-starter for single MCA scenarios given the operation of transferring from Tenant A to one of B or C can take upwards of an hour to complete.

Looking forward to hearing back!

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

ID: 444f20b5-6919-7322-236e-26fc16459acc
Version Independent ID: aa3f67d7-18d0-3a45-7432-76da8a94a1fd
Content: Azure Lighthouse in enterprise scenarios - Azure Lighthouse
Content Source: articles/lighthouse/concepts/enterprise.md
Service: lighthouse
GitHub Login: @JnHs
Microsoft Alias: jenhayes

@brad-lucas Thanks for your comment. We will review the issue and get back to you shortly.

Hi @JnHs,
I guess my core question when reviewing the documentation was how I could proceed as a generally new Azure customer.
The documentation seems to address the scenarios for "my enterprise only needs and uses one tenant" and "my enterprise needs and uses multiple tenants, managing underlying subscriptions with Lighthouse", but I feel like there's something missing in between along the lines of "my enterprise will need multiple tenants managed by Lighthouse, but has yet to set up anything (the tenants, their subscriptions, etc.)".
Not to overstate anything, but perhaps there is an overarching issue with a general lack of documentation for getting a multi-tenant architecture up and running. I've been working with sales and support teams across Azure and AAD and it's taken over a week to vet whether what I'm trying to do is even possible and then to actually set up the Microsoft agreements, etc.
I hope this helps clarify my issue, and thanks for following up with me in doing so!

@brad-lucas, thanks for the clarifications! You might find some useful information about multi-tenant architecture in general here: https://docs.microsoft.com/en-us/azure/architecture/guide/multitenant/overview - and specifically here: https://docs.microsoft.com/en-us/azure/architecture/guide/multitenant/approaches/resource-organization. I will plan to add these links to the Lighthouse/enterprise topic as well. (If there is info that you'd expect to find in that section that's not there, I'd encourage you to submit issues directly on those docs.)
I'm not sure there are specific considerations that would universally apply to an enterprise wanting to set up multiple tenants to be managed through Azure Lighthouse - there's a lot of flexibility to do this in whatever way makes sense for their scenarios as far as which resources are housed where. Some of the Azure service integration articles in the Lighthouse how-to guides may be useful as well.

I've added these links and will close this issue now, but please let us know if you have additional questions regarding this document.
#please-close


fix(libsinsp): check param num on connect/open/openat parsing

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Following the recent addition to extra parameters and their parsing to connect/open/openat (https://github.com/falcosecurity/libs/pull/235) we still want to be compatible with drivers and scap files that didn't have those params. This PR adds the relevant check.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

d9c8635 fix(libsinsp): check param num on connect/open/openat parsing

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Hi @LucaGuerra. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/ok-to-test

LGTM label has been added.  Git tree hash: e01dad47c75d7ab78491bc5e3ff99f076b39ea03

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @FedeDP


Menu: Menu items still show border on built product

Possibly Linux only.
Built product, with Dark+:

Dev, with Dark+:

We change some CSS order in the built product, which might override styles set in dev.

I'm not even able to debug this in the built product. As soon as I focus the devtools, that border is gone. @bpasero might know exactly where that style is.

I was only able to suppress it with:
.menubar-menu-items-holder .action-menu-item {
    outline-color: transparent !important;
}

Which is definitely not the fix. We should understand why this is different in the build vs dev and override the style properly.

this was addressed via https://github.com/Microsoft/vscode/commit/01fb34dc00c36566afc7ac55e09be4c17f2f1bb4


Upgrade to Java 17

To enable the Java upgrade, the following dependencies where upgraded too:

Lombok => 1.18.22
Spring Boot => 2.6.0

Currently the deployment with the Java 17 runtime fails:
$ ./gradlew appengineDeploy --refresh-dependencies
> Task :server:appengineStage FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':server:appengineStage'.
> com.google.cloud.tools.appengine.AppEngineException: Cannot process application with runtime: java17

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 14s
28 actionable tasks: 2 executed, 26 up-to-date

See https://cloud.google.com/appengine/docs/standard/java-gen2/runtime#java-17-preview
https://cloud.google.com/products#product-launch-stages
https://github.com/GoogleCloudPlatform/appengine-java-standard

Java 17 is available as preview feature since 16th March. The preview will last about six month.
Since I don't know how to circumvent the error above by using the preview feature, the Java 17 upgrade needs to wait for about six month.


[ENH] Add ability to time estimator methods

Is your feature request related to a problem? Please describe.
Having the ability to measure run-time of different estimator methods would be useful for several reasons, including:

Making it easy for users to get an estimate of timings in the case that something like fit time is important to them
Allow users to understand the timings of individual pipeline components (as well as the total pipeline time)

Right now you could use notebook cell magic to get timings for a particular method for a given estimator or pipeline. In the non-notebook case, a user could still get the timing of a specific method relatively easily. But this is difficult for composite functionality (a user could measure total time, but wouldn't be able to easily measure the time of the components in a pipeline).
Describe the solution you'd like
I'd like to see us add functionality to get the run time from estimator methods. A straight-forward approach would be to add functionality to the public base class methods that stores the start and end time for that method. This could then be retrieved by a new method (or property) that returns the difference between the times (it could take name of a method and return the times for that method).
The time module has time.perf_counter() and the difference in time between two calls seems like it could be used to measure the elapsed time of different methods.
One option is to alter the base classes directly with something like:
import time
class BaseObject:
    ...
    def _get_time(self):
        return time.perf_counter()

class BaseForecaster:
    """This example shows just measuring fit/predict, but could be applied to update, etc.

    The new attributes in a class would depend on the estimator type, e.g. expect
    "fit_time_" and "transform_time_" for timing a transformer, etc.
    """
    ...
    def __init__(self, ...):
        ... # usual stuff in __init__
        self.fit_time_
        self.predict_time_

    def fit(self, ...):
        st = self._get_time()
        ... # the usual stuff that is in fit
        self.fit_time_ = st - self._get_time()

    def predict(self, ...):
        st = self._get_time()
        ... # the usual stuff that is in predict
        self.predict_time_ = st - self._get_time()

Another alternative is to try and figure out a decorator to add the attributes and the functionality in the public methods.
Given the functionality being added to the base classes, things like ForecastingPipeline could be updated to capture the total timings of different steps in the pipeline (Note for transformers the fit time for a given transformer would be fit + transform time within a pipeline, since both are called during pipeline fit).
Describe alternatives you've considered
The alternative would be a more complex way of having some sort of wrapper (function, composite class, etc) that enabled this functionality. But not sure of the feasibility of getting the timings of the steps of a pipeline that way and it seems like a complex implementation relative to updateing the base classes. Plus carrying around the times in the base class shouldn't provide too much overhead in the base classes.
Another alternative is to just update things like ForecastingPipeline so that they store timings of each step in the pipeline. But provides less generality.
Additional context

Writing a decorator may be a good option here. We may also want to write timings to a dictionary with key beings methods since there will be a number of additional ones (update, transform, etc.) and perhaps add a get_timings method that returns all timings?
I like the simplicity of adding this to the estimator, but I'm not sure if it should be a core concern of an estimator. Is there an easy alternative of implementing this outside the estimator?


Feature: Hard Cap and Weekly Cap

Resolves #9 #50

@SamMousa please re-review. Now points behave as described by you in #50

LGTM, have skimmed over and not tested in game.

I have tested it to confirm as working as described in #50


HBASE-27574 Implement ClusterManager interface for Kubernetes

A basic implementation that supports taking destructive actions. Assume that services are running behind a resilient Deployment of some kind, and that the cluster will handle starting up replacement processes. Requires specification of a scoping namespace.

Transitive hull of the new dependencies. Should we be shading these?
[INFO] +- io.kubernetes:client-java:jar:17.0.0:test
[INFO] |  +- io.prometheus:simpleclient:jar:0.15.0:test
[INFO] |  |  +- io.prometheus:simpleclient_tracer_otel:jar:0.15.0:test
[INFO] |  |  |  \- io.prometheus:simpleclient_tracer_common:jar:0.15.0:test
[INFO] |  |  \- io.prometheus:simpleclient_tracer_otel_agent:jar:0.15.0:test
[INFO] |  +- io.prometheus:simpleclient_httpserver:jar:0.15.0:test
[INFO] |  |  \- io.prometheus:simpleclient_common:jar:0.15.0:test
[INFO] |  +- io.kubernetes:client-java-proto:jar:17.0.0:test
[INFO] |  +- org.yaml:snakeyaml:jar:1.33:test
[INFO] |  +- org.apache.commons:commons-compress:jar:1.22:compile
[INFO] |  +- org.bouncycastle:bcpkix-jdk18on:jar:1.72:test
[INFO] |  |  +- org.bouncycastle:bcprov-jdk18on:jar:1.72:test
[INFO] |  |  \- org.bouncycastle:bcutil-jdk18on:jar:1.72:test
[INFO] |  +- com.google.protobuf:protobuf-java:jar:3.21.10:compile
[INFO] |  +- org.apache.commons:commons-collections4:jar:4.4:test
[INFO] |  \- org.bitbucket.b_c:jose4j:jar:0.9.2:test
[INFO] +- io.kubernetes:client-java-api:jar:17.0.0:test
[INFO] |  +- io.swagger:swagger-annotations:jar:1.6.9:test
[INFO] |  +- com.squareup.okhttp3:okhttp:jar:4.10.0:test
[INFO] |  |  +- com.squareup.okio:okio-jvm:jar:3.0.0:test
[INFO] |  |  |  \- org.jetbrains.kotlin:kotlin-stdlib-common:jar:1.5.31:test
[INFO] |  |  \- org.jetbrains.kotlin:kotlin-stdlib:jar:1.6.20:test
[INFO] |  |     \- org.jetbrains:annotations:jar:13.0:test
[INFO] |  +- com.squareup.okhttp3:logging-interceptor:jar:4.10.0:test
[INFO] |  |  \- org.jetbrains.kotlin:kotlin-stdlib-jdk8:jar:1.6.10:test
[INFO] |  |     \- org.jetbrains.kotlin:kotlin-stdlib-jdk7:jar:1.6.10:test
[INFO] |  +- com.google.code.gson:gson:jar:2.10:compile
[INFO] |  \- io.gsonfire:gson-fire:jar:1.8.5:test

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 48s
master passed

+1 :green_heart:
compile
0m 19s
master passed

+1 :green_heart:
shadedjars
3m 53s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 14s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 33s
the patch passed

+1 :green_heart:
compile
0m 20s
the patch passed

+1 :green_heart:
javac
0m 20s
the patch passed

+1 :green_heart:
shadedjars
3m 49s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 13s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 42s
hbase-it in the patch passed.

16m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4979

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1eab1961a285 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / da261344cc

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/1/testReport/

Max. process+thread count
591 (vs. ulimit of 30000)

modules
C: hbase-it U: hbase-it

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 43s
master passed

+1 :green_heart:
compile
0m 24s
master passed

+1 :green_heart:
checkstyle
0m 10s
master passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 23s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 23s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

+1 :green_heart:
checkstyle
0m  8s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
9m  4s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 37s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 28s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s
The patch does not generate ASF License warnings.

23m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4979

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile spotbugs hbaseanti checkstyle

uname
Linux a1ff09085b00 5.4.0-1093-aws #102~18.04.2-Ubuntu SMP Wed Dec 7 00:31:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / da261344cc

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: hbase-it U: hbase-it

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

For better work together with K8s, I think we need to discuss more about how to define the actions...
A simple kill of a region server is not enough to reduce the number of region servers, as the deployment will soon start a new one...
Simply setting the number of pods is not applicable here as we can not control which region server it will kill...

I agree that there is a longer arch of a discussion re: HBase and a container runtime platform like Kubernetes. I believe that Kubernetes implements its own form of chaos, and I have not yet explored an implementation based on that tooling.
However. Just like the CM-based and coprocessor-based implementations before it, this has allowed me to use our existing ITBLL + Chaos tools in an environment that is convenient to what I have available to me in my organization. It's convenient to be able to run the same processes in the new deployment environment and have everything basically function. I'd like to share it with the community, especially if there's a path to us using similar tools as part of our project's resource budget.

I agree that there is a longer arch of a discussion re: HBase and a container runtime platform like Kubernetes. I believe that Kubernetes implements its own form of chaos, and I have not yet explored an implementation based on that tooling.
However. Just like the CM-based and coprocessor-based implementations before it, this has allowed me to use our existing ITBLL + Chaos tools in an environment that is convenient to what I have available to me in my organization. It's convenient to be able to run the same processes in the new deployment environment and have everything basically function. I'd like to share it with the community, especially if there's a path to us using similar tools as part of our project's resource budget.

Then let's not use the generate "KubernetesClusterManager" as the name? Maybe later we will have other type of K8s cluster manager...

Rebased and PR feedback.  Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 45s
the patch passed

+1 :green_heart:
compile
0m 17s
the patch passed

+1 :green_heart:
javac
0m 17s
the patch passed

+1 :green_heart:
shadedjars
4m 13s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 38s
hbase-it in the patch passed.

16m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4979

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b8f6afff9ae5 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 913cf6b96d

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/testReport/

Max. process+thread count
557 (vs. ulimit of 30000)

modules
C: hbase-it U: hbase-it

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 47s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 47s
master passed

+1 :green_heart:
compile
0m 19s
master passed

+1 :green_heart:
shadedjars
4m 49s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 13s
master passed

-0 :warning:
patch
5m  8s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 27s
the patch passed

+1 :green_heart:
compile
0m 17s
the patch passed

+1 :green_heart:
javac
0m 17s
the patch passed

+1 :green_heart:
shadedjars
5m 47s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 51s
hbase-it in the patch passed.

21m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4979

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b00f921f88c8 5.4.0-1088-aws #96~18.04.1-Ubuntu SMP Mon Oct 17 02:57:48 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 913cf6b96d

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/testReport/

Max. process+thread count
580 (vs. ulimit of 30000)

modules
C: hbase-it U: hbase-it

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 32s
master passed

+1 :green_heart:
compile
0m 24s
master passed

+1 :green_heart:
checkstyle
0m 10s
master passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 23s
master passed

-0 :warning:
patch
0m 29s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 12s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
checkstyle
0m  9s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
12m 47s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 38s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m  8s
The patch does not generate ASF License warnings.

30m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4979

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile spotbugs hbaseanti checkstyle

uname
Linux f7b7761c43f4 5.4.0-1093-aws #102~18.04.2-Ubuntu SMP Wed Dec 7 00:31:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 913cf6b96d

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
86 (vs. ulimit of 30000)

modules
C: hbase-it U: hbase-it

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4979/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

And I'm a bit interest on how do you guys manage datanode or namenode on K8s? They have local storage, so if you delete the pod and launch a new one at other places, the data will be lost...
Use stateful set?
Thanks.

Personally I prefer to use Exec API for this. It seems somewhat artificial to try reducing the pod count just for the sake of it.
IMO chaos monkey is for testing both hbase handling and deployment automation. Outside k8s, if you stop a regionserver process you better have monit or sysctl to start it back up. In kubernetes, this is handled for you.
So if chaos sends a kill 9, it's doing a good job of testing hire both systems handle a regionserver dying. Maybe in kubernetes you have an init container which gets in the way of the pod gracefully having a regionserver container dying. Chaos would expose that.
Otherwise I think kill -stop is an important feature and I wouldn't want to bury it in an option. So that's another reason just replacing ssh with Exec api would be nice.

And I'm a bit interest on how do you guys manage datanode or namenode on K8s? They have local storage, so if you delete the pod and launch a new one at other places, the data will be lost

We currently don't run DataNodes in k8s. For namenodes we use StatefulSet with EBS backed.
For DataNodes we don't want to use EBS, too expensive. When we eventually get to then we plan to use FlexVolumes to basically provision space on particular SSD-backed kube nodes. So if pod restarts, it would go to the same node if it's available. If not, it would go elsewhere and lose its data but this is how things work outside k8s and is handled by hdfs replication. Sadly can't give more details than this right now because it's been on hold for a while so we can work on other things.


[Bug] "atom core" deprecation after Split Diff: Toggle

Here's the deprecation message:
Assigning editor 260's height explicitly via position: 'absolute' and an assigned top and bottom implicitly assigns the autoHeight property to false on the editor. This behavior is deprecated and will not be supported in the future. Please explicitly assign autoHeight on this editor.

TextEditorComponent.measureDimensions - /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:1012:20
TextEditorComponent.becameVisible - /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:295:12
TextEditorComponent.checkForVisibilityChange - /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:994:16
atom-text-editor.attachedCallback - /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-element.js:87:22
atom-pane-axis.childAdded - /Applications/Atom.app/Contents/Resources/app.asar/src/pane-axis-element.js:95:12
Function.module.exports.Emitter.simpleDispatch - /Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14

Hello, and thanks for the contribution! This is an issue with a specific Atom API and I have previously logged https://github.com/atom/atom/issues/13736 for it. As of yet, it hasn't been looked into, so please make some noise over there so it gets fixed!

@mupchrch But if I activate split-diff from git-plus, atom doesn't send me the deprecation.

@mupchrch Any news on this issue ?

Sorry, glad you asked because I would have forgot to investigate since this issue is closed! Reopening - will hopefully get time to look tonight.

Ugh forgot to comment my findings, sorry @ooJerryLeeoo!
It looks like git-plus is setting up split-diff manually instead of just calling the toggle command. git-plus is feeding two editors directly to one of my API's and bypassing the split-diff logic that finds the visible editors and splits panes if there aren't two found side by side (the logic mentioned in atom/atom#13736). This is the logic that is causing the deprecation warning.

The bug is still there. And I don't have git-plus package.


_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 32s
Maven dependency ordering for branch

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  8s
Maven dependency ordering for patch

+1 :green_heart:
hadolint
0m  2s
There were no new hadolint issues.

+1 :green_heart:
shellcheck
0m  1s
There were no new shellcheck issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

_ Other Tests _

+0 :ok:
asflicense
0m  1s
ASF License check generated no output?

9m 15s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1580/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1580

Optional Tests
dupname asflicense hadolint shellcheck shelldocs

uname
Linux 5cb117936292 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 24961c5c34

Max. process+thread count
47 (vs. ulimit of 12500)

modules
C:  U:

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1580/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) shellcheck=0.4.6 hadolint=1.17.5-0-g443423c

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Element polyfill issue

On Chrome (version 52.0.2743.82) loading the Element.prototype.classList polyfill raises and exception:
Failed to execute 'appendChild' on 'Node': Only one element on document allowed.
See https://fredj.io/polyfill.html

Classlist is not required in chrome 52.  You are loading it with the always flag, but not the gated flag, which means you're trying to overwrite a native implementation with a polyfill.  In this case, the polyfill cannot overwrite the native implementation, but we don't consider this a problem.  Either include the gated flag, or remove the always one.


Points calculation broken?

Description
8.5.6 appears to have broken how ESGST works out how many points I have. At first I thought it was just visual bug in the header that said I had "7PP" instead of correctly saying "7,020P", but then I noticed that the enter buttons on the main page were red and had the "Not Enough Points" tool-tip, although I could still click the buttons to enter the giveaways.
Disabling the "Time To Point Cap Calculator" (1.36) option seems to be a workaround to remove the header points display bug, but the enter button is still claiming I haven't got enough points.
Maybe it's because I'm so far above the point cap?
Time To Point Cap Calculator (1.36) disabled:

Time To Point Cap Calculator (1.36) enabled:

v8.5.6 completely changed how the header elements are handled, so it's not a problem with your cap, I'll look into it.

I see this is closed. Any idea when 8.5.7 will post to the Chrome Extension page?

Firefox updates it almost immediately, while Chrome may take up to 24 hours, or more.

Great, thanks!


Migration of gst-plugins-base: few fixes

Remove with_egl, with_wayland, with_graphene, with_libpng & with_libjpeg options when with_gl is disabled, since these options don't contribute to package when gl is disabled
Move wayland-protocols to build requirements. There is a special trick for conan v1 one profile in order to generate pc file of wayland-protocols.
Add glib (and also wayland when with_wayland is enabled) to build requirements, except in case of conan v1 one profile (due to edge cases bug when dependencies are overidden).
Decide whether winflexbison is a build requirement (instead of bison/flex) based on OS of build machine rather than OS of host machine.

Summary
Changes to recipe:  lib/[version]
Motivation

Details

[ ] Read the contributing guidelines
[ ] Checked that this PR is not a duplicate: list of PRs by recipe
[ ] Tested locally with at least one configuration using a recent version of Conan

Thanks!


GH1184: Added support for manually including/excluding files for tools

[x] Query string should support multiple parameters with same name
[x] Add include/exclude parameter
[x] Better error messages
[x] Tests

@cake-build/team Ok, I think this is ready for review.

Relates to #1184

@patriksvensson are you in a position to rebase this?  And I can try to take a look tonight?

@gep13 Sure, I will do this during the day.

@gep13 Rebased

@gep13 Rebased against upstream/develop.


Windows update to 69.x.x.x

Hey,are there any plans to update Chrominium to Windows?

@alexoler Yes, it is in progress. See #475.


Integrate with spells so that the measured template is set up with difficult terrain

Currently you can add to the measured template, but it would be nice to be able to configure a spell to set that up automatically when they create a measured template.

Added this in the latest release.


Vulkan Mobile: Orientation Sensor / Some artifacts appear

Godot version
4.0.alpha12
System information
Android 12 Samsung m21
Issue description
The first rotation of the phone is ок. The second rotation changes the aspect ratio. Some artifacts appear. Default settings.

Steps to reproduce
AndroidAPK_Godot4_Alpha.apk - Run on smartphone and rotate 90 degrees.
Minimal reproduction project
Project:
test_12alpha.zip
Apk file:
AndroidAPK_Godot4_Alpha12.zip

@moomoosic Please upload a minimal reproduction project to make this easier to troubleshoot.

Is this still reproducible in 4.0 RC 3 or later?

The project's thread model is set to Multi-Threaded, which causes various rendering issues. For instance, attempting to resize the running project window's on desktop will cause the project to freeze (and possibly cause your system to lockup).


Can this tool help me connect port when docker run use --net="host"

Hi @631068264, I assume you are trying to use --net=host so that your container listens on a port from your macOS host instead of the Linux VM host (correct me if I'm wrong).
Currently this package does not solve that, although I can think of some options to make that happen (ie. monitor /proc/net/tcp and iptables on Linux VM and add port forwarding NAT rules on macOS using pfctl). Let me know if you think this would be useful.
In the mean time, you can replace Docker Desktop with Rancher Desktop (using dockerd runtime) which supports --net=host macOS host binding out of the box (via lima). I've been using Rancher Desktop as a drop-in replacement for Docker Desktop for about a month now without issues.

Thanks for your reply.
I  just wanted to find a solution or a tool help me, when use --net=host on OSX  can work like in linux. Because I always test my application  on local.
I'm not good at these(docker network on OSX, etc) so I'm sorry that I can' tell you sth more valuable. I even don't know how to connect the Linux VM on OSX.

Thanks for clarifying. If you are not tied to the official Docker Desktop, I would give something like Rancher Desktop a try as it supports what you are trying to do.
I'll keep this feature in mind for this package though and let you know if it's gets added in the future.

BTW a very nice feature to have, I have tried to map the docker container somehow to my local machine <IP_ADDRESS>, but don't have success with that.

This is exactly what I am looking for as well - if there is a way to do this it would be great.  I am specifically running into the issue where are the discoverable IoTs are on the host network and home assistant cannot auto discover devices and some devices do not report back due to lack of host networking in docker desktop for mac.

@alexandertsukanov @dro-ex Thanks for the comments.
@dro-ex That's a neat use case - unfortunately I don't think this tool will solve your problem. Assuming Home Assistant uses mDNS to discover devices, mDNS packets can't traverse layer 3 network boundaries, at least not without an mDNS reflector. I haven't been able to find any mac-based mDNS reflectors yet unfortunately.
FWIW, Rancher Desktop creates a layer 2 bridged network between macOS and the container VM (compared to a layer 3 network on Docker Desktop), which means protocols like mDNS are supported. This means that all you need to do is attach your container to a host or macvlan network to get access to your physical layer 2 LAN network.
I just tried tried this using --net=host and avahi-browser and successfully got a list of mDNS devices running on my network from inside the container:
$ docker run --net=host -it hsfeng/avahi-browse --all
...

Unless I am overlooking something, the above is not working with home assistant:
nerdctl run -d \            --name homeassistant \   --privileged \   -e TZ=TZ=America/Los_Angeles \   -v /Users/test/homeassistant/config:/config \   --net=host \       ghcr.io/home-assistant/home-assistant:stable
I am still getting "no devices on network"

@dro-ex I've never used Home Assistant before, but just gave it a quick try here. For me no devices were discovered at first, but then I realized that for me the default network interface picked by Home Assistant for discovery was wrong under Settings > System > Network. For me the correct interface for my LAN was rd0. After a restart all my devices started show up.
Let me know if that helps.

It's very strange - I am not getting any network settings in home assistant using Rancher Desktop - just a blank page - no errors.  It is working but no -net=hose access.  I've tried both nerdctl and docker as engines.  I am going to try some different things and see if I can the network settings to show up.

@dro-ex I had to set my profile to "Advanced Mode" to see the Network Settings. See:
https://www.home-assistant.io/integrations/network/
Was also getting a blank screen without that enabled.

Thank you!  It is indeed discovering local IoT devices - this is such good news.  Thank you!  I am now trying to learn wheat i need to to ditch portainer and docker desktop and recreate all the containers in rancher.  Thank you again!


./eosioc -v push action currency issue failed

root@ubuntu:~/eos/programs/eosioc# ./eosioc -v push action currency issue '{"to":"currency","quantity":"1000.0000 CUR"}' --permission currency@active
2741326ms thread-0   main.cpp:935                  operator()           ] Converting argument to binary...
2741483ms thread-0   main.cpp:1008                 main                 ] Failed with error: 13 St9exception: read_until: End of file
read_until: End of file:
{"server":"localhost","port":8888,"path":"/v1/chain/push_transaction","postdata":{"signatures":["EOSJxJcZPi9BvUWbxD4hKw5hpWizWhC3BTFTZDDYDp53aKPyEbZJmh7aX186K5EYfuBPPgCcsz9wkT1g7ekBud7fapLY2cLrh"],"compression":"none","data":"5ef3dc580000000000000000010000001e4d75af460000000000a53176010000001e4d75af4600000000a8ed3232180000001e4d75af4680969800000000000443555200000000"},"what":"read_until: End of file"}
thread-0  httpc.cpp:117 call

follow the instruction , then push action, it failed with "read_until: End of file"
and the eosiod core dump
the stack is:
Core was generated by `./eosiod'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f64beeb9aee in std::__cxx11::basic_string<char, std::char_traits, std::allocator >::_M_assign(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x00007f64beeb9aee in std::__cxx11::basic_string<char, std::char_traits, std::allocator >::_M_assign(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x00007f64beeb9ed9 in std::__cxx11::basic_string<char, std::char_traits, std::allocator >::operator=(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x000000000217883b in llvm::DataLayout::operator= (this=0x7ffdd9af5ba0, DL=...)
at /root/wasm-compiler/llvm/include/llvm/IR/DataLayout.h:200
#3  0x0000000002178705 in llvm::DataLayout::DataLayout (this=0x7ffdd9af5ba0, DL=...)
at /root/wasm-compiler/llvm/include/llvm/IR/DataLayout.h:196
#4  0x0000000002175810 in llvm::TargetMachine::createDataLayout (this=0x0)
at /root/wasm-compiler/llvm/include/llvm/Target/TargetMachine.h:124
#5  0x0000000002172f99 in LLVMJIT::JITUnit::compile (this=0x361c6e0, llvmModule=0x3529cf0)
at /root/eos/libraries/wasm-jit/Source/Runtime/LLVMJIT.cpp:556
#6  0x00000000021735fe in LLVMJIT::instantiateModule (module=..., moduleInstance=0x3502190)
at /root/eos/libraries/wasm-jit/Source/Runtime/LLVMJIT.cpp:616
#7  0x0000000002160913 in Runtime::instantiateModule(IR::Module const&, Runtime::ImportBindings&&) (module=...,
imports=<unknown type in /root/eos/programs/eosiod/eosiod, CU 0x1aa95ca, DIE 0x1aa9a4d>)
at /root/eos/libraries/wasm-jit/Source/Runtime/ModuleInstance.cpp:151
#8  0x0000000001edef27 in eosio::chain::wasm_cache_impl::fetch_entry(fc::sha256 const&, char const*, unsigned long)::{lambda()#1}::operator()() const (this=0x7ffdd9af6810) at /root/eos/libraries/chain/wasm_interface.cpp:229
#9  0x0000000001eded6e in eosio::chain::wasm_cache_impl::with_lock<eosio::chain::wasm_cache_impl::fetch_entry(fc::sha256 const&, char const*, unsigned long)::{lambda()#1}>(std::mutex&, eosio::chain::wasm_cache_impl::fetch_entry(fc::sha256 const&, char const*, unsigned long)::{lambda()#1}) (this=0x35003f0, l=..., f=...) at /root/eos/libraries/chain/wasm_interface.cpp:155
#10 0x0000000001edb25b in eosio::chain::wasm_cache_impl::fetch_entry (this=0x35003f0, code_id=...,
wasm_binary=0x7f647ecc9180 <error: Cannot access memory at address 0x7f647ecc9180>, wasm_binary_size=10241)
at /root/eos/libraries/chain/wasm_interface.cpp:209
#11 0x0000000001ed974f in eosio::chain::wasm_cache::checkout (this=0x34989d0, code_id=...,
wasm_binary=0x7f647ecc9180 <error: Cannot access memory at address 0x7f647ecc9180>, wasm_binary_size=10241)
at /root/eos/libraries/chain/wasm_interface.cpp:335
#12 0x0000000001f38b60 in eosio::chain::wasm_cache::checkout_scoped (this=0x34989d0, code_id=...,
wasm_binary=0x7f647ecc9180 <error: Cannot access memory at address 0x7f647ecc9180>, wasm_binary_size=10241)
at /root/eos/libraries/chain/include/eosio/chain/wasm_interface.hpp:83
#13 0x0000000001f317a8 in eosio::chain::apply_context::exec_one (this=0x7ffdd9af8230)
at /root/eos/libraries/chain/apply_context.cpp:24
#14 0x0000000001f349e8 in eosio::chain::apply_context::exec (this=0x7ffdd9af8230) at /root/eos/libraries/chain/apply_context.cpp:101
#15 0x0000000001c393f5 in eosio::chain::chain_controller::__apply_transaction (this=0x34985b8, meta=...)
at /root/eos/libraries/chain/chain_controller.cpp:1429
---Type  to continue, or q  to quit---
#16 0x0000000001c24efc in eosio::chain::chain_controller::_apply_transaction (this=0x34985b8, meta=...)
at /root/eos/libraries/chain/chain_controller.cpp:1455
#17 0x0000000001c23f1d in eosio::chain::chain_controller::_push_transaction(eosio::chain::transaction_metadata&&) (this=0x34985b8,
data=<unknown type in /root/eos/programs/eosiod/eosiod, CU 0x9862d8, DIE 0xcd91f1>)
at /root/eos/libraries/chain/chain_controller.cpp:317
#18 0x0000000001c23bca in eosio::chain::chain_controller::_push_transaction (this=0x34985b8, trx=...)
at /root/eos/libraries/chain/chain_controller.cpp:271

Currency contract is already deprecated. If you encounter similar problem with eosio.token, please open a new issue. I'm closing this issue. Thanks!


Send package versions as bundle metadata

Description

One of the main goals of the Bundle Metadata Upload work for the CC SteelArc team is to gather information on the packages and versions that constitute our customers' projects.
Utilizing the project's package.json, we will upload the dependencies and devDependencies as part of the bundle_metadata field of a Bundle's ssr_parameters
Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

Utilizing the preexisting getProjectPkg() function, access the package.json's dependencies and devDependencies fields
Add this data to ssr_parameters

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@bfeister Yup! This PR is focused on sending just the package versions


feat: add boost scope_exit

need skip url stability check
rework on #2938
closes #2938

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.scope_exit) have been updated in this PR. Please review the changes.

Thanks, @hofbi

You need a maintainer to add it, so feel free to ping one of us (we already subscribe to PRs though).


updating to support RGBA32F and EXT_color_buffer_float

I'm mostly creating this pull request for a place to discuss this issue/feature. How would I add EXT_color_buffer_float support? Even if this can't be merged into your branch, I need to fix it for my own project so I can debug.
I've added these changes, which prevent gl.FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors from being thrown on gl.checkFramebuffer().  However, I'm still getting the following errors:
const internalFormatInfo = textureInfo.getInternalFormatInfo(version.extras.format.internalFormat);

Uncaught TypeError: Cannot read property 'internalFormat' of undefined
    at TexturePreviewGenerator.draw (VM10542 TexturePreview.js:425)
    at SurfaceInspector.TextureView.inspector.updatePreview (TextureView.js:89)
    at SurfaceInspector.TextureView.inspector.setTexture (TextureView.js:117)
    at TextureView.setTexture (TextureView.js:734)
    at Tab.<anonymous> (TexturesTab.js:116)
    at EventSource.fire (EventSource.js:38)
    at LeftListing.selectValue (LeftListing.js:125)
    at HTMLDivElement.el.onclick (LeftListing.js:85)

and
if (!gl.getProgramParameter(program, gl.LINK_STATUS)) {
     gl.linkProgram(program);
}

Uncaught TypeError: Failed to execute 'getProgramParameter' on 'WebGL2RenderingContext': parameter 1 is not of type 'WebGLProgram'.
    at StateSnapshot.apply (StateSnapshot.js:290)
    at Frame.makeActive (Frame.js:395)
    at RedundancyChecker.run (RedundancyChecker.js:822)
    at TraceView.setFrame (TraceView.js:433)
    at Tab.<anonymous> (TraceTab.js:52)
    at EventSource.fire (EventSource.js:38)
    at LeftListing.selectValue (LeftListing.js:125)
    at Window.appendFrame (Window.js:355)
    at CaptureContext.captureCallback (HostUI.js:26)
    at stopCapturing (CaptureContext.js:58)

Dang, I don't remember the details
For the first error is it as simple as just adding the missing enums to the textureInfo stuff?

 LGTM

@greggman The changes in this commit fixed some problems, but those are still errors that result from running shaders with EXT_color_buffer_float


more tests

Tests for JsonAdaptedMeeting, Company & JobTitle

Codecov Report

Merging #256 (9e99861) into master (e9ee0fe) will increase coverage by 1.30%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #256      +/-   ##
============================================
+ Coverage     65.18%   66.48%   +1.30%
- Complexity      812      823      +11
============================================
  Files           119      119
  Lines          2760     2760
  Branches        341      341
============================================
+ Hits           1799     1835      +36
+ Misses          850      805      -45
- Partials        111      120       +9

Impacted Files
Coverage Δ

...u/address/storage/meeting/JsonAdaptedAttendee.java
36.36% <ø> (+36.36%)
:arrow_up:

...du/address/storage/meeting/JsonAdaptedMeeting.java
71.42% <ø> (+71.42%)
:arrow_up:

.../seedu/address/logic/parser/AddressBookParser.java

...edu/address/logic/parser/ContactDetailsParser.java

...ava/seedu/address/logic/parser/HomePageParser.java
72.72% <0.00%> (ø)

...address/logic/parser/ContactDetailsPageParser.java
42.85% <0.00%> (ø)

.../java/seedu/address/model/meeting/MeetingTime.java
90.90% <0.00%> (+3.03%)
:arrow_up:

src/main/java/seedu/address/model/person/Id.java
86.66% <0.00%> (+6.66%)
:arrow_up:

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 e9ee0fe...9e99861. Read the comment docs.


Add API to manually remove/unmount component in  cache

What problem does this feature solve?
When using vue-router to navigate in a larger SPA, keep-alive is a very nice way to keep views/components that are frequently visited in the cache. When the instance of the component are cached, one avoids time and energy to reload it into memory (especially GPU related assets, which otherwise would cause unnecessary loading delay for the user).
In other words, keep-alive helps building a snappy and smooth experience for the user.
However, this also means that the components that have been visited are adding up in the memory, and can also consume some CPU even if they are never to be visited again by the user.
One can argue that the "max" property can limit this, but, I think there can be many different reasons to control this manually instead. In our specific case, we would like to control this for performance reasons (based on frequency of times the component is visited, time since last visit, how time consuming is the component to load, memory consumption of the component, etc.).
Right now we have managed to fix this with a fork, where we expose the function pruneCacheEntry(key: CacheKey) in KeepAlive.ts, but it would have been much better if this was a part vue itself.
What does the proposed API look like?
<keep-alive ref="aliveKeeper">
</keep-alive>

...
this.$refs.aliveKeeper.removeFromCache(myVueComponent);

This has been discussed multiple times: https://github.com/vuejs/vue/issues/6259 https://github.com/vuejs/vue/issues/8028 https://github.com/vuejs/vue/issues/10487.
This is probably worth going through an RFC by comparing existing solutions with include, exclude and max

If include/exclude could match some unique feature of the instance (type or the instance itself), it might be sufficient, but I am not sure if that is a better solution than just explicitly remove an instance of a vue component from the cache.

Closed, tracking here https://github.com/vuejs/rfcs/pull/284

I used the following code, it seems ok:
      <router-view v-slot="{Component, route}">
        <keep-alive ref="keepAlive"><component :key="route.path" :is="Component" /></keep-alive>
      </router-view>

    onCloseTab(targetName) {
      const route = this.tabRoutes.find(route => targetName === route.params.f_id)
      this.$store.dispatch('removeTab', targetName)

      // 删除组件在keepalive里的cache，参考 pruneCacheEntry 这个方法的逻辑
      const key = route.path
      const keepAliveInstance = this.$refs.keepAlive.$
      const cache = keepAliveInstance.__v_cache
      const vnode = cache.get(key)
      if (vnode) {
        const renderer = keepAliveInstance.ctx.renderer
        let shapeFlag = vnode.shapeFlag
        if (shapeFlag & 256 /* COMPONENT_SHOULD_KEEP_ALIVE */) {
          shapeFlag -= 256 /* COMPONENT_SHOULD_KEEP_ALIVE */
        }
        if (shapeFlag & 512 /* COMPONENT_KEPT_ALIVE */) {
          shapeFlag -= 512 /* COMPONENT_KEPT_ALIVE */
        }
        vnode.shapeFlag = shapeFlag
        renderer.um(vnode, keepAliveInstance, keepAliveInstance.suspense)
        cache.delete(key)
      }
    }

@yuanjinyong  I did the similar trying before, but the __v_cache only exposed in develop mode, can not used in production.

Any update, hack or work around?
I'm trying to achieve something like this example, Where you can dynamically add, remove or change tabs components and there is no way to clear removed components cache.

I encountered the same issue when trying to implement tabs that share a same component. When a tab is closed by user, I would like to delete the cache of that particular instance only. Here is what I think would be the most elegant way to tackle this in Vue3.
Since KeepAlive takes include/exclude that accepts component names only, one of the most obvious solution to this problem is to wrap the shared component into an HOC that gives every instance a unique name. Here is my implementation:
const createUniqueComponent = (component) => {
  return markRaw(
    defineComponent({
      name: createUniqueId(), // any unique string generation method of your choice
      components: {
        uc: component
      },
      render() {
        return h(this.$.components.uc, null, this.$slots)
      }
    })
  )
}

Then, use it where you need to create the component instance, for example, in the router or a store. In my case, I am dynamically importing the component, so the code would look something like this:
tabs.push({
  ...
  page: createUniqueComponent(defineAsyncComponent(() => import('@/views/SomeTabPage')))
})

Finally, generate a computed property for use as the include prop for KeepAlive.
const keepAliveIncludes = computed(() => tabs.map((tab) => tab.page.name))

Now bind it to the include prop of your KeepAlive and enjoy the magic:
<KeepAlive :include="keepAliveIncludes">
  <component :is="tab.page">
</KeepAlive>


The demo is not working...

Showing loading message only: https://danbovey.uk/react-infinite-scroller/demo/

Console error:
[HTTP/1.1 401 Unauthorized 0ms]```

Yeah, this is still not working.
Probably an old soundcloud api key.


Add developer documentation

I want to make addons with this framework and need development documentation or wiki.
Also, if possible, could you add more optional fonts? Especially Chinese fonts.
Thank you.

This happens every time I press the esc button on my keyboard.
[gmod-xpgui-1.1.0] addons/gmod-xpgui-1.1.0/lua/xpgui/binding.lua:16: attempt to call method 'Close' (a nil value)
1. RemoveLast - addons/gmod-xpgui-1.1.0/lua/xpgui/binding.lua:16
2. v - addons/gmod-xpgui-1.1.0/lua/xpgui/binding.lua:32
3. unknown - lua/includes/modules/hook.lua:102

Adding DockMargin to buttons inside HorizontalScroller leads to overflow.

By the way, I have to make an independent version in order to add elements and fonts, but I will mark you as a developer.


SW-5607 Use rate-limited events for species notifications

Use RateLimitedEventPublisher to limit the rate of notifications about
participant project species list additions and changes, replacing the code that
scans for recent updates.
In addition to requiring less code, this improves the notification behavior:
previously, the code would defer notifying until at least 10 minutes had passed
since the last action on the species list, no matter how long that took. Now it
will send a notification the first time an action happens, followed by
notifications at most every 10 minutes if additional actions happen.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2416  👈
#2415
#2414
main

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

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Sep 16, 3:16 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


REST Client hangs if noContent response returned

From what I can tell its a valid thing to do, return a 204 no content response.
I'm also not 100% sure if its something wrong with the response or the rest client itself.  But whenever i hit an end point that returns a 204.  The rest client seems to just hang forever as though its still waiting for a response.
It you try it and it works, I am happy to assume its a problem at my end....

Related and duplicate reports: #93 #124 #158 #187 #191 .

The solutions to issues 93 and 124 work here. Remove the Content-Type header or set to some something other than application/json.


Add sme2 detection for aarch64

Add cpuinfo_has_arm_sme2 for aarch64.
Implemented using the values used here.
This also required changing the type of the variables used to store/pass the value of hwcap2 from uint32_t to uint64_t, since the flag for sme2 is at bit 37.

This is now good to go!


[GPoS] Update his valid stakes in validate action

(Close first, cause this behaviour does no effect to users)


[ENH] heterogeneous object/estimator should allow (name, estimator, other, ...) tuples

Currently, it is assumed that the collection of objects in heterogeneous estimators/objects is a parameter in the form of (name, estimator).
However, there are use cases where additional metadata is provided per estimator, e.g., sktime column ensembles, where additionally it is said whichcolumn the named estimator is applied to.
Therefore, we should think about whether, and if yes how, to extend the convention to (name, estimator, metadata, etc).
sktime currently has a relaxed version (added after factor out to skbase) with minimal changes where the logic takes 0th and 1st element from the tuple, but does not assume a length. E.g., name, est = tpl[0], tpl[1] instead of name,est = tpl and so on.
Also see discussion in https://github.com/sktime/skbase/pull/122

This is a feature which the PR https://github.com/sktime/skbase/pull/107 has.


Should REVERSE_CLIENT_ID be REVERSED_CLIENT_ID on website?

https://codelabs.flutter-io.cn/codelabs/google-photos-sharing/index.html#3

Good catch! Thanks, we have just updated the codelab.


BufWrite autocmd runs code from old saved version of file

In my .vimrc I have the following:
augroup test
  autocmd!

  " Run tests automatically when a file is saved
  autocmd BufWrite * if test#exists() |
    \   TestFile |
    \ endif
augroup END

Taken from the autocommands section of the readme - https://github.com/vim-test/vim-test#autocommands
With this code in place, vim-test runs the tests when I type :w in Vim's command line vim-tests runs the tests contained in the file, but the tests run are from a previously saved version of the file. The new changes that are being saved are not used in the test run.
Checking the issue tracker I do not see anyone else reporting this issue, but I've experienced it for some time. It occurs with Erlang, Elixir and Rust on my Ubuntu machine. Interestingly it does not occur on OSX. It's possible something else in my vimrc that is interfering with this plugin. Here is a link to my vimrc if anyone wants to take a look at it: https://github.com/Stratus3D/dotfiles/blob/master/vimrc#L502-L509

BufWrite commands are called before the buffer is written to the file. Have you tried a BufWritePost command as they are called after the file has been written?

@andrew-cybsafe it'd been a while since I investigated this issue, but I went back and updated my config so TestFile was called on BufWritePost and now everything is working! Not sure what I did wrong before, but it appears vim-test is working as expected. Thanks for your help!