Add tests for helptags command and substitute in Ex mode

Appears to fail on FreeBSD:
Failures:
From test_help.vim:
Found errors in Test_helptag_cmd():
function RunTheTest[40]..Test_helptag_cmd line 17: command did not fail: helptags Xdir
function RunTheTest[40]..Test_helptag_cmd line 22: command did not fail: helptags Xdir

Hi Bram,
On Sun, Feb 2, 2020 at 1:28 PM Bram Moolenaar<EMAIL_ADDRESS>wrote:

Appears to fail on FreeBSD:
Failures:
From test_help.vim:
Found errors in Test_helptag_cmd():
function RunTheTest[40]..Test_helptag_cmd line 17: command did not fail:
helptags Xdir
function RunTheTest[40]..Test_helptag_cmd line 22: command did not fail:
helptags Xdir

I am not sure why the test fails only on FreeBSD. I am not able to
reproduce this failure
on my local FreeBSD setup.

Yegappan

Codecov Report

Merging #5567 into master will decrease coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5567      +/-   ##
==========================================
- Coverage   82.93%   82.81%   -0.13%
==========================================
  Files         137      137
  Lines      151835   149206    -2629
==========================================
- Hits       125927   123562    -2365
+ Misses      25908    25644     -264

Impacted Files
Coverage Δ

src/libvterm/src/unicode.c
82.6% <0%> (-6.53%)
:arrow_down:

src/search.c
81.29% <0%> (-0.83%)
:arrow_down:

src/gui.c
62.91% <0%> (-0.73%)
:arrow_down:

src/mouse.c
76.07% <0%> (-0.72%)
:arrow_down:

src/screen.c
83.92% <0%> (-0.71%)
:arrow_down:

src/move.c
86.9% <0%> (-0.68%)
:arrow_down:

src/profiler.c
94.03% <0%> (-0.65%)
:arrow_down:

src/ops.c
89.05% <0%> (-0.62%)
:arrow_down:

src/scriptfile.c
89.65% <0%> (-0.56%)
:arrow_down:

src/debugger.c
93.58% <0%> (-0.53%)
:arrow_down:

... and 111 more

Continue to review full report at Codecov.

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


[Feature Request]: Auto-cancel old Actions Runs

What would you like to happen?
Right now, our actions runs deal with long queues on a pretty much daily basis. Part of the reason for this is that if you make 5 commits in quick succession, 5 sets of workflow runs are queued and it takes a long time to work through all of them.
We can work around this by auto-canceling outdated runs. We're already doing this in Tour of Beam and it should be generalizable to the rest of the repo (or at least the workflows that are queued based on pull request pushes).
For reference, auto cancel docs: https://docs.github.com/en/enterprise-cloud@latest/actions/using-jobs/using-concurrency#example-using-concurrency-to-cancel-any-in-progress-job-or-run
Issue Priority
Priority: 2
Issue Component
Component: build-system

@Abacn do you have the bandwidth to take this on? I think it could be a really impactful small change if it can alleviate the build queue times. If not, I'll either take it on or find someone else.

.take-issue

Since doing this, our average queue has gone way down - previously it was consistently hovering around 2+ hours at this point in the day; currently it is around half an hour. Thanks for doing it @Abacn


Add prop for custom maxRippleOpacity

@timomeh :
A curious, why the rippleColor to as maxRippleOpacity 0.12?
For performance reasons or do not know so?

I can take care of this issue if it's still of interest. @timomeh thoughts?

Sure! That would be awesome

I am currently (at this moment) doing a big refactor/rewrite of the whole BottomNavigation. I'll include this feature in the upcoming version.

Closed with v1.0.0 🎉


Azure Pipeline shallow fetch =1 by default

Newly created pipelines now have shallow fetch enabled and set to 1 by default:

Not sure since when this happens, but... perhaps it would be useful to mention it in this documentation?
I also opened this issue here: https://github.com/MicrosoftDocs/azure-devops-docs/issues/12732

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

ID: b28abf7f-ecdf-8037-acd9-722690424372
Version Independent ID: b28abf7f-ecdf-8037-acd9-722690424372
Content: steps.checkout definition
Content Source: content/steps-checkout.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

Closing as duplicate of https://github.com/MicrosoftDocs/azure-devops-docs/issues/12732.
cc @steved0x for awareness

This has been added to the documentation and should be live shortly.
https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/steps-checkout?view=azure-pipelines#remarks
https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/azure-repos-git?view=azure-devops&tabs=yaml#shallow-fetch
Thank you for letting us know.


⚠ Bofrost.at has degraded performance

In befbf72, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2610 ms

Resolved: Bofrost.at performance has improved in 5154c1f.


Inference time increases with custom model training.

Compare to base model that i use for transfer learning, the model i extracted increases inference time after custom object training. is it th normal behaviour

Hi @asguradian, this repo relies on a dated version of the TensorFlow api. We've moved to a more future proof version here: https://github.com/cloud-annotations/training
I encourage you to try it out and reopen this issue there if you are still running into problems


[google_sign_in] on flutter web not popping up

Goal
I try to implement a signIn with Google in Flutter Web. I use GoogleSignn 4.1.1 and Firebase Auth 0.15.4. I do not get any error message. It just does not pop up.
What I did

I registered the web app in Firebase (Added Dependencies) and even added the <meta> Tag with the google-signin-client_id
The Firebase Auth with Google works when I run it on Android
I also ran the Example App from GoogleSignIn in Web. It also does not pop up.

This is my Login Code (Works on Android) (it does not output "alreadyLoggedIn" btw)
    final FirebaseAuth _auth = FirebaseAuth.instance;
    FirebaseUser user = await _auth.currentUser();
    if (user != null) {
      log.d('alreadyLoggedIn');
    } else {
      final GoogleSignIn _googleSignIn = GoogleSignIn(clientId: Constants.GOOGLE_SIGN_IN_CLIENT_ID);
      final GoogleSignInAccount googleUser = await _googleSignIn.signIn();
      final GoogleSignInAuthentication googleAuth =
          await googleUser.authentication;
      final AuthCredential credential = GoogleAuthProvider.getCredential(
        accessToken: googleAuth.accessToken,
        idToken: googleAuth.idToken,
      );
      await _auth.signInWithCredential(credential);
      user = await _auth.currentUser();
      assert(user.email != null);
      assert(user.displayName != null);
      assert(!user.isAnonymous);
      assert(await user.getIdToken() != null);
    }
    return user;
    }

Here is output of flutter doctor -v
[✓] Flutter (Channel beta, v1.14.6, on Linux, locale en_US.UTF-8)
• Flutter version 1.14.6 at /home/user/bin/flutter
• Framework revision fabeb2a16f (3 weeks ago), 2020-01-28 07:56:51 -0800
• Engine revision c4229bfbba
• Dart version 2.8.0 (build 2.8.0-dev.5.0 fc3af737c7)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /home/user/Android/Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.3
• Java binary at: /home/user/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/191.6010548/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at google-chrome
[✓] Android Studio (version 3.5)
• Android Studio at /home/user/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/191.6010548
• Flutter plugin version 43.0.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.3)
• IntelliJ at /home/user/.local/share/JetBrains/Toolbox/apps/IDEA-U/ch-0/193.6015.39
• Flutter plugin version 43.0.3
• Dart plugin version 193.6015.53
[✓] Connected device (2 available)
• Chrome     • chrome     • web-javascript • Google Chrome 80.0.3987.106
• Web Server • web-server • web-javascript • Flutter Tools
• No issues found!

Hi @SteinFluss
Could you please provide flutter run --verbose and try to log in?
Thank you

