🐛 [firebase_auth] AppleAuthProvider and signInWithProvider crashes on OS 16.13.1

Bug report
Describe the bug
Some iphones can't log in through apple, and they get a crash. I'm seeing this from all prod users on OS 16.13.1. I can't reproduce on OS 16.1.1.
Steps to reproduce
final appleProvider = AppleAuthProvider()
  ..addScope('email')
  ..addScope('name');

UserCredential userCredential =
    await FirebaseAuth.instance.signInWithProvider(appleProvider);

Firebase crashlytics:

Expected behavior
Not to crash, and log in successfully with Apple instead.

Additional context
Add any other context about the problem here.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.0, on macOS 13.2 22D49 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] Connected device (2 available)
[✓] HTTP Host Availability
• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.19.0
Flutter SDK 3.7.0
mobile 0.1.3+9

dependencies:
- async 2.10.0 [collection meta]
- bloc 8.1.1 [meta]
- cached_network_image 3.2.3 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- connectivity_plus 3.0.3 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- cupertino_icons 1.0.5
- device_info_plus 8.1.0 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32]
- diffutil_sliverlist 0.5.1 [flutter diffutil_dart]
- dio 5.0.1 [http_parser meta path]
- dotted_border 2.0.0+3 [flutter path_drawing]
- drift 2.5.0 [async convert collection js meta stream_channel sqlite3]
- equatable 2.0.5 [collection meta]
- firebase_analytics 10.1.4 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.2.9 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.7.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.0.15 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.2.5 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_bloc 8.1.2 [flutter bloc provider]
- flutter_dotenv 5.0.2 [flutter]
- flutter_fgbg 0.2.2 [flutter]
- flutter_native_splash 2.2.18 [args flutter flutter_web_plugins js html image meta path universal_io xml yaml]
- flutter_svg 1.1.6 [flutter meta path_drawing vector_math xml]
- fluttertoast 8.2.1 [flutter flutter_web_plugins]
- google_sign_in 6.0.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- hive 2.2.3 [meta crypto]
- hive_flutter 1.1.0 [flutter hive path_provider path]
- image 4.0.15 [archive meta xml]
- image_picker 0.8.6+4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_platform_interface]
- in_app_review 2.0.6 [flutter in_app_review_platform_interface]
- intl 0.17.0 [clock path]
- json_annotation 4.8.0 [meta]
- location 4.4.0 [flutter location_platform_interface location_web]
- logger 1.2.2
- lottie 2.2.0 [archive flutter path vector_math]
- meta 1.8.0
- mixpanel_flutter 2.0.0 [flutter flutter_web_plugins js]
- package_info_plus 3.0.3 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface win32]
- path 1.8.2
- path_provider 2.0.13 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- platform_device_id 1.0.1 [flutter platform_device_id_platform_interface platform_device_id_macos platform_device_id_linux platform_device_id_web platform_device_id_windows device_info]
- pretty_dio_logger 1.3.1 [dio]
- retrofit 4.0.1 [dio meta]
- rxdart 0.27.7
- screenshot 1.3.0 [flutter]
- share_plus 6.3.1 [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]
- social_share 2.3.1 [flutter path_provider]
- sprintf 7.0.0
- sqlite3_flutter_libs 0.5.13 [flutter]
- url_launcher 6.1.10 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.7 [crypto]

dev dependencies:
- build_runner 2.3.3 [args async analyzer build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- drift_dev 2.5.2 [charcode collection recase meta path json_annotation stream_transform args logging cli_util yaml io drift sqlite3 sqlparser analyzer analyzer_plugin source_span package_config pub_semver build build_resolvers build_config dart_style source_gen string_scanner]
- flutter_lints 2.0.1 [lints]
- 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]
- hive_generator 2.0.0 [build source_gen hive analyzer source_helper]
- json_serializable 6.6.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- retrofit_generator 5.0.0 [analyzer build built_collection code_builder dart_style dio retrofit source_gen tuple]

transitive dependencies:
- _fe_analyzer_shared 54.0.0 [meta]
- _flutterfire_internals 1.0.16 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.6.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]
- archive 3.3.6 [crypto path pointycastle]
- args 2.4.0
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.3.1 [analyzer async convert crypto glob logging meta path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.1.1 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.2.0 [analyzer async build collection crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.7 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.4.3 [built_collection collection fixnum meta]
- 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
- charcode 1.3.1
- checked_yaml 2.0.2 [json_annotation source_span yaml]
- cli_util 0.3.5 [meta path]
- clock 1.1.1
- code_builder 4.4.0 [built_collection built_value collection matcher meta]
- 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 0.17.2 [source_span]
- dart_style 2.2.4 [analyzer args path pub_semver source_span]
- dbus 0.7.8 [args ffi meta xml]
- device_info 2.0.3 [flutter device_info_platform_interface]
- device_info_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- diffutil_dart 3.0.0
- fake_async 1.3.1 [clock collection]
- ffi 2.0.1
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.3.21 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.1+12 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.11.11 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.2.8 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.5.3 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.2.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.3.15 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.2.14 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.2.15 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.1.0
- flutter_blurhash 0.7.0 [flutter]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_plugin_android_lifecycle 2.0.8 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 3.2.0 [async path]
- glob 2.1.1 [async collection file path string_scanner]
- google_identity_services_web 0.2.0 [js meta]
- google_sign_in_android 6.1.7 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.5.2 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.3.1 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.11.0+1 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http js]
- graphs 2.2.0 [collection]
- html 0.15.1 [csslib source_span]
- http 0.13.5 [async http_parser meta path]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image_picker_android 0.8.5+8 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 2.1.11 [flutter flutter_web_plugins image_picker_platform_interface]
- image_picker_ios 0.8.7 [flutter image_picker_platform_interface]
- image_picker_platform_interface 2.6.3 [cross_file flutter http plugin_platform_interface]
- in_app_review_platform_interface 2.0.4 [flutter url_launcher plugin_platform_interface platform]
- io 1.0.4 [meta path string_scanner]
- js 0.6.5 [meta]
- lints 2.0.1
- location_platform_interface 2.3.0 [flutter meta plugin_platform_interface]
- location_web 3.1.1 [flutter flutter_web_plugins http_parser js location_platform_interface meta]
- logging 1.1.1
- matcher 0.12.13 [meta stack_trace]
- material_color_utilities 0.2.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]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.0.23 [flutter path_provider_platform_interface]
- path_provider_foundation 2.1.2 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.9 [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.4 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 5.1.0 [meta]
- platform 3.1.0
- platform_device_id_linux 1.0.0 [flutter]
- platform_device_id_macos 1.0.0 [flutter]
- platform_device_id_platform_interface 1.0.0 [flutter plugin_platform_interface]
- platform_device_id_web 1.0.0 [flutter flutter_web_plugins platform_device_id_platform_interface]
- platform_device_id_windows 1.0.0 [flutter]
- plugin_platform_interface 2.1.4 [meta]
- pointycastle 3.6.2 [collection convert js]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 6.0.5 [collection flutter nested]
- pub_semver 2.1.3 [collection meta]
- pubspec_parse 1.2.2 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- recase 4.1.0
- share_plus_platform_interface 3.2.0 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shelf 1.4.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.3 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.2.7 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.3 [analyzer collection source_gen]
- source_span 1.9.1 [collection path term_glyph]
- sqflite 2.2.5 [flutter sqflite_common path]
- sqflite_common 2.4.2+2 [synchronized path meta]
- sqlite3 1.9.1 [collection ffi js meta path]
- sqlparser 0.27.0 [meta collection source_span charcode]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- synchronized 3.0.1
- 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]
- timing 1.0.1 [json_annotation]
- tuple 2.0.1
- typed_data 1.3.1 [collection]
- universal_io 2.2.0 [collection meta typed_data]
- url_launcher_android 6.0.24 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.1 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.3 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.3 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.15 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.4 [flutter url_launcher_platform_interface]
- vector_math 2.1.4
- watcher 1.0.2 [async path]
- web_socket_channel 2.3.0 [async crypto stream_channel]
- win32 3.1.3 [ffi]
- xdg_directories 1.0.0 [meta path process]
- xml 6.2.2 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

@damiafuentes
Can you provide the error log in properly formatted text ?
Although I don't have iOS 16 device, but ran plugin example on iOS 15.3.1 device which worked properly.

Here's the whole stack trace. It works fine for me on 16.1.1. I am only seeing crashes on 16.3.1 and 16.2.0.
ios_16.3.1_stacktrace.txt
ios_16.2.0_stacktrace.txt

Thanks for the update. Since I don't have iOS 16 to verify on and was able to login using iOS 15 properly using plugin example as mentioned earlier, I'll keep this issue open for team's thoughts.
/cc @Lyokone

I've just tested the auth example app. Also added the additional name scope. Running on my device which has iOS 16.3.1 installed.
No problem signing in with Apple. We're going to need a reproduction. Thanks.


Error setting slider value in a Layer Effect with nexrender in NodeJS

Hello,
I am trying to modify a slider value in an After Effects project using nexrender. Here is the JSON object I am using:
{
    "type": "data",
    "layerName": "Control Panel",
    "property": "Effects.Ans.Slider",
    "value": 1
}

However, when I attempt to execute this, I receive the following error message:
Error: Object of type ShapeLayer found where a Number, Array, or Property is needed
I have confirmed that 'Control Panel' is the exact name of the layer in my After Effects project and 'Effects.Ans.Slider' is the correct path to the property I wish to change. The 'Ans' is an effect that has been applied to the 'Control Panel' layer and it indeed has a slider control.

I have also confirmed that this property should accept a number as a value.
Could you provide any insight on why this error might be occurring, or suggest any potential solutions?
Any help would be greatly appreciated!

OK, I resolved the issue. You have to use only Solid or NullObject as control panel.


Remove startDateId and endDateId default prop values

Fix for https://github.com/airbnb/react-dates/issues/326
The ids were made required but their default prop values were not removed and as such the required aspect was useless. This addresses that issue.
This is technically breaking.
to: @ljharb @erin-doyle @airbnb/webinfra

Coverage remained the same at 86.571% when pulling<PHONE_NUMBER>0562ec62b0f083196ca67a3da1d21c on maja-make-drp-ids-required into e0d96f66f74ccd13dd799a962919bad60738dbf4 on master.

@majapw why is this breaking? If the props are required, then the defaultProp was never needed.
We definitely shouldn't worry about someone who was ignoring propType warnings.

@ljharb the props have been required for a while, but because default props were also provided, then people wouldn't see an error when not using their own ids. if we remove the default props, then people who were previously not seeing an error will now see one.  that was my motivation for marking it as breaking.

