GoogleSignIn.signIn() returns null on macos

What package does this bug report belong to?
google_sign_in
What target platforms are you seeing this bug on?
macOS
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  _discoveryapis_commons:
    dependency: transitive
    description:
      name: _discoveryapis_commons
      sha256: "113c4100b90a5b70a983541782431b82168b3cae166ab130649c36eb3559d498"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.7"
  _fe_analyzer_shared:
    dependency: transitive
    description:
      name: _fe_analyzer_shared
      sha256: f256b0c0ba6c7577c15e2e4e114755640a875e885099367bf6e012b19314c834
      url: "https://pub.dev"
    source: hosted
    version: "72.0.0"
  _flutterfire_internals:
    dependency: transitive
    description:
      name: _flutterfire_internals
      sha256: "9371d13b8ee442e3bfc08a24e3a1b3742c839abbfaf5eef11b79c4b862c89bf7"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.41"
  _macros:
    dependency: transitive
    description: dart
    source: sdk
    version: "0.3.2"
  analyzer:
    dependency: transitive
    description:
      name: analyzer
      sha256: b652861553cd3990d8ed361f7979dc6d7053a9ac8843fa73820ab68ce5410139
      url: "https://pub.dev"
    source: hosted
    version: "6.7.0"
  args:
    dependency: transitive
    description:
      name: args
      sha256: "7cf60b9f0cc88203c5a190b4cd62a99feea42759a7fa695010eb5de1c0b2252a"
      url: "https://pub.dev"
    source: hosted
    version: "2.5.0"
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  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: "79b2aef6ac2ed00046867ed354c88778c9c0f029df8a20fe10b5436826721ef9"
      url: "https://pub.dev"
    source: hosted
    version: "4.0.2"
  build_resolvers:
    dependency: transitive
    description:
      name: build_resolvers
      sha256: "339086358431fa15d7eca8b6a36e5d783728cf025e559b834f4609a1fcfb7b0a"
      url: "https://pub.dev"
    source: hosted
    version: "2.4.2"
  build_runner:
    dependency: "direct dev"
    description:
      name: build_runner
      sha256: dd09dd4e2b078992f42aac7f1a622f01882a8492fef08486b27ddde929c19f04
      url: "https://pub.dev"
    source: hosted
    version: "2.4.12"
  build_runner_core:
    dependency: transitive
    description:
      name: build_runner_core
      sha256: f8126682b87a7282a339b871298cc12009cb67109cfa1614d6436fb0289193e0
      url: "https://pub.dev"
    source: hosted
    version: "7.3.2"
  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: c7913a9737ee4007efedaffc968c049fd0f3d0e49109e778edc10de9426005cb
      url: "https://pub.dev"
    source: hosted
    version: "8.9.2"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  charcode:
    dependency: transitive
    description:
      name: charcode
      sha256: fb98c0f6d12c920a02ee2d998da788bca066ca5f148492b7085ee23372b12306
      url: "https://pub.dev"
    source: hosted
    version: "1.3.1"
  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: f692079e25e7869c14132d39f223f8eec9830eb76131925143b2129c4bb01b37
      url: "https://pub.dev"
    source: hosted
    version: "4.10.0"
  collection:
    dependency: transitive
    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: ec30d999af904f33454ba22ed9a86162b35e52b44ac4807d1d93c288041d7d27
      url: "https://pub.dev"
    source: hosted
    version: "3.0.5"
  csslib:
    dependency: transitive
    description:
      name: csslib
      sha256: "706b5707578e0c1b4b7550f64078f0a0f19dec3f50a178ffae7006b0a9ca58fb"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  dart_quill_delta:
    dependency: transitive
    description:
      name: dart_quill_delta
      sha256: "302e389e704afecab4ad7a4ddcb76aa57ea7ca01fc36ccf54b6c41c6e04c94a4"
      url: "https://pub.dev"
    source: hosted
    version: "10.4.9"
  dart_style:
    dependency: transitive
    description:
      name: dart_style
      sha256: "99e066ce75c89d6b29903d788a7bb9369cf754f7b24bf70bf4b6d6d6b26853b9"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.6"
  device_info_plus:
    dependency: transitive
    description:
      name: device_info_plus
      sha256: a7fd703482b391a87d60b6061d04dfdeab07826b96f9abd8f5ed98068acc0074
      url: "https://pub.dev"
    source: hosted
    version: "10.1.2"
  device_info_plus_platform_interface:
    dependency: transitive
    description:
      name: device_info_plus_platform_interface
      sha256: "282d3cf731045a2feb66abfe61bbc40870ae50a3ed10a4d3d217556c35c8c2ba"
      url: "https://pub.dev"
    source: hosted
    version: "7.0.1"
  diff_match_patch:
    dependency: transitive
    description:
      name: diff_match_patch
      sha256: "2efc9e6e8f449d0abe15be240e2c2a3bcd977c8d126cfd70598aee60af35c0a4"
      url: "https://pub.dev"
    source: hosted
    version: "0.4.1"
  equatable:
    dependency: transitive
    description:
      name: equatable
      sha256: c2b87cb7756efdf69892005af546c56c0b5037f54d2a88269b4f347a505e3ca2
      url: "https://pub.dev"
    source: hosted
    version: "2.0.5"
  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: "16ed7b077ef01ad6170a3d0c57caa4a112a38d7a2ed5602e0aca9ca6f3d98da6"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.3"
  file:
    dependency: transitive
    description:
      name: file
      sha256: "5fc22d7c25582e38ad9a8515372cd9a93834027aacf1801cf01164dac0ffa08c"
      url: "https://pub.dev"
    source: hosted
    version: "7.0.0"
  firebase_auth:
    dependency: "direct main"
    description:
      name: firebase_auth
      sha256: "6f5792bdc208416bfdfbfe3363b78ce01667b6ebc4c5cb47cfa891f2fca45ab7"
      url: "https://pub.dev"
    source: hosted
    version: "5.2.0"
  firebase_auth_platform_interface:
    dependency: transitive
    description:
      name: firebase_auth_platform_interface
      sha256: "80237bb8a92bb0a5e3b40de1c8dbc80254e49ac9e3907b4b47b8e95ac3dd3fad"
      url: "https://pub.dev"
    source: hosted
    version: "7.4.4"
  firebase_auth_web:
    dependency: transitive
    description:
      name: firebase_auth_web
      sha256: "9d315491a6be65ea83511cb0e078544a309c39dd54c0ee355c51dbd6d8c03cc8"
      url: "https://pub.dev"
    source: hosted
    version: "5.12.6"
  firebase_core:
    dependency: "direct main"
    description:
      name: firebase_core
      sha256: "06537da27db981947fa535bb91ca120b4e9cb59cb87278dbdde718558cafc9ff"
      url: "https://pub.dev"
    source: hosted
    version: "3.4.0"
  firebase_core_platform_interface:
    dependency: transitive
    description:
      name: firebase_core_platform_interface
      sha256: f7d7180c7f99babd4b4c517754d41a09a4943a0f7a69b65c894ca5c68ba66315
      url: "https://pub.dev"
    source: hosted
    version: "5.2.1"
  firebase_core_web:
    dependency: transitive
    description:
      name: firebase_core_web
      sha256: "362e52457ed2b7b180964769c1e04d1e0ea0259fdf7025fdfedd019d4ae2bd88"
      url: "https://pub.dev"
    source: hosted
    version: "2.17.5"
  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_colorpicker:
    dependency: transitive
    description:
      name: flutter_colorpicker
      sha256: "969de5f6f9e2a570ac660fb7b501551451ea2a1ab9e2097e89475f60e07816ea"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  flutter_keyboard_visibility:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility
      sha256: "98664be7be0e3ffca00de50f7f6a287ab62c763fc8c762e0a21584584a3ff4f8"
      url: "https://pub.dev"
    source: hosted
    version: "6.0.0"
  flutter_keyboard_visibility_linux:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility_linux
      sha256: "6fba7cd9bb033b6ddd8c2beb4c99ad02d728f1e6e6d9b9446667398b2ac39f08"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  flutter_keyboard_visibility_macos:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility_macos
      sha256: c5c49b16fff453dfdafdc16f26bdd8fb8d55812a1d50b0ce25fc8d9f2e53d086
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  flutter_keyboard_visibility_platform_interface:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility_platform_interface
      sha256: e43a89845873f7be10cb3884345ceb9aebf00a659f479d1c8f4293fcb37022a4
      url: "https://pub.dev"
    source: hosted
    version: "2.0.0"
  flutter_keyboard_visibility_web:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility_web
      sha256: d3771a2e752880c79203f8d80658401d0c998e4183edca05a149f5098ce6e3d1
      url: "https://pub.dev"
    source: hosted
    version: "2.0.0"
  flutter_keyboard_visibility_windows:
    dependency: transitive
    description:
      name: flutter_keyboard_visibility_windows
      sha256: fc4b0f0b6be9b93ae527f3d527fb56ee2d918cd88bbca438c478af7bcfd0ef73
      url: "https://pub.dev"
    source: hosted
    version: "1.0.0"
  flutter_lints:
    dependency: "direct dev"
    description:
      name: flutter_lints
      sha256: "3f41d009ba7172d5ff9be5f6e6e6abb4300e263aab8866d2a0842ed2a70f8f0c"
      url: "https://pub.dev"
    source: hosted
    version: "4.0.0"
  flutter_localizations:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_quill:
    dependency: "direct main"
    description:
      name: flutter_quill
      sha256: "58275536722c19e08d983ae5456ef0f13dbc16a2576f239054da3564b4e2776a"
      url: "https://pub.dev"
    source: hosted
    version: "10.4.9"
  flutter_quill_delta_from_html:
    dependency: transitive
    description:
      name: flutter_quill_delta_from_html
      sha256: "5461df689818d34237f7a5109763e1e4663b973c2a44a46c398bbd46381d297a"
      url: "https://pub.dev"
    source: hosted
    version: "1.4.0"
  flutter_test:
    dependency: "direct dev"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_web_plugins:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  frontend_server_client:
    dependency: transitive
    description:
      name: frontend_server_client
      sha256: f64a0333a82f30b0cca061bc3d143813a486dc086b574bfb233b7c1372427694
      url: "https://pub.dev"
    source: hosted
    version: "4.0.0"
  get:
    dependency: "direct main"
    description:
      name: get
      sha256: e4e7335ede17452b391ed3b2ede016545706c01a02292a6c97619705e7d2a85e
      url: "https://pub.dev"
    source: hosted
    version: "4.6.6"
  glob:
    dependency: transitive
    description:
      name: glob
      sha256: "0e7014b3b7d4dac1ca4d6114f82bf1782ee86745b9b42a92c9289c23d8a0ab63"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  google_identity_services_web:
    dependency: transitive
    description:
      name: google_identity_services_web
      sha256: "5be191523702ba8d7a01ca97c17fca096822ccf246b0a9f11923a6ded06199b6"
      url: "https://pub.dev"
    source: hosted
    version: "0.3.1+4"
  google_sign_in:
    dependency: "direct main"
    description:
      name: google_sign_in
      sha256: "0b8787cb9c1a68ad398e8010e8c8766bfa33556d2ab97c439fb4137756d7308f"
      url: "https://pub.dev"
    source: hosted
    version: "6.2.1"
  google_sign_in_android:
    dependency: transitive
    description:
      name: google_sign_in_android
      sha256: "5a47ebec9af97daf0822e800e4f101c3340b5ebc3f6898cf860c1a71b53cf077"
      url: "https://pub.dev"
    source: hosted
    version: "6.1.28"
  google_sign_in_ios:
    dependency: transitive
    description:
      name: google_sign_in_ios
      sha256: "4898410f55440049e1ba8f15411612d9f89299d89c61cd9baf7e02d56ff81ac7"
      url: "https://pub.dev"
    source: hosted
    version: "5.7.7"
  google_sign_in_platform_interface:
    dependency: transitive
    description:
      name: google_sign_in_platform_interface
      sha256: "1f6e5787d7a120cc0359ddf315c92309069171306242e181c09472d1b00a2971"
      url: "https://pub.dev"
    source: hosted
    version: "2.4.5"
  google_sign_in_web:
    dependency: transitive
    description:
      name: google_sign_in_web
      sha256: "042805a21127a85b0dc46bba98a37926f17d2439720e8a459d27045d8ef68055"
      url: "https://pub.dev"
    source: hosted
    version: "0.12.4+2"
  googleapis:
    dependency: "direct main"
    description:
      name: googleapis
      sha256: "864f222aed3f2ff00b816c675edf00a39e2aaf373d728d8abec30b37bee1a81c"
      url: "https://pub.dev"
    source: hosted
    version: "13.2.0"
  graphs:
    dependency: transitive
    description:
      name: graphs
      sha256: "741bbf84165310a68ff28fe9e727332eef1407342fca52759cb21ad8177bb8d0"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  hive:
    dependency: transitive
    description:
      name: hive
      sha256: "8dcf6db979d7933da8217edcec84e9df1bdb4e4edc7fc77dbd5aa74356d6d941"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.3"
  hive_flutter:
    dependency: "direct main"
    description:
      name: hive_flutter
      sha256: dca1da446b1d808a51689fb5d0c6c9510c0a2ba01e22805d492c73b68e33eecc
      url: "https://pub.dev"
    source: hosted
    version: "1.1.0"
  hive_generator:
    dependency: "direct dev"
    description:
      name: hive_generator
      sha256: "06cb8f58ace74de61f63500564931f9505368f45f98958bd7a6c35ba24159db4"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.1"
  html:
    dependency: transitive
    description:
      name: html
      sha256: "3a7812d5bcd2894edf53dfaf8cd640876cf6cef50a8f238745c8b8120ea74d3a"
      url: "https://pub.dev"
    source: hosted
    version: "0.15.4"
  http:
    dependency: transitive
    description:
      name: http
      sha256: b9c29a161230ee03d3ccf545097fccd9b87a5264228c5d348202e0f0c28f9010
      url: "https://pub.dev"
    source: hosted
    version: "1.2.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"
  intl:
    dependency: "direct main"
    description:
      name: intl
      sha256: d6f56758b7d3014a48af9701c085700aac781a92a87a62b1333b46d8879661cf
      url: "https://pub.dev"
    source: hosted
    version: "0.19.0"
  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: c1b2e9b5ea78c45e1a0788d29606ba27dc5f71f019f32ca5140f61ef071838cf
      url: "https://pub.dev"
    source: hosted
    version: "0.7.1"
  json_annotation:
    dependency: transitive
    description:
      name: json_annotation
      sha256: "1ce844379ca14835a50d2f019a3099f419082cfdd231cd86a142af94dd5c6bb1"
      url: "https://pub.dev"
    source: hosted
    version: "4.9.0"
  leak_tracker:
    dependency: transitive
    description:
      name: leak_tracker
      sha256: "3f87a60e8c63aecc975dda1ceedbc8f24de75f09e4856ea27daf8958f2f0ce05"
      url: "https://pub.dev"
    source: hosted
    version: "10.0.5"
  leak_tracker_flutter_testing:
    dependency: transitive
    description:
      name: leak_tracker_flutter_testing
      sha256: "932549fb305594d82d7183ecd9fa93463e9914e1b67cacc34bc40906594a1806"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.5"
  leak_tracker_testing:
    dependency: transitive
    description:
      name: leak_tracker_testing
      sha256: "6ba465d5d76e67ddf503e1161d1f4a6bc42306f9d66ca1e8f079a47290fb06d3"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.1"
  lints:
    dependency: transitive
    description:
      name: lints
      sha256: "976c774dd944a42e83e2467f4cc670daef7eed6295b10b36ae8c85bcbf828235"
      url: "https://pub.dev"
    source: hosted
    version: "4.0.0"
  logging:
    dependency: transitive
    description:
      name: logging
      sha256: "623a88c9594aa774443aa3eb2d41807a48486b5613e67599fb4c41c0ad47c340"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  macros:
    dependency: transitive
    description:
      name: macros
      sha256: "0acaed5d6b7eab89f63350bccd82119e6c602df0f391260d0e32b5e23db79536"
      url: "https://pub.dev"
    source: hosted
    version: "0.1.2-main.4"
  markdown:
    dependency: transitive
    description:
      name: markdown
      sha256: ef2a1298144e3f985cc736b22e0ccdaf188b5b3970648f2d9dc13efd1d9df051
      url: "https://pub.dev"
    source: hosted
    version: "7.2.2"
  matcher:
    dependency: transitive
    description:
      name: matcher
      sha256: d2323aa2060500f906aa31a895b4030b6da3ebdcc5619d14ce1aada65cd161cb
      url: "https://pub.dev"
    source: hosted
    version: "0.12.16+1"
  material_color_utilities:
    dependency: transitive
    description:
      name: material_color_utilities
      sha256: f7142bb1154231d7ea5f96bc7bde4bda2a0945d2806bb11670e30b850d56bdec
      url: "https://pub.dev"
    source: hosted
    version: "0.11.1"
  meta:
    dependency: transitive
    description:
      name: meta
      sha256: bdb68674043280c3428e9ec998512fb681678676b3c54e773629ffe74419f8c7
      url: "https://pub.dev"
    source: hosted
    version: "1.15.0"
  mime:
    dependency: transitive
    description:
      name: mime
      sha256: "801fd0b26f14a4a58ccb09d5892c3fbdeff209594300a542492cf13fba9d247a"
      url: "https://pub.dev"
    source: hosted
    version: "1.0.6"
  package_config:
    dependency: transitive
    description:
      name: package_config
      sha256: "1c5b77ccc91e4823a5af61ee74e6b972db1ef98c2ff5a18d3161c982a55448bd"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.0"
  path:
    dependency: transitive
    description:
      name: path
      sha256: "087ce49c3f0dc39180befefc60fdb4acd8f8620e5682fe2476afd0b3688bb4af"
      url: "https://pub.dev"
    source: hosted
    version: "1.9.0"
  path_provider:
    dependency: transitive
    description:
      name: path_provider
      sha256: fec0d61223fba3154d87759e3cc27fe2c8dc498f6386c6d6fc80d1afdd1bf378
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  path_provider_android:
    dependency: transitive
    description:
      name: path_provider_android
      sha256: "6f01f8e37ec30b07bc424b4deabac37cacb1bc7e2e515ad74486039918a37eb7"
      url: "https://pub.dev"
    source: hosted
    version: "2.2.10"
  path_provider_foundation:
    dependency: transitive
    description:
      name: path_provider_foundation
      sha256: f234384a3fdd67f989b4d54a5d73ca2a6c422fa55ae694381ae0f4375cd1ea16
      url: "https://pub.dev"
    source: hosted
    version: "2.4.0"
  path_provider_linux:
    dependency: transitive
    description:
      name: path_provider_linux
      sha256: f7a1fe3a634fe7734c8d3f2766ad746ae2a2884abe22e241a8b301bf5cac3279
      url: "https://pub.dev"
    source: hosted
    version: "2.2.1"
  path_provider_platform_interface:
    dependency: transitive
    description:
      name: path_provider_platform_interface
      sha256: "88f5779f72ba699763fa3a3b06aa4bf6de76c8e5de842cf6f29e2e06476c2334"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  path_provider_windows:
    dependency: transitive
    description:
      name: path_provider_windows
      sha256: bd6f00dbd873bfb70d0761682da2b3a2c2fccc2b9e84c495821639601d81afe7
      url: "https://pub.dev"
    source: hosted
    version: "2.3.0"
  platform:
    dependency: transitive
    description:
      name: platform
      sha256: "9b71283fc13df574056616011fb138fd3b793ea47cc509c189a6c3fa5f8a1a65"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.5"
  plugin_platform_interface:
    dependency: transitive
    description:
      name: plugin_platform_interface
      sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.8"
  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: c799b721d79eb6ee6fa56f00c04b472dcd44a30d258fac2174a6ec57302678f8
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  quiver:
    dependency: transitive
    description:
      name: quiver
      sha256: ea0b925899e64ecdfbf9c7becb60d5b50e706ade44a85b2363be2a22d88117d2
      url: "https://pub.dev"
    source: hosted
    version: "3.2.2"
  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: "073c147238594ecd0d193f3456a5fe91c4b0abbcc68bf5cd95b36c4e194ac611"
      url: "https://pub.dev"
    source: hosted
    version: "2.0.0"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_gen:
    dependency: transitive
    description:
      name: source_gen
      sha256: "14658ba5f669685cd3d63701d01b31ea748310f7ab854e471962670abcf57832"
      url: "https://pub.dev"
    source: hosted
    version: "1.5.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"
  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"
  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: "5b8a98dafc4d5c4c9c72d8b31ab2b23fc13422348d2997120294d3bac86b4ddb"
      url: "https://pub.dev"
    source: hosted
    version: "0.7.2"
  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"
  url_launcher:
    dependency: transitive
    description:
      name: url_launcher
      sha256: "21b704ce5fa560ea9f3b525b43601c678728ba46725bab9b01187b4831377ed3"
      url: "https://pub.dev"
    source: hosted
    version: "6.3.0"
  url_launcher_android:
    dependency: transitive
    description:
      name: url_launcher_android
      sha256: e35a698ac302dd68e41f73250bd9517fe3ab5fa4f18fe4647a0872db61bacbab
      url: "https://pub.dev"
    source: hosted
    version: "6.3.10"
  url_launcher_ios:
    dependency: transitive
    description:
      name: url_launcher_ios
      sha256: e43b677296fadce447e987a2f519dcf5f6d1e527dc35d01ffab4fff5b8a7063e
      url: "https://pub.dev"
    source: hosted
    version: "6.3.1"
  url_launcher_linux:
    dependency: transitive
    description:
      name: url_launcher_linux
      sha256: e2b9622b4007f97f504cd64c0128309dfb978ae66adbe944125ed9e1750f06af
      url: "https://pub.dev"
    source: hosted
    version: "3.2.0"
  url_launcher_macos:
    dependency: transitive
    description:
      name: url_launcher_macos
      sha256: "9a1a42d5d2d95400c795b2914c36fdcb525870c752569438e4ebb09a2b5d90de"
      url: "https://pub.dev"
    source: hosted
    version: "3.2.0"
  url_launcher_platform_interface:
    dependency: transitive
    description:
      name: url_launcher_platform_interface
      sha256: "552f8a1e663569be95a8190206a38187b531910283c3e982193e4f2733f01029"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  url_launcher_web:
    dependency: transitive
    description:
      name: url_launcher_web
      sha256: "772638d3b34c779ede05ba3d38af34657a05ac55b06279ea6edd409e323dca8e"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.3"
  url_launcher_windows:
    dependency: transitive
    description:
      name: url_launcher_windows
      sha256: "49c10f879746271804767cb45551ec5592cdab00ee105c06dddde1a98f73b185"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.2"
  uuid:
    dependency: "direct main"
    description:
      name: uuid
      sha256: "83d37c7ad7aaf9aa8e275490669535c8080377cfa7a7004c24dfac53afffaa90"
      url: "https://pub.dev"
    source: hosted
    version: "4.4.2"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  vm_service:
    dependency: transitive
    description:
      name: vm_service
      sha256: f652077d0bdf60abe4c1f6377448e8655008eef28f128bc023f7b5e8dfeb48fc
      url: "https://pub.dev"
    source: hosted
    version: "14.2.4"
  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: "97da13628db363c635202ad97068d47c5b8aa555808e7a9411963c533b449b27"
      url: "https://pub.dev"
    source: hosted
    version: "0.5.1"
  web_socket:
    dependency: transitive
    description:
      name: web_socket
      sha256: "3c12d96c0c9a4eec095246debcea7b86c0324f22df69893d538fcc6f1b8cce83"
      url: "https://pub.dev"
    source: hosted
    version: "0.1.6"
  web_socket_channel:
    dependency: transitive
    description:
      name: web_socket_channel
      sha256: "9f187088ed104edd8662ca07af4b124465893caf063ba29758f97af57e61da8f"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.1"
  win32:
    dependency: transitive
    description:
      name: win32
      sha256: "68d1e89a91ed61ad9c370f9f8b6effed9ae5e0ede22a270bdfa6daf79fc2290a"
      url: "https://pub.dev"
    source: hosted
    version: "5.5.4"
  win32_registry:
    dependency: transitive
    description:
      name: win32_registry
      sha256: "723b7f851e5724c55409bb3d5a32b203b3afe8587eaf5dafb93a5fed8ecda0d6"
      url: "https://pub.dev"
    source: hosted
    version: "1.1.4"
  xdg_directories:
    dependency: transitive
    description:
      name: xdg_directories
      sha256: faea9dee56b520b55a566385b84f2e8de55e7496104adada9962e0bd11bcff1d
      url: "https://pub.dev"
    source: hosted
    version: "1.0.4"
  yaml:
    dependency: transitive
    description:
      name: yaml
      sha256: "75769501ea3489fca56601ff33454fe45507ea3bfb014161abc3b43ae25989d5"
      url: "https://pub.dev"
    source: hosted
    version: "3.1.2"
