fix: fix issues with native node fetch

This is an attempt to fix the issue highlighted in nuxt/nuxt#19245 and nuxt/nuxt#19245/issuecomment-1575671354.

I saw where the PR code was modified in Files changed,  I remember this issue antfu/vitesse-nuxt3, the issue error is still exists when I update with nuxi upgrage -f and the ofetch has update to v1.1.0.
I hope the information I provide can provide assistance for possible future repairs.

 ERROR  Failed to fetch web fonts                                                                                23:15:36

 ERROR  fetch failed (https://fonts.googleapis.com/css2?family=DM+Sans&family=DM+Serif+Display&family=DM+Mono&display=swap)                                  23:15:36

  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async $fetchRaw2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:215:14)
  at async Module.$fetch2 (/G:/repo/test/learn-X6/node_modules/.pnpm/ofetch@1.1.0/node_modules/ofetch/dist/shared/ofetch.d438bb6f.mjs:239:15)

I'm using Node v20 too, but it somehow works on my machine. Have you tried deleting node_modules, .nuxt, .output folders?

I have deleted node_modules, .nuxt, .output.
This error exist on Node v20 and v19, but v16 will be ok. So I still use v16 in the past few months due to the issue.

I used nvm to manage the nodejs version. I just upgraded  nvm  to the latest version 1.11.1 and then reinstalled nodejs. Amazingly, this error disappeared on node v20.3.0,  but still exists on v19.9.0.

This problem may already have been fixed by this pr nodejs/node#47732 since node v20.2.0


dbeaver multi monitor setup - washed out tables

I have a multi-monitor setup and I usually have dbeaver maximized on one window while I work on the other monitor.
But with the latest version of dbeaver, the tables open become washed out when I move my cursor onto another window on my other monitor, which makes it impossible to read the data.
How do I disable this feature?
I am using Ubuntu 18.10.

Could you post a screenshot?

there is no any updates almost a year,
@craigcarnell if an issue is still actual for you feel free to reopen the ticket or create a new one.


generate id automatically with type integer

is there a way to generate id automatically and the id column type is int?

@yeudit there isn’t. I suppose one could generate a UUID and then save its integer representation in an int column, but I see no reason not to just store it as a UUID in that case.
It’s not possible to have auto-incrementing integer columns in a distributed database like Cassandra, because that would require close coordination between all nodes, which would defeat the purpose of a masterless data store.


Overwritting dialog settings with payload

The nodes are set to allow the overwriting of the defined dialog values with msg properties.
This is the not the prefered way for node-red nodes which is where you can only send a msg property if the defined dialog value has been left unset (blank)
See https://groups.google.com/forum/#!topic/node-red/ZFca1eslzog

this logic was inherited from the original repository. I'll correct it.

this has been corrected in the latest version.


re-upload error chunk

Hi @MRdotB,
I have modified this code to support re-uploading error chunk

Hey thanks for the pull request. :+1:
Could you just put the code with xo linting.
I have a concern.
Can a upload retry fail for an infinite number of time ?
Maybe limit the retry to let's say 3-5 and after this throw the error to user will be a better behavior ?


ARROW-623: Fix segfault in repr of empty field

Small fix for not segfaulting when printing an empty field.

Can you open a JIRA and prefix the PR title with ARROW-XXX:?

Opened https://issues.apache.org/jira/browse/ARROW-623

Bottom line: the statement pyarrow.Field() is not supported for users -- it creates a malformed object. The class docstring should bear a warning like https://github.com/apache/arrow/blob/master/python/pyarrow/table.pyx#L323

Looks like the build stalled for some other reason. Merging, thanks!


Fixes to .md code to allow images to be displayed properly

:camera: Screenshots

:page_facing_up: Context
Problem with images not being displayed
:pencil: Changes
Described on screenshot :D
:paperclip: Related PR
none
:no_entry_sign: Breaking
nope
:hammer_and_wrench: How to test
just load the page and let's pray it works!
:stopwatch: Next steps
have breakfast hahaha

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@all-contributors please add @ricardoprins for doc


Change wide-separators and color properties for new Gtk versions

With new gtk version the Separator height has regressed
This patch check the new gtk version and if case its

= 3.16 the properties color, and -GtkWidget-wide-separators
changes to work values.

This is a regression.
Fixes #4902

Hum, disabling the wide separators isn't helping:

That is wayyy thinner than in the designs.
Plus, I should probs say that IMO, this bug should be WONTFIX.  Having the separators go full height is far more like the palette separators.  Keeping things the same is good :)

Yes, you're right.
Maybe we can keep it as 'WONTFIX' until we found a right solution.
Ignacio Rodríguez
SugarLabs at Facebook
https://www.facebook.com/pages/SugarLabs/187845102582
2015-10-11 0:32 GMT-03:00 Sam<EMAIL_ADDRESS>
Hum, disabling the wide separators isn't helping:
https://camo.githubusercontent.com/fce626a4e7fc71fbb2d1b139cea786393092b3be/68747470733a2f2f692e6779617a6f2e636f6d2f61353966663534613463386634653262336364313634383238663465326636332e706e67
That is wayyy thinner than in the designs.
Plus, I should probs say that IMO, this bug should be WONTFIX. Having the
separators go full height is far more like the palette separators. Keeping
things the same is good :)
—
Reply to this email directly or view it on GitHub
https://github.com/sugarlabs/sugar-artwork/pull/79#issuecomment-147151109
.


[ERROR] Amplify Stuck at Deploy Step (Updating edge config)

Hi. My deployment is currently stuck at the Deploy Step:
2020-11-29T19:00:24 [INFO]: Starting Deployment
2020-11-29T19:00:24 [INFO]: Updating Edge config
The weird thing is that it worked just fine earlier.
My app Id:
d3gpao1uvtwh19 (eu-west-1)
Created as a continuation to: https://github.com/aws-amplify/amplify-console/issues/1250
as requested by @litwicki
Thanks.

Issue is likely due to versions of Amplify ala https://github.com/aws-amplify/amplify-console/issues/1298
Downgrading to 4.32.0 helps the build and deployment succeed.


lead to crash when i'm in the workgroup

hello
when the computer in the workgroup ,after the installing, i change the pass and the system crash...
Is this tool  only applicable to windows ad domain?

Hi @cldog, the DLL was only tested on AD domain controllers, but because of the way that password filters work, it should work for local computers as well.  Can you give more details about how you configured it? Make sure you put a valid public key and exfiltration domain in the registry and that you are using the right bitness (32 or 64 depending on target system). If that still doesn't work, you can try building the DLL in debug mode and seeing the output of the log file in C:\Windows\Temp\logFile.txt. You can also compile the PoC project to run the password filter manually, allowing you to debug and test the behavior before it's used as an implant.
I hope this helps.


Revert "remove gifs"

Reverts pulumi/pulumi-hugo#2203 so we can get gifs back in the deployments blog

Can this be closed?

closing this, @EvanBoyle let us know if you still have concerns.


GitHub Action downloads the execution graph bundle

Could you run the smoke test before merging this? Thanks!!


Update to React 18?

Question
Do you plan to update the package to make it compatible with React 18? I'm currently using this in a project which has been upgraded to React 18, so have no option but to use the --force flag in production, which is undesirable. Can you please let me know if and when you plan to update this to React 18? Thanks!

I've also experienced the same problem. there is no other option other than --force

anyone tried this package?
https://github.com/tlundstrom/fad-react-bootstrap-table2

I found this package fad-react-bootstrap-table2 while looking for react 18 support. I tried to compare the source but there are a lot of changes.


Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Repository problems
Renovate tried to run on this repository, but found these problems.

WARN: Custom registries are not allowed for this datasource and will be ignored
WARN: Package lookup failures

Rate-Limited
These updates are currently rate-limited. Click on a checkbox below to force their creation now.

