Infinite Loop when trying to build project

Step 3:
This project uses inject library that works with code generation, execute the following command to generate files:
flutter packages pub run build_runner build --delete-conflicting-outputs
or watch command in order to keep the source code synced automatically:
flutter packages pub run build_runner watch

This step is never completing it seems.
> flutter packages pub run build_runner build --delete-conflicting-outputs
[INFO] Generating build script...
[INFO] Generating build script completed, took 370ms

[WARNING] Deleted previous snapshot due to missing asset graph.
[INFO] Creating build script snapshot......
[INFO] Creating build script snapshot... completed, took 11.6s

[INFO] Initializing inputs
[INFO] Building new asset graph...
[INFO] Building new asset graph completed, took 998ms

[INFO] Checking for unexpected pre-existing outputs....
[INFO] Deleting 3 declared outputs which already existed on disk.
[INFO] Checking for unexpected pre-existing outputs. completed, took 5ms

[INFO] Running build...
[INFO] inject_generator:inject_generator on test/widget_test.dart:Generating DI summary for boilerplate|test/widget_test.dart
[INFO] inject_generator:inject_generator on test/widget_test.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/app_theme.dart:Generating DI summary for boilerplate|lib/constants/app_theme.dart
[INFO] inject_generator:inject_generator on lib/constants/app_theme.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/assets.dart:Generating DI summary for boilerplate|lib/constants/assets.dart
[INFO] inject_generator:inject_generator on lib/constants/assets.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/colors.dart:Generating DI summary for boilerplate|lib/constants/colors.dart
[INFO] inject_generator:inject_generator on lib/constants/colors.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/dimens.dart:Generating DI summary for boilerplate|lib/constants/dimens.dart
[INFO] inject_generator:inject_generator on lib/constants/dimens.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/font_family.dart:Generating DI summary for boilerplate|lib/constants/font_family.dart
[INFO] inject_generator:inject_generator on lib/constants/font_family.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/strings.dart:Generating DI summary for boilerplate|lib/constants/strings.dart
[INFO] inject_generator:inject_generator on lib/constants/strings.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/local/constants/db_constants.dart:Generating DI summary for boilerplate|lib/data/local/constants/db_constants.dart
[INFO] inject_generator:inject_generator on lib/data/local/constants/db_constants.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/local/datasources/post/post_datasource.dart:Generating DI summary for boilerplate|lib/data/local/datasources/post/post_datasource.dart
[INFO] inject_generator:inject_generator on lib/data/local/datasources/post/post_datasource.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/apis/posts/post_api.dart:Generating DI summary for boilerplate|lib/data/network/apis/posts/post_api.dart
[INFO] inject_generator:inject_generator on lib/data/network/apis/posts/post_api.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/constants/endpoints.dart:Generating DI summary for boilerplate|lib/data/network/constants/endpoints.dart
[INFO] inject_generator:inject_generator on lib/data/network/constants/endpoints.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/dio_client.dart:Generating DI summary for boilerplate|lib/data/network/dio_client.dart
[INFO] inject_generator:inject_generator on lib/data/network/dio_client.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/exceptions/network_exceptions.dart:Generating DI summary for boilerplate|lib/data/network/exceptions/network_exceptions.dart
[INFO] inject_generator:inject_generator on lib/data/network/exceptions/network_exceptions.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/rest_client.dart:Generating DI summary for boilerplate|lib/data/network/rest_client.dart
[INFO] inject_generator:inject_generator on lib/data/network/rest_client.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/repository.dart:Generating DI summary for boilerplate|lib/data/repository.dart
[INFO] inject_generator:inject_generator on lib/data/repository.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/sharedpref/constants/preferences.dart:Generating DI summary for boilerplate|lib/data/sharedpref/constants/preferences.dart
[INFO] inject_generator:inject_generator on lib/data/sharedpref/constants/preferences.dart:After resolve
[INFO] Generating SDK summary...
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[INFO] inject_generator:inject_generator on lib/data/sharedpref/shared_preference_helper.dart:Generating DI summary for boilerplate|lib/data/sharedpref/shared_preference_helper.dart
[INFO] inject_generator:inject_generator on lib/data/sharedpref/shared_preference_helper.dart:After resolve
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:

Bad state: Future already completed
[INFO] 2.5s elapsed, 1/17 actions completed.
[INFO] 3.6s elapsed, 1/17 actions completed.
[INFO] 4.6s elapsed, 1/17 actions completed.
[INFO] 5.6s elapsed, 1/17 actions completed.
[INFO] 6.7s elapsed, 1/17 actions completed.
[INFO] 7.8s elapsed, 1/17 actions completed.
[INFO] 8.9s elapsed, 1/17 actions completed.
[INFO] 10.0s elapsed, 1/17 actions completed.
[INFO] 11.0s elapsed, 1/17 actions completed.
[INFO] 12.0s elapsed, 1/17 actions completed.
[INFO] 13.1s elapsed, 1/17 actions completed.
[INFO] 14.2s elapsed, 1/17 actions completed.
[INFO] 15.2s elapsed, 1/17 actions completed.
[INFO] 16.3s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.1s, waiting on:
  - inject_generator:inject_generator on lib/constants/app_theme.dart
  - inject_generator:inject_generator on lib/constants/assets.dart
  - inject_generator:inject_generator on lib/constants/colors.dart
  - inject_generator:inject_generator on lib/constants/dimens.dart
  - inject_generator:inject_generator on lib/constants/font_family.dart
  .. and 11 more

[INFO] 17.6s elapsed, 1/17 actions completed.
[INFO] 18.7s elapsed, 1/17 actions completed.
[INFO] 19.7s elapsed, 1/17 actions completed.
[INFO] 20.8s elapsed, 1/17 actions completed.
[INFO] 21.9s elapsed, 1/17 actions completed.
[INFO] 23.0s elapsed, 1/17 actions completed.
[INFO] 24.0s elapsed, 1/17 actions completed.
[INFO] 25.0s elapsed, 1/17 actions completed.
[INFO] 26.1s elapsed, 1/17 actions completed.
[INFO] 27.2s elapsed, 1/17 actions completed.
[INFO] 28.2s elapsed, 1/17 actions completed.
[INFO] 29.3s elapsed, 1/17 actions completed.
[INFO] 30.4s elapsed, 1/17 actions completed.
[INFO] 31.4s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.1s, waiting on:
  - inject_generator:inject_generator on lib/constants/app_theme.dart
  - inject_generator:inject_generator on lib/constants/assets.dart
  - inject_generator:inject_generator on lib/constants/colors.dart
  - inject_generator:inject_generator on lib/constants/dimens.dart
  - inject_generator:inject_generator on lib/constants/font_family.dart
  .. and 11 more

[INFO] 32.7s elapsed, 1/17 actions completed.
[INFO] 33.8s elapsed, 1/17 actions completed.
[INFO] 34.9s elapsed, 1/17 actions completed.
[INFO] 36.0s elapsed, 1/17 actions completed.
[INFO] 37.1s elapsed, 1/17 actions completed.
[INFO] 38.1s elapsed, 1/17 actions completed.
[INFO] 39.2s elapsed, 1/17 actions completed.
[INFO] 40.3s elapsed, 1/17 actions completed.
[INFO] 41.4s elapsed, 1/17 actions completed.
[INFO] 42.5s elapsed, 1/17 actions completed.
[INFO] 43.6s elapsed, 1/17 actions completed.
[INFO] 44.7s elapsed, 1/17 actions completed.
[INFO] 45.7s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.0s, waiting on:
  - inject_generator:inject_generator on lib/constants/app_theme.dart
  - inject_generator:inject_generator on lib/constants/assets.dart
  - inject_generator:inject_generator on lib/constants/colors.dart
  - inject_generator:inject_generator on lib/constants/dimens.dart
  - inject_generator:inject_generator on lib/constants/font_family.dart
  .. and 11 more

[INFO] 47.7s elapsed, 1/17 actions completed.
[INFO] 48.8s elapsed, 1/17 actions completed.
[INFO] 49.9s elapsed, 1/17 actions completed.
[INFO] 51.0s elapsed, 1/17 actions completed.
[INFO] 52.0s elapsed, 1/17 actions completed.
[INFO] 53.0s elapsed, 1/17 actions completed.
[INFO] 54.1s elapsed, 1/17 actions completed.

Thank you

