ProcessException: No such file or directory

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter run
exception
ProcessException: ProcessException: No such file or directory
Command: /usr/bin/xcodebuild -project /Users/xuexin/Makeblock/Flutter/flutter_plugins/webview_plugin/ios/Runner.xcodeproj -target Runner -showBuildSettings
#0      _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:489:7)
#1      _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:634:18)
#2      Process.runSync (dart:io-patch/process_patch.dart:66:12)
#3      LocalProcessManager.runSync (package:process/src/interface/local_process_manager.dart:83:20)
#4      _runWithLoggingSync (package:flutter_tools/src/base/process.dart:343:48)
#5      runCheckedSync (package:flutter_tools/src/base/process.dart:297:10)
#6      XcodeProjectInterpreter.getBuildSettings (package:flutter_tools/src/ios/xcodeproj.dart:177:24)
#7      IosProject.buildSettings (package:flutter_tools/src/project.dart:364:42)
#8      IosProject.isSwift (package:flutter_tools/src/project.dart:356:23)
#9      RunCommand.usageValues (package:flutter_tools/src/commands/run.dart:229:35)
<asynchronous suspension>
#10     FlutterCommand._sendUsage (package:flutter_tools/src/runner/flutter_command.dart:411:58)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:392:17)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#13     _rootRun (dart:async/zone.dart:1124:13)
#14     _CustomZone.run (dart:async/zone.dart:1021:19)
#15     _runZoned (dart:async/zone.dart:1516:10)
#16     runZoned (dart:async/zone.dart:1463:12)
#17     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#18     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:375:20)
#19     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#20     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:396:21)
<asynchronous suspension>
#21     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#22     _rootRun (dart:async/zone.dart:1124:13)
#23     _CustomZone.run (dart:async/zone.dart:1021:19)
#24     _runZoned (dart:async/zone.dart:1516:10)
#25     runZoned (dart:async/zone.dart:1463:12)
#26     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#27     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#28     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#29     new Future.sync (dart:async/future.dart:224:31)
#30     CommandRunner.run (package:args/command_runner.dart:112:14)
#31     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#32     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:22)
<asynchronous suspension>
#33     _rootRun (dart:async/zone.dart:1124:13)
#34     _CustomZone.run (dart:async/zone.dart:1021:19)
#35     _runZoned (dart:async/zone.dart:1516:10)
#36     runZoned (dart:async/zone.dart:1500:12)
#37     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#38     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#39     _rootRun (dart:async/zone.dart:1124:13)
#40     _CustomZone.run (dart:async/zone.dart:1021:19)
#41     _runZoned (dart:async/zone.dart:1516:10)
#42     runZoned (dart:async/zone.dart:1463:12)
#43     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#44     runInContext (package:flutter_tools/src/context_runner.dart:56:24)
<asynchronous suspension>
#45     run (package:flutter_tools/runner.dart:51:10)
#46     main (package:flutter_tools/executable.dart:62:9)
<asynchronous suspension>
#47     main (file:///Users/xuexin/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#48     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#49     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

flutter doctor
[✓] Flutter (Channel beta, v1.7.8+hotfix.2, on Mac OS X 10.14.5 18F132, locale zh-Hans-CN)
    • Flutter version 1.7.8+hotfix.2 at /Users/xuexin/flutter
    • Framework revision 2e540931f7 (10 days ago), 2019-07-02 09:31:07 -0700
    • Engine revision b1cb0d9e9b
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/xuexin/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • CocoaPods version 1.7.3

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.2.0

[✓] Connected device (1 available)
    • MI 6 • e0f63c14 • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

[✓] Flutter (Channel beta, v1.7.8+hotfix.2, on Mac OS X 10.14.5 18F132, locale zh-Hans-CN)
• Flutter version 1.7.8+hotfix.2 at /Users/xuexin/flutter
• Framework revision 2e540931f7 (10 days ago), 2019-07-02 09:31:07 -0700
• Engine revision b1cb0d9e9b
• Dart version 2.4.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
• Android SDK at /Users/xuexin/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 10.2.1, Build version 10E1001
• CocoaPods version 1.7.3
[✓] iOS tools - develop for iOS devices
• ios-deploy 1.9.4
[✓] Android Studio (version 3.4)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 37.0.1
• Dart plugin version 183.6270
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
[✓] VS Code
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.2.0
[✓] Connected device (1 available)
• MI 6 • e0f63c14 • android-arm64 • Android 8.0.0 (API 26)
• No issues found!

@xuexin Is the issue still relevant using current flutter stable v1.9.1+hotfix.2?

No


🐛 Bug Report: oauth2-proxy provider token refresh failure

📜 Description
At my company, we are using the oauth2-proxy provider to log in to Backstage. This is working quite fine until now (apart from that sign-out issue which has been known for quite a while: https://github.com/backstage/backstage/issues/12016).
What we have noticed now, and which we thought it was fixed in the past, is the automatic token refresh. This usually happens after some time of inactivity and then a user focusing back on the Backstage window. This issue gets automatically fixed if the user refreshes the page, but it looks pretty odd and we got questions about it.
I've managed to fix the issue in our instance (or I'm pretty sure of it at least) by extending the ProxiedSignInPage headers. Doing something like this:
          <ProxiedSignInPage
            {...props}
            provider="oauth2Proxy"
            headers={{ 'Access-Control-Allow-Credentials': 'true' }}
          />

I also believe this could be done directly in this function, by adding this new header along with the already set "x-requested-with".
But I'm worried that this might cause issues for other providers. So I prefer asking first. If this might be a fix for the issue, I would gladly open a MR with this fix.
Just tested it more, and even though it seemed to work, there's still one place that needs to be considered: the endpoint to api/permissions/authorize. This one is not sending the header as the authentication provider, so the error also appears in there. Therefore, I believe the place to fix it might be the AuthService implementation.
👍 Expected behavior
We would expect the refresh to just happen in the background and the user to not really care about this entire process. However, they are getting some authentication errors in the UI which are not really true, because refreshing the page will solve that problem.
👎 Actual Behavior with Screenshots
As an example, this is the error message we get if we analyze the requests in the developer mode:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at <KEYCLOAK_ID_WITH_INTERNAL_STUFF>&state=EQ2mPmaJYvKewL623ifct9KrymBHdffml5T__hBpeRE%3A%2Fapi%2Fauth%2Foauth2Proxy%2Frefresh. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’)

👟 Reproduction steps
After some investigation, mainly looking at the requests, I managed to find the root cause:

Open the catalog in Backstage (for example, other page would work exactly the same)
Leave the page open for some time
When the user focuses back, and since we use the permissions plugin as well, some requests to /api/permissions/authorize are triggered. If the token is expired, it then tries to refresh the token using /api/auth/oauth2Proxy/refresh
This call is returning a 302 with a Location header which is pointing to our keycloak instance, and which will be used to refresh the token
This request is failing due to a CORS policy, and therefore the error authenticating happens and it appears in the UI to the users

🖥 Your Environment
$ yarn backstage-cli info
OS:   Linux 6.5.0-27-generic - linux/x64
node: v20.10.0
yarn: 3.6.3
cli:  0.26.6 (installed)
backstage:  1.27.4