[ ] fix(deps): update github.com/kendru/darwin/go/depgraph digest to 4d1c7e9 [ci skip]
[ ] fix(deps): update github.com/nsmithuk/local-kms digest to e4d9425 [ci skip]
[ ] fix(deps): update github.com/syndtr/goleveldb digest to 126854a [ci skip]
[ ] fix(deps): update github.com/vishalkuo/bimap digest to a9fb9b5 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update golang.org/x/exp digest to 814bf88 [ci skip]
[ ] fix(deps): update google.golang.org/genproto/googleapis/api digest to df926f6 [ci skip]
[ ] chore(deps): update crytic/slither-action action to v0.3.1 [ci skip]
[ ] chore(deps): update dependency @types/chai-as-promised to v7.1.8 [ci skip]
[ ] chore(deps): update dependency @types/react to v18.2.59 [ci skip]
[ ] chore(deps): update dependency autoprefixer to v10.4.17 [ci skip]
[ ] chore(deps): update dependency concurrently to v8.2.2 [ci skip]
[ ] chore(deps): update dependency depcheck to v1.4.7 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-react to v7.33.2 [ci skip]
[ ] chore(deps): update dependency husky to v8.0.3 [ci skip]
[ ] chore(deps): update dependency postcss to v8.4.35 [ci skip]
[ ] chore(deps): update dependency postcss to v8.4.35 [ci skip]
[ ] chore(deps): update dependency typescript to v4.9.5 [ci skip]
[ ] chore(deps): update graphqlcodegenerator monorepo [ci skip] (@graphql-codegen/cli, @graphql-codegen/client-preset, @graphql-codegen/introspection)
[ ] chore(deps): update mariadb docker tag to v10.11.7 [ci skip]
[ ] chore(deps): update scribemd/docker-cache action to v0.3.7 [ci skip]
[ ] chore(deps): update yarn to v1.22.21 [ci skip]
[ ] fix(deps): update dependency @emotion/react to v11.11.3 [ci skip]
[ ] fix(deps): update dependency @headlessui/react to v1.7.18 [ci skip]
[ ] fix(deps): update dependency @popperjs/core to v2.11.8 [ci skip]
[ ] fix(deps): update dependency @reduxjs/toolkit to v1.9.7 [ci skip]
[ ] fix(deps): update dependency @tailwindcss/forms to v0.5.7 [ci skip]
[ ] fix(deps): update dependency @tailwindcss/typography to v0.5.10 [ci skip]
[ ] fix(deps): update dependency @wagmi/core to v1.4.13 [ci skip]
[ ] fix(deps): update dependency autoprefixer to v10.4.17 [ci skip]
[ ] fix(deps): update dependency dayjs to v1.11.10 [ci skip]
[ ] fix(deps): update dependency keccak to v3.0.4 [ci skip]
[ ] fix(deps): update dependency next to v13.5.6 [ci skip]
[ ] fix(deps): update dependency postcss to v8.4.35 [ci skip]
[ ] fix(deps): update dependency react-redux to v8.1.3 [ci skip]
[ ] fix(deps): update dependency react-spring to v9.7.3 [ci skip]
[ ] fix(deps): update dependency start-server-and-test to v2.0.3 [ci skip]
[ ] fix(deps): update dependency supertest to v6.3.4 [ci skip]
[ ] fix(deps): update dependency ts-jest to v29.1.2 [ci skip]
[ ] fix(deps): update dependency wagmi to v1.4.13 [ci skip]
[ ] fix(deps): update dependency yarn to v1.22.21 [ci skip]
[ ] fix(deps): update docusaurus monorepo to v2.4.3 [ci skip] (@docusaurus/core, @docusaurus/module-type-aliases, @docusaurus/preset-classic, @docusaurus/theme-live-codeblock)
[ ] fix(deps): update module cloud.google.com/go/kms to v1.15.7 [ci skip]
[ ] fix(deps): update module github.com/99designs/gqlgen to v0.17.44 [ci skip]
[ ] fix(deps): update module github.com/99designs/gqlgen to v0.17.44 [ci skip]
[ ] fix(deps): update module github.com/99designs/gqlgen to v0.17.44 [ci skip]
[ ] fix(deps): update module github.com/btcsuite/btcd/btcec/v2 to v2.3.2 [ci skip]
[ ] fix(deps): update module github.com/coinbase/rosetta-sdk-go to v0.8.4 [ci skip]
[ ] fix(deps): update module github.com/dgraph-io/ristretto to v0.1.1 [ci skip]
[ ] fix(deps): update module github.com/gartnera/gcloud to v0.0.19 [ci skip]
[ ] fix(deps): update module github.com/gorilla/websocket to v1.5.1 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/golang-lru/v2 to v2.0.7 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-provider-kubernetes to v1.13.4 [ci skip]
[ ] fix(deps): update module github.com/hedzr/log to v1.6.25 [ci skip]
[ ] fix(deps): update module github.com/mattn/go-isatty to v0.0.20 [ci skip]
[ ] fix(deps): update module github.com/migueleliasweb/go-github-mock to v0.0.23 [ci skip]
[ ] fix(deps): update module github.com/migueleliasweb/go-github-mock to v0.0.23 [ci skip]
[ ] fix(deps): update module github.com/miguelmota/go-ethereum-hdwallet to v0.1.2 [ci skip]
[ ] fix(deps): update module github.com/sirupsen/logrus to v1.9.3 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/services/rfq to v0.0.49 [ci skip]
[ ] fix(deps): update module github.com/thoas/go-funk to v0.9.3 [ci skip]
[ ] fix(deps): update module github.com/ugorji/go/codec to v1.2.12 [ci skip]
[ ] fix(deps): update module github.com/vburenin/ifacemaker to v1.2.1 [ci skip]
[ ] fix(deps): update module github.com/vektah/gqlparser/v2 to v2.5.11 [ci skip]
[ ] fix(deps): update module github.com/vektah/gqlparser/v2 to v2.5.11 [ci skip]
[ ] fix(deps): update module go.uber.org/automaxprocs to v1.5.3 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/mysql to v1.5.4 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/driver/sqlite to v1.5.5 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] fix(deps): update module gorm.io/gorm to v1.25.7 [ci skip]
[ ] chore(deps): update crazy-max/ghaction-import-gpg action to v5.4.0 [ci skip]
[ ] chore(deps): update dependency @babel/core to v7.23.9 [ci skip]
[ ] chore(deps): update dependency @babel/eslint-parser to v7.23.10 [ci skip]
[ ] chore(deps): update dependency @storybook/testing-library to ^0.2.0 [ci skip]
[ ] chore(deps): update dependency @testing-library/react to v14.2.1 [ci skip]
[ ] chore(deps): update dependency @typechain/ethers-v5 to v10.2.1 [ci skip]
[ ] chore(deps): update dependency chai to v4.4.1 [ci skip] (chai, @types/chai)
[ ] chore(deps): update dependency eslint to v8.57.0 [ci skip]
[ ] chore(deps): update dependency eslint to v8.57.0 [ci skip]
[ ] chore(deps): update dependency eslint-config-prettier to v8.10.0 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-import to v2.29.1 [ci skip]
[ ] chore(deps): update dependency hardhat to v2.20.1 [ci skip]
[ ] chore(deps): update dependency lint-staged to v11.2.6 [ci skip]
[ ] chore(deps): update dependency markdownlint to ^0.33.0 [ci skip]
[ ] chore(deps): update dependency markdownlint-cli2 to v0.12.1 [ci skip]
[ ] chore(deps): update dependency node to v16.20.2 [ci skip]
[ ] chore(deps): update dependency node to v16.20.2 [ci skip]
[ ] chore(deps): update dependency nodemon to v3.1.0 [ci skip]
[ ] chore(deps): update dependency prettier to v2.8.8 [ci skip]
[ ] chore(deps): update dependency prettier-plugin-solidity to v1.3.1 [ci skip]
[ ] chore(deps): update dependency prettier-plugin-solidity to v1.3.1 [ci skip]
[ ] chore(deps): update dependency prettier-plugin-solidity to v1.3.1 [ci skip]
[ ] chore(deps): update dependency size-limit to v8.2.6 [ci skip]
[ ] chore(deps): update dependency solhint to v3.6.2 [ci skip]
[ ] chore(deps): update dependency solhint-plugin-prettier to ^0.1.0 [ci skip]
[ ] chore(deps): update dependency solhint-plugin-prettier to v0.1.0 [ci skip]
[ ] chore(deps): update dependency tailwindcss to v3.4.1 [ci skip]
[ ] chore(deps): update dependency tslib to v2.6.2 [ci skip]
[ ] chore(deps): update dependency typechain to v8.3.2 [ci skip]
[ ] chore(deps): update dependency typedoc to ^0.25.0 [ci skip]
[ ] chore(deps): update dependency typedoc-plugin-markdown to v3.17.1 [ci skip]
[ ] chore(deps): update dependency typescript to v4.9.5 [ci skip]
[ ] chore(deps): update dependency typescript to v5.3.3 [ci skip]
[ ] chore(deps): update dependency webpack to v5.90.3 [ci skip]
[ ] chore(deps): update franzdiebold/github-env-vars-action action to v1.3.0 [ci skip]
[ ] chore(deps): update helm release clickhouse to v3.7.0 [ci skip]
[ ] chore(deps): update helm release jaeger to v0.74.1 [ci skip]
[ ] chore(deps): update helm release mysql to v9.22.0 [ci skip]
[ ] chore(deps): update helm release mysql to v9.22.0 [ci skip]
[ ] chore(deps): update helm release mysql to v9.22.0 [ci skip]
[ ] chore(deps): update helm release mysql to v9.22.0 [ci skip]
[ ] chore(deps): update helm/chart-releaser-action action to v1.6.0 [ci skip]
[ ] chore(deps): update helm/chart-testing-action action to v2.6.1 [ci skip]
[ ] chore(deps): update helm/kind-action action to v1.9.0 [ci skip]
[ ] chore(deps): update jaxxstorm/action-install-gh-release action to v1.11.0 [ci skip]
[ ] chore(deps): update jest monorepo to v29.7.0 [ci skip] (jest, jest-environment-jsdom)
[ ] chore(deps): update mathieudutour/github-tag-action action to v6.1 [ci skip]
[ ] chore(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] chore(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] chore(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] chore(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] chore(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] chore(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] chore(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] chore(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] chore(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] chore(deps): update module google.golang.org/api to v0.167.0 [ci skip]
[ ] chore(deps): update module k8s.io/kubectl to v0.29.2 [ci skip]
[ ] chore(deps): update node.js to v14.18.2 [ci skip]
[ ] chore(deps): update prom/prometheus docker tag to v2.50.1 [ci skip]
[ ] chore(deps): update rinchsan/renovate-config-validator action to v0.2.0 [ci skip]
[ ] chore(deps): update wandalen/wretry.action action to v1.4.5 [ci skip]
[ ] fix(deps): update aws-sdk-go-v2 monorepo [ci skip] (github.com/aws/aws-sdk-go-v2, github.com/aws/aws-sdk-go-v2/config, github.com/aws/aws-sdk-go-v2/service/kms)
[ ] fix(deps): update dependency @apollo/client to v3.9.5 [ci skip]
[ ] fix(deps): update dependency @babel/core to v7.23.9 [ci skip]
[ ] fix(deps): update dependency @changesets/cli to v2.27.1 [ci skip]
[ ] fix(deps): update dependency @cloudflare/next-on-pages to v1.9.0 [ci skip]
[ ] fix(deps): update dependency @depay/web3-mock to v14.17.0 [ci skip]
[ ] fix(deps): update dependency @ethersproject/address to v5.7.0 [ci skip]
[ ] fix(deps): update dependency @headlessui/react to v1.7.18 [ci skip]
[ ] fix(deps): update dependency @mui/material to v5.15.11 [ci skip]
[ ] fix(deps): update dependency @rainbow-me/rainbowkit to v1.3.6 [ci skip]
[ ] fix(deps): update dependency @reduxjs/toolkit to v2.2.1 [ci skip]
[ ] fix(deps): update dependency @rtk-query/graphql-request-base-query to v2.3.1 [ci skip]
[ ] fix(deps): update dependency @segment/analytics-next to v1.64.0 [ci skip]
[ ] fix(deps): update dependency @testing-library/jest-dom to v5.17.0 [ci skip]
[ ] fix(deps): update dependency @testing-library/react to v13.4.0 [ci skip]
[ ] fix(deps): update dependency @types/node to v18.19.18 [ci skip]
[ ] fix(deps): update dependency @vercel/analytics to v1.2.2 [ci skip]
[ ] fix(deps): update dependency @vercel/analytics to v1.2.2 [ci skip]
[ ] fix(deps): update dependency @visx/shape to v3.5.0 [ci skip]
[ ] fix(deps): update dependency babel-jest to v29.7.0 [ci skip]
[ ] fix(deps): update dependency chart.js to v3.9.1 [ci skip]
[ ] fix(deps): update dependency cypress to v13.6.6 [ci skip]
[ ] fix(deps): update dependency date-fns to v2.30.0 [ci skip]
[ ] fix(deps): update dependency dotenv to v16.4.5 [ci skip]
[ ] fix(deps): update dependency eslint to v8.57.0 [ci skip]
[ ] fix(deps): update dependency eslint-config-prettier to v8.10.0 [ci skip]
[ ] fix(deps): update dependency ethers to v6.11.1 [ci skip]
[ ] fix(deps): update dependency graphql to v16.8.1 [ci skip]
[ ] fix(deps): update dependency graphql to v16.8.1 [ci skip]
[ ] fix(deps): update dependency react-chartjs-2 to v4.3.1 [ci skip]
[ ] fix(deps): update dependency recharts to v2.12.1 [ci skip]
[ ] fix(deps): update dependency sharp to ^0.33.0 [ci skip]
[ ] fix(deps): update dependency solidity-coverage to v0.8.8 [ci skip]
[ ] fix(deps): update dependency tailwind-merge to v1.14.0 [ci skip]
[ ] fix(deps): update dependency tiny-invariant to v1.3.3 [ci skip]
[ ] fix(deps): update dependency ts-node to v10.9.2 [ci skip]
[ ] fix(deps): update dependency typescript to v5.3.3 [ci skip]
[ ] fix(deps): update dependency viem to v1.21.4 [ci skip]
[ ] fix(deps): update kubernetes packages to v0.29.2 [ci skip] (k8s.io/apiextensions-apiserver, k8s.io/apimachinery, k8s.io/client-go, k8s.io/kubectl)
[ ] fix(deps): update module cloud.google.com/go/bigtable to v1.21.0 [ci skip]
[ ] fix(deps): update module github.com/aws/smithy-go to v1.20.1 [ci skip]
[ ] fix(deps): update module github.com/aws/smithy-go to v1.20.1 [ci skip]
[ ] fix(deps): update module github.com/aws/smithy-go to v1.20.1 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/brianvoe/gofakeit/v6 to v6.28.0 [ci skip]
[ ] fix(deps): update module github.com/btcsuite/btcd to v0.24.0 [ci skip]
[ ] fix(deps): update module github.com/clickhouse/clickhouse-go/v2 to v2.20.0 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 [ci skip]
[ ] fix(deps): update module github.com/gin-contrib/cors to v1.5.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/google/uuid to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/googleapis/gax-go/v2 to v2.12.2 [ci skip]
[ ] fix(deps): update module github.com/grpc-ecosystem/grpc-gateway/v2 to v2.19.1 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/consul/sdk to v0.16.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/go-hclog to v1.6.2 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/go-plugin to v1.6.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/golang-lru to v0.6.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/golang-lru to v0.6.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-exec to v0.20.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-go to v0.22.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-go to v0.22.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-log to v0.9.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-mux to v0.15.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-sdk/v2 to v2.33.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-sdk/v2 to v2.33.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-sdk/v2 to v2.33.0 [ci skip]
[ ] fix(deps): update module github.com/hashicorp/terraform-plugin-sdk/v2 to v2.33.0 [ci skip]
[ ] fix(deps): update module github.com/hedzr/cmdr to v1.11.26 [ci skip]
[ ] fix(deps): update module github.com/invopop/jsonschema to v0.12.0 [ci skip]
[ ] fix(deps): update module github.com/jarcoal/httpmock to v1.3.1 [ci skip]
[ ] fix(deps): update module github.com/jarcoal/httpmock to v1.3.1 [ci skip]
[ ] fix(deps): update module github.com/jellydator/ttlcache/v3 to v3.2.0 [ci skip]
[ ] fix(deps): update module github.com/josephburnett/jd to v1.8.1 [ci skip]
[ ] fix(deps): update module github.com/lmittmann/w3 to v0.14.6 [ci skip]
[ ] fix(deps): update module github.com/lmittmann/w3 to v0.14.6 [ci skip]
[ ] fix(deps): update module github.com/lmittmann/w3 to v0.14.6 [ci skip]
[ ] fix(deps): update module github.com/lmittmann/w3 to v0.14.6 [ci skip]
[ ] fix(deps): update module github.com/lmittmann/w3 to v0.14.6 [ci skip]
[ ] fix(deps): update module github.com/otiai10/copy to v1.14.0 [ci skip]
[ ] fix(deps): update module github.com/prometheus/client_golang to v1.19.0 [ci skip]
[ ] fix(deps): update module github.com/prometheus/client_golang to v1.19.0 [ci skip]
[ ] fix(deps): update module github.com/puzpuzpuz/xsync to v1.5.2 [ci skip]
[ ] fix(deps): update module github.com/ravilushqa/otelgqlgen to v0.15.0 [ci skip]
[ ] fix(deps): update module github.com/ravilushqa/otelgqlgen to v0.15.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/richardwilkes/toolbox to v1.106.0 [ci skip]
[ ] fix(deps): update module github.com/sethvargo/go-githubactions to v1.2.0 [ci skip]
[ ] fix(deps): update module github.com/sethvargo/go-githubactions to v1.2.0 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/ethergo to v0.1.23 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/services/scribe to v0.1.26 [ci skip]
[ ] fix(deps): update module github.com/synapsecns/sanguine/services/scribe to v0.1.26 [ci skip]
[ ] fix(deps): update module github.com/uptrace/opentelemetry-go-extra/otelgorm to v0.2.3 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/urfave/cli/v2 to v2.27.1 [ci skip]
[ ] fix(deps): update module github.com/valyala/fasthttp to v1.52.0 [ci skip]
[ ] fix(deps): update module github.com/vektra/mockery/v2 to v2.42.0 [ci skip]
[ ] fix(deps): update module github.com/vektra/mockery/v2 to v2.42.0 [ci skip]
[ ] fix(deps): update module github.com/viant/toolbox to v0.34.5 [ci skip]
[ ] fix(deps): update module github.com/yamashou/gqlgenc to v0.19.2 [ci skip]
[ ] fix(deps): update module github.com/yamashou/gqlgenc to v0.19.2 [ci skip]
[ ] fix(deps): update module github.com/yamashou/gqlgenc to v0.19.2 [ci skip]
[ ] fix(deps): update module github.com/zclconf/go-cty to v1.14.2 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin to v0.49.0 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc to v0.49.0 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc to v0.49.0 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc to v0.49.0 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp to v0.49.0 [ci skip]
[ ] fix(deps): update module go.opentelemetry.io/contrib/propagators/b3 to v1.24.0 [ci skip]
[ ] fix(deps): update module go.uber.org/atomic to v1.11.0 [ci skip]
[ ] fix(deps): update module go.uber.org/atomic to v1.11.0 [ci skip]
[ ] fix(deps): update module go.uber.org/atomic to v1.11.0 [ci skip]
[ ] fix(deps): update module go.uber.org/zap to v1.27.0 [ci skip]
[ ] fix(deps): update module go.uber.org/zap to v1.27.0 [ci skip]
[ ] fix(deps): update module golang.org/x/mod to v0.15.0 [ci skip]
[ ] fix(deps): update module golang.org/x/mod to v0.15.0 [ci skip]
[ ] fix(deps): update module golang.org/x/mod to v0.15.0 [ci skip]
[ ] fix(deps): update module golang.org/x/mod to v0.15.0 [ci skip]
[ ] fix(deps): update module golang.org/x/net to v0.21.0 [ci skip]
[ ] fix(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] fix(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] fix(deps): update module golang.org/x/oauth2 to v0.17.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/sync to v0.6.0 [ci skip]
[ ] fix(deps): update module golang.org/x/time to v0.5.0 [ci skip]
[ ] fix(deps): update module golang.org/x/time to v0.5.0 [ci skip]
[ ] fix(deps): update module golang.org/x/tools to v0.18.0 [ci skip]
[ ] fix(deps): update module golang.org/x/tools to v0.18.0 [ci skip]
[ ] fix(deps): update module golang.org/x/tools to v0.18.0 [ci skip]
[ ] fix(deps): update module google.golang.org/api to v0.167.0 [ci skip]
[ ] fix(deps): update module google.golang.org/grpc to v1.62.0 [ci skip]
[ ] fix(deps): update module google.golang.org/grpc to v1.62.0 [ci skip]
[ ] fix(deps): update module google.golang.org/grpc to v1.62.0 [ci skip]
[ ] fix(deps): update module google.golang.org/grpc to v1.62.0 [ci skip]
[ ] fix(deps): update module google.golang.org/grpc to v1.62.0 [ci skip]
[ ] fix(deps): update module google.golang.org/protobuf to v1.32.0 [ci skip]
[ ] fix(deps): update module google.golang.org/protobuf to v1.32.0 [ci skip]
[ ] fix(deps): update module gorm.io/driver/clickhouse to v0.6.0 [ci skip]
[ ] fix(deps): update module k8s.io/apimachinery to v0.29.2 [ci skip]
[ ] fix(deps): update module k8s.io/apimachinery to v0.29.2 [ci skip]
[ ] fix(deps): update module k8s.io/apimachinery to v0.29.2 [ci skip]
[ ] fix(deps): update module k8s.io/apimachinery to v0.29.2 [ci skip]
[ ] fix(deps): update module k8s.io/apimachinery to v0.29.2 [ci skip]
[ ] fix(deps): update opentelemetry-go monorepo [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/exporters/otlp/otlptrace, go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc, go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/prometheus, go.opentelemetry.io/otel/metric, go.opentelemetry.io/otel/sdk, go.opentelemetry.io/otel/sdk/metric, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/sdk, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update opentelemetry-go monorepo to v1.24.0 [ci skip] (go.opentelemetry.io/otel, go.opentelemetry.io/otel/trace)
[ ] fix(deps): update react monorepo [ci skip] (@types/react, @types/react-dom)
[ ] chore(deps): update actions/cache action to v4 [ci skip]
[ ] chore(deps): update actions/github-script action to v7 [ci skip]
[ ] chore(deps): update actions/github-script action to v7 [ci skip]
[ ] chore(deps): update actions/github-script action to v7 [ci skip]
[ ] chore(deps): update actions/labeler action to v5 [ci skip]
[ ] chore(deps): update actions/setup-go action to v5 [ci skip]
[ ] chore(deps): update actions/setup-node action to v4 [ci skip]
[ ] chore(deps): update actions/setup-python action to v5 [ci skip]
[ ] chore(deps): update actions/stale action to v9 [ci skip]
[ ] chore(deps): update azure/setup-helm action to v4 [ci skip]
[ ] chore(deps): update crazy-max/ghaction-import-gpg action to v6 [ci skip]
[ ] chore(deps): update debian docker tag to v12 [ci skip]
[ ] chore(deps): update dependency @testing-library/jest-dom to v6 [ci skip]
[ ] chore(deps): update dependency @tsconfig/docusaurus to v2 [ci skip]
[ ] chore(deps): update dependency @typechain/ethers-v5 to v11 [ci skip]
[ ] chore(deps): update dependency @types/jest to v29 [ci skip]
[ ] chore(deps): update dependency babel-loader to v9 [ci skip]
[ ] chore(deps): update dependency chai to v5 [ci skip]
[ ] chore(deps): update dependency eslint-config-prettier to v9 [ci skip]
[ ] chore(deps): update dependency eslint-config-standard to v17 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-jsdoc to v48 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-prettier to v5 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-promise to v6 [ci skip]
[ ] chore(deps): update dependency eslint-plugin-unicorn to v51 [ci skip]
[ ] chore(deps): update dependency husky to v9 [ci skip]
[ ] chore(deps): update dependency image-minimizer-webpack-plugin to v4 [ci skip]
[ ] chore(deps): update dependency jest to v29 [ci skip]
[ ] chore(deps): update dependency lerna to v8 [ci skip]
[ ] <!-- unlimit-branch=renovate/lint-

See #16


hostapp-update-hooks: Add config.txt quirk for revpi-core-3

New balenaOS for revpi-core-3 will not boot if the config.txt
has an older dtoverlay=mmc entry.
Therefore we must add a hostapp update hook to remove this entry.
We name this quirk 9999-bootfiles to be sure it is run at the very
end so that no other hooks that may fail would run after it and as
such ending up rebooting in the older OS but with config.txt modified
by this quirk hook.
Changelog-entry: Add config.txt entry removal quirk for revpi-core-3
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

@resin-ci retest


Card sort exercise to inform Content Guide IA

[X] @joolswood to tweak cards in spreadsheet https://docs.google.com/spreadsheets/d/1i0lXqvZKbVauDqG5KwecBDPOwS6QoXFpojgkYOe3BeQ/edit#gid=0~~
[X] @maadonna will set it up the exercise.
[x] Confirm roles
[x] Draft release email

It's live!

Just looking for an update — can we close this card? :S

I'm doing analysis of results now - let's close it when I finish that

Card sort activity now completed! See results here: https://docs.google.com/spreadsheets/d/1i0lXqvZKbVauDqG5KwecBDPOwS6QoXFpojgkYOe3BeQ/edit#gid=372668572

@joolswood Could I ask you to give a brief summary on the results? :S

@klepas certainly. I'm hoping to go into it in depth with Content Clinic in 2 weeks' time but I can talk you through it before then.

@joolswood Keen to timebox a summary run-through to like 10–15mins or something. Lemme know when works for you? Happy to wait until we catch up in-person next week. (:

@klepas I'm happy to book in some time this arvo if the rest of the team are interested, otherwise have a chat Monday?


Lab 4 Level 3 Question on abstraction principle

Question: My KeyableMap class implements a put method that takes in a key-value pair of type V as mentioned in level 3 of Lab 4. As such, does creating put methods in other classes such as Course, Student and Roster that extends and overrides the put method in the KeyableMap class violate the abstraction principle ?
Clarifications: I ask this because implementing just the put method in the KeyableMap class alone returned me errors such as "KeyableMap cannot be converted to course" when i try to use the put function of adding courses to students and students to rosters.
Let me know if further clarification is needed

I am not too sure if it violates the abstraction principal but the problem lies within the generic class where the put method could only return a keyable type.
and in your course and student class, the return method for put would need to be course and student respectively.
and keyablemap is more general thatn course and thus cannot be converted.
the only way to solve this is to create overriding methods even though the code may be repeated.

no it does not break abstraction barrier because the idea is that you want to return a KeyableMap object after using put of which Course, Student, Roster are all subclasses of KeyableMaps

at level 3 what should the is put method signature look like? i know the return type is KeyableMap<V> but the parameter as type V gives me issues like OPs KeyableMap<Assessment> cannot be converted to course. also is KeyableMap<Course> a subtype of Student?

at level 3 what should the is put method signature look like? i know the return type is KeyableMap<V> but the parameter as type V gives me issues like OPs KeyableMap<Assessment> cannot be converted to course. also is KeyableMap<Course> a subtype of Student?
edit: i found out you were not suppose to abstract out the put method since the return type for each put method for each subclass is different

from the test cases u can see keyablemap is a course, keyablemap is a student, not the other way round (ie keyablemap is a subtype of student). to return a course, you might want to have a new constructor in course which calls the parent's constructor and copy the values of the key and immutablemap over.

at level 3 what should the is put method signature look like? i know the return type is KeyableMap<V> but the parameter as type V gives me issues like OPs KeyableMap<Assessment> cannot be converted to course. also is KeyableMap<Course> a subtype of Student?
edit: i found out you were not suppose to abstract out the put method since the return type for each put method for each subclass is different

from the test cases u can see keyablemap is a course, keyablemap is a student, not the other way round (ie keyablemap is a subtype of student). to return a course, you might want to have a new constructor in course which calls the parent's constructor and copy the values of the key and immutablemap over. this creates a new course with the updated immutable map.

do u mean that course is a keyablemap and student is a keyablemap ? also my understanding is that KeyableMap's put method takes in a V but when u put an assessment into a course, if u do not override the put method to return a new course but a keyablemap, this would cause problems when u try to put this "course" into the student as this "course" is a keyablemap rather than a course, and if u want to pass it into student's put as a course then u would have to explicitly typecast it to course
am i understanding it right? but actually why can i not just have student's put return a keyablemap<keyablemap> rather than a student

Hi Ian!  Adding put methods in classes like Course, Student, and Roster that tweak the put method from the KeyableMap class is totally fine and doesn't break the abstraction principle. This principle is all about keeping the nitty-gritty details hidden and offering a clear way to use things. In your situation, changing the put method in subclasses is a smart move to give a tailored implementation that suits each subclass, while still sticking to the overall idea of the put method from the KeyableMap class. As long as the new put methods keep the same overall vibe and purpose as the original, you're all good and keeping in line with the abstraction principle. Hope this helps!

hi im sure it will not violate the abstraction principle and you will definitely need to override the put method of your KeyableMap class in other classes so as to get the desired output

at level 3 what should the is put method signature look like? i know the return type is KeyableMap<V> but the parameter as type V gives me issues like OPs KeyableMap<Assessment> cannot be converted to course. also is KeyableMap<Course> a subtype of Student?
edit: i found out you were not suppose to abstract out the put method since the return type for each put method for each subclass is different

from the test cases u can see keyablemap is a course, keyablemap is a student, not the other way round (ie keyablemap is a subtype of student). to return a course, you might want to have a new constructor in course which calls the parent's constructor and copy the values of the key and immutablemap over. this creates a new course with the updated immutable map.

do u mean that course is a keyablemap(assessment) and student is a keyablemap(course) ? also my understanding is that KeyableMap's put method takes in a V but when u put an assessment into a course, if u do not override the put method to return a new course but a keyablemap(assessment), this would cause problems when u try to put this "course" into the student as this "course" is a keyablemap(assessment) rather than a course, and if u want to pass it into student's put as a course then u would have to explicitly typecast it to course
am i understanding it right? but actually why can i not just have student's put return a keyablemap(keyablemap(assessment)) rather than a student

yep, you will have to override the put methods in course and students to return a new course and student respectively. u cannot just have student's put return a keyablemap since we cant assign Student student = student.put(__) since keyablemap is not a student. (however, student is a keyablemap)

@iannntsw Since lab 4 is over for quite some time, mind if you close this issue? Thanks.


Failed to POST Large Result to DB/Catalog

Is this a request for help?:
 The error messages from the anchore-worker.log (shown below) indicates that the scan completes successfully but fails to record the result due to a Postgres DB error - 'invalid memory alloc request size<PHONE_NUMBER>'.
What did you expect to happen:
Expectation was for a successful result to be recorded for the scan.
Any relevant log output from /var/log/anchore:
anchore-worker.log
2021-10-18 16:24:31+0000 [-] [Thread-85] [anchore_engine.services.analyzer/perform_analyze_nodocker()] [INFO] performing analysis on image complete: <path-ecr/container-name@sha256:hash> 2021-10-18 16:24:31+0000 [-] [Thread-85] [anchore_engine.services.analyzer/process_analyzer_job()] [INFO] adding image analysis data to catalog: userid=admin imageId=<hash> imageDigest=<hash> 2021-10-18 16:24:42+0000 [-] "<IP_ADDRESS>" - - [18/Oct/2021:16:24:41 +0000] "GET /health HTTP/1.1" 200 5 "-" "curl/7.61.1" 2021-10-18 16:25:22+0000 [-] [Thread-85] [anchore_engine.clients.services.internal/dispatch()] [ERROR] Failed client call to service catalog for url: http://catalog:8228/v1/objects/analysis_data/<hash> Response: {'httpcode': 500, 'anchore_error_raw': 'b\'{\\n  "detail": {\\n    "error_codes": []\\n  },\\n  "httpcode": 500,\\n  "message": "(psycopg2.errors.InternalError_) invalid memory alloc request size<PHONE_NUMBER>\\\\n\\\\n[SQL: INSERT INTO archive_document (bucket, \\\\"archiveId\\\\", \\\\"userId\\\\", \\\\"documentName\\\\", created_at, last_updated, record_state_key, record_state_val, jsondata, b64_encoded) VALUES (%(bucket)s, %(archiveId)s, %(userId)s, %(documentName)s, %(created_at)s, %(last_updated)s, %(record_state_key)s, %(record_state_val)s, %(jsondata)s, %(b64_encoded)s)]\\\\n[parameters: {\\\'bucket\\\': \\\'analysis_data\\\', \\\'archiveId\\\': \\\’<hash>\\\’, \\\'userId\\\': \\\'admin\\\', \\\'documentName\\\': \\\’<hash>.json\\\’, \\\'created_at\\\':<PHONE_NUMBER>, \\\'last_updated\\\':<PHONE_NUMBER>, \\\'record_state_key\\\': \\\'active\\\', \\\'record_state_val\\\': None, \\\'jsondata\\\': \\\'{\\\\"document\\\\": [{\\\\"image\\\\": {\\\\"imageId\\\\": \\\\”<hash>\\\\”, \\\\"imagedata\\\\": {\\\\"analyzer_manifest\\\\": {}, \\\\"analy ... (775495736 characters truncated) ... <hash>\\\\”], \\\\"RepoTags\\\\": [\\\\"<path-ecr/container-name:tag>\\\\”]}}}}}]}\\\’, \\\'b64_encoded\\\': False}]\\\\n(Background on this error at: http://sqlalche.me/e/2j85)"\\n}\\n\'', 'anchore_error_json': {'detail': {'error_codes': []}, 'httpcode': 500, 'message': '(psycopg2.errors.InternalError_) invalid memory alloc request size<PHONE_NUMBER>\n\n[SQL: INSERT INTO archive_document (bucket, "archiveId", "userId", "documentName", created_at, last_updated, record_state_key, record_state_val, jsondata, b64_encoded) VALUES (%(bucket)s, %(archiveId)s, %(userId)s, %(documentName)s, %(created_at)s, %(last_updated)s, %(record_state_key)s, %(record_state_val)s, %(jsondata)s, %(b64_encoded)s)]\n[parameters: {\'bucket\': \'analysis_data\', \'archiveId\': \’<hash>\’, \'userId\': \'admin\', \'documentName\': \’<hash>.json\', \'created_at\':<PHONE_NUMBER>, \'last_updated\':<PHONE_NUMBER>, \'record_state_key\': \'active\', \'record_state_val\': None, \'jsondata\': \'{"document": [{"image": {"imageId": "<hash>”, "imagedata": {"analyzer_manifest": {}, "analy ... (775495736 characters truncated) ... <hash>”], "RepoTags": [“<path-ecr/container-name:tag>“]}}}}}]}\’, \'b64_encoded\': False}]\n(Background on this error at: http://sqlalche.me/e/2j85)'}} 2021-10-18 16:25:22+0000 [-] Traceback (most recent call last): 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/services/analyzer/__init__.py", line 145, in process_analyzer_job 2021-10-18 16:25:22+0000 [-]     rc = catalog_client.put_document('analysis_data', imageDigest, image_data) 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/clients/services/catalog.py", line 179, in put_document 2021-10-18 16:25:22+0000 [-]     return self.call_api(http.anchy_post, 'objects/{bucket}/{name}', path_params={'bucket': bucket, 'name': name}, body=json.dumps(payload)) 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/clients/services/internal.py", line 179, in call_api 2021-10-18 16:25:22+0000 [-]     return self.dispatch(base_url, method, path, path_params, query_params, extra_headers, body, connect_timeout, read_timeout, files) 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/clients/services/internal.py", line 237, in dispatch 2021-10-18 16:25:22+0000 [-]     raise e 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/clients/services/internal.py", line 234, in dispatch 2021-10-18 16:25:22+0000 [-]     return method(url=final_url, headers=request_headers, data=body, auth=auth, params=filtered_qry_params, verify=self.verify_ssl, files=files) 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/clients/services/http.py", line 269, in anchy_post 2021-10-18 16:25:22+0000 [-]     raise e 2021-10-18 16:25:22+0000 [-] Exception: failed post url=http://catalog:8228/v1/objects/analysis_data/<hash> 2021-10-18 16:25:22+0000 [-] 2021-10-18 16:25:22+0000 [-] During handling of the above exception, another exception occurred: 2021-10-18 16:25:22+0000 [-] 2021-10-18 16:25:22+0000 [-] Traceback (most recent call last): 2021-10-18 16:25:22+0000 [-]   File "/usr/local/lib/python3.6/site-packages/anchore_engine/services/analyzer/__init__.py", line 150, in process_analyzer_job 2021-10-18 16:25:22+0000 [-]     raise err 2021-10-18 16:25:22+0000 [-] anchore_engine.services.analyzer.CatalogClientError: Failed to upload analysis data to catalog - exception: failed post url=http://catalog:8228/v1/objects/analysis_data/<hash> 2021-10-18 16:25:22+0000 [-] [Thread-85] [anchore_engine.services.analyzer/process_analyzer_job()] [ERROR] problem analyzing image - exception: Failed to upload analysis data to catalog - exception: failed post url=http://catalog:8228/v1/objects/analysis_data/<hash>
What docker images are you using:

https://github.com/overleaf/overleaf

How to reproduce the issue:

Add large container (likely with a large number of vulnerabilities)

docker-compose exec api anchore-cli image wait path-to-ecr/container-name:tag

wait for analysis to complete
image fails to analyze and following error reported

Error: Requested image not found in system

Anything else we need to know:
Appears to be a known issue with Postgres accepting large number of rows/datasize within 1 field based upon searches of the error.

Hi @m4dsc1 we'll take a look. The insertion you're referring to is the save of the analysis document (a single large json object) into the db, so that size is a function of the amount of things found in an image.


get-objects --skip and --skip-hash options

Idea:

--skip to skip downloading a file if it already exists with the same filename
--skip-hash to skip downloading a file if it already exists AND the MD5 hash has not changed (more expensive as needs to calculate the local hash)

Originally posted by @simonw in https://github.com/simonw/s3-credentials/issues/78#issuecomment-1248398247

Can add this for put-objects too:

#68


I would like to know about the necessity of updating the kernel module in high kernel. Is there any detailed documentation?

What to document

https://falco.org/docs/install-operate/ plus run falco --version to see the compatible driver version.
In addition, if you upgrade the Falco userspace binary typically you also need to unload the old kernel module and reload a newer kernel module that is compatible. Similar procedure when upgrading your kernel as the kernel module has to be specifically compiled for your uname -r kernelrelease.

What I want to know may not be this. I want to know the necessity of kernel modules existing in higher versions.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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.


Having trouble with basic fadeIn transition

Great lib, but i just can't get it to work, even basic transition like fadeIn, its so frustrating.
What am i missing????
I've made an example,
https://aeroplancow.github.io/
Thanks in advance.

When i add Barba.Pjax.start();
then link doesn't work.

Ok watch
https://www.youtube.com/watch?v=EApR7BCzXCk
https://redstapler.co/barba-js-tutorial-add-transition-effect/

Best of luck!

Yeah, i tried that as well but then i get this kind of error.

solution:
run in through localhost


Add LTS versions for enterprises

Description of the new feature / enhancement

LTS = Long-term support

These versions would only include the toys and functions we consider stable. To ensure that, we should release such versions some weeks after the release of the normal version.
These versions could be released 4 times a year or less.
Maybe exclusivly tot his version we could include #14973
Scenario when this would be used?
Some enterprises are using PowerToys, even when it's only in a preview state. So when we add a version with long-term support, it would be much more secure for these enterprises to use these versions and other ones would feel secure to use it too.
Supporting information
A possible implementation to make it easier for the team to develop PowerToys, without having to maintain two versions we could just add a new build configuration and marking with pragma directives which parts should be built for the LTS version and which not.

Should be a work item after v1.0.

no plans for this as of now,


Black screen on SysNAND boot

part 5, aureiNAND, on Finalising setup step number 5 i reboot and i get nothing but a black screen. I can press L+R to get to decrypt9 and LRY for emunand9 but other than that nothing. I do the Black screen on SysNAND boot after injecting CTRNAND troubleshoot since that seems to be my issue but then i get an error: aurei/firmware(90).bin doesnt match this console, or its encrypted. im at an impasse at what to do.

Redownload and recopy the file.
This section is for issues, not troubleshooting.

is this not a damn issue? nowhere in your guide does it help with this or mention this happening at all

I will block you if you keep swearing at me.
There are more appropriate channels for troubleshooting, the github issues
section is for actual issues with the guide such as incorrect instructions
or typos
Your personal issues do not belong here, try asking on GBAtemp, Reddit,
IRC, messaging me, or even emailing me (my email is on my profile page).
On Fri, Mar 25, 2016, 10:49 PM ezgamerx<EMAIL_ADDRESS>wrote:

is this not a damn issue? nowhere in your guide does it help with this or
mention this happening at all
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/Plailect/Guide/issues/32#issuecomment-201688652


Dast Proxy Server URL Does not Exist

Please update ReadMe with new URL for Proxy Server. The below URL does not work.
https://github.com/hclproducts/appscan-automation-framework/blob/master/Extras/AppScan_Proxy_Server/DastProxyServerStandalone.1.1.403.zip

Need to add instructions for downloading proxy server, since it will not be hosted in this repo


No tsd.json file created with the project

The SharePoint Framework Yeoman generator doesn't create a tsd.json file with the typings required by the project. That file is required to correctly restore required typings after getting the project from the source control.

Internally, we checkin the typings directly to source control, which is why we are missing the tsd.json.
Also, there are typings which are not distributed via tsd in that folder (e.g. @ms/odsp.d.ts).
We didn't find much value in downloading the typings later, as effectively tsd.json records a commit number and then tsd install uses that to get the typings. If it is always the same typing (which it will be if the commit # doesn't change), why even bother? Why not just check it in?

Update: it is now recommended to use @types scoped packages for typings files. This is recorded as an entry in the package.json.


Algorithm for README.md

Algorithm for README.md

A hexadecimal sequence: seq.
Length of this hexadecimal sequence: L.
An index for a value in this hexadecimal sequence: idx

when I = J

Changes of r in arc(I)

i = from 0 to L-1
i = from L-1 to 0

Result paths (blue) derives from given circle (dashed line) and value changes along y axis (red).


Something with CircleCI

It's not using check suites, see what we can figure out.

I think I did this so now its using checks https://circleci.com/docs/2.0/build-processing/#getting-started


Running deployments of addons agents outside managed cluster

Signed-off-by: zhujian<EMAIL_ADDRESS>

@JustinKuli PTAL

/approve
/hold
hold for 24 hours for any further comment

/lgtm
/hold cancel


CronJobs not visible in the UI

Setup

Rancher version: v2.7.5
Rancher UI Extensions: N/A
Browser type & version: Chrome Version 116.0.5845.97

Describe the bug

After upgrading to Rancher v2.7.5 from v2.7.1, we are unable to view Cronjobs through the UI in our downstream cluster. The sidebar still shows the amount of CronJobs that we have our downstream cluster. When we go to the page via Workloads > CronJobs, we get the following message:

There are no rows to show.

We've looked into the developer tools and see a 500 Internal Server Error from the backend. The call is made to this url:
https://<cluster_url>/k8s/clusters/<cluster_id>/v1/batch.cronjobs
In the response of the only thing we can see is: EOF. We've also looked in the Rancher Pod logs, but there is no error message there. In the Ingress Controller logs, we only see the 500 returned by cattle-system-rancher-80.

To Reproduce

We are not sure how to reproduce. We have another Rancher instance running on the same version and CronJobs present, but this instance does not have the same issue.
Result
There are no CronJobs shown while there are in the downstream cluster. The monitoring links in the Rancher Monitoring UI are disabled.
Expected Result

The CronJobs should be displayed and the Monitoring links should be re-enabled.
Screenshots

Additional context

I've found https://github.com/rancher/dashboard/issues/9031 that looks like the same issue. But this was fixed by upgrading to v2.7.5.

This happened to me as well yesterday. Upgraded 2 clusters from kubernetes version 1.24.10 to 1.26.8. Rancher app version has not been changed, still on 2.7.6.
Cronjobs can not be listed anymore and we get a 500 Internal server error in the browser console. We can also not click any monitoring links, all unavailable.
So it seems this issue can occur by upgrading Rancher app or kubernetes version.

Our issue has gone away after upgrading Rancher to v2.7.9.

Just updated to 2.7.9 and our issues are also solved now.

Closing, this seems to have been fixed in or before 2.7.9


istioctl upgrade from 1.4.10 to 1.5.10 fails with "Asset charts/security/certmanager not found"

Bug description
I have a successful and functioning installation of Istio 1.4.10 running in KIND. It was created by way of istioctl (1.4.10) and personalized IstioControlPlane CRD.
I'm trying to upgrade to 1.5.10.
I get his error when running istioctl upgrade
2020-09-26T14:28:02.080363Z	info	Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

more details below...
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Successful upgrade from 1.4.10 to 1.5.10
Steps to reproduce the bug
Get your KIND cluster running with some nodes, I happen to have two nodes.
docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                                                                    NAMES
971f066271b8        kindest/node:v1.18.2   "/usr/local/bin/entr…"   8 minutes ago       Up 8 minutes                                                                                kind-worker
4de640966873        kindest/node:v1.18.2   "/usr/local/bin/entr…"   8 minutes ago       Up 8 minutes        <IP_ADDRESS>:8080->80/tcp, <IP_ADDRESS>:8443->443/tcp, <IP_ADDRESS>:34577->6443/tcp   kind-control-plane

I supply istioctl with an IstioControlPlane crd (as per documentation https://istio.io/v1.5/docs/setup/upgrade/istioctl-upgrade/#upgrade-steps which states if you installed istio with IstioControlPlane you should supply it to istioctl for upgrade )
If you installed Istio using the -f flag, for example istioctl manifest apply -f <IstioControlPlane-custom-resource-definition-file>, then you must provide the same -f flag value to the istioctl upgrade command.

I use this command...
~/Downloads/istio-1.5.10/bin/istioctl upgrade -f /depot/localkube/terraform/istio-manifest.yaml --force --log_output_level debug

the --force option is necessary as the istioctl upgrade command fails without it.
Prior to failure of upgade I am greeted with the following message.
user@user-lu:/depot/user/localkube$ ~/Downloads/istio-1.5.10/bin/istioctl upgrade -f /depot/user/localkube/terraform/istio-manifest.yaml --force --log_output_level debug
2020-09-26T14:26:23.220015Z	debug	Config loaded from file: /depot/user/localkube/kind/kubeconfig.yaml

proto: tag has too few fields: "-"
2020-09-26T14:26:23.255771Z	info	installer	ReadProfileYAML for profile name: default
2020-09-26T14:26:23.255902Z	info	installer	Loading values from compiled in VFS at path profiles/default.yaml
Control Plane - citadel pod - istio-citadel-5f4959969-wtpdv - version: 1.4.10
Control Plane - galley pod - istio-galley-6bcf8f95b9-crxbx - version: 1.4.10
Control Plane - pilot pod - istio-pilot-854cd475fb-tn2rp - version: 1.4.10
Control Plane - policy pod - istio-policy-7845546488-v9bz7 - version: 1.4.10
Control Plane - sidecar-injector pod - istio-sidecar-injector-797d656c8f-cxb96 - version: 1.4.10
Control Plane - telemetry pod - istio-telemetry-6b796d944d-k5rwh - version: 1.4.10

Upgrade version check passed: 1.4.10 -> 1.5.10.

2020-09-26T14:26:32.143431Z	info	installer	ReadProfileYAML for profile name: /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator/profiles/default.yaml
2020-09-26T14:26:32.143547Z	info	installer	Loading values from local filesystem at path /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator/profiles/default.yaml
Upgrade check: Warning!!! The following IOPS will be changed as part of upgrade. Please double check they are correct:
addonComponents:
  grafana:
    k8s: -> map[replicaCount:1]
  istiocoredns: -> map[enabled:false]
  kiali:
    enabled: false -> true
    k8s: -> map[replicaCount:1]
  prometheus:
    k8s: -> map[replicaCount:1]
  tracing:
    enabled: false -> true
components:
  base: -> map[enabled:true]
  egressGateways:
    '[#0]':
      k8s: map[hpaSpec:map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-egressgateway]] resources:map[limits:map[cpu:2000m memory:1024Mi]
        requests:map[cpu:100m memory:128Mi]] strategy:map[rollingUpdate:map[maxSurge:100%
        maxUnavailable:25%]]] ->
  ingressGateways:
    '[#0]':
      enabled: true -> false
      k8s: map[hpaSpec:map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-ingressgateway]] resources:map[limits:map[cpu:2000m memory:1024Mi]
        requests:map[cpu:100m memory:128Mi]] strategy:map[rollingUpdate:map[maxSurge:100%
        maxUnavailable:25%]]] ->
  pilot:
    k8s:
      env:
        '[?->0]': -> map[name:PILOT_ENABLE_FALLTHROUGH_ROUTE value:1]
        '[0->?]': map[name:POD_NAME valueFrom:map[fieldRef:map[apiVersion:v1 fieldPath:metadata.name]]]
          ->
        '[1->?]': map[name:POD_NAMESPACE valueFrom:map[fieldRef:map[apiVersion:v1
          fieldPath:metadata.namespace]]] ->
      hpaSpec: map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-pilot]] ->
      readinessProbe:
        periodSeconds: 30 -> 5
