chore(deps): Update tree-sitter dependencies to versions supporting Node 20

This PR upates the different tree-sitter dependencies to versions that are compatible with Node 19/20.
Background
The previously used version 0.20.x of tree-sitter (the exact version number depends on the specific tree-sitter-* sub-package) does not work on Node 19 and higher, leading to errors like the following:
Request initialize failed with message: bad export type for `tree_sitter_(tsx|csharp|typescript|...)_external_scanner_create`: undefined (Internal Error)

This broke e.g. the Official Cucumber VS Code extension when VS Code updated to a newer version of Node 19 (and later Node 20) that was not supported at the time by the tree-sitter library, but support has since been implemented and subsequently shipped in tree-sitter v0.21.0 and above.
Should fix the bad export type for ... error once the updated version is included cucumber/language-server and then cucumber/vscode that has been reported at least a couple times:

Fixes cucumber/language-server#102
Fixes cucumber/vscode#234
Fixes cucumber/vscode#243
Fixes cucumber/vscode#247
Fixes cucumber/vscode#155

Sidenote on versioning & compatibility of tree-sitter
The versioning and release scheme of the tree-sitter libraries is a bit "messy": The tree-sitter-typescript/tree-sitter-rust/... sub-libraries have a strong dependency on the major version number of tree-sitter, such that versions of the component libraries that require different major versions of the tree-sitter library cannot be used together. But they are:

Not released at the same time.
Do not have an central versioning number scheme.
Introduce incompatible dependency upgrades from one patch version to the next (e.g<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>while<EMAIL_ADDRESS>requires tree-sitter@0.22.1).