Sure, here it is:
flutter run -d chrome --verbose
[  +17 ms] executing: [/home/user/bin/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +16 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] fabeb2a16f1d008ab8230f450c49141d35669798
[        ] executing: [/home/user/bin/flutter/] git describe --match v*.. --first-parent --long --tags
[   +3 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[        ] v1.14.6-0-gfabeb2a16
[   +4 ms] executing: [/home/user/bin/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] executing: [/home/user/bin/flutter/] git ls-remote --get-url origin
[   +2 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +24 ms] executing: [/home/user/bin/flutter/] git rev-parse --abbrev-ref HEAD
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[  +16 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +15 ms] executing: /home/user/Android/Sdk/platform-tools/adb devices -l
[   +3 ms] Exit code 0 from: /home/user/Android/Sdk/platform-tools/adb devices -l
[        ] List of devices attached
[   +9 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +22 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +60 ms] Found plugin cloud_firestore at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.2+1/
[   +4 ms] Found plugin cloud_firestore_web at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.0+3/
[   +8 ms] Found plugin firebase_auth at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.15.4/
[   +1 ms] Found plugin firebase_auth_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[   +1 ms] Found plugin firebase_core at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.3+3/
[   +1 ms] Found plugin firebase_core_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[        ] Found plugin firebase_messaging at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-5.1.8/
[  +17 ms] Found plugin flutter_local_notifications at /home/user/.pub-cache/hosted/pub.dartlang.org/flutter_local_notifications-1.1.6/
[  +22 ms] Found plugin google_sign_in at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.1.1/
[   +1 ms] Found plugin google_sign_in_web at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.8.3/
[   +3 ms] Found plugin in_app_purchase at /home/user/.pub-cache/hosted/pub.dartlang.org/in_app_purchase-0.3.1/
[  +13 ms] Found plugin rate_my_app at /home/user/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.4.1/
[   +1 ms] Found plugin share at /home/user/.pub-cache/hosted/pub.dartlang.org/share-0.6.3+5/
[        ] Found plugin shared_preferences at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+1/
[        ] Found plugin shared_preferences_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+4/
[   +1 ms] Found plugin shared_preferences_web at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+3/
[   +8 ms] Found plugin url_launcher at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.1/
[        ] Found plugin url_launcher_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+2/
[        ] Found plugin url_launcher_web at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.0+2/
[  +99 ms] Found plugin cloud_firestore at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.2+1/
[   +1 ms] Found plugin cloud_firestore_web at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.0+3/
[   +5 ms] Found plugin firebase_auth at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.15.4/
[   +1 ms] Found plugin firebase_auth_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[        ] Found plugin firebase_core at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.3+3/
[        ] Found plugin firebase_core_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[        ] Found plugin firebase_messaging at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-5.1.8/
[   +5 ms] Found plugin flutter_local_notifications at /home/user/.pub-cache/hosted/pub.dartlang.org/flutter_local_notifications-1.1.6/
[   +5 ms] Found plugin google_sign_in at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.1.1/
[        ] Found plugin google_sign_in_web at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.8.3/
[   +2 ms] Found plugin in_app_purchase at /home/user/.pub-cache/hosted/pub.dartlang.org/in_app_purchase-0.3.1/
[   +7 ms] Found plugin rate_my_app at /home/user/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.4.1/
[        ] Found plugin share at /home/user/.pub-cache/hosted/pub.dartlang.org/share-0.6.3+5/
[        ] Found plugin shared_preferences at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+1/
[        ] Found plugin shared_preferences_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+4/
[        ] Found plugin shared_preferences_web at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+3/
[   +4 ms] Found plugin url_launcher at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.1/
[        ] Found plugin url_launcher_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+2/
[        ] Found plugin url_launcher_web at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.0+2/
[  +82 ms] Generating /home/user/prog/todo_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +58 ms] Launching lib/main.dart on Chrome in debug mode...
[        ] Building application for the web...
[ +233 ms] Found plugin cloud_firestore at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.2+1/
[        ] Found plugin cloud_firestore_web at /home/user/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.0+3/
[   +2 ms] Found plugin firebase_auth at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.15.4/
[        ] Found plugin firebase_auth_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[        ] Found plugin firebase_core at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.3+3/
[        ] Found plugin firebase_core_web at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[        ] Found plugin firebase_messaging at /home/user/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-5.1.8/
[   +2 ms] Found plugin flutter_local_notifications at /home/user/.pub-cache/hosted/pub.dartlang.org/flutter_local_notifications-1.1.6/
[   +2 ms] Found plugin google_sign_in at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.1.1/
[        ] Found plugin google_sign_in_web at /home/user/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.8.3/
[   +1 ms] Found plugin in_app_purchase at /home/user/.pub-cache/hosted/pub.dartlang.org/in_app_purchase-0.3.1/
[   +5 ms] Found plugin rate_my_app at /home/user/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.4.1/
[        ] Found plugin share at /home/user/.pub-cache/hosted/pub.dartlang.org/share-0.6.3+5/
[        ] Found plugin shared_preferences at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6+1/
[        ] Found plugin shared_preferences_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-0.0.1+4/
[        ] Found plugin shared_preferences_web at /home/user/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-0.1.2+3/
[   +4 ms] Found plugin url_launcher at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher-5.4.1/
[        ] Found plugin url_launcher_macos at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-0.0.1+2/
[        ] Found plugin url_launcher_web at /home/user/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-0.1.0+2/
[+5733 ms] Starting daemon...
[ +140 ms] Initializing inputs
[   +7 ms] Reading cached asset graph...
[ +291 ms] Reading cached asset graph completed, took 289ms
[ +213 ms] Checking for updates since last build...
[+1476 ms] Checking for updates since last build completed, took 1.5s
[   +6 ms] Initializing inputs
[   +1 ms] Reading cached asset graph...
[        ] Reading cached asset graph completed, took 289ms
[        ] Checking for updates since last build...
[        ] Checking for updates since last build completed, took 1.5s
[+1121 ms] About to build [web]...
[   +2 ms] Running build...
[+1031 ms] 1.0s elapsed, 2/5 actions completed.
[+1056 ms] 2.1s elapsed, 4/5 actions completed.
[ +879 ms] Running build completed, took 2.8s
[        ] Caching finalized dependency graph...
[   +5 ms] Caching finalized dependency graph completed, took 155ms
[   +5 ms] Succeeded after 3.0s with 8 outputs (6 actions)
[   +7 ms] Building application for the web... (completed in 12.2s)
[        ] Attempting to connect to browser instance..
[+3490 ms] Debug service listening on ws://<IP_ADDRESS>:36247/TNMnd9klJOI=
[ +411 ms]       Failed to load asset at path: packages/build_web_compilers/src/dev_compiler/dart_sdk.js.
                      Status code: 404

                      Headers:
                      {
                  "date": "Mon, 17 Feb 2020 14:22:09 GMT",
                  "content-length": "9",
                  "x-frame-options": "SAMEORIGIN",
                  "content-type": "text/plain; charset=utf-8",
                  "x-xss-protection": "1; mode=block",
                  "x-content-type-options": "nosniff",
                  "server": "dart:io with Shelf",
                  "via": "1.1 shelf_proxy"
                }

                      Content:
                      Not Found}

[  +42 ms] Attempting to connect to browser instance.. (completed in 3.9s)
[        ] Warning: Flutter's support for web development is not stable yet and hasn't
[        ] been thoroughly tested in production environments.
[        ] For more information see https://flutter.dev/web
[        ] 🔥  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
[        ] For a more detailed help message, press "h". To quit, press "q".
[   +4 ms] Debug service listening on ws://<IP_ADDRESS>:36247/TNMnd9klJOI=

Hi @SteinFluss
Did you add firebase config in your web/index.html
<body>
  <script src="https://www.gstatic.com/firebasejs/7.5.0/firebase-app.js"></script>
  <script src="https://www.gstatic.com/firebasejs/7.5.0/firebase-auth.js"></script>
  <your firebase config here>
  <script src="main.dart.js" type="application/javascript"></script>
</body>

Thank you

web/index.html looks like this:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="google-signin-client_id"
          content=""/>
    <title>Listly</title>
    <!-- The core Firebase JS SDK is always required and must be listed first -->
    <script src="https://www.gstatic.com/firebasejs/7.8.2/firebase-app.js"></script>
    <script src="https://www.gstatic.com/firebasejs/7.8.2/firebase-firestore.js"></script>
    <script src="https://www.gstatic.com/firebasejs/7.8.2/firebase-auth.js"></script>
    <script src="https://www.gstatic.com/firebasejs/7.8.2/firebase-analytics.js"></script>
    <script src="https://www.gstatic.com/firebasejs/7.8.2/firebase-messaging.js"></script>

    <script>
        // Your web app's Firebase configuration
        var firebaseConfig = {
            apiKey:
            authDomain:
            databaseURL:
            projectId:
            storageBucket:
            messagingSenderId:
            appId:
            measurementId:
        };
        // Initialize Firebase
        firebase.initializeApp(firebaseConfig);
        // firebase.analytics();
    </script>
    <script src="main.dart.js" type="application/javascript"></script>
</head>
<body>
</body>
</html>

I just removed the private fields

Also as i wrote, I tried to run the example App in chrome and it did not work either.

Hi, I have a successful experience with google sign in. Do you have any errors in your console?
Also please look on this ticket https://github.com/flutter/flutter/issues/49539 may be it will be helpful.

Thanks a lot for your help. I still could not make it work.

I looked at the ticket and tried to run it with:flutter run -d chrome --web-hostname localhost --web-port 8080
I set up the google console part like so: https://imgur.com/a/wFzZCVk
It still does not work and does not log any errors in the console

It turns out, I somehow did not correctly copy the client is. Works now. Thanks for all the help! I will close this now.


Oman kaupan ja tuotteen tiedot näkyvät hintalistauksen yläpuolella

Codecov Report

Merging #18 into dev will decrease coverage by 0.48%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             dev      #18      +/-   ##
=========================================
- Coverage   17.5%   17.02%   -0.49%
=========================================
  Files         15       15
  Lines        457      470      +13
  Branches      49       51       +2
=========================================
  Hits          80       80
- Misses       374      387      +13
  Partials       3        3

Impacted Files
Coverage Δ

...in/java/hifian/hintahaukka/ListPricesFragment.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


UI Slider Arrow Button Size Adjustment

Is there a way to increase the size of the of the arrow buttons for the sliders (horizontal and vertical) without just increasing the height or width of the entire slider? It was probably done like this so the arrow buttons remain square or circular, but that means thin sliders have tiny buttons.
Is this possible?

You can change the font size via theming:
"horizontal_scroll_bar.@arrow_button":
{
    "font":
    {
        "size": 32
    }
}

Though from my testing this doesn't work spectacularly well with very small sliders as the font line spacing gradually slides the actual text off the screen and padding makes the usable area even smaller. I think you'd be better with setting actual images (again via theming) for the arrows for very small sliders/scrollbars:
"horizontal_scroll_bar.#left_button":
{
    "images":
    {
        "normal_image": {
            "package": "data.images",
            "resource": "small_left_arrow.png"
        }
    }
}

I've added a PR here: #652
to make it easier to disable the text based arrows on a scrollbar or slider buttons (or set them to some other character).


Spelling fix

/check-enforcer override

/check-enforcer override

/azp run net - identity - ci

@pakrym:  Do you mind seeing if there's a member of the EngSys team around this week that can either clear the merge blockers or override and merge?   The license and check enforcer steps were triggered while the pipelines were experiencing issues and do not appear to be properly associated with this PR.


The test searches provided by teams exceeded the 1000 limit - could the user select the limit from some options possibly (1000, 2,500, 5000?)

Of the four test searches I tried (maybe not 100% accurately) two exceeded the limit (2,724 and 1,613)

Might also be worth making flag of limit hit even more obvious


Enable ITs

