chore(remix-dev): mute spurious warnings when using Yarn

When running yarn dev in some setups (e.g. in my case, when using Deno Deploy, but (if memory serves me well) not when using Remix  App Server), the following warnings are shown right after Building Remix app in development mode...:
The path "@remix-run/deno" is imported in server.ts but @remix-run/deno is not listed in your package.json dependencies. Did you forget to install it?
The path "@remix-run/react" is imported in src/entry.server.tsx but @remix-run/react is not listed in your package.json dependencies. Did you forget to install it?
The path "react" is imported in src/routes/index.tsx but react is not listed in your package.json dependencies. Did you forget to install it?
The path "react-dom/server" is imported in src/entry.server.tsx but react-dom is not listed in your package.json dependencies. Did you forget to install it?

These warnings are triggered because several packages don’t list their dependencies correctly according to (the somewhat more stringent) requirements of Yarn. This leads to several similar errors along the lines of “X tried to access Y, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound”. These errors are caught and the warnings above are shown instead.
I have been informed that it is currently not desirable to update all package dependencies according to Yarn guidelines, in which case I think it’s best to mute these warnings for Yarn PnP users.

Since these are only warnings & don't block anything else, I think we can just leave this as-is.
As said in https://github.com/remix-run/remix/pull/3566#discussion_r906420249: the warning will disappear automatically once we made the switch to @remix-run/router.

As I understood it, the migration to @remix-run/router will fix warnings on react and react-dom dependencies. The warnings above include other dependencies (e.g. @remix-run/deno, but presumably also for other integrations). Will the switch to the new router fix those as well?
In addition, the messaging of these warnings (“X is not listed in your package.json dependencies”) is incorrect.

Hi @pcattori @mcansh, is there anything I can do to help this move along?
My console output for yarn dev:
The path "@remix-run/react" is imported in src/root.tsx but "@remix-run/react" was not found in your node_modules. Did you forget to install it?
The path "@apollo/client" is imported in src/routes/admin/organizations/controls/AddUserToOrganization.tsx but "@apollo/client" was not found in your node_modules. Did you forget to install it?
The path "react-intl" is imported in src/routes/profile/displayPreferences/DisplayPreferences.tsx but "react-intl" was not found in your node_modules. Did you forget to install it?
The path "react" is imported in src/routes/profile/displayPreferences/Card.tsx but "react" was not found in your node_modules. Did you forget to install it?
The path "react/jsx-dev-runtime" is imported in src/routes/admin/ui/Suggestions.tsx but "react/jsx-dev-runtime" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/react-fontawesome" is imported in src/routes/authors/CorrectionSection.tsx but "@fortawesome/react-fontawesome" was not found in your node_modules. Did you forget to install it?
The path "@remix-run/node" is imported in src/entry.server.tsx but "@remix-run/node" was not found in your node_modules. Did you forget to install it?
The path "deepmerge-ts" is imported in src/routes/admin/groups/controls/GrantGroupAdminPrivileges.tsx but "deepmerge-ts" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faLink" is imported in src/routes/team/Person.tsx but "@fortawesome/free-solid-svg-icons/faLink" was not found in your node_modules. Did you forget to install it?
The path "slate" is imported in src/routes/authors/editorSection/EditorSection.tsx but "slate" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faChartLine" is imported in src/routes/educational-institutions.tsx but "@private/fontawesome/pro-light-svg-icons/faChartLine" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faGrinWink" is imported in src/routes/publishers/RegistrationMarks.tsx but "@private/fontawesome/pro-light-svg-icons/faGrinWink" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faCheck" is imported in src/routes/authors/CorrectionSection.tsx but "@private/fontawesome/pro-light-svg-icons/faCheck" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons" is imported in src/routes/book/coverPage/CoverPage.tsx but "@fortawesome/free-solid-svg-icons" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons" is imported in src/routes/login/LoginForm.tsx but "@private/fontawesome/pro-regular-svg-icons" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faEnvelope" is imported in src/routes/publishers/index.tsx but "@private/fontawesome/pro-light-svg-icons/faEnvelope" was not found in your node_modules. Did you forget to install it?
The path "react-scroll" is imported in src/routes/privacy-policy.tsx but "react-scroll" was not found in your node_modules. Did you forget to install it?
The path "slate-react" is imported in src/routes/authors/editorSection/EditorSection.tsx but "slate-react" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faTable" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-light-svg-icons/faTable" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faPencilAlt" is imported in src/routes/authors/CorrectionSection.tsx but "@private/fontawesome/pro-light-svg-icons/faPencilAlt" was not found in your node_modules. Did you forget to install it?
The path "react-dom/server" is imported in src/entry.server.tsx but "react-dom/server" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faLink" is imported in src/routes/educational-institutions.tsx but "@private/fontawesome/pro-light-svg-icons/faLink" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faSmileWink" is imported in src/routes/publishers/RegistrationMarks.tsx but "@private/fontawesome/pro-light-svg-icons/faSmileWink" was not found in your node_modules. Did you forget to install it?
The path "js-cookie" is imported in src/routes/login/LoginForm.tsx but "js-cookie" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faEnvelopeOpen" is imported in src/routes/publishers/index.tsx but "@private/fontawesome/pro-light-svg-icons/faEnvelopeOpen" was not found in your node_modules. Did you forget to install it?
The path "@headlessui/react" is imported in src/routes/profile/index.tsx but "@headlessui/react" was not found in your node_modules. Did you forget to install it?
The path "react-router-dom" is imported in src/routes/admin/groups/AdminGroupPanel.tsx but "react-router-dom" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faLongArrowRight" is imported in src/routes/qr/index.tsx but "@private/fontawesome/pro-light-svg-icons/faLongArrowRight" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons" is imported in src/routes/library.tsx but "@private/fontawesome/pro-solid-svg-icons" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faBold" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faBold" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faTimes" is imported in src/routes/authors/CorrectionSection.tsx but "@private/fontawesome/pro-light-svg-icons/faTimes" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faStopwatch" is imported in src/routes/educational-institutions.tsx but "@private/fontawesome/pro-light-svg-icons/faStopwatch" was not found in your node_modules. Did you forget to install it?
The path "react-use" is imported in src/routes/profile/displayPreferences/Color.tsx but "react-use" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faPlusSquare" is imported in src/routes/profile/settings.tsx but "@private/fontawesome/pro-light-svg-icons/faPlusSquare" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faPlus" is imported in src/routes/library.tsx but "@private/fontawesome/pro-solid-svg-icons/faPlus" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faCode" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faCode" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faTrophyAlt" is imported in src/routes/educational-institutions.tsx but "@private/fontawesome/pro-light-svg-icons/faTrophyAlt" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faLongArrowRight" is imported in src/routes/book/coverPage/CoverPage.tsx but "@private/fontawesome/pro-regular-svg-icons/faLongArrowRight" was not found in your node_modules. Did you forget to install it?
The path "axios" is imported in src/routes/publish/index.tsx but "axios" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faFilm" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faFilm" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faImage" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faImage" was not found in your node_modules. Did you forget to install it?
The path "react-helmet-async" is imported in src/routes/book/coverPage/CoverPage.tsx but "react-helmet-async" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faIndent" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faIndent" was not found in your node_modules. Did you forget to install it?
The path "react-tsparticles" is imported in src/routes/educational-institutions.tsx but "react-tsparticles" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faArrowCircleDown" is imported in src/ui/Arrow.tsx but "@private/fontawesome/pro-light-svg-icons/faArrowCircleDown" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faItalic" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faItalic" was not found in your node_modules. Did you forget to install it?
The path "tsparticles" is imported in src/routes/educational-institutions.tsx but "tsparticles" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faLink" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faLink" was not found in your node_modules. Did you forget to install it?
The path "react-router" is imported in src/routes/publish/index.tsx but "react-router" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faListOl" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faListOl" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faListUl" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faListUl" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faOutdent" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faOutdent" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faRedo" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faRedo" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faUnderline" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faUnderline" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faUndo" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-regular-svg-icons/faUndo" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faArrowCircleRight" is imported in src/ui/landingPage/LibraryPreview.tsx but "@private/fontawesome/pro-light-svg-icons/faArrowCircleRight" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faQrcode" is imported in src/ui/form/QrInput.tsx but "@private/fontawesome/pro-regular-svg-icons/faQrcode" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faCaretDown" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-solid-svg-icons/faCaretDown" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faQuoteLeft" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@private/fontawesome/pro-solid-svg-icons/faQuoteLeft" was not found in your node_modules. Did you forget to install it?
The path "@react-spring/web" is imported in src/routes/authors/editorSection/Toolbar.tsx but "@react-spring/web" was not found in your node_modules. Did you forget to install it?
The path "react-dom" is imported in src/routes/authors/editorSection/Toolbar.tsx but "react-dom" was not found in your node_modules. Did you forget to install it?
The path "zxcvbn" is imported in src/ui/form/validatedInput/ValidatedInput.tsx but "zxcvbn" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faHeart" is imported in src/ui/landingPage/mockup/AnimatedComment.tsx but "@private/fontawesome/pro-solid-svg-icons/faHeart" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faSpinnerThird" is imported in src/ui/Spinner.tsx but "@private/fontawesome/pro-light-svg-icons/faSpinnerThird" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faEnvelope" is imported in src/ui/Link.tsx but "@private/fontawesome/pro-regular-svg-icons/faEnvelope" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faTimesCircle" is imported in src/ui/form/RemoveButton.tsx but "@fortawesome/free-solid-svg-icons/faTimesCircle" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faPenFancy" is imported in src/ui/Footer.tsx but "@fortawesome/free-solid-svg-icons/faPenFancy" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faExternalLink" is imported in src/ui/Link.tsx but "@private/fontawesome/pro-regular-svg-icons/faExternalLink" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faTachometerAlt" is imported in src/ui/Footer.tsx but "@fortawesome/free-solid-svg-icons/faTachometerAlt" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faBooks" is imported in src/ui/Footer.tsx but "@private/fontawesome/pro-solid-svg-icons/faBooks" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faAngleRight" is imported in src/content/annotation/discussion/Discussion.tsx but "@private/fontawesome/pro-regular-svg-icons/faAngleRight" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faTrashAlt" is imported in src/content/annotation/note/Note.tsx but "@private/fontawesome/pro-regular-svg-icons/faTrashAlt" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faWindowMinimize" is imported in src/content/annotation/note/Note.tsx but "@private/fontawesome/pro-regular-svg-icons/faWindowMinimize" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faChevronDown" is imported in src/ui/tableOfContents/RecursiveTree.tsx but "@private/fontawesome/pro-light-svg-icons/faChevronDown" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faBriefcase" is imported in src/ui/header/CompanyDropDownMenu.tsx but "@fortawesome/free-solid-svg-icons/faBriefcase" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faChevronDown" is imported in src/ui/tableOfContents/RecursiveTree.tsx but "@private/fontawesome/pro-solid-svg-icons/faChevronDown" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faUserCircle" is imported in src/ui/header/UserIcon.tsx but "@fortawesome/free-solid-svg-icons/faUserCircle" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faUserGraduate" is imported in src/ui/header/ProductDropDownMenu.tsx but "@fortawesome/free-solid-svg-icons/faUserGraduate" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faInfoCircle" is imported in src/ui/header/CompanyDropDownMenu.tsx but "@private/fontawesome/pro-light-svg-icons/faInfoCircle" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faSignIn" is imported in src/ui/header/UserIcon.tsx but "@private/fontawesome/pro-regular-svg-icons/faSignIn" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faBuilding" is imported in src/ui/header/ProductDropDownMenu.tsx but "@private/fontawesome/pro-light-svg-icons/faBuilding" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faFilter" is imported in src/ui/toolbar/buttons/Summary.tsx but "@fortawesome/free-solid-svg-icons/faFilter" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faAngleLeft" is imported in src/ui/toolbar/buttons/PreviousPage.tsx but "@fortawesome/free-solid-svg-icons/faAngleLeft" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faAngleRight" is imported in src/ui/toolbar/buttons/NextPage.tsx but "@fortawesome/free-solid-svg-icons/faAngleRight" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faUniversity" is imported in src/ui/header/ProductDropDownMenu.tsx but "@private/fontawesome/pro-light-svg-icons/faUniversity" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faList" is imported in src/ui/toolbar/buttons/TableOfContentsToggle.tsx but "@fortawesome/free-solid-svg-icons/faList" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faLongArrowDown" is imported in src/ui/guidedTour/steps/ScrollDown.tsx but "@private/fontawesome/pro-light-svg-icons/faLongArrowDown" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faTimes" is imported in src/ui/toolbar/buttons/Escape.tsx but "@private/fontawesome/pro-regular-svg-icons/faTimes" was not found in your node_modules. Did you forget to install it?
The path "@fortawesome/free-solid-svg-icons/faMoon" is imported in src/ui/toolbar/buttons/ColorTheme.tsx but "@fortawesome/free-solid-svg-icons/faMoon" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faMessage" is imported in src/ui/toolbar/annotate/CommentModeButton.tsx but "@private/fontawesome/pro-regular-svg-icons/faMessage" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-regular-svg-icons/faNote" is imported in src/ui/toolbar/annotate/NoteModeButton.tsx but "@private/fontawesome/pro-regular-svg-icons/faNote" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFilter" is imported in src/ui/toolbar/buttons/Summary.tsx but "@private/fontawesome/pro-light-svg-icons/faFilter" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faMessage" is imported in src/ui/toolbar/annotate/CommentModeButton.tsx but "@private/fontawesome/pro-solid-svg-icons/faMessage" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faNote" is imported in src/ui/toolbar/annotate/NoteModeButton.tsx but "@private/fontawesome/pro-solid-svg-icons/faNote" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faLightbulb" is imported in src/ui/toolbar/buttons/ColorTheme.tsx but "@private/fontawesome/pro-solid-svg-icons/faLightbulb" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faLightbulbOn" is imported in src/ui/toolbar/buttons/ColorTheme.tsx but "@private/fontawesome/pro-solid-svg-icons/faLightbulbOn" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faCommentsAlt" is imported in src/ui/popup/selectionButtons/DiscussionButton.tsx but "@private/fontawesome/pro-solid-svg-icons/faCommentsAlt" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faDownload" is imported in src/content/block/file/File.tsx but "@private/fontawesome/pro-light-svg-icons/faDownload" was not found in your node_modules. Did you forget to install it?
The path "filesize" is imported in src/content/block/file/File.tsx but "filesize" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFile" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFile" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileAlt" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileAlt" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileArchive" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileArchive" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileAudio" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileAudio" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileChartPie" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileChartPie" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileCode" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileCode" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileCsv" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileCsv" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFilePdf" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFilePdf" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileSpreadsheet" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileSpreadsheet" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faPaperPlane" is imported in src/content/annotation/discussion/comment/controls/SendButton.tsx but "@private/fontawesome/pro-solid-svg-icons/faPaperPlane" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-solid-svg-icons/faUsers" is imported in src/content/annotation/discussion/comment/controls/VisibilitySelector.tsx but "@private/fontawesome/pro-solid-svg-icons/faUsers" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileVideo" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileVideo" was not found in your node_modules. Did you forget to install it?
The path "@private/fontawesome/pro-light-svg-icons/faFileWord" is imported in src/content/block/file/icon.ts but "@private/fontawesome/pro-light-svg-icons/faFileWord" was not found in your node_modules. Did you forget to install it?