(though that does not strictly violate SemVer requirements due to still being a 0.x.y development version).
The approach taken here was to look for the newest version of tree-sitter for which all sub-libraries have at least one compatible release (which came out to be<EMAIL_ADDRESS>and to choose the newest version of each sub-library that still supports<EMAIL_ADDRESS>(which eliminated a few of the most recent releases).
Related PRs
This PR subsumes/replaces #225 as well as the following automated PRs (which have build failures due to trying to update the different dependencies separately):

#180
#183
#184
#185
#188 (tree-sitter updated to 0.21.1 instead of 0.22.1 due to compatibility requirements, see below)
#189 (tree-sitter-python updated to 0.23.4 instead of 0.23.6 due to compatibility requirements, see below)
#201
#234

Tests
Tested with a custom build of cucumber/vscode to work on my current VS Code version:
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.3-300.fc41.x86_64

A note on "missing import symbols" errors
If there are issues with missing import symbols (namely missing symbol 'abort' from module 'env') after this update, this is due to a (too old) version of emscripten being used to compile tree-sitter to WASM.
The solution in that case is to install a newer version of emscripten.

tree-sitter currently uses emscripten v3.1.64
My development environment used emscripten v3.1.74

@kieran-ryan Test failures should be fixed now (npm test completed successfully when I ran it on my machine just now).

@kieran-ryan Test failures should be fixed now (npm test completed successfully when I ran it on my machine just now).

Thanks a bunch for the contribution first and foremost @cr7pt0gr4ph7 - and for a well-documented pull request; will be super to have this issue resolved! Will look to fully test and review soon as I can - as time allows off on the back of holidays. Checking, are you testing on Windows by any chance; or any other other detail you can provide on your runtime? Will try to replicate difference in test outcome between running locally and the pipeline. There are some disparities in testing with the project which require resolution at some point to improve the contributing experience.
Suspect failing due to instability of query specifiers in tree-sitter language implementations (at least very early versions pinned in the package) which may have changed since with these updates - see tree-sitter-rust #226 for reference of associated changes. May not be the case, though was anticipating query changes with these upgrades.
Tree-sitter's live playground can be used to check the query and test data associated with a language-implementation for compatibility - compared to the older versions our queries were compatible with; though you may want to run a local tree-sitter playground against the specific language implementation versions you are running locally for accuracy as they may differ.

Checking, are you testing on Windows by any chance; or any other other detail you can provide on your runtime?

I'm running on Linux Bluefin (Fedora-based) inside a Docker container:
$ uname --all
Linux a8f8f4bfa59d 6.11.3-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Oct 10 19:18:36 UTC 2024 x86_64 GNU/Linux

$ node --version
v22.12.0

Will try to replicate difference in test outcome between running locally and the pipeline. There are some disparities in testing with the project which require resolution at some point to improve the contributing experience.

I'll have a look at the failed tests.

Suspect failing due to instability of query specifiers in tree-sitter language implementations (at least very early versions pinned in the package) which may have changed since with these updates - see tree-sitter-rust #226 for reference of associated changes. May not be the case, though was anticipating query changes with these upgrades.

The test failures which I could observe locally were partially due to syntax tree changes in tree-sitter-csharp. I'll have a look!

Tree-sitter's live playground can be used to check the query and test data associated with a language-implementation for compatibility - compared to the older versions our queries were compatible with; though you may want to run a local tree-sitter playground against the specific language implementation versions you are running locally for accuracy as they may differ.

Thanks for the pointer! I actually looked for a Tree-sitter playground, but Google did not provide any helpful results. The manual page you linked does not even appear on the first page of results...


Start up windows batch file to start the translator

not neccessary but wouldn't hurt adding this

@S3RL4 you created this PR twice

@S3RL4 you created this PR twice

yeah b

This may not work if people are installing the python packages in a virtual environment and have to specify the full path to the python executable.


update the readme file, it is outdated to v0.2.4

Will write new docs after the release of v0.5.0

ITIS DONE


Add line comments to legacy parser

Actually, let's not do this right now. This PR makes multiple tests fail where the empty pattern literal is used // and also the rules around // have to be slightly changed because of arguments that contain // somewhere. Both things can be solved, but it's not worth our time right now.


Link to COMPLETE documentation for YAML files for containers

We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
THEN please provide a link. There is no link to provide feedback on the article:
azure-docs/articles/container-instances/container-instances-multi-container-yaml.md (and several others related to creating container groups). Further, the HTML page rendering is broken (at least in MS Edge on Windows 10) - lots of extraneous !INCLUDE and !NOTE garbage.
THE FUNDAMENTAL ISSUE WITH TUTORIALS:
YAML files are mentioned in several articles related to creating a container group. The tutorial readmes have specific content for the specific narrow issue addressed by the tutorial. But there is no link to a specification (documentation for all options/properties) for YAML files to describe container groups.
It is aggravating and frustrating to have to bounce between multiple slightly related "tutorials" to try to piece together what can and cannot be done with particular technology (in this case, describing the container instance using YAML, and specifically, figuring out how to specify the dnsConfig property, and figuring out what minimum set of properties is required and what are optional).
Jack

Hi @TurtleBeach - Thank you for your feedback! We will review and update as appropriate.

CC: @dlepow @MicahMcKittrick-MSFT

@TurtleBeach - Thanks very much for the feedback. We have a backlog documentation work item to create reference documentation for the ACI YAML files, and based on your feedback I will recommend that we prioritize this work higher. In the meantime, you might take a look at the container group/instance properties configurable in the Resource Manager template spec. While the YAML syntax differs (obviously) from the template JSON, and the template allows you to specify other Azure resources, the template spec should help clarify the hierarchy of properties, which are required or optional, etc. I hope this helps.
cc:/ @dkkapur


Prepare to Release 6.0.0

6.0.0 will actually be released once the PR from next -> main is merged.


Missing output value

Hey guys,
I'm at the very beginning of my SD journey, just started to play around, focusing mainly on the Depth Map videos.
My issue is that I just can't figure out what's the missing output value. What do you recommend?
Traceback (most recent call last):
File "D:\Net programok\Stable Diffusion\stable-diffusion-webui\venv\lib\site-packages\gradio\routes.py", line 422, in run_predict
output = await app.get_blocks().process_api(
File "D:\Net programok\Stable Diffusion\stable-diffusion-webui\venv\lib\site-packages\gradio\blocks.py", line 1326, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "D:\Net programok\Stable Diffusion\stable-diffusion-webui\venv\lib\site-packages\gradio\blocks.py", line 1229, in postprocess_data
self.validate_outputs(fn_index, predictions)  # type: ignore
File "D:\Net programok\Stable Diffusion\stable-diffusion-webui\venv\lib\site-packages\gradio\blocks.py", line 1204, in validate_outputs
raise ValueError(
ValueError: An event handler (f) didn't receive enough output values (needed: 4, received: 3).
Wanted outputs:
[gallery, textbox, model3d, html]
Received outputs:
[None, "", "AttributeError: 'str' object has no attribute 'df'Time taken: 0.00s"]

Quick fix would be removing the last ".df" on line 56 of core.py
You could also revert to and older commit as discussed here https://github.com/thygate/stable-diffusion-webui-depthmap-script/issues/308

Sorry, my bad. Fixed now.


Update numpy array resolver

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

Comparison is base (1e9871a) 100.00% compared to head (fcb389c) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #178   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         7    +1
  Lines          165       175   +10
  Branches        34        34
=========================================
+ Hits           165       175   +10

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


🐛 [cloud_firestore] Fatal Exception: NSInvalidArgumentException -[NSNull getDocumentsWithSource:completion:]: unrecognized selector sent to instance

Bug report
Describe the bug
The application is crashing only in release mode (i have never seen this in profile or debug, but only when my app was on TestFlight).
Possibly linked to #6900 in the "Firestore logic handling for this", and only happens in release mode with TestFlight.
Really not often (2 times for 100 sessions in my app).
In debug / profile mode it never happened.
It's quite hard to debug as it doesn't give an error line from our code, and since this only happens in release mode i have no idea where to find such error in my app...
Steps to reproduce
Steps to reproduce the behavior:
Have no idea how to reproduce unfortunately as it happened only in release mode when my users are using it from TestFlight.
Expected behavior
The application should not crash.
Additional context
Here are the logs from Crashlytics :
Fatal Exception: NSInvalidArgumentException
-[NSNull getDocumentsWithSource:completion:]: unrecognized selector sent to instance 0x1ee0e1c00

Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                 0x18b2fe708 __exceptionPreprocess
1  libobjc.A.dylib                0x19fe087a8 objc_exception_throw
2  CoreFoundation                 0x18b201bfc -[NSOrderedSet initWithSet:copyItems:]
3  CoreFoundation                 0x18b301260 ___forwarding___
4  CoreFoundation                 0x18b303560 _CF_forwarding_prep_0
5  Runner                         0x1009b1700 -[FLTFirebaseFirestorePlugin queryGet:withMethodCallResult:] + 471 (FLTFirebaseFirestorePlugin.m:471)
6  Runner                         0x1009afb9c -[FLTFirebaseFirestorePlugin handleMethodCall:result:] + 226 (FLTFirebaseFirestorePlugin.m:226)
7  Flutter                        0x103618e44 (Missing)
8  Flutter                        0x10332b690 (Missing)
9  Flutter                        0x1036321a8 (Missing)
10 Flutter                        0x1035cdf78 (Missing)
11 Flutter                        0x1035cfdf8 (Missing)
12 CoreFoundation                 0x18b2791d4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
13 CoreFoundation                 0x18b278dd0 __CFRunLoopDoTimer
14 CoreFoundation                 0x18b278220 __CFRunLoopDoTimers
15 CoreFoundation                 0x18b271fd4 __CFRunLoopRun
16 CoreFoundation                 0x18b271308 CFRunLoopRunSpecific
17 GraphicsServices               0x1a28f4734 GSEventRunModal
18 UIKitCore                      0x18dcef75c -[UIApplication _run]
19 UIKitCore                      0x18dcf4fcc UIApplicationMain
20 Runner                         0x10038c5a8 main + 6 (AppDelegate.swift:6)
21 libdyld.dylib                  0x18af2dcf8 start

Crashed: com.google.firebase.crashlytics.ios.exception
0  FirebaseCrashlytics            0x1017bcd64 FIRCLSProcessRecordAllThreads + 180
1  FirebaseCrashlytics            0x1017bd144 FIRCLSProcessRecordAllThreads + 1172
2  FirebaseCrashlytics            0x1017b5f64 FIRCLSHandler + 48
3  FirebaseCrashlytics            0x1017b0930 __FIRCLSExceptionRecord_block_invoke + 92
4  libdispatch.dylib              0x18aeeb81c _dispatch_client_callout + 20
5  libdispatch.dylib              0x18aefa910 _dispatch_lane_barrier_sync_invoke_and_complete + 60
6  FirebaseCrashlytics            0x1017b00d0 FIRCLSExceptionRecord + 212
7  FirebaseCrashlytics            0x1017b03c8 FIRCLSExceptionRecordNSException + 536
8  FirebaseCrashlytics            0x1017afcb0 FIRCLSTerminateHandler() + 396
9  libc++abi.dylib                0x19fee8fa0 std::__terminate(void (*)()) + 20
10 libc++abi.dylib                0x19feebeac __cxa_rethrow + 148
11 libobjc.A.dylib                0x19fe08904 objc_exception_rethrow + 44
12 CoreFoundation                 0x18b2713f4 CFRunLoopRunSpecific + 836
13 GraphicsServices               0x1a28f4734 GSEventRunModal + 164
14 UIKitCore                      0x18dcef75c -[UIApplication _run] + 1072
15 UIKitCore                      0x18dcf4fcc UIApplicationMain + 168
16 Runner                         0x10038c5a8 main + 6 (AppDelegate.swift:6)
17 libdyld.dylib                  0x18af2dcf8 start + 4

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, 2.2.3, on macOS 11.5.2 20G95 darwin-x64, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[!] Android Studio (version 2020.3)
    ✗ Unable to find bundled Java version.
[✓] Connected device (4 available)

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.13.4
Flutter SDK 2.2.3
myappname 1.0.0+1

dependencies:
- app_tracking_transparency 2.0.1 [flutter]
- badges 2.0.1 [flutter]
- better_player 0.0.73 [flutter cupertino_icons wakelock pedantic meta flutter_widget_from_html_core visibility_detector path_provider collection xml]
- cached_network_image 3.1.0 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- camera 0.9.2+2 [camera_platform_interface flutter pedantic quiver flutter_plugin_android_lifecycle]
- clipboard 0.1.3 [flutter]
- cloud_firestore 2.5.1 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 3.0.2 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- connectivity 3.0.6 [flutter meta connectivity_platform_interface connectivity_macos connectivity_for_web]
- country_code_picker 2.0.2 [flutter modal_bottom_sheet collection universal_platform]
- crypto 3.0.1 [collection typed_data]
- cupertino_back_gesture 0.1.0 [flutter]
- cupertino_icons 1.0.3
- extended_image 4.2.1 [extended_image_library flutter meta]
- extended_tabs 2.3.0 [flutter]
- firebase_analytics 8.3.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_auth 3.1.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.6.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.2.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_database 7.2.1 [firebase_core flutter]
- firebase_dynamic_links 2.0.9 [firebase_core flutter]
- firebase_in_app_messaging 0.5.0+9 [firebase_core flutter meta]
- firebase_messaging 10.0.6 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_performance 0.7.0+9 [firebase_core firebase_core_platform_interface firebase_performance_platform_interface flutter]
- firebase_storage 10.0.3 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_app_badger 1.2.0 [flutter]
- flutter_arc_text 0.5.0 [characters flutter]
- flutter_cache_manager 3.1.2 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_contacts 1.1.0+4 [flutter]
- flutter_facebook_auth 3.5.1 [flutter flutter_facebook_auth_platform_interface flutter_facebook_auth_web]
- flutter_image_compress 1.1.0 [flutter]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_local_notifications 8.1.1+2 [flutter flutter_local_notifications_platform_interface platform timezone]
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_sound_lite 8.3.10 [path_provider recase uuid provider path synchronized logger flutter flutter_sound_platform_interface flutter_sound_web]
- flutter_staggered_grid_view 0.4.0 [flutter]
- flutter_svg 0.22.0 [flutter meta path_drawing vector_math xml]
- fluttertoast 8.0.8 [flutter flutter_web_plugins]
- geocoding 2.0.1 [flutter geocoding_platform_interface]
- geolocator 7.6.0 [flutter geolocator_platform_interface geolocator_android geolocator_apple geolocator_web]
- google_maps_flutter 2.0.8 [flutter flutter_plugin_android_lifecycle google_maps_flutter_platform_interface]
- google_mobile_ads 0.13.4 [meta flutter]
- google_sign_in 5.1.0 [flutter google_sign_in_platform_interface google_sign_in_web meta]
- image_editor 1.0.0 [flutter]
- in_app_review 2.0.3 [flutter in_app_review_platform_interface]
- intl 0.17.0 [clock path]
- light_compressor 1.2.1 [flutter]
- modal_bottom_sheet 2.0.0 [flutter]
- path 1.8.0
- path_provider 2.0.3 [flutter path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- permission_handler 8.1.4+2 [flutter meta permission_handler_platform_interface]
- photo_manager 1.3.1 [flutter]
- progressive_image 2.0.0 [flutter]
- provider 6.0.0 [collection flutter nested]
- pull_to_refresh 2.0.0 [flutter]
- rive 0.7.28 [collection flutter graphs http meta]
- scroll_to_index 2.0.0 [flutter]
- scrollable_positioned_list 0.2.0-nullsafety.0 [flutter collection]
- share_plus 2.1.4 [meta mime flutter share_plus_platform_interface share_plus_linux share_plus_macos share_plus_windows share_plus_web]
- shared_preferences 2.0.7 [flutter meta shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sign_in_with_apple 3.0.0 [flutter meta]
- sliver_tools 0.2.5 [flutter]
- sqflite 2.0.0+4 [flutter sqflite_common path]
- translator 0.1.7 [http]
- url_launcher 6.0.10 [flutter meta url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.4 [crypto]
- video_thumbnail 0.4.3 [flutter]
- visibility_detector 0.2.0 [flutter]
- volume_watcher 2.0.1 [flutter]
- webview_flutter 2.0.12 [flutter]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- archive 3.1.2 [crypto path]
- args 2.2.0
- async 2.6.1 [meta collection]
- boolean_selector 2.1.0 [source_span string_scanner]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- camera_platform_interface 2.1.0 [cross_file flutter meta plugin_platform_interface stream_transform]
- characters 1.1.0
- charcode 1.2.0
- clock 1.1.0
- cloud_firestore_platform_interface 5.4.1 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.4.1 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.0.10 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.0.12 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.15.0
- connectivity_for_web 0.4.0+1 [connectivity_platform_interface flutter_web_plugins flutter]
- connectivity_macos 0.2.1+2 [flutter connectivity_platform_interface]
- connectivity_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- cross_file 0.3.1+4 [flutter meta]
- csslib 0.17.0 [source_span]
- extended_image_library 3.1.0 [crypto flutter http_client_helper path path_provider]
- fake_async 1.2.0 [clock collection]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 2.0.1 [flutter meta]
- firebase_analytics_web 0.3.0+1 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_auth_platform_interface 6.1.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.1.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.1 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.1.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.1.2 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 3.0.5 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.0.5 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_performance_platform_interface 0.0.1+2 [firebase_core flutter plugin_platform_interface]
- firebase_storage_platform_interface 4.0.2 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.0.2 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flutter_blurhash 0.6.0 [flutter meta pedantic]
- flutter_facebook_auth_platform_interface 2.7.0 [flutter plugin_platform_interface]
- flutter_facebook_auth_web 2.6.0+2 [flutter flutter_web_plugins js flutter_facebook_auth_platform_interface]
- flutter_local_notifications_platform_interface 4.0.1 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 2.0.3 [flutter]
- flutter_sound_platform_interface 8.3.10 [flutter meta plugin_platform_interface logger]
- flutter_sound_web 8.3.10 [flutter_sound_platform_interface flutter logger flutter_web_plugins meta js]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- flutter_widget_from_html_core 0.6.2 [csslib flutter html]
- geocoding_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- geolocator_android 1.0.0 [flutter geolocator_platform_interface]
- geolocator_apple 1.2.0 [flutter geolocator_platform_interface]
- geolocator_platform_interface 2.3.4 [flutter plugin_platform_interface vector_math meta]
- geolocator_web 2.0.6 [flutter flutter_web_plugins geolocator_platform_interface]
- google_maps_flutter_platform_interface 2.1.1 [collection flutter meta plugin_platform_interface stream_transform]
- google_sign_in_platform_interface 2.0.1 [flutter meta quiver]
- google_sign_in_web 0.10.0+2 [flutter flutter_web_plugins google_sign_in_platform_interface js meta]
- graphs 2.0.0
- html 0.15.0 [csslib source_span]
- http 0.13.3 [async http_parser meta path pedantic]
- http_client_helper 2.0.2 [http]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image 3.0.2 [archive meta xml]
- in_app_review_platform_interface 2.0.2 [flutter url_launcher plugin_platform_interface platform]
- js 0.6.3
- logger 1.1.0
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- mime 1.0.0
- nested 1.0.0 [flutter]
- octo_image 1.0.0+1 [flutter flutter_blurhash]
- path_drawing 0.5.1 [vector_math meta path_parsing flutter]
- path_parsing 0.2.1 [vector_math meta]
- path_provider_linux 2.0.2 [flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.2 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.3 [ffi flutter meta path path_provider_platform_interface win32]
- pedantic 1.11.1
- permission_handler_platform_interface 3.6.1 [flutter meta plugin_platform_interface]
- petitparser 4.1.0 [meta]
- platform 3.0.2
- plugin_platform_interface 2.0.1 [meta]
- process 4.2.3 [file path platform]
- quiver 3.0.1 [matcher]
- recase 4.0.0
- rxdart 0.27.2
- share_plus_linux 2.0.4 [share_plus_platform_interface file flutter meta url_launcher]
- share_plus_macos 2.0.2 [share_plus_platform_interface flutter]
- share_plus_platform_interface 2.0.1 [flutter meta mime plugin_platform_interface]
- share_plus_web 2.0.4 [share_plus_platform_interface url_launcher flutter flutter_web_plugins meta]
- share_plus_windows 2.0.3 [share_plus_platform_interface flutter meta url_launcher]
- shared_preferences_linux 2.0.2 [file meta flutter path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.2 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.2 [flutter flutter_web_plugins meta shared_preferences_platform_interface]
- shared_preferences_windows 2.0.2 [flutter file meta path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- sqflite_common 2.0.1 [synchronized path meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0
- term_glyph 1.2.0
- test_api 0.3.0 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.8.0 [path]
- typed_data 1.3.0 [collection]
- universal_platform 1.0.0+1
- url_launcher_linux 2.0.2 [flutter]
- url_launcher_macos 2.0.2 [flutter]
- url_launcher_platform_interface 2.0.4 [flutter plugin_platform_interface]
- url_launcher_web 2.0.4 [flutter flutter_web_plugins meta url_launcher_platform_interface]
- url_launcher_windows 2.0.2 [flutter]
- vector_math 2.1.0
- wakelock 0.5.3+3 [flutter meta wakelock_macos wakelock_platform_interface wakelock_web wakelock_windows]
- wakelock_macos 0.1.0+2 [flutter flutter_web_plugins wakelock_platform_interface]
- wakelock_platform_interface 0.2.1+2 [flutter meta]
- wakelock_web 0.2.0+2 [flutter flutter_web_plugins js wakelock_platform_interface]
- wakelock_windows 0.1.0+1 [flutter wakelock_platform_interface win32]
- win32 2.2.9 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.1.2 [collection meta petitparser]
- yaml 3.1.0 [collection source_span string_scanner]

Hi @Tom3652
This looks like a duplicate of https://github.com/FirebaseExtended/flutterfire/issues/6972
If you think it isn't let me know but closing this for now.
Thank you

Hi @markusaksli-nc, thanks.
I am really not able to tell if this is linked or the same, but it seems that it is as i also mentioned in the issue so no problem to mark it as duplicate, unless i find the root cause in the meantime.


circular object references cause a stack overflow

If you try to diff two objects that contain a circular reference, you get a stack overflow.
var a = {}, b = {}, c = {};
a.b = b;
b.a = a;
c.a = a;
diff(b, c); // Error

Covered by #2


[Nox.Lib] Design Auditable

Define Nox Auditable Entities

Consolidate Field Names and align with workplace definition
Implementation Strategy
This includes Soft delete
Just related to the latest state of the Entity, close /part of the Entity attributes / table

Consider how we define the User in our model


Firmware not connected

Hi,
i am using a RPI4B with Ubuntu on it. I changed the interface in the docker-compose to AMA0 and when i start, this is what i get:
14:35:38:181 discovery server date: Sun, 08 Oct 2023 14:35:38 GMT
14:35:38:181 	 local time seems to be ok
14:35:40:519 DEV Tick.Init: booted after 8000 seconds
14:35:48:595 dev /dev/ttyAMA0
14:35:53:019 start reconnect to network
14:35:58:269 failed to reconnect to network try=1
14:36:02:604 dev /dev/ttyAMA0
14:36:03:518 failed to reconnect to network try=2
14:36:08:518 try to reconnect to network try=3
and it says Firmware Not connected in the UI

What device do you have?
Paste full compose file

Raspberry Pi 4B
version: "2"
services:
  deconz:
    image: deconzcommunity/deconz
    container_name: deconz
    restart: always
    ports:
      - 80:80
      - 443:443
    volumes:
      - /opt/deconz:/opt/deCONZ
    devices:
      - /dev/ttyAMA0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTA=0

How do i set this variable with using docker-compose? docker-compose up -d -e DECONZ_DEVICE=/dev/ttyAMA0 ?
How can i check if the host OS recognized the Raspbee?

version: "2"
services:
  deconz:
    image: deconzcommunity/deconz
    container_name: deconz
    restart: always
    ports:
      - 80:80
      - 443:443
    volumes:
      - /opt/deconz:/opt/deCONZ
    devices:
      - /dev/ttyAMA0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTA=0
      - DECONZ_DEVICE=/dev/ttyAMA0
      ````

Can you do a ls -all /dev/tty* to see if even the device exists?

Yes, its listed like this:
crw-rw---- 1 root  dialout 204,  64 Okt 11 20:57 /dev/ttyAMA0

When checking in dmesg do you find /dev/ttyAMA0? Is it recognized as a Raspbee?

All i find with dmesg | grep "AMA0" is
[0.887869] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2

Around the timestamp do you see any more info?

Nothing unusual i think
[    0.793941] zswap: loaded using pool zstd/z3fold [    0.798431] Key type .fscrypt registered [    0.798447] Key type fscrypt-provisioning registered [    0.813475] Key type encrypted registered [    0.813502] AppArmor: AppArmor sha1 policy hashing enabled [    0.813534] ima: No TPM chip found, activating TPM-bypass! [    0.813566] ima: Allocated hash algorithm: sha1 [    0.813591] ima: No architecture policies found [    0.813645] evm: Initialising EVM extended attributes: [    0.813651] evm: security.selinux [    0.813657] evm: security.SMACK64 [    0.813663] evm: security.SMACK64EXEC [    0.813669] evm: security.SMACK64TRANSMUTE [    0.813674] evm: security.SMACK64MMAP [    0.813679] evm: security.apparmor [    0.813685] evm: security.ima [    0.813690] evm: security.capability [    0.813696] evm: HMAC attrs: 0x1 [    0.818025] uart-pl011 fe201000.serial: there is not valid maps for state default [    0.819836] uart-pl011 fe201000.serial: cts_event_workaround enabled [    0.819932] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2 [    0.826376] of_cfs_init [    0.826472] of_cfs_init: OK [    0.862516] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA [    0.871089] Freeing unused kernel memory: 5568K [    0.898935] Checked W+X mappings: passed, no W+X pages found [    0.898967] Run /init as init process [    0.898974]   with arguments: [    0.898981]     /init [    0.898986]     fixrtc [    0.898991]     splash [    0.898995]   with environment: [    0.899000]     HOME=/ [    0.899005]     TERM=linux [    1.752733] usb_phy_generic phy: dummy supplies not allowed for exclusive requests [    1.764321] bcmgenet fd580000.ethernet end0: renamed from eth0 [    1.773977] xhci_hcd 0000:01:00.0: enabling device (0000 -> 0002) [    1.774052] xhci_hcd 0000:01:00.0: xHCI Host Controller [    1.774096] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [    1.774542] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000e40000000890 [    1.775008] xhci_hcd 0000:01:00.0: xHCI Host Controller

Seems fine indeed!
The issue is I can't reproduce it.

Can it be related to me running an external harddrive instead of using an SD card? I had really weird problems in the past (for example if the harddrive is too close to the raspberry pi, the bluetooth doesnt work anymore and so on)

It can absolutely be related to interference. Especially when running the OS on an SSD drive. You should try ruling that out by booting on an SD card or moving the SSD for away on an extension cable etc.

If the problem persists after 100% ruling out interference issues, reopen this issue.

Hey, i have the same Problem - it appears totally random als it worked all the time since yesterday. How did you solve? (im not using a ssd).


About hyperparameters

Hi, thanks for sharing your great works.
I'm trying to reproduce the result of ERM(3rd row in Table.1 from your paper), but I got a bit lower performance on OfficeHome dataset. I ran your source code with hyperparameters described in your paper(lr=1e-05, weight_decay=1e-02, last dropout=0.1), and I got 72.767% of target accuracy averaged on 3 different random seeds. I think I'm missing some other hyperparameters such as classifier LR multiplier or attention dropout probability in vision transformer which are not clarified in the paper.
Could you kindly share the searched hyperparameters on each dataset?

Thanks. I'll try again with the updated command.
By the way, I found that hparams['lr_classifier'] does not affect the learning rate in the optimizer for ERM in https://github.com/zhengzangw/DoPrompt/blob/main/domainbed/algorithms.py#L111. I think this should be fixed.

Thank you for pointing this out. I have modified the code to match our experiment version.


Add Authentication/Authorization support

Hardening the Code and add unit Tests.

Hi @kreuzhofer,
Apologies for the late code review! I (and I'm sure Tom as well) have been quite busy with work.
Thanks for all the work, like Tom said, a pretty solid implementation, even more so with the extra hardening/ error cases you added in the last few commits.
I've got a couple of comments / questions, let me know what you think:

How users would provide the IAuthorizationProvider

The IAuthorizationProvider could be passed in on the http server level. That way the instantiation for RestRouteHandler and StaticFileRouteHandler wouldn't have to change and I think in most cases the authorization provider would be the same for the entire server.. The authorization provider could then be provided on the IHttpServerRequest to the RestRouteHandler and the StaticFileRouteHandler.
The authorisation provider could then be added to the HttpServerConfiguration so the user can use that to specify it.

RestRouteHandler, authorize attribute

More a nice to have then a must have, but when RestControllerRequestHandler.RegisterController is called, we could parse it for Authorize attributes on the controller level and pass that into the GetRestMethods call.
In the GetRestMethods method we would then either cache the authorize attribute from the controller, or the (override) authorize attribute on the method in RestControllerMethodInfo.

StaticFileRouteHandler

I think for now what you did to authorize everything if an IAuthorizationProvider is passed in is great.
If we go with my suggestion of point 1 then we do lose a bit of flexibility there so I think we then need some way in the static file route handler to tell if it should execute the authorization procedure.
I would then suggest passing an interface into the StaticFileRouteHandler like:
AuthorizedFilePaths = new []{ AuthorizedFilePath("\directory"),
AuthorizedFilePath("\directory\file")};
The reason for the AuthorizedFilePath being a class is so in the future we can add roles / exceptions, etc.

minor renaming / refactorings, not 100% required for pull request merging imo

In RestRouteHandler _authenticationProvider should actually be named _authorizationProvider.
Could potentially do the parsing of the Authorisation header in a custom header (like ContentLengthHeader, etc.)
In DemoCredentialValidator.AuthenticateHelper you could do Task.FromResult((username == "user" && password == "pass");) and remove the async keyword instead of adding the pragma
Why does IAuthorizationProvider Task as a return type and ICredentialValidator use a IAsyncOperation as a return type?
PassThroughCredentialValidator seems to not be used anywhere, are you going to do anything with this?
When using AuthenticatedPerCallControllerSample TotalCallsHandled is never increased since the InstanceCreationType is PerCall.

@kreuzhofer do  you mind if I apply some of the review notes above so we can get this pull request merged back in? I think it's a nice piece of functionality to have.

Hi @Jark, sorry for the late answer. I had some other urgent stuff, which blocked me completely from continuing on this. I will review this again and make some fixes to make it work with the development branch this week. Lets then review again.
about your comments:

Yes, this makes sense. I will have a look into it and move the code to the upper level.
Maybe we could chat about this. Is this about performance?
this makes totally sense, but I would suggest taking it as it is for now and then make another step forward to improve it.
Renamings I will do. Async fix, will do. The rest is mostly for demo purposes. The PassThroughCredentialValidator can be used to validate the credentials agains the local admin user credentials for the management web-portal. I will test this a bit further if it works and if yes, will include a sample for it. Otherwise, I will remove it.


StringWriter.ready should not return false when at the end.

You mean StringReader?

Oops, yes, it is StringReader.


Remove wrong check in QueryCompiler::IsSupported

(as discussed in the team meeting today)
We do support ExpressionType::VALUE_PARAMETER in the codegen engine, even though IsSupported says otherwise. Only tested by running the test suite.

Coverage decreased (-0.6%) to 76.821% when pulling cf38be1f5b34440321f7d5222b1b8a77a93f9c46 on tcm-marcel:fix/issupported into<PHONE_NUMBER>0dced1cba836c1d173dde0a05be7e4 on cmu-db:master.

Looks like the prepared_stmt_test is failing due to the serialization issue identified in #1377. Let's wait for a fix to that before merging this. Or include this PR into a PR that fixes the larger issue.

Just FYI you can fix the failing test by explicitly issuing PREPARE and EXECUTE SQL queries. The bug is not necessarily due to a bug in the network layer, but rather lack of ability to do type inference, which is unlikely to be implemented soon.


Update Dockerfile CMD to python3

Newer Pi builds require python3 to launch properly.

@balena-ci I self-certify!


PrivacyInfo.xcprivacy is needed before May 1, 2024 for iOS

This SDK uses UserDefaults in ios/RnDeviceRisk.swift. Apple requires privacy declaration before 5/1/2024:
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api

Hey @CatChen ,
Thanks for contacting us. Socure latest Device Risk SDKs are shipped with a Privacy Manifest file(PrivacyInfo.xcprivacy) to comply with latest requirements. Please update your iOS Device SDK version to 4.1.2.
Kind regards,


Model definition not included when response definition has an external $ref containing a schema $ref

Problem statement
Not sure how to say that in a simple way, the example may be more relevant :)
Model definition is not included when a response definition has an external $ref containing a schema with $ref.
With swagger flatten the model definition is missing,
swagger validate throw this error :
some references could not be resolved in spec. First found: object has no key "Error"

Steps to reproduce
responses.yaml:
swagger: '2.0'
info:
  title: Responses
  version: 0.1.0
definitions:
  Error:
    type: object
    description: |
      Contains all the properties any error response from the API will contain.
      Some properties are optional so might be empty most of the time
    required:
      - code
      - message
    properties:
      code:
        description: the error code, this is not necessarily the http status code
        type: integer
        format: int32
      message:
        description: a human readable version of the error
        type: string
      helpUrl:
        description: an optional url for getting more help about this error
        type: string
        format: uri

responses:
  BadRequest:
    description: Bad request
    schema:
      $ref: '#/definitions/Error'

paths:
  /:
    get:
      summary: GET
      operationId: getAll
      responses:
        200:
          description: Ok

swagger.yaml
swagger: '2.0'
info:
  title: Object
  version: 0.1.0

paths:
  /:
    get:
      summary: GET
      operationId: getAll
      responses:
        200:
          description: Ok
        400:
          $ref: './responses.yaml#/responses/BadRequest'

Commands
swagger validate swagger.yaml
swagger flatten swagger.yaml

Environment
swagger version: dev

Just guessing that the $ref isn't being resolved in the right file.  Does it work if you reference ./responses.yaml#/definitions/Error?  (Not that I think you should do this in the end, just guessing about the cause.)

Yes it work by setting ./responses.yaml#/definitions/Error in the responses.yaml file.
Will use this workaround thanks :)

Could reproduce this and the work around as well, but could not find a fix right away.
Again a failure with $refs...
Opened a dedicated issue for that in go-openapi/spec#65

have you tried running flatten before generating?

@casualjim  It seems he has. I tested this directly with spec and this $ref is not resolved at all, unless you explicit the filename (in its own file!), as suggested @gregmarr

@casualjim yes, with swagger flatten the model definition is missing, but no error is thrown.
@fredbi thanks for the review, i tried to find a fix too but this is too complicated to me :s

@BertrandGouny  go-openapi/spec#70 should solve your issue.

@fredbi I pulled master and did the following:
go get -u github.com/go-swagger/go-swagger/cmd/swagger
go install github.com/go-swagger/go-swagger/cmd/swagger
./bin/swagger validate file.yaml

2018/04/11 13:53:51
The swagger spec at "/Users/fultonbyrne/Desktop/photic-docs/_data/networkmanager_swagger.yaml" showed up some valid but possiby unwanted constructs.
2018/04/11 13:53:51 See warnings below:
2018/04/11 13:53:51 - WARNING: parameter "#/parameters/includeChildren" is not used anywhere

The swagger spec at "/Users/fultonbyrne/Desktop/photic-docs/_data/networkmanager_swagger.yaml" is invalid against swagger specification 2.0.
See errors below:
- some references could not be resolved in spec. First found: object has no key "Release"

The spec is more important than the gopkg.toml, unless you want me to check every single commit number in your attachment?

Let me get to minimal viable. There's nothing really special that we're doing. It's just that the refs point to items within the same document.

What is the TL,DR of your gopkg? you got an updated spec and validate compared to the go-swagger vendor in go-swagger?

Yup, I've updated to use all the latest versions so I believe and yet it still can't resolve $refs that point within the file via #/definitions/Model.

I assume it has something to do with transitive $ref ($ref pointing to another file then another $ref in the same file). Correct in your case?

So, no his workaround does not work in this case. The $ref points to
"./networkmanager_swagger.yaml/#/definitions/Membership" which is in the same file to begin with.

So the root yaml file has references to itself that include the filename?  That's a bit odd.  The case where I suggested adding that before was for when the reference was in a different file referenced from the root, and I was only suggesting that as a test, not a permanent fix.  I would not expect a reference to a definition in the same file to be qualified with the filename.

Thank you Greg. I was just suggesting this to help pinpointing the actual issue.

After trying to achieve a minimal reproducible I've identified that there's something amiss with our definition. I'll keep working with it to see if I can isolate the issue. Thank you all for your help!
I've really loved this tool so far. It's gotten me farther than any other swagger tool I've used yet. The validator is incredibly helpful most of the time. Thank you all for your work!

Any update on this ? the fix seems to not solve the issue example

I could narrow the issue and prepare a more general testcase.
However, the fix is not obvious.
The problem lies in spec expandResponse() and expandParameter() when the SkipSchema=true option is used (which is what the flatten command uses).
With this option, remote $ref's on the response (or parameter) object are properly expanded, but the content of their schema is left unchanged. So any $ref which is in the remote schema is not relocated to the new root after expansion (or even expanded).
This does not happen when SkipSchema=false, because all $ref's are properly processed.
These functions should in my opinion be updated to expand remote $ref (and only those) in the schema, even though the skipSchema flag is set.


:sparkles: implement more of the Azure DevOps client

What kind of change does this PR introduce?
Includes:

GetBranch
GetSuccessfulWorkflowRuns
ListCheckRunsForRef
ListStatuses
ListWebhooks
SearchCommits

Also, includes comments about methods which can never be implemented:

GetOrgRepoClient

Org repository, AKA the <org>/.github repository, is a GitHub-specific feature

ListLicenses

Azure DevOps doesn't have a license detection feature. Thankfully, the License check falls back to file-based detection.

Still need to implement:

ListReleases

Needs a little more investigation to line up the Azure DevOps implementation with what Scorecard expects

(Is it a bug fix, feature, docs update, something else?)

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
Missing implementations for the methods listed above
What is the new behavior (if this is a feature change)?**

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
Next step of #4177
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

implement more of the Azure DevOps client

How do Branch-Protection and SAST look now?

SAST works perfectly

I'll note this is falling back to the github detection of the .github/workflows, and not through your added vstfs:///build/build string (which will be more likely for AZDO projects I assume?)

The issue with ListReleases on Azure DevOps is it doesn't have a concept of a release in the same way that GitHub and GitLab do

I'm curious if we should just continue on the ListReleases ErrUnsupportedCheck so we get branch protection data for the default branch at least

I'll note this is falling back to the github detection of the .github/workflows, and not through your added vstfs:///build/build string (which will be more likely for AZDO projects I assume?)

That's an issue with the check itself than with the Azure DevOps client. There are definitely a couple of checks like that.
The SAST check specifically would need to be updated to look for all YAML files in the repository, because Azure Pipelines files can be in any arbitrary location in the repository, and look for the AdvancedSecurity-Codeql-Analyze task. See Code scanning for GitHub Advanced Security for Azure DevOps for more information.

I'm curious if we should just continue on the ListReleases ErrUnsupportedCheck so we get branch protection data for the default branch at least

Yes, that would be one approach. But I don't want to expand the scope of this PR too much more.

The SAST check specifically would need to be updated to look for all YAML files in the repository, because Azure Pipelines files can be in any arbitrary location in the repository, and look for the AdvancedSecurity-Codeql-Analyze task

Whoops, I had meant CI-Tests, as that's what you added the vstfs:///build/build string for.


Update README.md

Fixed all issues.

accidently i closed the last  PR :(
as well I think that i had mistake by commitig to master before i create my new branch and I dont realy understand how to fix . I am opening a new PR(on master) but Liora i would like your help to fix my issue for the next time.

Could you please add me to this PR aswell 😅


[typescript]  SliderProps are not compatible with JSX.IntrinsicAttributes

When I used RangeSlider in my project, I have encountered with such an error:
Property 'min' does not exist on type 'IntrinsicAttributes'

To resolve it, I found out that in src/RangeSlider.tsx when you export the module, you don't specify type for gestureHandlerRootHOC function, rather using generic version. So solution is:
export default gestureHandlerRootHOC<SliderProps & JSX.IntrinsicAttributes>(RangeSlider);

Same here


Add helm arguments use case in documentation

Is your feature request related to a problem? Please describe.
I am using the suggested argocd-vault-plugin-helm config :
  configManagementPlugins: |
    - name: argocd-vault-plugin
      generate:
        command: ["argocd-vault-plugin"]
        args: ["generate", "./"]
    - name: argocd-vault-plugin-helm
      generate:
        command: ["sh", "-c"]
        args: ["helm ${helm_args} template . > all.yaml && argocd-vault-plugin generate all.yaml"]
    - name: argocd-vault-plugin-kustomize
      generate:
        command: ["sh", "-c"]
        args: ["kustomize build . > all.yaml && argocd-vault-plugin generate all.yaml"]

In argocd application manifest you can define additional configs for helm :
    helm:
      # Extra parameters to set (same as setting through values.yaml, but these take precedence)
      parameters:
      - name: "nginx-ingress.controller.service.annotations.external-dns\\.alpha\\.kubernetes\\.io/hostname"
        value: mydomain.example.com
      - name: "ingress.annotations.kubernetes\\.io/tls-acme"
        value: "true"
        forceString: true # ensures that value is treated as a string

      # Release name override (defaults to application name)
      releaseName: guestbook

      # Helm values files for overriding values in the helm chart
      # The path is relative to the spec.source.path directory defined above
      valueFiles:
      - values-prod.yaml
      ....

Using argocd-vault-plugin, this helm config is not possible.
As a workaround I used this config:
  configManagementPlugins: |
    - name: argocd-vault-plugin
      generate:
        command: ["argocd-vault-plugin"]
        args: ["generate", "./"]
    - name: argocd-vault-plugin-helm
      generate:
        command: ["sh", "-c"]
        args: ["helm ${helm_args} template . > all.yaml && argocd-vault-plugin generate all.yaml"]
    - name: argocd-vault-plugin-kustomize
      generate:
        command: ["sh", "-c"]
        args: ["kustomize build . > all.yaml && argocd-vault-plugin generate all.yaml"]

argocd application manifest:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: rollouts-demo-dev
  namespace: argo-cd
  labels:
    environment: dev
  finalizers:
  - resources-finalizer.argocd.argoproj.io
spec:
  destination:
    server: https://mycluster.info
    namespace: dev
  project: argo-rollouts-demo
  source:
    path: config/helm/rollouts-demo
    plugin:
      name: argocd-vault-plugin-helm
      env:
        - name: helm_args
          value: -f values-dev.yaml -f values-dev-tag.yaml
    repoURL: https://github.com/mytheresa/argo-rollouts-demo.git
    targetRevision: HEAD

Maybe this could be added to the documentation, or maybe there is a better way to handle this.

@marcportabellaclotet-mt Hi, to my knowledge that is the only workaround I'm aware of. For AVP to do it's job, it needs the rendered YAML manifests, which requires helm template beforehand. Unf, a ArgoCD plugin invocation of Helm will not honor the helm config options of the Argo app implicitly. In our usage of AVP we use a similar trick to you, using environment variables in the Argo app that can be consumed in the plugin command.
Feel free to open a PR to put this in the docs!

I still think this is worth adding to the docs as a heads up to helm users! I had to search around in the issues to figure it out myself.

Great, Is it fine if I raise a PR this week about adding this documentation? Or repo maintainters prefer to do it by themself?

Go ahead @marcportabellaclotet-mt!


Add optional param for cloud config

Since cloud config affects all deployments it feels weird to me to group it up with one of them. For that reason we've kept it out of this resource's scope.
You may be interested in the bosh-config resource though: https://github.com/EMC-Dojo/bosh-config-resource
Thanks for the PR anyway!


changes

OPS Build status updates of commit 4b65287:
:clock10: Preparing: average preparing time is 43 sec(s)

OPS Build status updates of commit 4b65287:
:clock10: Incremental building: average incremental building time is 18 sec(s)

OPS Build status updates of commit 4b65287:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/release-notes/Insider/17763.md
:white_check_mark:Succeeded

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


add mtef3 support

Created submodules Mathtype3 and Mathype5.
Calls from outside can still use Mathtype::Converter as before.
Mathtype::Converter will throw NotImplementedError if mtef version is not 3 or 5.

Thank you for this PR, looks good! One question, how different are the records between MTEF 3 and MTEF 5? Could some of those records be deduplicated or are there differences everywhere?

The way options are handled is different beetween MTEF 3 and 5.
Would need to write an individual BinData type for options which parses them the right way, then most records could be unified I think.

Thank you for your contributions @sbulka, this looks like you're adding amazing value to the project! I still have that concern of code duplication between MTEF 3 and MTEF 5. If you can somehow address that, I would merge this straight away (and then further contributions can be more granular).

Just found some time to work on the "easy-to-merge" classes.
Unfortunately still needs some more work on classes where the options have to be handled differently.
Btw. its possible I encounter some .eps and .gif files in the upcoming weeks, so will likely add support for those too.

Absolutely fantastic, @sbulka! I'd be OK with abstracting only virtually identical classes. If there are situations where it's tricky to abstract the different handling of options, I say we keep those separated and not worry about it.
If you can resolve the new merge conflicts (sorry, it's an inline/block fix that arrived in master in the mean time), I'll merge this straight way.

Passes tests now.
I want to keep features more branch-separated, so future PR can be accepted easier.
Thank you for your effort too! :)
On the remaining separate classes:
Hardest part to refactor is the Payload class, because it requires some 'default' choices.
Didn't get the way to extend these choices in subclasse, yet.
The remaining classes depend on that in some way, but should then be an easy thing to do.

Awesome, thank you for your contribution! 👍

@sbulka Mathtype 0.1.0 has been released: https://rubygems.org/gems/mathtype 🎉


P2 load sample timeout

change the sample service to create a sample summary straight away, kick off the upload in the background and return immediately
change the collection exercise service to create a sample link immediately but only activate it when it receives a message on the sample-outbound-exchange with routing key Sample.SampleUploadFinished.binding
change response-operations-ui to display the state of the upload and any successful completion or error

 P2 Load sample timesout and doesn't generate samplelink record in collectionexercise

Codecov Report

Merging #156 into master will increase coverage by 0.23%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #156      +/-   ##
==========================================
+ Coverage   95.53%   95.77%   +0.23%
==========================================
  Files          35       35
  Lines        1680     1680
==========================================
+ Hits         1605     1609       +4
+ Misses         75       71       -4

Impacted Files
Coverage Δ

...esponse_operations_ui/views/collection_exercise.py
97.26% <100%> (ø)
:arrow_up:

..._ui/controllers/collection_exercise_controllers.py
91% <0%> (+4%)
:arrow_up:

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 2dd5c5a...0f2f265. Read the comment docs.


"Beuca" and "Plopi" are listed in the drop-down menu

Description:
"Beuca" and "Plopi" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Beuca" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Beuca, TELEORMAN (Beuca)" and "Comuna Beuca, TELEORMAN".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Plopi" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Plopi, TELEORMAN (Beuca)".


Whitelabel error page

https://authz-playground.example.org/aaa shows:
Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

A simple error template similar to OpenConext-authorization-server would be fine.

Fixed in 678e42fc9803373f4939c217519b5c44b3088911


mkcloud porting for dirmaint (s390x)

For more information about DirMaint, see http://www.vm.ibm.com/related/dirmaint/overview.html

Please can you make it clear what dirmaint actually is, for those of us who are clueless about s390x?

@aspiers sure, added to the PR comment and will add it to the first git commit message.

@dirkmueller Thanks! I think it would also be worth adding a comment to the top of mkcloud-dirmaint.sh, since the question would presumably most often arise when looking at that file (or a reference to it) for the first time.

@aspiers done

@aspiers rebased after your change to the DNAT stuff merged. please review whether I did that correctly


feat: let user specify systemd restart time

As a user, I want to manage with precision the way consul systemd unit works.
This PR lets the user specify the duration applied to the Consul systemd unit in case of failure before trying to restart it.
A default value is set in order to keep the previous behaviour of the role.

Thank you!


SyntaxError: nuxt/router.js: Support for the experimental syntax 'dynamicImport' isn't currently enabled

Version
v2.8.1
Reproduction link
https://github.com/virskor/clodraForumFE
Steps to reproduce
yarn install
yarn dev
What is expected ?
after update to 2.8.1, my NuxtJS application occurs problem.  it's running well before that.
my NodeJS version is v11.
and i am using yarn.
.barbelrc
{
"env": {
"test": {
"presets": [
[
"@babel/preset-env",
{
"targets": {
"node": "current"
}
}
]
]
}
}
}
after adding @babel/plugin-syntax-dynamic-import, problems still exsting.
What is actually happening?
ERROR in ./.nuxt/router.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
SyntaxError: /Users/virs/clodraForumFE/.nuxt/router.js: Support for the experimental syntax 'dynamicImport' isn't currently enabled (5:40):
3 | import { interopDefault } from './utils'
4 |

5 | const _40f7591f = () => interopDefault(import('../pages/callback.vue' /* webpackChunkName: "pages/callback" /))
|                                        ^
6 | const _1216da14 = () => interopDefault(import('../pages/categories.vue' / webpackChunkName: "pages/categories" /))
7 | const _26c888f9 = () => interopDefault(import('../pages/categories/index.vue' / webpackChunkName: "pages/categories/index" */))
8 | const _06a675a1 = () => interopDefault(import('../pages/categories/_id.vue'

This bug report is available on Nuxt community (#c9571)

Duplicate of https://github.com/nuxt/nuxt.js/issues/4839


Example cannot be imported in Windows for python >= 3.8

Some while ago, I marked the test as allowed to fail, but it would be wise to open an issue to track the problem.
The SWIG example compiles fine in all Window versions, generating the following files:
adding 'mymath/_bindings.pyd'
adding 'mymath/bindings.py'
adding 'mymath/libbindings.dll.a'
adding 'mymath/include/mymath.h'
adding 'mymath/lib/libmymath.a'
adding 'mymath-0.0.0.dist-info/METADATA'
adding 'mymath-0.0.0.dist-info/WHEEL'
adding 'mymath-0.0.0.dist-info/top_level.txt'
adding 'mymath-0.0.0.dist-info/RECORD'

However, when it is imported in the tests, it fails with the following error (more details in any CI job):
=================================== ERRORS ====================================
____________________ ERROR collecting tests/test_mymath.py ____________________
ImportError while importing test module 'D:\a\cmake-build-extension\cmake-build-extension\examples\swig\tests\test_mymath.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
c:\hostedtoolcache\windows\python\3.9.5\x64\lib\importlib\__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests\test_mymath.py:3: in <module>
    import mymath.bindings
c:\hostedtoolcache\windows\python\3.9.5\x64\lib\site-packages\mymath\bindings.py:18: in <module>
    from . import _bindings
E   ImportError: DLL load failed while importing _bindings: The specified module could not be found.
=========================== short test summary info ===========================
ERROR tests/test_mymath.py
!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
============================== 1 error in 0.37s ===============================

I have no idea what could cause this error. I marked as allowed to fail also the new Python 3.9 job.

I also caught the following in the Python 3.7 job:
C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-t1xho44w\overlay\Lib\site-packages\wheel\bdist_wheel.py:82: RuntimeWarning: Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
    warn=(impl == 'cp')):
  C:\Users\RUNNER~1\AppData\Local\Temp\pip-build-env-t1xho44w\overlay\Lib\site-packages\wheel\bdist_wheel.py:87: RuntimeWarning: Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
    sys.version_info < (3, 8))) \

The second warning disappears if Python >= 3.8.

There's a similar report in https://github.com/opencv/opencv/issues/19972#issuecomment-832171608, but I couldn't find any helpful information.


[MINOR][SQL] Remove unused pattern matching variables in Optimizers.

What changes were proposed in this pull request?
This PR removes unused pattern matching variable in Optimizers in order to improve readability.
How was this patch tested?
Pass the existing Jenkins tests.

Test build #58679 has started for PR 13145 at commit 007b7c9.

Looks reasonable, but I wonder if this should be done at once for all of the code base?

Test build #58679 has finished for PR 13145 at commit 007b7c9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58679/
Test PASSed.

Thank you for review, @srowen .
Probably, there exists similar cases in other modules, too.
But, for the other module, I guess the patterns are simple and the most complex pattern matchings are used in optimizers due to the nature of optimization. Also, until now, it seems there exists no suitable automatic tool  for doing for all of the code base. When I searched for this, I found that Scala open issue for this; https://issues.scala-lang.org/browse/SI-8040 .

Merged to master

Thank you, @srowen.

Also merged to 2.0 -- seems safe enough and might avoid merge conflicts


Unable to generate an instance_spy for Gitlab::Client

Here's an interesting problem. For my project unit tests I'm doubling the Gitlab::Client. Here is a stripped-down example:
require 'gitlab'

describe 'Creating an instance_spy on the client' do
  let(:gitlab_client) { instance_spy ::Gitlab::Client, get_file: 'foo' }

  before :each do
    allow(::Gitlab).to receive(:client).and_return(gitlab_client)
  end

  it 'ought to work' do
    client = Gitlab.client(endpoint: 'foo')
  end
end

This fails in an interesting manner:
Creating an instance_spy on the client
  ought to work (FAILED - 1)

Failures:

  1) Creating an instance_spy on the client ought to work
     Failure/Error: raise Error::MissingCredentials.new("Please set an endpoint to API") unless @endpoint

     Gitlab::Error::MissingCredentials:
       Please set an endpoint to API
     # ./lib/gitlab/request.rb:90:in `set_request_defaults'
     # ./lib/gitlab/api.rb:16:in `initialize'
     # ./lib/gitlab.rb:18:in `new'
     # ./lib/gitlab.rb:18:in `client'
     # ./lib/gitlab.rb:23:in `method_missing'
     # ./spy_spec.rb:4:in `block (2 levels) in <top (required)>'
     # ./spy_spec.rb:7:in `block (2 levels) in <top (required)>'

Finished in 0.00164 seconds (files took 0.17132 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spy_spec.rb:10 # Creating an instance_spy on the client ought to work

Looking into the source (I've tried this against both release 3.6.1 and master), I think I know what the problem is: in order for rspec to validate the stubbed method, it must first see if the class responds to the method. At that point, it hits either Gitlab.respond_to? or Gitlab.respond_to_missing?, depending on the gem version. This create a client object with no options, which fails because endpoint is not specified.
I want to stub the client, but in doing so it creates the client. Catch22!
Anyway, if I stub the method that does the validation, I get past this problem, but it seems like a bit of a hack to have to work around it like that (and not intuitive to the next person who comes along):
require 'gitlab'

describe 'Creating an instance_spy on the client' do
  let(:gitlab_client) { instance_spy ::Gitlab::Client, get_file: 'foo' }

  before :each do
    allow_any_instance_of(::Gitlab::Client).to receive(:set_request_defaults).and_return(nil)
    allow(::Gitlab).to receive(:client).and_return(gitlab_client)
  end

  it 'runs very nicely, thank you' do
    client = Gitlab.client(endpoint: 'foo')
    expect(client.get_file('a','b','c')).to eq 'foo'
  end
end

Any ideas? Should I be doing this a different way?

Sorry man, I looked a this a while back but could not figure out a different way.


don't check conflict for migration pod with only static mac

What type of this PR

Bug fixes

It returned conflict error if kubevirt VM pod with only static mac(no static IP configured) during migration because that mac address is conflicted with the existing pod.
Add parameter to func GetRandomAddress() to skip check conflict for migration pod
Which issue(s) this PR fixes:
relates to #1253 #1001

Thanks! @chestack


Fixed Image Link

Fixes #12

Hi, I just fixed an issue, can I be added so I can complete the pull request. Thank you

Hi! Thanks for your contribution!
Although, there're a few points that we should address here:

It'll be awesome if you follow the conventional commits standards;
To really solve the problem it should use the absolute path to the raw asset for both images on README.md. e.g: https://raw.githubusercontent.com/ifood/ifood-docusaurus-theme/main/docs/ifood_docusaurus.svg
In order to accept your PR you must sign the CLA

Sorry for the inconvenience, we still working on a better contributors experience.


Search field has no input limit

I can type an unlimited amount of characters in the search field. When this was allowed in the Allihoopa app, I managed to put down the whole site. I don't know if this is fixed on the backend, but to be safe we should definitely fix this in the GUI.

This was fixed in #20.


feat: display organization lookup error if organization is not found.

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description
This PR adds the feature to display an error message if the entered organization is not found or is invalid while completing the second step of onboarding.
Related Tickets & Documents
Fixes #700

Mobile & Desktop Screenshots/Recordings
https://user-images.githubusercontent.com/48399373/209354402-a484e0e9-20eb-434c-a23b-7af20f8c95d2.mov

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@shamimbinnur what's left to get this ready to merge?

Getting this error if I change from "any" to any other type

https://user-images.githubusercontent.com/48399373/211603717-f7a59e7e-439a-405d-872d-32ffe18ff7d2.mov

The GitHub API does throw an error though if the org is invalid. We may need need to type the error as unknown in the try and cast it as Error & { status: number } to be able to access the status code.

The GitHub API does throw an error though if the org is invalid. We may need need to type the error as unknown in the try and cast it as Error & { status: number } to be able to access the status code.

I disagree with this, octokit.request is not typed return nor error because it's not supposed to throw; if that was the case, try cathing those blocks is fine, the way it is set up now it's encapsulating more logic than needed.
Whereas the response variable should be checked for data and error, the code itself is mapping the data over an array assuming it will work. This will not, and instead of throwing an API error it will throw a message saying that null is not an object, that is generic message, an empty object {} which can't be typed.
We simply cannot use try/catch as a magic rubber band for writing incomplete code and in general, throwing errors should be avoided in client environments.

Maybe now we should think about a different logic for this.

ocktokit.request does return a rejected promise with an error, so using the try/catch with the await is what we need https://www.npmjs.com/package/@octokit/request#request
From the docs
If an error occurs, the promise is rejected with an error object containing 3 keys to help with debugging:

error.status The http response status code
error.request The request options such as method, url and data
error.response The http response object with url, headers, and data

ocktokit.request does return a rejected promise with an error, so using the try/catch with the await is what we need https://www.npmjs.com/package/@octokit/request#request
From the docs
If an error occurs, the promise is rejected with an error object containing 3 keys to help with debugging:

error.status The http response status code
error.request The request options such as method, url and data
error.response The http response object with url, headers, and data

@brandonroberts going to try this.

The design of the error message is not blocking. I have opened an issue to explore error message design in the entire app. I'll leave a comment inline on the copy.
https://github.com/open-sauced/insights/issues/781


Multilingual support

It would be really nice if Voyager had multilingual support.
This however would require a lot of modifications in the current system:

[ ] Language Switcher on front-end
[x] Language Switcher on admin panel
[ ] Enable/Disable Language Switcher from the front-end/admin panel
[ ] The current views should use language translations
[ ] We should be able to select which languages can be used
[x] Menu builder should support multilingual, in that way that it should be possible to add other strings/urls for different menu items
[x] The current page system should support multilingual, in that way that the fields can be translated
[ ] Configuration for defining language routes, some people might want the routes to be the same like (example.com/about-me should be the same url for all languages, however it translate the language according to a language set for that user somehow) or prefixed with the language code like (example.com/en/about-me and example.com/XX/about-me).
[x] Categories should support multilingual for fields
[x] Posts should support multilingual for fields

I think we should wait for Laravel 5.4 because it will have better localization features:
http://themsaid.com/laravel-54-localization-json-20161117/

Look awesome! Let's wait for Laravel 5.4.
Then we can focus on something else until that.

I will be implementing some of this topics on a project I'm working at the moment, I can share with you later.
I'll be using JSON data type for the translated fields. Do you like this approach?

@akaZorg, you mean for the Eloquent?

Yes, something like the guys from Spatie created: https://github.com/spatie/laravel-translatable.
Do you consider on using dependencies like this one?

I think that the codebase may lay on that dependency. However only for developers using the translation system. So I think it should make a translate: boolean to the Voyager config, which leaves every bit of track that a translation system exists from the UI, and nether require that dependency. So users that wish to use translations can enable translations and add the dependency easy using composer require spatie/laravel-translatable.

However that might not be 100% possible just like that, since the package uses a trait that have to be implemented.
Any ideas?

I have no ideas about that trait, need to dive into it... I've been busy with other stuff, will catch you later.

Laravel 5.4 is officially released.

It is a good idea to support multilingual and im ready to contribute on that. I can translate to Arabic langauage when you are ready.

Im currently working on making the BREAD translatable #561

+1

+1

+1

I can contribute to the Persian (fa-ir) translation and also help in making the UI RTL supportive. Let me know when I could contribute on this.

@hosseinhkj: Please join #789

I can contribute to the Persian (zh_CN) translation

'Admin Login' => '后台登陆',
'Login' => '登陆',
'Sign In' => '登陆',
'Sign in below' => '登陆以下',
'Logging in...' => '登陆中...',
'The given credentials dont match with an user registered' => '给定的凭据与注册的用户不匹配',
'dashboard' => '控制台',
'media' => '媒体',
'password' => '密码',
'Logout' => '退出',
'email address' => 'Email地址',
'View All' => '显示全部',
'You have' => '您有',
'in your database. Click on button below to view all' => '在您的数据库. 点击下面按钮查看全部信息',
'To view analytics you\'ll need to get a google analytics client id and add it to your settings for the key google_analytics_client_id. Get your key in your Google developer console:'
    => '要查看分析数据，您需要获取Google Analytics（分析）客户端ID，并将其添加到密钥 google_analytics_client_id 在设置中。 在Google开发人员控制台中取得您的密钥：',
'Make sure to setup the appropriate relationship in the' => '确保在中设置适当的关系',
'method of the' => '方法',
'class' => '类',

'Relationship' => '关系',
'Custom' => '定制',

'Add New' => '新建',
'New' => '新建',
'Cancel' => '取消',
'View' => '查看',
'Edit' => '编辑',
'Delete' => '删除',
'Rename' => '改名',
'Viewing' => '显示',
'published' => '发表',
'draft' => '草稿',
'pending' => '待定',

if someone need ，call me

Is there any new about languages ?

When you want Dutch support, feel free to message me!

I can contribute to the Spanish LA (es_la) translation

I can contribute to the Brazilian Portuguese translation (pt-br)

I can help on persian (fa) language
but I don't know exactly how to contribute

Hello @marktopper
Am using your package to generate admin panel for mobile API
and I will translate the admin panel to Arabic, Please share more information about contribution guidelines.
I will start merging i18n and feature/rtl-support and test or improve them.

Hi @marktopper
I can also translate it to Russian
@mbdwey how do you use Voyager admin for RTL? You also need menu in right, no?

@warlight, wonderful, we already have the translation files for you to start on.
And we have the RTL branch with RTL support, however, there are still a few issues on it that we will have to resolve before it makes it into a release.

@mbdwey Yes please test the RTL branch, I do not use RTL myself, so its hard for me to tell if everything is fine.
Also here you can see the English translation file: https://github.com/the-control-group/voyager/blob/master/publishable/lang/en/voyager.php

@marktopper I also can start translating to Hebrew. But I don't know it well) And I don't understand if everything is ok with RTL.
'Admin Login' => 'Войти под администратором',
'Login' => 'Войти',
'Sign In' => 'Зарегистрироваться',
'Sign in below' => '',//where can I find it?
'Logging in...' => 'Авторизация...',
'The given credentials dont match with an user registered' => 'Не верный логин или пароль',
'dashboard' => 'Панель управления',
'media' => 'Медиа',
'password' => 'Пароль',
'Logout' => 'Выйти',
'email address' => 'Email адрес',
'View All' => 'Все',
'You have' => 'У Вас',
'To view analytics you'll need to get a google analytics client id and add it to your settings for the key google_analytics_client_id. Get your key in your Google developer console:'
=> 'Чтобы подключить Google Analytics, Вам следует получить id клиента и добавить его в настройки для  google_analytics_client_id . Получите ключ в панели разработчика Google',
'in your database. Click on button below to view all' => 'в вашей базе данных. Нажмите на кнопку внизу, чтобы увидеть все',
'Make sure to setup the appropriate relationship in the' => '',//where can I find it?
'method of the' => 'Метод',
'class' => 'Класс',
'Relationship' => 'Связь',
'Custom' => 'Особенный',//where can I find it?
'Add New' => 'Добавить',
'New' => 'Новый',
'Cancel' => 'Отмена',
'View' => 'Показать',
'Edit' => 'Редактировать',
'Delete' => 'Удалить',
'Rename' => 'Переименовать',
'Viewing' => '',//where can I find it?
'published' => 'Опубликовано',
'draft' => 'Черновик',
'pending' => '',//where can I find it?

@marktopper, can I make pull request for translation?

@warlight I see 😄

Is possible to use the translations also for the files? For example save a audio guide for different languages. Thank you.

@asolagmbh great point!
Voyager doesn't support "file translation" and we should work on that. Please open an issue requesting this feature. Thanks.
This is easy to implemented.

Hello!
I can contribute with Spanish translation (es_ES).
Great package!!!! Thank you!

can anyone tell me how to translate relationships in voyager??


pwa polymer templates in visual studio 2017

A suggestion I wanted to provide to polymer team. I am not sure who exactly will be responsible to create a polymer template for visual studio 2017. So I have requested visual studio team as well for this and now I am requesting the feature here to the polymer team.
Polymer and web components play main role in creating awesome progressive web apps.
Visual Studio 2017 should integrate with Polymer to give it the templates already present in polymer-cli.
Also ASP.NET CORE 2.0 already has templates with angular and react, polymer should also have templates with asp.net core 2 with pwa stuff included like service worker e.t.c.
Reason to use VS 2017 templates

easy deployment to azure and other services
easy integration with multiple types of identity providers including Azure AD B2C which supports email sign up, and all social sign ups along with password reset easily.
awesome intellisense and brilliant development experience.

Reason to use polymer

Future of web development is web components and polymer is probably best tool to make them.
polymer also provides brilliant support for pwas.
Those who dont want to use heavy frameworks like angular, vue and react e.t.c, should use polymer because it is simpler and is able to give us a perfect pwa which can run on probably every device possible.

So if we combine polymer with VS 2017 it will be a perfect environment for future of web development.
P.S : here is the link of my request on visual studio user voice, please go to this link and vote the idea if you like it.
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/31776661-pwa-template-for-polymer-2-and-3-with-asp-net-core
Thanks.

This is more of a tooling suggestion, kicking to @justinfagnani

I have made a project template for private use. It's just a simple ASP.NET Core 2.0 project with Polymer.
PolymerTemplate.zip


Token in withAuthUserTokenSSR seems to be missing details compared to the client rendered version

Describe the bug
I'd like to be able to use the token in SSR to make calls to our API which also uses gip tokens for auth.
The token I get from await AuthUser.getIdToken() within getServerSideProps withAuthUserTokenSSR is invalid when trying to make requests.
The tokens I get client side are all fine and requests made with them have all succeeded.
I inspected the contents of the JWTs and the one generated client side contains more information than its server-side counterpart:
Contents of Client side JWT:
{
  "iss": "https://securetoken.google.com/xxxx-yyyyy-12345",
  "aud": "xxxx-yyyyy-12345",
  "auth_time":<PHONE_NUMBER>,
  "user_id": "abcstkLCsEy111MpciZ1RoY12345",
  "sub": "abcstkLCsEy111MpciZ1RoY12345",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "email"<EMAIL_ADDRESS>  "email_verified": true,
  "firebase": {
    "identities": {
      "email": [
<EMAIL_ADDRESS>      ]
    },
    "sign_in_provider": "password"
  }
}

Contents of SSR JTW:
{
  "iss": "https://securetoken.google.com/xxxx-yyyyy-12345",
  "aud": "xxxx-yyyyy-12345",
  "auth_time":<PHONE_NUMBER>,
  "user_id": "abcstkLCsEy111MpciZ1RoY12345",
  "sub": "abcstkLCsEy111MpciZ1RoY12345",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "firebase": {
    "identities": {},
    "sign_in_provider": "custom"
  }
}

I have cookies set to sameSite: "lax" and secure: "false" while I'm running locally and I can see the cookies with the correct name from the config available in the response object in getServerSideProps.
Versions
next-firebase-auth version:  v1.0.0-canary.8
Firebase JS SDK:  9.6.2
Next.js: 12.0.7
To Reproduce
Steps to reproduce the behavior:

Sign in and redirect to page that uses getServerSideProps and withAuthUserTokenSSR
Make a request with in withAuthUserTokenSSR e.g.

export const getServerSideProps = withAuthUserTokenSSR({
    whenUnauthed: AuthAction.REDIRECT_TO_LOGIN,
    whenAuthed: AuthAction.RENDER,
    appPageURL: "/"
})(async ({AuthUser}) => {
    const token = await AuthUser.getIdToken()
    console.log({AuthUser})

    try {
        const response = await fetch('https://api-endpoint', {
            method: 'GET',
            headers: {
                Authorization: `GipIdToken ${token}`,
            },
        })
....
    return {
        props: {token}
    }
})

Expected behavior
I would expect the JWT on server-side to contain the same information as that on the client.
Additional context
No additional context.
Thanks! It's super convenient library even with just the client side stuff working for me at the moment.

This is expected: we need to use a custom token to be able to refresh it server-side when it expires (see code here). However, we could pass additional custom claims to add, for example, email and email_verified.
@aidanbarrett When you say the token is "invalid", what's not working for you? Is your endpoint expecting an email property in the token?

Thanks for that @kmjennison. I've tracked down the problem.
The issue is that my endpoint is expecting the tenantId to be included in the token and I see that there is a PR (#429) open for tenanted workflows already.
Passing through custom claims could be a super handy feature though!


properly handle active card checks

Where metadata.hide_amount == true:

[x] Don't display amount
[x] Hide transaction status in detail view

metadata.notes may be a good determiner, as well.

Let user hide items delayed to 0.6.0


validate_webhook Isn't Working

I believe validate_webhook may be broken:
        webhook = pusher.validate_webhook(
            request.headers.get("X-Pusher-Key"),
            request.headers.get("X-Pusher-Signature"),
            request.data,
        )

This always returns None even if I copy and paste the key, signature, and data directly.
It is failing specifically on line 118 in authentication_client.py:
        if not verify(self.secret, body, signature):
            return None

The signature appears to always be different than the one returned by hmac.compare in signature.py.

I'm using django-rest-framework and I had to use the raw request.body to fix this. json.dumps(request.data) does not work.


Add preset system

Hello @yupferris
With a musician we are really thinking to use this master piece synth for our next 64k intro.
He want to have the ability to save preset of each synth (he is using renoise), so I created this issue with a plan to complete it later. I posted the issue here as a reminder because I don't find a issue panel on my fork, if it bother tell me I will remove it.
lamogui

Hi!
Issues can be enabled on github forks in the settings panel.


When DO machine reports failure when getting provisioned , they do not get cleanup.

**Rancher versions: v2.1.0-rc3
Steps to Reproduce:
Created DO clusters with 1 node.
When DO nodes were getting provisioned , we hit the following error:
2018/09/20 16:51:21 [ERROR] NodeController c-ksb8w/m-mrgsf [node-controller] failed with : Error creating machine: Error in driver during machine creation: invalid character '<' looking for beginning of value

and we retry again and succeed.
rancher-server logs:
2018/09/20 16:49:33 [INFO] stdout: Creating CA: management-state/node/nodes/sanadtest2/certs/ca.pem
2018/09/20 16:49:34 [INFO] stdout: Creating client certificate: management-state/node/nodes/sanadtest2/certs/cert.pem
2018/09/20 16:49:34 [INFO] stdout: Running pre-create checks...
2018/09/20 16:49:35 [INFO] stdout: Creating machine...
2018/09/20 16:49:35 [INFO] stdout: (sanadtest2) Creating SSH key...
2018/09/20 16:49:39 [INFO] stdout: (sanadtest2) Creating Digital Ocean droplet...
2018/09/20 16:49:41 [INFO] stdout: (sanadtest2) Waiting for IP address to be assigned to the Droplet...
2018/09/20 16:51:21 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/09/20 16:51:21 [INFO] stdout:
2018/09/20 16:51:21 [INFO] Generating and uploading node config sanadtest1
2018/09/20 16:51:21 [ERROR] NodeController c-ksb8w/m-mrgsf [node-controller] failed with : Error creating machine: Error in driver during machine creation: invalid character '<' looking for beginning of value
2018/09/20 16:51:24 [INFO] stdout: The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2018/09/20 16:51:24 [INFO] stdout:
2018/09/20 16:51:24 [INFO] Generating and uploading node config sanadtest2
2018/09/20 16:51:24 [ERROR] NodeController c-nfp59/m-xx52r [node-controller] failed with : Error creating machine: Error in driver during machine creation: invalid character '<' looking for beginning of value
2018/09/20 16:51:24 [INFO] Generating and uploading node config
2018/09/20 16:53:21 [INFO] stdout: Creating CA: management-state/node/nodes/sanadtest1/certs/ca.pem
2018/09/20 16:53:21 [INFO] stdout: Creating client certificate: management-state/node/nodes/sanadtest1/certs/cert.pem
2018/09/20 16:53:22 [INFO] stdout: Running pre-create checks...
2018/09/20 16:53:24 [INFO] stdout: Creating machine...
2018/09/20 16:53:24 [INFO] stdout: (sanadtest1) Creating SSH key...
2018/09/20 16:53:28 [INFO] stdout: (sanadtest1) Creating Digital Ocean droplet...
2018/09/20 16:53:29 [INFO] stdout: (sanadtest1) Waiting for IP address to be assigned to the Droplet...
2018/09/20 16:53:32 [INFO] stdout: Waiting for machine to be running, this may take a few minutes...
2018/09/20 16:53:39 [INFO] stdout: Creating CA: management-state/node/nodes/sanadtest2/certs/ca.pem
2018/09/20 16:53:39 [INFO] stdout: Creating client certificate: management-state/node/nodes/sanadtest2/certs/cert.pem
2018/09/20 16:53:40 [INFO] stdout: Running pre-create checks...
2018/09/20 16:53:41 [INFO] stdout: Creating machine...
2018/09/20 16:53:41 [INFO] stdout: (sanadtest2) Creating SSH key...
2018/09/20 16:53:46 [INFO] stdout: (sanadtest2) Creating Digital Ocean droplet...
2018/09/20 16:53:47 [INFO] stdout: (sanadtest2) Waiting for IP address to be assigned to the Droplet...
2018/09/20 16:53:47 [INFO] stdout: Waiting for machine to be running, this may take a few minutes...

After this we are left with 2 machines in DO .DO machine creation that reported failure when getting provisioned , did not get cleaned up.

@StrongMonkey can you investigate?

@cjellick if docker-machine failed at the very early stage when rancher haven't got back the credential and machine info from docker, the machine will not be cleaned up. I think this should be a general issue for docker-machine.

@sangeethah do you know what caused the
invalid character '<' looking for beginning of value

error?

@cjellick We see this issue happen once in a while when provisioning DO machines. Nothing was done specifically to see this failure.

The error is shown when the DO API returns HTML <html>.., when the API can't return a proper JSON response (due to issues at DO).

I dont think we can do anything about this in v2.1. Will revisit as part of machine refactor in 2.2


samba4Full: update from 4.3.6 to 4.3.8

Things done

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS

[x] Fits CONTRIBUTING.md.

This should be backported to 16.03 (it has the milestone, but commenting as well just to be sure.)

Changed commit description to:

Fixes the following security issues:

CVE-2015-5370 (Multiple errors in DCE-RPC code)
CVE-2016-2110 (Man in the middle attacks possible with NTLMSSP)
CVE-2016-2111 (NETLOGON Spoofing Vulnerability)
CVE-2016-2112 (LDAP client and server don't enforce integrity)
CVE-2016-2113 (Missing TLS certificate validation)
CVE-2016-2114 ("server signing = mandatory" not enforced)
CVE-2016-2115 (SMB IPC traffic is not integrity protected)
CVE-2016-2118 (SAMR and LSA man in the middle attacks possible)

See http://badlock.org/ for details.

And pushed to release-16.03.