Hmm, I guess that's technically breaking, but I also think people ignoring propType warnings are OK to break :-p

None of the documentation is updated to reflect this change, it still says "required: no". Also I can't find documentation what startDateId and endDateId actually even do or why I would want to set them. In the readme they are listed under OPTIONAL props (note the caps).

but because default props were also provided, then people wouldn't see an error when not using their own ids

Noone was ignoring an error, because there never was one. Removing the defaultProp absolutely was a breaking change. /rant 😉

It looks like we have a few propType warnings when running the tests now.  Not a big deal but kind of annoying:
Warning: Failed prop type: The prop `startDateId` is marked as required in `withStyles(DateRangePicker)`, but its value is `undefined`.
    in withStyles(DateRangePicker)
Warning: Failed prop type: The prop `endDateId` is marked as required in `withStyles(DateRangePicker)`, but its value is `undefined`.
    in withStyles(DateRangePicker)
Warning: Failed prop type: The prop `startDateId` is marked as required in `DateRangePicker`, but its value is `undefined`.
    in DateRangePicker
Warning: Failed prop type: The prop `endDateId` is marked as required in `DateRangePicker`, but its value is `undefined`.
    in DateRangePicker

Fair enough, my bad.
@majapw, should we revert this and publish a v16.0.2, and then rerevert it for a v17?

That seems reasonable to me! It'd be good to add a blurb about the id as
well in the README.
I am sans computer for ten days so would appreciate if you did that @ljharb.
Sorry for the warnings!
On Fri, Dec 15, 2017, 11:12 AM Jordan Harband<EMAIL_ADDRESS>wrote:

Fair enough, my bad.
@majapw https://github.com/majapw, should we revert this and publish a
v16.0.2, and then rerevert it for a v17?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/pull/866#issuecomment-352060224,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUdtVoxxG4RHFLxwqOtKptOyPVgPJYDks5tAqiAgaJpZM4QuXjl
.

No prob, I'll take care of it today (revert + publish + put up rerevert PR)

Whoops, this is actually in v15. I'll revert it in v15.5.2 tonight/tomorrow, but leave it in v16 (and add the docs).

v15.5.2 is published; i'll follow up with a docs PR for v16 this weekend.


fix 'incompatible character encodings' error

fix 'incompatible character encodings' error, when include a template with none ascii characters (like cjk characters)

@solotimes Thanks for the pull request. Would you mind putting together a small test case for this?

I went ahead and merged this and cut a new release. Thanks for the contribution!
@solotimes I had to update a couple of the tests, though. Consider ensuring the existing specs pass before submitting a pull request, please :).

sorry for my careless, and @hypomodern thanks for fixing the specs , i shall be more careful next time.


Output multiple props

Work on #47 and #54

thank you @mcm104
still to do:

delete this branch in our local clones
and check to see what else one does after merging a pull request?

@mcm104 maybe you and I could share informally about going through this pull request at the next linked data team git and GitHub study session, whenever that is
We did some stuff:

Submitted the pull request via the browser
Resolved merge conflicts, also in the browser
Merged, also in the browser
Deleted the remote copy of the branch, in the browser
I pulled changes following the merge
I deleted my local copy of the branch following the merge

note to self @briesenberg07

Do we have a meeting for that in September? I'm only seeing October on my calendar and my temporary position runs out before then 😬


⚠ Bofrost.lu has degraded performance

In ba2396a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1690 ms

Resolved: Bofrost.lu performance has improved in c3c6b0c after 9 minutes.


Audio is not defined.

So, i am trying to run the package on a next JS app, and i get this error, some on know how to fix?

What version are you using?

I am using this versions
"@yudiel/react-qr-scanner": "^1.2.10",
"next": "^14.1.0",
"react": "^18.2.0",
"react-dom": "^18.2.0"

That error is from a previous version. In 1.2.10 it was fixed. Could you check that your .lock file is referencing that version? You could also try to delete your node_modules and recreate it. Please let me know.

The . lock file is referencing version 1.2.10, and I tried to delete the node_modules, but I had no success in solving the issue.

I have multiple apps deploy to vercel and none of them is presenting this issue with the latest version. I also created a Sandbox and was not able to reproduce it

Thanks for your help! I'll keep looking for a solution and let you know when I find it.

you probably have SSR on the component. make sure it's rendered on the client
import dynamic from 'next/dynamic'

const DynamicQrScanner = dynamic(() => import('@yudiel/react-qr-scanner').then(mod => mod.QrScanner), {
    ssr: false
  });

<DynamicQrScanner
                    containerStyle={{
                        height:"100%",
                        paddingTop: "unset"
                    }}
                    onDecode={(result) => console.log(result)}
                    onError={(error) => console.log(error?.message)}
                    />

I was having the same issue and @nick-tw answer solved my problem. Thank you so much.

This should be fixed in the beta version 2.0.0-beta.2. Please note that there are also many changes in this version. Go over the README.

I have the same problem
version: ^2.0.0-beta.3

I am Also facing the same problem.
but I resolved  it.
the problem is that Audio URL is underfed on server side. node is server endearment, so it not supported Audio JavaScript API.
Indicational state is false

i hope it will work for everyone

This issue should be fixed on 2.0.0-beta.8. There are breaking changes for this beta release.


Inconsistent text styling of Wallpaper Engine properties

Can't really change these strings here, so making an issue.

Should be one of the following:

UI volume and Text size (preferred as general properties above are sentence-cased)
UI Volume and Text Size

Has been fixed, closing.


refactor: improve cron scripts

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
107

Relevant Lines:
107

💛  - Coveralls


python311Packages.blinkpy: 0.21.0 -> 0.22.0

Diff: https://github.com/fronzbot/blinkpy/compare/refs/tags/v0.21.0...v0.22.0
Changelog: https://github.com/fronzbot/blinkpy/releases/tag/v0.22.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 251436 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.blink

4 packages built:

python310Packages.blinkpy
python310Packages.blinkpy.dist
python311Packages.blinkpy
python311Packages.blinkpy.dist

Update is part of #251878.


add a resource loader for lighting, and lambert materials

(i suspect that PointLightResourceLoader should actually be a LightResourceLoader which can handle lights of any kind? or lights should be pulled in by GLTF?)

I've based the PBR material support off this PR and now we can have uniform lighting with glTF assets. Closing this, but thanks for the help!


[Bug]: Why not add support for rtc6705

Before submitting your bug report, please confirm you have completed the following steps

