How to set the short range of L515 with python code?

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{L515}

Firmware Version
(<IP_ADDRESS>)

Operating System & Version
{Win (10) }

Kernel Version (Linux Only)
None

Platform
PC

SDK Version
{ 2.5.1 }

Language
{python }

Segment
{Robot }

Issue Description
<Describe your issue / question / feature request / etc..>
I start the depth camera through python code, and the depth screen appears in the Max range mode, but my project needs to use the camera's short range mode. How to set the L515's short range mode through code in python? Is there an example code? Please help me

！！How to use python code to implement this function on the SDK！！

Hi @Drift-Of-Little-Forest  Here is Python code for setting the Short Range preset.
# Declare sensor object and set options
depth_sensor = profile.get_device().first_depth_sensor()
depth_sensor.set_option(rs.option.visual_preset, 5) # 5 is short range, 3 is low ambient light

https://github.com/IntelRealSense/librealsense/issues/8619 is an example of a full Python script that uses this code to define the preset.

Hi@Drift-of-Little-Forest以下是用于为 L515 相机型号设置短距离预设的 Python 代码。
# Declare sensor object and set options
depth_sensor = profile.get_device().first_depth_sensor()
depth_sensor.set_option(rs.option.visual_preset, 5) # 5 is short range, 3 is low ambient light

#8619是一个完整的 Python 脚本示例，该脚本使用此代码来定义预设。
Thank you very much for your help

Hi @Drift-Of-Little-Forest Here is Python code for setting the Short Range preset for the L515 camera model.
# Declare sensor object and set options
depth_sensor = profile.get_device().first_depth_sensor()
depth_sensor.set_option(rs.option.visual_preset, 5) # 5 is short range, 3 is low ambient light

#8619 is an example of a full Python script that uses this code to define the preset.

I want to know the difference between color alignment depth and depth alignment color, please help me

With depth to color alignment, the size of the depth field of view (FOV) will be resized to the size of the color FOV.  When the color FOV is smaller then the depth FOV, this means that the outer edges of the depth image may be excluded from the aligned image.
With color to depth alignment, the color FOV is resized to match the depth FOV size.  When the color FOV is smaller, this means that the color data will stretch out to fit the depth FOV size and depth information at the image edges will not be excluded from the aligned image.

With depth to color alignment, the size of the depth field of view (FOV) will be resized to the size of the color FOV. When the color FOV is smaller then the depth FOV, this means that the outer edges of the depth image may be excluded from the aligned image.
With color to depth alignment, the color FOV is resized to match the depth FOV size. When the color FOV is smaller, this means that the color data will stretch out to fit the depth FOV size and depth information at the image edges will not be excluded from the aligned image.
The L515 camera model has a depth FOV of 70° × 55° and a color FOV of 70° × 43°.

Thanks for your help！

Hi @Drift-Of-Little-Forest  Do you require further assistance with this case, please?  Thanks!

Yes, the higher the color resolution the better the image quality, as a high resolution image is made up of many tiny pixels whilst a low resolution image is made up of a smaller number of large pixel 'blocks' that can look more blurred and muddy.
In regard to the depth image, accuracy does increase as resolution increases and decreases as resolution decreases.  Each camera model has a depth resolution at which accuracy will be optimal.  For the D415 camera model it is 1280x720 and for most other 400 Series models it is 848x480.  For the L515, 1024x768 will be the best depth resolution for accuracy.

Yes, the higher the color resolution the better the image quality, as a high resolution image is made up of many tiny pixels whilst a low resolution image is made up of a smaller number of large pixel 'blocks' that can look more blurred and muddy.
In regard to the depth image, accuracy does increase as resolution increases and decreases as resolution decreases. Each camera model has a depth resolution at which accuracy will be optimal. For the D415 camera model it is 1280x720 and for most other 400 Series models it is 848x480. For the L515, 1024x768 will be the best depth resolution for accuracy.

嗨@Drift小森林请问您需要此案的进一步帮助吗？谢谢！

I want to know the specific concepts of different depth resolutions. For example, the higher the color resolution is, the more detailed the pixel points of the real image are. The higher the depth resolution is, the more accurate the depth distance of a point in the measured object is? If you have time, I hope you can help me again.

See above at https://github.com/IntelRealSense/librealsense/issues/11053#issuecomment-1304753468 for the answer  :)

是的，颜色分辨率越高，图像质量越好，因为高分辨率图像由许多微小像素组成，而低分辨率图像由较少数量的大像素“块”组成，看起来更加模糊和模糊。
关于深度图像，精度确实随着分辨率的增加而增加，随着分辨率的降低而降低。每个相机型号都有一个深度分辨率，在该分辨率下精度将是最佳的。对于 D415 相机型号，它是 1280x720，对于大多数其他 400 系列型号，它是 848x480。对于L515，1024x768将是精度的最佳深度分辨率。

Thank you very much for your help

Hi @Drift-Of-Little-Forest  Do you require further assistance with this case please?  Thanks!