Enable members of trusted_for_ITs and any training group to see/use these tools.
There is also the option of using only the first commit from this and making the interactive tools open to everyone.

This has been vetoed.


Partially theme the integrated terminal, highlight self and cls in Python

Thank you for reviewing my PR!
I started using your theme earlier this week and found myself wanting a few additional things highlighted:
Partially theme the integrated terminal
Overriding ansiRed and ansiGreen makes git diffs more readable
Before:

After:

Overriding ansiBrightBlack makes command line flags more readable
Before:

After:

Highlight self and cls in Python
Before:

After:

Thank you for the contribution! I was meaning to get these done. I'll push out a release soon as well to distribute the changes 💃


Feature/divided compartments

Note: Includes PR #46 — resolve that PR first
New compartment info structure for FVM.

Make algorithm::sum, algorithm::mean more generic, allowing use with array types.
Add div_compartment compartment representation, that holds geometric information for each half of a compartment that will then be used in calculating control volumes.
Add three compartmentalisation schemes/policies that discretize a segment into div_compartment objects:

div_compartment_by_ends divides based only on the segment end points and radii.
div_compartment_sampler forms frusta by sampling the segment radius at each compartment boundary
div_compartment_integrator computes the compartment areas and volumes exactly by summing all frustra in the intersection of the segment and the compartment span.

Rebased on master.


Add command to spawn surgery tools around the player

About the PR
Because spawning them one by one gets annoying really fast.
Requires https://github.com/space-wizards/space-station-14/pull/3720
Requires https://github.com/space-wizards/space-station-14/pull/3719
Requires https://github.com/space-wizards/RobustToolbox/pull/1658

Make this a generalized command that takes in an EntityListPrototype ID and spawns all those entities around the player. Then you could do something like spawnlist SurgeryCommandToolsand anything could expand it.

Done in https://github.com/space-wizards/space-station-14/pull/3721/commits/4ed35ff4b5047d2caa50cda79cbcf08e003b3804, I expect the cow tools entity list prototype PR.


Issue 838: Use archives and Git LFS for proof sessions

Closes #838

The approach of using Git LFS has been discarded (cf. https://github.com/Componolit/RecordFlux/issues/838#issuecomment-965145011).


Imagefap ripper names folders poorly

Ripme version: 1.5.7
Java version:  1.8.0
Operating system:  Ubuntu 16.04
Exact URL you were trying to rip when the problem occurred: http://www.imagefap.com/pictures/5115649/Dominique and http://www.imagefap.com/pictures/3032731/Dominique
Please include any additional information about how to reproduce the problem:

Expected Behavior
The ripper should add the albums UID to the end folder name, so it doesn't download 2 different albums with the same name to the same folder
Actual Behavior
The ripper downloads both albums to the same folder

Fixed in release 1.5.9


Strange & incorrect assertion error after upgrade to 3.19.0

Summary
Upgrading from 3.16.1 to 3.19.0 causes strange assertion errors.
The test fails if it is ran like below. However, if you uncomment the sysout, the test is green. It works fine in AssertJ 3.16.1
To Reproduce:
package org.jobrunr.jobs.mappers;

import com.google.gson.Gson;
import com.google.gson.GsonBuilder;
import com.google.gson.TypeAdapter;
import com.google.gson.stream.JsonReader;
import com.google.gson.stream.JsonWriter;
import org.junit.jupiter.api.Test;

import java.io.File;
import java.io.IOException;
import java.nio.file.Path;
import java.nio.file.Paths;

import static org.jobrunr.JobRunrAssertions.assertThat;

public class AssertJTest {

    @Test
    void testIssue() {
        System.out.println(System.getProperty("java.version"));

        Gson gson = new GsonBuilder().registerTypeHierarchyAdapter(Path.class, new PathAdapter().nullSafe()).create();
        TestMetadata expectedMetadata = new TestMetadata("/tmp");

        String serializedMetadata = gson.toJson(expectedMetadata);
        TestMetadata actualMetadata = gson.fromJson(serializedMetadata, TestMetadata.class);

        // uncomment to make test succeed
        // System.out.println(actualMetadata.getPath());

        assertThat(actualMetadata).usingRecursiveComparison().isEqualTo(expectedMetadata);
    }

    public static class TestMetadata {
        private Path path;
        private File file;

        public TestMetadata(String dir) {
            this.path = Path.of(dir);
            this.file = new File(dir);
        }

        public Path getPath() {
            return path;
        }

        public File getFile() {
            return file;
        }
    }

    public static final class PathAdapter extends TypeAdapter<Path> {
        @Override
        public void write(final JsonWriter jsonWriter, final Path path) throws IOException {
            jsonWriter.value(path.toString());
        }

        @Override
        public Path read(final JsonReader jsonReader) throws IOException {
            return Paths.get(jsonReader.nextString());
        }
    }
}

there were a few breaking changes between 3.16 and 3.19 regarding the recursive comparison, see the release notes. Some of these breaking changes can be reverted (like calling usingOverriddenEquals  or Assertions.setExtractBareNamePropertyMethods(true);) try with these and see how it goes.
I haven't run your test case yet but I suspect actualMetadata.getPath() to have some side effects which change the values being compared.

there were a few breaking changes between 3.16 and 3.19 regarding the recursive comparison, see the release notes. Some of these breaking changes can be reverted (like calling usingOverriddenEquals  or Assertions.setExtractBareNamePropertyMethods(true);) try with these and see how it goes.
I haven't run your test case yet but I suspect actualMetadata.getPath() to have some side effects which change the values being compared.

Ok, thanks for the swift reply.
I'll read the release notes and get back at you.

Ok, thanks for the swift reply.
I'll read the release notes and get back at you.

solved by adding usingOverriddenEquals(). Sorry for the hassle.

solved by adding usingOverriddenEquals(). Sorry for the hassle.

no problem, happy to help.

no problem, happy to help.


Error Page Snippet

Hi @arufars
I would like to propone a new snippet to quickly create the error page, according to the official Next Docs
Error page
'use client' // Error components must be Client Components

import { useEffect } from 'react'

export default function Error({
  error,
  reset,
}: {
  error: Error
  reset: () => void
}) {
  useEffect(() => {
    // Log the error to an error reporting service
    console.error(error)
  }, [error])

  return (

Something went wrong!

      <button
        onClick={
          // Attempt to recover by trying to re-render the segment
          () => reset()
        }
      >
        Try again
      </button>

  )
}

Thank you for your suggestion!
I'm pleased to inform you that I have implemented the changes you proposed in my repository. The implementation I have made can be found here: arufars/snippet-next#error.
If you have any further questions or additional feedback, please don't hesitate to let me know.
Thank you for opening the issue 🚀


Enable using GPT timer as OS Timer on RT1xxx boards

This switches the default kernel timer from Systick to the GPT timer on NXP RT1xxx boards. Switching from Systick to the GPT timer will allow RT boards to enter deeper sleep states without the kernel timer stopping. GPT1 is used as the hardware timer, and must be enabled in the board's DTS file with status = "okay" to enable the timer driver

Adding DNM, as some tests are still failing on this PR that CI has not caught.

PR has been update to fix CI failures. One of the CI failures was due to a kernel test making an incorrect assertion, and I've added a change to this PR to fix it.
tests/kernel/threads/thread_apis checks k_busy_wait by delaying for 100us, then verifying the thread usage time has increased by at least 100us worth of hardware cycles.
However, the assertion used the macro zassert_true(dt >= k_cyc_to_us_floor64(100), NULL);, which is incorrect: this is comparing the elapsed cycles to the number of microseconds that pass in 100 cycles. For most fast hardware clocks, this assertion will pass, since very few microseconds pass in 100 cycles. However, for the 32KHz GPT clock this assertion will fail. The correct assertion is the following: zassert_true(dt >= k_us_to_cyc_floor64(100), NULL);

CI is failing because of a bug introduced by #40183, #41025 fixes the issue

Removing DNM label, as PR is now passing all CI tests internally


[Update] Remove unused environment value

Description
This PR removes the isSampleInfoViewVisible environment value as it is no longer used in the Sample Viewer.
Linked Issue(s)

NA (quick fix)

How To Test

Ensure the Sample Viewer builds as expected.

Thanks for catching this. The file should have been removed as part of this comment: https://github.com/Esri/arcgis-maps-sdk-swift-samples/pull/77#discussion_r1019730664 which I missed.


DRAFT: Failing test from pad team

This is a test from the PAD team. Currently fails.
We should understand why it fails, and either:

If it's an Fx bug --> fix it
If it's user error --> what's the "right" way to do this?

Cleared up by #551, now only RecordType is derivable. That should push folks in the right direction of using ToTable instead of constructing a derived TableType to wrap a record.


Multi-channel pick-up-tip "low_power_z" current must be higher than single-channel

overview
Because there are more tips to press into, the motor current being set on the Z or A axis during a low_power_z motion should be higher (preliminary tests found 0.3 amps works well for p300 multi-channel)

behavior
Right now, all calls to move using low_power_z set the current to 0.1 amps. This does not create enough force to properly seal with all 8 tips, cause some tips to fall off, or uneven volumes across the channels.
To accomplish this, the Pipette could determine the correct current in amps by using it's type or number of channels. Pipette could then set it's mount's motor current before and after motions along the Z axis.

steps to reproduce
Run a protocol on v3a using a multi-channel pipette

blocked by #565


Investigate post-processing effects (brightness, etc)

Some work completed in the next version, but more work in the future versions.

Thank you for the adjustments! That is a great start! Maybe Gamma would be useful as well but being able to dial in contrast and brightness gives such a better image!!! thank you thank you thank you! :)

Don't forget to someday consider inverse foveated blur as a complement to FR.


telling users they need to activate account when they try to login