[X] Searched the issue is not already listed in the Issue List (I've searched it)
[X] Searched in the Quicksilver Users' Group for questions relating to tech support.
[X] Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.

Bug description
I want to use RTC6705 to drive my vtx, but this firmware does not support it, do you have a way to add a driver for RTC6705
Steps to reproduce

Expected behavior
，
MacOS Version
None
Quicksilver Version
No response
Relevant Plugins
，
Crash Logs or Spindump
，
Screenshots
，
Additional info
，

Sorry, I think you have the wrong repo -- I have no idea what you're talking about.


Creates adapters by directory

This enables support for automatically adding a directory of adapters. It will
be read on the first load and utilize the existing registration flow.

also, we would not be unregistering adapters with adapter dir approach right?

You can unregister these adapters using the management API


JMinvJt_damping results in pinocchio quaternion assertion

In GitLab by @wxmerkt on Oct 10, 2019, 14:57
I've added 1e-12 damping to every action model as follows (in quadruped.py):
dmodel = crocoddyl.DifferentialActionModelContactFwdDynamics(self.state, self.actuation, contactModel, costModel)
dmodel.JMinvJt_damping = 1e-12
model = crocoddyl.IntegratedActionModelEuler(dmodel, timeStep)

When solving, I now receive the following assertion crash:
python: /opt/openrobots/include/pinocchio/math/quaternion.hpp:89: void pinocchio::quaternion::firstOrderNormalize(const Eigen::QuaternionBase<Derived>&) [with D = Eigen::Map<Eigen::Quaternion<double>, 0>]: Assertion `static_leq::op(math::fabs(N2-1.), epsilon)' failed.

Without damping, the assertion in the DifferentialActionModelContactFwdDynamics triggers.

In GitLab by @wxmerkt on Oct 10, 2019, 14:58
changed the description

In GitLab by @cmastalli on Oct 10, 2019, 15:13
This assertion occurs when your quaternion inside the state is wrong, e.g. all values are infinity or NaN. Pinocchio detected in Debug mode compilation (i.e. Debug mode compilation of Crocoddyl).
You need to tell me more to understand why you have wrong values in the quaternions. This could happen with the divergence in the rollout of the dynamics.

In GitLab by @cmastalli on Oct 10, 2019, 15:15
But we should expect our solver to leave the rollout loop before this happens

In GitLab by @wxmerkt on Oct 10, 2019, 15:15
I compiled both Pinocchio and Crocoddyl in Debug mode to trace down another bug. This happens when you run the quadrupedal_gaits.py example, i.e., the one using FDDP. All the changes I made is to (a) set pseudoImpulse=False and (b) to add the 1e-12 damping as described above in quadruped.py.

In GitLab by @cmastalli on Oct 10, 2019, 20:28
Thanks for reporting it.
Please note that the impulse dynamics are still in experimental phase. I didn't have time to check myself them. And we solve the impulse dynamics differently compared with the legacy Python code (i.e. through Cholesky decomposition)
As soon as possible, I'll investigate this issue if this is still unsolved.


Remove implicit permanent for text inputs

Enhancement and bug fix
Description
CableReady now handles the responsibility of protecting text input values which allows us to remove this concern from StimulusReflex.
This provides a much more robust protection for text input values.
Designed to work with CableReady changes in PR https://github.com/hopsoft/cable_ready/pull/33
Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

I'm hoping that this may also address #159

https://discordapp.com/channels/629472241427415060/683317077423292582/703972444649553940


"Ghost" of dragged items is off

This is quite likely a result of using a higher DPI display (Surface 3):
https://i.imgur.com/FU3eSNL.png
My task bar is further on the left, so the coordinates of the dragged item "ghost" are apparently scaled by the same factor I have set for scaling UI elements (180% in this case).

Hm, can't reproduce it. Tried changing UI scaling on first/second/both monitors, having the program window on first/second monitor and fullscreen/windowed.

I just tried changing my display settings from 180% scaling to 100% scaling, which eliminated the issue. Switching back to 180% brought it back, so it's definitely the cause.
Did you log out between the changes (it prompted me to and wouldn't apply them without it)?

Yeah, did not log out. Seems like it applied to everything but PoESkillTree (I got no prompt though). I can reproduce it now.

Whee!


crash when quickly press the "change color" option item under EditActivity

the suspicious code:
// Note colour menu item clicked -> show colour picker dialog
if (id == R.id.action_note_colour) {
colorPickerDialog.show(getFragmentManager(), "colourPicker");
return true;
}
the correct/safe code (check the DialogFragment before show):
// Note colour menu item clicked -> show colour picker dialog
if (id == R.id.action_note_colour) {
if(!colorPickerDialog.isAdded()) {
colorPickerDialog.show(getFragmentManager(), "colourPicker");
}
return true;
}

Hey @tingsu, I no longer maintain the project unfortunately. You can however make a PR if you want and I'll merge it.


[DOCUMENTATION] Update Portfolio

Added start and end of extracts

Coverage remained the same at 81.148% when pulling e24be990bc7f0ecce86f00bcd515617bda87867b on jeffreygohkw:master into abb20214cf70955083d9f89e1f4bd7e114991031 on CS2103AUG2017-W09-B2:master.

Coverage remained the same at 81.148% when pulling e24be990bc7f0ecce86f00bcd515617bda87867b on jeffreygohkw:master into abb20214cf70955083d9f89e1f4bd7e114991031 on CS2103AUG2017-W09-B2:master.


Issue4

makes node and npm child processes run from the current working directory of Pixiedust's home directory
ensures there is a node_modules directory in Pixiedust's home directory

I've done as you suggest here @DTAIEB. All a node directory is created which is where node and npm are run from


Log errors on Cadence index access

It looks like this is already done on master now. I think Cadence improved its error logging in that respect.

Mainnet 7 is not working, so this might be required after all.

They seem to have fixed that upstream in Cadence, as the error messages are now included in the Cadence output.


fix(link): removed extra span element

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 81.508%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
6802

Relevant Lines:
7642

💛  - Coveralls


Fix interface name for IExceptionFilter

Fixes a small issue in the docs listing the interfaces.

@samneirinck  thanks!


add example with uncertain delay

Codecov Report

Merging #54 (ad8a271) into master (9a07763) will decrease coverage by 0.31%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #54      +/-   ##
==========================================
- Coverage   89.98%   89.66%   -0.32%
==========================================
  Files          17       17
  Lines        2546     2555       +9
==========================================
  Hits         2291     2291
- Misses        255      264       +9

Impacted Files
Coverage Δ

src/uncertainty_interface.jl
84.42% <0.00%> (-2.72%)
:arrow_down:

Continue to review full report at Codecov.

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


[BUG] The unnecessary import of the numpy library.

While going through the main.py file of the project I found that the numpy library is unnecessarily imported in the main.py file.
It has no use in the whole project and should be removed from the file.
Please assign me this issue @ombhojane Sir

hey you can raise a PR, but it might not get hactoberfest badge, because we're looking for more meaningful contributions.
you can look around explainableai package, explore, give it a shot! and raise meaningful PRs! @PreetSharma-12

No problem Sir, I would still like to raise a PR as I am contributing for the betterment of the project.


Add ability to send audio to camera

I started experimenting with sending audio to the camera, ideally in the future to start use it as media_player device in Home Assistant, basically having ability to play any mp3.
Branch talk_experiments
Test file:
from pytapo import Tapo
import json
import asyncio
import logging

logging.basicConfig(level=logging.DEBUG)
# change variables here
host = ""  # change to camera IP
user = ""  # your username
password = ""  # your password
password_cloud = ""  # set to your cloud password

tapo = Tapo(host, user, password, password_cloud)

devID = tapo.getBasicInfo()["device_info"]["basic_info"]["dev_id"]

async def download_async():
    print("Starting...")
    mediaSession = tapo.getMediaSession()
    async with mediaSession:
        payload2 = {
            "params": {"talk": {"deviceId": devID, "mode": "aec"}, "method": "get"},
            "type": "request",
        }

        payload = json.dumps(payload2)
        output = b""
        dataChunks = 0

        print("Opened session")
        async for resp in mediaSession.transceive(payload):
            if resp.mimetype == "video/mp2t":
                # if len(resp.plaintext) != 376:
                dataChunks += 1
            else:
                # print(resp.plaintext)
                pass

            # if dataChunks > 2000:
            #    break

        fileName = "./output/stream.ts"
        print("Saving to " + fileName + "...")
        file = open(fileName, "wb")
        file.write(output)
        file.close()

loop = asyncio.get_event_loop()
loop.run_until_complete(download_async())

The main part is currently trying to open a working mp2 file, read first 1520 bytes (the same size as tapo is sending payloads in) and send it to the camera.
Unfortunately, nothing happens.

I don't know if FFmpeg able to generate properly TS file for Tapo cameras. Because they using not popular codec for this container:
https://github.com/AlexxIT/go2rtc#source-tapo
https://github.com/AlexxIT/go2rtc#stream-to-camera

Thank you, I am looking into this, it looks really great!

I do not plan to implement this feature as it was already done very well inside https://github.com/AlexxIT/WebRTC#stream-to-camera and https://github.com/AlexxIT/go2rtc#stream-to-camera.

its a funny coincidence during the weekend I also tried to decompile the official tapo app to get the audio backchannel :zany_face:
if you are interested, here are the extracted java classes that produce the mp2t stream https://gitlab.com/Gretulililinka/TapoTalk/-/tree/master/java_src
and proof thats working https://gitlab.com/Gretulililinka/TapoTalk/-/tree/master/
blog ( czech lang :czech_republic: )about how I found it  https://www.abclinuxu.cz/blog/GretinBlogisek/2023/2/tapovoko-129535-128226

Is go2rtc's stream-to-camera working on your devices ?
I've tried go2rtc and back channel audio either doesn't work at all or crash my camera (cause a reboot).

@Boteium intermittently for me, usually it does after a camera reboot. Please open issue in go2rtc repo.


Updated test code

Printing from test functions (to stdout) is now suppressed unless the verbose flag is given, to clean up output while testing. Also added a testdir flag used to specify the test directory.

Not sure if this module is necessary.  I expect, pytest can do everything.

This is a stale pr with conflicts.  I believe, pytest configuration/conftest.py should be changed instead.
But feel free to reopen, if you disagree.


Implement JSON-LD

Figure out how to implement JSON-LD responses on REST API for compose records

Dup #477


Wrong classification model output

Converted model from keras to NCNN. Pre-processing used in keras(python) is as follows
# reading image in cv Mat format
orig = cv2.imread('black.png')
# Converting image from BGR to RGB
image = cv2.cvtColor(orig, cv2.COLOR_BGR2RGB)
# Resizing image to 128x128
image = cv2.resize(image, (128, 128))
# Convert image to float by and normalize by dividing it by 255
image = image.astype("float") / 255.0
# Convert image to array
image = img_to_array(image)
# Expand numpy array dimentions
image = np.expand_dims(image, axis=0)
# Load keras model
model = tf.keras.models.load_model('cnn128.h5')
# Give input to keras model
pred = model.predict(image)[0]

I tried to replicate the steps in c++ for NCNN model
// reading image in cv Mat format
Mat image = imread("eyes.jpg"); //read image
// Converting image from BGR to RGB
cv::cvtColor(image, image, cv::COLOR_BGR2RGB);
// Resizing image to 128x128
Mat img;
resize(image, img, Size(128, 128));
// Convert image to float by and normalize by dividing it by 255
img.convertTo(img,CV_32F);
img /= 255.0;
// Load ncnn model
ncnn::Net smallCNN;
smallCNN.load_param("cnn128.param");
smallCNN.load_model("cnn128.bin");
// converting cv::Mat image to ncnn::Mat
ncnn::Mat in = ncnn::Mat::from_pixels(img.data, ncnn::Mat::PIXEL_RGB, img.cols, img.rows);
// Give input to ncnn model
ncnn::Extractor ex = smallCNN.create_extractor();
ex.input("conv2d_8_input_blob", in);

when run the code, as an output I am getting this value
8 = 1.000000
7 = 0.000000
6 = 0.000000

where 8 is the label and 1.000000 is the probability. correct label is 0 and not 8
can anyone please help to understand what went wrong in input processing ?

Can you provide the model for debugging?

@MarsTechHAN
Model link: https://drive.google.com/drive/folders/1--ZzTFtdDkgRxsezZfW65is5KVBfJh8I?usp=sharing
Full c++ inference program
#include <vector>
#include <opencv2/core/core.hpp>
#include <opencv2/highgui/highgui.hpp>
#include <opencv2/imgproc/imgproc.hpp>

#include <opencv2/ml.hpp>
#include <iterator>
#include <fstream>
#include "dirent.h"
#include "net.h"

using namespace cv::ml;
using namespace std;
using namespace cv;

/* Function is taken from one of NCNN examples */
static int print_topk(const std::vector<float>& cls_scores, int topk)
{
    // partial sort topk with index
    int size = cls_scores.size();
    std::vector<std::pair<float, int> > vec;
    vec.resize(size);
    for (int i = 0; i < size; i++)
    {
        vec[i] = std::make_pair(cls_scores[i], i);
    }

    std::partial_sort(vec.begin(), vec.begin() + topk, vec.end(),
                      std::greater<std::pair<float, int> >());

    // print topk and score
    for (int i = 0; i < topk; i++)
    {
        float score = vec[i].first;
        int index = vec[i].second;
        fprintf(stderr, "%d = %f\n", index, score);
    }

    return 0;
}

int main()
{
    	// reading image in cv Mat format
	Mat image = imread("eyes.jpg"); //read image
	// Converting image from BGR to RGB
	cv::cvtColor(image, image, cv::COLOR_BGR2RGB);
	// Resizing image to 128x128
	Mat img;
	resize(image, img, Size(128, 128));
	// Convert image to float by and normalize by dividing it by 255
	img.convertTo(img,CV_32F);
	img /= 255.0;
	// Load ncnn model
	ncnn::Net smallCNN;
	smallCNN.load_param("cnn128.param");
	smallCNN.load_model("cnn128.bin");
	// converting cv::Mat image to ncnn::Mat
	ncnn::Mat in = ncnn::Mat::from_pixels(img.data, ncnn::Mat::PIXEL_RGB, img.cols, img.rows);
	// Give input to ncnn model
	ncnn::Extractor ex = smallCNN.create_extractor();
	ex.input("conv2d_8_input_blob", in);

        ncnn::Mat out;
    	ex.extract("dense_5_Softmax_blob", out);

	vector<float> v1;
	std::vector<float> cls_scores;
	cls_scores.resize(out.w);
    	for (int j = 0; j < out.w; j++)
    	{
       	 	cls_scores[j] = out[j];
		std::cout<<"score: "<<out[j];
    	}
	print_topk(cls_scores, 3);
    	return 0;
}

Thanks! Can you also provide the original keras model comparing?

Uploaded kerass model same folder here: https://drive.google.com/drive/folders/1--ZzTFtdDkgRxsezZfW65is5KVBfJh8I?usp=sharing

Here is the keras2ncnn debug mode output (by inputing random data), it seems like the network forward path is completely identical, so the problem may be in the pre-processing stage of the network. Can you try to extract the conv2d_8_input and conv2d_8  layers and comparing them to the image in the line pred = model.predict(image)[0]
conv2d_8_input
==================================
Layer Name: conv2d_8, Layer Shape: keras->(1, 43, 43, 16) ncnn->(16, 43, 43)
Max:    keras->0.819 ncnn->0.819        Min: keras->-0.964 ncnn->-0.964
Mean:   keras->-0.083 ncnn->-0.083      Var: keras->0.215 ncnn->0.215
Cosine Similarity: 0.00000
Keras Feature Map:      [ 0.084  0.128 -0.216 -0.194  0.106 -0.197 -0.051  0.18  -0.159 -0.058]
Ncnn Feature Map:       [ 0.084  0.128 -0.216 -0.194  0.106 -0.197 -0.051  0.18  -0.159 -0.058]
==================================
Layer Name: max_pooling2d_8, Layer Shape: keras->(1, 22, 22, 16) ncnn->(16, 22, 22)
Max:    keras->0.819 ncnn->0.819        Min: keras->-0.693 ncnn->-0.693
Mean:   keras->0.097 ncnn->0.097        Var: keras->0.178 ncnn->0.178
Cosine Similarity: 0.00000
Keras Feature Map:      [0.128 0.016 0.106 0.18  0.16  0.01  0.062 0.162 0.175 0.135]
Ncnn Feature Map:       [0.128 0.016 0.106 0.18  0.16  0.01  0.062 0.162 0.175 0.135]
==================================
Layer Name: conv2d_9, Layer Shape: keras->(1, 11, 11, 32) ncnn->(32, 11, 11)
Max:    keras->0.994 ncnn->0.994        Min: keras->-1.331 ncnn->-1.331
Mean:   keras->-0.115 ncnn->-0.115      Var: keras->0.370 ncnn->0.370
Cosine Similarity: -0.00000
Keras Feature Map:      [0.594 0.511 0.582 0.539 0.646 0.273 0.217 0.661 0.864 0.311]
Ncnn Feature Map:       [0.594 0.511 0.582 0.539 0.646 0.273 0.217 0.661 0.864 0.311]
==================================
Layer Name: max_pooling2d_9, Layer Shape: keras->(1, 6, 6, 32) ncnn->(32, 6, 6)
Max:    keras->0.994 ncnn->0.994        Min: keras->-0.900 ncnn->-0.900
Mean:   keras->0.034 ncnn->0.034        Var: keras->0.345 ncnn->0.345
Cosine Similarity: 0.00000
Keras Feature Map:      [0.594 0.721 0.724 0.661 0.864 0.175]
Ncnn Feature Map:       [0.594 0.721 0.724 0.661 0.864 0.175]
==================================
Layer Name: conv2d_10, Layer Shape: keras->(1, 6, 6, 64) ncnn->(64, 6, 6)
Max:    keras->1.508 ncnn->1.508        Min: keras->-2.416 ncnn->-2.416
Mean:   keras->-0.259 ncnn->-0.259      Var: keras->0.535 ncnn->0.535
Cosine Similarity: 0.00000
Keras Feature Map:      [-0.803 -0.622 -0.666 -0.458 -0.862 -0.529]
Ncnn Feature Map:       [-0.803 -0.622 -0.666 -0.458 -0.862 -0.529]
==================================
Layer Name: max_pooling2d_10, Layer Shape: keras->(1, 3, 3, 64) ncnn->(64, 3, 3)
Max:    keras->1.508 ncnn->1.508        Min: keras->-1.635 ncnn->-1.635
Mean:   keras->0.068 ncnn->0.068        Var: keras->0.479 ncnn->0.479
Cosine Similarity: 0.00000
Keras Feature Map:      [-0.622 -0.458 -0.529]
Ncnn Feature Map:       [-0.622 -0.458 -0.529]
==================================
Layer Name: conv2d_11, Layer Shape: keras->(1, 3, 3, 64) ncnn->(64, 3, 3)
Max:    keras->2.364 ncnn->2.364        Min: keras->-3.498 ncnn->-3.498
Mean:   keras->-0.388 ncnn->-0.388      Var: keras->0.852 ncnn->0.852
Cosine Similarity: -0.00000
Keras Feature Map:      [-0.083  0.35   1.077]
Ncnn Feature Map:       [-0.083  0.35   1.077]
==================================
Layer Name: max_pooling2d_11, Layer Shape: keras->(1, 2, 2, 64) ncnn->(64, 2, 2)
Max:    keras->2.364 ncnn->2.364        Min: keras->-2.076 ncnn->-2.076
Mean:   keras->-0.044 ncnn->-0.044      Var: keras->0.713 ncnn->0.713
Cosine Similarity: 0.00000
Keras Feature Map:      [0.35  1.077]
Ncnn Feature Map:       [0.35  1.077]
==================================
Layer Name: flatten_2, Layer Shape: keras->(1, 256) ncnn->(1, 1, 256)
Max:    keras->2.364 ncnn->2.364        Min: keras->-2.076 ncnn->-2.076
Mean:   keras->-0.044 ncnn->-0.044      Var: keras->0.713 ncnn->0.713
Cosine Similarity: 0.00000
Keras Feature Map:      [ 0.35   0.873 -0.533 -0.701 -1.271  0.158 -0.739 -0.816  0.883 -0.247]
Ncnn Feature Map:       [ 0.35   0.873 -0.533 -0.701 -1.271  0.158 -0.739 -0.816  0.883 -0.247]
Top-k:
Keras Top-k:    88:2.364, 174:1.651, 127:1.642, 195:1.427, 25:1.396
ncnn Top-k:     88:2.364, 174:1.651, 127:1.642, 195:1.427, 25:1.396
==================================
Layer Name: dense_4, Layer Shape: keras->(1, 256) ncnn->(1, 1, 256)
Max:    keras->6.627 ncnn->6.627        Min: keras->0.000 ncnn->0.000
Mean:   keras->0.997 ncnn->0.997        Var: keras->1.479 ncnn->1.479
Cosine Similarity: 0.00000
Keras Feature Map:      [0.    0.    1.482 1.711 2.979 5.397 0.    0.248 0.    1.833]
Ncnn Feature Map:       [0.    0.    1.482 1.711 2.979 5.397 0.    0.248 0.    1.833]
Top-k:
Keras Top-k:    82:6.627, 12:6.439, 90:5.565, 129:5.425, 201:5.404
ncnn Top-k:     82:6.627, 12:6.439, 90:5.565, 129:5.425, 201:5.404
==================================
Layer Name: dense_5_Softmax, Layer Shape: keras->(1, 9) ncnn->(1, 1, 9)
Max:    keras->1.000 ncnn->1.000        Min: keras->0.000 ncnn->0.000
Mean:   keras->0.111 ncnn->0.111        Var: keras->0.314 ncnn->0.314
Cosine Similarity: -0.00000
Keras Feature Map:      [0. 0. 0. 0. 0. 0. 0. 0. 1.]
Ncnn Feature Map:       [0. 0. 0. 0. 0. 0. 0. 0. 1.]
Top-k:
Keras Top-k:    8:1.000, 2:0.000, 5:0.000, 1:0.000, 0:0.000
ncnn Top-k:     8:1.000, 2:0.000, 5:0.000, 7:0.000, 6:0.000
Done!

Something like this happened before... but I just not able to find where the accuracy mismatched.

yes, same for me too. But will try to print the output of first layer in both keras and NCNN, then we might be able to solve it. Will let you know if I get any success ! Thanks though

Maybe you can also give me a test picture and expected output

@MarsTechHAN
Image is updated in the same drive link: https://drive.google.com/drive/folders/1--ZzTFtdDkgRxsezZfW65is5KVBfJh8I?usp=sharing
Expected output: Label Index: 0

Cool, let me have a look.

@MarsTechHAN
How did you print these values ?
If possible can you please help me with the program which prints it ?

@MarsTechHAN
How did you print these values ?
If possible can you please help me with the program which prints it ?

It's keras2ncnn's build-in debug mode, by running:
python3 -mkeras2ncnn -i MODEL_FILE.h5 -d

However, it still contains a lot of bug. I am thinking of using docker for it. You can refer this code snap for your program:
https://github.com/MarsTechHAN/keras2ncnn/blob/e3f90c44fbb814d068f0d76d0da27027bfe218e1/keras2ncnn/keras_debugger.py#L32-L51
and this for loading:
https://github.com/MarsTechHAN/keras2ncnn/blob/e3f90c44fbb814d068f0d76d0da27027bfe218e1/keras2ncnn/keras_debugger.py#L308-L309

@MarsTechHAN
Did you get whats wrong in the processing ? I am not able to understand.

@MarsTechHAN
One thing I noticed is this, in keras the dimensions of input are type: float32[?,128,128,3] and in NCNN is type: float32[128,128,3]
Keras is 4D and NCNN is 3D, do you how to convert the NCNN image to 4D ?

@MarsTechHAN
While using the debugger I am getting this error
python3 -mkeras2ncnn -i cnn128.h5 -d

error
ValueError: ('Unrecognized keyword arguments:', dict_keys(['ragged']))

@MarsTechHAN
One thing I noticed is this, in keras the dimensions of input are type: float32[?,128,128,3] and in NCNN is type: float32[128,128,3]
Keras is 4D and NCNN is 3D, do you know how to convert the NCNN image to 4D ?

ncnn does not have 4D tensor and the batch dim. The dim of the keras is 4-D because of the batch, you dont need that in the ncnn. So no worrying, it's correct.

@MarsTechHAN
While using the debugger I am getting this error
python3 -mkeras2ncnn -i cnn128.h5 -d

error
ValueError: ('Unrecognized keyword arguments:', dict_keys(['ragged']))

Can you paste the full ouptut log?  It seems like not the issue from the debugger


Feature: Wheel picker component

Why?
Because of feedback that the current way of selecting duration needs to be improved (https://hfnswedenab.atlassian.net/browse/NMA-3755)
What?
A wheel picker for selecting an integer value by turning the wheel to the desired value. This can be extended later to support decimals as well, but for now it's only integers.
Design - This is first iteration and the tickers are different because of reasons. But I've clearified this with Magnus, so this version is an acceptable first version.
Version Change
Minor
UI Changes

Light
Dark

https://user-images.githubusercontent.com/675434/186686074-ef66dbb6-ce9c-474c-9e53-bc9fea6b03ff.mp4
TODO

Link this PR with member app PR when it's ready.

I'm wondering if there's a need to show that multiple turns have been taken, or if it's understandable that it just continues around like that.

It was just something I tried and showed to Magnus, and he wanted to keep it. Gives a bit more feedback to the user imo.

I will review with more detail, but a quick look at the code and I didn't see any use of haptic, which is beneficial for these kinds of components

from the Haptique app from

Yeah, using
hapticGenerator: UIImpactFeedbackGenerator = .init(style: .medium)

hapticGenerator.impactOccurred()

is better for each value.
I think the semantic is a bit different than notification success...
more info https://developer.apple.com/design/human-interface-guidelines/patterns/playing-haptics

Yeah, using
hapticGenerator: UISelectionFeedbackGenerator = .init()

hapticGenerator.selectionChanged()

is better for each value.
I think the semantic is a bit different than notification success...
more info developer.apple.com/design/human-interface-guidelines/patterns/playing-haptics

Alright, nice thanks! I'm not too familiar with the haptic system, and I could only find .success, .warning and .error. I'll update 👍


BECanvas doesn't seem to work for .Net 5

I'm migrating a project that worked fine in .Net 3.1 and, when trying to convert it to .Net 5 BECanvas, no longer works. The reference to BECanvasComponent remains null.

I suspect this project has been abandoned.

Thank you, mizrael. What would be the alternative you advise me to draw in Blazor with .Net 5?
In some projects with .Net 5 BECanvas seems to work fine, but in others it does not and I do not understand where the difference is.

Honestly I don't have an alternative. I raised a PR a while ago, but got
no response. I even contacted both @galvesribeiro and @attilah , but they
didn't reply. I am considering creating a fork and publishing it on Nuget.
On Sat., Dec. 26, 2020, 10:07 a.m. rperazzolli<EMAIL_ADDRESS>wrote:

Thank you, mizrael. What would be the alternative you advise me to draw in
Blazor with .Net 5?
In some projects with .Net 5 BECanvas seems to work fine, but in others it
does not and I do not understand where the difference is.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BlazorExtensions/Canvas/issues/94#issuecomment-751364722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK52KEDJVWD5I25NN4Q2PTSWX323ANCNFSM4VJ64NMA
.

The fault was exclusively mine.
The component is working properly. When translating code from Blazor Server 3.1 to Blazor WebAssembly 5, I made changes that affected the operation.
Thanks for your help.


Document update. Commit on behalf of Don(v-donglo2@microsoft.com).

Update swagger with refined wording to prepare for new document web site.

This change is

 https://github.com/Azure/azure-sdk-for-ruby/pull/589

No modification for NodeJS

 https://github.com/Azure/azure-sdk-for-python/pull/885


customsDeclaration.create returning zod errors when using previously valid customsItems.create objects

In version v2.1.2 (attempting upgrade from 1.7.1)
When using the client.customsDeclarations.create method. I used to be able to pass an array of customsItems objectIds in the items field. These were successfully created using the the client.customsItems.create method.
In the latest version, the type CustomsDeclarationCreateRequest
has the items property typed as
items: Array<CustomsItemCreateRequest>;
When I send the same configuration objects which previously worked using customsItems.create, several zod typing errors are returned.
example request
 {
  "contentsType": "MERCHANDISE",
  "contentsExplanation": "{example} merchandise",
  "nonDeliveryOption": "RETURN",
  "certify": true,
  "certifySigner": "Example User",
  "items": [
    {
      "description": "{example} merchandise",
      "quantity": 1,
      "netWeight": "8",
      "massUnit": "oz",
      "valueAmount": "159",
      "valueCurrency": "USD",
      "originCountry": "US"
    }
  ]
}

errors returned from
await client.customsDeclarations.create(exampleRequest)
{
    "status": "rejected",
    "reason": {
    "writeToLog": false,
    "originalError": {
        "name": "SDKValidationError",
        "cause": {
        "issues": [
            {
            "received": "",
            "code": "invalid_enum_value",
            "options": [
                "FILED_ELECTRONICALLY",
                "SUMMARY_REPORTING",
                "NOT_REQUIRED"
            ],
            "path": [
                "b13a_filing_option"
            ],
            "message": "Invalid enum value. Expected 'FILED_ELECTRONICALLY' | 'SUMMARY_REPORTING' | 'NOT_REQUIRED', received ''"
            },
            {
            "code": "invalid_type",
            "expected": "string",
            "received": "boolean",
            "path": [
                "commercial_invoice"
            ],
            "message": "Expected string, received boolean"
            },
            {
            "received": "",
            "code": "invalid_enum_value",
            "options": [
                "NOEEI_30_37_a",
                "NOEEI_30_37_h",
                "NOEEI_30_37_f",
                "NOEEI_30_36",
                "AES_ITN"
            ],
            "path": [
                "eel_pfc"
            ],
            "message": "Invalid enum value. Expected 'NOEEI_30_37_a' | 'NOEEI_30_37_h' | 'NOEEI_30_37_f' | 'NOEEI_30_36' | 'AES_ITN', received ''"
            },
            {
            "received": "",
            "code": "invalid_enum_value",
            "options": [
                "DDP",
                "DDU",
                "FCA",
                "DAP",
                "eDAP"
            ],
            "path": [
                "incoterm"
            ],
            "message": "Invalid enum value. Expected 'DDP' | 'DDU' | 'FCA' | 'DAP' | 'eDAP', received ''"
            }
        ],
        "name": "ZodError"
        },
        "rawValue": {
        "object_created": "2024-05-06T03:21:14.498Z",
        "object_updated": "2024-05-06T03:21:14.498Z",
        "object_id": "5599a71217df4977b3185499ae8bb11d",
        "object_owner"<EMAIL_ADDRESS>        "object_state": "VALID",
        "certify_signer": "example user",
        "certify": true,
        "items": [
            "e761308d66684857a6cc3a2e3b3fd3f6"
        ],
        "non_delivery_option": "RETURN",
        "contents_type": "MERCHANDISE",
        "contents_explanation": "example merchandise",
        "exporter_reference": "",
        "importer_reference": "",
        "invoice": "",
        "commercial_invoice": false,
        "license": "",
        "certificate": "",
        "notes": "",
        "eel_pfc": "",
        "aes_itn": "",
        "disclaimer": "",
        "incoterm": "",
        "metadata": "",
        "test": true,
        "b13a_filing_option": "",
        "b13a_number": "",
        "is_vat_collected": false
        }
    },
    "type": "shipping_transaction_processing",
    "status": 400
    }
}

They seem to be primarily issues with zod enum values. Interestingly, an objectId does seem to have been generated for the customsItem.
Please advise on whether this behavior is a bug or if there are reasonable defaults to use for all of these enums.

this is a known issue and is something I will be picking up this week.  basically, we are returning an empty string for some enum fields and an enum is a closed set - and an empty string is not a valid return value.
the problem is not with the input, it's with the output.  the request actually succeeds (hence, the objectId), but fails during deserialization of the response.

@shippo-lueders
Thank you for the update. Will keep an eye out for the next version

@alsoscotland https://www.npmjs.com/package/shippo/v/2.2.3 has been published which should resolve this issue.
sorry it took so long, the issue of enums is a bit thorny.  in this particular case, we're returning an empty string for enums which we really shouldn't be doing but there are very possibly clients depending on this behavior, so we can't alter that behavior without likely breaking some clients.  more generally, we have fields represented as enums (e.g. service level) which will absolutely vary over time.  the solution we've opted for is to separate the models based on whether the schema is used for input or output.  for input schemas, the field is an enum; for output schemas, the field is a string.  the rationale being, enums are valuable for input models b/c they offer code completion in IDEs.
I've only done this for the customs models so far but it's likely we'll make this approach more ubiquitous.  the other (and simpler) option would be to eliminate enums completely from fields and just use string, where the enum is still available as a schema object but just not directly referenced as a field type.  internally, this is simpler; but the belief is that this would lead to a worse user experience.  as a user of the SDK, any thoughts you have on the subject are appreciated.

@shippo-lueders
Thank you for the update. For what it is worth I have opted out of using typescript string enums in my API code personally in favor of other options like union types or template literal types.
For me, the duality of enums getting exported as both types and values always caused a little confusion for me. It is a topic that seemingly gets debated a ton and has merits from multiple perspectives.
In terms of consumption, I think that this means I now have to import the enum type and reference its properties directly off from the value when calling the APIs. This may be confusing to some people if they are trying to use the string value of the enum member directly when attempting to call the API methods.
I have not tried it but it might be worth investigating something like this for your output types.
type DistanceUnitEnumOutputType = ${DistanceUnitEnum} & '';

@shippo-lueders Found this yesterday
https://www.youtube.com/watch?v=jjMbPt_H3RQ
It does a very good job of illustrating the details around enums


Table crashed

Describe the bug (current behavior)
when I update @itwin/itwinui-react (1.42.0--->2.12.22), my table component crashed when reload.

Expected Behavior
No response
Link to minimal repro
No response
Steps To Reproduce
No response
Anything else?
No response

It's impossible for us to help you with just a screenshot of the error. Can you provide more details?
My only guess is that your Table columns contain loose JSX nodes, in which case you can try to use a function instead.
- Header: <MyComponent />
+ Header: () => <MyComponent />


Initial commit with the code pulled out of our main app.

@kennydude I made a minor change to get rid of unused imports and other PEP8 stuff - can you run over this and make sure it all looks good.

:+1: Good to go


Optimize InsertOptimizeEngine.java

Fixes #1990.

Pull Request Test Coverage Report for Build 7088

37 of 58 (63.79%)  changed or added relevant lines in 7 files are covered.
3 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 71.241%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/strategy/encrypt/ShardingEncryptorEngine.java
0
3
0.0%

sharding-core/sharding-core-rest/src/main/java/org/apache/shardingsphere/core/routing/type/standard/StandardRoutingEngine.java
1
4
25.0%

sharding-core/sharding-core-rest/src/main/java/org/apache/shardingsphere/core/rewrite/SQLRewriteEngine.java
9
15
60.0%

sharding-core/sharding-core-rest/src/main/java/org/apache/shardingsphere/core/optimizer/engine/encrypt/EncryptInsertOptimizeEngine.java
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/strategy/encrypt/ShardingEncryptorEngine.java
1
28.57%

sharding-core/sharding-core-rest/src/main/java/org/apache/shardingsphere/core/optimizer/engine/sharding/insert/InsertOptimizeEngine.java
1
98.48%

sharding-core/sharding-core-rest/src/main/java/org/apache/shardingsphere/core/routing/type/standard/StandardRoutingEngine.java
1
65.52%

Totals

Change from base Build 7085:
-0.01%

Covered Lines:
11187

Relevant Lines:
15703

💛  - Coveralls


Add docker to generate protos and build SDK locally

This PR updates the Dockerfile to automatically generate the model files from the *.proto definitions, for those looking to buld the SDK themselves. These files are not included in the repo, but are required to build the solution.
Readme file updated with instructions.

Done.
Wouldn't squashing take care of it anyway?

@dcmiddle @rbuysse

@ryjones I should probably abandon this PR and submit new one with the suggestions in this discussion. I haven't gotten around to doing it, but I will have some availability this week.

Closing this and will submit a new PR with the discussed changes.


Serious memory leak

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T12:44:48.751Z)
OS Version: Linux x64 4.13.0-16-generic
Extensions: Extensions are disabled

Steps to Reproduce:

Launch visual studio
See memory usage over time

Reproduces without extensions: Yes

Please see the tips at https://github.com/Microsoft/vscode/wiki/Performance-Issues to provide more details to help us narrow this down.


Develop

Supporting runtime choice of instance types.
Linker can automatically cast from type T to type Array[T] when calling a task.


Getting Started Guide for Contributors?

Would be great to have a getting started guide for developers looking to contribute to the platform.
https://digitalax.gitbook.io/digitalax/ seems to speak to the composition of the solution.
A requirement for a parallel to the above for developers beyond the read me when getting started.
Reading code is of course standard - in addition presenting a straight forward and clear Getting Started Guide may catalyze community interest.

https://github.com/DIGITALAX/digitalax-contracts/blob/main/CONTRIBUTING.md
Done. Thanks for your participation

https://github.com/DIGITALAX/digitalax-contracts/blob/main/CONTRIBUTING.md
Done. Thanks for your participation


Update main.c

Call functions with params for porting v8. (Legacy NULLS from v7 deleted)
Wait correct amount of time in while loop. Use assets given by functions.
issue : https://github.com/lvgl/lvgl/issues/1839#issuecomment-705440508

Thanks for the PR @Coffeeye , I'm still not sure how are we going to handle support for multiple versions of LVGL on main.c. Maybe adding #if guards might be a possible idea? such as
#if LVGL_VERSION_MAJOR >= 8
        /* LVGL v8 */
#else
        /* LVGL v7 */
#endif

Any ideas on how to proceed @tore-espressif ?

This is a fork of the project named porting v8 so imo .md should be only with that info and examples made typical for v8.
If I were you @C47D , that would be beyond doubt

Yup, the port_v8 branch is pretty old and it was just an experiment. The current intention is to support both versions of LVGL on the same example.

Yup, the port_v8 branch is pretty old and it was just an experiment. The current intention is to support both versions of LVGL on the same example.

Finally found LovyanGFX the best drivers which works with v8.x for both Arduino and ESP-IDF.
ESP-IDF & Arduino samples for WT32-SC01 using LVGL8 + LOVYANGFX
Device : WT32-SC01
Display / Touch Drivers : LovyanGFX
Widgets : LVGL 8.x
ESP-IDF => WT32-SC01 + LVGL8 + LOVYANGFX
https://github.com/sukesh-ak/LVGL8-WT32-SC01-IDF
Arduino => WT32-SC01 + LVGL8 + LOVYANGFX
https://github.com/sukesh-ak/LVGL8-WT32-SC01-Arduino


Feature: implement toString for PutMessageAdapter and AckMessageAdapter

Is there an existing proposal for this?

[X] I have searched the existing proposals

Is your feature request related to a problem?
From the logs you can see that toString is implemented to PushMessageAdapter only.
12:27:06,590 (main) ERROR SessionStressIT:267 Last PUT : com.bloomberg.bmq.Session$QueueAdapter$PutMessageAdapter@6b05a1fd
12:27:06,590 (main) ERROR SessionStressIT:268 Last ACK : com.bloomberg.bmq.Session$QueueAdapter$AckMessageAdapter@45ac5ad1
12:27:06,592 (main) ERROR SessionStressIT:269 Last PUSH: [ Queue URI: bmq://bmq.test.mmap.priority/java-it-cbc42d86-7c43-4f7c-8377-be88b7a06108 ][ PushHeader [ Flags=2 MessageWords=267 OptionsWords=2 CompressionType=0 HeaderWords=8 QueueId=0 MessageGUID=0003E7000002F90E62391B26CF840BF9 SchemaWireId=1 ] ][ PushMessage [ SubQueueIds [ [0] ] ][ Payload ["................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................***" ][ MessageProperties [ [ MessageProperty [ Type=STRING Name=routingId Value="abcd-efgh-ijkl" ] ][ MessageProperty [ Type=INT64 Name=timestamp Value=123456789 ] ] ] ] ]

Describe the solution you'd like
Implement toString for PutMessageAdapter and `AckMessageAdapter
Alternatives you considered
No response

Hi @sindhunaydu
Thanks for your interest!

Hi @678098, I created a PR. While trying to setup the project locally I ran into couple of issues,

when I ran the $ mvn clean install command, I'm getting the following error -

No docker image was provided
Script usage:
	docker-build.sh image_name
	BMQ_DOCKER_IMAGE=image_name docker-build.sh
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

In the readme file Docker was not mentioned, not sure what I am missing here.

In the Building BlazingMQ Backend section, the link to setting up backed seems to be broken, its returning a 404 (https://github.com/bloomberg/blazingmq-sdk-java/blob/main/www.github.com/bloomberg/blazingmq)

@sindhunaydu thank you for the feedback,

This problem is related to integration tests run. We use docker image with bmqbrkr here to test SDK.
We will make this process smooth once we have docker image published in a public registry.
For now it's easier to use other mvn commands, to build: mvn clean compile to run UTs: mvn -B -q -Dspotbugs.skip=true -Dspotless.check.skip=true test
Updated broken link here: https://github.com/bloomberg/blazingmq-sdk-java/pull/17

Thanks for the fix @678098. and yes, this command works - mvn -B -q -Dspotbugs.skip=true -Dspotless.check.skip=true test.

Fixed: https://github.com/bloomberg/blazingmq-sdk-java/pull/16


Add b.p.fuelCladLocked

Description
This PR adds a block parameter to indicate if the fuel and clad are physically locked. This is a common interaction of interest in SFRs.
Also cleaning up _isFuelLocked in the axialExpansionChanger to leverage ArmiObject::getComponent.

Checklist

[x] This PR has only one purpose or idea.
[ ] Tests have been added/updated to verify that the new/changed code works.

Its use is reserved for separate ARMI plugins.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[ ] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

@sammiller11235

@john-science I think it's safe to say coverage drop is coverage spray here.


Extract lambda to named function in monai transforms for dataloader

Description
Pickling of lambda functions is not supported in Windows, causing issue with get_features when iterating over dataset. Extraction of lambda x: x["image_path"].as_tensor() into named function called image_as_tensor on get_transforms sidesteps the issue.
Change adds support for running get_features on Windows 10.
See here: https://discuss.pytorch.org/t/cant-pickle-local-object-dataloader-init-locals-lambda/31857
Related Issue
https://github.com/AIM-Harvard/foundation-cancer-image-biomarker/issues/306
Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[x ] 🔧 Bug fix (non-breaking change which fixes an issue)
[ ] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[ ] I've read the CODE_OF_CONDUCT.md document.
[x ] I've read the CONTRIBUTING.md guide.
[ ] I've updated the code style using make codestyle.
[ ] I've written tests for all new methods and classes that I created.
[ ] I've written the docstring in Google format for all the methods and classes that I used.

Summary by CodeRabbit

New Features

Introduced a new function to convert image paths to tensor representations, enhancing the transformation process.

Improvements

Streamlined transformation logic by replacing inline functions with a dedicated method for better readability and maintainability.

@iamrjgs Thank you for proposing this PR! I will merge this and closed the associated issue


use FileOutputStream and FileInputstream for roundTripStateEngine in HollowHistoryUI

Trying to write to temp file and use FileOutputStream and FileInputStream to apply changes in HollowHistoryUIKeyIndex

Thoughts on this @toolbear ?

Hi @toolbear,
Updated the code based on your comments! Thanks!


Set release "Installation Directory" to /Applications

Fixes an issue where xcode builds generic xcode archives instead of iOS app archives
http://stackoverflow.com/a/30921685/1720355

Is this a thing that still needs to happen?

Yeah, I think we actually need to not set it in this project. It causes a super weird error so it would be best to prevent it.

Here's where I fixed it in Tropos https://github.com/thoughtbot/Tropos/pull/155

Cool, we could just delete that key as part of our project setup.

This can be closed now that #245 is merged.


Experiment: Proxy models for transforming scraped data into OCD format

As I was working through Code Rush development, I struggled a bit to get my mind around our most complex management commands: localcandidatecontests.
Two observations stood out to me:

The command is doing more than just loading CandidateContest objects. It is also creating the lion's share of our Election records and Candidacies. That requires it to contains numerous model methods that both overlap and spiral off from each other.
Several of those methods, with names like get_election_from_name, exist primarily to transform and preprocess records from the scraped data models on an object-by-object basis.

Attached is an experiment with simplifying the command by breaking it apart and offloading the object transformations to Django's proxy model system.
In addition to separating some of the programming logic for simplicity and readability, my hope is that this technique would allow for unittests tailored for the proxies. That would allow us to verify the many edge cases we need to handle with this difficult dataset.
Let's talk it over during Monday's class. I'm interested to get your take on this approach.

Coverage decreased (-0.5%) to 89.075% when pulling e588e58176a4f934b8ecd6a3d31f9ab16e82ccbd on separate-ocd-election into df17260472d9c671dd6f416e1b45c85553c19ac3 on master.


Provisions Count in Registry is including/counting views of the module's Registry page

Bug description 🐞
The provisions count for a module's listing in the Registry is counting page views.

This module has never been used, and it increments every time I refresh the page. Because the module has never been used, I'm not sure whether the bug is that page views are being added to module downloads, or if provisions is only displaying page views.
I'm currently running Terrakube 2.23.2
Steps to reproduce

Publish a module in the registry in a Terrakube Workspace
View the module
Note the provision count
Refresh the page
Note the increased provision count

Additionally, it appears the count increases even when viewing/refreshing the top level Registry page.
Expected behavior
Only the number of time the module has been downloaded to a workspace is displayed.
Example repository
No response
Anything else?
No response

The UI is using the same registry endpoint so if you see the registry in the UI it will be the same as downloading when using the terraform CLI that is why the count change


[FR] have intermediate calculations forwarded to next interation step in FOR-loop

In AQL it is not possible to have a state within a FOR-loop.
This is a very simple example:
FOR i IN [2,-1,4,-8,8]
// this internally calulates
// s = 2
// s += -1      | this is ok, because this will set s to 1
// s += 4
// s += -8      | this is not ok, because this will set s to -3
// s += 8
COLLECT AGGREGATE s=SUM(i)
RETURN s        | this returns 5, but I want it to return 13

What if I want to only add the value of i to s if the current s + i results in a positiv value? It is not impossible because I don't know anything about the current s.
Idea
Why not introduce a REDUCE next to COLLECT and WINDOW that allows to read intermediate values to achieve something that could be done with map-reduce.
FOR i IN [2,-1,4,-8,8]
REDUCE s = i + CURRENT INTO sumUp
FILTER sumUp.s >= 0
RETURN sumUp.s           | this would return 13

or for multiple calculations
FOR i IN [2,-1,4,-8,8]
REDUCE s = i + CURRENT.s, t = i - CURRENT.t INTO sumUp
FILTER sumUp.s >= 0 && sumUp.t != 0
RETURN sumUp

I would like to try an implementation. Is there anything that speaks against it technically wize? Any thing wrong with my thoughts?

related to https://github.com/arangodb/arangodb/pull/9139

thx to @mpoeter for clarifying that this is not going to work or that it is far from being trivial, resp.


Vim: Caught deadly signal ABRT!

After compiling vim from source I'm getting the above error. Any help to solve it?

Not sure of this is related to your crash, but check whether you have these command line options to compile Vim (without them, Vim will crash at startup):
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1

Normally the configure script should take care of setting those options, but perhaps it did not work for you somehow.
If you still have a crash, please provide a stack trace with gdb, or better, run Vim with valgrind like this for example:
$ valgrind --track-origins=yes --num-callers=50 ./vim 2> valgrind.log

And provide the output in valgrind.log if you see errors there.

Well I uninstalled the self compiled version . Because I found a package vim-nox on Debian repository which did my job :-)
Should I close this issue?

Well, a self-compiled version should also work. So a backtrace could help to see if there is an actual problem with Vim. So if you can, please also provide the gdb backtrace and answer the other questions.

I have the same exact issue but it seems to kick in with hidden files
vim(54562,0x7fff738aa000) malloc: *** error for object 0x616d726f665f676e: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Process 54562 stopped

Yes, this is already a known problem, I am sure, there will be a patch soon.  BTW: I believe there is an error in your timer script/plugin.

I have the same problem and this is how I produce the issue.

Type vim ~/.vim/vimrc. Press Enter.
Do nothing but press a key.

Vim immediately exits and shows the same error like in the screenshot above. Also, pressing some other keys like i are doing exact same thing.
$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul  9 2017 17:13:01)
MacOS X (unix) version
Included patches: 1-703
Compiled by Homebrew