من: Marcus<EMAIL_ADDRESS>تم الإرسال: 19/ذو الحجة/1441 10:01 م
إلى: zubairehman/flutter-boilerplate-project<EMAIL_ADDRESS>نسخة: simsimatoo<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>الموضوع: Re: [zubairehman/flutter-boilerplate-project] flutter-boilerplate-project (#68)
This step is never completing it seems.

flutter packages pub run build_runner build --delete-conflicting-outputs
[INFO] Generating build script...
[INFO] Generating build script completed, took 370ms

[WARNING] Deleted previous snapshot due to missing asset graph.
[INFO] Creating build script snapshot......
[INFO] Creating build script snapshot... completed, took 11.6s
[INFO] Initializing inputs
[INFO] Building new asset graph...
[INFO] Building new asset graph completed, took 998ms
[INFO] Checking for unexpected pre-existing outputs....
[INFO] Deleting 3 declared outputs which already existed on disk.
[INFO] Checking for unexpected pre-existing outputs. completed, took 5ms
[INFO] Running build...
[INFO] inject_generator:inject_generator on test/widget_test.dart:Generating DI summary for boilerplate|test/widget_test.dart
[INFO] inject_generator:inject_generator on test/widget_test.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/app_theme.dart:Generating DI summary for boilerplate|lib/constants/app_theme.dart
[INFO] inject_generator:inject_generator on lib/constants/app_theme.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/assets.dart:Generating DI summary for boilerplate|lib/constants/assets.dart
[INFO] inject_generator:inject_generator on lib/constants/assets.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/colors.dart:Generating DI summary for boilerplate|lib/constants/colors.dart
[INFO] inject_generator:inject_generator on lib/constants/colors.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/dimens.dart:Generating DI summary for boilerplate|lib/constants/dimens.dart
[INFO] inject_generator:inject_generator on lib/constants/dimens.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/font_family.dart:Generating DI summary for boilerplate|lib/constants/font_family.dart
[INFO] inject_generator:inject_generator on lib/constants/font_family.dart:After resolve
[INFO] inject_generator:inject_generator on lib/constants/strings.dart:Generating DI summary for boilerplate|lib/constants/strings.dart
[INFO] inject_generator:inject_generator on lib/constants/strings.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/local/constants/db_constants.dart:Generating DI summary for boilerplate|lib/data/local/constants/db_constants.dart
[INFO] inject_generator:inject_generator on lib/data/local/constants/db_constants.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/local/datasources/post/post_datasource.dart:Generating DI summary for boilerplate|lib/data/local/datasources/post/post_datasource.dart
[INFO] inject_generator:inject_generator on lib/data/local/datasources/post/post_datasource.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/apis/posts/post_api.dart:Generating DI summary for boilerplate|lib/data/network/apis/posts/post_api.dart
[INFO] inject_generator:inject_generator on lib/data/network/apis/posts/post_api.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/constants/endpoints.dart:Generating DI summary for boilerplate|lib/data/network/constants/endpoints.dart
[INFO] inject_generator:inject_generator on lib/data/network/constants/endpoints.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/dio_client.dart:Generating DI summary for boilerplate|lib/data/network/dio_client.dart
[INFO] inject_generator:inject_generator on lib/data/network/dio_client.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/exceptions/network_exceptions.dart:Generating DI summary for boilerplate|lib/data/network/exceptions/network_exceptions.dart
[INFO] inject_generator:inject_generator on lib/data/network/exceptions/network_exceptions.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/network/rest_client.dart:Generating DI summary for boilerplate|lib/data/network/rest_client.dart
[INFO] inject_generator:inject_generator on lib/data/network/rest_client.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/repository.dart:Generating DI summary for boilerplate|lib/data/repository.dart
[INFO] inject_generator:inject_generator on lib/data/repository.dart:After resolve
[INFO] inject_generator:inject_generator on lib/data/sharedpref/constants/preferences.dart:Generating DI summary for boilerplate|lib/data/sharedpref/constants/preferences.dart
[INFO] inject_generator:inject_generator on lib/data/sharedpref/constants/preferences.dart:After resolve
[INFO] Generating SDK summary...
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[INFO] inject_generator:inject_generator on lib/data/sharedpref/shared_preference_helper.dart:Generating DI summary for boilerplate|lib/data/sharedpref/shared_preference_helper.dart
[INFO] inject_generator:inject_generator on lib/data/sharedpref/shared_preference_helper.dart:After resolve
[SEVERE] inject_generator:inject_generator on test/widget_test.dart:
Bad state: Future already completed
[INFO] 2.5s elapsed, 1/17 actions completed.
[INFO] 3.6s elapsed, 1/17 actions completed.
[INFO] 4.6s elapsed, 1/17 actions completed.
[INFO] 5.6s elapsed, 1/17 actions completed.
[INFO] 6.7s elapsed, 1/17 actions completed.
[INFO] 7.8s elapsed, 1/17 actions completed.
[INFO] 8.9s elapsed, 1/17 actions completed.
[INFO] 10.0s elapsed, 1/17 actions completed.
[INFO] 11.0s elapsed, 1/17 actions completed.
[INFO] 12.0s elapsed, 1/17 actions completed.
[INFO] 13.1s elapsed, 1/17 actions completed.
[INFO] 14.2s elapsed, 1/17 actions completed.
[INFO] 15.2s elapsed, 1/17 actions completed.
[INFO] 16.3s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.1s, waiting on:

inject_generator:inject_generator on lib/constants/app_theme.dart
inject_generator:inject_generator on lib/constants/assets.dart
inject_generator:inject_generator on lib/constants/colors.dart
inject_generator:inject_generator on lib/constants/dimens.dart
inject_generator:inject_generator on lib/constants/font_family.dart
.. and 11 more

[INFO] 17.6s elapsed, 1/17 actions completed.
[INFO] 18.7s elapsed, 1/17 actions completed.
[INFO] 19.7s elapsed, 1/17 actions completed.
[INFO] 20.8s elapsed, 1/17 actions completed.
[INFO] 21.9s elapsed, 1/17 actions completed.
[INFO] 23.0s elapsed, 1/17 actions completed.
[INFO] 24.0s elapsed, 1/17 actions completed.
[INFO] 25.0s elapsed, 1/17 actions completed.
[INFO] 26.1s elapsed, 1/17 actions completed.
[INFO] 27.2s elapsed, 1/17 actions completed.
[INFO] 28.2s elapsed, 1/17 actions completed.
[INFO] 29.3s elapsed, 1/17 actions completed.
[INFO] 30.4s elapsed, 1/17 actions completed.
[INFO] 31.4s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.1s, waiting on:

inject_generator:inject_generator on lib/constants/app_theme.dart
inject_generator:inject_generator on lib/constants/assets.dart
inject_generator:inject_generator on lib/constants/colors.dart
inject_generator:inject_generator on lib/constants/dimens.dart
inject_generator:inject_generator on lib/constants/font_family.dart
.. and 11 more

[INFO] 32.7s elapsed, 1/17 actions completed.
[INFO] 33.8s elapsed, 1/17 actions completed.
[INFO] 34.9s elapsed, 1/17 actions completed.
[INFO] 36.0s elapsed, 1/17 actions completed.
[INFO] 37.1s elapsed, 1/17 actions completed.
[INFO] 38.1s elapsed, 1/17 actions completed.
[INFO] 39.2s elapsed, 1/17 actions completed.
[INFO] 40.3s elapsed, 1/17 actions completed.
[INFO] 41.4s elapsed, 1/17 actions completed.
[INFO] 42.5s elapsed, 1/17 actions completed.
[INFO] 43.6s elapsed, 1/17 actions completed.
[INFO] 44.7s elapsed, 1/17 actions completed.
[INFO] 45.7s elapsed, 1/17 actions completed.
[WARNING] No actions completed for 15.0s, waiting on:

inject_generator:inject_generator on lib/constants/app_theme.dart
inject_generator:inject_generator on lib/constants/assets.dart
inject_generator:inject_generator on lib/constants/colors.dart
inject_generator:inject_generator on lib/constants/dimens.dart
inject_generator:inject_generator on lib/constants/font_family.dart
.. and 11 more

[INFO] 47.7s elapsed, 1/17 actions completed.
[INFO] 48.8s elapsed, 1/17 actions completed.
[INFO] 49.9s elapsed, 1/17 actions completed.
[INFO] 51.0s elapsed, 1/17 actions completed.
[INFO] 52.0s elapsed, 1/17 actions completed.
[INFO] 53.0s elapsed, 1/17 actions completed.
[INFO] 54.1s elapsed, 1/17 actions completed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/zubairehman/flutter-boilerplate-project/issues/68#issuecomment-671088864, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFYYRD5LWNTMT24ESRIXJXDR73W7VANCNFSM4PYS64VA.

Hi @simsimatoo i also face this issue, pls advise @zubairehman. thanks.

Hello, today I have noticed it's happening also in my project. I downloaded clean flutter-boilerplate-project repository and problem still exists. Best regards.

Hi,
I had the same issues. I have solved this problem by:

flutter upgrade
flutter pub upgrade
flutter clean
flutter pub get
flutter packages pub run build_runner build --delete-conflicting-outputs --verbose

It's worked for me. Best regards.

my brother
I want add Arabic language
Language(code: 'AR', locale: 'ar', language: 'Arabic'),

من: radoo11<EMAIL_ADDRESS>تم الإرسال: 21/ذو الحجة/1441 01:54 م
إلى: zubairehman/flutter-boilerplate-project<EMAIL_ADDRESS>نسخة: simsimatoo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>الموضوع: Re: [zubairehman/flutter-boilerplate-project] flutter-boilerplate-project (#68)
Hi,
I had the same issues. I have solved this problem by:

flutter upgrade
flutter pub upgrade
flutter clean
flutter pub get
flutter packages pub run build_runner build --delete-conflicting-outputs --verbose

It's worked for me. Best regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/zubairehman/flutter-boilerplate-project/issues/68#issuecomment-671876165, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFYYRDYWAJJT5IVRKUUDACTSAEPM5ANCNFSM4PYS64VA.

@simsimatoo will add support to that.
Will also update all the dependencies and push the updates.
Thanks.

Hi,
I had the same issues. I have solved this problem by:

flutter upgrade
flutter pub upgrade
flutter clean
flutter pub get
flutter packages pub run build_runner build --delete-conflicting-outputs --verbose

It's worked for me. Best regards.

it works seamlessly thanks

I had same issus. and I resolved by changing dependency of analyzer version from analyzer: ^0.39.12  to 0.39.14.
Now it works well.

AddOns:
if you still facing a build issue then try with Administrator privilege and move source_gen, analyzer, intl in dev_dependencies.

If any one still facing this issue please follow these steps:

Move these dependencies source_gen, analyzer and intl from dependency_overrides: to dev_dependencies: .
Run these commands in terminal which are given below:
flutter upgrade
flutter pub upgrade
flutter clean
flutter pub get
flutter packages pub run build_runner build --delete-conflicting-outputs --verbose

If any one still facing this issue please follow these steps:

Move these dependencies source_gen, analyzer and intl from dependency_overrides: to dev_dependencies: .
Run these commands in terminal which are given below:
flutter upgrade
flutter pub upgrade
flutter clean
flutter pub get
flutter packages pub run build_runner build --delete-conflicting-outputs --verbose

Followed this, and have my version as below worked for me.
  source_gen: 0.9.6
  analyzer: 0.39.14
  intl: ^0.16.1

Flutter release 1.22.0 stable version, when build project it said "Bad state: Unexpected diagnostics: This requires the 'non-nullable' language feature to be enabled." with infinite loop.

For anyone that still facing this issue, please make sure your flutter version is v1.xx.xx, because when you run flutter upgrade it'll upgraded into flutter v2.0, I've been trying to figuring this out for hours until I realize that I'm using flutter v2.0.
If you need to back to flutter v1.xx.xx you can run this steps :

flutter downgrade
flutter doctor
flutter clean
Maybe you need to checkout your repo to the original version because the pubspec.yaml already changed on your previous attempt.
flutter pub get
flutter packages pub run build_runner watch --delete-conflicting-outputs

I hope this can save your time.

For anyone that still facing this issue, please make sure your flutter version is v1.xx.xx, because when you run flutter upgrade it'll upgrade the flutter into v2.0, I've been trying to figuring this out for hours until I realize that I'm using flutter v2.0.
If you need to back to flutter v1.xx.xx you can run this steps :

flutter downgrade
flutter doctor
flutter clean
Maybe you need to checkout your repo to the original version because the pubspec.yaml already changed on your previous attempt.
flutter pub get
flutter packages pub run build_runner watch --delete-conflicting-outputs

I hope this can save your time.

For anyone that still facing this issue, please make sure your flutter version is v1.xx.xx, because when you run flutter upgrade it'll upgrade the flutter into v2.0, I've been trying to figuring this out for hours until I realize that I'm using flutter v2.0.
If you need to back to flutter v1.xx.xx you can run this steps :

flutter downgrade
flutter doctor
flutter clean
Maybe you need to checkout your repo to the original version because the pubspec.yaml already changed on your previous attempt.
flutter pub get
flutter packages pub run build_runner watch --delete-conflicting-outputs

I hope this can save your time.

I still have this issue, the project cannot be built and run infinitely [INFO] 2.6s elapsed, 1/17 actions completed.. I am on an Apple M1 device, only this command flutter packages pub run build_runner watch --delete-conflicting-outputs  has the issue, other ones from the instruction work well.

What I did was to downgrade my flutter version and run the builder again. After that I upgraded to the newest flutter version again. Build will still not work but everything else works.

@aminazirani Can you share the command and what version you downgraded? Thanks a lot!


docs($interpolate): typo

There was missing JS at line 141.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs only, example fix.
What is the current behavior? (You can also link to an open issue here)
Somewhat confusing:
var exp = $interpolate('Hello {{name | uppercase}}!');
expect(exp({name:'AngularJS'})).toEqual('Hello ANGULAR!');

Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format

Thanks for the PR. Can you sign the CLA?

I signed it!


Run E2E also with Avro

Closing this for now as it requires custom Kafka Connect Avro (De)serializer or using a schema registry as the popular Avro SerDes require schema registry.


Moving lightsail(3) resources to v1beta1 version

lightsail

[ ] aws_lightsail_container_service_deployment_version
[ ] aws_lightsail_lb_certificate_attachment
[ ] aws_lightsail_lb_https_redirection_policy

aws_lightsail_container_service_deployment_version - error during applying.

aws_lightsail_lb_certificate_attachment - needs certificate.

aws_lightsail_lb_https_redirection_policy - depends of aws_lightsail_lb_certificate_attachment


docs: add "Error handling" section to README

Fixes #579

Released: v0.30.1 🎉
This has been released in v0.30.1!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


elasticsan preview refresh microsoft.elasticsan 2022-12-01-preview

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. [ July]
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

/azp run

Hi @rkmanda , can you please review this PR? We have an ETA to close on this by 12th of this month.

@PreetPRG - Nice changes. Signing off for ARM with comments. Please still consider remaining 3 active comments from me.

Hi @mentat9 , do you know how to merge the PR, I am not authorized to merge the PR, if possible can you please help me with merging?

this js sdk breaking is caused by this pr


Push notification shows incoming tx multiple times

Seems like the push notification needs a bit of tweaking, it shows the incoming transaction multiple times:

Device: Moto G5
OS: Android 7.0
Bug was reproduced on the same device

Are you sure these dupes are multiples of a single incoming transaction? Maybe it was the old notification that wasn't cleared by you. You have to either swipe, or click on the notification to remove it.

The screenshot shows one single notification, I'm sure. I noticed this issue during the first incoming tx on my wallet (from faucet  request). After I dismissed the first notification (which looked identical) I requested a second faucet transfer to take this screenshot.

In some cases the tx is displayed 5 times, in other cases 2, 3 or 4. I've also seen the correct version (1) but so far it has varied each time I requested funds.

Fixed in https://github.com/decred/dcrandroid/commit/a881d6da436a4f22bc2a807f62e771adad4db174 @ #156

Fixed in


AU Effect disapears after clicking on Close button

Hello dear developer!
Please see on a bug video below:
https://github.com/user-attachments/assets/b19bae4c-bcd3-4c2d-b839-808ceb7c86aa

This is intended behavior when running in Compact mode :-)

But AU window is disappeared. I guess it's not intended behavior, isn't it?

It is intended ... when you close the effects panel, the app assumes you are finished with the effects (in Compact mode) ... keep in mind that the Compact app mode is a limited-interaction app mode ... this means that the app will make certain assumptions about how the user will interact with it ... it will not be as full-featured as the Modular and Unified app modes ... those modes should allow all core functionality without restrictions, but Compact app mode simply does not allow multiple windows to hang around ... it is meant to be ... "Compact" 😁

... but I guess you like to monitor the sound with your AU window ? In that case, I will think of a way to allow this in Compact mode as well... it was not how it was intended to be in Compact mode, but let's see

... but I guess you like to monitor the sound with your AU window ? In that case, I will think of a way to allow this in Compact mode as well... it was not how it was intended to be in Compact mode, but let's see

Yes, exactly, thank you so much. I see that in current version is working well in Compoct mode. I like it.

Sorry @kartik-venugopal, when I was testing last build I found that it does not work. Also I found double main window. It looks like bug.

Log file, should be useful.
aural.log

Hey, can you please give me the steps to reproduce the double window in Compact Mode ? I am not able to reproduce that. Thanks.

It's to hard. I cannot to reproduce it. I did not understand what exactly hapend in that time.

Fixed, AU windows will now stay open. Will release soon.


python310Packages.gaphas: 3.8.0 -> 3.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.gaphas is: "GTK+ based diagramming widget"
meta.homepage for python310Packages.gaphas is: "https://github.com/gaphor/gaphas"
meta.changelog for python310Packages.gaphas is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.8.1 with grep in /nix/store/q7n0y4lc4v1rpg615y7l8smz1jljswlw-python3.10-gaphas-3.8.1
found 3.8.1 in filename of file in /nix/store/q7n0y4lc4v1rpg615y7l8smz1jljswlw-python3.10-gaphas-3.8.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
gaphor
python310Packages.gaphas
python39Packages.gaphas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q7n0y4lc4v1rpg615y7l8smz1jljswlw-python3.10-gaphas-3.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.gaphas https://github.com/r-ryantm/nixpkgs/archive/4dede45d4e1f18fd2a84a70bb5434cb04f6e5976.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q7n0y4lc4v1rpg615y7l8smz1jljswlw-python3.10-gaphas-3.8.1
ls -la /nix/store/q7n0y4lc4v1rpg615y7l8smz1jljswlw-python3.10-gaphas-3.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

gaphor
python310Packages.gaphas
python39Packages.gaphas

Maintainer pings
cc @WolfangAukang for testing.

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

3 packages built:

gaphor
python310Packages.gaphas
python39Packages.gaphas


Supporting to distinguish multiple consent forms during onboarding via an identifier (#50)

Support for storing multiple consent forms (#50)
:recycle: Current situation & Problem
Closes #50
In the case of multiple OnboardingConsentView, it was impossible to distinguish the individual consent forms when storing in the Standard, as the "store" function of the OnboardingConstraint only receives a PDFDocument as a parameter and no additional information.
:gear: Release Notes

Added a parameter "identifier" to OnboardingConsentView and OnboardingConstraint.
If an identifier is specified when creating an `OnboardingConsentView', then the store function will be called with that identifier; otherwise the identifier is set to the default value "DefaultConsentDocument".
UITests/TestApp has been changed accordingly to test the new functionality of having multiple (in this case two) consent forms.

Added "First" and "Second" Test View and Rendering View
ExampleStandard has been changed to distinguish the two consent forms based on their identifiers "FirstConsentDocument" and "SecondConsentDocument"

:books: Documentation
*Documented changes in the appropriate Markdown files.
:white_check_mark: Testing

Adapted UI Test app to include a second OnboardingConsentView with an identifier different from the first one.

If you accept this PR, there are implications for SpeziTemplateApplication and SpeziStudyApplication, as both use an OnboardingConsentView and require to add the "identifier" parameter to the respective Standard. I am happy to make those changes if this PR gets accepted.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

Thank you very much @PSchmiedmayer for the detailed and thoughtful feedback! I went over it carefully and incorporated your suggestions. I will also add some considerations I had in mind to your comments.
Regarding the failing test, I saw that we got the following error on iPadOS. "The request was denied by service delegate (SBMainWorkspace) for reason: NotFound ("Application "edu.stanford.spezi.onboarding.testappuitests.xctrunner" is unknown to FrontBoard")"
I am not sure how to solve this, can I do anything on my side to fix this?
Thanks again!
Best,
Patrick

Hi @PSchmiedmayer,
thanks again for the thoughtful feedback! I went over it carefully and have incorporated all of it, and hope I haven't overlooked anything. I also closed most of the conversations except two which I left open for potential further discussion. Let me know what you think :)
Thanks again!
Best

Thanks again @PSchmiedmayer for the suggestions! Much appreciated.
I have incorporated them and added a response to your last comment.
Also thanks for checking again the test runners! Curious to see whether they will run through now :)

Thanks @PSchmiedmayer, I have incorporated the suggestions! :)

Thank you very much @PSchmiedmayer, excited to see the code getting merged into Spezi!
I have added the default identifier.
Regarding the failing tests, to me it looks like a performance issue, or in general an issue with the runners. I attached a screenshot of the error from the xcresult file:

Thanks for taking a look at the tests; I will try to investigate this later this week!

Thanks! I also have incorporated the last changes regarding the default document identifier.

@RealLast We have worked on some UI testing infrastructure improvements in #55 and once this is merged we can pull this in to this PR and merge it from there 👍

@RealLast We have merged the fixed for the builds on the main branch and have also updated out build agents; it would be amazing if you can merge main to this branch to eventually merge this PR; let me know if you have any questions or run into any issues!

Thanks @PSchmiedmayer for checking it, I have resolved the comment! Waiting for the merge :)


reduce q 1

challenge 1 passes! feel free to complete and re-submit the assignment for additional credit. Thanks!


⚠ Jenkins Plugins Artifactory has degraded performance

In 0758fdc, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2661 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 229d167 after 47 minutes.


Unify groupId for off-chain groups

Description

Use same ID for off-chain groups in DB and Smart contract
Set off-chain group limit to 100 in UI

Related Issue
#139
Does this introduce a breaking change?

[x] Yes
[ ] No

Other information
DB schema is changed. No migration is provided now.
Remove all tables and let TypeORM recreate the tables.

Group names should still be unique right? We don't want two groups with the same name

The unique key in the DB is for groups from all users. I thought of this, and had a feeling that two separate admins might need same group name. Eg: "Github contributors", "Company employees". Do we need to restrict on that level?
We can add a unique key for (userId + groupName) though. But not sure if we want to be more restrictive at this point unless we technically have to?
Let me know your thoughts, I can update.

The unique key in the DB is for groups from all users. I thought of this, and had a feeling that two separate admins might need same group name. Eg: "Github contributors", "Company employees". Do we need to restrict on that level?
We can add a unique key for (userId + groupName) though. But not sure if we want to be more restrictive at this point unless we technically have to? Let me know your thoughts, I can update.

Umh I think it's fine for now, looks like something we can understand later, when actual people start using ZKGroups maybe


Accessory View and Accessory Type support for iOS8

I'm not a fan of this either. I recognize that these numbers might change in later versions and this proposes a problem.
The issue here is that the width isn't the actual width of the accessoryView it seems that the width of the actual view is being accounted for. What is not being accounted for is the margin between the accessoryView.trailing and UITableViewCell.trailing.
I don't know of any way to actually access a variable for that space or to compute it. From my research and experimentation, 10.0f for accessoryType and 15.0f for accessoryView is the "Magic Number".

@JRG-Developer If you have any suggestions or want to discuss how to do this differently, give me a call!

I've done some more experimentation, and changing other constraints on the cell seems to alter this number. I'm trying to see if I can reverse engineer the formula. I'll close this and make another pull request if I can get it.

Yep, this can indeed be frustrating. :/
Fortunately, iOS 8 provides support from Apple for calculating dynamic table view cell size! Perhaps, this issue will just be put off until iOS 7 support can be dropped?
:]


can not build cross-platform with fox

got error
1 errors occurred:
--> linux/amd64 error: exit status 2
Stderr: # gopkg.in/rana/ora.v4
../../gopkg.in/rana/ora.v4/drvStmt.go:18: undefined: Stmt

Sorry, but what is "fox" ?

BTW cgo is needed, so cross-compilation is not easy!

yes, i thought too simple


Is it possible to return a Promise from onBefore?

I need to perform async transformation of the whole markup before any other transformers.

Added support to a async onBefore on v2.5.2 :wink:


Document the System.PullRequest.SourceCommitId variable

Adding the variable mentioned in issue #4588 as it was confirmed to be officially supported in issue #9801

@juliakm

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thank you @brianaeng!
#sign-off


Inserting using QueryBuilder requires columns even though they have a defaultRaw / default value

Describe the bug
Trying to insert using a QueryBuilder still requires every non-optional property of the entity to be given, even though some of those properties have a defaultRaw.
Making all properties that have a default value also optional to pass the type checking cannot be an option.
Reproduction
import { Entity, ManyToOne, PrimaryKey, Property } from '@mikro-orm/core';

@Entity({ tableName: 'directories' })
export class Directory {
	@PrimaryKey({ type: 'uuid', nullable: false, defaultRaw: 'UUID()', unique: true })
	readonly id!: string;

	@Property({ type: 'varchar', nullable: false })
	readonly name!: string;

	@Property({ type: 'tinyint', nullable: false, default: false })
	readonly isRecycled!: boolean;

	@Property({ type: 'datetime', nullable: false, defaultRaw: 'current_timestamp()' })
	readonly createdAt!: Date;

	@Property({ type: 'datetime', nullable: false, defaultRaw: 'current_timestamp() on update current_timestamp()' })
	readonly updatedAt!: Date;
}

await entityManager
    .createQueryBuilder(Directory, "directories")
    .insert({
        name: "test"
    }); // TypeError: not assignable to `RequiredEntityData<Directory>`

What driver are you using?
@mikro-orm/mariadb
MikroORM version
6.0.4
Node.js version
v.20.5.1<EMAIL_ADDRESS>Operating system
Windows 11
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

That's only a type-level issue, you need to mark those properties with runtime defaults via Opt type (or via OptionalProps symbol), otherwise TS only sees required properties - there is no way to detect there is a runtime default. Decorators options are not relevant here, they don't have any effect on type level.
https://mikro-orm.io/docs/property-validation#properties-with-default-value

Maybe we should add a reference to that in the docs under https://mikro-orm.io/docs/defining-entities#optional-properties?
Perhaps this would make optional properties with typescript clearer.


Catboost added with hyper parameter tuning

Fixes Issue🛠
Closes #95
Description👨💻
CatBoost implementation using hyper-parameter tuning using Optuna.The optuna took over 10 hours to run and hence the submission was a little late.
Type of change📄

[] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How this has been tested✅
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I am an Open Source Contributor

Screenshots/GIF📷
Test and training results

Scatter plot of predicted test values

Scatter plot of predicted training values

Pls provide model name as well in the title of both the graphs @Shubhra-31

Done the changes, kindy check @Rakesh9100

please check @Rakesh9100

Pls run black main.py on your editor and then commit to pass the linting check workflow @Shubhra-31

Already told you to do this pls @Shubhra-31

Could you explain what exactly I have to do ? I am not sure what to do.

Open the project folder in your local editor i.e. Visual Studio and then open the terminal and run black main.py and file will be updated with indentation changes and then do the commit @Shubhra-31

Please check @Rakesh9100

You can see the lint check has been failed. Pls follow https://github.com/Rakesh9100/ML-Project-Drug-Review-Dataset/pull/104#issuecomment-1595844316 properly or connect me on discord. @Shubhra-31


[UIK-2421][docs] Added the Add filter pattern

Motivation and Context
I've added a page for the new Add filter pattern.
The example is a draft with some initial components and data.
Types of changes

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

Checklist:

[ ] My code follows the code style of this project.
[x] I have updated the documentation accordingly or it's not required.
[ ] Unit tests are not broken.
[ ] I have added changelog note to corresponding CHANGELOG.md file with planned publish date.
[ ] I have added new unit tests on added of fixed functionality.

I also was thinking that we will need to check the example in the future from the accessibility point of view.

Yep, I'll probably have to provide some a11y instructions while preparing the task for development, at least focus behavior when adding/removing filters. And then we'll a11y-test the example when it's ready.

@j-mnizhek Maybe you have some ideas about component name?

Folks, I've found that input for Position filter shows 2 Clear buttons when there is a value entered 👻

Folks, I've found that input for Position filter shows 2 Clear buttons when there is a value entered 👻

Should be fixed. pull the latest changes

@j-mnizhek Maybe you have some ideas about component name?

Leaving this comment for the history: we've choosen AddFilter for the name.

@ilyabrower translations are added


Release v2.13.0+rev1

Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

Superseded by https://github.com/resin-os/resin-jetson-tx1/pull/4


Add triage permissions for dianazig

Nomination
GitHub User
Provide the following information about the GitHub user:

Diana Zigterman
dianazig
Google

Supporting Documents
Diana is a USB-C power delivery expert.  We would like to enable triage permission so Diana can participate in reviews of the USB-C power delivery subsystem on Zephyr.
https://github.com/zephyrproject-rtos/zephyr/pull/39383
https://github.com/zephyrproject-rtos/zephyr/pull/51660

@DianaZig for visibility

@DianaZig has been added as a user with Triage permission.

Thank you!


There was no code review/PR for this commit.  Did you configure your fork/repo correctly?
It breaks the Travis output logs: https://travis-ci.org/j2objc-contrib/j2objc-common-libs-e2e-test/builds/82874786
There's already a normal PR for this that actually fixes Joda build: https://github.com/j2objc-contrib/j2objc-common-libs-e2e-test/pull/41 (see above, it is still red)

@brunobowden - did you configure your fork correctly?  your commit went straight to upstream master instead of origin branch.

My mistake. I believe I cloned the original repo instead of my fork.


LGTM.com - false positive

Description of the false positive
Git.apply here is calling a static function, not calling the built-in apply.

URL to the alert on the project page on LGTM.com
https://lgtm.com/projects/g/eamodio/vscode-gitlens/snapshot/0119be24d14a664ae5b9807df5f0d1d367badbda/files/src/git/gitService.ts?sort=name&dir=ASC&mode=heatmap#xf59607030876bf5:1

Thank you for reporting this, @eamodio! I've put up a fix (https://github.com/Semmle/ql/pull/1996).


Test .Rmd notebooks within Jupyter using online mybinder.org service

Hey @mwouts,
Was reminded of your tool thanks to your comment here: https://github.com/rstudio/rmarkdown/issues/1020#issuecomment-406168864
I was wondering if you have heard of https://mybinder.org/ and, if so, if you had considered using the service to render .Rmd notebooks within Jupyter in an interactive way on Binder without converting to .ipynb. You can link to specific .ipynb within Binder and perhaps it can also work with .Rmd notebooks using nbrmd? I could give it a go sometime this weekend, but I would appreciate your thoughts in general.
Cheers,
A.

Hi @RaoOfPhysics , thanks for your interest.
At first sight I would say that chances that everything works together are small!
But indeed we should give it a try, and I'd be curious to test as well.
I expect possible issues with the following points:

is it possible to edit 'jupyter_notebook_config.py' on Binder?
can nbrmd be installed in the python environment to which jupyter belongs?

Another question: if you only provide the .Rmd file in Binder, you don't expect Binder to show the outputs before the notebook is actually executed, right?

Pinging @betatim and @choldgraf in the hope that one of them will have answers to your questions! (Apologies, both.)

You can include the config file in your Git repository as .jupyter/jupyter_notebook_config.py and it will end up in ~/.jupyter/jupyter_notebook_config.py when the image is built for use with a BinderHub.

Thanks @betatim , @RaoOfPhysics . I just tried, and it worked on the first attempt ! I'm quite impressed. I just had to include binder config files in this commit, and then my notebooks became available in binder at
https://mybinder.org/v2/gh/mwouts/notebooks/master
I guess we're not done yet, as my notebook repo does not include a pure R example (my Rmd notebooks there are mostly python). I'll try to add one.

I've just pushed a simple Rmd R sample, that works well with binder/nbrmd/jupyter.
Thanks @RaoOfPhysics for suggesting this, it was very helpful.
I'll definitely use binder to provide live examples for the nbrmd / nbsrc packages!

Great to hear it worked so smoothly!
One tip: I would specify versions for your dependencies in requirements.txt. Helps with making the builds reproducible and this way you can trigger a rebuild of the image in mybinder.org when you want to explicitly upgrade to a newer version of a dependency. Otherwise you have to make a dummy/empty commit just to trigger the rebuild

Thanks @betatim . Yes I like the suggestion of specifying versions, and actually that's what I had to do for #21 .
I've now added a binder for my project as well, which works very nicely. I could put almost all my binder configuration in a binder folder, except for .jupyter/jupyter_notebook_config.py which became effective only when I moved it at the root of my project. Do you think I should report that at the binder project?

Looks great, @mwouts! :D But do I have to change the kernels or something to get it to work? On Fourier_with_ioslides.Rmd for example, the "magics" aren't working if I use the R kernel.
Error in parse(text = x, srcfile = src): <text>:1:1: unexpected SPECIAL
1: %%
    ^
Traceback:

I'm also getting an error that knitr isn't installed.
Error in loadNamespace(name): there is no package called ‘knitr’
Traceback:

1. knitr::opts_chunk
2. getExportedValue(pkg, name)
3. asNamespace(ns)
4. getNamespace(ns)
5. tryCatch(loadNamespace(name), error = function(e) stop(e))
6. tryCatchList(expr, classes, parentenv, handlers)
7. tryCatchOne(expr, names, parentenv, handlers[[1L]])
8. value[[3L]](cond)

Well, I'm afraid that Fourier_with_ioslides.Rmd is not the best example! That's a complex python/R notebook that works in rstudio (renders there to an interactive HTML presentation). I think there's no chance to have that notebook rendered correctly in jupyter, because there's a strong assumption that python cells are executed by reticulate.
For now there is only one working example, which is https://mybinder.org/v2/gh/mwouts/notebooks/master?filepath=sample_R.Rmd.
Also, feel free to explore the package itself in binder, and open .py and .Rmd test files as notebooks, at https://mybinder.org/v2/gh/mwouts/nbrmd/master
Finally, yes, when you open a rstudio Rmd file for the first time in jupyter you will have to select a kernel. When you save the jupyter notebook as Rmd, then the kernel information is added to the yaml header.

So, as long as one isn't mixing kernels in the same file, it should work like a dream.

Ok I see, well now it has been mentioned here, that's probably enough!
@betatim , I have a question relative to #23 - is it possible to open text files in a text editor in binder?
For the demo I'd like to show how the python notebook, once edited in a text editor, can be reloaded into Jupyter, with outputs and variables preserved... I've seen that rstudio is available with urlpath=rstudio - are there python-oriented text editors which I can open using a similar syntax?


Failed to snapshot build script .dart_tool/build/entrypoint/build.dart

[SEVERE] Failed to snapshot build script .dart_tool/build/entrypoint/build.dart.
This is likely caused by a misconfigured builder definition.
[SEVERE] ../../.pub-cache/hosted/pub.dartlang.org/retrofit_generator-1.1.0/lib/src/generator.dart:700:39: Error: The method 'getDisplayString' isn't defined for the class 'DartType'. - 'DartType' is from 'package:analyzer/dart/element/type.dart' ('../../.pub-cache/hosted/pub.dartlang.org/analyzer-0.36.4/lib/dart/element/type.dart').Try correcting the name to the name of an existing method, or defining a method named 'getDisplayString'.      return refer(constant.typeValue.getDisplayString());

I upgraded the third party libraries, the error is solved


User can't copy values from text fields in "Calculated Values" window. After CTRL+C nothing is copied to the clipboard.

Affected Version: Standalone, Remote, release\2.1
Steps to Reproduce:

Create some structure, for example, benzene.
Click 'Calculated Values' button.
Select value in 'Chemical Formula' field, press CTRL+C.
Open Notepad and press CTRL+P.
Repeat p.4-5 for fields: Molecular Weight, Exact Mass, Elemental Analysis.

Expected Result:
User can copy all information in text fields.
Actual Result:
Nothing copied to the clipboard after CTRL+C action. User can't paste this information in external resources.

Issue is closed as fixed.


chore: remove monitoring automation setup

https://del-monitoring-setup--express--adobecom.hlx.page/express/

Codecov Report

Merging #452 (1e6dbd8) into stage (04bdf9f) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            stage     #452      +/-   ##
==========================================
- Coverage   30.02%   29.96%   -0.07%
==========================================
  Files         124      124
  Lines       23740    23740
==========================================
- Hits         7129     7113      -16
- Misses      16611    16627      +16

see 1 file with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Convert the org.carlspring.strongbox.storage.repository.Repository class to use RepositoryPath objects instead of File-s

We should try to avoid the use of File-s at all cost. There are a couple of methods in the org.carlspring.strongbox.storage.repository.Repository class that are currently returning File-s. A minor refactoring will be required in order to sort this out.

@ptirador are you working on this ?

Uhm, no at the moment. You can take it if you want.

Implemented by @fu


test if aot works with the sample

https://github.com/ozkanpakdil/test-microservice-frameworks/tree/main/Dotnet6Microservice can be converted to 7
then test if can it build with https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/ put a performance report for it in the results.

https://ozkanpakdil.github.io/microservicetests/2023-02-26-microservice-framework-test-17.html

added dotnet 7 aot right bottom


Add translatable strings for Religion field

Added translatable strings to the Religion field for the most common documented values of the religion key. This PR includes each value with at least 100 occurrences and some mention on this wiki page. There are many more religion values in use, but the less common values would likely be more difficult for translators to translate. They’ll still be visible in the dropdown, just not translated yet.
Working towards #254.

I think what we should do is using the same scheme for this field and the denomination field. Does that change anything for this PR? 🤔

Denomination will be a much more difficult task, because it’s so open-ended. (My past self from 2010 should’ve campaigned hard to make it a freeform text key similar to operator/operator:wikidata…) I’m unsure which form to use for that field. For some denominations (roman_catholic), the adjective form is more natural, but plenty of other denominations lack an adjective form in the first place (assemblies_of_god, iglesia_ni_cristo). We can get by with a few exceptions in Religion, but Denomination will be all over the place.

@tyrasd Is some extra research/help/review required here? I am not a native speaker but may try recruiting some.
(I am interested in denomination stuff as I plan to use it for https://github.com/streetcomplete/StreetComplete/issues/1737 )

Upon reflection, I think we should go with the adjective forms of religions, where available. People sometimes need to coin new religion values. If they see that most of the menu items are -isms, they may perceive a need to include -ism in the raw tag value, even though that hasn’t been the general practice. This consideration is specific to English, which happens to be the language of raw tag values; translators can choose the form most suitable in their respective languages.


Add OpenTrace adapters or utilities

Placeholder for any changes from supporting standard OpenTrace app updates

Turns out it's actually very simple to migrate from OpenTrace to Herald, especially with Herald's detection of OpenTrace natively now. So this will be closed here, and added as a documentation task on the website for the dev/migration guide.


[WIP] Improve deployment scripts + Typescript support

@dmtrKovalenko This is the first attempt to improve the deployment scripts.
This makes a build folder, puts all files compiled plus dist in there.
I added 2 definition files for testing. I'll add more if you like what I did here.
Closes #75
Closes #78

Hi. Is it still in progress?

@dmtrKovalenko You can merge this if you wish. it's only work in progress for the typings. I can make another PR for the typings.


ACT-688 Rename Beneficiary model "Individual"

The Beneficiary model should be renamed Individual and the following fields changed:

Beneficiary name → First Name (charField)


dereference of a possible NULL pointer in library

tvgPaint.h line 139 : no test after calloc()
tvgPictureImpl.h line 235: no test after malloc
reported by Visual Studio

tvg doesn't guarantee those safety of the memory issues.

ok, closing


Error when want to "efterlyse" the word "take away"

The page appears when search on the word.
http://www.wign.dk/request/take away

Looks like that the issue appears when "efterlyse" a word that contain a space.

No, it doesn't work in all words that don't exist in the db in beforehand. Looking at the code now @Kennik89 :)


[prim_lfsr] Fix spyglass lint warnings

Spyglass complains about unassigned signals in the gen_unknown_type generate block.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

Fix looks OK!


peripheral-firmware: extract on boot by default

This improves the situation for flake users, as previously they had to either add the non-redistributable firmware to their repositories or go without the firmware.
This change also brings the ISO into line with the regular NixOS modules as storing the peripheral firmware in the Nix Store is no longer a requirement.

I do not think I agree with this change at this time.

It exposes us to race conditions between drivers which need the firmware and the extraction of it.
It means firmware is less controlled by the generational mechanism which could create incompatibilities in updates. Admittedly this is not exceptionally well defined by default but these changes would make rolling back a firmware ESP file update through the bootloader menu impossible.
It brings Python and a bunch of libraries into the system closure.

Let's revisit this once the mechanism by which firmware updates occur is defined. I will give some more thought to the flakes case in a bit.

Is it possible we could have this available as a module option, off by default? I would like to use it, but would have to maintain my own fork of nixos-apple-silicon, or use @Enzime's branch if it's not maintained here.


Correct Sonatype Taxonomy URL & Typos

Update URL for Sonatype URL:  the target page has been renamed.
Correct several spelling errors in README

Thanks @msymons


PanNuke dataset problem？

Hello, there seems to be an error in the PanNuke dataset.His Fold2 data download keeps showing that it's Fold3, is there a problem here?

Thanks, I solved it.


Introduce TextureViewType and handle detection from Texture

Introduce TextureViewType and handle detection from Texture, fixes #245.
Support for all backends.

Looks pretty good overall. Could you please add at least one test case covering the most important use for this, e.g. using a non-array Texture inside an array view? It also needs to have a full implementation for all backends, but I think you're already closing the gap there.

Test just landed!


Refactor Tests and Import Resources

Pull Request (PR) description
This PR refactors unit and integration tests to bring them in line with standards.
It also refactors the CertificateImport and PFXImport resources to share more code.
I did this in preparation for #194 which should be done for both resources.

Refactor integration tests to update to latest standards.
Refactor unit tests to update to latest standards.
CertificateImport:

Refactor to use common functions and share more code with PfxImport
resource.
Resource will now only throw an exception if the PFX file does not exist
and it needs to be imported.
Removed file existence check from Path parameter to enable the resource
to remove a certificate from the store without the need to have the
access to the certificate file.
Removed ShouldProcess because it is not required by DSC Resources.

CertificatePfx:

Refactor to use common functions and share more code with
CertificateImport resource.
Resource will now only throw an exception if the certificate file does
not exist and it needs to be imported.

This Pull Request (PR) fixes the following issues
Task list

[x] Added an entry under the Unreleased section of the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

@johlju - would you mind reviewing? Sorry about the size of this one - it was a bit of a refactoring job and should simplify things somewhat.

This change is

Codecov Report

Merging #202 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff         @@
##           dev   #202    +/-   ##
===================================
+ Coverage   88%    88%   +<1%
===================================
  Files        7      7
  Lines      943    936     -7
  Branches     1      0     -1
===================================
- Hits       831    830     -1
+ Misses     111    106     -5
+ Partials     1      0     -1


Upgrade spring-security to align with spring-boot 3.1.5

Upgrade spring-security to align with spring-boot 3.1.5

And we should backport to 4.0.x

I have backported


Missing subcommand in help using register

Hi there,
I used the the script found at 'https://gist.github.com/973082' to generate the following output
%./lab.rb
Tasks:
  lab.rb create [subcommand]  # create various things, e.g. labs, images, networks
  lab.rb help [TASK]          # Describe available tasks or one specific task

% ./lab.rb create
Tasks:
  lab.rb help [COMMAND]  # Describe subcommands or one specific subcommand
  lab.rb image [NAME]    # create image with given [NAME]
  lab.rb lab [NAME]      # create lab with given [NAME]
  lab.rb network [NAME]  # create network with given [NAME]

As seen above I entered
./lab.rb create

but in the help output the comand 'create' is missing. Could you add the command which was used create to the help output?
% ./lab.rb create
Tasks:
  lab.rb create help [COMMAND]  # Describe subcommands or one specific subcommand
  lab.rb create image [NAME]    # create image with given [NAME]
  lab.rb create lab [NAME]      # create lab with given [NAME]
  lab.rb create network [NAME]  # create network with given [NAME]

Thank you very much.
Cheers,
max_meyer

Here is a fix for this one https://github.com/wycats/thor/pull/196


Fix alpha blending

Closes  #465
I introduced this regression during the update to the latest wgpu-py. I added a test to prevent that in the future.

Lol. Looks like our example testing has been disabled for a while. All tests (and generations) are skipped. Looks like it does not detect lavapipe correctly.

Lol, a few example screenshots are set back to what they were before #468.


maxLifetime = 0 and idleTimeout = 0

Running performance tests on a postgres instance, we (me and my team) noticed a spike in response time during the very first requests, after the boot of the app.
The resulting plot was something like this (this is just meant to give you an idea, don't take it too seriously :)):

It shows the response time of our app under a load of 5/6 requests per second.
Setting both maxLifeTime and idleTimeout to zero, we were able to get rid of the initial spike.
Our take on that, is that creating all the connections together when the application starts up (we are using minConnection == maxConnection == 25) causes the spike.
My questions are:

Is it reasonable that creating 25 connections cause such a problem (first requests really took about 2 seconds to get back to us)? I would expect the creation of few connections to take a few milliseconds.
Is it bad to have connections open forever? (consider that my application is the only process using that database)

Exploring the history of the source code of hikari, I found this condition (that is not there anymore):
if (maxLifetime == 0 && idleTimeout == 0) {
  logger.warn("setting idleTimeout to {}ms.", IDLE_TIMEOUT);
  idleTimeout = IDLE_TIMEOUT;
}

I guess you went through this very problem :), and you decided that you didn't really like maxLifetime == 0 && idleTimeout == 0.

@calippo First question is, what version of HikariCP?
It is strange that either maxLifeTime or idleTimeout would eliminate the spike.  Neither should come into play during the first few minutes of startup.
idleTimeout is actually ignored when minimumIdle == maxConnections.
maxLifeTime similarly should not come into play until 30 minutes after startup.
ThreadLocalRandom can block the acquisition thread if enough entroy is not available.  On Linux this can be mitigated with -Djava.security.egd=file:/dev/./urandom" (yes, the /./ is necessary).
Connection creation speed varies quite a lot by database.  MySQL can typically setup a new connection in single-digit milliseconds.  Oracle over SSL can sometimes take 20-30 seconds per-connection.
I am curious why and if the spike is truly mitigated by either of the two variables you mentioned.  Certainly, setting a low minimumIdle would increase startup time -- but not if load immediately ramps up.
What does the database CPU and disk I/O look like during the spike?

Q1: First question is, what version of HikariCP?

A1: We are using slick 3.1.1, that uses hikari 2.3.7

Q2: It is strange that either maxLifeTime or idleTimeout would eliminate the spike. Neither should come into play during the first few minutes of startup.

A2: The reason why they came into play (in our opinion) is because we didn't shutdown the test setup between consecutive tests. With maxLifeTime == 0 && idleTimeout == 0, we only had the spike in the first test run 'since the connection was already opened' (at least this was our guess). The JVM was appropriately warmed up by the testing framework.

idleTimeout is actually ignored when minimumIdle == maxConnections.

:+1: I read about it but didn't manage to find it in the actual code

Connection creation speed varies quite a lot by database. MySQL can typically setup a new connection in single-digit milliseconds. Oracle over SSL can sometimes take 20-30 seconds per-connection.

Woah, didn't know about this. You have a similar estimate for postgres?

Lastly, it's not great to have connections "open forever" because something usually kills them eventually -- often databases have a maxLifeTime of their own. Better for the pool to retire and replace them in an orderly fashion rather than discovering a dead connection at the time that the application needs one.

Ok, I see your point is: "it's better to control connections rather then being controlled by connections" :)
Recap:

idleTimeout is completely ignored in our configuration. What we're doing is completely configured by maxLifeTime = 0
maxLifeTime = 0 is not a great configuration
beware connections create can take seconds
a possible solution for the problem would be -Djava.security.egd=file:/dev/./urandom"

Fortunately it looks that the performances of our app are good enough for our use case. I'm not sure we're going to test performances again (I'm likely going to set maxLifeTime to a reasonable amount of time).
The configuration consequences are now clear to me, I think you can close this issue. In case we go back testing the connection pool I'll update this with details (i.e. disk I/O CPU etc).

@brettwooldridge
hi, brettwooldridge.
I have a question about maxLifeTime and connection eviction.
My production database has 60s of wait_timeout.
HikariCP recommands maxLifeTime = wait_timeout - 30s.
so, I set up maxLifeTime 30s.
Every 30 seconds, i can get logs 'connection was evicted'.
2018-04-25 17:16:27.529 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@4c17abf9
2018-04-25 17:16:27.938 DEBUG 5501 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : hikariPool - Closing connection org.mariadb.jdbc.MariaDbConnection@316bf091: (connection was evicted)
2018-04-25 17:16:27.968 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@517ba0b8
2018-04-25 17:16:27.970 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - After adding stats (total=10, active=10, idle=0, waiting=0)
2018-04-25 17:16:28.646 DEBUG 5501 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : hikariPool - Closing connection org.mariadb.jdbc.MariaDbConnection@4a4f19a0: (connection was evicted)
2018-04-25 17:16:28.656 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@3db7055e
2018-04-25 17:16:29.258 DEBUG 5501 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Pool stats (total=30, active=15, idle=15, waiting=0)
Every 30 seconds!
Would not the load on the database?

@brettwooldridge
Thank you for your reply.!!
How much more efficient is it to create connections than the test-while-idle method?
Is there anything I can refer to?
if constantly making new connections is not expensive, there seems to be no reason to use DBCP...
Does HikariCP use a special way to create a connection?
😃


Feature 9 - Add a logger

Log information to a better debuggability and knowledge of the pipeline execution

Rejected because a library can't use a logging system, it could interfere with the logger of the user code


SUBMARINE-647. Change Workbench user name

What is this PR for?
The user name at the top-right corner is liuxun, should change to admin
What type of PR is it?
[Bug Fix]
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-647
How should this be tested?
https://travis-ci.org/github/kobe860219/submarine/builds/731279516
Screenshots (if appropriate)

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

https://github.com/apache/submarine/blob/cdb2e7f8b17c1badbcd0601d8200b947f9a37a97/submarine-server/server-core/src/main/java/org/apache/submarine/server/workbench/rest/SysUserRestApi.java#L228


Match Story Tab

Adds a story tab to the matches page which tells the story of the match.
I've added template strings in the lang file which will allow this to be converted into different languages.

Good job btw! 🦄

Seems to be a conflict to resolve

Not sure how to do timings for all of the events without looking super repetitive. I'm thinking maybe having the time just to the right of each event, just a bit faded out or something. Thoughts?

any more changes before release?


tmux config and instructions need to be worked out

tmux0 config and instructions need to be worked out.
There seem to be some subtle issues here, I have bash shell working 100%, but the tmux session, intiated by tmuxinator has not picked up all the correct shims and settings.  E.g the bundler plugin would be a reasonable minimal use case to show works.
For easier configuration see tmuxinator1

I don't know what tmuxinator is.

I've clarified - consider reopening?

ensure that tmux is creating shells that are the same in type (login, interactive) as without.
Inside tmux your shell should be more or less the same, so as long as PATH is set the the init is called it's very doubtful to be an rvenv issue.


'There is more than one profile' while tring to export

Hello,
I tried to export doing this command :
ffpass export -t passwords.csv -d . -v
The output was :
There is more than one profile
I run Python 3.7.4 on windows 10 and firefox 69.0.1 (64-bit)

I think -d . is incorrect. What happens without this option?

ffpass export -t passwords.csv -v
result :
There is more than one profile
usage: ffpass export [-h] [-t TO_FILE] -d DIRECTORY [-v]
ffpass export: error: the following arguments are required: -d/--directory/--dir

-d/--directory/--dir  seems mandatory

Then you need to locate your profile directory: https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data

I did
ffpass export -t passwords.csv -v -d <profile_dir_path>
it worked, thanks.


Aarch64 macOS trap on vld1q

When building a more complex app with NEON intrinsics, I get a runtime trap on vld1q_s32. I did some searching and could not find a tracking issue upstream for this in Cranelift. I additionally tried RUSTFLAGS= "target-feature=-neon" to no avail.
trap at Instance { def: Item(DefId(2:41824 ~ core[8ff7]::core_arch::arm_shared::neon::generated::vld1q_s32_x2)), args: [] } (_ZN4core9core_arch10arm_shared4neon9generated12vld1q_s32_x217hbeca48d3375ec01eE): llvm.aarch64.neon.ld1x2.v4i32.p0i32

While I understand it is not a priority, if I could be pointed to where this set of instructions is being tracked in cranelift I would much appreciate it.

The general tracking issue for this is https://github.com/rust-lang/rustc_codegen_cranelift/issues/171, but I keep issues for individual intrinsics open too. By the way do you know which crate uses this intrinsic? You should be able to get a backtrace with a debugger.

    frame #0: 0x00000001071f2808 game`_$LT$$RF$mut$u20$W$u20$as$u20$core..fmt..Write..write_fmt..SpecWriteFmt$GT$::spec_write_fmt::h6a3c139bdf9273a6 at mod.rs:444:32
   thread #12, name = 'Compute Task Pool (4)', stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
     frame #0: 0x00000001071f2808 game`_$LT$$RF$mut$u20$W$u20$as$u20$core..fmt..Write..write_fmt..SpecWriteFmt$GT$::spec_write_fmt::h6a3c139bdf9273a6 at mod.rs:444:32
 Target 0: stopped.

With opt-level=0 on LLVM, I do not see that intrinsic used. It seems to get emitted regardless of optimization settings on Cranelift.
I was able to trace this trap back to the crate, zune-jpeg. It has a default feature for neon that I can disable until neon support is more mature.
Thanks again for all your help!


chore(buildpacks): update go, php, nodejs, python, and scala buildpacks

See
https://github.com/heroku/heroku-buildpack-go/compare/v41...v42
https://github.com/heroku/heroku-buildpack-php/compare/v107...v108
https://github.com/heroku/heroku-buildpack-nodejs/compare/v90...v91
https://github.com/heroku/heroku-buildpack-python/compare/v80...v81
https://github.com/heroku/heroku-buildpack-scala/compare/v70...v71

I've tested all these against the respective deis example apps.


[Relay] add: 1d-interpolate relay op

Upstream this op from the original PR by @alexwong .
Add a 1d-linear interpolate (same function as np.interp)

@masahi , could you help to take a look at this PR?


3/26/2019 Publish

OPS Build status updates of commit c46dd66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/batch-ai.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview)

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.


Setup user-agent string for Python

#2370 introduced core API's for user agent string manipulation.
Each language should ensure that it adds a channel argument with key= GRPC_ARG_PRIMARY_USER_AGENT_STRING (in grpc.h) and a value as defined in https://github.com/grpc/grpc-common/blob/master/PROTOCOL-HTTP2.md.
For example, Ruby release 1.2.3 would set it to "grpc-ruby/1.2.3"

Implementations would be encouraged to ensure that the version string does not need to be set in many different places.

@soltanmm, I think this is very separable from everything else that we're doing. The version number is currently encoded in setup.py, right? Is there a way to make it accessible from inside the code? What if we moved it into the code itself; could setup.py find it there?
I think the legacy libraries do something smart with not-replicating-the-version-number-thither-and-yon; we may want to follow what they do.

First thing that comes to mind is having setup.py generate a file at build-time and place it in the package tree (as things are similarly done e.g. in 'configure' steps of lotsa libs). Alternatively, it should be possible for setup.py to find files in the package tree (it certainly can find them just about anywhere else).
I'm weakly against the idea of putting the version number anywhere else but setup.py, as that's where the other bits of our metadata go and where most projects seem to put their project metadata.


Fix: CharacterCount component not resetting red error text after valid input

Fixes bug #463 where error class is assigned correctly when user inputs more than expected characters into CharacterCount component but didn't get removed.
Triggers error:

Resets error class when user corrects input:

Hi @nikkialgar thanks a lot for your PR. Unfortunately, I just tried it and I can still see some behavior that is not correct. One of the tests I did is to go over the limit and then select all the text and delete it. The counter reset back but the color of the text is still red

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (b368e20) 100.00% compared to head (7de37a3) 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##           release/0.8      #471   +/-   ##
=============================================
  Coverage       100.00%   100.00%
=============================================
  Files               61        61
  Lines             1202      1203    +1
  Branches           457       458    +1
=============================================
+ Hits              1202      1203    +1

Impacted Files
Coverage Δ

src/characterCount/CharacterCount.tsx
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hi @daniele-zurico, I have fixed the bug; please review in your time


Tile place shortcut

          Looks great thanks for adding these shortcuts!

If you're interested in getting even fancier with it you could also add shortcuts for placing tiles. The backend actually returns a complete list of valid tile place locations in the targets list so it could look something like press p > all valid placement locations light up with a number > press corresponding number > tile is placed. This is beyond the scope of this PR but could be a cool interaction if you're ever interested in adding that as well.
Originally posted by @freglyc in https://github.com/quibbble/carcassonne/pull/11#pullrequestreview-1807232593

Yea i already imagined something like that and searched for methods in the drag and drop library (dnd-kit) for automatically picking up the tile and having it at the mouse cursor without moving the mouse to get the tile.
So far i just found, that this library works with arrow keys to move the tile with the keyboard if the DraggableToken has a tabindex (test commit)


upload_fileobj types in S3Client are wrong.

    def upload_fileobj(
        self,
        Fileobj: FileobjTypeDef,
        Bucket: str,
        Key: str,
        ExtraArgs: Dict[str, Any] = ...,
        Callback: Callable[..., Any] = ...,
        Config: TransferConfig = ...,
    ) -> None:

This function contradicts to
S3.Client.upload_fileobj(Fileobj, Bucket, Key, ExtraArgs=None, Callback=None, Config=None)

meaning ExtraArgs, Callback, Config is not optional in stub files, thus leading to errors. Latest version of stubs, boto3, everything.

Thank you for the report.
Yes, looks like this function is injected by boto3, so it should be manually annotated. I will release a fix this week.

Fix in the latest release. Please update to mypy-boto3-s3 1.28.27 and let me know if it works as it should.

@vemel it works as expected now. thanks matey!


[Bug]: TypeError: kill() missing 1 required positional argument: 'self'

What happened?

I keep getting this error when i run the colab for the first time, everytime
I was using the stable version of the Meina_V8 model colab
Console logs
Traceback (most recent call last):
  File "/content/stable-diffusion-webui/launch.py", line 362, in <module>
    start()
  File "/content/stable-diffusion-webui/launch.py", line 356, in start
    webui.webui()
  File "/content/stable-diffusion-webui/webui.py", line 240, in webui
    app.add_middleware(GZipMiddleware, minimum_size=1000)
  File "/usr/local/lib/python3.9/dist-packages/starlette/applications.py", line 139, in add_middleware
    raise RuntimeError("Cannot add middleware after an application has started")
RuntimeError: Cannot add middleware after an application has started
Error in atexit._run_exitfuncs:
TypeError: kill() missing 1 required positional argument: 'self'

Is there an existing issue for this?

[X] I have searched the existing issues and checked the recent builds/commits

Are you using the latest version of the colab notebook?

[X] Yes, i am using the latest version from the repo

Which colab notebook did you use?
Miena_V8
Which repo branch did the colab you use comes from ?
stable
Which tunnel did you use ?
--multiple
What browsers do you use to access the WebUI ?
Mozilla Firefox

seems somehow the WEBAPI version is wrongly installed to 0.95, try this fix:
find "!sed -i -e 's/fastapi==0.90.1/fastapi==0.89.1/g' /content/stable-diffusion-webui/requirements_versions.txt" in run.ipynb, and replace it with
"#!sed -i -e 's/fastapi==0.90.1/fastapi==0.89.1/g' /content/stable-diffusion-webui/requirements_versions.txt
!pip install --upgrade --force-reinstall fastapi==0.90.1"

seems somehow the WEBAPI version is wrongly installed to 0.95, try this fix: find "!sed -i -e 's/fastapi==0.90.1/fastapi==0.89.1/g' /content/stable-diffusion-webui/requirements_versions.txt" in run.ipynb, and replace it with "#!sed -i -e 's/fastapi==0.90.1/fastapi==0.89.1/g' /content/stable-diffusion-webui/requirements_versions.txt !pip install --upgrade --force-reinstall fastapi==0.90.1"

Works perfectly now, thank you!

Hi @ClownOfMadness 👋 thanks ❤ fixed


Verus integration

Mariposa has gone through some major refactoring, which should incorporate an updated version of this functionality now.

Mariposa has gone through some major refactoring, which should incorporate an updated version of this functionality now.


[Info.plist] Update version number to 0.90.6

Closes https://github.com/realm/realm-cocoa/issues/1542.
\c @tgoyne

There's two plists that need to be updated. sh build.sh set-version 0.90.6 updates both of them.

@tgoyne thanks, fixed

:+1:

Can one of the admins verify this patch?


RuntimeError: User specified an unsupported autocast device_type 'mps'

When trying the model on a m1 with the webview I get the following error: RuntimeError: User specified an unsupported autocast device_type 'mps'
$ python -m detikzify.webui --light

Running on local URL:  http://<IP_ADDRESS>:7860

To create a public link, set `share=True` in `launch()`.
/Users/robin/IdeaProjects/playground/venv/lib/python3.12/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
You are using a model of type detikzify to instantiate a model of type . This is not supported for all configurations of models and can yield errors.
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
....
RuntimeError: User specified an unsupported autocast device_type 'mps'

According to this post (https://github.com/oobabooga/text-generation-webui/issues/5695#issuecomment-1992717978) this is a issue with transformers==4.38.2
pip show transformers
Name: transformers
Version: 4.38.2
Summary: State-of-the-art Machine Learning for JAX, PyTorch and TensorFlow
Home-page: https://github.com/huggingface/transformers
Author: The Hugging Face team (past and future) with the help of all our contributors (https://github.com/huggingface/transformers/graphs/contributors)
Author-email<EMAIL_ADDRESS>License: Apache 2.0 License
Location: /Users/robin/IdeaProjects/playground/venv/lib/python3.12/site-packages
Requires: filelock, huggingface-hub, numpy, packaging, pyyaml, regex, requests, safetensors, tokenizers, tqdm
Required-by: detikzify

Installing 4.38.1 fixes the issues and I can run the model (Very slowly):
pip install "transformers==4.38.1"

Thanks for the report! Related to #1, seems to be bug in transformers. Maybe we can just pin the transformers version to 4.38.1 for now.


[PdrDashboard, v0.2] Allow user predictoor addresses configuration

Target
Allow user to configure default predictoor addresses and easily see data based on that
To do

[x] allow user to specify own predictoor addresses by a new "my_addresses" section inside "predictoor_ss" of ppss.yaml file
[x] when dashboard is started and "my_addresses" are set, make the predictoor addresses inside the table and all the corresponding feeds selected( this will calculate and show the data for predictoors )
[x] add a button called "My Predictoors" which resets the tables selected values to the predictoors from ppss.yaml, just like when the app is first started

@KatunaNorbert I realised I initially marked #1403 as "work on" because it was before you merged the feed switch. Combined, I think the functionality now works as expected and we can close this issue. Can you confirm?

Yes, we can close it


possible new johnoliver sub: r/AccidentalRenaissance

Poll results posted yesterday, today has seen some really nice artwork posted.

thanks so much /gen for flagging this sub! the artwork there is really something (in a good way), and i’m glad it’s going on the list.
annoyingly my bot didn’t pick up on it (because the post announcing the results wasn’t stickied), so thanks again for manually flagging. i’ll add a label to this issue to hopefully remind me to check in on it every so often (to make sure it’s still sticking to the john oliver theme).
anyway. CONFIRMED JOHNOLIVERIFIED

relevant part of the post for posterity:

You voted, we listened. We are now accepting photos of John Oliver, and the names "John" or "Oliver" must be somewhere in the title.
The photos can be as Renaissance as you like, from photoshops like the banner image, or AI, or just slap an oil paint filter on it. Or don't. Honestly, as long as John Oliver is in it? And it isn't NSFW? You're golden.
If you came to the comment section to ask why the hell we're accepting photos of John Oliver:
We took a vote and "Reopen the sub and only accept photos of John Oliver" was overwhelmingly the top choice. We on the mod team might be "landed gentry," but we believe in democracy.


Use webpack-dev-middleware or similar?

From @glebec on February 24, 2017 6:29
This can improve the build process by making refreshes wait for builds to recompile before serving the updated bundle. Since the bundle is compiled in memory and not written to a file (in dev mode), it is also faster to generate.
Alternatively, but probably more confusingly for students, webpack-dev-server can proxy the Bones API backend.
Hot Module Replacement is awesome but requires people write the frontend of their project in a compatible way, so I don't think we need to take this feature into account when it comes to deciding Bones's build system.
However, incorporating some form of LiveReload may be a nice touch. There isn't any one canonical way to do so, though you can see some notes / one potential approach here.
Copied from original issue: queerviolet/bones#22

You know, looking more into it, I think that activating HMR for Bones might not be too tricky after all — not requiring further knowledge or special action by students. https://webpack.js.org/guides/hmr-react/
If so, this would beat LiveReload by a mile. I'm definitely going to do a proof of concept and see how it works out.

About the refresh-wait and in-memory builds: doesn't seem high priority but I like it! Is there something we have to / should do to disable it in production?

Yes, we can do a dynamic check based on NODE_ENV which will add the middleware or not accordingly. The precise details I haven't worked out, but the middleware is explicitly intended to be dev-only so one would imagine it shouldn't be too hard to disable in production.

About the proxy: are there any benefits to this?

Eh, not really. I'm leaning away from webpack-dev-server which is too "magical" for my tastes and apparently has known issues with Node 7 besides.

Live reloading: love this idea. All for it.

Yeah, it's something I'll look into.

From @omriBernstein on February 24, 2017 21:16
About the refresh-wait and in-memory builds: doesn't seem high priority but I like it! Is there something we have to / should do to disable it in production?
About the proxy: are there any benefits to this?
Live reloading: love this idea. All for it.

Started researching HMR but it was proving tricky in practice. Want to keep at it but for now https://github.com/FullstackAcademy/bones/commit/fa55bcf6767ddbf247a26dbeb38878147013c4d6 implements LiveReload support.


Chips

Hey @acburst, would you like to check my chips javascript / api functionality? I need to incorporate tests and other stuff. Tell me if you think that i am going well.

I think you have to clean your pull request, 243 commits it's huge. Save your work, re-fork the repository and do a new PR with only changed files.

hey @TyrionGraphiste np! I will do it this night

Looks promising. Will review this when its cleaned up!