[cloud_firestore]: FirebaseFirestore instanceFor working only with (default) database on Windows

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Core, Database, Storage
Which platforms are affected?
Windows
Description
My project has several databases within GCP. In the Firebase project, I can see these databases, and they are all created correctly in Native mode. On MacOS, when I try to access another database through FirebaseFirestore.instanceFor(app, databaseId ), no problems occur. Whereas on Windows I always get only the (default) database.
Reproducing the issue

Initialise Firebase in the application.
Try to use non-default database later:
FirebaseFirestore.instanceFor(    app: Firebase.apps.first,    databaseId: 'databaseName',  );

Firebase Core version
3.1.0
Flutter Version
3.22.2
Relevant Log Output
No error log. It is written to (default) database. I can't drop/modify it.

Flutter dependencies

Expand Flutter dependencies snippet

 cloud_firestore 5.0.1 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.6
- dio 5.4.2+1 [async http_parser meta path]
- ffi 2.1.2
- fhir 0.12.0 [freezed_annotation intl json_annotation uuid xml2json yaml]
- firebase_auth 5.1.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 3.1.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- fluentui_system_icons 1.1.232 [flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_animate 4.5.0 [flutter flutter_shaders]
- flutter_hooks 0.20.5 [flutter]
- flutter_local_notifications 16.3.3 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_secure_storage 9.0.0 [flutter flutter_secure_storage_linux flutter_secure_storage_macos flutter_secure_storage_platform_interface flutter_secure_storage_web flutter_secure_storage_windows meta]
- flutter_svg 2.0.10+1 [flutter http vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_windowmanager 0.2.0 [flutter]
- freezed 2.4.7 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- gap 3.0.1 [flutter]
- glass_kit 3.0.0 [flutter]
- go_router 13.2.2 [collection flutter flutter_web_plugins logging meta]
- google_fonts 6.2.1 [flutter http path_provider crypto]
- hooks_riverpod 2.5.1 [collection flutter flutter_hooks flutter_riverpod riverpod state_notifier]
- intl 0.19.0 [clock meta path]
- intl_utils 2.8.7 [analyzer archive args dart_style http intl path petitparser yaml]
- logger 2.2.0
- pdfrx 1.0.65 [collection crypto ffi flutter http path path_provider rxdart synchronized url_launcher vector_math web]
- riverpod_annotation 2.3.5 [meta riverpod]
- screen_capturer 0.2.1 [flutter screen_capturer_linux screen_capturer_macos screen_capturer_platform_interface screen_capturer_windows]
- shared_preferences 2.2.2 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sliver_tools 0.2.12 [flutter]
- url_launcher 6.2.5 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]

dev dependencies:
- build_runner 2.4.9 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_lints 2.0.3 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math leak_tracker_flutter_testing async boolean_selector characters collection leak_tracker leak_tracker_testing material_color_utilities meta source_span stream_channel string_scanner term_glyph vm_service]
- icons_launcher 2.1.7 [args image path universal_io yaml]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- pubspec_dependency_sorter 1.0.4 [logger pubspec flutter]
- riverpod_generator 2.4.0 [analyzer build build_config collection crypto meta path riverpod_analyzer_utils riverpod_annotation source_gen]
- riverpod_lint 2.3.10 [analyzer analyzer_plugin collection custom_lint_builder meta path riverpod riverpod_analyzer_utils source_span yaml]
- superlint 1.0.0

dependency overrides:
- superlint 1.0.0

transitive dependencies:
- _fe_analyzer_shared 67.0.0 [meta]
- _flutterfire_internals 1.3.37 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 6.4.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- analyzer_plugin 0.11.3 [analyzer collection dart_style pub_semver yaml]
- archive 3.4.10 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.1 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.1 [built_collection built_value crypto http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.4.2 [analyzer async build collection convert crypto graphs logging package_config path pool pub_semver stream_transform yaml]
- build_runner_core 7.3.0 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.9.1 [built_collection collection fixnum meta]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- ci 0.1.0
- cli_util 0.4.1 [meta path]
- clock 1.1.1
- cloud_firestore_platform_interface 6.2.7 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 4.0.1 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins]
- code_builder 4.10.0 [built_collection built_value collection matcher meta]
- collection 1.18.0
- convert 3.1.1 [typed_data]
- crypto 3.0.3 [typed_data]
- custom_lint 0.6.4 [analyzer analyzer_plugin args async ci cli_util collection custom_lint_core freezed_annotation json_annotation meta package_config path pub_semver pubspec_parse rxdart uuid yaml]
- custom_lint_builder 0.6.4 [analyzer analyzer_plugin collection custom_lint custom_lint_core glob hotreloader meta package_config path pubspec_parse rxdart]
- custom_lint_core 0.6.3 [analyzer analyzer_plugin collection glob matcher meta package_config path pubspec_parse source_span yaml]
- dart_style 2.3.6 [analyzer args collection path pub_semver source_span]
- dbus 0.7.10 [args ffi meta xml]
- fake_async 1.3.1 [clock collection]
- file 7.0.0 [meta path]
- firebase_auth_platform_interface 7.4.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.12.2 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser meta web]
- firebase_core_platform_interface 5.1.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.17.2 [firebase_core_platform_interface flutter flutter_web_plugins meta web]
- fixnum 1.1.0
- flutter_local_notifications_linux 4.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 7.0.0+1 [flutter plugin_platform_interface]
- flutter_riverpod 2.5.1 [collection flutter meta riverpod state_notifier]
- flutter_secure_storage_linux 1.2.0 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_macos 3.0.1 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_platform_interface 1.0.2 [flutter plugin_platform_interface]
- flutter_secure_storage_web 1.1.2 [flutter flutter_secure_storage_platform_interface flutter_web_plugins js]
- flutter_secure_storage_windows 3.0.0 [ffi flutter flutter_secure_storage_platform_interface path path_provider win32]
- flutter_shaders 0.1.2 [flutter vector_math]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math]
- frontend_server_client 4.0.0 [async path]
- glob 2.1.2 [async collection file path string_scanner]
- graphs 2.3.1 [collection]
- hotreloader 4.2.0 [collection logging path stream_transform vm_service watcher]
- http 1.2.1 [async http_parser meta web]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.1.7 [archive meta xml]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- json_annotation 4.8.1 [meta]
- leak_tracker 10.0.4 [clock collection meta path vm_service]
- leak_tracker_flutter_testing 3.0.3 [flutter leak_tracker leak_tracker_testing matcher meta]
- leak_tracker_testing 3.0.1 [leak_tracker matcher meta]
- lints 2.1.1
- logging 1.2.0
- matcher 0.12.16+1 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.8.0 [collection]
- meta 1.12.0
- mime 1.0.5
- package_config 2.1.0 [path]
- path 1.9.0
- path_parsing 1.0.1 [vector_math meta]
- path_provider 2.1.2 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- path_provider_android 2.2.2 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.2 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.2 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- petitparser 6.0.2 [meta]
- platform 3.1.4
- plugin_platform_interface 2.1.8 [meta]
- pointycastle 3.7.4 [collection convert js]
- pool 1.5.1 [async stack_trace]
- pub_semver 2.1.4 [collection meta]
- pubspec 2.3.0 [path pub_semver yaml uri]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- riverpod 2.5.1 [collection meta stack_trace state_notifier]
- riverpod_analyzer_utils 0.5.1 [analyzer collection crypto custom_lint_core freezed_annotation meta path source_span]
- rxdart 0.27.7
- screen_capturer_linux 0.2.0 [flutter screen_capturer_platform_interface shell_executor]
- screen_capturer_macos 0.2.0 [flutter screen_capturer_platform_interface shell_executor]
- screen_capturer_platform_interface 0.2.0 [flutter json_annotation plugin_platform_interface]
- screen_capturer_windows 0.2.0 [ffi flutter screen_capturer_platform_interface win32]
- shared_preferences_android 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.5 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.2 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.2 [flutter plugin_platform_interface]
- shared_preferences_web 2.3.0 [flutter flutter_web_plugins shared_preferences_platform_interface web]
- shared_preferences_windows 2.3.2 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- shell_executor 0.1.5
- sky_engine 0.0.99
- source_gen 1.5.0 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_span 1.10.0 [collection path term_glyph]
- sprintf 7.0.0
- stack_trace 1.11.1 [path]
- state_notifier 1.0.0 [meta]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- synchronized 3.1.0+1
- term_glyph 1.2.1
- test_api 0.7.0 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- timezone 0.9.2 [path]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- universal_io 2.2.2 [collection meta typed_data]
- uri 1.0.0 [matcher quiver]
- url_launcher_android 6.3.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.2.5 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.1.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.3.2 [flutter plugin_platform_interface]
- url_launcher_web 2.3.0 [flutter flutter_web_plugins url_launcher_platform_interface web]
- url_launcher_windows 3.1.1 [flutter url_launcher_platform_interface]
- uuid 4.4.0 [crypto sprintf meta fixnum]
- vector_graphics 1.1.11+1 [flutter http vector_graphics_codec]
- vector_graphics_codec 1.1.11+1
- vector_graphics_compiler 1.1.11+1 [args meta path_parsing xml vector_graphics_codec path]
- vector_math 2.1.4
- vm_service 14.2.1
- watcher 1.1.0 [async path]
- web 0.5.1
- web_socket_channel 2.4.4 [async crypto stream_channel web]
- win32 5.3.0 [ffi]
- xdg_directories 1.0.4 [meta path]
- xml 6.5.0 [collection meta petitparser]
- xml2json 6.2.3 [xml]
- yaml 3.1.2 [collection source_span string_scanner]

Additional context and comments
No response

@Yevgny - thanks for the report, we should be able to get this fixed 👍


Engine is busy

