[go_router] StatefulShellRoute can not reset StatefulShellBranch's state

What package does this bug report belong to?
go_router
What target platforms are you seeing this bug on?

Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  adaptive_breakpoints:
    dependency: transitive
    description:
      name: adaptive_breakpoints
      sha256: "56dd5f1016f4d5732b80628d1b63a29d8c9cabe4d66a8a5fe63fdbec7b3af5cd"
      url: "https://pub.dev"
    source: hosted
    version: "0.1.7"
  adaptive_navigation:
    dependency: "direct main"
    description:
      name: adaptive_navigation
      sha256: "87c08c5c8b954f2266518c1efb98a1d0ae09cd8cbef69c4d4fd7ea28d4b9fd51"
      url: "https://pub.dev"
    source: hosted
    version: "0.0.10"
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  clock:
    dependency: transitive
    description:
      name: clock
      sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  collection:
    dependency: "direct main"
    description:
      name: collection
      sha256: ee67cb0715911d28db6bf4af1026078bd6f0128b07a5f66fb2ed94ec6783c09a
      url: "https://pub.dev"
    source: hosted
    version: "1.18.0"
  cupertino_icons:
    dependency: "direct main"
    description:
      name: cupertino_icons
      sha256: d57953e10f9f8327ce64a508a355f0b1ec902193f66288e8cb5070e7c47eeb2d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.6"
  fake_async:
    dependency: transitive
    description:
      name: fake_async
      sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.1"
  ffi:
    dependency: transitive
    description:
      name: ffi
      sha256: "7bf0adc28a23d395f19f3f1eb21dd7cfd1dd9f8e1c50051c069122e6853bc878"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.0"
  file:
    dependency: transitive
    description:
      name: file
      sha256: "5fc22d7c25582e38ad9a8515372cd9a93834027aacf1801cf01164dac0ffa08c"
      url: "https://pub.dev"
    source: hosted
    version: "7.0.0"
  flutter:
    dependency: "direct main"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_test:
    dependency: "direct dev"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_web_plugins:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  go_router:
    dependency: "direct main"
    description:
      path: ".."
      relative: true
    source: path
    version: "13.1.0"
  logging:
    dependency: "direct main"
    description:
      name: logging
      sha256: "623a88c9594aa774443aa3eb2d41807a48486b5613e67599fb4c41c0ad47c340"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  matcher:
    dependency: transitive
    description:
      name: matcher
      sha256: "1803e76e6653768d64ed8ff2e1e67bea3ad4b923eb5c56a295c3e634bad5960e"
      url: "https://pub.dev"
    source: hosted
    version: "0.12.16"
  material_color_utilities:
    dependency: transitive
    description:
      name: material_color_utilities
      sha256: "9528f2f296073ff54cb9fee677df673ace1218163c3bc7628093e7eed5203d41"
      url: "https://pub.dev"
    source: hosted
    version: "0.5.0"
  meta:
    dependency: transitive
    description:
      name: meta
      sha256: a6e590c838b18133bb482a2745ad77c5bb7715fb0451209e1a7567d416678b8e
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  nested:
    dependency: transitive
    description:
      name: nested
      sha256: "03bac4c528c64c95c722ec99280375a6f2fc708eec17c7b3f07253b626cd2a20"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  path:
    dependency: transitive
    description:
      name: path
      sha256: "8829d8a55c13fc0e37127c29fedf290c102f4e40ae94ada574091fe0ff96c917"
      url: "https://pub.dev"
    source: hosted
    version: "1.8.3"
  path_provider_linux:
    dependency: transitive
    description:
      name: path_provider_linux
      sha256: f7a1fe3a634fe7734c8d3f2766ad746ae2a2884abe22e241a8b301bf5cac3279
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  path_provider_platform_interface:
    dependency: transitive
    description:
      name: path_provider_platform_interface
      sha256: "88f5779f72ba699763fa3a3b06aa4bf6de76c8e5de842cf6f29e2e06476c2334"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  path_provider_windows:
    dependency: transitive
    description:
      name: path_provider_windows
      sha256: "8bc9f22eee8690981c22aa7fc602f5c85b497a6fb2ceb35ee5a5e5ed85ad8170"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  platform:
    dependency: transitive
    description:
      name: platform
      sha256: "12220bb4b65720483f8fa9450b4332347737cf8213dd2840d8b2c823e47243ec"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.4"
  plugin_platform_interface:
    dependency: transitive
    description:
      name: plugin_platform_interface
      sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.8"
  provider:
    dependency: "direct main"
    description:
      name: provider
      sha256: cdbe7530b12ecd9eb455bdaa2fcb8d4dad22e80b8afb4798b41479d5ce26847f
      url: "https://pub.dev"
    source: hosted
    version: "6.0.5"
  shared_preferences:
    dependency: "direct main"
    description:
      name: shared_preferences
      sha256: "81429e4481e1ccfb51ede496e916348668fd0921627779233bd24cc3ff6abd02"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.2"
  shared_preferences_android:
    dependency: transitive
    description:
      name: shared_preferences_android
      sha256: "8568a389334b6e83415b6aae55378e158fbc2314e074983362d20c562780fb06"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  shared_preferences_foundation:
    dependency: transitive
    description:
      name: shared_preferences_foundation
      sha256: "7708d83064f38060c7b39db12aefe449cb8cdc031d6062280087bc4cdb988f5c"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.5"
  shared_preferences_linux:
    dependency: transitive
    description:
      name: shared_preferences_linux
      sha256: "9f2cbcf46d4270ea8be39fa156d86379077c8a5228d9dfdb1164ae0bb93f1faa"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  shared_preferences_platform_interface:
    dependency: transitive
    description:
      name: shared_preferences_platform_interface
      sha256: "22e2ecac9419b4246d7c22bfbbda589e3acf5c0351137d87dd2939d984d37c3b"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  shared_preferences_web:
    dependency: transitive
    description:
      name: shared_preferences_web
      sha256: "7b15ffb9387ea3e237bb7a66b8a23d2147663d391cafc5c8f37b2e7b4bde5d21"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.2"
  shared_preferences_windows:
    dependency: transitive
    description:
      name: shared_preferences_windows
      sha256: "841ad54f3c8381c480d0c9b508b89a34036f512482c407e6df7a9c4aa2ef8f59"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_span:
    dependency: transitive
    description:
      name: source_span
      sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  stack_trace:
    dependency: transitive
    description:
      name: stack_trace
      sha256: "73713990125a6d93122541237550ee3352a2d84baad52d375a4cad2eb9b7ce0b"
      url: "https://pub.dev"
    source: hosted
    version: "1.11.1"
  stream_channel:
    dependency: transitive
    description:
      name: stream_channel
      sha256: ba2aa5d8cc609d96bbb2899c28934f9e1af5cddbd60a827822ea467161eb54e7
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  term_glyph:
    dependency: transitive
    description:
      name: term_glyph
      sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"
  test_api:
    dependency: transitive
    description:
      name: test_api
      sha256: "5c2f730018264d276c20e4f1503fd1308dfbbae39ec8ee63c5236311ac06954b"
      url: "https://pub.dev"
    source: hosted
    version: "0.6.1"
  url_launcher:
    dependency: "direct main"
    description:
      name: url_launcher
      sha256: c512655380d241a337521703af62d2c122bf7b77a46ff7dd750092aa9433499c
      url: "https://pub.dev"
    source: hosted
    version: "6.2.4"
  url_launcher_android:
    dependency: transitive
    description:
      name: url_launcher_android
      sha256: "507dc655b1d9cb5ebc756032eb785f114e415f91557b73bf60b7e201dfedeb2f"
      url: "https://pub.dev"
    source: hosted
    version: "6.2.2"
  url_launcher_ios:
    dependency: transitive
    description:
      name: url_launcher_ios
      sha256: "75bb6fe3f60070407704282a2d295630cab232991eb52542b18347a8a941df03"
      url: "https://pub.dev"
    source: hosted
    version: "6.2.4"
  url_launcher_linux:
    dependency: transitive
    description:
      name: url_launcher_linux
      sha256: ab360eb661f8879369acac07b6bb3ff09d9471155357da8443fd5d3cf7363811
      url: "https://pub.dev"
    source: hosted
    version: "3.1.1"
  url_launcher_macos:
    dependency: transitive
    description:
      name: url_launcher_macos
      sha256: b7244901ea3cf489c5335bdacda07264a6e960b1c1b1a9f91e4bc371d9e68234
      url: "https://pub.dev"
    source: hosted
    version: "3.1.0"
  url_launcher_platform_interface:
    dependency: transitive
    description:
      name: url_launcher_platform_interface
      sha256: a932c3a8082e118f80a475ce692fde89dc20fddb24c57360b96bc56f7035de1f
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  url_launcher_web:
    dependency: transitive
    description:
      name: url_launcher_web
      sha256: fff0932192afeedf63cdd50ecbb1bc825d31aed259f02bb8dba0f3b729a5e88b
      url: "https://pub.dev"
    source: hosted
    version: "2.2.3"
  url_launcher_windows:
    dependency: transitive
    description:
      name: url_launcher_windows
      sha256: ecf9725510600aa2bb6d7ddabe16357691b6d2805f66216a97d1b881e21beff7
      url: "https://pub.dev"
    source: hosted
    version: "3.1.1"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  web:
    dependency: transitive
    description:
      name: web
      sha256: afe077240a270dcfd2aafe77602b4113645af95d0ad31128cc02bce5ac5d5152
      url: "https://pub.dev"
    source: hosted
    version: "0.3.0"
  win32:
    dependency: transitive
    description:
      name: win32
      sha256: "464f5674532865248444b4c3daca12bd9bf2d7c47f759ce2617986e7229494a8"
      url: "https://pub.dev"
    source: hosted
    version: "5.2.0"
  xdg_directories:
    dependency: transitive
    description:
      name: xdg_directories
      sha256: faea9dee56b520b55a566385b84f2e8de55e7496104adada9962e0bd11bcff1d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
