Cannot read properties of null (reading 'useRef')

Not sure this is the correct place to ask, but I have some issues with using Moti when building both to simulator and to real device.
Specs:

MacBook Pro 2021 (M1 processor)
React: 17.0.2
React Native: 0.66.0
Moti: 0.17.1

The app crashes with an error saying:

"Cannot read properties of null (reading 'useRef')"
"Cannot read properties of null (reading 'useContext')"

It seems to be related to AnimatePresence. When looking into the code it seems like it's coming from:
<EMAIL_ADDRESS>(Row: 1623)
Worth mentioning is that it work for me previously, but I did a clean install of the repo and since then this issue keeps occuring.
Tried what I could think of:

rm -rf node_modules/
pod deintegrate
npm i
pod install
Making sure that all metro bundlers are closed
Clean build folder
Turning of remote debugging
npm cache clear --force
npm start

a few questions. are you in a monorepo? do you have multiple versions of react installed?
try running yarn why react

Absolutely, here it is:

a few questions. are you in a monorepo? do you have multiple versions of react installed?
try running yarn why react

This is the following response when I run "yarn why react":
`
<EMAIL_ADDRESS>peer
node_modules/@motify/core/node_modules/react
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/framer-motion
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/components
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/react-dom
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/framer-motion
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/components
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>peer
node_modules/@ui-kitten/eva-icons/node_modules/react
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons/node_modules/react-native-eva-icons
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>node_modules/react
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@papercups-io/chat-widget-native
<EMAIL_ADDRESS>from the root project
peer react@"16 || 17" from<EMAIL_ADDRESS>node_modules/@react-native-community/cameraroll
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/hooks
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@fullstackcraft/react-native-keyboard-shift
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-native-firebase/app
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-firebase/messaging
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0" from<EMAIL_ADDRESS>node_modules/mini-create-react-context
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-freeze
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@notifee/react-native
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@papercups-io/chat-widget-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| 0.60 - 0.68 || 1000.0.0" from<EMAIL_ADDRESS>node_modules/@react-native-async-storage/async-storage
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/cameraroll
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-native-community/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/hooks
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@fullstackcraft/react-native-keyboard-shift
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-native-firebase/app
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-firebase/messaging
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-contacts
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-device-info
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-fast-image
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-gesture-handler
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@">= 0.59" from<EMAIL_ADDRESS>node_modules/react-native-google-places-autocomplete
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-image-picker
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-image-resizer
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-iphone-x-helper
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-keyboard-aware-scroll-view
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-keyboard-aware-scroll-view
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-linear-gradient
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-permissions
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-quick-base64
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-safe-area-context
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-svg
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/components
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-webview
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/react-native-fast-image
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-gesture-handler
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-image-picker
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-permissions
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-quick-base64
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-safe-area-context
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-svg
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/components
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react@"*" from<EMAIL_ADDRESS>node_modules/react-native-webview
<EMAIL_ADDRESS>from the root project
peer react@">=15" from<EMAIL_ADDRESS>node_modules/react-router
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer react@">=15" from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/react-shallow-renderer
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-test-renderer
dev<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-test-renderer
dev<EMAIL_ADDRESS>from the root project
niklasliljendahl@MacBook-Pro-som-tillhor-Niklas ios % npm install --global yarn
niklasliljendahl@MacBook-Pro-som-tillhor-Niklas ios % cd ..
niklasliljendahl@MacBook-Pro-som-tillhor-Niklas jippoo % npm install --global yarn
added 1 package, and audited 2 packages in 1s
found 0 vulnerabilities
niklasliljendahl@MacBook-Pro-som-tillhor-Niklas jippoo % npm why react
<EMAIL_ADDRESS>peer
node_modules/@motify/core/node_modules/react
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/framer-motion
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/components
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/react-dom
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/@motify/core/node_modules/framer-motion
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@motify/components
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/moti
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>peer
node_modules/@ui-kitten/eva-icons/node_modules/react
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons/node_modules/react-native-eva-icons
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>node_modules/react
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@papercups-io/chat-widget-native
<EMAIL_ADDRESS>from the root project
peer react@"16 || 17" from<EMAIL_ADDRESS>node_modules/@react-native-community/cameraroll
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/hooks
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@fullstackcraft/react-native-keyboard-shift
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-native-firebase/app
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-firebase/messaging
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/core
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0" from<EMAIL_ADDRESS>node_modules/mini-create-react-context
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-freeze
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@notifee/react-native
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@papercups-io/chat-widget-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| 0.60 - 0.68 || 1000.0.0" from<EMAIL_ADDRESS>node_modules/@react-native-async-storage/async-storage
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/cameraroll
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-native-community/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-community/hooks
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@fullstackcraft/react-native-keyboard-shift
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-native-firebase/app
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-native-firebase/messaging
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-contacts
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-device-info
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-fast-image
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-gesture-handler
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@">= 0.59" from<EMAIL_ADDRESS>node_modules/react-native-google-places-autocomplete
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-image-picker
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-image-resizer
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-iphone-x-helper
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-keyboard-aware-scroll-view
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-keyboard-aware-scroll-view
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-linear-gradient
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-permissions
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-quick-base64
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-safe-area-context
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-svg
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/components
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react-native@"" from<EMAIL_ADDRESS>node_modules/react-native-webview
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/react-native-fast-image
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-gesture-handler
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react-native-gesture-handler@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-image-picker
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-permissions
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-quick-base64
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-safe-area-context
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/elements
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react-native-safe-area-context@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-screens
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/bottom-tabs
<EMAIL_ADDRESS>from the root project
peer react-native-screens@">= 3.0.0" from<EMAIL_ADDRESS>node_modules/@react-navigation/native-stack
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-reanimated
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-redash
<EMAIL_ADDRESS>from the root project
peer react@"" from<EMAIL_ADDRESS>node_modules/react-native-svg
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/components
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer react-native-svg@"" from<EMAIL_ADDRESS>node_modules/@ui-kitten/eva-icons
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-native-countdown-circle-timer
<EMAIL_ADDRESS>from the root project
peer react@"*" from<EMAIL_ADDRESS>node_modules/react-native-webview
<EMAIL_ADDRESS>from the root project
peer react@">=15" from<EMAIL_ADDRESS>node_modules/react-router
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer react@">=15" from<EMAIL_ADDRESS>node_modules/react-router-native
<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>node_modules/react-shallow-renderer
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-test-renderer
dev<EMAIL_ADDRESS>from the root project
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-test-renderer
dev<EMAIL_ADDRESS>from the root project
`

Yeah I see. So your version of npm automatically installs peer deps. if you use the npm legacy peer deps feature it should fix it. or, set a resolution of react to 17.0.2 inside or your package.json.
Plainly, you should only use one version. Using yarn would also solve this.

Yeah I see. So your version of npm automatically installs peer deps. if you use the npm legacy peer deps feature it should fix it. or, set a resolution of react to 17.0.2 inside or your package.json.
Plainly, you should only use one version. Using yarn would also solve this.

I'll try with using Yarn instead!
But when you say set a resolution of react inside the package.json, do you mean specify the version explicitly or are there any other way of "set a resolution of react to 17.0.2"?

Managed to get it to work with:
npm i --legacy-peer-deps
Thanks a lot!

Keystone requires a higher version of Next.js, specifically version 13.3 or above. If you encounter an error, please make sure to use at least this version. To fix the issue, you can add the following code to your package.json file:
"resolutions": {
  "next": "~13.3.0"
}

By adding this code, you're specifying a resolution to use Next.js version 13.3.0 or a compatible version. This can help resolve the problem you're facing. Make sure to save the package.json file after making this change.


Add label filter for antrea-ci garbage cleanup job

The script in #1377 cleans up too much namespaces, including those related to CAPV (Cluster API Provider vSphere). This PR fixes this bug by adding a label filter to the current kubectl get ns command.

/skip-all


check the return value of EVP_MD_fetch in ecdh_exch.c & dh_exch.c

Check the return value of EVP_MD_fetch in ecdh_exch.c:285 & dh_exch.c:347.

