chore(deps): update dependency react-native-gesture-handler to v2

This PR contains the following updates:

Package
Type
Update
Change

react-native-gesture-handler
dependencies
major
^1.4.1 -> ^2.0.0

Release Notes

software-mansion/react-native-gesture-handler
v2.6.0
Compare Source
❗ Important changes

Add experimental web implementation by @Warus15 in https://github.com/software-mansion/react-native-gesture-handler/pull/2157
Validate children of GestureDetector to check if there is only one native view that can be a target of the gestures by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2132
Add onLongPress callback to Gesture Handler buttons by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2083
Detect duplicate instances by @piaskowyk and @kkafar in https://github.com/software-mansion/react-native-gesture-handler/pull/2155, https://github.com/software-mansion/react-native-gesture-handler/pull/2162, https://github.com/software-mansion/react-native-gesture-handler/pull/2173, https://github.com/software-mansion/react-native-gesture-handler/pull/2174
Export custom RefreshControl component and add logic required to handle it by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2137
Compatibility with React Native 0.70, replace NDK with CMake by @tomekzaw and @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2153

🐛 Bug fixes

Make gestures work on non-editable TextInput on Android by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2112
fix: remove explicit folly version by @kacperkapusciak in https://github.com/software-mansion/react-native-gesture-handler/pull/2148
Pass disabled prop to the BaseButton in TouchableNativeFeedback by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2141
Fix some edge cases in state flow on Android when handler is waiting for another one by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2145
Build only required architectures on Android by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2126
Remove unsafe methods by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2130
Cancel gestures when an uninterruptible native gesture becomes active by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2129
Fix default max distance for long press on Android by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2095
Make Gesture Handler on web respect simultaneousHandlers prop when used on a ScrollView by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2125
Check if loaded module is really Reanimated in reanimatedWrapper by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2179
Use angle-bracket imports by @tomekzaw in https://github.com/software-mansion/react-native-gesture-handler/pull/2180
fix: RCT_NEW_ARCH_ENABLED=0 to disable new arch by @nomi9995 in https://github.com/software-mansion/react-native-gesture-handler/pull/2178

👍 Improvements

Display a more expressive error message when Gesture Handler receives more than one child by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2131
Use non-deprecated Handler constructor by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2163
Upgrade Docusaurus & theme to match Reanimated by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2166
Make Example app run on web by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2110
Update issue template by @kacperkapusciak in https://github.com/software-mansion/react-native-gesture-handler/pull/2165

🔢 Miscellaneous

Update version requirements in docs and README by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2077
Bump moment from 2.29.2 to 2.29.4 in /ci/e2e by @dependabot in https://github.com/software-mansion/react-native-gesture-handler/pull/2123
Bump terser from 4.8.0 to 4.8.1 in /docs by @dependabot in https://github.com/software-mansion/react-native-gesture-handler/pull/2136
Add runOnJS where necessary in Drag and Drop example by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2144
Mention automatic workletization of callbacks in the docs by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2124
chore: typo in issue template by @kkafar in https://github.com/software-mansion/react-native-gesture-handler/pull/2176

New Contributors

@piaskowyk made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2155
@kkafar made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2173
@Warus15 made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2157
@nomi9995 made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2178

Full Changelog: https://github.com/software-mansion/react-native-gesture-handler/compare/2.5.0...2.6.0
v2.5.0
Compare Source
❗ Important changes

Add activateAfterLongPress modifier to Pan gesture by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1938
Make NativeViewGestureHandler behave more like on iOS when wrapping TextInput by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2017
Extract handlers when child view is handling touch with pointerEvents='box-none' by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2024
Fix sound effects on nested buttons, add touchSoundDisabled prop by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2047

🐛 Bug fixes

Update  scroll view class check in RNNativeViewHandler on Fabric by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2031
Fix simultaneousHandlers prop on NativeViewGestureHandler on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2018
Don't use reanimated module in a worklet by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2070
Schedule calling dropAllGestureHandlers on main queue by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2028
Refactor how ripple animation is applied to GestureHandlerButton by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2014
Make sure that react-native-macos is supported by using the web fallback by @hsjoberg in https://github.com/software-mansion/react-native-gesture-handler/pull/2010
Default import package.json in src/utils by @nandorojo in https://github.com/software-mansion/react-native-gesture-handler/pull/2036
Fix wrong coordinates when multiple gestures are tracking different pointers on Android by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2098
Fix touchable inspector for Gesture Handler buttons by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2103
Fix wrong coordinated reported by Fling gesture on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2059
Fix Kotlin compiler error inferred type Context? by @muhamad-rizki in https://github.com/software-mansion/react-native-gesture-handler/pull/2096
Fix: use different touchHandler on Fabric by @WoLewicki in https://github.com/software-mansion/react-native-gesture-handler/pull/2104
Fix state flow for manual activation on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1912
Fix importing PressabilityDebugView on web by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2109
Upgrade Gesture Handler and FabricExample to support RN 0.69 by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2053

🔢 Miscellaneous

Fix Markdown format by @nidelson in https://github.com/software-mansion/react-native-gesture-handler/pull/2107
Add a guide for migrating to the new API by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2076
Create more general extension mechanism for NativeViewGestureHandler on Android by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2016
Delete App.js from FabricExample by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2035

New Contributors

@hsjoberg made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2010
@nandorojo made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2036
@muhamad-rizki made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2096

Full Changelog: https://github.com/software-mansion/react-native-gesture-handler/compare/2.4.2...2.5.0
v2.4.2
Compare Source
🐛 Bug fixes

Fix resolution of refs in the old API by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2019
Use constant value for translation when DrawerLayout is idle by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2005
Fix compatibility with @types/react^18.0.0 by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2030
Don't update shared value containing the gesture config unless the config has changed by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2037

🔢 Miscellaneous

Upgrade Example app dependencies and React Native by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1989
Move helper functions outside of useAnimatedGesture by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/2034

Full Changelog: https://github.com/software-mansion/react-native-gesture-handler/compare/2.4.1...2.4.2
v2.4.1
Compare Source
🐛 Bug fixes

Support monorepos with new architecture by @oblador in https://github.com/software-mansion/react-native-gesture-handler/pull/2015
Add mocks for flushOperations in https://github.com/software-mansion/react-native-gesture-handler/commit/daaeea8cae2d22f0aa18cc9479c829ce387b6014, originally by @Alex5ander in https://github.com/software-mansion/react-native-gesture-handler/pull/2008

🔢 Miscellaneous

Add ndkVersion to Android project by @maximzhemerenko in https://github.com/software-mansion/react-native-gesture-handler/pull/2012

New Contributors

@maximzhemerenko made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/2012

Full Changelog: https://github.com/software-mansion/react-native-gesture-handler/compare/2.4.0...2.4.1
v2.4.0
Compare Source
❗ Important changes

Basic web support for GestureDetector by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1934
Remove warning about the old API by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1960
Suppress deprecated warnings by @jakub-gonet in https://github.com/software-mansion/react-native-gesture-handler/pull/1886
Effectively remove RNGestureHandlerEnabledRootView by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1936
Add a workaround for pointerCount must be at least 1 by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1982
Add cancelsTouchesInView prop on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1688
Implement sending events directly to Reanimated on Fabric by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1987

🐛 Bug fixes

Fix TypeScript typing issues with setTimeout by removing NodeJS types by @henrikra in https://github.com/software-mansion/react-native-gesture-handler/pull/1959
Pass accessibilityActions properties by @pooyahrtn in https://github.com/software-mansion/react-native-gesture-handler/pull/1963
Use device events when remote debugging is enabled by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1929
Don't send events on iOS when target is nil by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1946
Fix props on GestureHandlerButton by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1967
Add missing props to GestureButton type by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1981
Fix gestures not attaching to views on iOS when using Fabric by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1979
Fix Fabric checks happening too early by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1923
Drop all gesture handlers on invalidate by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1988
Fix nested buttons with outer one disabled on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1991

🔢 Miscellaneous

Fixed a typo in example url by @ghorbani-m in https://github.com/software-mansion/react-native-gesture-handler/pull/1931
Update @react-navigation version & fix example bug. by @alantoa in https://github.com/software-mansion/react-native-gesture-handler/pull/1942
Updated Tap Gesture Handler Documentation by @ajatdarojat45 in https://github.com/software-mansion/react-native-gesture-handler/pull/1962
Use C++17 for Fabric on iOS by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1932
Add compileOptions to build.gradle. Needed for<EMAIL_ADDRESS>to work by @EmmaSteady in https://github.com/software-mansion/react-native-gesture-handler/pull/1937
Update documentation for wix/react-native-navigation by @Yrsafam in https://github.com/software-mansion/react-native-gesture-handler/pull/1965
Rewrite codegen config with TypeScript by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1952

New Contributors

@ghorbani-m made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/1931
@ajatdarojat45 made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/1962
@pooyahrtn made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/1963
@EmmaSteady made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/1937
@Yrsafam made their first contribution in https://github.com/software-mansion/react-native-gesture-handler/pull/1965

Full Changelog: https://github.com/software-mansion/react-native-gesture-handler/compare/2.3.2...2.4.0
v2.3.2
Compare Source
⚠ Breaking changes