@lensbart This is on my list of things to revisit for the week. I'll let you know if there's any way to make progress on this on our end.

@lensbart from reading this and related issues, it seems like there are two causes for the spurious warnings:

Dependencies being pulled in by react-router that should be fixed when we internally switch to @remix-run/router
Other dependencies

It seems to me that for (2), it might be a good idea to do what you suggested:
"peerDependenciesMeta": {
    "react": {
      "optional": true
    },
    "react-dom": {
      "optional": true
    }
  }

peerDependenciesMeta is part of the package.json spec, so its not yarn-specific, which is why I'm especially leaning towards that.
Beyond (1) being fixed via @remix-run/router soon, and fixing (2) via peerDependenciesMeta would there be anything else we would need to address?

Thanks for looking into it, @pcattori!

Beyond (1) being fixed via @remix-run/router soon, and fixing (2) via peerDependenciesMeta would there be anything else we would need to address?

Most of the warnings quoted above are not due to a missing peerDependenciesMeta setting. The check for this warning (which this PR circumvents) fails to detect some dependencies that are indeed available. Not sure why, but doesn’t tooling (ESLint / TypeScript) typically help warn against uninstalled dependencies, anyway?
The @private/... dependencies you see listed are installed from a private repository. Yarn can be configured to install from a private repository as follows:
# .yarnrc.yml
npmScopes:
  private:
    npmAlwaysAuth: true
    # Include trailing `-` to prevent `yarn` from failing in CI environment where `AWS_CODEARTIFACT_AUTH_TOKEN` is not available.
    npmAuthToken: '${AWS_CODEARTIFACT_AUTH_TOKEN-}'
    npmRegistryServer: 'https://something.d.codeartifact.us-east-1.amazonaws.com/npm/private'

In conclusion, I think the check for the warning should either be compatible with all package managers and resolution mechanisms (npm, yarn, yarn pnp, pnpm), or be disabled for those that are incompatible.
Hope this helps!

In conclusion, I think the check for the warning should either be compatible with all package managers and resolution mechanisms (npm, yarn, yarn pnp, pnpm), or be disabled for those that are incompatible.

Well said; I agree.

@pcattori Is there anything I can do to help move this forward? I also created https://github.com/remix-run/remix/issues/4346 to summarise other outstanding issues for Yarn PnP support.
Thank you!

@lensbart sorry for the delay! I was busy getting married last week 😅
If you can just change the warnings to be enabled for npm and yarn (rather than being disabled for pnpm), then I think we're good to merge this 😁

Congrats on getting married, by the way!!! 🥳🥳🥳

If you can just change the warnings to be enabled for npm and yarn (rather than being disabled for pnpm)

Just for the avoidance of confusion: Plug‘n’Play is a feature of Yarn, abbreviated as PnP. This is unrelated to the pnpm package manager.

Looking at this again, I just realized I was talking as if this PR was for pnpm support, not yarn pnp.
So what I'm actually looking for here is something like:
if (usingNode || usingBasicYarn) {
  warn()
}

Specifically, I think we still need the process.versions.pnp check to differentiate basic Yarn from Yarn PnP.
So maybe something like:
let pkgManager = getPreferredPackageManager()
if (pkgManager === "node" || (pkgManager === "yarn" && process.versions.pnp === null)) {
  warn()
}

interestingly enough, I'm looking into upgrading esbuild to use the native pnp stuff over there and i don't get any warnings with it https://github.com/mcansh/remix-pnp-test
0.0.0-experimental-aed5bfbf7

@pcattori Done!

@mcansh Interesting. Does that also fix the issue with import aliases, described as the third problem in this issue?

@mcansh Interesting. Does that also fix the issue with import aliases, described as the third problem in this issue?

it seems to, but typescript (in vscode) is furious as it doesn't know about pnp

@mcansh Make sure to yarn dlx @yarnpkg/sdks vscode for editor support

@mcansh Make sure to yarn dlx @yarnpkg/sdks vscode for editor support