sdks:
  dart: ">=3.2.0 <4.0.0"
  flutter: ">=3.16.0"

Steps to reproduce
In stateful shell navigation with a bottom nav bar I would like to reset the current tab to an initial state AND jump to a different tab.
My naive attempts to simply combine two Router.go() statements have not worked and I am not sure if this should be working, or if there is another way to implement the desired behavior.
Expected results
Tab C should be visible but when returning to Tab A, that one should be in the initial state.
Actual results
When using go(), replace(), or branch_to(), the reset of Tab A is ignored.
When using pop(), Tab A is reset, but becomes unusable afterwards. (No more clicking on A details.)
Code sample
https://github.com/githubmonkey/flutter_packages/commit/bbeec93c14e33d1294bc06584f07662f1909cc80
This change adds an additional button to the official statefull_shell_route example. The idea is to  reset one tab to the initial route while jumping to a second tab.
It
Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.9, on macOS 13.6.3 22G436 darwin-arm64, locale en-GB)
    • Flutter version 3.16.9 on channel stable at /Users/sylvia/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 41456452f2 (9 days ago), 2024-01-25 10:06:23 -0800
    • Engine revision f40e976bed
    • Dart version 3.2.6
    • DevTools version 2.28.5

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/sylvia/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 73.0.4
    • Dart plugin version 231.8109.91

[✓] VS Code (version 1.85.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.78.0

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 13.6.3 22G436 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 121.0.6167.139

[✓] Network resources
    • All expected network resources are available.

• No issues found!```

</details>

Thanks for the report. I can reproduce the issue with the modified package sample code.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.16.9, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.16.9 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 41456452f2 (14 hours ago), 2024-01-25 10:06:23 -0800
    • Engine revision f40e976bed
    • Dart version 3.2.6
    • DevTools version 2.28.5

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.85.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 120.0.6099.234

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.20.0-1.0.pre.20, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.20.0-1.0.pre.20 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f8a77225f3 (13 hours ago), 2024-02-04 14:28:18 +0000
    • Engine revision f34c658b96
    • Dart version 3.4.0 (build 3.4.0-99.0.dev)
    • DevTools version 2.31.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.85.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (3 available)
    • iPad (mobile)   • 00008103-000A1464346A201E • ios            • iOS 17.2 21C62
    • macOS (desktop) • macos                     • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome                    • web-javascript • Google Chrome 121.0.6167.139

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

I am having this problem, how do we reset the state of statefulshellroute? if it'd be the regular shellRoute, that's easy, state automatically get reset, there should be a way to force that behavior in statefulshellroute too

Gracias por atenderme
El dom, 30 jun 2024, 10:19, Berkay Can @.***> escribió:

I am having this problem, how do we reset the state of statefulshellroute?
if it'd be the regular shellRoute, that's easy, state automatically get
reset, there should be a way to force that behavior in statefulshellroute
too
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/142867#issuecomment-2198478000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSPMHDCQS3HE2H344VGGDZJ65QRAVCNFSM6AAAAABCYG7XLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGQ3TQMBQGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have the same issue as well. can anyone help?


Add RabbitMQ Template

Goal
A feature-rich RabbitMQ template for building robust and scalable message queue systems.
Payout
$250
Expectation
Contribute a RabbitMQ template showcasing queue creation, message publishing, and consumer handling. Consider demonstrating RabbitMQ clustering and high-availability configurations. Comprehensive documentation will assist users in making the most of RabbitMQ.

completed by @6ixfalls
template repo: https://github.com/railwayapp-templates/rabbitmq


why divide Jτaa by 2

Hi, thanks for the great work. I have a question that I would like to ask.
In the input.jl file, within the function input_impulse!, why is it necessary to divide Jτaa by 2 when calculating pbody.state.Jτ2, especially considering that in impulse_transform, Diagonal([sones(3); 0.5 * sones(3)]) * transpose([X Q]) has already divided by 2?

Thanks for your answer.

I guess that this is related to dealing with the orientation as a quaternion.


Add more values to recognized templates to mixer integration test

Improve error verbosity

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

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

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

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

/ok-to-test

Assigning Mandarjog cause these changes are just an addition to his previous string slice of crs. Should be a super quick review for him. :)
/assign @mandarjog

@johnholiver: PR needs rebase.

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

@kyessenov could you have a look at this PR? It is super simple and it has been open for more than a month. I've just added the other templates that can be used during integration testing. I've noticed you even added the apa template here like 2w ago (made me rebase).
This will allow ppl that are following the OOT adapter walkthrough to do integration test to adapters that are not based on metric template (mine, for example, is based on authorization). Otherwise, devs can be confused by the failures in their integration tests.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: johnholiver
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

@johnholiver: PR needs rebase.

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

@johnholiver: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-unit-tests

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

@johnholiver: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-integ-local-tests

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

@johnholiver: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-integ-local-tests

prow/istio-presubmit.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-presubmit

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

@johnholiver: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-integ-local-tests

prow/istio-presubmit.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-presubmit

prow/istio-integ-k8s-tests.sh
ba567bfaae6895417b0caf61f5f738de08edd632
link
/test istio-integ-k8s-tests

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

@kyessenov just rebased it and pointed the PR to release-1.1
Not sure why but the tag cla:yes got removed by doing that

CLA bot has a random bug that invalidates PRs switching the base...
I assume the CLA is signed since the bot has not complained the first time.

/lgtm

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

Needs approval from an approver in each of these files:

mixer/OWNERS [kyessenov]

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


Plot.ecdf goes into the infinite loop

Hi,
Looks like Plot.ecdf love its work so much that it can run forever :-)
The following code snippet says that "subplot 0 0 is out" and hangs while eating 100% of CPU.
let plot_histogram basename a =
  let open Owl_plplot in
  let stt = calculate_vector_stats a in
  let fn = sprintf "%s-%f-%f.ps" basename stt.min stt.max in
  let m = Mat.of_array a (A.length a) 1 in
  let h = Plot.create ~m:2 ~n:1 fn in
  Plot.(subplot h 0 0; histogram ~h ~bin:200 m);
  printf "I: plot_histogram: subplot 0 0 is out\n%!";
  Plot.(subplot h 1 0; ecdf ~h m);
  printf "I: plot_histogram: subplot 1 0 is out\n%!";
  Plot.output h;

gdbprofiler says the process spend most of its time (after entering Plot.ecdf) in __memmove_sse2_unaligned_erms. GitHub doesn't allow me to attach out.cpuprofile, so please see screenshots below:

So here is a simple script I've tried:
open Owl_plplot

let x = Dense.Ndarray.D.(uniform [|100|]);;
let x' = Dense.Ndarray.D.to_array x;;
let a, b = Stats.ecdf x';;

let h = Plot.create "test.png";;
let _ = Plot.ecdf ~h x;;
let _ = Plot.output h;;

Both  Stats.ecdf and Plot.ecdf work as expected. So perhaps the issue is related with specific input data used, e.g. a very large ndarray?

@jzstark thank you jianxin, feel free to remove the bug tag if it is certain that this is not a bug.

@jzstark, the size of the array is pretty moderate: 22716 elements. What is the O-complexity of Stats.ecdf?

@jzstark, please, ignore my previous question.
I found the problem: Stats.ecdf goes into infinity if there is at least one NaN among the values of the input array.

Hey, friendly bump here.
Will this be fixed any time soon or noted in the documentation?

Added to the bulk fix PR: https://github.com/owlbarn/owl/pull/534


[Proposal] Infer vite's dev-server port on SSR to leverage [ngSrc]'s full path automatically

Which scope/s are relevant/related to the feature request?
platform
Information
Hello,
Currently, when working with SSR locally on Vite DevServer, there's no way to infer the baseURL to prepend requests for the assets given that Domino can't figure out what's going on.
When debugging Angular's source code, window.location.href is resolved to / which is used to construct the asset url like new URL(assetPath, window.location.href). Right now, if you just throw a relative path like /assets/image.png the server will throw an exception and that's it.
In production things are easier because we can provide the imageLoader, no big deal.
Right now, if you dont supply a full path like http://localhost:{PORT}/assets/image.png, SSR will throw an error when using img[ngSrc].
Describe any alternatives/workarounds you're currently using
What I do today for development purposes

Tell Vite's server that we want to work with specific port and it should be strict.
If we're in development, provide an environment variable like DEV_PORT.

file: vite.config.ts
// ...redacted
server: {
    port: 4202,
    strictPort: true
},
define: {
    ...(mode === 'development'
        ? {
              'import.meta.env.DEV_PORT': '4202'
          }
        : {}),
    'import.meta.vitest': mode !== 'production'
}
// ...redacted

In my assetPath function, test if we're running in SSR and if there's a DEV_PORT defined and if so, return the full local url so SSR can successfully fetch the image.

file: assets-path.ts
export const assetPath = (file: string) => {
    if (import.meta.env.SSR && !!import.meta.env?.['DEV_PORT']) {
        return `http://localhost:${import.meta.env.DEV_PORT}/assets/${file}`;
    }

    return `/assets/${file}`;
};