Dependencies:
  @backstage/app-defaults                                          1.5.5
  @backstage/backend-app-api                                       0.7.5
  @backstage/backend-common                                        0.21.7, 0.22.0
  @backstage/backend-defaults                                      0.2.18
  @backstage/backend-dev-utils                                     0.1.4
  @backstage/backend-openapi-utils                                 0.1.11
  @backstage/backend-plugin-api                                    0.6.18
  @backstage/backend-tasks                                         0.5.23
  @backstage/backend-test-utils                                    0.3.8
  @backstage/catalog-client                                        1.6.5
  @backstage/catalog-model                                         1.5.0
  @backstage/cli-common                                            0.1.13
  @backstage/cli-node                                              0.2.5
  @backstage/cli                                                   0.26.6
  @backstage/config-loader                                         1.8.0
  @backstage/config                                                1.2.0
  @backstage/core-app-api                                          1.12.5
  @backstage/core-compat-api                                       0.2.5
  @backstage/core-components                                       0.14.7
  @backstage/core-plugin-api                                       1.9.2
  @backstage/dev-utils                                             1.0.32
  @backstage/e2e-test-utils                                        0.1.1
  @backstage/errors                                                1.2.4
  @backstage/eslint-plugin                                         0.1.8
  @backstage/frontend-plugin-api                                   0.6.5
  @backstage/integration-aws-node                                  0.1.12
  @backstage/integration-react                                     1.1.27
  @backstage/integration                                           1.11.0
  @backstage/plugin-api-docs                                       0.11.5
  @backstage/plugin-app-backend                                    0.3.67
  @backstage/plugin-app-node                                       0.1.18
  @backstage/plugin-auth-backend-module-atlassian-provider         0.1.10
  @backstage/plugin-auth-backend-module-aws-alb-provider           0.1.10
  @backstage/plugin-auth-backend-module-azure-easyauth-provider    0.1.1
  @backstage/plugin-auth-backend-module-bitbucket-provider         0.1.1
  @backstage/plugin-auth-backend-module-cloudflare-access-provider 0.1.1
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.13
  @backstage/plugin-auth-backend-module-github-provider            0.1.15
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.15
  @backstage/plugin-auth-backend-module-google-provider            0.1.15
  @backstage/plugin-auth-backend-module-guest-provider             0.1.4
  @backstage/plugin-auth-backend-module-microsoft-provider         0.1.13
  @backstage/plugin-auth-backend-module-oauth2-provider            0.1.15
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.11
  @backstage/plugin-auth-backend-module-oidc-provider              0.1.9
  @backstage/plugin-auth-backend-module-okta-provider              0.0.11
  @backstage/plugin-auth-backend                                   0.22.5
  @backstage/plugin-auth-node                                      0.4.13
  @backstage/plugin-auth-react                                     0.1.2
  @backstage/plugin-catalog-backend-module-gitlab                  0.3.16
  @backstage/plugin-catalog-backend-module-incremental-ingestion   0.4.23
  @backstage/plugin-catalog-backend-module-ldap                    0.5.34
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.16
  @backstage/plugin-catalog-backend-module-unprocessed             0.4.5
  @backstage/plugin-catalog-backend                                1.22.0
  @backstage/plugin-catalog-common                                 1.0.23
  @backstage/plugin-catalog-graph                                  0.4.5
  @backstage/plugin-catalog-import                                 0.11.0
  @backstage/plugin-catalog-node                                   1.12.0
  @backstage/plugin-catalog-react                                  1.12.0
  @backstage/plugin-catalog-unprocessed-entities-common            0.0.1
  @backstage/plugin-catalog-unprocessed-entities                   0.2.4
  @backstage/plugin-catalog                                        1.20.0
  @backstage/plugin-events-node                                    0.3.4
  @backstage/plugin-home-react                                     0.1.13
  @backstage/plugin-home                                           0.7.4
  @backstage/plugin-kubernetes-backend                             0.17.1
  @backstage/plugin-kubernetes-common                              0.7.6
  @backstage/plugin-kubernetes-node                                0.1.12
  @backstage/plugin-kubernetes-react                               0.3.5
  @backstage/plugin-kubernetes                                     0.11.10
  @backstage/plugin-org                                            0.6.25
  @backstage/plugin-permission-backend                             0.5.42
  @backstage/plugin-permission-common                              0.7.13
  @backstage/plugin-permission-node                                0.7.29
  @backstage/plugin-permission-react                               0.4.22
  @backstage/plugin-proxy-backend                                  0.4.16
  @backstage/plugin-scaffolder-backend-module-azure                0.1.10
  @backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.8
  @backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.8
  @backstage/plugin-scaffolder-backend-module-bitbucket            0.2.8
  @backstage/plugin-scaffolder-backend-module-gerrit               0.1.10
  @backstage/plugin-scaffolder-backend-module-gitea                0.1.8
  @backstage/plugin-scaffolder-backend-module-github               0.2.8
  @backstage/plugin-scaffolder-backend-module-gitlab               0.4.0
  @backstage/plugin-scaffolder-backend                             1.22.7
  @backstage/plugin-scaffolder-common                              1.5.2
  @backstage/plugin-scaffolder-node                                0.4.4
  @backstage/plugin-scaffolder-react                               1.8.5
  @backstage/plugin-scaffolder                                     1.20.0
  @backstage/plugin-search-backend-module-catalog                  0.1.24
  @backstage/plugin-search-backend-module-pg                       0.5.27
  @backstage/plugin-search-backend-module-techdocs                 0.1.23
  @backstage/plugin-search-backend-node                            1.2.23
  @backstage/plugin-search-backend                                 1.5.9
  @backstage/plugin-search-common                                  1.2.11
  @backstage/plugin-search-react                                   1.7.11
  @backstage/plugin-search                                         1.4.11
  @backstage/plugin-techdocs-backend                               1.10.5
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.10
  @backstage/plugin-techdocs-node                                  1.12.4
  @backstage/plugin-techdocs-react                                 1.2.4
  @backstage/plugin-techdocs                                       1.10.5
  @backstage/plugin-user-settings-backend                          0.2.17
  @backstage/plugin-user-settings                                  0.8.6
  @backstage/release-manifests                                     0.0.11
  @backstage/repo-tools                                            0.9.0
  @backstage/test-utils                                            1.5.5
  @backstage/theme                                                 0.5.5
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.8

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Hello @ivangonzalezacuna, thanks for opening this issue 🙌🏻.
We think that including credentials on the fetch request would be a good idea. Would you be willing to create the pull request with the fix to contribute with us?

I think this should be it, right? https://github.com/backstage/backstage/pull/25233
From the docs, looks like the credentials: include wasn't enough and browsers will still reject the requests. Hope the tiny change is the correct one :smile:

Hi. Any other possible solution? The one I tried, as I got pointed out in there, it wouldn't really fix the problem.

This call is returning a 302 with a Location header which is pointing to our keycloak instance, and which will be used to refresh the token
This request is failing due to a CORS policy, and therefore the error authenticating happens and it appears in the UI to the users

These last steps have me a bit confused, is the 302 happening because it requires user action? It could be that refresh at this point is broken because the user session has expired and should ideally fail. If the user session is still active but needs a redirect over to Keycloak either way then you may need a CORS configuration on that end to allow the incoming request. That'd be something to configure in Keycloak rather than Backstage though.


[Hitman] Version 1.9.0 Broke the Camera System

Just as I discovered the fact that someone made a rather awesome camera system for the newest HITMAN, version 1.9.0 that launched on January 31st came out.
I tried injecting the camera into HITMAN but it seems the update has done broke it as it gets stuck on "Waiting for camera struct interception..."
Figured I'd open an issue so this is known about.

Well, am I fast or what? ;) :P https://github.com/FransBouma/InjectableGenericCameraSystem/commit/f4719964cdd2e10ec4aa481bcbc1398dd4d75526
Yeah it was expected, they promised a patch/update on Jan 31st, so I figured it would break. I found most of it back yesterday evening and fixed the missing stuff this morning.
the patch broke the hud toggle we use as well, so I'll make a hud toggle in just a moment and then I'll wrap it up and release an updated camera :) Stay tuned!

Here you go :)
https://github.com/FransBouma/InjectableGenericCameraSystem/tree/master/Cameras/Hitman2016


about auth 2 in web

in normal api gemini on used it on web flutter app shwing erorr 401 'expected oauth 2 access token in flutter'
why ?
and how to fix it in this package ?

Did you add your Gemini Api Key?
Le mer. 20 déc. 2023 à 10:53, najm-flutter @.***> a
écrit :

in normal api gemini on used it on web flutter app shwing erorr 401
'expected oauth 2 access token in flutter'
why ?
and how to fix it in this package ?
—
Reply to this email directly, view it on GitHub
https://github.com/ged-flod/google_gemini/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLWSOQQFOCGM7TAPSSM3WDYKKYP5AVCNFSM6AAAAABA4RCD26VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAMRRGE2DKMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Did you add your Gemini Api Key? Le mer. 20 déc. 2023 à 10:53, najm-flutter @.> a écrit :
…
in normal api gemini on used it on web flutter app shwing erorr 401 'expected oauth 2 access token in flutter' why ? and how to fix it in this package ? — Reply to this email directly, view it on GitHub <#4>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMLWSOQQFOCGM7TAPSSM3WDYKKYP5AVCNFSM6AAAAABA4RCD26VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TAMRRGE2DKMI . You are receiving this because you are subscribed to this thread.Message ID: @.>

yes

Can you share a code  sample ?


How does go2rtc prioritize streams from the same camera?

Hi, Alex!
I was just wondering how go2rtc prioritizes multiple streams from the same camera. I have a CCTV connected via ethernet and Wi-Fi, with different IPs for each connection type.
So, in my config, I have the following:
streams:
  outdoor_front_hd:
    # wired
    - rtsp://secret:secret@<IP_ADDRESS>:554/user=admin_password=_channel=0_stream=0&protocol=unicast&onvif=ture.sdp?real_stream
    # wireless
    - rtsp://secret:secret@<IP_ADDRESS>:554/user=admin_password=_channel=0_stream=0&protocol=unicast&onvif=ture.sdp?real_stream