just did 😆 - i know very little about pnp haha - if you want to toy around 0.0.0-experimental-aed5bfbf7 is available for all remix packages 😄

@mcansh I can get it to work with that experimental branch, thanks. (I still see the redundant warnings that this PR fixes.)

@lensbart thanks for giving it a run! surprised i didn't get the warnings, so good thing we merged this 🙂


Update README.md

onChange is not called on the load even if the crop was adjusted. This is so that we can detect user changes using this callback as opposed to changes (adjustments) made by the library during the initialization.
Close #99

Thanks 👍


"The domain you entered is invalid or unavailable" in domain management

App Id: arn:aws:amplify:us-east-2:286574893818:apps/d1fmnb6hndzup5
Region: us-east-2
Step: setting up custom domain
Status: available (but not working)
Issue/question
I've deployed an Amplify React app successfully from a repository. I go under Domain Management and click on Add Domain, then type anything on the domain I want to hook this up to (iccsafe.org, though it will be on some kind of a sub-domain), and click on Configure Domain. I'm then given the below error message.
Error message
The domain you entered is invalid or unavailable
Additional information
I'm not given any guidance as to why this would be, it's obviously a domain that exists. What other reasons would it not be eligible here?

@bclarkicc  iccsafe.org should work. Can you check it again? (Please make sure no space include)

@Joycehao19 It definitely does not. I've made sure there are no spaces or anything in it, and I still get that message as of this morning.

Looking into it, this has to do with restrictions on my account. Going to close this issue.

Same Issue. Is it already solved? Can you share me how to solve please?

@HeinMynn My AWS account actually had permission restrictions on it that were preventing me from doing this. Those permissions just had to be added to my account by our administrator, and it was fixed. Obviously may be different for you.

Just in case anybody else winds up here - I had the same behavior trying to connect to a 3rd-party managed domain. Make sure your AWS IAM account has permissions for Route 53. I noticed in the console that network calls to Route 53 were failing, updated permissions, and it resolved the issue.

Get a certificate from ACM and add it to your Route53 records after your certificate validates try again in the Amlipy it will work this time.


Location module

The intent of this module is to be able to ask Leon to suggest nearby theaters, restaurants, and he can.
Feature Use Case
Leon, recommend a nearby café with a rating above four
I get that Leon is intended to be safe, offline, and secure, so it would make sense if this would not be a feature to be added at this time. Thanks a lot for considering my feature, ~Shark

@importshark  adding near by hotels can be through google maps API then that's a whole lot of improvement
Is that what u mean or any other way to work with?

Yeah essentially that. Being able to get the current location and access information about nearby businesses, parks, etc.

@importshark Its great but the API key Needs to be generated right ? Its a paid process any Idea to work over?

@AthithyaIthayan yeah that's the problem. We can probably talk more about this when the core is rewritten

code?
Ig we can at least let him open google maps through a command as of now?


UI

Summary
A UI is not a deliverable of the CompLOINC project, but it could be nice to have a demo.
Options

Bioportal, OLS, etc (if we need read only)
TermHub (possibly; pending future development of code system management)

@joeflack4 I Think There  Is Some issue In The This page https://loinc.org/twitter/
It Should Be Look Like This I Guess : -

But The HTML Code Of Widget  Is Also Printing :

Can I Resolve This Issue.....!

@Chetax Thank you for bringing this website error to our attention. The page has been corrected. For future reference, please contact us using our website form for this type of issue. This GitHub repo is a separate project unrelated to the loinc.org website.

Ok Sir


Remove newlines represented by LF as well as CRLF

The quoted-printable standard seems to require CRLF line breaks, but many clients support LF too. This patch allows for supporting the LF case in addition to CRLF.
This should fix #35.

Hi guys, was this already merged?


[Issue-2586] Update chainlist

Related issue(s)
#2586
Is your feature request related to a problem(s)? Please describe.

[x]  Remove explorer on Genshiro network
[x]  Update chain subspace gemini 3h (Issue-180 Chainlist)

🚀 Deployed on https://pr-2587--sw-web-runner.netlify.app

https://github.com/Koniverse/SubWallet-ChainList/issues/180


Add & update dependencies through vcpkg and find_package, fix warnings/msvc errors & include issues

[ ] Mingw build test
[ ] Everything works :)

[ ] Mingw build test
[ ] Everything works :)

Makefile actually needs to get fixed still, but I would honestly just drop support of that

Looks good to me!


Add AnyNode and AnyNodeRef unions

This introduces two new unions AnyNode and AnyNodeRef. They represent unions over all node python nodes and differ in that AnyNodeRef stores a reference where AnyNode is the owned version.
Being able to pass an arbitrary node will become necessary in the formatter where I want to have a single function that decides to which node a comment should be associated (it accepts the parent node, preceding, and following nodes as AnyNodeRef).
I further plan to use the indextree crate in the formatter that will allow us to access the parent/ancestor nodes. This requires a uniform type for all nodes and AnyNodeRef fits that bill perfectly.
This looks like a lot of code. Most of it is just boilerplate (thanks multiline edits!). The API is:
AnyNode

AnyNode::from(node): AnyNode::from(if_stmt)
AnyNode::from(union): AnyNode::from(stmt)
AnyNode::union() -> Option<Union>: node.statement() returns Some if the node is any statement
AnyNode::node() -> Option<Node>: node.if_stmt() returns Some if the node is an if statement
AnyNode::as_node() -> Option<&Node>: node.as_if_stmt() returns Some if the node is an if statement
AnyNode::is_node() -> bool: node.is_if_stmt() returns true if the node is an if statement.
AnyNode::as_ref() -> AnyNodeRef: Returns a reference to this node.

Nodes