This works but it's hackish (at least for me).
Proposal
Some ideas came to mind:

Vite's analog-plugin could leverage some of this and provide the DEV_PORT automatically like I'm doing, ports can be randomly assigned, so this would make things less hardcoded.

Or analog-plugin could receive a new property like: { ssrBaseUrl: 'INFER' | (string & {}) }.
2.1 if a string is passed, its supposed to be a full base url like: 'http://localhost:4200' or;
2.2 if 'INFER' is passed, analog plugin could somehow infer internally the dev-server port and somehow inject the value http://localhost:{VITE_DEV_PORT} into window.location.href in Domino (or some other magic) so everything would work out of the box.

These are my main ideas, I'm happy to hear about you guys :)
PS: I can't provide any PR for this today because I have 29 days to finish a gigant project, but I felt it was worth it to bring this discussion here.
Renato
I would be willing to submit a PR to fix this issue

[ ] Yes
[X] No

I had this same problem, but the problem I could see was the url param in the server method inside of main.server.ts, that URL should be absolute, not only the URL path; seeing here https://github.com/analogjs/analog/blob/beta/packages/vite-plugin-nitro/src/lib/plugins/dev-server-plugin.ts#L51, the req and res object are sent in a third parameter, and I were able to solve the ngSrc problem with this update:
import { bootstrapApplication } from '@angular/platform-browser';
import { AppComponent } from './app/app.component';
import { config } from './app/app.config.server';
import { renderApplication } from '@angular/platform-server';
import { enableProdMode } from '@angular/core';
import { IncomingMessage } from 'node:http';

if (import.meta.env.PROD) {
  enableProdMode();
}

const bootstrap = () => bootstrapApplication(AppComponent, config);

export default async function render(
  _path: string,
  document: string,
  { req }: { req: IncomingMessage & { originalUrl: string } },
) {
  const protocol = getRequestProtocol(req);
  const { originalUrl, headers } = req;

  return await renderApplication(bootstrap, {
    document,
    url: `${protocol}://${headers.host}${originalUrl}`,
  });
}

export function getRequestProtocol(
  req: IncomingMessage,
  opts: { xForwardedProto?: boolean } = {},
) {
  if (
    opts.xForwardedProto !== false &&
    req.headers['x-forwarded-proto'] === 'https'
  ) {
    return 'https';
  }

  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  return (req.connection as any)?.encrypted ? 'https' : 'http';
}

Interesting find @osnoser1! If this works when deployed also, we could probably provide this in the object with req and res as baseUrl. This could be an opportunity to use it server side also with an interceptor so you don't have to prefix HttpClient requests with the full baseUrl

Awesome 😄
I'm fixing the problems I found when integrating analog withå the current app I'm working on. When I deploy it, I'll test it and let you know if this change worked


Scala 3 support

Fixes #17

Thanks for bringing the Scala 3 branch up to the latest version, @raboof. Since we do not want to squash this branch but merge it, would it be possible to clean the commits up a bit? I'm not super concerned about all those little merges but maybe the cleanup/format commits could be squashed?

would it be possible to clean the commits up a bit? I'm not super concerned about all those little merges but maybe the cleanup/format commits could be squashed?

Yes, done! (I forgot what a PITA rebasing merges was, even with --rebase-merges and rerere :laughing:)

now that https://github.com/apache/incubator-pekko/pull/273 is merged, can you upgrade the scala 3 version to 3.2.2? - jackson 2.14.2 uses Scala v3.2 as the minimum supported version

Jup, done - I kinda had to since the build takes the latest Pekko snapshot by default, and that now indeed requires 3.2.2 for Scala 3.