I have run the jmeter_stop.sh and if I rerun the script again its not working its just show engine is busy
Logs:
Starting the test @ Thu Apr 27 15:03:41 UTC 2023<PHONE_NUMBER>419)
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Engine is busy - please try later
Remote engines have been started
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445

023-04-27 15:13:56,220 ERROR o.a.j.e.ClientJMeterEngine: Error in rconfigure() method
java.lang.IllegalStateException: Engine is busy - please try later
at org.apache.jmeter.engine.RemoteJMeterEngineImpl.rconfigure(RemoteJMeterEngineImpl.java:144) ~[ApacheJMeter_core.jar:5.0 r1840935]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_181]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_181]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_181]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_181]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) ~[?:1.8.0_181]
at sun.rmi.transport.Transport$1.run(Transport.java:200) ~[?:1.8.0_181]
at sun.rmi.transport.Transport$1.run(Transport.java:197) ~[?:1.8.0_181]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_181]
at sun.rmi.transport.Transport.serviceCall(Transport.java:196) ~[?:1.8.0_181]
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) ~[?:1.8.0_181]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) ~[?:1.8.0_181]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) ~[?:1.8.0_181]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_181]
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) ~[?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_181]
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283) ~[?:1.8.0_181]
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260) ~[?:1.8.0_181]
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) ~[?:1.8.0_181]
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) ~[?:1.8.0_181]
at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) ~[?:1.8.0_181]
at com.sun.proxy.$Proxy19.rconfigure(Unknown Source) ~[?:?]
at org.apache.jmeter.engine.ClientJMeterEngine.runTest(ClientJMeterEngine.java:151) [ApacheJMeter_core.jar:5.0 r1840935]
at org.apache.jmeter.engine.DistributedRunner.start(DistributedRunner.java:132) [ApacheJMeter_core.jar:5.0 r1840935]
at org.apache.jmeter.engine.DistributedRunner.start(DistributedRunner.java:149) [ApacheJMeter_core.jar:5.0 r1840935]
at org.apache.jmeter.JMeter.runNonGui(JMeter.java:1071) [ApacheJMeter_core.jar:5.0 r1840935]
at org.apache.jmeter.JMeter.startNonGui(JMeter.java:973) [ApacheJMeter_core.jar:5.0 r1840935]
at org.apache.jmeter.JMeter.start(JMeter.java:555) [ApacheJMeter_core.jar:5.0 r1840935]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_181]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_181]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_181]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_181]
at org.apache.jmeter.NewDriver.main(NewDriver.java:245) [ApacheJMeter.jar:5.0 r1840935]
2023-04-27 15:13:56,221 ERROR o.a.j.u.JMeterUtils: Engine is busy - please try later
2023-04-27 15:13:56,221 INFO o.a.j.e.DistributedRunner: Remote engines have been started


Respect updated DNS SD broadcast names in TV app

When a device is advertising over dns-sd and the TX bits change (device name) a message is sent out to indicate that the old advertisement should be expired and the new one should be used.
In the current implementation of the casting app, we stop listening to updates after the discoveryDurationSeconds timeout. This causes us to miss messages and Android seems to fall back to the cached value of the DNS advertisement.
We need to change the usage pattern here so that clients stop the discovery manually after it is started and keep it active for the lifetime they need it for.
I also updated the test apps to behave a bit nicer with discovered commissioners.
Fixes #25492

Checkmark for the purposes of updating a sample app with changes and checkmarks from app owner - I have not deeply checked the logic and without a review for 1 week this probably qualifies for fast track.
Had a comment about oddness of having a hash/equals that only considers partial class data (and I can understand usage in the array adapter ... but it is odd/unexpected that if (contains) { remove(); } add is not actually a noop but rather replaces same;fkey data).
leaving up to app maintainer to decide what to do with it, I am giving the checkmark in advance.

Thanks! - To clarify the behavior, it does the contains to check if it is "effectively" equal, but in actual use there are some elements that might change on a new broadcast update (such as the broadcast name), and in those cases i still want the button updated.


Fix DLC and add padding for CANFD frames