Node::cast(AnyNode) -> Option<Self>: IfStmt::cast(any_node) returns Some if any_node is an if statement.
Node::cast_ref(AnyNodeRef) -> Option<&Self>: IfStmt::cast_ref(node)returnsSomeif thenode` is an if statement.

AnyNodeRef

AnyNodeRef::from(&node)
AnyNodeRef::from(&union)
AnyNodeRef::as_node() -> Option<&Node>
AnyNodeRef::is_node() -> bool

Current dependencies on/for this PR:

main

PR #4578   👈

This comment was auto-generated by Graphite.

If we use indextree in the formatter, should we consider using it in the linter? We have our own Node type, we do our own child-to-parent and sibling tracking. It'd be nice to use the same thing in both places, if we can.

I think we could replace Node already today with AnyNodeRef, at least if we're okay that it now covers all Nodes and not just Expr and Stmt.
Let me see how my experience is with indextree but I think re-using it could make sense (could also allow sharing more state between formatter and linter).

Sounds good. Certainly doesn't need to block this PR or its use in the formatter.


Update dependency versions of toolkit

FYI, I noticed some other dependency issues, and have a draft PR up: https://github.com/Esri/arcgis-toolkit-dotnet/pull/392
Mostly these address warnings, but I recall issues creating archives (apk) without the constraintlayout dependency changes.


what does this line mean in README?

A weight of 1 will sample images that match the prompt roughly as well as images usually match prompts like that in the training set.

I can't wrap my head around this sentence. Could you please explain it with different wording? Thanks!

many thanks!


Docker image fixes

Docker build was broken due to different naming of the artifact from Go, paths changed and glide has been removed.
This should fix these issues (haven't got time to properly test it all)
Signed-off-by: Willem van Dreumel<EMAIL_ADDRESS>

Current coverage is 2.24% (diff: 100%)

Merging #117 into master will not change coverage

@@            master      #117   diff @@
========================================
  Files           32        32
  Lines         7523      7523
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
  Hits           169       169
  Misses        7337      7337
  Partials        17        17

Powered by Codecov. Last update 8857d70...67e7798

i think we should move out of the Dockerfile the build process
as @tboerger will build binaries, we'll just have to add them in the shipped IMAGE.
PR incoming in my case :)

@xinty Actually, the whole point of a Dockerfile is to allow the user to build the binary him/herself. We should not be putting binaries in there if we can build it ourselves.

Not sure if I understand @LefsFlarey correctly. But what will happen is that everyone can simply run make buildon their machine and create a binary. Our CI Pipeline will then use the binary created by the same command and simply copy it into the docker image. No need to have Go inside the container. Just a binary.
Right @tboerger ?

Agree @metalmaze

It will be automated, the makefile tasks are already there, just need to add drone as ci

Changed the whole docker image to be able to run it as unprivileged user (needed for some docker environments like OpenShift v3 which do not allow to run as root) and merged the current master into the pull request

I'm really not a fan of the current approach. I really dislike the switch away from Alpine.

It should definitively be possible to build Gitea on an alpine container without too much hassle.

So we agree to build only on official images

Should we take https://github.com/go-gitea/gitea/pull/288 in favor of this?

Thanks for the work, we have merged #288 now to properly build docker images.


Issues with login

I've been trying to play around with this and have had issues getting the login stuff working. I haven't been able to log in successfully using a token or using the email method. Is it working for anyone else or is there something I'm missing?

I've been trying to play around with this and have had issues getting the login stuff working. I haven't been able to log in successfully using a token or using the email method. Is it working for anyone else or is there something I'm missing?

Hi,
Couple of things to help debug this for you:

For email auth: Is your email service imap enabled?
Can you add the following debug arg before running your node app and share the output:        export DEBUG="Arlo:*"


Fix Inkscape CLI options

Inkscape's CLI options have changed since this was written, which broke it. The Inkscape CLI wiki page has the changes listed. This should have the same behavior, but I'm not an Inkscape expert. I tested it with a few SVGs I had lying around and it worked for all of them, which is a very professional and thorough testing method ;)

Fixed with commit 64fa78f4eb0730e08231c98522fe6df986f9b369.
Thank you @CartConnoisseur for your help.


Option (-option/-o) flag to avoid polluting CLI flags

There's room for minor options that would otherwise pollute the CLI flags.
For example, if someone wants an opt-out for the directory listing,
we might have to add an overly verbose --no-directory-listing flag or similar.
A better approach might be for minor tweaks to the generated output
that aren't necessarily part of the contract to go into "options" (similar to asciidoc page attributes).

This seems unnecessary. We can get to this when we have those options.


issue when snapshoting a container

Hello
I use lxc 2.0.8 on ubuntu.
In order to backup a container, i want to  :

snapshot it
publish it and finally export it.

I met a trouble in snapshot step :
due to rsync issue ( vanish files), snapshot never ends. It always output errors with vanished files.
In unix, vanished files is not blocking for rsync.
How can i workaround this issue in order to make snapshot step OK ?
Best regards

Hmm, so you're using LXD but with the "dir" backend then?
First can you make sure you're running an up to date LXD (2.0.10 is what you should be getting on up to date 16.04 LTS), then try to reproduce the issue again. If it still happens, then please provide the content of /var/log/lxd/lxd.log.

Note that snapshots on the directory backend are always going to be unreliable as they're not atomic and so will be inherently inconsistent. But this shouldn't cause hangs. Rsync warnings should be ignored and rsync errors should cause LXD errors. A hang is somewhat surprising and hopefully something which got fixed in more recent bugfix releases.

I try with lxd 2.0.10 on ubtunu 16.04 with same issues :
lxc snapshot xxxxxxxxxxxx
error: rsync failed: file has vanished: "/var/lib/lxd/containers/************************
file has vanished: "/var/lib/lxd/containers/************************
rsync warning: some files vanished before they could be transferred
As you said, rsync shouldn't issue due to vanished files. In my case, Rsync output error.
lxd.log

@zoum9 did that hang or just fail?
If hang, can you look at whether you still have some rsync processes running?

It  's just failed, so no snapshot.
I want Snapshot end, even if it s not reliable.
According to me, Snapshot musn't ouput errors (warning)  and end, even with vanished files

Did you publish an lxd update for this ?
Indeed, i don't see update despite your modifications .
Best regards

@zoum9, this commit is in master but not in 2.18. It will be available in 2.19 though.

Ok , thanks.
On my ubuntu server ( ubuntu 16, xenial, the last release avalaible is 2.0.10)
If i want to test this new release, i must download source code wich is master ?

@zoum9, 2.19 was releases yesterday it should be available in the backports soon I guess or through the PPA.

Ok, so to test it, i have to upgrade my os in order to download 2.19 wich is not yet ready, isn't it ?

You don't have to upgrade your whole OS, you can just update to 2.19 if that is possible for you. 2.19 is ready and released but it takes some time for the package to be published in the archive.

The snap is going to update to 2.19 today, but I'm not sure that moving from the deb to the snap is necessarily worth it just for this one fix :)


Feat/custom headers

This adds a new function to set custom headers:
pactffi_verifier_add_custom_header(
      handle: *mut handle::VerifierHandle,
      header_name: *const c_char,
      header_value: *const c_char
    )

Resolves #182

Awesome, Thanks Ron. Signature looks good, I'll take a look at implementation tomorrow


Considering chrome-aws-lambda

The initial plan was using chrome-aws-lambda instead of ~chunky boi~ Chromium, so helping me with this would be nice.

I'll take a look at this today!

Closed due to update version 0.2.0 (#8)


DOC: Add hint on how to render task graphs horizontally

[ ] Tests added / passed
[ ] Passes flake8 dask

Thanks @xhochy !
I hope that the workshop went well.


Hmm, cla/linuxfoundation shows that a CLA is needed but I have already signed the commit with git commit -s. Even after re-push it is still shows the same message.
Any idea what could be the reason for this?

I signed it

/lgtm

/approve


Go to the project settings.
Configure Dropbox.
Click to change the folder and select one of your folders, look at the blue message that appears.

Expected
The blue message that says connect "/folder"? would be attached to the bottom of the folder browser.
Actual
The message box is below the browser and not connected.

This may be the intended behavior due to the fact that the bottom of the browser has rounded corners and the top of the alert has rounded corners but, no matter what, we do need consistency, and all of the other add-ons have the blue message attached to the bottom of the browser.


Exception# Invalid character

I don't know what's the problem with this ` character in #Chakra JavaScript engine. I'm unable to render my script into Internet Explorer 11.
If anyone explain me this problem, I would be graceful.
Here is the browser information below:
Internet Explorer 11
Version: 11.0.9600.17278
Update Version: 11.0.12 (KB2977629)
navigator.userAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; InfoPath.2; rv:11.0) like Gecko
Please look the following attachment:
1#

2#

Strings denoted by backticks are a newish language feature (template literals), which IE does not support. IE is no longer being updated (except for security fixes). If you want to support IE you will need to change to use a normal string literal (i.e. denoted with either single or double quotes) or use a library to polyfill them.


Add support for a map facet

Original author: iainsproat (June 23, 2010 16:48:55)
Add a map facet to display geolocations.
The scatter facet already works similarly and so does most of the hard work already, but produces the output as an image.  An option next to the scatter facet 'show in map' might work, or we'd have to have a way to flag that a column is a coordinate.  (maybe could be could be inferred from the protograph?)
Original issue: http://code.google.com/p/google-refine/issues/detail?id=94

This should be handled by an extension.

Hi, wow this was filed quite long ago!
I just want to be able to see the facet/cluster I'm seeing on a map. I came across this extension, but they don't seem to have that. What I presently have to do is export as CSV, then import it in a mapping app like geojson.io.
There's a complication that the latitude and longitude are usually stored in two separate columns.
How about Export > To Map? We could do some tweaks to the existing HTML table export option.

Hi @answerquest we'll be eventually changing our UI to a more modern framework, quite possibly based on React, and so extensions will have to be re-written.
Having said that, this need you have to make it easier to export to a map should be handled by an extension.  We won't add this to our core, mainly because there are many kinds of mapping applications and endpoints that could be utilized, so its best to have extensions handle that where the community that is interested in their particular Mapping need, can directly contribute to those extensions and enhance them, without disturbing our core.
If someone wants to work on this extension need, my suggestion would be to begin in 2019, since this fall/winter 2018 we plan to begin changing quite a few things.

I'd be tempted to agree with Thad here too - this would be a good feature for an extension focused of geo data. Feel free to reopen if you disagree.


Setting a slice of memory without having to enumerate

It's nice that the WASM memory can be inspected with a slice operator:
from wasmtime import *
engine = Engine()
store = Store(engine)
module = Module.from_file(engine, "./hello.wasm")
instance = Instance(store, module, [])
exports = instance.exports(store)
memory = exports["memory"]

Then
>>> memory.data_ptr(store)[1024:1029]
[114, 97, 116, 115, 0]

but it's not possible to set it that way which seems like a bug, or at least a missing feature:
>>> data = memory.data_ptr(store)
>>> data[1024:1028] = [114, 97, 116, 116]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: sequence index must be integer, not 'slice'

You can work around it by iterating:
for i,v in enumerate("fats".encode('utf-8')): data[i] = v

Ah sorry I don't know much about python bulk array assignment, but if a different type should be returned by the methods here that's more idiomatic that seems like a reasonable thing to do!

Agree, but I have no idea how to achieve it. All I know is bulk assignment works with an actual list of bytes, and wasmtime._memory.Memory .data_ptr() is masquerading as a list of bytes. So it should be possible.

This seems to work:
>>> from ctypes import *
>>> data = (c_ubyte*memory.data_len(store)).from_address(addressof(memory.data_ptr(store).contents))
>>> data[0:10] = "helloworld".encode('utf-8')
>>> data[0:10]
[104, 101, 108, 108, 111, 119, 111, 114, 108, 100]
>>> memory.data_ptr(store)[0:10]
[104, 101, 108, 108, 111, 119, 111, 114, 108, 100]

I've also been playing around with wasmtime, got a toy program running but I was reading and writing memory one byte at a time.
Glad to see there's a bulk read method available (it didn't occur to me to use a slice), a bulk write would also be very welcome!

Playing around with this a little more, memory.data_ptr(store)[:res_length] returns an actual list of integer objects. You can call bytes on it, but it's very inefficient. Realistically no one's going to be treating this as a list of integers, so I'd suggest changing the API to just return a bytes or bytearray instance directly.

this is very important as it's the most obvious bottleneck
python have many ways of doing it, for example
bytearray(b'helloworld') or array.array('B', b'helloworld')
I believe if set_item is passed a slice instead of index, it should iterate instead of raising exception
    ptr = memory.data_len(store)
    ptr[start:end]=bytearray(b'helloworld')
TypeError: sequence index must be integer, not 'slice'

>>> buff=bytearray(b'hello world')
>>> buff[0:5]=b'HELLO'
>>> for i in buff: print(i)
72
69
76
76
79
32
119
111
114
108
100

for comparison, on my example wasm3 slice set took ~1ms
in wasmtime it took ~900ms
this is 900x slower!!

here they suggest to cast the C pointer to memoryview
memory_ptr = memory.data_ptr(store)
buff = memoryview(ctypes.cast(memory_ptr, ctypes.POINTER(ctypes.c_ubyte*size)))
buff_bytes = buff.bytes()

https://stackoverflow.com/questions/43810423/what-is-the-most-efficient-way-to-copy-an-externally-provided-buffer-to-bytes
but I got endianess problems
https://bugs.python.org/issue39610
NotImplementedError: memoryview: unsupported format &<B

any clue how to set a slice to bytearray or bytes or similar list of bytes?