Incase people are not aware, we are discussing merging this branch for the initial release on the mailing list (https://lists.apache.org/thread/pcyfs9wqsd81od20mk3jtd0w04bf0lm6). As you can tell, there is overall agreement that this is a good idea.
@raboof From what I can tell the only thing that is necessary is to cleanup the commits, correct?

@raboof From what I can tell the only thing that is necessary is to cleanup the commits, correct?

I'd say it's cleaned up. ideally we'd rebase to fix 62afca7 where it was introduced instead of in a separate commit, but that goes back quite far and is tedious/error-prone, so I propose we just leave it where it is now.
Some more reviewing and testing would be good (I haven't tested in depth since a number of complicated rebases, so a mistake could have slipped in), otherwise I think this is probably good to go.

@raboof could you update to Scala 3.3.0? Pekko core now uses that version (Scala 3.3.0 was released yesterday).

@pjfanning @raboof
@jrudolph Set up a cleaned up version of this branch with all of the merge conflicts removed, let me find it.

Closed in favour of https://github.com/apache/incubator-pekko-http/pull/150 which has the PR history cleaned up by @jrudolph and merged with latest main.


Add Athena Connection Support

Add an Athena URI builder to make_connection_string(), assuming for now that Athena is the only connection when an AWS connection type is given. This is an incorrect assumption, but we currently do not have asks for other use cases figuring out how to differentiate these may be a non-trivial issue.
Closes: #90

@diman82 let me know if this is working for you and I'll merge+release

Hello, thank you for this PR! Just when I needed to add Athena validation to a project.
I have a particular use-case that is conflicting with my combination of parameters:
  GreatExpectationsOperator(
      task_id="my_gx_validation",
      data_asset_name="some_data_asset_name_not_important",
      query_to_validate="SELECT * FROM my_db.my_table WHERE dt = '2023-02-07-03",
      conn_id="aws_default",
      checkpoint_name="my_checkpoint",
      data_context_root_dir=ge_root_dir,
  )

I have the athena connection string specified in my datasources in the great_expectations config:
datasources:
  awsathena_datasource:
    module_name: great_expectations.datasource
    data_connectors:
      default_runtime_data_connector_name:
        module_name: great_expectations.datasource.data_connector
        batch_identifiers:
          - default_identifier_name
        class_name: RuntimeDataConnector
      default_inferred_data_connector_name:
        module_name: great_expectations.datasource.data_connector
        include_schema_name: true
        class_name: InferredAssetSqlDataConnector
    execution_engine:
      module_name: great_expectations.execution_engine
      connection_string: awsathena+rest://@athena.us-east-1.amazonaws.com?s3_staging_dir=s3://my-athena-results-bucket
      class_name: SqlAlchemyExecutionEngine
    class_name: Datasource

My checkpoint config:
name: my_checkpoint
config_version: 1.0
template_name:
module_name: great_expectations.checkpoint
class_name: Checkpoint
run_name_template: '%Y%m%d-%H%M%S-my-run-name-template'
expectation_suite_name: my_expectation_suite_name
batch_request: {}
action_list:
  - name: store_validation_result
    action:
      class_name: StoreValidationResultAction
  - name: store_evaluation_params
    action:
      class_name: StoreEvaluationParametersAction
  - name: update_data_docs
    action:
      class_name: UpdateDataDocsAction
      site_names: []
evaluation_parameters: {}
runtime_configuration: {}
validations:
  - batch_request:
      datasource_name: awsathena_datasource
      data_connector_name: default_inferred_data_connector_name
      data_asset_name: my_data_asset_name
      data_connector_query:
        index: -1
    expectation_suite_name: my_expectation_suite_name
profilers: []
ge_cloud_id:
expectation_suite_ge_cloud_id:

So, if I try to remove the data_asset_name from the operator parameters
  GreatExpectationsOperator(
      task_id="my_gx_validation",
      #data_asset_name="some_data_asset_name_not_important",
      query_to_validate="SELECT * FROM my_db.my_table WHERE dt = '2023-02-07-03",
      conn_id="aws_default",
      checkpoint_name="my_checkpoint",
      data_context_root_dir=ge_root_dir,
  )

in order to instead let the operator pick the existing datasource from the checkpoint, the operator fails at line 199 during the constructor validation:
        # A data asset name is also used to determine if a runtime env will be used; if it is not passed in,
        # then the data asset name is assumed to be configured in the data context passed in.
        if (self.is_dataframe or self.query_to_validate or self.conn_id) and not self.data_asset_name:
            raise ValueError("A data_asset_name must be specified with a runtime_data_source or conn_id.")

Is it possible to have this issue addressed in this PR ? Or maybe I'm not using the correct combination of parameters 😄
Thanks again for your work denimalpaca!

OK, so I've setup the following code in my dag:
TABLE = "country_codes"
REGION = "us-west-2"
ATHENA_DB = "dbr"
S3_PATH = "s3://seekingalpha-data/aws-athena-query-results-744522205193-us-west-2"
base_path = Path(__file__).parents[2]
ge_root_dir = os.path.join(base_path, "include", "great_expectations")

with DAG(
    "great_expectations.athena",
    start_date=datetime(2023, 2, 2),
    description="Example DAG showcasing loading and data quality checking with Athena and Great Expectations.",
    doc_md=__doc__,
    schedule_interval=None,
    template_searchpath=os.path.join(sql_templates_dir, 'great_expectations'),
    catchup=False,
) as dag:
    ge_athena_validation = GreatExpectationsOperator(
        task_id="ge_athena_validation",
        data_context_root_dir=ge_root_dir,
        conn_id="aws_default",
        params={"region": REGION, "athena_db": ATHENA_DB, "s3_path": TABLE},
        expectation_suite_name="dbr.country_codes",
        data_asset_name=TABLE,
        fail_task_on_validation_failure=False,
    )
    chain(
        ge_athena_validation,
    )

And I get the following error message:
[2023-02-15, 14:01:29 UTC] {base.py:73} INFO - Using connection ID 'aws_default' for task execution.
[2023-02-15, 14:01:29 UTC] {taskinstance.py:1768} ERROR - Task failed with exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/great_expectations/datasource/new_datasource.py", line 66, in __init__
    self._execution_engine = instantiate_class_from_config(
  File "/usr/local/lib/python3.9/site-packages/great_expectations/data_context/util.py", line 92, in instantiate_class_from_config
    class_instance = class_(**config_with_defaults)
  File "/usr/local/lib/python3.9/site-packages/great_expectations/execution_engine/sqlalchemy_execution_engine.py", line 328, in __init__
    self.engine = sa.create_engine(connection_string, **kwargs)
  File "<string>", line 2, in create_engine
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/deprecations.py", line 375, in warned
    return fn(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/create.py", line 522, in create_engine
    entrypoint = u._get_entrypoint()
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/url.py", line 662, in _get_entrypoint
    cls = registry.load(name)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 343, in load
    raise exc.NoSuchModuleError(
**sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:awsathena.rest**

@diman82 can you try installing the package "pyathena[SQLAlchemy]"

Hello, thank you for this PR! Just when I needed to add Athena validation to a project.
I have a particular use-case that is conflicting with my combination of parameters:
  GreatExpectationsOperator(
      task_id="my_gx_validation",
      data_asset_name="some_data_asset_name_not_important",
      query_to_validate="SELECT * FROM my_db.my_table WHERE dt = '2023-02-07-03",
      conn_id="aws_default",
      checkpoint_name="my_checkpoint",
      data_context_root_dir=ge_root_dir,
  )

I have the athena connection string specified in my datasources in the great_expectations config:
datasources:
  awsathena_datasource:
    module_name: great_expectations.datasource
    data_connectors:
      default_runtime_data_connector_name:
        module_name: great_expectations.datasource.data_connector
        batch_identifiers:
          - default_identifier_name
        class_name: RuntimeDataConnector
      default_inferred_data_connector_name:
        module_name: great_expectations.datasource.data_connector
        include_schema_name: true
        class_name: InferredAssetSqlDataConnector
    execution_engine:
      module_name: great_expectations.execution_engine
      connection_string: awsathena+rest://@athena.us-east-1.amazonaws.com?s3_staging_dir=s3://my-athena-results-bucket
      class_name: SqlAlchemyExecutionEngine
    class_name: Datasource

My checkpoint config:
name: my_checkpoint
config_version: 1.0
template_name:
module_name: great_expectations.checkpoint
class_name: Checkpoint
run_name_template: '%Y%m%d-%H%M%S-my-run-name-template'
expectation_suite_name: my_expectation_suite_name
batch_request: {}
action_list:
  - name: store_validation_result
    action:
      class_name: StoreValidationResultAction
  - name: store_evaluation_params
    action:
      class_name: StoreEvaluationParametersAction
  - name: update_data_docs
    action:
      class_name: UpdateDataDocsAction
      site_names: []
evaluation_parameters: {}
runtime_configuration: {}
validations:
  - batch_request:
      datasource_name: awsathena_datasource
      data_connector_name: default_inferred_data_connector_name
      data_asset_name: my_data_asset_name
      data_connector_query:
        index: -1
    expectation_suite_name: my_expectation_suite_name
profilers: []
ge_cloud_id:
expectation_suite_ge_cloud_id:

So, if I try to remove the data_asset_name from the operator parameters
  GreatExpectationsOperator(
      task_id="my_gx_validation",
      #data_asset_name="some_data_asset_name_not_important",
      query_to_validate="SELECT * FROM my_db.my_table WHERE dt = '2023-02-07-03",
      conn_id="aws_default",
      checkpoint_name="my_checkpoint",
      data_context_root_dir=ge_root_dir,
  )

in order to instead let the operator pick the existing datasource from the checkpoint, the operator fails at line 199 during the constructor validation:
        # A data asset name is also used to determine if a runtime env will be used; if it is not passed in,
        # then the data asset name is assumed to be configured in the data context passed in.
        if (self.is_dataframe or self.query_to_validate or self.conn_id) and not self.data_asset_name:
            raise ValueError("A data_asset_name must be specified with a runtime_data_source or conn_id.")

Is it possible to have this issue addressed in this PR ? Or maybe I'm not using the correct combination of parameters 😄
Thanks again for your work denimalpaca!

Hey @deathwebo , in this case you should remove the conn_id, as that is only supposed to be specified if you aren't using a checkpoint or data context config. The addition of the conn_id param was to allow users who are primarily Airflow users to not have to write checkpoint configs or data context configs.

@diman82 have you had a chance to test this?

@denimalpaca Sorry, awas too busy last 2 weeks.
I've started testing it, seems to be working fine, but I need a couple of more days to verify and get back with confirmation/additional findings..

@diman82 any news here? Would love to merge this PR and do a release.


[Issue] HTML is vanilla

The HTML templates are currently unmodified from the starter files and need to be re-written to better show information and coding competency.

Fixed up the html to look a lot less slapdash. Won't have time to make things prettier for this project.


sf deploy metadata throws Error while deploying destructive changes.

Summary
I am using "sf deploy metadata" to deploy the destructive changes in org, It throws the error when I have an empty destructiveChanges.xml file which is an expected behaviour But suppose I am executing the command as a part of continuous integration/ Pipeline then I may have destructive Changes or may not. So when I do not have anything to delete I will keep the destructiveChanges.xml as
destructiveChanges.xml
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
      <version>62.0</version>
</Package>

and this is where when using below command it throws an error and failed to execute further commands.
command:
sf deploy metadata --manifest manifest/destructiveChanges/package.xml  -o <OrgAlias> --pre-destructive-changes manifest/destructiveChanges/destructiveChanges.xml

it throws: Error (NothingToDeploy): No local changes to deploy.
It should be a warning but it throws an error for empty file. I did tried using placeholder or random component with --ignore-warnings flag but it might be possible that when I mis-spell any class or component name it'll ignore rather than giving me an error.
Steps To Reproduce
Provided all the details in summery.

Download salesforce CLI.
authorise the org first and provide alias using "sf org web login --alias myorg".
create a folder with package.xml and destructiveChanges.xml file.
keep destructiveChanges.xml as same as package.xml and try running above command.
It will throw an error "No local changes to deploy."

Expected result
I know that it's an expected result that cli throws an error of no local changes to deploy. But What should be steps to be care of or any implementation suggestion to avoid running or to skip the command if the destructiveChanges.xml is empty.
Actual result
It throws an error. "No local changes to deploy." as expected.
Additional information
package.xml
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <version>62.0</version>
</Package>

destructiveChanges.xml
Empty File:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <version>62.0</version>
</Package>

With Placeholder:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>NoClassExistWithTheName</members>
        <name>ApexClass</name>
    </types>
    <version>62.0</version> <!-- Use the version that is compatible with your Salesforce org -->
</Package>

System Information
Bash or Vs Code Terminal.
{
  "architecture": "darwin-arm64",
  "cliVersion"<EMAIL_ADDRESS>  "nodeVersion": "node-v22.11.0",
  "osVersion": "Darwin 23.6.0",
  "rootPath": "/Users/saurabh.mulay/.local/share/sf/client/2.67.7-3acb081",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.8 (core)",
    "@oclif/plugin-commands 4.1.8 (core)",
    "@oclif/plugin-help 6.2.16 (core)",
    "@oclif/plugin-not-found 3.2.25 (core)",
    "@oclif/plugin-plugins 5.4.15 (core)",
    "@oclif/plugin-search 1.2.14 (core)",
    "@oclif/plugin-update 4.6.10 (core)",
    "@oclif/plugin-version 2.2.15 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.21 (core)",
    "@oclif/plugin-which 3.2.17 (core)",
    "@salesforce/cli 2.67.7 (core)",
    "apex 3.6.2 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.73 (core)",
    "data 3.11.3 (core)",
    "deploy-retrieve 3.15.11 (core)",
    "devops-center 1.2.26 (user) published 25 days ago (Sun Nov 03 2024)",
    "info 3.4.18 (core)",
    "limits 3.3.39 (core)",
    "marketplace 1.3.4 (core)",
    "org 5.1.4 (core)",
    "packaging 2.9.0 (core)",
    "schema 3.3.40 (core)",
    "settings 2.4.4 (core)",
    "signups 2.6.1 (user) published 25 days ago (Sat Nov 02 2024) (latest is 2.6.6)",
    "sobject 1.4.45 (core)",
    "telemetry 3.6.20 (core)",
    "templates 56.3.29 (core)",
    "trust 3.7.41 (core)",
    "user 3.6.2 (core)",
    "@salesforce/sfdx-scanner 4.7.0 (user) published 29 days ago (Tue Oct 29 2024)"
  ]
}

Using a destructive changes manifest as you have above does not cause any deployment problems.  However, deploying an empty manifest (the package.xml as in your example above) is user error and will throw an error by design.  An error will cause a non-zero exit code from the command so that scripts will not continue.  Changing this behavior would cause regressions from lots of customers who depend on this behavior.


Unable to get EVAL-ADTF3175D-NXZ data for using ADIToFGUI Tool

Hi,
We are having EVAL-ADTF3175D-NXZ eval system and are trying to get data using the ADIToFGUI Windows Tool as per instruction provided here.
However, we are not able to get any information from the Camera.
We also tried the Troubleshooting steps provided here but they didn't work.
Following are some of the logs we found in GUI App:
I0826 18:25:42.834313  1528 ADIToF.cpp:83] SDK version: 3.0.0 | branch: adsd3500 | commit: 5eef987
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0826 18:25:46.657864  1528 system_impl.cpp:80] SDK built with websockets version:3.1.0
I0826 18:25:46.658862  1528 usb_sensor_enumerator.cpp:55] Looking for USB connected sensors
I0826 18:25:46.685214  1528 system_impl.cpp:123] SDK built with websockets version:3.1.0
I0826 18:25:46.686213  1528 network_sensor_enumerator.cpp:53] Looking for sensors over network
[2022/08/26 18:25:46:6900] NOTICE: Creating Vhost 'default' (serving disabled), 1 protocols, IPv6 off
I0826 18:25:51.933068 17564 ADIMainWindow.cpp:1128] Preparing camera. Please wait...
I0826 18:25:51.934067 17564 camera_itof.cpp:133] Initializing camera
[2022/08/26 18:25:51:9456] NOTICE: Creating Vhost 'default' (serving disabled), 1 protocols, IPv6 off
I0826 18:25:57.094662 17564 camera_itof.cpp:206] Found Depth ini file: ../config/RawToDepthAdsd3500_mp.ini
I0826 18:25:57.094662 17564 camera_itof.cpp:206] Found Depth ini file: ../config/RawToDepthAdsd3500_qmp.ini
I0826 18:25:57.094662 17564 camera_itof.cpp:218] Current Depth ini file is: ../config/RawToDepthAdsd3500_mp.ini
E0826 18:25:57.119984 17564 camera_itof.cpp:261] Failed to read intrinsics for adsd3500!
E0826 18:25:57.119984 17564 ADIMainWindow.cpp:1152] Could not initialize camera!