after a user signs up, but haven't yet activated, an attempt to login will simply tell the user that the email/password was invalid. this is because login() seems to return nil when the activation state is pending, even though the provided email/pw is correct.
it would be nice with an easy way to send uses to a page telling them they still need to activate their account.

outdated


"init" has quite a number of bugs...

version of tsed - 3.20.12

selecting pnpm will fail many setups due to peer-dependancies. Use npm or yarn.
selecting "linter + lint on commit" will fail as the project does not do a "git init" or similar
selecting graphql generates wrong code in "src/config/index.ts" - no comma
the generated "package.json" file has bad "script" definitions for other than yarn. "npm run tsc" fails, should be just "tsc"
selecting all (besides "lint on commit" - see above) will fail to "build" with missing typescript declarations. Specifically: @types/inquirer, @types/fs-extra, @types/oidc-provider
When the above is fixed there are a number of errors that suggest incompatible libs/modules have been installed. I stopped here.

Hope this is not too terse, tried to keep it simple to reproduce.

Hello @alf5
Thanks for your feedback.

selecting pnpm will fail many setups due to peer-dependancies. Use npm or yarn.

PNPM is really unstable tool. While NPM and Yarn have a good peerdependencies resolution, PNPM doesn't seems to work as expected. I'm not responsible about this issue. I prefer to remove this option until, there is no people to maintain this feature.

selecting "linter + lint on commit" will fail as the project does not do a "git init" or similar

Sorry but, it's not a bug. If you select this options, you have to run the git init after. CLI isn't responsible to do that.
But it's not a problem, the project will be correctly generated.

When the above is fixed there are a number of errors that suggest incompatible libs/modules have been installed. I stopped here.
GraphQL is a bit complicated because, the module compatibility change every month... So, the solution is to not provide this options or fix the graphql version.

I'll try to fix the CLI for the graphql option
See you
Romain

Using NPM, husky is ok:

Fixed ;)


Getting white screen of death when using it with a DateTimeField

Hi there,
using this on a form and part of a DateTimeField on a 3.1.2 install and getting the white screen and this error in the logs,
Fatal error:  Call to a member function setForm() on a non-object in /home/sites/xxxxxxxxxxxxx/framework/forms/FieldList.php on line 436

Cheers
Mick

+1, experiencing this one also, though not particularly in a DateTimeField. any resolve on this? it is really frustrating to debug this kind of issues.

for the next one who might experience this, the cause of the problem is maybe you've chained your field which returns a non field object and being passed in your field list. happens to me when i try to chain getValidator.


Implement feature flag that will allow us to deploy site to production URL early

We need to do as much upfront work as possible to make the site available on the public URL without actually allowing people to access the site before the official launch date.

Closing this as no longer needed.


Add MockBukkitException

Description
Adds a new type of exception, MockBukkitException. This can be used as a general exception when a more specific RuntimeException isn't available.
This also removes the ReflectionAccessException implemented in #811 since it's located in the wrong class, and the new exception will do just fine.
Checklist
The following items should be checked before the pull request can be merged.

[x] Code follows existing style.
[ ] Unit tests added (if applicable).

Not really the biggest fan of just replacing one Generalized Exception with another one without adding anything to it really. I would either go for static Instances of the Exception in the Mockbukkit exception for different cases or just implement the Special Exceptions on top of RuntimeException


Provide common test helpers.

