fix Initial control mode

Currently when changing control mode before activation the control mode will not change immediately. After activation the hardware interface activating earlier then the controller handler so it starts in the initial state, and changes control mode immediately.
Goal is it should start with the new control mode

Control mode change while deactivation fixed with a bad implementation. The problem is fixed by the controller handler is activated in the configuration callback.

Further task is to implement this in the proper way


Key Vault data-plane SDK with certificate feature

This change is to add the key vault data-plane SDK that is based on AutoRest.
Additionally, key vault's core, cryptography and extension libraries are refactored and moved from 0.9 branch to master branch.

Runtime changes detected. pull request created. CI running:


The url '/saml/metadata ' does not work.

contextProvider at MetadateDisplayFileter class is null. I see other pull request that fix the bug, but it isn't fixed in any release yet. ¿Anyone knows when it is going to be released?

Run into the same problem... seems like it was discussed previously and the source code has the fix... However seems like there were no releases since Mar-2018... should we expect new releases in the nearby future or build from the source?

@rwinch any chance of getting a release on this project. I believe the feature this issue is talking about has been completed on Aug 23, 2018 f656fbed06666c7b43d844961e383bba5945a26e but a release has never went out.


Google rate limit eventually times out

If there are too many trend requests in a session, google authentication times out. Find a way to gather the trend data over multiple sessions.

Switching user credentials doesn't seem too effective, as it prevents the script to run with other credentials over different machines, plus google's bot detection will possibly go into overdrive.
Try to check if the files from earlier requests are there, if so don't waste precious requests over them.

A bit more info, this is the error that is being thrown out:

requests.exceptions.ConnectionError: HTTPConnectionPool(host='www.google.com', port=80): Max retries exceeded with url: /trends/fetchComponent?cid=TIMESERIES_GRAPH_0&q=remove+cookies+computer&export=3&hl=en-US&date=01%2F2011+66m&geo=US (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x110cb7c50>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known',))

Turns out if the number of requests from a valid credential exceeds a certain limit even if the requests are spaced out, google stops listening to them completely if they are made in succession over a certain time period. Switching to a newer credential resolved it.

No useful way around this, follow the strategy:

Add more google accounts, switch to a pool rather than single authentication
Exit only when we have exhausted the pool
Requests are costly, remember everything possible - the data and the failed attempts, everything.

Switching account doesn't help, all request cap is based on IP it seems.

Handled through queued and delayed requests. Closing.


Update year in license

this isn't actually legally needed - existing copyrights aren't invalidated by the advent of a new year

I see, then merge/close as you wish :smile:

Thanks but I think I will stay with the first release year :)


fix: Breaking typo in 0005-remove-dupe-multi-user-target.patch

@utkarsh2102 So... I messed up the patch :frowning_face: There was a trailing "r" typo that will almost definitely break the service file as is. Do I need to create another d/changelog entry? I will if I need to and add it as an extra commit here :smile:

Also, is it worth me creating a new LP bug or shall I just add the new patch there and ask for it to be sponsored, uploaded to lunar, then SRU?

So... I messed up the patch  There was a trailing "r" typo that will almost definitely break the service file as is. Do I need to create another d/changelog entry? I will if I need to and add it as an extra commit here

Yes, each upload warrants a separate d/ch entry with a new version. We cannot reuse the versions we've already used. Just like serials in the image builds.

Also, is it worth me creating a new LP bug or shall I just add the new patch there and ask for it to be sponsored, uploaded to lunar, then SRU?

No, we can (and should) use the same bug for tracking that. I'll mark it from "Fix released" to "New" again.

Yes, each upload warrants a separate d/ch entry with a new version. We cannot reuse the versions we've already used. Just like serials in the image builds.

Added a d/ch entry via fa3cfd9364118723ec0e92ab2ac526a963bf2832 and sponsored the upload.


Fix pulp_pull media type checking

Signed-off-by: Tim Waugh<EMAIL_ADDRESS>Not sure why the tests didn't spot this.

The tests are fine, there doesn't seem to be any way to test for this failure. With recent Python versions these strings just get put into the same objects, even with explicit copy.

@mlangsdorf, the reason this fix is required is that is is a test to see if the two things are the same object (i.e. a is b means id(a) == id(b)), whereas == is the less strict test to see if the two things compare as equal.
In day-to-day code, is None is the main case for using is.

I saw this and thought it should work because the plugin uses the same constant. I realize now that it's not the same object because the value is being passed across systems.

Ah, figured out how to make the test catch this: using json.loads().


Misc Fixes

Without tracked properties, set() is still necessary with native class style modules -- updated existing direct class property assignments in the pagination decorators accordingly
In addition to moment() objects, also serialize Date object query param values to strings
Allow the serialized date format to be customized if needed
remove some commented out code

@bakerac4 bump :P


Fixes #115: Use uuid instead of node-uuid

The uuid package is unsafe, node-uuid is virtually identical and is the replacement. So far as I can tell, it's a drop in replacement. Trying the default configuration manually, it appears to work as expected.

👍 Thanks

Published v4.2.0


Consistent loop implementation in CFE_TBL_FindTableInRegistry and CFE_TBL_FindFreeRegistryEntry

Is your feature request related to a problem? Please describe.
Loops could be the same but aren't:
https://github.com/nasa/cFE/blob/84ba9a9974794e239b989cdc4e2359216e44fab0/modules/tbl/fsw/src/cfe_tbl_internal.c#L510-L525
https://github.com/nasa/cFE/blob/84ba9a9974794e239b989cdc4e2359216e44fab0/modules/tbl/fsw/src/cfe_tbl_internal.c#L543-L556
Describe the solution you'd like
Consistent implementation
Describe alternatives you've considered
None
Additional context
Code review - note this is style suggestion only
Requester Info
Jacob Hageman - NASA/GSFC

No longer relevant since https://github.com/nasa/cFE/pull/2539


fix timestamp format issue for range partitioned table

the format of Timestamp/Date use a static variable, it is not proper.
the format of Timestamp/Date:
during dataloading,  if load sql specific datefromat, use it. if not, use carbon property.
during query, use spark/hive dateformat.
during create table, use carbon property.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2519/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/404/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2520/

LGTM

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/405/Failed Tests: 2carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-core: 2org.apache.carbondata.core.writer.CarbonFooterWriterTest.testWriteFactMetadataorg.apache.carbondata.core.writer.CarbonFooterWriterTest.testReadFactMetadata


duplicated subworkflow in FORK_JOIN_DYNAMIC

Describe the bug
two subworkflow were forked in FORK_JOIN_DYNAMIC.

Details
Conductor version:
Persistence implementation: MySQL
Queue implementation:  Dynoqueues
Lock: Local
Workflow definition:
Task definition:
Event handler definition:

I've got the same problem (duplications of subworkflow invocation) even without dynamic fork. I found out that problem lies directly in SUB_WORKFLOW task status flow.
SubWorkflow changes state from SCHEDULED to IN_PROGRESS only when child workflow is started and it appears that the time between taking subworkflow task from the queue and switching its state to IN_PROGRESS is often enough for WorkflowRepairService to push this task on the queue again and start it.
Only workaround that comes to my mind is to switch the repair service off (set conductor.workflow-repair-service.enabled property to false). Is it actually only solution to this problem?
Wouldn't be better if SubWorkflow changed the state to IN_PROGRESS just after it's taken from the queue?

After moving to v3.13.8 I've started getting this error when calling subworkflow in FORK_JOIN_DYNAMIC:
Workflow ${workflowid} is terminated because of Parent workflow has been terminated with reason: No dynamic tasks could be created for the Workflow: ${workflowname.id}, Dynamic Fork Task: ${taskname}/${taskreferencename}Attempted to create a duplicate task reference name: ${taskreferencename}
But all the task descriptions I feed into the FORK_JOIN_DYNAMIC have a different taskreferencename (doublechecked it in several ways).
Could this be related to this issue?
I use FORK_JOIN_DYNAMIC in several other workflows (but with simple tasks instead of call_sub_workflow) and this doesn't seem to happen there...

setting conductor.workflow-repair-service.enabled to false did not help...


🐛 [firebase_messaging] android.os.BadParcelableException crash application

Bug report
Describe the bug
I'm getting app crash error on Firebase Crashlytics:
Log error:
Fatal Exception: android.os.BadParcelableException: Parcelable protocol requires subclassing from Parcelable on class com.google.firebase.messaging.w0
       at android.os.Parcel.readParcelableCreator(Parcel.java:3406)
       at android.os.Parcel.readParcelable(Parcel.java:3337)
       at android.os.Parcel.readValue(Parcel.java:3239)
       at android.os.Parcel.readArrayMapInternal(Parcel.java:3636)
       at android.os.BaseBundle.initializeFromParcelLocked(BaseBundle.java:292)
       at android.os.BaseBundle.unparcel(BaseBundle.java:236)
       at android.os.Bundle.getParcelable(Bundle.java:1002)
       at android.content.Intent.getParcelableExtra(Intent.java:9187)
       at io.flutter.plugins.firebase.messaging.b.d(:22)
       at io.flutter.plugins.firebase.messaging.FlutterFirebaseMessagingBackgroundService.l(:2)
       at io.flutter.plugins.firebase.messaging.FlutterFirebaseMessagingBackgroundService.j()
       at d4.d.run(:4)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:226)
       at android.os.Looper.loop(Looper.java:313)
       at android.app.ActivityThread.main(ActivityThread.java:8751)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

Steps to reproduce
Steps to reproduce the behavior:

Use firebase_messaging: ^14.6.1

Expected behavior
There shouldn't be crashes.
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.0, on macOS 13.0 22A380 darwin-arm64, locale en-VN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[!] Xcode - develop for iOS and macOS (Xcode 14.2)
    ! CocoaPods 1.10.2 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] Connected device (3 available)