Can anyone help to troubleshoot the same?

Hello,
We are looking into this and we will come back with an answer as soon as possible.

With the latest SDK release, I was able to capture and visualize the Frame on Linux platform.
Closing the issue.


feat: feature gated geth compatibilty

Addresses #11

Heads up @roynalnaruto sha3 already ships with keccak256 so you can lose the tiny-keccak dependency I think 🙏

This is amazing, thank you so much for the quick PR! This definitely works well for me. I'm working on adding commands to cast to make it have more feature parity with seth and this will help with listing the local keystore accounts


运行readme里面的例子出错，是提供的模型和参数对不上吗？

Drop parameter dla_up.ida_2.up_1.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.actf.0.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.actf.0.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.actf.0.running_mean.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.actf.0.running_var.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.actf.0.num_batches_tracked.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.conv.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.conv.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.conv.conv_offset_mask.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.node_1.conv.conv_offset_mask.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.actf.0.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.actf.0.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.actf.0.running_mean.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.actf.0.running_var.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.actf.0.num_batches_tracked.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.conv.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.conv.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.conv.conv_offset_mask.weight.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.
Drop parameter dla_up.ida_2.proj_2.conv.conv_offset_mask.bias.If you see this, your model does not fully load the pre-trained weight. Please make sure you have correctly specified --arch xxx or set the correct --num_classes for your own dataset.