Changed them. However, I still think that although there may be some checks that occur far in the following functions, it is a better habit to check immediately for memory allocation functions as some context relationships are easier omitted during maintenance in the future. By checking in time, we do not need to worry whether the subsequent functions have validity checks.

Sorry, I misunderstood. I should not refactor like the last commit as there are several if statements in ossl_digest_is_allowed(). If # if !defined(OPENSSL_NO_FIPS_SECURITYCHECKS) or if (ossl_securitycheck_enabled(ctx)) does not satisfy, pdhctx->kdf_md would not be checked inside ossl_digest_is_allowed().
And current commit seems to be the version commented by @t8m. I kept the check before the call to ossl_digest_is_allowed(), so we can easier know where and why returns 0.

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This pull request is ready to merge

Squashed and merged to master branch. Thank you for your contribution.


Rename subscription resource

Although it seems to me that subscription resource is a long used and pretty set in stone term,
I would like point out that the naming may be confusing:
From the term alone, one could get the idea that a subscription resource is a resource whose representation describes a subscription. Especially, when modelling the resource where requests are submitted to as a container (#36), or even more, when considering materializing requests for subscriptions in such a container.
In my mind, what is currently referred to as a subscription resource is a resource whose representation describes a service that provides the subscription/notification functionalities. (independent of that resource being also a container or can be POSTed to)
Thus, I would like to propose the terms subscription service resource which is described by its subscription service representation.

The notion of container is not part of Solid Notifications Protocol. "Resources" all the way down.
The subscription request (POST) and the response representations use the notification-channel-data-model and relevant notification-channel-types data model.
I don't have a strong opinion on re-naming, i.e., whether to use subscription resource or subscription service or subscription service resource. I would just say that the spec currently uses:

topic resource
description resource
subscription resource
notification channel

I find "resource" to be sufficient/simple. Notification channel may need to be referred as the notification channel resource, where applicable. Or, as you suggest, change subscription resource to subscription service resource.
Do others have thoughts/suggestions on this? We can still change / have more consistency.

Just to clearify, I do not take issue in the usage of the term resource but the ambiguity of the term subscription resource as it may be confused with a resource representing a subscription.
As the current notion of subscription resource refers to a resource where one can create/register a subscription via HTTP POST, I feel we could be more precise in terms of naming here.

I would second @uvdsl here. Furthermore, if we were to go down the container (containing resources for a subscription) route in the future, we would have the term "subscription resource" available to us.

My preference is "Subscription Service", which might then also be referred to as "Subscription Service Resource" where we need to make it explicit that we are referring to an HTTP resource.

I'd welcome renaming to "subscription service", but I propose an alternative view that can potentially tie up some loose ends:
The behaviour of subscription resource/service resembles a specialisation of LDN inbox with a particular data model. The inbox accepts subscription requests with optional features about a topic.
The request can be further specified with particular activity types (or shapes, see activityType proposal in https://github.com/solid/notifications/pull/147 ).
The inbox can contain accepted subscriptions. Subscriptions can be modified or removed (TBD with https://github.com/solid/notifications/issues/145 ).
While the minimal implementation of a Subscription Service need not have subscription resource be an inbox, it can certainly be extended in that way (re ldn-channel-2023). So, from ldn-channel-2023's point of view, the subscription resource/service thing is really a subscription inbox. notify:subscription need not be defined as a rdfs:subPropertyOf ldp:inbox either. Whether it is called service or inbox is perhaps minor/bikeshedding in the end.
If we introduce the notion where subscriptions (active notification channels) are identifiable units where they can be modified or removed for some (all?) channel types, there is not a whole lot difference from regular container/inbox behaviour. I think this actually ties up a bunch of our considerations, including https://github.com/solid/notifications/issues/36 .

I am ok with "Subscription Inbox", though it is weird to subscribe to an Inbox because Inboxes accept mail not generates a letter on a request for a mail.
To @udvsl's original point, subscription resource is too generic, can imply many things and is confusing. Alternatives that show the thing dispenses subscriptions are acceptable.

Renaming Subscription Resource to Subscription Service works for me me.
I'd like to know what @elf-pavlik @acoburn thinks about this proposal or have other thoughts.

https://github.com/solid/notifications/commit/edd6c91cea26af4547bfe7e23dbc7a4b7fa1aa3e closed this issue by renaming subscription resource to subscription service as per https://github.com/solid/notifications-panel/blob/main/meetings/2023-02-02.md#rename-subscription-resource-to-subscription-service .


Loosen nullability restrictions added in #3205 (#3226)

Which issue does this PR close?

Closes #3226
Rationale for this change

#3205 added restrictions to prevent nulls in non-nullable children of a StructArray. Whilst on the face of it this sounds sensible, the issue is that nulls in StructArray and FixedSizeListArray both take up space in their children. This leads to the question of "what value should the child have for a null in its parent". In the case of DictionaryArray there isn't a valid placeholder value that can be used, the value at a null index is undefined.
This PR works around this by loosening the restriction to allow a null in a non-nullable child array provided it corresponds to a null in the parent. This ensures that the children are valid, and can be safely interpreted outside the context of their parent, whilst also ensuring that the semantics of nullability are preserved.
What changes are included in this PR?

Are there any user-facing changes?

Thanks for this, looks like there was some nuance I missed in regards to nested types & nullability

Not at all, the ecosystem as a whole does not seem to handle this in a consistent manner. It certainly isn't documented :laughing:


IBAN.isValid ignores non-alphanumeric characters

E.g.
const notValidIban = 'DE893704 0044 0532 0130 __00^#&#*#*(#';

IBAN.isValid(notValidIban); // true

Looks like it considers only aphanumeric characters, here I have a valid iban, but polluted with special characters, and it's still treated as valid

Hello,
Thanks for the report.
Indeed, this is a duplicate of #35


Cannot read properties of undefined (reading 'importKey')

Cannot read properties of undefined (reading 'importKey')

#129


Confirm a PK is enrolled when checking secure boot state on linux systems

Previous check only verified that secure boot was enable in the EFI settings, not that the systems was booted with it.

/lgtm


Add verify documentation action

This is only to check it works. It will move to the project template after we have verified it works

Can this be closed now?

done


Record Voice of the User

I want to record every command which is being transcribed by annyang. Because i want to differentiate between two voices. Is it possible to get speaker id using annyang?

No, it is not. annyang uses the browser's built in speech recognition engine which only gives you access to the transcript of what was said


Text not showing correctly on Tests (Command Palete)

I have some unit tests on my python project. Whenever I run the tests on vs code and then I want to see the output, the text is squeezed together on the command palette. If I switch to another theme it works properly.
This bug also happens when I configure my tests to choose what test framework I want to work with.
I included attached screenshots to better understand the problem.

Here is the same bug in the configuration of test framework.

And here it's displayed correctly with another theme.

Yikes, that's no good. I'll fix it, though I'm low on time so will be at least a month or so. Also open to PRs.

No pressure! I will take a look tho I have never modified any theme


APK Tool 2.3.0 Not Working

I tried apktool d, apktool b without changing anything. And it gives me parse error while installing to Android device. The message "There was a problem parsing the package".

Thanks for the report! Unfortunately there isn't enough information for me to triage this issue properly. Please be sure to try and provide any logcat and/or stacktrace possible. I can reopen this if details are provided.


[WIP] Start working on object literals.

Only two forms work ATM:

{"a": 1}
{a}

(obviously, the empty object, {}, parses as well)

To do ASAP after merging this PR:

[ ] make sure property lookup works on objects constructed by object literals
[ ] make sure obj[key] lookup works on them, too
[ ] implement getprop, update, extend, and id properties
[ ] implement the Q::Identifier { ... } syntax
[ ] make sure it works on all the Q types
[ ] make sure Object { ... } works
[ ] remove the function constructors from the built-in functions
[ ] update the tutorial and web page

rebased once again

Ven: please review https://github.com/masak/007/commit/2fbc86aaee124c0ceb49f54f4adcf0509e062ead which is basically a squash of all the commits with various fixes/touch-ups/changes as per this backlog.
If you're fine with what's there, I will merge.

fd02a5b0bdab25c4daea2d77f458fa3354aad6ac


Singularity fails to build

Following up https://bitbucket.org/omuse/omuse/issues/19/singularity-recipe-fails-to-build
Installation progresses, but fails later on :
Building wheels for collected packages: mpi4py
  Building wheel for mpi4py (setup.py) ... done
  Created wheel for mpi4py: filename=mpi4py-3.0.3-cp36-cp36m-linux_x86_64.whl size=2550550 sha256=31350a25826377bd13c2d97a9256868749d407fad9577284353a37da614c9652
  Stored in directory: /root/.cache/pip/wheels/d6/73/83/ad9dd3ebae512829ab3f21657f76403dc4aa6649e1118c9369
Successfully built mpi4py
Installing collected packages: wheel, pluggy, more-itertools, py, pytest, amuse-framework, mpi4py, omuse
  Attempting uninstall: wheel
    Found existing installation: wheel 0.31.1
    Uninstalling wheel-0.31.1:
      Successfully uninstalled wheel-0.31.1
  Running setup.py develop for omuse
Successfully installed amuse-framework-13.2.1 more-itertools-8.4.0 mpi4py-3.0.3 omuse pluggy-0.13.1 py-1.9.0 pytest-5.4.3 wheel-0.34.2
+ python3 setup.py build_code --code-name dales --inplace
running build_code
building libraries and community codes
build, for logging, see 'build.log'
[21:48:26] building dales
Community codes not built (because of errors):
================================================================================
 * dales
================================================================================
0 out of 1 codes built, 0 out of 0 libraries built
Traceback (most recent call last):
  File "setup.py", line 76, in <module>
    data_files=all_data_files,
  File "/usr/local/lib/python3.6/site-packages/setuptools/__init__.py", line 165, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib64/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/opt/omuse/support/setup_codes.py", line 1217, in run
    BuildCodes.run(self)
  File "/opt/omuse/support/setup_codes.py", line 1096, in run
    raise Exception("No succesful builds detected. Aborting.")
Exception: No succesful builds detected. Aborting.
FATAL:   failed to execute %post proc: exit status 1
FATAL:   While performing build: while running engine: while running /usr/libexec/singularity/bin/starter: exit status 255

NOTE: Using git tag v1.2:
commit caa7673c23406ccef1174836cdff2d7151d50f65 (HEAD, tag: v1.2)
Merge: 71ad0cd 930d266
Author: ipelupessy<EMAIL_ADDRESS>Date:   Mon Apr 6 12:11:36 2020 +0200
Merge branch 'master' of github.com:omuse-geoscience/omuse****

I am able to build and run dales locally without Singularity (on Arch Linux) though.

I agree with @fjansson that the versions should be pinned for the sake of reproducibility. Not just Python packages, but perhaps also the OS, which is loosely pinned:
https://github.com/omuse-geoscience/omuse/blob/caa7673c23406ccef1174836cdff2d7151d50f65/Singularity#L23-L24
See https://hub.docker.com/_/centos?tab=tags.
Another alternative would be build the singularity image and upload it somewhere safe.

Thank you @ashwinvis for reporting the build failure, and sorry for the slow response. I just tested building the image on Arch Linux, and got a similar failure, which turned out to be caused by CMake not liking that the DALES build directory already exists:
CMake Error: The current CMakeCache.txt directory /opt/omuse/src/omuse/community/dales/dales-build/CMakeCache.txt is different than the directory /home/fjansson/work_F/cwi-code/omuse/src/omuse/community/dales/dales-build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt

I think building OMUSE and DALES in-place without singularity before trying to build the singularity image causes this. After removing the dales-build directory, I succeeded in building the image. I think a better fix would be to ensure that these paths don't collide.
A way to view the build.log file is to use the sandbox option and request that the files are not removed if the build fails:
sudo singularity build --no-cleanup -s sandbox Singularity
less rootfs-xxxx/opt/omuse/build.log

For pinning the OS version: I see the base image we use, centos:8 is being updated, and that there are tagged versions e.g. centos:8.2.2004 which presumably stay unchanged.  But our current recipe anyway uses yum to install dependencies (and the recipe starts with a yum update) so I think pinning the base image is not a guarantee that nothing will change (although I'd expect centos updates to be rather conservative exactly for the reason that they don't want to break things). I'd be in favour of archiving a known-good image as well as the recipe.
Good news in the centos:8 image being updated is that the OpenMPI bug there might have been fixed, if so we can stop building it manually in the recipe. I'll test this.

I must also confide I did not see the debugging instructions among the comments. I confirm that I was getting the "CMake Error" and with a fresh clone I can build the image.

I think a better fix would be to ensure that these paths don't collide.

Yes that seems necessary. Either with an out-of-source build with CMake or ensuring that the sources are clean from build artifacts by doing a git-clone, for instance.


Solver app

Hello 😊
in this mini project @ZahraArshia  and I implemented:

a test for factorial, reverse and fizzbuzz methods.
a class called Solver
a method called factorial that takes one argument, an integer N, and returns the factorial for the number to make it pass tests.
a method called reverse that takes one argument, a string word, and returns word reversed and to make it pass tests.
a method called fizzbuzz and make it passes the tests.

Thank you for the review 😉

Thank you for the review @Gambit142 😉


Only 6 pages are available. Page 7+/12 are not generated

I am unable to load any page after 6th, in index and in the tag pages. They are not generated.
Homepage: Aba's Blog
6th page: https://aba-blog.xyz/page/6/index.html
7th page (fails): https://aba-blog.xyz/page/7/index.html

It seems that you're storing and loading your posts in a different way, I don't think this is an issue with the theme since Liebling is using the standard method to load the next and previous posts by using the corresponding helpers.
I'm afraid that I can't help you here, I would suggest you to debug your implementation or to look for help in the forums.

I will close this issue for now, please feel free to reopen it if needed.


Azure SQL also supports Managed Identities

While Azure SQL is mentioned under Azure services that support Azure AD authentication, it is not mentioned under Azure services that support managed identities for Azure resources.
According to the documentation of Azure SQL however, you can enable a System assigned managed identity to an Azure SQL Server resource, see for example Assign an identity to the Azure SQL logical server.
Based on this, Azure SQL should probably be added to the list under Azure services that support Azure AD authentication.

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

ID: 726adac9-1848-01a6-9586-842c81f820f7
Version Independent ID: 249db438-8c95-8e69-f69e-8e48fcd0b359
Content: Azure Services that support managed identities - Azure AD
Content Source: articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md
Service: active-directory
Sub-service: msi
GitHub Login: @barclayn
Microsoft Alias: barclayn

@jurjenoskam Thank you for your feedback . We will investigate and update the thread.

@jurjenoskam Thank you for your feedback. We have a work item to track this suggestion. We are working on an approach to keep that article up to date and we will evaluate this work item when start implementing the changes.

#please-close


Resolve SymbolFlags.Type only at first in jsdoc getTypeFromTypeReference

Before falling back to SymbolFlags.Value.
Previously, by having both simultaneously at first, we'd find the local symbol of a merged const/type alias symbol, which only actually has value meaning applied to it. In normal codepaths, we'd skip over that to the export symbol of the same name, which has the intended type meaning.
This fixes a regression in the webpack user test. (When we started binding @enum tags a typedefs, we started having merged const/type aliases with separate export/local symbols in js (just like in TS), which were previously much harder to make)

@RyanCavanaugh seeing as this fixes a regression from 3.5 (though I didn't open an issue for it), would we want to port this to the 3.6 final release?

note specifically that exported @enum is broken, and (in theory) @typedefs that share a name with an exported value. We've never seen any of the second kind, though.

@typescript-bot cherry-pick this to release-3.6


Error on page hub.github.com

# open the GitHub compare view between two releases
git compare v0.9..v1.0

but must be git compare v0.9...v1.0 (3 dots)

This looks like it's handled: https://github.com/github/hub/blob/1e8f4f4f83c8dc3058ccf0a9d082d553796dc210/features/compare.feature#L66-L69

❯ hub version
git version 2.3.2
hub version 2.2.0-rc1-38-g1409606

git compare images-desktop/v1.42.0..images-desktop/v1.42.2
# opens https://github.<enterprise>/<path>/compare/images-desktop/v1.42.0..images-desktop/v1.42.2

git compare images-desktop/v1.42.0...images-desktop/v1.42.2
# opens https://github.<enterprise>/<path>/compare/images-desktop/v1.42.0...images-desktop/v1.42.2
# and its correct address

@a-x- The two dots .. are converted into three dots ... only for simple expressions. Yours has slashes, so you need to use .... We avoid parsing complex expressions in order to not mangle any of its content. This is by design. Sorry that you tripped up on it.

ok
btw, slash here is simply part of branch

Yeah, I understand. But it's better that you pass triple dot yourself when building out compare ranges between branches that have special characters.

ok


Add try/except block to remote process

Done, but I think it might be non-trivial to deal with KeyboardInterrupts and such on the remote process.


Add OIIO make_texture function to Python bindings

Allows for .tx file conversion without having to call MakeTX

#2529


Question about training dataset

Hey, thanks for the great work!
I had a question about the training dataset for the end-to-end VNLI model. In the paper you mention:
Specifically, we finetune BLIP2 and PaLI-17B using a dataset comprising 110K text-image pairs labeled with alignment annotations. This includes 44K examples from COCO-Con, 3.5K from PickaPic-Con, 20K from COCO t2i and 40K from the training split of the SNLI-VE dataset.
However, I was unable to find the training split on AWS/Huggingface. Are there plans to release it, or if it has already been released, could you please point me to where I can find it?

Hi, we will publish it soon, working on data release. We will update. Thank you :)

Hi, it's updated now in the project website, sorry for the delay, please ask if anything is unclear
CSV: https://seetrue.s3.amazonaws.com/wysiwyr_train.csv
Images: https://drive.google.com/file/d/1M1CKmYkIdpFYjCOc9JwXHP5Z7E91CJl3/view?usp=drive_link


Fix remove package metadata from dist.lock

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


请问咱们这个模型怎么移植到安卓手机上去呢

please reference to https://tensorflow.google.cn/mobile/prepare_models.

@xsr-ai can you provide a android model to repaly.
thanks, best wishes

not now, sorry.


Added test in CI

Modified the workflow file to run the tests in the GitHub actions

@gemanor I have modified the test to use https://github.com/marketplace/actions/gabrielbb-xvfb-action?version=v1.6
because the clipboardy  package we are using for the copy has a problem with headless environment's  such as ci
reference: https://github.com/sindresorhus/clipboardy/issues/63#issuecomment-676484369


[Automation] Generate Fluent Lite from azurestackhci#package-preview-2023-09

[Automation] Generate Fluent Lite from azurestackhci#package-preview-2023-09

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-azurestackhci


save should add .json suffix automatically

More details please. We didn't ever had problems with saving

If you talk about graph save inside App.py on windows suffix added by default, since filters and extension specified. I believe on Linux it behaves a bit differently

Ok. That means qfiledialog works differently on Linux, will fix it


Bump jekyll from 3.2.1 to 3.9.0

Bumps jekyll from 3.2.1 to 3.9.0.

Release notes
Changelog
Commits

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

deprecated pr


fix to unlimited arguments

We will be able to get variable length argument Intersection types with this PR.
const ONE =   { type: 1 as 1 };
const TWO =   { type: 2 as 2 };
const THREE = { type: 3 as 3 };
const FOUR =  { type: 4 as 4 };
const FIVE =  { type: 5 as 5 };

const merged1 = Object.assign(ONE, TWO, THREE, FOUR);
const merged2 = Object.assign(ONE, TWO, THREE, FOUR, FIVE);

[before]
const merged1: { type: 1 } & { type: 2 } & { type: 3 } & { type: 4 }
const merged2:　any

[after]
const merged1: { type: 1 } & { type: 2 } & { type: 3 } & { type: 4 }
const merged2: { type: 1 } & { type: 2 } & { type: 3 } & { type: 4 } & { type: 5 }

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

Files from lib folder are generated from src/lib folder. Some files from src/lib are generated from TSJS-lib-generator repository.
Read Contributing lib.d.ts fixes for more info.


calibrateCamera compatibility with OpenCV3

calibrateCamera now needs to explicitly provide the cameraMatrix and distCoeffs parameters. E.g.
        ret, camera_matrix, dist_coeffs, rvecs, tvecs = \
            calibrateCamera(objectPoints=self.grids,
                            imagePoints=self.grid_candidates,
                            imageSize=self.image_size,
                            flags=CALIB_FIX_K4 |
                            CALIB_FIX_K5 |
                            CALIB_ZERO_TANGENT_DIST,
                            cameraMatrix=None,
                            distCoeffs=None)

Depends on #11 (in case different OpenCV implementations provide different APIs)


Get-ForensicNetworkList returns "Source array was not long enough"

I'm using Win 8.1 64-bit
I tried:
PS C:\Windows\system32> Get-ForensicNetworkList
Get-ForensicNetworkList : Source array was not long enough. Check srcIndex and length, and the array's lower bounds.
At line:1 char:1

Get-ForensicNetworkList

  + CategoryInfo          : NotSpecified: (:) [Get-ForensicNetworkList], ArgumentException
  + FullyQualifiedErrorId : System.ArgumentException,PowerForensics.Cmdlets.GetNetworkListCommand

Then I've extracted 3.reg file and tried like this:
PS C:\Windows\system32> Get-ForensicNetworkList -HivePath C:\3.reg
Get-ForensicNetworkList : Source array was not long enough. Check srcIndex and length, and the array's lower bounds.
At line:1 char:1

Get-ForensicNetworkList -HivePath C:\3.reg

  + CategoryInfo          : NotSpecified: (:) [Get-ForensicNetworkList], ArgumentException
  + FullyQualifiedErrorId : System.ArgumentException,PowerForensics.Cmdlets.GetNetworkListCommand

What version of PowerForensics are you using?  Is it the version from the github release?  Also is the exported reg file from Windows 8.1 or is PowerForensics being run from Win 8.1 or both?

What version of PowerForensics are you using? Is it the version from the github release?

v.1.1 from Github

Also is the exported reg file from Windows 8.1 or is PowerForensics being run from Win 8.1 or both?

Both

PS C:\Windows\system32> $stacktrace
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 len
gth, Boolean reliable)
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 len
gth)
at PowerForensics.Registry.NamedKey.GetSubKeys(Byte[] bytes, String key) in C:\Users\tester\Documents\GitHub\PowerFo
rensics\PowerForensics\src\Windows\Registry\Cells\NamedKey.cs:line 264
at PowerForensics.Registry.NamedKey.GetInstances(Byte[] bytes, String path, String key) in C:\Users\tester\Documents
\GitHub\PowerForensics\PowerForensics\src\Windows\Registry\Cells\NamedKey.cs:line 162
at PowerForensics.Artifacts.NetworkList.GetInstances(String hivePath) in C:\Users\tester\Documents\GitHub\PowerForen
sics\PowerForensics\src\Artifacts\NetworkList.cs:line 79
at PowerForensics.Cmdlets.GetNetworkListCommand.ProcessRecord() in C:\Users\tester\Documents\GitHub\PowerForensics\P
owerForensics\src\Cmdlets\Artifacts\Get-NetworkList.cs:line 40
at System.Management.Automation.CommandProcessor.ProcessRecord()

I think these issues should be fixed in https://github.com/Invoke-IR/PowerForensics/releases/tag/1.1.1


Add support for elevation in DrawerLayoutAndroid

It didn't work for a few reason. First, the drawer view NEEDS to have a background color or no shadow will ever render. Second, we need to use the setDrawerElevation method instead of setElevation for DrawerLayout. Finally we need to actually pass the style value (maybe we could just pass elevation but I don't really think it can cause any issues) down to the native component as it is not the case at the moment.
I also added a default style to elevation of 16 which is the standard for material design according to https://www.google.com/design/spec/patterns/navigation-drawer.html#navigation-drawer-specs. I could also default it to 0 so it keeps the same appearance as before but I think it looks better this way.
Closes #6022
Test plan
Tested using the DrawerLayout in the UIExplorer app.
Before, elevation 0

After, elevation 16

FYI, BUCK is not happy with the change.
https://circleci.com/gh/facebook/react-native/2971

Module com.facebook.react.views.drawer.ReactDrawerLayoutManager has already registered a property named "elevation"

The props preprocessor doesn't like me overriding the elevation prop implementation :(
@lexs would this be easy to support? Otherwise I can just rename the prop to something else and set it in the js component.

Assuming they have the same type etc you should be able to override the
method.
On Tue, 23 Feb 2016 11:50 Janic Duplessis<EMAIL_ADDRESS>wrote:

Module com.facebook.react.views.drawer.ReactDrawerLayoutManager has already registered a property named "elevation"
The props preprocessor doesn't like me overriding the elevation prop
implementation :(
@lexs https://github.com/lexs would this be easy to support? Otherwise
I can just rename the prop to something else and set it in the js component.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/6100#issuecomment-187668518
.

I tried adding the @Override annotation to see if it changed anything but it didn't. One has a generic type maybe it's why it doesn't work.
Base class:
public void setElevation(T view, float elevation) {

Subclass
public void setElevation(ReactDrawerLayout view, float elevation) {

@janicduplessis Which version are you running on? I know there was a bug regarding overriding methods previously. I'll check tomorrow what version the fix went into.

@lexs I assume you mean what version of buck, I just tried with a fresh pull from master. That is what the build running on CI is doing too.

Not sure we want to set the color to white, besides that looks good overall. Thanks for doing this! Once you and @lexs figure out the tests let's merge it.

@lexs Any update on this? If it seems hard to fix I can just rename the prop for now to unblock this.

@janicduplessis Can you please rebase to see both Travis (iOS & JS) and CircleCI (Android) tests passing?
We've fixed the tests so we're back to green now:
https://travis-ci.org/facebook/react-native/builds
https://circleci.com/gh/facebook/react-native/tree/master

@janicduplessis Sorry for not responding sooner, totally missed the emails.
You should be able to have the following:
  @Override
  public void setElevation(ReactDrawerLayout view, float elevation) {
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
      view.setDrawerElevation(PixelUtil.toPixelFromDIP(elevation));
    }
  }

@lexs I just decided to check how to fix it (that timing!), I changed the ReactPropertyProcessor to check types and only throw if the type are different. This allow leaving the annotation like I did initially. Let me know if you thinks that's fine otherwise I can do what you suggested. :)

Yeah you'll need to change it to the @Override I mentioned.
The reason for this is that while the annotation processor might behave correctly in the case where you add the same property again the old, reflection-based implementation will not (and it's still used if you don't build by Buck).
I agree that you should be able to override properties in the way you did initially but currently behavior is basically undefined. The reflection-based version will pick one of them. This is why I added the error initially. In practice the override approach has worked every time this have come up (two times now). So fixing this is pretty low-prio.

Yea it's a pretty rare case, it did work when I tested with the reflection based version (it picked the good one I guess). I changed the message a bit to point to the right direction if it happens again and changed it to what you suggested.

@mkonicek All the tests are passing now and the prop issue is figured out!

@facebook-github-bot shipit

Thanks!

Fails to compile in fb CI with:
ReactAndroid/src/main/java/com/facebook/react/views/drawer/ReactDrawerLayoutManager.java:96:
error: cannot find symbol
[CONTEXT]       view.setDrawerElevation(PixelUtil.toPixelFromDIP(elevation));

Any ideas?

Yes, sorry for not getting back sooner. This fails internally because we're on an older version of the Android support lib. We've landed a newer version and I'm gonna try to switch over the DrawerAndroid component to it. It shouldn't need any changes on your part.

@janicduplessis Turns out this will be really hard to land as-is. The reason is we're on an older version of the support library internally an upgrading is going to take a while. I'm sorry about this. To land this for now could you perhaps rewrite the call to DrawerLayout.setDrawerElevation() to use reflection (or some other method that doesn't require the method to exist) :).

@lexs Updated to call the method with reflection as you suggested!

Updated with the warning log.

@facebook-github-bot shipit

@facebook-github-bot shipit

@lexs I see you abandoned the internal diff with a comment "will reimport". Since it uses reflection now I'll merge it as is.

Yes, that was my intention. Thanks Martin!
On Fri, 18 Mar 2016 17:30 Martin Konicek<EMAIL_ADDRESS>wrote:

@lexs https://github.com/lexs I see you abandoned the internal diff
with a comment "will reimport". Since it uses reflection now I'll merge it
as is.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/6100#issuecomment-198409052


add forceExtent

fixes #89
note that the extent's definition in this PR is [[xmin, ymin], [xmax, ymax]], more in line with, for example zoom.extent. Defaults to [[0,0], [960,500]].
by @gka

oops I realize this duplicates https://github.com/d3/d3-force/pull/115 in some (simpler) way.

Seems to me that this pull request establishes hard boundary, which is undesired as you will get node overlapping. #115 uses forces instead, which should work better. This notebook showcases it https://observablehq.com/@john-guerra/d3-force-boundary

Here is a comparison
#163 https://observablehq.com/d/606866e6c1db4809
#115 https://observablehq.com/@john-guerra/d3-forceboundary

Just in case there is interest in a solution that includes bouncing off the container walls, there is https://github.com/vasturiano/d3-force-surface

Thank you for ruining my "productivity" with you awesome game of pong!!!! 👏

Sorry I went really too fast on this issue. I've now made a test bed with the three forces here: https://observablehq.com/d/21d2053b3bc85bce
Unfortunately in this specific situation (in particular, there is no forceCollide), as you progressively shrink the box, I don't think anything works really well :(

Randomizing positions every time we move the slider might be the issue, here it is keeping node positions https://observablehq.com/d/7acdd31a46c120be
Seems to me (and my bias) that forceBoundary does the better job

Agree with you that  forceBoundary is currently the best (or "least worst") in this playground, but for me it's still not "good enough" in the sense that the nodes end up all on top of each other on the boundary (as they do with that version of "forceExtent"). I tend to think we need more research if we want something simple and solid for the core of d3-force. But it's surprisingly hard!

If you set the strength of force boundary to a high value then you can overpower the other forces
https://observablehq.com/d/7acdd31a46c120be

Sure, but in that case it's not a "boundary" force anymore—it becomes more like a central gravitation. What would be the ideal force to contain a simulation in a box?  It should behave properly (no jumps etc), it should not let points get out of the box, and I believe it should not impact points if they're not near the boundary (or near points that are near the boundary). Current state of the art to achieve this with D3 seems to be a mix of forceBoundary + forceCollide, why not—but d3-force is the only module where you have to do so much tweaking and tuning to get things looking right. And you have to do it again each time you change the data.

There is another possibility which is to have a force that forces (excuse the pun) the nodes inside the container by manipulating the nodes positions instead of just the velocities. This is semi unusual in forces but is perhaps appropriate here. forceCenter does that too by the way. It also may be the only way to guarantee that a node does not escape the container.
I've just made one that hard limits the nodes positions to specified range. It also slows down nodes if it predicts they will land outside the range in the following iteration, so it applies the restriction proactively.
https://github.com/vasturiano/d3-force-limit
It also allows for setting restrictions in just one dimension, and also setting different ranges for different nodes, via accessor functions. That may be overkill for the specific case of container walls, but maybe useful in other scenarios in which you want certain nodes to cross some boundaries.
@fil I've added a suggestion on your notebook that adds forceLimit to compare the behaviour.

I think I'm closer to @mbostock's answer to this question https://stackoverflow.com/questions/9573178/d3-force-directed-layout-with-bounding-box
I do think that nodes should be allowed to exit the boundary, for instance when users drag them.
With forceBoundary you can also define what is the distance to the border in which the force will come in effect. That will address @Fil desire of

I believe it should not impact points if they're not near the boundary (or near points that are near the boundary

I need to look more into @vasturiano's approach, but I have found weird results in the pasts changing the node positions instead of their velocities. Having said that, the bouncing nodes demos look amazing. Seems like a really good solution when what you want is a wall that cannot be crossed by any means. It force limit works extremely well as a wall in https://observablehq.com/d/21d2053b3bc85bce
In my use cases what I have usually wanted is a force that tries to keep my nodes visible inside my drawing canvas. I don't mind if they have to leave for a moment, as long as they try to return. And I don't want nodes to stay in the limit of the canvas as that generates overlapping

As an attempt to address the issue of nodes gathering on the container's edge I've added an enhancement that lets you specify a soft repelling force away from the edges, with configurable intensity. This acts only within a certain margin of proximity of the boundary and the intensity decays linearly with the distance within this margin. A bit like having a cushioning effect.
I've put together a demo here: https://observablehq.com/@vasturiano/d3-force-limit
I don't know if it's perfect, but it does handles the limit a bit more graciously.
This really feels like a more challenging problem than it appears initially, but it's such a common use case that it's important to get just right. 😃

I've added a collision force in the test notebook, making sure the constraint force was coming in last (a requirement for d3-force-limit because it's using look-ahead). I think it works very well—I'm adding a few suggestions at https://github.com/vasturiano/d3-force-limit/issues/1
PS: It's a bit strange that this discussion happens on this failed PR—but hey, it's so good to see the progress!

And now forceWalls appeared in https://observablehq.com/d/21d2053b3bc85bce ; I think we're getting a bit closer with each step (as suits a force simulation).

... This acts only within a certain margin of proximity of the boundary and the intensity decays linearly with the distance within this margin. A bit like having a cushioning effect.

Forcebounday also features a similar effect, https://www.npmjs.com/package/d3-force-boundary#boundary_border

But seems like my implementation draws nodes to the center whereas @vasturiano's drive them perpendicularly out of the border. I looks good in the observable. Not sure if it was intentional, but changed the left cushion from 0 to 10 in https://observablehq.com/d/21d2053b3bc85bce

Not sure if it was intentional

yes it was to show the cushion's "impact" ( can a cushion have an impact? :) )—but it's ugly.

here's a new iteration of forceWalls, with a simpler API : https://observablehq.com/d/66b419d51abee995

I like that api schema a lot. The way you can specify a complex polygon like an ellipse using a set of hyperplane walls is extremely cool.
Actually, it gave me another idea. What if we'd be able to specify a wall as an x => y function in addition to the hyperplane fashion. Something like:
.walls([{ y: 30 }, x => (x + 3)**2])

Then we could have curved walls without having to quantize them out of multiple planes.

I've taken another route completely and came up with a solution using a Sliced Optimal Transport approach.
Test forceTransport at https://observablehq.com/d/21d2053b3bc85bce
The gist of the algorithm is:

sort all the nodes on x, send the first towards x=0, the second towards x = width/(n-1), etc all the way up to x=width for the last point.
sort all the nodes on y, send the first towards y=0, the second towards y = height/(n-1), etc all the way up to y=height for the last point.

The first part is an OT on the x direction (or "slice"), and the second an OT in the y direction. (We could separate them into transportX and transportY if we wanted, like forceX and forceY.)
We can put up a similar piece of code to do the same for a disk (or an ellipse), by slicing the data on the angle (atan) and radius^2 dimensions—it's a bit less stable but results in a nice "fill a disk" force.

I've now found a way to properly transport to a disk

Hi Fil! At first glance, this looks really cool, I'm moving between
countries right now, so i expect to check it by the end of the week
John.
From my phone, brevity and all
http://johnguerra.co
On Sat, Nov 7, 2020, 10:50 AM Philippe Rivière<EMAIL_ADDRESS>wrote:

I've taken another route completely and came up with a solution using a
Sliced Optimal Transport approach.
Test forceTransport at https://observablehq.com/d/21d2053b3bc85bce
The gist of the algorithm is:

sort all the nodes on x, send the first towards x=0, the second
towards x = width/(n-1), etc all the way up to x=width for the last point.
sort all the nodes on y, send the first towards y=0, the second
towards y = height/(n-1), etc all the way up to y=height for the last point.

The first part is an OT on the x direction (or "slice"), and the second an
OT in the y direction. (We could separate them into transportX and
transportY if we wanted, like forceX and forceY.)
We can put up a similar piece of code to do the same for a disk (or an
ellipse), by slicing the data on the angle (atan) and radius^2
dimensions—it's a bit less stable but results in a nice "fill a disk" force.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/d3/d3-force/pull/163#issuecomment-723461723, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJJCS4HV4UC7RZP7YOUKEDSOVUFBANCNFSM4OIQZQKA
.

This looks really cool @Fil, would love to be able to use it as a part of d3 or as a module. Please let me know if I can help in any way

You can definitely play with the algorithm and see what it does (and doesn't). I don't think it's ready at all for being a module.

Ahhhh I forgot that I could test it simply importing from your notebook
😁🤷🏼♂
Here is a test with a sparse network from one of my student's work
https://observablehq.com/d/a98827b7f86dd773
Force transport only cares to move the points if they are beyond the
extent, right? That can be positive as it allows for better combination
with other forces...
On Tue, Apr 20, 2021 at 12:53 PM Philippe Rivière @.***>
wrote:

You can definitely play with the algorithm and see what it does (and
doesn't). I don't think it's ready at all for being a module.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/d3/d3-force/pull/163#issuecomment-823558337, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJJCS4YSCLYOYX7D66QO7DTJXLS7ANCNFSM4OIQZQKA
.

--
John Alexis Guerra Gómez
https://johnguerra.co

To get a better intuition of the sliced OT algorithm, suppose we are on a unique dimension x. The points are ordered according to their x:
0-1----------2-3-4----5--6-------7
now we want this to be more balanced we'll move them according to their position (x) relative to their expected position (i/n):
→0-→1---2←---3←--4-----→5--→6---7←
repeat the procedure on the vertical axis, and you get the rectangular forceTransport.
To get to the disc transport you need to apply this procedure along a "rotating" direction, and the delicate part is in the choice of angles (number and distribution), because taking 1 random direction at each step makes the movement very unstable.

Very cool Philippe, thanks for explaining!
On Tue, Apr 20, 2021 at 11:18 PM Philippe Rivière @.***>
wrote:

To get a better intuition of the sliced OT algorithm, suppose we are on a
unique dimension x. The points are ordered according to their x:
0-1----------2-3-4----5--6-------7
now we want this to be more balanced we'll move them according to their
position (x) relative to their expected position (i/n):
→0-→1---2←---3←--4-----→5--→6---7←
repeat the procedure on the vertical axis, and you get the rectangular
forceTransport.
To get to the disc transport
@.***/disc-transport> you need to apply this
procedure along a "rotating" direction, and the delicate part is in the
choice of angles (number and distribution), because taking 1 random
direction at each step makes the movement very unstable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/d3/d3-force/pull/163#issuecomment-823807686, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJJCS75X265VXVPFJJ4UTDTJZU47ANCNFSM4OIQZQKA
.

--
John Alexis Guerra Gómez
https://johnguerra.co


Members panel style is broken in new visual scripts

Godot version:
3.2.4beta1
OS/device including version:
Windows 10
Issue description:
When you create a new visual script the Members panel is unstyled, black fonts and no icons so you can't really tell what you are supposed to do to create new variables. Once you click the invisible buttons it shows up properly.
Steps to reproduce:
Create a node, create and add a new visual script
Minimal reproduction project:
Link to video demonstrating the issue: https://www.youtube.com/watch?v=RK72M61oUDA

Sometimes it happens on master too.

I've seen that in master today indeed. It used to be fine, so I guess it's a regression?

Well, yeah I think its regression from somewhere between 3.2 and 3.2.3

Still happening in 3.2.4.beta3


Updates an endpoint and a call

Updates an endpoint and a call

Thank you for your contribution! We are aware that the lib doesn't work because the endpoints have changed.
Although we are not fully using it, I'm gonna try out this change to see if it works everywhere.

Thanks for your contribution, I see you discovered about the new API endpoints the thing is I believe they are generated addresses that depends on the user session so hardcoding them will only make the code work for some moments for you only. Also now they have a different login system that needs some kind of handshake first

The new token URI works for me. But this account_emergency change no.
Gonna try later on to see if they keep changing the URIs indeed.

Hi guys, just a heads up:
To get these URLs you must query them at the discovery endpoint.
Its just a GET request that will return all endpoints available


Upgrade UK to data sampler

This PR upgrades the UK part datamodule to ocf-data-sampler.  This works towards #273
Notes:

The datamodules for wind and pvsite have not been updated
This breaks PVNet for wind and pvsites due to an update in the target variable shape, and in the time units coming from data-sampler
I have also stripped out the exponential weighted losses. We haven't used them in a very long time if ever
Also stripped out parts of model training test routine, we only ever use train and validate
There are also a couple of minor bug fixes and clean ups that struck me along the way
Update tests

More of a general question, looking through am I right in thinking that we are (for the UK regional stuff at least) moving from saving batches (batch_size number of samples saved together) to saving each individual sample in separate .pt files, does the extra writes (a write to .pt for each sample now) and reads impact batch creation time / training times significantly or is it negligible?

Starting to use this code to test out the Site Torch Dataset pipeline, whilst doing that I thought it would be good to update the config example parameters in the datamodule folder which mention "batch" to "samples" to align with the new save_samples.py script

is it good to merge this? Make sure @Sukh-P is working from that branch then?

Well there is still the example configs to update, but yeh then we could merge into the dev-data-sampler branch


Commited changes

I am submitting some updates to Firefly Theme
I have changed

Added

Changed

Fixed

Why should this have been updated

[1.1.1] - 14.02.2022
Added

Checkbox Styling
Styling vor hr elements

Fixed

Removed Headline-Underlining for H1 and H2 Headlines
Reduced bottom margin from Headline (H2-H5) to 10px


[Gitcoin Bounty] - zkSync v2 Account Abstraction tutorial: Daily Spending Limit

zkSync v2 Account Abstraction tutorial: Daily Spending Limit
Prize Bounty

600 USDC (via Ethereum or zkSync)

Challenge Description
Create a tutorial that shows developers how to use account abstraction to create an account with a daily spending limit.
We are looking for outstanding developers and educators to help showcase the benefits of account abstraction. For this bounty, participants will create a tutorial that shows developers how to use account abstraction to build an account with a daily spending limit.
The tutorial will be a combination of code and explanatory text that walks developers through building the application step-by-step. Before starting, please have a look through our existing tutorials to get a feel for the writing style.
Requirements
Technical Requirements

Account has a daily spending limit in ETH
Account will reject transactions if daily spending limit has been exceeded
Project should contain smart contracts for the account abstraction and scripts to deploy the contracts and simulate spending on different days.
Limit can be changed by external admin account
Project must be deployed to zkSync 2.0 testnet
Project must contain basic testing (info on how to run local tests is available in this section of the zkSync docs).

Writing Requirements

Code must be clearly commented
Submission must follow tutorial format: code + explanatory text (see resources for examples)
The submission is original and not cross-posted from somewhere else

Submission Requirements

Must be submitted in markdown format
Must include Github repository with code of the full project

Judging Criteria
Submissions that fulfill the Requirements above that have the same quality or higher of our current tutorials (see Resources below). We ask that before getting started that you submit a brief overview of how you will approach the project so that we can be as efficient as possible with everyone's time.
Winner Announcement Date
Upon successful submission of a tutorial that covers all the Requirements of the bounty.
Resources

Existing zkSync tutorials
zkSync v2 documentation

My submission is here: https://github.com/porco-rosso-j/daily-spendlimit-tutorial

this was published. thanks


build: update the package dependencies

Getting below error, do check out if that can be fixed with dependencies.
warning @cord.network/sdk > @cord.network/did > @cord.network/augment-api > @polkadot/rpc-provider ><EMAIL_ADDRESS>versions below 1.x are no longer maintained

@amarts
I think we need to update the version of rpc-provider which has the connect module. But to keep it consistent better to update versions of all the polkadot dependencies.
  "devDependencies": {
    "@polkadot/api": "^10.12.2",
    "@polkadot/typegen": "^10.12.2",
    "@types/node": "^20.11.6",
    "glob": "^7.1.1",
    "rimraf": "^5.0.5",
    "tsx": "^4.7.0",
    "typescript": "^5.3.3",
    "yargs": "^17.7.2"
  },
  "dependencies": {
<EMAIL_ADDRESS>"workspace:*",
    "@polkadot/rpc-augment": "^10.12.2",
    "@polkadot/rpc-core": "^10.12.2",
    "@polkadot/rpc-provider": "^10.12.2"
  }

What version should we update to. I tried updating to latest got errors during build.

@amarts @vatsa287 can you assign me this issue


UriFormatException: Invalid URI: Invalid port specified.

Running the sample 2d platform scene gives this error.
UriFormatException: Invalid URI: Invalid port specified.
UnityEngineInternal.WebRequestUtils.MakeInitialUrl (System.String targetUrl, System.String localUrl) (at C:/buildslave/unity/build/Modules/UnityWebRequest/Public/WebRequestUtils.cs:548)
UnityEngine.Networking.UnityWebRequest.set_url (System.String value) (at C:/buildslave/unity/build/Modules/UnityWebRequest/Public/UnityWebRequest.bindings.cs:400)
UnityEngine.Networking.UnityWebRequest..ctor (System.String url, System.String method) (at C:/buildslave/unity/build/Modules/UnityWebRequest/Public/UnityWebRequest.bindings.cs:176)
HappyFunTimes.HFTSite+Informer+d__15.MoveNext () (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:90)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at C:/buildslave/unity/build/Runtime/Export/Coroutines.cs:17)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
HappyFunTimes.Informer:Inform(Boolean, MonoBehaviour, Byte[], String) (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:72)
HappyFunTimes.d__8:MoveNext() (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:241)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
HappyFunTimes.HFTSite:Init(Options) (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:175)
HappyFunTimes.HFTManager:StartServer() (at Assets/HappyFunTimes/HappyFunTimesCore/HFTManager.cs:272)
HappyFunTimes.HFTManager:Start(HFTRuntimeOptions, GameObject) (at Assets/HappyFunTimes/HappyFunTimesCore/HFTManager.cs:57)
HappyFunTimes.HFTConnectionManager:StartHappyFunTimes() (at Assets/HappyFunTimes/HappyFunTimesCore/HFTConnectionManager.cs:54)
HappyFunTimes.PlayerSpawner:StartHappyFunTimes() (at Assets/HappyFunTimes/HappyFunTimesCore/PlayerSpawner.cs:104)
HappyFunTimes.PlayerSpawner:Start() (at Assets/HappyFunTimes/HappyFunTimesCore/PlayerSpawner.cs:172)
https://imgs.info/i/k7tFw

Can you try this one?
https://github.com/greggman/hft-unity3d/releases/tag/v2.1.7

Hi @greggman  the issue with the URI was gone and its having this different issue.
SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
System.Net.Sockets.Socket.ReceiveFrom (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.Net.EndPoint& remoteEP) (at <3845a180c26b4889bc2d47593a665814>:0)
System.Net.Sockets.Socket.ReceiveFrom (System.Byte[] buffer, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.Net.EndPoint& remoteEP) (at <3845a180c26b4889bc2d47593a665814>:0)
System.Net.Sockets.UdpClient.Receive (System.Net.IPEndPoint& remoteEP) (at <3845a180c26b4889bc2d47593a665814>:0)
DNS.Client.RequestResolver.UdpRequestResolver.Request (DNS.Client.ClientRequest request) (at Assets/HappyFunTimes/HappyFunTimesCore/DNS/Client/RequestResolver/UdpRequestResolver.cs:28)
DNS.Client.ClientRequest.Resolve () (at Assets/HappyFunTimes/HappyFunTimesCore/DNS/Client/ClientRequest.cs:73)
DNS.Client.DnsClient.Resolve (DNS.Protocol.Domain domain, DNS.Protocol.RecordType type) (at Assets/HappyFunTimes/HappyFunTimesCore/DNS/Client/DnsClient.cs:83)
DNS.Client.DnsClient.Resolve (System.String domain, DNS.Protocol.RecordType type) (at Assets/HappyFunTimes/HappyFunTimesCore/DNS/Client/DnsClient.cs:72)
DNS.Client.DnsClient.Lookup (System.String domain, DNS.Protocol.RecordType type) (at Assets/HappyFunTimes/HappyFunTimesCore/DNS/Client/DnsClient.cs:42)
HappyFunTimes.HFTDnsUtils.GetIPAddresses (System.String domain, DNS.Protocol.RecordType type) (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTDnsUtils.cs:20)
HappyFunTimes.HFTSite.GetIPAddresses (DNS.Protocol.RecordType type) (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:155)
HappyFunTimes.HFTSite.Init (HappyFunTimes.HFTSite+Options options) (at Assets/HappyFunTimes/HappyFunTimesCore/Server/HFTSite.cs:172)
HappyFunTimes.HFTManager.StartServer () (at Assets/HappyFunTimes/HappyFunTimesCore/HFTManager.cs:272)
HappyFunTimes.HFTManager.Start (HappyFunTimes.HFTRuntimeOptions options, UnityEngine.GameObject gameObject) (at Assets/HappyFunTimes/HappyFunTimesCore/HFTManager.cs:57)
HappyFunTimes.HFTConnectionManager.StartHappyFunTimes () (at Assets/HappyFunTimes/HappyFunTimesCore/HFTConnectionManager.cs:54)
HappyFunTimes.PlayerSpawner.StartHappyFunTimes () (at Assets/HappyFunTimes/HappyFunTimesCore/PlayerSpawner.cs:104)
HappyFunTimes.PlayerSpawner.Start () (at Assets/HappyFunTimes/HappyFunTimesCore/PlayerSpawner.cs:172)


test: reducing logspam

I've never been happy with the setupLogging method I added to MTE. Now that it's a year later and we no longer have the engine-tests/MTE split to worry about, I might understand things well enough to do better.
Contains
Brief description of what the PR does
How to test
Brief description of how to test / confirm this PR before merging
Outstanding before merging

[ ] log filter for module tests
[ ] document how module maintainers can configure the filter
[x] add archive of full test report to the jenkins build, in case you want to get the non-Jenkins-truncated output

In this branch's current state, things work fine for engine-tests. If you look at the console output for the integrationTest step, there's only the warnings from Java itself: https://jenkins.terasology.io/teraorg/job/Terasology/job/engine/view/change-requests/job/PR-5022/2/pipeline-console/
and when you look at the output for a specific test, you see it has some: https://jenkins.terasology.io/teraorg/job/Terasology/job/engine/view/change-requests/job/PR-5022/2/testReport/org.terasology.engine.integrationenvironment/MTEExtensionTestWithPerClassLifecycle/Integration_Tests___firstTestFindsThings__/
(The ...[truncated 19025 chars]... there is Jenkins, not the test execution. Its threshold for output on passing tests is very small. It keeps a bit more for failed tests.)
The thing I haven't checked yet, and I expect is not filtered, is the output of module tests.

Things to know about junit and logging: JUnit uses java.util.logging. We consolidate that with our own slf4j-based logging using jul-to-slf4j


How to pick only videos?

I can't see how to pick videos or only videos.
Is it not supported? or I'm missing something?

It is not supported. But I should probably add it some day...

Duplicate #30

Do we have video picker support for this library?

How can we disable videos while image picker appears? Currently it will show photos and videos.


Empty option objects

Removed paragraph about empty objects as the example above no longer follows this convention

Good call.  I'll need to look at this.  I did find a good solution for this, but I probably should add a note about how this works now.   Options objects will automatically become required of they have any non-optional properties contributed by plugins


Greenkeeper/@nestjs/testing 7.0.11

:tada: This PR is included in version 3.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add alpha and notalpha modifiers

Coverage increased (+0.02%) to 99.467% when pulling 9a4f2abbd0d79f7fdc83c89e6dce0b317bd055e7 on frederikhors:add-alpha-and-notalpha-modifiers into df5a59bfe050f4dd502ba297b9b5e8302aae6218 on go-playground:master.

This seems very similar to #26
one is ascii and the other works with unicode, perhaps the naming can be improved to denote that?

I agree. Done in other PR.


Redefine attribute, solve the problem of compilation in IAR envir…

Redefine attribute, solve the problem of compilation in IAR environment

Thanks!


openshift: use separate network security groups

Moved from https://github.com/kargakis/acs-engine/issues/62
@pweil- @jim-minter

@jackfrancis can be assigned to me


[Render Bug] Green vertical lines between glyphs using PL fonts

Windows Terminal version
1.11.2921.0
Windows build number
10.0.22000.0
Other Software
PowerShell 7.2.0
Steps to reproduce
open up wt.
set font to something with powerlines, like MesloLGM NF
set fontsize to anything (i tried from 9 to 14)
install and run oh-my-posh to see glyph corruption.
Expected Behavior

no malformed green line on ubuntu terminal between system logo and right white arrow glyph
Actual Behavior

Green line between windows glyph and right white arrow glyph.
This is a continuation of the issue started here:
https://github.com/JanDeDobbeleer/oh-my-posh/issues/1332

This looks like a duplicate of #8993.

Yep, thanks!
/dup #8993


Having trouble setting this up

Hey - I found out abut jasmine-given from a frontend masters tutorial.  I'm trying to do the setup now for a different project, but using jasmine 2.4 instead of 1.3.  Here's my SpecRunner.html
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>Jasmine Spec Runner v2.4.1</title>

  <link rel="shortcut icon" type="image/png" href="lib/jasmine-2.4.1/jasmine_favicon.png">
  <link rel="stylesheet" href="lib/jasmine-2.4.1/jasmine.css">

  <script src="lib/jasmine-2.4.1/jasmine.js"></script>
  <script src="lib/jasmine-2.4.1/jasmine-html.js"></script>
  <script src="lib/jasmine-2.4.1/boot.js"></script>

  <script type="text/javascript" src="spec/helpers/jasmine-given.js"></script>

   <!-- include vendor files here... -->
   <script type="text/javascript" src="vendor/coffee-script.js"></script>
   <script type="text/javascript" src="number-shortening-filter.js"></script>
   <script type="text/coffeescript" src="spec/number-shortening-filter-spec.coffee"></script>

</head>

<body>

  <script type="text/javascript">

</body>
</html>

My test file is spec/number-shortening-filter-spec.coffee.  Just to try and get it to do something, I made it
describe "Testing describe", ->
  Given -> @subject = Array 1,2,3
  Then -> @subject == null

When I serve the SpecRunner.html though, I get the jasmine test-runner page that says "No specs found".
Here's what my filestructure looks like:

Ok, its an issue with coffee-script, since compiling the coffeescript to js, this works fine.


Fixes #15

The settings file wasn't being encoded when it was read in, and was therefore interpreted as a buffer.

Wow, thanks for investigating!


Add dashscope like zhipuai.

dashscope is alibaba ai service.
It contains many llm services, including Llama2 (now with free api!), 通义千问开源 7B、14B 模型 (now with free api!), and more!

从文档上看，通义千问的开源模型不需要申请，目前免费使用，其他模型都需要申请才能限时免费使用。
We can add it to enhance our capabilities and also test more use cases such as the code completion helper(like Github copilot)

dashscope is alibaba ai service.
It contains many llm services, including Llama2 (now with free api!), 通义千问开源 7B、14B 模型 (now with free api!), and more!
从文档上看，通义千问的开源模型不需要申请，目前免费使用，其他模型都需要申请才能限时免费使用。
We can add it to enhance our capabilities and also test more use cases such as the code completion helper(like Github copilot)

@Abirdcfly  This is great! And can you pls also take this issue https://github.com/kubeagi/arcadia/issues/79 to find a way to use  zhipuai & dashscope  in langchain

Thought we can close this issue now. @Abirdcfly


Image: zoom controls

Users also encountered some difficulties controlling the zoom functionality on the images.

UV defaults - can't really control

Looks like upgrade to UV v3.0.36 fixed this
Zoom controls contain title attribute
Tested with Chromevox 53