[url_launcher] No longer receiving PlatformException when opening a deep link (custom scheme)

What package does this bug report belong to?
url_launcher
What target platforms are you seeing this bug on?
iOS
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  _fe_analyzer_shared:
    dependency: transitive
    description:
      name: _fe_analyzer_shared
      sha256: ae92f5d747aee634b87f89d9946000c2de774be1d6ac3e58268224348cd0101a
      url: "https://pub.dev"
    source: hosted
    version: "61.0.0"
  adaptive_number:
    dependency: transitive
    description:
      name: adaptive_number
      sha256: "3a567544e9b5c9c803006f51140ad544aedc79604fd4f3f2c1380003f97c1d77"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  analyzer:
    dependency: transitive
    description:
      name: analyzer
      sha256: ea3d8652bda62982addfd92fdc2d0214e5f82e43325104990d4f4c4a2a313562
      url: "https://pub.dev"
    source: hosted
    version: "5.13.0"
  appcheck:
    dependency: "direct main"
    description:
      name: appcheck
      sha256: a9e5852e8c9d14342cfa3569fc464a1d49a49eac41e3d006f5825ce54663678f
      url: "https://pub.dev"
    source: hosted
    version: "1.0.6"
  args:
    dependency: transitive
    description:
      name: args
      sha256: eef6c46b622e0494a36c5a12d10d77fb4e855501a91c1b9ef9339326e58f0596
      url: "https://pub.dev"
    source: hosted
    version: "2.4.2"
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  base_x:
    dependency: transitive
    description:
      name: base_x
      sha256: "519abcdafd637d4b6bd7e72fabd8f9264935f804b9b9f6c5d8411c7d52cbf8fd"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.1"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  bs58:
    dependency: transitive
    description:
      name: bs58
      sha256: "3ed24dadf386ca749ff50af678be1131ef569a3583a6f37b87b90c032270c767"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.2"
  build:
    dependency: transitive
    description:
      name: build
      sha256: "80184af8b6cb3e5c1c4ec6d8544d27711700bc3e6d2efad04238c7b5290889f0"
      url: "https://pub.dev"
    source: hosted
    version: "2.4.1"
  build_config:
    dependency: transitive
    description:
      name: build_config
      sha256: bf80fcfb46a29945b423bd9aad884590fb1dc69b330a4d4700cac476af1708d1
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  build_daemon:
    dependency: transitive
    description:
      name: build_daemon
      sha256: "5f02d73eb2ba16483e693f80bee4f088563a820e47d1027d4cdfe62b5bb43e65"
      url: "https://pub.dev"
    source: hosted
    version: "4.0.0"
  build_resolvers:
    dependency: transitive
    description:
      name: build_resolvers
      sha256: a7417cc44d9edb3f2c8760000270c99dba8c72ff66d0146772b8326565780745
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  build_runner:
    dependency: "direct dev"
    description:
      name: build_runner
      sha256: "67d591d602906ef9201caf93452495ad1812bea2074f04e25dbd7c133785821b"
      url: "https://pub.dev"
    source: hosted
    version: "2.4.7"
  build_runner_core:
    dependency: transitive
    description:
      name: build_runner_core
      sha256: "6d6ee4276b1c5f34f21fdf39425202712d2be82019983d52f351c94aafbc2c41"
      url: "https://pub.dev"
    source: hosted
    version: "7.2.10"
  build_version:
    dependency: "direct dev"
    description:
      name: build_version
      sha256: "4e8eafbf722eac3bd60c8d38f108c04bd69b80100f8792b32be3407725c7fa6a"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  built_collection:
    dependency: transitive
    description:
      name: built_collection
      sha256: "376e3dd27b51ea877c28d525560790aee2e6fbb5f20e2f85d5081027d94e2100"
      url: "https://pub.dev"
    source: hosted
    version: "5.1.1"
  built_value:
    dependency: transitive
    description:
      name: built_value
      sha256: ff627b645b28fb8bdb69e645f910c2458fd6b65f6585c3a53e0626024897dedf
      url: "https://pub.dev"
    source: hosted
    version: "8.6.2"
  cached_network_image:
    dependency: "direct main"
    description:
      name: cached_network_image
      sha256: f98972704692ba679db144261172a8e20feb145636c617af0eb4022132a6797f
      url: "https://pub.dev"
    source: hosted
    version: "3.3.0"
  cached_network_image_platform_interface:
    dependency: transitive
    description:
      name: cached_network_image_platform_interface
      sha256: "56aa42a7a01e3c9db8456d9f3f999931f1e05535b5a424271e9a38cabf066613"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.0"
  cached_network_image_web:
    dependency: transitive
    description:
      name: cached_network_image_web
      sha256: "759b9a9f8f6ccbb66c185df805fac107f05730b1dab9c64626d1008cca532257"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  checked_yaml:
    dependency: transitive
    description:
      name: checked_yaml
      sha256: feb6bed21949061731a7a75fc5d2aa727cf160b91af9a3e464c5e3a32e28b5ff
      url: "https://pub.dev"
    source: hosted
    version: "2.0.3"
  clock:
    dependency: transitive
    description:
      name: clock
      sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  code_builder:
    dependency: transitive
    description:
      name: code_builder
      sha256: "315a598c7fbe77f22de1c9da7cfd6fd21816312f16ffa124453b4fc679e540f1"
      url: "https://pub.dev"
    source: hosted
    version: "4.6.0"
  coinbase_wallet_sdk:
    dependency: "direct main"
    description:
      name: coinbase_wallet_sdk
      sha256: "0e8d78359a2d8e6e7c57274342bb9d8b7257d4b42961a09399acc50d254aeae8"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.7"
  collection:
    dependency: "direct main"
    description:
      name: collection
      sha256: ee67cb0715911d28db6bf4af1026078bd6f0128b07a5f66fb2ed94ec6783c09a
      url: "https://pub.dev"
    source: hosted
    version: "1.18.0"
  convert:
    dependency: transitive
    description:
      name: convert
      sha256: "0f08b14755d163f6e2134cb58222dd25ea2a2ee8a195e53983d57c075324d592"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.1"
  crypto:
    dependency: transitive
    description:
      name: crypto
      sha256: ff625774173754681d66daaf4a448684fb04b78f902da9cb3d308c19cc5e8bab
      url: "https://pub.dev"
    source: hosted
    version: "3.0.3"
  cryptography:
    dependency: transitive
    description:
      name: cryptography
      sha256: df156c5109286340817d21fa7b62f9140f17915077127dd70f8bd7a2a0997a35
      url: "https://pub.dev"
    source: hosted
    version: "2.5.0"
  cupertino_icons:
    dependency: "direct main"
    description:
      name: cupertino_icons
      sha256: d57953e10f9f8327ce64a508a355f0b1ec902193f66288e8cb5070e7c47eeb2d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.6"
  custom_sliding_segmented_control:
    dependency: "direct main"
    description:
      name: custom_sliding_segmented_control
      sha256: "05b73fa48d57218bfdf806bad68a859812b216cd81fe81c6cbefde89f39eb257"
      url: "https://pub.dev"
    source: hosted
    version: "1.8.1"
  dart_style:
    dependency: transitive
    description:
      name: dart_style
      sha256: "1efa911ca7086affd35f463ca2fc1799584fb6aa89883cf0af8e3664d6a02d55"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  ed25519_edwards:
    dependency: transitive
    description:
      name: ed25519_edwards
      sha256: "6ce0112d131327ec6d42beede1e5dfd526069b18ad45dcf654f15074ad9276cd"
      url: "https://pub.dev"
    source: hosted
    version: "0.3.1"
  eip1559:
    dependency: transitive
    description:
      name: eip1559
      sha256: c2b81ac85f3e0e71aaf558201dd9a4600f051ece7ebacd0c5d70065c9b458004
      url: "https://pub.dev"
    source: hosted
    version: "0.6.2"
  eip55:
    dependency: transitive
    description:
      name: eip55
      sha256: "213a9b86add87a5216328e8494b0ab836e401210c4d55eb5e521bd39e39169e1"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.2"
  event:
    dependency: transitive
    description:
      name: event
      sha256: eb4814de94cbf6a10da9c4f652bc654087d7066e33566b5036822e6c0b24befb
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  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: "1b92bec4fc2a72f59a8e15af5f52cd441e4a7860b49499d69dfa817af20e925d"
      url: "https://pub.dev"
    source: hosted
    version: "6.1.4"
  fixnum:
    dependency: transitive
    description:
      name: fixnum
      sha256: "25517a4deb0c03aa0f32fd12db525856438902d9c16536311e76cdc57b31d7d1"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  flutter:
    dependency: "direct main"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_cache_manager:
    dependency: transitive
    description:
      name: flutter_cache_manager
      sha256: "8207f27539deb83732fdda03e259349046a39a4c767269285f449ade355d54ba"
      url: "https://pub.dev"
    source: hosted
    version: "3.3.1"
  flutter_svg:
    dependency: "direct main"
    description:
      name: flutter_svg
      sha256: d39e7f95621fc84376bc0f7d504f05c3a41488c562f4a8ad410569127507402c
      url: "https://pub.dev"
    source: hosted
    version: "2.0.9"
  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"
  freezed:
    dependency: "direct dev"
    description:
      name: freezed
      sha256: "21bf2825311de65501d22e563e3d7605dff57fb5e6da982db785ae5372ff018a"
      url: "https://pub.dev"
    source: hosted
    version: "2.4.5"
  freezed_annotation:
    dependency: "direct main"
    description:
      name: freezed_annotation
      sha256: c3fd9336eb55a38cc1bbd79ab17573113a8deccd0ecbbf926cca3c62803b5c2d
      url: "https://pub.dev"
    source: hosted
    version: "2.4.1"
  frontend_server_client:
    dependency: transitive
    description:
      name: frontend_server_client
      sha256: "408e3ca148b31c20282ad6f37ebfa6f4bdc8fede5b74bc2f08d9d92b55db3612"
      url: "https://pub.dev"
    source: hosted
    version: "3.2.0"
  glob:
    dependency: transitive
    description:
      name: glob
      sha256: "0e7014b3b7d4dac1ca4d6114f82bf1782ee86745b9b42a92c9289c23d8a0ab63"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  graphs:
    dependency: transitive
    description:
      name: graphs
      sha256: aedc5a15e78fc65a6e23bcd927f24c64dd995062bcd1ca6eda65a3cff92a4d19
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  http:
    dependency: "direct main"
    description:
      name: http
      sha256: d4872660c46d929f6b8a9ef4e7a7eff7e49bbf0c4ec3f385ee32df5119175139
      url: "https://pub.dev"
    source: hosted
    version: "1.1.2"
  http_multi_server:
    dependency: transitive
    description:
      name: http_multi_server
      sha256: "97486f20f9c2f7be8f514851703d0119c3596d14ea63227af6f7a481ef2b2f8b"
      url: "https://pub.dev"
    source: hosted
    version: "3.2.1"
  http_parser:
    dependency: transitive
    description:
      name: http_parser
      sha256: "2aa08ce0341cc9b354a498388e30986515406668dbcc4f7c950c3e715496693b"
      url: "https://pub.dev"
    source: hosted
    version: "4.0.2"
  io:
    dependency: transitive
    description:
      name: io
      sha256: "2ec25704aba361659e10e3e5f5d672068d332fc8ac516421d483a11e5cbd061e"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
  js:
    dependency: transitive
    description:
      name: js
      sha256: f2c445dce49627136094980615a031419f7f3eb393237e4ecd97ac15dea343f3
      url: "https://pub.dev"
    source: hosted
    version: "0.6.7"
  json_annotation:
    dependency: "direct main"
    description:
      name: json_annotation
      sha256: b10a7b2ff83d83c777edba3c6a0f97045ddadd56c944e1a23a3fdf43a1bf4467
      url: "https://pub.dev"
    source: hosted
    version: "4.8.1"
  json_rpc_2:
    dependency: transitive
    description:
      name: json_rpc_2
      sha256: "5e469bffa23899edacb7b22787780068d650b106a21c76db3c49218ab7ca447e"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.2"
  json_serializable:
    dependency: "direct dev"
    description:
      name: json_serializable
      sha256: aa1f5a8912615733e0fdc7a02af03308933c93235bdc8d50d0b0c8a8ccb0b969
      url: "https://pub.dev"
    source: hosted
    version: "6.7.1"
  lints:
    dependency: "direct dev"
    description:
      name: lints
      sha256: cbf8d4b858bb0134ef3ef87841abdf8d63bfc255c266b7bf6b39daa1085c4290
      url: "https://pub.dev"
    source: hosted
    version: "3.0.0"
  logger:
    dependency: transitive
    description:
      name: logger
      sha256: "6bbb9d6f7056729537a4309bda2e74e18e5d9f14302489cc1e93f33b3fe32cac"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.2+1"
  logging:
    dependency: transitive
    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"
  mime:
    dependency: transitive
    description:
      name: mime
      sha256: e4ff8e8564c03f255408decd16e7899da1733852a9110a58fe6d1b817684a63e
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
  mockito:
    dependency: "direct dev"
    description:
      name: mockito
      sha256: "4b693867cee1853c9d1d7ecc1871f27f39b2ef2c13c0d8d8507dfe5bebd8aaf1"
      url: "https://pub.dev"
    source: hosted
    version: "5.4.3"
  network_image_mock:
    dependency: "direct dev"
    description:
      name: network_image_mock
      sha256: "855cdd01d42440e0cffee0d6c2370909fc31b3bcba308a59829f24f64be42db7"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  octo_image:
    dependency: transitive
    description:
      name: octo_image
      sha256: "45b40f99622f11901238e18d48f5f12ea36426d8eced9f4cbf58479c7aa2430d"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.0"
  package_config:
    dependency: transitive
    description:
      name: package_config
      sha256: "1c5b77ccc91e4823a5af61ee74e6b972db1ef98c2ff5a18d3161c982a55448bd"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.0"
  package_info_plus:
    dependency: transitive
    description:
      name: package_info_plus
      sha256: "88bc797f44a94814f2213db1c9bd5badebafdfb8290ca9f78d4b9ee2a3db4d79"
      url: "https://pub.dev"
    source: hosted
    version: "5.0.1"
  package_info_plus_platform_interface:
    dependency: transitive
    description:
      name: package_info_plus_platform_interface
      sha256: "9bc8ba46813a4cc42c66ab781470711781940780fd8beddd0c3da62506d3a6c6"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.1"
  path:
    dependency: transitive
    description:
      name: path
      sha256: "8829d8a55c13fc0e37127c29fedf290c102f4e40ae94ada574091fe0ff96c917"
      url: "https://pub.dev"
    source: hosted
    version: "1.8.3"
  path_parsing:
    dependency: transitive
    description:
      name: path_parsing
      sha256: e3e67b1629e6f7e8100b367d3db6ba6af4b1f0bb80f64db18ef1fbabd2fa9ccf
      url: "https://pub.dev"
    source: hosted
    version: "1.0.1"
  path_provider:
    dependency: transitive
    description:
      name: path_provider
      sha256: a1aa8aaa2542a6bc57e381f132af822420216c80d4781f7aa085ca3229208aaa
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  path_provider_android:
    dependency: transitive
    description:
      name: path_provider_android
      sha256: "6b8b19bd80da4f11ce91b2d1fb931f3006911477cec227cce23d3253d80df3f1"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.0"
  path_provider_foundation:
    dependency: transitive
    description:
      name: path_provider_foundation
      sha256: "19314d595120f82aca0ba62787d58dde2cc6b5df7d2f0daf72489e38d1b57f2d"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  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: "94b1e0dd80970c1ce43d5d4e050a9918fce4f4a775e6142424c30a29a363265c"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  path_provider_windows:
    dependency: transitive
    description:
      name: path_provider_windows
      sha256: "8bc9f22eee8690981c22aa7fc602f5c85b497a6fb2ceb35ee5a5e5ed85ad8170"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  petitparser:
    dependency: transitive
    description:
      name: petitparser
      sha256: cb3798bef7fc021ac45b308f4b51208a152792445cce0448c9a4ba5879dd8750
      url: "https://pub.dev"
    source: hosted
    version: "5.4.0"
  platform:
    dependency: transitive
    description:
      name: platform
      sha256: ae68c7bfcd7383af3629daafb32fb4e8681c7154428da4febcff06200585f102
      url: "https://pub.dev"
    source: hosted
    version: "3.1.2"
  plugin_platform_interface:
    dependency: transitive
    description:
      name: plugin_platform_interface
      sha256: da3fdfeccc4d4ff2da8f8c556704c08f912542c5fb3cf2233ed75372384a034d
      url: "https://pub.dev"
    source: hosted
    version: "2.1.6"
  pointycastle:
    dependency: transitive
    description:
      name: pointycastle
      sha256: "7c1e5f0d23c9016c5bbd8b1473d0d3fb3fc851b876046039509e18e0c7485f2c"
      url: "https://pub.dev"
    source: hosted
    version: "3.7.3"
  pool:
    dependency: transitive
    description:
      name: pool
      sha256: "20fe868b6314b322ea036ba325e6fc0711a22948856475e2c2b6306e8ab39c2a"
      url: "https://pub.dev"
    source: hosted
    version: "1.5.1"
  pub_semver:
    dependency: transitive
    description:
      name: pub_semver
      sha256: "40d3ab1bbd474c4c2328c91e3a7df8c6dd629b79ece4c4bd04bee496a224fb0c"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  pubspec_parse:
    dependency: transitive
    description:
      name: pubspec_parse
      sha256: c63b2876e58e194e4b0828fcb080ad0e06d051cb607a6be51a9e084f47cb9367
      url: "https://pub.dev"
    source: hosted
    version: "1.2.3"
  qr:
    dependency: transitive
    description:
      name: qr
      sha256: "64957a3930367bf97cc211a5af99551d630f2f4625e38af10edd6b19131b64b3"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.1"
  qr_flutter_wc:
    dependency: "direct main"
    description:
      name: qr_flutter_wc
      sha256: a926bf6bcf7d350eea48480e205ccffffca5cc84b5d77fb2b256318693e40d07
      url: "https://pub.dev"
    source: hosted
    version: "0.0.3"
  rxdart:
    dependency: transitive
    description:
      name: rxdart
      sha256: "0c7c0cedd93788d996e33041ffecda924cc54389199cde4e6a34b440f50044cb"
      url: "https://pub.dev"
    source: hosted
    version: "0.27.7"
  sec:
    dependency: transitive
    description:
      name: sec
      sha256: "8bbd56df884502192a441b5f5d667265498f2f8728a282beccd9db79e215f379"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  shared_preferences:
    dependency: transitive
    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: "7bf53a9f2d007329ee6f3df7268fd498f8373602f943c975598bbb34649b62a7"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.4"
  shared_preferences_linux:
    dependency: transitive
    description:
      name: shared_preferences_linux
      sha256: c2eb5bf57a2fe9ad6988121609e47d3e07bb3bdca5b6f8444e4cf302428a128a
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  shared_preferences_platform_interface:
    dependency: transitive
    description:
      name: shared_preferences_platform_interface
      sha256: d4ec5fc9ebb2f2e056c617112aa75dcf92fc2e4faaf2ae999caa297473f75d8a
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  shared_preferences_web:
    dependency: transitive
    description:
      name: shared_preferences_web
      sha256: d762709c2bbe80626ecc819143013cc820fa49ca5e363620ee20a8b15a3e3daf
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  shared_preferences_windows:
    dependency: transitive
    description:
      name: shared_preferences_windows
      sha256: f763a101313bd3be87edffe0560037500967de9c394a714cd598d945517f694f
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  shelf:
    dependency: transitive
    description:
      name: shelf
      sha256: ad29c505aee705f41a4d8963641f91ac4cee3c8fad5947e033390a7bd8180fa4
      url: "https://pub.dev"
    source: hosted
    version: "1.4.1"
  shelf_web_socket:
    dependency: transitive
    description:
      name: shelf_web_socket
      sha256: "9ca081be41c60190ebcb4766b2486a7d50261db7bd0f5d9615f2d653637a84c1"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
  shimmer:
    dependency: "direct main"
    description:
      name: shimmer
      sha256: "5f88c883a22e9f9f299e5ba0e4f7e6054857224976a5d9f839d4ebdc94a14ac9"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.0"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_gen:
    dependency: transitive
    description:
      name: source_gen
      sha256: fc0da689e5302edb6177fdd964efcb7f58912f43c28c2047a808f5bfff643d16
      url: "https://pub.dev"
    source: hosted
    version: "1.4.0"
  source_helper:
    dependency: transitive
    description:
      name: source_helper
      sha256: "6adebc0006c37dd63fe05bca0a929b99f06402fc95aa35bf36d67f5c06de01fd"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.4"
  source_span:
    dependency: transitive
    description:
      name: source_span
      sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  sprintf:
    dependency: transitive
    description:
      name: sprintf
      sha256: "1fc9ffe69d4df602376b52949af107d8f5703b77cda567c4d7d86a0693120f23"
      url: "https://pub.dev"
    source: hosted
    version: "7.0.0"
  sqflite:
    dependency: transitive
    description:
      name: sqflite
      sha256: "591f1602816e9c31377d5f008c2d9ef7b8aca8941c3f89cc5fd9d84da0c38a9a"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.0"
  sqflite_common:
    dependency: transitive
    description:
      name: sqflite_common
      sha256: "1b92f368f44b0dee2425bb861cfa17b6f6cf3961f762ff6f941d20b33355660a"
      url: "https://pub.dev"
    source: hosted
    version: "2.5.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"
  stream_transform:
    dependency: transitive
    description:
      name: stream_transform
      sha256: "14a00e794c7c11aa145a170587321aedce29769c08d7f58b1d141da75e3b1c6f"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.0"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  synchronized:
    dependency: transitive
    description:
      name: synchronized
      sha256: "5fcbd27688af6082f5abd611af56ee575342c30e87541d0245f7ff99faa02c60"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.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"
  timing:
    dependency: transitive
    description:
      name: timing
      sha256: "70a3b636575d4163c477e6de42f247a23b315ae20e86442bebe32d3cabf61c32"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.1"
  typed_data:
    dependency: transitive
    description:
      name: typed_data
      sha256: facc8d6582f16042dd49f2463ff1bd6e2c9ef9f3d5da3d9b087e244a7b564b3c
      url: "https://pub.dev"
    source: hosted
    version: "1.3.2"
  universal_io:
    dependency: transitive
    description:
      name: universal_io
      sha256: "1722b2dcc462b4b2f3ee7d188dad008b6eb4c40bbd03a3de451d82c78bba9aad"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.2"
  url_launcher:
    dependency: "direct main"
    description:
      name: url_launcher
      sha256: d25bb0ca00432a5e1ee40e69c36c85863addf7cc45e433769d61bed3fe81fd96
      url: "https://pub.dev"
    source: hosted
    version: "6.2.3"
  url_launcher_android:
    dependency: transitive
    description:
      name: url_launcher_android
      sha256: "31222ffb0063171b526d3e569079cf1f8b294075ba323443fdc690842bfd4def"
      url: "https://pub.dev"
    source: hosted
    version: "6.2.0"
  url_launcher_ios:
    dependency: transitive
    description:
      name: url_launcher_ios
      sha256: bba3373219b7abb6b5e0d071b0fe66dfbe005d07517a68e38d4fc3638f35c6d3
      url: "https://pub.dev"
    source: hosted
    version: "6.2.1"
  url_launcher_linux:
    dependency: transitive
    description:
      name: url_launcher_linux
      sha256: "9f2d390e096fdbe1e6e6256f97851e51afc2d9c423d3432f1d6a02a8a9a8b9fd"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.0"
  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: "980e8d9af422f477be6948bdfb68df8433be71f5743a188968b0c1b887807e50"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.0"
  url_launcher_web:
    dependency: transitive
    description:
      name: url_launcher_web
      sha256: "7286aec002c8feecc338cc33269e96b73955ab227456e9fb2a91f7fab8a358e9"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.2"
  url_launcher_windows:
    dependency: transitive
    description:
      name: url_launcher_windows
      sha256: "7754a1ad30ee896b265f8d14078b0513a4dba28d358eabb9d5f339886f4a1adc"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.0"
  uuid:
    dependency: transitive
    description:
      name: uuid
      sha256: df5a4d8f22ee4ccd77f8839ac7cb274ebc11ef9adcce8b92be14b797fe889921
      url: "https://pub.dev"
    source: hosted
    version: "4.2.1"
  vector_graphics:
    dependency: transitive
    description:
      name: vector_graphics
      sha256: "0f0c746dd2d6254a0057218ff980fc7f5670fd0fcf5e4db38a490d31eed4ad43"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.9+1"
  vector_graphics_codec:
    dependency: transitive
    description:
      name: vector_graphics_codec
      sha256: "0edf6d630d1bfd5589114138ed8fada3234deacc37966bec033d3047c29248b7"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.9+1"
  vector_graphics_compiler:
    dependency: transitive
    description:
      name: vector_graphics_compiler
      sha256: d24333727332d9bd20990f1483af4e09abdb9b1fc7c3db940b56ab5c42790c26
      url: "https://pub.dev"
    source: hosted
    version: "1.1.9+1"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  wallet:
    dependency: transitive
    description:
      name: wallet
      sha256: "569c91c2af13a9e1119c001f9c09218eccf3f383eb8d15ba13a5b558010c1bc0"
      url: "https://pub.dev"
    source: hosted
    version: "0.0.12+1"
  walletconnect_flutter_v2:
    dependency: "direct main"
    description:
      name: walletconnect_flutter_v2
      sha256: a3654aa71221f15be6b20663759fad3eb3a37dc486f72860d7eb69c1e39d682b
      url: "https://pub.dev"
    source: hosted
    version: "2.1.12"
  watcher:
    dependency: transitive
    description:
      name: watcher
      sha256: "3d2ad6751b3c16cf07c7fca317a1413b3f26530319181b37e3b9039b84fc01d8"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  web:
    dependency: transitive
    description:
      name: web
      sha256: afe077240a270dcfd2aafe77602b4113645af95d0ad31128cc02bce5ac5d5152
      url: "https://pub.dev"
    source: hosted
    version: "0.3.0"
  web3dart:
    dependency: transitive
    description:
      name: web3dart
      sha256: "31f93cf84b8c874d7ffb363959249d7e479115fe12cf46f30b037dcad6750b22"
      url: "https://pub.dev"
    source: hosted
    version: "2.7.2"
  web_socket_channel:
    dependency: transitive
    description:
      name: web_socket_channel
      sha256: cc1f6c632a248278a091fd7d9a68f624906830f7c1c5aa66503fae0804633e1c
      url: "https://pub.dev"
    source: hosted
    version: "2.4.2"
  win32:
    dependency: transitive
    description:
      name: win32
      sha256: "9e82a402b7f3d518fb9c02d0e9ae45952df31b9bf34d77baf19da2de03fc2aaa"
      url: "https://pub.dev"
    source: hosted
    version: "5.0.7"
  x25519:
    dependency: transitive
    description:
      name: x25519
      sha256: cec3c125f0d934dccba6c4cab48f3fbf866dc78895dcc5a1584d35b0a845005b
      url: "https://pub.dev"
    source: hosted
    version: "0.1.1"
  xdg_directories:
    dependency: transitive
    description:
      name: xdg_directories
      sha256: "589ada45ba9e39405c198fe34eb0f607cddb2108527e658136120892beac46d2"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.3"
  xml:
    dependency: transitive
    description:
      name: xml
      sha256: "5bc72e1e45e941d825fd7468b9b4cc3b9327942649aeb6fc5cdbf135f0a86e84"
      url: "https://pub.dev"
    source: hosted
    version: "6.3.0"
  yaml:
    dependency: transitive
    description:
      name: yaml
      sha256: "75769501ea3489fca56601ff33454fe45507ea3bfb014161abc3b43ae25989d5"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.2"