[✓] Network resources

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.0.0
Flutter SDK 3.10.0
kvcrm_app 1.9.12+30

dependencies:
- analyzer 5.11.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- badges 3.1.1 [flutter]
- bloc 8.1.1 [meta]
- cupertino_icons 1.0.5
- dartx 1.1.0 [characters collection crypto meta path time]
- dartz 0.10.1
- diacritic 0.1.3
- dio 5.1.2 [http_parser meta path]
- dotted_border 2.0.0+3 [flutter path_drawing]
- email_validator 2.1.17
- file_picker 5.3.0 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface ffi path win32]
- firebase_analytics 10.4.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_core 2.13.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.3.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.6.1 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_app_badger 1.5.0 [flutter]
- flutter_bloc 8.1.2 [flutter bloc provider]
- flutter_fgbg 0.2.2 [flutter]
- flutter_keyboard_visibility 5.4.1 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_linux flutter_keyboard_visibility_macos flutter_keyboard_visibility_web flutter_keyboard_visibility_windows flutter]
- flutter_local_notifications 14.0.0+2 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_localizations 0.0.0 [flutter intl characters clock collection js material_color_utilities meta path vector_math]
- flutter_speed_dial 6.2.0 [flutter]
- flutter_sticky_header 0.6.5 [flutter value_layout_builder]
- flutter_svg 2.0.5 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_typeahead 4.3.3 [flutter flutter_keyboard_visibility flutter_sticky_header]
- freezed_annotation 2.2.0 [collection json_annotation meta]
- get_it 7.6.0 [async collection]
- image_picker 0.8.7+5 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_platform_interface]
- injectable 2.1.1 [get_it]
- intl 0.18.0 [clock meta path]
- json_annotation 4.8.1 [meta]
- mime_type 1.0.0
- package_info_plus 4.0.0 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface win32]
- pretty_dio_logger 1.3.1 [dio]
- remove_emoji 0.0.9
- shared_preferences 2.1.1 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shimmer 2.0.0 [flutter]
- syncfusion_flutter_core 21.2.5 [vector_math flutter]
- syncfusion_flutter_datepicker 21.2.5 [flutter intl syncfusion_flutter_core]
- url_launcher 6.1.11 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.7 [crypto]

dev dependencies:
- build_runner 2.4.4 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- dart_code_metrics 5.7.3 [analyzer analyzer_plugin ansicolor args collection crypto dart_code_metrics_presets file glob html http meta path platform pub_updater source_span uuid xml yaml]
- dart_code_metrics_presets 1.7.0
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- freezed 2.3.3 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- injectable_generator 2.1.5 [build source_gen path glob analyzer code_builder dart_style injectable collection recase]
- json_serializable 6.6.2 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]

transitive dependencies:
- _fe_analyzer_shared 59.0.0 [meta]
- _flutterfire_internals 1.3.1 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer_plugin 0.11.2 [analyzer collection dart_style pub_semver yaml]
- ansicolor 2.0.1
- args 2.4.1
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.0 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.2.0 [analyzer async build collection crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.8 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.5.0 [built_collection collection fixnum meta]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- clock 1.1.1
- code_builder 4.4.0 [built_collection built_value collection matcher meta]
- collection 1.17.1
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+4 [js meta]
- crypto 3.0.3 [typed_data]
- csslib 0.17.2 [source_span]
- dart_style 2.3.1 [analyzer args path pub_semver source_span]
- dbus 0.7.8 [args ffi meta xml]
- fake_async 1.3.1 [clock collection]
- ffi 2.0.2
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.6.1 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.4+1 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_core_platform_interface 4.8.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.5.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.1 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.1 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.1.0
- flutter_keyboard_visibility_linux 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_macos 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_keyboard_visibility_windows 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_local_notifications_linux 4.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 7.0.0+1 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 2.0.14 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 3.2.0 [async path]
- glob 2.1.1 [async collection file path string_scanner]
- graphs 2.3.0 [collection]
- html 0.15.3 [csslib source_span]
- http 0.13.6 [async http_parser meta]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image_picker_android 0.8.6+14 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 2.1.12 [flutter flutter_web_plugins image_picker_platform_interface]
- image_picker_ios 0.8.7+4 [flutter image_picker_platform_interface]
- image_picker_platform_interface 2.6.3 [cross_file flutter http plugin_platform_interface]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- lints 2.1.0
- logging 1.1.1
- matcher 0.12.15 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.2.0
- meta 1.9.1
- mime 1.0.4
- nested 1.0.0 [flutter]
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path 1.8.3
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_linux 2.1.10 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.6 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.6 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.4.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.4 [meta]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 6.0.5 [collection flutter nested]
- pub_semver 2.1.4 [collection meta]
- pub_updater 0.3.0 [http json_annotation process pub_semver]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- recase 4.1.0
- shared_preferences_android 2.1.4 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.2.2 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.2.0 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.2.0 [flutter plugin_platform_interface]
- shared_preferences_web 2.1.0 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.2.0 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.3.2 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.3 [analyzer collection source_gen]
- source_span 1.9.1 [collection path term_glyph]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.5.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- time 2.1.3 [clock]
- timezone 0.9.2 [path]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- url_launcher_android 6.0.33 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.4 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.16 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.6 [flutter url_launcher_platform_interface]
- value_layout_builder 0.3.1 [flutter]
- vector_graphics 1.1.5+1 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.5+1
- vector_graphics_compiler 1.1.5+1 [args meta path_parsing xml vector_graphics_codec]
- vector_math 2.1.4
- watcher 1.1.0 [async path]
- web_socket_channel 2.4.0 [async crypto stream_channel]
- win32 4.1.4 [ffi]
- xdg_directories 1.0.0 [meta path process]
- xml 6.3.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]

@tuyennvt
Is there a way for you to provide steps to replicate or a pattern that leads to this crash ?
There have been similar reports earlier but without concrete steps to replicate or wasn't replicable. One such maybe you can try to use is as mentioned here and see if it replicates at your end or not.


Introduce short, random reconnection delay

Description
To mitigate concerns like #74 due to connection storms on the broker, we have had some discussion around introducing a short random delay to the broker reconnection logic.
As an initial number, we discussed up to 30s as a maximum delay.
What is unclear at this time is if this would improve matters during large disconnect/reconnect cycles or have an affect of extend any issues resulting from it.
We discussed internally potential load testing on a non production platform - that would go some way to fine tuning this connection delay.
As a side note, there are other strategies and ongoing works that will further mitigate potential connection storm like  issues - however these are not quickly achievable tasks.
related: #74
related: #98
Epic/Story
No response
### Tasks
- [ ] https://github.com/FlowFuse/device-agent/issues/314
- [ ] https://github.com/FlowFuse/nr-project-nodes/issues/103

both merged


[Bug] Multihead task routines eval steps not specified.

Description
What feature/issue was addressed?
Eval steps is not specified for multihead task routines. Did not manage to see where it is being used initially.
How was it resolved/added?
Specified eval steps in default configs, so future devs know to configure it.
Any dependencies required for the change?
Issue reference
Please reference the issue this PR will close: #95.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (Specify)

Tests
Any reproducable method of testing to verify changes?
List relevant details for the test configuration.
Checklist

[x] I have performed a self-review of my own code. Feel free to destroy my PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.

Will document these in https://github.com/whizzmobility/models/wiki/Configuring-experiments eventually.


return nothing using full text search with mariadb 10 and next.js 13

Bug description
Simply speaking, search field is not working without any error messages.
There is no search results in the codes below...
How to reproduce

enabled the necessary preview features in my Prisma schema.
database schema includes the appropriate full-text indexes.
Prisma Client has been regenerated after making schema changes.

Expected behavior
No response
Prisma information

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["fullTextSearch", "fullTextIndex"]
}

datasource db {
  provider     = "mysql"
  url          = env("DATABASE_URL")
  relationMode = "prisma"
}

model apartment {
  id          Int                @id @default(autoincrement())
  name        String             @db.VarChar(50)
  address     String             @db.VarChar(100)
  gu          String             @db.VarChar(20)
  dong        String             @db.VarChar(20)
  use_date    Int
  household   Int
  contract    Int
  meter_date  Int
  latitude    Float
  longitude   Float
  consumption apt_elec_consump[]

  @@fulltext([name])
}

const apartment = await prisma.apartment.findMany({
    where: {
      name: {
        search: "word",
      },
    },
  });

Environment & setup

OS: Ubuntu 20.04
Database: Mariadb 10
Node.js version: 18.17.1