Given my config above, will go2rtc prioritize the wired stream because it comes first in the config? Or does it prioritize streams (exactly the same stream, just from different addresses) some other way?
Ideally, I want it to prioritize the wired stream but use the wireless as a failover in case some smartass decides to cut the cable to the camera before sneaking into my home.

Go2rtc queries all sources one by one. It will stop when all client codecs will match. Everything will work like you want.

Awesome! Thanks!


[framework] make ImageFiltered a repaint boundary

Forked from https://github.com/flutter/flutter/pull/116229
Just the ImageFiltered change
See also: https://github.com/flutter/flutter/issues/101990

Oh right. the goldens are changing because we're not specifying which repaint boundary we want


api/v1beta1/VMUser: adds tokenRef

it allows to fetch value for Bearer Token authorization at VMAuth from pre-created secret.
It works with the same rules as passwordRef

@f41gh7 Can you create the latest release. We are waiting for this feature to go live


Process String Array parameters in Endpoints

Issue #, if available:
Internal JS-5234
Description of changes:
Process String Array parameters in Endpoints

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

There's no diff in codegen, since no models contain StringArray parameters.
Testing will be done in util-endpoints/src/mocks, similar to https://github.com/smithy-lang/smithy-typescript/pull/1374


Dead links on Wiki Page: Making-Box-Files 4.0

On this wiki page:
https://github.com/tesseract-ocr/tesseract/wiki/Making-Box-Files---4.0
The link to the

Box File
Tif Image

Is missing -- Leads to the Github's 404 error page.
(P.S. I'm a newbie and want to try Tesseract)
Thanks :)

Thanks for the report.
To try tesseract, you don't need to make box files. It works out of the box for hundreds of languages.
tesseract --help
will give you the syntax

I have updated the wiki page. You can close this issue.

Thanks for you help :smile:


No need of lsp-rust-enable

Yeah, it's a feature. The readme says

automatic RLS configuration with eglot or lsp-mode

Did you try 987847e ?

