Camer Plugin Preview Rotated

The camera plugin version 0.8.1 is turning the camera preview rotated by 1 quarter in iOS while it is being used as Flutter Module.

@therealblue10
can you provide your flutter doctor -v and a minimal reproducible code sample
possibly related to
https://github.com/flutter/flutter/issues/25232
https://github.com/flutter/flutter/issues/45227
https://github.com/flutter/flutter/issues/73670
https://github.com/flutter/flutter/issues/78685

@therealblue10
Please provide above requested details to properly address your issue.
Thanks.

Steps to Reproduce

Take the example flutter app provided with camera plugin
Create a flutter module
Present the example app inside the iOS app using a new Flutter Engine and a different vm-entry-point
You will see an inverted camera preview

Take the example flutter app provided with camera plugin
Remove the local path and add the latest camera library (camera: ^0.8.1) from pub.dev
Create a flutter module

4. Present the example app inside the iOS app using a new Flutter Engine and a different vm-entry-point

@therealblue10
I believe this step is what is usually intended for  "producing a minimal reproducible code sample"
the issue might really come down to the specific implementation
and someone else implementation can differ from yours; it would be useful if you could provide your sample directly

iOS Side Code
    `let flutterEngine = FlutterEngine.init(name: "Camera")
    flutterEngine.run(withEntrypoint: "cameraEntryPoint")
    GeneratedPluginRegistrant.register(with: flutterEngine);
    let cameraViewController = FlutterViewController.init(engine: flutterEngine, nibName: nil, bundle: nil)
    self.navigationController?.pushViewController(cameraViewController, animated: true)`

Flutter Side Code
// ENTRY POINTS
@pragma('vm:entry-point')
void cameraEntryPoint() => runApp(CameraApp());

@therealblue10
This still looks like code sample in pieces. What we would like to have is a complete reproducible code sample that we can simply copy paste and run that shows the issue. You may push the sample code in a repo and provide the link here that we can clone and directly run to verify the issue.
Thanks.
Also check the related issues mentioned earlier and see if any of those look similar to yours.

Yes, that would do I think. I will push the code.
Get Outlook for iOShttps://aka.ms/o0ukef

From: darshankawar @.>
Sent: Tuesday, April 6, 2021 11:28:59 AM
To: flutter/flutter @.>
Cc: Rohit Kumar @.>; Mention @.>
Subject: Re: [flutter/flutter] Camer Plugin Preview Rotated (#79709)
@therealblue10https://github.com/therealblue10
This still looks like code sample in pieces. What we would like to have is a complete reproducible code sample that we can simply copy paste and run that shows the issue. You may push the sample code in a repo and provide the link here that we can clone and directly run to verify the issue.
Thanks.
Also check the related issues mentioned earlier and see if any of those look similar to yours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/79709#issuecomment-813845846, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOVGLXHQI2CNXE5DG62IW5DTHKPKHANCNFSM42KLI2UA.

Having the same behavior. CameraPreview gets rotated by 90 degrees when the phone is rotated vertically, however returns to the normal state in horizontal phone position. It is reproduced on iOS only.

Having the same behavior. CameraPreview gets rotated by 90 degrees when the phone is rotated vertically, however returns to the normal state in horizontal phone position. It is reproduced on iOS only.

@yurijdvornyk
can you provide your flutter doctor -v and a minimal reproducible code sample

What we would like to have is a complete reproducible code sample that we can simply copy paste and run that shows the issue.

Here is the flutter doctor output. Working on a minimal piece of code where you can reproduce it.
`flutter doctor -v
[✓] Flutter (Channel stable, 2.0.2, on macOS 11.1 20C69 darwin-x64, locale en-GB)
• Flutter version 2.0.2 at /Users/yurii.dvornyk/Documents/flutter
• Framework revision 8962f6dc68 (5 weeks ago), 2021-03-11 13:22:20 -0800
• Engine revision 5d8bf811b3
• Dart version 2.12.1
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/yurii.dvornyk/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• ANDROID_HOME = /Users/yurii.dvornyk/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• 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 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.55.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.21.0
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 90.0.4430.72
• No issues found!`

@iapicca , it's quite simple to reproduce it.
Simply run the library example code with landscape locked on your iOS device:) [currently testing on XS]
I just added locking the orientation into the beginning of initState method of the example (https://github.com/flutter/plugins/blob/master/packages/camera/camera/example/lib/main.dart):
 @override
  void initState() {
    super.initState();
    SystemChrome.setPreferredOrientations([
      Platform.isIOS
          ? DeviceOrientation.landscapeRight
          : DeviceOrientation.landscapeLeft
    ]);
    WidgetsBinding.instance?.addObserver(this);
    .............
    }

You can see the result on preview attached.
https://user-images.githubusercontent.com/7055902/115115260-1b7fb180-9f9c-11eb-901a-5634244fabc5.mov

Hi @iapicca , were you able to reproduce this issue?

Hi everyone,
Was facing this issue for the last few days. By reading documentation & example project code carefully I found these functions very useful:
CameraController.lockCaptureOrientation
CameraController.unlockCaptureOrientation
Locking the capture orientation did trick for me.

Hi @iapicca @darshankawar , were you able to reproduce this issue?

@yurijdvornyk
sorry, I can't repro on ios

@Ahsanwarsi , yep, works for me like a charm! Thanks a lot!
cc @therealblue10 @iapicca @darshankawar

@darshankawar @iapicca Here is the code, please take a pull and run the iOS example app on a real device.  https://github.com/therealblue10/flutter_camera_issue

@therealblue10
Please check if this is similar to https://github.com/flutter/flutter/issues/76210

@darshankawar Not sure how to resolve this issue for newer versions in the ticket number you pointed out. I would request to run the example code and find out the potential issues. Further, if it was resolved in the previous version and introduced again in the latest version that itself raises an alarm which you should be looking. It's a direct plugin issue rather than being an implementation issue. Hope Flutter team resolves it soon rather than dodging the issue with lot of threads.

@therealblue10 Thanks for the repro code, but I see a black screen upon running your code on physical device.
Nevertheless, I tried the official camera plugin example on latest stable and using latest plugin version (0.8.1) with which I see the camera preview rotated as below:

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.0.5 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision adc687823a (4 days ago), 2021-04-16 09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

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

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 89.0.4389.128

! Doctor found issues in 1 category.

Hope Flutter team resolves it soon rather than dodging the issue with lot of threads.

Also, nobody is trying to dodge any issues. We both are in it together to make this framework and plugin better and user friendly.
Moreover, you never provided a repro use case earlier.  The code sample you earlier provided was not complete to work with and the issue I referred earlier was to make sure / confirm if you are facing similar behavior.

A similar issue was fixed and merged into Master, https://github.com/flutter/flutter/issues/76210. Not sure if it has reached stable yet, but tagging @mvanbeusekom for further insights.

@darshankawar thank you for making me aware of this issue, I am looking into it.
I quickly tested with the current example App which you suggest also shows this behaviour, but I cannot reproduce it. Here are the steps I took:

Clone the flutter/plugins repo: git clone git@github.com:flutter/plugins.git;
Change into the packages/camera/camera/example folder: cd plugins/packages/camera/camera/example;
Build the iOS version of the example App: flutter build ios --no-codesign;
Edit the pubspec.yaml and replace the camera path reference with the latest pub.dev version:   camera: ^0.8.1;
Run the App on a real iPhone (in my case an iPhone 12 mini): flutter run -d <device_id>

Now the App runs normally (orientation is correct), also when rotating the orientation is updated correctly. Did you take any specific steps in the App or when configuring the example App?
I will try the reproduction example provided by @therealblue10 next, but it would be good to get everything on the same page.

 flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.3 20D91 darwin-x64, locale en-GB)
    • Flutter version 2.0.4 at /Users/maurits/fvm/versions/stable
    • Framework revision b1395592de (3 weeks ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/maurits/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/maurits/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • 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 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 55.1.4
    • Dart plugin version 203.7759

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

[✓] Connected device (2 available)
    • M2003J15SC (mobile) • 106fdad20410 • android-arm64  • Android 10 (API 29)
    • Chrome (web)        • chrome       • web-javascript • Google Chrome 89.0.4389.128

I have also tried the reproduction example provided by @therealblue10, but like @darshankawar I also only get a black screen. I am not familiar with Flutter Modules which makes it difficult for me to see what is wrong in the reproduction example. If I find some time I will look into it as it is an interesting topic, but it would help if @therealblue10 could make sure the code is correct.

@mvanbeusekom The catch here is to run iOS app and integrate flutter as Flutter module and running the code as another vm entry point.
Flutter Side
// ENTRY POINTS
@pragma('vm:entry-point')
void cameraEntryPoint() => runApp(CameraApp());

iOS Side
@IBAction func showFlutterViewController(_ sender: Any) {
let flutterEngine           = FlutterEngine.init(name: "Camera")
flutterEngine.run(withEntrypoint: "cameraEntryPoint")
GeneratedPluginRegistrant.register(with: flutterEngine);
let cameraViewController = FlutterViewController.init(engine: flutterEngine, nibName: nil, bundle: nil)
self.navigationController?.pushViewController(cameraViewController, animated: true)
}

@mvanbeusekom @darshankawar I don't know who fixed what but after renaming the button to open the Flutter camera, it started workday correctly miraculously. Attached is the video.
@darshankawar You needed to tap the next button to open Flutter screen from the first screen (Black screen with Navigation Bar and Next button on the top right corner)
https://user-images.githubusercontent.com/61498844/115726840-b6afc700-a3a0-11eb-92b4-798273315913.MP4

I've also got @therealblue10's example working. I had to run pod deintegrate in the CameraPluginTest project followed by pod install.
After that, when I opened the CameraPluginTest project in Xcode I was able to select the CameraPluginTest target and run the application. For me the orientation is also as it should be (see video)
https://user-images.githubusercontent.com/13098888/115729446-b524d580-a385-11eb-84a9-2a8449a27438.MP4

@mvanbeusekom As I said, for some reason, it started working correctly but another issue is camera exception that you see for a split of a second. We can close this issue now probably.

Unfortunately, the issue still persists. There is something wrong with the camera plugin, I can't find what.

@therealblue10, could it be something related to your app picking an older version of the camera plugin? Version 0.8.1 was al about fixing this issue.
Could you try removing all camera plugin versions from your local pub cache. Usually this is located in ~/.pub-cache/hosted/pub.dartlang.org on a macOS machine. So something like this should do the trick:
rm -rf ~/.pub-cache/hosted/pub.dartlang.org/camera*

I definitely can but why I am sure about the version 0.8.1 contains the issue is because 0.8.0 works fine Here is a screenshot from 0.8.0 version. Further, I have verified in pubspec.lock file for the version. Only 0.8.1 had this issue.

I deintegrated the pod and installed in again for some reason it works well. I am closing this issue. Thank everyone for the support!


Added checkbox support

I'll add the version bump to this PR once it has been reviewed/approved.

@Samsinite, I altered this to allow for the following syntax:
{{bootstrap-input type="checkbox" label='Unlimited' value=product.unlimited}} instead of {{bootstrap-input type="checkbox" label='Unlimited' checked=product.unlimited}}
I thought it might be one less thing to remember if you always pass the value in as value and let the addon handle how it works, rather than have the consumer of this addon need to remember that in the use case of checkbox you don't use value, you use checked.

I like the single interface idea, but lets keep the template as simple as possible and related to markup only. You can decorate the value and checked properties to achieve this:
valueDecorator: Ember.computed('value', 'type', function() { ... },
checkedDecorator: Ember.computed('value', 'type', function() { ... }

{{input value=valueDecorator checked=checkedDecorator ...}}

Also, have you eaten your own dog food on this (npm linked and tested it in an app)? If not, please at least manually test it in the dummy app inside of the addon or write some component integration tests to make sure the checkboxes are working correctly and that nothing else is broken.

Updated and manually tested.


Sizing of Alarm

I've tried using custom.css to adjust the alarm size. No luck. Any help pointing me in the right direction would be very much appreciated.

Hi,
what do you mean by "Alarm"? Do you mean the clock itself? You can just use the transform-scale operator from css to scale the element like so:
.mmm-touchalarm {
  transform: scale(2);
}


[BEAM-8696] protobuf-java 3.14.0 in line with libraries BOM 16.3.0

Upgrading the protobuf version to make it in-line with the one in the libraries BOM.
Linkage Check
There's no new linkage errors: https://gist.github.com/suztomo/401dfa525b385346b6fcec091bff7f42

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java Precommit

Run Java Precommit

Run GoPortable PreCommit

Run Website_Stage_GCS PreCommit

???
11:21:40 > Task :website:setupVirtualenv
11:21:40 Using base prefix '/usr'
11:21:40 New python executable in /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Website_Stage_GCS_Commit/src/build/website/gradleenv/bin/python3
11:21:40 Also creating executable in /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Website_Stage_GCS_Commit/src/build/website/gradleenv/bin/python
11:21:40 Installing setuptools, pip, wheel...
11:21:43
11:21:43   Complete output from command /home/jenkins/jenkin...radleenv/bin/python3 - setuptools pip wheel:
11:21:43   Looking in links: /usr/local/lib/python3.5/dist-packages/virtualenv_support
11:21:43 Collecting setuptools
11:21:43   Using cached https://files.pythonhosted.org/packages/9e/d4/b99a960314121a003e9f39c61dfde01a1010bb47661e193a7722f7f32d52/setuptools-54.2.0-py3-none-any.whl
11:21:43 setuptools requires Python '>=3.6' but the running Python is 3.5.2

Run Website_Stage_GCS PreCommit

Run Website_Stage_GCS PreCommit

Run GoPortable PreCommit

Run Python PreCommit

Run Python_PVR_Flink PreCommit

Run Java PreCommit

Run GoPortable PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java Precommit

Run GoPortable PreCommit

R: @kennknowles

Is this worth a cherry pick to 2.29.0? Currently there are other blockers, and this would seem to overall reduce the risk of that release.

@kennknowles That’s a good idea. Can you cherry-pick this?

I could do it, but here is the process:
git checkout -b cherrypick-14412 github/release-2.29.0
git cherry-pick 7bdad6c9fc7afa91cfde40a6afe81c74d3026888
git push suztomo
<open PR to release-2.29.0 branch>

Created a PR https://github.com/apache/beam/pull/14456
Thank you for the guide!


Debugging not possible with example: nextjs-server-components

Bug report
Describe the bug
This example runs fine with npm run dev, but crashes when debugging on Webstorm or VsCode. The following error is copied from Webstorm.
TypeError: Cannot read properties of undefined (reading 'cookies') at cookies (webpack-internal:///(sc_server)/./node_modules/next/dist/client/components/headers.js:23:25) at getCookie (webpack-internal:///(sc_server)/./node_modules/@supabase/auth-helpers-nextjs/dist/index.js:355:33) at createServerSupabaseClient (webpack-internal:///(sc_server)/./node_modules/@supabase/auth-helpers-shared/dist/index.js:355:52) at createServerComponentSupabaseClient (webpack-internal:///(sc_server)/./node_modules/@supabase/auth-helpers-nextjs/dist/index.js:346:71) at RootLayout (webpack-internal:///(sc_server)/./app/layout.tsx:25:120) at preloadComponent (/Users/zeebs/GitRepos/supabase-next13-auth-example/examples/nextjs-server-components/node_modules/next/dist/server/app-render.js:79:22) at /Users/zeebs/GitRepos/supabase-next13-auth-example/examples/nextjs-server-components/node_modules/next/dist/server/app-render.js:750:24 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async createComponentTree (/Users/zeebs/GitRepos/supabase-next13-auth-example/examples/nextjs-server-components/node_modules/next/dist/server/app-render.js:749:25) at async wrappedRender (/Users/zeebs/GitRepos/supabase-next13-auth-example/examples/nextjs-server-components/node_modules/next/dist/server/app-render.js:891:47) {digest: "1536623941", stack: "TypeError: Cannot read properties of undefined (re…de_modules/next/dist/server/app-render.js:891:47)", message: "Cannot read properties of undefined (reading 'cookies')"}
To Reproduce
clone and run the nextjs-server-components example (run's fine with npm run dev)
Then try and run with debugger attached (i've tried both Webstorm and VSCode)
-> should crash with Unhandled Runtime Error: Cannot read properties of undefined (reading 'cookies')
Expected behavior
Should run same in debugger as in dev mode
System information

MacOS
Chrome, Brave, Safari
Version of supabase-js: 2.0.4
Version of Node.js:  18.7.0

Additional context
Am looking to migrate to server-components architecture, but won't until I'm confident that I can debug my code easily

  createServerComponentSupabaseClient({         headers,         cookies,     })
I'm having the same error.

The debugger likely has no understand of a monorepo and this could potentially be causing the issue. Closing this as its more related to the debugging tool than the codebase.


Bug: Cannot set ps_iter to 0

The Estimation class does not work with ps_iter = 0.

Fixed: https://github.com/sdu-cfei/modest-py/pull/40


Add a note about staticlibs

Fixes https://github.com/hughsie/uefi-sbom-best-practices/issues/17

Proposed tweaks:

Much better, thanks!


MSX 1/2: suffixes and Incompatibilities

ArkOS 1.4 (latest online update) -> MSX1/2 Issues:
Suffixes that are propagated on the "ArkOS Emulators and Ports information" page (.msx1, .msx2) are not working and are non-standard.
The standard would be .mx1/.mx2, but in ArkOS these suffixes don't work. So far only the .rom suffix works. Maybe fMSX cannot interpret 4-lettter suffixes?
Many MSX2 games don't work at all or getting blank screens/weird resolution changes with the RetroArch (64-bit) core.

Thank you for reporting this.  I will correct the extension issue with the next update.  For MSX 2, can you try the suggestion in the link below and let me know if that works?
https://retropie.org.uk/docs/MSX/#setting-default-screen-on-msx2-and-turbor-machines

I think the suggestion to type something in is not practical on the user side,
but i looked at Retrobat and Recalbox and found that they use blueMSX
as the default MSX/MSX2 Emulator, whereas ArkOS uses fMSX.
Maybe changing the core could make a difference?
Tried different MSX2-games (50Hz/60Hz) on both systems and all work out of the box.

Bluemsx is available in ArkOS and is the default emulator for Coleco.  If you're familiar with Retroarch, can you load the games through retroarch using the bluemsx core and confirm that it truly resolves the issue?  Then I can incorporate it as the default core for msx in the next future update.

I can confirm that the games i tested with blueMSX do work, you can set blueMSX as the new standard core
for MSX1/MSX2, but... there is no button mapping for MSX1/2 with blueMSX - Someone needs to create a new mapping that fits the MSX systems.

Thank you for helping to test blueMSX.  Today's updates includes adding blueMSX as an additional and the default MSX1/2 emulator.


[Sub-issue] change fragment_articles_edited.xml and item_rv_articles_edited.xml to use constraintLayout

@ujjwalagrawal17  I want to work on this

Fixed in #116


Request to Assign Autocomment Issue File

I am keen on contributing to the repository by creating an autocomment feature for newly opened issues.
This feature will promptly acknowledge the creation of issues and provide contributors with relevant information and guidance. I believe implementing this feature would enhance the user experience and streamline the issue management process.
Assigning me this task under gssoc24 would be a valuable opportunity, and I look forward to contributing to the project in this capacity.

please assign me this issue to me under gssoc 24
i ll complete it very soon


rustc: 1.29.0 -> 1.29.1

Motivation for this change
Fixing a security sensitive bug in the rust stdlib.
From the changelog:

The standard library's str::repeat function contained an out of bounds write
caused by an integer overflow. This has been fixed by deterministically
panicking when an overflow happens.

This change should not break anything that wasn't broken on 1.29.0 before. I have been rebuilding large portions of nixpkgs on the current staging head and didn't encounter many issues.
We should probably provide backports to 18.03 & 18.03 following the patch proposed on the original announcement mail.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: rustc
Partial log (click to expand)
cannot build derivation '/nix/store/ggf8cp4pzbc1g3l7aryrmcnmlrda57sn-xmlto-0.0.28.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/y760i4bbln7cdiq7fmnlag5x4ivjzn23-opensp-1.5.2.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/gk9y8r5hxp1flr1fbzhxk3pghlvy3swq-swift-corefoundation.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/ravvpxxzcfjq22wrhmh340qx4bb5w0il-apple-framework-IOKit.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/8pqgq2lh74npwfa92hspp6z9jcws15s2-docbook2X-0.8.8.drv': 16 dependencies couldn't be built
cannot build derivation '/nix/store/3xcx7zsc3nf4qqzx01d3mb3n1315f66p-apple-framework-Security.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/pc51qs0v2xrzh6fazzkccpj0l3gqmsj0-git-2.19.0.drv': 29 dependencies couldn't be built
cannot build derivation '/nix/store/3v54z42cfc7dfz40r47knwh683rafyr8-rustc-bootstrap-1.28.0.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/xs36ffkpkp5q1cs92ilnb9a0qrpyhga1-rustc-1.29.1.drv': 16 dependencies couldn't be built
error: build of '/nix/store/xs36ffkpkp5q1cs92ilnb9a0qrpyhga1-rustc-1.29.1.drv' failed

Timed out, unknown build status on x86_64-linux (full log)
Attempted: rustc
Partial log (click to expand)
   Compiling rustc-rayon v0.1.1
   Compiling rustc_data_structures v0.0.0 (file:///build/rustc-1.29.1-src/src/librustc_data_structures)
   Compiling arena v0.0.0 (file:///build/rustc-1.29.1-src/src/libarena)
   Compiling syntax_pos v0.0.0 (file:///build/rustc-1.29.1-src/src/libsyntax_pos)
   Compiling rustc_errors v0.0.0 (file:///build/rustc-1.29.1-src/src/librustc_errors)
   Compiling proc_macro v0.0.0 (file:///build/rustc-1.29.1-src/src/libproc_macro)
   Compiling syntax_ext v0.0.0 (file:///build/rustc-1.29.1-src/src/libsyntax_ext)
   Compiling rustc_typeck v0.0.0 (file:///build/rustc-1.29.1-src/src/librustc_typeck)
building of '/nix/store/bg9j1jh39id3vmyal51mkh5nskdnwka9-rustc-1.29.1.drv' timed out after 3600 seconds
error: build of '/nix/store/bg9j1jh39id3vmyal51mkh5nskdnwka9-rustc-1.29.1.drv' failed

@andir please merge this together with #47556

When backporting to 18.03 don't forget to also disable the checkPhase there as well.

Maybe this should go straight to staging-next, since it's security sensitive.

staging-next has been merged in the meantime so no need to change the branch anymore.

@Mic92 I added those commits to this branch.
Let me know if this looks good or if this can be merged :-)

Success on aarch64-linux (full log)
Attempted: rustc
Partial log (click to expand)
/nix/store/62him3syh1wkcjjwi21gnxj15lzwv3g3-rustc-1.29.1

Timed out, unknown build status on x86_64-linux (full log)
Attempted: rustc
Partial log (click to expand)
make[3]: Entering directory '/build/rustc-1.29.1-src/build/x86_64-unknown-linux-gnu/llvm/build'
Scanning dependencies of target LLVMAArch64Disassembler
make[3]: Leaving directory '/build/rustc-1.29.1-src/build/x86_64-unknown-linux-gnu/llvm/build'
make[3]: Entering directory '/build/rustc-1.29.1-src/build/x86_64-unknown-linux-gnu/llvm/build'
[ 71%] Building CXX object lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o
[ 71%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMTargetTransformInfo.cpp.o
[ 71%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/MLxExpansionPass.cpp.o
[ 71%] Building CXX object lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86TargetMachine.cpp.o
building of '/nix/store/bg9j1jh39id3vmyal51mkh5nskdnwka9-rustc-1.29.1.drv' timed out after 1800 seconds
error: build of '/nix/store/bg9j1jh39id3vmyal51mkh5nskdnwka9-rustc-1.29.1.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: rustc
Partial log (click to expand)
cannot build derivation '/nix/store/l1sp2v620mgvmg4y2pgmrzg6ycr0ndsn-xmlto-0.0.28.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/nb3p1pc8kjn64i1hj6lf5xrn1kzbq9bk-opensp-1.5.2.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/lgvd6crk3gbw3h7n16lgf36cbgxwdgdn-swift-corefoundation.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/biqrvwkxlx0rrvyxjwb61rzi5d33mwh0-apple-framework-IOKit.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/cbwjdv23b2zh2vfgjzkg676z2n04cbrh-docbook2X-0.8.8.drv': 16 dependencies couldn't be built
cannot build derivation '/nix/store/n4sfjl84a64483fkbmfb6hwydmii1rvk-apple-framework-Security.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/06vry6q4fxcpc85zqfg3wwh1s46pcknq-git-2.19.0.drv': 29 dependencies couldn't be built
cannot build derivation '/nix/store/pib6d1l56gjj5ssp691p1p8nhdlsln46-rustc-bootstrap-1.28.0.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/mlwmqvjfpq5f5kpahj1l02andwpljixx-rustc-1.29.1.drv': 15 dependencies couldn't be built
error: build of '/nix/store/mlwmqvjfpq5f5kpahj1l02andwpljixx-rustc-1.29.1.drv' failed

@andir they can be actually squashed into one commit apart from that it looks good to me.

@Mic92 Done.

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: rustc
Partial log (click to expand)
cannot build derivation '/nix/store/l1sp2v620mgvmg4y2pgmrzg6ycr0ndsn-xmlto-0.0.28.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/nb3p1pc8kjn64i1hj6lf5xrn1kzbq9bk-opensp-1.5.2.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/lgvd6crk3gbw3h7n16lgf36cbgxwdgdn-swift-corefoundation.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/biqrvwkxlx0rrvyxjwb61rzi5d33mwh0-apple-framework-IOKit.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/cbwjdv23b2zh2vfgjzkg676z2n04cbrh-docbook2X-0.8.8.drv': 16 dependencies couldn't be built
cannot build derivation '/nix/store/n4sfjl84a64483fkbmfb6hwydmii1rvk-apple-framework-Security.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/06vry6q4fxcpc85zqfg3wwh1s46pcknq-git-2.19.0.drv': 29 dependencies couldn't be built
cannot build derivation '/nix/store/pib6d1l56gjj5ssp691p1p8nhdlsln46-rustc-bootstrap-1.28.0.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/mlwmqvjfpq5f5kpahj1l02andwpljixx-rustc-1.29.1.drv': 16 dependencies couldn't be built
error: build of '/nix/store/mlwmqvjfpq5f5kpahj1l02andwpljixx-rustc-1.29.1.drv' failed

Success on x86_64-linux (full log)
Attempted: rustc
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/rbpwrw2lm25avxzjmrhbmpnxk3lz51qf-rustc-1.29.1-man
gzipping man pages under /nix/store/rbpwrw2lm25avxzjmrhbmpnxk3lz51qf-rustc-1.29.1-man/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/rbpwrw2lm25avxzjmrhbmpnxk3lz51qf-rustc-1.29.1-man
checking for references to /build in /nix/store/rbpwrw2lm25avxzjmrhbmpnxk3lz51qf-rustc-1.29.1-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/2hj4dr36halfd1dn95nrmmpfcahxm6ka-rustc-1.29.1-doc
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/2hj4dr36halfd1dn95nrmmpfcahxm6ka-rustc-1.29.1-doc
checking for references to /build in /nix/store/2hj4dr36halfd1dn95nrmmpfcahxm6ka-rustc-1.29.1-doc...
/nix/store/sazlp6x75286c9lnw01qd5xsspdx125v-rustc-1.29.1

Success on aarch64-linux (full log)
Attempted: rustc
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/b136lnmbssxq0qbwxcznr7a63vyssqyd-rustc-1.29.1-man
gzipping man pages under /nix/store/b136lnmbssxq0qbwxcznr7a63vyssqyd-rustc-1.29.1-man/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/b136lnmbssxq0qbwxcznr7a63vyssqyd-rustc-1.29.1-man
checking for references to /build in /nix/store/b136lnmbssxq0qbwxcznr7a63vyssqyd-rustc-1.29.1-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/dbbbfxc7vhcnyhsjdjw1pxpf02hxfbaj-rustc-1.29.1-doc
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/dbbbfxc7vhcnyhsjdjw1pxpf02hxfbaj-rustc-1.29.1-doc
checking for references to /build in /nix/store/dbbbfxc7vhcnyhsjdjw1pxpf02hxfbaj-rustc-1.29.1-doc...
/nix/store/4nbhw0wz5fvxa2xszyb4x20wdq0qgpk6-rustc-1.29.1

@andir did you backport this to staging-18.09?


Cross-Site Scripting (XSS) vulnerability - CVE-2024-6484

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of a tag due to inadequate sanitization. This vulnerability could enable attackers to execute arbitrary JavaScript within the victim's browser.
Found a medium-level vulnerability issue in the Fortify scan for all versions below 5.3.3
References
https://github.com/advisories/GHSA-9mvj-f7w8-pvh2
Reduced test cases
vulnerability issue
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.3.3

Thanks for reporting an issue @mohan26
As mentioned in https://github.com/advisories/GHSA-9mvj-f7w8-pvh2 and https://www.herodevs.com/vulnerability-directory/cve-2024-6484, this CVE affects Bootstrap >=2.0.0 <=3.4.1.
Both these versions are EOL (End-Of Life) are won't be updated. It is recommended to upgrade your project to the latest version of Bootstrap.

@julien-deramond As I have mentioned in the description I have already using upgraded version - 5.3.3 , please recheck on this

@julien-deramond As I have mentioned in the description I have already using upgraded version - 5.3.3 , please recheck on this

Hello @julien-deramond,
Any update regarding this?
Best regards,
João Lola

Our security team is evaluating the impact on v5 based on the recent CVEs.
If there's an impact, we'll patch the v5. For now, v5 is considered as not impacted.
This specific CVE, as mentioned in its description is not related to v5. So I'm closing this issue.


[Code Addition Request]: Network Vulnerability Scanner

Have you completed your first issue?

[X] I have completed my first issue

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Latest Merged PR Link
https://github.com/UTSAVS26/PyVerse/issues/746#issuecomment-2430699109
Project Description
Building  a tool that scans networks for open ports, services, and potential vulnerabilities, similar to Nmap.
Key Features:

Port Scanning: Implement a basic TCP/UDP port scanner to identify open ports on a target machine.
Service Detection: After identifying open ports, detect what services (like HTTP, FTP, etc.) are running.
Banner Grabbing: Fetch service banners to find version information that may indicate vulnerabilities.

Tech Stack:

Python: Use Python’s socket module for port scanning and libraries like Scapy for packet crafting and sniffing.

Full Name
Jivan Jamdar
Participant Role
GSSOC

@UTSAVS26 assign this issue to me


Reaching the border with elytras

Hello,
When we reach the border while using elytras, we are teleported back to the ground.
On the other hand when we reach the border while flying in creative mode, the behaviour is different : We are teleported ~3 blocks back but on the same Y coordinates.
Could it be possible to have the same behaviour in elytras please ?

 While it sounds like a good idea on paper, not very good overall.

Oh, okay. Why would it stop the player from gliding ?
I'm assuming the plugin is teleporting players a few blocks back when I hit the border.
As a test, if I'm gliding on elytras and I use a /minecraft:tp command to teleport myself elsewhere but still in the air, I will still be gliding.

Mmmm, I still don't know man, I feel as if an anticheat will just kick a player for that.

I will elaborate onto why I think this is important (at least for me, but others can also experience this problem).
I have a world which is like a "Skyblock" world. There are islands floating around but it's mostly void. Players are exploring this world mainly using elytras.
The problem is, when they reach the border while using elytras they are teleported in x=0,y=60,z=0 which is inside a block so they die.
I understood that WorldBorder is trying to teleport them on ground. But as there no ground, the plugin is not handling it correctly. In the rare case when a player reaches the border with a floating island beneath him, he is teleported on this island.
Please explain to me the difference for an anticheat between WorldBorder teleporting you back on land (which can be far from where you were gliding) or just ~3 blocks back but still gliding on elytras as you were before.

Sorry for the late response, Was feeling a bit off, so I re-read what the main question was and the answer is pretty simple. Creative mode allows a Toggle Fly on/off, able to ACTUALLY FLY and stop whenever you want; While elytras is based on you actually not flying and toggling, but gliding. You can't stop in one spot while Gliding with elytras for long periods of time.
Since you can stay still in the air without moving in creative, ( also you are pretty much invincible, can't take damage ) the plugin counts the air blocks as a "safe spot" due to you not actually going to fall down, and that your FLYING is TOGGLED ON..
I hope what I said makes sense, it's kinda rough to understand but that's pretty much the answer I can come up with.

No worries for the late response we are not in a hurry.
It seems to me that you don't use elytras often. No you're not gonna fall down instantly. If you chose to be gliding with elytras then AIR is a safe spot to be teleported to because you were already in the air.
Conversely, ground could be an unsafe spot if there are mobs around that you chose to avoid using elytras.
But okay let's say that air is not safe. I think there is still a bug that I tried to explain above :
When I reach the border using elytras and there is no "safe ground" then the plugin is teleporting me in a wall and I die. I happens in a "Skyblock" world where it's mostly void or in the nether when there is lava beneath me.

As I had previously stated beforehand, elytras are not technically "flying", they are "Gliding". Flying being able to toggle on/off, go up/down and stay in one spot in the air, while gliding being (I guess toggleable) a constant movement, going only down.

What does this have to do with my last message ? Do you want me to open another issue now that we agreed that teleporting the player to the ground is a good behaviour ? In this new issue I will describe situations when the teleportation is not done correctly.

If it's a bug report, then this should have been made as a bug report to begin with. As far as I'm aware, if there is no safe spot, it will teleport the player to the world's spawn. I believe it counts 0/64/0 as the default coords, not really checked too much into that part of the code. As I have stated before, I am simply maintaining this project until further notice. Developers are free to push changes that could/would fix an issue and I can release a version with it.

If it's a bug report, then this should have been made as a bug report to begin with.

Before reporting the bug I wanted to discuss why is the player teleported to the ground while on elytras. Because if you had agreed that this was not a good behaviour and changed it, there would have been no bug to report.

As far as I'm aware, if there is no safe spot, it will teleport the player to the world's spawn.

You might be right, this position could be the spawn of the world. More precisely the spawn of the map if I play on this map in singleplayer for example.
But as I redefined the spawn using Multiverse a long time ago, I had no idea what this coordinate was.


i2d_ASN1_bio_stream is not documented on its ostensible man page

The list of documented functions at https://www.openssl.org/docs/man1.1.1/man3/ includes i2d_ASN1_bio_stream.  It is hyperlinked to https://www.openssl.org/docs/man1.1.1/man3/i2d_ASN1_bio_stream.html .  The latter page describes many i2d_ functions, including the _bio functions, but not the _bio_stream function, which has three unique parameters (in, flags, and it) not shared with the _bio forms:
int i2d_ASN1_bio_stream(BIO *out, ASN1_VALUE *val, BIO *in, int flags,
                        const ASN1_ITEM *it)

If this function is meant for public use it should be documented, and if not, removed from the API list.
I observe this in the public web page as well as the OpenSSL 1.1.1k sources (in doc/man3/d2i_X509.pod).

If this function is meant for public use it should be documented, and if not, removed from the API list.

I'm sure you didn't mean it that way, but that's a little harsh.  OpenSSL has long had a problem with its documentation and is working to fix it.  Care to help?

Sorry, I did not intend that to sound critical.  As the rest of my report is simply stating observations, the purpose of that sentence is to explicitly say what is wrong about those observations, as this is a bug report.  Also, I genuinely don't know if the _stream function is meant to be public.  How would you recommend I communicate this sort of thing in the future?
As for helping to document it, I'm willing to do that, but I'd need to figure out what it does first.  I've been studying the code (the function itself is not large, but it calls into a lot of other code, including the polymorphic function tables in it), but am still far from being able to say with confidence how it's meant to be used and what restrictions apply.

How would you recommend I communicate this sort of thing in the future?

Just ask the question.

this function seems to be used to create an output out  (a file probably)  , while serializing val  into it  .
val could be either a PCKS7 or CMS (enveloping ?)  signature
It will append the content of in when flags bit SMIME_STREAM is set.
Else it ignores the in parameter , and just create the output.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Jinja seems to be taking longer than it should be

This can be seen when generating code in the python optimizer (though I imagine it can be seen just about anywhere Codegen objects are used to generate functions).
Perhaps something can be done to speed it up.
Here is a profile of symforce_py_optimizer_test.py, modified to generate 1000 distinct priors:

This has been sped up. Also, now only a tiny fraction of the time is spent in jinja functions (and instead almost all the time is spent in codegen functions):


Update reference-claims-mapping-policy-type.md

update JWT restricted claim sets per discrepancy between documents and our source codes. https://identitydivision.visualstudio.com/Engineering/_queries/edit/2296167/?triage=true

@cfzhang6688
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

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

I'm closing this PR because the CLA has not been signed.


Question: Build on stable rust?

Will riker build on stable rust in the near future?
What hurdles are there for building on stable?

once async/await get stabilized (which is very soon by the way near Aug this year). also we are using futures v0.3 which i think is not stable yet for the same reason.


Support for HTMX OOB swaps

I like the direction of this project. To use HTMX out-of-band swaps with Thymeleaf, I need the ability to return multiple components:

my main component

A separate component. A total perhaps

Is this supportable with your library? Any tips on how that might be implemented if a PR were desired?

Hey @checketts thanks for the suggestion!
You are happily invited to submit a PR.
A bit of context:
Currently there are two different ways the viewcomponents are rendered. The one way where you render a nested component shouldn't be a problem because you could just insert multiple components next to each other.
`

`
The one that would need some investment to implement is the way where you return a ViewContext from your Controller Method -> the root component.
The ViewComponentMethodReturnValueHandler is responsible for this. It checks if a controller method returns a viewcontext and then puts that into a ModelAndViewContainer and returns that -> then the standard thymeleaf renderer takes over.
To implement multiple component returns we would need to create a new MethodReturnValueHandler that looks for a list of ViewComponents and then renders them directly into a ResponseEntity body.
The code from the ViewComponentProcessor could be used. Part of it should be extracted that they render the exact same way.
I'll look at it later this weekend!

I got it working! I'll release a new version tomorrow!

That is great! I look forward to trying it out!

Hey @checketts I just released version v0.4.2 you can grab from jitpack.
I updated the docs and published an example


[instrumentation] Uprade to the latest OTEL

Packages impacted by this PR

@azure/opentelemetry-instrumentation-azure-sdk

Issues associated with this PR
Describe the problem that is addressed by this PR
Updates to latest OTEL
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

/check-enforcer reset

/check-enforcer evaluate

@microsoft-github-policy-service rerun

/check-enforcer reset

/check-enforcer evaluate


Roll Flutter Engine from 6f941c961b05 to ece261308977 (17 revisions)

https://github.com/flutter/engine/compare/6f941c961b05...ece261308977
2024-11-22<EMAIL_ADDRESS>[Impeller] delete Impeller sim opt out. (flutter/engine#56706)
2024-11-22<EMAIL_ADDRESS>[Impeller] Ensure that SnapshotControllerImpeller has a rendering context before creating the snapshot (flutter/engine#56743)
2024-11-22<EMAIL_ADDRESS>[DisplayList] migrate DlColorSource objects to Impeller geometry (flutter/engine#56735)
2024-11-22<EMAIL_ADDRESS>[Impeller] libImpeller: Tinker on the README. (flutter/engine#56761)
2024-11-22<EMAIL_ADDRESS>[Impeller] dont create temp vec for discard. (flutter/engine#56759)
2024-11-22<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from zhFzwYCH-N_wasTnM... to D5CBHuB2c-v3Zai-c... (flutter/engine#56757)
2024-11-22<EMAIL_ADDRESS>Roll Dart SDK from 141291fd570d to 8b65a7a628e2 (1 revision) (flutter/engine#56755)
2024-11-22<EMAIL_ADDRESS>[Impeller] cache and reuse openGL framebuffer attachments. (flutter/engine#56746)
2024-11-22<EMAIL_ADDRESS>Roll Skia from 700e685861c8 to e7caf38140ce (25 revisions) (flutter/engine#56756)
2024-11-22<EMAIL_ADDRESS>Roll Dart SDK from c1106f7e4cde to 141291fd570d (1 revision) (flutter/engine#56748)
2024-11-22<EMAIL_ADDRESS>[engine] more consistently flush dart event loop, run vsync callback immediately (flutter/engine#56738)
2024-11-22<EMAIL_ADDRESS>Extract backend-specific code in ShellTestPlatformView (flutter/engine#56722)
2024-11-22<EMAIL_ADDRESS>Eliminate ShellTestPlatformView::BackendType::kDefaultBackendType (flutter/engine#56744)
2024-11-22<EMAIL_ADDRESS>Roll Skia from 2614590b4f32 to 700e685861c8 (1 revision) (flutter/engine#56725)
2024-11-22<EMAIL_ADDRESS>Roll Dart SDK from b36e4d731d67 to c1106f7e4cde (12 revisions) (flutter/engine#56742)
2024-11-22<EMAIL_ADDRESS>[Impeller] libImpeller: A C++ wrapper to the Impeller API. (flutter/engine#56682)
2024-11-21<EMAIL_ADDRESS>[Impeller] Run simulator tests with Impeller enabled. (flutter/engine#56740)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from zhFzwYCH-N_w to D5CBHuB2c-v3
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

AutoRoller is stopped; closing the active roll.


fix(cursor): cursor.count not respecting parent readPreference

Fix wrong placement and typo in options argument in
cursor.s.topology.command, and test that specified readPreference
is passed in to that call.
Fixes NODE-1511

I think this is worth backporting to the 3.0 branch. @mbroadst @kvwalker throughts?

@daprahamian agreed

@daprahamian agreed. Furthermore, the bug encountered with using ReadPreference.SECONDARY vs ReadPreference.secondary should be handled by the use of resolveReadPreference... I think we should investigate this further.

I made a ticket to track the ReadPreference in MongoClients ctor here


Add information gathering options to registry request form.

On the request form, where teams enter information about their project, gather some additional information about what services the project uses. This information will be used in reporting to better understand what teams need and what features they use. The first team to use this information will be the shared components team.

Waiting on J-P to give is a list of services / things that we should include in the web form.

Duplicate of #76


Remove login/logout service from Manifest.

Auth isn't in a place yet where we can support it.
Closes #576

Github's having issues this morning, but your comment's resolved when it updates.

Coverage decreased (-0.04%) to 99.964% when pulling 0c1ad3ba90b32d24fbe5d40d8a60c638e7e564f1 on remove_hsh into 8b4fb27eeb7a8d84d7f8b4076ee72102df0dc0ca on master.

Coverage decreased (-0.04%) to 99.964% when pulling 0c1ad3ba90b32d24fbe5d40d8a60c638e7e564f1 on remove_hsh into 8b4fb27eeb7a8d84d7f8b4076ee72102df0dc0ca on master.


Barcode face

Barcode clockwatchface
A scannable EAN-8 compatible clockwatchface for your Bangle 2
The format of the bars are
||HHmm||MMwc||

Left section: HHmm

H: Hours
m: Minutes

Right section: MM9c

M: Day of month
w: Day of week
c: Calculated EAN-8 digit checksum

Apart from that

The upper left section displays total number of steps per day
The upper right section displays total number of steps from last boot ("stepuptime")
The face updates every 5 minutes or on demand by pressing the hardware button

This clockwathface is aware of theme choice, so it will adapt to Light/Dark themes.

That's a great idea - thanks!


Better specify PowerFlowData parametric type aliases

This:

is

deeply unsettling and
problematic for multiple dispatch.

I'm not fully convinced that these pseudo-subtypes should be based on the types of the matrices they contain; that feels like an implementation detail, even though it's a pretty fundamental one. One can at least in principle imagine a pair of PowerFlowDatas with the same types of matrices except you want to solve them differently. Maybe the PowerFlowData contains the PowerFlowEvaluationModel it was constructed with, is parameterized on that, and that's what the aliases key onto? Or maybe one is required to pass a PowerFlowEvaluationModel to solve_powerflow! along with the PowerFlowData? Guess this overlaps with https://github.com/NREL-Sienna/PowerFlows.jl/issues/38.

For now I'll just strictly specify vPTDFPowerFlowData as has been done for all the other aliases. I still think this might warrant rethinking more deeply later.


Refactor

This is a proposed refactoring with some new majour feature and some changes

do not rely only on conda, support mamba, virtualenvs and custom inizialization scripts
use click actions, now they are defined as start / kill / list
ability to kill all the remote servers

everything is documented in the new README

@Olllom ?

Thanks!


[Python] allow pydantic < 3.0 in deps

Please, update pydantic version pin in pyproject.toml to < 3.0 instead <2.5.0. Pydantic already has 2.5.2 tag.
I start big migration in my company from Pydantic 1.x to 2.5.2 and it's blocked;(

@FyZzyss I'm a python noob, will this work: https://github.com/flipt-io/flipt-client-sdks/pull/36/files ?

@markphelps Wow! Thank you for such quick response.
Yes, this will work

@markphelps Will you be create a new tag for https://github.com/flipt-io/flipt-python with updated deps? For quick installation from pypi


material-ui bug?

use material-ui
    7:1   warning  Expected an assignment or function call and instead saw an expression  no-unused-expressions
    8:21  warning  Expected '!==' and instead saw '!='                                    eqeqeq
    9:26  warning  Expected '===' and instead saw '=='                                    eqeqeq
    9:43  error    'define' is not defined                                                no-undef
    9:55  error    'define' is not defined                                                no-undef
   41:9   warning  'samsungBrowser' is assigned a value but never used                    no-unused-vars
  284:26  warning  Expected '===' and instead saw '=='                                    eqeqeq
  284:61  warning  Expected '===' and instead saw '=='                                    eqeqeq
  366:20  warning  Expected '===' and instead saw '=='                                    eqeqeq
  367:38  warning  Expected '===' and instead saw '=='                                    eqeqeq
  373:20  warning  Expected '===' and instead saw '=='                                    eqeqeq
  374:20  warning  Expected '===' and instead saw '=='                                    eqeqeq
  479:7   warning  Assignment can be replaced with operator assignment                    operator-assignment

✖ 13 problems (2 errors, 11 warnings)

Sorry, but I don’t understand what exactly you are reporting in this issue.
We only run ESLint on the user code in src. Are these warnings in your code, or did you somehow run ESLint on the material-ui library? Why are you saying this is related to material-ui at all?
Have you tried fixing these warnings? What is the file they are located in? Can you show its source?

Closing because you didn’t fill the template, and the issue description is very vague. If those are lint errors in your code, please fix them. If you think there is a bug in CRA, please file another issue and fill the template. Thanks!


[axe-core warning] - Ensures aria-hidden elements do not contain focusable elements

Feature Request
When the abstract modal is open, we set aria-hidden on the root element to prevent VoiceOver on iOS from shifting the virtual cursor outside of the modal.
However, we don't currently do anything to disable children within the aria-hidden="true" element.
This PR should fix part of the issue once #608 is merged.
We'll have to add the inert polyfill to terra overlay as it uses similar logic using aria-hidden.
Description

WDIO Axe Error Report
 Notification-dialog with No Message is accessible:
expected no accessibility violations but got:
        {
  "description": "Ensures aria-hidden elements do not contain focusable elements",
  "help": "ARIA hidden element must not contain focusable elements",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
  "id": "aria-hidden-focus",
  "impact": "serious",
  "nodes": [
    {
      "all": [
        {
          "data": null,
          "id": "focusable-disabled",
          "impact": "serious",
          "message": "Focusable content should be disabled or be removed from the DOM",
          "relatedNodes": [
            {
              "html": "<button id=\"trigger-notification-dialog\" class=\"Button-module__button___3afIE Button-module__neutral___ZyOh8\" type=\"button\" aria-disabled=\"false\">Trigger NotificationDialog</button>",
              "target": [
                "#trigger-notification-dialog"
              ]
            }
          ]
        }
      ],
      "any": [],
      "failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
      "html": "
",
      "impact": "serious",
      "none": [],
      "target": [
        "#root"
      ]
    }
  ],
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412"
  ]
}
running chrome
AssertionError: expected no accessibility violations but got:
        {
  "description": "Ensures aria-hidden elements do not contain focusable elements",
  "help": "ARIA hidden element must not contain focusable elements",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
  "id": "aria-hidden-focus",
  "impact": "serious",
  "nodes": [
    {
      "all": [
        {
          "data": null,
          "id": "focusable-disabled",
          "impact": "serious",
          "message": "Focusable content should be disabled or be removed from the DOM",
          "relatedNodes": [
            {
              "html": "<button id=\"trigger-notification-dialog\" class=\"Button-module__button___3afIE Button-module__neutral___ZyOh8\" type=\"button\" aria-disabled=\"false\">Trigger NotificationDialog</button>",
              "target": [
                "#trigger-notification-dialog"
              ]
            }
          ]
        }
      ],
      "any": [],
      "failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
      "html": "
",
      "impact": "serious",
      "none": [],
      "target": [
        "#root"
      ]
    }
  ],
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412"
  ]
}
    at Context.<anonymous> (/Users/bj031910/repos/terra-framework/node_modules/terra-toolkit/lib/wdio/services/TerraCommands/accessiblity.js:13:54)
    at new Promise (<anonymous>)
    at new F (/Users/bj031910/repos/terra-framework/node_modules/core-js/library/modules/_export.js:36:28)

WDIO Axe Error Report
```
1) ApplicationLayout Toggles menu when small is accessible:
expected no accessibility violations but got:
        {
  "description": "Ensures aria-hidden elements do not contain focusable elements",
  "help": "ARIA hidden element must not contain focusable elements",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
  "id": "aria-hidden-focus",
  "impact": "serious",
  "nodes": [
    {
      "all": [
        {
          "data": null,
          "id": "focusable-disabled",
          "impact": "serious",
          "message": "Focusable content should be disabled or be removed from the DOM",
          "relatedNodes": [
            {
              "html": "",
              "target": [
                ".ApplicationHeader-module__toggle-button___2GANm"
              ]
            },
            {
              "html": "Skip to Content",
              "target": [
                ".ApplicationHeaderLayout-module__skip-content___1vGmQ"
              ]
            }
          ]
        }
      ],
      "any": [],
      "failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
      "html": "",
      "impact": "serious",
      "none": [],
      "target": [
        "main"
      ]
    }
  ],
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412"
  ]
}
running chrome
AssertionError: expected no accessibility violations but got:
        {
  "description": "Ensures aria-hidden elements do not contain focusable elements",
  "help": "ARIA hidden element must not contain focusable elements",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
  "id": "aria-hidden-focus",
  "impact": "serious",
  "nodes": [
    {
      "all": [
        {
          "data": null,
          "id": "focusable-disabled",
          "impact": "serious",
          "message": "Focusable content should be disabled or be removed from the DOM",
          "relatedNodes": [
            {
              "html": "",
              "target": [
                ".ApplicationHeader-module__toggle-button___2GANm"
              ]
            },
            {
              "html": "Skip to Content",
              "target": [
                ".ApplicationHeaderLayout-module__skip-content___1vGmQ"
              ]
            }
          ]
        }
      ],
      "any": [],
      "failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
      "html": "",
      "impact": "serious",
      "none": [],
      "target": [
        "main"
      ]
    }
  ],
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412"
  ]
}
    at Context. (/Users/bj031910/repos/terra-framework/node_modules/terra-toolkit/lib/wdio/services/TerraCommands/accessiblity.js:13:54)
    at new Promise ()
    at new F (/Users/bj031910/repos/terra-framework/node_modules/core-js/library/modules/_export.js:36:28)

ApplicationLayout Renders primary nav menu when small is accessible:
expected no accessibility violations but got:
{
"description": "Ensures aria-hidden elements do not contain focusable elements",
"help": "ARIA hidden element must not contain focusable elements",
"helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
"id": "aria-hidden-focus",
"impact": "serious",
"nodes": [
{
"all": [
{
"data": null,
"id": "focusable-disabled",
"impact": "serious",
"message": "Focusable content should be disabled or be removed from the DOM",
"relatedNodes": [
{
"html": "<button type="button" class="ApplicationHeader-module__toggle-button___2GANm" aria-label="Toggle Menu" data-application-header-toggle="true">",
"target": [
".ApplicationHeader-module__toggle-button___2GANm"
]
},
{
"html": "<button type="button" class="ApplicationHeaderLayout-module__skip-content___1vGmQ">Skip to Content",
"target": [
".ApplicationHeaderLayout-module__skip-content___1vGmQ"
]
}
]
}
],
"any": [],
"failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
"html": "",
"impact": "serious",
"none": [],
"target": [
"main"
]
}
],
"tags": [
"cat.name-role-value",
"wcag2a",
"wcag412"
]
}
running chrome
AssertionError: expected no accessibility violations but got:
{
"description": "Ensures aria-hidden elements do not contain focusable elements",
"help": "ARIA hidden element must not contain focusable elements",
"helpUrl": "https://dequeuniversity.com/rules/axe/3.2/aria-hidden-focus?application=axeAPI",
"id": "aria-hidden-focus",
"impact": "serious",
"nodes": [
{
"all": [
{
"data": null,
"id": "focusable-disabled",
"impact": "serious",
"message": "Focusable content should be disabled or be removed from the DOM",
"relatedNodes": [
{
"html": "<button type="button" class="ApplicationHeader-module__toggle-button___2GANm" aria-label="Toggle Menu" data-application-header-toggle="true">",
"target": [
".ApplicationHeader-module__toggle-button___2GANm"
]
},
{
"html": "<button type="button" class="ApplicationHeaderLayout-module__skip-content___1vGmQ">Skip to Content",
"target": [
".ApplicationHeaderLayout-module__skip-content___1vGmQ"
]
}
]
}
],
"any": [],
"failureSummary": "Fix all of the following:\n  Focusable content should be disabled or be removed from the DOM",
"html": "",
"impact": "serious",
"none": [],
"target": [
"main"
]
}
],
"tags": [
"cat.name-role-value",
"wcag2a",
"wcag412"
]
}
at Context. (/Users/bj031910/repos/terra-framework/node_modules/terra-toolkit/lib/wdio/services/TerraCommands/accessiblity.js:13:54)
at new Promise ()
at new F (/Users/bj031910/repos/terra-framework/node_modules/core-js/library/modules/_export.js:36:28)

This has been resolved in a prior PR and is no longer being reported when running axe-core with the WCAG 2.1 AA ruleset.


What about a ColorField that implements a color scale

that is a ColorField that assigns a color to a scalar value as is often used when visualizing simulation results:
 (https://forum.ansys.com/discussion/3553/i-made-a-repository-for-color-maps-for-cfd-post-and-fluent)
https://github.com/3MFConsortium/spec_volumetric/tree/develop_070
@asartorellihxgn : please add/change use case for you

Color fields can often be used for display information from scalar simulation results fields on 3d printed geometry. With the current implementation of color field, if one were coming from a simulation tool then they would be locked into a particular color map. This could present a few issue when physically printing parts:

If one were to export a part containing a color field generated from a  simulation field where peak stress is say 1MPa and this corresponds to red on the color map, and then later exports another part that will be used for comparison where peak stress is 2MPa and this also corresponds to red on it's color map. Then one is not able to readily discern the difference between the two. By storing the data of the underlying scalar fields and converting to a color field at a later time, they could use a matching color map where 2MPa is red and 1 MPa is green for example.
There exist a large variety of color maps to convert from scalar fields to color fields often products from even the same company may use a different color map. It could be useful to end consumers to be able to use a matching color map regardless of where the original data is coming from.


Add UDP middlewares support

What does this PR do?

Adds UDP middlewares support
Adds UDP IPWhitelist middleware
Updates the API to serve UDP middlewares info

Motivation
Fixes #8463
More

[x] Added/updated tests
[x] Added/updated documentation
[ ] Added/updated webui

Additional Notes

This PR is extremely useful, but also very important. Can we please have some very close introspection on the code (not just the tests) from core maintainers? This PR is from a random user in China with no previous commits. It's quite a large refactor of UDP packet handling. It would be ideal for core maintainers to write this code themselves

Traefik accepts pull requests and issues from all over the globe regardless of national origin.
All pull requests undergo the same code review.
Requesting that other community members have a different experience with Traefik based on national origin goes against our Code of Conduct, which you can read here: https://github.com/traefik/traefik/blob/master/CODE_OF_CONDUCT.md (edited)

Just a follow up on this PR, we have been focusing somewhere else lately but we still want to bring middleware support for UDP, so reviewing and iterating on this PR will be prioritized after we release the next minor in the next two weeks, thanks for the patience.

unfortunately we couldn't get to this PR in time so we're updating its target release to the next major version, which should have a beta until end of Q4

unfortunately we couldn't get to this PR in time so we're updating its target release to the next major version, which should have a beta until end of Q4

Thank you for following up. It's been a while since the last commit, and I'll get around to rechecking this PR before the reviewing.

What is missing to get this into v3?  Anything I can do to help?

Hello @ichxxx and @Olen , we're finally getting back to this and while discussing it internally we had a hard time to get a real use case for the included middleware.
I can definitely see benefits on having the middleware mechanism ready for UDP as well, specially if we manage to add plugins support outside HTTP, so anyone could write custom code. But before that happens we need a good justification to add this, in the form of a specific middleware that's required in a real use case.
Can you help us on by providing what was the use case that motivated you? (to contribute and / or require this contribution)
The more specific around the tooling, environment and use case the better.

My use case is using Traefik as a simple "firewall" (I know that is not what it is made for, but it has some advantages), as I am dockerizing basically everything.
So the middlewares that are most important to me are geoblocking and whitelisting so I can allow access to certain udp services from a limited number of sources.
By using traefik in front of the services, I don't need to expose the services directly on the host, and I can keep a simple, common config in docker-compose.yaml no matter what kind of service we are talking about.

I use Traefik to expose some udp services, such as Filebeat. But I don't want these services to be completely exposed except the ip I trust. In this case, ip allowlist are required. Of course, I could write the ip allowlist logic in each of these udp services, but it is a bit inelegant, and I think it should be done at the gateway layer.

Same as @ichxxx , I expose multiple UDP services via traefik. Including video game servers, vpn servers, and dns servers. Sometimes I need to configure a backend for a particular CIDR range and I agree that should be done at the gateway layer

@ddtmachado, same use-case as others have mentioned: since I'm using docker for various services that use TCP and UDP, having Traefik+plugins as a type of firewall would be very helpful and convenient!

Oh this would be so great! I am trying to write a TCP and UDP middleware right now and just found out UDP routes had no middleware support :)

Just to add a real world example that is relevant only for UDP:
We are providing a RADIUS service (using Dockerized FreeRADIUS). State is only stored in an SQL database (which can be a cloud-based DBaaS or a centralized SQL cluster/Galera) while the actual RADIUS servers should be scaled horizontally as long as a proxy provides an entrypoint for the IP endpoint.
For security reasons, only specific Access Point IP ranges should be able to send RADIUS requests to the RADIUS server which means that a IPWhiteList middleware is needed.
This is a clear cut case for Traefik as the dynamic proxy entrypoint provider with IP white listing firewalling middleware.

Hi! Is there an expected version/date when this will be merged? I'd love to use UDP middlewares, as I'm currenty using this awesome middleware to shutdown unused services. However, I'd love to use UPNP without having to first wake up the service using HTTP. Hopefully this adds to potential usecases that you have been looking for.
Cheers!

This would be really great if you are still looking at this! Lots of use cases on our side for our network/dns services.

Can this be priortized? At least for feature parity? Is there a reason this was dropped?

Hello,
Sorry for the delay, but we were focused on releasing Traefik v3.0, and UDP middleware was not part of the roadmap.
We are still interested in this feature, but to be able to review it the conflicts have to be fixed.
@ichxxx could you please fix the conflicts? (rebase it on the master branch)

Hello,
Sorry for the delay, but we were focused on releasing Traefik v3.0, and UDP middleware was not part of the roadmap.
We are still interested in this feature, but to be able to review it the conflicts have to be fixed.
@ichxxx could you please fix the conflicts? (rebase it on the master branch)

Okay, I will fix the conflict when I have time.

Hey @ichxxx,

Okay, I will fix the conflict when I have time.

Are you still interested in moving forward on this PR?
As @kevinpollet said, even if we are still interested in this feature, this PR was opened a long time ago, and because we were focused on other features, we have frozen it and it's now outdated with a lot of changes to bring before being in a reviewable status.
If the work seems too huge for you we propose to close this PR and allow you or another contributor to open a new one to tackle this topic.
We keep it open while waiting for your feedback, and once again please apologize again for the long time with no action on this PR.

Hello @ichxxx,
Thank you for your feedback.
As I said previously, we are still interested in this feature, if you or another contributor want to move forward on this PR or open a new one on this topic, please let us know, and we will work with you to ensure you have all the information needed.


Telecon, October 22nd, 12:30 PM PST/3:30 PM EST

Our next call will take place on October 22nd at 12:30 PM PST/3:30 PM EST.
The link for the call is: https://washington.zoom.us/j/577460042

@mattcieslak can you join?

Would 4pm EST work?

That would work for me. In the worst case, join us midway through.
On Sat, Oct 19, 2019 at 5:08 AM Matt Cieslak<EMAIL_ADDRESS>wrote:

Would 4pm EST work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nipreps/dmriprep/issues/23?email_source=notifications&email_token=AAA46NVI5ASJJ7KFWNY4HA3QPL2E3A5CNFSM4I6WS2T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBXN7YY#issuecomment-544137187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA46NUPWOL34FNKL55Q66DQPL2E3ANCNFSM4I6WS2TQ
.

Is this still on?

Yes! Since no one else weighed in about moving this, let's keep it at 12:30
PM PT tomorrow. If you can only join at 1 PM (4 PM ET) that's fine and we
can spend a couple of minutes towards the end scheduling the next call for
a time that is convenient for you as well.
On Mon, Oct 21, 2019 at 1:00 PM Matt Cieslak<EMAIL_ADDRESS>wrote:

Is this still on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nipreps/dmriprep/issues/23?email_source=notifications&email_token=AAA46NQ6K4ZW6ITZ757COSTQPYC6FA5CNFSM4I6WS2T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB3TEFY#issuecomment-544682519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA46NWJRQGC7VDOIUO27LDQPYC6FANCNFSM4I6WS2TQ
.

I will be there

@arokem please post an issue with the next one :)


TestBrokerDeletedRecreated deletes the broker only

Using DeleteResources isn't a good idea since that function deletes
some internal resources like RBAC (for eventshub), etc
Fixes #1510

/cherry-pick release-1.1

/cherry-pick release-1.0

/cc @aliok @devguyio @matzew

/test pull-knative-sandbox-eventing-kafka-broker-upgrade-tests

/cherry-pick release-1.2

/retest

/retest

EOF error
/retest


fix: .ident hover in patterns

This is the result of many hours of debugging. When you use | .succ x => in a pattern, it was not giving the hover for constant Nat.succ, only the whole term Nat.succ x. If you write | Nat.succ x => however you do get the hover for the constant. The reason is because the termInfo for Nat.succ is added during collectPatternVars, but this is too early for dotted identifiers and they are only resolved once we enter the pattern. But once isPattern is true, we discard generated termInfos and replace them with a patternRef expr annotation.
Normally that would be okay because these annotations are later unpacked after the dependent match eliminator has done its job, but it turns out that for the constructor head itself it will clobber patternRef annotations. Plus, even if it did preserve them we aren't really interested in the post-match-elimination expression here, we want to record the data early like is done for plain identifiers.
The solution is simple: override the isPattern suppression for this particular termInfo, since we want it to act like it was done before we entered the pattern.

I want to review this PR before merging.
I am assigning myself as a reviewer.

Thanks for the changes. I will merge as soon as the conflicts above have been addressed.


stats: Resolve decRefCount()/set-cleanup race and increase refcount rep from 16-bits to 32-bits

Description:
Turns out there was a real race between the stats embedded ref-counts and the sets held in the allocator. You could race the destruction of a stat after a ref-count decrements to zero against the cleanup of the stat from the table.
The cleanest solution is to hold the allocator's lock while decrementing the ref-count, so that we can remove the stat from the table before releasing the lock.
I don't expect this to contend often, because usually there are not a large number of threads simultaneously deleting stats scopes (xDS) and calling Allocator::counters() and Allocator::gauges() (admin mostly). However it can happen, and thus we have a race that doesn't happen that much.
During investigation, I did follow what was almost certainly a red herring, which was a 64k limit on ref-count size. Including the fix for that here too as it is possible to exceed it in principle (a test to do so was easy), and we can at least put out warnings when the counts go high, and not crash. There's no cost to allowing 32 bits for the ref-count, as there was padding available for use. This also prints a warning every time the use-count reaches a multiple of 10k so we can get more hints as to which stats might have a lot of uses.
Risk Level: low
Testing: //test/common/stats:thread_local_store_test (especially the new one).
Docs Changes: n/a
Release Notes: n/a
Fixes: #9448

hold off on review; the latest version of the test found another race.

IDK what's up with CI, but I think this PR is correct including format, and is IMO ready for review.

/retest

/azp run

/azp run envoy-macos

Thanks Matt -- great comments on this. Waiting for CI and the 1000-iteration run now; the one on thread_local_store_test takes a while; the allocator_impl one finished very fast.

/azp run envoy-linux


[Enhancement] Disable Dead Channels

Hi,
Currently the program detects dead links already and displays an "Availability" percentage for each playlist. I think that such data should also be visible in the log file meaning that each dead URL should be listed in the log.
Further to that, what if there was an option in the "Settings" menu to disable dead channels on the fly when the playlist is checked?  Obviously such check would also re-enable the channel if it is available again upon recheck.
I think the majority would prefer not seeing a channel rather than visible but not working.
I can create the above behaviour using Python and modifying the JSON file to disable the channels, but an integrated feature would make this awesome project even better.
Thanks,
Nic

The Availability column refers to the M3U / XMLTV file, not to the individual streams in the M3U.
Each M3U / XMLTV file is cached so that the latest version of the file is always available. If a server is currently down, the version from the cache is used. That is also in the log.
In order to recognize dead links, all streaming URLs from the M3U would have to be queried regularly, that would be several thousand requests a day. I can imagine that some providers would not like that.
Even if this function were implemented, it would not work with Plex. Channels that are deactivated in xTeVe are also deactivated in Plex. Plex does not automatically activate any channels if they are active again in xTeVe. Each channel would have to be activated manually in Plex.

8 months ago I tried to clean things up with IPTV by tweaking things but at the end of the day when I thought I made progress, it just wasn't much better. I started playing around with connecting 2+ IPTV providers and several epg providers and I am close to having a noticeably better experience.  Guides are actually easy to deal with (just bulky), it's all about having more than one source of IPTV. This can be difficult to find because sometimes it's hard to tell who the source provider is. Many IPTV providers in one way or another use the same source and there are far fewer sources than providers, which include resellers. By keeping an up to date mapping of your provider's channel lists with your lineup, when a channel is called for they can be tested for basic availability. The first one that passes the test is used. A very large quantity of streams for each channel can be made available as long as one can be selected and used before plex times out. A small caveat of this, weather it is a simple php get_headers, an ffprobe command or a vlc connect will momentary require a +1 stream which can affect the playback of any currently active streams and make parallel testing of streams very difficult to manage. If the resources are available, a local streaming server can be set up to provide an offline video url to use in the event zero streams are available. This is where I am at in the testing phase.
This can make the issue of down channel management a non-issue and channel customization easier. So the idea of testing the streams is good, it just needs to be applied correctly.

Thanks @xteve-project for the clarification of the availability field for playlists and thanks to @GroupMaster for the in dept explanation for a way forward, will indeed follow similar steps :)


Error downloading portal via CLI

Hi,
I seem to get the same error regardless of my configuration when attempting to download a portal on an M1 Macbook Air:

I am authenticated via an app registration that is connected to the portal as an Application User.
Any suggestions would be appreciated.
Thank you.

Sorry about the late response. The issue was reported on 18th June, after the latest release, Is this issue still happening?

@harisrovca your use-case, using an appID/SPN/AppUser to authenticate is generally supported by pac CLI, but afaik, the paportal API endpoints do not support AppId/SPN authentication yet.
@ameyaapte1 can you pls confirm?
@JadyVelrada does this still repro with current pac CLI 1.9.9 that ships with the latest VS Code extension? Our expectation is, that was fixed/addressed

Yes the paportal API doesn't support AppId/SPN authentication but the pac cli supports it (Dataverse authentication)

Closing this issue for inactivity, please feel free to reopen if you are still facing difficulties


[SHARK_INFERENCE] Add ESRGAN model test file

-- This commit adds ESRGAN model test file to SHARK_INFERENCE.
TODO:
-- Add a README.md. (Done)
Signed-off-by: Abhishek Varma<EMAIL_ADDRESS>

Have added this draft PR for the ESRGAN model :-
Will be working on the TODO added in the PR summary.

Adding a script was an overkill so created a concise README instead.

@powderluv @pashu123 @Shukla-Gaurav @vivekkhandelwal1 @PhaneeshB
This PR is ready for review. Can someone review this and let me know the changes that'll be warranted as part of this PR?
(I'll add the credits to the original repository from which this model was captured)

CI action seems to have unrelated error - @pashu123 @Shukla-Gaurav @PhaneeshB @vivekkhandelwal1  @powderluv
ImportError while importing test module '/data/anush/actions-runner/_work/SHARK/SHARK/tank/test_models.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/data/anush/hostedtoolcache/Python/3.10.5/x64/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tank/test_models.py:13: in <module>
    from shark.shark_inference import SharkInference
shark/shark_inference.py:12: in <module>
    from shark.iree_utils.compile_utils import (
shark/iree_utils/compile_utils.py:14: in <module>
    import iree.runtime as ireert
E   ModuleNotFoundError: No module named 'iree.runtime'


Bundled software versions as a potential indicator of new firmware compatibility?

Hey @Effix .
I have some news. I've received quite a few badges from different suppliers now (via eBay and AliExpress) and some of them have clear external differences. I've also received quite a few different loader programs for Windows too, and have discovered the merits and limits of most of them.
Aside from the ability to display half-tones that your firmware UNIQUELY unlocks, I've been able to get good results out of Mini LED Display v9.17, v9.92 and to a lesser extent, v10.2. I've overcome the apparent (but falsely so) 8-frame limitation by learning how the software works. While a little counter intuitive, I can now program plenty of screen time. I'm yet to find the storage limit of any of the badges I've received.
There was one anomaly among the various software received. "HD Smart" is quite a different program, that works with art in 11x11 pixel blocks. These include loading animated .gif files (rather than manually loading a series of .bmp files or similar), which is a big plus.
I wanted to ask you what software was bundled with your b1236 and b1248 badges? I suspect that could be a rough indicator of what components are inside the chassis. Version numbers of the compatible supplied software would be good to know.
I'd prefer not to open up too many more of the badges I've received, as I'd like to resell some of them as artworks to recover some of the costs sunk into this project already.

Do you recall whether the software title was "Mini LED Display Vx" or similar? I have a program here called "LED Mini Board - Badge English V5" which might be a match? It's very limiting, and wouldn't allow me to animate full screen 1-bit images the way I can with Mini LED Display V9.17 or upwards. I think I found that title by scrounging online... I don't believe I have any hardware compatible with "LED Mini Board".

I believe it was the Mini Board one - it was very limited. Like 6 messages and only static images.

Does this look like the program that came with your badges, @Effix ?

Yeah, that looks familiar.
I wouldn't necessarily assume that a badge shipped with that software is guaranteed to be compatible. Any hardware revision that implements the same protocol would work.

Yeah, I figured it could be a clue that might suggest compatibility, but wouldn't be a given.
The above program was the obvious candidate following your description of the software that was bundled with your badges.
The more useful software (Mini LED 9.17+) has 8 universal slots rather than this 6/2 configuration, each of which can be used to hold a string of text, one long (wide) image, or a sequence/set of images (Mini LED 9.92+ only). By choosing "Animation" as the effect for any of these slots, a new frame is assumed every 48 or 36 pixels when the badge plays back any image data.

I have some news. I've received quite a few badges from different suppliers now (via eBay and AliExpress) and some of them have clear external differences. I've also received quite a few different loader programs for Windows too, and have discovered the merits and limits of most of them.

Hi, sorry for the necropost, but I appear to be in a somewhat similar situation you were in, just 6 years in the future. ;)
I got a few badges, did some research online, and decided to do a little art project for some of my local pinball friends. Then I proceeded to buy several badges from different sellers to get various colors at better prices, and ended up with a set of different hardware. Most of them have been 11x44, and work with what appears to be updated software to what you received (or fond) within this thread. Most of my badges are still usable with their software, though getting my artwork onto all of them is going to be more of a challenge than I anticipated. In case you're curious, here's my work in progress website that has various custom animations I've created, or adapted from some games.
My question is this... Do you still have copies of the old badge software, and would you be willing to share? :)
Currently I've got these, which all have various pros and cons, but are at least capable of what I assume was the same trick you discovered years ago -- using a BMP that is basically 11 tall x 44*N wide where N is the number of frames of the animation, and then setting the animation flag so it shows them in rapid succession.

But I just received a few more badges that only linked to an Android app (a very poor quality app, as is true with most of the apps for these things -- the Windows software isn't great either, but it's generally way better than the apps!) None of the software I've tried, or the python projects I've found online can connect to this different badge type. And I'm hoping maybe it's old, and perhaps compatible with one of the types you ended up with back in the day... There's one thing that distinguishes this one from the others I've seen -- it doesn't have the "coffee" animation when charging, but instead has a flashing lightening bolt  with the battery image on screen.
I know it's a long shot, but I figured I'd ask. Currently, the only thing I can put on this new set of badges is text and what I guess I'd call "emoji" images -- they default to 11x11, can be mixed with the text, but can be made to grow to a max of 11x128 in the app. But 128 wide is not nearly enough for anything but simple animations. And the image importer in the app is so poor it corrupts/dithers/resizes everything loaded, so it would require remaking every single image pixel by pixel, by hand, and with only 2 frames total of animation. :( The badge does get recognized as "something" when plugged into Windows, and I expect there is some software, somewhere, that might work with it. I had no luck with Linux options, though they work fine for my other badges. Any pointers or suggestions from your struggles in the past would be appreciated! I followed your journey here in comments. Hope your project(s) worked out in the end!

Here's a fun fact about the .bge file format that that program uses. If you hex-edit the speed to something invalid, you can achieve a much higher FPS than what the program will ever allow you to do. I used to upload a "spritesheet" through the logo feature and use that hack to get smooth animations on there. Hope this helps!

Unfortunately, I am unable to find my original disk. It was one of those mini cds like what J0w03L archived. I'm not even sure that version would left you flip through frames of a sprite sheet or if it was just a sliding image. Probably the best you could do with that version is flip between the two image slots it had.


Remove netcoreapp3.1 and net5.0 from TargetFrameworks and add net8.0

Is your feature request related to a problem? Please describe.
Currently, I see in the csproj files <TargetFrameworks>netstandard2.0;net461;netstandard2.1;netcoreapp3.1;net5.0;net6.0</TargetFrameworks>
Describe the solution you'd like
Remove netcoreapp3.1 and net5.0 and add net8.0.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for hinting this. Removing the "end of support" targets is probably a good idea. net461 should be replaced by net462 as well. I have to check if we introduce any breaking change  that way, but in theory netstandard2.0 and netstandard2.1 should still ensure compatibility with netcoreapp3.1 and net5 projects.


Please release the latest code

Using the current release version, Mistral models cannot be used with VLLM, getting the error 'ValueError: Quantization is not supported for <class 'vllm.model_executor.models.mistral.MistralForCausalLM'>'.
After the last release, lots of changes were added for Mistral models, without good GPU support VLLM cannot be built from the source, please release the latest build to Pypi so that everyone can access the latest features.

#1346 looks to be underway for release today.

@casper-hansen Thanks for the update.


UI to show fetch data status and more

Need to let the user know when we are still waiting for data or processing something.

loading animation on the sidepanel done


ISPN-15396 Netty 4.1.104.Final

https://issues.redhat.com/browse/ISPN-15396

Supersedes https://github.com/infinispan/infinispan/pull/11588 and https://github.com/infinispan/infinispan/pull/11589

failures are unrelated

Integrated into main, thanks @tristantarrant !


perf: ionic setup sass

From @mifama on February 6, 2015 23:16
Type: perf
Platform: desktop browser
I updated the ionic version to last version, and now when I do 'ionic setup sass' it's return

Copied from original issue: driftyco/ionic#3049

Could you paste the contents from ionic info?
Scanning the node-sass issues, it looks like theres an issue filed about this and Node v0.12

I have this issue too, ionic info shows:
Your system information:

OS: Windows 8.1
Node Version: v0.12.0
Cordova CLI: 4.3.0
Ionic Version: 1.0.0-rc.0
Ionic CLI Version: 1.3.14

@toby1kenobi can you post some of the error log as you saw them? It'd help to see that.
Or, did you have the same output as the original poster?

@toby1kenobi and @mifama - Try updating your package.json file - change gulp-sass to be this:
"gulp-sass": "^1.3.3",
This should bump gulp-sass to use node-sass 2.x, which should resolve that issue.

Closing - since this is more of a node-sass and gulp-sass issue.

Sorry for delay, will try your suggestion

Please do. I was able to recreate it last night on my Windows machine like you had, and bumping that version solved the issue.
One other thing to note - at first I had trouble since Python is required, I installed 3.5, that had some issues. I found a stackoverflow post that specified using Python 2.7, which also helped.
Not sure if that is absolutely required though.

Brilliant, that did it - thanks!

Yep. Were you running python 2.7 or 3.5?

2.7 - I was anyway, but as a result of some previous node-related situation


replace RMSProp with adam as optimizer

Adam with default parameters converges faster here than the RMSProp (At least during the first 50 epochs)

I don't see, how the tests/keras/test_callbacks.py::test_TensorBoard_convnet  test could be affected by the change

CLose and reopen your PR to rerun the tests

But why? You haven't provided any concrete justification for this change.

Due to hardware limitations, I first only compared the training and validation loss during the first 25 epochs.
Here adam constantly achieved lower loss than RMSProp.
However, I do not achieve a logloss of 0.55 after 50 epochs (as described in the comment in the code) with any of the optimizers. For both optimizers it seems to me that the training loss converges to approx. 0.75 (even after 100 epochs) but adam reaches this threshold faster.


Document PULUMI_SKIP_UPDATE_CHECK on install page.

Problem description
Pulumi supports PULUMI_SKIP_UPDATE_CHECK to skip checking for new versions but this doesn't appear to be documented anywhere except in the original PR (https://github.com/pulumi/pulumi/pull/2680).
We should document usage of PULUMI_SKIP_UPDATE_CHECK at https://pulumi.com/docs/reference/install/ since this is the URL that's referenced in the upgrade message.
$ pulumi help
warning: A new version of Pulumi is available. To upgrade from version '0.17.25' to '0.17.26', run
   $ brew upgrade pulumi
or visit https://pulumi.com/docs/reference/install/ for manual instructions and release notes.
Pulumi - Cloud Native Infrastructure as Code

To begin working with Pulumi, run the 'pulumi new' command:

    $ pulumi new
...

Thanks for reporting this, @clstokes . I've addressed via #1489


Abp.Zero.Ldap has not been mentioned under the Module Zero Nuget Packages

Abp.Zero.Ldap has not been mentioned under the Module Zero Nuget Packages.I think it should be mentioned under it here : Module Zero Nuget Packages

Fixed it. Thanks ;)