This PR fixes the calculation of the data length code (DLC) for CANFD frames with extended data length.
The current code only returns the data length which is incorrect for frames with data length > 8 (also see: https://elearning.vector.com/mod/page/view.php?id=368)
I have currently implemented the fix so that DLC=0 is returned if the data length is invalid. I am not completely satisfied with this solution, as a check when creating a CANFD frame would probably make more sense but requires changing the CanFdFrame::init function.
Please let me know what you think about this.

I recently came across a case where I initialized and sent a CANFD frame with a payload whose length is not a valid CANFD data length. I therefore digged a little deeper and discovered that CANFD frames are also being sent with an invalid data length. Here is the example code for creating and sending a CANFD frame with an invalid DataLength (DL=11):
let sock = CanFdSocket::open("vcan0").expect("open canfd socket0");
let id = StandardId::new(0x123).expect("create CAN id");
// invalid data length (DL=11)
let data: &[u8] = &[0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xAA, 0xBB];
let flags: FdFlags = FdFlags::all();
let frame = CanFdFrame::with_flags(id, data, flags).expect("create CANFD frame");
sock.write_frame(&frame).expect("send frame");

The candump output of the (via cangw connected) vcan1 interface looks like this:
vcan1  123  [11]  11 22 33 44 55 66 77 88 99 AA BB

As you can see a invalid CANFD frame with a data length of 11 ist being transmittet.
In comparison, when sending the same frame using the following  cansend command
cansend vcan0 123##F112233445566778899AABB

the data is being correctly padded with 0 to the next valid data length (in this case 12).
vcan1  123  [12]  11 22 33 44 55 66 77 88 99 AA BB 00

I therefore updated the CanFdFrame::init and CanFdFrame::set_data functions in the last commit to correctly add padding to the data when needed.

Oh, BTW, on a closer 2nd look, I realized you don't need to manually add zero padding to the FD frame (along with the added allocation/deallocation). The creation of the underlying C variable zeros out the whole struct already, including the data field:
let mut frame = canfd_frame_default();

So all you need to do is copy in the user data, even if it's not a valid length, and then set the length to a valid value.


experimental skip npm install

Hey @osdevisnot, thanks for contributing. If I read the code correctly, this wouldn't handle anything with a transitive dependency, correct? It looks like it would correctly read each dependency from unpkg, but then if they loaded anything themselves it would 💩
Is there something that unpkg would provide that npm install isn't getting you? Is the idea just to remove the npm install step if we can?

Closing this as ROI for frontend only dependencies is not worth the tradeoffs. Also, this PR did not consider compiling transitive dependencies correctly.


make ScatterSwap hasher lazy load the spinner_map

Results below represent running this across 60K IDs
Before:
Total allocated: 1,159,998,278 bytes (11820720 objects)
Total retained:  1858 bytes (9 objects)

allocated memory by gem
-----------------------------------
1150377516  scatter_swap/lib
   ...

allocated memory by file
-----------------------------------
1145577276  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb
   ...

allocated memory by location
-----------------------------------
 528026400  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:33
 311655582  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:9
 163208160  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:32
  68283414  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:27
  19200960  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:58
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:41
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:48
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:8
  12000600  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:67
   ...

After:
Total allocated: 1,043,832,510 bytes (10500655 objects)
Total retained:  1778 bytes (7 objects)

allocated memory by gem
-----------------------------------
1034211708  scatter_swap/lib
  ...

allocated memory by file
-----------------------------------
1034211708  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb
   ...

allocated memory by location
-----------------------------------
 311655582  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:100
 240012000  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:32
 195849792  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:31
 144007200  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:34
  68283414  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:24
  19200960  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:70
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:48
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:57
  14400720  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:99
  12000600  /Users/connor/dev/scatter_swap/lib/scatter_swap/hasher.rb:82
  ...

Apologies about this. I had intended to submit this PR on our own fork.


CNDB-10732: Reproduction tests and fixes for CNDB-10732 and CNDB-10535

What is the issue
The issue is that we assert the presence of the indexes at the boundary of the query being handled, and then the QueryController assumes these won't change. Two cases were identified:

one where we use assertions that might not even be enabled in prod environments.
another one where the precondition actually is doing what it is expected but it does not give enough information.

What does this PR fix and why was it fixed
Added reproduction tests for both cases identified. Fix by adding UnsupportedExceptions, though I am not sure whether we won't prefer preconditions with improved messages for both places. Open to suggestions and to hear other people opinion.
Current CI looks good to me but there is issue with building artifacts today, thus I do not have CNDB PR to upgrade the CC version. Though I think in the meantime the PR can be reviewed already.
Checklist before you submit for review

[ ] Make sure there is a PR in the CNDB project updating the Converged Cassandra version
[ ] Use NoSpamLogger for log lines that may appear frequently in the logs
[ x] Verify test results on Butler
[ x] Test coverage for new/modified code is > 80%
[ x] Proper code formatting
[ x] Proper title for each commit staring with the project-issue number, like CNDB-1234
[ x] Each commit has a meaningful description
[ x] Each commit is not very long and contains related changes
[ ] Renames, moves and reformatting are in distinct commits

Oh I just realized I missed this comment - https://github.com/datastax/cassandra/pull/1423/files#r1850397603
On it...

Checked CI, nothing new exposed.  This seems ready for another round of review

CI LGTM, some leaks have. been detected, but we have also seen this lately in other tests,er exception handling here is highly unlikely to trigger it.
I will create the other repo PR and post it on the issue.


When I use whisper.cpp, it took me 1160 milliseconds to transcribe a 27-second .wav file. However, when I used this package, it took me 11538 milliseconds. I only change link package.

It's recommended to use the SPM package from the main whisper.cpp repo.


Error on generating video larger than 512,512.

I installed the FreeInit-hf code locally, it runs perfect on 512,512. Then I set the size at 512,768, here is the error:
Traceback (most recent call last):
File "F:\FreeInit-hf-main\venv\lib\site-packages\gradio\routes.py", line 488, in run_predict
output = await app.get_blocks().process_api(
File "F:\FreeInit-hf-main\venv\lib\site-packages\gradio\blocks.py", line 1431, in process_api
result = await self.call_function(
File "F:\FreeInit-hf-main\venv\lib\site-packages\gradio\blocks.py", line 1103, in call_function
prediction = await anyio.to_thread.run_sync(
File "F:\FreeInit-hf-main\venv\lib\site-packages\anyio\to_thread.py", line 33, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "F:\FreeInit-hf-main\venv\lib\site-packages\anyio_backends_asyncio.py", line 877, in run_sync_in_worker_thread
return await future
File "F:\FreeInit-hf-main\venv\lib\site-packages\anyio_backends_asyncio.py", line 807, in run
result = context.run(func, *args)
File "F:\FreeInit-hf-main\venv\lib\site-packages\gradio\utils.py", line 707, in wrapper
response = f(*args, **kwargs)
File "F:\FreeInit-hf-main\app.py", line 287, in animate
sample_output = pipeline(
File "F:\FreeInit-hf-main\venv\lib\site-packages\torch\autograd\grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "F:\FreeInit-hf-main\animatediff\pipelines\pipeline_animation.py", line 590, in call
latents = freq_mix_3d(z_T.to(dtype=torch.float32), z_rand, LPF=self.freq_filter)
File "F:\FreeInit-hf-main\animatediff\utils\freeinit_utils.py", line 24, in freq_mix_3d
x_freq_low = x_freq * LPF
RuntimeError: The size of tensor a (96) must match the size of tensor b (64) at non-singleton dimension 3
**I think the problem is at the LPF part, I print out the shape of x_freq and LPF. x_freq: torch.Size([1, 4, 16, 96, 64]) , LPF: torch.Size([1, 4, 16, 64, 64]), since the generation size is 512,768 the latent size should be 96,64. Please check the code of LPF. Thanks a lot **

The bug comes from app.py. the update_filter fail to update the data comes from gr. By delecting the code it works well. And also it need to change the order of height_slider and width_slider of update_filter.
这个bug应该是app.py中的update_filter出问题导致的.我将中间几行代码注释掉,然后调整了height_slider, width_slider的顺序,可以成功输出512,768甚至512,1024了,可以看一下.
# self.set_width = width_slider
# self.set_height = height_slider
# self.selected_filter_type = filter_type_dropdown
# self.set_d_s = d_s
# self.set_d_t = d_t
if self.set_width != width_slider or self.set_height != height_slider or self.selected_filter_type != filter_type_dropdown or self.set_d_s != d_s or self.set_d_t != d_t:
self.update_filter(height_slider, width_slider , filter_type_dropdown, d_s, d_t)

@drnighthan The resolution bug has been fixed. Thanks for your feedback!


Import instances from VMware into a KVM cluster fails

ISSUE TYPE

Bug Report

COMPONENT NAME

VM import

CLOUDSTACK VERSION

cloudstack-management-<IP_ADDRESS>-SNAPSHOT.20240109

CONFIGURATION

OS / ENVIRONMENT

Rocky 8 KVM
SUMMARY

After the virt-v2v has converted the VMware VM, management server fails the VM import operation into KVM with the below error:
2024-01-09 07:32:18,036 ERROR [o.a.c.v.UnmanagedVMsManagerImpl] (API-Job-Executor-3:ctx-5f472c22 job-56 ctx-71211ae9) (logid:d2274e91) Error importing VM: Unable to look up template by id 202
com.cloud.exception.InvalidParameterValueException: Unable to look up template by id 202
        at com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:4478)
        at com.cloud.vm.UserVmManagerImpl.importVM(UserVmManagerImpl.java:8230)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

STEPS TO REPRODUCE

1. Add an existing VMware DC with VMs to a zone with KVM cluster.
2. Import an unamanaged instance from VMware to KVM.

Marking this for 4.19.0 milestone as it is a bug with one of the major new features.
This seems similar to https://github.com/apache/cloudstack/issues/8432
I guess we need to either remove https://github.com/apache/cloudstack/blob/main/server/src/main/java/org/apache/cloudstack/vm/UnmanagedVMsManagerImpl.java#L1114-L1116 or refactor the check to prevent further issues.
@nvazquez

@nvazquez , might this be the same issue as https://github.com/apache/cloudstack/pull/8433#issuecomment-1878475879 , not being able to add a VM due to root disk size being to small?


Feature request: custom view value for select and autocomplete

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
Select and Autocomplete allow custom view values, for example:
https://material.io/guidelines/components/menus.html#menus-usage

This Menu allows icons in addition to text.
I understand the example is a Menu not Select or Autocomplete, but they are under the same category in Material Design
What is the current behavior?
The values are limited to strings, and doesn't allow custom layout inside the Select and Autocomplete dropdown.
What is the use-case or motivation for changing an existing behavior?
As per the example screenshot.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material 2.0.0-beta.6

Have you try something like:

    text to the left

text to the right

In the autocomplete md-option? It works with text. Maybe it works with icons to (material fonts of fontawesome).

Take a look at this plunker: https://plnkr.co/edit/v3EoZp?p=preview

@julianobrasil that looks great thanks!
However I accidentally noticed that your code doesn't work on Firefox 53.0.3
Can you raise a bug for that?
Thanks!

I think it's an issue with nested divs in Firefox. I modified the plunker. This will work both in Chrome, Firefox, Edge and IE:

{{ state }}

            add_location
            {{state}}

Closing this since I believe it's doable today (it would just be your mat-option template). Free free to open another issue if that's not the case.


Inputs to TensorFlow serving REST API

I have build a seq2seq model by referring to this tutorial.
https://keras.io/examples/nlp/lstm_seq2seq/
After training the model, instead of saving the model directly, I saved the encoder_model and decoder_model separately.I'm using TensorFlow serving to deploy these two models.
Encoder model input was a numpy array of length 1, so I converted that to JSON to pass it to REST API. This worked and I got the desired result.
But, for decoder this method didn't worked as length of decoder_input is 3 and data_type is numpy array.
Following the block of decode_sequence function where decoder_model is called.
dec_model_url = "http://localhost:8400/v1/models/dec_model:predict"
headers = {
    'content-type': "application/json;charset=UTF-8'",
    'cache-control': "no-cache",
    'Accept':'application/json'
    }
    while not stop_condition:
        decoder_ip = ([target_seq] + states_value)
        target_seq1 = target_seq.tolist()
        target_seq1=[target_seq1]

        states_value1 = states_value
        states_value1[0] = states_value1[0].tolist()
        states_value1[1] = states_value1[1].tolist()

        decoder_ip1 = (target_seq1 + states_value1[0] + states_value1[1])
        start_main = '{"instances":'
        end_main = '}'
        decoder_ip1 = start_main + str(decoder_ip1) +end_main

        output_tokens, h = requests.request("POST", dec_model_url, data=decoder_ip1, headers=headers)

When I run this, I got the following error.

{"error": "instances is a plain list, but expecting list of objects as multiple input tensors required as per tensorinfo_map'

What is the correct way to pass the decoder_model inputs with REST API?

Hi @VallabhMahajan1 ,
Could you please check the attached resources 1, 2 & 3 and let us know if it helps.
Thankyou!


Fix issue with parsing Project jsons

Hi @matteocrippa !
Today I've opened Aswesome Swift app and it doesn't show anything. I've fixed issue with JSON parsing in this PR. Also, I've updated Xcode settings for v 9.4.1, and update cocoa pods version.

@serhii-londar thx
Yep the project is a bit outdated


Filtering resource group collection supports filtering only on tags

Please update the docs for operation ResourceGroups_List that the filter parameter supports filtering on tags only.
Related: https://github.com/Azure/azure-sdk-for-go/issues/2480

Any update on this @jhendrixMSFT ?

@chidmdxx can you please follow up on this?

This has been updated in our most recent API version (2021-04-01); therefore, this issue will be closed now.


GPII-4176: escaping console.log in JS wrapper for JSON content.

https://issues.gpii.net/browse/GPII-4176

@the-t-in-rtf would you be able to review this PR?

@jobara, good catch.  I'd like to pair this with the long-standing open pull to add console.log to eslint-config-fluid, and to review/merge this after that one, so that we're also testing your small change here with the updated defaults.
cc: @amb26

@the-t-in-rtf I've updated the PR to use eslint-config-fluid v1.4.0 and fixed issues with console.log as well.

@the-t-in-rtf I'm closing this PR now that https://github.com/GPII/gpii-grunt-lint-all/commit/89c9c99349d9141d86b66765322815efea92a7e6 has resolved this issue. Can you please publish a new release of this package though, as the places that use eslint-config-fluid v1.4.0 with this will fail due to the bug in earlier versions.

Sorry, @jobara, totally missed this.  There is a dev release with the changes here:
1.0.6-dev.20191126T114627Z.377dbc8.GPII-4246
We are working on one more change (removing JSONlint in favour of our own custom task), I plan to cut a full release once that's done.

@the-t-in-rtf sounds good and thanks for the dev release.

@jobara, I finished the other work, the full 1.0.6 release is out now.

excellent, thanks :)


Title changed for Drink Water Reminder project

🛠 Issue (#1470)

Closes #1470
Description
Changed title for Drink Water Reminder project.
Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

@zugzwang03 / @harshit-paneri please approve my pull request.


Distingish button for locationAlways and locationWhenInUse

Hi,
is there a possibility to change the text for button "Enable Location" in case of locationAlways to "Enable Location Always"?
Otherwise users will be confused, because they do not know which of the Location Options are required to grant.
Thanks,
Ghent

Good day! Soon the release of a new version, you should study it when it comes out.


ProjectSettings: Fix description of physics jitter

Did someone just copy-pasted the line and forgot to change or what?

Thanks!

It's a minor typo, so I'm removing the cherrypick label.


Beca ZHT002: Added current temperature diagnostic

Added datapoint for current temperature (for use with custom thermostat cards)

There is already a climate entity with the current temperature embedded.


Basic scholarships, need to figure out a way to narrow down results

@divad12 Here's the branch I've been working on. If you pull and run locally you'll notice there's a lot of scholarships, so I'll have to try and narrow it down further.

Cool! Thanks for working on this.
I haven't pulled and run locally, but if you put up some screenshots I'll leave feedback. :)

So I'm still working out the expanded view, but here's a screenshot to give you an idea of how many there can be for one user. (This is about half of the ones on my profile screen) Hence the need (I think) to narrow down the results further than just program.

Ooh yeah, that's a lot to look through. I remember applying for some of these. :)
How many are there in total (looks like there were some cut off in the screenshot)? If there were just those 11, I'd be ok with reading through each of these, especially if I were eligible for most of them and can just submit one application (maybe with modifications) to most of these.
How are you filtering results so far? By faculty (eg. Engineering) or program (eg. Mechatronics)? If you wanted to filter by more than just program, what else can you filter by (supposing we had the data)? Year? Marks?

There are around 25 of them I believe, so I don't want to make people read through all of them. Currently I'm filtering by program only, but it looks like we can search by other parameters as well. For example, each scholarship has a field called enrollment_year, which follows the pattern of Year (One | Two | Three | Four). There are also fields for citizenship, and eligibility. Eligibility is interesting, as it's a combination of other fields, and also includes a minimum average needed, if one exists.
I think if we were to make a one-time form where they can fill out the extra data, we could provide much more accurate results, making the entire process optional and giving the best results with the data we have. I'd also provide a "this doesn't apply to me" option for each scholarship, but ideally each user only has to use it < 5 times, rather than potentially 15 like I would currently.
I also think it'd be good to write a function that takes a scholarship and a person's info and determines if they're eligible for it, returning a Boolean. Then I could take ~10 scholarships from the API, and write some unit tests to see how accurate we can categorize them. Definitely feeling some testing on this one, if we aim to narrow down the results.

So, 25 scholarships is a lot to look through, but if I'm eligible 2/5 of them, then I wouldn't mind. And if there was a "x" button that would hide those scholarships indefinitely (maybe there could be a "show hidden" button), then I don't think that's too bad.
A form to filter even more could be nice, but I'm not sure if it's worth the effort of either you coding that up (along with associated UI) or the user filling it out to filter out just a few scholarships.
I think it will suffice to start with just what you have plus the "x" button (for "this doesn't apply to me"). Launch that as an MVP and we can consider adding additional filtering.
And tests++

What did you have in mind for the "hide" component? I'm alternating between having it next to the title, or in the expanded area of the scholarship. I've attached a screenshot of what I have so far, feel free to leave feedback. I agree, let's ship the MVP and then can discuss better searching. I think after I add the dismiss functionality it should be pretty close.

I think you can have it in the expanded area, sort of like our "remove from profile" button:

... and you can also have it to the side of the bar on hover:

If you implement just one, go with the first, because it's more clear what it does and not having it on hover allows it to be mobile-friendly (not that our site is mobile-friendly at all, lol).
With the UI, I think you can just re-use the course bar UI where there's no gap between the bars:

Saves space, and we generally reserve the bar-with-caret UI to expand/hide a list of things, rather than one thing.
Going even further, I think you can just re-use (or steal) the inner course bar UI as well:

Good suggestions, thanks for the feedback David! I'll definitely look at reusing our existing components, and extracting them out in to a reusable component (if only we were using React for that :P )
That last screenshot you gave looks really good too, I think once we have something with that look/functionality, that'll be a good MVP and it can go out. I'm still a bit worried about having too many scholarships to start, but after a user goes through their list once it should only be relevant scholarships from that point on.

So, @divad, speaking of React, I know we've talked about this before, but what are your thoughts on making some React components that are self contained, rather than making some cumbersome Backbone Views/Collections/Models? I decided to take a shot at implementing scholarships in React, and can push a branch if you're interested in checking it out. Seems to be A LOT cleaner. Here's a screenshot as well, not a carbon-copy of what we already have, but I think it looks pretty good (still open for feedback though).

I'm not again writing new components in React, especially if it's cleaner and you enjoy writing it more. :)
With regards to the styling, agree with more separation when expanded. There's other little details I like about the course bar that I think it would be good to make consistent here — no gap on top of the vertical separator, larger right margin on icons, capital case and letter spacing for the bottom two links. You can feel free to just copy the CSS from the course view (though re-using is ideal, but I'm not going to require it here).

Alright @divad12, I think it's ready for a look. There are still a few things I'm tweaking, but the core part of the code is definitely ready :) I've attached a screenshot below, but for this one it's probably best if you pull and run locally to see. Feel free to be especially picky on this one, since it's the first React PR for Flow. I think it turned out a lot cleaner than using Backbone!

Awesome! I will try to review this within the next 7 days. If I don't please bug me.

Ping @divad12, think you'll have time for a review this weekend?

Finally took a look — sorry for the delay.
Awesome first pass! Code looks pretty good and I just have some nits. React is a lot more readable and clear.
Screenshot looks good but I haven't pulled and tested locally yet.

What'd be really really super duper awesome is if there was some way to have faceted navigation so that users can quickly see what they're eligible for and what they're not.

Alright @divad12 and @jlfwong, I went through most of your comments, with the only things left being the issue of serving the minified prod version of React on the server.
I posted in Hipchat on two ways to do that, so feel free to pop in and let me know which you prefer.
After that, I think it's ready to merge, and then I can iterate on it if there's any suggestions.

Again, I will try to get to this before next Monday. :)

Create a js_prod folder, which is a copy of the existing folder, but minified, prod versions of the filers. (Looks like you guys had this one at some point)

Have a dev and prod folder, which would each have a copy of React. When the server starts, it copies the correct version of the file in to server/static/js/ext.

I'm leaning towards the first option, and preference either way?

I don't think you need separate folders... just stick both the dev and prod versions of React into server/static/js/ext and serve the appropriate file based on the environment. I think that should be possible right... though I don't have as much context as you do at this point.

Alright, it should load the right file now, depending on the environment. I tagged you in a comment on the part I'm slightly concerned about, but I think it'll be fine. Take a look, let me know what you think. Hopefully we can get this out the door soon.
Oh, @KartikTalwar sorry how long it's taken, but should be ready soon!

I'm excited! :-D

Sorry for the delay in reviewing Jeff!
Things look good except we gotta figure out the React dev/prod loading thing. I need to sleep now and my brain's a little too fried to figure this out now. Have you tested that the current way you're testing things (checking window.env in config_settings.js) works in production?
You can take a look at this too if it's any help:
http://stackoverflow.com/questions/16130351/how-to-load-environment-specific-configuration-with-requirejs
Feel free to just discuss here.

Alright @divad12, went through final cleanup, and I think it should handle the different environments. We'll want to test on my computer and yours most likely, before it gets deployed.
Also, side effect of merging this is that master should go green. For some reason it's red currently, but my branch fixes it. (Not sure why, it really shouldn't)

Ping @divad12, would like to get this merged.

@divad12 alright, personal goal is to get this merged by the end of next weekend.
Steps to test locally:

Check out the branch
run PYTHONPATH=.. python data/aggregator.py scholarships which should put the scholarships in Mongo
go to your profile, you should see a section for scholarships, and ~30 of them.

Let me know if you have any feedback or concerns.

Ok, testing!
Ran into this issue:

(rmc) 15:04:41 david-retina @ [ rmc ] (rmc@(f65dd3f...)) PYTHONPATH=.. python data/aggregator.py scholarships
Fetching scholarships
Traceback (most recent call last):
File "data/aggregator.py", line 423, in
func()
File "data/aggregator.py", line 379, in update_scholarships
rmc_crawler.get_scholarships()
File "/Users/david/redccnt/code/rmc/data/crawler.py", line 290, in get_scholarships
with open(filename, 'w') as f:
IOError: [Errno 2] No such file or directory: '/Users/david/redccnt/code/rmc/data/scholarships/scholarships.json'

Looks like I needed to create the directory rmc/data/scholarships. You can add this as a directory to git by creating the directory, add a file in it called .gitkeep (by convention), and then checking in that file.
Ran into another issue — GET http://localhost:5000/static/js/scholarship.js?1433811685 returns a 404. Do I need to do anything to get the React stuff to work locally?
Sorry for the delay — no computer access last week!

Oh I see the modifictation to local_server.sh. Ran npm install and that fixed it.

You're right, I need to add that directory!
Also, are the jsx node tools installed for you? It seems like they're not starting when you start the server, which means the file won't compile.

Saw your comment partway through making mine.
Yeah, you'd need to run npm install, my bad. That won't be an issue on prod though, because we compile the jsx once, on deploy.
Also, no worries about the delay, biking from SF to LA is a reasonable excuse I guess ;)

Added the .gitkeep file, how do scholarships look on your profile page locally?

Looks great!
Some comments:
Can we make these white instead of transparent, like the course bars?

nit: can we made the padding of these scholarship boxes match the padding of the course boxes?

vs.

How about make the » into a down caret, and correspondingly an up caret when expanded?

What do you think about changing the title from just "Scholarships" to "Scholarships you may qualify for" to be tad bit clearer what this section is about?
How about make the more info link open in a new tab/window?
Awesome stuff! This is so close to merging! Thank you for the test plan.

No problem! It was almost correct, but that's why I had you test cause I don't see the issues like the one with the directory.
Those suggestions sound good, quick question about the carets though. Do we want them to be up, down, or match the course reviews? Cause right now, they have left/right carets for the expanding section.