The problem is here: https://github.com/brotzeit/rustic/blob/master/rustic-util.el#L196
Stack trace:
Debugger entered--Lisp error: (void-function lsp-rust-enable)
  lsp-rust-enable()
  rustic-setup-rls()
  rustic-mode()
  set-auto-mode-0(rustic-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer fonts.rs> "~/Downloads/github.com/Wilfred/remacs/rust_src/src..." nil nil "~/Downloads/github.com/Wilfred/remacs/rust_src/src..." (3181720 2051))
  find-file-noselect("/home/compro/Downloads/github.com/Wilfred/remacs/r..." nil nil nil)
  find-file("/home/compro/Downloads/github.com/Wilfred/remacs/r...")
  projectile--find-file(nil)
  projectile-find-file()
  projectile-switch-project-by-name("~/Downloads/github.com/Wilfred/remacs/" nil)
  #f(compiled-function (project) #<bytecode 0x2144c0d>)("~/Downloads/github.com/Wilfred/remacs/")
  projectile-completing-read("Switch to project: " ("~/Downloads/github.com/Wilfred/remacs/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/froyg/thittam/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/.spacemacs.d/" "~/Downloads/git.savannah.gnu.org/git/emacs/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/.ihsec/spacemacs/" "~/.ihsec/simple-emacs/" "~/Downloads/github.com/lugnitdgp/nitdgp_website/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/MaskRay/ccls/" "~/Downloads/github.com/Compro-Prasad/dotfiles/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/metakgp/chillzone-frontend/" "~/Dropbox/programs/notes/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/NITDgpOS/MemeFinder/" "~/Downloads/gitlab.com/Compro-Prasad/test_site/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/Compro-Prasad/finalyear/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/gitlab.com/Compro-Prasad/VEgreEdge/" "~/Downloads/gitlab.com/Compro-Prasad/journal/" "~/Downloads/github.com/lugnitdgp/lugnitdgp.github...." "~/Downloads/github.com/Compro-Prasad/Bhatauli_Scho..." "~/Downloads/gitlab.com/Compro-Prasad/guessing-game..." "~/Downloads/gitlab.com/Compro-Prasad/first-rust-ap..." "~/Downloads/github.com/Compro-Prasad/lgm/" "~/Downloads/github.com/Compro-Prasad/dotfiles/emac..." "~/Downloads/github.com/Compro-Prasad/dotfiles/emac...") :action #f(compiled-function (project) #<bytecode 0x2144c0d>))
  projectile-switch-project(nil)
  funcall-interactively(projectile-switch-project nil)
  call-interactively(projectile-switch-project nil nil)
  command-execute(projectile-switch-project)

It was reported to lsp-mode repo: https://github.com/emacs-lsp/lsp-mode/issues/581

Hmmm. I tried it a week ago and the process started with 987847e. But I will take a look at it.

Do I need to do: (setq rustic-rls-pkg 'lsp-mode)

Yeah I changed the default package to eglot last week, because I didn't have a fix.

@Compro-Prasad please give my PR a go and see if it works fine for you. I am using an up to date version of lsp-mode with success.


Allow custom list type converter

See also #60
For example:
class Note {
  @JsonField(typeConverter = ImageConverter.class)
  List<Image> images;
}

@EricKuck Any plans to merge this?

This looks lika very useful feature.
Is it possible to get it in sync it with master @Saketme?
@EricKuck is it possible to get this feature prioritized?


Expected datetime, date, or time, got: '%s'" % ical

On the master branch, commit https://github.com/pimutils/todoman/commit/f2a006b2b057a33c6d06cafb7e4ab9ba7c61d8c2, todo list gives
Failed to read entry /home/konfekt/.local/share/vdirsyncer/todo/Todo4182454.ics.
Traceback (most recent call last):
  File "/home/konfekt/.local/lib/python3.6/site-packages/todoman/model.py", line 954, in update_cache
    cal = icalendar.Calendar.from_ical(cal)
  File "/home/konfekt/.local/lib/python3.6/site-packages/icalendar/cal.py", line 383, in from_ical
    vals = factory(factory.from_ical(vals))
  File "/home/konfekt/.local/lib/python3.6/site-packages/icalendar/prop.py", line 348, in from_ical
    "Expected datetime, date, or time, got: '%s'" % ical
ValueError: Expected datetime, date, or time, got: ''

as soon as the ics file contains the three empty entries
DTSTART:
STATUS:
COMPLETED:

Unfortunately, the Android applications aCalendar Tasks and OpenTasks both generate these empty fields by default.

Deleting these three empty entries resolves the error.

Looks like empty values for these fields are not valid (as per RFC5545).
If I have the time, I might work around accepting these invalid values, however, you should report this to these Android tasks, since they're generating what seems to be, invalid iCalendar files.

This issue has just been brought to my attention and I've tried to reproduce this immediately. So far I have not been successful. @Konfekt can you give me the exact steps to create such a broken ics file with OpenTasks and CalDAV-Sync? When I create a simple task with a due date in OpenTasks this gets uploaded to my server:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//dmfs.org//mimedir.icalendar//EN
BEGIN:VTODO
DUE:20181121T230000Z
CREATED:20181121T224931Z
LAST-MODIFIED:20181121T224931Z
SUMMARY:test123
STATUS:NEEDS-ACTION
DTSTAMP:20181121T224932Z
UID:21fb24f7-1bf4-4748-b257-7f437ab326fe.1542840572545
END:VTODO
END:VCALENDAR

That looks correct to me.
What kind of CalDAV server are you using? Are there any other tools involved?
Can you post a full ics that was uploaded to your server by CalDAV-Sync?
I'd advise against accepting broken input. Being fault tolerant only leads to faulty software. It's good to reject broken data and reach out to the creator of it.

Looks like a Memotoo issue. Aside from the empty fields, there is another issue with this. A CalDAV server is not supposed to change file name nor UID of the object, but Memotoo clearly changed the UID.  Also the PRODID field has been removed.
This may well be the reason for why the other direction doesn't work either. I imported your ics file onto my server and it was synced without any problem. I'll try to reactivate my Memotoo account and test it.

Thank you, yes, it would be good to know which servers do not invalidate the uploaded ICS files.


Fix dead links

1.  https://amethyst.rs/doc
https://amethyst.rs/doc contains a dead link at

Previous Stable Version (0.12)

Browse the API Reference

https://docs.amethyst.rs/v0.12.0/amethyst/returns a 404.
I don't know if they're still hosted under the amethyst.rs domain somewhere, alternatively you might want to link to https://docs.rs/amethyst/0.12.0/amethyst/ instead.
I'm not sure how to open a PR to fix this, when I search for the strings I can't find them in this repo, at least not on the master branch. It's probably in a different part of your build / content pipeline.
2. README.md
README.md links to https://amethyst-engine.org/ in line 3. The link appears to be unreachable.

Update for 0.15: Dead link is still there:

Previous Stable Version (0.14)

Browse the API Reference

]


Added Postgrex query options.

Added Postgrex connection options.
For my use case I need to increase the connection timeout for queries that took longer than 15000 ms to execute.
Added connection_options(can set here all options supported by Postgrex) to the moebius config:
 :moebius,
       connection: [
         hostname: "hostname",
         username: "username",
         password: "",
         port: 5432,
         database: "database"
       ],
       connection_options: [
        timeout: 45000
       ],
       scripts: "test/SQL"

Thanks! I do believe we pipe whatever you put in the connection straight to Postgrex... did you try to just add timeout to the options?

That was the first thing I tried, but didn’t work for me.

OK - what I'd like to do is address that as an issue as that's what's supposed to happen. Would you like to open that? Would love to see your config code as well so I could make sure I have a proper test :). Also - by "didn't work" I assume you mean that the timeout wasn't honored? If you have detail on how you figured that I would appreciate.

The Postgrex query statement is like this: query(conn, statement, params, opts \ []) where timeout is passed in the opts and not conn. You were only passing the :pool option in the Postgrex.query call(in the execute function), so other options included here in the doc: https://hexdocs.pm/postgrex/Postgrex.html#query/4 , will be ignored; that is why,  if you add the timeout on the connection it will not be honored.

Rob, did you had the time to review this PR?

No not yet


Smoke Test -> Master

Docs Build status updates of commit dc87c53:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/FrameworksIndex/azure-dotnet-preview.xml
:white_check_mark:Succeeded

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/AadAuthenticationParameters.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/Access.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/AddressSpace.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGateway.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayAuthenticationCertificate.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayAutoscaleConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayAvailableSslOptions.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayAvailableWafRuleSetsResult.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendAddress.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendAddressPool.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealth.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealthHttpSettings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealthOnDemand.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealthPool.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealthServer.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHealthServerHealth.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayBackendHttpSettings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayConnectionDraining.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayCookieBasedAffinity.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayCustomError.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayCustomErrorStatusCode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallDisabledRuleGroup.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallExclusion.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallMode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallRule.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallRuleGroup.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFirewallRuleSet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFrontendIPConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayFrontendPort.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayHeaderConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayHttpListener.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayIPConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayOnDemandProbe.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayOperationalState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayPathRule.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayPrivateEndpointConnection.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayPrivateLinkConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayPrivateLinkIpConfiguration.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayPrivateLinkResource.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayProbe.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayProbeHealthResponseMatch.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayProtocol.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Management.Network.Models/ApplicationGatewayRedirectConfiguration.xml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


how can I run your app?

after made .env file with SECRET_KEY and DEBUG,
I tried to run the server.
but it wasm't work on my computer.
below message is about error log information.
could you tell me how can I fix it?

when I checked your setting file, it has DEVELOPER_KEY.
but I have no idea to guess how can I set it.
I need your advice.

from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager
File "C:\ProgramData\Anaconda3\envs\bigdatateam\lib\site-packages\django\contr
ib\auth\base_user.py", line 47, in
class AbstractBaseUser(models.Model):
File "C:\ProgramData\Anaconda3\envs\bigdatateam\lib\site-packages\django\db\mo
dels\base.py", line 103, in new
app_config = apps.get_containing_app_config(module)
File "C:\ProgramData\Anaconda3\envs\bigdatateam\lib\site-packages\django\apps
registry.py", line 252, in get_containing_app_config
self.check_apps_ready()
File "C:\ProgramData\Anaconda3\envs\bigdatateam\lib\site-packages\django\apps
registry.py", line 135, in check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

It's the GOOGLE DEVELOPER YOUTUBE API for scraping youtube videos
https://console.developers.google.com/apis/library  and choose YouTube Data API v3 to get your api key

It's the GOOGLE DEVELOPER YOUTUBE API for scraping youtube videos
https://console.developers.google.com/apis/library and choose YouTube Data API v3 to get your api key

I'll do test it and share the result at here dude :)
thank you so much


Mbtiles charts with no name do not work

@netAction do you happen to have an example file that I could replicate this problem with?

Built using https://github.com/mapbox/mbutil from a directory with just directories of PNG tiles, no metadata file.
./mb-util --scheme=xyz --image_format=png   ./tiles/ naked-testchart.mbtiles

naked-testchart.mbtiles.zip

Confirm it works (y)


Add port to show_list of containers provider and removed commented code

@miq-bot add_label ui, enhancement, providers/containers

Just a question not for this patch
Do atomic providers have little icons for that show_list table? (same as openshift and k8s in the screenshot)

Just a question not for this patch
Do atomic providers have little icons for that show_list table? (same as openshift and k8s in the screenshot)

I'm not sure I understand the question, but if you are asking if there's a need for a smaller version of the icon, then afaik it's the same icon that gets resized through the product. There's the icon named vendor-kubernetes.png, for example, and then it's reused and resized in various screens (including topology)

I'm not sure I understand the question, but if you are asking if there's a need for a smaller version of the icon, then afaik it's the same icon that gets resized through the product. There's the icon named vendor-kubernetes.png, for example, and then it's reused and resized in various screens (including topology)

Yeah, that answers it.

@simon3z @martinpovolny @h-kataria please review

LGTM :+1:

looks good


incomplete ways after restoring

After #2135 the graph can contain incomplete ways (i.e. ways where one or more of its nodes are not present in the graph - just like incomplete relations) under certain circumstances. For example:

Have a multipolygon (or route, …) relation that spans over two data tiles A and B (way w1 is completely in A)
while editing in region A, split way w1
abort the mapping session, restore from region B
the graph will now contain the multipolygon relation, way w1 and the split remainder (say way w-1), but not any of the nodes of w1 and w-1.

I noticed that this causes problems with the current multipolygon code: it causes entity nxxx not found exceptions during graph.childNodes() because some nodes are in fact missing.
I'm not sure how to fix this properly. A possible fix (for the multipolgon case) would be to add something like the following to the relation member filter:
… && graph.entity(member.id).nodes.every(function(node) { graph.hasEntity(node.id); });

Another fix would be to include all involved (but most of the time unchanged) childNodes in the localStorages saves. But this would potentially quite blow up the amount of data to be stored.
Also, I'm not sure if similar exceptions could come up in other modules, too?

from @pnorman

The nodes and way/full calls are pretty fast now that they're running on cgimap. Could we just fetch whatever we need to complete what's incomplete?

I'm planning to fix this with nodes call to fetch the missing nodes.
from @jfirebaugh

iD must block the UI while the nodes are downloaded.

I found with conflict resolution that nodes calls are pretty fast (certainly faster than loading tiles, which is what iD would otherwise be doing).  Also I think having iD pause a few seconds after the user chooses "restore" is acceptable.

Both nodes and way/full are "current state only" -- there's no way to request particular versions or points in time. So we'd need to think about a conflict resolution strategy for cases where nodes were added or deleted.

Existing conflict resolution will handle added nodes (the user just won't see them until they save and see the conflict resolution UI).
If the nodes call returns that the node has been deleted, I can replace it with a local new node, so the renderer doesn't choke on "entity not found" errors.  Conflict resolution will catch this too and prompt the user whether to keep the node or remove it.

Today I realized:

I never actually implemented the "iD must block the UI while the nodes are downloaded." part of this..
Adding temp nodes to avoid Entity Not Found errors doesn't work because the temp nodes won't have loc, which is essential in a lot of other parts of the code (area/extent calculation)
Blocking UI alone is insufficient because the missing childnodes are loaded asynchronously and in batches, triggering map redraws.  So I needed to block both UI and redrawing while these missing child nodes are loaded asynchronously.

This was implemented in a393248, 970a5de and fixes a lot of the Entity Not Found errors that can occur after the user restores their history.


Output collides with the prompt

Description
When running neofetch after upgrading to Kubuntu 22.10, the output now collides with the prompt
Neofetch version
7.1.0
Screenshot

Config file
can't upload on pastebin, gets flagged for whatever reason, it's the default config
Verbose log
https://pastebin.com/F4kMKWeD

It’s a known issue, but there’s a workaround:
https://github.com/dylanaraps/neofetch/issues/2195#issuecomment-1246184442


Implement periodic cpu usage tracking in resource groups

This PR contains the following changes at a high level:

Periodically update and cache cpu usage for resource groups.
Add memory and cpu usage update at query completion.
Update eligibility through a post-order traversal in updateEligibilityAll after resource usage update to avoid calling updateEligibility recursively in the internalRefreshStats.
Rename processQueuedQueries to reflect what the method is doing
move memory limit check in canRunMore for better readability.

Resolves #1059 . @dain @wagnermarkd

@dain @raghavsethi I've updated the PR addressing your comments.
Numbers for TestResourceGroups benchmark:

Benchmark
(children)
(queries)
Time taken (us/op) (Before)
Time taken (us/op) (With updateEligibilityInSubTreemethod)
Time taken (us/op)(After removing updateEligibilityInSubTree method as in c16e711 )

BenchmarkResourceGroup.benchmark
1000
100
1.364
216.476
2.499

BenchmarkResourceGroup.benchmark
1000
1000
13.428
236.021
33.543

BenchmarkResourceGroup.benchmark
1000
10000
495.993
1148.303
1211.227

BenchmarkResourceGroup.benchmark
10000
100
1.094
2353.871
2.405

BenchmarkResourceGroup.benchmark
10000
1000
12.18
2489.451
26.708

BenchmarkResourceGroup.benchmark
10000
10000
445.518
4522.486
717.43

BenchmarkResourceGroup.benchmark
100000
100
1.217
33370.087
2.151

BenchmarkResourceGroup.benchmark
100000
1000
14.851
31872.003
26.752

BenchmarkResourceGroup.benchmark
100000
10000
455.631
32303.722
534.325

After seeing that the benchmark takes a lot longer to execute with updateEligibilityInSubTree method, I replaced its usage with updateEligibilityOnPathToRoot calls in internalCpuQuotaGeneration and updateResourceUsageAndGetDelta.  This change (a bit more than) doubles the time taken for the update (from before this PR), which seems reasonable to me given that we're updating two values per node now.
Removing updateEligibilityInSubTree requires us to invoke updateEligibilityOnPathToRoot method inside and internalGenerateCpuQuota. This works well for shallow trees, even with a high fanout. But I've a concern that it might not work well for deep trees. Do you think we should optimize this further?

@raghavsethi I think updateEligibilityInSubtree method created some confusion. I've removed it (here looking at the benchmark result. That might simplify things, and work well for shallow trees at least.  Happy to schedule a call if required for discussing this further.

If that's the case, it seems like we one have one updateEligibility method, can we rename it back?

@raghavsethi Addressed your comments.

Minor changes requested, looks generally good.

@raghavsethi Thanks for the review, I've updated the PR addressing your latest comments.

It's definitely not great behavior and could lead to a lot of user confusion, did your change make this worse? If not, then you can address it in a follow up PR.

This has been the behavior before the change as well. But it starves a queued query only if new queries submitted between the invocation of cpu quota generation and updateGroupsAndProcessQueuedQueries exceed limits instantaneously.

Can you go ahead and squash your commits into a single commit?

@phd3 could you provide a draft of the release notes for this change?

Merged, thanks for your contribution!

when we upgrade to version 318 or later we found that there is a very big bug

Could you provide your resource groups config file?


FAQ Plus Running Script issue

I went through the guided steps for implementing FAQ Plus and after running the script for deploy to Azure, we didn’t find any resources created in the Azure.
Attached screen shot for the error generated during running the script.
Please advise.

Please advise on this issue? noting that its production environment and i am in urgent need to fix the issue

there's been a couple of changes to the az ad app cmdlets.
I have resolved these by updating the deploy.ps1 script:
az ad app update --id $app.appId --sign-in-audience AzureADMultipleOrgs --enable-id-token-issuance $AllowImplicitFlow --required-resource-accesses './AdAppManifest.json'
az ad app create --display-name $appName --end-date '2299-12-31T11:59:59+00:00' --sign-in-audience AzureADMultipleOrgs --enable-id-token-issuance $AllowImplicitFlow --required-resource-accesses './AdAppManifest.json'
az ad app update --id $app.appId --web-redirect-uris @RedirectUris


shortcuts!

really small scale, but I miss shortcuts when they're not present. suggestions:

cmd-[ and cmd-] for page back and page forward
cmd-, for settings (eventually)
cmd-/ for keyboard shortcuts display
probably a chord for update-all; cmd-shift-a?
probably something simple cmd-(1,2,3,4,5,6,7?) for swapping main sections
alt(-shift)?-up/down likely useful for switching sections too

possibly the first ones to be implement are cmd-/, next,prev,
the rest no idea where to connect them atm


Don't submit wrapper pull requests to WS Repos for every PR on this repo

This (https://github.com/adafruit/Wippersnapper_Protobuf/pull/121#pullrequestreview-1192348381) should not have submitted a pull request. We may want to update the workflow to only submit wrapper pull requests on release, and create a new release for it.
Not sure how to parse it out otherwise, suppose we could check if the PR contains .proto files.
@lorennorman  - thoughts?

Yep we can check if .proto files were modified. I do similar stuff in the components and boards repos to make sure only certain files are modified, it starts with the gather-relevant-files job and the files list gets input into later steps. So we have a jumping off point when we're ready to fix this.


Move some dosomething_sms workflows into separate ds-mdata-responder tool

Comeback Clothes has the start-campaign transition and tip delivery in dosomething_sms.workflows.inc. Let's take it out of there and move it to the ds-mdata-responder tool.

[ ] add to ds-mdata-responder
[ ] remove from dosomething_sms.workflows.inc
[ ] update mData settings on Mobile Commons

omg this is the most done thing that's never been closed

Whoa whoa whoa, this is still on my todo list


HDFS-17476. fix: False positive "Observer Node is too far behind" due to long overflow.

Description of PR
seeAlse : https://issues.apache.org/jira/browse/HDFS-17476
In the code GlobalStateIdContext#receiveRequestState(), if clientStateId is a small negative number, clientStateId-serverStateId may be greater than
（ESTIMATED_TRANSACTIONS_PER_SECOND due to overflow
* TimeUnit.MILLISECONDS.toSeconds(clientWaitTime)
* ESTIMATED_SERVER_TIME_MULTIPLIER）,
resulting in false positives that Observer Node is too far behind.

How was this patch tested?
hi, I'm not sure whether I need to add a new UT. I think the existing UT is ok.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 19s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 51s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 46s

trunk passed

+1 :green_heart:
shadedclient
21m 28s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  2s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 42s

the patch passed

+1 :green_heart:
shadedclient
21m  0s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
206m 50s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

296m 59s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6747/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6747

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 65c6ad4a45da 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4208a984b11713148b6b6eba9f898d3d16c41fdd

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6747/1/testReport/

Max. process+thread count
4062 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6747/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

I have run multiple ut checks locally that failed, and they all passed.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 00s

No case conflicting files found.

+0 :ok:
spotbugs
0m 00s

spotbugs executables are not available.

+0 :ok:
codespell
0m 00s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m 00s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
91m 28s

trunk passed

+1 :green_heart:
compile
6m 17s

trunk passed

+1 :green_heart:
checkstyle
5m 00s

trunk passed

+1 :green_heart:
mvnsite
6m 56s

trunk passed

+1 :green_heart:
javadoc
6m 10s

trunk passed

+1 :green_heart:
shadedclient
152m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 48s

the patch passed

+1 :green_heart:
compile
3m 43s

the patch passed

+1 :green_heart:
javac
3m 43s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 28s

the patch passed

+1 :green_heart:
mvnsite
4m 17s

the patch passed

+1 :green_heart:
javadoc
3m 41s

the patch passed

+1 :green_heart:
shadedclient
162m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 46s

The patch does not generate ASF License warnings.

434m 43s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6747

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
MINGW64_NT-10.0-17763 cf76230213b6 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 4208a984b11713148b6b6eba9f898d3d16c41fdd

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/1/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/1/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 00s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m 00s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
85m 56s

trunk passed

+1 :green_heart:
compile
6m 03s

trunk passed

+1 :green_heart:
checkstyle
4m 37s

trunk passed

+1 :green_heart:
mvnsite
6m 15s

trunk passed

+1 :green_heart:
javadoc
5m 43s

trunk passed

+1 :green_heart:
shadedclient
141m 45s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 27s

the patch passed

+1 :green_heart:
compile
3m 20s

the patch passed

+1 :green_heart:
javac
3m 20s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 16s

the patch passed

+1 :green_heart:
mvnsite
3m 52s

the patch passed

+1 :green_heart:
javadoc
3m 20s

the patch passed

+1 :green_heart:
shadedclient
152m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 08s

The patch does not generate ASF License warnings.

406m 30s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6747

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
MINGW64_NT-10.0-17763 5b0a86518b3f 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 4208a984b11713148b6b6eba9f898d3d16c41fdd

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/2/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/2/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@Hexiaoqiao @ZanderXu @haiyang1987 hi, If you have time, please help to take a look at this pr, thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 01s

No case conflicting files found.

+0 :ok:
spotbugs
0m 00s

spotbugs executables are not available.

+0 :ok:
codespell
0m 00s

codespell was not available.

+0 :ok:
detsecrets
0m 00s

detect-secrets was not available.

+1 :green_heart:
@author
0m 01s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m 00s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
87m 35s

trunk passed

+1 :green_heart:
compile
6m 26s

trunk passed

+1 :green_heart:
checkstyle
4m 52s

trunk passed

+1 :green_heart:
mvnsite
6m 36s

trunk passed

+1 :green_heart:
javadoc
6m 08s

trunk passed

+1 :green_heart:
shadedclient
144m 09s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 28s

the patch passed

+1 :green_heart:
compile
3m 23s

the patch passed

+1 :green_heart:
javac
3m 23s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 18s

the patch passed

+1 :green_heart:
mvnsite
3m 57s

the patch passed

+1 :green_heart:
javadoc
3m 37s

the patch passed

+1 :green_heart:
shadedclient
154m 32s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 17s

The patch does not generate ASF License warnings.

413m 25s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6747

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
MINGW64_NT-10.0-17763 cdbf5294217d 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 5f6e761f92c501b59ae53a552e64b5d6f54f20c1

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/3/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6747/3/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Hi @haiyang1987 @ZanderXu would you mind to take review?


Fail CI if rake swig causes changes

Closes https://github.com/robinst/taglib-ruby/issues/136
This adds a CI check that will cause a failed check if we accidentally commit a _wrap.cxx file that does not match the corresponding .i file.

Here is an example failure, triggered by an intentionally wrong modified wrap file:
https://github.com/robinst/taglib-ruby/actions/runs/8602424269/job/23571960305?pr=139

I will remove the "wrong" test commit now.

Nice, thanks! Merged.


Review comment links don't work for files that exceed max_git_diff limits

Gitea Version
1.16.0+dev-581-gbaed01f24
Git Version
No response
Operating System
No response
How are you running Gitea?
try.gitea.io
Database
No response
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
With #16829 and #17739 we can now display files beyond MAX_GIT_DIFF_FILES and MAX_GIT_DIFF_LINES, and add review comments on them.
But the files view initially only loads the first page of files, and only those files that don't exceed the max lines.
So direct links (e.g. when navigating from the conversation view) to comments that are added on such files do not work.
Example:

https://try.gitea.io/jpraet-org/test-repo/pulls/1/files#issuecomment-112226 (a comment on file 105, but only 100 are loaded)
https://try.gitea.io/jpraet-org/test-repo/pulls/2/files#issuecomment-112222 (a commend on a large file)

Screenshots
No response

I don't think we can fix this very easily.

It depends on our frontend refactoring to provide a better frontend component mechanism.

It depends on our frontend refactoring to provide a better frontend component mechanism.

So, the front-end can detect that isssuecomment-xxx is specified in the URL, and it can very easily check if it's in the DOM.
When the code knows that it's the DOM, do nothing, but if it sees that isssuecomment-xxx isn't in the dom, and it sees that the show more files button is present(and code will make a guess that this comment is in those files), then it could show a popup:
"It seems like that a specific comment should be shown, but the comment could not be found in the loaded files. Would you like to load the additional files of this PR and see if it's present in those" (something along those lines).


rtaudio: 5.2.0 -> 6.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/thestk/rtaudio/releases.
meta.description for rtaudio is: A set of C++ classes that provide a cross platform API for realtime audio input/output
meta.homepage for rtaudio is: https://www.music.mcgill.ca/~gary/rtaudio/
Closes #274031.
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.0 with grep in /nix/store/a4wfdzw4a0b8icsq66x86gbbpv001j32-rtaudio-6.0.0
found 6.0.0 in filename of file in /nix/store/a4wfdzw4a0b8icsq66x86gbbpv001j32-rtaudio-6.0.0

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

44 total rebuild path(s)

44 package rebuild(s)

First fifty rebuilds by attrpath
abracadabra
bambootracker
bambootracker-qt6
cubicsdr
djv
flowblade
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_9Packages.osmosdr
gnuradioPackages.osmosdr
gqrx
gqrx-gr-audio
gqrx-portaudio
hikounomizu
jacktrip
libsForQt5.kdenlive
libsForQt5.mlt
mlt
muse
openwebrx
opl3bankeditor
opn2bankeditor
plasma5Packages.kdenlive
plasma5Packages.mlt
pothos
python310Packages.mlt
python310Packages.soapysdr-with-plugins
python311Packages.mlt
python311Packages.soapysdr-with-plugins
qradiolink
rtaudio
rtl_433
sdrangel
sdrpp
shotcut
sigdigger
soapyaudio
soapysdr-with-plugins
srsran
suscan
synfigstudio
theforceengine
welle-io
zrythm

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a4wfdzw4a0b8icsq66x86gbbpv001j32-rtaudio-6.0.0
ls -la /nix/store/a4wfdzw4a0b8icsq66x86gbbpv001j32-rtaudio-6.0.0/bin

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

42 packages failed to build:

abracadabra
bambootracker
bambootracker-qt6
cubicsdr
djv
flowblade
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_9Packages.osmosdr
gnuradioPackages.osmosdr
gqrx
gqrx-gr-audio
gqrx-portaudio
hikounomizu
jacktrip
libsForQt5.kdenlive
libsForQt5.mlt
mlt
muse
openwebrx
opl3bankeditor
opn2bankeditor
pixinsight
pothos
python310Packages.mlt
python310Packages.soapysdr-with-plugins
python311Packages.mlt
python311Packages.soapysdr-with-plugins
qradiolink
rtl_433
sdrangel
sdrpp
shotcut
sigdigger
soapyaudio
soapysdr-with-plugins
srsran
suscan
synfigstudio
theforceengine
welle-io
zrythm

1 package built:

rtaudio

Maintainer pings
cc @magnetophon for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/thestk/rtaudio/releases.
meta.description for rtaudio is: A set of C++ classes that provide a cross platform API for realtime audio input/output
meta.homepage for rtaudio is: https://www.music.mcgill.ca/~gary/rtaudio/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.1 with grep in /nix/store/0kcsa6mc739cw0k348211m8gfic118x3-rtaudio-6.0.1
found 6.0.1 in filename of file in /nix/store/0kcsa6mc739cw0k348211m8gfic118x3-rtaudio-6.0.1

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

42 total rebuild path(s)

42 package rebuild(s)

First fifty rebuilds by attrpath
abracadabra
cubicsdr
djv
flowblade
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_9Packages.osmosdr
gnuradioPackages.osmosdr
gqrx
gqrx-gr-audio
gqrx-portaudio
hikounomizu
jacktrip
libsForQt5.kdenlive
libsForQt5.mlt
mlt
muse
openwebrx
opl3bankeditor
opn2bankeditor
plasma5Packages.kdenlive
plasma5Packages.mlt
pothos
python310Packages.mlt
python310Packages.soapysdr-with-plugins
python311Packages.mlt
python311Packages.soapysdr-with-plugins
qradiolink
rtaudio
rtl_433
sdrangel
sdrpp
shotcut
sigdigger
soapyaudio
soapysdr-with-plugins
srsran
suscan
synfigstudio
theforceengine
welle-io
zrythm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0kcsa6mc739cw0k348211m8gfic118x3-rtaudio-6.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0kcsa6mc739cw0k348211m8gfic118x3-rtaudio-6.0.1
ls -la /nix/store/0kcsa6mc739cw0k348211m8gfic118x3-rtaudio-6.0.1/bin

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

40 packages failed to build:

abracadabra
cubicsdr
djv
flowblade
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_9Packages.osmosdr
gnuradioPackages.osmosdr
gqrx
gqrx-gr-audio
gqrx-portaudio
hikounomizu
jacktrip
libsForQt5.kdenlive
libsForQt5.mlt
mlt
muse
openwebrx
opl3bankeditor
opn2bankeditor
pixinsight
pothos
python310Packages.mlt
python310Packages.soapysdr-with-plugins
python311Packages.mlt
python311Packages.soapysdr-with-plugins
qradiolink
rtl_433
sdrangel
sdrpp
shotcut
sigdigger
soapyaudio
soapysdr-with-plugins
srsran
suscan
synfigstudio
theforceengine
welle-io
zrythm

1 package built:

rtaudio

Maintainer pings
cc @magnetophon for testing.

LGTM

@ofborg eval

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

34 packages failed to build:

abracadabra
cubicsdr
djv
gnuradio
gnuradio3_8
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_8Packages.osmosdr.dev
gnuradio3_9
gnuradio3_9Packages.osmosdr
gnuradio3_9Packages.osmosdr.dev
gnuradioPackages.osmosdr
gnuradioPackages.osmosdr.dev
gqrx
gqrx-gr-audio
gqrx-portaudio
jacktrip
openwebrx
openwebrx.dist
opl3bankeditor
opn2bankeditor
pothos
python311Packages.soapysdr-with-plugins
python312Packages.soapysdr-with-plugins
qradiolink
rtl_433
sdrangel
sigdigger
soapyaudio
soapysdr-with-plugins
srsran
suscan
welle-io
zrythm

20 packages built:

flowblade
hikounomizu
krita
libsForQt5.kdenlive (plasma5Packages.kdenlive)
libsForQt5.mlt (plasma5Packages.mlt)
libsForQt5.mlt.dev (plasma5Packages.mlt.dev)
mlt
mlt.dev
muse
python311Packages.mlt
python311Packages.mlt.dev
python312Packages.mlt
python312Packages.mlt.dev
qt6Packages.mlt (yuzuPackages.mlt)
qt6Packages.mlt.dev (yuzuPackages.mlt.dev)
rtaudio
sdrpp
shotcut
synfigstudio
theforceengine

Main failure is soapyaudio, on which all of the radio stuff depends.

soft bump

soft bump

r-ryantm is a bot, if there a re build failures a new pr must be made

soft bump

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

1 package marked as broken and skipped:

yuzuPackages.mlt

33 packages failed to build:

abracadabra
cubicsdr
djv (djv-2.0.8-unstable-2021-07-31.log)
gnuradio
gnuradio3_8
gnuradio3_8Packages.ais
gnuradio3_8Packages.osmosdr
gnuradio3_8Packages.osmosdr.dev
gnuradio3_9
gnuradio3_9Packages.osmosdr
gnuradio3_9Packages.osmosdr.dev
gnuradioPackages.osmosdr
gnuradioPackages.osmosdr.dev
gqrx
gqrx-gr-audio
gqrx-portaudio
openwebrx
openwebrx.dist
opl3bankeditor (opl3bankeditor-1.5.1.log)
opn2bankeditor (opn2bankeditor-1.3.log)
pothos
python311Packages.soapysdr-with-plugins
python312Packages.soapysdr-with-plugins
qradiolink
rtl_433
sdrangel
sigdigger
soapyaudio (soapyaudio-0.1.1.log)
soapysdr-with-plugins
srsran
suscan
welle-io
zrythm (zrythm-1.0.0-beta.4.9.1.log)

21 packages built:

flowblade
hikounomizu
jacktrip
krita
libsForQt5.kdenlive (plasma5Packages.kdenlive)
libsForQt5.mlt (plasma5Packages.mlt)
libsForQt5.mlt.dev (plasma5Packages.mlt.dev)
mlt
mlt.dev
muse
python311Packages.mlt
python311Packages.mlt.dev
python312Packages.mlt
python312Packages.mlt.dev
qt6Packages.mlt
qt6Packages.mlt.dev
rtaudio
sdrpp
shotcut
synfigstudio
theforceengine

I'm not in favour of landing this as-is, as it would still break the significant amount of RtAudio uses. If RtAudio 6.x is urgently desired, then smth like a separate rtaudio_6 could be proposed, and the regular rtaudio could eventually be switched over to 6.x.
Tickets need to be raised / fixes need to be sent in the respective upstreams to make them compatible with 6.x.

At least one of those applications (zrythm) has been updated to work with rtaudio v6, but is waiting on this package to be updated before our package can be updated. zrythm is waiting on the gnome 46 PR to be merged too, so this is not its only holdup. I don't know about the radio packages though. Merging as rtaudio_6 might be the way to go for now.

[zrythm] has been updated to work with rtaudio v6, but is waiting on this package to be updated before our package can be updated

To avoid this "who should be bumped first" situation, maybe the commit(s) with the v6 changes could be applied/reverted based on the rtaudio version? i.e. what https://github.com/NixOS/nixpkgs/pull/246368 tried to do.

I don't know about the radio packages though.

Most of the failures come from their dependency soapyaudio FTBFS.


LazyColumn gets stuck scrolling when an item is too big.

I haven't isolated a reproducer for this yet but when the size of an item in the LazyColumn is really close to size of the LazyColumn itself, the scrollbar keeps snapping back, preventing further scrolling.
To escape this, I have to scrolll very aggressively, or fast enough to beat the snap.

Note to self: https://github.com/androidx/androidx/blob/d3a8167883356ee9c2d8cc7b48cc0463a8780c74/compose/foundation/foundation/src/desktopMain/kotlin/androidx/compose/foundation/Scrollbar.desktop.kt#L458

Fix 0.5.0........

Sorry this has nothing to do with srollbar. LazyColumn does this by itself.

https://user-images.githubusercontent.com/14130965/125849316-8885173f-faf6-4b52-8e66-b5d42a56e3fb.mp4

Tracked it down to this here https://github.com/androidx/androidx/blob/9f596ce819a7fd24401992aa249596d0dbc21d1d/compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/lazy/LazyListMeasure.kt#L34 .

Moved to here https://issuetracker.google.com/issues/179593134 . It's not desktop specific.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Dropdown menus instantiation

I don't know if this is a bug or a documentation issue. I spent several hours trying to figure out why my dropdown menus (copying the site example directly) looked like this:

Then I realized I need to manually instantiate them using
new Foundation.DropdownMenu($(['data-dropdown-menu']), {});

I thought this was the purpose of adding the data-dropdown-menu attribute. Am I missing something obvious, or does the documentation need to be more specific that adding Javascript code is necessary to get them to work?!

Your JavaScript might not be initializing properly. Make sure you're calling $(document).foundation(). If that doesn't work, check to see if you have any console errors.

Closing based on lack of response.  If you're still seeing this please reopen with info about how you are initializing the foundation javascript.


FAB-4267 Homebrew installer for MacOSX

remove peer
Change-Id: Iac33f2360209341a698b313930f92fd153c7034e
Signed-off-by: Christopher Ferris<EMAIL_ADDRESS>

Thank you for your contribution! This is a read only mirror, however. Please submit your change using gerrit.
you would need to check out the repo here: https://gerrit.hyperledger.org/r/#/admin/projects/homebrew-fabric and make your edits, pushing them to gerrit
here is a walkthrough for zephyrproject which is much the same WRT setting up an LFID, adding ssh keys, etc:
https://www.zephyrproject.org/doc/1.1.0/collaboration/code/gerrit_accounts.html
feel free to ask on rocket.chat - https://chat.hyperledger.org/ - discuss in #fabric
one note: when you set up your LFID do not use social logins the first time, create the account and you can add social logins later


Expose memfd on (Free?)BSD

According to the FreeBSD man pages memfd_create() has been present since 13.0. Should it be exported like it is for Android and Linux?

Yes.  Would you like to prepare a PR?

Sure thing


Junk piles can end up floating in the air when terraforming

Reproduction: terraform on a tile with junk on it!

Never made it to main 😅


Add list of implemented elements to README

A list of elements that have been implemented as PlantUML elements should be added to the README, so that it is easy to quickly check to see which components can be added to diagrams without checking the individual .puml files.

all components now have sprites and macros


[sw, secure_boot] Secure Boot integration: on-device tests

Introduction
The production chip will run Secure Boot, which means that all the on-device tests should be run via Mask ROM -> ROM_EXT -> test chain. At this point all the on-device tests use "legacy" boot rom in sw/device/boot_rom and "legacy" flash loader in sw/device/exts.
The end goal is to shift completely from the "legacy" execution chain to Secure Boot. This issue outlines several paths to this goal.
Solution 1 - Gradual transition
Gradual transition without disrupting current CI and development flow. The main idea is to create redundancy - all of the existing tests would run as normal. But with minimal effort we "piggy-back" the Secure Boot tests onto existing framework. The example of this approach can be found in #5352 .
This approach doesn't require additional step in Azure Pipelines, both test sets will be executed in the same step.
Upsides:

Gradual and non-invasive

Downsides (Please not that eventually these downsides are expected to disappear - with the final switch):

Redundancy
Longer CI execution times

Solution 2 - full transition
Full transition from running tests on the "legacy" boot_rom to Secure Boot.
Upsides:

Done in one go
No redundancy
Similar CI execution times

Downsides:

More to consider
More disruptive
Harder to pinpoint issues
One big PR

Additional comments
This issue is intended as conversation starter, any comments and suggestions are very welcome.
Open questions

Should we have a stripped down version of Mask ROM and ROM_EXT for some testing?
...

The production chip will run Secure Boot, which means that all the on-device tests should be run via Mask ROM -> ROM_EXT -> test chain.

I question that assumption, at least in that generality. I see two types of tests:

Applications that will run on OpenTitan "production" and/or use multiple subsystems that need to be properly initialized.
Low-level unit or smoke tests (e.g. the DIF smoke tests), typically using a single IP block.

Tests of the first category benefit from running them in a "close to production" environment, i.e. after the full ROM/ROM_EXT has completed.
Tests of the second category are meant to test low-level hardware interaction. They are often run in HW development environments to smoke-test the software interface and the hardware block itself. There I mainly value test execution time and a high signal-to-noise ratio: I want to focus on the test code itself, not debug a potentially huge framework around it.
So what's the story on "time to test" with the mask rom-based approach? How many cycles do we need to execute in the bootloader before we reach the test itself?

So what's the story on "time to test" with the mask rom-based approach? How many cycles do we need to execute in the bootloader before we reach the test itself?

That is a good question. The honest answer is that - at the moment we don't know.
Also, I am not sure that the sequence of how we test the DIFs, etc... is optimal - as some of the DIFs are used inside the boot_rom or Mask ROM, before the tests are run.

Thanks for creating this issue @silvestrst. I think how we transition to the new Mask ROM code and which Mask ROM code we use for tests are somewhat orthogonal:
Lean Mask ROM for focused tests: I didn't see this in the meeting notes but IIRC we mentioned that we should probably have a lean version of the Mask ROM (similar to what we have right now) for smoke-tests and DV as @imphil points out (for better test execution time and less noise). The thing is, since we don't have this distinction right now, we can keep using the current code for most of the tests until we have a plan for the lean version. But when we are ready, that transition should probably be gradual.

So what's the story on "time to test" with the mask rom-based approach? How many cycles do we need to execute in the bootloader before we reach the test itself?

We don't have a number yet but I think it is safe to assume that it won't be negligible due to signature verification.
Transition: IMHO we should handle this gradually as you captured in the first bullet, i.e.

keep implementing the new Mask ROM code (along unit-tests that run on the host),
add necessary tests to the CI (in a run-but-ignore fashion initially),
announce the change,
swap the new and old code, and
remove the old one after we are confident.

So what do you guys think of the #5352 approach?

@alphan am I understanding correctly that you are suggesting we start gradually switching to Mask ROM based on-device testing once we have this "lightweight Mask ROM" for testing?
But in general, what are you thoughts on dupping testing for CI purposes and gradually adding different testing bits to Mask ROM, like in #5352?

For me, the questions are:
Looking ahead, do we want smoke tests be booted by the 'full' mask ROM? => Consensus is that even if we did support this, we'd want a stripped down mask ROM too. Is there any value at all in having these tests loaded via the mask ROM? Is "run all existing smoke tests via the mask ROM" itself intended as a mask ROM smoke test?

Is there any value at all in having these tests loaded via the mask ROM?

Well, my rationale is following - the production code will be Mask ROM, so we should run any on-device tests that add to the coverage via Mask ROM. Practically there probably is not too much difference, but it is better to be safe than sorry.

@mundaym can this be closed?

Yes I think so.


Update sbt to 1.4.7

Updates org.scala-sbt:sbt from 1.4.6 to 1.4.7.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch

Superseded by #460.


100% CPU usage (sometimes)

Version: 0.4.0
Platform: Linux  5.7.7-arch1-1 #1 SMP PREEMPT Wed, 01 Jul 2020 14:53:16 +0000 x86_64 GNU/Linux
Subsystem: ?
Rust: rustc 1.45.0

I see similar behaviour as #109. If I run a simple bastion program, ~50% of the runs one of my cpus goes to 100%
I can reproduce this with something as simple as:
fn main() {
    let config = Config::new().hide_backtraces();
    Bastion::init_with(config);
    Bastion::start();
    Bastion::block_until_stopped();
}

Hey, that's an interesting one, I'll try to reproduce it!

I need to dig deeper with a profiler, but I just ran into a lot of allocations / resizes in the hot path while profiling something else, #260 may or may not have an impact here ^^

     5.03%  bastion-async-t  weird             [.] _ZN99_$LT$core..iter..adapters..Enumerate$LT$I$GT$$u20$as$u20$core..iter..traits..iterator..Iterator$GT$4next17h4df0d33504e02321E
     4.86%  bastion-async-t  weird             [.] _ZN85_$LT$core..slice..Iter$LT$T$GT$$u20$as$u20$core..iter..traits..iterator..Iterator$GT$4next17h7c6ba6c4ca7d97bfE
     4.12%  bastion-async-t  weird             [.] _ZN5alloc5slice10merge_sort17heb79efdfbfab3bedE
     3.92%  bastion-async-t  weird             [.] _ZN5alloc5slice11insert_head17hf6717e21221c8cabE
     3.63%  bastion-async-t  weird             [.] _ZN4core4sync6atomic11atomic_load17he0b9c62d2c6d7ceaE```

So I've been able to reproduce it, and I'm working on it through #261 261

Ok I think it starts looking good!
@anlumo @pietgeursen could you please give it an other try targeting igni/affine_steal_sort on bastion and bastion-executor ? 🙏

Nice one @o0Ignition0o!
I tried out that branch and it seems to fix it. My testing is super basic, I'm just starting and stopping the program a bunch and checking the cpu usage. But cpu usage always stays low.

Amazing news! There's still a couple of tweaks I'm trying to perform, but it will definitely have a good impact for everyone, thanks a lot for raising this issue!


PR_SET_MDWE and PR_GET_MDWE

Requesting support for PR_SET_MDWE and PR_GET_MDWE (Linux 6.3) as seen in the following PoC.
#![forbid(unsafe_op_in_unsafe_fn)]
#![allow(non_camel_case_types)]

use core::ffi::*;
use core::ptr;

type c_size_t = usize;
type c_off_t = i64;

const PR_SET_MDWE: i32 = 65;
//const PR_GET_MDWE: i32 = 66;

// Bitflags
const PR_MDWE_REFUSE_EXEC_GAIN: u64 = 1;

//const PROT_NONE: c_int = 0;
const PROT_READ: c_int = 1;
const PROT_WRITE: c_int = 2;
const PROT_EXEC: c_int = 4;

const MAP_PRIVATE: c_int = 0x0002;
const MAP_ANONYMOUS: c_int = 0x0020;

const MAP_FAILED: *mut c_void = -1 as _;

const EACCES: c_int = 13;

extern "C" {
    fn prctl(option: c_int, arg2: c_ulong, arg3: c_ulong, arg4: c_ulong, arg5: c_ulong) -> c_int;
    fn mmap(
        addr: *mut c_void,
        length: c_size_t,
        prot: c_int,
        flags: c_int,
        fd: c_int,
        offset: c_off_t,
    ) -> *mut c_void;
    fn mprotect(addr: *mut c_void, len: c_size_t, prot: c_int) -> c_int;
    fn __errno_location() -> *mut c_int;
}

fn prctl_set_mdwe(bits: u64) {
    let rv = unsafe { prctl(PR_SET_MDWE, bits, 0, 0, 0) };
    assert!(rv == 0);
}

fn main() {
    prctl_set_mdwe(PR_MDWE_REFUSE_EXEC_GAIN);

    let ptr1 = unsafe {
        mmap(
            ptr::null_mut(),
            4,
            PROT_WRITE | PROT_EXEC,
            MAP_PRIVATE | MAP_ANONYMOUS,
            -1,
            0,
        )
    };
    assert!(unsafe { *__errno_location() } == EACCES);
    assert!(ptr1 == MAP_FAILED);

    let ptr2 = unsafe {
        mmap(
            ptr::null_mut(),
            4,
            PROT_READ | PROT_WRITE,
            MAP_PRIVATE | MAP_ANONYMOUS,
            -1,
            0,
        )
    };
    let rv2 = unsafe { mprotect(ptr2, 4, PROT_EXEC) };
    assert!(unsafe { *__errno_location() } == EACCES);
    assert!(rv2 == -1);

    let ptr3 = unsafe {
        mmap(
            ptr::null_mut(),
            4,
            PROT_READ | PROT_EXEC,
            MAP_PRIVATE | MAP_ANONYMOUS,
            -1,
            0,
        )
    };
    let rv3 = unsafe { mprotect(ptr3, 4, PROT_EXEC) };
    assert!(rv3 == 0);
}

btw, thanks. Choosing this crate was a good decision.


Update Issue - 90363111

default description
URL tested: http://ci.bsstag.com/welcome
Open URL on Browserstack

Property
Value

Browser
Chrome 76.0

Operating System
Windows 7

Resolution
1024x612

Screenshot Attached
Screenshot URL

Click here to reproduce the issue on Browserstack

Updated Screenshot Attached


fix: check if global is available before accessing its property

This shouldn't be necessary anymore. This was fixed in https://github.com/scniro/react-codemirror2/pull/260, but I don't think we pushed an updated tsc compilation from the previous fix.


refactor(mediator): remove client-webapi

We're currently processing your upload.  This comment will be updated when the results are available.