As mentioned in #386, it would be nice to be able to reuse the stream test pattern (cf. #339) across modules. Currently metamorph and metafacture-mangling make use of it, plus metafacture-yaml once #400 is accepted. There are more candidates that could potentially benefit from it.
I'd like to propose metafacture-test as a new module, with org.metafacture.test.StreamTestHelpers (or maybe org.metafacture.test.helpers.StreamTest) as a starting point. There's always the possibility to extract more test patterns in the future.
It would be a testImplementation dependency for the aforementioned modules.
Would something like this be acceptable? (See also the brief discussion in #386.)
P.S.: While at it, it might make sense to configure test logging (showStandardStreams = true and exceptionFormat = 'full') globally for all subprojects. Unwanted output should be suppressed or otherwise dealt with.
org.metafacture.flowcontrol.ObjectExceptionCatcherTest > shouldCatchException STANDARD_ERROR
    [Test worker] ERROR org.metafacture.flowcontrol.ObjectExceptionCatcher - 'Exception Message' while processing object: data

org.metafacture.flowcontrol.ObjectThreaderTest > shouldSplitAllObjectsToAllThreadedDownStreamReceivers STANDARD_ERROR
    [Test worker] INFO org.metafacture.flowcontrol.ObjectThreader - Adding thread 1
    [Test worker] INFO org.metafacture.flowcontrol.ObjectThreader - Adding thread 2

org.metafacture.json.JsonDecoderTest > testShouldProcessRecordsInArrayRoot STANDARD_ERROR
    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
    SLF4J: Defaulting to no-operation (NOP) logger implementation
    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

org.metafacture.monitoring.StreamLoggerTest > shouldActAsSinkIfNoReceiverIsSet STANDARD_ERROR
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - start record 1
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - start entity entity
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - literal literal=value
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - end entity
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - end record
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - resetStream
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - closeStream

org.metafacture.monitoring.StreamLoggerTest > shouldForwardAllReceivedEvents STANDARD_ERROR
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - start record 1
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - start entity entity
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - literal literal=value
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - end entity
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - end record
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - resetStream
    [Test worker] DEBUG org.metafacture.monitoring.StreamLogger - closeStream

org.metafacture.monitoring.ObjectTimerTest > testShouldHandleImmediateCloseStreamWithNoProcessing STANDARD_ERROR
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Executions: 0; Cumulative duration: 0s; Average duration: 0s
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Time to close stream:  14µs 965ns

org.metafacture.monitoring.ObjectTimerTest > testShouldMeasureExecutionTime STANDARD_ERROR
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 1: 150ms 138µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 2: 20ms 82µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 3: 30ms 130µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 4: 202ms 164µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Executions: 4; Cumulative duration: 402ms 515µs; Average duration: 100ms 629µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Time to close stream:  6µs 170ns

org.metafacture.monitoring.StreamTimerTest > testShouldHandleImmediateCloseStreamWithNoProcessing STANDARD_ERROR
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Executions: 0; Cumulative duration: 0s; Average duration: 0s
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Time to close stream:  1µs 470ns

org.metafacture.monitoring.StreamTimerTest > testShouldMeasureExecutionTime STANDARD_ERROR
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 1: 150ms 242µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 2: 20ms 149µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 3: 30ms 123µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Execution 4: 202ms 170µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Executions: 4; Cumulative duration: 402ms 685µs; Average duration: 100ms 671µs
    [Test worker] INFO org.metafacture.monitoring.TimerBase - Time to close stream:  5µs 111ns

org.metafacture.metamorph.test.validators.StreamValidatorTest > shouldFailIfEndRecordEventIsMissing STANDARD_ERROR
    [Test worker] INFO org.metafacture.metamorph.test.validators.StreamValidator - Event Stream: 1{}

Maybe also print Morph/Fix script on failure.

As these scripts can comprise several thousand lines a snippet would be fine.

As these scripts can comprise several thousand lines

Not usually in tests, though, right? Those are (almost?) always small scripts with the minimum number of instructions required for the particular test.

BTW: This idea was inspired by the Metafix test helper, only limited to test failures so it wouldn't clutter the regular test output.

Ah, right, sorry, of course - it's about tests ... so just ignore my comment :)

configure test logging (showStandardStreams = true and exceptionFormat = 'full') globally for all subprojects.

Already done in #417.


python3Packages.pyrender: init at 0.1.45

Description of changes
PyRender is really nice to have when working with 3D triangle meshes and point clouds.
This pr also does a fixup of pyopengl, possibly fixing #217275.
The deleted check works when build without sandbox on nixos.

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This force-push adds some pyopengl fixes, possibly fixing #217275.

Rebased on top of #79154
I check if the pyopengl fix was still needed, and it is.

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

1 package failed to build:

ib-controller

72 packages built:

friture
friture.dist
gnss-sdr
gnuradio
gnuradio3_9
gnuradioMinimal (gnuradio3_9Minimal)
gnuradio3_9Packages.gnuradio
gnuradio3_9Packages.grnet
gnuradio3_9Packages.osmosdr
gnuradio3_9Packages.osmosdr.dev
gnuradioPackages.gnuradio
gnuradioPackages.osmosdr
gnuradioPackages.osmosdr.dev
gqrx
gqrx-gr-audio
gqrx-portaudio
inkcut
inkcut.dist
inkscape-extensions.inkcut
mnemosyne
mnemosyne.dist
mymcplus
mymcplus.dist
napari (python310Packages.napari)
napari.dist (python310Packages.napari.dist)
opcua-client-gui
opcua-client-gui.dist
plots
plots.dist
printrun
printrun.dist
python310Packages.binwalk-full
python310Packages.binwalk-full.dist
python310Packages.boxx
python310Packages.boxx.dist
python310Packages.bpycv
python310Packages.bpycv.dist
python310Packages.enamlx
python310Packages.enamlx.dist
python310Packages.pyopengl
python310Packages.pyopengl.dist
python310Packages.pyqtgraph
python310Packages.pyqtgraph.dist
python310Packages.pyrender
python310Packages.pyrender.dist
spyder (python310Packages.spyder)
spyder.dist (python310Packages.spyder.dist)
python310Packages.stytra
python310Packages.stytra.dist
python310Packages.zcs
python310Packages.zcs.dist
python311Packages.binwalk-full
python311Packages.binwalk-full.dist
python311Packages.enamlx
python311Packages.enamlx.dist
python311Packages.pyopengl
python311Packages.pyopengl.dist
python311Packages.pyqtgraph
python311Packages.pyqtgraph.dist
python311Packages.pyrender
python311Packages.pyrender.dist
python311Packages.spyder
python311Packages.spyder.dist
run-scaled
steamos-devkit
steamos-devkit.dist
tribler
video2midi
xpra
xpra.dist
xpraWithNvenc
xpraWithNvenc.dist

This force-push:

switch to disabledTestPaths
switch to pythonRelaxDepsHook
preprend env. to PYOPENGL_PLATFORM
checkInputs -> nativeCheckInputs

@ofborg build python310Packages.pyrender python311Packages.pyrender
@ofborg build python310Packages.pyopengl python311Packages.pyopengl

This force push:

rebase on master
revert pythonRelaxDepsHook

Is it just me, or is pythonRelaxDepsHook flaky?
@ofborg build python310Packages.pyrender python311Packages.pyrender
@ofborg build python310Packages.pyopengl python311Packages.pyopengl


Attempting to handle non-array data in errormessage function

Getting an error that data.map is not a function. Suspect that this is due to the data field not being passed in as an array in certain cases. Threw some quick logic around it to only map if it is an array.

Not needed anymore.


Fix sdk v3

:tada: This PR is included in version 3.5.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Stack offset highlighting doesn't work for different instructions

If you click on a particular stack offset, objdiff highlights other instances of that offset for similar instructions (e.g. stfs/lfs) as expected:

However, it misses instances that are for a completely different instruction (e.g. addi doesn't highlight lfs and lfs doesn't highlight addi):

Example function: dLib_checkActorInCircle
Versions tested on: 0.5.2, 0.6.0

Thanks for the report! I fixed this by comparing signed immediates and register offsets and considering them equivalent. If there are other instances where the highlight doesn't pick up things that it semantically should, please let me know.


feat(portal): adding portal package

Closes
DES-90
Changelog
New

Adding portal package

Notes
Being a utility component I'm going to forego adding a story for this component.
Definition of done

[ ] Development completed
[ ] Reviewers assigned
[ ] Unit and integration tests
[ ] Meets minimum browser support
[ ] Meets accessibility requirements
[ ] Changeset added

Being a utility component I'm going to forego adding a story for this component

How might we inform customers of this utility component then? What are your thoughts with DSW?

We could document it, but more than likely this will be used as a building block for other components. I didn't think about the API documentation thought. I guess we would make a story for it.


fix: update example runtimes

Resolve mismatch between builder runtime version and example versions, which was causing incompatibility issues with builder sites that were created with images.

Looks good, but how come we're doing 0.11.4 when the latest version is 0.11.19?

Consistency - since Alan just bumped to 0.11.4 in the typescript example, I wanted all examples to be consistent with that. I could just bump everything (except bigcommerce) to be 0.11.19. Any preferences?

Looks good, but how come we're doing 0.11.4 when the latest version is 0.11.19?

Consistency - since Alan just bumped to 0.11.4 in the typescript example, I wanted all examples to be consistent with that. I could just bump everything (except bigcommerce) to be 0.11.19. Any preferences?

Let's bump them all to 0.11.19. We should have all examples be up to date with the latest version of the runtime.
Also, how come we're no updating the BigCommerce example? Is that build failing as a result of the update? Given the error I'd assume that the example is broken independent of the runtime version being used.

Sounds good. Will do. For the bigcommerce issue, you are correct - the issue is irrelevant to runtime and hasn't built properly in a while. Per my discussion with @joshuawootonn in Slack, the advice was to not upgrade bigcommerce and open a ticket for the build issues. Do you think we should move forward with the upgrade anyways?

Looks good, but how come we're doing 0.11.4 when the latest version is 0.11.19?

Consistency - since Alan just bumped to 0.11.4 in the typescript example, I wanted all examples to be consistent with that. I could just bump everything (except bigcommerce) to be 0.11.19. Any preferences?

Let's bump them all to 0.11.19. We should have all examples be up to date with the latest version of the runtime.
Also, how come we're no updating the BigCommerce example? Is that build failing as a result of the update? Given the error I'd assume that the example is broken independent of the runtime version being used.

Sounds good, will update everything. For the bigcommerce issue, you are correct - the issue is irrelevant to runtime and hasn't built properly in a while. Per my discussion with @joshuawootonn in Slack, the advice was to not upgrade bigcommerce and open a ticket for the build issues. Do you think we should move forward with the upgrade anyways?

I still think we should upgrade the runtime because if somebody uses the example but provides their own store they might get things working but if the runtime is outdated they could run into other issues.
We should definitely create an issue in Linear to track the problem with our default store, though.

@migueloller I've updated all package runtimes and the associated lockfiles


the model doest use train data anymore

I got a problem with a model i trained, if normally i could continue training from checkpoint, now for unknow reason the model only do validation and test step but with train data =0, however the path to the training data is corrrect and i did*t change it

Not enough information to help: what commands are you running, how the data is stored, what is the output


MINOR: Change ConnectDistributed system test to use KafkaVersion instead of string

Recently, #7000 added a method to the KafkaVersion class used in the Kafka system tests. Until then, ConnectDistributed tests passed a string as the version, and this happened to work since no methods were required. But the KafkaVersion.support_named_listeners() method added in #7000 and required in tests/kafkatest/services/kafka/templates/kafka.properties appears to have broken the ConnectDistributed system tests. Changing the latter to use KafkaVersion instead of string fixes the system tests.
I'll run a system test build before this should be merged to trunk and 2.3.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The system test run of ConnectDistributedTest (https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2761/console) had 11 tests pass and 1 fail because Kafka Connect failed to start on node: ubuntu@worker5, which is a notoriously irritating error that happens only occasionally.
Given that all of these system tests failed before this change, we should still be able to merge this and backport at least to the 2.3 branch, and potentially back to the 1.0 branch.

System test run with the updated PR (https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2767/) had the same two failures from Randall's test run yesterday with his PR. Randall mentioned that these looked like intermittent failures. But I am not sure the compatibility tests would ever have worked against a <IP_ADDRESS> broker. The logs show that the Connect client sent an ApiVersions request that the <IP_ADDRESS> broker didn't recognize. So I looked at the last successful run and those were working since all the compatibility tests were always running against a dev broker because version was being set as String rather than the expected KafkaVersion. Updated the test to remove compatibility test with <IP_ADDRESS> brokers.

@ijuma Thanks for the review, merging to trunk with detailed commit message.


Clean up and improve host function trampoline API

The new API guarantees at compile time that host functions use this API correctly from start to finish.


chore(relay-angular-chat): bump to @waku/core 0.0.10 & other @waku/* packages

Blocking
While I have bumped up and fixed @waku/* packages and API, and upgraded other npm packages -- there are errors seen within chainsafe and libp2p deps.
Not sure if this is Angular specific.
cc @weboko @fryorcraken any ideas here?
Error: node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.d.ts:230:5 - error TS2416: Property 'getPeers' in type 'GossipSub' is not assignable to the same property in base type 'PubSub<GossipsubEvents>'.
  Type '() => import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]' is not assignable to type '() => import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]'.
    Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]'.
      Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId'.
        Type 'RSAPeerId' is not assignable to type 'PeerId'.
          Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").RSAPeerId' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").RSAPeerId'.
            The types returned by 'toCID().toV0().toJSON()' are incompatible between these types.
              Property ''/'' is missing in type '{ code: 112; version: 0; hash: Uint8Array; }' but required in type '{ '/': ToString<CID<unknown, 112, 18, 0>, string>; }'.

230     getPeers(): PeerId[];
        ~~~~~~~~

  node_modules/@libp2p/interface-peer-info/node_modules/multiformats/dist/types/src/cid.d.ts:191:9
    191         '/': API.ToString<CID<Data, Format, Alg, Version>, string>;
                ~~~
    ''/'' is declared here.

Error: node_modules/@chainsafe/libp2p-gossipsub/dist/src/index.d.ts:273:5 - error TS2416: Property 'getSubscribers' in type 'GossipSub' is not assignable to the same property in base type 'PubSub<GossipsubEvents>'.
  Type '(topic: string) => import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]' is not assignable to type '(topic: string) => import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]'.
    Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId[]'.

273     getSubscribers(topic: TopicStr): PeerId[];
        ~~~~~~~~~~~~~~

Error: node_modules/@waku/create/dist/index.d.ts:9:46 - error TS2694: Namespace '"/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@waku/core/dist/lib/relay/index"' has no exported member 'CreateOptions'.

9 declare type RelayCreateOptions = waku_relay.CreateOptions;
                                               ~~~~~~~~~~~~~

Error: node_modules/libp2p/dist/src/connection-manager/index.d.ts:171:5 - error TS2416: Property 'getConnections' in type 'DefaultConnectionManager' is not assignable to the same property in base type 'ConnectionManager'.
  Type '(peerId?: import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId | undefined) => import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-connection/dist/src/index").C...' is not assignable to type '(peerId?: import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId | undefined) =><EMAIL_ADDRESS>    Types of parameters 'peerId' and 'peerId' are incompatible.
      Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId | undefined' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId | undefined'.
        Type 'RSAPeerId' is not assignable to type 'PeerId | undefined'.
          Type 'RSAPeerId' is not assignable to type 'Secp256k1PeerId'.
            Types of property 'type' are incompatible.
              Type '"RSA"' is not assignable to type '"secp256k1"'.

171     getConnections(peerId?: PeerId): Connection[];
        ~~~~~~~~~~~~~~

Error: node_modules/libp2p/dist/src/connection-manager/index.d.ts:172:5 - error TS2416: Property 'openConnection' in type 'DefaultConnectionManager' is not assignable to the same property in base type 'ConnectionManager'.
  Type '(peerId: PeerId, options?: AbortOptions | undefined) => Promise<Connection>' is not assignable to type '(peer: PeerId | Multiaddr, options?: AbortOptions | undefined) => Promise<Connection>'.
    Types of parameters 'peerId' and 'peer' are incompatible.
      Type 'PeerId | Multiaddr' is not assignable to type 'PeerId'.
        Type 'RSAPeerId' is not assignable to type 'PeerId'.
          Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").RSAPeerId' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").RSAPeerId'.
            The types returned by 'toCID().toV0().toJSON()' are incompatible between these types.
              Type '{ '/': ToString<CID<unknown, 112, 18, 0>, string>; }' is missing the following properties from type '{ code: 112; version: 0; hash: Uint8Array; }': code, version, hash

172     openConnection(peerId: PeerId, options?: AbortOptions): Promise<Connection>;
        ~~~~~~~~~~~~~~

Error: node_modules/libp2p/dist/src/connection-manager/index.d.ts:173:5 - error TS2416: Property 'closeConnections' in type 'DefaultConnectionManager' is not assignable to the same property in base type 'ConnectionManager'.
  Type '(peerId: PeerId) => Promise<void>' is not assignable to type '(peer: PeerId) => Promise<void>'.
    Types of parameters 'peerId' and 'peer' are incompatible.
      Type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-info/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId' is not assignable to type 'import("/Users/danisharora099/Developer/status/examples/examples/relay-angular-chat/node_modules/@libp2p/interface-peer-id/dist/src/index").PeerId'.
        Type 'RSAPeerId' is not assignable to type 'PeerId'.

173     closeConnections(peerId: PeerId): Promise<void>;
        ~~~~~~~~~~~~~~~~

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

✖ Failed to compile.

The first error is most likely due to a breaking change in a libp2p interface and the fact that libp2p-gossipsub and waku uses two different version of said interface.
Easiest is to bump all js-waku deps (working on that).
or you can find what interface has a breaking change (looks like interface-peer-id) and pin down the version.

this happens quite often with libp2p packages in general, in particular libp2p-gossipsub.
This reason alone is enough to extract Waku Relay from @waku/core. Especially that we would recommend developer to use light push/store/filter first and consider relay only for privacy concerns (being aware of the scalability limitations).

this happens quite often with libp2p packages in general, in particular libp2p-gossipsub.
This reason alone is enough to extract Waku Relay from @waku/core. Especially that we would recommend developer to use light push/store/filter first and consider relay only for privacy concerns (being aware of the scalability limitations).

https://github.com/waku-org/js-waku/issues/1151

This now should be fixed on master thanks to https://github.com/waku-org/js-waku/pull/1160
with https://github.com/waku-org/js-waku/pull/1155 in place, a release should appear soon


Pr/18

Hey,
I added tests and pushed the version number to 1.2.0. It's now also uploaded to npm
Thanks for your contribution!
Cheers


Image Scanning with Private Endpoint

The documentation says that Image Scanning via ASC is not available if private endpoint is enabled on ACR. Is there a Microsoft recommended best practice around an alternative way of scanning images stored in ACR with a private endpoint?

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

ID: 8e01945a-5892-a416-716f-c499f110586c
Version Independent ID: e2aef346-266f-3e69-842d-58004084609b
Content: Set up private link - Azure Container Registry
Content Source: articles/container-registry/container-registry-private-link.md
Service: container-registry
GitHub Login: @dlepow
Microsoft Alias: danlep

@pnarsi
Thanks for your Question! We are currently investigating and will get back on this.

@dlepow Can you add your comments on this ask.

Hi folks,
We are working through various solutions to assure we can maintain the highest level of security when enabling cross service access to resources in a VNet.
We do not yet have an ETA.
Alternative options include security scanning solutions that can be stood up within the VNet like AquaSec, Twistlock/Palto Alto Networks, Claire and other container scanning and runtime security solutions.
Steve

@SteveLasker Thanks for sharing the details.

@pnarsi
Hope the provided information is helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.

I believe the question is answered, so closing the issue. Thanks!
#please-close


Left Analog starts moving cursor

When I restarted parsec soda, the problem went away.
It's never happened before, could a player somehow switch to some other mode? Don't know how to reproduce but I'll update it if happens again...

Scratch that. Issue was due to another program.


Introduce bitset to manage bool flags in mock_layer unit test.

As the title said, there are some bool flags in mock_layer class which needs to be tidied up. Maybe bitset is needed.

Closing this since the linked PR has been merged.


Unexpected behavoir of "asList()" with and EMBEDDED ODocument as an argument

I ran into this issue while trying to work around #5532.  In that issue there is a case where the same query is either returning a HashSet or an ODocument.  I was trying to use the "asList()" method as a workaround to ensure that in either case, the value returned would be a list.  While I did always get a list returned, the values in the list were not as expected when the query returned an ODocument (It did work fine for a HashSet).
The "asList()" function (OSQLMethodAsList.java) seems to be intended to convert various collections and single items to a list.  The documentation states that if a single element is passed to this method, a new list will be created with the single element in it.
On line 44, the class checks to see if the value is already a list.  If so, it just returns it.  On line 50 it checks for null, and returns an empty list.  On line 56, it checks to see if the value is a collection and uses the "addAll" constructor of ArrayList to create a new list with all the elements.  On line 62, the class detects an Iterable, and iterates over the value, adding each element to a new list.  Lastly, on line 73 the class assumes that the value is a single element and adds it to a new list.
The problem here is that ODocument itself implements Iterable<Entry<String, Object>>.  Therefore instead of getting a list with a single ODocument init, the caller winds up with a List of Entry<String, Object>.  I suppose there could be a rare case where this is desired, however I believe that the user would expect a list with a document in it.  For all other types, Dates, Numbers, Strings, and even Sets / Lists of documents, you will wind up with the values intact, just in a list.  Pulling apart the document itself into a list, seems strange.  For example, I would not expect the asList method to turn a String into a list of individual characters.
If this is actually the indented behavior, then I would suggest updating the documentation to explicitly state that the ODocument will be converted into a list of Key Value pairs.
In either case, I would be more than willing to either update the code, or the documentation based on your thoughts.  I didn't want to move ahead with either until I understand what the expected behavior is.
Keep up the good work!

@luigidellaquila if you would like, I can submit a quick PR for this.


How to generate jsdoc-style comments ?

for example:
/** @type {Aarray} array */

/**
 * @param {string} str
 */

Thank you.

The following line overwrites javascripts alternative delimiters to /** */:
let g:NERDCustomDelimiters = { 'javascript': { 'left': '//', 'leftAlt': '/**','rightAlt': '*/' } }
Just add it to your init.vim and it should work.
The only problem (for me at least) is that the justification for multline comments is kind of wonky:
/**
  * this is a sexy comment
  */

instead of
/**
 * this is a sexy comment
 */

So it's not a perfect solution, but it's the closest you can get with just NERDCommenter; one might wonder whether it's more effort to do it this way or to just manually add another asterisk...


Array root documentation

Maybe I am missing the point... but I don't understand how, why or when the root option works – I am putting it in all sorts of places, on get/post, on namespaces/resources, on CollectionSerializer constructs... and it is never doing what I expect.
I am expecting root: 'users' to make the output:
{
  "users": [
    {
      "name": "steve"
    }
  ]
}

I see past issues that this changed at some point, is there documentation missing around this?
Also I found an issue from years ago that seemed to indicate root: false stopped working on collections at some point – that'd be handy too
Am I right in thinking that a CollectionSerializer with a root option doesn't realise that root until an Adapter handles it or something?
In a bunch of cases in the API I am working on we are returning CollectionSerializer instances from controller action, I've been toying with switching those to a render call – but that doesn't accept any options either

I am currently toying with patching a custom render_collection method onto endpoints to achieve the functionality I want, would be good to get rid of this if there's a way:
module EndpointExtension
  def render_collection(resources, serializer:, root:)
    resources = ActiveModel::Serializer::CollectionSerializer.new(resources, serializer: serializer, scope: self)
    resources = {root => resources}
    resources
  end
end

Grape::Endpoint.send(:include, EndpointExtension)

@stevelacey - can you check what your adapter is set to? The default AMS adapter is attributes, which ignores that root option. Perhaps you want to use the json adapter.
See https://github.com/rails-api/active_model_serializers/blob/v0.10.6/docs/general/adapters.md for details.
You can override the default by adding ActiveModelSerializers.config.adapter = :json in an initializer.

Yeah it’s set to json
On Wed, 8 Nov 2017 at 16:20, Darren Cheng<EMAIL_ADDRESS>wrote:

@stevelacey https://github.com/stevelacey - can you check what your
adapter is set to? The default AMS adapter is attributes, which ignores
that root option. Perhaps you want to use the json adapter.
See
https://github.com/rails-api/active_model_serializers/blob/v0.10.6/docs/general/adapters.md
for details.
You can override the default by adding ActiveModelSerializers.config.adapter
= :json in an initializer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ruby-grape/grape-active_model_serializers/issues/81#issuecomment-342758044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARq-33xRyKq2GSKhZ4y9J2vBDLUqjYOks5s0XJlgaJpZM4QI6hK
.


Styling css and js

Just curious. Looked at the source code, and I liked how you formatted it. E.g. in css the ':' are vertically simmetrical. How did you do that? Did you use any tool? I couldn't find any. It really helps with readability

Hey @mihaisavezi, you can use a plugin (depending on your editor) to align chunks of code based on characters. You could also run your CSS through online formatters!
Cheers :)


