Attempt to read RESP Errors message

Following #981.
Attempt to read RESP Errors message from input stream when IOException occurs during sendCommand.
I need some reviews about introducing Protocol.readLine(inputStream) method.
I made it at Protocol class for consistency of read/write operation but there is a chance of unintended usage of it. Another option is directly using like inputStream.readLine() at Connection.sendCommand method.
Exception message in stack trace

AS-IS

redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketException: Broken pipe
	at redis.clients.jedis.Connection.sendCommand(Connection.java:107)
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)

TO-BE

redis.clients.jedis.exceptions.JedisConnectionException: -ERR Protocol error: invalid multibulk length
	at redis.clients.jedis.Connection.sendCommand(Connection.java:107)
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)

I'm afraid that we can't read a line from InputStream when (socket / read) timeout has been occurred and it could be blocked.
1.

IMO we have to answer these questions to make it really works.

Could we peek InputStream and read bytes which are current available?
Is it better to show response which may be partial?
Is it better to show partial response which doesn't start with -ERR?

@HeartSaVioR
Yes, I think so, I'm testing about availability of InputStream. I'll add some commits within after few days.
Number 2/3, how about to check \r\n? REDIS protocol spec said Redis RESP Error ends with \r\n.

@itugs OK, to wrap it up, when JedisConnectionException occurs

Check availability of InputStream, and read available "bytes" (and convert to String)
Check that it starts with -ERR. Use origin JedisConnectionException if it doesn't.
Check that it contains "\r\n". If it does, pick that line and use it for wrapping JedisConnectionException's message.

@HeartSaVioR Good. Let's try.

@itugs @HeartSaVioR have thought about a way to test this?. I think there might be a way of doing it. I'll give it a thought and comment here.

@marcosnils Currently we already know various ways how to let Redis disconnects connection. :)

@HeartSaVioR yeahh but this case is different because redis needs to send the error before disconnecting. So I guess it's going to be a tricky one but I believe it can be done.

@marcosnils We can use Redis limitation which @itugs found at networking.c though it can be changed. Maybe it would be hard to change.

@HeartSaVioR @marcosnils At first I'll use that limitation and searching for other cases.
Would you let me know if there are any existed test cases for broken write connection due to server RST?
One another point I need to test is read timeout when try to read RESP Error message,
but think behavior of Redis will 1) send RESP Error message, 2) close connection.
So we could think that RESP Error message is always present in input buffer.
If then there is no need to test timeout. How do you think?

@itugs You can refer PublishSubscribeCommandTest.handleClientOutputBufferLimitForSubscribeTooSlow() but it's slightly complicated cause we need to settle precondition (change some configurations to Redis).

@HeartSaVioR Thanks, I'll check it.

@itugs @HeartSaVioR I came up with something that tests it:
  @Test
  public void getErrorAfterConnectionReset() throws IOException {
	class TestConnection extends Connection {
		@Override
		protected Connection sendCommand(ProtocolCommand cmd, byte[] ...args) {
			return super.sendCommand(cmd, args);
		}

	}

	TestConnection conn = new TestConnection();
	byte[][] params = new byte[1024 * 1024 +1][100];

	try {
		conn.sendCommand(Command.HMSET,params);
	} catch (JedisConnectionException jce) {
		assertEquals("-ERR Protocol error: invalid multibulk length", jce.getMessage());
		return;
	}
	fail("Should throw exception");
  }

I'd like your opinions

@marcosnils @HeartSaVioR I improve codes and add test cases.
@marcosnils Your first question is commented in codes.
Second one, the reason of new method of Protocol class is written at my initial PR comment.
In shortly, I made it for consistency. I thought Protocol class is where have responsibilities of read/write.
During this PR I feel that better location of process*/read*/send* is inside of Connection because these methods are tightly coupled with Input/OutStream.

@itugs thanks for the updates. I've made a second review to the PR and I still have some suggestions / questions. I'll comment the code shortly

@marcosnils Any updates for this?

@itugs sorry for the delay. I've made some comments to your changes. Let me know if something needs clarification.

@itugs once you make the changes we can merge!.

@marcosnils I updated PR. Thanks.

LGTM.

LGTM too!

Marcos merged this into master, 2.7, 2.8 branches.

Thanks!


Convert Vukuzazi to OWL

Vukuzazi - (northern KwaZulu-Natal - South Africa) - Interactions between HIV, tuberculosis (TB), environmental exposures and non-communicable diseases. (Public and Creative Commons BY (CC BY))

[ ] store TSV in data/
[ ] update data/README.md
[ ] write conversion script
[ ] create metadata TTL
[ ] update Makefile to build OWL

@beckyjackson Please revise that checklist as needed, and copy your revised checklist to the other conversion issues.

Closed by #21


Block edge 4.3.28

4.3.28 needs to be disabled:
2 clusters currently failing (18%),  2 gone (18%),and  7 successful (64%), out of 11 who attempted the update over 7d
Currently failing classification:
* Single master: 1
* Untriaged: 1

4.3.28 can be enabled again:
1 clusters currently failing ( 7%),  1 gone ( 7%),and 12 successful (86%), out of 14 who attempted the update over 7d
Currently failing classification:
* Single master: 1
* Untriaged: 1


React Native Meetup Belgium

Hey guys,
I am (or we, FLAVR are) organising a React Native meetup on Wednesday and as far as I know it's the first one in Belgium. I have worked a lot with RN before and was just wondered if there were some things I should definitely mention or cannot forget.
I made a little hackathon project on a private GitHub repo including some basic Relay, Redux, Immutable, etc. As I don't want to share the solution publicly before the event, I will keep the repo private and will invite people in case you want to take a look. I already invited @nicklockwood and @vjeux to the repo. If you have any remarks on the project, feel free to let me know.
Greets,
dejakob

@dejakob I suggest you post this to the RN Community FB group, it's a better place to discuss this sort of topic. Feel free to tag me and we'll follow up there https://www.facebook.com/groups/react.native.community/


Sync eng/common directory with azure-sdk-tools for PR 9113

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/9113  See eng/common workflow

/check-enforcer override
These failures are unrelated to this change.


Init and close of devices

There is a potential bug by design in how devices are treated in the fei4_run_base.
While devices are initialized only once in the pre_run method when isinstance(self.conf['dut'], Dut) is true they are always closed in the cleanup_run method.
When writing a prim list this means that a Serial port is for example closed and not reopened when rerunning the scan.
How to deal with this?

will send you files.

The change in fei4_run_base I also tried yesterday, with the same result, that pyBar hangs and is not responding anymore. The latest log lines are:
2015-06-30 10:54:41,936 - root - [INFO    ] (MainThread) Found adapter card: Single Chip Adapter Card with ID 74
2015-06-30 10:54:41,946 - root - [INFO    ] (MainThread) Initializing fei4_rx from module basil.HL.fei4_rx (Version: 2)

did you also use SiUsb.py?

Yes I did.

2 possibilities:

only close USB device at the end of each run. All other devices are kept open. Potential hazard: Devices are not properly closed after the last run (but this may depend on the python implementation).

close all devices at the end of each run and initialize at the beginning of each run. Potential problem: This may slow down things a little bit.

I'm fine with solution 1. since all implementations we use (and I know, e.g. pySerial, pyVisa, pyZeroMq) close the device when the object is destroyed. Also the OS should always automatically take the control of the device if the program is closes / crashes ?


setRelease on JS doesn't set release on native

Platform:

[x]  iOS
[ ]  Android

paranoid redacted npm ls:
<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
Config:
Sentry.config(__CONFIG__.sentry.dsn, {
  deactivateStacktraceMerging: false,
  logLevel: SentryLog.Verbose,
  disableNativeIntegration: false,
  ignoreModulesExclude: [],
  ignoreModulesInclude: ["RNSentry"],
}).install();

I am using a custom release name for JS and native. I've got it all wired up and it's working great (I upload source maps from my own script not through xcode or android build process). When app boots I run Sentry.setRelease after my .install(). However when iOS native crashes are being reported I am getting the default release name<EMAIL_ADDRESS>Is there any way to persist the release name changes on native? I'm pretty sure it's just uploading before running the JS code that changes release name.

I will check this right now.