installPackagePath: /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator
  ->
values:
  certmanager: map[hub:quay.io/jetstack image:cert-manager-controller tag:v0.6.2]
    ->
  gateways:
    istio-egressgateway:
      env: map[ISTIO_META_ROUTER_MODE:sni-dnat] ->
      name: -> istio-egressgateway
      ports: '[map[name:http2 port:80] map[name:https port:443] map[name:tls port:15443
        targetPort:15443]] ->'
      zvpn: map[enabled:true suffix:global] ->
    istio-ingressgateway:
      env: map[ISTIO_META_ROUTER_MODE:sni-dnat] ->
      meshExpansionPorts:
        '[?->1]': -> map[name:tcp-istiod port:15012 targetPort:15012]
      name: -> istio-ingressgateway
      ports: '[map[name:status-port port:15020 targetPort:15020] map[name:http2 port:80
        targetPort:80] map[name:https port:443] map[name:kiali port:15029 targetPort:15029]
        map[name:prometheus port:15030 targetPort:15030] map[name:grafana port:15031
        targetPort:15031] map[name:tracing port:15032 targetPort:15032] map[name:tls
        port:15443 targetPort:15443]] ->'
      zvpn:
        enabled: true -> false
  global:
    istioNamespace: -> istio-system
    istiod: -> map[enabled:true]
    jwtPolicy: -> third-party-jwt
    mountMtlsCerts: -> false
    mtls:
      auto: false -> true
    pilotCertProvider: -> istiod
    sts: -> map[servicePort:0]
  grafana:
    image:
      tag: 6.4.3 -> 6.7.4
    replicaCount: 1 ->
  istiocoredns:
    enabled: false ->
  kiali:
    dashboard:
      grafanaInClusterURL: -> http://grafana:3000
      jaegerInClusterURL: -> http://tracing/jaeger
    replicaCount: 1 ->
  mixer:
    telemetry:
      useMCP: true ->
  pilot:
    ingress:
      ingressControllerMode: OFF -> STRICT
    useMCP: true ->
  prometheus:
    provisionPrometheusCert: -> true
    replicaCount: 1 ->
    tag: v2.12.0 -> v2.15.1
  security:
    trustDomain: cluster.local ->
  sidecarInjectorWebhook:
    rewriteAppHTTPProbe: false -> true
  telemetry:
    v1:
      enabled: true -> false
    v2:
      enabled: false -> true
  tracing:
    jaeger:
      tag: 1.14 -> 1.16