Private or Internal Names

The section on Private or Internal Names should be revised to recommend the use of the internal keyword rather than prefixing with _.

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

ID: 5cc4b9d4-0214-5c5c-4528-20d345c87a2d
Version Independent ID: 4e5ad251-dec1-1e76-7089-eb8862d24160
Content: Microsoft Q# Style Guide - Microsoft Quantum
Content Source: articles/contributing/style-guide.md
Product: quantum
GitHub Login: @cgranade
Microsoft Alias: chgranad

Thanks for filling the issue. I addressed this in #909 but I can't add you as a reviewer since you're not in the list of collaborators for this repo (we can add you I think).


how to configure to support different api？

I am new to Ocelot and have created a demo gateway project successfully.
The question is how to support many different api(s).
For example:
webapi A  on  http://a.com
/api/product
/api/user
... other 10 resources.
webapi B on http://b.com
/api/order
/api/address
....other 20 resources.
not only  get or put。
so is there any good way to configure ？
or we can configure  as this:
"ReRoutes": [
{
"DownstreamPathTemplate": "/api/{controller}}",
"DownstreamScheme": "http",
"DownstreamHost": "a.com",
"DownstreamPort": 80,
"UpstreamPathTemplate": "/api/webapi1/{controller}",
"UpstreamHttpMethod": "Get,Post,Put,Delete"
},
{
"DownstreamPathTemplate": "/api/{controller}}",
"DownstreamScheme": "http",
"DownstreamHost": "a.com",
"DownstreamPort": 80,
"UpstreamPathTemplate": "/api/webapi2/{controller}",
"UpstreamHttpMethod": "Get,Post,Put,Delete"
}
]
Any reply is appreciated.