OK, so I tried it.
Start App -> Set Release -> Native Crash (by calling Sentry.nativeCrash();)-> Restart App -> Crash will be sent with Release I set before
What is really strange it was working every other time, so it must be a threading issue.
I've noticed that if I wait a few seconds after I set the release and then crash it works if I set the release and immediately crash afterward, it doesn't work (it sometimes does work).
I also found another issue in sentry-cocoa where it will not work when you call reportUserException multiple times (which isn't called from react native at all).
I am still trying to figure out where I have the race condition, just so I know, were you doing the same, trying out a crash?
OR
Did that happen in the wild?

Yeah it was a debug option in my app I was pressing that causes a JS crash, then I triggered another that caused a native crash.
I forgot if I was in debug mode which just shows a red screen I can dismiss and keep using the app or if it was a production environment that actually crashes the app. I think it was in a production environment.

@JAStanton Can you please upgrade to 0.17.1
This should be fixed there.

sure, let me give it a try


Admin and User  Dashboard Re-Updated

.
@kartikcode  take a look...

admin/index has user side interface. Kindly rectify it.


Add n_qubits to qobj.config and qobj.exp.config

Add qobj.config.n_qubits and qobj.experiment.config.n_qubits
during transpile(). This field is not part of the qobj_schema, but
needed for the online simulator at the moment.

Summary
Details and comments

Please note this was required by the API folks - seems to be a required field for the online simulators.


NixOS image generation tests

We currently have no VM tests that directly test our image generation scripts, and probably should. Things like nixos/tests/ec2.nix test it indirectly but most other tests share the store with the host.
A lot of the image testing machinery could probably be shared with the installer tests, too, since the checks we want to run after running the installer are probably the same as the tests we want to run after booting an image.

For an example of why this makes me sad, I want to adjust the GCE and Azure image generation processes to use make-disk-image.nix but I don't have an easy way to test either image without signing up for an account in both those systems. With AWS, I just ran the EC2 tests and got a decent amount of confidence in the outcome.

I'd say this is still important!
FWIW, in builds.sr.ht, we do test the NixOS images as part of the daily image refresh, so that's another way make-disk-image.nix gets indirectly tested

I think it's still important, but I probably won't work on this, so next time I'll just let the bot close it

I am interested into picking this up, first I have questions.
Currently, qemu-vm runs make-disk-image to create its store image and run tests over it.
We would like to test make-disk-image, so we have two conceptual ways:

we create a VM test with the proper contents and it uses make-disk-image : we do this all the time ;
we create a VM test and we want to invoke make-disk-image directly ourselves with our parameters and say to the VM : boot this image and not the usual storeImage : we rarely do this, except in makeEc2Test (which is currently broken due to QEMU changes, I submitted #187855 to fix it, but amazon-init seems broken for now).

So, my question is: what do we want to test in (2) that we do not in (1) ?
Some options are obviously not covered, but a simple answer would be : we can create more knobs in qemu-vm to expose them, the ultimate knob being replacing the whole image.
Note that there are definitely some difficult API design decisions as fileSystems is generated carefully and passing an arbitrary image would require to scrap everything I guess and relies on sound image generation.
That being said, once we have consensus on goals, my plan is more or less the following one:

Create an intermediate mechanism called makeTestFromImage which would be a lower-level primitive for makeEc2Test and even makeTest (but not right right now I guess, because the way QEMU VM modules is architectured, it is not super easy to achieve).
Rewrite EC2/OpenStack tests on the top of it.
Ideally, I'd like to create new image tests such as Proxmox image tests, using vma extract && qemu-img convert for example.
Test make-disk-image over the cartesian product of all options we are interested in.

I would also be interested into exercising limits of cptofs as there are some bugs we have seen on those, on multiple platforms.
What do you say?


🐛 [firebase_auth] The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.

Bug report
Describe the bug
I have integrated Firebase into my Flutter Android app and have been using Firebase Authentication successfully for more than a month. However, today when trying to verify a user's phone number using the phone authentication method, I started receiving the following error:
E/FirebaseAuth(31189): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17006 null
D/FirebaseAuth(31189): Invoking original failure callbacks after phone verification failure for +xxxxxx, error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.
Steps to reproduce

Initializing firebase and FirebaseAppCheck
Putting the phone number for testing ( which is added in the console and have been using it for a month )
Getting the error i mentioned above.
On firebase App check metrics, the requests for authentication are considered Verified requests.

Expected behavior
I expect the phone verification process to work smoothly
Sample project
https://github.com/openclues/firebaseProblem/blob/main/SendOtp
Additional context

I have verified that the provided API key and SHA-1/SHA-256 fingerprints in my Firebase project settings match those from my Flutter app.
The provider is enabled on Firebase console
Usign real device.
The same projectId so, the application not trying to interact with another firebase project.

Flutter doctor
Click To Expand
[✓] Flutter (Channel stable, 3.7.8, on Microsoft Windows [Version 10.0.25905.1000], locale en-US)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Chrome - develop for the web
[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.11)
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.80.1)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Click To Expand
Dart SDK 2.19.5
Flutter SDK 3.7.8
Taafaa 1.1.0+15

dependencies:
- animate_do 3.0.2 [flutter]
- autoscale_tabbarview 1.0.2 [flutter]
- cached_network_image 3.2.3 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- card_swiper 2.0.4 [flutter]
- change_app_package_name 1.1.0
- connectivity_plus 4.0.1 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- cupertino_icons 1.0.5
- dart_code_metrics 5.7.5 [analyzer analyzer_plugin ansicolor args collection crypto dart_code_metrics_presets file glob html http meta path platform pub_updater source_span uuid xml yaml]
- device_info_plus 9.0.2 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32 win32_registry]
- easy_localization 3.0.1 [flutter shared_preferences intl args path easy_logger flutter_localizations]
- equatable 2.0.5 [collection meta]
- firebase_app_check 0.1.5+1 [firebase_app_check_platform_interface firebase_app_check_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.7.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.15.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_messaging 14.4.0 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flag 6.0.0 [flutter flutter_svg enum_to_string]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_bloc 8.1.2 [flutter bloc provider]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_iconly 1.0.2 [flutter]
- flutter_local_notifications 14.1.1 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_native_splash 2.2.19 [args flutter flutter_web_plugins js html image meta path universal_io xml yaml]
- font_awesome_flutter 10.4.0 [flutter]
- google_fonts 4.0.3 [flutter http path_provider crypto]
- http 0.13.5 [async http_parser meta path]
- image_picker 1.0.0 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- in_app_purchase 3.1.7 [flutter in_app_purchase_android in_app_purchase_platform_interface in_app_purchase_storekit]
- intl 0.17.0 [clock path]
- page_transition 2.0.9 [flutter]
- permission_handler 10.4.1 [flutter meta permission_handler_android permission_handler_apple permission_handler_windows permission_handler_platform_interface]
- pin_code_fields 7.4.0 [flutter]
- pretty_qr_code 2.0.3 [flutter qr]
- print_remover 1.0.1
- provider 6.0.5 [collection flutter nested]
- purchases_flutter 5.3.0 [flutter freezed_annotation json_annotation]
- share_plus 7.0.2 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shared_preferences 2.1.0 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sliver_header_delegate 0.0.5 [flutter]
- spring 2.0.2 [simple_animations supercharged universal_platform vector_math flutter]
- thawani_payment 0.0.6 [http webview_flutter webview_flutter_android webview_flutter_wkwebview flutter]
- url_launcher 6.1.11 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- whatsapp_unilink 2.1.0

dev dependencies:
- flutter_launcher_icons 0.13.1 [args checked_yaml cli_util image json_annotation path yaml]

transitive dependencies:
- _fe_analyzer_shared 61.0.0 [meta]
- _flutterfire_internals 1.3.4 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.13.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- analyzer_plugin 0.11.2 [analyzer collection dart_style pub_semver yaml]
- ansicolor 2.0.1
- archive 3.3.7 [crypto path pointycastle]
- args 2.4.0
- async 2.10.0 [collection meta]
- bloc 8.1.1 [meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- cached_network_image_platform_interface 2.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.2 [flutter flutter_cache_manager cached_network_image_platform_interface]
- characters 1.2.1
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- cli_util 0.4.0 [meta path]
- clock 1.1.1
- collection 1.17.0
- connectivity_plus_platform_interface 1.2.4 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+4 [js meta]
- crypto 3.0.2 [typed_data]
- csslib 1.0.0 [source_span]
- dart_code_metrics_presets 1.8.0
- dart_style 2.3.2 [analyzer args path pub_semver source_span]
- dbus 0.7.8 [args ffi meta xml]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- easy_logger 0.0.2 [flutter]
- enum_to_string 2.0.1
- fake_async 1.3.1 [clock collection]
- ffi 2.0.1
- file 6.1.4 [meta path]
- file_selector_linux 0.9.2 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.0 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3 [cross_file file_selector_platform_interface flutter]
- firebase_app_check_platform_interface 0.0.9+1 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_app_check_web 0.0.11+1 [_flutterfire_internals firebase_app_check_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.16.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.6.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core_platform_interface 4.8.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.6.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_messaging_platform_interface 4.3.0 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.3.0 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- flutter_blurhash 0.7.0 [flutter]
- 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_localizations 0.0.0 [flutter intl characters clock collection js material_color_utilities meta path vector_math]
- flutter_plugin_android_lifecycle 2.0.15 [flutter]
- flutter_svg 1.1.6 [flutter meta path_drawing vector_math xml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- glob 2.1.2 [async collection file path string_scanner]
- html 0.15.4 [csslib source_span]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.0.17 [archive meta xml]
- image_picker_android 0.8.7+3 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 2.2.0 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.8 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.8.0 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- in_app_purchase_android 0.3.0+10 [collection flutter in_app_purchase_platform_interface json_annotation]
- in_app_purchase_platform_interface 1.3.4 [flutter plugin_platform_interface]
- in_app_purchase_storekit 0.3.6+4 [collection flutter in_app_purchase_platform_interface json_annotation]
- js 0.6.5 [meta]
- json_annotation 4.8.1 [meta]
- matcher 0.12.13 [meta stack_trace]
- material_color_utilities 0.2.0
- meta 1.8.0
- mime 1.0.4
- nested 1.0.0 [flutter]
- nm 0.5.0 [dbus]
- octo_image 1.0.2 [flutter flutter_blurhash]
- package_config 2.1.0 [path]
- path 1.8.2
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- path_provider 2.0.15 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- path_provider_android 2.0.24 [flutter path_provider_platform_interface]
- path_provider_foundation 2.2.1 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.10 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.6 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.7 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- permission_handler_android 10.3.0 [flutter permission_handler_platform_interface]
- permission_handler_apple 9.1.3 [flutter permission_handler_platform_interface]
- permission_handler_platform_interface 3.11.0+1 [flutter meta plugin_platform_interface]
- permission_handler_windows 0.1.3 [flutter permission_handler_platform_interface]
- petitparser 5.1.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.4 [meta]
- pointycastle 3.7.3 [collection convert js]
- process 4.2.4 [file path platform]
- pub_semver 2.1.4 [collection meta]
- pub_updater 0.3.0 [http json_annotation process pub_semver]
- qr 3.0.1 [meta]
- rxdart 0.27.7
- share_plus_platform_interface 3.2.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences_android 2.1.2 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.2.0 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.2.0 [flutter plugin_platform_interface]
- shared_preferences_web 2.1.0 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.2.0 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- simple_animations 3.1.1 [flutter supercharged pedantic]
- sky_engine 0.0.99
- source_span 1.9.1 [collection path term_glyph]
- sqflite 2.2.8+4 [flutter sqflite_common path]
- sqflite_common 2.4.5 [synchronized path meta]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- string_scanner 1.2.0 [source_span]
- supercharged 2.1.1 [supercharged_dart flutter]
- supercharged_dart 2.1.1
- synchronized 3.1.0
- term_glyph 1.2.1
- test_api 0.4.16 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.9.2 [path]
- typed_data 1.3.1 [collection]
- universal_io 2.2.0 [collection meta typed_data]
- universal_platform 1.0.0+1
- url_launcher_android 6.0.26 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.3 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.4 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.16 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.6 [flutter url_launcher_platform_interface]
- uuid 3.0.7 [crypto]
- vector_math 2.1.4
- watcher 1.0.2 [async path]
- webview_flutter 4.0.7 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]
- webview_flutter_android 3.5.2 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 2.2.0 [flutter meta plugin_platform_interface]
- webview_flutter_wkwebview 3.3.0 [flutter path webview_flutter_platform_interface]
- win32 4.1.4 [ffi]
- win32_registry 1.1.0 [ffi win32]
- xdg_directories 1.0.0 [meta path process]
- xml 6.2.2 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]```

</details>

---

Please help. Same issue

Please help. Same issue

What is the exact error you got?

@openclues Initially it was working correctly, but it gives the below error. Even the earlier production build is giving same error.
I thought something is wrong in the project, so deleted that project, created a new one, but it's still same.
Also tried downgrading flutter to 3.3.3 & 3.7.12, doesn't work. Neither downgrading the plugins work.
E/FirebaseAuth(24002): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17006 null
D/FirebaseAuth(24002): Invoking original failure callbacks after phone verification failure for +96512345678,
error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.

  firebase_core: 2.14.0
  firebase_auth: 4.6.3
  firebase_ui_auth: 1.4.3

Doctor summary (to see all details, run flutter doctor -v): [✓] Flutter (Channel stable, 3.10.6, on macOS 13.3.1 22E772610a darwin-arm64, locale en-IN) [✓] Android toolchain - develop for Android devices  Android SDK version 32.1.0-rc1) [✓] Xcode - develop for iOS and macOS (Xcode 14.3) [✓] Chrome - develop for the web [✓] Android Studio (version 2021.3) [✓] VS Code (version 1.80.1) [✓] Connected device (3 available) [✓] Network resources
Also I get IntegrityService : linkToDeath , but this is something I used to get earlier also, that's why I created a new project and never enabled integrity services but still no luck.
Please help, we were supposed to go live and at end moment this is happening. Also production is not working anymore.
CC - @nilevars

@openclues Initially it was working correctly, but it gives the below error. Even the earlier production build is giving same error.
I thought something is wrong in the project, so deleted that project, created a new one, but it's still same.
Also tried downgrading flutter to 3.3.3 & 3.7.12, doesn't work. Neither downgrading the plugins work.
E/FirebaseAuth(24002): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17006 null
D/FirebaseAuth(24002): Invoking original failure callbacks after phone verification failure for +96512345678,
error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.

  firebase_core: 2.14.0
  firebase_auth: 4.6.3
  firebase_ui_auth: 1.4.3

Doctor summary (to see all details, run flutter doctor -v): [✓] Flutter (Channel stable, 3.10.6, on macOS 13.3.1 22E772610a darwin-arm64, locale en-IN) [✓] Android toolchain - develop for Android devices Android SDK version 32.1.0-rc1) [✓] Xcode - develop for iOS and macOS (Xcode 14.3) [✓] Chrome - develop for the web [✓] Android Studio (version 2021.3) [✓] VS Code (version 1.80.1) [✓] Connected device (3 available) [✓] Network resources
Also I get IntegrityService : linkToDeath , but this is something I used to get earlier also, that's why I created a new project and never enabled integrity services but still no luck.
Please help, we were supposed to go live and at end moment this is happening. Also production is not working anymore.
CC - @nilevars

Yes, That is exactly the same problem.

@openclues Initially it was working correctly, but it gives the below error. Even the earlier production build is giving same error.
I thought something is wrong in the project, so deleted that project, created a new one, but it's still same.
Also tried downgrading flutter to 3.3.3 & 3.7.12, doesn't work. Neither downgrading the plugins work.
E/FirebaseAuth(24002): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17006 null
D/FirebaseAuth(24002): Invoking original failure callbacks after phone verification failure for +96512345678,
error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.

  firebase_core: 2.14.0
  firebase_auth: 4.6.3
  firebase_ui_auth: 1.4.3

Doctor summary (to see all details, run flutter doctor -v): [✓] Flutter (Channel stable, 3.10.6, on macOS 13.3.1 22E772610a darwin-arm64, locale en-IN) [✓] Android toolchain - develop for Android devices Android SDK version 32.1.0-rc1) [✓] Xcode - develop for iOS and macOS (Xcode 14.3) [✓] Chrome - develop for the web [✓] Android Studio (version 2021.3) [✓] VS Code (version 1.80.1) [✓] Connected device (3 available) [✓] Network resources
Also I get IntegrityService : linkToDeath , but this is something I used to get earlier also, that's why I created a new project and never enabled integrity services but still no luck.
Please help, we were supposed to go live and at end moment this is happening. Also production is not working anymore.
CC - @nilevars

I am sorry, can i ask when this problem started ?

@openclues
It looks like it could be a server glitch as based on above reports, the same error is thrown in production environment as well, so I suggest you all to wait for some time and see if it starts working again or not.
As you mentioned you have already been using the plugin and it suddenly started to throw the error, that too, 17006 as null, it may not be specific to any plugin changes unless you upgraded your flutterfire plugins and then started to see the issue.
Also, see this and check if it helps in your case or not.

Well to specify everything in details.
Login/SignUp with OTP was working fine for all the selected countries, but suddenly I saw in OTP verification screen, I am getting an error like "The given Sign in provider for this Firebase project. Enable it in Firebase console, under sign in ...... ". I was pretty sure everything was turned on and set up was correctly done as it was working previously.
Then I read somewhere it's related to OAUTH client, I created a new firebase project, created a new app id & new signing key and it started working again.
Then I realised I have used same key to sign two different applications in playstore, which conflicted the keys and as soon as both the apps were live firebase started blocking the project logins for both Android & iOS.
Finally I unpublished both the apps with same key, created new firebase project, and published fresh apps, with new bundle ID & new UNIQUE signing keys for both the apps.
Strangely after this it started working again.
@openclues Maybe this way you can make your project work
But now it only works for Indian number, other countries still show the above error. So If it's working for one country it must work for other countries.
Also SMS region policy is set correctly to Allow the countries I am trying to. Also If I add whitelisted numbers for that country still it doesn't work. So something must be blocking from Firebase side. This is very crucial and we're stuck in this.
@darshankawar Please look into this once. And Thank you for your time.
CC - @nilevars

I have an issue when tested my app on Kuwaiti numbers, I get "The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, ..", even though it works perfectly on Egyptian phone numbers.
I tried setting Kuwait in settings under firebase authentication tab, and same error occurs.
Please help.

Removed the project.
Created a new project.
The problem is still the same Invoking original failure callbacks after phone verification failure for +96812341234, error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.

Looking at the error being received Invoking original failure callbacks after phone verification failure for +96812341234, error - The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section"., the first step is obviously to check if the given sign-in provider is really enabled and committed in the firebase console, because the error indicates that could be the reason.
I also suggest to reach out to firebase support because reading one of the comments, it says that the phone sign-in works for one number but not for other, so it may be an issue from server side, so I request everyone facing this issue to reach out to firebase support and see what they say.
https://firebase.google.com/support

Added ticket to Firebase Support team. let's see.

Hi there, I am facing the exact same issue. The sign-in provider is properly enabled in my Firebase project. I can confirm that it is not happening with all phone numbers. Phone numbers of some countries are working.
I hope this issue will be solved as soon as possible. We're losing new customers due to this issue.
@krishna700 Did you get any update from Firebase Support Team?

@isyedaliraza
Yes after writing couple of emails and describing the issue correctly they have fixed it.

Thank you for your quick response.
The project ID is ************ & Project Number is ************
Country code facing this issue (+965), KW
I believe the issue is not with OTP delivery, cause it's not even going to the delivery stage and rejecting beforehand.
Supporting point why I say this:-
Even if I add a whitelist number as ************, it shows the same error which I have attached the screenshot of the error from device & from my firebase
for your reference.
Please forward this github link to the concerned engineer. https://github.com/firebase/flutterfire/issues/11288 I have described everything in this link.
Even if I add a whitelist number of USA code, it doesn't work.
Only Indian numbers are working for both whitelisted and normal numbers
Also added the screenshot that the countries are allowed.
Initially I have done everything possible, starting with a new firebase project, removing published apps from stores, creating a new signing key, and a new app ID.
And if it was an issue from my development side, it won't work for Indian numbers also, so definitely we're good from the config side & code part.
I think something is blocking the requests to firebase. Also User Activity logging is enabled. App Check is disabled.
Hope you understand our concern. And provide a quick resolution for the issue.

@darshankawar Please close the issue

why ? You wrote this issue ?
maybe it is fixed for you. but it still not fixed with me.
Next time ask to close just issues you wrote bro.

@openclues My bad. I thought it's fixed from the firebase team for everyone. It's better to to contact Firebase. As definitely this is from their backend.
Also did you tried adding a whitelisted number, are you getting the same issue?

@openclues My bad. I thought it's fixed from the firebase team for everyone. It's better to to contact Firebase. As definitely this is from their backend.
Also did you tried adding a whitelisted number, are you getting the same issue?

I have sent them and still waiting.
Yes i am testing with whitelisted number and getting the same error.

Issue isn't solved for me, yet.

Firebse answered me.
According to the details that you kindly shared, the phone number that you reported is from Omen country, I must confirm that your case is not isolated, as we've received similar reports from other clients. This suggests an outage in our SMS service. Our expert Authentication team has been diligently working on investigating the matter.
Our priority at this moment is to identify the root cause of this issue and implement a suitable resolution as swiftly and effectively as possible. I assure you that our team is putting forth its best efforts to restore the service to its full functionality.
While the investigation is ongoing, I will ensure that you are promptly updated with any new information or progress we make in resolving this issue.
Should you have any further queries or require additional support during this time, please do not hesitate to reach out. It's my commitment to you to provide assistance to the best of my ability.
I thank you once again for your understanding and patience. Rest assured, we're doing everything in our power to address this concern promptly

@wellRoundedAppDev what region are you operating from? Have you tried reaching out to firebase support?
@openclues, it seems that the issue is indeed from firebase and not the plugin, I'm not sure if there's anything we can do from here


Get outgoing follow requests

Form

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Question
Hi,
I can't seem to find a way to get the current follow request that I made (request to follow private accounts, not yet accepted/denied).
The data is accessible with this url https://www.instagram.com/accounts/access_tool/current_follow_requests
but is it with this library?
Thank you

I'm looking for this too. Is there such a feature in the API?


Fix BLS12 G2PreparedGadget's AllocVar with a divisive twist

Description
When working in Aleo's new Marlin implementation, we need gadgets for SonicPC, in which one needs to prepare a G2 element on BLS12-377.
It appears that the following two allocated variables are different:

G2PreparedVar, via AllocVar on a G2Prepared
G2PreparedVar, via prepare_g2 on a G2Var

This seems to be because the AllocVar on G2Prepared is specific to a BLS12 pairing where G2 has a multiplicative twist (i.e., TwistType::M). And the same conversion does not work for a divisive twist.
The case for the multiplicative twist:

It interprets the ell_coeff as (a, b, c) and allocates (a/c, b/c) for the gadget case.
This works correctly:

in the native world, the ell function is to compute mul_014 over (a, bx, cy)
in the constraint world, the ell function is to compute mul_014 over (a/c, b/c x, y)

The case for the divisive twist:

It interprets the ell_coeff as (a, b, c) and wrongly allocates (a/c, b/c), which indeed should be (b/a, c/a).
This works incorrectly:

in the native world, the ell function is to compute mul_034 over (ay, bx, c)
in the constraint world, the ell function now computes mul_034 over (y, a/c x, 1) but it should be (y, b/a x, c/a)

There are multiple ways to fix: let the native follow the constraint, let the constraint follow the native, or let the AllocVar take care of the conversion. This PR does the last one, by making AllocVar implementation of G2PreparedVar aware of such difference.
We did not discover this bug before because we commonly use BLS12-381 (type-M), but not BLS12-377 (type-D).
This is related to https://github.com/AleoHQ/snarkVM/pull/317

One question: do we want to keep the tests in this PR? They require additional dev dependencies since ark-test-curves does not have BLS12-377 or G2 of BLS12-381.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

We did not discover this bug before because we commonly use BLS12-381 (type-M), but not BLS12-371 (type-D).

Do you mean BLS12-377 here?

We did not discover this bug before because we commonly use BLS12-381 (type-M), but not BLS12-371 (type-D).

Do you mean BLS12-377 (type D) here?

Yes. Thanks for catching this.

Thanks for the fix! I'm surprised this doesn't result in a cyclic dependency, as ark-bls12-377 itself depends on r1cs-std when the r1cs feature is on. It might be worthwhile to move the test to ark-curve-constraint-tests, so that it's exercised directly for bls12-377 always?

Good idea. Then my plan is as follows: drop the test from this PR and make a new PR in ark-curve-constraint-tests that adds this test.

Sounds good!

Changes have been made. A separate PR will be created in arkworks-rs/curves


Minor fixes

Hello!
Stumbled upon some minor issues with a DPI scaled Maya UI, I believe the After is the intended appearance.

Before
After

The way I deal with this personally is by wrapping any pixel value, such as setFixedWidth(10) in a conversion function, such as MQtUtil.dpiScale. For brevity, I typically call this function px such that we end up with something readable, that is appropriately sized at any scale.
widget.setFixedWidth(px(10))

There are probably one or more pixel values I've missed, and I spotted a few embedded in stylesheets as well. Those will need wrapping as well for a fully scalable UI.
I've also added an auto-load of a plug-in that was assumed to be loaded when generating the control rig, namely mayaHIK. I was planning on adding more commits to this if/as I stumble upon more things. Generating a larger pull-request.
Unless you prefer smaller pull-request? In which case I can leave this as-is, and continue on another branch.

Nice catch, thanks, Markus!


Stelpro Thermostat - Not see humidity sensor

Hello,
Rpi 3 + usb dongle zigbee
Home assistant - Last release
MQTT and zigbee2MQTT installed
I'm paired 9 Stelpro Thermostat SMT402. All work great, but i'm not showing the hmidity sensor in Home Assistant.
state from zigbee2MQTT send :
{
    "humidity": 45,
    "linkquality": 108,
    "local_temperature": 24,
    "occupied_heating_setpoint": 5,
    "operation": "idle",
    "pi_heating_demand": 0,
    "running_state": "idle",
    "system_mode": "heat"
}

I can't seeing sensor from humidity for all my Stelpro Device.
Try add this on my configuration and the sensor not have value :
- platform: "mqtt"
    state_topic: "zigbee2mqtt/0xf8f005fffff961f4"
    availability_topic: "zigbee2mqtt/bridge/state"
    unit_of_measurement: "%"
    device_class: "humidity"
    value_template: "{{ value_json.humidity }}"

What is wrong ?
Thank you

Why are you not using auto-discovery?

Maybe there is a problem with the discovery message, not the state one. Can you check how your discovery messages look like when adding the integration?

No, how i can check that ? I checked in logs... but i'm nothing...

in Dashboard  for stelpro, i'm see that

By reading https://www.zigbee2mqtt.io/devices/SMT402.html it seems that the humidity is not exposed as a sensor for this. I don't think this issue is for the add-on repo. Maybe try opening an issue here: https://github.com/Koenkk/zigbee2mqtt/issues for more support.


pull request for e2e test at 12/27/2016 19:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[BDGR-170] [WIP] Load continuity into vMix and VTs into OBS

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 21.74%. Comparing base (8f01909) to head (2de9c94).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #385      +/-   ##
==========================================
- Coverage   22.09%   21.74%   -0.36%
==========================================
  Files          95       95
  Lines        3620     3620
  Branches      604      604
==========================================
- Hits          800      787      -13
- Misses       2670     2681      +11
- Partials      150      152       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Too much (unnecessary) trailing going on

For example...
$ tpl -g "time(test1),statistics,halt" samples/fib.pl
fib(35)=14930352 PASSED
% Time elapsed 21.430s, 89582114 Inferences, 4.180 MLips
Goals 89582115, Matches 68948871.
Max frames 29860704, choices 1, trails 59721404, slots 89582107, heap pages 1.
Active frames 29860705, choices 0, trails 59721405, slots 89582107, heap pages 1.
Backtracks 39088167, TCOs:0, Recovered frames: 0, slots: 0, Queue: 0

Some improvement, 33% faster...
$ tpl -g "time(test1),statistics,halt" samples/fib.pl
fib(35)=14930352 PASSED
% Time elapsed 13.547s, 89582114 Inferences, 6.613 MLips
Goals 89582115, Matches 68948871.
Max frames 29860704, choices 1, trails 29860702, slots 89582107, heap pages 1.
Active frames 29860705, choices 0, trails 29860703, slots 89582107, heap pages 1.
Backtracks 39088167, TCOs:0, Recovered frames: 0, slots: 0, Queue: 0

Currently Logtalk doesn't run with these changes, so more to be done.

Done for now


add sound with cli

I am starting DJV from a script to play an image sequence:
djv.exe .\seq.1001.jpeg -speed 25 -in_out 1001 1200
Can I specify a WAV sound file to play with sequence?

Hi, separate audio files are not currently supported, but I am working on it and hope to include the functionality with the next release.

Thanks, keeping fingers crossed. This will be huge feature

Do you have any estimation when can we expect this feature ?
thanks

I'm currently working on rewriting the playback "engine" (which includes the sound support), and then I need to integrate that work with DJV, so a few months at least...


proposal: testing: allow importing API from _test.go functions in other tests

What version of Go are you using (go version)?
1.14
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
GOOS="darwin"
GOARCH="amd64"
What did you do?
In order to make it visible for tests that are located on different packages, I had to move a common database mock to a non _test.go file.
You can view it here:
https://github.com/fernandomachado90/go-transactions/blob/master/core/database_mock.go
What did you expect to see?
I wanted to be able to import and use common _test.go functions on different packages.
What did you see instead?
In order to avoid code duplication and reuse the same mock code in other places I have to make it available outside a _test.go file, which works but seems odd.

It seems to me that using a common package is the right approach.
Presumably when we import a package we don't normally want to be able to refer to testing functions.  Even from test code, we normally want to use the standard package API, not a testing API.  So if we were to support this, we would need some additional mechanism to say "import the testing API for package foo".  But few people would ever use that mechanism.
Since the need is unusual, and there is a way to do it by using a shared package, I don't see a compelling reason to add this feature.

Hi @ianlancetaylor, even when I use a shared package I still have to include test-only code along with production code so it can be seen and used by other packages, which seems like a bad practice.

duplicate of the previously declined #31135 ?

It is common for packages to expose standard API that is mainly useful for testing.
That just goes in the non-_test.go files.
This does in fact appear to be a duplicate of #31135.

No change in consensus, so declined.
— rsc for the proposal review group


convert Booster model into LGBMClassifier

Description
I used mmlspark.LightGBMClassifier to train a model and saved it and then used lightgbm.Booster to load model, then I want to convert it into onnx model. For some reason, I need to convert Booster into LGBMClassifier before I am able to convert it to onnx.
The part of code snippet:
from lightgbm import Booster, LGBMClassifier

# first used mmlspark.LightGBMClassifier to train a model,
# then saved mode
# then used lightgbm.Booster to load model
bst = Booster(model_file='mmpspark_lightgbmclassifier_model.txt')

print('The type of model: ', type(bst))
# The type of model:  <class 'lightgbm.basic.Booster'>

# then need to convert Booster into LGBMClassifier

Please refer to https://github.com/microsoft/LightGBM/issues/1942#issuecomment-453975607.


Extend test coverage to preview site.

References #7.
This should help instill a bit more confidence when upgrading dependency versions, etc.

Yes, this has been roughly implemented (83% coverage.)


WIP: fix tests

The tests are not successful anymore due to new basic auth and change of permissions / locations in actinia-core deployment at actinia.mundialis.de. This PR tries to fix them again

added auth and user in interface init for tests

The fix for the basic auth by the tests is also needed by some endpoints which must not request authentication (/collections and /collections/{name}).


[WFLY-17616] Upgrade SmallRye Reactive Messaging to 4.4.0

https://issues.redhat.com/browse/WFLY-17616

/retest

@kabir This has a conflict.

@bstansberry 4.4.0 was released in the meantime so I have bumped to that. It now pulls in a bunch of opentelemetry instrumentation jars - I'll double check on email

@bstansberry https://github.com/wildfly/wildfly/pull/16330 needs the mentioned opentracing instrumentation jars. I have reworked how I include them to be in line with how #16330 uses them.
CC @jasondlee

I put the 'hold' label on this while we validate whether the #16630 roll-back to OTel 1.20 breaks this.  #16633 combines the two in order to validate this.


updated User management configuration settings

Hello @ayrotideysarkar,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This is a very good start, @ayrotideysarkar! Thank you.
Please remember to write in full, complete sentences including proper capitalization and punctuation. Also, remember to use existing documentation content as a guide when drafting new content. Many existing docs pages contain similar language that you should apply in your own drafts to ensure consistency.
Once you have this content fully drafted with the above guidelines in mind, I'll review the PR in full. Thanks!

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@cwarnermm  can you check and give feedback  for the changes I made?

Hi @ayrotideysarkar! Is this PR draft complete or are you planning on making additional updates?

Hi @ayrotideysarkar! Is this PR draft complete or are you planning on making additional updates?

it's not completed I will add some more details I just need your feedback before adding more details

Our team's process is to provide feedback when this PR is draft complete. Thanks!


endpoint: Set endpoint state to "ready" also after failure.

Set endpoint's state to "ready" also after failure, but make sure
endpoint's Status is not chnaged to "OK" in that case, so that cilium
API will return endpoint's state as "not-ready".
Move setting the endpoint's realized policy revision later to the
point when we know the build succeeded.
Fixes: #2069
Reported-by: Ian Vernon<EMAIL_ADDRESS>Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

Rebase to master.


Referenced link to the "Sample - gather.ps1" has not been tested on Windows 10

[Enter feedback here]

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

ID: af8c59c3-65e9-1e4c-f78d-8d2770e88690
Version Independent ID: 0d0b65d8-5026-8232-5658-561d88cc2065
Content: Simulate a Windows 10 deployment in a test environment (Windows 10) - Windows Deployment
Content Source: windows/deployment/deploy-windows-mdt/simulate-a-windows-10-deployment-in-a-test-environment.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

Points worth of note:

https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/simulate-a-windows-10-deployment-in-a-test-environment?source=docs
(2.) Download the sample Gather.ps1 script from the TechNet gallery and copy it to a directory named C:\MDT on PC0001. (https://go.microsoft.com/fwlink/p/?LinkId=619361)
The go.microsoft.com URL redirects to https://gallery.technet.microsoft.com/Perform-a-standalone-MDT-227fdcd0
Last updated: 4/10/2014 (April 10, 2014) (!)
Also worth noting: https://docs.microsoft.com/en-us/teamblog/technet-gallery-retirement (TechNet Gallery Retirement): "We are retiring the TechNet Gallery. Make sure to back up your code. [Learn More]"

Also documented on the TechNet Gallery page:
Verified on the following platforms

Windows 10
No

Windows Server 2012
No

Windows Server 2012 R2
No

Windows Server 2008 R2
No

Windows Server 2008
No

Windows Server 2003
No

Windows Server 2016
No

Windows 8
Yes

Windows 7
Yes

Windows Vista
No

Windows XP
No

Windows 2000
No

This script is tested on these platforms by the author. It is likely to work on other platforms as well. If you try it and find that it works on another platform, please add a note to the script discussion to let others know.

GitHub search for related code: https://github.com/search?l=PowerShell&q="Gather.ps1"&type=Code
We might want to check if MDT Standalone operation could be an issue in Windows 10 deployment.

Hello,
I checked the content of gather.ps1, and the only thing it does is running ZTIGather.wsf script in debug mode.
As ZTIGather.wsf supports Windows 10 (https://github.com/tyglander/MDT/blob/master/ZTIGather.wsf), I do not see any problem with using it.
Thank you

@tim-toolman Please let us know if you still have any question regarding the issue you have raised initially.
The issue is being closed since your question seems to be answered. Feel free to re-open this issue if you feel that it hasn't been answered or that there are further suggestions to improve the documentation itself.
Thanks.


Correction for raw affiliation Ingénierie des Agro-polymères et Technologies Émergentes; Paris-Saclay Food and Bioproduct Engineering

Correction needed for raw affiliation Ingénierie des Agro-polymères et Technologies Émergentes; Paris-Saclay Food and Bioproduct Engineering
raw_affiliation_name: Ingénierie des Agro-polymères et Technologies Émergentes; Paris-Saclay Food and Bioproduct Engineering
new_rors: 0000n5x09;03gmkya61
previous_rors: 0000n5x09
works_examples: W3123751978
contact: d2f8d2a2309f286b7c7c9680373a5472:5187e7c721a8c276f40bf278c96450a907be @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


│Bug: AttributeError: 'GroupTreeQualityMetrics' object has no attribute 'mutations_per_sample'

Error in logging in mutations_per_sample loop exit. We should add some tests to catch these cases.

Fixed in #377


Refactor types module

Fixes #136
This PR organizes the types for each API endpoint into their own modules, matching the module structure in the base namespace.
Work that remains:

Factoring out modules in impls

Some open questions:

I maintained a flat namespace for the types using pub use to reduce churn. However, now that the types are properly modularized, I think it would be an improvement to remove pub use and access the types using module names instead. What do you think?

A few data structures are shared between chat, edit, and completion. As the latter two are deprecated and unlikely to be updated, I moved those data structures into chat to better express their future usage. Should they remain, or should they be moved into a common module?

Hi @sharifhsn ,
Thank you for this PR, you have organized the code really well!  So much less clutter - appreciate your work.  Adding comments for macros is nice touch!

Factoring out modules in impls

I think this is fine, otherwise it may get very fragmented. This can be revisited later if required.

I maintained a flat namespace for the types using pub use to reduce churn. However, now that the types are properly modularized, I think it would be an improvement to remove pub use and access the types using module names instead. What do you think?

I think  flat namespace should be fine for now without over-modularizing.

A few data structures are shared between chat, edit, and completion. As the latter two are deprecated and unlikely to be updated, I moved those data structures into chat to better express their future usage. Should they remain, or should they be moved into a common module?

Your judgement here is reasonable - going with the current APIs and future usage and not with deprecated ones. Looks good to me in this PR


Needs to remove references to UIWebView

you can no longer submit apps that use UIWebView (from december) so this needs to be changed to WKWebView!

UIWebView isn't used anymore. Have you made sure to update?

Hi @nnhubbard, when I pulled in the dependency with CocoaPods the other day it resolved to your last tagged release https://github.com/nnhubbard/ZSSRichTextEditor/releases/tag/<IP_ADDRESS> in November of 2014 which uses the UIWebView. So I think if you create a new tag/release it will resolve to the latest version version with the updated WkWebView code from go. Thanks in advance! 👍

Just don't use CocoaPods. We haven't ever updated that.


REPL/interactive mode for multiple queries

Right now, to do multiple queries in ayb, one must write ayb query <database> <query> for each query they want to execute in the database. Adding a REPL/interactive mode for multiple queries could help to execute multiple queries easier.
For example, instead of doing this:
sugui@yukari:~$ ayb client query sugui/test-from-cli "create table numbers(spelling varchar, num integer);"

Rows: 0
sugui@yukari:~$ ayb client query sugui/test-from-cli "insert into numbers values ('seven', 7)"

Rows: 0
sugui@yukari:~$ ayb client query sugui/test-from-cli "select * from numbers"
 spelling | num
----------+-----
 seven    | 7

Rows: 1

It could exist something like a client interactive option to enter an interactive mode where you can simply start to write queries into the same database.
sugui@yukari:~$ ayb client interactive sugui/test-from-cli
sugui@sugui/test-from-cli> create table numbers(spelling varchar, num integer);

Rows: 0
sugui@sugui/test-from-cli> insert into numbers values ('seven', 7);

Rows: 0
sugui@sugui/test-from-cli> select * from numbers;
 spelling | num
----------+-----
 seven    | 7

Rows: 1
sugui@sugui/test-from-cli> ^C
sugui@yukari:~$

This is an improvement I told @sofiaritz about. She told me I could open an issue for that, so here it is :)

Thank you for this excellent idea, @Suguivy! :) I would love to get this feature into ayb. Your proposal looks great to me. Two thoughts on this implementation

It looks like we can rely on rustyline do do the heavy lifting of reading a line of input with support for history, hotkeys, etc.
Can you or @sofiaritz think of any reason why we need to give it its own CLI command? For example, do we want ayb client interactive sugui/test-from-cli  with an explicit interactive command, or should it be ayb client query sugui/test-from-cli, and if there's no query at the end of this command, it implicitly goes into interactive mode?

I'm quite excited about this idea, and would love to either help you contribute it if you wanted to write the code, or to write it and get your feedback on an early implementation. (And no problem if you wanted to share the idea but not more than that.) Do you have a preference?

Thank you for the response @marcua! I will reply now to the two points you highlighted:

I think that the rustyline library you linked to, is a good choice to automatically manage things like hotkeys and history. Another important thing is, do we want to store the history in a file to use it on proper executions? In my opinion it's a good idea, to allow revisiting past queries.

I think that it can be a good idea to use the same ayb client query <database> command without any query to automatically enter the interactive mode. We don't really need any special command for that, but I think we should document it in the description of the command when using the --help flag.

And yes, I'd like to write the feature! It's been a while since I don't code in Rust and maybe my experience in the language is not so broad, but I'll try my best. I don't have many time because of work but I think it's not so hard to implement, so I'd be pleased to contribute. 😊

I agree with @Suguivy points, although the persistent query history may be complex to implement (should the history be global or db-specific? how do we allow users to disable it? what about logging into a different instance, how should history react to that? etc).
Re: contributing. Feel free to ask me any questions you may have or any problems that may arise while implementing this feature in Matrix :)
No pressure though :p

Hooray @Suguivy and thank you @sofiaritz! It sounds like rustyline, ayb client query <database> with no query, and a --help update is what we'll need. To @sofiaritz 's point, supporting saved history is helpful but likely complicated experience-wise, so perhaps in the v1 we can benefit from rustyline's history within a session, but not across sessions (no need to save to a file).
It's wonderful you'd like to contribute code. :) If you end up not having enough time, etc., just let us know and we can jump in to help, since this feature is a great idea! In terms of getting started:

All/almost all of the changes are likely to be in https://github.com/marcua/ayb/blob/main/src/bin/ayb.rs
Around this part of the code you can make query be not required, and update the --help text.
This region of the code is where you can see if query is missing, and if so, add the rustyline loop.

I'm grateful for your submitting this issue, and excited at the prospect of your first contribution. Thank you so much, and thank you to @sofiaritz for being so welcoming! :)

Thank you again for this excellent idea and for your code contribution @Suguivy! I've submitted and merged #292, which is a follow-on to the code. I ran into similar issues with you on error types, so I didn't implement the ? recommendations I initially made. The PR is mostly cargo fmt and cargo clippy with some additional clarifications of error messages and an update to the README since we can now show off our cool new interactive mode.
I hope you find ayb useful, and that you feel welcome to contribute to the project in the future. Your feedback so far has been wonderful, and I look forward to more of it! :)


Add a virtual destructor for the ClientContext::GlobalCallbacks.

This should be a no-op change.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Please update copyrights: (from the sanity test):
src/core/census/initialize.c modified 2016 but copyright only extends to 2015
src/cpp/client/client_context.cc modified 2016 but copyright only extends to 2015
src/cpp/server/server.cc modified 2016 but copyright only extends to 2015
tools/jenkins/build_interop_stress_image.sh modified 2016 but copyright only extends to 2015
tools/jenkins/grpc_interop_stress_cxx/Dockerfile modified 2016 but copyright only extends to 2015
tools/jenkins/grpc_interop_stress_cxx/build_interop_stress.sh modified 2016 but copyright only extends to 2015
tools/jenkins/run_interop_stress.sh modified 2016 but copyright only extends to 2015
tools/run_tests/run_stress_tests.py modified 2016 but copyright only extends to 2015

The copyrights for the files that I modified are updated. PTAL

Failing tests (all in gcov) look to be a problem with the infrastructure. In console log there is:
SUCCESS: All tests passed
but then:
error response from daemon: lstat /var/lib/docker/aufs/mnt/45c25c967a4c5b2fd339bfc5f67a3b497bad04515eef953aa8553f66edde6b23/var/local/git/grpc/report.xml: no such file or directory
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Finished: FAILURE
Will merge.


Lab2 Bubble, Insertion, Merge Sorting

Fixes #188
Review of colleague's PR #
Changes proposed in this PR:

Add bubble sort
Test bubble sort
Add insertion sort
Test insertion sort
Add merge sort
Test merge sort

Hi @juliaogris, would you be able to help me with resolving these problems?
Should I keep these sorting algorithms in seperate folders or should they all be in one file? I am not sure what to do here or how to call them in a way that will be accepted.
Or should there only be the more complex of the algorithms in the given file?
Thanks
-Cameron


Using websocket to get variables

The current web socket API is not documented and uses Firebase authentication tokens.
In order to have variables available in Companion we need add a publicly available and documented web socket that uses the same authentication method Authorization: Bearer YOUR_API_KEY
Events (thinking out loud):

Timer changes (start, stop, reset, ...)
Message changes (show, hide, color, text, ...)
Blackout (true, false)

What time/date format works best for Companion? Will ISO strings work? "2021-12-03T06:52:14.141Z"
In response to:

@estilles @nacalai creator of stagetimer.io here. Sorry for reviving this thread 😅
Currently the API does not return values. Internally we use web sockets. How could we make values like message text or current time available as variables in Companion?

Hey Lukas! We spoke briefly via email a few weeks ago. I've been meaning to send you and Liz a message regarding adding feedbacks and variables to the module.
There're many ways to tackle this, but since you're already using web sockets internally, that might be the way to go. I guess my questions are:

Do you have the web sockets API documented?
Does is use any sort of authentication (like Room ID and API Key)?

If the answers to these questions are yes, then we can definitely use web sockets to add feedbacks and variables to the module.
This is a separate topic though. We should probably create a separate issue.
Originally posted by @estilles in https://github.com/bitfocus/companion-module-hermann-stagetimerio/issues/1#issuecomment-985256752

In order to have variables available in Companion we need add a publicly available and documented web socket that uses the same authentication method Authorization: Bearer YOUR_API_KEY

That would be great! I'm assuming the module will stop using the REST API, and this new web sockets API will will provide the ability to both trigger Stagetimer actions and receive state/feedbacks as well. Correct?
Is this new web sockets API currently on your roadmap?

Events (thinking out loud):

Timer changes (start, stop, reset, ...)
Message changes (show, hide, color, text, ...)
Blackout (true, false)

Definitely. I can probably think of a few more.

This new web sockets API will provide the ability to both trigger Stagetimer actions and receive state/feedbacks as well. Correct?

Should not be too difficult to implement all endpoints as events. So yes.

Is this new web sockets API currently on your roadmap?

It is now ;)

Definitely. I can probably think of a few more.

By all means, please :)

That's great news. Please let me know when you have an API I can use to test and update this module.
Right now your REST API provides the ability to:

start/stop/toggle/reset/flash the current timer in a room
select the next/previous timer in a room
"tweak" add/substract time from the current timer in a room
toggle blackout on/off the timer in a room
ping a room
start/stop/toggle/reset/flash a specific timer
set a specific timer as the current timer
show/hide/toggle/flash a message in a room

The following could be useful:
Settings

Hide Logo
Hide progress bar
Logo size
Logo position: top left/top center/top right/center left/center/center right/bottom left/bottom/center/bottom right
Set timer font/size
Set message font/size
Set text to default/high contrast/inverted/shadow
Set text to default/white/black/green screen/blue screen/corporate/parchment/crowd/pencils/stars/streets

Timers

Set timer title/extra
Set timer trigger mode: manual/linked/schedule/until
Set timer Duration
Set timer wake-up time (yellow/red)
Show/hide/toggle title

Messages

Set message text
set message color white/green/read
Set/toggle text attributes: bold/case

It would be nice to have to ability to retrieve the state of the following:

For Feedbacks and variables

logo show/hide state
progress bar show/hide state
room blackout state
timer start/stop state
message show/hide state

Additional variables

Timer title/extra
Timer time remaining
Message text

I'm sure I'm missing something. If I remember I'll update this thread.

@estilles I'll get back to you as soon as I have time to work in this. Probably early January 👍

Sounds good @lhermann. I'll be standing by.

Sounds good @lhermann. I'll be standing by.

Can I help you working on this?

Hey @estilles, sorry for the delay here. I had some personal things coming in between. The topic is till top 2 on our priority list.

@lhermann! Great to hear from you. I was out sick for a while as well at the beginning of the year. I'm back now, so will just stand by for your updates.

Following this project with interest!
+1 to get countdown timer variables back into Companion so a countdown clock and feedback colors can be added to a button.

@davidjoshuaford I did not forget about this. stagetimer.io became a bit more propular than I expected so I'm knee-deep into scaling right now which unfortunately took priority.

Great to hear of its success! We used it on a live broadcast over the weekend and it kept our east coast and west coast studios in sync.
Would love to see ST feedback coming into Companion so that buttons can be triggered by a ST producer.
ie when a Stage Timer producer starts a timer, it presses a button to switch AUX outputs, play hyperdeck, mutes a mic etc. You could essentially build program cues around it and automate a ROS.

@lhermann I'm more than happy to continue helping out whenever you're ready.

New API is released including a publicly available websocket: https://stagetimer.io/docs/api-v1/

@estilles let me know if I can help you


Restart cannot be accessed after modifying the html

Hi，I  modify the html（just add a character），and then i run “docker-compose restart” ，all the container is running ，but the port 8000 cannot be accessed .
Have you encountered such a problem?

Report an error：
“”503 Service Unavailable
No server is available to handle this request.“”


Add vendors Fivetran and Databricks

- name: 'Fivetran'
  source: 'https://fivetran.com/docs/logs/cloudwatch/setup-guide'
  accounts: ['834469178297']
- name: 'Databricks'
  source: 'https://docs.databricks.com/administration-guide/account-settings/aws-accounts.html'
  accounts: ['414351767826']

Resolved by #469


intellisense for Python not working

I tried several options and solutions to get IntelliSense to work with Python on VS Code, but none worked.

/extPython


docker-compose tutorial requires modifications to deploy app

Problem description
I have been following the instructions in the "Get started with Docker Compose" tutorial and found that I needed to modify the instructions slightly to get the app to deploy properly. Two modifications are needed:

If I follow the instructions as-is to create the contents of composetest/ and then run docker-compose up, I get the following error message:

$ docker-compose up
Creating network "composetest_default" with the default driver
Creating composetest_redis_1
Creating composetest_web_1
Attaching to composetest_redis_1, composetest_web_1
redis_1  | 1:C 20 Apr 13:32:52.515 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
web_1    | python: can't open file 'app.py': [Errno 2] No such file or directory
composetest_web_1 exited with code 2

As suggested at this issue report for Docker Compose, it seems that there's some conflict between the volumes array in docker-compose.yml and the ADD instruction in the Dockerfile. I've fixed this by commenting out the volumes section in docker-compose.yml (lines 7 and 8).

Although the tutorial says that the app will be visible at http://<IP_ADDRESS>:5000/, this doesn't resolve for me. Instead I have to find the IP address of my Docker machine with docker-machine ip and then open http://DOCKER_MACHINE_IP:5000/. This is similar to the instructions for Docker Machine on a Mac, but I am on Windows.

The tutorial should be updated so that it is clear when these steps must be taken to run the given code.
Problem location
The problem is located here: Getting started with Docker Compose
Project version(s) affected
I am running Docker on Windows 7. Here is information about my versions of Docker and Docker Compose:
$ docker version
Client:
 Version:      17.05.0-ce-rc1
 API version:  1.28 (downgraded from 1.29)
 Go version:   go1.7.5
 Git commit:   2878a85
 Built:        Wed Apr 12 19:43:25 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.04.0-ce
 API version:  1.28 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Wed Apr  5 18:45:47 2017
 OS/Arch:      linux/amd64
 Experimental: false

$ docker-compose version
docker-compose version 1.11.2, build f963d76f
docker-py version: 2.1.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

Suggestions for a fix
I'm not sure exactly when these steps must be taken, but the tutorial should make it clear when they must be done to deploy the app.

Assigning to @gbarr01 to verify issue

Hi, @morrisalp, the issue you reference seems different. In (#1616), the user cannot mount a local volume from a remote machine. I don't believe this is what you are experiencing.
I wonder if you problem is closer to #3157? If so, have you tried restarting/recreating your VM?


Add url-tvg and x-tvg-url fields to m3u

I was setting up a new Android TV box and realized that when setting up xteve in TiViMate, I only needed to input the m3u address, it didn't have to ask me for the xmltv address.
So it turns out that xteve adds two fields to the m3u that seem to make finding the xmltv automatic in some iptv clients. Would be nice to have those fields in dizquetv's xmltv to wield this power.
#EXTM3U url-tvg="http://<IP_ADDRESS>:35500/xmltv/xteve.xml" x-tvg-url="http://<IP_ADDRESS>:35500/xmltv/xteve.xml"

@vexorian Is this going to get pushed to 0.0.70 instead?  I didn't see this in the changelog for 0.0.69, nor do I see this in my M3U when using 0.0.69.

Seems small enough to be allowed in 1.0.2

Isn't 1.0.2 only for bugfixes?  This reads like an enhancement to me.

The spirit of the rule is to avoid features that could break the release or features that would break compatibility with the api library or features that require new documentation. This is neither of them.


[Storage Blobs Service] fix bug in blob tags

Would be nice if you could reference the issue or connect the PR to the issue.
Or provide some description to the PR about the solution strategy


Add template for proposals

As discussed in this week's meeting, add a template for people to use to submit proposals so that they are more accessible for people to compare.

#13 creates a folder called proposals and perhaps that's where these changes should land with a link in the existing README.md

Thanks for putting this together @jdolitsky. LGTM


can you please provide an example of using a trained model to make prediction given (fake) live streamed data

Hi,
Can you please provide an example of using a trained model to make prediction given (fake) live streamed data?
For example, suppose I used the qrun to run the LightGBM model with workflow_config_lightgbm.yaml. Then the fitted model will be saved. Suppose I have live stream data for csi300, I can append the live data for today to the existing data in Qlib to have a data frame which is sufficient for the model to calculate the features for making prediction, e.g., the ones in Alpha158.
Is it possible to use the dataframe in memory to update the features in Alpha158 and then use the LGBModel.predict() to generate prediction under the current code? If so, can you please give an example?
Thanks!

@wan9c9
Hi, here is an example that you can serve model  and update predictions daily.

You should update data in Qlib's database. https://github.com/microsoft/qlib#automatic-update-of-daily-frequency-data-from-yahoo-finance
After the data updated, you can follow this example to update predictions daily https://github.com/microsoft/qlib/blob/main/examples/online_srv/update_online_pred.py

Currently, updating data in memory directly is not supported.

Thanks, I’ll look into it!
…
On Mon, Mar 7, 2022 at 4:33 AM you-n-g @.> wrote: @wan9c9 https://github.com/wan9c9 Hi, here is an example that you can serve model and update predictions daily. 1. You should update data in Qlib's database. https://github.com/microsoft/qlib#automatic-update-of-daily-frequency-data-from-yahoo-finance 2. After the data updated, you can follow this example to update predictions daily https://github.com/microsoft/qlib/blob/main/examples/online_srv/update_online_pred.py Currently, updating data in memory directly is not supported. — Reply to this email directly, view it on GitHub <#951 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB2AXZVVGRFNSYYAE3SDDSDU6XENBANCNFSM5P6POUSA . You are receiving this because you were mentioned.Message ID: @.>

hi. @wan9c9  How it works?


Can't install Microsoft.Graph.Communications.Calls.Media nuget package in UWP app

https://www.nuget.org/packages/Microsoft.Graph.Communications.Calls.Media/<IP_ADDRESS>0
Error	NU1202	Package Microsoft.Graph.Communications.Calls.Media <IP_ADDRESS>0 is not compatible with uap10.0.17763 (UAP,Version=v10.0.17763) / win10-xxx. Package Microsoft.Graph.Communications.Calls.Media <IP_ADDRESS>0 supports:

net462 (.NETFramework,Version=v4.6.2)
net472 (.NETFramework,Version=v4.7.2)

Hosting a real-time/app-hosted media bot within a UWP application is not an intended/supported scenario; such bots should be run as services in Azure.
cc: @zhengni-msft

Thanks @ssulzer. It wasn't for hosting a bot within a UWP app. It was for receiving and calling other users from a UWP application.


Feature/add typescript

Still work in progress

@ryanwoconnor I opened here a MR with the conversion to Typescript. This is based on the MR with the architecture refactor of the repo (one vs multiple monorepos).
My suggestion would be to have a separate main branch for /main-refactoring/ where we can merge at the end everything onto. This main-refactoring will only merge to /main/ at the very end once we have tested all the code. Let me know what are your thoughts on this!


removed IDPSSODescriptor from SP metadata

I'm integrating your library with ADFS and ADFS 2.0 is not able to add SP by URL because of IDPSSODescriptor that is present in SP metadata.
I replaced values with pointers in EntityDescriptor, so when SP or IDP is not needed - it is not marshaled to xml.

I recognize that this breaks the API, and I was putting off merging it until I can get a more reasonable versioning strategy going, but that is taking longer than I'd  hoped. I think this offers enough of a correctness improvement to be worth merging immediately, especially given that this part of the API isn't currently widely used.


Not sure if this is an issue

@rebaz94 I'm not sure if this is an issue or a limitation of firestore but shouldn't the order be something else?
// Format: {id}. {rank}
4. aaz
2. aaza
1. aazan   --> previously ccc and wanted to put it between 4 and 2 which gave "aazan"

Also tested this with Isar db and it got the same result.
The query:
var fs = FirebaseFirestore.instance;
fs.collection('foo').orderBy('rank').get()
  .then((res) {
    res.docs.forEach((DocumentSnapshot item) {
      Map data = item.data() as Map<String, dynamic>;
      print('${data['num']}:${data['rank']}');
    });
  });

Hi @enchance
Thank you for issue, maybe there is a bug. but one question how you generate the rank? why aaz is 3 character but aaza is 4 character?
When you generate a rank, if the length is not equal it will add a character until both rank have equal length. in this case you generating rank between aaza and aaza which is same rank. maybe I should throw error if both rank is equal.
if you ensure both rank is same length, it will generate correctly.
print(lexoRank.getRankBetween(firstRank: 'aaaz', secondRank: 'aaza')); // aamz
print(['aaza', 'aaaz', 'aamz']..sort()); // [aaaz, aamz, aaza]

I must admit I was running several values to test its accuracy. It's possible this scenario might never arise as I randomly chose areas which might never have come up considering the length is checked.
Regarding the use of generateInitialRank() for rebalancing, how often do you think should it be run?
I also created a next rank generator for this purpose as well. What do you think?
String nextLexoRank(String base, [int incr=6]) {
  int lastUnit = base.toLowerCase().codeUnits[base.length - 1];
  // 122 is a 'z'
  if(lastUnit > 122 - incr) return base + 'a';

  var newchar = String.fromCharCode(lastUnit + incr);
  var retainstr = base.substring(0, base.length - 1);

  return retainstr + newchar;
}

generateInitialRank used to generate short rank values.
for example if you have 3 rank values like: a, b, c and if you reorder the position of rank too much, the size of rank will increase each time if there is not possible value between two rank. for example if you reorder 50 times between two rank like a and b
check this:
  final ranks = <String, String>{};
  final String first = 'a';
  String second = 'b';

  for (int i = 0; i < 50; i++) {
    final rank = lexoRank.getRankBetween(firstRank: first, secondRank: second); // an
    ranks['$first-$second'] = rank;
    second = rank;
  }

  print(ranks.entries.map((e) => '${e.key}: ${e.value}').join('\n'));
  final values = ranks.values.toList();
  final shouldRebalanced = lexoRank.shouldRebalanced(
    values,
    maxRankLength: 5,
  );
  print('should rebalanced: ${shouldRebalanced.exceeded}, exceeded:${shouldRebalanced.exceededPercent}');

it generates
a-b: an
a-an: ag
a-ag: ad
a-ad: ab
a-ab: aan
a-aan: aag
a-aag: aad
a-aad: aab
a-aab: aaan
a-aaan: aaag
a-aaag: aaad
a-aaad: aaab
a-aaab: aaaan
a-aaaan: aaaag
a-aaaag: aaaad
a-aaaad: aaaab
a-aaaab: aaaaan
a-aaaaan: aaaaag
a-aaaaag: aaaaad
a-aaaaad: aaaaab
a-aaaaab: aaaaaan
a-aaaaaan: aaaaaag
a-aaaaaag: aaaaaad
a-aaaaaad: aaaaaab
a-aaaaaab: aaaaaaan
a-aaaaaaan: aaaaaaag
a-aaaaaaag: aaaaaaad
a-aaaaaaad: aaaaaaab
a-aaaaaaab: aaaaaaaan
a-aaaaaaaan: aaaaaaaag
a-aaaaaaaag: aaaaaaaad
a-aaaaaaaad: aaaaaaaab
a-aaaaaaaab: aaaaaaaaan
a-aaaaaaaaan: aaaaaaaaag
a-aaaaaaaaag: aaaaaaaaad
a-aaaaaaaaad: aaaaaaaaab
a-aaaaaaaaab: aaaaaaaaaan
a-aaaaaaaaaan: aaaaaaaaaag
a-aaaaaaaaaag: aaaaaaaaaad
a-aaaaaaaaaad: aaaaaaaaaab
a-aaaaaaaaaab: aaaaaaaaaaan
a-aaaaaaaaaaan: aaaaaaaaaaag
a-aaaaaaaaaaag: aaaaaaaaaaad
a-aaaaaaaaaaad: aaaaaaaaaaab
a-aaaaaaaaaaab: aaaaaaaaaaaan
a-aaaaaaaaaaaan: aaaaaaaaaaaag
a-aaaaaaaaaaaag: aaaaaaaaaaaad
a-aaaaaaaaaaaad: aaaaaaaaaaaab
a-aaaaaaaaaaaab: aaaaaaaaaaaaan
a-aaaaaaaaaaaaan: aaaaaaaaaaaaag

so depend on your application you could periodically check if rank should rebalanced or not.
if your issue solved, please close the issue.
Thank you


Add Support of net standard 2.0

Hello,
I have added support of netstandard 2.0. :)
(#38.)

@jgiacomini Just a question, why is the netstandard2.0 target neccessary? There is a netstandard 1.3 target, that should fit. 🤔 I always thought one has to target the lower netstandard, but probably I am mistaken. 😇

Hello @bytefish,
It's good to have the lowest compatibility possible.
But when you are in compatibility mode netstandard 1.3 you drag lot of depencies. (14 depencies).
=> If you provide the netstandard 2.0 you have a nuget package without any dependencies.  (+ they will use the lastest version of dll you reimport manually).
Hope that helps.

@jgiacomini Thanks for the explanation! 😎 With .NET you never stop learning. 🤗 I will create a new NuGet package tommorow, which includes the updated dependency. Thanks again.

I had the same issue in my lib :)
Maybe you can check if netstandard 1.6 is dependency less.
I didn't check hahah.
Thanks again for your work on this lib.

@jgiacomini Honestly I wonder if this isn't a NuGet bug pulling the wrong dependencies. If I target netframework 1.3, then to me it states "I support all netstandard >= 1.3". Why does it pull old dependencies. Yes, I can say it also targets 2.0 and make it easier for NuGet. But why does it needs such a hint? 🤨🤔

Another remark.
Do you know you can enable easily the sourcelinking with this lib =>
Microsoft.SourceLink.GitHub
An explanation here :
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx

Cool! I will have a look.

@bytefish  in your csproj you tell to nuget to user specific version of dll.
Nuget just follow your order.

<Package ...
When I use your lib in my .netcore 2.2 app => It download14 dlls more than possible, if you ship a version compatible .net standard 2.0, my app will have only one dll to download. :)

Do you think continue supporting 1.3 makes a lot of sense? I have the feeling, that 97% of the world are using or going to use netstandard 2.0 anyway.

Yes it's cost nothing to you, it s just one target :)

On the other hand, maybe existing code uses it, so this change would qualify as a breaking change. And I don't want to increase to 3.0 right now.

On one of my projet  I have supported lot of .netstandard versions you can read how I do it :
https://github.com/jgiacomini/Tiny.RestClient/blob/master/Tiny.RestClient/Tiny.RestClient.csproj
More the .netstandard is lower more I have to add dependencies hahaha. :)

Cool Project! For every Xamarin.Forms and .NET project I introduce my own REST Client abstraction (based on the FcmSharp code). I might switch & contribute to yours instead.
My approach is different though. Basically I have introduced a Request Builder:

https://github.com/bytefish/FcmSharp/blob/master/FcmSharp/FcmSharp/Http/Builder/HttpRequestMessageBuilder.cs

This HttpRequestBuilder enabled you to configure the Request (Headers, Methods, URL Segments, Query Parameters, JSON Content, ...). In the Clients I am then passing the HttpRequestBuilder around, so they can add some more Headers, like here:
https://github.com/bytefish/FcmSharp/blob/master/FcmSharp/FcmSharp/Http/Client/FcmHttpClient.cs#L69
I am not argueing for or against your design. But maybe this gives you an idea about different design choices and you might find it useful in other projects. :-)


MaaS post migrate playbook errors fails on hosts that aren't hosts[0]

Running maas-20151013-6-post-migrate.yml after a migration fails on the second task because {{ maas_post_checks.stdout_lines | sort }} doesn't result in a list or set.
This needs to | default([]) to prevent spurious errors and accidental errors in running the migration playbooks.

cc @xeregin


Add support for IMAGE locator type

https://github.com/appium/java-client/pull/990

any idea when this can be implemented? Im eagerly waiting.

I plan to do this on the weekend. You're more than welcome to contribute if you think you have the capacity to do it before then

@akinsolb : Can i expect this to be in next release?


DSFD Object Handler (abapGit#6948)

Added the DSFD Object Handler as specified in abapGit#6948

please open a PR with test objects => https://github.com/abapGit-tests/DSFD

@fvalves: Is there an AFF specified for DSFD, see https://github.com/SAP/abap-file-formats? Can you provide an example of a serialized object?

Example available at https://github.com/abapGit-tests/DSFD

@albertmink any comments? it looks good to me

welcome to abapGit as a contributor 🎉


[C#][Flight] Add DoExchange initial implementation

Describe the enhancement requested
Add initial implementation for DoExchange method.
PRs and other links:

https://github.com/apache/arrow/pull/40691

Component(s)
C#, FlightRPC

Issue resolved by pull request 40691
https://github.com/apache/arrow/pull/40691


Update container-runtime package versions

Issue #, if available:
Resolves #985, Closes #800
Description of changes:
Updates container-runtime packages to the most recent versions available in AL2 repos.
docker-0.10.17-1.amzn2
containerd-1.6.6-1.amzn2
runc-1.1.3-1.amzn2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing Done

Manually built AMIs for each K8S version/architecture
Ran EKS conformance tests on all variations of AMIs:

k8s version
arch
runtime
status

1.21
amd64
containerd-1.6.6
pass

1.22
amd64
containerd-1.6.6
pass

1.23
amd64
containerd-1.6.6
pass

1.21
arm64
containerd-1.6.6
pass

1.22
arm64
containerd-1.6.6
pass

1.23
arm64
containerd-1.6.6
pass

1.21
amd64
docker-20.10.17
pass

1.22
amd64
docker-20.10.17
pass

1.23
amd64
docker-20.10.17
pass

1.21
arm64
docker-20.10.17
pass

1.22
arm64
docker-20.10.17
pass

1.23
arm64
docker-20.10.17
pass

Looks like there is already a duplicate PR and issue out there for this.  #985  and #986 .

Thanks for putting this together -- we just need to verify that these package versions are also available in the partitions:

aws-cn
aws-us-gov

Let me see if I can figure that out.  Thanks!

OK, so for sure in aws-cn.
containerd.x86_64                      1.6.6-1.amzn2                  amzn2extra-docker
containerd-stress.x86_64               1.6.6-1.amzn2                  amzn2extra-docker
docker.x86_64                          20.10.17-1.amzn2               amzn2extra-docker
runc.x86_64                            1.1.3-1.amzn2                  amzn2extra-docker

I verified aws-us-gov:
sudo yum list available | grep -e runc -e containerd -e docker
containerd.x86_64                      1.6.6-1.amzn2                  amzn2extra-docker
docker.x86_64                          20.10.17-1.amzn2               amzn2extra-docker
runc.x86_64                            1.1.3-1.amzn2                  amzn2extra-docker

We're good to go 👍


Use new repository mamba-org/micromamba-releases for download

There is a new source for micromamba releases at mamba-org/micromamba-releases. There you can download the binaries directly without needing to extract them. This would make this role usable on systems where bzip2 is not installed.
In https://micromamba.pfx.dev/install.sh the release URL is generated as follows:
if [[ "${VERSION:-}" == "" ]]; then
  RELEASE_URL=https://github.com/mamba-org/micromamba-releases/releases/latest/download/micromamba-$PLATFORM-$ARCH
else
  RELEASE_URL=https://github.com/mamba-org/micromamba-releases/releases/download/micromamba-$VERSION/micromamba-$PLATFORM-$ARCH
fi

Hey @pavelzw, sorry this slipped my radar. Would there still be value in fixing this?

For me personally not really; I don't use this role because I only need to install micromamba and nothing else in Ansible.
For this, it's easier to use the following:
    - name: Install micromamba
      ansible.builtin.get_url:
        url: https://github.com/mamba-org/micromamba-releases/releases/download/{{ micromamba.version }}/micromamba-linux-64
        dest: /usr/local/bin/micromamba
        checksum: sha256:{{ micromamba.sha256 }}
        mode: '0755'
      register: result
      until: result is succeeded
      retries: 3
      delay: 10
      environment: "{{ proxy_env }}"

Oh cool, thanks for the recipe! Given that, perhaps we should deprecate this role? The other stuff feels a bit hacky.

Sure 🤷


docs: ensure consistency between README and program help.

Also add note about SLD export versions. Add additional usage examples.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: