Issue with CHROME_EXECUTABLE when used with Arc Browser

Steps to reproduce
I have installed Arc browser and I only have two browsers on my macOS system. Safari and Arc. So while running flutter doctor I always had an error saying Chrome Browser is missing. I set CHROME_EXECUTABLE to point to the Arc app so Flutter knows I am using that browser.
Now every time I run flutter doctor or even open a flutter project in VS Code I am getting this issue.
Steps:

Install Arc Browser
Set CHROME_EXECUTABLE to Arc App
Run flutter doctor or just open any flutter project in VSCode
You will see a new window or error dialog of Arc (screenshot attached)

Also running flutter doctor takes time after showing VS Code (version 1.89.0) because after that line flutter checks for available devices. That scanning process took some time and showed the dialog I mentioned and in the case of flutter doctor -v, the command got stuck at searching for connected devices until I closed that dialog.
Expected results
flutter doctor should run normally as CHROME_EXECUTABLE set to Chrome Browser path as Arc is also a Chromium-based browser.
Actual results
While running flutter doctor or opening a flutter project on VSCode Arc displays that error window.
While running flutter doctor -v command got stuck scanning for connected devices until I closed the error window of Arc that opened after running this command.
Code sample
Code sample
flutter doctor
flutter doctor -v

Screenshots or Video

Screenshots / Video demonstration

Here is the Screen Recording
https://drive.google.com/file/d/1edTlctlX2ql7xgPUOnh1zlrL9I_3Uuqp/view

Flutter Doctor output
Doctor output of Stable
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.4.1 23E224 darwin-arm64, locale en-US)
    • Flutter version 3.19.6 on channel stable at /Users/os/Developer/sdk/flutter
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision 54e66469a9 (3 weeks ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc1)
    • Android SDK at /Users/os/Library/Android/sdk
    • Platform android-34, build-tools 35.0.0-rc1
    • ANDROID_HOME = /Users/os/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/os/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Arc.app/Contents/MacOS/Arc

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.89.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.88.0

[✓] Connected device (2 available)
    • macOS (desktop)   • macos                                         • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)      • chrome                                        • web-javascript •

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Doctor output of Master Chanel
[!] Flutter (Channel master, 3.22.0-30.0.pre.11, on macOS 14.4.1 23E224 darwin-arm64, locale en-US)
    • Flutter version 3.22.0-30.0.pre.11 on channel master at /Users/os/Developer/sdk/flutter-dev
    ! Warning: `flutter` on your path resolves to /Users/os/Developer/sdk/flutter/bin/flutter, which is not inside your current Flutter SDK
      checkout at /Users/os/Developer/sdk/flutter-dev. Consider adding /Users/os/Developer/sdk/flutter-dev/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/os/Developer/sdk/flutter/bin/dart, which is not inside your current Flutter SDK checkout at
      /Users/os/Developer/sdk/flutter-dev. Consider adding /Users/os/Developer/sdk/flutter-dev/bin to the front of your path.
    ! Upstream repository git@github.com:kishan-dhankecha/flutter.git is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to git@github.com:kishan-dhankecha/flutter.git to dismiss this error.
    • Framework revision c90e18c6f5 (9 hours ago), 2024-05-09 20:32:11 -0700
    • Engine revision c0917b14fc
    • Dart version 3.5.0 (build 3.5.0-138.0.dev)
    • DevTools version 2.36.0-dev.5
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks
      and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc1)
    • Android SDK at /Users/os/Library/Android/sdk
    • Platform android-34, build-tools 35.0.0-rc1
    • ANDROID_HOME = /Users/os/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/os/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Arc.app/Contents/MacOS/Arc

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.89.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.88.0

[✓] Connected device (3 available)
    • macOS (desktop)                 • macos                                         • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad                         • darwin         • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                    • chrome                                        • web-javascript •

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

I never heard about Arc Browser before, but it is obviously a different browser than Chrome. I don't understand why you want to specify it as a CHROME_EXECUTABLE. Even though it claims to be a Chromium-based, it doesn't mean that it is 100% compatible with Chrome. It is possible that browser doesn't support some features that Flutter needs.
If you want to use a different browser, you can run flutter with $ flutter run -d web-server and then open the browser of your choice and navigate to http://localhost:PORT where PORT is the port number that flutter printed to the console.

I can reproduce this with Arc but not with Edge(another chromium-based browser).  Arc might be doing something else that under the hood that leads to the crash/delay with retrieving the connected devices.
Labeling for further investigation

flutter doctor -v
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.4.1 23E224 darwin-arm64, locale en-GB)
    • Flutter version 3.19.6 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (4 weeks ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Arc.app/Contents/MacOS/Arc

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.88.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.88.0

[✓] Connected device (4 available)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.4.1 21E236
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript •

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.22.0-31.0.pre.21, on macOS 14.4.1 23E224 darwin-arm64, locale en-GB)
    • Flutter version 3.22.0-31.0.pre.21 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current
      Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front
      of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current
      Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c336c2a44e (69 minutes ago), 2024-05-13 01:47:29 -0400
    • Engine revision 57e74a1b38
    • Dart version 3.5.0 (build 3.5.0-147.0.dev)
    • DevTools version 2.36.0-dev.5
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to
      perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Arc.app/Contents/MacOS/Arc

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.88.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.88.0

[✓] Connected device (5 available)
    • Nexus (mobile)                  • 00008020-001875E83A38002E • ios            • iOS 17.4.1 21E236
    • Dean’s iPad (mobile)            • 00008103-000825C811E3401E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript •

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Thanks for the detailed issue report!
To my knowledge, Flutter only officially supports debugging with Google Chrome^1. Flutter will try to work with any Chromium-based browser (like Edge), but compatibility is not guaranteed.
If you wish to test your Flutter web app on Arc, @bc-lee's earlier comment might be helpful.


Pin resilience4j-retry version temporarily

Due to https://github.com/resilience4j/resilience4j/issues/1472, resilience4j-all:1.7.1 pom is broken and there is no resilience4j-bom:1.7.1 released either. Does it make sense to stay on a healthy version instead of this partially broken release?

@zieka What do you think? Thanks.

Hi @honnix
Is there some specific issue (in the context of rewrite) that is manifesting due to the bug in rewrite?

@tkvangorder Thanks for looking at this. No there is no issue related to rewrite. It's mostly a problem or just annoying on our side. Since we have been using resilient4j-bom to manage and enforce dependency versions, the absence of the latest version of this bom would require us to manually manage those versions. Hence this PR to see whether rewrite would like to temporarily stay on a slightly old version. If this doesn't make much sense from rewrite's perspective, I can close it.

thanks sam!

Thank you all! Appreciate it.

@honnix We're going to go ahead and do a point release 7.11.1 so that you can depend on a version that has a pinned back resilience4j. As a compromise, we won't plan on doing patch releases of all the downstream rewrite modules unless we hear back that there is some further inconvenience there.

@jkschneider Yeah that sounds very reasonable. Thanks for the help!

@honnix we have released 7.11.1 and it is now out on maven central!
https://github.com/openrewrite/rewrite/releases/tag/v7.11.1


Generated Swagger UI did not display security basic authentication

I am using swashbuckle.core 5.5.3. The swagger generated UI did not display the basic authentication that I specified in app configuration.
Example:
c.BasicAuth("basic").Description("Basic HTTP Authentication over TLS");

And I did not specify any apikey here, but an api_key shows up there.

I had to hide the APIKey and Explore buttons using a custom CSS injection:
form#api_selector input#input_apiKey {
    display: none;
}

form#api_selector A#explore {
    display: none;
}

@coderangerdan  Hide the API key does not make swagger UI show the security for basic authentication.

@leonluocheng
The api_key textbox shows all the time:
https://github.com/domaindrivendev/Swashbuckle/blob/master/Swashbuckle.Core/SwaggerUi/CustomAssets/index.html#L144
Can you give us a link to a project that reproduces your issue?
That can help me troubleshoot your problem

@heldersepu cool, I customized the index page to remove that text box.
I also double checked with swagger UI teams, they told me the newest version of swagger UI does not contain this issue (displaying basic authentication security). but looks like swashbuckle.core use the old version of swagger UI. Please refer to this: https://github.com/swagger-api/swagger-ui/issues/1108#issuecomment-303930907
I am using nuget packge for integrating to my project. is there an way we can update the swagger UI in the swashbuckle.core?

Yes Swashbuckle still using an old version of  Swagger UI, the new one(3.x) still has way to many bug...

See #798.
Upgrading the UI to 3.x is an entirely different topic, already captured as an issue


[Suggestion] Completed Category

I know it's weird, but it'd be nice if we could mark doujins as completed, that way I know what I've read, and I don't have to keep them in my favorites tab.
(Also it'd be nice if we could add filters to "random manga" button)

Also I'm not sure how bookmarks work, I added one, but nothing shows up under "manage bookmarks"
Do I need to login

@jay5656 I liked your idea!
Though its good, its even better if @Dar9586 added an custom category feature.
Like: Completed, Read later, Don't read etc.
In other words its like an playlist feature but instead, there are mangas.

I will try to implement it for the next update (I'll try to add the opportunity to add also custom statuses)

Also I'm not sure how bookmarks work, I added one, but nothing shows up under "manage bookmarks"
Do I need to login

To use the bookmarks there is no need to do the login and it seems to work, could you provide more information about the problem

To use the bookmarks there is no need to do the login and it seems to work, could you provide more information about the problem

Let's see. So if I go to a manga and click a page, then click 3 dots and add bookmark here. And then leave that manga and click "manage bookmarks" nothing but a black screen appears, (if I go back to a manga it'll say "resume to page x" but I should be able to see what I have bookmarked under the "manage bookmarks" tab)

To use the bookmarks there is no need to do the login and it seems to work, could you provide more information about the problem

Let's see. So if I go to a manga and click a page, then click 3 dots and add bookmark here. And then leave that manga and click "manage bookmarks" nothing but a black screen appears, (if I go back to a manga it'll say "resume to page x" but I should be able to see what I have bookmarked under the "manage bookmarks" tab)