Prisma Version
prisma                  : 5.3.1
@prisma/client          : 5.3.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 61e140623197a131c2a6189271ffee05a7aa9a59 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 61e140623197a131c2a6189271ffee05a7aa9a59 (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.3.1-2.61e140623197a131c2a6189271ffee05a7aa9a59
Default Engines Hash    : 61e140623197a131c2a6189271ffee05a7aa9a59
Studio                  : 0.494.0
Preview Features        : fullTextIndex, fullTextSearch

Hi @daeb2a, is it ok for you to share your database dump (or Prisma seed.ts file) with us, for reproduction purposes? Have you by any chance tried the same code against a MySQL 8 database instance?

Hi @jkomyno, I haven't tried in MySQL 8. Here's a part of database dumps!
apartment.zip

What SQL query does "search" vs "contains" generate?

@alexpirine I couldn't get it what you mean. Please give me a chance to understand what you said.

@alexpirine I couldn't get it what you mean. Please give me a chance to understand what you said.

I thought
const apartment = await prisma.apartment.findMany({
    where: {
      name: {
        contains: "word",
      },
    },
  });

works, while
const apartment = await prisma.apartment.findMany({
    where: {
      name: {
        search: "word",
      },
    },
  });

doesn't.

@romaob Thank you for answering! but your suggestion is not working to mine. since it was not working with search, I solved this issue using contains with js methods like below.
  let combinedKeyword = [];
  const letterArray = keyword?.split("");
  if (letterArray) {
    for (let i = 0; i <= letterArray.length; i++) {
      for (let j = 2; j <= letterArray.length; j++) {
        combinedKeyword.push(letterArray.slice(i, j).join(""));
      }
    }
  }
  const filteredKeyword = combinedKeyword.filter((word) => word.length >= 2);
  const ultimateKeyword = filteredKeyword.map((word) => ({
    name: {
      contains: word,
    },
  }));

  const apartment = await prisma.apartment.findMany({
    where: {
      OR: ultimateKeyword.length === 0 ? undefined : ultimateKeyword,
    }
  });

@janpio I definately typed codes like below which are totally same as the documentations.
I just tried the way below because I wanted to check first if the codes in the simplest structure are working. but that couldn't get any results.
// All posts that contain the words 'cat' or 'dog'.
const result = await prisma.posts.findMany({
  where: {
    body: {
      search: 'cat dog',
    },
  },
})

Can you enable Prisma Client query logging and share the query that this executes? Can you also shared a screenshot of the data in that table that you would expect to be returned?

Hey @danx2y ,
Did you get a chance to have a look at my colleagues previous comment? It'd be helpful for us to move your issue forward.
Thank you 🙏

Hi @danx2y, can you please take a look at this comment, and provide an answer below?
Without that, I'm afraid we won't be able to reproduce this issue, and we'll be forced to close it. Thanks!

@jkomyno @SevInf @janpio Sorry for late replying, I will try it tonight!

@jkomyno @SevInf @janpio I just checked db server shut down now so I couldn't check more.... Since I can't handle the server now this issue should be closed....Sorry for saying that

Thank you @danx2y, I'll close issue as non-reproducible for now. Feel free to comment if you'll encounter it again and will be able to provide requested info.


Success Stories - Implemented Template and Styles

When there are only 2 items on a row the are located in the left and right column with the middle column remaining empty.  Otherwise, looks good.


added yaml example config file

This patch adds an example config yaml file.

Referencing issue https://github.com/emccode/rexray/issues/43

Hi @clintonskitson,
I'd like to close this PR without accepting it so I can create a default config file that includes all of the default options as well as commented out provider options with explanations. Thoughts?

one thing to add is to please note where the config.yml file needs to be dropped so RR can read it. or note if it must be referenced during sudo rexray service start
thanks gents

Hi @kacole2,
The command already shows one place:
REX-Ray:
  A guest-based storage introspection tool that enables local
  visibility and management from cloud and storage platforms.

Usage:
  rexray [flags]
  rexray [command]

Available Commands:
  volume      The volume manager
  snapshot    The snapshot manager
  device      The device manager
  adapter     The adapter manager
  service     The service controller
  version     Print the version
  help        Help about any command

Global Flags:
  -c, --config="/home/akutz/.rexray/config.yaml": The REX-Ray configuration file
  -?, --help[=false]: Help for rexray
  -h, --host="tcp://:7979": The REX-Ray service address
  -l, --logLevel="info": The log level (panic, fatal, error, warn, info, debug)
  -v, --verbose[=false]: Print verbose help information

Use "rexray [command] --help" for more information about a command.

However, I'll update the docs to reflect the official locations. FWIW, anyone can open a PR and update the docs. :)

thanks... i didn't notice that.
as for the hidden directory /home/akutz/.rexray/, was that created during sudo rexray service install? Just curious because I will need to retrieve the home path for the current user and append that folder for the docker-machine process.

Hi @kacole2,
It doesn't exist. The rule is that the config file is parsed first from $HOME/.rexray/config.yaml if it exists and then /etc/rexray/config.yaml if that exists. Otherwise it doesn't use a config file unless one is specified on the command line with the flag you see above.

Perfect.  Thanks

On Sep 11, 2015, at 3:25 PM, Schley Andrew Kutz<EMAIL_ADDRESS>wrote:
Hi @kacole2,
It doesn't exist. The rule is that the config file is parsed first from $HOME/.rexray/config.yaml if it exists and then /etc/rexray/config.yaml if that exists. Otherwise it doesn't use a config file unless one is specified on the command line with the flag you see above.
—
Reply to this email directly or view it on GitHub.

I'm good with that @akutz


编译命令：
make -j4 > /dev/null

报错信息：
Note: checking out '1.1.7'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at b02bfa7... Tag open source release 1.1.7.
Note: checking out '1.8.4'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at ddabf50... 1.8.4; soversion=20
Note: checking out 'v2.2.4'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at 9a19306... bump version to 2.2.4
CMake Warning:
  Manually-specified variables were not used by the project:
    BUILD_TESTING
Note: checking out 'v1.2.8'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at 5089329... zlib 1.2.8
Note: checking out '77592648e3f3be87d6c7123eb81cbad75f9aef5a'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at 7759264... repair wrong namespace problem
Note: checking out '9f75c5aa851cd877fb0d93ccc31b8567a6706546'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
  git checkout -b new_branch_name
HEAD is now at 9f75c5a... Merge pull request #2337 from sergiocampama/deprecation
/Serving/core/cube/cube-transfer/src/github.com/Badangel/logex/file_logger.go:22:2: no Go files in /Serving/core/cube/cube-transfer/src/github.com/mipearson/rfw
make[2]: *** [core/cube/cube-transfer/CMakeFiles/logex] Error 1
make[1]: *** [core/cube/cube-transfer/CMakeFiles/logex.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [all] Error 2

该文件是在编译过程中下载的，当网络条件不好的时候会遇到。


secp256k1

Since, now we have secp256k1 in https://github.com/C0MM4ND/dart-elliptic as well, do you that makes this package redundant?

Honestly speaking, yes. But google doesnt allow us to delete the package so I have to continue maintaining this repo/package.


Drop support for Python 2

We've been getting a number of support cases over the past few months for upgrading tuspy to the latest version (https://github.com/vimeo/vimeo.py/pull/136). Unfortunately we can't do that because support for Python 2 was dropped in version 0.2.2.
Let's drop our support for Python 2 as well, upgrade tus, and release a 2.0 release. Let's also branch off the current master so we can retain the ability to do support releases for the 1.x release branch if need be.

ok thank you

Hi, is there any news on this? Thanks

Please see PR https://github.com/vimeo/vimeo.py/pull/147 to drop support for Python 2.


Attacks show +0 to hit?

For some reason attacks are showing +0 to hit, but if actually rolled, they roll the appropriate modifiers (Ability Modifier + Challenge Rating Modifier).

Is this effecting all attacks and all creatures? Does this happen when Monster Blocks is the only module enabled? What version of Monster Blocks, dnd5e, and Foundry are you running?

Solved: Outdated Dynamic Effect module


Toolkit Update

Fixes a few issues with integration workflows
Adds "Composer Unused" for cruft package detection

codeigniter4/settings is clearly used but I think since all its interactions happen through the helper function it is a bit opaque to "Composer Unused" so I'm ignoring it for now.


Potential memory leak in sql stats search

It appears come rxJava objects are holding onto the dashboard results, specifically many many instances of ValStr.
Seen in 5.2.3

Released speculative fix in 5.3.4


First request running twice

Right now, visiting a page that has a trpc query in it's load function (ex. /authors) , will result in that trpc query running twice. First on the server, then again on the client. This is happening  (I think) because we're not using the  fetch provided by load.
Note: This is only applicable to the first request, since all other requests after that are client side only.
There two ways to go around this issue:

Move the trpc query from load to a page endpoint.
Find a way to make trpc use the  fetch provided by load. No idea how.

This would ensure that the request would not happen twice. It would happen only on the server.
From the docs:

When fetch runs on the server, the resulting response will be serialized and inlined into the rendered HTML. This allows the subsequent client-side load to access identical data immediately without an additional network request.

Update: Moving the trpc query from load to a page endpoint breaks the Date type. I tried passing load's fetch to trpc client but couldn't really get it to click.

Thanks a lot for investigating this and coming up with the PR!

Update: Moving the trpc query from load to a page endpoint breaks the Date type. I tried passing load's fetch to trpc client but couldn't really get it to click.

Is this happening even if you're using the superjson transformer?

Also, there might be a slight problem with this:
const url = browser ? '/trpc' : 'http://localhost:3000/trpc';
const client = (loadFetch?: typeof fetch) =>
  trpc.createTRPCClient<Router>({
    url: loadFetch ? '/trpc' : url,
      ...(loadFetch && { fetch: loadFetch }),
});

The client gets recreated every time. I don't how what's the overhead, but I think we could better do it like this:
let client: TRPCClient<Router>;
export default (loadFetch?: typeof fetch) => {
  if (!client) {
    const url = browser ? '/trpc' : 'http://localhost:3000/trpc';
    client = trpc.createTRPCClient<Router>({
      url: loadFetch ? '/trpc' : url,
      transformer: trpcTransformer,
      ...(loadFetch && { fetch: loadFetch })
    });
  }
  return client;
};

What do you think?

Is this happening even if you're using the superjson transformer?
Yeah.

The client gets recreated every time. I don't how what's the overhead.

That's true. It'd be great if there was a way to avoid that. Besides the fact that there would be multiple clients floating around, one other thing I noticed is that trpc will not batch queries unless they belong to the same client.
So instead of this:
export const load: Load = async ({ params, fetch }) => {
  const [authors, books] = await Promise.all([
    trpc(fetch).query('authors:browse', params.id),
    trpc(fetch).query('books:list'),
  ]);
  // ...

You'd do this (if you want to benefit from query batching):
export const load: Load = async ({ params, fetch }) => {
  const trpcClient = trpc(fetch);
  const [authors, books] = await Promise.all([
    trpcClient.query('authors:browse', params.id),
    trpcClient.query('books:list'),
  ]);
  // ...

Regarding your suggestion
I think your second snippet is on the right track. But it doesn't fix the duplication because the first two requests need the same url (/trpc). After the first two requests (1 on server, 1 on client), we should be able to keep using the same client instance (I think).
If we do that, we should keep in mind that sveltekit's fetch is what enables us to use the same relative url. Without it, we'd have to always check const url = browser ? '/trpc' : 'http://localhost:3000/trpc'

Perhaps @KATT would know if it's currently possible to pass in fetch to an existing trpc client without creating a new instance. Or, if it's not currently possible, what we could try to make it happen.
And if it's not possible at all, whether the overhead for creating a new trpc client for each request is negligible or something to worry about.

I think your second snippet is on the right track. But it doesn't fix the duplication because the first two requests need the same url (/trpc). After the first two requests (1 on server, 1 on client), we should be able to keep using the same client instance (I think).

You're right.

There might me a much simpler way we can get the desired behavior.
// client/trpc.ts
const client = trpc.createTRPCClient<Router>({
	url: '/trpc',
	transformer: trpcTransformer,
});
export default client;

// index.svelte
export const load: Load = async ({ params, fetch }) => {
  trpc.runtime.fetch = fetch; // <-- This
  trpc.query('authors:browse', params.id),
  // ...

Granted, I haven't tested this beyond some basic functionality on my machine, but at first glance querying & batching work seamlessly.
There is another issue though. runtime's type signature is marked as readonly, and I'm not sure why.
Summary:
Benefits of this approach:

No more duplicate trpc clients.

Because fetch property of the existing client instance is updated rather than create a new instance on every query.

No more duplicate queries in ssr mode.

sveltekit's fetch -> enables use of relative url -> which then enables sveltekit to avoid a duplicate network request in the client

Cons:

Type error because runtime is marked as readonly.
Apporach hasn't been tested sufficiently.

Anyways, it's something we can explore if we want to.

After some testing, I wouldn't recommed the approach I outlined in my previous comment:
trpc.runtime.fetch = fetch

While this approach may seem to work fine initially, you'll run into unwanted behavior where the trpc client instance is shared amongst different sessions/users. To see this in action, add authz to your trpc router, and run some parallel tests simulating users with different authz rules (using playwright, etc). You'll notice then that your auth rules/middleware/context is suffering from cross contamination between different users/sessions.
I have a feeling it could be related to the part in the docs which states:

Mutating any shared state on the server will affect all clients, not just the current one.

Instead, use the approach outlined in this pr, which works perfectly fine.


Buffer overflow

Avoided para and made in point @SANTHOSH17-DOT

PLease add difficulty tag sir or else i will not getting point in my iwoc competion @SANTHOSH17-DOT PLease sir

can you merge it sir or if any change needed then please comment sir @SANTHOSH17-DOT


seo edits

Docs Build status updates of commit 6769eda:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/quickstart/create-and-publish-a-package-using-visual-studio.md
:white_check_mark:Succeeded
View

docs/what-is-nuget.md
:white_check_mark:Succeeded
View

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.


Lost an access to the cluster after 17->19 upgrade

Description
Hi, we were doing 17 to 19 cluster upgrade and there was this change:
# module.eks.kubernetes_config_map.aws_auth[0] will be destroyed
  - resource "kubernetes_config_map" "aws_auth" {
      - binary_data = {} -> null
      - data        = {
          - "mapAccounts" = jsonencode([])
          - "mapRoles"    = <<-EOT
                - groups:
                  - system:bootstrappers
                  - system:nodes
                  rolearn: ***eu-demo2021033013554161720000000e
                  username: system:node:{{EC2PrivateDNSName}}
                - groups:
                  - system:masters
                  rolearn: ***eu-demo-admin
                  username: eu-demo-admin
                - groups:
                  - system:bootstrappers
                  - system:nodes
                  rolearn: ***role/default-eks-node-group-20230607090420909900000004
                  username: system:node:{{EC2PrivateDNSName}}
            EOT
          - "mapUsers"    = <<-EOT
                - "groups":
                  - "system:masters"
                  "userarn": "***user/automation-user-eu-demo"
                  "username": "automation-user-eu-demo"
            EOT
        } -> null
      - id          = "kube-system/aws-auth" -> null
      - immutable   = false -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {
              - "app.kubernetes.io/managed-by" = "Terraform"
              - "terraform.io/module"          = "terraform-aws-modules.eks.aws"
            } -> null
          - name             = "aws-auth" -> null
          - namespace        = "kube-system" -> null
          - resource_version = "342874526" -> null
          - uid              = "c5bff957-fa59-4821-97bf-77acd3cbea61" -> null
        }
    }

  # module.eks.kubernetes_config_map_v1_data.aws_auth[0] will be created
  + resource "kubernetes_config_map_v1_data" "aws_auth" {
      + data          = {
          + "mapAccounts" = jsonencode([])
          + "mapRoles"    = <<-EOT
                - "groups":
                  - "system:bootstrappers"
                  - "system:nodes"
                  "rolearn": "arn:***role/default-eks-node-group-20230607090420909900000004"
                  "username": "system:node:{{EC2PrivateDNSName}}"
                - "groups":
                  - "system:masters"
                  "rolearn": "arn:***role/eu-demo-admin"
                  "username": "eu-demo-admin"
            EOT
          + "mapUsers"    = <<-EOT
                - "groups":
                  - "system:masters"
                  "userarn": "arn:***user/automation-user-eu-demo"
                  "username": "automation-user-eu-demo"
            EOT
        }
      + field_manager = "Terraform"
      + force         = true
      + id            = (known after apply)

      + metadata {
          + name      = "aws-auth"
          + namespace = "kube-system"
        }
    }

Versions

Module version [Required]:
19.15.2
Terraform version:
1.0.9
Provider version(s):

+ provider registry.terraform.io/gavinbunney/kubectl v1.14.0
+ provider registry.terraform.io/hashicorp/aws v4.57.0
+ provider registry.terraform.io/hashicorp/azurerm v2.66.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.3.2
+ provider registry.terraform.io/hashicorp/google v3.82.0
+ provider registry.terraform.io/hashicorp/helm v2.2.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.20.0
+ provider registry.terraform.io/hashicorp/null v3.2.1
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/hashicorp/time v0.9.1
+ provider registry.terraform.io/hashicorp/tls v4.0.4
+ provider registry.terraform.io/hashicorp/vault v2.23.0
+ provider registry.terraform.io/terraform-aws-modules/http v2.4.1

Reproduction Code [Required]
cluster_encryption_config = {
    provider_key_arn = aws_kms_key.encryption.arn
    resources        = ["secrets"]
  }

  manage_aws_auth_configmap = true
  create_kms_key            = false

  aws_auth_users = setunion([
    {
      userarn  = aws_iam_user.automation_user.arn
      username = aws_iam_user.automation_user.name
      groups   = ["system:masters"]
    }
  ], var.eks_map_users)

  aws_auth_roles = [
    {
      rolearn  = aws_iam_role.eks_admin_role.arn
      username = aws_iam_role.eks_admin_role.name
      groups = [
        "system:masters"
      ]
    }
  ]

Steps to reproduce the behavior:
 no
 yes
 apply
Expected behavior
kubectl able to access the cluster
Actual behavior
kubectl get pods
error: You must be logged in to the server (Unauthorized)

Additional context
all role arn are exactly the same.
Maybe you know how to proceed with recovering the cluster?

probably duplicate of #2600

upd: I restored the access, there was no configmap at all.

Exactly, the plan states it will first destroy the aws-auth ConfigMap which configures authentication. After its removal you are no longer authorized to perform any actions (e.g. create the new aws-auth). There is no AWS API to modify the aws-auth ConfigMap, so you have to use the K8s API itself.
To prevent accidents like this some TF modules ignore any changes to aws-auth after its initial creation.

Although I understand that it's not clear to me what's the way to handle the migration. Or aws_auth configmap in general.

Alright, I think I figured that out. In my case I should use create_aws_auth_configmap = true to prevent existing configmap removal and wait for https://github.com/aws/containers-roadmap/issues/185


Deduplicate gltf materials during scene writing

This is a new feature for GLTF writer, to deduplicate identical materials and only write the necessary number of unique materials, rather than a material per model. Different models using the same material will correctly reference the single instance of this material.
This improves size of the resulting GLTF/GLB file without changing the functionality in any way. This is adhering to GLTF spec - the separation of materials from models and explicit reference via material index encourages reuse of material objects imo.

This is a great addition! One way to improve efficiency and avoid unnecessary checks is to change the signature of AddMaterial(mat PolyformMaterial) to take a pointer AddMaterial(mat *PolyformMaterial).
This way we can first check if the pointers are referencing the same thing, and if not, then we start doing our equality checks.
It's a breaking change to the API, but a very tiny one.

This is a great addition! One way to improve efficiency and avoid unnecessary checks is to change the signature of AddMaterial(mat PolyformMaterial) to take a pointer AddMaterial(mat *PolyformMaterial).
This way we can first check if the pointers are referencing the same thing, and if not, then we start doing our equality checks.
It's a breaking change to the API, but a very tiny one.

Cool. I didn't want to break the API, but if you think it's ok - I'll add that.

@EliCDavis I don't have write access to your repo, so I don't have a merge button to click 🙂
Can you push the button on your end please?


Vite v5 compatibility?

When installing this package in a project using Vite v5, I get the following warning:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^4.0.0".

The plugin still seems to work, however.
Are there plans to officially support Vite v5 by updating the peer dependency specification?

Hey @mattbrictson yep definitely plan on updating to officially support Vite v5. It most definitely won't need any updates other than the peer dependency you mentioned. Thanks for the reminder.

Release 3.0.0 which adds support for Vite v5. Please let me know if you experience any issues. https://github.com/cmalven/vite-plugin-sass-glob-import/releases/tag/3.0.0

@Jackky90 I just released 3.0.1 which will hopefully fix this issue. Would you mind trying it out and letting me know if it works for you?

@Jackky90 I just released 3.0.2 which will hopefully fix this issue. Would you mind trying it out and letting me know if it works for you?

Will check this in next 10 hours, ok

@Jackky90 I just released 3.0.2 which will hopefully fix this issue. Would you mind trying it out and letting me know if it works for you?

Sorry, completely forgot to check this out yesterday. Just got updated and at first sight all working as expected. I think you can close this issue now. If I find something weird I will reopen issue either create new, depends.


[Bug] pulsar - avro.version has a vulnerability CVE-2021-43045

Search before asking

[X] I searched in the issues and found nothing similar.

Version
For the pulsar version : 2.11.0 facing a high vulnerability CVE-2021-43045 related to packages:

org.apache.avro:avro
org.apache.avro:avro-protobuf
org.yaml:snakeyaml

Below are the versions available in pulsar client.

<avro.version>1.10.2</avro.version>
<snakeyaml.version>1.31</snakeyaml.version>

Maven Dependency

pulsar
org.apache.pulsar
2.11.0

Minimal reproduce step
Run the blackDuck Scan.
What did you expect to see?
Internal Jar need to expected to fix the blackDuck issues.
What did you see instead?
vulnerability

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@velagalasantosh The linked CVE seems to be only related to C# version of Avro, right?

I understand this is getting flagged (and it will be fixed ASAP). From a risk perspective though it wouldn't apply as a vulnerability:

Closing as invalid.
This is a vulnerability report for .NET SDK. We're using the Java SDK only.


Better Search

Funguje to, staci doladit ako to vyzera:

Viac info postnem sem.

Tak uz to vyzera lepsie a funguje to paradne

![selection_018](https://user-images.githubusercontent.com/419849/37080869-e4230b68-21e7-11e8-

looks cool

Len pre evidenciu

Hi there,
Congratulations, your search is now ready!
I've successfully configured the underlying crawler and it will now run every 24h.
You're now a few steps away from having it working on your website:

Copy the following CSS/JS snippets and add them to your page

Add a search input if you don't have any yet, and update the inputSelector value in the code snippet to a CSS selector that targets your input field.
Optionally customize the look and feel by following the DocSearch documentation (https://community.algolia.com/docsearch/documentation/)
You can also check your configuration in the github repo (https://github.com/algolia/docsearch-configs/blob/master/configs/keboola_developers.json). Feel free to open pull requests!

Feel free to get back to us if you have any issues or questions regarding the integration.
We'd also be happy to get your feedback and thoughts about DocSearch - so we can continue to improve it.
Have a nice day :)

^ Podstatna je ta cast, kde pise, ze si to mozeme doladit poslanim PR:

You can also check your configuration in the github repo (https://github.com/algolia/docsearch-configs/blob/master/configs/keboola_developers.json). Feel free to open pull requests!


Result list for region overview is sometimes empty, sometimes correct

When inspecting a region, e.g. https://explorer.eo2cube.org/product/s2_c1_l2a/regions/33UVV, the result list is sometimes as expected:

But sometimes it is empty, claiming "No datasets":

Note that this is the same dataset! Requested only shortly apart, without any commands having run in the meantime.
This may change within seconds. I loaded the link repeatedly and it feels like it's fine in maybe a third of the cases, but wrong in the other two thirds.
I tried to refresh the product by running cubedash-gen --verbose --force-refresh s2_c1_l2a, but that didn't fix it. I can post the log if that helps. Let me know what other information you would like to see to narrow down a reason for this behaviour, as I understand that it's probably hard to debug anything from the current info in this bug report.
Expected behaviour: Consistent output at every request.

Anyone has an idea why this might be happening? It's quite an annoying bug when people want to browse our available data as they falsely think there is none. I'd be open to do some fixing myself, but would appreciate a hint where I should start looking.

Hi Christoph, I can't say I've ever seen this behaviour before, and so far I have been unable to recreate it. The only thing I can think of as to what might be causing it is some sort of issue with database connectivity, but I can't say for certain. If you could provide the logs, that might be helpful.


Two test un xfails

Fix a couple tests that were incorrectly sensitive to the difference between release and release-assert mode. NFC.
rdar://35537905
rdar://35639403

@swift-ci please test and merge


Confusion regarding volume of S1 Data Vesicle RF was tested on

I had a question regarding the size of the S1 data the synapse detection has been run on in VESICLE.
As per my understanding, the original images from the microscope (in correspondence from Harvard) were of size 16384x16384 at 3nmx3nmx29nm ~ 129614um^3. However, in the VESICLE paper, it is said that the downsampled S1 that the RF was run on was 60,000um^3. Could you please help me understand the discrepancy? In the original Kasturi paper, they say their volume is ~80,000um^3 after chopping the 6nm data, which is still larger that 60,000um^3.

Cool - glad you found this!  What brings you here?
We ran on an inscribed cube - basically we did our best to take the largest cuboid that had data on all 1850 slices, which came out to about 60,000 um.  If you need more (or the actual bounds), I can pull - just let me know!

Hey William,
Thank you for your prompt reply. This helps!
I was trying to compare the estimates of number of synapses in S1 based on
the Kasturi paper and those suggested by your paper and I was confused by
the discrepancy in the volume, but this makes it clear.
Thanks,
Shibani
On 11 May 2016 at 17:24, William Gray<EMAIL_ADDRESS>wrote:

Cool - glad you found this! What brings you here?
We ran on an inscribed cube - basically we did our best to take the
largest cuboid that had data on all 1850 slices, which came out to about
60,000 um. If you need more (or the actual bounds), I can pull - just let
me know!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/neurodata/vesicle/issues/12#issuecomment-218594817

--
Shibani Santurkar| Graduate Student | Electrical Engineering and Computer
Science | MIT


Would like to use Hystrix with many independent deployments that have the same ApplicationContext.id, but this breaks the HystrixDashboard

In a nutshell, using Docker, for example, where our name, profile(s), and port are the same, when we try to use Hystrix & aggregate data through Turbine to display it to a Hystrix Dashboard, we get bad results due to the code in org.springframework.cloud.netflix.hystrix.stream.HystrixStreamTask
private void addServiceData(JsonGenerator json, ServiceInstance localService)
		throws IOException {
	json.writeObjectFieldStart("origin");
	json.writeStringField("host", localService.getHost());
	json.writeNumberField("port", localService.getPort());
	json.writeStringField("serviceId", localService.getServiceId());
	if (this.properties.isSendId()) {
		json.writeStringField("id", this.context.getId());
	}
	json.writeEndObject();
}

The 'id' field here ends up being the same for all deployments, yet it carries differing information payloads, and that messes up the aggration along the bus into Turbine & the Hystrix Dashboard.
Might I suggest making that a combination of the other three fields?
localService.serviceId:localService.Host:localService.Port?
Or, perhaps have a property that could be dropped in?

The id might be defaulting to something insufficiently unique in your environment, but it's really up to you to set it (e.g. with spring.application.index if you use the out of the box listeners). The default is controlled in ContextIdApplicationContextInitializer from Spring Boot.

The spring.application.index is definitely a step in the right direction, however with say, deployed Docker containers, how will be easily able to assign unique spring.application.index values?  This seems to be a bit of a managerial point of failure.

@TabberGit see #131 if you set hystrix.stream.amqp.send-id=false to allow disabling of sending the context id as the metric id, Turbine AMQP then defaults to serviceId:host:port. Probably not documented.

@spencergibb I see where you're going with this, but with the latest spring-cloud-netflix-hystrix-stream-1.1.0-BUILD-SNAPSHOT code, it seems to have no effect.  I've put the following into application.yml:
 hystrix:
   stream:
     amqp:
       send-id: false

Somehow, the metrics are still being sent along the same way as previously.  I'm guessing you have code somewhere to try and modify the conditional if(this.properties.isSendId()), however this still comes in as true.
If this conditional did cause the isSendId() to return false, it would result in the following json, correct:
 origin: {
   host: <host>
   port: <port>
   serviceId: <serviceId>
 }

which would be unique per Eureka registration.

Sorry, the property name changed when we moved to spring-cloud-stream. hystrix.stream.queue.send-id=false.

Spencer, first off, thank you.  This is exactly the info I needed.
One last question before we close this, I don't quite understand how send-id is mappable to the sendId field.  In those @ConfigurationProperties definitions, are dashes used as a replacement for camel casing the field names?

https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-relaxed-binding
So, can we close this?

Perfect.  Thank you.
Yes, close away.


Update UG

Partially addresses #187

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
see 51 files with indirect coverage changes


Reusing too old connection (ECONNRESET)

The issue actually occurred in https://github.com/windkh/node-red-contrib-telegrambot and has been reported in https://github.com/windkh/node-red-contrib-telegrambot/issues/172 but connection management is not actually done there, so I think the underlying problem is somewhere in here.
A while ago I noticed that messages were randomly not send out to Telegram, the error message is ECONNRESET.
I traced the problem with tcpdump and found the following sequence of events:

Message shall be send.
TCP connection is established.
Message is send.
Connection is not closed (probably to be reused).
Nothing happens for minutes to hours.
Next message shall be send.
Bot tries to reuse connection from step 2.
Telegram server thinks WTF? and resets the connection. Result is ECONNRESET.
Sending of message failed.

So I guess the problem is that telegram-bot-api tries to reuse a connection that may be hours old and which has been forgotten by the server for ages.
Either this needs to be changed to always (or at least if the old connection is too old) making a new connection or alternatively, sending must be retried at least one time after ECONNRESET.
Implementing keep-alive packages (if supported by Telegram) might also be a solution.

Some more information I learned from the package dump:
From what I can see, there are up to three connection active at the same time. Probably one polling connection for each of the two bots I'm running and one if messages are being sent to the bots.
Usually something will happen a couple of times per second, matching the default polling frequency of 300 ms.
But: Whenever the connection reset happens, all three connections have stopped transmitting data for something like 10 minutes or longer, sometimes hours. So I guess something somewhere went wrong and the polling stopped. Then, after a while, the Telegram server closes the connection, because they idled for too long.
If the telegram-bot-api then tries to send a message using the hours old connection, the server doesn't know where to put that and sends the reset.
But that means that the bot wouldn't be receiving messages for a while, anyway.
So I think I have to revert my analysis of the problem: It's not that sending reuses and old long-forgotten connection, but that a polling fault is not detected and the bot stays offline without anyone noticing. But it may be that the problem is in the Node-Red Bot part, which may ignore polling fault messages and fails to trigger a reconnection.
Who would you say should be responsible for detecting and correcting such a problem? The API or the code using the API?

Erm, sorry about the noise, I just found the documentation about reacting to polling errors.
From what I can see this should be done already in the code using the API, but maybe something is wrong there.
We'll come back when we know if the problem is in the user code or in the API.

OK, here we go again: We are by now quite sure that telegram-bot-api somehow misses the lost connection and never sends out the polling_error message.
Any hints how we best debug this?

any news about this?

Haven't been able to debug this any further, but it is still happening with node-red-contrib-telegrambot 9.4.3, which uses node-telegram-bot-api 0.52.0.
You can see the code that should handle the polling error here: https://github.com/windkh/node-red-contrib-telegrambot/blob/a771b3489fe83a1901cc0c84e18657aba1c497f2/telegrambot/99-telegrambot.js#L219
As far as I can see, this should be working, but apparently it's not, because there are no traces of it visible in the log files.
So my current conclusion is that the API for some reason never detects the polling error or never sends out the polling_error message. Then of course the node red bot never has a chance to do something.
If you have any ideas how to debug this any further, let me know and I'll give it a try.

What's the workaround for this? Is there a way to reestablish connection? I tried creating a new instance of bot every time I need it, but for some reason I still get this error after around 2 hours of it running.

I still see the problem every now and then:
7 Apr 04:42:58 - [warn] [telegram bot:be37e9ae.15b438] EFATAL: Error: read ECONNRESET
7 Apr 04:42:58 - [warn] [telegram bot:be37e9ae.15b438] Network connection may be down. Trying again.

But it doesn't seem to cause any problems anymore, at least I do not see any failed messages send.
Mostly the problem went away when I switched my podman containers to host-network. I had to do that for other reasons and I do not like it, but I did not find the time to fix it.
If you want to, you can try an automatic resending:
[
    {
        "id": "df053379.7f5398",
        "type": "telegram sender",
        "z": "43c781d9.ddbfa",
        "name": "",
        "bot": "be37e9ae.15b438",
        "haserroroutput": true,
        "outputs": 2,
        "x": 590,
        "y": 80,
        "wires": [
            [],
            [
                "82a4edf0.6199e8"
            ]
        ]
    },
    {
        "id": "4d842a0e.6df4c4",
        "type": "delay",
        "z": "43c781d9.ddbfa",
        "name": "",
        "pauseType": "rate",
        "timeout": "5",
        "timeoutUnits": "seconds",
        "rate": "1",
        "nbRateUnits": "5",
        "rateUnits": "second",
        "randomFirst": "1",
        "randomLast": "5",
        "randomUnits": "seconds",
        "drop": false,
        "outputs": 1,
        "x": 540,
        "y": 140,
        "wires": [
            [
                "df053379.7f5398"
            ]
        ]
    },
    {
        "id": "82a4edf0.6199e8",
        "type": "function",
        "z": "43c781d9.ddbfa",
        "name": "Retry",
        "func": "if( msg.error ) {\n    if( msg.error.includes( \"ECONNRESET\" ) ) {\n        if( msg.retries ) {\n            if( msg.retries > 3 ) {\n                msg.my_error = \"ECONNRESET, but retries > 3, so not retrying.\";\n                return [ null, msg ];\n            }\n            else {\n                msg.retries++;\n                msg.my_error = \"ECONNRESET, retrying...\";\n                msg_retry = RED.util.cloneMessage( msg );\n                delete msg_retry.error;\n                return [ msg_retry, msg ];\n            }\n        }\n        else {\n            msg.retries = 1;\n            msg.my_error = \"ECONNRESET, retrying...\";\n            msg_retry = RED.util.cloneMessage( msg );\n            delete msg_retry.error;\n            return [ msg_retry, msg ];\n        }\n    }\n    else {\n        msg.my_error = \"Other error.\";\n        return [ null, msg ];\n    }\n}\nelse {\n    msg.my_error = \"Telegram sent failed, but no error message.\";\n    return [ null, msg ];\n}\n",
        "outputs": 2,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "x": 770,
        "y": 200,
        "wires": [
            [
                "4d842a0e.6df4c4"
            ],
            [
                "edef2391.a6805"
            ]
        ]
    },
    {
        "id": "be37e9ae.15b438",
        "type": "telegram bot",
        "botname": "XXX",
        "usernames": "",
        "chatids": "",
        "baseapiurl": "",
        "updatemode": "polling",
        "pollinterval": "300",
        "usesocks": false,
        "sockshost": "",
        "socksport": "6667",
        "socksusername": "anonymous",
        "sockspassword": "",
        "bothost": "",
        "botpath": "",
        "localbotport": "8443",
        "publicbotport": "8443",
        "privatekey": "",
        "certificate": "",
        "useselfsignedcertificate": false,
        "sslterminated": false,
        "verboselogging": true
    }
]

7 Apr 04:42:58 - [warn] [telegram bot:be37e9ae.15b438] EFATAL: Error: read ECONNRESET
7 Apr 04:42:58 - [warn] [telegram bot:be37e9ae.15b438] Network connection may be down. Trying again.

I'm getting the same above error. In our country telegram is ban and I also attach vpn but still getting this error how to resolve? If any can solve please lemme know....
Here is the code:
const TelegramBot = require("node-telegram-bot-api");
const token = "7533601475:AAHy4ZqEoWpS3vKhryZRh7wtAdZ0tRlxIQ0";
const bot = new TelegramBot(token, { polling: true });
bot.on("message", (msg) => {
const chatId = msg.chat.id;
const messageText = msg.text;
if (messageText === "/start") {
bot.sendMessage(chatId, "Welcome to the bot!");
}
});
here is the error:
error: [polling_error] {"code":"EFATAL","message":"EFATAL: Error: read ECONNRESET"}


mlkem pk validation

pk validation for ml-kem
kem API cleanup (move encaps and decaps functions into public key and ciphertext)
ml-kem rename
fixed fuzzers

Do we still leave the folder name and file names as kyber* ?

I'd prefer renaming, but felt like it would make things harder than necessary right now for the proofs.

There is a weird structure in the current code, where the IND-CCA code is in kyber.rs and is one folder up from the rest of the code, and this file is then called within the 3 kyber instances. It would be better to have an indcca.rs file within the kem/kyber/ folder and have the current kyber.rs act as a wrapper for the three instances?

That's been an open issue for a while. We didn't do it because of the proofs. The correct structure would be to have an empty kyber module and everything in the kyber directory, or the three variants in the kyber module and everything else below.
I'm fine either way.


Addition

Installing VIB on ESXi 5.5 generates the error: VIB VMWare_bootbank_esx-vmdkops-service_0.14.0577889-0.0.1 requires esx-version >= 6.0.0
However, this version requirement isnt documented. Just like he Docker version is called out, it would be beneficial to call out that the ESXi version should be 6.0 or higher.

Good catch. Looks like README calls out ESX versions but documentation doesn't.
@shuklanirdesh82 Should ESX and Docker version be part of prerequisite.md

Should ESX and Docker version be part of prerequisite.md

Yeah, I will add such information. Thanks @nnf97 for catching!

Right. I saw that on the readme. However, it phrases it as 'tested on', which to my mind means, it is possible that this thing will work on other versions, but no one had the time or resources to actually test it on the other versions.
The error message clearly says it should be ESXi 6.0 as the  lowest version.
I will update the readme as well to indicate that 6.0 and up is a 'requirement', if you don't mind.
On Jun 12, 2017, at 5:28 PM, Prashant Dhamdhere <notifications<EMAIL_ADDRESS>wrote:
Good catch. Looks like READMEhttps://github.com/vmware/docker-volume-vsphere/blob/master/README.md calls out ESX versions but documentation doesn't.
@shuklanirdesh82https://github.com/shuklanirdesh82 Should ESX and Docker version be part of prerequisite.mdhttps://github.com/vmware/docker-volume-vsphere/edit/gh-pages/jekyll-docs//prerequisite.md
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vmware/docker-volume-vsphere/pull/1392#issuecomment-307934561, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFDVaD9p2Rz-mt9_MIfSotKzkzo8vy9mks5sDa2LgaJpZM4N3X2N.

@nnf97 Correct. Anything below ESXi 6.0 is not supported.

I will update the readme as well to indicate that 6.0 and up is a 'requirement', if you don't mind.

Sure thing and thanks in advance,


Add size interface to list

This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[ ] #patch# - backwards-compatible bug fix
[x] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Removed default value for defaultHeight property.
Updated smoke-and-mirror to consume listRowHeight instead of defaultHeight.
Updated frost-checkbox in frost-list-item-section, now it reacts to size.
Updated frost-list-item-container-base to generate its height based on listRowHeight.
Added new interface size that defaults to medium.
Added new computed property listRowHeight calculates based on defaultHeight and size.

Changes Unknown when pulling e1a3b357bf1b7a49d2ba5702463e1bf0b2943a2e on quincyle:small-view into ** on ciena-frost:master**.

Changes Unknown when pulling 84ccd52c5bafe328ed9c2c99cff5b01c9d43f4db on quincyle:small-view into ** on ciena-frost:master**.

👍

Changes Unknown when pulling 681614b421bb411a709943708632d3b638c8d623 on quincyle:small-view into ** on ciena-frost:master**.

Changes Unknown when pulling 681614b421bb411a709943708632d3b638c8d623 on quincyle:small-view into ** on ciena-frost:master**.

@notmessenger Appreciate for the fast review.


Parameter Select issue with mouse movement

To help us understand your issue, please specify important details, primarily:

NeoDash version: 2.4.2

Neo4j Database version: 5.12 (Enterprise)

Steps to reproduce
We have a Parameter Select report that sets a property given a specific node label, and the property which is an integer (not sure if that's the key to the issue or not)

This works as expected so long as we're really careful about changing the integer after one has already been entered.
If we're a little sloppy with the mouse though and highlight the numbers (possibly making the UI think we're moving the numbers), the Report fails with the error:
An unexpected error occurred. Try refreshing the component.
TypeError: s.toLowerCase is not a function
    at https://your.url.here/bundle.js:2:9596913
    at v (https://your.url.here/bundle.js:2:9598851)
    at https://your.url.here/bundle.js:2:9619699
    at ti (https://your.url.here/bundle.js:152:1553619)
    at Ni (https://your.url.here/bundle.js:152:1561763)
    at Hl (https://your.url.here/bundle.js:152:1607754)
    at Ec (https://your.url.here/bundle.js:152:1592991)
    at _c (https://your.url.here/bundle.js:152:1592919)
    at wc (https://your.url.here/bundle.js:152:1592782)
    at hc (https://your.url.here/bundle.js:152:1589769)

This requires logging out and back in to the dashboard to make the Parameter Select report usable again.

Thank you for your feedback, it will be out in the next release.

Could you check that it works now?

Alfredo,
Apologies for the delay in getting back, what version is this fixed in?  We're still on 2.4.3 because of SSO auth issues with 2.4.4.
Thanks!

It should've been fixed in 2.4.4, could you please check? If you get the same bug, please share a screen share and the dashboard json if possible.

Alfredo,
Apologies, we can't check, as we're still on 2.4.3 because of SSO auth issues with 2.4.4.

Alfredo, just moved to 2.4.4 and can validate that this bug has been squashed.  Thank you!


Transpiled async generators don't unwrap returned promise values

cc @rbuckton
TypeScript Version:  2.9.0-dev.20180515

Search Terms:
Code
await (async function* () { return Promise.resolve(0); })().next()
// also should be covered by tests
await (async function* () { return Promise.reject(1); })().next()

Expected behavior:
Object{value: 0, done: true}
Actual behavior:
Object{value: Promise{}, done: true}
Playground Link:
Related Issues:

@rbuckton ?


as set of utility functions for lowdb,  extending notation

You have a bunch of useful (and well documented) repos! super thx.
If you had a little example code in the docs showing how to add them to lowdb at over 35K stars you'd get more exposure.  Maybe they'd even take a PR as an included set of utility functions, although a few duplicate stuff in underscore.   Still I might just drop lowdb and use notation since I'll probably do my own read/writes.
Is there a supported way to extend notation like with lowdb?
db._

Database lodash instance. Use it to add your own utility functions or third-party mixins like underscore-contrib or underscore-db.

db._.mixin({
  second: function(array) {
    return array[1]
  }
})

const post1 = db.get('posts').first().value()
const post2 = db.get('posts').second().value()

Thanks. I've never used lowdb - seems promising though.
Notation takes an object. Lowdb (db methods in general) work with arrays (i.e. result-sets). So this needs to be considered.
I think you can mix notation in like below:
db._.mixin({
  notateFirst: function (array) {
    var first = array[0].value();
    return (new Notation(first)).clone();
  }
})

Then you can do:
const notation1 = db.get('posts').notateFirst();
notation1
    .merge({ 'my.newProp': 'here' })
    .remove('deep.down.prop')
    .value; // modified post value

Actually you wouldn't even need this. Just use the result object and init a Notation from that.
const post1 = db.get('posts').first().value();
const notation1 = Notation.create(post1)
    .clone()
    .merge({ 'my.newProp': 'here' })
    .remove('deep.down.prop')
    .value;

Notation will/should not support mixins. It's not a (multi-goal) tool-belt. Rather, it's a goal-specific tool which needs to be improved with a clean roadmap.
What is the feature you need, that Notation does not have already?
Thanks for the input.


Release workflow for monorepo

Description
Setup Release Please Github workflow for automating changelogs,
versioning and releases for the apps and components in this repo.
In order for this to work, all commits need to be in conventional commits style.
After a PR with changes is merged to master, the workflow will detect changes and create a "Release PR" with the changes related to the app/component. These Release PR's will accumulate changes and update their versions until they're merged. After merging, the Release PR will create a version tag, which should trigger a release action just like creating a tag manually and pushing would. Tags are prefixed with the component name, as defined in the package.json.
This is just the basic setup and might need some tweaking still.
Issues
Closes
HH-280:
Related
Testing
Automated tests
Manual testing
Screenshots
Additional notes

Codecov Report

Merging #139 (5732776) into main (3152959) will decrease coverage by 9.91%.
 Consider uploading reports for the commit 9dbd8a1 to get more accurate results

@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
- Coverage   57.12%   47.21%   -9.92%
==========================================
  Files         269      170      -99
  Lines        6316     3768    -2548
  Branches     1434      861     -573
==========================================
- Hits         3608     1779    -1829
+ Misses       2566     1903     -663
+ Partials      142       86      -56

Impacted Files
Coverage Δ

apps/sports-helsinki/src/assets/icons/IconArt.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

apps/sports-helsinki/src/assets/icons/IconFood.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

apps/sports-helsinki/src/assets/icons/IconRead.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...pps/sports-helsinki/src/assets/icons/IconCraft.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...pps/sports-helsinki/src/assets/icons/IconDance.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...pps/sports-helsinki/src/assets/icons/IconGames.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...pps/sports-helsinki/src/assets/icons/IconMusic.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...ps/sports-helsinki/src/assets/icons/IconMovies.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...s/sports-helsinki/src/assets/icons/IconTheatre.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...sports-helsinki/src/assets/icons/IconLanguages.tsx
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 125 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Here's a test run, how it would now generate PR's:
1.1.0 (2023-01-10)
Features

Add favicon to article archive (#127) (04d95d5)
Enable HDS server side rendering support (932e980)
Grey placeholders in form components (#128) (6b95e83)
hobbies: Remove search link and categories from footer (b3b0681)
Use the prefetched menus and languages as navigation and footer props (48e80f9)

Bug Fixes

Add event translations to the article page (#105) (8a21149)
Archive page style fixes (#124) (b96c067)
Check install issues (62ee14b)
cms-pages: The collection of the static page paths (3345627)
Integrity and code quality issues (8b489cb)
Large card mobile view new hcrc version (#104) (33a0f09)
Linter issues (8b489cb)
Page link URLs (8b0ccd5)
Stylings of input outlines (#121) (cbdf04e)
Typecheck issues (8b489cb)
Ui bugs archive page (#132) (5e20c09)
Ui style fixes carousel and cards (#116) (19e111c)

This PR was generated with Release Please. See documentation.
updates: 6
❯ Fetching apps/hobbies-helsinki/package-lock.json from branch hh-280-changelogs
⚠ file apps/hobbies-helsinki/package-lock.json did not exist
❯ Fetching apps/hobbies-helsinki/npm-shrinkwrap.json from branch hh-280-changelogs
⚠ file apps/hobbies-helsinki/npm-shrinkwrap.json did not exist
❯ Fetching apps/hobbies-helsinki/samples/package.json from branch hh-280-changelogs
⚠ file apps/hobbies-helsinki/samples/package.json did not exist
❯ Fetching apps/hobbies-helsinki/CHANGELOG.md from branch hh-280-changelogs
❯ Fetching apps/hobbies-helsinki/package.json from branch hh-280-changelogs
✔ updating from 1.0.0 to 1.1.0
❯ Fetching .release-please-manifest.json from branch hh-280-changelogs
apps/hobbies-helsinki/package-lock.json:  [class PackageLockJson extends DefaultUpdater]
apps/hobbies-helsinki/npm-shrinkwrap.json:  [class PackageLockJson extends DefaultUpdater]
apps/hobbies-helsinki/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
apps/hobbies-helsinki/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
apps/hobbies-helsinki/package.json:  [class PackageJson extends DefaultUpdater]
.release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
title: chore(hh-280-changelogs): release events-helsinki 0.4.0
branch: release-please--branches--hh-280-changelogs--components--events-helsinki
draft: false
body: :robot: I have created a release beep boop
0.4.0 (2023-01-10)
Features

Add favicon to article archive (#127) (04d95d5)
Change default search results order for events (#115) (fc78c84)
Enable HDS server side rendering support (932e980)
events: Tune landing page category search shortcuts (e2b0d1b)
Grey placeholders in form components (#128) (6b95e83)
Only kids events search filter (#129) (ed22030)
Use the prefetched menus and languages as navigation and footer props (48e80f9)

Bug Fixes

Add event translations to the article page (#105) (8a21149)
Archive page button border (#136) (3152959)
Archive page style fixes (#124) (b96c067)
Button style for sports and events (#134) (912fb8c)
Check install issues (62ee14b)
cms-pages: The collection of the static page paths (3345627)
Integrity and code quality issues (8b489cb)
Large card mobile view new hcrc version (#104) (33a0f09)
Linter issues (8b489cb)
Page link URLs (8b0ccd5)
Remove link and categories from footer (#130) (b482f31)
Stylings of input outlines (#121) (cbdf04e)
Typecheck issues (8b489cb)
Ui bugs archive page (#132) (5e20c09)
Ui style fixes carousel and cards (#116) (19e111c)

This PR was generated with Release Please. See documentation.
updates: 6
❯ Fetching apps/events-helsinki/package-lock.json from branch hh-280-changelogs
⚠ file apps/events-helsinki/package-lock.json did not exist
❯ Fetching apps/events-helsinki/npm-shrinkwrap.json from branch hh-280-changelogs
⚠ file apps/events-helsinki/npm-shrinkwrap.json did not exist
❯ Fetching apps/events-helsinki/samples/package.json from branch hh-280-changelogs
⚠ file apps/events-helsinki/samples/package.json did not exist
❯ Fetching apps/events-helsinki/CHANGELOG.md from branch hh-280-changelogs
❯ Fetching apps/events-helsinki/package.json from branch hh-280-changelogs
✔ updating from 0.3.0 to 0.4.0
❯ Fetching .release-please-manifest.json from branch hh-280-changelogs
apps/events-helsinki/package-lock.json:  [class PackageLockJson extends DefaultUpdater]
apps/events-helsinki/npm-shrinkwrap.json:  [class PackageLockJson extends DefaultUpdater]
apps/events-helsinki/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
apps/events-helsinki/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
apps/events-helsinki/package.json:  [class PackageJson extends DefaultUpdater]
.release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
title: chore(hh-280-changelogs): release sports-helsinki 0.4.0
branch: release-please--branches--hh-280-changelogs--components--sports-helsinki
draft: false
body: :robot: I have created a release beep boop
0.4.0 (2023-01-10)
Features

Add a context and a provider for navigation component (df9e968)
Add favicon to article archive (#127) (04d95d5)
Enable HDS server side rendering support (932e980)
Give a menu as a prop into the Navigation component (b35793b)
Grey placeholders in form components (#128) (6b95e83)
Include a header menu query in the global CMS data (0427b6f)
sports: Add the subgraph support (1058afd)
sports: Added venue translations (a998ce7)
sports: Graphql next api apollo server (c0c066d)
sports: Make search shortcuts change automatically based on season (54de034)
sports: Map search page and a map view component (e815b74)
sports: Search utilities for search mode switching (3742500)
sports: Service map component for events and venues (94eef90)
sports: Switch landing search shortcuts to Liikunta ones (b157929)
Use the prefetched menus and languages as navigation and footer props (48e80f9)

Bug Fixes

Add event translations to the article page (#105) (8a21149)
Archive page button border (#136) (3152959)
Archive page style fixes (#124) (b96c067)
Button style for sports and events (#134) (912fb8c)
Check install issues (62ee14b)
cms-pages: The collection of the static page paths (3345627)
Deactivate the show map -link in the large venue card (44d7579)
Integrity and code quality issues (8b489cb)
Large card mobile view new hcrc version (#104) (33a0f09)
Linter issues (8b489cb)
Page link URLs (8b0ccd5)
Remove link and categories from footer (#130) (b482f31)
Stylings of input outlines (#121) (cbdf04e)
Typecheck issues (8b489cb)
Ui bugs archive page (#132) (5e20c09)
Ui style fixes carousel and cards (#116) (19e111c)
Venues search variables (#106) (a31de0d)

This PR was generated with Release Please. See documentation.
updates: 6
❯ Fetching apps/sports-helsinki/package-lock.json from branch hh-280-changelogs
⚠ file apps/sports-helsinki/package-lock.json did not exist
❯ Fetching apps/sports-helsinki/npm-shrinkwrap.json from branch hh-280-changelogs
⚠ file apps/sports-helsinki/npm-shrinkwrap.json did not exist
❯ Fetching apps/sports-helsinki/samples/package.json from branch hh-280-changelogs
⚠ file apps/sports-helsinki/samples/package.json did not exist
❯ Fetching apps/sports-helsinki/CHANGELOG.md from branch hh-280-changelogs
❯ Fetching apps/sports-helsinki/package.json from branch hh-280-changelogs
✔ updating from 0.3.0 to 0.4.0
❯ Fetching .release-please-manifest.json from branch hh-280-changelogs
apps/sports-helsinki/package-lock.json:  [class PackageLockJson extends DefaultUpdater]
apps/sports-helsinki/npm-shrinkwrap.json:  [class PackageLockJson extends DefaultUpdater]
apps/sports-helsinki/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
apps/sports-helsinki/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
apps/sports-helsinki/package.json:  [class PackageJson extends DefaultUpdater]
.release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
title: chore(hh-280-changelogs): release events-helsinki-components 0.1.0
branch: release-please--branches--hh-280-changelogs--components--events-helsinki-components
draft: false
body: :robot: I have created a release beep boop
0.1.0 (2023-01-10)
Features

Add favicon to article archive (#127) (04d95d5)
Enable HDS server side rendering support (932e980)
Grey placeholders in form components (#128) (6b95e83)
sports: Added venue translations (a998ce7)
sports: Graphql next api apollo server (c0c066d)
sports: Map search page and a map view component (e815b74)
sports: Service map component for events and venues (94eef90)

Bug Fixes

Archive page style fixes (#124) (b96c067)
Check install issues (62ee14b)
Integrity and code quality issues (8b489cb)
Large card mobile view new hcrc version (#104) (33a0f09)
Linter issues (8b489cb)
Stylings of input outlines (#121) (cbdf04e)
Typecheck issues (8b489cb)
Ui bugs archive page (#132) (5e20c09)
Ui style fixes carousel and cards (#116) (19e111c)
Visible component fix breakpoint class names (#114) (81ade63)

This PR was generated with Release Please. See documentation.
updates: 6
❯ Fetching packages/components/package-lock.json from branch hh-280-changelogs
✔ updating from 0.0.7 to 0.1.0
❯ Fetching packages/components/npm-shrinkwrap.json from branch hh-280-changelogs
⚠ file packages/components/npm-shrinkwrap.json did not exist
❯ Fetching packages/components/samples/package.json from branch hh-280-changelogs
⚠ file packages/components/samples/package.json did not exist
❯ Fetching packages/components/CHANGELOG.md from branch hh-280-changelogs
❯ Fetching packages/components/package.json from branch hh-280-changelogs
✔ updating from 0.0.7 to 0.1.0
❯ Fetching .release-please-manifest.json from branch hh-280-changelogs
packages/components/package-lock.json:  [class PackageLockJson extends DefaultUpdater]
packages/components/npm-shrinkwrap.json:  [class PackageLockJson extends DefaultUpdater]
packages/components/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
packages/components/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
packages/components/package.json:  [class PackageJson extends DefaultUpdater]
.release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
title: chore(hh-280-changelogs): release events-helsinki-common-i18n 0.1.0
branch: release-please--branches--hh-280-changelogs--components--events-helsinki-common-i18n
draft: false
body: :robot: I have created a release beep boop
0.1.0 (2023-01-10)
Features

Add favicon to article archive (#127) (04d95d5)
hobbies: Remove search link and categories from footer (b3b0681)
sports: Added venue translations (a998ce7)
sports: Make search shortcuts change automatically based on season (54de034)
sports: Map search page and a map view component (e815b74)
sports: Search utilities for search mode switching (3742500)
sports: Service map component for events and venues (94eef90)
sports: Switch landing search shortcuts to Liikunta ones (b157929)

Bug Fixes

Integrity and code quality issues (8b489cb)
Linter issues (8b489cb)
Remove link and categories from footer (#130) (b482f31)
Typecheck issues (8b489cb)

This PR was generated with Release Please. See documentation.
updates: 6
❯ Fetching packages/common-i18n/package-lock.json from branch hh-280-changelogs
⚠ file packages/common-i18n/package-lock.json did not exist
❯ Fetching packages/common-i18n/npm-shrinkwrap.json from branch hh-280-changelogs
⚠ file packages/common-i18n/npm-shrinkwrap.json did not exist
❯ Fetching packages/common-i18n/samples/package.json from branch hh-280-changelogs
⚠ file packages/common-i18n/samples/package.json did not exist
❯ Fetching packages/common-i18n/CHANGELOG.md from branch hh-280-changelogs
❯ Fetching packages/common-i18n/package.json from branch hh-280-changelogs
✔ updating from 0.0.1 to 0.1.0
❯ Fetching .release-please-manifest.json from branch hh-280-changelogs
packages/common-i18n/package-lock.json:  [class PackageLockJson extends DefaultUpdater]
packages/common-i18n/npm-shrinkwrap.json:  [class PackageLockJson extends DefaultUpdater]
packages/common-i18n/samples/package.json:  [class SamplesPackageJson extends DefaultUpdater]
packages/common-i18n/CHANGELOG.md:  [class Changelog extends DefaultUpdater]
packages/common-i18n/package.json:  [class PackageJson extends DefaultUpdater]
.release-please-manifest.json:  [class ReleasePleaseManifest extends DefaultUpdater]
title: chore(hh-280-changelogs): release federation-router 1.1.0
branch: release-please--branches--hh-280-changelogs--components--federation-router
draft: false
body: :robot: I have created a release beep boop
1.1.0 (2023-01-10)
Features

router: Compose a new supergraph with venues schema and Tprek datasource (33dc2f9)
router: Propagate the headers from the requests (d28724e)
router: Venues subgraph added to the federation router (03dcb61)

This PR was generated with Release Please. See documentation.
updates: 4