well, disable your timer plugins as a workaround.

Disabling Shougo/neocomplete.vim plugin did the job as workaround.

I went back to 8.0.698

Looks like this is likely fixed with https://github.com/vim/vim/commit/cae24be4a808d60313913cc6feea6c2bee2e2a42.
For reference, the backtrace I saw was:
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
  * frame #0: 0x000000010d78a83b vim`free_msglist + 15
    frame #1: 0x000000010d78af5a vim`discard_exception + 387
    frame #2: 0x000000010d78a7e3 vim`discard_current_exception + 27
    frame #3: 0x000000010d775a39 vim`check_due_timer + 516
    frame #4: 0x000000010d805013 vim`WaitForChar + 69
    frame #5: 0x000000010d804f51 vim`mch_inchar + 267
    frame #6: 0x000000010d87ad83 vim`ui_inchar + 161
    frame #7: 0x000000010d7abea1 vim`inchar + 535
    frame #8: 0x000000010d7adfe2 vim`vgetorpeek + 1356
    frame #9: 0x000000010d7ad6d0 vim`vgetc + 325
    frame #10: 0x000000010d7aeddb vim`safe_vgetc + 9
    frame #11: 0x000000010d740cfe vim`edit + 2206
    frame #12: 0x000000010d7ed184 vim`invoke_edit + 79
    frame #13: 0x000000010d7e25b0 vim`normal_cmd + 4717
    frame #14: 0x000000010d8b5d9b vim`main_loop + 1216
    frame #15: 0x000000010d8b5675 vim`vim_main2 + 4034
    frame #16: 0x000000010d8b4168 vim`main + 4840
    frame #17: 0x00007fffbea48235 libdyld.dylib`start + 1