Maybe it isn't very clear but they are two different bookmark
This Add bookmark are the one added to the Manage bookmarks

This one create only a notification to resume

@Dar9586 I noticed the pre-release with categories, thank you so much!

@Dar9586 I noticed the pre-release with categories, thank you so much!

Thank you for opening this issue. If you notice some problem or have suggestion please let me know

(Also, an option to change where photos are saved would be nice because they don't appear in my gallery when saved, only the folder location)

I will try to add that in the next update


chore: bdd-nh-1593015813 to 0.0.1

chore: Promote bdd-nh-1593015813 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Cannot add frame, queue is full

Cannot add frame, queue is full
2022-06-28 09:03:39.722 23090-25238/com.alexvas.rtsp.demo W/System.err: java.net.SocketTimeoutException: Read timed out
2022-06-28 09:03:39.722 23090-25238/com.alexvas.rtsp.demo W/System.err:     at java.net.SocketInputStream.socketRead0(Native Method)
2022-06-28 09:03:39.723 23090-25238/com.alexvas.rtsp.demo W/System.err:     at java.net.SocketInputStream.socketRead(SocketInputStream.java:119)
2022-06-28 09:03:39.723 23090-25238/com.alexvas.rtsp.demo W/System.err:     at java.net.SocketInputStream.read(SocketInputStream.java:176)
2022-06-28 09:03:39.723 23090-25238/com.alexvas.rtsp.demo W/System.err:     at java.net.SocketInputStream.read(SocketInputStream.java:144)
2022-06-28 09:03:39.723 23090-25238/com.alexvas.rtsp.demo W/System.err:     at com.alexvas.utils.NetUtils.readData(NetUtils.java:229)
2022-06-28 09:03:39.723 23090-25238/com.alexvas.rtsp.demo W/System.err:     at com.alexvas.rtsp.RtspClient.readRtpData(RtspClient.java:604)
2022-06-28 09:03:39.724 23090-25238/com.alexvas.rtsp.demo W/System.err:     at com.alexvas.rtsp.RtspClient.execute(RtspClient.java:501)
2022-06-28 09:03:39.724 23090-25238/com.alexvas.rtsp.demo W/System.err:     at com.alexvas.rtsp.widget.RtspSurfaceView$RtspThread.run(RtspSurfaceView.kt:228)

Hello,
I can't help you with this info. You need to know that:

I don't know any context about the crash/problem to reproduce or get an idea about the case.
In your error the package is not my package and all crash lines are not in my code. Your code is obviusly modified.
If you have problems with my code modified. I need to tell you that I can't give you full support for it (maintain modifications are you own responsability obviously) but I can try give you hints about the problem if you explain me the objetive and share me code changes if necessary


Wider browser release

This has been outlined originally in the new funding proposal of 2021: %Y2iyBckEhcWvxX6a1+9ELeP6wFYD80QNdhvR50V1C7E=.sha256.

Wider browser release
Patchfox now runs on Firefox, Chromium-based browsers, and Safari. Getting it to run is just half of the game, getting it to ship on these browsers extension store, and working out any browser-specific quirks is much harder.
I’ll work to get Patchfox into the Chrome Web Store and Mac App Store (yes, Mac App Store, that’s where Safari Extensions live)

For this task to be completed, the following issues need to be closed:

[x] #97 - Ship Patchfox for Google Chrome.
[x] #98 - Ship Patchfox for Brave Browser.
[x] #99 - Ship Patchfox for Microsoft Edge.
[x] #100 - Ship Patchfox for Vivaldi.
❌ #101 - Ship Patchfox for Opera.
❌ #102 - Ship Patchfox for Safari.

Some of these got already closed and could be checked, I think.

Just checked them. I don't know why I had the impression that that would happen automagically :D

Be aware that release for Opera and Safari are Tier 3 priorities, and other issues will be worked out before them.

Closing the issues for Safari and Opera as I can't implement them at the moment. Safari requires too many changes and Opera is not answering.


Rule: Added a new flag for max-source-resolution

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
Fixes #7077
Added a new flag for max-source-resolution

Hey @yeya24 I have added the changelog, can you please take a look?

cc @MichaHoffmann @bwplotka @GiedriusS

@yeya24 will this be merged?


BOOMER FONT: Letter F

i want to write the code for font F

Already done under #17

I guess it is the second time this happened to you. Would you like to work on 1 or 7 for boomer?


Add "op timestamp" to "messageClientIdShouldHaveLeft" error thrown in Container

Once we get this error, the container is closed. However, the document is not in an unreliable / corrupted state. The op that causes this can come back and fail at somewhere down the stack.
Adding "op timestamp" will give an indication of when this document was corrupted. Also, investigate and add other fields that can help debugging this issue.

Also related - https://github.com/microsoft/FluidFramework/issues/5095

@ksbrar and I may fix this up with #5095


[crane] crane-transform task does not run in CRC

Following the instructions of the exercise Stateless app mirror I found the following exception on my CRC.
+ /crane version
crane:
	Version: v0.0.3
crane-lib:
	Version: v0.0.5
+ /crane transform --ignored-patches-dir= --flags-file= --export-dir=/var/crane/export --transform-dir=/var/crane/transform
Error: Object 'Kind' is missing in '{"APIResource":{"kind":"Alertmanager","name":"alertmanagers","namespaced":true,"singularName":"alertmanager","verbs":["delete","deletecollection","get","list","patch","create","update","watch"]},"error":{"ErrStatus":{"apiVersion":"v1","code":403,"details":{"group":"monitoring.coreos.com","kind":"alertmanagers"},"kind":"Status","message":"alertmanagers.monitoring.coreos.com is forbidden: User \"rmarting-redhat.com\" cannot list alertmanagers.monitoring.coreos.com in the namespace \"guestbook\": no RBAC policy matched","metadata":{},"reason":"Forbidden","status":"Failure"}}}'
Usage:
  crane transform [flags]
  crane transform [command]

Available Commands:
  list-plugins Return a list of configured plugins
  optionals    Return a list of optional fields accepted by configured plugins

Flags:
  -e, --export-dir string               The path where the kubernetes resources are saved (default "export")
  -h, --help                            help for transform
      --ignored-patches-dir string      The path where files that contain transformations that were discarded due to conflicts are saved. If left blank, these files will not be saved.
      --optional-flags stringToString   A comma-separated list of flag-name=value pairs. These flags with values will be passed into all plugins that are executed in the transform operation. (default [])
  -p, --plugin-dir string               The path where binary plugins are located (default "plugins")
      --plugin-priorities strings       A comma-separated list of plugin names. A plugin listed will take priority in the case of patch conflict over a plugin listed later in the list or over one not listed at all.
  -s, --skip-plugins strings            A comma-separated list of plugins to skip
  -t, --transform-dir string            The path where files that contain the transformations are saved (default "transform")

Global Flags:
      --debug               Debug the command by printing more information
  -f, --flags-file string   Path to input file which contains a yaml representation of cli flags. Explicit flags take precedence over input file values.

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

My migration environment is based on:

src: It is a shared OCP3.11 environment
dest: It is a local CRC environment

❯ crc version
CodeReady Containers version: 1.36.0+c0f4e0d3
OpenShift version: 4.9.8 (embedded in executable)

Same issue in the exercise Stateless app migration with kustomize. It seems that crane cluster tasks are not ready to work in CRC (OpenShift 4.9.8).
This issue blocks my migration scenario from OCP3 to OCP4. :/

Maybe this issue should be created in crane-runner repo. WDYT?


[Internal]: Try out different language switcher

Multiple folks recently got confused by reading a document that's designed for the wrong language, see https://github.com/microsoft/playwright/issues/32861
for an example. I think we can reduce this by making the language switcher more apparent, like this:

Decided against it for now.


Test files with the word "setup" crash on Windows

Test files with the word "setup" somewhere in the filename (e.g. test_setup.c) cause a Windows dialog to pop-up with the standard message "Windows can't open this file...To open this file, Windows needs to know what program you want to use to open it." The test runner then fails with the following output:
Test 'test_setup.c'
Compiling test_setup_runner.c...
Compiling test_setup.c...
Compiling unity.c...
Compiling foo.c...
Compiling cmock.c...
Linking test_setup.out...
Running test_setup.out...
ERROR: Test executable "test_setup.out" failed.

Produced no output to $stdout.
And exited with status: [0] (count of failed tests).
This is often a symptom of a bad memory access in source or test code.

rake aborted!
C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/generator_helper.rb:36:in test_results_error_handler' C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/generator.rb:153:in generate_test_results'
C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/rules_tests.rake:42:in block in <top (required)>' C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/task_invoker.rb:74:in invoke_test_results'
C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/test_invoker.rb:68:in block in setup_and_invoke' C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/test_invoker.rb:32:in each'
C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/test_invoker.rb:32:in setup_and_invoke' C:/sandbox/191-008/ceedling_validation/test_ceedling/vendor/ceedling/lib/ceedling/rules_tests.rake:57:in block (2 levels) in <top (required)>'
Tasks: TOP => build/test/results/test_setup.pass
(See full trace by running task with --trace)

OVERALL TEST SUMMARY
No tests executed.

Changing the filename causes the test to run with no issues.

It sounds like a similar issue to #116 . I'm not sure if there is a simple fix for this the only thing I can think of is prevent Ceedling from creating an executable that contains setup (or patch for the other case).

Thanks for pointing out that link. It's useful to know that there are multiple keywords that need to be avoided. Seems like there isn't necessarily a simple solution, but it would be useful to have this documented in the manual (couldn't find it if it's already there).

I had the same problem, but solved it by getting this Group Policy setting disabled: "User Account Control: Detect application installations and prompt for elevation".

Hi guys. I seem to have a similar issue with the word "update" somewhere in the test file name.  Can you confirm that it is in fact the same issue?


Implement Syncer.Synced()

I need this method, otherwise I have to implement my own Syncer. Later on, it might prove helpful when porting hostd and renterd, too.
It has been working fine in my tests so far. If needed, minSyncedPeers and minTimeUntilSynceed can be added to the config options.

I confess that I have always found Synced() to be kind of a gross hack. It conflates multiple questions:

"Have I performed IBD with a reasonable number of peers?"
"Does my blockchain tip match the 'real' tip, i.e. the tip I would see on a public explorer?"
"Is my wallet balance and transaction history up-to-date?"
"If I broadcast a transaction, will my peers accept it?"

Now, it is usually the case that the answer to all of these questions is the same (whether that answer is yes or no). But it is not guaranteed. Maybe you are getting eclipse-attacked. Maybe the public explorer got hacked. Maybe your wallet hasn't had any activity for hundreds of thousands of blocks.
My understanding is that generally, apps want a Synced bool so that they can a) inform the user that their wallet balance is not final, and b) prevent the user from trying sending to send transactions too soon. I suggest handling these cases separately. Instead of "synced/not synced," tell the user that their balance is up-to-date as of block X at timestamp T. And instead of waiting until "synced" to allow transactions, allow them as soon as the last known block is within 1 day. Separately, you can add an (optional) setting to compare the local tip against a public explorer, and display a checkmark or something when it matches.
I realize I'm probably in the minority here, so perhaps @n8maninger or @ChrisSchinnerl could weigh in with their thoughts. Anyway, I do appreciate you taking the time to understand and modify the Syncer code. The implementation itself looks fine to me.