sdks:
  dart: ">=3.2.0 <4.0.0"
  flutter: ">=3.16.0"

Steps to reproduce
Just try to open a deep link such as the following:
metamask://wc?uri=whatever

(MetaMask app must not be installed in the device)
Expected results
A PlatformException as on Android:
PlatformException(ACTIVITY_NOT_FOUND, No Activity found to handle intent { metamask://wc?uri=whatever }, null, null)

Actual results
Nothing at all is happening on iOS. No error but app is not opening either.
Code sample
Code sample
try {
  await launchUrl(Uri.parse('metamask://wc?uri=whatever'));
} on PlatformException catch (e) {
  // No exception is received here
} catch (e) {
 // No exception is received here either
 }

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.0, on macOS 14.2.1 23C71 darwin-arm64, locale en-US)
    • Flutter version 3.16.0 on channel stable at /Users/alfreedom/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db7ef5bf9f (8 weeks ago), 2023-11-15 11:25:44 -0800
    • Engine revision 74d16627b9
    • Dart version 3.2.0
    • DevTools version 2.28.2

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/alfreedom/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/alfreedom/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.6b829.9-10027231)
    • 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.13.0

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

[✓] Android Studio (version 2022.3)
    • 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.6b829.9-10027231)

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

[✓] Connected device (6 available)
    • RMX3201 (mobile)             • SKMZMVMJRSBIN7ZH                     • android-arm64  • Android 11 (API 30)
    • sdk gphone64 arm64 (mobile)  • emulator-5554                        • android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 15 Alfreedom (mobile) • *************************            • ios            • iOS 17.2.1 21C66
    • iPhone 13 mini (mobile)      • 65E4D373-0434-467C-BCD4-A598036D2875 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)              • macos                                • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)                 • chrome                               • web-javascript • Google Chrome 116.0.5845.179
    ! Error: Browsing on the local area network for iPhone Alfreedom. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

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