Thank you very much for your help. I haven't encountered any new difficulties yet
?浮生未歇?
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "IntelRealSense/librealsense"                                                                                @.>;
发送时间: 2022年11月12日(星期六) 下午3:32
@.>;
<EMAIL_ADDRESS>主题: Re: [IntelRealSense/librealsense] How to set the short range of L515 with python code? (Issue #11053)
Hi @Drift-Of-Little-Forest  Do you require further assistance with this case please?  Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Case closed due to solution achieved and no further comments received.


Github Actions: use official clippy-check

The feature we needed/wanted is now merged and available in the official action.

bors r+


Handle scenario where auth data is missing for selected atsign on demo app

[x] Handle when @sign is found in keychain and all the other related information is missing in keychain.
[x] Make changes to fit the demo @signs' easily into onboarding widget.

The changes are available in trunk branch of at_hello_world app.


chainntnfs+lnrpc/chainrpc: add ChainNotifier RPC subserver

TODO: description...
Depends on #2291.

It doesn't build:
joost@joost-ThinkPad-T440s $ make  tags="signrpc walletrpc chainrpc"
 Building debug lnd and lncli.
GO111MODULE=on go build -v -tags="dev signrpc walletrpc chainrpc" -o lnd-debug -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.5.1-beta-172-g45fad52f1e7ddf027c10c926fc6065198945c0a3" github.com/lightningnetwork/lnd
github.com/lightningnetwork/lnd/lnrpc/chainrpc
# github.com/lightningnetwork/lnd/lnrpc/chainrpc
lnrpc/chainrpc/chainnotifer_server.go:209:2: undefined: confEvent
lnrpc/chainrpc/chainnotifer_server.go:209:13: undefined: err
lnrpc/chainrpc/chainnotifer_server.go:212:5: undefined: err
lnrpc/chainrpc/chainnotifer_server.go:213:10: undefined: err
lnrpc/chainrpc/chainnotifer_server.go:215:8: undefined: confEvent
lnrpc/chainrpc/chainnotifer_server.go:224:20: select case must be receive, send or assign recv
lnrpc/chainrpc/chainnotifer_server.go:224:25: undefined: confEvent
lnrpc/chainrpc/chainnotifer_server.go:251:14: select case must be receive, send or assign recv
lnrpc/chainrpc/chainnotifer_server.go:251:19: undefined: confEvent
lnrpc/chainrpc/chainnotifer_server.go:266:19: undefined: confEvent
lnrpc/chainrpc/chainnotifer_server.go:266:19: too many errors
Makefile:99: recipe for target 'build' failed
make: *** [build] Error 2

Reminder: immediately send current block after RegisterBlockEpochNtfn

Ntfr log not enabled in main log.go.

If there is so much duplication, can't more be extracted into reusable methods first and build the new functionality on top of that?
dupl -t 80
found 2 clones:
  bitcoindnotify/bitcoind.go:332,361
  btcdnotify/btcd.go:381,410
found 2 clones:
  bitcoindnotify/bitcoind.go:228,261
  btcdnotify/btcd.go:296,329
found 3 clones:
  bitcoindnotify/bitcoind.go:199,225
  btcdnotify/btcd.go:268,293
  neutrinonotify/neutrino.go:282,307
found 2 clones:
  txnotifier.go:499,527
  txnotifier.go:821,849
found 2 clones:
  bitcoindnotify/bitcoind.go:478,637
  btcdnotify/btcd.go:529,689
found 2 clones:
  height_hint_cache.go:119,233
  height_hint_cache.go:236,351
found 3 clones:
  bitcoindnotify/bitcoind.go:1027,1106
  btcdnotify/btcd.go:1041,1122
  neutrinonotify/neutrino.go:946,1025
found 2 clones:
  bitcoindnotify/bitcoind_test.go:32,49
  btcdnotify/btcd_test.go:30,47
found 2 clones:
  bitcoindnotify/bitcoind.go:282,318
  btcdnotify/btcd.go:331,367
found 2 clones:
  bitcoindnotify/bitcoind.go:735,749
  btcdnotify/btcd.go:796,810

Found total 10 clone groups.

This is just automated output, if the code is slightly different it isn't reported by dupl.

Tried to build several commits with git bisect and manually too. Seems that many of them aren't building.


Not playing/hangs on next song

In one of my playlists I keep hitting the issue that the last 3 songs of my playlist fail to play. On Spotify OSX I have selected Librespot running on my RPi. When it reaches the song  in the interface before the failing ones it just doesn't go to the next and keeps hanging on the last one. When I select the next song it starts 'playing', but Librespot doesn't log the new song and though the progressbar moves in Spotify, there is no audio.
I also tried running Librespot with --verbose, but nothing is outputted.
Is this due to CDN for example? Can I get more debug output out of Librespot?
I am using Raspotify compiled with the current master of Librespot.

INFO:librespot_playback::player: Track "nyepi" loaded DEBUG:librespot_audio::fetch: File e78b42a721592a2de8436a6c3b94ea2a78f478f5 complete DEBUG:librespot_core::session: Session[0] strong=3 weak=4 DEBUG:librespot_core::session: Session[0] strong=3 weak=4 DEBUG:librespot_connect::spirc: At track 11 of 15 <"spotify:user:peterdekr:playlist:7wxwjYJQXDjhtE3kdd1ZmV"> update [true] DEBUG:librespot_playback::player: command=Load(SpotifyId(u128!(267662077716844162978646694263632685810)), true, 0) INFO:librespot_playback::player: Loading track "City Gardens" with Spotify URI "spotify:track:67YlhgBxHM8uZAANzSPnc6" DEBUG:librespot_audio::fetch: Downloading file b48e835716bd7e41dce43c612f0eed109bdf690d DEBUG:librespot_playback::player: Normalisation Data: NormalisationData { track_gain_db: -3.550003, track_peak: 0.8924745, album_gain_db: -4.459999, album_peak: 0.91598123 } DEBUG:librespot_playback::player: Applied normalisation factor: 0.66450745 INFO:librespot_playback::player: Track "City Gardens" loaded DEBUG:librespot_audio::fetch: File b48e835716bd7e41dce43c612f0eed109bdf690d complete DEBUG:librespot_core::session: Session[0] strong=3 weak=4 DEBUG:librespot_core::session: Session[0] strong=3 weak=4 DEBUG:librespot_core::session: Session[0] strong=3 weak=4
Here it played the first song ok, and then hangs at the end in Spotify and won't go to the new one. Nothing in the log indicating that something goes wrong.

What bitrate are you using? I've got a report of a track which would not play if librespot was told to stream in 320kbps, but the track wasn't available in that bitrate (for whatever reason). What if you run librespot with --bitrate=96? Would it get past your tracks?

I indeed am using 320kbps. I switched to 96kbps and it actually seems to solve the issue. It now progresses to the next track. Will test a bit more. Unfortunately it's not a solution since I want to keep using 320kbps, but definitely a hint to what is causing it.

@michaelherger I added the mentioned track to my playlist, but at 320kbps there seems no issue with that specific track.

Correct: the user who reported the issue to me confirmed that it started working again after a few days.

I had a similar issue when booting up the (headless) RPi and when skipping songs too fast. The progress bar in the spotify app was moving but librespot just hung. Sometimes it took minutes to load the track and to start playing.
Then I noticed that the kernel ran out of entropy for the /dev/random RNG which is probably used by librespot for Diffie-Hellman key generation (reading from /dev/random blocks until enough entropy is available). I could solve the issue by installing rng-tools and setting up rngd (it uses RPi's HW-RNG to feed the kernel entropy pool).

I believe this should be properly fixed since https://github.com/librespot-org/librespot/pull/381 as we noticed this issue more consistently with podcasts which often don't have high qualities available.
My solution was: https://github.com/librespot-org/librespot/pull/381/files#diff-f582d878256027ce3c970a26de626b55R544

Great, I compiled and now it runs perfectly on those songs. Thanks for your work!


Fix setting the LTP305 brightness

The birghtness setting on the LTP305 driver didn't work because the local variable hid the member variable.

Thank you!


refactor: keep nvml active during fastapi lifetime

This pull request ensures that nvml is kept active during the FastAPI lifetime. It also cleans up the code a bit.

I was able to test with new container build on segment-anything-2 runner and both /hardware/info and /hardware/stats worked.


Leaving notification did not work

Great geofence on ionic example, man! However I tried adding notification when leaving the area, but I got no notification when I am outside the radius. Did you try this?
Also, it seems like the application can only get position when it is connected to wifi.

Looks like there was wrong transition type code used for exit event. It was 0 should be 2.


Create v1.6.0 release

Coverage remained the same at 34.07% when pulling 4c457686f16bced814af0f8aa8d98d36165a25eb on zhiyuhe/v160_new_release into f0dad8bfb1e00bfa25197b152ed660f66466f192 on master.


[11.x] Add whereDateTime and orWhereDateTime to query Builder

This adds two new methods to the query builder class to make it easier to work with multiple time zones. Dates are typically stored in UTC but it can be difficult to compare those dates when working with multiple timezones.
Using ->whereDate('created_at', '2024-03-01')  would return all dates stored as March 1 2024 but this includes dates from the previous day and excludes dates from late on the day if the user not expecting UTC.
whereDateTime()  will convert a Carbon object to UTC (or whatever timezone is set in app.timezone) so that it can compare dates in the timezone that was expected.
whereDateTime('created_at','>=', new Carbon('2024-03-01', 'America/Chicago')) would return all rows with a created_at date of 2024-03-01 05:00:00 or after. (Chicago is currently -5 UTC)

Developers that are changing the carbon timezone from the default app.timezone should be aware of the implications. Perhaps a note in the documentation would better suffice.

@ahinkle this change is about supporting multiple timezones in an app. So the default timezone would remain UTC but the date for the query comparison would be based on the user's timezone.

I want to advise against merging this, sorry. These methods, even documented properly, will just cause confusion to users. If you use a different timezone in your app config than your database records, you should just explicitly change the timezone of your datetime/carbon instance before using it as a where constraint. This makes this explicit and clear to a developer.
In general I very much recommend against using anything else than UTC and use timezones purely as a presentation format, optionally saving the timezone to present in close to the database record.

I completely agree with storing the dates as UTC. The goal for this was not specifically for apps that have changed the default timezone but more for handling user provided dates on a datetime column. For example, if a user selects a date or date range to view, then that date has to be converted to UTC before it can accurately be compared to the database values.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

ok, makes sense. Thanks everyone for the discussion.
I created a trait with a couple other functions to make it easier to compare these dates. I've added it to a gist if it's helpful for anyone else. DateTimeCompare


Keyboard not showing when flutter driver extension is enabled

Steps to Reproduce
Run the following main.dart via flutter run on a physical device and tap on either of the fields presented.
import 'package:flutter/material.dart';
import 'package:flutter_driver/driver_extension.dart';

void main() {
  // Enable integration testing with the Flutter Driver extension.
  // See https://flutter.dev/testing/ for more info.
  enableFlutterDriverExtension();
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData.dark(),
      home: MyHomePage(
        title: "Issue #2 Reproduction",
      ),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.spaceEvenly,
          children: <Widget>[
            Form(
              child: Column(
                mainAxisAlignment: MainAxisAlignment.spaceAround,
                children: <Widget>[
                  TextFormField(
                    obscureText: false,
                    decoration: InputDecoration(
                      hintText: "Username",
                    ),
                  ),
                  TextFormField(
                    obscureText: true,
                    decoration: InputDecoration(
                      hintText: "Password",
                    ),
                  ),
                ],
              ),
            )
          ],
        ),
      ),
    );
  }
}