I think having a Synced method is very useful and considering that coreutils is implementing the Syncer which has the most information on what other peers currently consider synced it is probably also the place to put it.
That said I think waiting for at least 10 minutes before considering us synced breaks many use-cases. e.g. the Autopilot in renterd relies on Synced and having to wait for 10 minutes every time you start the autopilot ruins UX.
I think a reasonable assumption would be to check 2 things.

do we have a minimum of n peers. e.g. 6
have all of those peers reported that they don't have anymore blocks for us
has the latest block arrived within the last hour

That's probably the best any node in a trustless, distributed environment can do anyway without a trusted entity which we don't want to rely on for the security of our daemons.
We can only hope to make the Syncer as resilient to various attacks as possible via our implementation.

The method returns true in two cases:

if minimum 5 peers say that we are synced
OR
if 10 minutes have passed since we have started syncing.

In my tests on Zen, I usually gain the minimum peer count within less than a minute. On Anagami, though, I have to wait 10 minutes, because I usually don't get to connect to 5 peers there.

I don't see a reason not to add it. I would suggest a few changes, though:

Make minSyncedPeers configurable as WithMinPeers
Remove minTimeUntilSynced. Not enough peers is a valid reason not to consider a node synced.
Check if the last block timestamp is less than 24 hours ago. If the node hasn't received a recent block from a peer, we're not synced, or the whole network is experiencing issues.

Anagami is a special (temporary) case; nothing should be built with Anagami in mind.

the Autopilot in renterd relies on Synced

@ChrisSchinnerl If your Synced heuristic was "the last known block is <24 hrs old," would that break anything? I can see it causing mild issues, like transactions failing.  Anything else?
Separately: what if instead of adding Synced method to Syncer, we added it to gateway.Peer? Then clients can implement whatever heuristic they want.

renterd currently operates under the same heuristics that siad provides. Which I think is that peers don't have any blocks for us? We want it to be as accurate as possible when interacting with hosts because once we consider ourselves synced, the renter will only grant +-12 blocks or so as wiggle room to hosts when trying to agree on a block height.
If we considered ourselves synced with the last block being 24 hours old we'd have to increase that threshold with hosts as well since they might be 144 blocks ahead of us when we consider ourselves synced. So I'd rather have it be smaller than that.
Exposing all that info in a different way would be fine as well imo. Maybe even better since we can tweak it ourselves and even have users make their own choices.

For the record: this is the logic that siad uses:
// peers. After the deadline though, it will recognize the blockchain
// download as complete even with only one peer. This deadline is helpful
// to local-net setups, where a machine will frequently only have one peer
// (and that peer will be another machine on the same local network, but
// within the local network at least one peer is connected to the braod
// network).```

renterd currently operates under the same heuristics that siad provides.

IIRC, renterd switched over to the same heuristic hostd uses: last block timestamp < 1 hour

the renter will only grant +-12 blocks or so as wiggle room to hosts when trying to agree on a block height

I wonder if this is something we could address in RHPv4. Like, if the host thinks the renter is behind, it could send a header chain proving it.
Anyway, I think some combination of:

Checking last block timestamp
Checking the Synced flag on individual peers
Comparing tip against public explorer

should be sufficient for anyone's needs. Unless there are further objections, I suggest we add the Synced flag to gateway.Peer, like so:
type Peer struct {
	UniqueID UniqueID
	Version  string
	Addr     string
	ConnAddr string
	Inbound  bool
	smux     *smux.Session // for v1
	mux      *mux.Mux      // for v2
	mu       sync.Mutex
	synced   bool
	err      error
}

// Synced returns the peer's sync status.
func (p *Peer) Synced() bool {
	p.mu.Lock()
	defer p.mu.Unlock()
	return p.synced
}

// SetSynced sets the peer's sync status.
func (p *Peer) SetSynced(synced bool) {
	p.mu.Lock()
	defer p.mu.Unlock()
	p.synced = synced
}

and call SetSynced in the Syncer code where appropriate. (This would also let us remove the synced field from Syncer.) @mike76-dev, does that sound ok to you?

True, but gateway.Peer is not in the syncer package 😅

@mike76-dev, does that sound ok to you?

Yeah, that should be fine. I can take over the PRs, if nobody minds.

@mike76-dev, does that sound ok to you?

Yeah, that should be fine. I can take over the PRs, if nobody minds.

We will be moving Peer and the RPc implementations out of core and into coreutils. Hold off on any changes until then

@mike76-dev now that #10 is merged, feel free to proceed

Can you rebase and squash this so we get a clean history?

Thanks!


Issue abandoning claim

It's a rare event that happens. Not all the time.
When a user tries to abandon a claim it notifies that the claim has been abandon but does not.
video: https://gyazo.com/681aa611df6ec37dd97259540d086a54
GP: 644 SF: 3323

What is luckperms version? This sounds a lot like sync issues in the past...

4.2.41 I am using a build from July 1st. I should update and test it
latest is 4.2.51.
Luckperms on Ore probably needs a update unless those are RBs only it's at 4.2.17.

Create a new ticket if this occurs with latest GP.

Yeah, will do. Thanks again blood.


[question] nextgen_crypto::ed25519::Ed25519PrivateKey: std::clone::Clone is not satisfied

when I  building vm_genesis of branch [testnet] there is a error:
error[E0277]:
the trait bound nextgen_crypto::ed25519::Ed25519PrivateKey: std::clone::Clone is not satisfied
----- /libra/language/vm/vm_genesis/src/lib.rs:61:5

in "language/vm/vm_genesis/src/lib.rs"
_#[derive(Debug, Clone)]
pub struct Account {
    pub addr: AccountAddress,
    pub privkey: Ed25519PrivateKey,
    pub pubkey: Ed25519PublicKey,
}_

See "/crypto/nextgen_crypto/src/ed25519.rs"
/// An Ed25519 public key
#[derive(Clone, Debug)]
pub struct Ed25519PublicKey(ed25519_dalek::PublicKey);

but Ed25519PrivateKey is not derived clone, however, Ed25519PublicKey is derived clone.

I can't reproduce this on the latest testnet at 171a766095954ff6eecf7147a4847b3c3590cdae or
master at afbfd77bf380175ef6739e166b7e70608fc56a19, what's the commit you are working on?

Closed for lack of activity, feel free to reopen with more data @dofork


Ensure that DaemonSet Pods are ready

This simplifies the check if the DaemonSet Pods are running (and ready).

Will provide further unit tests/refactoring in another PR.


Inconsistent naming

Many thanks for a great package.
I've noticed a small inconsistency concerning random forests: the key in foo.best_config() is max_leaves, which differs from sklearn's max_leaf_nodes.

I have created an PR #1310 to fix the issue mentioned...

I have created an PR #1310 to fix the issue mentioned...

Hi @Programmer-RD-AI , #1310 won't fix the issue, I've raised #1320 to address it.

https://github.com/microsoft/FLAML/pull/1320#issuecomment-2244505018


Feature/test docker unittest

This is a Travis test to ensure a failed unit test in docker fails the build.

Coverage remained the same at 53.925% when pulling b968b490a7c4d820b66cef235b6cdafd90078a12 on TomHAnderson:feature/test-docker-unittest into 6d45064514260162e382a56555873a5a748d1611 on zfcampus:master.


agent: Add EnableRouteMTUForCNIChaining to propagate MTU to pods when CNI chaning is used

/ci-awscni

/ci-awscni

/ci-eks

/ci-awscni

/ci-eks

/ci-awscni

/test

/ci-awscni

/ci-awscni

/ci-awscni

/ci-awscni

/ci-awscni

/ci-awscni

/ci-awscni

/ci-awscni

/test

Why is this different from EnableRouteMTU?


Replace maven by gradle

Is your feature request related to a problem? Please describe.
When working with multiple plugins, such as when making a patch release, security plugin is a 1-off and creates unnecessary friction.
See https://github.com/opensearch-project/opensearch-plugins/pull/119 and https://github.com/opensearch-project/opensearch-build/blob/main/scripts/components/security/build.sh#L70 as examples.
Describe the solution you'd like
Replace maven with standardized gradle implementation just like all the other plugins in OpenSearch.