Hi @hanyubao,
with the current version you must map all resources, but recently was made a modification to manage many api(s) more easyly (#89). I guess this changes will be available soon in Nuget package but @TomPallister can say you with more exactly. While you can use the code of the master branch if you are in a hurry.

thank you @juancash

@juancash I can release a new version now I think..give me a few minutes! Just enough time before work starts! :)

@juancash Ive just released 1.4.3, your change will be in it! :D

@TomPallister Excellent, thank you very much :D
@hanyubao you can use the new version to implement your scenario.

@TomPallister @juancash
That's great! Thanks for all your effort.

@TomPallister
Hi again, I´m using the version 1.4.3 but seems something works different or something is wrong, because now my "POST" requests are not working. Seems something about the headers, but I´m not sure. I´m trying to debug to found where is the problem. If I use the version 1.4.2 or the branch that I pushed in #89 all works fine. Do you know if has changed the way of process the request types, headers or body in the requests?
Thanks.

@TomPallister It seems that at least the content-type comes empty to the api (after pass by the gateway).

@juancash I will look at it asap! might be something to do with recent refactoring!

Ive found the issue and am fixing atm!

@juancash @hanyubao I have pushed version 1.4.4, this should fix the issue with no content type when using POST. It was a regression brought in after some refactoring.
I have only written a failing unit test and made it pass, I have not had time to manually test yet but I'm confident this is the problem and it will work now -_-

Sorry, looks like it was my refactoring in #88 that broke this!

Easy to miss and there should have already been a unit test around it so my fault! Its nice to work on a code base where you can just add a failing test though :)

@binarymash @TomPallister
No problem ;) . Thanks to both of you for your effort and speed.

Going to close this issue now i think @juancash changes have solved the problem. It is much easier to configure re route ;)
Massive thanks for the work @juancash !!

@juancash   thx for your help,but is there a nuget release or version for this issue? any  final document for multipe verbs is welcome.
@TomPallister have a good holiday^_^

@hanyubao yes, you can download the project and use the code in master until a new version is published in the nuget. Remember that now the UpstreamHttpMehtod property is a list.
You can see an example in the PR # 94.


How to prevent the entire project from being recompiled due to modifying CMakeLists.txt (IDFGH-13903)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I want to use a library as an idf component but it doesn't come with its own cmake file for idf. There are some cross board files in the library, which I don't need, but I'm not sure which ones I don't need. I can only keep modifying the idf_component_register.SRCS parameters to test, which is a terrible experience. Every time I add even one file to my SOURCE_FILES, it will cause the entire project of more than 1400 source files to be recompiled. I have never hated c++ so much. Is there any way to solve this problem? I also use arduino-esp32 as my component. Maybe there is a way to pre-compile some things as static libraries to reduce compilation time?
set(SOURCE_FILES
    "src/Arduino_DataBus.cpp"
    ...)

idf_component_register(
    INCLUDE_DIRS "src"
    SRCS ${SOURCE_FILES}
    PRIV_REQUIRES "arduino"
)