Actually, go ahead and pull, and let me know what you think. Changes should all be there.

Awesome, LGTM now!
Feel free to merge and deploy. And announce on the social medias! Great work.

Woo!
ᐧ

Great job everyone! Love this use of our Awards endpoint. Great stuff.

This feature doesn't work for my undergraduate program (which, UWFlow hides from the user, so they cannot change it).


Allow --select and --ignore to be combined

Here we update the logic in the StyleGuide to allow users to specify both
--select and --ignore to combine the power of both flags. Take for
example:
$ pep8 --select=E1 --ignore=E112 testsuite/E11.py
The example shows that we are now allowed to filter out E112 while
selecting the other E1xx checks.
A (potentially unfortunate) consequence of this change is that if a user
specifies --select without --ignore and has codes ignored in their
config file, then we will merge that into the options and continue to
ignore those codes.
Closes #390

The tests are going to fail, but I wanted to throw this up for @glyph and others to test.

So right now this accommodates the use case in the commit message, select something broad but ignore the rest. It doesn't, however allow for the inverse, e.g.,
pep8 --select=E24 --ignore=E

I'm not sure we need to either. Semantically that's the same thing as
pep8 --select=E24

That said, it doesn't behave exactly the same way. Take for example
~/s/pep8 git:bug/390 ❯❯❯ python pep8.py --ignore=E --select=E1 testsuite/W19.py
~/s/pep8 git:bug/390 ❯❯❯ python pep8.py --select=E1 testsuite/W19.py
testsuite/W19.py:12:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:16:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:19:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:21:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:24:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:26:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:31:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:32:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:35:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:38:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:43:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:44:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:45:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:52:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:54:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:57:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:58:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:62:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:63:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:64:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:65:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:71:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:73:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:77:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:78:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:81:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:83:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:92:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:99:2: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:106:1: E101 indentation contains mixed spaces and tabs
testsuite/W19.py:125:1: E101 indentation contains mixed spaces and tabs

The question I have is, do we want to pre-process these options to check for problems like this and warn the user or just silently do "the right thing"? Technically we've been doing what someone thought was the right thing for a while now and it's actually been not very intuitive. I'd love to get some feedback on this before proceeding.

The question I have is, do we want to pre-process these options to check for problems like this and warn the user or just silently do "the right thing"?

The behaviour you described, where --ignore=E --select=E1 allows a file with E101 issues to pass, feels surprising to me.
I feel like "most specific wins" is the least astonishing behaviour here, so for a file with E101 issues (pseudocode):

pep8 -> fail
pep8 --ignore E -> pass
pep8 --select E -> fail
pep8 --ignore E --select E1 -> fail
pep8 --select E --ignore E1 -> pass
pep8 --select E --ignore E -> helpful error message

et cetera
Naturally I've not yet looked into the practicalities of tests / implementation here, but I'd be interested in your views please!

The behaviour you described, where --ignore=E --select=E1 allows a file with E101 issues to pass, feels surprising to me.

Right. I feel the same. To me, I'm thinking that we should say "well, the selected code(s) is(are) a subset of ignore, we should just use the generic --select logic and discard the ignore values". Make sense?

"well, the selected code(s) is(are) a subset of ignore, we should just use the generic --select logic and discard the ignore values"

I've played around with this in a few incarnations, and I'm not sure I follow what you mean, sorry.
What would you expect the following to do on a file with E101 and E102 errors:
$ pep8  --select E --ignore E1 --select E10 --ignore E101
$ pep8  --ignore E --select E1 --ignore E10 --select E101

So I wouldn't expect repeated usage of --select and --ignore to produce anything coherent. Let me break it down into 4 distinct examples though:

pep8 --select E --ignore E1 I expect pep8 to only report on lines with codes starting with E but not E1 (e.g., E2xx, E3xx, etc.)
pep8 --select E10 --ignore E101 If we had something like E102 I would expect that to be the only code shown, since E101 is the only E10 class code, I expect nothing to be printed. If this was something like pep8 --select E11 --ignore E111 I'd expect E112, E113, ..., E116 to all be shown if present.
pep8 --ignore E --select E1 I would expect this to work the same as pep8 --select E1 does now
pep8 --ignore E10 --select E101 I would expect this to work the same as pep8 --select E101 does nwo

Ah, I think I've realised my issue here - I'm interpreting select as analogous to "enable" or "allow" rather than "choose" or "pick" (i.e. assuming everything is enabled by default, using select without ignore would be a noop)
I should have realised from the behaviour you demonstrated in https://github.com/PyCQA/pep8/pull/433#issuecomment-135285103 - my bad!
I'm'a take some time to try fix my mental model ;)

@doismellburning no worries! --select has weird mental models for different people. It's hard to explain it correctly all the time.

@sigmavirus24 -- Other than the merge conflicts, do you believe this PR is mergeable?

I suspect you might also have new / more insight now from your work with flake8

This could be merged. I'm less inclined to work on the rebase given that the functionality is included in Flake8 in a significantly better way that's far more powerful.
I can rebase this, if people really want it here. Previously Flake8 needed it here but 3.0 makes it unnecessary.

I think it would be valuable for those that don't use pycodestyle by way of flake8. I'll take it myself to update the pull request and merge it.

I think it would be valuable for those that don't use pycodestyle by way of flake8. I'll take it myself to update the pull request and merge it.

Maybe but pycodestyle only had that bug reported by Flake8 users who were redirected here. Further, this is something of a breaking change that should have only been included in 2.0. So unless you're eager for a 3.0, I don't think this is a change you should deliver any time soon.


:tada: Tracking issue for v0.19.0 release :tada:

This is a tracking issue for the upcoming v0.19.0 release 🎉
There are a number of things that I think should be completed before release and some others that would be nice to see included but shouldn't prevent the release. None of this is set in stone and I welcome everyone to comment below whether you think something should be added or removed from either list!
Blocking (in no particular order):

[x] #2034
[x] #2035 (this issue exists in the master example too)
[x] #1946
[ ] #1852
[ ] #1642
[x] #2061
[ ] #2056
[x] #2072
[x] #2116
[ ] #2125

Notable but not blocking (in no particular order):

#1851
#1844
#1858
#1860
#1892
#1891
#1853
#1633
#1609
#925
#2048
#2050

Issues that can be closed by new release

#1986
#1985
#1045

Two of these issues are about services that are going to be removed, so can't be fixed, and one is a more general
critique of the router which has been re-written.
Misc
Some extra bits to do before the release:

[x] Review dependencies
[x] Review and list issues that are resolved by the new release (more of a note to self 💭)
[ ] Confirm that each example is working correctly (the CI only checks if they compile)
[ ] Consider migration information and where it would live - yew.rs? as a discussion?
[ ] Update CHANGELOG
[ ] ...and probably more 😉

Expect all sections to change - I will update it as we go :)

Can we pin this issue?

Can we pin this issue?

Oh, could've sworn I had already pressed the button 😅

Should we also add an example that uses function components to the list?
I wonder whether it's useful to base this off an existing example so that users can compare the two
approaches side by side.

#2125 Is a nice feature and just missing documentation. Would be nice to have it for yew 0.19, so will add it to the list. Let me know if this is not ok.

#2125 Is a nice feature and just missing documentation. Would be nice to have it for yew 0.19, so will add it to the list. Let me know if this is not ok.

Even if we can't release it alongside 0.19, we could always release yew-agent 0.2. Agents are a separate crate now

@hamza1311 oh that's right, thx
No reason to keep it in this list then

I moved still open issues to 0.19 milestone, so I think this can be closed.

Also leaving a comment here:
Moderators are working on setting up some automation for releases and 0.19 release is being held hostage because of that.

Re-opening this. The can be closed when 0.19 is released.

Does it make sense to reconsider this statement in the README as part of the 0.19 release?
Note: Yew is not (yet) production ready but is great for side projects and internal tools.

For example:
Note: Yew is not 1.0 yet, so expect API changes.

Having used the master branch now for a while, I wonder if yew v0.19 is truly not ready for production use, keeping the above caveat in mind.

Does it make sense to reconsider this statement in the README as part of the 0.19 release?
Note: Yew is not (yet) production ready but is great for side projects and internal tools.

For example:
Note: Yew is not 1.0 yet, so expect API changes.

Having used the master branch now for a while, I wonder if yew v0.19 is truly not ready for production use, keeping the above caveat in mind.

I would not reccomend yew in production, the api might change too mutch, to the point where you will be refactoring your app more than writing features.
I do agree that we are getting a lot closer to  1.0 and maybe even the next after 0.19 release might be the one.
But until then I believe the statement in the README is valid

The scary words "Yew is not (yet) production ready" make me think more of random crashes than API breakage. If you just mean that you don't promise API stability, then say that you don't promise API stability.

I agree with both your positions. I can see that you don't want people to be disappointed or frustrated by having to do major refactoring on API changes. However if you are open and transparent about this, it would be the user's decision if they want to take that work on, or not.
As @jbg pointed out, the current statement, does not do justice to all the work that went into yew up to this point and the level of quality it is currently at.
So maybe make the statement even more explicit:
Note: Yew is not 1.0 yet, so expect API changes. Be prepared to do major refactoring due to breaking API changes.

I agree with both your positions. I can see that you don't want people to be disappointed or frustrated by having to do major refactoring on API changes. However if you are open and transparent about this, it would be the user's decision if they want to take that work on, or not.
As @jbg pointed out, the current statement, does not do justice to all the work that went into yew up to this point and the level of quality it is currently at.
So maybe make the statement even more explicit:
Note: Yew is not 1.0 yet. Be prepared to do major refactoring due to breaking API changes.

Could you make a PR?

Sure.