#1121 was a first attempt at this.
This PR is outdated and it does too many things: move CI to gradle, upgrade gradle version, update tests (apparently this last one was more involved as it introduced a new runner)...
We are prioritizing work on our test suite, to start using the OpenSearch Test Framework, and moving to gradle is part of that initiative. That said, @cliu123, do you think there is a subset of that PR that we could merge, moving to gradle while leaving the tests mostly unchanged until we tackle that larger body of work?

PR: https://github.com/opensearch-project/security/pull/1592


Milestone 1

Fix run issues with PS script
Fix run issue with Python script
Fix issue with creating teams in Phoenix

API needs to be changed back


Best approach to hide some parameters in logs

What is the best approach to hide some data in logs?
For example, I have request, where user entered his or her password, and response where new password arrives back.
I'm using Log middleware and MessageFormatter::DEBUG format to log request data.
But I would prefer to replace data in request and response.
By default it logs password=123456 for request and new_password=654321 from response.
Currently I've extended MessageFormatter::format method and replaced such entrances with a regular expressions.
Anyway I wonder if there is other approach for this issue?

I would say MessageFormatter is the best approach that you can currently do.


fix, refactor, chore(egen): Fix model deployment to endpoint using Deployment Resource Pool, Replaces K80 with T4 GPUs, Documentation link update, corrections from template.

This PR consists of the following updates:

Fix to deploy the model to endpoint using Deployment Resource Pool.
K80 replaced with T4 GPU.
Documentation link for Deployment Resource Pool.
Change model display name to "use" while uploading model_use to Vertex AI Model resource.
Refactors the notebook according to the notebook template (removes boilerplate elements, renames REGION with LOCATION and re-structures the sections).
Adds link for colab enterprise.
Removes the usage of future tense(will) according to the guidelines.
Update notebook to use TensorFlow 2.15.1 and TensorFlow Hub 0.16.1 due to specific model dependencies.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun

/gcbrun


Overflow Problem (Design Issue)

I have been using AdminLTE for my small rest based java project. I don't know what went wrong even i don't change anything to AdminLTE.min.css but my dashboard page looks like in this  picture . any suggestion will highly appreciated.

Yeah, I noticed the same issue when using it. One little hack that seem to fix it is to resize the window programmatically on load.
For me, this solved it:
$(document).ready(function(){
    $(window).resize();
});

This is happen if the app.js/app.min.js, bootstrap.min.js or jquery.js is not loaded in right order.

Thanks ezra-obiwale and REJack for important feedback. I have loaded js files like this order , first jquery , then bootstrap , after that angularjs and so on and finally app.min. I think this order is correct as per REJack comments. But i have seen , if my contents height is small like lower than 200-250px then this problems is still consists and more interestingly "content-wrapper" class "min-height" property is auto adjusted like 178px something like that. but when contents height is much above that then this problem disappears. also when debugging with chrome or firebug then this problem is gone. but without these it happens.

If this is still an issue, you may want to upgrade to v2.4 and test again. I am not sure if it'll solve the problem, but it is definitly worth upgrading if you are using AngularJS.
If you are interested, upgrade guide can be found here https://adminlte.io/docs/2.4/upgrade-guide
Thanks!


安装后运行npm遇到这个报错:Cannot find module

If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
My Environment

[ ] Windows 7 or below (not truly supported due to EOL - see wiki for details)

[ ] Windows 8

[ ] Windows 8.1

[X] Windows 10

[ ] Windows 10 IoT Core

[ ] Windows Server 2012

[ ] Windows Server 2012 R2

[ ] Windows Server 2016

[ ] My Windows installation is non-English.

I'm using NVM4W version:

[X] 1.1.7
[ ] 1.1.6
[ ] 1.1.5
[ ] 1.1.4
[ ] 1.1.3
[ ] 1.1.2
[ ] 1.1.1
[ ] Older
[ ] OTHER (Please Specify)

I have already...

[ ] read the README to be aware of npm gotchas & antivirus issues.
[ ] reviewed the wiki to make sure my issue hasn't already been resolved.
[X] verified I'm using an account with administrative privileges.
[ ] searched the issues (open and closed) to make sure this isn't a duplicate.
[ ] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