fixed by 8.0.0705

by typo command vim ~/. big rates repeats it, the iTerm2 got dead and can not quit with Ctrl + c, and vim progress took more than 60% cpu shown by Activity Monitor.
first run caused totally dead with output:
Vim: Caught deadly signal ABRT

Vim: Finished.
[1]    73564 abort      vim ~/.

and then, no die with another signal:
$vim ~/.
Vim: Caught deadly signal SEGV

Vim: Finished.
[1]    73824 segmentation fault  vim ~/.

and if iTerm2 not dead with "signal SEGV", command output after that on this iTerm window/tab tty messed up, this screen shot:

vim ver and my macos ver10.13.6
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jun 25 2019 20:35:29)
Included patches: 1-503, 505-680, 682-1283, 1365
Compiled by<EMAIL_ADDRESS>Normal version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    -mouse_sgr       +tag_old_static
-arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           -mouse_urxvt     -tcl
-balloon_eval    +folding         +mouse_xterm     -termguicolors
-browse          -footer          +multi_byte      -terminal
+builtin_terms   +fork()          +multi_lang      +terminfo
+byte_offset     -gettext         -mzscheme        +termresponse
+channel         -hangul_input    +netbeans_intg   +textobjects
+cindent         +iconv           +num64           +timers
-clientserver    +insert_expand   +packages        +title
-clipboard       +job             +path_extra      -toolbar
+cmdline_compl   +jumplist        -perl            +user_commands
+cmdline_hist    -keymap          +persistent_undo +vertsplit
+cmdline_info    +lambda          +postscript      +virtualedit
+comments        -langmap         +printer         +visual
-conceal         +libcall         -profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             -rightleft       +windows
+diff            +menu            +ruby/dyn        +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
-emacs_tags      -mouseshape      +startuptime     -xpm
+eval            -mouse_dec       +statusline      -xsmp
+ex_extra        -mouse_gpm       -sun_workshop    -xterm_clipboard
+extra_search    -mouse_jsbterm   +syntax          -xterm_save
-farsi           -mouse_netterm   +tag_binary

Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L/usr/local/lib -o vim        -lm -lncurses  -liconv -framework Cocoa

after upgrade to homebrew ver:
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 23 2019 17:05:41)
macOS version

bug still

@Justsoos please first try to reproduce with an uptodate Vim version. If you can still reproduce the crash, please provide a stack trace as mentioned earlier in this issue here.


headers instead of header

Running the program TestClient we have seen that the json sent to the endpoint has the field headers instead of header, as described in the xfs4iot documentation.

Thanks Alvaro.
You are right on this. the property name should be 'header' rather than 'headers'.
The reason of why KAL used 'headers' is because the XFS common interface had this property name 'headers' initially and corrected. However, KAL didn't update this fix internally in our SP framework accordingly.
We are tracking this issue internally and we will update SP framework once issue is addressed.

Hi Alvaro,
We are planning to add fix in the next package v0.0.2-alpha.2 including TextTerminal SP framework.
It will be published before next workshop planned on the 3rd August.

New package v0.0.2-alpha.2 addresses this issue.


Support Secp256r1 signature verification

Following up on a "Bonus Point" in #751, it'd be great to have Secp256r1 signature verification.
This would allow iOS/Android hardware-backed signatures, e.g. for smart contract wallets. (Similar: cosmos/cosmos-sdk#7718)

This would be doable. What do you need it for? We are curious about the use case and priority.

@reuvenpo do you have any opinion on this? You asked for Secp256r1 recently in a different context.

I was asking about it because I thought Cosmos were adding support for it on the client side, so I thought that I'd need to support it on the Secret Network's enclave side. But since that's not the case, I do not have any use for secp256r1 in any context.

For the record, I don't think it's a good design choice to put these functions in the final VM API. I think it should be in cw-plus and I'm sure there a way to eliminate all the bloat that comes with it by default in order to minimize binary size.

For the record, I don't think it's a good design choice to put these functions in the final VM API. I think it should be in cw-plus and I'm sure there is a way to eliminate all the bloat that comes with it by default in order to minimize binary size.

@webmaster128  can probably answer this better than me, but I think it's not so much an issue of module size (though that's relevant, too), but performance (gas usage).
By putting the crypto stuff in the VM, it compiles to native code instead of wasm, with a significant performance improvement. Given that crypto primitives are usually computationally intensive, this makes particular sense  here.

This request is resonable but out of scope for 1.0.0. A draft implementation is developed in #1083. It can be added to a running chain later on via a new feature flag in a non-breaking way.

This seems to become more important for account abstraction. I put this on the agenda for after CosmWasm 2.0.

See follow-up ticket https://github.com/CosmWasm/cosmwasm/issues/2001 for everything you need to know about secp256r1 support.


Quota exceeded not handled

⚠ Check for existing issues before proceeding. ⚠

[X] I have searched the existing issues, and there is no existing issue for my problem

Where are you using SuperAGI?
Linux
Which branch of SuperAGI are you using?
Main
Do you use OpenAI GPT-3.5 or GPT-4?
GPT-4
Which area covers your issue best?
Logging
Describe your issue.
I ran out of quota on my openai account and the agent kept trying to do the same thing in a loop over and over again.
How to replicate your Issue?
Have auto re-charge disabled on openAI accoint and have $0 balance and try to run any agent.
Upload Error Log Content
superagi-celery-1           | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] error_code=insufficient_quota error_message='You exceeded your current quota, please check your plan and billing details.' error_param=None error_type=insufficient_quota message='OpenAI API error received' stream_error=False
superagi-celery-1           | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/llms/openai.py:82] - OpenAi RateLimitError:
superagi-celery-1           | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] OpenAi RateLimitError:
superagi-celery-1           | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/llms/openai.py:82] - You exceeded your current quota, please check your plan and billing details.
superagi-celery-1           | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] You exceeded your current quota, please check your plan and billing details.
superagi-celery-1           | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/jobs/agent_executor.py:95] - Exception in executing the step: Failed to get response from llm
superagi-celery-1           | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] Exception in executing the step: Failed to get response from llm
superagi-celery-1           | [2023-09-23 21:31:51,020: INFO/MainProcess] Task execute_agent[0931cc4d-da39-4e36-b7b6-9aeb5b0c48aa] received
superagi-celery-1           | [2023-09-23 21:31:51,021: INFO/ForkPoolWorker-8] Task execute_agent[43c135c0-209d-41c8-8f2f-622ff660ee42] succeeded in 0.28975934800018877s: None

We're adding OpenAI Error Handling in the next version.


Error: deleting S3 Bucket (kf-artifact-store-***): BucketNotEmpty: The bucket you tried to delete is not empty

Describe the bug
When I use the terraform source code in link to uninstall Kubeflow on AWS with a command.
Steps To Reproduce
make delete

The bug is:
Error: deleting S3 Bucket (kf-artifact-store-***): BucketNotEmpty: The bucket you tried to delete is not empty
status code: 409, request id:***, host id: ***
Makefile:47: recipe for target 'delete-kubeflow-components' failed
make: *** [delete-kubeflow-components] Error 1

Expected behavior
I expected to resolve how to delete s3 bucket if it's empty
Environment

Kubernetes version: 1.21
Using EKS (yes/no), if so version? yes, 1.21
Kubeflow version: 1.6
AWS build number:
AWS service targeted (S3, RDS, etc.): fails on S3-RDS

Screenshots

Hi @namnd00 , thanks for reporting the issue. This is expected behavior. You will have to set the force_destroy_s3_bucket variable to true for deleting a non empty bucket. Can you check if you have set it to true?


Interface GRAPH not maintained in factory method

When running the ZADF_DEMO_AZURE_GRAPH program after configuring it, the error message "Interface Type not Maintained for Interface ADB2CGR_GE" occurs.
https://github.com/microsoft/ABAP-SDK-for-Azure/blob/adad8f956c98ebd218aae0eb4e37af6e90644e20/src/zadf/zcl_adf_service_factory.clas.abap#L100
Is there a reason the GRAPH instantiation is not implemented in zcl_adf_service_factory=>create( )?

Hi @colbyhemond,
We have moved the instantiation object for the same. Kindly check now and let us know if you are still facing issues.
Thanks,
Sanju

@Sanjukum19 that did the trick! Thanks!


Decouple geopyspark and geopyspark-netcdf versions

The two do not iterate at the same rate and while we have not imposed the semver on these projects yet it would be much easier to iterate and test rather than bumping the geopyspark-netcdf version manually.
The deeper issue is that the way geopyspark-netcdf jars are being discovered during runtime are coupled to the geopyspark version.

See https://github.com/geotrellis/geopyspark-netcdf/issues/16

geopyspark-netcdf has been replaced with NetCDF and HDF5 (through rasterio and/or the GDAL Python bindings).


Analyze and display item peak and RMS" - show which item is analyzed currently

Above action can analyze and display multiple selected items consecutively, cool.
However in the analyzing window it can't be seen which item is currently analyzed and displayed.

(sorry I've originally submitted on the old Googlecode before realizing it moved here)

Can be done via scripts now.


inconsistent lints between CI and local dev

very frustrating to correct clippy lints when clippy doesn't report them locally

Dup of #56


No workspace directory is generated

It doesnt generate a workspace directory

Hello, which version are you using?

the most recent version, i compiled it from source

The latest version of RetroMCP does not create workspaces anymore. You must manually create a workspace folder and import the projects there


NETOBSERV-117: show loading/empty/error state in netflow table

Shows empty and error states according to PatternFly guidelines.
This PR does not complete NETOBSERV-117. When NETOBSERV-72 and NETOBSERV-74 are completed, the "clear all filters" button will implement the supposed functionality.

It also adds a spinning icon that is shown when the page is loaded/refreshed completely but not when the table is refreshed through the dropdown:
https://user-images.githubusercontent.com/939550/147267936-4fb66656-6fbc-438e-88e9-ed5b7cc150da.mp4

LGTM, just need to rebase, and bind the Clear all filters button from bodyContent
You can move clearAll const from filters-toolbar.tsx to netflow-traffic.tsx and send it through props to share it between React.FC


s2p: Evaluate/Implement LRU cache with configurable size

It shall be evaluated whether an LRU cache results in a performance gain. If it does, it shall be implemented with a configurable size. In case it turns out that such a cache outperforms the PiSCSI legacy cache, the latter shall be removed.

Isn't better/easier to use mmap and let the kernel worry about caching which is quite good at?

If you want to let the kernel do the work just use one of the non-legacy caching modes, which are filesystem based.

Is not the same thing, each read/write operations requires context switches which are quite expensive...
I forgot to mention that mmap will NOT work for 32bit systems as it won't be able to map files over 2GB, so it's probably a bad idea anyway ...


Typo in README.md

"The cluter JSON below is for Azure Databricks" should be "The cluster..."

Fixed by #24


appengine/php72/wordpress sample does not work

Hi, I've been trying to deploy WP on GAE for several hours. I'm able to deploy the app by when accessing it I get into a redirect loop at /wp-admin.
I'm not very WP knowledgeable. Have anyone successfully deployed this sample?

I got the following error after deploy:
Warning: require(/srv/index.php): failed to open stream: No such file or directory in /srv/gae-app.php on line 41 Fatal error: require(): Failed opening required '/srv/index.php' (include_path='.:/usr/lib/php') in /srv/gae-app.php on line 41
any idea?

Looks like wordpress is not moved to the right place from the log:
Downloading the WordPress archive...
PHP Warning:  rename(): The first argument to copy() function cannot be a directory in /home/.../php72/wordpress/vendor/google/cloud-tools/src/Utils/WordPressProject.php on line 161
PHP Warning:  rename(/tmp/wordpress,/home/.../php72/wordpress/my-wordpress-project): Invalid cross-device link in /home/.../php72/wordpress/vendor/google/cloud-tools/src/Utils/WordPressProject.php on line 161

@tkhduracell this happened to me when I didn't add the app.yaml from files/app.yaml. Can you confirm you have an app.yaml that looks like the one here?
@liarsing This is from the command which downloads wordpress to a temporary directory and then moves it into the project directory. Is it possible your temporary directory (e.g. sys_get_temp_dir) is actually mounted from another device?

@bshaffer I used cloud shell to do this and the /tmp is pre-configured. After I changed the sys_get_temp_dir to another directory, wordpress deployed successfully.

I also just updated the WordPress README to be more readable, so hopefully this will also help

@tkhduracell I think the issue was also with a bug where App Engine Standard does not set the HTTPS server variable, which WordPress depends on. Without this, WordPress redirects to https, which causes an infinite loop. The fix is to do the following, which has been added to the WordPress sample front controller:

$_SERVER['HTTPS'] = $_SERVER['HTTP_X_APPENGINE_HTTPS'];

I'm closing this because I believe it's fixed, but please open a new issue if the problem persists!


global whitelist?

I have some mocha test files I want to standardize, but I'm getting errors about describe, it, etc being undefined.
normalize-license* master » standard --format
Error: Use JavaScript Standard Style (https://github.com/feross/standard)
  test/index.js:7:0: 'describe' is not defined.
  test/index.js:8:2: 'describe' is not defined.
  test/index.js:11:4: 'it' is not defined.

I know this is one of the things some people don't like about mocha, but I'm a fan of this design choice, as it reduces boilerplate code in tests. Is there a way to whitelist globals in package.json or something?

Add this to the top of your file:
/* global describe, it */
On Wednesday, April 1, 2015, Zeke Sikelianos<EMAIL_ADDRESS>wrote:

I have some mocha test files I want to standardize, but I'm getting
errors about describe, it, etc being undefined.
normalize-license* master » standard --format
Error: Use JavaScript Standard Style (https://github.com/feross/standard)
test/index.js:7:0: 'describe' is not defined.
test/index.js:8:2: 'describe' is not defined.
test/index.js:11:4: 'it' is not defined.
I know this is one of the things some people don't like about mocha, but
I'm a fan of this design choice, as it reduces boilerplate code in tests.
Is there a way to whitelist globals in package.json or something?
—
Reply to this email directly or view it on GitHub
https://github.com/feross/standard/issues/101.

--
Simple & Secure Bitcoin Wallet: https://www.coinbolt.com
Bitcoin / JavaScript: http://cryptocoinjs.com
Follow JP Richardson on Twitter: https://twitter.com/jprichardson

:metal:

For those who stumble upon this issue, @jprichardson's suggestion is a jshint thing: http://jshint.com/docs/

👍  thanks

For mocha globals specifics , I use /* eslint-env mocha */


angular.foreach object instance assignment issue

I don't know if this has been fixed in later versions, but in a project using angujarjs v1.2.4, I came across a situation with an angular.foreach going through a device array of objects, and assigning a string to an attribute of an object instance:
angular.forEach($scope.deviceArray, function(device, di) {
	$scope.deviceArray[di]._value = dataArray[di];
});

This is what I found through this method.  Let's say we have an object in the deviceArray at row 2, and it has the same attributes and attribute values as another object in that deviceArray (at row 4 and 5).  When we get to row 5 in this loop, if we assign deviceArray[5]._value to dataArray[5], then what happens is that the _value attribute in rows deviceArray[2] and deviceArray[4] gets assigned to what deviceArray[5]'s _value attribute is assigned, overwriting their previously assigned values.  I would assume that each object in this array would have its own uniqueness, primarily by index, but for some reason, when using an angular.forEach, it doesn't matter if I'm assigning row 2 or row 5, assigning the attribute of one updates all other ones in that array.
The way I fixed it was this way:
for (var a = 0; a < $scope.deviceArray.length; a++) {
	$scope.deviceArray[a]._value = dataArray[a];
}

Somehow, this worked and solved my problem, but I can't help but feel there is a problem with the angular.forEach in how it treats objects in arrays uniquely from each other.

Do you think that you could reproduce this issue? I'm not sure I understand what you're asking and could probably help if I did. I created a starter jsbin for you: http://jsbin.com/batiqi/edit

Closing due to lack of response. Feel free to reopen if you can provide more info.


FEAT: Use click for command line interface

The python click library has a number of advantages of argparse alone. We should use click for our command line interface (CLI).
https://dbader.org/blog/python-commandline-tools-with-click
https://dbader.org/blog/mastering-click-advanced-python-command-line-apps
https://click.palletsprojects.com/en/7.x/quickstart/

I'm not sure this is actually necessary right now. We can revisit this later if need be.


6e Boostable charges not working

When a value (the number of charges to boost with?) is entered in the bootable box, the attack roll is not rolled, and the bootable value is reset to zero.
Steps to reproduce:

Create a character with 1d6 Blast with 4 charges, and the Boostable advantage.
Attack a target character.
In the to hit dialogue change the Boostable to a 1. I assume this is supposed to use 1 extra charge.
When you click on the "Roll to Hit" button, the Boostable value is reset to 0 and there is no other change.

Works, but the boostable charge box clears when select new tokens or otherwise gets refreshed.