Yew v0.19.3 has been released 🎉 so I'm going to close this now 🥳


[MonorepoBuilder] Split command should allow remote Git repository URL to not end with '.git'

Hey there!
First of all, thank you for MonorepoBuilder, it really comes handy! We'd like to use it at work, but there is one little thing preventing us to do so: we use Azure DevOps as a Git host, and our repos URLs don't end with ".git". Our monorepo-builder.yml thus looks like this:
# monorepo-builder.yml
parameters:
    directories_to_repositories:
        packages/PackageBuilder<EMAIL_ADDRESS>        packages/MonorepoBuilder<EMAIL_ADDRESS>
Which fails when I try to run the split command:
> Composer\Config::disableProcessTimeout
> GITHUB_TOKEN=AUTHTOKEN monorepo-builder split

In RepositoryGuard.php line 28:

<EMAIL_ADDRESS>is not format for repository

I looked at the source code and it seems this regex is responsible for the validation. Is there a reason the (\.git) is not (\.git)??
Thanks!

Hi, thanks for feedback, I'm glad you find it useful.

Is there a reason the (.git) is not (.git)??

Nothing I can think of. Feel free to send PR :+1:

Great! PR #1595 opened 😉


Replace downcase with underscore for multi-word roots

It fixes a problem introduced in #761
When downcase was used, apierror instead of api_error was generated from ApiError entity.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

Coverage decreased (-0.08%) to 98.853% when pulling c298c26e39c7be709bc09307066e9952ecca2e1f on bikolya:fix-underscored-root into 294740b83635786a5c40a6fe07e8187bd279b27b on ruby-grape:master.

thanks … @bikolya, welcome 😄
and sorry for late replay

a bit curios … will have a look on it tonight

The CHANGELOG complaint is right, you're missing a colon after the PR :)

ah ok … thanks


replace rsc.io/letsencrypt in favour of golang.org/x/crypto

As per the readme over here, it's recommended to use acme/autocerts.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "no_rsc" git@github.com:tariq1890/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

requesting your review @caervs

@dmcgowan @thaJeztah any opinions on this vs #2915? From where I stand reducing our dependencies is always a win and as @tariq1890 points out this is recommended in the letsencrypt readme.

Also want to state that this PR will lay down the path for go mod migration :). I'll have that up once this is merged.

See also: https://github.com/docker/distribution/pull/2530

any opinions on this vs #2915?

I'm definitely not attached to #2915 - it was just to get rid of the fork, but (as Derek commented on that PR); that code needed replacing, so if this one does the job, I'm all in favour of that.

It looks like this PR is a duplicate of #2530 which was filed more than a year ago. It would be really great to see this merged. I am happy to get the PR review process going for this in case we are unable to revive the thread in #2530.

+1 this would be really nice to have. Currently dealing with some dependency hell related to needing to use the @dmcgowan fork of rsc.io/letsencrypt

Are documentation changes needed for this change?

I don't believe so. This PR intended to preserve any previous behaviour.

@caervs Did the e2e tests pass for this one?

Can I please get some response on this?

@tariq1890 yes turns out this change needs a few edits to work properly. Please:

Add Prompt:     autocert.AcceptTOS, to the manager as it requires a prompt function
Set tlsConf.NextProtos = append(tlsConf.NextProtos, acme.ALPNProto) (required for verification with letsencrypt
Add a note to the config docs that the ca-certificates package is required when using letsencrypt to trust the letsencrypt cert

In the meantime we really need a second review to get this in. @manishtomar ptal. Thanks.

@caervs Thanks for your review comments. This is ready for another round of review.

@caervs Do we have tests to verify this?

@manishtomar I have manually tested with no cache in place and restarting with existing cache. I have not tested with existing cache from letsencrypt fork carrying over into new cache, but I think that'd be overkill. Worst case the workaround is either to remove the cache or change the cache directory.


OSX Build failure, cupsGetPPD3

OSX 10.12 build failure:
$ go get github.com/google/cloud-print-connector/...
github.com/google/cloud-print-connector/cups
cgo-gcc-prolog:81:6: warning: 'cupsGetPPD3' is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
/usr/include/cups/ppd.h:366:22: note: 'cupsGetPPD3' has been explicitly marked deprecated here

I'm experiencing the same issue on 10.12.6.

I'm seeing more deprecations on macOS Mojave 10.14.1.  It doesn't seem to affect the build but I did want to bring attention to it.
$ go get github.com/google/cloud-print-connector/...
# github.com/google/cloud-print-connector/cups
cgo-gcc-prolog:86:11: warning: 'cupsGetPPD3' is deprecated: Use cupsCopyDestInfo and friends instead. [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/cups/ppd.h:366:113: note: 'cupsGetPPD3' has been explicitly marked deprecated here
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/cups/ppd.h:58:29: note: expanded from macro '_PPD_DEPRECATED'
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/cups/versioning.h:147:43: note: expanded from macro '_CUPS_DEPRECATED_1_6_MSG'
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/cups/versioning.h:142:55: note: expanded from macro '_CUPS_DEPRECATED_MSG'
$

Can someone please help me with this...I"m running 10.13.6

@mule1515 did you see if the binary built or not?  It might have been created but not put on your path correctly.

@mule1515 did you see if the binary built or not? It might have been created but not put on your path correctly.

@rnhurt no, i don't really know what i'm doing.  you think you can help me?


Add lastVerifiedBlockNumber to getStatus request

This change adds the lastVerifiedBlockNumber to the getStatus request, by fetching it from the witnesses params table and adding it if present. I think this is rather useful to immediately check the state of hive-engine nodes, without having to perform a second request.

Tested this also and works:
http://[2407:7000:9cb7:b800:d9d3:d7c:db4b:a7cd]:5010


ICMP checks fail when using IPv6 literal

I am using this simple config.yaml:
storage:
  file: /data/persistence
services:
  - name: crimson v4
    url: "icmp://<IP_ADDRESS>"
    conditions:
      - "[CONNECTED] == true"
  - name: crimson v6
    url: "icmp://[2a06:e881:5806:42:4c0:deff:fe2e:5910]"
    conditions:
      - "[CONNECTED] == true"
  - name: crimson.ortg.de
    url: "icmp://crimson.ortg.de"
    conditions:
      - "[CONNECTED] == true"
  - name: crimson tcp v6
    url: "tcp://[2a06:e881:5806:42:4c0:deff:fe2e:5910]:443"
    conditions:
      - "[CONNECTED] == true"

Only the ICMP-Check using the v6 literal is failing, everything else is working fine. Even the TCP-Check using the v6 literal.
I've seen that in client/client.go (here) you set the Network to ip4, maybe this could cause my check to fail?

When you say Even the TCP-Check using the v6 literal., do you mean that crimson tcp v6 works?
When I try it from my end, neither of them work. Might be a firewall or something, but when I try icmp://[::1], it works regardless of whether I use pinger.SetNetwork("ip4"), pinger.SetNetwork("ip6") or pinger.SetNetwork("ip")

When you say Even the TCP-Check using the v6 literal., do you mean that crimson tcp v6 works?

Yes, checking TCP for IPv6 works for me.

When I try it from my end, neither of them work. Might be a firewall or something, but when I try icmp://[::1], it works regardless of whether I use pinger.SetNetwork("ip4"), pinger.SetNetwork("ip6") or pinger.SetNetwork("ip")

This should not be a firewall issue, the host (or at least tcp port 443) is not firewalled. Are you using docker for testing this? If you don't explicitly enable IPv6 your container may not be able to reach the IPv6 internet.
I can reproduce the same behaviour using the Google DNS. ICMP does not work, while TCP Port 53 works fine.
  - name: google v6 icmp
    url: "icmp://[2001:4860:4860::8888]"
    conditions:
      - "[CONNECTED] == true"
  - name: google v6 tcp
    url: "tcp://[2001:4860:4860::8888]:53"
    conditions:
      - "[CONNECTED] == true"

Turns out that my ISP doesn't support IPv6, hence why it wasn't working.
That being said, after trying on a my laptop while connecting to another router , both of them work on windows:
2021/05/13 20:01:56 [watchdog][monitor] Monitored group=; service=google v6 icmp; success=true; errors=0; duration=174ms
2021/05/13 20:01:57 [watchdog][monitor] Monitored group=; service=google v6 tcp; success=true; errors=0; duration=169ms

On Docker, however, I wasn't able to make either work.
I can't promise I'll be able to find a fix anytime soon, as working on it requires me to work on it outside of my house, but at least you can use TCP for now, right?
If you or anybody else would like to have a go at fixing the issue, be my guest 😇

I have the same issue even when running outside of a docker container on a machine with full IPv6 connectivity.

The privilege issue is discussed in #697
As for specifying ipv6/ipv4, this was implemented in #661


Handle non-executable tmp directory

It seems some hosting services mount /tmp without execute permissions which means search won't work since we extract and execute rg from there. We could try /tmp, the binary's directory, and then the system-installed rg if it exists in that order (possibly we'll want to ensure it's at least a certain version---I don't think VS Code makes any changes to ripgrep but we might want to double-check). If all fail we should output a message explaining that search won't work and how to fix it.

It might be better to use $XDG_CACHE_HOME or $HOME/.cache instead of /tmp. Golang stdlib does a pretty good job of finding cache dir so I guess you could just copy that

Ahh good point, I like that.

1 for this. I have a dream that I can install this easily as 123 on all of my clients with their own jailed account + to avoid rebuilding it manually on each account... so all their extensions, config and stuff won't mix by others...


Added funtionality for multiplication operation

Modification of the multiplication operation function and added tests where if two strings are given as input and also if one string and one number is given.( we get an Internal Server Error ).

@badoolee ,Thank you for your valuable contribution!! Do check out other repositories from IEEE-VIT


How to use snmpset?

How to use snmpset?

snmpgo does not support a SNMP SetRequest.

I created #18.
Try it if you like.

👍


Full lab instructions need checking against updated UI

All the way through.
###This lab experience is terrible for learners:

The instructions are often not clear - the steps are often not in line with what appears on screen in the updated UI. It's confusing learners and they struggle to navigate around the application - they then can only focus on the aspect of navigating around, with frustration, which then impacts them also in the way they learn about what the exercise is actually trying to teach them.

the numbering is often askew as well... when asking learners to repeat the previous steps in most cases, that numbering does not match.

often when you have a lot of steps within a task, it's confusing to have them listed as a-b-c-d, because it is not easy to tick off what you have done - and therefore easy to miss a step.

My frustrations with this lab continues --- just about every single exercise comes up with errors!
Please Microsoft, let us know when you have fully revised this lab and tested it thoroughly. i will also feedback this extreme poor lab performance via MTM!

Hi,
The labs are updated and instructions are updated

Once the lab instructions are retested they will be updated in GitHub


500 Error when visiting webui page.

[2024-03-06 17:40:31,885] ERROR in app: Exception on / [GET]
Traceback (most recent call last):
File "/home/jiaye/anaconda3/envs/audiocraft/lib/python3.9/site-packages/flask/app.py", line 1463, in wsgi_app
response = self.full_dispatch_request()
File "/home/jiaye/anaconda3/envs/audiocraft/lib/python3.9/site-packages/flask/app.py", line 872, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/jiaye/anaconda3/envs/audiocraft/lib/python3.9/site-packages/flask/app.py", line 870, in full_dispatch_request
rv = self.dispatch_request()
File "/home/jiaye/anaconda3/envs/audiocraft/lib/python3.9/site-packages/flask/app.py", line 855, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
File "/media/jiaye/DATA/lyj/soft/stable diffusion/audiocraft-webui/webui.py", line 109, in index
model, prompt, topp, duration, cfg_coef, topk, temperature = load_last_gen_settings()
ValueError: not enough values to unpack (expected 7, got 3)

+1

No idea what's wrong but it falls back if that file is malformed for whatever reason now.


Fixed copying fonts when product flavor specified with Android Gradle Plugin 3.2+

Fixed copying fonts when product flavor specified with Android Gradle Plugin 3.2+
Ref: https://github.com/facebook/react-native/blob/master/react.gradle

Superseded by https://github.com/oblador/react-native-vector-icons/pull/960


More fixes for the HeliosSoloIT

If the DOCKER_HOST is <IP_ADDRESS>, fall back to Unix sockets instead.

Use the latest version of docker-client, which supports checking the OS
name directly rather than kernel version (for Boot2Docker detection).

Note that as part of the docker-client upgrade, we need to declare an
explicit dependency on commons-lang:commons-lang:2.6 to resolve a conflict
between docker-client and another package.

:+1:


PropertyFieldPeoplePicker not triggering ComponentDidUpdate

Not sure why adding People with this picker does not trigger CompDidUpdate in the underlying React component. Triggering the update or refreshing the page shows that props updates successfully.
Do you have to explicitly state this.properties.people = this.properties.people in the onPropertyPaneFieldChanged property?

Hi @robiharid,
Could you please provide a bit more explanation on what you're trying to achieve?
When the value is changed in PropertyFieldPeoplePicker we're updating the appropriate property of the web part and calling onPropertyChange. This actions lead to web part's re-render.
if (this.props.onPropertyChange && newValue) {
      this.props.properties[this.props.targetProperty] = newValue;
      this.props.onPropertyChange(this.props.targetProperty, oldValue, newValue);
// Other code

Hi @robiharid,
Could you please provide a bit more explanation on what you're trying to achieve?
When the value is changed in PropertyFieldPeoplePicker we're updating the appropriate property of the web part and calling onPropertyChange. This actions lead to web part's re-render.
if (this.props.onPropertyChange && newValue) {
      this.props.properties[this.props.targetProperty] = newValue;
      this.props.onPropertyChange(this.props.targetProperty, oldValue, newValue);
// Other code

hI @AJIXuMuK thanks for replying,
My problem was that the change was not triggering ComponentDidUpdate in my underlying Component.tsx do you know how I can force a rerender?

Could you please check that the render method of the web part is called after property change?
If yes - check if you're providing changed data to the component.
React may be smart enough to skip component's re-render if it's not needed.


Apple: Handle comma in resource names

Fixes #2836.
We use the comma as a separator when passing the resources from the tunnel process to the app process, but previously used .urlHostAllowed when percent-encoding, which means commas weren't percent-encoded. We fix that by using .alphanumerics, which percent-encodes commas as well.

@roop perhaps is there a serialization/deserialization library we can use so that we don't have to individually handle each edge case?

Hmm, yeah JSON might work since we're already depending on it?

roop/handle_commas_in_resource_names

This is a super simple list, and I don't think there can be any other edge cases.
This will get serialised-deserialized every second, so wanted to keep the serialisation simple if we can. I had already thought of the comma when writing the code, but the mistake is that I missed that the percent-encoding I used didn't include commas.


Cannot change group filter from another variable to none

0.10.0 lets you filter by group from none to any variable, but once you change the filter from none, it doesn't let you select it again unless you refresh the page

fixed in in 0.11.0

Functional Test: Filtered to group by Sex, then was able to group by none again
Pass


Add ESC + Direnv guide

Add a page that explains how to integrate ESC with Direnv.

I'm not entirely sure that this should be part of the getting started, but I didn't have a better idea of where to put it. Maybe we should have an "integrations" section?

(we should update https://github.com/direnv/direnv/wiki#tools-integration and add a link to this page once it is deployed)

Okay, this should be ready to go.
These changes now add a new section to the ESC menu, "Other Integrations", which links to the IaC guide and the new Direnv guide.

PTAL @arunkumar611


What if you really wanted to use a specific gem from the system, is there a way to do it with a hack or otherwise?

Hi All,
Similar to #1964 I would like bundle install to use a gem from the system if it is already installed there rather than installing it again in the local bundle.
My situation is this:

I am running Ruby in an enterprise environment, this is a Rhel5-based system with access to a tool collection from about 10 years ago. Individual users do not have root access.

Installing nokogiri in this environment is hard, despite that team's obvious effort to make it easier by packaging binaries, it is still hard to make it install reliably for all developers when they run bundle install.
It has however been successfully installed to the system Ruby and it is available from there.
In an effort to make user install more reliable we have specified an absolute version of nokogiri in all of our Gemfiles (the one that has been installed to the system), but nonetheless, nokogiri-related bundle install issues with individual user environments is a recurring problem.

Like #1964, what I would really like is for bundle install to recognize that the version of nokogiri the bundle needs is available from the system and to just use that, rather than trying to re-install it in the user's local gems.
It seems that the bundler core team do not want to provide this functionality, however as mentioned above using bundle --local is not really an option here.
Using something other than Bundler is not really an option either, since it is a great tool that solves 99.9% of our requirements except for this one thing.
So I am curious if any Bundler experts could advise on possible hacks that I could make to a fork of Bundler to enable this, or any other approach that they could recommend?
Many thanks in advance,
Stephen

As you note in your message, the way that Bundler works is to automatically set up gems from one place. You can choose whether to use "system" gems (meaning gems installed to the same place as the gem install command would use), or install bundled gems to a specific location dedicated to that application. In early alpha versions of Bundler, we experimented with the ability to use gems from both locations at the same time, and it was a huge failure. It was confusing, it caused bugs, and it was extremely hard to manage or reason about.
If your users can read the system gems, why not copy the installed copy of nokogiri into the local bundle? While I appreciate that Bundler nearly does what you want, we don't have plans to ever support simultaneously using gems from more than one place.

I think the issue is only to allow local-first resolution of gems with a separate switch, rather than force downloading newest version when version is not fixed. I couldn't see any compelling argument why user should not be allowed that freedom.


IterableDiffer needs one argument

node_modules/@swimlane/ngx-datatable/release/components/datatable.component.d.ts(409,16): error TS2314: Generic type 'IterableDiffer' requires 1 type argument(s).
angular 4.0.0-beta.5
@swimlane/ngx-datatable 6.0.1

doesn't occur with 6.0.0

We don't support Angular4 yet.

@amcdnl  thx
anyway this can be modified by simply changing rowDiffer: IterableDiffer to rowDiffer:KeyValueDiffer<{}.{}>

Can you PR that?

I just did

@amcdnl,
thanks for giving good data control ngx-datatable, i have used in my project, for few never feature i need to update angular 4, so when can we expect new release of  ngx-datatable support angular 4.
thanks.

for the time being any one can comment // rowDiffer: IterableDiffer;


How should we use this result to get a mesh from the sugar model?

https://github.com/Anttwo/SuGaR
When i get mesh from sugar model, i run with this task to get only the object i want and get pt file. how should i apply it to sugar model?

Hi, can you provide more information about what you did? The .pt file provided by SAGA is a binary mask for 3D Gaussians, i.e., 0 means background and 1 means foreground.

u did? The .pt file provided by SAGA is a binary mask for 3D Gaussians, i.e., 0 means background and 1 means foreground.

@Jumpat
You recommended the current repository when I posted an issue about how to remove everything but the objects from the sugar model and just get the object mesh.
So I'm wondering if I can apply this segmentation to the sugar model and get just the object mesh I want?

I think yes, since you can use SAGA to obtain the vertexes of the target object. Then you just need to retrieve all edges belong to it. However, you may need to implement it by yourself. I don't know whether sugar keeps the original attributes of Gaussians. I think this wouldn't be too hard.

I think yes, since you can use SAGA to obtain the vertexes of the target object. Then you just need to retrieve all edges belong to it. However, you may need to implement it by yourself. I don't know whether sugar keeps the original attributes of Gaussians. I think this wouldn't be too hard.

Thank you for your response. For now, I can only get the segmented 3dgs rendering result, not the mesh.


Avoids having a null pointer exception when typing an invalid command name

While trying the commands I made a typo in the bake command name and had a null pointer exception.
This displays a small error message.

This is ~80 commits behind, can you update it to latest?

Can't seem to find a way to merge the new branch... I'm new to github... I've managed to do a new branch with the same name apparently

The modification was already made in the main branch...


Use hyperdeck-connection

For NRK's Sofie project a connection library for the Blackmagic Design Hyperdeck devices was developed. This connection library takes care of reconnection, resending and serialization/deserialization. In addition it also has an events system in place for notifications.
The current implementation in this module has no concept of connection status, commands or notifications. Using hyperdeck-connection will greatly improve the resiliency towards network errors of this module. In addition it will make it easier to add feedback in a future PR.
What is left to do

[ ] Release hyperdeck-connection with new commands added for companion
[ ] Test new implementation with companion and a hyperdeck

I'm not sure if I am totally agreeing with you that the current module has no concept of connection status? It is done by the tcp library it uses. And effected by the on('status_change') event handler.
So it will probably not do much for network error resilency. But the other stuff is nice additions :) Go for it!

I'm not sure if I am totally agreeing with you that the current module has no concept of connection status? It is done by the tcp library it uses. And effected by the on('status_change') event handler.

Yeah, I misworded that. What I meant is that I believe it doesn't use TCP keepalive nor use the hyperdeck ping mechanism.

@baltedewit have you experienced issues with the TCP connectivity to a hyperdeck with Companion?  Because I've never had issues with this module in that regard.
Plus I'm in the middle of a re-write to add model detection and feedback, which for simplicity I added as index.js while leaving the existing file for the time being (https://github.com/bitfocus/companion-module-hyperdeck/blob/master/index.js).  So, your version bump to v1.2 is not necessary since v1.1 is the unreleased WIP.
Given this product has its interface documented and its relatively simple compared to something like ATEM which is quite complex and has to be reverse engineered ... I'm not seeing much gains by shifting over to a connection library.  If the TCP library in the project isn't up to snuff, I'd rather see time and effort put into bolstering that vs. side-stepping it since most modules don't have the convenience of a third-party library and lot of modules do use our internal library (such as the rest of the BMD modules).  But that all is not really my call, just my opinion.

Not to be negative @baltedewit, but the update to use your module does not really do anything as far as I can see. There is no tcpkeepalive in your module, and it would be as easy to add that flag to our own tcp system, so that all the other modules in companion using the general tcp module, also will benefit from it. So the only thing new is the notifications of changes. But you are not really using them in the pull request. So nothing added there either. If @krocheck is adding feedback support, then that is in fact a good change I would like :) Hope you are not taking this in a negative manner, really thanks for the effort!

I think you would gain a lot from both having a shared codebase with us and also having a more structured approach to parsing responses (async and sync).
I'd be up for spending a few more hours implementing feedback, but I can't be spending energy on discussions like using libraries or not etc. Sorry to hear you guys are not up for collaboration on this one.

Again, I think you are misunderstanding where I am coming from. But as far as I understood, krocheck has already done a lot of work with implementing data to/from the device and started on feedback handling. So it’s a bit up to him, if he wants to reimplement it using your module or not. I agree that a shared codebase could be good :) @krocheck decides :)

Let me digest this a little more because I didn't see the standing PR in the library to add things like the play command.  I was sifting through the code noting to myself that it felt incomplete but missed that.

@baltedewit this is still good to go?

Yeap, this one should be good!


The connected device doesn't support depth streaming!

Required Info

Camera Model
D435

Firmware Version

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
Linux firefly 4.4.77

SDK Version
2.0

development platform:  RK3399  http://wiki.t-firefly.com/index.php/Firefly-RK3399
we recomplied the librealsense from SDK 2.0 successfully.
But when we run the depth sample, we got the error like:
firefly@firefly:~/Downloads/librealsense-master/librealsense-master/examples/C/depth$ sudo ./rs-depth
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense USB2
Serial number:<PHONE_NUMBER>66
Firmware version: <IP_ADDRESS>
The connected device doesn't support depth streaming!
so what is the problem and how to resolve it?

For more information, you can check connected as USB2 or USB3 by popup message on RealSense Viewer when connected.

Hi @anson2004110,
could you give us guidelines of how to compile librealsense2 on RK3399, I'm having many issues with kernel version and openGl.
Best regards,
Felipe D.

hi @fadonoso
do you get guidelines of how to compile librealsense2 on RK3399?

Hi,
Not at all. Sorry mate.
On Tue, Oct 16, 2018, 08:52 SunQiChang<EMAIL_ADDRESS>wrote:

hi @fadonoso https://github.com/fadonoso
do you get guidelines of how to compile librealsense2 on RK3399?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/1091#issuecomment-430245445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvy4WnL1bkkGYtoZYLXtM_2PQD-JCa8ks5uleSHgaJpZM4RwQV0
.

Hi @anson2004110,
I compiled libsense-2.25.0 on Firefly RK3399,but it seems like the D435i doesn't connect to RK3399.
Did I miss some import step?


Crystal 0.7.5 compatible errors

Crystal 0.7.5 changed the name of IndexOutOfBounds to IndexError

Thanks

Some fast response there bro, thanks :)


[Feature] Typographical changes

Description
In the attached screenshot, you can see that for every text content, all the words start with capitals, which does not look very appropriate. Please allow me to format the texts.
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@rohansx Please assign this issue to me

@Pranav-Rustagi for now it's okay as we are yet to decide the things


Individual messages can be downloaded in Electronic Mail Format

Requirementes

[ ] Message viewer contains an action link/button/menu to download the message
[ ] Pressing the button download the message in EML format
[ ] Filename to be the message subject

Relates to:

#227


feat: use ledger proxy for hedera nodes

📝 Description
Use ledger proxy for hedera nodes
❓ Context

Impacted projects: ``
Linked resource(s): ``

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Integration tests are also failing for the same reason on develop.  Seems to not be an issue with this PR

To reiterate what the issue is here:
The integration tests cannot pass with the Hedera client being set up for the ledger proxies.   The Hedera SDK will automatically select GRPC nodes when running in node (instead of GRPCWeb).  The proxies still seem to work in-app.
Possible solutions include a mock client for only integration testing that uses the default nodes instead of the proxy nodes or skipping these tests for Hedera

Please do not close this PR

Hi @Sheng-Long, until we decide to do something more advanced, let's disable integration tests for Hedera :pensive:
Easiest way to do so, I think, is to simply remove "js" from here.

Hi @Sheng-Long, until we decide to do something more advanced, let's disable integration tests for Hedera 😔 Easiest way to do so, I think, is to simply remove "js" from here.

This did not seem to work

Please do not close this PR


winget install and upgrade fail with exit code -1073741819 for any package

Brief description of your issue
My team creates custom Azure VMs.
We use winget to install tools on the VM.
When user logs in to VM we run winget install for several packages.
All winget commands fail with exit code -1073741819.
After some time issue auto resolves itself.
I noticed that when I login to VM App Installer status in MS store is 'Pending'. Maybe the issue is related to the App Installer.
I found in documentation that I can run this command to register winget when I login for the first time:
Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
But I still see error after I run this command.
Issue started to happen recently. Everything worked fine previously.
Error code -1073741819 is not listed here: https://github.com/microsoft/winget-cli/blob/master/doc/windows/package-manager/winget/returnCodes.md.
Steps to reproduce
I run two commands on new VM after first login:
& winget upgrade --id "7zip.7zip" --exact --accept-package-agreements --accept-source-agreements
& winget install --id 'JanDeDobbeleer.OhMyPosh' --exact --accept-package-agreements --accept-source-agreements
both failed with exit code -1073741819
After some time issue auto resolves itself.
Expected behavior
Packages installed and updated.
Actual behavior
Operation fails with exit code -1073741819.
Environment
> winget --info
Windows Package Manager v1.2.10691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.2283
Package: Microsoft.DesktopAppInstaller v1.17.10691.0

PowerShell version information:

PSVersion                      7.3.7
PSEdition                      Core
GitCommitId                    7.3.7
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@nbdinara the version of WinGet included in that particular VM image (1.2.10691) is several versions back. I'd suggest upgrading App Installer to the latest version. You could either do that via the Microsoft Store or you could download the latest version from the releases page here at GitHub or via https://aka.ms/getwinget.


Fix doc

This is a fix of some issues I found after checking the riverpod website since the last merge.

Issues:

some typos.
'modifiers' section was not translated because the folder was not in the correct place.

All should be fixed now. I appologize for the inconsistencies

Thanks!


Documentation preparation for "make public"

Target
Overwork all documents - remove AIcrowd dependency

[ ] Search all file (work through): https://github.com/flatland-association/flatland-book (<- https://gitlab.aicrowd.com/flatland/flatland-book)
[ ] Readme.md
[x] GitHub Pages

https://github.com/actions/upload-pages-artifact
https://pages.github.com/
https://github.com/actions/deploy-pages

[ ] What about docs folder in this repo? Still deployed? Is all of its content covered by the book?
[ ] What about docstrings code documentation?
[ ] pr on aicrowd to link to current documentation

@manuschn I suggest using GitHub Pages for deploying up-to-date Flatland documentation. Any reservations?

GitHub Pages

API docs currently not generated:

https://github.com/flatland-association/flatland-book/blob/ddc13abc79535a0b53854854f9d90195a90696b5/_toc.yml#L34-L36
https://github.com/flatland-association/flatland-book/blob/main/import_env_doc.sh#L21
https://github.com/flatland-association/flatland-rl/blob/main/Makefile#L20 -> output empty