Remove jestUtils from the main index.ts and move it to separate package.json (https://github.com/software-mansion/react-native-gesture-handler/pull/1917 by @j-piasecki)

We felt that, although it's a breaking change, this fix important enough to warrant a patch release. If you started using fireGestureHandler and getByGestureTestId methods, change their import to react-native-gesture-handler/jest-utils.
❗ Important changes

Use native driver by default for TouchableOpacity animations (https://github.com/software-mansion/react-native-gesture-handler/pull/1924 by @j-piasecki)

v2.3.1
Compare Source
🐛 Bug fixes

Fix ripple animation on touchables in some cases (https://github.com/software-mansion/react-native-gesture-handler/pull/1877 by @j-piasecki)
Fix StyleSheet import in RNGestureHandlerButtonNativeComponent.js (https://github.com/software-mansion/react-native-gesture-handler/pull/1908 by @djMax)
Fix missing testID when createHandler props do not have one assigned (https://github.com/software-mansion/react-native-gesture-handler/pull/1910 by @virdesai)

🙌 Thank you for your contributions!
v2.3.0
Compare Source
:exclamation: Important changes

Gesture Handler for Fabric (https://github.com/software-mansion/react-native-gesture-handler/commit/0d1a917a3de5281656276e05bcbff1d832d8d624 by @tomekzaw and @j-piasecki)
Add FabricExample (https://github.com/software-mansion/react-native-gesture-handler/commit/d5344621046a69920fb078b592d6e428a5a154ee by @tomekzaw and @j-piasecki)
Add ability to fire gesture events in testing (https://github.com/software-mansion/react-native-gesture-handler/commit/273fa03679cea7a648fb6f8639d36c4f58b8934a by @jakub-gonet and @piaskowyk)

🐛 Bug fixes

Fix race condition between the orchestrator and the registry (https://github.com/software-mansion/react-native-gesture-handler/commit/ceec9f8adc2568e6a7483b52efd12a8adcf2c656 by @j-piasecki)
Rebuild Reanimated event only when needed (https://github.com/software-mansion/react-native-gesture-handler/commit/c09453377771add9a8a0630c72c9eb79e6f60f4a by @j-piasecki)
Fix tvOS compilation errors (https://github.com/software-mansion/react-native-gesture-handler/commit/e932a48106133c1ffd95e8f604d364993a405f1d by @j-piasecki)
Add modified ScaleGestureDetector from AOSP (https://github.com/software-mansion/react-native-gesture-handler/commit/ce1fec787f0329e6b22da6c9aa9f47de7e44592a by @j-piasecki)
Use the speed option in DrawerLayout (https://github.com/software-mansion/react-native-gesture-handler/commit/a6591e6b9fc78bc33885775b5e939066948684cc by @j-piasecki)

:+1: Improvements

Export change event payload types (https://github.com/software-mansion/react-native-gesture-handler/commit/0f1825345292e209dc1d572f54d83062ad5f27df by @jakub-gonet)
Add direction to Swipeable callbacks (https://github.com/software-mansion/react-native-gesture-handler/commit/48df23996c199892d2fbbace82aeb0fb654d0eb8 by @jakub-gonet)

:1234: Miscellaneous

Add runOnJS modifier to gestures (https://github.com/software-mansion/react-native-gesture-handler/commit/7ce194f5d48c6865b32b030eb9933d835c62f307 by @j-piasecki)

v2.2.1
Compare Source
This release backports a few important changes for Expo.
❗ Important changes

Basic web support for GestureDetector by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1934
Remove warning about the old API by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1960
Rebuild Reanimated event only when needed by @j-piasecki in https://github.com/software-mansion/react-native-gesture-handler/pull/1856

v2.2.0
Compare Source
❗ Important changes

Change absolute position to be relative to the window instead of the screen (https://github.com/software-mansion/react-native-gesture-handler/pull/1812) by @j-piasecki
Add notice for old API users (https://github.com/software-mansion/react-native-gesture-handler/pull/1817) by @jakub-gonet
We want to improve the discoverability of the new API so we added a one-time notice whenever an old gesture handler is used. Check out #1817 for information on how to disable it if you find the notice unhelpful.

🐛 Bug fixes

Use path relative to the directory of Reanimated when checking its version (https://github.com/software-mansion/react-native-gesture-handler/pull/1757) by @j-piasecki
Check major version of Reanimated when looking for common interface (https://github.com/software-mansion/react-native-gesture-handler/pull/1768) by @j-piasecki
Reset progress of handler when it finishes waiting ends (https://github.com/software-mansion/react-native-gesture-handler/pull/1795) by @j-piasecki
Use export type when exporting types (https://github.com/software-mansion/react-native-gesture-handler/pull/1791) by @j-piasecki
Send first onTouchesDown after gesture begins (https://github.com/software-mansion/react-native-gesture-handler/pull/1793) by @j-piasecki
Send state change event when awaiting handler finishes (https://github.com/software-mansion/react-native-gesture-handler/pull/1774) by @j-piasecki
Don't send UNDETERMINED to CANCELLED state change event (https://github.com/software-mansion/react-native-gesture-handler/pull/1796) by @j-piasecki

v2.1.3
Compare Source
Use export type when exporting types (https://github.com/software-mansion/react-native-gesture-handler/pull/1791) by @j-piasecki
v2.1.2
Compare Source
Use path relative to the directory of Reanimated when checking its version (https://github.com/software-mansion/react-native-gesture-handler/pull/1757) by @j-piasecki
v2.1.1
Compare Source
Changes

Add onChange callback to continuous gestures that carries change of value since the last event (https://github.com/software-mansion/react-native-gesture-handler/commit/605aab5009f079b391cba84ac511e51c19a37ae5 and https://github.com/software-mansion/react-native-gesture-handler/commit/e611e2d3b0daeee9552ced3f85b8a57b006ed8a5)

v2.1.0
Compare Source
Changes

Use common interface from Reanimated when available (#1747)
Add onFinalize callback (#1749)
Change invocation order of methods when resetting gesture recognizers (#1751)

v2.0.0
Compare Source
This release marks a new milestone in Gesture Handler - we added new API that's easier to use, tidied up some cruft that accumulated over the years and fixed many longstanding bugs. Check the changelog below.
For the documentation about the new API and newly added features please check out the updated docs page at https://docs.swmansion.com/react-native-gesture-handler/
:warning: Breaking changes

Adjust Swipeable's overshootFriction behavior (#1275) by @kolking
Fix min distance on Pan with custom activation criteria (#1696) by @j-piasecki
Remove deprecated props from PanGestureHandler (#1662) by @j-piasecki

:exclamation: Important changes

Add new API by @j-piasecki
New Manual Gesture feature by @j-piasecki
Add duration to long press event (#1505) by @j-piasecki
Allow resetting properties to default value (#1444) by @jakub-gonet
Fix TouchableOpacity visuals (#1567) by @jakub-gonet
Deprecate RNGestureHandlerEnabledRootView (#1605) by @jakub-gonet
Fix modals (#1603) by @jakub-gonet
Fix tap gesture handler inconsistency (#1682) by @j-piasecki
Update FlingGestureHandler on iOS (#1612) by @j-piasecki
Update PanGestureHandler on iOS (#1611) by @j-piasecki
Fix LongPressGestureHandler inconsistency (#1610) by @j-piasecki

🐛 Bug fixes

Reset velocity when beginning pan gesture (#1694) by @j-piasecki
Fix gesture handlers not working when children overflow their parent (#1618) by @j-piasecki
Fix nested touchables on Android (#1601) by @j-piasecki

:+1: Improvements

Expanded Jest mocks (#1364) by @TheWirv
Improved type definitions of Gesture Components (#1394) by @yfunk
Remove implicit inclusion of node types (#1420) by @jakub-gonet
Fix interactions between TapGH and PanGH (#1508) by @j-piasecki
Block touch handling when inspector is enabled (#252) by @osdnk, @jakub-gonet
Fix compatibilty with React 18 by @janicduplessis
Pass RNGH props to FlatList's underlying ScrollView (#1557) by @jakub-gonet
Add JSDocs (#1566) by @jakub-gonet
Fix buttons can get stuck on Android (#1512) by @bastiandev
Export SwipeableProps (#1598) by @SimonIT

:1234: Miscellaneous

Fix build-time warnings & add missing dependencies (#1446, #1447) by @jakub-gonet
Update Example app
Update docs by @moondef, @jakub-gonet, @jkadamczyk, @Andarius
Allow react-native-screens to work with Gesture Handler (#1323) by @WoLewicki
Fix iteration over argument mapping on web (#1504) by @machouz
Import UIManager directly from react-native (#1528) by @acoates-ms
Convert Java sources to Kotlin by @jakub-gonet
Adds github actions build checks (#1576) by @Ubax

:raised_hands: Thank you for your contributions!
v1.10.3
Compare Source
Patch release fixing Expo 41 support, types, and removing deprecation warning.
⌨  Typescript

Move types to type exports (#1389) by @jakub-gonet
Fix Timeout type (#1386) by @jakub-gonet

:1234: Miscellaneous

Update deprecated getConstants() call (#1379) by @jarod-legault
Remove GestureHandlerRootView.android.expo.tsx (#1383) by @jakub-gonet

:raised_hands: Thank you for your contributions!
v1.10.2
Compare Source
Patch release fixing missing mocks problem.
:bug: Bug fixes

Fix mocks import in jestSetup.js (#1377) by @jakub-gonet

:+1: Improvements

Adjust Platform constants import (#1211) by @drewandre
Copy Directions enum to JS (#1366) by @jakub-gonet

:1234: Miscellaneous

Lint unlinted files (#1362) by @jakub-gonet
Add Bob (#1360) by @jakub-gonet

:raised_hands: Thank you for your contributions!
v1.10.1
Compare Source
Patch release fixing most problems that came up after rewriting the library to TS.
:bug: Bug fixes

Move jestSetup.js to root dir (#1337) by @jakub-gonet
Keep same extensions on different platforms (#1351) by @jakub-gonet
Rename _handlerTag to handlerTag (#1357) by @jakub-gonet

⌨  Typescript

Fix gestureHandlerRootHOC types (#1347) by @alpha0010
Use PropsWithChildren in TouchableWithoutFeedback (#1345) by @jakub-gonet
Replace import React with import * as React (#1346) by @jakub-gonet
Export all compat *Properties types (#1356) by @jakub-gonet

:raised_hands: Thank you for your contributions!
v1.10.0
Compare Source
This release includes docs wording improvements thanks to @jtalz, some bugfixes and drawer improvement. We also rewritten source code of RNGH to Typescript.
:bug: Bug fixes

Fix interactions with NativeViewGestureHandler (#1034) by @ShaMan123
Use weak reference for storing rootViews in iOS (#1217) by @Norcy
Disable allowedScrollTypesMask in tvOS (#1278) by @csantos1113
Specify minimal SDK version for enableTrackpadTwoFingerGesture (#1301) by @KenCorma

:+1: Improvements

DrawerLayout: add onDrawerSlide() (#999) by @rorygarand
Add optional speed parameter to open/closeDrawer (#1133) by @jeremywho

⌨  Typescript

Rewrite to TS (#1327) by @WoLewicki and @jakub-gonet

:1234: Miscellaneous

Organize folder structure (#1199) by @jakub-gonet
Lint src/ directory (#1274) by @jakub-gonet
Clamp swipe animation in examples (#1290) by @mhkeller

:raised_hands: Thank you for your contributions!
v1.9.0
Compare Source
This release mainly fixes problems with hitslop property and web implementation, adds two-finger scrolling on iPadOS, adds tap sound on touchables, and improves TS typings.
:bug: Bug fixes

Fix GestureHandler isWithinBounds top hitslop (#1202) by @eeynard
Fix destructuring ref.props on the web (#1220) by @hosseinmd

:+1: Improvements

make PressGestureHandler web implementation to pass along the move event and fix the propTypes issue (#1098) by @connectdotz
Support RN headers in both namespaces on iOS (#1183) by @grit96
fix: move Swipeable and DrawerLayout type definition (#955) by @Naturalclar
Fix typings for enums (#1055) by @iyegoroff
Allow two finger touchpad scrolling on iPadOS (#1128) by @robertherber and @jakub-gonet
Allow minDurationMs=0 in LongPressGestureHandler (#1216) by @jacobp100
Add sound to Touchables on Android (#1172) by @jakub-gonet

:1234: Miscellaneous

Update docs to 0.63 (#1185) by @jakub-gonet
Add note about onGestureEvent in docs (#1189) by @jakub-gonet
Fix Xcode 12 compatibility (#1193) by @radko93
Update Detox and XCode CI version to 12 (#1191) by @jakub-gonet
Add fbjs as dependency (#1226) by @jakub-gonet
Fix wrong github link (#1229) by @sunnylqm
Fix broken link in docs (#1230) by @hehex9

:raised_hands: Thank you for your contributions!
v1.8.0
Compare Source
In this release, we fixed some long-standing threading issues which were crashing apps integrated with RNGH. Additionally,MAX_POINTERS_COUNT has been increased to support devices that handle up to 12 simultaneous touches.
:bug: Bug fixes

Fix threading issue in RNGestureHandlerStateChangeEvent (#1171) by @jakub-gonet
Fix thread safety of RNGestureHandlerModule methods ([#1173](https://togithub.com/software-mansion/react-native-gesture-

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: example/yarn.lock
error An unexpected error occurred<EMAIL_ADDRESS>connect ECONNREFUSED <IP_ADDRESS>:4873".


Accesability Issue. Mat-stepper

Reproduction
https://stackblitz.com/angular/rdypvkkpelo?file=app%2Fstepper-overview-example.ts
Steps to reproduce:

Add new header with any heading tag inside the stepper step.
Then run the jaws and if we check by using insert + F3 and then button list. All the buttons in the page are appending with the header.

Expected Behavior
What behavior were you expecting to see?
Button with its own name
Actual Behavior
What behavior did you actually see?
header then button name

Any update on this issue?

am also facing mentioned issue in mat stepper. Any information will be helpful for us.

i am also facing issue

josephperrott Any update on this?

@josephperrott Can this be fixed?

@crisbeto Can you please take a look at this issue.

I looked at this just now, and the button label seems normal:

Can you share a reproduction of what you're seeing? The linked stackblitz does not have any headers.

Closing since this seems to be working as expected.


PyPI releases!

At PyAstro16 we discussed that this astropy/regions package should be developed quickly in this repo at https://github.com/astropy/regions/ and then be merged in the Astropy core repo.
There hasn't been much development on astropy/regions after PyAstro16 though, there isn't much functionality, tests, docs yet ... it's not clear if it's feasible to get this done and stable before for Astropy 1.3.
I'd like to propose that we start doing releases on PyPI and announce them on astropy-dev, starting with 0.1 very soon (in a week or two).
A personal motivation for that is that I don't like having to update the bundled version of this package at gammapy.extern.regions because we have started using it for circles and need it to be available to end users. The main reason is that I think releases on PyPI and announcements on astropy-dev might attract some co-developers to this package and having had users means that the API and implementation is likely more robust when the time comes to move this to Astropy core.
I'd be happy to make the releases, and if someone else (@joleroi, @keflavich) wants to, even better!
Concerning package name, I propose plain regions (which amazing wasn't taken, so I reserved it right now: https://pypi.python.org/pypi/regions ) This is nice because it's the same as the current repo and package name, i.e. no confusion by users or developers.
I did consider astropy-regions as package name. That's more explicit, but also longer and then some people get confused if PyPI package and installed package names are different.
@keflavich @astrofrog @joleroi @eteq @larrybradley - Thoughts?

I agree that we need a spur for further development.  pypi release is a good move in that direction, so I support it.

https://github.com/astropy/regions/milestones/0.1

I'll make the 0.1 release this Saturday, July 9.
@astropy/regions-developers - If you have time to implement or improve something in astropy/regions in the next two days, please open up an issue or PR and put it under the 0.1 milestone.

+1 to making releases, it would be good to get usage before we consider merging into astropy anyway. I've gone down that route for wcsaxes and reproject.

Note that I think we should get https://github.com/astropy/regions/pull/20 merged in before the 0.1 release - but I don't have time to investigate the failures (there aren't many) - could someone else take a look at this?

I just merged #50 , we now have some docs:

http://astropy-regions.readthedocs.io/en/latest/
http://astropy-regions.readthedocs.io/en/latest/getting_started.html

I'll try to find time to work on this some more in the coming days.
Help would be appreciated, especially with #41  and writing this part: http://astropy-regions.readthedocs.io/en/latest/getting_started.html#ds9-region-strings and

FYI: I plan to make the 0.1 release later today after merging #60.
I know there's a lot of things to be improved, but why not "release early and often"!?

I've made the v0.1 tag and uploaded the sdist to PyPI:
https://pypi.python.org/pypi/regions
@astropy/regions-developers - Please test if pip install regions and `python -c 'import regions; regions.test()' works for you.
@bsipocz @mwcraig - Can you please make a conda package for regions?
@joleroi or @keflavich - Looks like I don't have permission at http://readthedocs.org/projects/astropy-regions/ to see the project settings and add "v0.2" as one that should be built. Whoever has permissions for this repo on RTD: please add me.

@bsipocz @mwcraig - Can you please make a conda package for regions?

Sure, I'm on it.

@keflavich, @larrybradley , @astrofrog - FYI: I've added you as owners on PyPI for
https://pypi.python.org/pypi/regions
just in case I get 👊  by a 🚌 .

Is there a template or good example for package release announcements?
Or should I just write something?
(in any case, I'll wait a few days in case there's an issue and so that the conda package is ready)

@cdeil  pip install regions works for me and all tests pass.  Thanks!

Tests pass for me, too.

Conda package: https://github.com/astropy/conda-channel-astropy/pull/59

@bsipocz - Thanks!
Could you please make a PR updating the install instructions in master concerning conda install?
http://astropy-regions.readthedocs.io/en/latest/installation.html
I think all that's needed is the command to run, and link to the URL where info about this conda package will be.
Is it this?
conda install --channel astropy regions

https://anaconda.org/astropy/regions

Sure. I got to go know, but will be back later this evening.

@bsipocz and @mwcraig - Thanks for making the conda package.
For me this works on Mac with Python 3.4:
conda install -c astropy regions
python -c 'import regions; regions.test()'

Maybe others here can try as well.
@joleroi - Looks like you're owner on RTD: http://readthedocs.org/projects/astropy-regions/
Can you make me (and maybe @keflavich @larrybradley @astrofrog ) co-owner so that we have permission to do such things as adding "v0.1" on RTD?

@cdeil I added you as maintainer on RTD, if others tell me (or you) their RTD names I (or you) can add them.

I'm bradley on RTD.

I get this when trying to install the package
[/home/kingj] conda install -c astropy regions
Fetching package metadata: ............
Solving package specifications: ..............
Error: Could not find some dependencies for regions: pytest-mpl

pytest-mpl shouldn't be a required dependency for regions.
I downloaded https://anaconda.org/astropy/regions/0.1/download/linux-64/regions-0.1-py35_0.tar.bz2
and looked at info/recipe/meta.yaml (a copy is here:
https://gist.github.com/cdeil/6c3a3c9172370fa17d51f5d71bc5f3e2#file-meta-yaml-L37
https://anaconda.org/astropy/regions)
  run:
  - python
  - astropy
  - pytest-mpl
  - matplotlib
  - wcsaxes

The pytest-mpl, matplotlib and wcsaxes dependencies are optional, they should never prevent conda install of regions.
@bsipocz and @mwcraig -- Can you change this?
I guess either we remove pytest-mpl, matplotlib and wcsaxes from the dependency list, and tell users to get the "full-featured version" by separately conda installing this in the docs.
Or we have two conda packages, e.g. regions and regions-all, or regions-core and regions.
We had the same issue / discussion for Gammapy, I think there also a proper solution isn't implemented yet for the conda builds.

@joleroi - Thanks for giving me access to RTD.
We now have this:

http://astropy-regions.readthedocs.io/en/v0.1/
http://astropy-regions.readthedocs.io/en/stable/
http://astropy-regions.readthedocs.io/en/latest/
where stable currently points to v0.1

So all that's left to do is fix the conda package issue before sending out the release announcement.

@mwcraig - It seems that the extras_require packages are picked up into the automatic recipe. Should we create one manually and edit these out from it, or you have a better solution in mind?

@bsipocz that option got added at pyastro16 when I sunpy needed (or at least wanted) extras, with the thought "Why not? What could go wrong?".
You can add this to requirements to prevent it: include_extras: false

"Why not? What could go wrong?".

Usually the answer to this is that everything will go wrong, especially where you're not expecting it. At least this is the way things work/stop working in ci-helpers ;)

@bsipocz @mwcraig - Thanks!
I've had issues and head scratching because of stealth updates over the years, so 👍  to implement the build number update feature.
But sure, agreed, it's OK to do a stealth update in this case, almost no-one will be affected.

I'm inclined to do the update now, rather than wait until the build number bumping is implemented. This is rather a trivial change that only fixes bugs (see, this is the other problematic statement that is hardly ever true).
The only other affected package is astroplan, but the conda packages for it was build before pyastro16, so it looks fine.

@cdeil - The conda packages should show up in the next ~30 mins here https://anaconda.org/astropy/regions/files

@bsipocz - Thanks!
The meta.yaml now correctly only has Astropy as dependency:
  run:
  - python
  - astropy

@joleroi - You could try conda install again:
http://astropy-regions.readthedocs.io/en/latest/installation.html#using-conda
I'll try to find time to wrap this up and send an announcement to astropy-dev tomorrow, if not on Monday.

I've sent the release announcement to astropy-dev:
https://groups.google.com/forum/#!topic/astropy-dev/QjXUl6wgM6M
I'm closing this issue now.
We can use #63 to discuss the next release: version 0.2.


Minor incompatability with plugin/theme repo

The download button and text are same color.

This also affects "Screen share" settings

That should be fixed now, with the new version


Dollar sign appended at end of NMDC TTH search requests

A failure in automated tests made me notice that the library explicitly appends a dollar sign at the end of every TTH search request:
https://github.com/direct-connect/go-dc/blob/9b3b849481748ab725415599f18bd6edcd351877/nmdc/search.go#L92
In this way, requests become:

$Search <IP_ADDRESS>:412 F?T?0?9?TTH:TO32WPD6AQE7VA7654HEAM5GKFQGIL7F2BEKFNA$|

instead of:

$Search <IP_ADDRESS>:412 F?T?0?9?TTH:TO32WPD6AQE7VA7654HEAM5GKFQGIL7F2BEKFNA|

what's the reason of this behavior? i could not find an explanation in both specifications and existing clients:
http://nmdc.sourceforge.net/Versions/NMDC-1.3.html#_search
thanks

Sometimes clients send the trailing $, I've seen this in the wild.
However you are right. On further examination of the source code, I see that most popular clients don't send trailing $. Marking this as a bug.


[Feature] Add tag annotation to allow tagging span with annotation

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] Bug fix
[x] New feature provided
[ ] Improve performance

This PR provides another annotation Tag (similar to Trace) to allow users to apply a tag to the current active span, it's more convenient to tag a trace in companion with @Trace:
@Trace
@Tag(key = "tag", value = "arg[0]")
public void method(String param) {
}

or multiple tags
@Trace
@Tags({
    @Tag(key = "tag1", value = "arg[0]"),
    @Tag(key = "tag2", value = "arg[1]"),
})
public void method(String param1, String param2) {
}

CI keeps failure. Please recheck.

Does this PR support we can using anntation write our agent plugins ?

Does this PR support we can using anntation write our agent plugins ?

In the test, it can't, because they are not in the release :) So they are copied into the test project too.

Does this PR support we can using anntation write our agent plugins ?

In the test, it can't, because they are not in the release :) So they are copied into the test project too.

Great feature!

Does this PR support we can using anntation write our agent plugins ?

Do you mean using @Tag in the agent plugin methods? No you can't, classes of agent plugins are ignored:
https://github.com/apache/skywalking/blob/1ee14fbbc8251a1faa5f3851d4f7d92f9ec1ab15/apm-sniffer/apm-agent/src/main/java/org/apache/skywalking/apm/agent/SkyWalkingAgent.java#L90-L98
so although you can annotate the plugin method with @Tag, it takes no effect

Does this PR support we can using anntation write our agent plugins ?

Do you mean using @Tag in the agent plugin methods? No you can't, classes of agent plugins are ignored:
https://github.com/apache/skywalking/blob/1ee14fbbc8251a1faa5f3851d4f7d92f9ec1ab15/apm-sniffer/apm-agent/src/main/java/org/apache/skywalking/apm/agent/SkyWalkingAgent.java#L90-L98
so although you can annotate the plugin method with @Tag, it takes no effect

Yes, you got what i thought.  I think it's meaningful & If we do, make our developer write plugins  simplfy. @kezhenxu94

Yes, you got what i thought. I think it's meaningful & If we do, make our developer write plugins simplfy. @kezhenxu94

It supports LocalSpan only now! :)

Making no-local span is more about exact and inject ContextCarrier :) Even we add that, I think it will be closer to OpenTracing APIs, even it is not widely used.

Yes, you got what i thought. I think it's meaningful & If we do, make our developer write plugins simplfy. @kezhenxu94

It supports LocalSpan only now! :)

@dmsolr nope, it supports any kinds of span (it is not related to specific kind of span), except for those annotated by RequestMapping and similar annotations that are intercepted by other agent plugins

I got it. We work with Spring-Annotations plugins.

Codecov Report

Merging #4152 into master will decrease coverage by 0.09%.
The diff coverage is 11.62%.

@@            Coverage Diff            @@
##           master    #4152     +/-   ##
=========================================
- Coverage   27.13%   27.03%   -0.1%
=========================================
  Files        1145     1147      +2
  Lines       25105    25141     +36
  Branches     3631     3641     +10
=========================================
- Hits         6812     6797     -15
- Misses      17690    17739     +49
- Partials      603      605      +2

Impacted Files
Coverage Δ

...it/activation/trace/TraceAnnotationActivation.java
0% <ø> (ø)
:arrow_up:

.../customize/interceptor/BaseInterceptorMethods.java
0% <ø> (ø)
:arrow_up:

...agent/core/plugin/match/MethodAnnotationMatch.java
0% <0%> (ø)
:arrow_up:

...lking/apm/agent/core/util/CustomizeExpression.java
0% <0%> (ø)

...re/plugin/match/logical/LogicalMatchOperation.java
0% <0%> (ø)
:arrow_up:

...tivation/trace/TagAnnotationMethodInterceptor.java
0% <0%> (ø)

...lkit/activation/trace/TagAnnotationActivation.java
0% <0%> (ø)

...vation/trace/TraceAnnotationMethodInterceptor.java
50% <45.45%> (-20%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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

Doc of https://github.com/apache/skywalking/blob/master/docs/en/setup/service-agent/java-agent/Application-toolkit-trace.md should be updated.

@wu-sheng did you find this? https://github.com/apache/skywalking/pull/4152/files#diff-26046b3a31cc7df0b065c9cdc6b03c7d

Got it now. Maybe browser cache, can't see it when I refreshed the page last time.


blob.text is not a function #861

hope this help to chain blob response to support .text to get data as native fetch

error in code commit


[Console] Purge and Suspend buttons not working

Describe the bug
Sorry if this is a duplicate issue, did a quick search through existing issues and could only find #330  with any mention of this.
In the console, the suspend and purge buttons seem permanently greyed out and not available/working for the end user.
To Reproduce
Steps to reproduce the behavior:

create a queue in console
send 100 messages to the queue
select the radio button for the address ( left side of the address name )
open the menu "three dots" next to the delete button
attempt to purge the queue ( not available ),  or suspend the queue ( not available ) ..when clicked the words go white and not visible, then the little menu closes and nothing happens

Expected behavior
addresses should be either purged or suspended, or these options should be removed until the functionality is implemented
Screenshots

Duplicate of #330


Easy Level Tasks

Title: Completion of Easy Level Tasks for JAVA Programming Internship at CSEdge
Description:
Hello Team,
I'm pleased to inform you that I have successfully completed the Easy Level Tasks assigned as part of my JAVA Programming Internship at CSEdge. Below is a brief summary of each task along with a short description of the solution implemented:

Simple Calculator:

Developed a basic calculator application capable of performing addition, subtraction, multiplication, and division operations.
Implemented a user-friendly interface (console-based or GUI) allowing users to input two numbers and select the desired operation.
Utilized Java's built-in arithmetic operations to perform calculations accurately and efficiently.

ToDo List:

Created a console-based application for managing a list of tasks.
Implemented functionalities such as adding tasks, deleting tasks, and marking tasks as completed.
Utilized data structures like ArrayList or LinkedList to store and manage the task list efficiently.

Number Guessing Game:

Implemented a simple number guessing game where the computer generates a random number within a specified range.
Provided the player with a certain number of attempts to guess the correct number.
Incorporated user input validation to ensure that only valid guesses are accepted.

Temperature Converter:

Built an application that converts temperatures between Celsius, Fahrenheit, and Kelvin scales.
Implemented conversion formulas for each temperature scale and provided options for users to select the desired conversion.
Ensured accurate conversion results by validating input and handling edge cases effectively.

I thoroughly enjoyed working on these tasks and found them immensely beneficial for enhancing my Java programming skills. I am grateful for the opportunity to tackle these challenges and learn from them.
Thank you for your guidance and support throughout this internship.
Best regards,
MADDHURI VENU

Kinda similar with another intern used same info


Extract version bridging logic from core into new version-bridge package

The pieces being moved here is what we've been using to allow for multiple versions of @backstage/core-plugin-api to be run in parallel within an app without causing 💥. This extracts it out to a separate, but still internal, package. The idea is to make use of this in a couple of new places, most notably @backstage/catalog-plugin-react.

@benjdlambert yep, I'm letting this sit for a bit in case we can come up with a better name x)
It doesn't actually export a context though, and isn't only for contexts. That stuff is mostly just a utility that wires up the VersionedValue and a global singleton. Here's an example of non-context usage: https://github.com/backstage/backstage/blob/671015f1323a8d7ad47814cb9d69993a38dd6366/packages/core-app-api/src/routing/types.ts#L28


[2pt] API documentation: Group task

Add full documentation for your API.

Created Api doc for auth, services and reservation end points

API docummentation:-


Stop consensus if N last blocks failed to persist

Problem
neo-go database lives on a disk. If there is no more space, the database can no longer grow and we will accumulate blocks in memory with these messages in logs:
2023-12-11T19:34:26.820Z        WARN        failed to persist blockchain        {"error": "write /var/lib/neo-go/mainnet.bolt: no space left on device"}

Nothing wrong in public networks, but in privnet scenario, where all nodes are likely to be similar in configuration, this situation can happen at the same time. This is pretty bad, because then we fail with OOM, restart neo-go and lose some of the last blocks (the exact number depends on the amount of RAM and timing), not to mention possible problems with consensus after restart.
Another problem is that clients connected to this particular node could not be prepared to time travelling.
Proposed solution
Add MaxFailedToPersistBlockCount: N config setting, which allows to stop consensus service if last N blocks failed to be persisted. The administrator can then extend partition or clean space via other means.
I am ready to do a PR if we accept this solution.
This is proved to be useful and we have encountered this situation twice. The second time this solution worked as expected and we were able to clean space on the partition and continue consensusing without restarting neo-go or losing any blocks.
2023-12-11T19:34:26.820Z        WARN        failed to persist blockchain        {"error": "write /var/lib/neo-go/mainnet.bolt: no space left on device"}
2023-12-11T19:34:26.820Z        INFO        stopping consensus service
....
2023-12-15T09:20:03.126Z        WARN        failed to persist blockchain        {"error": "write /var/lib/neo-go/mainnet.bolt: no space left on device"}
2023-12-15T09:20:10.957Z        INFO        persisted to disk        {"blocks": 6, "keys": 190, "headerHeight": 243508, "blockHeight": 243508, "took": "6.830437873s"}
2023-12-15T09:20:11.394Z        INFO        starting consensus service

In general, I don't like new magic options, alternatives are:

write failures can be treated as critical for CNs. But then they will just die and lose the block for sure which is not a nice scenario either.
consensus can be stopped in the event of write failure instead, so the node will stay alive for as long as it needs to, but it won't create new blocks. Maybe this one is better.
we can write internal consensus state to the disk separately and not allow to proceed to the next dBFT round until it's OK. This is reminiscent of what C# node does already, but obviously affects performance.

At the same time, some reaction to write failures can be useful for ordinary nodes too.
Any other suggestions?

consensus can be stopped in the event of write failure instead, so the node will stay alive for as long as it needs to, but it won't create new blocks. Maybe this one is better.

So this is similar to MaxFailedToPersistBlockCount: 1 in the proposed solution? Looks also good to me. The option was initially there to behave smoothly in case of transient failures, even though I don't have any particular example, besides "no space" which is not transient. No options does indeed look better.

So this is similar to MaxFailedToPersistBlockCount: 1 in the proposed solution?

Looks like.

in case of transient failures

Yeah, usually it's either "out of space" or "your disk/FS is broken, have fun".


lsd() got an unexpected keyword argument 'scale'

I encountered this problem when running the lsd algorithm, the scale parameter does not exist in the lsd algorithm, is there something wrong with the version imported by my pylsd at pip, maybe pip install pylsd2?

I just removed the scale property and ran,

I just removed the scale property and ran,I think the problem is the lsd algorithm


Text Field - change style

Hi, I would like to change text field css. Could this be somehow simply done ?
Concretely change width and font-size. Thanks

Hi Filip, see these threads.
https://stackoverflow.com/questions/51710700/react-datepicker-input-width-will-not-adjust-to-100
https://stackoverflow.com/questions/50391206/custom-input-field-on-datepicker

Thanks


mat-tab-nav-bar -> no horizontal scrolling

Bug, feature request, or proposal:
When using mat-tab-nav-bar instead of the mat-tab-group the horizontal scrolling does not appear (when overflowing)
What is the expected behavior?
Horizontal scrolling like the mat-tab-group
What is the current behavior?
No horizontal scrolling when width gets smaller and mat-tab-nav-bar is overflowing
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

Duplicate of #2177


how do polls -> masto work

Twitter doesn't expose poll metadata unless you have access to their Enterprise API.


[WIP] Add aggregation tests

Not happy with the type conversion in AggregateFromSegmentationOperationTest.scala yet

The get() methods are defined in GraphTestUtils.scala if you want to see.


[3.3.0] deprecated scss variable

Ionic version:  (check one with "x")
[ X] 3.x
I'm submitting a ...  (check one with "x")
[ X] feature request
Current behavior:
Just updated to ionic-angular 3.3.0 and got the following warning when I build my app:
[08:07:40]  uglifyjs started ...
WARNING: you are using a deprecated variable
Backtrace:
	node_modules/ionic-angular/themes/ionic.mixins.scss:182, in mixin `deprecated-variable`
	node_modules/ionic-angular/components/searchbar/searchbar.md.scss:70

Expected behavior:
Thought you might be interested. Expected: No warning.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:
@ionic/cli-utils : 1.2.0
Cordova CLI      : 7.0.1
Ionic CLI        : 3.2.0

local packages:
@ionic/app-scripts              : 1.3.7
@ionic/cli-plugin-cordova       : 1.0.0
@ionic/cli-plugin-ionic-angular : 1.0.0
Ionic Framework                 : ionic-angular 3.3.0

System:
Node       : v7.2.1
OS         : macOS Sierra
Xcode      : Xcode 8.3.2 Build version 8E2002
ios-deploy : 1.9.0
ios-sim    : 5.0.13

This issue was moved to driftyco/ionic-app-scripts#1011

Not exactly sure why this was moved, since this is something that needs to be fixed in Ionic's SCSS files, not in app-scripts.
I'm seeing a similar warning with 3.4.2:
WARNING: you are using a deprecated variable
Backtrace:
	node_modules/ionic-angular/themes/ionic.mixins.scss:192, in mixin `deprecated-variable`
	node_modules/ionic-angular/components/button/button.ios.scss:213

WARNING: you are using a deprecated variable
Backtrace:
	node_modules/ionic-angular/themes/ionic.mixins.scss:192, in mixin `deprecated-variable`
	node_modules/ionic-angular/components/button/button.md.scss:258

WARNING: you are using a deprecated variable
Backtrace:
	node_modules/ionic-angular/themes/ionic.mixins.scss:192, in mixin `deprecated-variable`
	node_modules/ionic-angular/components/button/button.wp.scss:206


Changing retryDelay is ignored for query

Describe the bug
tl;dr; When retryDelay is updated (e.g. based on a react state variable) the useQuery hook does not seem to update the underlying retryer.

I've tried to build a query which polls an endpoint until it succeeds. Per default, it's okay to have quite a forgiving and long retry delay but based on some user action, I can actually assume the query might succeed sooner and I wanted to adjust the retryDelay (basically using it as polling interval in this case) accordingly. I then introduced a state variable which I update over the course of time and was expecting the query retry logic to adapt to it - but it didn't.
Your minimal, reproducible example
https://stackblitz.com/edit/vitejs-vite-u6rzza?file=src%2FApp.tsx
Steps to reproduce

introduce state variable to control retryDelay
use the state variable to drive the retryDelay option of useQuery
Observe that changes to retryDelay don't take effect

Expected behavior
As a user, I expected that changes to the query configuration (like changing the retryDelay) will have an effect and change the query's behaviour but instead (and contrary to other query options like e.g. refetchInterval) a change in the retryDelay did not change the retry behaviour of the query.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: macOS, Windows
Browser: Edge

Tanstack Query adapter
react-query
TanStack Query version
v5.29.2
TypeScript version
v5.2.2
Additional context
I am aware there are workarounds out there like using refetchInterval instead (this is the same example from the reproducible stackblitz using refetchInterval instead) but this requires considering the queryFn not failed so that the refetch can happen and then check based on the (fake) data whether or not to keep refetching.
Another workaround I found is to include the retryDelay within the queryKey but while this gets the job done, it feels very awkward.
I don't consider this to be a big issue and probably an edge case but it still looks like unexpected behaviour to me and it cost me a couple of hours figuring out what's going on, so I thought I'd share it.

useQuery will only update the variables within it if the queryKey  is changed. As it stands, even changing the retryDelay the query will not have its values updated, since the queryKey has not changed
If you change line 12 to this one you will see that the problem has been solved
    queryKey: ['test', retryDelay],

refetchInterval is used to revalidate the query, so it will only work if it is successful

the options do update on the query, but not on the retry. Let me explain:
when a query starts to run, we create an internal retryer and pass options from the query to it:
https://github.com/TanStack/query/blob/7368bd0f62360c2395eb31b1abf97dbaf0af46ce/packages/query-core/src/query.ts#L527-L529
Then, that retryer takes those options, returns a promise and will resolve or reject it once the whole process of fetching is complete. This takes retries, network availability etc. into account. Fore example, the query might go into paused state in between and continue with retries later.
So the retryer will see the options from the time it was created (=when the fetch started). Usually, this is what you want because the retry process is opaque. The promise will resolve or reject eventually, and then, when a refetch occurs (which is different from a retry), the new values will be respected.
We could make those values reactive in between retries, but I think that'll open up a can of worms. What if you change retries from 5 to 2 while you are at the 3rd retry? What if you change networkMode to 'always' while the query is paused because you have no network connection? It's the safer approach to just trigger the whole process (fetch + retries) with a given set of options from creation time until it is finished. It's a bit how closures work with react functions, too.
Both retry and retryDelay can be a function, so you can define them as a function and use a ref to read the latest value inside of it if you really want.


"xxxLogic" not found

I used the get.find() method somewhere, however, sometimes it gets and sometimes it says that this logic cannot be found

I think you should provide more information to help @jonataslaw or whatever can to help you with this

I have two pages, after jumping from the first page to the second page, I refresh the data of the first page by fetching the logic of the first page through the get.find() method, but sometimes it gets and sometimes it doesn't. My first page already called get.put().

[GETX] "DrawMainLogic" deleted from memory
[GETX] "DrawMainLogic" onDelete() called
[GETX] "DrawMainLogic" deleted from memory
I looked at the log and found this, why was this logic deleted.

Get.toNamed(RouteConfig.drawDevice)
I use this to push new pages.
Now I find that it seems that I opened the first page multiple times at the same time, which has a chance of causing the controller of the first page to be created and deleted multiple times and then finally stop in the deleted state.

if you push a route to the same page, the controller will be deleted and recreated (since you would have the same screen if it didn't).
I'm glad you solved your problem.
Is there anything else, or can I close this issue?

Okay, thank you


Enhancement request: provide UML component diagrams

Support UML component diagrams.

I will say no need to be a strict UML component diagram, but can draw the main components in the system and main interaction between them


Cursor stack not syncing correctly

Stack in cursor stack does not get rendered

Stack does get synced correctly, but it still doesn't get rendered. Doesn't work either after increasing rendering layer


No doc on how to run tests

There's no tox.ini and if I try to run nosetests, I'm missing ansible.utils. My venv has Ansible 1.9.2 in it as that's what we run with.

There is a tox.ini - https://github.com/willthames/ansible-lint/blob/a8f89d33ac50c30cfe125eaffffa36b68af2ae69/tox.ini
Perhaps provide a pip freeze and the output of what happens when you run tox or nosetests.
I can try and recreate on a fresh VM when I have some time, but that's not right now I'm afraid.

Right, derp, I see it - I need to rebase my fork, thanks.


Embedding layer implementation and Reader for Text dataset for training

Got a request via email to implement embedding layer required for text classification.

Great news 👍

Implemenetd here:
https://github.com/deepakkumar1984/SiaNet/blob/master/SiaNet/Model/TextDataFrame.cs


@angular/material

Hi there,
the use of 'Md' in angular material has been deprecated, as a result, I am getting this trying to use the module:-
ERROR in node_modules/@protacon/ng-virtual-keyboard/dist/virtual-keyboard.directive.d.ts(2,10): error TS2305: Module '".../node_modules/@protacon/ng-virtual-keyboard/node_modules/@angular/material/material"' has no exported member 'MdDialog'.

Solved with latest release 0.7.0


3.1.0 link is broken in docs

http://hongminhee.org/libsass-python/changes.html#version-0-7-0
Click '3.1.0'

The correct link to point at (I think?) is https://github.com/sass/libsass/releases/tag/3.1.0


CRYPTO-53: Fix assembly, pom.xml, RELEASE-NOTES, README, NOTICE.txt...etc

Fixing https://issues.apache.org/jira/browse/CRYPTO-53
Fix assembly, pom.xml, RELEASE-NOTES, README, NOTICE.txt...etc for release

Thank @winningsix , patch update

LGTM Thanks @sundapeng

Thank @winningsix


batches_to_flight_data() should not require ownership of arguments

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The signature is:
pub fn batches_to_flight_data(
    schema: Schema,
    batches: Vec<RecordBatch>,
) -> Result<Vec<FlightData>, ArrowError> {

Which means if a caller can't give up ownership (needs to re-use for something else), they need to clone these expensive objects.
Describe the solution you'd like
Accept a reference instead.
Describe alternatives you've considered
Clone away.
Additional context

@alamb @tustvold thoughts?


Http3.newQuicClientCodecBuilder().build () takes a long time

The execution time is up to 40 milliseconds :
ChannelHandler codec = Http3.newQuicClientCodecBuilder()
.sslContext(context)
.maxIdleTimeout(5000 * 5000, TimeUnit.MILLISECONDS)
.initialMaxData(10000000)
.initialMaxStreamDataBidirectionalLocal(1000000)
.build();

I think there is really nothing we can do about this


add an example file for using the code as a function

Inputs: parameters, design variables, etc.
Ouputs: whatever (e.g, aoa, cl, cd)
It should handle all the file IO in a directory specified by the user. The default should be a temporary directory (so its deleted).

Added get_sim_data function in utils.py, which gets either the input yaml file or the overall_sim_out.yaml from a simulation and a run_flag and outputs a dictionary with AOA, cl, cd data. The run_flag ensures that a new simulation is optional.

Added run_case, run_naca0012, and run_30p30n functions to give a dictionary of essential inputs and get outputs.


Added the new pdlp solver (highs > 1.7) to the description, added warning

MIP warning probably relevant to most users; Highs solver is a bit special there, it just ignores integrality without notice.

I'm not sure what the codecov does


iQontrolHomematicIpThermostat doesn't set the control mode correctly

Describe the bug
Switching from manual to automatic control mode does not work.
To Reproduce
With a HmIP-WTH-2 which has the role iQontrolHomematicIpThermostat:

Go to extended dialog
Switch from the default automatic mode to manual (which works)
Switch from manual mode back to automatic (this does not work and it also tries to trigger boost)

Expected behavior
Switching back to manual mode should work.
Screenshots & Logfiles
n/a
Versions:

Adapter version: 2.0.0
Chrome: 105

Workaround
In index.js change:
Line 9784
var value = $("input[name='DialogThermostatControlModeCheckboxradio']:checked").val();

to
var value = parseInt($("input[name='DialogThermostatControlModeCheckboxradio']:checked").val());

and
Line 9799
var setValue = setValues[index] || true;

to
var setValue = setValues[index]
if (setValue === undefined) setValue = true

(Not sure if the workaround covers all cases, I just tried for my specific case which does not include boost for example.)

Hi, I am currently working on this - sorry for the long delay. Could you please send me the RAW of CONTROL_MODE? I have no HM-IP-Thermostat so it is difficult for me to figure out the problem. Many thanks!

Hi, I am currently working on this - sorry for the long delay.

Thanks and no worries. My workaround is doing fine and if I don't have to maintain it at some point in future since you fix it upstream, too I'm already more than happy. You're project is so very functional and time saving for building web app interfaces that even living with some of those bugs long term would still be no problem. So thanks a lot for your work :)

Could you please send me the RAW of CONTROL_MODE?

Anyways, I hardly have any experience with ioBroker and HM devices yet so I'm not exactly sure what you mean with RAW... Regarding the workaround I just had a quick look at the dev tools and saw that at https://github.com/sbormann/ioBroker.iqontrol/blob/e2afa70e0ca0bed7b7167867d08681edf6810ad9/www/index.js#L9784 a string was returned while I assumed an integer is what we actually wanted. So I added the parseInt here also I'm not entirely sure if it would have been required. And than what ultimately caused the problem in my case was that at https://github.com/sbormann/ioBroker.iqontrol/blob/e2afa70e0ca0bed7b7167867d08681edf6810ad9/www/index.js#L9799
setValue will fall back to true in case setValues[index] is 0 and that is the case for AUTO-MODE. This is why I changed it like described in my first post.
And here is the ioBroker object data for CONTROL_MODE in case that helps. But if you need more, just tell me where to find it and I'll post it!
{
  "type": "state",
  "common": {
    "name": "CONTROL_MODE",
    "role": "indicator",
    "def": 0,
    "type": "number",
    "read": false,
    "write": true,
    "min": 0,
    "max": 3
  },
  "native": {
    "MIN": 0,
    "OPERATIONS": 2,
    "MAX": 3,
    "FLAGS": 1,
    "ID": "CONTROL_MODE",
    "TYPE": "INTEGER",
    "DEFAULT": 0,
    "CONTROL": "HEATING_CONTROL_HMIP.CONTROL_MODE"
  },
  "from": "system.adapter.hm-rpc.0",
  "user": "system.user.admin",
  "ts":<PHONE_NUMBER>916,
  "_id": "hm-rpc.0.000A9FXXXXXXXX.1.CONTROL_MODE",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.user"
  }
}

Would it be possible for me to connect to your system (via Anydesk or RustDesk) and see what exactly happens when you change modes? Maybe next weekend?

Any Progress on that topic? I´m experiencing the same issues

@frankhetterich as an alternative i could offer to connect to your sytem via Anydesk or RustDesk and have a look, what is happening if you press the buttons. I think, it would not take much time to understand why the bug happens - but i need to see it.

@sbormann
Shure, i´m happy to help. How can get in direct contact?

Hi, sorry, was first on holiday and then ill.
Do you have time tomorrow? We could use Anydesk or Rustdesk if you want.
By the way: are you german? :)

Hallo,
ja ich spreche Deutsch und habe auch morgen Zeit. Wenn ich mir deine Webseite im GitHub Profil anschaue, wohne ich nicht weit von dir.
Wie kommen wir in direkten Kontakt?
Ich hab bis jetzt weder anydesk noch rustdesk installiert, ist aber kein Problem.
Gruß
Frank

Hi, am besten Du installiertst Anydesk und schickst mir dann Deine Anydesk-Nummer. Wollen wir einfach eine Zeit ausmachen, z.B. 14 Uhr? Bin aber zeitlich flexibel, hab nur abends keine Zeit.

Meine Anydesk ID ist 752 169 369. 14 Uhr passt heute bei mir auch.


Form dialog for temperature has unusual/obsolete units and bad tooltips

Expected behavior
The usual C and F should be there, and maybe K and R can stay, but I have my doubts anyone is going to ask a chatbot to specify a temperature in Delisle degrees (which I had to figure out on my own because these entries just have the letters themselves as tooltips without telling what they stand for).
Screenshots

@chrimc62
Better title for generator? e.g. F -> Fahrenheit (F)

The problem is that these are the actual enum values that are returned by LUIS and they need to match.  To fix this, I think we would have to change the UI code to be able to use .uischema to control this.  With that change, I could update the generator to generate the appropriate fragment.


fix: disable "file was deleted" alert until state interaction is fixed

:tada: This PR is included in version 0.14.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support for Binary Data using Razor Pages

I have created a new Visual Studio project using the Serverless Razor Pages template provided by the AWS SDK.  It works fine when I run it locally, but after deploying it images referenced via html img tags cannot be displayed (I am using a jpeg image in my project for testing).  I believe this is due to the support for binary files not being configured correctly.
According to this page

If your web application displays images, we recommend you serve those images from Amazon S3. This is more efficient for returning static content like images, Cascading Style Sheets, etc. Also, to return images from your Lambda function to the browser, you need to do extra configuration in API Gateway for binary data.

I have added the image/jpeg to the Binary Media Types in the API Gateway settings but they are still not being served correctly.  If I try hitting the image path directly from the browser I get "The image {image path} cannot be displayed because it contains errors.".  If I retrieve the image using Powershell it looks like the content is an array of integers.
a. Can anyone tell me what I'm doing wrong?
b. If this is an issue around the Binary Media Type configuration, can the required config be added to the serverless.template file in the Razor Pages VS template

Can you move this to the aws-lambda-dotnet repository where we handle these types of issues.

Moved to https://github.com/aws/aws-lambda-dotnet/issues/279


Reduce locking potential on DOS transition endpoint

Frameworks are now committed in a separate transaction, before the
briefs. This is to prevent the framework rows from being locked for any
longer than necessary. If there are lots of briefs to update, the
frameworks could be locked unnecessarily. The Framework rows are used
heavily by lots of api calls so that would be bad.
This also changes the way the briefs are loaded to only fetch the id and
framework_id columns. There's no need to pull all the data. This should
make the process faster.

Is the thing with the mock you were asking about the other day? How did you get it working?

Yeah it is, you can see how it works now here: https://github.com/alphagov/digitalmarketplace-api/pull/838/files?utf8=✓&diff=unified#diff-baaa491be1f5bd836bc99dac51719bd4R1320
Turns out that when you give side_effect an iterable, if one of the items is a called function, then that function is called immediately and not when the mock is called. so I was giving the mock mock.side_effect = [db.app.commit(), IntegrityError] which meant that commit was being called as soon as the tests were loaded, and not at the point the mock was called in the view.
By giving side_effect a generator, we can control when the function is called. Props to @risicle for that one.

By giving side_effect a generator, we can control when the function is called. Props to @risicle for that one.

Nice 💯


problem when closing, was not issuing for the onClose event

Hey ! I may not be relevant but I would say this was the pre 4.2 code, which was causing problems because the onClose event was triggered for each outside click, even when the dropdown is already closed.
I would therefore recommand adding a condition such as
if (this.isActive)             this.onClose.emit(false);
What do you think ?


Fragments of code in LoadDefinition#selectExecutors are redundancy

Alluxio Version:
2.6.0
Describe the bug
In alluxio.job.plan.load.LoadDefinition#selectExecutors method,  are the codes with comment below has useless redundency ?
    for (Map.Entry<WorkerInfo, Collection<LoadTask>> assignment : assignments.asMap().entrySet()) {
      Collection<LoadTask> loadTasks = assignment.getValue();
      // 1. Here，split the task list.
      List<List<LoadTask>> partitionedTasks =
          CommonUtils.partition(Lists.newArrayList(loadTasks), JOBS_PER_WORKER);
      // 2. But, here merge them, it seems that the above codes are useless.
      for (List<LoadTask> tasks : partitionedTasks) {
        if (!tasks.isEmpty()) {
          result.add(new Pair<>(assignment.getKey(), Lists.newArrayList(tasks)));
        }
      }
    }

To Reproduce
Do not reproduce.
Expected behavior
Do not split origin task List, result list add tasks directly.
Urgency
low
Are you planning to fix it
If we confirm it can be optimized，i can provide a patch
Additional context
No.

@bradyoo , Hi, Bradley, I saw the commit message is "Parallelize load definition within a worker". I don't understand how it works. Could you help me to understand it？Thanks a lot.

Hi, @calvinjia , could you help me to confirm it? Thanks a lot.
related to : https://github.com/Alluxio/alluxio/pull/10692


Rework generation of types and errors ABI fields

Closes #533 and closes #516

[x] I have updated CHANGELOG.md
[ ] I have documented my contribution in Tact Docs: https://github.com/tact-lang/tact-docs/pull/PR-NUMBER
[x] I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
[x] I have run all the tests locally and no test failure was reported
[x] I have run the linter, formatter and spellchecker
[x] I did not do unrelated and/or undiscussed refactorings

An internal discussion with @Gusarich has lead us to the decision of not to change ABI generation.


Thank you for this library

Thank you so much for building this library, it saved me a lot of time. You rock!
Does it support omitting certain properties from a struct?

@virtumonde Thanks for your warm words!
Yes it does. you can do it via db:"-" struct tag, please see this docs section for details and example.
@navirick Yep, apart from omitting struct fields, you can set a custom column name via db struct tag, see this docs section for details and example

@georgysavva Excellent. I tried that out and it works great. Very cool.
Question.. though it may not apply to this project.. is there any chance you'll add (or make another project) that allows the storage of a struct similar to how this is done? Seems like going both ways would be ideal when working with structs.

You mean when we have a struct filled with data and we want to save this data to the database?
I thought about implementing this actually. The only thing that stopped me is that different databases have a different symbol for query arguments:$ for postgres, ? for mysql and etc.
It will require the user to configure this somehow and it will complicate the library, so I decided to not add it.

BTW I added the list of all features to the readme file.

Yah.. and that's a good point. Oddly I thought this was a library for pgx which was postgresql. I came to it from pgx.. but I see you support others as well. Until we have generics you would be stuck implementing db specific implementations. I am good with that :D. The name though.. scany.. may contradict the opposite direction, pushy or story... :D

I don't like the idea of db specific implementations.
I have some plans for adding configuration ability for the user, maybe after this is implemented I can start thinking about this feature.
Alternatively, we could use this approach:
For Postgres:
"INSERT INTO users (id, name, age) ($id, $name, $age)" -> "INSERT INTO users (id, name, age) ($1, $2, $3)"

For MySQL:
"INSERT INTO users (id, name, age) (?id, ?name, ?age)" -> "INSERT INTO users (id, name, age) (?, ?, ?)"

For SQL server:
"INSERT INTO users (id, name, age) (@id, @name, @age)" -> "INSERT INTO users (id, name, age) (@p1, @p2, @p3)"

So the query will contain named argument with the special symbol specific for the database of the user and scany library will detect this symbol and resolve it to the proper query, valid for this database.
This way scany doesn't need any configuration from the user, because it gets the special symbol in every query.
But I have some doubts about this solution as well. Tell me what you think

Hello. Greetings and thanks for a great piece of code.
Do you have any kind of answer how scany is similar/different to sqlx?
Some of my projects are build with sqlx, but I want to switch to pgx and that's where scany arrives. :)
Thanks in advance!

@pashagolub Thanks for reaching out!

scany supports both database/sql and pgx native interface (when you use pgx as a standalone library, without database/sql layer). Also it can be extended to work with any db library. On the other hand, sqlx only works with database/sql.
In terms of scanning and mapping abilities, scany provides all features of sqlx.
Scany has a much simpler API/interface and much fewer concepts compared to sqlx, so I believe it should be easier to use.
Scany doesn't support the opposite direction of mapping when you insert data from your struct into the query, at least for now. We had a discussion about implementing this: https://github.com/georgysavva/scany/issues/12#issuecomment-682006759. sqlxhas this feature.

Those are the main points.

I don't like the idea of db specific implementations. I have some plans for adding configuration ability for the user, maybe after this is implemented I can start thinking about this feature.
Alternatively, we could use this approach: For Postgres:
"INSERT INTO users (id, name, age) ($id, $name, $age)" -> "INSERT INTO users (id, name, age) ($1, $2, $3)"

For MySQL:
"INSERT INTO users (id, name, age) (?id, ?name, ?age)" -> "INSERT INTO users (id, name, age) (?, ?, ?)"

For SQL server:
"INSERT INTO users (id, name, age) (@id, @name, @age)" -> "INSERT INTO users (id, name, age) (@p1, @p2, @p3)"

So the query will contain named argument with the special symbol specific for the database of the user and scany library will detect this symbol and resolve it to the proper query, valid for this database.
This way scany doesn't need any configuration from the user, because it gets the special symbol in every query. But I have some doubts about this solution as well. Tell me what you think

@georgysavva are these named query parameters already implemented into scany? i could perhaps integrate my library (https://github.com/anton7r/pgxe) into scany.

Hey @anton7r. No, I actually haven't started working on this yet. So feel free to shoot a PR with your integration!

@georgysavva yeah, opened it #71


[WIP] Support loading cached QCPortal datasets

see https://github.com/MolSSI/QCFractal/pull/802)
Description
Provide a brief description of the PR's purpose here.
Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] TODO 1

Questions

[ ] Question1

Status

[ ] Ready to go

Superseded by #284


Add George pet prices

In preparation for adding these to NPC value in profit trackers.
Structure:
"PET_ID": [COMMON_PRICE, UNCOMMON_PRICE, RARE_PRICE, EPIC_PRICE, LEGENDARY_PRICE, MYTHIC_PRICE]

0 means either this rarity of the pet doesn't exist or is not sellable to George.

is there already a skyhanni pr?

Not yet.


Feat/progress

Closes: #2390

@Hugos68 similar to the Tabs review, I'll approach this from a few perspectives:
Design
No issues with the design, everything matches my expectations! Great job!
DX
FYI the native <progress> element does not allow a minimum value. I'm not sure it provides any meaningful benefit here since progress should always start a "none".

RTL
You can implement simple RTL support using classes="-scale-x-[100%]" to mirror (flip) the element on the X-axis. I'd suggest doing this with a rtl: boolean prop. When activated append this to the parent element class list.
Code
Look for my code review comments shortly after this message appears.

@Hugos68 one more note - just noticed a couple merge conflicts. Make sure those are sorted before the next PR review as well. Please and thanks!

@Hugos68 I've completed my review and implemented a few changes.
See all changes in the commit here:
https://github.com/skeletonlabs/skeleton/pull/2556/commits/be24ed70d725bb9c062ac1f0b4962466ca5e004a

Cleaned up the preview page styles (because I have OCD heh)
Removed any references to min
Setup RTL demos (see below regarding animations)
Extended Tailwind to include animate-indeterminatevia the Skeleton Tailwind plugin
Renamed meterIndeterminateAnim to meterAnimate to follow Tailwind convention

The only issue I could not resolve was why the validation error for a value that exceeds a max is not working for me. But if it's working for you I'm not going to stress about it.
I'll follow up in a moment to resolve the merge conflicts.


vLLM always places spaces between special tokens

I have a model that in certain cases is expected to generate sequences of special tokens.  When I call in to vLLM the expected special tokens in the text of the response have spaces between them.  This is caused by an incomplete (when compared with the adapted huggingface version) API for _convert_tokens_to_string_with_added_encoders.  The referenced implementation (see below) allows for the caller to pass a spaces_between_special_tokens: bool but this option is absent from the vLLM implementation.
    # Adapted from
    # https://github.com/huggingface/transformers/blob/v4.28.0/src/transformers/tokenization_utils.py#L921
    # NOTE(woosuk): The following code is slow because it runs a for loop over
    # the output_tokens. In Python, running a for loop over a list can be slow
    # even when the loop body is very simple.```

I will work on a PR to add this functionality and plumb it through the SamplingParams.


How to get bitmap value after applying filter ?

Hello
I want to get filtered bitmap value after applying filter on image. How do i get it ?

Check this Wiki

thanks it works.


Mysql Problems

I keep getting this "warning" saying my DB driver is not initialized. I have tried changing the DB names, the DB driver, username, password and I still get this warning. I'm also stuck when joining on "vrp: checking identifiers". There is no documentation on how to actually fix this issue.

This is my server.cfg
endpoint_add_tcp "<IP_ADDRESS>:30120"
endpoint_add_udp "<IP_ADDRESS>:30120"

set DTF_Password "12345"

start mapmanager
start chat
start spawnmanager
start sessionmanager
start fivem
start hardcap
start rconlog
start playernames

start ghmattimysql

start vrp

restart sessionmanager

Here is the Base.lua DB config.
cfg.db = {   driver = "ghmattimysql",   host = "<IP_ADDRESS>",   database = "vrp",   user = "root",   password = "" }
And here is an image of my DB:

No tables are made, nothing.

Issues are not for help, after carefully reading the doc you can use the discord or the FiveM forum topic for that purpose.

same problem here!


Message Stuck on "Installing App" - How to Cancel

I'm currently testing the app and have disabled custom apps in the Teams admin center.  for 14 hours now. Is there any way to cancel the message to remove it from the queue?
Another note - in the v3 to v4 upgrade documentation (found here) under the "Add Permissions to Your App" section, I'm not clear if I'm supposed to add these permissions to the v3 app or the v4 app. The article is about deploying the v4 app, but the screenshots show the v3 app. I applied the permissions to the v4 app - not sure if that's related to the issue.

Think applying to the v4 app is correct. You should have 2 registered apps with v4. There's an authors app (needs the API permissions) and the end user app which doesn't apart from read users.

Think applying to the v4 app is correct. You should have 2 registered apps with v4. There's an authors app (needs the API permissions) and the end user app which doesn't apart from read users.

If allow custom apps is not permitted by policy or in the org wide settings the app won't proactively install. It will run through each target user and fail the proactive install. So how long it takes probably depends on how many users you're trying to send the message to. If you go into the Azure resource group you can see the tranctions under the Application Insights resource.

If allow custom apps is not permitted by policy or in the org wide settings the app won't proactively install. It will run through each target user and fail the proactive install. So how long it takes probably depends on how many users you're trying to send the message to. If you go into the Azure resource group you can see the tranctions under the Application Insights resource.

Thank you so much @bungleweed! You nailed it. After waiting a couple of days, the message would ultimately fail to most users. After disabling the "Auto Install" and republishing the "Authors" app, everything works great. I'll manage the app installation using a Teams policy. Thanks again for your responses!

Thank you so much @bungleweed! You nailed it. After waiting a couple of days, the message would ultimately fail to most users. After disabling the "Auto Install" and republishing the "Authors" app, everything works great. I'll manage the app installation using a Teams policy. Thanks again for your responses!

Hi, @mbearchell can you please elaborate on how you resolve this issue. am stuck at this right now. I have a tenant with users of up to 17000, The message got deliver if I use teams or security groups. but stuck at installing if we sent to everyone.  Note we deploy the user app to org-wide using the policy. thank you

Hey @lukman-oyee  - sure thing! In my case, we were blocking custom apps in our Global Teams App Permission Policy. This meant that Company Communicator wasn't able to install the application if you enabled "Auto Install" since it's a custom app (which is blocked on the tenant level).
In our case, the solution was:

Change the "Custom App" setting in the global Teams "App Permission Policy" to "Allow specific apps and block all others" then select "Company Communicator" as an app we're going to allow.
Change the global Teams "App Setup Policy" and selected "Company Communicator" to auto-install on all user instances of Teams by default (so that it would get installed, even before a message is sent out).
Redeploy the app to Azure using the desired "Auto Install" setting. I have found that simply changing this setting in Azure doesn't seem to work as desired, but republishing the app does.

I hope that helps!

Thank you @mbearchell  and @bungleweed.
We are closing this issue as it is solved.


cannot build old style SQL project in insiders, M1

Issue Type: Bug
Created a SQL project from AdventureWorksLT as an old-style SQL project.  Attempted to build and received a build failure for missing targets.
(SDK-style SQL projects build fine)
[ Build ]
> "/usr/local/share/dotnet/dotnet"  build "/Volumes/Storage/CodeRepos/sample-sandbox/deleteme/DatabaseProjectAdventureWorksLT/DatabaseProjectAdventureWorksLT.sqlproj" /p:NetCoreBuild=true /p:NETCoreTargetsPath="/Users/drewsk/.azuredatastudio-insiders/extensions/microsoft.sql-database-projects-0.19.0/BuildDirectory"
stdout: Microsoft (R) Build Engine version 17.2.0+41abc5629 for .NET
stdout: Copyright (C) Microsoft Corporation. All rights reserved.
stdout:
stdout:
stdout: /Volumes/Storage/CodeRepos/sample-sandbox/deleteme/DatabaseProjectAdventureWorksLT/DatabaseProjectAdventureWorksLT.sqlproj(55,3): error MSB4019: The imported project "/Users/drewsk/.azuredatastudio-insiders/extensions/microsoft.sql-database-projects-0.19.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the expression in the Import declaration "/Users/drewsk/.azuredatastudio-insiders/extensions/microsoft.sql-database-projects-0.19.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets" is correct, and that the file exists on disk.
stdout:
stdout:
stdout:
stdout: Build FAILED.
stdout:
stdout: /Volumes/Storage/CodeRepos/sample-sandbox/deleteme/DatabaseProjectAdventureWorksLT/DatabaseProjectAdventureWorksLT.sqlproj(55,3): error MSB4019: The imported project "/Users/drewsk/.azuredatastudio-insiders/extensions/microsoft.sql-database-projects-0.19.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the expression in the Import declaration "/Users/drewsk/.azuredatastudio-insiders/extensions/microsoft.sql-database-projects-0.19.0/BuildDirectory/Microsoft.Data.Tools.Schema.SqlTasks.targets" is correct, and that the file exists on disk.
stdout:     0 Warning(s)
stdout:     1 Error(s)
stdout:
stdout: Time Elapsed 00:00:00.15

Extension version: 0.19.0
Azure Data Studio version: azuredatastudio-insiders 1.40.0-insider (de3683dd018b1f28744f9eb8797a825bb38d784c, 2022-10-24T05:31:36.093Z)
OS version: Darwin arm64 22.1.0
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.51GB free)

Process Argv

Screen Reader
no

VM
0%

This is happening because the sql database projects extension hasn't been updated in insiders since the dependency on the DacFx dlls in STS was removed back in September. Copying the targets file from the DacFx nuget to the STS output was removed in https://github.com/microsoft/sqltoolsservice/pull/1674.
When the sql database projects extension gets updated in insiders, this shouldn't be a problem anymore. Users previously building legacy projects in insiders shouldn't be affected if they still have the targets file in the BuildDirectory from the past.


Don't interfere with global seed, using optional torch.generator support

torch-audiomentations should support torch.generator optionally, instead of always using the global seed.
Libraries that use pseudo-randomness and always interfere with the global seed are an anti-pattern, because they impede reproducibility.
A key use-case is this: You have validation set that is unrealistically "clean", but you want to add augmentations to simulate your test environment, which is more diverse. However, you want to deterministically introduce augmentations, so the validation set is the same every time.
The only workaround now is to with mucking with your global seed (that could have unintended consequences, and is easy to footgun on). The best solution is that torch-audiomentations can, optionally, use randomness independently from the global environment.

I forgot that one can obtain the global RNG state, then deterministically seed before augmentation, then recover the global RNG state.


amass: 4.0.4 -> 4.1.0

Diff: https://github.com/OWASP/Amass/compare/refs/tags/v4.0.4...v4.1.0
Changelog: https://github.com/OWASP/Amass/releases/tag/v4.1.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 246211 run on x86_64-linux 1

2 packages built:

amass
amass.wordlists


chore: update wesql component definition password generate rules

/cherry-pick release-0.8

fix issue: https://github.com/apecloud/kubeblocks/issues/6392


/api directory in root folder, should exist under /en/ for globalisation

Jekyll-redirect-from gem installed in site and requires  files to be in distinct folders. Pull request on its way.

Fixed.


[Feature]: Read pages non-sequentially when using HTTP Range Requests (and release from memory)

Is the feature relevant to the Firefox PDF Viewer?
No
Feature description
Currently, using HTTP Range Requests helps to quickly load and visualize the first pages of large PDF files, but it still requires loading all pages sequentially to render the last page, wouldn't it be possible to load pages non-sequentially (i.e. load from the last page backwards when loading page from history) and release page data from memory when loading new pages through Range Requests?
This would reduce loading times when the user wants to read the last page and avoid crashing low-memory machines.

This is the view from my system monitor after opening a 1.5 GB PDF on the last page (loaded from viewer history).
Even tho the pages are rendered only when visible, the page data seems to be held indefinitely.
Other PDF viewers
Evince seems to non-sequentially load only visible pages, appearing faster and using less memory.

Currently, using HTTP Range Requests helps to quickly load and visualize the first pages of large PDF files, but it still requires loading all pages sequentially to render the last page,

That would be caused by the structure of your PDF document then, since in many cases we unfortunately have to load many (or even all) pages in order for necessary data validation to be possible.

Even tho the pages are rendered only when visible, the page data seems to be held indefinitely.

In the default viewer, pages that are scrolled (sufficiently) out of view will have their resources released. Additionally, global resources will also be released (on both the main- and worker-threads) after a period of inactivity in the viewer.
(However, if/when the memory is being released is up to the browser and operating system and thus isn't something a JavaScript application can control.)

Given that this issue is unfortunately quite "light" on the details, we probably cannot really help much here.

That would be caused by the structure of your PDF document then, since in many cases we unfortunately have to load many (or even all) pages in order for necessary data validation to be possible.
I tried linearizing the document with QPDF but saw no change in behavior or improvement in performance, maybe something else is broken whithin the document, but thanks for the input.
In the default viewer, pages that are scrolled (sufficiently) out of view will have their resources released. Additionally, global resources will also be released (on both the main- and worker-threads) after a period of inactivity in the viewer.
Maybe I'm using an older or misconfigured version, got the demo to work locally and it worked as desired.


docker-machine status should return non-0 for errors

Without this patch:
❯ docker-machine status foo
error getting state for host foo: machine does not exist
Error

❯ echo $?
0

Will re-open after I sort out the licensing details.