更新了代码，可以了。。


Using fingerprintx as library

How to use as go libray, is there some exmaple？

Hey @faint-star, I just added some example code here: https://github.com/praetorian-inc/fingerprintx/blob/main/examples/scan.go and updated the readme. Thanks for your interest in fingerprintx!


Init golang and implement disk providers.

Description

Update .gitignore for golang.
Implement providers and models.
Add Init functions for models.
Implement base functions.
Implement DiskFileManager, DiskDirectoryManager and SystemPathProvider.
Implement unit test for DiskFileManager, DiskDirectoryManager and SystemPathProvider.
Add changelog.

Related issue(s)
#20 Init golang implementation
#21 Implement disk managers for golang
Checklist:

[x] It refers to an Issue.
[ ] It fixes a bug.
[x] It's a new feature (non-breaking change which adds functionality)
[ ] It's a breaking (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] CHANGELOG is updated.
[ ] Related language label is selected.

@mahdidelzendeh72 @Ali-YousefiTelori
Code conventions are not similar in different programming languages, so we can't implement exact same structure in different languages. For example there is no exception in Go and Rust, we should handle exceptions using error and Result. There isn't async keyword or Async methods or functions in Go but we have goroutine.
Best practices in one language like C# could be anti pattern in other languages like Go or Rust.
I believe we can't implement exact same code structure in all languages, best practices, code conventions and standards don't let us to do it, but we can implement readable and standard alternatives in other languages.


libkbfs: actually keep a favorites cache

This commit changes the favorites cache to not refresh until it is invalidated instead of refreshing every time.
Relevant PRs:

https://github.com/keybase/client/pull/14370
https://github.com/keybase/keybase/pull/3059

That's what we're currently doing - I was just concerned that we don't want
to block on fetching the favorites if we're offline - there's a situation
whereby we get invalidated and then get offline before the new favorites
arrive and then can't get the favorites at all. But it's a pretty unlikely
event.
On Wed, Oct 24, 2018 at 7:50 PM Jeremy Stribling<EMAIL_ADDRESS>wrote:

@strib commented on this pull request.
Looks good, but we should wait until the server side changes are in, and
then rerun CI, before fully approving this.
In libkbfs/favorites.go
https://github.com/keybase/kbfs/pull/1870#discussion_r227996860:

@@ -340,8 +338,9 @@ func (f *Favorites) RefreshCache(ctx context.Context) {
}
}

-// Get returns the logged-in users list of favorites. It
-// doesn't use the cache.
+// Get returns the logged-in user's list of favorites. It uses the cache.
+// TODO: decide on behavior if we've gotten an invalidation but not an updated
What are the choices here? If we've gotten an invalidation, I think the
Get should block on fetching the favorites (which is what should be
happening in this PR if I'm reading the code right.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/kbfs/pull/1870#pullrequestreview-168164550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEeyP7iIPa4e95wqHgoe3vGwrO-RU-gZks5uoPzVgaJpZM4X11A0
.

Oops, when I said "forthcoming" I really meant "there's another PR for that that I've now updated.
The newest commit invalidates the favorites cache after a week, for reasons described here: https://github.com/keybase/client/pull/14554


Add Awakener

Awakener allows cross-thread waking of a Poller instance.

@cynecx I've pushed a commit with your suggestions, let's see if it works :).

It worked, thanks @cynecx and @eduardosm.


Additional arguments onStateEnter are undefined

Version
v2000.1.4
What browsers are you seeing the problem on?
Chrome, Firefox
What happened?
The additional parameter is undefined. The console output is:
SHOVEL INTO undefined

What's the expected behavior?
The console output should be:
SHOVEL INTO right

Minimum reproducable code
const player = k.add([
    k.pos(16, constants.tileSize / 2),
    k.sprite("player", { frame: 0 }),
    k.state("idle", ["idle", "shovel"]),
    "player",
  ]);

  player.onStateEnter("shovel", (direction) => {
    console.log("SHOVEL INTO", direction);
  });

/** ... */

player.enterState("shovel", "right");

Live demo
No response
Is there an existing issue for this?

[X] I've searched and there is no existing issue for this bug

This is embarrassing hh keeping having problems with this. Fixed in #425 and released as v2000.1.5


Enabling gRPC service using deployment yaml

Purpose

Enabling gRPC service to be used APIM Analytics

Goals

This change allows WSO2 micro-gateway to publish analytics data using a gRPC service.

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


Pyperplan package.

Closes #14

Note that there is no run script. This means that it won't appear on the path at all, and pyperplan as a command-line executable will remain with the pip entrypoint.

Minor updates suggested.

Looks good to me. But does this support running planutils run pyperplan?

It does not. I suppose I could put a check in for planutils run {xyz} that checks for {xyz} on $PATH, and suggests just running that directly.
In this situation (i.e., runnable packages without a run file), it's more or less just an alias for installing from the right place.

I think it's easiest to have a "run" file for all packages. In most cases they will just forward all arguments to the main binary, but then usage is consistent.

But there's a clash on the namespace. In the activated environment, the pyperplan run file will never be hit because the pip installed is on the path first. What's the advantage of having it exist?

The advantage is that planutils run pyperplan works. Or am I overlooking something?

Hrmz...well I guess it's only an issue if the planutils PATH is prepended. Will make sure that is the order put in place, and bring in the run.


Question about changing backbone

Hello, I have a question about changing the backbones.
I want to change the backbone retinanet to ssd.
( customize 3 just like you customized 1 to 2 according to the paper )
I tried customizing it, and the following error occurred. ( look at link4 )
TypeError: init() missing 1 required positional argument: 'input_size'
So when I deleted input_size, I got the following error.
NameError: name 'input_size' is not defined
model, train_cfg, test_cfg are well inputted.
How can I fix this?

https://github.com/open-mmlab/mmdetection/blob/master/configs/_base_/models/retinanet_r50_fpn.py
https://github.com/yuantn/MI-AOD/blob/master/configs/_base_/retinanet_r50_fpn.py
https://github.com/open-mmlab/mmdetection/blob/master/configs/_base_/models/ssd300.py
https://github.com/bluvory/kuaicv/blob/main/ssd_vgg_custom.py

Have you modified Line 4~7 in configs/MIAOD.py?
The './_base_/retinanet_r50_fpn.py' need to be replaced by your ssd_vgg_custom.py.

yes I already fixed that

What if you uncomment the Line 6 in link 4?

If i uncomment it, this error occurs.
TypeError: init() missing 1 required positional argument: 'input_size'

Can I have a look at your outermost configuration file (like configs/MIAOD.py instead of configs/_base_/models/ssd300.py )?

handRL is our custom dataset and this file (hand2voc) has been changed to voc format.
https://github.com/bluvory/kuaicv/blob/main/MIAOD.py
https://github.com/bluvory/kuaicv/blob/main/handRL.py

I think that maybe you should add or modify something in this SSD+VOC configuration file to your MIAOD.py, such as train_pipeline, test_pipeline, and so on.
You can refer to the difference between MIAOD.py and the RetinaNet+VOC configuration file.

I changed the MIAOD.py like this on your advice,
but the error continues because the ssd_vgg_custom.py has not changed.
TypeError: init() missing 1 required positional argument: 'input_size'

It is really a confusing error... Could you provide your full output log?