Device Information
Unfortunately, my virtualization configs are screwed up, so I don't know whether this happens on emulated devices.
My test device is a Samsung Galaxy Note 4 (SM N910T) running Android 6.0.1
Extra Information
Here is my minimal reproduction branch with the code above.
Here is where I'm tracking this issue.
Logs
Nothing produced in the logs.
Flutter Doctor output:
$ flutter doctor -v
[√] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17134.556], locale en-US)
    • Flutter version 1.5.4-hotfix.2 at C:\flutter_windows_v0.11.11-beta\flutter
    • Framework revision 7a4c33425d (5 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at F:\AppData\Android\Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = F:\AppData\Android\Sdk
    • Java binary at: F:\Programs\Android\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.3)
    • Android Studio at F:\Programs\Android
    • Flutter plugin version 33.3.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] IntelliJ IDEA Ultimate Edition (version 2018.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2018.2.4
    • Flutter plugin version 31.1.3
    • Dart plugin version 182.5124

[√] VS Code (version 1.34.0)
    • VS Code at C:\Users\Jackie\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 2.26.0

[√] VS Code, 64-bit edition (version 1.26.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.26.0

[√] Connected device (1 available)
    • SM N910T • c253d892 • android-arm • Android 6.0.1 (API 23)

• No issues found!

When I remove enableFlutterDriverExtension(); from main(), the keyboard shows up.
Is this expected behavior?

Hello
I have the same issue ! THANKS !
I searched for hours to understand why  the keyboard doesn't appeared  !

No problem, I'll leave a link for anyone else struggling: https://github.com/flutter/flutter/issues/15415#issuecomment-505621936

Hi @pujitm
I see you found an open issue addressing the case you described
Please follow up on that issue.
I'm closing the current one as duplicate
if you disagree please write in the comments
and I will reopen it

I have same issue. Targeting Android API 30. Same happens for iOS :(


Logging API: onDidChangeLogLevel is called after the logLevel is changed.

Testing #164434
Not sure if this will be used to identify from -> to scenario for log level changes. But, since the logLevel on the channel is already set.

Yah that's the reason the event is called onDidChangeLogLevel and this is the common pattern in the API


Add a New Workspace

Some of our servers already have MMA installed. Is there a automated way to check if the MMA is up-to-date. If not, update to the latest version and add a new workspace

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

ID: 00a00a3e-a0df-7ee5-4733-7231bd7a024f
Version Independent ID: 94361683-e1e7-7e55-6993-86d3c2486a14
Content: Connect Windows computers to Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/platform/agent-windows.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@mboppe Thank you for your query, we will look into this and get back to you at the earliest.

@mboppe Sorry we don't have a out of box automated way to tell if the agent is up to date or not. However when you try to install the agent on a machine which already have one would show the message to upgrade the agent.
For now the best way i could think of is writing a custom script to validate the current version of MMA agent of the machine and install it accordingly if it isn't the latest version.
Below is the location which would help identify the current version of the MMA agent on the machine
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\CurrentVersion
Please see if agent installation via DSC  can help. Also sharing a custom script created by community members.
Hope the above information helps. At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


Fraction of a second unparsed {variable}

First of all kudos for your work as this is an awesome library.
I noticed one small thing though. Before reLift mounts into the page, you can see the unparsed {variable} for a fraction of a second.
You can check it here by clicking the Run button:
https://jsfiddle.net/hdfup3cg/
Vue, for example, has something called v-cloak, that is an attribute that you can add to an element you want to hide, while Vue is mounting.
Is there anything similar for reLift?

Never mind, this can be actually solved very easily with something like this:
created() {
        const el = document.getElementById('root');
        el.setAttribute("style", "display:visible");
    },

Full example here:
https://jsfiddle.net/rx0dupgh/

Hi,
You got the answer right. You don't even have to do it yourself, reLift internally will set display:block of the element.  Without doing anything in created(), the snippet below will achieve the same thing. All you need to do is have the element hidden.

...

reLiftHTML({
  el: `#root`,
  ...
})


invalid item in dependencies list

Env:
CPU: AMD 5950x;
OS: Linux liuyu-pc 5.11.0-25-generic #27~20.04.1-Ubuntu x86_64 GNU/Linux;
Docker:version 20.10.7, build f0df350
Steps:
follow the steps in README.md,build successfully,then import project to IDEA,appears errors like below :
Module intellij.android.projectSystem.gradle.sync: invalid item 'studio-sdk' in the dependencies list Module intellij.android.projectSystem.gradle.sync: invalid item 'studio-plugin-junit' in the dependencies list Module intellij.android.projectSystem.gradle.sync: invalid item 'studio-plugin-Kotlin' in the dependencies list Module intellij.android.projectSystem.gradle.sync.tests: invalid item 'studio-sdk' in the dependencies list Module intellij.android.projectSystem.gradle.sync.tests: invalid item 'studio-plugin-Kotlin' in the dependencies list Module intellij.android.projectSystem.gradle.sync.tests: invalid item 'studio-plugin-junit' in the dependencies list Module google-cloud-tools-as: invalid item 'studio-sdk' in the dependencies list Module google-cloud-tools-as: invalid item 'studio-plugin-Kotlin' in the dependencies list Module google-cloud-tools-as: invalid item 'studio-plugin-gradle' in the dependencies list Module google-cloud-tools-as: invalid item 'studio-plugin-Groovy' in the dependencies list Module google-cloud-tools-as: invalid item 'studio-plugin-git4idea' in the dependencies list Module intellij.android.build-attribution: invalid item 'studio-sdk' in the dependencies list Module intellij.android.build-attribution: invalid item 'studio-plugin-gradle' in the dependencies list Module intellij.android.build-attribution: invalid item 'studio-plugin-Kotlin' in the dependencies list Module intellij.android.build-attribution.tests: invalid item 'studio-sdk' in the dependencies list Module intellij.android.build-attribution.tests: invalid item 'studio-plugin-Kotlin' in the dependencies list Module intellij.android.build-attribution.tests: invalid item 'studio-plugin-gradle' in the dependencies list and so on.
Did you encounter the problem?
Any ideas? :)

Did you encounter the problem?

Yes, I did.

Any ideas?

You have at least 3 options:

Ignore (build in IDEA is successful, right?)
Create empty project libraries with expected names (e.g. studio-plugin-gradle, ...)
Cleanup modules by deleting references to non-existing libraries

IntelliJ IDEA follows approach #3. I didn't include this patch because large patches are hard to maintain and usually they won't be compatible with new studio sources.

Did you encounter the problem?

Yes, I did.

Any ideas?

You have at least 3 options:

Ignore (build in IDEA is successful, right?)
Create empty project libraries with expected names (e.g. studio-plugin-gradle, ...)
Cleanup modules by deleting references to non-existing libraries

IntelliJ IDEA follows approach *3. I didn't include this patch because large patches are hard to maintain and usually they won't be compatible with new studio sources.

After some research, I found the 'IDEA jdk' not be configed, so, added it : Project Structure->Platform Settings->SDKs;
Before rebuild project ,IDEA prompted 'Kotlin Plugin must 1.4.99 or lower', My IDEA is 212, it is not compat with Kotlin Plugin which version is 1.4.99 or lower, I reinstall IDEA-203, but i didnt found plugin 1.4.99, the version nearest 1.4.99 is 1.4.31,so i did and rebuild project again.Unfortunatly, also encounted error : Kotlin: [Internal Error] org.jetbrains.kotlin.codegen.CompilationException: Back-end (JVM) Internal error: Failed to generate expression: KtProperty
File being compiled: (13,3) in /home/liuyu/Downloads/android-studio-builder/aosp_source/tools/idea/platform/execution-impl/src/com/intellij/execution/impl/BeforeRunTaskHelper.kt
The root cause java.lang.IllegalStateException was thrown at: org.jetbrains.kotlin.codegen.state.KotlinTypeMapper$typeMappingConfiguration$1.processErrorType(KotlinTypeMapper.kt:122)
...
...
Caused by: java.lang.IllegalStateException: Error type encountered: [ERROR : ] (ErrorType).
 I guessed it is still relatived with Kotlin Plugin ,but didt find anything helpful after googling a lot.
I wonder whether it exists Kotlin Plugin which version is between 1.4.31 and 1.4.99,or is there  some method work around for building project?

I found the 'IDEA jdk' not be configed, so, added it
Ah. You are right. I forgot to mention this step. It is explained here: https://github.com/JetBrains/intellij-community/blob/202/README.md#intellij-build-configuration

1.4.31 should work fine. This exception looks like a bug in kotlin compiler. Please click "build" button again. If it fails with exactly the same error - please try "rebuild project". If error is different - keep trying to build the project via "build" button. Let me know if neither helped. I observe similar error time to time with kotlin compiler 1.4.x while compiling IDEA sources.

Cleanup: closing obsolete issues


Update github actions

Changes
In github workflows:

Bump golang version from ^1.15 to ^1.16 because 1.15 is no longer supported.
Bump ubuntu to latest because 16.04 is removed.

How to test
Tested with the forked version: https://github.com/nhatthm/go-keyring/runs/3522332469?check_suite_focus=true

👍

👍

👍

@mikkeloscar: looks like I need another +1, the one from Michael is not counted.

:+1:

@nhatthm thanks, I try to review all PRs here as @mikkeloscar does, too. So no worries about the company policy here with the 4 eyes. If one of us is not there he can also ask internal OSS guild to add there +1 or team members.

Cool, thanks mate 👍


JwtBearerHandler always returning 401 (even when 403 expected)

When using JwtBearerToken in the following way:
app.UseJwtBearerAuthentication(new JwtBearerOptions
            {
                AutomaticAuthenticate = true,
                AutomaticChallenge = true,
                TokenValidationParameters = tokenValidationParameters
            });

and then checking user roles on controller action like:
[Authorize(Roles="whateverrole"]
for a valid token that does contain roles claim (and claims are correctly mapped to roles which is confirmed by checking User.IsInRole("whateverroleisinJWT") being true for all roles assigned in JWT) but does not assign specific "whateverrole" to user JWTBearerMiddleware/Handler returns 401 instead of 403.
I have already seen some discussions about it but, honestly, haven't found out any satisfying explanation nor direction how to solve that actualy.
So, the question is...Is it really expected behavior that if user IsAuthenticated (so, token is valid and Identity is created) but not Authorized (does not have sufficient roles/claims) JWTBearerMiddleware should return 401 instead of 403? or is that just a bug?
Furthermore, if its expected, is there any non-workaround, non-hack way to use JWTBearerMiddleware so that it returns 403 when its supposed so?
Am i missing something or is this causing always to have that 401?
https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNetCore.Authentication.JwtBearer/JwtBearerHandler.cs#L212

Hmm..
The Challenge vs Forbid code is in the base class.
https://github.com/aspnet/Security/blob/da4730a3922dd885fdda013f5efa72010a7d0170/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L353
Jwt doesn't implement HandleForbidAsync, so it should inherit it from the base class:
https://github.com/aspnet/Security/blob/da4730a3922dd885fdda013f5efa72010a7d0170/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L332
We'll have to reproduce this and see why it's not taking the forbid code path.

Could the problem be the following:

in ChallengeAsync it calls:
https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L353

with parameter context.AuthenticationScheme which, for JWT, should be 'Bearer' (set in JWTBearerOptions constructor)

in
https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L210

it compares that authentication scheme ('Bearer' in this case) to AuthenticationManager.AutomaticScheme (which is 'Automatic'). that returns false and that might be the reason not going into handling Forbidden.

@codefactorydevelopment I don't think that's it, you missed the prior line https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L209

hm...right.
would be great if someone could try to reproduce this and confirm what is it about.

We do have a test for this scenario simulating what the authorize attribute does, can you try replacing the authorize attribute with the equivalent logic that's going on behind the covers that the filter is doing:
See https://github.com/aspnet/Security/blob/dev/test/Microsoft.AspNetCore.Authentication.Test/JwtBearer/JwtBearerMiddlewareTests.cs#L380
First turn off automatic challenge/authenticate
And in your action do this instead and see if it gives you a 403:
                            var result = await context.AuthenticateAsync(JwtBearerDefaults.AuthenticationScheme);
                            await context.ChallengeAsync(JwtBearerDefaults.AuthenticationScheme);

Thanks for your response.
So, i can confirm that when i remove Authorize attribute and put those lines into my action, i do get 403.
Now, what does that mean?

Looks like it might be an issue with automatic challenge, try setting the scheme explicitly in your Authorize
either
[Authorize(Roles = "whatever", ActiveAuthenticationScheme = "Bearer")]
Or setting it via the default policy:
            services.AddAuthorization(options =>
            {
                options.DefaultPolicy = new AuthorizationPolicyBuilder("Identity.Application").RequireAuthenticatedUser().Build();
            });

For more details see https://github.com/aspnet/Announcements/issues/210

Thank you.
I can confirm that setting a scheme explicitly worked and now returns 403 as expected.
Now, i am not familiar with publish process, so what does this mean? Should we use it this way with explicit setting? And, what is usual time to expect some real fixes for things like this?
Thanks

Can you share your project.json file? This is similar to an issue caused by mixing 1.0 and 1.1 packages

Sure. Here it is:
`{
"dependencies": {
"Microsoft.NETCore.App": {
"version": "1.0.1",
"type": "platform"
},
"Microsoft.AspNetCore.Mvc": "1.0.1",
"Microsoft.AspNetCore.Routing": "1.0.1",
"Microsoft.AspNetCore.Server.IISIntegration": "1.0.0",
"Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
"Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0",
"Microsoft.Extensions.Configuration.FileExtensions": "1.0.0",
"Microsoft.Extensions.Configuration.Json": "1.0.0",
"Microsoft.Extensions.Logging": "1.0.0",
"Microsoft.Extensions.Logging.Console": "1.0.0",
"Microsoft.Extensions.Logging.Debug": "1.0.0",
"Microsoft.Extensions.Options.ConfigurationExtensions": "1.0.0",
"System.IdentityModel.Tokens.Jwt": "5.1.2",
"Microsoft.AspNetCore.Authentication.JwtBearer": "1.1.0"
},
"tools": {
"Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"
},
"frameworks": {
"netcoreapp1.0": {
"imports": [
"dotnet5.6",
"portable-net45+win8"
]
}
},
"buildOptions": {
"emitEntryPoint": true,
"preserveCompilationContext": true
},
"runtimeOptions": {
"configProperties": {
"System.GC.Server": true
}
},
"publishOptions": {
"include": [
"wwwroot",
"**/*.cshtml",
"appsettings.json",
"web.config"
]
},
"scripts": {
"postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
}
}
`

Yup, don't mix 1.0 and 1.1. there's a known issue here with IISIntegration 1.0

oh, had now idea about that. thank you very much for that finding!
you are talking JwtBearer 1.1, right?
what do you suggest to do?

Update everything to 1.1 (or highest available)

Great, i will do that.
Thank you very much!

Ok, just to post a final confirmation for the case someone else run into this situation.
I can confirm that upgrading to Asp.Net Core 1.1 and upgrading all packages to latest versions did the job. Now 403 is return when expected.
Instructions on how to upgrade to 1.1 are here:
https://blogs.msdn.microsoft.com/webdev/2016/11/16/announcing-asp-net-core-1-1/
Thanks one more time!


Move scrapping title and description to FE

It's less peformant to do it in Node.js as it blocks one of the worker threads for it..

Cors issues in FE


Enable model redeployments with SDK

What this PR does / why we need it:
This PR introduces a minor tweak the the SDK which allows the redeployment of existing Merlin model versions using the deploy method.
Previously, performing the following operations below will result in the second call to deploy returning a {"error":"There is 'running' deployment for the model version"} error:
    # Create new model version
    with merlin.new_model_version() as v:
        merlin.log_model(model_dir=model_dir)

    # Deploy
    initial_endpoint = merlin.deploy(v)

    # Deploy using raw_deployment
    new_endpoint = merlin.deploy(v, deployment_mode=DeploymentMode.RAW_DEPLOYMENT)

In the new implementation introduced by this PR, the second deploy call will simply redeploy the router version (represented by v) with the new configuration (i.e. with the raw deployment setting).
Unrelated Modifications
This PR also introduces an additional check in the Update Endpoint controller to ensure that an endpoint being updated is not in the pending state (attempting to do so will return a 400 error). This changes the current behaviour of this endpoint (the Update Endpoint endpoint 🥴), as you might notice from some of the changes made to the unit tests.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

1. Calling `ModelVersion.deploy` with an already deployed model version passed as a parameter will redeploy the endpoint with the new configuration of the given version
2. Updating an endpoint that is in the pending state is no longer allowed

Checklist

[x] Added unit test, integration, and/or e2e tests
[x] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Unpopular opinion: can I black the entire Merlin SDK repo? Seeing how the model_test.py file got reformatted in https://github.com/caraml-dev/merlin/pull/456/files, I was wondering if we should just stick to some standard formatting :/

Unpopular opinion: can I black the entire Merlin SDK repo? Seeing how the model_test.py file got reformatted in https://github.com/caraml-dev/merlin/pull/456/files, I was wondering if we should just stick to some standard formatting :/

Doing this will make the PR huge with unrelated changes to the first intention. I rather 1) have separate formatting PR or 2) only format the file you originally modify for this PR.

have separate formatting PR

Let's do this then :) But in any case, I just updated my PR to match the formatting in that test file that was modified in that PR, so it's not urgent.

Zi Yi, can you also add new integration test for redeployment case?

Just added a new integration test for the model redeployment workflow :)