Hi @UradaSources. If I understood your situation correctly then in this case the best option would be to make sure that you are bulding with ccache enable. That means it will use the previously build source files from the cache if it hasn't been modified.
Depending on your OS and ESP-IDF version, it might be disabled by default. You can force it with the ``--ccache` command line argument:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-py.html#global-options

I'm closing this for inactivity. Please let us know if this needs further discussion.


Added MysqlShell 8.1.1

New updated PR of previous #47644 with dependencies defined in manifest file.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: the MySQL Shell documentation says:

For the Community and Commercial versions of MySQL Shell: Before installing MySQL Shell, make sure you have the Visual C++ Redistributable for Visual Studio 2015 (available at the Microsoft Download Center) installed on your Windows system.

Microsoft Reviewers: Open in CodeFlow

Looks like this is getting stuck on dependencies, since the feature is not yet released as stable

Yes, it's not getting through validation until we have the dependency support included in the validation pipelines. We're expecting the WinGet 1.6 client to be released at the end of the month. It will likely take a couple of weeks after that for >50% of clients to be updated, and then we'll begin validation with dependencies in earnest.

1.6 is ready, so can we run the pipelines again?

The pipelines are paused while we make some updates. Once they are re-enabled, the validation can be re-run.

Automatic Validation ended with:

Installation failed with exit code -1978335226
2023-09-18 06:32:58.953 [CLI ] ShellExecute installer failed: 1603 Property(S): ErrorDialog = ErrorDlg
MSI (s) (BC:F8) [06:32:58:557]: Product: MySQL Shell 8.1.1 -- Installation failed.
MSI (s) (BC:F8) [06:32:58:572]: Windows Installer installed the product. Product Name: MySQL Shell 8.1.1. Product Version: 8.1.1. Product Language: 1033. Manufacturer: Oracle and/or its affiliates. Installation success or error status: 1603.

@wingetbot waivers Add Validation-Shell-Execute


Update zio-json, zio-json-golden to 0.7.0

About this PR
📦 Updates

dev.zio:zio-json
dev.zio:zio-json-golden

from 0.6.2 to 0.7.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #156.


Release candidate 1.2

Description of PR
This PR makes all necessary updates for a new release.
The PR also implements a new workflow to automatically create a release on pypi, simply by creating and pushing tags. This is based on the work by @khaeru on the iam-units package.
As a third step, the PR refactors the version-attribute from versioneer to setuptools_scm.

Seems that the Windows-runners for GitHub Actions are currently out of order.

Thanks for the comments, @gidden - all done!


reformat docs/Deploy-Module.md

http://tachyon-project.org/master/Deploy-Module.html
after rendering to html, lists and bold fonts don't show properly.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/3253/
Test PASSed.

LGTM, thanks!


allow linking to containers not managed by the plugin

i thought i had seen an issue regarding this before, but perhaps it was for referencing volumes from other containers.
in any case, when starting a container via the plugin, i'd like to be able to link to an existing container that has been started via some other mechanism.
in an effort not to break existing configuration, my thought is to just add a new xml block to the run section:
<linkExternal>
  <link>container_name:env_var_prefix</link>
</linkExternal>

thoughts? i'm open to different element names, etc.

I thought linking already works also with external container names (and internal aliases). Is this not the case ?

unless i'm doing something wrong, it doesn't. i get this error message:
Cannot resolve image dependencies for start order

and w/o looking at the code, my guess is the plugin is looking for the image configuration so it can be started.
if you think we should just use the existing configuration elements and make the plugin smarter to check for an already running container if it can't find the image in the xml, that would work as well.

Ah, ok. Good point, but this is more a bug than a missing feature. Any externally linked container (i.e. any container which is not in the realm of the plugin) should be assumed to be up and running and hence don't need to be considered when calculating the start order.

hrm - how would you compare this w/ #73 b/c they are related in the sense that you want to reference something from an existing container.
should that code be made smarter to check for a running image if it's not found in the plugin configuration or should we use separate tags?

Yeah, you are right. Personally I think we shouldn't clutter the configuration namesspace to much, so I'm against having new tags without a super good reason ;-)
Maybe we can really be that smart to (a) first check whether it's an internal container (that we already do) and if not (b) check if another container with this name is running and than use that one. If neither (a) nor (b) then --> error.
What do you think ?

sounds good to me!

ok, then let's go this route and fix #73 in a similar way. I think we already have a DockerAccess.hasContainer() (and if not, should not hard to add).
If you like you can take it, otherwise I can go for it sometimes later (backlog is already quite long ;-)

i'll take care of it - i need this for something else i'm doing so that will motivate me to get it done.

Thanks a lot !

Any news on that one ? I want to cut a release on Friday and wonder whether it could be included.
No pressure, though ;-P (really)

unfortunately no, i'm still working on it - other things have gotten in the way.
i will try and get it finished over the weekend.

No hurry, there will always be a next release ;-P

i started working on this and i've got a question...
DockerAccess is becoming a little 'crowded' and i was going to pull some of the fine grained methods out of that class into a QueryService similar to what was done w/ the RunSevice (although that was spawned from code in the mojos) but i wanted to have a better understanding of why you made it a component before i did my implementation.
what does that get us verse just creating an instead of the class in the mojo, like how the LogDispatcher is handled, and just working w/ it that way? one thing it seems to prevent is the ability to inject dependencies into the component itself - i will admit i'm not a fan of passing the DockerAccess instance to every method, so i was trying to see if i could inject it into the service, but given how the docs for plexus are rather sparse now that codehaus has shutdown, i didn't have much luck.
worst case i figured i could just inject it w/ a setter at the start of the execute method which lead me to wonder why not just call new in the mojo and pass the client as a constructor arg.

Yeah, you are right. DockerAccess indeed is a bit too large. I also already thought about splitting it up.
The story behind RunService: My use case here was that for docker:watch I need to build images and to restart containers. These functionality was included in BuildMojo and RunMojo respectively. These Mojos were also too large. In order to avoid code duplication I made two things:

Introduced a AbstractDockerBuildMojo which is inherited by BuildMojo and WhatchMojo.
Introduced a new layer (I call it 'service layer') between the DAO (DockerAccess) and the Mojos. In that case it is the RunService which is both used by RunMojo and WatchMojo.

Of course ideally we would also have a BuildService similar to RunService since composition is nearly always better than inheritance. The problem with Maven is, although we have Plexus ad DI container, there are certain parts which can be only injected into Mojos (like the MavenProject I think). So sometimes you need inheritance in the Mojo hierarchy, but I have to revisit this again.
The point about RunService is that it carries state about the containers stareted. This state is shared by  start, stop and watch. So I need a singleton which can be easily achieved via plexus and this singleton is shared by all mojos.
DockerAcess can not really be injected because the creation is a bit more complex than a simple constructor and needs mojo parameters, too, which not available if using injection. So we can't use Plexus alone. Moving it down is indeed no so nice (but on the other not so super problematic), we could either consider the setter approach you propose or some thread local stuff with static methods for getting to DockerAccess.
new RunService(DockerAccess access)  is not possible because you want to share this singleton across multiple instances as said before.
Altough DockerAccess is a bit lengthy, we could split it up into multiple DAOs (QueryDao, ImageDao, ...). The difference of a 'Service' is that it is on top of the DAO. Ideally we have a complete layer like Mojo -> Service -> Dao, so that no Mojo accesses the DockerAccess directly and mostly serves only as a (stupid) entry point.

thanks for that explanation! it makes sense for shared state to be handled that way. i don't think a query service will need to share state, but i think it will probably be best to follow the component regardless.
i think a setter method could be added to RunService to inject DockerAccess just like you do for the logger which would simplify things.
ok...i'll finish this and put together an initial pull request and we can review. i think what i have in mind should offer some good flexibility and also puts us in a good position to offer a docker:ps mojo.

fixed in 0.13.2


Add/nvme support

Hello there,
I've added nvme support for the exporter.
It currently exports the following values: smart_status passed, critical_warning, available_spare, media_errors
I've also created a docker file which can be used to create a docker container from the exporter. I'm not a developer myself so if any corrections needed, happy to do it.

Hello! Can we get this PR in? This would be really useful to have!

yes, will be really good to have it on upstream!

@Sheridan Many thanks for the really nice exporter ! (Спасибо большое!)
I have used it with changes from this PR and it works nice. Also thank you @langizoli for the NVMe support!
I found only one strange behavior which I can't fix yet. When I have a server with both types of SSD drives, SATA + NVMe, then I always have a crashing of exporter:
# /opt/smartctl-exporter/smartctl_exporter -config=/etc/smartctl_exporter.yaml
[Warning] S.M.A.R.T. output reading error: exit status 1
[Warning] S.M.A.R.T. output reading error: exit status 1
panic: runtime error: index out of range [0] with length 0

goroutine 22 [running]:
main.(*SMARTctlInfo).mineVersion(0xc0000dceb8)
	/go/src/github.com/langizoli/smartctl_exporter/smartctlinfo.go:46 +0x942
main.(*SMARTctlInfo).Collect(...)
	/go/src/github.com/langizoli/smartctl_exporter/smartctlinfo.go:35
main.SMARTctlManagerCollector.Collect(0xc00022e060)
	/go/src/github.com/langizoli/smartctl_exporter/main.go:34 +0x1af
github.com/prometheus/client_golang/prometheus.DescribeByCollect.func1(0xa69ec0, 0xe0f3e0, 0xc00022e060)
	/go/src/github.com/prometheus/client_golang/prometheus/collector.go:90 +0x3b
created by github.com/prometheus/client_golang/prometheus.DescribeByCollect
	/go/src/github.com/prometheus/client_golang/prometheus/collector.go:89 +0x75

Config File:
smartctl_exporter:
  bind_to: "<IP_ADDRESS>:9633"
  url_path: "/metrics"
  fake_json: no
  smartctl_location: /usr/sbin/smartctl
  collect_not_more_than_period: "20s"
  devices:
  - /dev/sdb
  - /dev/sdc

And it doesn't matter if those existed NVMe drives enabled in config or not. It always gives me this error.
all disks on server:
# lsblk -l|egrep -oe '(sd[a-z]|nvme[0-9])'|sed -e 's/^/  - \/dev\//'| uniq
  - /dev/sda
  - /dev/sdb
  - /dev/sdc
  - /dev/nvme0
  - /dev/nvme1
  - /dev/nvme2
  - /dev/nvme3
  - /dev/nvme4

I thought may be it can be related to this PR changes, so I compiled original version without NVMe supports. But unfortunately I have the same problem somehow:
# /opt/smartctl-exporter/smartctl_exporter -config=/etc/smartctl_exporter.yaml -debug
[Panic] Failed parse %!s(*string=0xc0001f21f0): %!s(<nil>)
[Debug] Parsed options: {{<IP_ADDRESS>:9633 /metrics %!s(bool=false) /usr/sbin/smartctl 20s 20s [/dev/sdb /dev/sdc]}}
[Debug] Collecting S.M.A.R.T. counters, device: /dev/sdb
[Warning] S.M.A.R.T. output reading error: exit status 1
[Debug] Collecting S.M.A.R.T. counters, device: /dev/sdc
[Warning] S.M.A.R.T. output reading error: exit status 1
panic: runtime error: index out of range [0] with length 0

goroutine 22 [running]:
main.(*SMARTctlInfo).mineVersion(0xc0000deeb8)
	/go/src/github.com/Sheridan/smartctl_exporter/smartctlinfo.go:46 +0x942
main.(*SMARTctlInfo).Collect(...)
	/go/src/github.com/Sheridan/smartctl_exporter/smartctlinfo.go:35
main.SMARTctlManagerCollector.Collect(0xc000232060)
	/go/src/github.com/Sheridan/smartctl_exporter/main.go:34 +0x1af
github.com/prometheus/client_golang/prometheus.DescribeByCollect.func1(0xa69ec0, 0xe0f3e0, 0xc000232060)
	/go/src/github.com/prometheus/client_golang/prometheus/collector.go:90 +0x3b
created by github.com/prometheus/client_golang/prometheus.DescribeByCollect
	/go/src/github.com/prometheus/client_golang/prometheus/collector.go:89 +0x75

It's really strange. BTW I have tested on 5 different servers and 3 of them have this mixed type of SSD drives and have this problem. But 2 other servers only with NMVe and work well:
# lsblk -l|egrep -oe '(sd[a-z]|nvme[0-9])'|sed -e 's/^/  - \/dev\//'| uniq
  - /dev/nvme0
  - /dev/nvme1
  - /dev/nvme2
  - /dev/nvme3
  - /dev/nvme4

# cat /etc/smartctl_exporter.yaml
# Ansible managed
smartctl_exporter:
  bind_to: "<IP_ADDRESS>:9633"
  url_path: "/metrics"
  fake_json: no
  smartctl_location: /usr/sbin/smartctl
  collect_not_more_than_period: "20s"
  devices:
  - /dev/nvme0
  - /dev/nvme1
  - /dev/nvme2
  - /dev/nvme3
  - /dev/nvme4

# /opt/smartctl-exporter/smartctl_exporter -config=/etc/smartctl_exporter.yaml -debug
[Debug] Parsed options: {{<IP_ADDRESS>:9633 /metrics %!s(bool=false) /usr/sbin/smartctl 20s 20s [/dev/nvme0 /dev/nvme1 /dev/nvme2 /dev/nvme3 /dev/nvme4]}}
[Debug] Collecting S.M.A.R.T. counters, device: /dev/nvme0
[Debug] Collecting S.M.A.R.T. counters, device: /dev/nvme1
[Debug] Collecting S.M.A.R.T. counters, device: /dev/nvme2
[Debug] Collecting S.M.A.R.T. counters, device: /dev/nvme3
[Debug] Collecting S.M.A.R.T. counters, device: /dev/nvme4
[Info] Starting on <IP_ADDRESS>:9633/metrics
^C

I have no idea why it happens with mixed type of SSD drives. I used the same ansible role which I developed for all 5 severs but the behavior is different. I mean the problem not in permissions or some Selinux staff.
Can you help me with this please ? I can provide some more info or will be able to do some other tests.
I already tested it on CentOS 7 with smartmontools-7.0-2.el7.x86_64.

Well, finally I found the problem on my end. I had different versions. On some hosts smartctl was pre-installed and had 6.5 version.
smartctl 7.0 2018-12-30 r4883
smartctl 6.5 2016-05-07 r4318
smartctl 6.5 2016-05-07 r4318
smartctl 7.0 2018-12-30 r4883
smartctl 6.5 2016-05-07 r4318

I am ashamed. Sorry for the long reaction ...


Feature request - paranoid mode

It would be nice to have a "paranoid" mode that would prompt you to review the manifest before performing the install. Whilst the default and extras bucket should be trustworthy it gives me a bit more confidence to see exactly what's going to happen before the install.
This should probably be available as both a config value and a flag to install. I would be quite happy if all it did was open notepad with the manifest and then give you the option to continue or stop. This should also be added to update.

Duplicate of https://github.com/lukesampson/scoop/issues/2735.