here, I put both cases of errors in this link.
(input_size=300 is in (ssd_vgg_custom.py)[https://github.com/bluvory/kuaicv/blob/main/ssd_vgg_custom.py]
https://github.com/bluvory/kuaicv/blob/main/error.py

I think I have got the point of the problem, that is, you need to add input_size=input_size in the model.backbone (anywhere in Lines 11-16) in your ssd_vgg_custom.py.
The deep reason is that, all of this MI-AOD repository is based on MMDetection V2.3.0 but not the latest version of MMDetection. There are some differences between these two versions.

I got it. Thank you for your kind response.
Have a nice day :)

@bluvory  cna you please share ur implementation with retinanet repo


glfwCreateWindowSurface not defined for vulkan_raii.hpp

OS and version: Debian GNU/Linux 12 (bookworm) - Gnome Version 43.6
Compiler version: gcc (Debian 12.2.0-14) 12.2.0
Release or commit: 3.3.8-1
Build log:

[main] Building folder: XTVulcan build-debug
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /home/omaka/Documents/GitHub/XTVulcan/build --config Debug --target build-debug -j 6 --
[build] [ 25%] Building CXX object CMakeFiles/application.dir/src/application.cpp.o
[build] /home/omaka/Documents/GitHub/XTVulcan/src/application.cpp: In member function ‘void Application::createSurface()’:
[build] /home/omaka/Documents/GitHub/XTVulcan/src/application.cpp:320:62: error: ‘surfaceHandle’ was not declared in this scope
[build]   320 |     if (glfwCreateWindowSurface(*instance, window, nullptr, &surfaceHandle) != VK_SUCCESS)
[build]       |                                                              ^~~~~~~~~~~~~
[build] /home/omaka/Documents/GitHub/XTVulcan/src/application.cpp:320:9: error: ‘glfwCreateWindowSurface’ was not declared in this scope; did you mean ‘glfwCreateWindow’?
[build]   320 |     if (glfwCreateWindowSurface(*instance, window, nullptr, &surfaceHandle) != VK_SUCCESS)
[build]       |         ^~~~~~~~~~~~~~~~~~~~~~~
[build]       |         glfwCreateWindow
[build] gmake[3]: *** [CMakeFiles/application.dir/build.make:76: CMakeFiles/application.dir/src/application.cpp.o] Error 1
[build] gmake[2]: *** [CMakeFiles/Makefile2:111: CMakeFiles/application.dir/all] Error 2
[build] gmake[1]: *** [CMakeFiles/Makefile2:92: CMakeFiles/build-debug.dir/rule] Error 2
[build] gmake: *** [Makefile:124: build-debug] Error 2
[proc] The command: /usr/bin/cmake --build /home/omaka/Documents/GitHub/XTVulcan/build --config Debug --target build-debug -j 6 -- exited with code: 2
[driver] Build completed: 00:00:06.896
[build] Build finished with exit code 2

It seems like the error is cause because the compiler thinks VK_VERSION_1_0 is not defined in glfw3.h

#if defined(VK_VERSION_1_0)

But I can confirm it is defined when vulkan_raii.hpp is included. I don't know what else could cause this.
The issue can be fixed by manually including vulkan_core.h in the source file. But this shouldn't be necessary since vulkan_core.h is included in the vulkan_raii.hpp.

Are you including the vulkan_raii.hpp header before the GLFW one?

My header file was included last in my source file.
Thanks.

Header & library order issues are a pain. Glad you've resolved it!


Add Windows Server 2019 to steps

[Enter feedback here]
In Step 0, # 6, you say:  "On all source servers and on any destination servers running Windows Server 2012 R2 or Windows Server 2016, in Windows Admin Center,"
If this applies to Windows Server 2019 also, can you please update it to say so.
I am a Microsoft Certified Trainer who often directs students to Doc pages and you'd be surprised how often folks can get it wrong unless you are very specific.

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

ID: 2aa81041-3a2a-961a-05d5-4a845cc74ae2
Version Independent ID: fadf165a-5c81-0102-e096-7f527483313b
Content: Migrate a file server by using Storage Migration Service
Content Source: WindowsServerDocs/storage/storage-migration-service/migrate-data.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:IngridAtMicrosoft
gh issue comment 4426 -b #assign:IngridAtMicrosoft

Hello @davemct ,
We'd like to express our gratitude for your commitment to our documentation. Unfortunately, we’ve recently fallen short of our usual standards in addressing documentation concerns in a timely manner and offer our apologies for any inconvenience we’ve caused.
Because this issue is now outdated, we’re closing this request. If we've addressed the documentation issue, this thread will also be closed. This article is up to date for Windows Server 2019 and 2022, so versions referred to in specific steps should be accurate.
However, if you believe there’s still a documentation concern, you're encouraged to open a new GitHub issue. We welcome any additional suggestions for improving our documentation to provide a more satisfactory experience in the future. Thanks for your understanding and continued support.
#please-close


Added Tasks 1.8, 1.9, & 1.10 to BasicGates workbook

Added Tasks 1.8, 1.9, & 1.10 to BasicGates workbook

Could you check where the conflicts are coming from? Probably from a very similar place to the last pull request

Closeed due to conflicts

One thing you can try is copy the workbook with the new tasks someplace safe, delete your repository and fork it from scratch. This way you get a clean slate for your main branch, to which you can do those changes incrementally, rather than carrying the whole 50-commit history on this. I know I sometimes get my repo clones to the point at which this is the easiest thing to do :-)

I must have read your mind, that's exactly what I did.
I'm also making much use of draft pull requests.
On Sat, Nov 20, 2021 at 12:22 AM Mariia Mykhailova @.***>
wrote:

One thing you can try is copy the workbook with the new tasks someplace
safe, delete your repository and fork it from scratch. This way you get a
clean slate for your main branch, to which you can do those changes
incrementally, rather than carrying the whole 50-commit history on this. I
know I sometimes get my repo clones to the point at which this is the
easiest thing to do :-)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/QuantumKatas/pull/692#issuecomment-974535824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACS4UW56IQIOL5LFLLIPQX3UM3L3JANCNFSM5IHYQ4PQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I had a few more weird problem messages so I worked on adding  just one
extra task with draft pull request task 1.8, , which now has passed the
parser! I have the rest of the tasks ready, I thought to add them maybe two
at a time.
On Sat, Nov 20, 2021 at 12:22 AM Mariia Mykhailova @.***>
wrote:

One thing you can try is copy the workbook with the new tasks someplace
safe, delete your repository and fork it from scratch. This way you get a
clean slate for your main branch, to which you can do those changes
incrementally, rather than carrying the whole 50-commit history on this. I
know I sometimes get my repo clones to the point at which this is the
easiest thing to do :-)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/QuantumKatas/pull/692#issuecomment-974535824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACS4UW56IQIOL5LFLLIPQX3UM3L3JANCNFSM5IHYQ4PQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


multiple highlight colours for ground items plug-in

Is your feature request related to a problem? Please describe. I would like to be able to recolour different ground items different colours that are either all untradable or in the same price bracket.
A clear and concise description of what the problem is** only 1 highlight colour option in ground items
Describe the solution you'd like
A clear and concise description of what you want to happen. up to 3 different highlight colours that can be selected and cycled through (clicking the little + sign on a item on the ground would cycle the set colours you have chosen)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've
considered.  im not sure but maybe a customisable colour for individual or specific items, though i feel like this could be a bit messy or cause clutter in the settings with too many individual items coloured.
Additional context
Add any other context or screenshots about the feature request here.