@dsyer  the following line was too slow, it was even slower than setting the slice
>>> data = (ctypes.c_ubyte*memory.data_len(store)).from_address(ctypes.addressof(memory.data_ptr(store).contents))

how can we make it into memoryview without creating endianess problems?

here is my implementation which is 300x times faster than @dsyer
def set_slice(val, start=0, end=None):
    size = memory.data_len(store)
    if end is None: end=start+len(val)
    val_size = len(val)
    if end-start>val_size or end>size:
        raise IndexError("out of memory size")
    src_ptr = (ctypes.c_ubyte * val_size).from_buffer(val)
    dst_ptr = ctypes.addressof((ctypes.c_ubyte*val_size).from_address(ctypes.addressof(memory_ptr.contents)+start))
    ctypes.memmove(dst_ptr, src_ptr, val_size)
    return

it seems that there was endianess difference thats why @dsyer was slower
and that's why memoryview was failing

Hi folks, a related note here: it would be very nice if wasmtime-py could expose the wasm module memory with Python's Buffer Protocol. This would enable efficient binary array access, slicing and more, via the standard numpy interface. wasmer-python has this implemented.

wasmer-python has this implemented.

@thewtex no, it was worse in terms of performance, please check my article here

While I agree with the above comment, I think it should not be in the scope of this issue here and the already in-progress https://github.com/bytecodealliance/wasmtime-py/pull/134. @thewtex Maybe you can create a new issue?

@j-blue-arz yes, that's right. This would be in addition to @muayyad-alsadi nice setitem / slicing improvements. Issue created in #135 .

please check my article here

@muayyad-alsadi awesome article!!
Sorry if I was not clear, I meant the use of the buffer protocol with numpy instead of setitem / slicing. An example is here:
https://github.com/muayyad-alsadi/wasm-demos/pull/1
The results:
Slicing
_______
img2bytearray took 9 ms
grow:  238
slice set took 352 ms
wasm took 10 ms
slice to array 78 ms
array to image 7 ms
all took 458 ms

img2bytearray took 7 ms
slice set took 355 ms
wasm took 9 ms
slice to array 77 ms
array to image 7 ms
all took 460 ms

Buffer Protocol
_______
img2bytearray took 9 ms
slice set took 0 ms
wasm took 9 ms
slice to array 0 ms
array to image 8 ms
all took 28 ms

img2bytearray took 5 ms
slice set took 0 ms
wasm took 9 ms
slice to array 0 ms
array to image 8 ms
all took 24 ms

@thewtex  thank you that was very useful
here is the wasmtime code for
memory = instance.exports(store)['memory']
ptr_type = ctypes.c_ubyte * (memory.data_len(store))
memory_ptr = (ptr_type).from_address(ctypes.addressof(memory.data_ptr(store).contents))
np_mem = np.frombuffer(memory_ptr, dtype=np.uint8, offset=hb)


ENH: Add crop segment effect

Hi @lassoan, could you review this module when you have a chance? It crops an image to the extent of the current segment, with an option to add padding.
Thanks,
Sara

Hi @lassoan
Did you have a chance to look at the PR?

Thank you, it is a good start, just a couple of improvements are needed.
Wouldn't it make sense to generate a cropped volume for each visible segment automatically? (now the user needs to select a segment, create an output volume, and apply the effect for each piece).

I think that would be a useful addition.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Andras Lasso<EMAIL_ADDRESS>Sent: Wednesday, May 29, 2019 11:13:13 AM
To: lassoan/SlicerSegmentEditorExtraEffects
Cc: muratmaga; Comment
Subject: Re: [lassoan/SlicerSegmentEditorExtraEffects] ENH: Add crop segment effect (#19)
Thank you, it is a good start, just a couple of improvements are needed.
Wouldn't it make sense to generate a cropped volume for each visible segment automatically? (now the user needs to select a segment, create an output volume, and apply the effect for each piece).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flassoan%2FSlicerSegmentEditorExtraEffects%2Fpull%2F19%3Femail_source%3Dnotifications%26email_token%3DAFCMSFARTZKXDVD6FC5Z5R3PX3BTTA5CNFSM4HPVO5S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQGBRQ%23issuecomment-497049798&data=02|01||33944f02647f4fff50b108d6e461510e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636947503949174877&sdata=CsfEFv4FNcQ%2Bn6GXE6JxXxQimDb9mU5sdajVlvpvOWQ%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFCMSFEVBHHS2YNPEDGPJRDPX3BTTANCNFSM4HPVO5SQ&data=02|01||33944f02647f4fff50b108d6e461510e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636947503949184882&sdata=pC0qh2SqNbvTeLpcsXzzD9aHcfx8ZXiqg13QS0Q8unc%3D&reserved=0.

Thanks @lassoan, I'll update this to iterate over all segments.

I've just updated the pull request so that a cropped volume is automatically generated for each segment.

SplitVolume is fine…
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Andras Lasso<EMAIL_ADDRESS>Sent: Friday, May 31, 2019 4:45:06 AM
To: lassoan/SlicerSegmentEditorExtraEffects
Cc: muratmaga; Comment
Subject: Re: [lassoan/SlicerSegmentEditorExtraEffects] ENH: Add crop segment effect (#19)
@lassoan commented on this pull request.

In CMakeLists.txthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flassoan%2FSlicerSegmentEditorExtraEffects%2Fpull%2F19%23discussion_r289357149&data=02|01||0ccedfcba36f472fad2308d6e5bd6de2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636948999080222769&sdata=VGQSHgzgrBi3YtL9jZAf8xiWnGVRSjH7v01Bufh9g2g%3D&reserved=0:

@@ -29,6 +29,7 @@ add_subdirectory(SegmentEditorMaskVolume)
add_subdirectory(SegmentEditorSurfaceCut)
add_subdirectory(SegmentEditorWatershed)
add_subdirectory(SegmentEditorDrawTube)
+add_subdirectory(SegmentEditorCropSegment)

Masking effect name is "Mask volume", not "Mask segment". Anyway, I agree that it is better to avoid having the same name for a module. Since the main differentiator compared to Mask volume effect that it operates on many segments at once (otherwise we could have just added a cropping checkbox to Mask volume effect), we could name it as "Split volume". "Crop to segment" would be appropriate if we could crop different kinds of nodes, not just volumes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flassoan%2FSlicerSegmentEditorExtraEffects%2Fpull%2F19%3Femail_source%3Dnotifications%26email_token%3DAFCMSFHXNGAELHH6L55EMITPYEFUFA5CNFSM4HPVO5S2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB2HS7VY%23discussion_r289357149&data=02|01||0ccedfcba36f472fad2308d6e5bd6de2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636948999080242792&sdata=9JPox7Typ2oXEFOwOfxwHkReenfoeu4bh0E6mKhi7aE%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFCMSFHJF7572BTV7IE65WLPYEFUFANCNFSM4HPVO5SQ&data=02|01||0ccedfcba36f472fad2308d6e5bd6de2|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636948999080252797&sdata=SWx0xfc0yQl%2FI3nEHNFipKxyqyIf8flMpNpyymXX%2B34%3D&reserved=0.

Thank you, your changes have been integrated. I've also made some improvements (images are saved in a new subject hierarchy folder, parameters are saved in the scene, origin/extent computation for non-zero padding is fixed).

Thanks Andras!

Looks great! Thanks @lassoan

@smrolfe @muratmaga Would you mind writing a post on Slicer forum about this new effect? Add "feature" tag to the post (we use this when collecting information for release notes). Maybe also upload a youtube video and add a link to that in the post. Thank you!

@lassoan Sure! I can make a video will post the link. Thanks.

Hi Andras,
Sara and I are trying to prepare for a workshop that we will teach Tuesday, and as usual there is some last minute panic. Is the video something you want soon? We can probably do next week after the workshop. If you need for a demo (for something soon), I can send you a low-resolution scan that works wonderfully with grow from the seeds and split volume…. If not, we will make a video next week and post it on discourse.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Andras Lasso<EMAIL_ADDRESS>Sent: Wednesday, June 12, 2019 7:26:58 AM
To: lassoan/SlicerSegmentEditorExtraEffects
Cc: muratmaga; Mention
Subject: Re: [lassoan/SlicerSegmentEditorExtraEffects] ENH: Add crop segment effect (#19)
@smrolfehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsmrolfe&data=02|01||a9449c8bd46748b176a708d6ef4207b8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636959464201177138&sdata=r6pNIy%2BX9U8YDjUCqvpfGQbaLNGcWHPufLhrQwyX0IE%3D&reserved=0 @muratmagahttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmuratmaga&data=02|01||a9449c8bd46748b176a708d6ef4207b8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636959464201177138&sdata=C76SQE4fI3htEVAdlJuewsV80eQoLZkLi84bO2jrE3s%3D&reserved=0 Would you mind writing a post on Slicer forum about this new effect? Add "feature" tag to the post (we use this when collecting information for release notes). Maybe also upload a youtube video and add a link to that in the post. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flassoan%2FSlicerSegmentEditorExtraEffects%2Fpull%2F19%3Femail_source%3Dnotifications%26email_token%3DAFCMSFE2ZO47I3OSLEBEF6LP2EBTFA5CNFSM4HPVO5S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQTLDQ%23issuecomment-501298574&data=02|01||a9449c8bd46748b176a708d6ef4207b8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636959464201187150&sdata=yT5AqITt2YPAduj318Z1gltBosg8Y7OQChiFrxDl6Rk%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFCMSFDC3CQSZKXB6UCLF7TP2EBTFANCNFSM4HPVO5SQ&data=02|01||a9449c8bd46748b176a708d6ef4207b8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636959464201187150&sdata=AAFmTMHlGXkh6C42OzThGloJKckulDO2EgLqmzscqzw%3D&reserved=0.

Take your time, it is not urgent for me at all.


[Request] Use facades instead of raw Stripe classes

I've recently integrated the Cashier package into a project I'm working on and testing has become somewhat more complicated and constrained since. A lot of this is due to the fact that a test that involves the billing system and the user model will make actual calls to the Stripe API. Whilst this is okay for integration tests, it really slows down unit tests.
I suggest that instead of using the raw Stripe classes from the the Stripe package that instead facades be created and that those be used instead. The facades don't really have to do much other than pass on function calls but will allow for mocking using existing Laravel testing aids which will make testing much easier.

No plans for this at the moment.


fix this._super call in x-option

Gotta pass this when using .apply.

@Robdel12 Why didn't our test suite catch this?

No clue, also didn't even show up until @cafreeman / @tehviking were trying to use propTypes with x-select.


Update add-ssr schematics for 2.0/ng9

We need adjust our templates to use @nguniversalengine v.9 and Ivy

QA steps:

go to schematics folder
remove node_modules and run yarn to get latest libs
build schematics locally (projects/schematics -> yarn build && npm pack)
in any other folder, create clean angular app
apply your locally built schematics (ng add <path_to_tgz_file> --ssr) SSR mode is very important here
remember to supply occBaseUrl in environments.prod.ts
build app for SSR and serve an app

Expected results:

the application should launch smoothly in SSR mode


Make Node 6 precompiled binaries for all existing Node 4 precompiled binaries

Blocked by https://github.com/tessel/t2-compiler/issues/32
Blocked by https://github.com/tessel/t2-compiler/issues/33
Blocks https://github.com/tessel/t2-firmware/issues/206

:clap:

:+1:


Support glslify

Hi, I am using vscode-glsllint with code that requires functions with glslify. For example, I have the following:
#pragma glslify: random = require(glsl-random);

float f(vec2 p) {
  return random(p);
}

With this, I have the messages 'random' : no matching overloaded function found and '' : compilation terminated, both at line return random(p);.
Note that, as a consequence that compilation terminated, all the errors after that line are missed.
Is there any way to use the plugin with glslify?

The problem is, that glslangValidator only supports compatible files and glslify is like a preprocessor format for glsl, it is not a valid syntax for glsl.
To support glslify, the shaderfile must be preprocessed via glslify and then send to the glslangValidator.
I can imagine to implement this in the future...

Thanks, that would be really useful!

glslify is now supported


calico-node fail to run on Kubernetes 1.29 (calico-typha error)

Expected Behavior
calico-node should run after fresh tigera-operator on-prem deployment on Kubernetes 1.29
Current Behavior
calico-node fails to run due to readiness probe error:
calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused
I can't perform kubectl logs but looking through crictl logs on the container I see the following:
2024-01-29 10:50:22.296 [INFO][199362] tunnel-ip-allocator/discovery.go 179: Creating Kubernetes client for Typha discovery...
2024-01-29 10:50:22.296 [INFO][199362] tunnel-ip-allocator/discovery.go 195: (Re)discovering Typha endpoints using the Kubernetes API...
2024-01-29 10:50:22.303 [ERROR][199362] tunnel-ip-allocator/discovery.go 235: Didn't find any ready Typha instances.
2024-01-29 10:50:22.303 [FATAL][199362] tunnel-ip-allocator/startsyncerclient.go 49: Typha discovery enabled but discovery failed. error=Kubernetes service missing IP or port

Inside calico-typha logs I see the below warnings after the readiness heathcheck:
2024-01-29 08:26:17.901 [INFO][8] health.go 336: Overall health status changed: live=true ready=true
+----------------------------+---------+----------------+-----------------+--------+
|         COMPONENT          | TIMEOUT |    LIVENESS    |    READINESS    | DETAIL |
+----------------------------+---------+----------------+-----------------+--------+
| SyncServer                 | 20s     | reporting live | -               |        |
| bgp-cache                  | 20s     | reporting live | reporting ready |        |
| felix-cache                | 20s     | reporting live | reporting ready |        |
| node-status-cache          | 20s     | reporting live | reporting ready |        |
| tunnel-ip-allocation-cache | 20s     | reporting live | reporting ready |        |
+----------------------------+---------+----------------+-----------------+--------+
2024-01-29 08:26:48.559 [WARNING][8] rebalance.go 54: Failed to get number of Typhas error=<nil> numTyphas=0 thread="k8s-poll"
2024-01-29 08:27:18.599 [WARNING][8] rebalance.go 54: Failed to get number of Typhas error=<nil> numTyphas=0 thread="k8s-poll"

While normally I would expect to see something like sync_server.go 430: Accepted from <IP_ADDRESS>:47314 port=5473
Possible Solution
N/A
Steps to Reproduce (for bugs)

Deploy on-prem EKS-D 1.29-3 (basically kubeadm-based Kubernetes 1.29.0)
Deploy the tigera-operator
Use the below installation spec to deploy calico

Context
Trying to deploy Calico on on-prem kubeadm-based deployment of EKS-D 1.29 using the tigera-operator per the documentation.
Same configuration works fine on EKS-D 1.28, and also when adding an 1.29 worker node to an exiting 1.28 control-plane which is already running Calico..
Worth mentioning while the official documentation does not state Calico supports Kubernetes 1.29, it seems like people are using it in practice and the documentation even reference an issue with the nftables alpha feature of 1.29 (off by default).
Your Environment

Calico version 3.27.0
Orchestrator version (e.g. kubernetes, mesos, rkt): EKS-D 1.29-3 (Kubernetes 1.29.0)
Operating System and version:  Ubuntu 22.04.3 LTS (kernel 5.15.0-92-generic)
Tigera operator installation resource used:apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  # Configures Calico networking.
  calicoNetwork:
    bgp: Enabled
    # Note: The ipPools section cannot be modified post-install.
    ipPools:
    - blockSize: 26
      cidr: <IP_ADDRESS>/16
      encapsulation: IPIP
      natOutgoing: Enabled
      nodeSelector: all()

Hi @rrsela, do you have multiple network interfaces? You could configure IP auto-detection https://docs.tigera.io/calico/latest/networking/ipam/ip-autodetection

Hi @MichalFupso  - doesn't seem to help, at least I tried kubernetes-internal-ip but in any case I only got a single interface:
root@k8s-master-1:/home/ubuntu# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:5b:d9:16 brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    inet <IP_ADDRESS>/23 metric 100 brd <IP_ADDRESS> scope global dynamic ens3
       valid_lft 3455sec preferred_lft 3455sec
    inet6 fe80::f816:3eff:fe5b:d916/64 scope link
       valid_lft forever preferred_lft forever

This sounds like Typha isn't reporting ready, and so calico/node isn't able to find a valid instance to connect to. Do your typha pods report ready in the k8s API?

@caseydavenport they report as ready (probably as the health check passes):
root@k8s-master-1:/home/ubuntu# kubectl get pods -n calico-system -o wide
NAME                                       READY   STATUS    RESTARTS   AGE   IP             NODE           NOMINATED NODE   READINESS GATES
calico-kube-controllers-6ff5954966-zh929   0/1     Pending   0          10m   <none>         <none>         <none>           <none>
calico-node-5f9g2                          0/1     Running   0          10m   <none>         k8s-master-1   <none>           <none>
calico-node-6ncbj                          0/1     Running   0          10m   <none>         k8s-worker-1   <none>           <none>
calico-typha-75b899457d-cj2vz              1/1     Running   0          10m   <none>         k8s-worker-1   <none>           <none>
csi-node-driver-bgptp                      2/2     Running   0          10m   <IP_ADDRESS>   k8s-worker-1   <none>           <none>
csi-node-driver-zbl62                      2/2     Running   0          10m   <IP_ADDRESS>   k8s-master-1   <none>           <none>

root@k8s-master-1:/home/ubuntu# kubectl get events -n calico-system --field-selector involvedObject.name=calico-typha-75b899457d-cj2vz
LAST SEEN   TYPE     REASON      OBJECT                              MESSAGE
10m         Normal   Scheduled   pod/calico-typha-75b899457d-cj2vz   Successfully assigned calico-system/calico-typha-75b899457d-cj2vz to k8s-worker-1
10m         Normal   Pulling     pod/calico-typha-75b899457d-cj2vz   Pulling image "docker.io/calico/typha:v3.27.0"
10m         Normal   Pulled      pod/calico-typha-75b899457d-cj2vz   Successfully pulled image "docker.io/calico/typha:v3.27.0" in 8.84s (8.84s including waiting)
10m         Normal   Created     pod/calico-typha-75b899457d-cj2vz   Created container calico-typha
10m         Normal   Started     pod/calico-typha-75b899457d-cj2vz   Started container calico-typha

What does kubectl get endpoints say for the Typha service?  Felix queries the service and then picks a Typha to connect to based on that.

@matthewdupre it has none:
kubectl get endpoints -n calico-system
NAME           ENDPOINTS   AGE
calico-typha   <none>      10m

@rrsela Yeah, that would cause this.  Looking more carefully, I see kubectl is reporting IP  for Typha (and kube-controllers doesn't even have a NODE?!).
Normally you'd see the node IP appearing for Typha (and Calico-Node) and then everything else will probably work normally.  The question now is "how is Typha running without Kubernetes knowing its IP?"

Trying to run Typha in debug mode and failing to do so in operator-mode... But it made me think, could this be a Tigera issue? All I can see inside its log is repeating info & error messages regarding installation reconciliation:
{"level":"info","ts":"2024-03-07T06:34:57Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-03-07T06:34:57Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-03-07T06:34:58Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"periodic-5m0s-reconcile-event"}
{"level":"info","ts":"2024-03-07T06:34:58Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"tigera-operator","Request.Name":"tigera-ca-private"}
{"level":"info","ts":"2024-03-07T06:34:58Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"calico-system"}
{"level":"info","ts":"2024-03-07T06:34:59Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"default"}
{"level":"info","ts":"2024-03-07T06:34:59Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"active-operator"}
{"level":"info","ts":"2024-03-07T06:34:59Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"tigera-operator","Request.Name":"node-certs"}
{"level":"info","ts":"2024-03-07T06:35:00Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"tigera-operator","Request.Name":"typha-certs"}
{"level":"info","ts":"2024-03-07T06:35:00Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"calico-typha"}
{"level":"info","ts":"2024-03-07T06:35:01Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"calico-node"}
{"level":"info","ts":"2024-03-07T06:35:01Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"calico-node"}
{"level":"info","ts":"2024-03-07T06:35:01Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"calico-cni-plugin"}
{"level":"info","ts":"2024-03-07T06:35:02Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"calico-cni-plugin"}
{"level":"info","ts":"2024-03-07T06:35:02Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"csi-node-driver"}
{"level":"info","ts":"2024-03-07T06:35:02Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"calico-system","Request.Name":"calico-kube-controllers"}
{"level":"info","ts":"2024-03-07T06:35:03Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"calico-kube-controllers"}
{"level":"info","ts":"2024-03-07T06:35:27Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"calico"}
{"level":"info","ts":"2024-03-07T06:35:27Z","logger":"controller_windows","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-03-07T06:35:27Z","logger":"controller_apiserver","msg":"Reconciling APIServer","Request.Namespace":"","Request.Name":"default"}
{"level":"error","ts":"2024-03-07T06:35:27Z","logger":"controller_apiserver","msg":"Waiting for Installation to be ready","Request.Namespace":"","Request.Name":"default","reason":"ResourceNotReady","stacktrace":"github.com/tigera/operator/pkg/controller/status.(*statusManager).SetDegraded\n\t/go/src/github.com/tigera/operator/pkg/controller/status/status.go:356\ngithub.com/tigera/operator/pkg/controller/apiserver.(*ReconcileAPIServer).Reconcile\n\t/go/src/github.com/tigera/operator/pkg/controller/apiserver/apiserver_controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235"}
{"level":"info","ts":"2024-03-07T06:35:27Z","logger":"controller_installation","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"default"}

and kube-controllers doesn't even have a NODE?!

This makes sense - there are no nodes that Kubernetes deems acceptable for scheduling pods yet, so it hasn't been assigned one (note the "Pending" state)

The question now is "how is Typha running without Kubernetes knowing its IP?"

Yeah, this is strange, and suggests perhaps a problem with kubelet (who reports that IP address) or with the Node objects themselves - maybe check to see if kubectl get nodes lists Node IPs for your nodes? Bit of a long-shot, considering the csi daemonset is showing a pod IP:

csi-node-driver-bgptp                      2/2     Running   0          10m   <IP_ADDRESS>   k8s-worker-1

kubelet logs might explain more about why that pod has no IP...

Actually kubectl get nodes -owide does not show any IP:
root@k8s-master-1:/home/ubuntu# kubectl get nodes -owide
NAME           STATUS   ROLES           AGE     VERSION               INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
k8s-master-1   Ready    control-plane   6d12h   v1.29.0-eks-a5ec690   <none>        <none>        Ubuntu 22.04.3 LTS   5.15.0-92-generic   containerd://1.6.27
k8s-worker-1   Ready    <none>          6d12h   v1.29.0-eks-a5ec690   <none>        <none>        Ubuntu 22.04.3 LTS   5.15.0-92-generic   containerd://1.6.27

Although I do see the node's IP as a calico annotation:
root@k8s-master-1:/home/ubuntu# kubectl get node k8s-master-1 -oyaml
apiVersion: v1
kind: Node
metadata:
  annotations:
    csi.volume.kubernetes.io/nodeid: '{"csi.tigera.io":"k8s-master-1"}'
    kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock
    node.alpha.kubernetes.io/ttl: "0"
    projectcalico.org/IPv4Address: <IP_ADDRESS>/23
    projectcalico.org/IPv4IPIPTunnelAddr: <IP_ADDRESS>
    volumes.kubernetes.io/controller-managed-attach-detach: "true"

While on an 1.28 node I would get the node status' address attributes like these:
status:
  - address: XXX.XXX.XXX.XXX
    type: InternalIP
  - address: YYY
    type: InternalDNS
  - address: ZZZ
    type: Hostname

On the 1.29 node I don't see it at all...
BTW nothing much on kubelet log regarding typha itself:
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: I0311 19:17:14.064587    3912 topology_manager.go:215] "Topology Admit Handler" podUID="5fa6488f-3de6-45ea-84a8-1f86c525934a" podNamespace="calico-system" podName="calico-typha-6f4997b5f5-xm5sq"
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: E0311 19:17:14.065560    3912 cpu_manager.go:395] "RemoveStaleState: removing container" podUID="d6542f81-a511-4f6e-b4df-815443d49ce2" containerName="calico-typha"
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: I0311 19:17:14.066887    3912 memory_manager.go:354] "RemoveStaleState removing state" podUID="d6542f81-a511-4f6e-b4df-815443d49ce2" containerName="calico-typha"
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: I0311 19:17:14.190784    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"typha-certs\" (UniqueName: \"kubernetes.io/secret/5fa6488f-3de6-45ea-84a8-1f86c525934a-typha-certs\") pod \"calico-typha-6f4997b5f5-xm5sq\" (UID: \"5fa6488f-3de6-45ea-84a8-1f86c525934a\") " pod="calico-system/calico-typha-6f4997b5f5-xm5sq"
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: I0311 19:17:14.190909    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"kube-api-access-7wrc7\" (UniqueName: \"kubernetes.io/projected/5fa6488f-3de6-45ea-84a8-1f86c525934a-kube-api-access-7wrc7\") pod \"calico-typha-6f4997b5f5-xm5sq\" (UID: \"5fa6488f-3de6-45ea-84a8-1f86c525934a\") " pod="calico-system/calico-typha-6f4997b5f5-xm5sq"
Mar 11 19:17:14 k8s-master-1 kubelet[3912]: I0311 19:17:14.191161    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"tigera-ca-bundle\" (UniqueName: \"kubernetes.io/configmap/5fa6488f-3de6-45ea-84a8-1f86c525934a-tigera-ca-bundle\") pod \"calico-typha-6f4997b5f5-xm5sq\" (UID: \"5fa6488f-3de6-45ea-84a8-1f86c525934a\") " pod="calico-system/calico-typha-6f4997b5f5-xm5sq"
Mar 11 19:17:15 k8s-master-1 kubelet[3912]: I0311 19:17:15.929907    3912 pod_startup_latency_tracker.go:102] "Observed pod startup duration" pod="calico-system/calico-typha-6f4997b5f5-xm5sq" podStartSLOduration=1.9298010909999999 podStartE2EDuration="1.929801091s" podCreationTimestamp="2024-03-11 19:17:14 +0000 UTC" firstStartedPulling="0001-01-01 00:00:00 +0000 UTC" lastFinishedPulling="0001-01-01 00:00:00 +0000 UTC" observedRunningTime="2024-03-11 19:17:15.879945351 +0000 UTC m=+563260.200073104" watchObservedRunningTime="2024-03-11 19:17:15.929801091 +0000 UTC m=+563260.249928874"

Regarding the csi-node-driver, the kubelet log shows (plus some other pod's entries):
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.744381    3912 topology_manager.go:215] "Topology Admit Handler" podUID="11cfd63c-092c-4315-bf58-76d941895d82" podNamespace="calico-system" podName="calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: E0311 19:26:13.749062    3912 cpu_manager.go:395] "RemoveStaleState: removing container" podUID="be862780-8ea7-45df-99df-144baa14d087" containerName="calico-node"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: E0311 19:26:13.749785    3912 cpu_manager.go:395] "RemoveStaleState: removing container" podUID="be862780-8ea7-45df-99df-144baa14d087" containerName="install-cni"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: E0311 19:26:13.750159    3912 cpu_manager.go:395] "RemoveStaleState: removing container" podUID="be862780-8ea7-45df-99df-144baa14d087" containerName="flexvol-driver"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.750775    3912 memory_manager.go:354] "RemoveStaleState removing state" podUID="be862780-8ea7-45df-99df-144baa14d087" containerName="calico-node"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.838450    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"flexvol-driver-host\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-flexvol-driver-host\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.838908    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"policysync\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-policysync\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.839130    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-bin-dir\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-cni-bin-dir\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.839438    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"lib-modules\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-lib-modules\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.839745    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"tigera-ca-bundle\" (UniqueName: \"kubernetes.io/configmap/11cfd63c-092c-4315-bf58-76d941895d82-tigera-ca-bundle\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.839989    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-log-dir\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-cni-log-dir\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.840256    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"cni-net-dir\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-cni-net-dir\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.840589    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"xtables-lock\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-xtables-lock\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.840868    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"var-lib-calico\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-var-lib-calico\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.841099    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"kube-api-access-84lqc\" (UniqueName: \"kubernetes.io/projected/11cfd63c-092c-4315-bf58-76d941895d82-kube-api-access-84lqc\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.841347    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"node-certs\" (UniqueName: \"kubernetes.io/secret/11cfd63c-092c-4315-bf58-76d941895d82-node-certs\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.841695    3912 reconciler_common.go:258] "operationExecutor.VerifyControllerAttachedVolume started for volume \"var-run-calico\" (UniqueName: \"kubernetes.io/host-path/11cfd63c-092c-4315-bf58-76d941895d82-var-run-calico\") pod \"calico-node-sjqtf\" (UID: \"11cfd63c-092c-4315-bf58-76d941895d82\") " pod="calico-system/calico-node-sjqtf"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: I0311 19:26:13.895814    3912 scope.go:117] "RemoveContainer" containerID="45d0088dfc5c23ef6a7024d2768af1a3f0614238542f995730d3ff7286401104"
Mar 11 19:26:13 k8s-master-1 kubelet[3912]: E0311 19:26:13.896927    3912 pod_workers.go:1298] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"aws-cloud-controller-manager\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=aws-cloud-controller-manager pod=aws-cloud-controller-manager-4tsfg_kube-system(6af95188-e1cc-476c-a33b-9046efd953c9)\"" pod="kube-system/aws-cloud-controller-manager-4tsfg" podUID="6af95188-e1cc-476c-a33b-9046efd953c9"
Mar 11 19:26:15 k8s-master-1 kubelet[3912]: I0311 19:26:15.902932    3912 kubelet_volumes.go:161] "Cleaned up orphaned pod volumes dir" podUID="be862780-8ea7-45df-99df-144baa14d087" path="/var/lib/kubelet/pods/be862780-8ea7-45df-99df-144baa14d087/volumes"
Mar 11 19:26:19 k8s-master-1 kubelet[3912]: I0311 19:26:19.272500    3912 scope.go:117] "RemoveContainer" containerID="3d494b7c6300d707b53295cf31f43ed1dc70acf8f3d9ad95c0f56a47b7b963e2"
Mar 11 19:26:19 k8s-master-1 kubelet[3912]: I0311 19:26:19.273319    3912 scope.go:117] "RemoveContainer" containerID="92c9dbf840aabc7d8aefd3e1c963076ff0aa09df6db6ca7270c8fecdbc2dcd64"
Mar 11 19:26:19 k8s-master-1 kubelet[3912]: I0311 19:26:19.273620    3912 scope.go:117] "RemoveContainer" containerID="24455c7b0250b18577f095c1c9db842e732b40abc08b4610fecd1cd0211e98e6"
Mar 11 19:26:19 k8s-master-1 kubelet[3912]: E0311 19:26:19.274519    3912 pod_workers.go:1298] "Error syncing pod, skipping" err="[failed to \"StartContainer\" for \"ebs-plugin\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=ebs-plugin pod=ebs-csi-node-zlrmm_kube-system(d95b1805-89de-4aee-9ccd-e504b705f301)\", failed to \"StartContainer\" for \"node-driver-registrar\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=node-driver-registrar pod=ebs-csi-node-zlrmm_kube-system(d95b1805-89de-4aee-9ccd-e504b705f301)\", failed to \"StartContainer\" for \"liveness-probe\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=liveness-probe pod=ebs-csi-node-zlrmm_kube-system(d95b1805-89de-4aee-9ccd-e504b705f301)\"]" pod="kube-system/ebs-csi-node-zlrmm" podUID="d95b1805-89de-4aee-9ccd-e504b705f301"
Mar 11 19:26:19 k8s-master-1 kubelet[3912]: I0311 19:26:19.636820    3912 pod_startup_latency_tracker.go:102] "Observed pod startup duration" pod="calico-system/calico-node-sjqtf" podStartSLOduration=6.63677307 podStartE2EDuration="6.63677307s" podCreationTimestamp="2024-03-11 19:26:13 +0000 UTC" firstStartedPulling="0001-01-01 00:00:00 +0000 UTC" lastFinishedPulling="0001-01-01 00:00:00 +0000 UTC" observedRunningTime="2024-03-11 19:26:19.636251089 +0000 UTC m=+563803.956378821" watchObservedRunningTime="2024-03-11 19:26:19.63677307 +0000 UTC m=+563803.956900783"

@rrsela I am not entirely sure why that is, but it seems likely that the missing node IPs are causing this issue with Calico. I'd recommend investigating why those IPs stopped showing up in your environment.

@caseydavenport the thing is the same setup work with Flannel or Cilium, but not with Calico...
For example with Flannel:
root@demo-master-1:/# kubectl get nodes -owide
NAME            STATUS   ROLES           AGE     VERSION               INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
demo-master-1   Ready    control-plane   4m41s   v1.29.0-eks-a5ec690   <IP_ADDRESS>   <none>        Ubuntu 22.04.3 LTS   5.15.0-92-generic   containerd://1.6.27
demo-worker-1   Ready    <none>          4m22s   v1.29.0-eks-a5ec690   <IP_ADDRESS>    <none>        Ubuntu 22.04.3 LTS   5.15.0-92-generic   containerd://1.6.27

root@demo-master-1:/# kubectl get node demo-master-1 -oyaml
apiVersion: v1
kind: Node
metadata:
  annotations:
    csi.volume.kubernetes.io/nodeid: '{"ebs.csi.aws.com":"i-2a80c38632a34a80abcb2a4f55b275d3"}'
    flannel.alpha.coreos.com/backend-data: '{"VNI":1,"VtepMAC":"42:42:55:8f:b6:41"}'
    flannel.alpha.coreos.com/backend-type: vxlan
    flannel.alpha.coreos.com/kube-subnet-manager: "true"
    flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
    kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock
    node.alpha.kubernetes.io/ttl: "0"
    volumes.kubernetes.io/controller-managed-attach-detach: "true"
...
status:
  addresses:
  - address: <IP_ADDRESS>
    type: InternalIP
  - address: demo-master-1.symphony.local
    type: InternalDNS
  - address: demo-master-1.symphony.local
    type: Hostname
...

@rrsela do your nodes show Internal IPs prior to installing a CNI plugin?
I'm a little bit stumped about why this would have anything to do with Calico, since Calico doesn't actually modify the IP addresses of the nodes.

@caseydavenport I validated that the nodes do not have internal IPs prior to the CNI installation (also checked with Flannel to be sure) - seems like this field is being populated following the CNI deployment as part of the node status update, or at least its not there as long as the node has a KubeletNotReady condition due to missing CNI... Once Flannel was installed I got the internal IP, but not with Calico.

Based on the above I managed to replicate the issue with vanilla Kubernetes and not just EKS-D - as long as Kubelet is defined with --cloud-provider=external (so the CCM handles the node IP post CNI deployment) Typha is unable to get it (as it runs before the CCM can run) and calico-node fails to use it...
Not sure how/why it works on 1.28 though, maybe some internal cloud-provider code removals?

Interesting - does the external cloud provider CCM pod run with host networking or with pod networking?

@caseydavenport it runs with pod networking - at least the AWS cloud controller manager is..
BTW I found the 1.29 change regarding the default node IP behaviour - until this PR was merged nodes always had IPs even prior to the cloud provider (CCM) deployment...

Ok, so it sounds like because of that change nodes are not getting temporary IP addresses, which prevents calico/node from talking to the apiserver via Typha.
Since calico/node can't talk to Typha, pods never get networking and thus the external CCM isn't able to start, and we are in a deadlock situation.
These are the options that jump out at me, none of which are super appealing or necessarily a quick fix:

EKS needs to configure or expose the --node-ip option in order to maintain the older behavior as described in the linked PR.
The CCM needs to run with hostNetwork: true so that it isn't dependent on pod networking.
Calico needs reimplement the functionality that was removed as part of https://github.com/kubernetes/kubernetes/pull/121028 itself.

@rrsela I am closing it now, but feel free to reopen if you have any new information


[operator] manager.targetAllocatorImage.tag non-empty default value

Hello Team!
I want to mirror image repositories in order to avoid rate limt of DockerHub and/or ghcr.
On the other hand, I do not want to specify image tags for brevity.
Specifying both chart version and image tags is redundant.
helm install ... --set manager.collectorImage.repository=<mirror repo> # specifies only repository, NOT tag

This kind of installation works fine for operator and collector images because manager.image.tag and manager.collectorImage.tag has non-empty default value.
However, not working for target allocator image because manager.targetAllocatorImage.tag does not have non-empty default value.
https://github.com/open-telemetry/opentelemetry-helm-charts/blob/6a85b2d3f23d4f0bf79765e54c52199109a38a09/charts/opentelemetry-operator/values.yaml#L30-L38
https://github.com/open-telemetry/opentelemetry-helm-charts/blob/6a85b2d3f23d4f0bf79765e54c52199109a38a09/charts/opentelemetry-operator/templates/deployment.yaml#L49-L51
Therefore I want manager.targetAllocatorImage.tag to have non-empty default value like manager.image.tag or manager.collectorImage.tag.
Thanks!

Yes we can provide a default value for these, although instead of specifying the image version in the values.yaml we should really be using the appVersion.


Suggestion for another utility method

Paul Withers [3:46 PM]
How do you get the view SSJS variable in Java? Is there an easy helper method (and if using resolveVariable() what class do you cast to?)
I can't see anything obvious under ExtLibUtil
Jesse Gallagher [3:46 PM]
UIViewRoot is the base one, UIViewRootEx2 is the most specific
David Leedy [3:47 PM]
jesse has a method in his framework
Jesse Gallagher [3:47 PM]
I just use resolveVariable, and keep around a helper method in FrameworkUtils, yeah
Paul Withers [3:47 PM]
Well why haven't you submitted it to ExtLib? :smiling_imp:
David Leedy [3:47 PM]
public static UIViewRootEx2 getViewRoot() {
return (UIViewRootEx2) resolveVariable("view");
}

Feature added in ExtLib release 17


Create demos in katacoda for Move2Kube

Is your feature request related to a problem? Please describe.
For demonstrating to users capabilities of Move2Kube a demo in katacoda (https://www.katacoda.com/) will help.
Describe the solution you'd like
For each of the tutorials in konveyor.io, have a corresponding demo in https://www.katacoda.com/
Describe alternatives you've considered
Demos in konveyor.io

First flow is up in https://katacoda.com/move2kube. More will be added over time.
https://github.com/konveyor/move2kube-katacoda/pull/3