Confirm to proceed [y/N]? y
2020-09-26T14:28:01.700552Z	info	Running the following hooks which match source->target versions 1.4.10->1.5.10: istio.io/istio/operator/pkg/hooks.checkInitCrdJobs
2020-09-26T14:28:01.700636Z	info	Running hook istio.io/istio/operator/pkg/hooks.checkInitCrdJobs
2020-09-26T14:28:01.757251Z	info	installer	ReadProfileYAML for profile name: default
2020-09-26T14:28:01.757618Z	info	installer	Loading values from compiled in VFS at path profiles/default.yaml
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
2020-09-26T14:28:01.835151Z	info	installer	Applying Cluster specific settings: spec:
  values:
    global:
      jwtPolicy: first-party-jwt

2020-09-26T14:28:02.080363Z	info	Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
Istioctl binary for upgrade
1.5.10
Istioctl currently installed below:
./terraform/istio-1.4.10/bin/istioctl version
client version: 1.4.10
control plane version: 1.4.10
data plane version: 1.4.10 (1 proxies)

helm versions
helm version
version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"}

Kubectl Version
kubectl version --short
Client Version: v1.18.8

How was Istio installed?
./istio-1.4.10/bin/istioctl manifest apply -f ./istio-manifest.yaml -w --readiness-timeout 60s
the contents of that ./istio-manifest.yaml file are ...
apiVersion: install.istio.io/v1alpha2
kind: IstioControlPlane
metadata:
  creationTimestamp: null
spec:
  defaultNamespace: istio-system
  autoInjection:
    components:
      injector:
        enabled: true
    enabled: true
  configManagement:
    components:
      galley:
        enabled: true
    enabled: true
  gateways:
    components:
      egressGateway:
        enabled: false
      ingressGateway:
        enabled: false
    enabled: false
  policy:
    components:
      policy:
        enabled: true
    enabled: true
  security:
    components:
      certManager:
        enabled: false
      citadel:
        enabled: true
      nodeAgent:
        enabled: false
    enabled: true
  telemetry:
    components:
      telemetry:
        enabled: true
    enabled: true
  trafficManagement:
    components:
      pilot:
        enabled: true
        k8s:
          env:
            - name: PILOT_ENABLE_FALLTHROUGH_ROUTE
              value: "1"
    enabled: true
  values:
    global:
      proxy:
        accessLogFile: "/dev/stdout"
        accessLogEncoding: JSON
        envoyStatsd:
          enabled: false
        concurrency: 1
      useMCP: false
      outboundTrafficPolicy:
        mode: ALLOW_ANY
    pilot:
      sidecar: false
      traceSampling: 100
    prometheus:
      enabled: true
      retention: 7d
    tracing:
      enabled: true
    kiali:
      enabled: true
    grafana:
      enabled: false