i would like to colour the mallignum root planks differently to secondaries and would also like to change the colour of the iron axe and lockpick seperately too. its a minor but nice quality of life update (:

duplicate of https://github.com/runelite/runelite/issues/12274


Why are repeated fields only allowed at the last position of a paths string?

https://github.com/golang/protobuf/issues/1179 broke us and I don't understand why this constraint exists.  It noted,

field_mask.proto mentions that ...
// Field masks are used to specify a subset of fields that should be
// returned by a get operation or modified by an update operation.

...

// # Field Masks in Projections
// ...
// A repeated field is not allowed except at the last position of a
// paths string.

...

// # Field Masks in Update Operations
// ...
// Note that a repeated field is only allowed in the last position of a `paths` string.

Given those statements, I think FieldMask.IsValid should return false if a path contains a repeated field that is not in the last position.

Given the example in https://github.com/golang/protobuf/issues/1179 why is nests.s not a reasonable path?  Imagine extending Nested with a second field.  It seems reasonable to say you want one of those fields but not both.

Thanks @dsnet and @cybrcodr.  I've created a feature request over there, https://github.com/protocolbuffers/protobuf/issues/8547.


Graphics - Materials / Automated rendering tests

Changes
Material API for shaders
Doc describing the material API: https://md.fragcolor.xyz/CJ99UMacRAmsLj9Xnm2P3w
Automated graphics tests
Test code inside src/gfx/tests to test all graphics/windowing features supported by our engine.
src/gfx/tests/test_data.cpp/hpp contains code to load/store per platform/render API snapshots and either compare them against the previous or store a new copy
Automated graphics tests for asm.js
emrun provided with the emscripten SDK provides usefull functionality for running the above tests in a browser and reading back the results.
The test main.cpp and test_data.cpp contain calls to emrun_copyFileToOutput that copies the test results and generated test data (screenshots) to a dump_out folder
Builtin data management
We require some files to always be included in order to run (shader headers, fonts).
For asm.js this is done through --preload-file.
For other platforms that can bundle files alongside binaries src\gfx\paths.hpp provides some logic to find the correct paths for bundled assets independently of the working directory/executable location.
Previous content that was referenced from the bgfx source folder (fonts/precompiled shaders) have been moved to the content folder along with the makefiles. This allows us to keep the bgfx repo synced to upstream
Before removing draft status I plan to remove the precompiled shaders in favour of using the material system.
Bundled shaderc as a static/shared library
Allows the bgfx shader compiler to run directly from built executables. This removes the dependency on this being built externally and greatly reduces the amount of wrapper code required to work on asm.js when linked statically for example.
There are some issues:

inputs/outputs temporary files to/from the filesystem
not multi-threaded (due to preprocessor)
need to manually sync changes from bgfx shaderc

TODO

Replace usage of shaders with materials in current tests
Update GFX.Model/Draw & GLTF block implementations to use materials
Add graphics tests to CI runs where possible to run on test runners/virtual framebuffer

The main purpose of these changes is the provide a system that allow custom shaders/materials to work together with rendering functionality provided by the engine.
While there are a bunch of changes here I believe it's faster to make these at the same time rather than making some of these changes individually and having to update the tests each time which will later be changed anyway (this includes everything related to GFX.Model/Shader/Draw)
Dependent on guus/cmake_cleanup since I needed the project structure.

Looks of interesting stuff, a quick point I really would have appreciated we discussed before executing:

shaderc as library.. I tried for many days (weeks?) and scrapped it because it makes our binaries huge and it's something that can much easier scaled via opening processes... the current implementation (is already half supporting multi-thread) should just be ported to use edn for easier maintenance (our philosophy should be use chainblocks when possible). It's also not possible to use directly in WASM btw.

To be continued...

Looks of interesting stuff, a quick point I really would have appreciated we discussed before executing:
* shaderc as library.. I tried for many days (weeks?) and scrapped it because it makes our binaries huge and it's something that can much easier scaled via opening processes... the current implementation (is already half supporting multi-thread) should just be ported to use edn for easier maintenance (our philosophy should be use chainblocks when possible). It's also not possible to use directly in WASM btw.

To be continued...

Yeah as noted there are some issues. The thing is you don't have to include the hlsl/spirv/metal backend along if you're building for asm.js which makes the shader compiler very small. Already have the tests passing using this.
Since we're not using multi-threading shader compilation at the moment it might be worth using this for simplicity (independent builds, separate js files)
Anyways this was mainly to have the graphics code independently testable. It should be possible to use the exiting code for shader compilation when being used within chainblocks.

@guusw I never really planned to have a concept of "scene" btw, but rather chain graphs composing the whole final result.
Too many concepts I'm not sure of, we should go back to the drawing board. As everything seems to spawn complexity we don't want right now.
All I wanted was completing PBR shaders and add animations by what we specced out.

Closing this since it's the old bgfx implementation.


deleting TaxonName: DWC occurrence error

I am trying to delete a combination, which does not have any associated OTUs, and I have an error message:
https://github.com/SpeciesFileGroup/taxonworks/blob/78fa99b27/app/models/concerns/shared/dwc_occurrence_hooks.rb#L29

Request:

URL        : https://sfg.taxonworks.org/combinations/1182375.json
HTTP Method: PATCH
IP address : <IP_ADDRESS>
Parameters : {"combination"=>{"id"=>1182375, "verbatim_name"=>nil, "origin_citation_attributes"=>{"id"=>2565658, "source_id"=>31852, "pages"=>"36", "global_id"=>"gid://taxon-works/Citation/2565658"}, "verbatim_author"=>nil, "year_of_publication"=>nil, "roles_attributes"=>[], "subspecies_taxon_name_relationship_attributes"=>{"id"=>1738748, "_destroy"=>true}, "species_id"=>374965, "subspecies_id"=>nil, "genus_id"=>355903}, "extend"=>["protonyms", "origin_citation", "roles"], "controller"=>"combinations", "action"=>"update", "id"=>"1182375", "format"=>"json"}
Timestamp  : 2024-11-19 20:43:32 UTC
Server : taxonworks-69cfb979cf-qmmcj

Rails root : /app

Process: 295

seems to be fixed


MetaTensor: is_pinned and is_contiguous attributes

MetaTensors should be able to tell if a tensor is contiguous or pinned.

Problem is that the contiguous state of a tensor depends a lot on how it has been created.
For instance:
>>> x = torch.arange(1000).view(10, 10, 10)
>>> x.is_contiguous()
True
>>> x.transpose(0, -1).is_contiguous()
False

It is going to be quite challenging for MetaTensor to track this information in a reliable and testable way.
The benefit of this feature may not outweigh the complexity of the implementation and it's wiser to drop this for now.


[#3292] fix(spark-connector): passing Gravitino catalog properties to spark connector

What changes were proposed in this pull request?

passing Gravitino catalog properties with spark.bypass. prefix to spark connector
refactor the catalog properties transform logic.

Why are the changes needed?
Fix: #3292
Does this PR introduce any user-facing change?
yes, add document
How was this patch tested?

add UT
test in local envriment

ci failure not related, re trigger it.
> Could not resolve all files for configuration ':meta:compileProtoPath'.
   > Could not download protobuf-java-3.24.4.jar (com.google.protobuf:protobuf-java:3.24.4)
      > Could not get resource 'https://repo.maven.apache.org/maven2/com/google/protobuf/protobuf-java/3.24.4/protobuf-java-3.24.4.jar'.
         > Could not GET 'https://repo.maven.apache.org/maven2/com/google/protobuf/protobuf-java/3.24.4/protobuf-java-3.24.4.jar'.
            > Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>, repo.maven.apache.org/2a04:4e42:87:0:0:0:0:215] failed: Network is unreachable (connect failed)

@FANNG1 can you please identify the problems here?

@FANNG1 can you please identify the problems here?

download Jdbc driver failed, re trigger it.
TrinoConnectorIT > initializationError FAILED
    java.net.ConnectException: Connection timed out
        at java.base/sun.nio.ch.Net.connect0(Native Method)
        at java.base/sun.nio.ch.Net.connect(Net.java:579)
        at java.base/sun.nio.ch.Net.connect(Net.java:568)
        at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:593)
        at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
        at java.base/java.net.Socket.connect(Socket.java:633)
        at java.base/sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304)
        at java.base/sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:174)
        at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:183)
        at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:533)
        at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:638)
        at java.base/sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266)
        at java.base/sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:380)
        at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1242)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1128)
        at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1665)
        at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589)
        at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224)
        at com.datastrato.gravitino.integration.test.util.JdbcDriverDownloader.downloadJdbcDriver(JdbcDriverDownloader.java:33)
        at com.datastrato.gravitino.integration.test.trino.TrinoConnectorIT.startDockerContainer(TrinoConnectorIT.java:119)

@jerryshao is it ok to merge it ?