[ ] settings.txt
[ ] proxy support (Have you tried version 1.1.0+?)
[ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
[ ] Character escaping (Have you tried version 1.1.6+?)
[ ] A standard shell environment (terminal/powershell)
[X] A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior
1.原来nvm版本1.1.6将node版本10.x.x安装完成后发现npm模块不见了，无法运行
2.这个nvm软件更新1.1.7来进行安装node版本10.15.3 LTS，发现里面有存在npm模块的，打算运行npm模块报错：Cannot find module ，求解！！！
Actual Behavior

还有nvm文件夹里面setting.txt和在C盘目录setting.txt都一样配置的如下：
root: D:\NodeFiles\nvm
path: D:\NodeFiles\nodejs
arch: 64
proxy: none
node_mirror: https://npm.taobao.org/mirrors/node/
npm_mirror: https://npm.taobao.org/mirrors/npm/
Steps to reproduce the problem:
nvm install 10.15.3
nvm use 10.15.3
node -v //10.15.3出来了
npm -v //报错了，是上面截图提示的

将Git Bash输入10.15.3安装后，然后use 10.15.3运行出来发现有node，npm版本显示的，已经自行解决了的

将Git Bash输入10.15.3安装后，然后use 10.15.3运行出来发现有node，npm版本显示的，已经自行解决
你好，请问你是怎么解决的？


#933 added unit tests for ItineraryVolunteerListUpdatedHandler

Hello, Adam here.
I heard of you guys on the dotnetrocks podcast and that you are accepting contributions.
I wrote the unit tests requested in #933. Let me know if you expect further changes to this.
thanks

Thanks @adam-gligor for contributing.  pinging @mgmccarthy and @MisterJames to give it a quick review and offer any guidance or feedback before we merge.
Thanks again

@tonysurma, I'll take a look sometime today or later tonight

@adam-gligor nice work!
Can you make ShouldDispatchVolunteerAssignedNotification and ShouldDispatchVolunteerUnAssignedNotification test the explicit messages being generated by the handler? Right now, looks like you're making sure the items that change (assigned/unassigned) are being assigned correctly.
Also, things like values for {volunteerDashboardLink}, {itineraryDate} and {toFrom} should be tested as well as they relate to the different type of message strings being built.
You might also want to add a test for NotifyVolunteersCommand NOT being sent, which should happen in this conditional was met:
if (string.IsNullOrWhiteSpace(emailAddress) && string.IsNullOrWhiteSpace(phoneNumber))
    return;

Thanks!

Thanks for the quick feedback.
I made the following changes as you suggested:

Changed the class and method names
Updated the DispatchVolunteerAssignedNotification and DispatchVolunteerUnAssignedNotification to test the full content of the message
Added a new test NotDispatchNotificationWhenNoContactInformation

@adam-gligor , I'll try to get to this review by the end of the weekend, no guarantees though :wink:  Most likely, I'll be taking a look Monday. Thanks for the quick turnaround.

Looks good @adam-gligor! Thanks for the original review @mgmccarthy. Looks like everything is in place. :shipit:


Format method changes in the last 2.21 version

Description of the Issue and Steps to Reproduce:
In your webpack configuration:
new webpack.ContextReplacementPlugin(/moment[\/\\]locale$/, /fr/), // Only french

Then in your javascript code
var d = moment();
moment.format('dddd') // returns 'Saturday' in v2.21.0
moment.format('dddd') // return 'Samedi' in v2.20.1

The previous behavior was great, it returned the day in the good language but not now

I don't know what's changed to cause this issue. Would love more information, or other eyes here.

@FloV22 I was unable to re-create your issue using a simple webpack demo app. Is there any more information you can provide regarding this issue?
You can see my attempt by looking at https://github.com/knittingdev/moment-issue-4503
You'll notice two branches moment-2.21.0-test and moment-2.20.1-test which are attempting to recreate your issue given your recreation steps.
Please let me know if you have any questions. 😄


Implemented Threadpool to boost Data ingestion

Can you report what is the performance difference between before and after using the threadpool? Also add a benchmarking unit test for this.


Suggestion to place the price chart to the right of market data instead of below

A la

Instead of vertical (could be vertical on mobile though)

That's not a bad idea.  And maybe below instead we could have a "passive updates" window -- instead of the modal progress window, you could have a minimizable terminal-like window that just shows you updates as they arrive.

I would put the chart on a separate Stats & Charts tab.


Guessed wrong for http://depsy.org/package/python/catsim

It's a Python package that allow users to run simulations of computerized adaptive tests. I built it as part of my master's program.

Depsy is no longer being updated. See https://twitter.com/depsy_org/status/970376969782149120

OK, I'll close it then.


Add ProbeControlRoom

Only thing holding it back now appears to be the dependency on RasterPropMonitor, which is not yet available for KSP 1.2.x

#rebuild

Removing the BlockedOnDependency since RPM is available and it passed the checks

Cool!


Resin-supervisor.service missing dependency

Resin-supervisor.service should depend on the mount point created by etc-supervisor.conf.mount, so it can have access to the new data created by the update-supervisor.service.

@telphan please close the linked issue when the addressing PR is merged. (or use fixes)


Show in city ld14

Fails

:no_entry_sign:

Missing Test Files:

src/lib/Components/Buttons/__tests__/index-tests.tsx
src/lib/Scenes/Show/Components/Shows/__tests__/nearbyShows-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

:no_entry_sign:

[danger-plugin-jest] Could not read test results. Danger cannot pass or fail the build.

Warnings

:warning:

This PR comes from a fork, and won't get JS generated for QA testing this PR inside the Emission Example app.

  Generated by :no_entry_sign: dangerJS

👏Congrats on getting this in


Fix critical CWE-079,CWE-116

Signed-off-by: Taras Drozdovskyi<EMAIL_ADDRESS>Description
Fix critical alerts (CWE-079, CWE-116).
This fix should be a separate commit as we will need to reference it from another resource
Fixes #171
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
The result can be seen after merge code to the master branch and update LGTM.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@tdrozdovsky Thank you for the PR.
Could you show us what will be printed as a result?

@tdrozdovsky Thank you for the PR.
Could you show us what will be printed as a result?

A very good request! I have problems with my computer now, I think I'll prepare an answer within 2 hours. Thank you!

The result depends on the input parameters. EscapeString escapes special characters like: <, >, &, ' and ".
String processing example:
package main

import (
	"fmt"
	"html"
)

func main() {
	const s = "<script>alert('foo');</script>"
	const s1 = `"Fran & Freddie's Diner"<EMAIL_ADDRESS>
	fmt.Println(s)
	fmt.Println(html.EscapeString(s))
	fmt.Println(html.UnescapeString(html.EscapeString(s)))

	fmt.Println("")

	fmt.Println(s1)
	fmt.Println(html.EscapeString(s1))
	fmt.Println(html.UnescapeString(html.EscapeString(s1)))}

Rusult:
<script>alert('foo');</script>
<script>alert('foo');</script>
<script>alert('foo');</script>

"Fran & Freddie's Diner"<EMAIL_ADDRESS>"Fran & Freddie's Diner&#34<EMAIL_ADDRESS>"Fran & Freddie's Diner"<EMAIL_ADDRESS>
Cross Site Scripting Prevention: Output Encoding Rules Summary

I think we don't need to send

@t25kim @MoonkiHong The result depends on the input parameters. EscapeString escapes special characters like: <, >, &, ' and ".
String processing example:
package main

import (
	"fmt"
	"html"
)

func main() {
	const s = "<script>alert('foo');</script>"
	const s1 = `"Fran & Freddie's Diner"<EMAIL_ADDRESS>
	fmt.Println(s)
	fmt.Println(html.EscapeString(s))
	fmt.Println(html.UnescapeString(html.EscapeString(s)))

	fmt.Println("")

	fmt.Println(s1)
	fmt.Println(html.EscapeString(s1))
	fmt.Println(html.UnescapeString(html.EscapeString(s1)))}

Result:
<script>alert('foo');</script>
<script>alert('foo');</script>
<script>alert('foo');</script>

"Fran & Freddie's Diner"<EMAIL_ADDRESS>"Fran & Freddie's Diner&#34<EMAIL_ADDRESS>"Fran & Freddie's Diner"<EMAIL_ADDRESS>
Cross Site Scripting Prevention: Output Encoding Rules Summary

Thank you for the details!
I am not sure that we have to send deviceName and resourceName in this way since the receiver has to call UnescapeString function to read these messages correctly.
If the receiver doesn't need detail information, it might be better to send a simple message like "DeviceName not found".

I think we don't need to send

@t25kim @MoonkiHong The result depends on the input parameters. EscapeString escapes special characters like: <, >, &, ' and ".
String processing example:
package main

import (
	"fmt"
	"html"
)

func main() {
	const s = "<script>alert('foo');</script>"
	const s1 = `"Fran & Freddie's Diner"<EMAIL_ADDRESS>
	fmt.Println(s)
	fmt.Println(html.EscapeString(s))
	fmt.Println(html.UnescapeString(html.EscapeString(s)))

	fmt.Println("")

	fmt.Println(s1)
	fmt.Println(html.EscapeString(s1))
	fmt.Println(html.UnescapeString(html.EscapeString(s1)))}

Result:
<script>alert('foo');</script>
<script>alert('foo');</script>
<script>alert('foo');</script>

"Fran & Freddie's Diner"<EMAIL_ADDRESS>"Fran & Freddie's Diner&#34<EMAIL_ADDRESS>"Fran & Freddie's Diner"<EMAIL_ADDRESS>
Cross Site Scripting Prevention: Output Encoding Rules Summary

Thank you for the details!
I am not sure that we have to send deviceName and resourceName in this way since the receiver has to call UnescapeString function to read these messages correctly.
If the receiver doesn't need detail information, it might be better to send a simple message like "DeviceName not found".

@suresh-lc @sun-sharma Please check out if we have to send deviceName and resourceName in this way as pointed out by @t25kim. Thank you in advance.

@MoonkiHong @t25kim

If we can replace with a simple phrase like DeviceName not found, then I think this is the best way!
If we still need to display the deviceName, then if it does not contain special characters (<, >, &, ' and "), then everything is ok, , there is no need to UnescapeString

P.S. It is necessary to fix it in any case, since this is a critical error that can lead to the exploitation of our program!

@MoonkiHong @t25kim

If we can replace with a simple phrase like DeviceName not found, then I think this is the best way!
If we still need to display the deviceName, then if it does not contain special characters (<, >, &, ' and "), then everything is ok, , there is no need to UnescapeString

P.S. It is necessary to fix it in any case, since this is a critical error that can lead to the exploitation of our program!

As I know, deviceName can contain special characters like below. (refer to the API doc)

Let's find out a good solution after checking if deviceName and resourceName are required during response! 😁

@t25kim I looked at your comment above. I still think that the best way for us is not to display the deviceName. When a 404 error occurs, their API provides information, see below.

The request contains the device name and there is no need to confirm this name in the response.
I am very surprised that the name may contain special characters, as this is a critical security vulnerability.
@t25kim Thank you for considering this issue in detail. I think we can make the right decision.
Looking forward to your opinion!

@t25kim I looked at your comment above. I still think that the best way for us is not to display the deviceName. When a 404 error occurs, their API provides information, see below.

The request contains the device name and there is no need to confirm this name in the response.
I am very surprised that the name may contain special characters, as this is a critical security vulnerability.
@t25kim Thank you for considering this issue in detail. I think we can make the right decision.
Looking forward to your opinion!

@suresh-lc @sun-sharma This should be decided from you, since you are the original proposers for MNEDC.

I'd just like to give my opinion to Home Edge folks.  The security problem should be considered as the top priority rather than other problems. I agree that the best way is hiding hide the critical information such as deviceName and resourceName .  In case of multiple requests from the same client to the Edge device, we need to give the way to separate appropriate responses for each. So I think the piggyback style response might be considered. In this case, response can include deviceName or other information. If I misunderstood this context, please ignore it.^^

In short, the problem is not that deviceName and resourceName are sensitive information, but that they use special characters that can be used to inject malicious code and are then automatically launched using the html parser. Therefore, we have two options:

Remove deviceName and resourceName from the responce
Encode special symbols

@mgjeong @t25kim @MoonkiHong @suresh-lc @sun-sharma Please share your opinion.

The security problem should be considered as the top priority rather than other problems.

@mgjeong Thanks for your support and understanding

In short, the problem is not that deviceName and resourceName are sensitive information, but that they use special characters that can be used to inject malicious code and are then automatically launched using the html parser. Therefore, we have two options:

Remove deviceName and resourceName from the responce
Encode special symbols

@mgjeong @t25kim @MoonkiHong @suresh-lc @sun-sharma Please share your opinion.

@suresh-lc We need your opinion to treat this! PTAL..

I think the encoding the special symbols is required regardless the information type.^^.

In short, the problem is not that deviceName and resourceName are sensitive information, but that they use special characters that can be used to inject malicious code and are then automatically launched using the html parser. Therefore, we have two options:

Remove deviceName and resourceName from the response
Encode special symbols

@mgjeong @t25kim @MoonkiHong @suresh-lc @sun-sharma Please share your opinion.

@suresh-lc We need your opinion to treat this! PTAL..

@tdrozdovsky Let us go forward with option 1, since anyway the response (thru REST APIs) describes the context (based on the uri), so the response msg itself does not need to show up the deviceName and resourceName.

In short, the problem is not that deviceName and resourceName are sensitive information, but that they use special characters that can be used to inject malicious code and are then automatically launched using the html parser. Therefore, we have two options:

Remove deviceName and resourceName from the response
Encode special symbols

@mgjeong @t25kim @MoonkiHong @suresh-lc @sun-sharma Please share your opinion.

@suresh-lc We need your opinion to treat this! PTAL..

@tdrozdovsky Let us go forward with option 1, since anyway the response (thru REST APIs) describes the context (based on the uri), so the response msg itself does not need to show up the deviceName and resourceName.

@suresh-lc PTAL.

Dear Colleagues, please write each option which is preferable for you and I will fix it. It remains for us to fix these two errors and we will have no alerts from the LGTM.
Let's speed up this process!

Dear Colleagues, please write each option which is preferable for you and I will fix it. It remains for us to fix these two errors and we will have no alerts from the LGTM.
Let's speed up this process!

@tdrozdovsky Majority preference at this moment: Option 1 "Remove deviceName and resourceName from the response". Thank you.

Dear Colleagues, please write each option which is preferable for you and I will fix it. It remains for us to fix these two errors and we will have no alerts from the LGTM.
Let's speed up this process!

@tdrozdovsky Majority preference at this moment: Option 1 "Remove deviceName and resourceName from the response". Thank you.

Removing the critical information of device and resource is good and can be done immediately. We can also see how to  manage multiple requests from same client as @mgjeong had mentioned.

Dear Colleagues, please write each option which is preferable for you and I will fix it. It remains for us to fix these two errors and we will have no alerts from the LGTM.
Let's speed up this process!

@tdrozdovsky Majority preference at this moment: Option 1 "Remove deviceName and resourceName from the response". Thank you.

Removing the critical information of device and resource is good and can be done immediately. We can also see how to manage multiple requests from same client as @mgjeong had mentioned.

@suresh-lc @tdrozdovsky Let us focus on the option 1 first in this PR. The point suggested from @mgjeong can be treated in a separate issue/upcoming PR. What do you think?

Dear Colleagues, please write each option which is preferable for you and I will fix it. It remains for us to fix these two errors and we will have no alerts from the LGTM.
Let's speed up this process!

@tdrozdovsky Majority preference at this moment: Option 1 "Remove deviceName and resourceName from the response". Thank you.

Removing the critical information of device and resource is good and can be done immediately. We can also see how to manage multiple requests from same client as @mgjeong had mentioned.

@suresh-lc @tdrozdovsky Let us focus on the option 1 first in this PR. The point suggested from @mgjeong can be treated in a separate issue/upcoming PR. What do you think?

@MoonkiHong The current version of the PR implements the point suggested frim @mgjeong. But I think we can return to it when necessary.

Found this PR fixes security alerts.
https://github.com/lf-edge/edge-home-orchestration-go/pull/203/checks?check_run_id=1594072383

@t25kim This is great!!! Thank you for your passionate evaluation!


Hot reload is not working (OSX)

Environment

Operating System: Darwin
Node Version:     v18.14.0
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
Hey Team - I'm following along with the Mastering NUXT 3 class using - https://github.com/MasteringNuxt/mastering-nuxt-3
Describe the bug
I'm on OSX attempting to get things working for the very first lesson and when running pnpm dev, localhost does start but the arrows spin for a long time and hot reload doesn't work. I can manually refresh the page to see changes made to index.vue however.
I've tried the latest edge version of NUXT and no dice. I've also tried several recommendations in the Windows version of this issue: https://github.com/nuxt/nuxt/issues/18964#issuecomment-1459549393
Any assistance would be greatly appreciated.
Additional context
No response
Logs
No response

Yeah, latest edge should work but also latest "normal" (3.2.2)
Errors in the console? Worst case, feel free to create a tiny video with a fresh installation (via nuxt.new)

Thanks for the input - I installed 3.2.2 and got the following warnings, not really sure how to go about solving these:
`devDependencies:

nuxt 3.0.0

nuxt 3.2.2 (3.2.3 is available)

WARN  Issues with peer dependencies found
.
├─┬ @nuxtjs/tailwindcss 6.1.3
│ └─┬ @nuxt/postcss8 1.1.3
│   ├─┬ css-loader 5.2.7
│   │ └── ✕ missing peer<EMAIL_ADDRESS>|| ^5.0.0"
│   └─┬ postcss-loader 4.3.0
│     └── ✕ missing peer<EMAIL_ADDRESS>|| ^5.0.0"
└─┬ @tailwindcss/typography 0.5.8
└── ✕ missing peer<EMAIL_ADDRESS>|| insiders"
Peer dependencies that should be installed:
<EMAIL_ADDRESS>|| insiders"<EMAIL_ADDRESS><5.0.0 || >=5.0.0 <6.0.0"`
I went ahead and ran pnpm dev anyway, and the same issue persists. I'm not getting any console errors.

Would you provide a reproduction? 🙏

Hey Daniel - does this link work?: https://stackblitz.com/edit/github-vhctgb
I've not tried to provide a repo before.

Does it not work for you in the sandbox? (It does for me.)
I think it might be an issue with your setup. Can you try in an incognito window, or in a fresh browser profile? Maybe try clearing your service workers.
What is your full directory path? Sometimes libraries like vite or rollup have issues with paths with spaces or quotation marks in them.
Finally, do you see any errors in your network tab (ie. files that couldn't be downloaded)?

Thanks for the input. I just now tried the sandbox and it did work. I'll give those suggestions a try asap.

Hey Daniel - I can confirm that attempting to run dev in an incognito window unfortunately did not fix the issue. If full directory path is the same as RootDir as supplied by npx nuxi info, then that is:
/Applications/MAMP/htdocs/nuxt/nuxt-3/mastering-nuxt-3-main/mastering-nuxt-3
If I'm incorrect, please let me know how I can find the full directory path. In my Google searches on this I've also come across NUXT_APP_BASE_URL but I haven't discovered how to retrieve it. As an aside, I wouldn't think storing the NUXT files within MAMP would be an issue. I'm also not actively running a local Mamp server instance (which I also wouldn't think would be an issue either way). I can relocate the NUXT files if that might be useful.
I'm not seeing any Console errors currently. However another data point is the tailwind viewer never loads. I try to launch it and I just get a spinning empty browser tab. Eventually, the following error appears within the Visual Studio Code terminal:
[nuxt] [request error] [unhandled] [500] Body is unusable                                                                 13:53:13   at specConsumeBody (node:internal/deps/undici/undici:6372:15)     at Response.text (node:internal/deps/undici/undici:6272:18)     at $fetchRaw2 (./node_modules/.pnpm/ofetch@1.0.1/node_modules/ofetch/dist/shared/ofetch.502a4799.mjs:192:43)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)     at async default (./node_modules/.pnpm/@nuxt+vite-builder@3.2.2_vue@3.2.47/node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:16:23)     at async Object.renderToString (./node_modules/.pnpm/vue-bundle-renderer@1.0.2/node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19)                                                                                13:46:42   at async ./.nuxt/dev/index.mjs:717:21     at async ./.nuxt/dev/index.mjs:378:22     at async Object.handler (./node_modules/.pnpm/h3@1.5.0/node_modules/h3/dist/index.mjs:1196:19)     at async Server.toNodeHandle (./node_modules/.pnpm/h3@1.5.0/node_modules/h3/dist/index.mjs:1271:7) [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/__nuxt_vite_node__/invalidates)              13:54:43   at async $fetchRaw2 (./node_modules/.pnpm/ofetch@1.0.1/node_modules/ofetch/dist/shared/ofetch.502a4799.mjs:180:24)     at async default (./node_modules/.pnpm/@nuxt+vite-builder@3.2.2_vue@3.2.47/node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:16:23)     at async Object.renderToString (./node_modules/.pnpm/vue-bundle-renderer@1.0.2/node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19)     at async ./.nuxt/dev/index.mjs:717:21     at async ./.nuxt/dev/index.mjs:378:22     at async Object.handler (./node_modules/.pnpm/h3@1.5.0/node_modules/h3/dist/index.mjs:1196:19)     at async Server.toNodeHandle (./node_modules/.pnpm/h3@1.5.0/node_modules/h3/dist/index.mjs:1271:7)

I have the same issue, MacOS Big Sur, node v16.17.1, Nuxt 3.3.1, pnpm 7.14.0. Just boilerplate nuxt with pnpm dlx nuxi init

I'll try nuxt v 3.1.1 and report back. Thanks!

[nuxt] [request error] [unhandled] [500] Body is unusable

Nuxt3.3.1 + Node v18.13.0 gives the same error.
However, this does not occur with Node v18.15.0.

Hey Team - combined with Node v18.15.0, neither Nuxt 3.1.1, 3.3.1, nor 3.3.3 worked for me. When attempting 3.4.0 I get a new error: Named export 'consola' not found. Various attempts to fix that have also failed.

I was able to fix the 3.4.0 error using:
"pnpm": {     "overrides": {       "consola": "3.0.1"     }   }
in package.json then reinstalling using: pnpm install --shamefully-hoist
hot reload still not working. It's a very hard reset in the browser situation at this point.

Perhaps you were using firefox? I switched to chrome, and it now works fine.

Here are the latest issues I've found in  v3.5 & v3.6 versions:
1- The warnings about peer dependencies:
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ @nuxt/devtools
  ├── ✕ missing peer vite@"*"
  ├─┬ vite-plugin-inspect
  │ └── ✕ missing peer<EMAIL_ADDRESS>|| ^4.0.0"
  ├─┬ vite-plugin-vue-inspector
  │ └── ✕ missing peer<EMAIL_ADDRESS>|| ^4.0.0-0"
  └─┬ @nuxt/devtools-kit
    └── ✕ missing peer vite@"*"
✕ Conflicting peer dependencies:
  vite

I had to add auto-install-peers=true to .npmrc as suggested after pnpm install.
2- I had to disable devtools in nuxt.config.ts, otherwise I get: performance is not defined error (I know it's experimental feature).
3- Lastly the message:
WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <5.1.0

YOUR TYPESCRIPT VERSION: 5.1.3

Please only submit bug reports when using the officially supported version.

Can these issues be solve somehow with by installing stable versions (--prod option)?
I believe all these issues are related to my old node version v14.18.3 (I know it's too old), although I've upgraded node two times last year, that's wasn't easy when maintaining too many projects simultaneously, that's ok if it was a library, but for a web framework, that's feel like we need more stable LTS versions for Nuxt?

I'm closing this as I can't reproduce and the latest comments are not really related to the original reported issue. If you can provide a reproduction or some steps I can take to reproduce on OSX, let me know and I'll reopen.


Create Sample App Ownership and Consent slices

Ownership and Consent Slices
Viewers of the current ownership and consent used in try it out screen.
Implementation defined in #116

waiting on #117 to test and merge


Make API_BASE_URL configurable

If API_BASE_URL were configurable, then pyAirtable could be used to send write requests (POST, PATCH, PUT, DELETE) via the Sequin proxy:

See https://docs.sequin.io/airtable/reference#how-to-write-through-the-proxy

Sequin proxies requests to the Airtable API. All it requires is to send API requests to https://proxy.sequin.io/api.airtable.com instead of https://api.airtable.com.

I have not tested this, not it's documented, but you should be able to do this:
from pyairtable import Table
Table.API_BASE_URL = "https://proxy.sequin.io/api.airtable.com"

Let me know if it works

Would be worth to document :)


Accuracy difference between Tesseract and other

#Environment

Tesseract Version: 4.1

Platform: Windows 10 and Ubuntu 16

I'm using tesseract for a long time and really super thankful for all who supporting and developing it. That's not a post about complaining or something about that. It's more to understand how the results with tesseract can be improved.
I've tried to compare some output from different OCR providers based on their private tech and it seems the difference currently is huge. Please check it.
That's a Tesseract result without any preprocessing:

That's a result of Azure OCR service without any preprocessing:

That's a Tesseract result with any preprocessing:

Yeah with binarization and some tweaks that result is much better but still, there is a lot of mistakes.
I see that you guys collecting ideas for version 5.0 and there are my suggestions:

It seems tesseract needs some kind of build-in preprocessing of image: binarization, white balancing. noise reduction using OpenCV cause that's the biggest gap comparing to others.
Even with pre-processing, the accuracy is lower compared to other providers. I don't know what's the reason here but definitely should be addressed in future releases.

Meanwhile, If somebody has ideas about how I can improve accuracy with tesseract you are more then welcome.

IMO you are mixing here several topics. So first let me explain you why your comparison is not correct:

comparing tesseract to Azure: you are comparing OCR engine (tesseract) with complex computer vision solution. If you want to be faire, you need to compare Azure computer vision with Google vision. Or compare tesseract with other opensource OCR libraries, if you want to get correct picture.
you are comparing opensource solution with proprietary solution => everybody can use tesseract know-how for free (it use very permissive licence), but nobody has access to proprietary solution for free or under permissive licence.
you are comparing solution with limited resources (tesseract) with solution of multibilion company with large portfolio of patents, financing a lof of research etc.
you are comparing solution that you can run localy on your computer with cloud based solution. This has several consequences:
a) you can get much better computer power/performance on cloud than on local computer
b) you have absolutely no control (in cloud) of your data and information you asked for analyze.

Next topic is about philosophy: tesseract is OCR engine/library. It does one thing and best way as possible. That was reason why image opening and some image processing was changed from own solution to leptonica. There is no aim (and capacity) to extend focus from OCR to image processing. There are other tools for it (e.g. Scantailor for book/documents, or OpenCV). Integration should be done outside of tesseract => as new project.
IMHO here are much more needed tasks like table reconstruction, formatting reconstruction or better document layout  analyze (header, footer, footnotes, titles..)

@Gaploid Hi, Im also working on preprocessing the images to pass it to Tesseract ocr for improving the accuracy. Would you like to share some knowledge with me? I have done some preprocessing steps like resizing, converting2gray, binarization(otsu+adaptive+binary) in different combinations and i did smoothening and noise removal. Still i couldnt achieve the desired accuracy.


Documentation link is broken

GitHub repo and README links to https://fsprojects.github.io/Fabulous/ but that 404's.

Thanks for the report. It should be fixed now


broadsea-atlasdb: Docker volume does not let initialization scripts to run.

Hi,
In the docker-compose.yml, because of following lines:
volumes:
    - atlasdb-postgres-data:/var/lib/postgresql/data
    - ./100_populate_source_source_daimon.sql:/docker-entrypoint-initdb.d/100_populate_source_source_daimon.sql:ro

I receive the skipping initialization warning, which leads ./100_populate_source_source_daimon.sql:/docker-entrypoint-initdb.d/100_populate_source_source_daimon.sql:ro script to not to run.

Linked issue: https://stackoverflow.com/questions/59715622/docker-compose-and-create-db-in-postgres-on-init
https://registry.hub.docker.com/_/postgres/
I have checked the solutions and applied could not resolve it. Any recommendations?

@SukruHan
The scripts are only executed when the atlasdb Docker container is started for the first time. Subsequently the Docker volume retains the data so there is no need to run the scripts again.
If you are sure that you want to start over with the initial state of the atlasdb and rerun the scripts then you can remove the docker volume: (note this will remove any database inserts/updates you may have previously applied to the database! This command cannot be undone!)
docker volume rm atlasdb-postgres-data


Add lint-staged

A quick note to self to add lint-staged to prevent errors such as #453 to not happen again. When I have time.

Closed in #459 and #460.


#5690: Recurisvely add ttl submodules and wrap their functions

As reported in #5690 functions like ttnn.experimental.operations.primary.transformers.group_attn_matmul do not get wrapped by the register_ttl_operation_as_ttnn_operation because the code to do so only looks at direct attributes of ttl.operations.primary and does not recurse into the transformers submodule.
This code fixes that.
Note: this PR replaces the previous https://github.com/tenstorrent-metal/tt-metal/pull/5692 which was based on an incorrect branch

Made redundant by https://github.com/tenstorrent-metal/tt-metal/pull/5652


[BUG] On Desktop, sometimes the first hybrid node you click becomes locked in both teleop and auto and appears with the cone icon.

As far as I can tell, it only happens when you've just loaded the page.

This only occurs if you click a hybrid node first.

Fixed in 763bba3


Add batchworker support to SDK

Adds batchworker support to SDK

Merging to get all changes together and continue testing in workers...


chore: update to v0.3.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: host: sk-video=1.1.10 must contain a space between the name and the pin, i.e. sk-video =1.1.10
requirements: run: sk-video=1.1.10 must contain a space between the name and the pin, i.e. sk-video =1.1.10

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Scanner changes

There are 2 commits in this PR.

Commit should go to azcopy repo as it export the different APIs.
Commit where a sample scanner.go is there which utilize these exported APIs to give scanner functionality. We are utilizing azcopy creation of crawler code which is linked to traverser interface depending on type of source directory.

Need to try with /dev/NULL as destination if it works we can provide dummy destination to /dev/NULL.
Right now i tried with giving src-> local filesystem, dest-> blob and vice-versa.

@nitin-deamon could you also include @johnmic in these PRs so he can build some context etc? Thanks!

@nitin-deamon could you also include @johnmic in these PRs so he can build some context etc? Thanks!

done @shalinijoshi19

Could you please add mohsha-msft nakulkar-msft adreed-msft as reviewers and to this repo? Thanks

Could you please add mohsha-msft nakulkar-msft adreed-msft as reviewers and to this repo? Thanks

Hi @zezha-msft I added them to repo. Once they accept the invitation , i will added them as reviewer.

There are 2 commits in this PR.

Commit should go to azcopy repo as it export the different APIs.
Commit where a sample scanner.go is there which utilize these exported APIs to give scanner functionality. We are utilizing azcopy creation of crawler code which is linked to traverser interface depending on type of source directory.

Need to try with /dev/NULL as destination if it works we can provide dummy destination to /dev/NULL.
Right now i tried with giving src-> local filesystem, dest-> blob and vice-versa.

@nitin-deamon do we have an updated set of commits at this point already? My assumption is we were going to split this so that #1 could be a new PR in the azcopy repo and #2 would be merged into our msazure instance?

Hey @nitin-deamon when do you think we'd be able to close on this one? Are there more changes for us to look at since?

@shalinijoshi19 Already created the branch in azcopy repo, and cherry pick the changes to it. I need to push changes to our Repo.


feature:

Did you check the tree-sitter docs?

[x] I have read all the tree-sitter docs if it relates to using the parser

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like

Describe alternatives you've considered
No response
Additional context
Adding code-lens commands to run BAZEL commands
Bazel has runnable rules, like:
go_binary(
    name = "main",
    embed = [":main_lib"],
    visibility = ["//visibility:public"],
)

and buildable, like:
go_library(
    name = "main_lib",
    srcs = ["main.go"],
    deps = [
    ],
    visibility = ["//visibility:private"],
)

Currently the extension doesn't have code lens commands to run/build these rules. Is it possible to add them?

this is a parser not an lsp.


Inconsistent quoting on unknown flag error

 unknown flag `f'
https://github.com/jessevdk/go-flags/blob/6b9493b3cb60367edd942144879646604089e3f7/parser.go#L535
Use of both backtick and single quote.

This is an intentional typographic approximation of quotation marks in ASCII. It's a blast from the past.


Bluetooth headphones not showing in sd.query_devices()

I'm running python3.8 on arch linux. When I use sd.play() it plays the audio to the built-in speaker. To change the device used sd.query_devices() but the output is
   0 HDA Intel PCH: ALC3266 Analog (hw:0,0), ALSA (2 in, 2 out)
   1 HDA Intel PCH: HDMI 0 (hw:0,3), ALSA (0 in, 8 out)
   2 HDA Intel PCH: HDMI 1 (hw:0,7), ALSA (0 in, 8 out)
   3 HDA Intel PCH: HDMI 2 (hw:0,8), ALSA (0 in, 8 out)
   4 HDA Intel PCH: HDMI 3 (hw:0,9), ALSA (0 in, 8 out)
   5 HDA Intel PCH: HDMI 4 (hw:0,10), ALSA (0 in, 8 out)
   6 sysdefault, ALSA (128 in, 128 out)
   7 front, ALSA (0 in, 2 out)
   8 surround40, ALSA (0 in, 2 out)
   9 surround51, ALSA (0 in, 2 out)
  10 surround71, ALSA (0 in, 2 out)
  11 hdmi, ALSA (0 in, 8 out)
* 12 default, ALSA (128 in, 128 out)
  13 dmix, ALSA (0 in, 2 out)

From my understanding none of these is the Bluetooth headphone connect to my laptop. How can I get sounddevice to detect my bluetooth headphones?

Tinkering with the bluez-alsa package and installing pulseaudio-alsa solved this issue!

Tinkering with the bluez-alsa package and installing pulseaudio-alsa solved this issue!

I'm having the same issue, what tinkering did you do to get all this to work?

@ApplicationNinja see https://github.com/spatialaudio/python-sounddevice/issues/343#issuecomment-875038235. Maybe that helps.


Project Status?

Hi, I have accidentally found this repo and implemented it inside my demo app and it works great. But gotta ask is this project over/abandoned/done? I am just curious since it's a long time from last update and I do like how it behaves.
Thank you!

Good question.  I am still monitoring and merging pull requests anytime someone contributes, but I haven't contributed much to this project myself in quite a while.  I'm open to new pull requests anytime.


selectYear-trigger not working

Hi, thanks for the nice plugin!
During the integration I noticed that the event "selectYear" doesn't work.

Hello, thank you for the appreciation! :slightly_smiling_face:
There's no selectYear event yet because I just thought no one will need it :sweat_smile: I'll add it.

Oh sorry, i mixed "events" and "methods"! I want to fetch events of the selected month by an api-call an add the results with the method "addCalendarEvent". This api-call should be executed if the year is changing. The event "selectYear" would be nice. ;-)

Hello, sorry for the late response. But the event selectYear has been added now! :hugs:


v1.13 Backports 2023-01-23

[ ] #23009 -- daemon: Fix BPF host routing can't be enabled if the devices are wildcard (@ysksuzuki)
[ ] #22975 -- Bpf: Add missing policy match cases (@jrajahalme)
[x] #22671 -- ingress/model: Support multiple certs based on SNI (@sayboras)
[ ] #23095 -- docs: Improve wording for deny policies limitation (@joestringer)
[x] #23135 -- docs: Improve IPsec guide (@pchaigno)
[ ] #22408 -- hubble: Update the reason label for hubble_drop_total metric (@michi-covalent)
[ ] #23124 -- Bump Linux minimum version to 4.19.57 (or equivalent) (@joestringer)
[x] #23141 -- Document socket LB tracing (@aditighag)
[ ] #23140 -- build(deps): update package dependencies (@fengshunli)
[ ] #23134 -- docs: update committer security requirements (@xmulligan)
[x] #23099 -- gha: Pin minikube version used in CI (@sayboras)
[ ] #23025 -- docs: Mark pod-short option in Hubble metrics as deprecated (@lambdanis)
[ ] #22756 -- bpf: nodeport: handle revDNAT for local backends at to-netdev/to-overlay (@julianwiedmann)
[x] #23158 -- IPsec: Refactor ipSecReplaceState{In,Out} functions (@pchaigno)
[x] #23195 -- gh: fix indentation bug in ingress workflows (@julianwiedmann)
[ ] #22695 -- refactoring of fetching cilium manifests in OKD installation (@zisisli)
[ ] #22913 -- docs: Update Minikube ver. requirement and manual BPFFS mount instructions   (@kimstacy)
[x] #23225 -- docs: Fix inconsistent node label in egress gateway guide (@pchaigno)
[ ] #23163 -- images/runtime: bump iptables package to 1.8.8 (@jibi)

PRs skipped due conflicts:

#22425 -- gh/workflows: tune LVH VM params (@brb)
#22928 -- CODEOWNERS: Cover test/bpf_tests by sig-datapath (@christarazi)
#23020 -- ci: extend nat46x64 l4lb test suite (@borkmann)
#23145 -- Use workflow configuration variables for quay organization names (@michi-covalent)
#23137 -- clustermesh/types: don't panic on invalid IP in PrefixClusterFromCIDR (@tklauser)
#23170 -- k8s/watchers: Fix race condition in init functions (@christarazi)
#21980 -- datapath: Fix L7 reply to outside when endpoint routes disabled (@brb)

Once this PR is merged, you can update the PR labels via:
$ for pr in 23009 22975 22671 23095 23135 22408 23124 23141 23140 23134 23099 23025 22756 23158 23195 22695 22913 23225 23163; do contrib/backporting/set-labels.py $pr done 1.13; done

or with
$ make add-label BRANCH=v1.13 ISSUES=23009,22975,22671,23095,23135,22408,23124,23141,23140,23134,23099,23025,22756,23158,23195,22695,22913,23225,23163

/test-backport-1.13

/test-backport-1.13

/test-runtime

previous runtime https://jenkins.cilium.io/job/Cilium-PR-Runtime-net-next/4634

k8s-1.21-kernel-4.9 hit https://github.com/cilium/cilium/issues/23047
k8s-1.26-kernel-net-next hit https://github.com/cilium/cilium/issues/21519

/mlh new-flake Cilium-PR-K8s-1.18-kernel-4.9

Merging this one since the failure in Cilium-PR-K8s-1.18-kernel-4.9 was not seen in other tests runs with the same kernel version and different k8s version. We will re-run a full CI in https://github.com/cilium/cilium/pull/23243 as well to have more data.


Check if Cluster is ready and if control plane rolling update has finished

What this PR does

Add common basic test that checks if Cluster Ready condition has Status=True.
Add upgrade test that checks if control plane rolling update has finished (if it has started).

The second test here is the more important one, as it makes sure that a control plane rolling update has finished before it executes other tests.
Before having this control plane rolling update test, other post-upgrade tests would continue running even though the cluster upgrade has not been completed, so those test would make checks in a cluster that has a mix of old and new nodes.
Now with the new control plane rolling update test at least control plane nodes should be done with a rolling update, so the subsequent checks will be more reliable.
Checklist

[x] Update changelog in CHANGELOG.md.
[x] Update clustertest to a released version (waiting on https://github.com/giantswarm/clustertest/pull/166)

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites


Split run script

Adding config + dockerfile support to automatically name the node. Previously defaulted to 'ejabberd@localhost'.
I've added an environment variable EJABBERD_NODENAME to the Dockerfile, to give the base name for the node(s).
The HOSTNAME environment variable is dynamically set when running, and is concatenated after the EJABBERD_NODENAME to generate the ERLANG_NODE environment variable, which is needed while generating the ejabberdctl.cfg file.
Finally, I've added a extra option next to 'start' and 'live': 'shell' will simply run /bin/bash inside the docker container.

I think the EJABBERD_NODENAME get in conflict with https://github.com/rroemhild/docker-ejabberd/blob/master/run#L154-157. I copied this part to the wrong pre-script. It should be left in the run script to get processed on early stage. Or did I miss something?

I add ERLANG_NODE back to the run-script with the latest commit 0b2abbe5.

No EJABBERD_NODENAME is meant to be able to define the part before the '@' via an environment variable (e.g. in the Dockerfile). The part after the '@' will default to the hostname.

If I'm not getting it wrong erlang adds the hostname to nodename https://github.com/rroemhild/docker-ejabberd/blob/master/ejabberdctl.cfg.tpl#L121-L137

You are correct.
Also I understand that you currently generate a random password, but looking at clustering multiple ejabberd nodes, It might be usefull to be able to define the password with an environment variable (maybe even in the docker file)? That way, all the ejabberd nodes that will be added in the cluster, will have the same password for the admin user.

Added an envvar to define admin passwords and cherry-picked your commits 615cb3144e5ce75b17bb3ff03523c254d6a0cc1a and 1d2ebc8a25dd88999f77da618b3e2bbda05ca538 to keep the commit log clean, hopefully this is ok for you.

Great, thanks!


Core: Json.Stringify does not escape double quotes

io.gatling.core.json.Json.stringify method stringifies objects as JSON strings. This generally works fine, but not when a string value has double quotes. This would seem safe generally, but not when a whole JSON is stringified. Imagine this case:
val mapOriginalValue = Map[String,Any]("key1" -> "Regular foo", "key2" -> "Quoted \"foo\"");
val stringifiedMap = stringify(mapOriginalValue);
println("Stringified JSON: " + stringifiedMap);

expected output would be
Stringified JSON: {"key1":"Regular foo","key2":"Quoted \"foo\""}
instead the result is
Stringified JSON: {"key1":"Regular foo","key2":"Quoted "foo""}
This is not valid JSON.
I have tried to find where the problem is. In file Json.scala line 48, escaping is implemented for line feeds but not double quotes.
Adding escaping for double quotes is easy and I can prepare a PR, but this might break existing code, depending on this "feature". You can recommend the proper solution and I can implement it.
val originalValue = "Quoted \"foo\"";
val expectedValue = "Quoted \\\"foo\\\"";
val stringified = stringify(originalValue);
if (originalValue == expectedValue) {
	println("Stringified works properly")
} else {
	println("Stringify is not working properly")
}

results in Stringify is not working properly

Thanks for reporting!
Are you interested in contributing a fix?

yes. I am testing a fix right now, but I am not sure if maybe someone somewhere is using this code in a wrong way and the fix will break their code

Added PR https://github.com/gatling/gatling/pull/3297 to fix this

Replaced with PR #3298


The discord badge is broken

The discord badge at the top of the README shows that the widget is disabled.
https://blog.discord.com/add-the-discord-widget-to-your-site-d45ffcd718c6

I enabled it, closing.


Multithreaded Client

Addresses #2218.
This introduces two changes.

Internally, it has the client library hold and accept some S: Signer + Send + Sync instead of some dyn Signer. This makes the Client (and other) types Send and Sync.
We change all std::rc::Rc to std::sync::Arc so that the Client (and other) types can be shared across threads. This allows builders to write multithreaded (async, parallel) codes that use an anchor_client::Client.

We also update the client/example to include a single and multithreaded test..

This seems cool for sure but looks like a major breaking change / a lot of rewriting will be needed by anyone using the new client?

I think this is good to merge just two things

please add it as a breaking change to the changelog
Based on some CI test errors, it looks like the zero copy test uses the client and is broken, so it also needs to be updated

Hopefully we can merge and someone of the insane people who use anchor/master to dev off of can give comments on how it affects their client experience!

BTW this should no longer introduce breaking changes and all tests pass

Excellent, I will review and merge. Have you added the changelog?
On Fri, Feb 3, 2023, 7:22 AM cavemanloverboy @.***>
wrote:

BTW this should no longer introduce breaking changes and all tests pass
—
Reply to this email directly, view it on GitHub
https://github.com/coral-xyz/anchor/pull/2321#issuecomment-1415210074,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAHMGD24XOAKNKVUZM7S2DWVSW3HANCNFSM6AAAAAATCJPB5Q
.
You are receiving this because you commented.Message ID:
@.***>

I'm going to merge this before it goes on any longer but before releasing the next version of anchor it would be really helpful if you were able to write up something about how to use the new multithreaded option and whether anything needs to be changes about existing tests to use it. e.g. In the example test there's a slightly complicated type alias for the test function, should all multithreaded tests be written using such a pattern / type?