Environment where bug was observed (cloud vendor, OS, etc)
Linux VM w/KIND installed
uname -a
Linux myworkstation-lu 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I tried downgrading helm from v3.3.4 to v2.14.3 and failed
helm version
Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}

and my istioctl output
2020-10-04T13:02:15.125216Z	debug	Config loaded from file: /depot/localkube/kind/kubeconfig.yaml

proto: tag has too few fields: "-"
2020-10-04T13:02:15.180864Z	info	installer	ReadProfileYAML for profile name: default
2020-10-04T13:02:15.180984Z	info	installer	Loading values from compiled in VFS at path profiles/default.yaml
Control Plane - citadel pod - istio-citadel-5f4959969-7zm57 - version: 1.4.10
Control Plane - galley pod - istio-galley-6bcf8f95b9-zzl6v - version: 1.4.10
Control Plane - pilot pod - istio-pilot-854cd475fb-mgg6f - version: 1.4.10
Control Plane - policy pod - istio-policy-7845546488-k9pgz - version: 1.4.10
Control Plane - sidecar-injector pod - istio-sidecar-injector-797d656c8f-2gmcg - version: 1.4.10
Control Plane - telemetry pod - istio-telemetry-6b796d944d-vl6nq - version: 1.4.10

Upgrade version check passed: 1.4.10 -> 1.5.10.