Feedback for “Windows 1click Installer”

I paid $5 for the Windows 1-Click Installer, but I didn't get a download link.

Same here, I just submitted my own thread...
Did you get yours? How?

Hi, thank you for your support! After purchasing, you will receive an email from Lemon Squeezy, in which there will be a View Order button. After clicking this button, the download page will open.


Merge with zls-vscode

Pushed (all?) the changes on the zls end, I believe all that remains is working out which parts are extension-controlled and which parts are zls-controlled :)


Update default image to 1.24.17

This PR updates the default image and k8s version.  We have this new image in the gallery and it contains teleport binary.
Trigger e2e tests
/run cluster-test-suites

The test suite doesn't overwrite image or k8s version. See https://github.com/giantswarm/cluster-test-suites/blob/main/providers/capz/upgrade/test_data/cluster_values.yaml
This change will be effective in the e2e tests.
/run cluster-test-suites

Failed with an unrelated error. Re-triggering. I will watch it closely.
/run cluster-test-suites


Just wanna be able to use the market etc.
x3nos#4460

Can't seem to find any extra info regarding your discord ban besides 'Insulting staff'. I hope you have learned to do better in time since then. I have unbanned you.


Support: How to deal with installed fonts such as fontsource/roboto

Hi,
I'm using fontsource to bundle fonts alongside my website, but the fonts are loaded as font-face css blocks when the file is imported, and that leads to the fonts not being prefetched.
I wanted to use this package to deal with that and add prefetch directives for the fonts, however I'm unsure how to configure that.
I import '@fontsource/roboto at my React entrypoint, but that is too late for a Vite plugin to see the fonts.
Any suggestions on the pattern to tackle installed fonts?

Hello @JesalR
This feature has been included in the v1.0.0
Here are the details: https://github.com/cssninjaStudio/unplugin-fonts#fontsource


feat(client-redirects): make plugin respect onDuplicateRoutes config

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[x] If this is a new API or substantial change: the PR has an accompanying issue (closes #7615) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

LGTM 👍


[Feature] Region switching feature on the xcloud page

We would like the ability to switch the region of the xcloud page (not the server region).
Especially in the Japanese store, games from other countries are often not released due to various reasons such as ratings, etc. There are a certain number of Japanese users who switch the store region to use the overseas version of the store.
Of course, we know that changing the URL will change the region of the xcloud page. However, it seems less complicated if the region can be selected from a drop-down list.

Does changing the URL really allow you to play unavailable games? I thought it was based on your IP address?

Does changing the URL really allow you to play unavailable games? I thought it was based on your IP address?

Here are the search results comparing the differences by changing only the region of the URL. (ja-JP and en-US)

As you can see, there are many games that are not available in ja-JP, such as "Dead island", "Dead space", and "Waking dead". This is despite the fact that some of these games include Japanese in the game.
These games can be played on JapanEast servers, for example, regardless of the server region.
Since this is an official xcloud specification, changing the URL region should not be subject to a ban.

Nah, I don't think Xbox care. Just play it.


Clicking on the namespace does nothing in javascript

Repro steps:

Open tutorial chase the pizza in javascript
Second step click on the namespace, nothing happens

Category should open up. Same issue with python tutorials.

this is working for me in both typescript and python (chrome / windows)

Could you double check / see if it gives any gives any errors in console or something? Not sure what it could be

main.js:1
   Uncaught TypeError: Cannot read properties of undefined (reading 'tutorialHintCounter')
at le.tutorialCardHintCallback (main.js:1:155116)
at Object.<anonymous> (main.js:1:711722)
at o (pxtapp.js:1:64003)

I think first do the start the pizza in blocks and click on the stuff and later go back and do the same one in javascript.


Inconsistent performance

Hello, whenever I try to single-weave on MCH during the Hypercharge window, there is inconsistency with latency mitigation.
Sometimes I experience no delay at all, sometimes I do, and sometimes I experience delay for n/5 times out of total 5 Heatblasts.
I dont have problems with double-weaving on normal GCDs. Only with single-weaving Richochet/Gauss Round on Heatblast during the Hypercharge window as explained above.
I'm currently using Mode 3 with Reduce Packet Delay, FPS synchronization, and Fixed FPS options disabled, I have also attached the log file below.
Do you recommend I alter any of these settings for a more consistent performance?
Thanks as always!
XivAlexander_20220121_231600_038.log
XivAlexander_20220121_231638_981.log

I tested previous versions and for some reason, .43 seems to show the best result. Feels like latency mitigation is not enough or stable for the latest version.


[OpenID Connect Discovery] A validate button for the resident Idp entity id value

Requirement
Fix for the issue enables resident Idp entity id to be used as an OIDC issuer location. Therefore the resident Idp entity id needs to be validated as a valid OIDC issuer location.
Improvement
A validate button in the UI for the resident Idp entity id .

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


proposal: cmd/go: vendor: only copy files that the Go build system recognizes

Proposal Details
Currently go mod vendor copies all files in a package except:

files whose name ends with _test.go
files named go.mod and go.sum
files whose names ends with .go and contain a go:build ignore constraint

This means that other random files are copied into the vendored directory.  For example, the vendored golang.org/x/sys/unix in the main repo includes mkall.sh, mkerrors.sh, and README.md.  There is no reason to vendor those files.
I propose that we change go mod vendor to only copy files that go build recognizes.  This is files that end with .go, .c, .cxx, .swig, and so forth.  Making this change would also require go mod vendor to look for go:embed directives and copy over all files that they mention (for example, the vendored files in GOROOT/src/cmd/vendor/github.com/google/pprof/internal/driver/html).

Maybe?  I wrote this as a proposal because it's clearly a user-visible change.  But if we want to just call the current behavior a bug, that is fine with me.
CC @matloob

On the other hand, already we have to do all sorts of tricks to force the build system to include certain C and H files. Restricting this more will be a problem. There should also be a way to tell go build that a file is actually necessary. See for example this: https://github.com/go-gl/glfw/blob/master/v3.3/glfw/build_cgo_hack.go

cc @samthanawalla
I think there are some subtleties here that make it more than just a bug. For instance, in the linked issue, https://github.com/golang/go/issues/26366#issuecomment-900748742 there's a user who wants to make sure that the LICENSE files are copied in the vendor directory.

That too is important. Some open source license require to be distributed together with the code even when vendoring. Some pragma like //go:vendor [filename] would be useful for that.

@bjorndm I'm suggesting that we copy all files that the Go build system recognizes, which includses all files with extensions .c and .h.
@matloob We already copy all files that start with metaPrefixes, including LICENSE; I don't think that should change.

@ianlancetaylor I think the main problem of go vendor, like for glfw-go  is with subdirectories that contain only C and H files without Go files. It would be nice if that could also be supported without hacks.

@ianlancetaylor Ah, got it.

@bjorndm Are you saying that that does not work today?  That seems like a separate issue from this one.

@ianlancetaylor The file I linked above is an example of the hack that is necessary to get go mod vendor to keep C and H files in subdirectories. I'm here to make sure that this hack keeps on working at least. But you are right, not needing this hack is a separate issue.

This seems reasonable to me.


Different from the output of the HF inference

Looking forward to your reply! I set the temperature=0.1, top-k=10, top-p=0.75，I think i infer the same prompt, I will get the same output, through test the hf and vllm inference, HF will get stable output then vllm sometimes get the different output. Is this normal? The parameters of the two inferences are the same and do not bring the same constraints.

I have encountered the same problem. I tested on a set of 40 cases and found that the results for 15 cases were different from the results obtained using huggingface.


Requesting non-existing identifiers returns error 500

Requesting a non-existing identifier results in a HTTP 500 error. This should not be the case. Instead the system should return error 404 so that a client can distinguish a non-existing code from a real server-side error.
Example:
Request URL
https://oskiosk.herokuapp.com:443/identifiers/1234.json
Response Body
{
"status": "500",
"error": "Internal Server Error"
}
Response Code
500
Response Headers
{
"content-type": "application/json; charset=utf-8"
}

Fixed in ffe4296.


v1.0.0 Goal

TODO:

[x] Update addon to use Ember v3.22.0 as well as modernize the syntax #122 #123
[x] Update dependency of ember-firebase-service to v8.0.0 #125
[x] Convert to TypeScript for better maintainability
[x] Move docs to simple markdown files so that we could have proper versioning for it. Then maybe at some point pick up a well known static docs system.
[x] See feasibility to use Firebase Emulator for testing instead of mock-cloud-firestore

[x] Add support for Firebase Emulator
[x] Remove mock-cloud-firestore from project

[x] Move firestoreSettings to config/environment.js
[x] Setup Firestore configurations in an instance-initializer

Will cut out a final 0.x.x release by weekend then may leave it for a while or so until I'm confident of its stability then finally bump it for 1.0.0.

🎉

🎉


What is the difference between play and replay?

When I use the replay() to run an animation, the animation doesn't work correctly (there are several multiple iterations of the animation that shouldn't be there). However, when I use the play() to run animation, it all works well, without any repetitions.
Question:

Why is this happening?
What is the difference between the play() and replay() in my case (codepen (pay attention to event listener))?

What's happens here is that you for each click adds some animation data to the timeline using .then() on each polygon. You don't redefine the animation, you add to the chain. Like an array push.
So when you use .play(), you starts playing from the timeline position where you stopped last time, and plays through the newly added animation data that you declared in the .then() function.
When you instead use .replay(), you restart the entire animation from frame 0. So each time you click now, you will add some more animation data and play from the beginning.
So the difference is that with .play() you start playing the animation/timeline from where you last stopped (with an optional parameter to shift the animation from that time on space), and with .replay() you start from the beginning of the animation/timeline.

@Sandstedt, thank you!

@Sandstedt, how can I redefine the animation? What's the method I need?

@Sandstedt, I have a lot of questions should I create a new issues every time?

@Viksna-Maxim, of course not :smile: !
If you doesn't find any answer on Github issues+mojs docs, please join the Slack channel in order to ask your questions: https://join.slack.com/t/mojs/shared_invite/zt-dcqt2syv-2ndsIdesrutP28AyAqZSfg.
Thanks a lot!

@Sandstedt, can you help? Please explain to me why this code doesn't work
const btn = document.querySelector('#btn');
const myCurve = "M0, 100 C0, 100 44.87788059660561, -39.91911058306421 55, -50 C65.12211940339441, -60.08088941693578 60.41952358273102, 29.403014378078353 70, 40 C79.58047641726898, 50.59698562192165 92.68868024988831, -14.728263011137487 95, -15 C97.31131975011169, -15.271736988862513 100, 0 100, 0 ";
const myCurve2 = "M0, 100 C0, 100 6.761905065604619, 110 6.761905065604619, 110 C6.761905065604619, 110 15, 70 15, 70 C15, 70 30, 140 30, 140 C30, 140 100, 0 100, 0 ";

const OPTS = {
    parent:         btn,
    shape:          'rect',
    fill:           'red',
    rx:             '2px',
    ry:             '2px',
    radiusX:         2,
    isShowStart:      true,
    isShowEnd:        true,
    duration:       200
};

const polygon1 = new mojs.Shape({
    ...OPTS,
    radiusY:         10,
    angle:          90,
    left:           30,
    top:            30,
    x:              {0:3},
    y:              {0:3},
});

const polygon2 = new mojs.Shape({
    ...OPTS,
    radiusY:         20,
    angle:          90,
    left:           40,
    top:            40,
});

const polygon3 = new mojs.Shape({
    ...OPTS,
    radiusY:         10,
    angle:          90,
    left:           50,
    top:            50,
    x:              {0:-3},
    y:              {0:-3},
});

const timeline = new mojs.Timeline();

timeline
.add(
    polygon1, polygon2, polygon3
);

new MojsPlayer({ add: timeline, isPlaying: true });

var isOpen = false;

btn.addEventListener( 'click', function () {

    if(!isOpen) {

        polygon1
        .tune({ angle: {90:135, easing: myCurve} })
        .replay();

        polygon2
        .tune({ angle: {90:45, easing: myCurve} })
        .replay();

        polygon3
        .tune({ angle: {90:135, easing: myCurve} })
        .replay();

        isOpen = !isOpen;
    } else {

        polygon1
        .tune({ angle: {90:135, easing: myCurve2} })
        .replayBackward();

        polygon2
        .tune({ angle: {90:45, easing: myCurve2} })
        .replayBackward();

        polygon3
        .tune({ angle: {90:135, easing: myCurve2} })
        .replayBackward();

        isOpen = !isOpen;
    }
});

@Viksna-Maxim please ask on Slack as I said... thanks.


Build with LTO in release mode by default

Enables link time optimizations by default in release mode, yielding 3-12% better performance for the entire flow.

nangate45/ibex run
Mean [s]
Min [s]
Max [s]
Relative

No LTO
256.417 ± 1.089
252.747
258.500
1.12 ± 0.01

With LTO
228.625 ± 1.979
223.222
230.904
1.00

nangate45/black_parrot run
Mean [s]
Min [s]
Max [s]
Relative

No LTO
2961.542 ± 14.714
2937.151
2987.307
1.06 ± 0.01

With LTO
2795.283 ± 26.873
2725.632
2822.192
1.00

nangate45/ariane133 run
Mean [s]
Min [s]
Max [s]
Relative

No LTO
5807.242 ± 17.377
5791.852
5832.0591
1.03 ± 0.02

With LTO
5651.473 ± 71.611
5550.869
5739.271
1.00

I've tried enabling this before, but the GUI fails to run under LTO. Have you tried running the GUI?

https://github.com/InBetweenNames/gentooLTO/issues/444

It also might be possible to compile the GUI without LTO and the other parts with, but I never looked into how that might work.

If LTO doesn't work out AutoFDO might be a more stable option https://gcc.gnu.org/wiki/AutoFDO/Tutorial

Please also give a summary of the impact on link time of using whatever option you settle on.

Full build
Linking only

No LTO
8 min 23 s
5 s

With LTO
9 min 23 s
1 min 30 s

On GCC 13.2.1, i7-9700 (8 cores)
The GUI actually works for me with LTO (Arch Linux, Qt 5.15.12). I'll try with Clang. Also, seems like the CI is failing on Clang.

If it's not possible to build only the GUI without LTO, then maybe CMake can just error if both LTO and the GUI are enabled.

If we're not going to enable it by default, there's no point in this PR. Closing it.
For future reference:

If you want to build with LTO, use -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON (or -DLINK_TIME_OPTIMIZATION=ON) when configuring
The GUI worked for me with LTO (Qt 5.15.12), so this issue may have been resolved. (Also, for CI I recommend -DBUILD_GUI=no)
Use a new-ish compiler and avoid the BFD linker (the default GNU linker). For me, BFD segfaulted with Clang. Use gold, lld, or mold. They're much faster anyway: LTO link time with Clang+any of these is about twice as fast as GCC+BFD.

We could make it the default but there needs to be an option to turn it off for developers in an edit/compile/run loop.

For sure, you don't want LTO while developing. I'll get back to this then.

@kbieganski are you still planning to get back to this?

I'm busy with other stuff at the moment, so if anyone is willing to take over, go ahead.


Atom terribly slow after .202

I got the last update (.202, Linux) and something is terribly broken. Atom never shined for it's speed, but it got completely slow after the last update.
Just scrolling (with --safe) on a ~8.000 lines CSS file hits the 100% usage of 1 of the cores of my CPU. Also, memory usage keeps increasing after every ~500 scrolled lines.

Does this happen with every file?
/cc @nathansobo

Also, doing that same thing without --safe, with the minimap, feels completely laggy and memory usage gets even bigger.
All this is on  Debian 8, x64, 64gb RAM, 8 cores CPU@3,7Ghz.
 Even with a composer.lock file that didn't even got color-highlighted (plain-text was selected, instead of JSON)

Would you be willing to capture a CPU profile and/or share the file in question?

@nathansobo Sure, I can do both things, just tell me how

@alexandernst To capture a CPU profile, open the dev tools with ctrl-alt-i or View > Developer > Toggle Dev Tools. Then go to the Profiles tab. With Collect JavaScript CPU Profile selected, click start. Then do your scrolling. It will be even slower now because we're measuring. Then click stop. You should now see the profile appear at the left and you can save it.
Email that and the file in question to me at<EMAIL_ADDRESS>Not sure if I'll be able to reproduce but I can at least see if we're doing something crazy CPU wise on the UI thread.

Another thing you could capture is a timeline of scrolling. After capturing it you can right click and choose Save Timeline Data....

There seems to be a bug with Chrome. When I try to save the timeline or the cpu profile record, I get the "Save as..." dialog, I select the file/folder where I want the files to be saved, the files get created, but they're empty. (I'm running Atom with --safe, should I run it in normal mode?)

No, that must be an issue with Electron on Linux because it works for me on Mac. Any interesting pieces of the timeline you could at least screenshot?

http://ibin.co/23E0PfdEGeYl

@alexandernst Thanks... can you switch to the "Chart" view and show me one frame's worth?

Not sure if that is what you're asking for: http://ibin.co/23E1wtfuS7f2 ?

That looks pretty bad, but I'll need it from the profile tab rather than the timeline to get more detail on what is happening...

Also, I'd be interested in a comparison of the timeline on 0.202.0 with 0.201.0. From the timeline performance doesn't look fantastic but it also doesn't seem too bad except for a couple of frames. Like roughly 30 FPS for the most part. But it's all relative depending on hardware. I'm curious about the performance degrading from the previous release and it would be nice to see a picture of that happening.

http://ibin.co/23E4NhMAR1zy

Ok, I can provide you with screenshots of .201 later today, I must go now.

Thanks very much for your time! It's tough to get a handle on some of these performance issues from a distance so this kind of information really helps.