• No issues found!

iOS doesn't throw when there is not a handler available. Per the docs:
/// Returns true if the URL was launched successful, otherwise either returns
/// false or throws a [PlatformException] depending on the failure.

You are discarding the return value. Closing as the behavior is consistent with the documentation.
(https://github.com/flutter/flutter/issues/127665 tracks improving the difference in error handling.)


WIP: citations generation: React app

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/867

closed for https://github.com/inveniosoftware/invenio-app-rdm/pull/869


Iox #415 refactor service registry

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[x] Assign PR to reviewer

Notes for Reviewer

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior

[ ] Each unit test case has a unique UUID

[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

Reviewer notes
Only change the internal implementation of ServiceRegistry to use a vector, but NOT the interface (except for extension with one method removeAll).
References

Closes nothing

@elfenpiff Note that it builds on MacOS and Windows with small size (like 100 entries, did not test the limit), but fails with 5000. I suspect it is the stack size but did not look into it yet. Not sure what is set in these environments or whether there is another problem.
We need to increase the limits and ensure it builds on these as well.


Toolkit with motion repro stuttering in fs2020

Hello,
I really love this toolkit and I have a feedback that I don't know if it's a known issue.
When I enable motion repro from openxr developer tools, fs2020 starts stuttering even fps is high enough (I don't mean motion repro artifacts, it flickers like fps drops). I tried every variation (use latest preview of openxr runtime, lowered render scale both openxr and fs2020, lowered all of the graphic settings in sim etc.) but no luck. Even with the lowest graphic settings and highest fps (approx. 40-50). Then I tried uninstall this toolkit and motion repro started working fluidly again.
I am seeing this issue since installed toolkit. Is it possible to use toolkit with motion repro without stutter?
I tested everything with/without the latest versions:
Windows version is 11,
Updated openxr developer tools,
Updated toolkit,
Updated fs2020 ( I also tested it with the latest beta version of the sim),
Updated gpu driver,
Updated mobo drivers etc.
everything is new.
My system is:
HP Reverb G2
RTX2080
AMD 5600x
32 gb ram
Here is my log:
XR_APILAYER_NOVENDOR_toolkit.log

Ok I found it. My prediction dampening was -%50... When I move it to approx -20%, everything get smooth again.


Error [parser.cc:701] Error finding file [panda] | Error Code 1: Msg: Unable to read file:panda

Hi,
While launching ignition, simulator can't load the panda robot model.
ros2 launch panda_description view_ign.launch.py
Output:
[ign gazebo-1] Error [parser.cc:701] Error finding file [panda].
[ign gazebo-1] [Err] [UserCommands.cc:998] Error Code 1: Msg: Unable to read file:panda
...
[rviz2-5] [ERROR] [1643904244.369392818] [moveit_ros_visualization.motion_planning_frame]: Action server: /recognize_objects not available
...
[move_group-3] [ERROR] [1643904255.757169280] [moveit.simple_controller_manager.follow_joint_trajectory_controller_handle]: Action client not connected: joint_trajectory_controller/follow_joint_trajectory
[move_group-3] [ERROR] [1643904270.774255338] [moveit.simple_controller_manager.follow_joint_trajectory_controller_handle]: Action client not connected: gripper_trajectory_controller/follow_joint_trajectory

Is there anything else that I need to configure?

Hello @liushuya7,
As mentioned under panda_description/README.md, you might need to export IGN_GAZEBO_RESOURCE_PATH as such:
export IGN_GAZEBO_RESOURCE_PATH=${REPO_DIR}/panda_description${IGN_GAZEBO_RESOURCE_PATH:+:${IGN_GAZEBO_RESOURCE_PATH}}

You could do it inside your setup script if that's more convenient.
If that is not the issue, try manually executing .git_hooks/pre-commit_convert_xacros.bash to trigger URDF/SDF/SRDF generation.
Hope this helps.

Hi @AndrejOrsula, could you tell me how to replace the content in {REPO_DIR}? I tried to replaced it with the direct path to panda_description but result no good. Thank you!

Hello @0smile, ${REPO_DIR} should be the directory path to this repository, i.e. wherever you cloned panda_ign_moveit2 repository. In this way, ${IGN_GAZEBO_RESOURCE_PATH} will point to the panda_description package that contains the panda SDF model.

Hello @0smile, ${REPO_DIR} should be the directory path to this repository, i.e. wherever you cloned panda_ign_moveit2 repository. In this way, ${IGN_GAZEBO_RESOURCE_PATH} will point to the panda_description package that contains the panda SDF model.

It works! Thanks a lot!


Optional clearing of the restarted_this_frame flag

In the very niche case of reusing timers on repeat after a certain amount of frames, users may want to pause them on the same frame they repeat. The issue is that timer_check will pass when the timer is resumed, as the RESTARTED_THIS_FRAME key is not cleared.
Using sequences or destroying the timer will avoid this issue. However, we could potentially safely clear this flag in some places (timer_unpause seems like the best place to do it), but need to think about other ramifications. Right now the behavior is supposed to be "paused timers act identically to the frame on which they were paused" , but this already may be violated in the case of timer_check. I think this would be pretty safe as long as we make sure we don't allow the flag to be cleared if (for whatever reason) it were paused and unpaused on the same frame.

note for self: since TIME_CURRENT is not updated on paused timers, timer_check actually does not violate this rule

[438d76e3d7baf25f51ea0841404962029fdde945]
added optional argument, keeping this as experimental for now


GitHub link missing from PyPI

Heads-up: there's no link to this repo on the project's PyPI page

If it weren't for codecov, I wouldn't have been able to find it.
I believe this link can be added with the repository attr of [tool.poetry]

Thanks for pointing that out!  We have a bunch of additions coming from a new contributor so when I release the new version with those changes I'll make sure to add the docs as well!


PR: Implement Kite onboarding

Description of Changes
Kite onboarding means that a Python-file is opened at startup to show what Kite is able to provide.
The file is only shown once (controlled by a setting).
This PR updates the completion extension to open up the file after the main window was displayed and when the kite client is ready.
To do / open questions:

[x] I couldn't find a way to run code after all startup actions were run. Currently the last opened files are restored after main.restore_scrollbar_position was emitted. This restore takes the focus away from the current file. Therefore I'm using a delay via QTimer.singleShot here, but this is more of a hack. Is there a hook to run code at the end of the startup?

[x] Is accessing self.main and opening a new editor in a completion plugin okay or should this be avoided? An editor plugin could do the same, but I didn't know how to handle the dependency to the Kite client in the completion plugin in this case.

[x] Kite's spec states that a notification should be displayed if the retrieval of the onboarding file from Kite failed. Is there existing functionality in the Spyder SDK to display a notification with links/actions?

[ ] Disable this if the Enable Kite setting is off. The setting is not yet on master, afaik.

[x] Wrote at least one-line docstrings (for any new functions)

[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: jansorg

Hello @jansorg! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/completion/kite/__init__.py:

Line 25:80: E501 line too long (83 > 79 characters)

In the file spyder/plugins/completion/kite/plugin.py:

Line 48:80: E501 line too long (85 > 79 characters)
Line 61:80: E501 line too long (89 > 79 characters)
Line 95:80: E501 line too long (82 > 79 characters)
Line 96:80: E501 line too long (101 > 79 characters)
Line 110:80: E501 line too long (86 > 79 characters)

Hi @jansorg , some feedback to your questions:

I couldn't find a way to run code after all startup actions were run. Currently the last opened files are restored after main.restore_scrollbar_position was emitted.

Maybe we can add a signal for this propose. I think we can add it at the end of the method post_visible_setup (the same method that emits the restore_scrollbar_position) of the MainWindow (mainwindow.py).

Is accessing self.main and opening a new editor in a completion plugin okay or should this be avoided?

You can call the MainWindow (mainwindow.py) from the Kite plugin, although I think there is a method on the MainWindow called open_file which you can use instead of calling directly the editor through the MainWindow

Kite's spec states that a notification should be displayed if the retrieval of the onboarding file from Kite failed. Is there existing functionality in the Spyder SDK to display a notification with links/actions?

In case of error you could display a QMessageBox dialog. You can find some examples of this dialog at the mainwindow.py and some more info about this widget from the docs of Qt here.

@dalthviz Thanks for the feedback! I've responded and fixed the obvious issues.

I fixed a bug which I accidentally added with my last fix to this PR.
This is ready for Spyder. It's probably best to wait until kite's public release is ready too. It needs to bundle the Spyder onboarding file data, this will most likely happen with today's releas.

The latest public release of Kite now includes the onboarding file data which is needed for this PR.

Disable this if the Enable Kite setting is off. The setting is not yet on master, afaik.

That will be added in PR #10301, so let's wait until that one is merged so that you can do this afterwards.

@ccordoba12 @dalthviz
Please take a look at the updated logic here. I now attempt to request & show the Kite onboarding file in two cases:

When Spyder starts, after the editor is fully initialized.
When we receive a valid response from the Kite daemon (connected to the sig_response_ready, etc signals).

this is necessary if the user installs & starts Kite in the middle of a Spyder session: either via the in-Spyder install flow, or manually by downloading it from Kite.com
also, this cleanly handles the race condition where Spyder finishes initializing before the Kite daemon is available.

After the onboarding file is shown once, we never show it again. Let me know what you think.

@naman @jansorg @ccordoba12 seems like Spyder could freeze if Kite isn't installed or is unreachable with this PR. I will push some changes to tackle such behavior (basically by using signals instead of directly calling the client for the onboarding file). After that this should be ready :+1:

@dalthviz thanks!
I think it wouldn't freeze if Kite isn't installed/running (since the ConnectionError happens fast), but there may be other edge cases in which it might (if the Kite daemon had a bug and didn't return the onboarding file quickly), so it makes sense to be extra safe.
Thanks for handling the fix -- let me know if you need anything from my end.

I will push some changes to tackle such behavior

Thanks a lot @dalthviz for helping @metalogical to finish this one!

Failing tests are unrelated to the changes on this PR


Fixing failure building RN codegen CLI on Windows

Ensuring the file paths uses forward slashes as separator to avoid the characters from being interpreted as ASCII escape characters.
Summary

Changelog
Fixing build failure building RN codegen CLI on Windows. Ensuring the file paths uses forward slashes as separator to avoid the characters from being interpreted as ASCII escape characters.
[Android] [Fixed] - Fixing failure building RN codegen CLI on Windows
Test Plan
Ensured RN main branch builds on Windows with new architecture turned on.

Done .. The other errors seems unrelated to this change.


import/no-cycle should not trigger for Flow imports

This is a regression of #1098 (fix in PR #1126) that was re-introduced in v2.17.0.
v2.16.0 works as expected. v2.17.2 still has this regression.

Not sure if it is on the radar of this project, but it is also worth mentioning there is a similar issue with Typescript.

@jonathanrdelgado it is, if an issue is filed - please file one if there isn’t one already.

Has anybody had time to look into this? 2.17.3 still has this regression 🙏

Hey folks. I looked into this and it turns out the reason for the regression is that the original fix was subsequently removed by this pr
if you look at the current state of the file, it hasn't changed since this break
https://github.com/benmosher/eslint-plugin-import/blob/master/src/rules/no-cycle.js#L34

Thanks, seems like a simple PR to restore it, but with a test case to prevent it from being removed again.

I don't really have context for why this was removed so I may not be the best person for this. I tried to write a test case to reproduce the error we get on our codebase but to my surprise, no error occurs. It could be that I'm not using the tests properly but it could also be that this error only is reproducible with a certain kind of setup.

https://github.com/benmosher/eslint-plugin-import/pull/1494 was opened to fix this on 5th Oct, but as yet has not been approved.
cc: @ljharb

Yes, thanks, I'm aware. It's been on my list.

Great, thanks 😀

Thank you for this :D :D


Allow easy retrieval of the vote

this will be convenient if we want other SCs to check the outcome, for example if the vote is a merkle root of a tree containing detailed info about the execution of that commitment

not relevant with v4 protocol


Many pods take a long time to be in running state and crash a lot in larger clusters

Spegel version
v0.0.22
Kubernetes distribution
k3s
Kubernetes version
v1.28.8+k3s1
CNI
Cilium
Describe the bug
Hi! First of all thanks a lot for this useful project. It's helping work around problems with pulling images from some nodes in Hetzner Cloud when their IPs have previously been banned by registries for some reason.
I am testing Spegel with a couple of clusters between 200 and 400 nodes, and while many pods are running, many others crash continuously and in the logs I see attempting to acquire leader lease followed by gracefully shutdown. What am I missing?
Another question I had is related to firewall. At the moment I am not opening any ports in the firewall for Spegel and it seems to work anyway, at least I see all nodes pulling images that are often problematic for the problem explained above. Is this OK or am I supposed to open ports? If I need to open ports, are there any security implications or is the communication between nodes encrypted on that port?
Thanks a lot in advance!

Update: it seems that only 100 pods are running at the same time. Is this a known limitation?

Hm, if there is no message between attempting to acquire leader lease and shutdown gracefully that implies that the central context was cancelled, probably by some other part of spegel. There are no other interesting messages in the log? If not, my guess would be that the pod is receiving a SIGTERM from Kubernetes.
Just to be sure: are you consistently seeing exactly 100 pods starting successfully? I did some superficial searching but I cannot find a good candidate for a limit in that range, so I'm wondering if this is the result of configuration in your environment? Some operator injecting a ResourceQuota in the namespace perhaps, or configuration for watchers in etcd? If so, there might be some interesting events on the failing pods.
Apart from the registry being a type: NodePort service, there is nothing special about spegel inter-pod communication, so it should not normally require firewall configuration. If spegel doesn't know of an image, it will return 404, expecting Kubernetes to find the image by some other means.

Hi @bittrance ! There is no other useful information in the logs unfortunately and yes, always max 100. I have tested with several different clusters and always see the same limit. I have also tested with brand new clusters with nothing that (to my knowledge) could cause such a limit, also because Spegel is the only thing that seems to be limited always the same way. I have also tested with Postgres instead of etcd (with k3s) with the same result. What could I try to troubleshoot and find what's causing this limit? It's really weird because it's a daemonset. Thanks!

@vitobotta I do not think that you need to make any firewall configuration changes on your nodes. All traffic goes through the k8s CNI so as long as that is working Spegel should work.
Your issues with 200+ node clusters is an interesting one. So far I have only run benchmarks with 100 nodes. The problem can come from multiple different sources. My best guess is that there is limit reached in regards to leader election or daemonset IPs.

Yesterday I was working with a 500 node cluster and had again the same problem. Interestingly, I tried k3s' embedded Spegel version, and it works fine. I mean it doesn't use a daemonset since Spegel is embedded, but from a cursory look it seemed that all nodes had connections with each other on port 5001 as expected from k3s' docs.

Makes sense with your observations. You are correct that exposing port 5001 between nodes is required as the p2p component runs on that.
I had a thought which may explain the issues you are seeing. I was reading about others having issues with leader election in large clusters, and one common issue was the time it took. My best guess is that the startup probe times out because leader election is taking too long. This is why you are seeing instances shut down without any error, as the signal sent cancels the context which stops the process.
The first step here is to add a log to make it a bit more clear why thins are being shutdown. Second of all is to explore how to fix this long term for large clusters. Either my just increasing the startup time or some other optimization.
If I remember correctly k3s does not use leader election for bootstrapping. Either way I think you are better off running the embedded Spegel in k3s even after we figure out how to solve this.

I think I see what you are saying. I can use the embedded spegel for clusters created with my project in Hetzner Cloud since it uses k3s, but I would also like to try Spegel at work with GKE clusters because it's pretty handy :)

I have observed something interesting today. When upgrading Spegel where a lease has existed before, all pods will wait for 60 seconds until they agree on a new leader. This is also the max duration for the startup probe. I will explore this further to see if I have missed some timeout.

@vitobotta have you observed similar issues with the latest release of Spegel?


UI placing/margin at MinWidth

Which version of the app?
WinUI 3 Gallery
Description
When making the window as small as possible, there is too much margin next to the title and controls.
Screenshots

Windows version
No response
Additional context
No response

@niels9001 is this maybe because the VisualState in PageHeader does not mix with the VisualState in ItemPage or AllControlsPage? Maybe it's better to use one padding at the right place.

Hmm.. I thought we fixed this with the overhaul. Apparently not..
@jay-o-way Yeah that might make sense

Or, it's because
https://github.com/microsoft/WinUI-Gallery/blob/c3cf8db5607c71f5df51fd4eb45d0ce6e932d338/WinUIGallery/ItemPage.xaml#L55
does work, but
https://github.com/microsoft/WinUI-Gallery/blob/c3cf8db5607c71f5df51fd4eb45d0ce6e932d338/WinUIGallery/Controls/PageHeader.xaml#L21


Tips for namespace name

When i try to give namespace name something like "pages:home" i catch error. I guess problem in this fragment. Perhaps it would be correct, when action would be the last part of actionName?

yeah, try and make namespaces single words, as when calling send they'll be prefixed already. e.g.

namespace: 'user`
action: logout
send('user:logout')

does that make sense? Cheers!

Maybe you are right. Lets make all more simply! :)


No module named main

After successfully installing soccer-cli, this is the traceback error I'm getting when trying to use it
Traceback (most recent call last):
  File "C:\x\x\Anaconda\lib\runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\x\x\Anaconda\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\x\x\Anaconda\Scripts\soccer.exe\__main__.py", line 5, in <module>
ImportError: No module named main

Thanks !

Seems like you are using windows. I didn't test it out on that. Let me test it out on windows I will let you know.

I append this issue ticket here with another one I get on win10 powershell.
PS C:\Users\Hermann> soccer --standings --league=BL
POS     CLUB                              PLAYED        GOAL DIFF     POINTS
Traceback (most recent call last):
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\Scripts\soccer-script.py", line 9, in <module>
    load_entry_point('soccer-cli==<IP_ADDRESS>', 'console_scripts', 'soccer')()
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\lib\site-packages\click\core.py", line 700, in __call__
    return self.main(*args, **kwargs)
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\lib\site-packages\click\core.py", line 680, in main
    rv = self.invoke(ctx)
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\lib\site-packages\click\core.py", line 873, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\lib\site-packages\click\core.py", line 508, in invoke
    return callback(*args, **kwargs)
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\Scripts\main.py", line 179, in main
    get_standings(league)
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\Scripts\main.py", line 92, in get_standings
    print_standings(req.json())
  File "C:\Users\Hermann\AppData\Local\Programs\Python\Python35\Scripts\main.py", line 108, in print_standings
    goaldiff=str(team["goalDifference"]), points=str(team["points"])
TypeError: non-empty format string passed to object.__format__

Every other command is working perfect, only --standings lead to this error message.

Hi @Heart1010 ! Unfortunately, I don't have a windows machine and I am not able to reproduce this error on my linux. It would be nice if someone in the community could help me with this.

Latest git, cmd on Windows 10, Python 2.7.10 (Anaconda):
[py2] C:\Users\thurask\git\soccer-cli>soccer --standings --league=BL
POS     CLUB                              PLAYED        GOAL DIFF     POINTS
1       Borussia Dortmund                 3             10            9
2       FC Bayern M├╝nchen                3             9             9
3       VfL Wolfsburg                     3             4             7
4       1. FC K├╢ln                       3             3             7
5       1. FSV Mainz 05                   3             3             6
6       Bayer Leverkusen                  3             -1            6
7       FC Ingolstadt 04                  3             -2            6
8       Eintracht Frankfurt               3             2             4
9       FC Schalke 04                     3             0             4
10      Hertha BSC                        3             -1            4
11      Werder Bremen                     3             -2            4
12      SV Darmstadt 98                   3             0             3
13      Hamburger SV                      3             -5            3
14      TSG 1899 Hoffenheim               3             -2            1
15      FC Augsburg                       3             -2            1
16      Hannover 96                       3             -4            1
17      VfB Stuttgart                     3             -6            0
18      Bor. M├╢nchengladbach             3             -6            0

Thanks @thurask for clearing it out. @Heart1010 the package isn't python3.x compatible, you'll need to use it with python2.x. Let me know if that resolves the issue.

http://stackoverflow.com/questions/29613676/python-typeerror-non-empty-format-string-passed-to-object-format
2015-09-02 21:49 GMT+02:00 Archit Verma<EMAIL_ADDRESS>
Thanks @thurask https://github.com/thurask for clearing it out.
@Heart1010 https://github.com/Heart1010 the package isn't python3.x
compatible, you'll need to use it with python2.x. Let me know if that
resolves the issue.
—
Reply to this email directly or view it on GitHub
https://github.com/architv/soccer-cli/issues/1#issuecomment-137224991.

@Heart1010 if you change team=u''.join(team["teamName"]).encode('utf-8') to just team["teamName"], in the print_standings function in main.py, it should work fine in python3.

I'm having the same issue but in Python 2.7

@nare469 Thanks!

Hi, Thanks for this, i hope we get it working soon, i have similar issue, im using Archlinux and on launch i get ..
cirrus  blade  soccer-cli  soccer --standings --league=EPL
Traceback (most recent call last):
File "/usr/bin/soccer", line 9, in
load_entry_point('soccer-cli==<IP_ADDRESS>', 'console_scripts', 'soccer')()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 568, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2720, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2380, in load
return self.resolve()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2386, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "build/bdist.linux-x86_64/egg/soccer/main.py", line 21, in
ImportError: No module named config
cirrus  blade  soccer-cli 
regards
(sorry my programming skills are limited to 5 line shell scripts)

heh i fixed my error by simply sourcing my ~/.zshrc  where i point to the API key, after sourcing it works great, i LOVE it, thanks brogrammer.

@cirrusUK   where is the command "w3m"?


Croatian localization in hr.json.

Added Croatian translations for user interface in hr.json.

Well done, thank you! I will merge this either later tonight or tomorrow :)

Changes Unknown when pulling d05f1c17cbaf966089ffedd088f601e4f2933d59 on nevenjovanovic:hrvatski into ** on latin-language-toolkit:master**.

Merged through #629 - thanks again @nevenjovanovic!


/engine/extend/ or /engine/extend/manifest/ or both?

Go to https://docs.docker.com/engine/extend/
This doc exists, but it forwards to https://docs.docker.com/engine/extend/manifest/
/engine/extend/manifest/ Does not have an entry in the left nav, and seems like a weird place to end up when a doc exists at engine/extend, however there is a pre-existing redirect_from: that someone put there at some point trying to override it.

@thaJeztah do you know why this is this way? These files are managed in docker/docker.

It should not forward; I noticed that one in your meta update in the docker/docker repo. The redirect was a copy/paste error in the manifest.md file


Updating Custom Blocked Words

Please add instruction under:
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-naming-policy#custom-blocked-words
for updating the blocked words list. Customers question how updating the list works and the doc isn't clear on if updates are appended or overwritten.
[Enter feedback here]

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

ID: e3fb85a8-d842-f101-909e-86751922da43
Version Independent ID: 0c99b5ef-753e-1085-a682-c55ea4059207
Content: Enforce group naming policy in Azure Active Directory
Content Source: articles/active-directory/users-groups-roles/groups-naming-policy.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @curtand
Microsoft Alias: curtand

@sympleconfigmgr
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

Hi @sympleconfigmgr
Thanks for your contribution!! I updated the article appropriately. #please-close


boards: doc: Include only index documents to toctree

Use correct glob pattern to exclude common rst helpers from toctree.

@finikorg there seems to be a CI failure in the documentation build:
[1/2] Running Sphinx HTML build...
/runner/_work/zephyr/zephyr/doc/_build/src/boards/x86/common/efi_boot.rst: WARNING: document isn't included in any toctree
/runner/_work/zephyr/zephyr/doc/_build/src/boards/x86/common/net_boot.rst: WARNING: document isn't included in any toctree
FAILED: CMakeFiles/html

@finikorg there seems to be a CI failure in the documentation build:
[1/2] Running Sphinx HTML build...
/runner/_work/zephyr/zephyr/doc/_build/src/boards/x86/common/efi_boot.rst: WARNING: document isn't included in any toctree
/runner/_work/zephyr/zephyr/doc/_build/src/boards/x86/common/net_boot.rst: WARNING: document isn't included in any toctree
FAILED: CMakeFiles/html

Yes, noticed, added fix for that.


RC Spot Check - Gravity and Orbits 1.5.0-rc.2

Gravity and Orbits 1.5.0-rc.2 has had issues fixed since RC.1 and is ready for QA testing.  The links produced by the deploy task are:
https://phet-dev.colorado.edu/html/gravity-and-orbits/1.5.0-rc.2/phet/gravity-and-orbits_en_phet.html
https://phet-dev.colorado.edu/html/gravity-and-orbits/1.5.0-rc.2/phet-io/
The issues to be verified are listed in https://github.com/phetsims/gravity-and-orbits/milestone/4.  Feel free to copy them here if you wish.  There are currently 11 open issues.  Each issue describes how it can be verified.  Most verifications just require 1 platform.  Aside from verifying the milestone issues, please just test for 5 minutes or so to see if anything else has been disturbed.
UPDATE: As mentioned in https://github.com/phetsims/gravity-and-orbits/issues/393#issuecomment-879335836

Thanks!  For issues like these, I recommend closing when they have been confirmed fixed in RC.2.  Then when the milestone list https://github.com/phetsims/gravity-and-orbits/milestone/4 is empty, we are ready to publish.  Sound OK?

Issues:

[x] https://github.com/phetsims/gravity-and-orbits/issues/400
[x] https://github.com/phetsims/gravity-and-orbits/issues/402
[x] https://github.com/phetsims/gravity-and-orbits/issues/398
[x] https://github.com/phetsims/gravity-and-orbits/issues/394
[x] https://github.com/phetsims/gravity-and-orbits/issues/395
[x] https://github.com/phetsims/gravity-and-orbits/issues/391
[x] https://github.com/phetsims/gravity-and-orbits/issues/389
[x] https://github.com/phetsims/gravity-and-orbits/issues/393
[x] https://github.com/phetsims/gravity-and-orbits/issues/399
[x] https://github.com/phetsims/gravity-and-orbits/issues/403
[x] https://github.com/phetsims/gravity-and-orbits/issues/404

Looks like qa is done with spot check.

1.5 has been published, closing.


Windows Defender detects v1.15.1 as a trojan

[X] I have read the FAQ.
[X] I have searched in existing issues.

Environment

OS: Windows 10, 2004
scrcpy version: v1.15.1
installation method: Windows release

Describe the bug
Windows Defender claims this version of scrcpy contains Trojan:Win32/Emali.A!cl.

Same problem

Arf, this is the same problem as #1102 :disappointed:
Does it only block scrcpy-noconsole.exe, or also scrcpy.exe?
Is it only v1.15.1? Does it affects v1.15 or v1.14?

Wow, Windows defender is triggered by v1.15.1 but not by 1.15:

scrcpy-win64-v1.15.1.zip: https://www.virustotal.com/gui/file/78fba4caad6328016ea93219254b5df391f24224c519a2c8e3f070695b8b38ff/detection
scrcpy-win64-v1.15.zip: https://www.virustotal.com/gui/file/dd514bb591e63ef4cd52a53c30f1153a28f59722d64690eb07bd017849edcba2/detection

The only source code difference between the two versions is: 976761956f5ff8a806a8547e7a1af9e4e7e3d77c and 633a51e9c4c64ed549a9a44f8348ded528268451 :thinking:

Windows Defender is mad. There are same issues in many repositories. Just allow it or disable it.

Does it only block scrcpy-noconsole.exe, or also scrcpy.exe?

So far it only seems to complain about the -noconsole variant.

scrcpy.exe has been removed as well on my machine a few hours after scrcpy-noconsole.exe.

Hi, should be related -
Just got blocked by Chrome on trying to download, getting this message:
"scrcpy-win64-v1.15.1.zipFailed - Virus detected"
V1.15 did not triggered such a message.
Great tool and thanks for your effort!!

Just got blocked by Chrome on trying to download, getting this message:
"scrcpy-win64-v1.15.1.zipFailed - Virus detected"

Yes, I guess it's Windows defender too:
https://windowsreport.com/failed-virus-detected-chrome/

So, you don’t have to blame Google Chrome but your own antivirus software as it is the one showing the Failed, virus detected alert message.

I'm not sure there is a simple way to report false positives (and make them confirm that the file does not contain a trojan).

@rom1v did you try to submit the binaries to Microsoft?
https://docs.microsoft.com/en-us/windows/security/threat-protection/intelligence/submission-guide

oh, ok. Just thought it can help in someway.
Anyway, with allowing it on Windows Defender I could make the download and work.
Thanks.

Thank you for the link.

Can I submit a sample without signing in?
Yes, you many submit a file as an anonymous home customer. You will get a link to a webpage where you can view the status of the submission.

Contrary to what this page says, as soon as I click on submit, it requires to be logged with some account.
I just created an account and submitted "as a software developer" the file scrcpy-noconsole.exe.

Contrary to what this page says, as soon as I click on submit, it requires to be logged with some account.

Yeah, I experienced the same frustration... It might have been available when they first launched the portal.
Anyway, let's hope they can give us more info on why they flagged it, and maybe unflag it.

Is it ok to use v1.15.0 instead? Is it much of a difference ? I've noticed both were published very near each other...

Can confirm:

Is it ok to use v1.15.0 instead? Is it much of a difference ? I've noticed both were published very near each other...

Here is the diff: v1.15...v1.15.1
v1.15.1 was a hotfix for #1643

@SimonMarquis Doesn't seem so important, no?

It's probably Defender detecting some kind of evil in one of the SHA sums.
I don't know too much about antivirus though 🤔

@AndroidDeveloperLB no it doesn't seem that important and if v1.15 works for you, I guess you can keep it for now.
@metaa we'll see what the submission of the binary to Microsoft will tell us. 🤷

For some reason, v1.16 is not detected as a trojan: https://www.virustotal.com/gui/file/3f30dc5db1a2f95c2b40a0f5de91ec1642d9f53799250a8c529bc882bc0918f0/detection
:tada:
The problem is not "solved", but now that it seems ok with the latest release, I close this issue since it's a duplicate of #1102.

I just created an account and submitted "as a software developer" the file scrcpy-noconsole.exe.

Analyst comments:
The submitted files do not meet our criteria for detection. No detection will be added for these files.
More detailed information about the approach and criteria categories currently used by the Microsoft researchers are available here:
https://www.microsoft.com/en-us/wdsi/antimalware-support/malware-and-unwanted-software-evaluation-criteria
Thank you for contacting Microsoft.

I'm not sure to understand why it does not meet their criteria. And in that report, they say "no malware detected" :thinking:

I'm not sure to understand why it does not meet their criteria. And in that report, they say "no malware detected" 🤔

Microsoft being Microsoft.
I think as long as it doesn't occur with the newer versions, we can safely drop this case.

@rom1v I rescanned the file through VirusTotal and it says no malware detected from Microsoft anymore, but it is still detected as malware with SecureAge APEX and Rising, but that is not a huge issue. https://www.virustotal.com/gui/file/d07c28b00f59281fc0db77c8ad10fc8f7d6effbd4371331068f62ce2188e6f07/detection

What does it mean "meet our criteria for detection" ?
There is a criteria to detect viruses?

The submitted files do not meet our criteria for detection. No detection will be added for these files.
More detailed information about the approach and criteria categories currently used by the Microsoft researchers are available here:
https://www.microsoft.com/en-us/wdsi/antimalware-support/malware-and-unwanted-software-evaluation-criteria
Thank you for contacting Microsoft.

I'm not sure to understand why it does not meet their criteria. And in that report, they say "no malware detected" 🤔

I believe what they mean is those files don't meet their criteria for detection as malware.

But it's their AV app that reported it as such...
I don't understand.


modelOptions debounce and valueChanges listener

Hello, can anyone tell me if debounce default value taken into account when we use valueChanges listener?
In the example this.model.startEffectiveDate have old value inside valueChanges listener:
model: any;
{
  key: 'startEffectiveDate',
  type: 'custom-datepicker',
  props: {
    label: 'EffectiveDate',
    placeholder: '',
    required: true,
    showIcon: true,
	modelOptions: {
    debounce: {
      default: 0,
    },
  },

  hooks: {
    onInit: (field: FormlyFieldConfig) => {

      field.formControl.valueChanges.pipe().subscribe({
        next: newEffectiveDate => {
          if (newEffectiveDate) {

            // Now we update the model so our code is working
            // this.model.startEffectiveDate = newEffectiveDate;

            console.log(this.model.startEffectiveDate == newEffectiveDate);
          }
        },
    },
  }
},

no, valueChanges is managed from Angular forms which doesn't support debounce.
Instead use: field.options.fieldChanges


InfoEnchantment -> EnchantmentState

InfoEnchantment is not an enchantment called "Info".

this is more like an entry than a state. the entry is like an alt to Map.Entry Enchantment, Integer.

How about EnchantmentInfo? "info enchantment" probably means it is an enchantment in the tooltip info

It's not really an enchantment info (just an enchantment together with the level). EnchantmentEntry could work, but it's a bit vague.

It's not a state either. A state sounds like a Map<Enchantment, Integer> that is bound to an item stack to me.

Yeah, true. I think I'll open an issue for name suggestions.


This commit closes the issue #2033.

Added a fix for issue #2033 based on #1353 and https://github.com/SpiderLabs/ModSecurity/commit/9ac9ff8223c0a9d7723a312204659ff72c9cc685.
The fix is basically the same as is used for #1353, adding a sanity check after the arguments are parsed. I added the check for ctl:ruleRemoveTargetById as well as ctl:ruleRemoveTargetByMsg.
I'm currently unable to check this in the environment where it first occurred and I currently cannot reproduce the error as it was reported to me.
Note: This change also fixes inconsistent whites pace on the original fix.

Hi @studersi,
Thank you for your contribution. I've changed the commit name to reflect what you have placed on the CHANGELOG.

Perfect, thank you!


Added the DDLog.h which should fix the C99 compiler errors.

Set the podspec file to 'CocoaLumberjack', '~> 1.0'. It solves the problem.


CI: run benches with hyperfine rather than bash

The hyperfine installation is cached so this should not cost a lot of CI time.
This is step 1/2 to getting rid of the BASH variable hack.

:pushpin: Commit a62ef8fcc90da451605454355d89e9f2aa19594e has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit a62ef8fcc90da451605454355d89e9f2aa19594e with merge b21f5794f3c2c4fe7504fab3062c1ac68bd14a55...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 4bbd098f5032cb75f7799d6f3183e764f284fe7c has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 4bbd098f5032cb75f7799d6f3183e764f284fe7c with merge 2b676f2b0e9f187782285abb9585fe1ed727dbc3...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 2b676f2b0e9f187782285abb9585fe1ed727dbc3 to master...


first run

hello,
im kinda stuck on: the server is now up and running and should be up within 10 mins ark
server runnin: no
listening no
did i do anything wrong?

maybe something wrong with your settings?

Is this still a problem?


HIVE-25441: Incorrect deltas split for sub-compactions when using

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

recheck


adding metricminer

i added metricminer to the list. metricminer is a tool that i developed during my masters and PhD in order to extract data from Git repositories. It is a lean Java DSL. Documentation is in Github.

Thank you!


Order.getStatus() returns null

Immediately after calling client.placeOrder() a call to order.getStatus returns null.  This is unexpected.  Shouldn't it return a Status instance?  The call to placeOrder() places an order and seems to work as expected.

Yeah. That’s how it works in the integration tests. Can you try and sleep for a few seconds and then call the getStatus? Maybe TDA has a synchronization delay between their internal servers.
On Tue, Jul 7, 2020, at 07:30, FreeGoldRush wrote:

Immediately after calling client.placeOrder() a call to order.getStatus returns null. This is unexpected. Shouldn't it return a Status instance? The call to placeOrder() places an order and seems to work as expected.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/studerw/td-ameritrade-client/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQHJA42L2QXGD2LO4CDVE3R2MIOXANCNFSM4OSYR2BQ.

@FreeGoldRush Did the sleeping for a few seconds solve your problem?

Sorry, have not tried it yet.  Sleeping isn't an option.  I'll probably just create a Thread that checks order status every 250 ms or something until it gets a valid value.


Unable to compile v3.8 with VS2015 [fix included]

When compiling, build log reports issues with dxerr.lib and __vsnprintf function.
As an workaround, add this line:
int (WINAPIV * __vsnprintf)(char , size_t, const char, va_list) = _vsnprintf;
in gfxD3D9Shader.cpp after #include "gfx/D3D9/gfxD3D9Device.h"

Fix doesn't seem to be working for me.

My temp fix is in:
Torque3D\Engine\source\gfx\D3D9\gfxD3D9Device.h
comment out
// #include <DxErr.h>
\Torque3D\Engine\source\gfx\D3D9\gfxD3D9Shader.cpp
under if ( res != D3D_OK && smLogErrors )
comment out
//     Con::errorf( "GFXD3D9Shader::_compileShader - Error compiling shader: %s: %s (%x)",
//         DXGetErrorStringA(res), DXGetErrorDescriptionA(res), res );

Fix doesn't seem to be working for me
Well, I was compiling it using Release mode, didn't tested Debug mode though.

I don't get these errors in latest dev branch.

I get the same error on the lastest version of the engine. Microsoft says the dxerror.lib is deprecated and should be dropped (DXSDK -> Windows SDK). For a workaround I used the same fix as @Krakean namely:
int (WINAPIV * __vsnprintf)(char , size_t, const char, va_list) = _vsnprintf;
i added this line after an including <windows.h> somewhere in mainLoop.cpp.
and the error goes away.

As far as I know dxerr source code can be found on this blog post and is under MsPl license. I can tra to include chat if you with.

@mattiascibien Thx.
I already found this Blog post myself but hadn't the time to test it yet. IMO the DXERR lib should be completely dropped than just including a workaround. I haven't had the time to actually search the code where the lib is actively used but it should be easy to do so or to replace it with an alternative.

i Will tra to cheek as I wait to hear from the devs too.

Yea me too.
Am 30.12.2015 11:05 schrieb "Mattias Cibien"<EMAIL_ADDRESS>
i Will tra to cheek as I wait to hear from the devs too.
—
Reply to this email directly or view it on GitHub
https://github.com/GarageGames/Torque3D/issues/1449#issuecomment-167971775
.

Should be resolved by http://forums.torque3d.org/viewtopic.php?f=40&t=473 if ya'll want to help beat that up so we can get that in.

Resolved via PR #1566


update libwebp to 1.0.1

Closing this: we now rely on bazel to manage deps, and libwebp has been upgraded to the latest on master.


Add ability to revalidate external resource requests

An added 'revalidate' argument allows Cache-Control: max-age=0 to be added in cases where it's desirable for artifact repositories or caching proxies to revalidate requests:

Listing version metadata
Resource has exceeded it's cache lifetime on disk, such as dynamic/snapshot dependencies or when --refresh-dependencies is specified

Some more background here:
https://groups.google.com/forum/#!topic/gradle-dev/nTWs8SfTUA8

Hi @DanielThomas, thanks for the contribution.
Could you please sign the Gradle CLA so we can go forward with the change? The Contribution Guidelines are here for your reference.

Signed!

I had a look over the changes. If possible we should also add some integration tests for the following scenarios to see the effect of the new behavior from the end user's perspective.

Usage of --refresh-dependencies from the command line and without it
Default TTL behavior for dynamic and changing dependencies
Definition of custom TTL parameters for dynamic and changing dependencies

Would mind adding some tests for those scenarios?
Looking at the functionality holistically it might also make sense to look at the headers that are part of the response and their effect on the expiration of the local cache.

I added an verification for an existing --refresh-dependencies to ensure that the cached artifact is revalidated when fetched. The fact that DefaultCacheAwareExternalResourceAccessor is hit at all is a function of the cache policy, so integration tests for all cases would be verifying the same behavior.

I should add - one thing this approach doesn't allow for is a forced revalidation on --refresh-dependencies if there isn't already a cached resource. DefaultCacheAwareExternalResourceAccessor isn't aware of the prevailing cache policy, or the type of the artifact, so we can't make a better decision that doesn't involve issuing every request from the resource accessor with revalidate...

Hi Daniel,
Thanks for the added integration test and words.

The fact that DefaultCacheAwareExternalResourceAccessor is hit at all is a function of the cache policy, so integration tests for all cases would be verifying the same behavior.

I still think that covering all the use cases mentionned by @bmuschko is worth it as it will guarantee no future regressions and demonstrate the feature from a user point of view.

I should add - one thing this approach doesn't allow for is a forced revalidation on --refresh-dependencies if there isn't already a cached resource. DefaultCacheAwareExternalResourceAccessor isn't aware of the prevailing cache policy, or the type of the artifact, so we can't make a better decision that doesn't involve issuing every request from the resource accessor with revalidate...

From what I understand, the current approach triggers revalidation only if we already have a cached version locally, right ? If it is, then when using --refresh-dependencies without having those dependencies already resolved and cached revalidation is not done, still right?

I've added some additional expectations - is there anywhere else you'd suggest these belong?
That's right.

@bmuschko @eskatos @ghale anything else you need from me here, and if not, any indication on when this will land? If this will miss the boat for 2.14, we'll temporarily fork Gradle internally so we can get this improvement and roll out the feature, as long as we have some confidence that we'll have this capability in a regular release in future.

@bmuschko @eskatos @ghale please can you have another look on this pull request. would love to get this one finished.

@DanielThomas : Sorry for the long delay here.  We got a little crossed up with respect to who has handling this PR and it languished.  In any event, I've taken a look and for the most part it looks good.  I've left you a comment about one change that looks a little problematic to me.  I also noticed that it seems to be doing something bad to PluginResolutionServiceTestServer, causing some tests to fail under the plugin-use subproject (bunch of failed tests around error response scenarios).  We need to get that fixed before we can merge this.  If you need help figuring out what's going on there, give me a shout.

@DanielThomas Are you still feeling like following up with this and check if this is still needed? If yes, could you check the merge conflicts and check @ghale's comment above (https://github.com/gradle/gradle/pull/607#issuecomment-233388994).

@jjohannes we've got a contract with Gradle Inc. to finish this work.

I'm taking over this PR and rebasing onto master. I will also look at the failing tests.


second devenv up always crashes with overmind

Describe the bug
When I run devenv up, stop the process, and then run devenv up again it crashes with the following error message:

To reproduce
# Make a new ihp project
nix run nixpkgs#ihp-new test

cd test

# Open flake.nix and enable overmind by adding the following to line 40:
# process.implementation = "overmind";

# First start
devenv up

# After 30 secs stop the process using CTRL C

# Second start
devenv up

# Now the error happens:
# overmind: listen unix /tmp/devenv-d8acd82/overmind.sock: bind: no such file or directory

Version
devenv: 1.0.5 via flakes
devenv.url = "github:cachix/devenv?rev=800f19d1b999f89464fd8e0226abf4b3b444b0fa";

I run into this pretty regularly. Any ideas how this could be fixed @sandydoo @domenkozar ?


Input error on Chrome for Android

There is strange input behaviour when using xterm.js in Chrome for Android as seen here
Video courtesy of @ajdlinux in this issue and the bug brought to my attention here
It looks like previous input characters are duplicated whenever a "special" character (eg backspace, enter) is pressed. However I cannot replicate the initial bug in the video where characters replace one another.
Currently affects Sourcelair and MicroPython on Unicorn which uses xterm.js version 2.6.0. The problem does not manifest in Firefox for Android 53.0.2.

Browser: Chrome for Android 58.0.3029.83
OS: Android 7.1.2

Likely related to not using the input event (see https://github.com/sourcelair/xterm.js/issues/469, https://github.com/sourcelair/xterm.js/issues/265).
Note that we don't explicitly support mobile yet.

I've observed the same behavior in Android 5.1.1 browsers:

Google Chrome 65.0.3325.109
Firefox 59.0.2

Each time I press backspace whatever happens to be in the buffer is printed minus the last char. That output is then appended to the buffer and is repeated if I press it again.

We don't support mobile OS' currently. Track https://github.com/xtermjs/xterm.js/issues/1101 for progress on this.


No aiGetPredefinedLogStream function in assimp

I'm trying to follow https://github.com/assimp/assimp/blob/master/samples/SimpleOpenGL/Sample_SimpleOpenGL.c
but I can't find function aiGetPredefinedLogStream at line 341. What am I missing?

Hey @Immueggpain,
aiGetPredefinedLogStream is the only function in Assimp that returns a struct by value. That's not a problem for LWJGL, but it would require an additional native binary to support. I didn't want to introduce an entire shared library (per platform) just for one function, which does not provide critical functionality anyway and can easily be emulated (with a custom AILogStreamCallback).
I have this in my todo list though and eventually will be supported.

@Spasi Oh I see. That totally makes sense. I will use AILogStreamCallback instead. Also thank you for your reply!
P.S. It seems to me that beta has less bugs and is more stable than the current 3.1.1 release, is it just my illusion? LOL

Is there plans to implement this now that the Assimp binding has a shared library?

Sounds good, thank you for explaining.

Requesting another look at this since it seems you suggested libffi 3.3 would fix this, and it appears to be out since Nov. 16 2019.

LWJGL has replaced dyncall with libffi which, among other nice things, made it possible to implement aiGetPredefinedLogStream. Sorry that it took so long!


Support repeated fields

Some command-line programs want to have an argument specified multiple times: maybe the thing to do is to understand a T::Array type as necessarily implying repetition, but that might be too cute.

Fixed by #16.


pinning and unpinning change of state.

initial state of importmap.rb which is stock rails 7 installation + trix
pin "application", preload: true
pin "@hotwired/turbo-rails", to: "turbo.min.js", preload: true
pin "@hotwired/stimulus", to: "stimulus.min.js", preload: true
pin "@hotwired/stimulus-loading", to: "stimulus-loading.js", preload: true
pin_all_from "app/javascript/controllers", under: "controllers"
pin "trix"
pin "@rails/actiontext", to: "actiontext.js"

pin the library:  bin/importmap pin stimulus-library and the process installs two external references (stimulus and actiontext) without preload: true on stimulus
pin "application", preload: true
pin "@hotwired/turbo-rails", to: "turbo.min.js", preload: true
pin "@hotwired/stimulus", to: "https://ga.jspm.io/npm<EMAIL_ADDRESS>pin "@hotwired/stimulus-loading", to: "stimulus-loading.js", preload: true
pin_all_from "app/javascript/controllers", under: "controllers"
pin "trix"
pin "@rails/actiontext", to: "actiontext.js"pin "stimulus-library", to<EMAIL_ADDRESS>pin "date-fns/formatDistanceToNow", to<EMAIL_ADDRESS>pin "date-fns/formatDuration", to<EMAIL_ADDRESS>pin "date-fns/intervalToDuration", to<EMAIL_ADDRESS>pin "date-fns/isPast", to<EMAIL_ADDRESS>pin "date-fns/toDate", to<EMAIL_ADDRESS>pin "dialog-polyfill", to<EMAIL_ADDRESS>pin "lodash-es/camelCase", to<EMAIL_ADDRESS>pin "lodash-es/clamp", to<EMAIL_ADDRESS>pin "lodash-es/debounce", to<EMAIL_ADDRESS>pin "lodash-es/get", to<EMAIL_ADDRESS>pin "lodash-es/set", to<EMAIL_ADDRESS>pin "lodash-es/upperFirst", to<EMAIL_ADDRESS>pin "mitt", to<EMAIL_ADDRESS>pin "smoothscroll-polyfill", to<EMAIL_ADDRESS>
unpin  ... bin/importmap unpin stimulus-library and the situation is a far cry from the initial situation
pin "application", preload: true
pin "@hotwired/turbo-rails", to: "turbo.min.js", preload: true
pin "@hotwired/stimulus-loading", to: "stimulus-loading.js", preload: true
pin_all_from "app/javascript/controllers", under: "controllers"
pin "trix"
pin "@rails/actiontext", to: "actiontext.js"pin "stimulus-library", to<EMAIL_ADDRESS>
The information about stimulus call being a wrapper for @hotwired/stimulus needs to be searched out with great effort; so it is not obvious how to handle this when osmethign goes wrong.  Combine that with the lack of preload and the number of variables at play are increasing past a comfort zone.
I am posting this because I have had issues in past & could not trace, nor rollback efficiently and effectively. without spinning up a new application (bare minimum a trace is here)

What exactly do you want me to do about this? @dvodvo
I have no control over what the `bin/importmap' script does.
That script is maintained by Rails, not me.
Likewise, the difference between stimulus and @hotwired/stimulus, not my problem either. Those packages are maintained by Rails, and any documentation of their behaviour should be in the Stimulus documentation.

I have opened an issue on this matter with importmap-rails.  I thought it worthwhile at least to advise


how to get VM image scheduled deprecation date

Hello
When running project on several months, it s key to know if the same VM image will be available from start to end of the project to ensure application OS consistency.
Instead of detecting if an OS image is already deprecated, it would be more interesting to be able to get the deprecated scheduled date if there is one. With such information, you are able to choose the proper image at the beginning of the project and be sure that all VM of the project will run the exact same release.
Thank you
Frederic GALLOS

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

ID: 1ae5bf9f-47d8-ad01-af78-ddd78604301f
Version Independent ID: 7979d401-a6f0-6cfd-1497-300a6a1d988e
Content: Deprecated Azure Marketplace images - Azure Virtual Machines
Content Source: articles/virtual-machines/deprecated-images.yml
Service: virtual-machines
Sub-service: imaging
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@fgs91
Thanks for your feedback! We will investigate and update as appropriate.

@fgs91
Thank you for your feedback. I understand that it is important to ensure application OS consistency when running a project over several months, and that knowing the scheduled deprecation date for a VM image would be helpful in choosing the proper image at the beginning of the project.
Currently, Azure provides information on the deprecation status of VM images, but does not provide information on the scheduled deprecation date. However, you can use the Azure VM Image Builder service to create custom VM images that include the latest updates and patches, and then use these custom images to ensure consistency across your VMs.
With Azure VM Image Builder, you can create a pipeline that automatically builds and tests custom VM images, and then publishes them to your Azure subscription. This allows you to ensure that all of your VMs are running the same image with the latest updates and patches.
I hope this information is helpful. Let me know if you have any further questions or concerns.


Update To Babel 6.x

Babel 6.x has a new plugin architecture which breaks assumptions used to transpile + cache Babel in 3rd party packages. babel-core looks for the plugins and presets (specified below) in directories relative to the .js file being transpiled. Thus, because the plugins and presets are included in ${PATH_TO_ATOM}/node_modules (and not ~/.atom/packages/some-random-package/node_modules), they are not found. There is no way to give babel-core a root directory from which to search.
This leaves us with two paths forward:

Submit a PR to babel-core to add an option for specifying a presetRoot and a pluginRoot
Require 3rd party packages wishing to use babel to add the required packages to their package.json

Migration Notes:

[ ] Update static/babelrc.json:

[ ] Clear file
[ ] Add "presets": ["es2015", "stage-0", "react"]
[ ] Add "plugins" : ["syntax-async-functions"]
[ ] Add "sourceMaps": "inline"

[ ] Add in babel-polyfill at needed locations:

[ ] static/index.html?
[ ] src/browser/main.coffee?

[ ] Update package.json and build/package.json
[ ] Update build/Gruntfile.coffee

package.json
"babel-core": "^6.4.5",
"babel-plugin-syntax-async-functions": "^6.3.13",
"babel-polyfill": "^6.3.14",
"babel-preset-es2015": "^6.3.13",
"babel-preset-stage-0": "^6.3.13",
"babel-preset-react": "^6.3.13",

Gruntfile.coffee
  babelConfig =
    options:
      extends: '../static/babelrc'
    dist:
      files: [
        expand: true
        src: [
          'src/**/*.js'
        ]
        dest: appDir
      ]

This is related to #10509.

Per @paulcbetts, we could look into using electron-compile to externalize this responsibility from Atom itself.

If I'm understanding the issue correctly, option 2 generally sounds better to me although it would sometimes be less convenient. Relying on Atom for here seems problematic because whatever plugins it provides will always have the potential to be out of date.
Does electron-compile address that concern? Would it actually be possible to use in the near term? I mean, does it work with the versions of electron Atom is shipping?

Yes I think electron-compile is the best path forward at this time.


Add extra_vars option for in the "ts" section

This option is needed when regular expressions are used to specify variables for ncclimo. This makes the variable list more flexible.
For example, if the variables are specified with a mix of wildcards and variable names like
ncclimo -v area,'^DF_', it will fail.
But ncclimo -v '^DF_' --var_xtr=area will work.
This PR adds the --var_xtr option.
I tested it successfully on compy and chrysalis.

It is good to know that this PR helps #31 as well. I am merging it now.