2020-10-04T13:02:32.674256Z	info	installer	ReadProfileYAML for profile name: /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator/profiles/default.yaml
2020-10-04T13:02:32.674365Z	info	installer	Loading values from local filesystem at path /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator/profiles/default.yaml
Upgrade check: Warning!!! The following IOPS will be changed as part of upgrade. Please double check they are correct:
addonComponents:
  grafana:
    k8s: -> map[replicaCount:1]
  istiocoredns: -> map[enabled:false]
  kiali:
    enabled: false -> true
    k8s: -> map[replicaCount:1]
  prometheus:
    k8s: -> map[replicaCount:1]
  tracing:
    enabled: false -> true
components:
  base: -> map[enabled:true]
  egressGateways:
    '[#0]':
      k8s: map[hpaSpec:map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-egressgateway]] resources:map[limits:map[cpu:2000m memory:1024Mi]
        requests:map[cpu:100m memory:128Mi]] strategy:map[rollingUpdate:map[maxSurge:100%
        maxUnavailable:25%]]] ->
  ingressGateways:
    '[#0]':
      enabled: true -> false
      k8s: map[hpaSpec:map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-ingressgateway]] resources:map[limits:map[cpu:2000m memory:1024Mi]
        requests:map[cpu:100m memory:128Mi]] strategy:map[rollingUpdate:map[maxSurge:100%
        maxUnavailable:25%]]] ->
  pilot:
    k8s:
      env:
        '[?->0]': -> map[name:PILOT_ENABLE_FALLTHROUGH_ROUTE value:1]
        '[0->?]': map[name:POD_NAME valueFrom:map[fieldRef:map[apiVersion:v1 fieldPath:metadata.name]]]
          ->
        '[1->?]': map[name:POD_NAMESPACE valueFrom:map[fieldRef:map[apiVersion:v1
          fieldPath:metadata.namespace]]] ->
      hpaSpec: map[maxReplicas:5 metrics:[map[resource:map[name:cpu targetAverageUtilization:80]
        type:Resource]] minReplicas:1 scaleTargetRef:map[apiVersion:apps/v1 kind:Deployment
        name:istio-pilot]] ->
      readinessProbe:
        periodSeconds: 30 -> 5
installPackagePath: /tmp/istio-install-packages/istio-1.4.10/install/kubernetes/operator
  ->
values:
  certmanager: map[hub:quay.io/jetstack image:cert-manager-controller tag:v0.6.2]
    ->
  gateways:
    istio-egressgateway:
      env: map[ISTIO_META_ROUTER_MODE:sni-dnat] ->
      name: -> istio-egressgateway
      ports: '[map[name:http2 port:80] map[name:https port:443] map[name:tls port:15443
        targetPort:15443]] ->'
      zvpn: map[enabled:true suffix:global] ->
    istio-ingressgateway:
      env: map[ISTIO_META_ROUTER_MODE:sni-dnat] ->
      meshExpansionPorts:
        '[?->1]': -> map[name:tcp-istiod port:15012 targetPort:15012]
      name: -> istio-ingressgateway
      ports: '[map[name:status-port port:15020 targetPort:15020] map[name:http2 port:80
        targetPort:80] map[name:https port:443] map[name:kiali port:15029 targetPort:15029]
        map[name:prometheus port:15030 targetPort:15030] map[name:grafana port:15031
        targetPort:15031] map[name:tracing port:15032 targetPort:15032] map[name:tls
        port:15443 targetPort:15443]] ->'
      zvpn:
        enabled: true -> false
  global:
    istioNamespace: -> istio-system
    istiod: -> map[enabled:true]
    jwtPolicy: -> third-party-jwt
    mountMtlsCerts: -> false
    mtls:
      auto: false -> true
    pilotCertProvider: -> istiod
    sts: -> map[servicePort:0]
  grafana:
    image:
      tag: 6.4.3 -> 6.7.4
    replicaCount: 1 ->
  istiocoredns:
    enabled: false ->
  kiali:
    dashboard:
      grafanaInClusterURL: -> http://grafana:3000
      jaegerInClusterURL: -> http://tracing/jaeger
    replicaCount: 1 ->
  mixer:
    telemetry:
      useMCP: true ->
  pilot:
    ingress:
      ingressControllerMode: OFF -> STRICT
    useMCP: true ->
  prometheus:
    provisionPrometheusCert: -> true
    replicaCount: 1 ->
    tag: v2.12.0 -> v2.15.1
  security:
    trustDomain: cluster.local ->
  sidecarInjectorWebhook:
    rewriteAppHTTPProbe: false -> true
  telemetry:
    v1:
      enabled: true -> false
    v2:
      enabled: false -> true
  tracing:
    jaeger:
      tag: 1.14 -> 1.16

Confirm to proceed [y/N]? y
2020-10-04T13:03:27.113960Z	info	Running the following hooks which match source->target versions 1.4.10->1.5.10: istio.io/istio/operator/pkg/hooks.checkInitCrdJobs
2020-10-04T13:03:27.114102Z	info	Running hook istio.io/istio/operator/pkg/hooks.checkInitCrdJobs
2020-10-04T13:03:27.190443Z	info	installer	ReadProfileYAML for profile name: default
2020-10-04T13:03:27.190931Z	info	installer	Loading values from compiled in VFS at path profiles/default.yaml
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
2020-10-04T13:03:27.286777Z	info	installer	Applying Cluster specific settings: spec:
  values:
    global:
      jwtPolicy: first-party-jwt

2020-10-04T13:03:27.509659Z	info	Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

Error: failed to apply the Istio Control Plane specs. Error: failed to generate manifest: Asset charts/security/certmanager not found

@howardjohn thank you. That got me past that issue. Looks like I'm getting further into the upgrade with new errors but I will research that separately.


address component showBoth prop

Description:
Fixes #915, but instead of keeping it default we enable it with showBoth prop (We can go with it being default too!, I am completely 50 50 on it so both seems good solution)

Test code :

"use client";

import type { NextPage } from "next";
import { Address } from "~~/components/scaffold-eth";

const Home: NextPage = () => {
  const demoAddress = "0x34aA3F359A9D614239015126635CE7732c18fDF3";

  return (
    <>

Address Component Showcase

Without showBoth

Size: xs

                  <Address size="xs" address={demoAddress} />

Size: sm

                  <Address size="sm" address={demoAddress} />

Size: base(default)

                  <Address size="base" address={demoAddress} />

Size: lg

                  <Address size="lg" address={demoAddress} />

Size: xl

                  <Address size="xl" address={demoAddress} />

Size: 2xl

                  <Address size="2xl" address={demoAddress} />

Size: 3xl

                  <Address size="3xl" address={demoAddress} />

With showBoth

Size: xs(default)

                  <Address size="xs" address={demoAddress} showBoth />

Size: sm

                  <Address size="sm" address={demoAddress} showBoth />

Size: base

                  <Address size="base" address={demoAddress} showBoth />

Size: lg

                  <Address size="lg" address={demoAddress} showBoth />

Size: xl

                  <Address size="xl" address={demoAddress} showBoth />

Size: 2xl

                  <Address size="2xl" address={demoAddress} showBoth />

Size: 3xl

                  <Address size="3xl" address={demoAddress} showBoth />

    </>
  );
};

export default Home;

// dynamic: --------------------------
/* const Home: NextPage = () => {
  const demoAddress = "0x34aA3F359A9D614239015126635CE7732c18fDF3";
  const sizes: ("xs" | "sm" | "base" | "lg" | "xl" | "2xl" | "3xl")[] = ["xs", "sm", "base", "lg", "xl", "2xl", "3xl"];

  return (
    <>

Address Component Showcase

Without showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} />

                ))}

With showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} showBoth />

                ))}

    </>
  );
};

export default Home; */

Also fixed the size of Copy Icon not being displayed properly in our original address component:

Main branch
this branch

Notice in this branch the size of copyIcon is responsive with respect to text size as compared to main branch

And one more nit: when loading with showBoth option component jumps a bit. It will cause to jump everything beyond the component. See also: https://web.dev/articles/cls

Yeah I wan't sure how best we could fix the layout shift, but I added currently the skeleton for now :
https://github.com/user-attachments/assets/c5c7fa2f-0c70-495c-804f-4b111afb988d
So if the address has ENS we show skeleton until fetching and then ens name instead of it. But if the ENS name is not present we fallback to normal address component(without showBoth)

Good changes, thanks!
Updated a bit:

added 4xl size, so font-size on showBoth 3xl differs from showBoth 2xl
added possibility to use format="long" with showBoth
removed old useEffects which caused small jump

https://github.com/user-attachments/assets/67668bef-c255-4d6c-8cf3-6c179d9317bd

Yeah I wan't sure how best we could fix the layout shift, but I added currently the skeleton for now :
So if the address has ENS we show skeleton until fetching and then ens name instead of it. But if the ENS name is not present we fallback to normal address component(without showBoth)

I think it's a good solution! I thought about something like fixing height of component, but it will add empty space around, when showBoth is false. So I thing it's ok for now

Updated a bit:

added 4xl size, so font-size on showBoth 3xl differs from showBoth 2xl
added possibility to use format="long" with showBoth
removed old useEffects which caused small jump

Thanks @rin-st makes sense!

This looks great @technophile-04 !! <3
The only thing that does not quite convince me is the showBoth prop. It's a bit vague. Not a big deal, but let me open some options:

hideAddress - hideAddressIfEns /  showAddress or showAddressIfEns: depending on the default.
full / compact: depending on the default. We already have the long / short so it might be a bit confusing (I've never used the long format btw)

IDK, just throwing it out there..... Happy to merge as it's too.

This looks great @technophile-04 !! <3
The only thing that does not quite convince me is the showBoth prop. It's a bit vague. Not a big deal, but let me open some options:

hideAddress - hideAddressIfEns /  showAddress or showAddressIfEns: depending on the default.
full / compact: depending on the default. We already have the long / short so it might be a bit confusing (I've never used the long format btw)

IDK, just throwing it out there..... Happy to merge as it's too.

Maybe something more explicit like showAddressAndEns?

This looks great @technophile-04 !! <3
The only thing that does not quite convince me is the showBoth prop. It's a bit vague. Not a big deal, but let me open some options:

hideAddress - hideAddressIfEns /  showAddress or showAddressIfEns: depending on the default.
full / compact: depending on the default. We already have the long / short so it might be a bit confusing (I've never used the long format btw)

IDK, just throwing it out there..... Happy to merge as it's too.

hmm, #915 title says that both should be shown by default.
So I think hideAddressIfEns is a good option

Just pushed a changes removing showBoth prop and now using onlyEnsOrAddress. Hence now showing ENS + Address as default.
When you pass onlyEnsOrAddress we get the same behaviour as current main brach.
Here is the behaviour for default thing <Address address={demoAddress} />

This will show all three things (loading skeleton as placeholder for ENS name while loading)
If there is not ENS for that address then it fallbacks only blockie with address (same size as main branch)

Case 1 demo address as has ENS :

https://github.com/user-attachments/assets/fe1d2181-fdbf-468a-a69b-9b6e77564c80

Case 2 Demo :

Now here there will be a layout shift. The layout won't be that much visible if you don't pass any styles. But if you pass higher sizes then layout shift is more visible since when 3 three things are shown we want to scale blockie to 4th step and when no ens is present we want to decrease it size.
https://github.com/user-attachments/assets/70f99e7c-0203-40d7-9d6f-883a29e89be8

here is example test code :

"use client";

import type { NextPage } from "next";
import { Address } from "~~/components/scaffold-eth";

const Home: NextPage = () => {
  // address without ENS
  // const demoAddress = "0x4e123738A66427ee9BD0C9dc67C09af397A7D93e";

  // atg.eth address
  const demoAddress = "0x34aA3F359A9D614239015126635CE7732c18fDF3";

  return (
    <>

Address Component Showcase

              <Address address={demoAddress} />

Only Address or ENS

Size: xs

                  <Address size="xs" address={demoAddress} onlyEnsOrAddress />

Size: sm

                  <Address size="sm" address={demoAddress} onlyEnsOrAddress />

Size: base(default)

                  <Address size="base" address={demoAddress} onlyEnsOrAddress />

Size: lg

                  <Address size="lg" address={demoAddress} onlyEnsOrAddress />

Size: xl

                  <Address size="xl" address={demoAddress} onlyEnsOrAddress />

Size: 2xl

                  <Address size="2xl" address={demoAddress} onlyEnsOrAddress />

Size: 3xl

                  <Address size="3xl" address={demoAddress} onlyEnsOrAddress />

Default Address Behaviour

Size: xs(default)

                  <Address size="xs" address={demoAddress} />

Size: sm

                  <Address size="sm" address={demoAddress} />

Size: base

                  <Address size="base" address={demoAddress} />

Size: lg

                  <Address size="lg" address={demoAddress} />

Size: xl

                  <Address size="xl" address={demoAddress} />

Size: 2xl

                  <Address size="2xl" address={demoAddress} />

Size: 3xl

                  <Address size="3xl" address={demoAddress} />

    </>
  );
};

export default Home;

// dynamic: --------------------------
/* const Home: NextPage = () => {
  const demoAddress = "0x34aA3F359A9D614239015126635CE7732c18fDF3";
  const sizes: ("xs" | "sm" | "base" | "lg" | "xl" | "2xl" | "3xl")[] = ["xs", "sm", "base", "lg", "xl", "2xl", "3xl"];

  return (
    <>

Address Component Showcase

Without showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} />

                ))}

With showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} showBoth />

                ))}

    </>
  );
};

export default Home; */

Great, thanks!
One more nit: after 8df4dbc Address component without size prop (default) has different font-sizes for address when loading and when loaded, but if size is passed it has same font-size. As I understand we need to decrease font-size everywhere when loading or not decrease at all
https://github.com/user-attachments/assets/d2763f6a-b812-49e8-86ff-820fe96dad5e

One more nit: after 8df4dbc Address component without size prop (default) has different font-sizes for address when loading and when loaded, but if size is passed it has same font-size. As I understand we need to decrease font-size everywhere when loading or not decrease at all

I played with it (a lot) and as I understand we have two options.

Use the same address font size with onlyEnsOrAddress prop and without it.

Pros: Readable text
Cons: Big layout shift, big height difference between components with the same size but with different onlyEnsOrAddress prop

https://github.com/user-attachments/assets/d5277d95-e34a-4bf9-84e3-73bc71a2383e

Use smaller address size without onlyEnsOrAddress or when loading if no ens.

Pros: Smaller layout shift; smaller height difference between components with the same size but with different onlyEnsOrAddress prop, so it looks better on loading
Cons: small font-size on size="xs", and even size="sm" when showing both address and ens(or skeleton). Notable layout shift on size="xs" and size="sm"

https://github.com/user-attachments/assets/5594adee-d840-4654-a64b-af14a45f4884
Both cases uses default size="base", so default component behaves the same as with size="base"
Pushed the second option since I think it looks better but feel free to update/revert if needed

Thanks @rin-st, yup option 2 makes a lot of sense to me and feels intuitive, Also mostly people will be using default Address component without passing any size in most cases so looks good in that and its getting freaking messier and messier as we try to make it very very perfect but it looks great now I feel!! Lol yesterday in flight I was trying to solve it and came up with https://github.com/scaffold-eth/scaffold-eth-2/pull/942 but your solution looks more robust and works great!!
Just pushed a commit updating the loading state when address is undefined inline with new styles.

Before :

https://github.com/user-attachments/assets/cc6643c5-85ec-47a3-b429-8647cbcf82b9

After :

https://github.com/user-attachments/assets/d59b31ce-e3fd-456a-b24d-d4a35db1bcf3

cc @carletex for his final thoughts once! But looks good to me!

Thanks all for the detailed display testing and exploring this!
I really like how it looks :+1:

Just pushed a commit updating the loading state when address is undefined inline with new styles.

Good point! Completely forgot about this state.
Noticed that height of the component is different when loading and when address, so we have two jumps when loading in this case:
https://github.com/user-attachments/assets/f83621ff-4e7a-4643-915e-5a24fc7c6224
Or one when we have ens:
https://github.com/user-attachments/assets/e61d4801-7db0-444b-880e-780141534df0
First thought is to make gap between items 1px, so second jump will not be so noticeable. But it looks not so good on large sizes. I didn't push this change, feel free to update if you think it's better than current.
https://github.com/user-attachments/assets/17dd88e2-0577-492c-9ebd-dfaa4c5d670a
Also, noticed that loading of components with onlyEnsOrAddress has a larger height
https://github.com/user-attachments/assets/ed686b01-9004-4817-8615-939ca52697cb

Also, noticed that loading of components with onlyEnsOrAddress has a larger height

Fixed this
https://github.com/user-attachments/assets/e021c3b8-ff62-4ef8-a94e-039786e02b28
Page code

"use client";

import { useEffect, useState } from "react";
import type { NextPage } from "next";
import { Address } from "~~/components/scaffold-eth";

const Home: NextPage = () => {
  const [demoAddress, setDemoAddress] = useState<string | undefined>(undefined);
  const [demoAddressEns, setDemoAddressEns] = useState<string | undefined>(undefined);

  useEffect(() => {
    const timer = setTimeout(() => {
      setDemoAddress("0x4e123738A66427ee9BD0C9dc67C09af397A7D93e");
      setDemoAddressEns("0x34aA3F359A9D614239015126635CE7732c18fDF3");
    }, 2_000);

    return () => clearTimeout(timer);
  }, []);

  return (
    <>

Address Component Showcase

Only Address or ENS

Size: xs

                  <Address size="xs" address={demoAddress} onlyEnsOrAddress />

Size: sm

                  <Address size="sm" address={demoAddress} onlyEnsOrAddress />

Size: base(default)

                  <Address size="base" address={demoAddress} onlyEnsOrAddress />

Size: lg

                  <Address size="lg" address={demoAddress} onlyEnsOrAddress />

Size: xl

                  <Address size="xl" address={demoAddress} onlyEnsOrAddress />

Size: 2xl

                  <Address size="2xl" address={demoAddress} onlyEnsOrAddress />

Size: 3xl

                  <Address size="3xl" address={demoAddress} onlyEnsOrAddress />

Default Address Behaviour

Size: xs

                  <Address size="xs" address={demoAddress} />

Size: sm

                  <Address size="sm" address={demoAddress} />

Size: base (default)

                  <Address size="base" address={demoAddress} />

Size: lg

                  <Address size="lg" address={demoAddress} />

Size: xl

                  <Address size="xl" address={demoAddress} />

Size: 2xl

                  <Address size="2xl" address={demoAddress} />

Size: 3xl

                  <Address size="3xl" address={demoAddress} />

Default Address Behaviour (with ens)

Size: xs

                  <Address size="xs" address={demoAddressEns} />

Size: sm

                  <Address size="sm" address={demoAddressEns} />

Size: base (default)

                  <Address size="base" address={demoAddressEns} />

Size: lg

                  <Address size="lg" address={demoAddressEns} />

Size: xl

                  <Address size="xl" address={demoAddressEns} />

Size: 2xl

                  <Address size="2xl" address={demoAddressEns} />

Size: 3xl

                  <Address size="3xl" address={demoAddressEns} />

    </>
  );
};

export default Home;

// dynamic: --------------------------
/* const Home: NextPage = () => {
  const demoAddress = "0x34aA3F359A9D614239015126635CE7732c18fDF3";
  const sizes: ("xs" | "sm" | "base" | "lg" | "xl" | "2xl" | "3xl")[] = ["xs", "sm", "base", "lg", "xl", "2xl", "3xl"];

  return (
    <>

Address Component Showcase

Without showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} />

                ))}

With showBoth

                {sizes.map(size => (

Size: {size}

                    <Address size={size} address={demoAddress} showBoth />

                ))}

    </>
  );
};

export default Home; */

Tysm @rin-st!! Make sense!

Merging this 🙌


VMLaunch Mods #2

This patch includes updates to support the hyperkernel as well
as keep EPT inline with Bareflank's CR3 implementation. This also
goes hand in hand with the vmlaunch mods that were made in
Bareflank
Signed-off-by: “Rian<EMAIL_ADDRESS>

Codecov Report

Merging #14 into master will not impact coverage.

@@          Coverage Diff          @@
##           master    #14   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          33     33
  Lines        2353   2353
  Branches       60     60
=====================================
  Hits         2353   2353

Impacted Files
Coverage Δ

src/vmcs/test/test_vmcs_intel_x64_eapis.cpp
100% <ø> (ø)
:white_check_mark:

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 dd31d66...18337a1. Read the comment docs.