I switched back to .201 and after some more tests, I must say that on numbers .202 is better than .201. Both the CPU usage and the memory usage in .202 is (a tinny bit) lower. Nevertheless .202 feels slower. It may be because something is blocking the UI for more time, perhaps.

Are there any outlier frames, perhaps where we're doing garbage collection, where 0.202 is worse?

Also, is it just scrolling, or other things too?

Have a look at this: http://ibin.co/23GKK7u3mDhA
Atom (.201) is spending considerably less time "Scripting"

Also, overall, .201 is rendering 99% of the frames at 60FPS, while .202 is having trouble keeping the FPS on 30.
More tips: I have the Logitech MX and I'm scrolling with the scroll wheel while unlocked (the scroll wheel doesn't make the "click" noise)

Seems we are spending a bit more time building the lines up in my tests. Here's a 2 second summary of 0.201 scrolling hard in huge.js:

Here's a 2 second summary from master:

Strange thing is there's more total time idle in the new implementation. I believe you that it feels slower, but I'm having trouble reproducing it. There's a PR that will land very soon that should boost scrolling paint performance that may make this better again. Perhaps we can pick this up once that lands next week.

Ok, I'll keep an eye on Atom updates and keep posting my findings here. Ping me when the patch is merged and released, please :)

Also, the more detailed information you can give me on what's slow based on these profiles, the better I'll be able to address it.  Thanks for your time!

Can you give me some general tips about what exactly should I be looking for? Can you show me a screenshot of a profile dump with a function that is slow?

It's all relative really. In your case we're taking too long to generate a frame when scrolling. So you perform scrolling and then take a look at that frame. Maybe do that in 0.201 and latest and compare them. How do they look different? Is there something that's taking way longer in one frame than the other.  Here's an example of me zoomed in on a frame. Compared with the version where it was faster, is anything worse? Not sure how realistic a path this is without me being able to look directly, but if I can get a good view of something clearly taking way longer, it could help. We need to get snapshot saving fixed on Linux.

@alexandernst: do you still notice significant lags while scrolling or #6733 did by any chance help with this issue? Also, #7101 is going to further improve performance, so you may want to have a look at that as well.
Any information or update on this would be very welcome: thank you! :bow:

@as-cii I'm waiting for a new release to test the changes. Will report as soon as a new release is available.

I'm closing this as this got fixed somewhere between .203 and .208


Issue#6-NAB Data Visualisation

Closing Issue #6 .....Simple Visualisation of the nyc_taxi.csv data of NAB using plotly. There are different kinds of visualisations of the same data in the .ipynb file.

Looks like the checks are failing because the data isn't present in the repo. If the file size is small then feel free to put the csv in the data folder. Otherwise, read the csv directly from a link.


Add EFO trait form - additional form validation needed

In looking over the data in the EFO_TRAIT table there is a row with the value for the SHORT_FORM column of "1001114". The correct value should be "EFO_1001114" therefore the form validation should have prevented this incorrect entry.
Also, the value for this entry needs to be updated in the database.

Another incorrect value has since been added for the row for the trait "pantothenic acid", the SHORT_FORM value in the table is CHEBI:7916, but should be CHEBI_7916.

Closed since now incorporated into specifications for new features in DepoCuration


🐞 fix: assumePayable exclude 0x08

close #386.
For minimum changes, just excludes 0x08

I don't follow why we want to exclude 0x08—it seems payable? The below does not revert
function test_payablePrecompiles() external {
  (bool success,) = payable(address(8)).call{value: 1 ether}("");
  require(success, "call failed");
}

I don't follow why we want to exclude 0x08—it seems payable? The below does not revert
function test_payablePrecompiles() external {
  (bool success,) = payable(address(8)).call{value: 1 ether}("");
  require(success, "call failed");
}

I don't understant quitely either. But the following test will revert with EvmError: Revert.
    function test_payablePrecompiles() external {
        payable(address(8)).transfer(1 ether);
    }

That example fails because .transfer only forwards 2300 gas, which is insufficient gas for the precompile to execute, there it reverts. If you check this address on mainnet or goerli you will see successful ETH transfers to it, such as https://goerli.etherscan.io/tx/0x32bac49d3b8d4200946bdcc32b8f0c4f90bcce80757410f01477c9a1f871a748
Going to close this as a result since the address is payable, and if it were not the current check would fail :)

That example fails because .transfer only forwards 2300 gas, which is insufficient gas for the precompile to execute, there it reverts. If you check this address on mainnet or goerli you will see successful ETH transfers to it, such as https://goerli.etherscan.io/tx/0x32bac49d3b8d4200946bdcc32b8f0c4f90bcce80757410f01477c9a1f871a748
Going to close this as a result since the address is payable, and if it were not the current check would fail :)

Thanks for your answer. However, address 0x8 will lead to the fail of send ETH in fuzz test unless use call to send ETH rather than transfer. In most time, we will use transfer rather call as transfer is more safe.
For the original intention of assumePayable: https://github.com/foundry-rs/foundry/issues/3631, I still suggest excluding address 0x8 in assumePayable.

You should not rely on the minimal gas forwarding of transfer for reentrancy protection, and in general you should not use transfer: https://consensys.net/diligence/blog/2019/09/stop-using-soliditys-transfer-now/

You should not rely on the minimal gas forwarding of transfer for reentrancy protection, and in general you should not use transfer: https://consensys.net/diligence/blog/2019/09/stop-using-soliditys-transfer-now/

This is really beyond my knowledge. Thanks for your time again!


postgresqlPackages.{pgvecto-rs,timescaledb_toolkit}: fix build on darwin

cargo-pgrx runs a temporary PostgreSQL cluster when building. This needs to run with unix sockets only, otherwise it breaks in the darwin sandbox.
Follow up on https://github.com/NixOS/nixpkgs/pull/357677#pullrequestreview-2456386269
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This will require a rebase with https://github.com/NixOS/nixpkgs/pull/358496 being merged.

@wolfgangwalther are you backportingor should I?


fix: add build constraint to ensure 1.11 compatibility

Fixes: #1602

Looks like there are some more in the other modules will, be adding more constraints as I find them


Failed building wheel for easydict

When I ran
pip3 install -r requirements.txt
It said:
Failed building wheel for easydict
Failed building wheel for python-gflags
Is this OK?

@deeprun If some of the module was failed on installation. You may separately install them by hands:)


Error Installing DLRS 2.11 package in a scratch org

Describe the bug
When trying to install version 2.11 of the DLRS into a scratch org, I am getting the following error: The package version is not fully available. If this is a recently created package version, try again in a few minutes or contact the package publisher.
To Reproduce
Steps to reproduce the behavior:

Create a new scratch org.
Execute sfdx force:package:install --package 04t0N000000IyYr to install version 2.11
The following error appears in the console: ERROR running force:package:install:  The package version is not fully available. If this is a recently created package version, try again in a few minutes or contact the package publisher.

Expected behavior
The terminal should ask: Grant access (y/n)? and proceed with normal installation.
Screenshots

Additional context
Running on MacOS Mojave.
Source API version 47.0.
I attempted to install version 2.9 of the application by running sfdx force:package:install --package 04tb0000000UvwL. It makes it through the command prompts but fails when trying to install with the error: Package(033b0000000Pf2A) AppExchange Package is Deprecated The AppExchange package has been deprecated and can no longer be installed.
This had been working for a few years.

**Update: ** I ran the following command for version 2.11.1: sfdx force:package:install --package 04t0N000001E2L5. I guess this bug could be closed? I wish the error message was more useful, like There is a newer version of the package you must install. But that doesn't seem like an issue for this repo.


NavigationView causes crash in Reunion-0.5 pre UWP

Describe the bug
Defining NavigationView on the MainPage throws exception with Reunion-0.5pre
Steps to reproduce the bug

Create a blank WinUI 3 for UWP application with Project Reuninon SDK.
Put NaviagionView on the MainPage.
Run the app

Expected behavior
The app to run correctly
Screenshots

Stack Trace
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 15294327) ReturnHr(1) tid(6e24) 80070490 Element not found.
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 15293FE7) ReturnHr(2) tid(6e24) 80070490 Element not found.
onecore\internal\sdk\inc\wil\opensource/wil/com.h(1256)\Microsoft.UI.Input.dll!7BA3EDAB: (caller: 7BA3F8FD) ReturnHr(1) tid(6e24) 80004002 No such interface supported
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 15293FE7) ReturnHr(3) tid(6e24) 80070490 Element not found.
'App14.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.ProjectReunion.0.5-Prerelease_0.52103.9000.0_x86__8wekyb3d8bbwe\Microsoft.DirectManipulation.dll'.
'App14.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Windows.Energy.dll'.
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 15294327) ReturnHr(4) tid(6e24) 80070490 Element not found.
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 152941D6) ReturnHr(5) tid(6e24) 80070490 Element not found.
onecoreuap\windows\wgi\winrt\display\displaycommon.cpp(411)\Windows.Graphics.dll!152944D2: (caller: 15294327) ReturnHr(6) tid(6e24) 80070490 Element not found.
onecoreuap\base\mrt\runtime\src\cresourcemanagerinternal.cpp(682)\mrmcorer.dll!14485348: (caller: 1448D98A) ReturnHr(1) tid(6e24) 80073B1F ResourceMap Not Found.
onecoreuap\base\mrt\runtime\src\cresourcemanagerinternal.cpp(575)\mrmcorer.dll!1448DA5B: (caller: 14484957) ReturnHr(2) tid(6e24) 80073B1F ResourceMap Not Found.
onecoreuap\base\mrt\runtime\src\cresourcemanagerinternal.cpp(1672)\mrmcorer.dll!1448497D: (caller: 14484E65) LogHr(1) tid(6e24) 80073B1F ResourceMap Not Found.
App14.exe has triggered a breakpoint.
Exception thrown at 0x764C46D2 (KernelBase.dll) in App14.exe: 0x00000004: The system cannot open the file (parameters: 0x80073B1F, 0x00000003).
Unhandled exception at 0x764C46D2 (KernelBase.dll) in App14.exe: 0x00000004: The system cannot open the file (parameters: 0x80073B1F, 0x00000003).
onecoreuap\base\mrt\runtime\com\winrt\core\lib\winrtresourcemap.cpp(444)\mrmcorer.dll!144DA8BB: (caller: 14087AA9) ReturnHr(3) tid(6e24) 80073B1F ResourceMap Not Found.
Exception thrown at 0x764C46D2 (KernelBase.dll) in App14.exe: WinRT originate error - 0x80073B1F : 'ResourceMap Not Found.'.
NuGet package version:
WinUI 3 - Project Reunion 0.5 Preview: 0.5.0-prerelease
Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