sdks:
  dart: ">=3.5.0 <4.0.0"
  flutter: ">=3.24.0"

Steps to reproduce
I have set up project files as per the documentation. Everything works as expected on Android and iOS, but on macos, the signIn() call returns null after the user is selected in the browser.
Run:
final googleAccount = await GoogleSignIn().signIn();

Expected results
Open browser to allow user to sign in (or select existing user), return to app and googleAccount should be initialized.
Actual results
Opens the browser, but after selecting account to use, googleAccount is null. There are no warnings or errors in the logs.
Code sample
Code sample
final googleAccount = await GoogleSignIn().signIn();

Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
There are no warnings or errors in the logs.
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.24.0, on macOS 14.6.1 23G93 darwin-arm64, locale en-CA)
    • Flutter version 3.24.0 on channel stable at /Users/brent/fvm/versions/3.24.0
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 80c2e84975 (4 weeks ago), 2024-07-30 23:06:49 +0700
    • Engine revision b8800d88be
    • Dart version 3.5.0
    • DevTools version 2.37.2

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

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

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

[✓] Android Studio (version 2024.1)
    • 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.10+0-17.0.10b1087.21-11609105)

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

[✓] Connected device (6 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554                            • android-arm64  • Android 13 (API 33) (emulator)
    • iPad (3) (mobile)               • 48f239165db2144df466935b36173111cd512a4d • ios            • iOS 17.5.1 21F90
    • iPhone 15 (mobile)              • D12DF208-76C6-4F95-8B5D-6353EB3B5A17     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-4 (simulator)
    • macOS (desktop)                 • macos                                    • darwin-arm64   • macOS 14.6.1 23G93 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad                    • darwin         • macOS 14.6.1 23G93 darwin-arm64
    • Chrome (web)                    • chrome                                   • web-javascript • Google Chrome 128.0.6613.85

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

• No issues found!

For web you have to use this google_sign_in_web package

Have you connect it with firebase Google sign in orrr with  Google cloud

I'm not exactly sure what you are asking. I have configured both firebase and google cloud backends. I have initialized firebase in my app. I am calling GoogleSignIn(...).signIn().
It works fine on Android and iOS, but it is not working if I run on macos.

@bkleineibst Thanks for the update.
I believe you need to setup entitlements as mentioned here https://docs.flutter.dev/platform-integration/macos/building#setting-up-entitlements

Thanks @darshankawar.
I had already set up entitlements as per the google_sign_in_ios guide: https://pub.dev/packages/google_sign_in_ios#macos-setup
According to the guide, not setting these will result in a keychain_error PlatformException, which I was not seeing, even if I removed the entitlement.
The page that you linked mentioned the com.apple.security.network.client entitlement. Enabling this resolved the issue.
I'm not sure if this case could be handled better by the plugin, but at the very least, I think the google_sign_in_ios documentation should be updated to mention that this entitlement is also required for macos.
I also tried to remove the keychain-access-groups entitlement, after adding the com.apple.security.network.client one, and the app still works fine. It seems like this is only required for FirebaseAuth, but GoogleSignIn works fine without it.
Thanks for the help.

Good to now it helped to resolve your issue. Closing as such.

, I think the google_sign_in_ios documentation should be updated to mention that this entitlement is also required for macos.

You may file a separate issue so that we can track it properly.


Cloning the OpenTitan repository by following is giving error

Description
Cloning the OpenTitan repository by following is giving error as in snippet.
git clone https://github.com/lowRISC/opentitan.git

I'm not sure what could cause this, but GitHub was having some trouble yesterday so maybe that's to blame.
I'm closing this (because I don't think there's anything we can do about it!) but please re-open if there's anything else that comes up.

Hello
the URL -  https://github.com/lowRISC/opentitan.git/info/refs is said to be
phased out.
[image: image.png]
Please suggest
On Wed, Dec 18, 2024 at 9:42 PM Rupert Swarbrick @.***>
wrote:

Closed #25676 https://github.com/lowRISC/opentitan/issues/25676 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/25676#event-15705819830, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZD7MQPA4B3JPZALTUXC7D2GGNH7AVCNFSM6AAAAABTYDB2CKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVG4YDKOBRHE4DGMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You'll need to update your git client, says GitHub:
Please upgrade your git client.
GitHub.com no longer supports git over dumb-http: https://github.com/blog/809-git-dumb-http-transport-to-be-turned-off-in-90-days

For more help: https://docs.github.com/en/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors


Bump to v1.13.3

Updates:

client-go
k8s images
api-server flags
etcd
core-dns

There may some other ancillary flags/features to upgrade, but intend to leave that as follow up.

/lgtm
/approve


fix(jellyfish-network): Fix missing devnet case

What this PR does / why we need it:
Fixes missing devnet case
Additional comments?:
Added support for devnet in legacy-api and ocean-api-client packages

Required for testing on Scan - https://github.com/WavesHQ/scan/pull/1656


Add HaxeDevelop icon for .hxproj files

HaxeDevelop is a very popular IDE for Haxe. It uses .hxproj as the extension for its Haxe project format.
This is it from me for now. ;)