May 2019 Update (18362)
Yes

Device form factor
Saw the problem?

Desktop
Yes

Duplicate of https://github.com/microsoft/microsoft-ui-xaml/issues/4496

Duplicate of #4496

Saw the other one, however the root cause of this issue seems different to me. This one is in UWP and it doesn't seem to be related to brushes.

@ojhad FYI.  If this is a different issue from 4496 and this is unique to UWP we should tag it with Winui3-UWP tag as well.

@kalintodorov does the work around huoyaoyuan suggests in #4496 work for your UWP application?

Disable C++ exceptions as shown here: https://github.com/microsoft/microsoft-ui-xaml/issues/4510

@kalintodorov does the work around huoyaoyuan suggests in #4496 work for your UWP application?

No - it doesn't work.

Disable C++ exceptions as shown here: #4510

Already did that - continues to crash :)

@kalin-todorov , I'm using NavigationView here: https://github.com/Noemata/FakePOS/blob/master/FakePOS/FakePOSuwp/Views/ShellView.xaml
After disabling c++ exceptions, it's working in this app.  So there may be more in the mix than just the NavigationView in your case.

@Noemata attaching sample project here:
App15.zip

@kalin-todorov , sorry to report this, but your sample is working for me:

Hm interesting - my Win 10 is 18362.1256 and running the project with the latest preview 16.10 preview 1.

@kalin-todorov , obviously VS unlikely to be the issue, I just wanted to give you the full picture of what my side looks like.  The OS could be, or something else on your system that has gummed things up.  I have run into other problems with WinUI over UWP, but not what you're seeing.  I'm going to wait for the next release before I seriously start looking at WinUI over UWP.  It doesn't bring anything new to the table yet other than making it easy to author across UWP and desktop.  I'm hoping perf isn't degraded for the UWP side of things as that will void the prospect of considering WinUI over UWP for most of my customers (high perf TV Broadcasting apps).  Fingers crossed Microsoft keeps the UWP side of things as is or improves things even more.

FYI: upgraded the OS to 19041 and the project started to work.

@kalin-todorov , cool that you got it resolved!

Hi @kalin-todorov, you should see a fix for this bug in the upcoming WinUI 3/Project Reunion 0.8 Preview, which you can expect soon. Thanks for filing this!


Broke up the large tex file into chapter files

Issue #6

I also standardized the line length among the different files/paragraphs so it's slightly easier to read the TeX. I have a few other formatting changes I think might help but I'll propose those in a separate PR/issue


feat: bulk document tagging

Pull Request Checklist

[x] Target branch: This pull request targets the dev branch.
[x] Description: Implemented bulk tagging and untagging functionality for selected documents.
[x] Changelog: A changelog entry has been added at the bottom of the PR description.
[ ] Documentation: Relevant documentation has been updated to reflect the new functionality.
[x] Dependencies: No new dependencies were added.
[ ] Testing: Tests have been written and run to validate the changes.
[x] Code review: A self-review of the code has been performed, addressing coding standard issues and ensuring adherence to the project's coding standards.
[x] Prefix: The pull request title has been prefixed with "feat: ".

Changelog Entry
Description
This pull request implements bulk tagging and untagging functionality for selected documents, addressing the feature request in issue #3110. This enhancement improves workflow efficiency by allowing users to manage tags for multiple documents simultaneously.
Added

New UI elements for selecting multiple documents in the document list.
Functionality to display common tags for selected documents.
Bulk tagging feature to add tags to multiple selected documents at once.
Bulk untagging feature to remove tags from multiple selected documents at once.

Changed

Updated the document list interface to support multi-selection.
Modified the tag management interface to work with multiple documents.

Fixed

Resolved inefficiency in tagging multiple documents individually.

Additional Information

This feature addresses the user story described in issue #3110, where a user needed to tag multiple documents.
The implementation follows the suggestions made in the issue, including the ability to add and delete tags for selected documents.
Care has been taken to ensure that adding a tag that already exists on a document does not create duplicates, and removing a non-existent tag does not cause errors.

Screenshots or Videos

Thanks for the PR, but Document workspace will be entirely overhauled with https://github.com/open-webui/open-webui/issues/3527.


Update requirements.txt

Installed and started service.
Error:
Error: Command failed: python remind_sansprint.py Traceback (most recent call last): File "/home/nika/Applications/ReMind/remind_sansprint.py", line 12, in  import rumps File "/home/nika/.local/lib/python3.12/site-packages/rumps/init.py", line 25, in  from . import notifications as _notifications File "/home/nika/.local/lib/python3.12/site-packages/rumps/notifications.py", line 14, in  import Foundation ModuleNotFoundError: No module named 'Foundation'
So, added python requirement for Foundation.

Works fine now. :)


Error while trying to compile on Fedora 23 Cloud

I'm using this vagrant VM
All I'm really looking for is a more up to date Swift binary that imports Glibc together with Foundation, therefore i don't really need to have this fixed, i just need the binary :stuck_out_tongue_winking_eye:
cmark: using standard linker
+ cd /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/cmark-linux-x86_64
+ /usr/bin/cmake -G Ninja -DCMAKE_C_COMPILER:PATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:PATH=/usr/bin/clang++ -DCMAKE_BUILD_TYPE:STRING=Release /home/vagrant/rpmbuild/BUILD/cmark
-- The C compiler identification is Clang 3.7.0
-- The CXX compiler identification is Clang 3.7.0
-- Check for working C compiler using: Ninja
-- Check for working C compiler using: Ninja -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler using: Ninja
-- Check for working CXX compiler using: Ninja -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test HAVE_FLAG_ADDRESS_SANITIZER
-- Performing Test HAVE_FLAG_ADDRESS_SANITIZER - Failed
-- Performing Test HAVE_FLAG_SANITIZE_ADDRESS
-- Performing Test HAVE_FLAG_SANITIZE_ADDRESS - Failed
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Looking for stdbool.h
-- Looking for stdbool.h - found
-- Performing Test HAVE___BUILTIN_EXPECT
-- Performing Test HAVE___BUILTIN_EXPECT - Success
-- Performing Test HAVE___ATTRIBUTE__
-- Performing Test HAVE___ATTRIBUTE__ - Success
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.4.3", minimum required is "3")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/cmark-linux-x86_64
++ cmake_config_opt cmark
++ product=cmark
++ [[ Ninja == \X\c\o\d\e ]]
+ /usr/bin/cmake --build /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/cmark-linux-x86_64 -- -j1 all
[66/66] Linking CXX executable api_test/api_test
llvm: using standard linker
+ cd /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/llvm-linux-x86_64
+ /usr/bin/cmake -G Ninja -DCMAKE_C_COMPILER:PATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:PATH=/usr/bin/clang++ '-DCMAKE_C_FLAGS=  -fno-stack-protector' '-DCMAKE_CXX_FLAGS=  -fno-stack-protector' -DCMAKE_BUILD_TYPE:STRING=Release -DLLVM_ENABLE_ASSERTIONS:BOOL=TRUE -DLLVM_TOOL_SWIFT_BUILD:BOOL=NO '-DLLVM_TARGETS_TO_BUILD=X86;ARM;AArch64' -DLLVM_INCLUDE_TESTS:BOOL=TRUE -LLVM_INCLUDE_DOCS:BOOL=TRUE -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINTERNAL_INSTALL_PREFIX=local /home/vagrant/rpmbuild/BUILD/llvm
-- The C compiler identification is Clang 3.7.0
-- The CXX compiler identification is Clang 3.7.0
-- The ASM compiler identification is Clang
-- Found assembler: /usr/bin/clang
-- Check for working C compiler using: Ninja
-- Check for working C compiler using: Ninja -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler using: Ninja
-- Check for working CXX compiler using: Ninja -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for dirent.h
-- Looking for dirent.h - found
-- Looking for dlfcn.h
-- Looking for dlfcn.h - found
-- Looking for errno.h
-- Looking for errno.h - found
-- Looking for execinfo.h
-- Looking for execinfo.h - found
-- Looking for fcntl.h
-- Looking for fcntl.h - found
-- Looking for inttypes.h
-- Looking for inttypes.h - found
-- Looking for limits.h
-- Looking for limits.h - found
-- Looking for link.h
-- Looking for link.h - found
-- Looking for malloc.h
-- Looking for malloc.h - found
-- Looking for malloc/malloc.h
-- Looking for malloc/malloc.h - not found
-- Looking for ndir.h
-- Looking for ndir.h - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for signal.h
-- Looking for signal.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for sys/dir.h
-- Looking for sys/dir.h - found
-- Looking for sys/ioctl.h
-- Looking for sys/ioctl.h - found
-- Looking for sys/mman.h
-- Looking for sys/mman.h - found
-- Looking for sys/ndir.h
-- Looking for sys/ndir.h - not found
-- Looking for sys/param.h
-- Looking for sys/param.h - found
-- Looking for sys/resource.h
-- Looking for sys/resource.h - found
-- Looking for sys/stat.h
-- Looking for sys/stat.h - found
-- Looking for sys/time.h
-- Looking for sys/time.h - found
-- Looking for sys/uio.h
-- Looking for sys/uio.h - found
-- Looking for termios.h
-- Looking for termios.h - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for utime.h
-- Looking for utime.h - found
-- Looking for valgrind/valgrind.h
-- Looking for valgrind/valgrind.h - not found
-- Looking for zlib.h
-- Looking for zlib.h - found
-- Looking for fenv.h
-- Looking for fenv.h - found
-- Looking for FE_ALL_EXCEPT
-- Looking for FE_ALL_EXCEPT - found
-- Looking for FE_INEXACT
-- Looking for FE_INEXACT - found
-- Looking for mach/mach.h
-- Looking for mach/mach.h - not found
-- Looking for mach-o/dyld.h
-- Looking for mach-o/dyld.h - not found
-- Looking for histedit.h
-- Looking for histedit.h - found
-- Performing Test HAVE_CXXABI_H
-- Performing Test HAVE_CXXABI_H - Success
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Looking for pthread_getspecific in pthread
-- Looking for pthread_getspecific in pthread - found
-- Looking for pthread_rwlock_init in pthread
-- Looking for pthread_rwlock_init in pthread - found
-- Looking for pthread_mutex_lock in pthread
-- Looking for pthread_mutex_lock in pthread - found
-- Looking for dlopen in dl
-- Looking for dlopen in dl - found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for compress2 in z
-- Looking for compress2 in z - found
-- Looking for el_init in edit
-- Looking for el_init in edit - found
-- Looking for setupterm in tinfo
-- Looking for setupterm in tinfo - found
-- Looking for arc4random
-- Looking for arc4random - not found
-- Looking for backtrace
-- Looking for backtrace - found
-- Looking for getpagesize
-- Looking for getpagesize - found
-- Looking for getrusage
-- Looking for getrusage - found
-- Looking for setrlimit
-- Looking for setrlimit - found
-- Looking for isatty
-- Looking for isatty - found
-- Looking for futimens
-- Looking for futimens - found
-- Looking for futimes
-- Looking for futimes - found
-- Looking for writev
-- Looking for writev - found
-- Looking for mallctl
-- Looking for mallctl - not found
-- Looking for mallinfo
-- Looking for mallinfo - found
-- Looking for malloc_zone_statistics
-- Looking for malloc_zone_statistics - not found
-- Looking for mkdtemp
-- Looking for mkdtemp - found
-- Looking for mkstemp
-- Looking for mkstemp - found
-- Looking for mktemp
-- Looking for mktemp - found
-- Looking for closedir
-- Looking for closedir - found
-- Looking for opendir
-- Looking for opendir - found
-- Looking for readdir
-- Looking for readdir - found
-- Looking for getcwd
-- Looking for getcwd - found
-- Looking for gettimeofday
-- Looking for gettimeofday - found
-- Looking for getrlimit
-- Looking for getrlimit - found
-- Looking for posix_spawn
-- Looking for posix_spawn - found
-- Looking for pread
-- Looking for pread - found
-- Looking for realpath
-- Looking for realpath - found
-- Looking for sbrk
-- Looking for sbrk - found
-- Looking for srand48
-- Looking for srand48 - found
-- Looking for lrand48
-- Looking for lrand48 - found
-- Looking for drand48
-- Looking for drand48 - found
-- Looking for strtoll
-- Looking for strtoll - found
-- Looking for strtoq
-- Looking for strtoq - found
-- Looking for strerror
-- Looking for strerror - found
-- Looking for strerror_r
-- Looking for strerror_r - found
-- Looking for strerror_s
-- Looking for strerror_s - not found
-- Looking for setenv
-- Looking for setenv - found
-- Looking for dlerror
-- Looking for dlerror - found
-- Looking for dlopen
-- Looking for dlopen - found
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test HAVE_INT64_T
-- Performing Test HAVE_INT64_T - Success
-- Performing Test HAVE_UINT64_T
-- Performing Test HAVE_UINT64_T - Success
-- Performing Test HAVE_U_INT64_T
-- Performing Test HAVE_U_INT64_T - Success
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
-- Performing Test LLVM_HAS_ATOMICS
-- Performing Test LLVM_HAS_ATOMICS - Success
-- Performing Test SUPPORTS_NO_VARIADIC_MACROS_FLAG
-- Performing Test SUPPORTS_NO_VARIADIC_MACROS_FLAG - Success
-- Target triple: x86_64-unknown-linux-gnu
-- Native target architecture is X86
-- Threads enabled.
-- Doxygen disabled.
-- Sphinx disabled.
-- Go bindings disabled.
-- Could NOT find OCaml (missing:  OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- Could NOT find OCaml (missing:  OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- OCaml bindings disabled.
-- Performing Test LLVM_NO_OLD_LIBSTDCXX
-- Performing Test LLVM_NO_OLD_LIBSTDCXX - Success
-- Performing Test C_SUPPORTS_FPIC
-- Performing Test C_SUPPORTS_FPIC - Success
-- Performing Test CXX_SUPPORTS_FPIC
-- Performing Test CXX_SUPPORTS_FPIC - Success
-- Building with -fPIC
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG - Success
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Success
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Success
-- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR
-- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR - Success
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP - Success
-- Performing Test CXX_SUPPORTS_CXX11
-- Performing Test CXX_SUPPORTS_CXX11 - Success
-- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS
-- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS - Success
-- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS
-- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS - Success
-- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS
-- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS - Success
-- Performing Test C_SUPPORTS_FDATA_SECTIONS
-- Performing Test C_SUPPORTS_FDATA_SECTIONS - Success
-- Performing Test CXX_SUPPORTS_FDATA_SECTIONS
-- Performing Test CXX_SUPPORTS_FDATA_SECTIONS - Success
-- Found PythonInterp: /usr/bin/python2.7 (found version "2.7.10")
-- Constructing LLVMBuild project information
-- Targeting X86
-- Targeting ARM
-- Targeting AArch64
-- Clang version: 3.8.0
-- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG
-- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Success
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    LLVM_TOOL_SWIFT_BUILD

-- Build files have been written to: /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/llvm-linux-x86_64
++ cmake_config_opt llvm
++ product=llvm
++ [[ Ninja == \X\c\o\d\e ]]
+ /usr/bin/cmake --build /home/vagrant/rpmbuild/BUILD/build/buildbot_linux/llvm-linux-x86_64 -- -j1 all
[1370/1921] Building CXX object tools/clang/lib/ASTMatchers...namic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o
FAILED: /usr/bin/clang++   -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/clang/lib/ASTMatchers/Dynamic -I/home/vagrant/rpmbuild/BUILD/llvm/tools/clang/lib/ASTMatchers/Dynamic -I/home/vagrant/rpmbuild/BUILD/llvm/tools/clang/include -Itools/clang/include -Iinclude -I/home/vagrant/rpmbuild/BUILD/llvm/include -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3    -UNDEBUG  -fno-exceptions -fno-rtti -MMD -MT tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o -MF tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o.d -o tools/clang/lib/ASTMatchers/Dynamic/CMakeFiles/clangDynamicASTMatchers.dir/Registry.cpp.o -c /home/vagrant/rpmbuild/BUILD/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp
clang: error: unable to execute command: Killed
clang: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 3.7.0 (tags/RELEASE_370/final)
Target: x86_64-redhat-linux-gnu
Thread model: posix
clang: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
clang: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /tmp/Registry-482878.cpp
clang: note: diagnostic msg: /tmp/Registry-482878.sh
clang: note: diagnostic msg:

********************
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1, aborting
./utils/build-script: command terminated with a non-zero exit status 1, aborting
error: Bad exit status from /var/tmp/rpm-tmp.0kt808 (%install)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.0kt808 (%install)

Apparently it was a just an issue caused my the amount of RAM i allocated to the VM :confused: .
And with that, I've finally built something a bit more recent :smiley: .
Here it is if anyone is interested.


Camera for windows failed to initialize camera on some camera such as Elgato Facecam Pro or OBSBot

What package does this bug report belong to?
camera
What target platforms are you seeing this bug on?
Windows
Have you already upgraded your packages?
Yes
Dependency versions
name: test_camera
description: "A new Flutter project."
version: 1.0.0+1
environment:
sdk: '>=3.2.6 <4.0.0'
dependencies:
flutter:
sdk: flutter
camera_platform_interface: ^2.1.2
camera_windows: ^0.2.1+9
cupertino_icons: ^1.0.2
dev_dependencies:
flutter_test:
sdk: flutter
flutter_lints: ^2.0.0
uses-material-design: true
Steps to reproduce

Connect 2 webcam. one logitech Brio 4 webcam and one Elgato Facecam pro
Start window's default camera application to verify both camera is working in windows.
Run camera_windows example code and 2 cameras was found
Switch camera to logitech webcam and press create camera and preview is displayed.
Switch camera to Elgato Facecam Pro and press create camera, Error message appear "Failed to initialize camera: camera_error: Failed to initialize video preview".

Expected results
Since both webcam is working normally in default windows camera application, it should work normally in flutter.
Actual results
In general, normal/generic webcam is working fine wht camera_window but some more expensive webcam such as OBSBot Tiny, Instra360 Link and most recently Elgato Facecam Pro do not work and having problem when it try to connect and initialize preview.
Code sample
Code sample
  Widget _buildPreview() {
    return CameraPlatform.instance.buildPreview(_cameraId);
  }

Screenshots or Videos

Screenshots / Video demonstration
https://youtu.be/B3ctjTXAQh0

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.16.9, on Microsoft Windows [Version 10.0.22621.3007], locale en-AU)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[X] Android toolchain - develop for Android devices
    X Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.5)
[!] Android Studio (not installed)
[√] VS Code (version 1.86.0)
[√] Connected device (3 available)
[√] Network resources

This looks similar to https://github.com/flutter/flutter/issues/140014 so please follow-up in it for further updates.
Closing as duplicate. If you disagree, write in comments and I'll reopen it.


Checksum Console Warning

Markup changes (ex: add

 to any component w/ style included) cause this checksum console warning:

Current work-around is to restart DEV.

Something here might be able to fix it? Warning: pretty long 😆  (i didnt read it all yet)
explanation on why this happens and what he did there (but its pretty old)

So not sure if you want to close this or not but i've experienced a few times where this happened to me.
In all cases, it is actually a valid warning. It means that you have some code on the client that does not match what your server returns - which is true.
I've also had some cases (with redux-form) where this warning persisted even after a server restart but still it was a valid warning and i had to do something to make it go away correctly.

We're trying to clean up the project and close issues.
We didnt hear back from you regarding this so i'll assume it was resolved.
In case you still have an issue with this, please comment here or open a new issue.


Fix TLSChallenge certificate test flake and increase cert expiry date

Description
Fix TLSChallenge certificate test flake and increase cert expiry date.
The cert expires now after ~200years for the load balancer.
Additionally the documentation was improved to make it easier to exchange certificates if necessary.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

Run unit tests

Why is there an empty operator/helm_deploy/deploy.yaml file?


Include support for updating multiple fields in management command

Describe the problem
We have a system which needs different configs at different times (e.g. weekday/weekend). Rather than implement multiple fields in Constance to support these different contexts, it would be convenient to have a scheduled task which changes the necessary fields at certain times. Then from a maintenance perspective, we won't need to implement multiple fields for a given behaviour; instead we can maintain a config and just update it when we need to.
In order to do this, it would be good to support updating a list of fields in the management command, rather than just one.
Steps to reproduce
No reproduction.
System configuration
Feature request for all configurations.

To do this you can always create a custom command.
Also, you can propose your realisation as a PR that the community will discuss.