Published all your PRs right now in 1.7.3. Thanks for your great work @Gama11!

Thank you for the great extension! :)
Is .gitkeep working for you? I get a generic file icon there, hm...

it's working locally...

Must've been something wrong locally. I switched from the git version to the official one from the extension installer again and it works now. :+1:

I've tried the released one recently installed from the marketplace and it's working! Thanks for this! :+1:


Build tests on AppVeyor

To be really useful we have to ensure that Boost Matheval builds on all platforms.

Partially fixed in 02de3a27933ffc2f4ec91ef804c8222e4b45c38a.
Building tests still fails including but not limited to these errors
C:\Libraries\boost_1_59_0\boost/test/impl/test_tools.ipp(397): error C2491: 'boost::test_tools::tt_detail::prod_report_format': definition of dllimport function not allowed
C:\Libraries\boost_1_59_0\boost/test/tools/old/impl.hpp(117): error C2375: 'boost::test_tools::tt_detail::equal_impl': redefinition; different linkage
C:\Libraries\boost_1_59_0\boost/test/tools/old/impl.hpp(118): error C2264: 'boost::test_tools::tt_detail::equal_impl': error in function definition or declaration; function not called

Now it somehow builds (I don't know why) but the tests don't run.  They fail with ***Exception: Other
https://ci.appveyor.com/project/hmenke/boost-matheval/build/1.0.19

A solution was found with the help of the Stack Overflow user sehe: https://stackoverflow.com/questions/47168753
Entirely fixed in 5e780397bc4cde6941295474d788c8cd70e1af77


PHPMyAdmin

I tried to connect by default credentials root/tiger, but have this problem:
Cannot log in to the MySQL server
mysqli_real_connect(): The server requested authentication method unknown to the client [caching_sha2_password]
mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client

Instead of localhost use mysql. Yes, it's weird but heh.
I had the same problem when I tried to install WP.

@pin147 Can you elaborate? I have the same problem as Zibulon but don't know what you mean by 'using mysql'.

@KappaDistributive
It's a hostname of MySQL server. See the following example,
<?php
$link = mysqli_connect("mysql", "root", "tiger", null);
if (!$link) {
    echo "Error: Unable to connect to MySQL." . PHP_EOL;
    echo "Debugging errno: " . mysqli_connect_errno() . PHP_EOL;
    echo "Debugging error: " . mysqli_connect_error() . PHP_EOL;
    exit;
}
echo "Success: A proper connection to MySQL was made! The docker database is great." . PHP_EOL;
echo "Host information: " . mysqli_get_host_info($link) . PHP_EOL;
mysqli_close($link);

See the connection function, we are passing mysql as a first parameter and that is a hostname. Generally, we use localhost for most of the cases, but in this case, it is different.


TCP_QUICKACK not durable

Hi,
This isn't an actual bug report since I have not confirmed the problem with Netty. But Netty has been a big source of inspiration for the Hazelcast networking, so we would like to give something back.
I was running into extremely slow communication between the sender and receiver and a congested (on purpose) local socket which caused 40ms RTT pauses continuously.

I finally figured out that the TCP_QUICKACK setting isn't durable:
https://topic.alibabacloud.com/a/linux-tcp-delay-confirmation_1_16_31848681.html
https://github.com/microsoft/cpprestsdk/issues/1201
So even if you set it, it gets unset after some time. I confirmed this in the Hazelcast code by checking the status of TCP_QUICKACK.
So apparently the setting needs to be reapplied after every read. I had a peek at the Netty code and it seems that TCP_QUICKACK is only set when you are configuring the socket. So I guess Netty can suffer from the problem where TCP_QUICKACK is enabled by the user, but it gets unset.
After reapplying the TCP_QUICKACK, our performance problem was resolved.
Regards,
Peter

It seems there is an earlier ticket:
https://github.com/netty/netty/issues/8129
And it seems that the user needs to be aware of the non permanent behavior of the setting and need to reapply it.


[FLOC 2389] Update info in the Flocker Doc landing page

Fixes 2389
Note - the issue requests that the content be copied from the Introduction to Flocker page - I thought this was unnecessary repetition, and have written a short intro to the documentation, and what the user can expect to find.

Looks good, merge when happy.


Fix eslint

Lowering the @types/vscode version introduced some eslint errors

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

v0.120.0
v0.120.0
GitHub release

Your semantic-release bot :package::rocket:


Implement event check-in handler

Implements #72

This PR looks working, but now we need to prove this with tests.
Plz implement some in https://github.com/GDG-Ukraine/gdg.org.ua/blob/master/src/tests/test_rest_controller.py file.
You may replace and drop lots of its contents, since it doesn't contain any real tests.
Add new data into DB inside of populate_db() function. It instantiates models, adds those to session and then commits data into DB.
Please check asserts available at http://docs.cherrypy.org/en/latest/pkg/cherrypy.test.html#cherrypy.test.webtest.WebCase
there's getPage() available for HTTP queries
You may check https://bitbucket.org/webknjaz/blueberrypy-wk/src/cb2753de29c4ec0f1be00baf2e828b35e0939b47/src/blueberrypy/tests/test_tools.py?at=default&fileviewer=file-view-default#test_tools.py-104 for some web test examples

I'm merging this. Tests to be written later as a part of #94


Failed Action needs investigation

https://github.com/nanomq/NanoNNG/actions/runs/4581400673/jobs/8090900895

it is fixed in https://github.com/nanomq/NanoNNG/pull/496.


Gateway fails to deliver message

When message is sent from an external sender in response to an internal message:
<EMAIL_ADDRESS>(expanded from lgx@ubikom.cc): Command died with status 1:
"/home/ubuntu/ubikom/ubikom-gateway". Command output: [90m15:38:08[0m
[33mDBG[0m connecting to lookup service [36murl=[0malpha.ubikom.cc:8825
[90m15:38:08[0m [33mDBG[0m sending mail
<EMAIL_ADDRESS>[90m15:38:08[0m
[1m[31mFTL_[0m_[0m failed to send message [31merror=[0m_[31m"failed to
get receiver public key: rpc error: code = InvalidArgument desc = invalid
name"_[0m
Looks like it pulls a wrong key (for ubuntu@ubikom.cc).

The problem is with multiple addresses, it expects a single one.

Fixed


Tab Menu Not Working

Tab menu does not work for regular users. The sound works, but other than that, nothing else works.

Unrelated to Clockwork, issue only with your server.


Using Servor For Auto Reload

On the Snowpack tutorial, they recommend using servor instead of serve because it has live reload.
Tutorial (Serve & Run Your Application):
https://www.snowpack.dev/#installing-a-dev-server
The NPM Servor Package:
https://www.npmjs.com/package/servor
However, when I run their command npx servor --reload (or npx servor --reload dist)
It shows up as a blank page, have you tried running svelvet with servor? I'm probably messing up the command or the setup. But it does seem to be an easy way for you to add auto-refresh to the project by using this other dev server with minimum effort.

@jakedeichert haha same here, I had the same thought when @lukejacksonn showed it to me :)

Closing this issue in favor of #32

@theword released v0.2.0 with servor built in! https://github.com/jakedeichert/svelvet/pull/34


Unclear why bottom-up prover is missing a possible proof (the one I've been using)

I'm mystified by a behavior of metamath-lamp. Its bottom-up prover found some proofs, but not the one I've been using. What am I missing?
Here's the background. In the lamp-guide I present this as a proof of 2p2e4, which of course works. It uses addassi and eventually 3eqtr4ri in its justifications:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopBefore","label":"2p2e4","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove that 2 + 2 = 4.","varsText":"","disjText":"","stmts":[{"label":"1","typ":"p","isGoal":false,"cont":"|- 1 e. CC","jstfText":": ax-1cn"},{"label":"2","typ":"p","isGoal":false,"cont":"|- 2 e. CC","jstfText":": 2cn"},{"label":"3","typ":"p","isGoal":false,"cont":"|- 2 = ( 1 + 1 )","jstfText":": df-2"},{"label":"4","typ":"p","isGoal":false,"cont":"|- ( 2 + 2 ) = ( 2 + ( 1 + 1 ) )","jstfText":"3 : oveq2i"},{"label":"5","typ":"p","isGoal":false,"cont":"|- 3 = ( 2 + 1 )","jstfText":": df-3"},{"label":"6","typ":"p","isGoal":false,"cont":"|- 4 = ( 3 + 1 )","jstfText":": df-4"},{"label":"7","typ":"p","isGoal":false,"cont":"|- ( 3 + 1 ) = ( ( 2 + 1 ) + 1 )","jstfText":"5 : oveq1i"},{"label":"8","typ":"p","isGoal":false,"cont":"|- 4 = ( ( 2 + 1 ) + 1 )","jstfText":"6 7 : eqtri"},{"label":"9","typ":"p","isGoal":false,"cont":"|- ( ( 2 + 1 ) + 1 ) = ( 2 + ( 1 + 1 ) )","jstfText":"2 1 1 : addassi"},{"label":"2p2e4","typ":"p","isGoal":true,"cont":"|- ( 2 + 2 ) = 4","jstfText":"9 8 4 : 3eqtr4ri"}]}

However, when I try to more aggressively automate finding the proof, the tool finds other longer proofs but somehow misses this version of the proof. If I delete the steps 1, 2, and 9 (|- 1 e. CC and |- 2 e. CC and |- ( ( 2 + 1 ) + 1 ) = ( 2 + ( 1 + 1 ) )) and remove the justification for the goal, I end up with this proof state:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopBefore","label":"2p2e4","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove that 2 + 2 = 4.","varsText":"","disjText":"","stmts":[{"label":"3","typ":"p","isGoal":false,"cont":"|- 2 = ( 1 + 1 )","jstfText":": df-2"},{"label":"4","typ":"p","isGoal":false,"cont":"|- ( 2 + 2 ) = ( 2 + ( 1 + 1 ) )","jstfText":"3 : oveq2i"},{"label":"5","typ":"p","isGoal":false,"cont":"|- 3 = ( 2 + 1 )","jstfText":": df-3"},{"label":"6","typ":"p","isGoal":false,"cont":"|- 4 = ( 3 + 1 )","jstfText":": df-4"},{"label":"7","typ":"p","isGoal":false,"cont":"|- ( 3 + 1 ) = ( ( 2 + 1 ) + 1 )","jstfText":"5 : oveq1i"},{"label":"8","typ":"p","isGoal":false,"cont":"|- 4 = ( ( 2 + 1 ) + 1 )","jstfText":"6 7 : eqtri"},{"label":"2p2e4","typ":"p","isGoal":false,"cont":"|- ( 2 + 2 ) = 4","jstfText":""}]}

I select the goal and click on "unify" to enter the bottom-up prover. I disable "Allow new disjoints" and "Allow new variables", and leave enabled "Allow new steps". I set "Statement length restriction to "Unrestricted", and the Allowed statements for both the first level and other levels is set to exactly steps 4 and 8. Search depth stays at 4. I then click on "Prove".
There are 3 pages of proofs, all of which work. E.g.:
1 [ : eqid ]	✓	|- ( 2 + 2 ) = ( 2 + 2 )
2	[ : 2cn ]	✓	|- 2 e. CC
9	[ : ax-1cn ]	✓	|- 1 e. CC
10	[2 9 9 : addassi ]	✓	|- ( ( 2 + 1 ) + 1 ) = ( 2 + ( 1 + 1 ) )
11	[4 1 10 : 3eqtr4ri ]	✓	|- ( ( 2 + 1 ) + 1 ) = ( 2 + 2 )
2p2e4	[8 11 : eqtr2i ]	✓	|- ( 2 + 2 ) = 4

However, the proof I use in my demonstration only adds 3 steps (for addassi, ax-1cn, and 2cn). It's not clear to me why the bottom-up prover can't also detect this case in its search. Is this another example where the lack of full unification is missing a case? A bug? Is it something else? Thanks!

Here's more information. When I do a bottom-up search the same way, but expressly require that the root be 3eqtr4ri, the only option presented is:
1	[ : eqid ]	✓	|- 4 = 4
2	[ : eqid ]	✓	|- ( 2 + 2 ) = ( 2 + 2 )
9	[ : 2cn ]	✓	|- 2 e. CC
10	[ : ax-1cn ]	✓	|- 1 e. CC
11	[9 10 10 : addassi ]	✓	|- ( ( 2 + 1 ) + 1 ) = ( 2 + ( 1 + 1 ) )
12	[4 2 11 : 3eqtr4i ]	✓	|- ( 2 + 2 ) = ( ( 2 + 1 ) + 1 )
2p2e4	[8 1 12 : 3eqtr4ri ]	✓	|- ( 2 + 2 ) = 4

That's a lot of eqid use. Nothing wrong with that, many people use that style, but it seems odd that it's the only option presented, even though I know there's another proof that uses fewer statements: 3eqtr4ri, addassi, ax-1cn, and 2cn.

And more information. I turned on log level 2 on the bottom-up search with the root 3eqtr4ri. It went backwards but only found two working approaches.
I looked at the failing approaches. One said:
New variables are not allowed, but one had to be created when unifying essential hypothesis #1:
1: ?
2: |- 4 = ( ( 2 + 1 ) + 1 )
3: |- ( 2 + 2 ) = ( 2 + ( 1 + 1 ) )

Allowing new variables gave more options but it still didn't lead to the same proof being an option. Which is unexpected to me.

Hi David,
mm-lamp counts length of a proof by depth of its proof tree. Two proofs may have same depth, but they may use assertions with different number of arguments. Each argument becomes a step. The different number of arguments results in different number of steps. So two proofs may have different number of steps but from mm-lamp point of view they are both of the same length.
I think this is what happens in the first part of your question. The two screenshots below demonstrate this for the two proofs:
proof-1 - the one you've started with.
proof-2 - the one you've found with bottom-up prover after removing some steps in the proof-1.
I hope this explains the first part of your question (why mm-lamp doesn't see a shorter proof).
As of the second part (why mm-lamp finds only one proof when you instruct it to use 3eqtr4ri), it requires more time for investigation, I will reply a bit later.
Proof-1:

Proof-2:

mm-lamp counts length of a proof by depth of its proof tree. Two proofs may have same depth, but they may use assertions with different number of arguments. Each argument becomes a step. The different number of arguments results in different number of steps. So two proofs may have different number of steps but from mm-lamp point of view they are both of the same length.

Sure, I was expecting that. But the diagrams above show 2 different proofs with the same depth. (depth 7 if you count the intermediate expressions as you did above, depth 4 if you only count the justifications). Shouldn't they both show up?

depth 7 if you count the intermediate expressions as you did above, depth 4 if you only count the justifications

You are right, I mistakenly included extra steps, correct length is 4.
And yes indeed your initial proof is not showing up in the bottom-up results. At the moment I don't understand why. I need more time for analysis.

I think you are right and this is a bug. My idea (I have to verify it yet) that specifying that you want to use steps 4 and 8 should be enough to find the required substitution for 3eqtr4ri. But mm-lamp matches steps with the assertion hypotheses in not the most efficient way. The most efficient way would be to match the second essential hypothesis with the step 8, and then match the third essential hypothesis with the step 4. In that case all the variables of the assertion are bound to correct subexpressions. But mm-lamp begins matching with the first essential hypotheses. This leads to the error you pointed out "New variables are not allowed, but one had to be created when unifying essential hypothesis # 1:".
I am almost sure this is the root cause. But in this case I am impressed how all your comments are precise in trying to help me to find the root cause :)

The most efficient way would be to match the second essential hypothesis with the step 8, and then match the third essential hypothesis with the step 4. In that case all the variables of the assertion are bound to correct subexpressions. But mm-lamp begins matching with the first essential hypothesis.

It sounds like the problem is that the tool should be trying all possibilities (all permutations) & it's only trying one. Basically, it sounds like it's missing an iteration. If that's correct, then adding the iteration may slow down the search (if it has to go to the same depth) but it would make useful results more likely :-).
It makes sense why testing would miss this, if that's the problem. If the test case tries the correct match first, it would work just fine. You have to use a test case where the first-tried hypothesis doesn't work. What's more, all the individual returned results would be correct, the problem is that the returned results would be incomplete.

This bug is fixed on dev. It works fine for me for the example from this issue. I have not checked other cases, but all the integration tests pass. Please check how it works for you.
The root cause was exactly as I described.
I think mm-lamp tries all possible permutations. But this is not enough. Actually the result also depends on in which order mm-lamp matches each permutation.
In the fix, I changed this order. Previously used order was not very efficient. Now, I think, it's more efficient. Effectively, I removed some possibilities from being considered and added others. This doesn't change much overall number of possibilities being checked. So it should not affect performance. I think that majority (if not all) of the removed possibilities were useless, and all the added possibilities are useful. So I expect better automated proof-finding after this fix, exactly as you predicted :)
After this fix, you may achieve the desired result with the below steps (after removing 1, 2, and 9 steps in the editor):

Select the goal and click on "unify" to enter the bottom-up prover.
Disable "Allow new disjoints" and "Allow new variables", and leave enabled "Allow new steps".
Leave "Statement length restriction" as "Less".
Set the Allowed statements for the first level to exactly steps 4 and 8. Leave "None" for "other levels".
Search depth stays at 4.
Click on "Prove".

The proof which uses 3eqtr4ri, addassi, ax-1cn and 2cn will be found.
You also may skip step 4 in the instruction above (set "Allowed statements first level" = All). The proof will be found, but it will take more time.
I will test dev environment during one or two days, and then I will release it.

This bug is fixed on dev. It works fine for me for the example from this issue.

Wonderful!! Thank you so much.

I have not checked other cases, but all the integration tests pass. Please check how it works for you.

I will. The obvious way is to try other steps in various proofs and see if they can now be found.
I have high hopes that this change will make its automation far more effective without any special casing. Which would be great. In the long run I think it will need some special automation, and someday a programming language, but being able to do much without those is excellent.

I will test dev environment during one or two days, and then I will release it.

Will this be version 12, silently another 11, or 11.0.1? Asking for a friend :-).

I tried syl in "easy mode" - that continues to work: https://lamp-guide.metamath.org/#easy-proof-of-syl
I tried proving syl in "hard mode" (axioms only per https://lamp-guide.metamath.org/#hard-mode-proving-syl-using-only-axioms.
I first tried in super-hard-mode with no intermediate steps to help it. I then tried a bottom-up proof for the final qed step. All steps allowed at all levels, statement length unrestricted, anything allowed. It did not find it (to be fair it didn't before either). Shouldn't it find it? It's less than depth 4. It does identify ax-mp as a possible first step backwards, with the right pattern, but doesn't manage to complete it. Here's what it found:
3		?	|- &W1
4		?	|- ( &W1 -> ( ph -> ch ) )
qed	[3 4 : ax-mp ]	?	|- ( ph -> ch )

Here is the setup I used:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopAfter","label":"ax-3","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove syl.","varsText":"","disjText":"","stmts":[{"label":"1","typ":"e","isGoal":false,"cont":"|- ( ph -> ps )","jstfText":""},{"label":"2","typ":"e","isGoal":false,"cont":"|- ( ps -> ch )","jstfText":""},{"label":"qed","typ":"p","isGoal":true,"cont":"|- ( ph -> ch )","jstfText":""}]}

That didn't work, so I gave it an intermediate step to use (as described in the tutorial). Here's my new setup:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopAfter","label":"ax-3","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove syl.","varsText":"","disjText":"","stmts":[{"label":"1","typ":"e","isGoal":false,"cont":"|- ( ph -> ps )","jstfText":""},{"label":"2","typ":"e","isGoal":false,"cont":"|- ( ps -> ch )","jstfText":""},{"label":"3","typ":"p","isGoal":false,"cont":"|- ( ( ph -> ps ) -> ( ph -> ch ) )","jstfText":""},{"label":"qed","typ":"p","isGoal":false,"cont":"|- ( ph -> ch )","jstfText":""}]}

Bottom-up proving on either the goal or step before the goal doesn't find the proof, even with Unrestricted & using all steps.
I to go now. Thoughts? Is this expected behavior?

Will this be version 12, silently another 11, or 11.0.1? Asking for a friend :-).

This will be version 12 :) I plan to never silently update existing versions because of the caching issue I described here https://github.com/metamath/lamp-guide/issues/78#issuecomment-1613776103   As of 11.0.1, I still think that just increasing version by 1 will be sufficient.

Is this expected behavior?

I need more time to understand what's going on. But if you are reading this and can reply, could you please confirm that you found an example which worked before the fix and doesn't work after the fix? Or you are describing something new? Because this fix will not drastically increase power of the prover. I think the increase is relatively small.

could you please confirm that you found an example which worked before the fix and doesn't work after the fix? Or you are describing something new? Because this fix will not drastically increase power of the prover. I think the increase is relatively small.

The super-hard-mode test did not work before, and it doesn't work now, so this is unchanged behavior.  Still, I'd like to understand this behavior. I think I do, but I'd like to confirm.
In this case, the bottom-up prover working from the goal won't find a full solution, but it will find this:
4		?	|- &W1
5		?	|- ( &W1 -> ( ph -> ch ) )
qed	[4 5 : ax-mp ]	?	|- ( ph -> ch )

It should be able to eventually backtrack to find a match, because the work variable &W1 has the right type. However, I think the problem is that the work variable &W1 is in multiple places and we're doing matching not full unification. Therefore, if it unified &W1 the tool would have to propagate the match, but since it can't do that it refuses the match. Is that correct?

BTW, here's a final proof. Backwards from the goal it's only depth 3, and there are few axioms/theorems to try so a backwards search should find it easily. Again, I think it's because the bottom-up prover can't do full unification of work variables that occur in multiple places, but I'd like confirmation (or clarification if I misunderstood what it's doing:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopBefore","label":"ax-3","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove syl.","varsText":"","disjText":"","stmts":[{"label":"syl.1","typ":"e","isGoal":false,"cont":"|- ( ph -> ps )","jstfText":""},{"label":"syl.2","typ":"e","isGoal":false,"cont":"|- ( ps -> ch )","jstfText":""},{"label":"3","typ":"p","isGoal":false,"cont":"|- ( ( ps -> ch ) -> ( ph -> ( ps -> ch ) ) )","jstfText":": ax-1"},{"label":"4","typ":"p","isGoal":false,"cont":"|- ( ( ph -> ( ps -> ch ) ) -> ( ( ph -> ps ) -> ( ph -> ch ) ) )","jstfText":": ax-2"},{"label":"2","typ":"p","isGoal":false,"cont":"|- ( ph -> ( ps -> ch ) )","jstfText":"syl.2 3 : ax-mp"},{"label":"1","typ":"p","isGoal":false,"cont":"|- ( ( ph -> ps ) -> ( ph -> ch ) )","jstfText":"2 4 : ax-mp"},{"label":"syl","typ":"p","isGoal":true,"cont":"|- ( ph -> ch )","jstfText":"syl.1 1 : ax-mp"}]}

Hi David,
Yes, for all the cases you mentioned as those which could not be proved by the bottom-up prover the reason is that full unification is not implemented. However, for one case I doubt it will become "bottom-up provable" even after the full unification is implemented. I mean this case:

And the corresponding JSON:
{"srcs":[{"typ":"Web","fileName":"","url":"https://us.metamath.org/metamath/set.mm","readInstr":"StopAfter","label":"ax-3","resetNestingLevel":true,"allLabels":[]}],"descr":"Prove syl.","varsText":"","disjText":"","stmts":[{"label":"1","typ":"e","isGoal":false,"cont":"|- ( ph -> ps )","jstfText":""},{"label":"2","typ":"e","isGoal":false,"cont":"|- ( ps -> ch )","jstfText":""},{"label":"qed","typ":"p","isGoal":true,"cont":"|- ( ph -> ch )","jstfText":""}]}

Is mmj2 able to prove it automatically? (I need some time to set it up, but if you use mmj2 often that may be easy for you to check; if not, then please don't mind, I'll check it myself). If mmj2 is able to prove it, then do you know if it uses some heuristics or full unification only is enough to prove this?

In this case, the bottom-up prover working from the goal won't find a full solution, but it will find this:
4		?	|- &W1
5		?	|- ( &W1 -> ( ph -> ch ) )
qed	[4 5 : ax-mp ]	?	|- ( ph -> ch )

It should be able to eventually backtrack to find a match, because the work variable &W1 has the right type. However, I think the problem is that the work variable &W1 is in multiple places and we're doing matching not full unification. Therefore, if it unified &W1 the tool would have to propagate the match, but since it can't do that it refuses  the match. Is that correct?

Currently, mm-lamp can find "what to place instead of variables in assertions". It cannot do the same for expressions (i.e. "what to place instead of variables in steps"). |- ( &W1 -> ( ph -> ch ) ) is a step, and &W1 is a variable in a step, so mm-lamp doesn't attempt to find "what to put instead of &W1". I plan to implement "what to place instead of variables in steps" but only for the very first level, i.e. when the root assertion gets applied to the step to prove. Implementing this for further levels might be very complex. I will check it more deeply, of course, but for now I feel like I will have to rewrite a lot of code (all the prover logic), and I don't have time for this. That's why I doubt that full unification will be able to solve this particular issue with &W1.
I have already released this fix to "prod" https://expln.github.io/lamp/v12/index.html Please confirm this issue may be closed. (I mentioned one of the comments in another relevant issue for not to forget it - https://github.com/expln/metamath-lamp/issues/77#issuecomment-1616826010 )

is mmj2 able to prove this automatically?

No, though mmj2 doesn't have exactly the same capability as
"bottom-up prover" either.
mmj2 has a different approach.
It has some built-in automations, some used automatically & some
you have to say "okay to try" using "!".
You can't ask it to fill in arbitrary depths, it only goes depth 1 and then
tries to use various built-in rules to try our further depths
(which results in fast results when it works, and no results when it doesn't).
The closest equivalent would be this, and it can't fully automate this:
$( <MM> <PROOF_ASST> THEOREM=syllogism LOC_AFTER=ax-3
hd1::syllogism.1 |- ( ph -> ps )
hd2::syllogism.2 |- ( ps -> ch )
!qed::         |- ( ph -> ch )
$)

If you give mmj2, it will fill in a little:
$( <MM> <PROOF_ASST> THEOREM=syllogism LOC_AFTER=ax-3
hd1::syllogism.1 |- ( ph -> ps )
hd2::syllogism.2 |- ( ps -> ch )
!              |- ( ( ph -> ps ) -> ( ph -> ch ) )
!qed::         |- ( ph -> ch )
$)

Here's what it generates in this case (it's looking for me to fill in a "d1" label):
$( <MM> <PROOF_ASST> THEOREM=syllogism LOC_AFTER=ax-3
hd1::syllogism.1 |- ( ph -> ps )
hd2::syllogism.2 |- ( ps -> ch )
!d3::          |- ( ( ph -> ps ) -> ( ph -> ch ) )
qed:d1,d3:ax-mp |- ( ph -> ch )
$)

mmj2 can do this automatically:
$( <MM> <PROOF_ASST> THEOREM=syllogism LOC_AFTER=
h              |- ( ph -> ps )
h              |- ( ps -> ch )
!              |- ( ph -> ( ps -> ch ) )
!              |- ( ( ph -> ps ) -> ( ph -> ch ) )
!qed           |- ( ph -> ch )
$)

Resulting in:
$( <MM> <PROOF_ASST> THEOREM=syllogism LOC_AFTER=
hd1::syllogism.1 |- ( ph -> ps )
hd2::syllogism.2 |- ( ps -> ch )
d3:d2:a1i      |- ( ph -> ( ps -> ch ) )
d4:d3:a2i      |- ( ( ph -> ps ) -> ( ph -> ch ) )
qed:d1,d4:ax-mp |- ( ph -> ch )
$=  ( syllogism.1 syllogism.2 wi a1i a2i ax-mp ) ABFACFDABCBCFAEGHI $.
$)

Thank you for this useful update. I will compare it to how mm-lamp works when the full unification is implemented.
I am closing this issue since the original problem is resolved. Please feel free to re-open this issue if you think there is still something to be handled.


Vite & elm-spa recursive error during development

My package.json scripts are defined as follows:
"scripts": {
    "start": "npm install && npm run dev",
    "dev": "concurrently \"elm-spa watch\" \"vite --config vite.config.js\"",
    "build": "elm-spa gen && vite build"
  },

My package.json dependencies are:
  "devDependencies": {
    "@tailwindcss/forms": "^0.3.2",
    "@tailwindcss/typography": "^0.4.0",
    "autoprefixer": "^10.2.5",
    "concurrently": "^6.3.0",
    "elm": "^0.19.1-5",
    "elm-analyse": "^0.16.5",
    "elm-format": "^0.8.5",
    "elm-spa": "^6.0.4",
    "elm-test": "^0.19.1-revision6",
    "tailwindcss": "^2.2.15",
    "trix": "^1.3.1",
    "vite": "^2.6.7",
    "vite-plugin-elm": "^2.5.0"
  }

While running in dev, my terminal is being flooded with errors message each time I update an .elm file. Here is a reduced sample of the errors:
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Model.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Model.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at runMicrotasks (<anonymous>)
[1]       at processTicksAndRejections (node:internal/process/task_queues:96:5)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Model.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Model.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at runMicrotasks (<anonymous>)
[1]       at processTicksAndRejections (node:internal/process/task_queues:96:5)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29) (x2)
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Msg.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Msg.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Msg.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Msg.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29) (x2)
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Pages.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Pages.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:34 PM [vite] Internal server error: /.elm-spa/generated/Gen/Pages.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Pages.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29) (x2)
[1] 1:43:35 PM [vite] Internal server error: /.elm-spa/defaults/Pages/NotFound.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/defaults/Pages/NotFound.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:35 PM [vite] Internal server error: /.elm-spa/generated/Page.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Page.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:36 PM [vite] Internal server error: /.elm-spa/generated/Gen/Model.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Model.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:36 PM [vite] Internal server error: /.elm-spa/generated/Gen/Msg.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Msg.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:37 PM [vite] Internal server error: /.elm-spa/generated/Page.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Page.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:37 PM [vite] Internal server error: /.elm-spa/generated/Gen/Pages.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Pages.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)
[1] 1:43:37 PM [vite] Internal server error: /.elm-spa/generated/Gen/Pages.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/generated/Gen/Pages.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29) (x2)
[1] 1:43:37 PM [vite] Internal server error: /.elm-spa/defaults/Effect.elm: NO MAIN .elm file is requested to transform by vite. Probably, this file is just a depending module
[1]   Plugin: vite-plugin-elm
[1]   File: /Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/.elm-spa/defaults/Effect.elm
[1]       at formatError (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42190:46)
[1]       at TransformContext.error (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42186:19)
[1]       at Object.transform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:42400:25)
[1]       at async doTransform (/Users/<redacted>/Projects/src/github.com/fluidgalleries/core-console/node_modules/vite/dist/node/chunks/dep-713b45e1.js:56738:29)

The errors will continue for some time (4 secs+), until the errors stop, leaving the app sometimes in a correctly updated state, or in a malformed state. If I kill the dev process and restart , the first build will work fine, but then further elm file updates will continue spewing errors.
These errors do not occur during production build (npm run build)
I'm not 100% certain, but I believe this may have only started occurring after I ejected my Main.elm file.
Any assistance would be appreciated, as my productivity has slowed to a crawl. Thank you!

I got more or less the same issue when trying to upgrade Vite from v2.4.4 -> v2.6.14.
Reverting Vite back down to v2.4.4 appears to have fixed it again.

Same issue when testing Vite v2.5.1         , should probably mention that I'm running vite-plugin-elm 2.5.1


When shouldAdvanceTime: true and doing some synchronous work, time should still pass

We understand you have a problem and are in a hurry, but please provide us with some info to make it much more likely for your issue to be understood, worked on and resolved quickly.

FakeTimers version : 9.1.0
Environment : macOS Moterey 12.2.1
Example URL :
Other libraries you are using: tap

What did you expect to happen?
Time should still pass even when doing synchronous work
What actually happens
time is not updating
How to reproduce
Added test case in #423

Never mind:

Please note that this is achieved using the original setImmediate() API

It stated at the docs how it's implemented which means setImmediate won't be called when sync code is running because of how the event loop works...


2.x.x http2 idle state (version 1)

I've implemented HTTP2 idle state using the IdleStateHandler and custom HTTP2 stream open and close events.
The idea being you shutdown when there are no open streams (it is up to the open streams to handle idle state) and an read idle event has been triggered.
The standard HTTP2 events are not generated by the channel handlers created by configureAsyncHTTPServerPipeline so I have to create custom events and pass them back to the channel as outbound events to say when streams open and close..
An alternative method can be found in #371

closed in favour of #601


split tests for null_pool() into top-level tests

Codecov Report

Merging #23 (da64df3) into master (3179239) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         3    +2
  Lines          458       470   +12
=========================================
+ Hits           458       470   +12

Impacted Files
Coverage Δ

tests/test_dbver.py
100.00% <ø> (ø)

tests/conftest.py
100.00% <100.00%> (ø)

tests/test_null_pool.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add installation from oci helm

Since we have released a oci image for helm chart. We can add a guide to help users install kmesh without clone the code repo

https://github.com/orgs/kmesh-net/packages/container/package/kmesh-helm

hey @hzxuzhonghu  can you assign this issue to me

Hello! I noticed that we need to add installation instructions for the OCI Helm chart to the documentation. Here’s a draft of the steps I suggest:
Log in to the OCI registry:
 helm registry login ghcr.io

**Pull the helm chart:**
```bash
helm chart pull ghcr.io/kmesh-net/kmesh-helm:v0.5.0

**Export the chart:**
```bash
helm chart export ghcr.io/kmesh-net/kmesh-helm:v0.5.0

**Install the chart:**
```bash
helm install kmesh-release ./kmesh-helm

**please let me know if this looks good or if there are any other details we should add**

Hello! I noticed that we need to add installation instructions for the OCI Helm chart to the documentation. Here’s a draft of the steps I suggest:
Log in to the OCI registry:
 helm registry login ghcr.io
Pull the helm chart:
helm chart pull ghcr.io/kmesh-net/kmesh-helm:v0.5.0
Export the chart:
helm chart export ghcr.io/kmesh-net/kmesh-helm:v0.5.0
Install the chart:
helm install kmesh-release ./kmesh-helm
All the commands are in Bash
please let me know if this looks good or if there are any other details we should add

I guess login0 is not a must
and we can also use one cmd helm install  kmesh --version v0.5.0 oci://ghcr.io/kmesh-net/kmesh-helm -n kmesh-system

yeah it is making it more clear that login is unnecessary in this case

@hzxuzhonghu hey i have mailed you on your mail. Please do have a look on it.

@hzxuzhonghu hey i have mailed you on you're mail. Please do have a look on it.
what do you mean? i haven't received anything


Just want to clarify

Running pods on the node are scheduled on other nodes in the cluster : Here we specially mentioned about the PODS, Is it create all other resources like secrets, certifications and configs maps ?

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

ID: a14a3f84-28b4-0a2a-4da7-47cb4d66689f
Version Independent ID: d1ffdd88-ab9a-9f55-8689-526e7415b326
Content: Kubernetes on Azure tutorial - Upgrade a cluster
Content Source: articles/aks/tutorial-kubernetes-upgrade-cluster.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@AdimUser secrets, certifications and configs maps are stored in the etcd by the kubernetes control plane. Pod configurations are also stored there.
So when control plane moves a pod to another node, It will associate the secretes, config maps to the new pods as well.

@AdimUser
I will close this out for now. If you need additional help please open a new issue


chg:dev:No issue:Create ParserFactory to get DDL/SqlQuery Parser

ParserFactory will return the DDL/SqlQuery parser based on the sql query. The factory will store SqlQueryParser state (for caching purpose) and creates new instance only if connection info changes.
Also, added attribute type in ParserResult to distinguish between DDL/SelectQuery.

You should create an issue for the PR.

Other than the point that @amoghmargoor brought up, it looks good to me. What is the motivation ? You can use ParserFactory in other places such as the Quark Service with QDS ?

@vrajat yes. I am planning to use ParserFactory in QuarkService with QDS.

OK
On Tue, May 24, 2016 at 3:12 PM adeshr<EMAIL_ADDRESS>wrote:

@vrajat https://github.com/vrajat yes. I am planning to use
ParserFactory in QuarkService with QDS.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/qubole/quark/pull/83#issuecomment-221218448


HxModal Scrolling disabled after modal closed using browser back button

I'm experiencing an issue with HxModal. When a modal is open and the user navigates away using the browser back button, scrolling on the rest of the page becomes disabled. This persists until the user refreshes the entire site.
You can experience it on the help page
https://havit.blazor.eu/components/HxModal
click open any modal and hit the browser back button

Duplicates #110, waiting for fix in Bootstrap.


[FIX] Operator: test certs fixed

Re-generate test certs for the next 10 years.
Provide doc on how to generate these.

Change-Id: I4ffe32657e8d4752f0fab69ae78e8232f7cc85fd

ty!


Altered bug fix for line from boolean (See #154)

Low-res solution for isLine boolean. Compare to #154

Could we close this?

Go on then.


Label Translation

Translate the Label Field, it is often useful, as Pages have different Labels for different Languages.

mhm, I thought the label is used like a internal identifier. like the page id. so I didn't translate it. you sure this still works?

Hi schneikai,
Yes it works and I allow blank so can fall back to translatable.
As I found there is no way to get the Page Title, I need the label to be the  translated title.
The slug n fullpath is able to get the translations of a page.
Arthur CHAN
Co-founder
Talkgoal.com
On Mar 25, 2015, 2:06 AM, at 2:06 AM, Kai Schneider<EMAIL_ADDRESS>wrote:

mhm, I thought the label is used like a internal identifier. like the
page id. so I didn't translate it. you sure this still works?

Reply to this email directly or view it on GitHub:
https://github.com/schneikai/comfortable-mexican-sofa/pull/4#issuecomment-85625739

Hi @schneikai ,
I found the Translate has a redirect field too. I wonder how it works?
Isn't the redirect should follow the translatable instead?

Hi @schneikai
I have to say I appreciate your codes! My site works with your translation codes!
http://hongkonghealth.org/
The translation label is all important, I use it for the navigation menu in the header.

I added translated labels. I didn't merge your pull request though because I had to update a couple of tests as well. Thanks anyway :)


[Snyk] Upgrade semantic-release from 19.0.4 to 19.0.5

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade semantic-release from 19.0.4 to 19.0.5.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2022-08-23.

Release notes

Package name: semantic-release

19.0.5 - 2022-08-2319.0.5 (2022-08-23)
Reverts

Revert "fix(deps): update dependency yargs to v17" (#2534) (8f07522), closes #2534 #2533

19.0.4 - 2022-08-2219.0.4 (2022-08-22)
Bug Fixes

deps: update dependency yargs to v17 (#1912) (f419080)

    from semantic-release GitHub release notes

Commit messages

Package name: semantic-release

8f07522 Revert "fix(deps): update dependency yargs to v17" (#2534)
2f4bcef docs: add semantic-release-react-native to plugin list (#2523)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Superseded by #94


grammar: can be have -> can contain

I just saw the same problem and fixed it slightly differently