Make all navigation links from Recent topics row go to topic

In Recent topics, it's easy to accidentally click on a stream and end up in the interleaved stream view when one is actually trying to go to a topic.
To address this, we should have all navigation clicks anywhere on a row in the Recent topics (other than the mute button, etc.) go to the topic, rather than the interleaved stream view. This should feel intuitive, as the entire row represents the topic.
CZO discussion

Closing in favor of #22621.


Step overlaps duration for some step names

See

I believe the prefix of running is redundant any way. Perhaps the easy fix is to trim the step name down?

It might sound redundant. The status of this build is running, and the current step is runningPostRolloutTasks the step changes throughout the build process, so is an indicator of where it is at.
If the idea is to trim the steps, then this needs to be raised in the build-deploy-tool.
For now I think if the screen size is adjusted, shifting the location of the build step to below the status would solve this problem pretty well.


More webfont formats

http://ranf.tl/2014/12/23/self-hosting-google-web-fonts/

Coverage remained the same at 48.427% when pulling 2d12b15c16f9ec85fc0fb9081e4f02d0c4a0ff8f on font-formats into 52c14885b64eb0f859a5264c42fd58c9d09ba664 on master.

Coverage remained the same at 48.427% when pulling 58210557fa8ac5800d0c81abc5655affac3a696b on font-formats into 52c14885b64eb0f859a5264c42fd58c9d09ba664 on master.


Merge demo to master

Since upstream code (cli.py) already has dummy code inside (which I was mistaken to think that it wasn't,) it would be better to take them out after merging these changes.

merging seems better.


Add "Restart app" button to Developer Settings

... using Process Phoenix. Enhancement #58

Current coverage is 81.14%

Merging #152 into master will decrease coverage by -0.44% as of 5eea90b

@@            master    #152   diff @@
======================================
  Files           38      38
  Stmts          554     557     +3
  Branches        47      47
  Methods          0       0
======================================
  Hit            452     452
  Partial         29      29
- Missed          73      76     +3

Review entire Coverage Diff as of 5eea90b

Powered by Codecov. Updated on successful CI builds.

:+1:

:+1:

:+1:

Thanks!


Derivative of jitted function gives NaN, but derivative of regular function gives 0

Description
jax.jit(lambda x, k: x**k)(0.0, 0)

this gives Array(1., dtype=float64, weak_type=True) as expected
jax.jacfwd(lambda x, k: x**k)(0.0, 0)

gives Array(0., dtype=float64, weak_type=True) as (I think) expected - x**0 == 1 for all x, and derivative of a constant is zero.
jax.jacfwd(jax.jit(lambda x, k: x**k))(0.0, 0)

this gives Array(nan, dtype=float64, weak_type=True) Which seems possibly wrong, or at least inconsistent.
The same behavior holds true whether its the inner function that gets jitted or the jacobian funtion, and in both forward and reverse mode
What jax/jaxlib version are you using?
jax version=0.4.13, jaxlib version=0.4.13
Which accelerator(s) are you using?
CPU
Additional system info
No response
NVIDIA GPU info
No response

Thanks for the report!
I believe this issue was fixed by #17996; if you upgrade to jax version 0.4.19 or later you should see the expected output.


Destroy method is not working as expected

Description

I don't know why, but this lib create <svg /> and insert it into end of body tag when we call chart.render()
That's OK!
But when i call chart.destroy() this svg never remove from DOM !!
Steps to Reproduce

Render chart
Try to destroy it
DOM will not clear as we expected

Expected Behavior
We must have a clean DOM after calling chart.destroy()
Actual Behavior
<svg /> will remain in <body /> even after calling chart.destroy()
Reproduction Link
https://cdpn.io/SaeedPooyanfar/fullpage/LYmQqJV
https://codepen.io/SaeedPooyanfar/pen/LYmQqJV
Click on ApexCharts#destroy button and check DOM

Hello, I see the  being removed on button click as expected. I used your codepen link.

I also cannot reproduce using your codepen link. It works as expected.

@AlexParton
@brianlagunas
The chart itself yes
But look at the latest tag in body
I see a SVG element there that created by the lib.

This is causing problem running unit tests (with jest) https://github.com/apexcharts/react-apexcharts/issues/427


Fix BBR handshake and guarantee timely measurements

This change is

By "please do the cleanups" I mean "please do the cleanups I explicitly called out in other comments". The testing+refactoring could be done in this PR or the next one: your choice.

(Oh, and thanks for the fine review!)


Fixes for XR animation frame loop

Fixes:

Issue #115: rework xrSession.requestAnimationFrame to use a single device frame handler and a list of callbacks, to match the spec algorithm and prevent multiple vrDisplay.submitFrame calls per frame
Issue #114: Instantiate new XRFrame on each frame and each input source event dispatch
Add active and animationFrame booleans to XRFrame, toggle them appropriately, and check them during pose population per spec

Notes for Review:

Given how central the frame loop is, please be very critical in reviewing this logic.
My testing has been only on Oculus Quest, and only via my own framework code [edit: and the webxr-samples repo]. I would appreciate help testing on other devices, and if there are some other good testcases out there I should be aware of to run this against I'd love to know about them.
The test-xr-session.js test file is busted so I haven't added anything there to test these changes, but I'd feel much better if I could, so I may try to at least get that one into a runnable state so I can add to it.
I removed the suspendedCallback in favor of the callbacks array, and I think the logic around suspension (pausing/restarting the device frame loop) is correct, but I don't know how to actually test the suspension. Tips welcome.

No worries! As conflicts go this is an easy one to unwrap, but thank you for the resolution tips.
Your other comments all make perfect sense, I'll work through them shortly.

Conflicts are resolved (via rebase) and all the fixes from that first round of code review have been made.
I've now tested this with the webxr-samples repo without issue, but still welcome additional testcase sources. As well as hints around how to test the session suspension logic.

Looks great! Thank you so much!


Support for manifest location in  tag

Is your feature request related to a problem? Please describe.
Website manifests don't necessarily remain in the same location when the site is updated.
Describe the solution you'd like
Add support for locating the manifest using a  tag from the website content.

Example of a site with URL encoded manifest: https://privacy.samsunginter.net/
Their manifest tag looks like this:
<link rel="manifest" href="data:application/manifest+json,%7B%0A%09%22dir%22:%20%22ltr%22,%0A%09%22lang%22:%20%22en%22,%0A%09%22name%22:%20%22Security%20and%20Privacy%20Wizard%22,%0A%09%22short_name%22:%20%22Security%20and%20Privacy%20Wizard%22,%0A%09%22scope%22:%20%22https://privacy.samsunginter.net/%22,%0A%09%22display%22:%20%22standalone%22,%0A%09%22start_url%22:%20%22https://privacy.samsunginter.net/%22,%0A%09%22url%22:%20%22https://privacy.samsunginter.net/%22,%0A%09%22background_color%22:%20%22rgb(242,%20242,%20242)%22,%0A%09%22theme_color%22:%20%22rgb(242,%20242,%20242)%22,%0A%09%22description%22:%20%22This%20guide%20will%20help%20you%20make%20Samsung%20Internet%20be%20as%20secure%20as%20possible%20and%20explain%20how%20it%20protects%20you.%22,%0A%09%22orientation%22:%20%22any%22,%0A%09%22related_applications%22:%20[],%0A%09%22prefer_related_applications%22:%20false,%0A%09%22icons%22:%20[%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-512-512.png%22,%0A%09%09%09%22sizes%22:%20%22512x512%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/maskable_icon.png%22,%0A%09%09%09%22sizes%22:%20%22682x682%22,%0A%09%09%09%22type%22:%20%22image/png%22,%0A%09%09%09%22purpose%22:%20%22maskable%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-192-192.png%22,%0A%09%09%09%22sizes%22:%20%22192x192%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-144-144.png%22,%0A%09%09%09%22sizes%22:%20%22144x144%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-96-96.png%22,%0A%09%09%09%22sizes%22:%20%2296x96%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-72-72.png%22,%0A%09%09%09%22sizes%22:%20%2272x72%22%0A%09%09%7D,%0A%09%09%7B%0A%09%09%09%22src%22:%20%22https://privacy.samsunginter.net/assets/icons/images/android-launchericon-48-48.png%22,%0A%09%09%09%22sizes%22:%20%2248x48%22%0A%09%09%7D%0A%09]%0A%7D%0A">


Add lineDotDash option to ol.style.Stroke

It would be nice to have an extra lineDotDash option in ol.style.Stroke for dot-dash pattens.
Type Array. | undefined.
The array would hold 4 values:

line width
width between elements (lines or dots)
number of consecutive dashes
number of consecutive dots

ol.style.Stroke already has a lineDash option; what would this new option provide?

With lineDash you draw a patten like "- - -"
With lineDotDash you would be able to draw like "- . - . -" (with dots on the same level as dashes).

With lineDash you get anything you want, depending on your dash array. For a dash-dotted line, try a dash array like [9, 3, 3, 3].


wget return 302

wget https://github.com/wagoodman/dive/releases/download/v0.9.2/dive_0.9.2_linux_amd64.deb
--2023-01-26 11:57:41--  https://github.com/wagoodman/dive/releases/download/v0.9.2/dive_0.9.2_linux_amd64.deb
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found

Latest version is v.0.10.0 tho

same thing
wget https://github.com/wagoodman/dive/releases/download/v0.10.0/dive_0.10.0_linux_amd64.deb
sudo apt install ./dive_0.10.0_linux_amd64.deb
--2023-01-26 12:15:23--  https://github.com/wagoodman/dive/releases/download/v0.10.0/dive_0.10.0_linux_amd64.deb
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found

No idea, tried it in a ubuntu container and it completed successfully.
Does wget download the file?

dive_0.10.0_linux_amd64.deb.4                     0%[                                                                                ]       0  --.-KB/s    in 0s

Alright, so it's a networking issue.
Are you behind a VPN, or in a country that has internet limitations or something of sorts?
Can you wget anything off of the internet?

You are right. I can't download anything.
I use virtual box. Could it be because of this?

Could be.
Do you have internet access inside the machine at all?
In any case, it's not a dive issue.

I have internet. I can clone this project, for example.
Thanx. I close issue and resolve this problem.


Fix rule offset

Codecov Report
Patch coverage: 100.00% and project coverage change: -1.23 :warning:

Comparison is base (28696a0) 77.34% compared to head (de48eff) 76.12%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #759      +/-   ##
==========================================
- Coverage   77.34%   76.12%   -1.23%
==========================================
  Files          18       18
  Lines        7377     7354      -23
==========================================
- Hits         5706     5598     -108
- Misses       1671     1756      +85

Impacted Files
Coverage Δ

src/compiler.jl
77.78% <100.00%> (-0.09%)
:arrow_down:

... and 6 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


use pdo instead of deprecated mysqli functions

not gonna toot my own horn, but you'll see some minor security fixes here too.

Accepted. Thanks for doing this: I haven't had the time or interest to overhaul the PHP stuff, especially the example web interface elements. The caveat in the readme was my attempt to not screw people over with outdated code, but this definitely preferable.

Not a problem. I was looking to use it and noticed the code used. I wanted to help you build something that I, and others, will be able to use in the future php7 which afaik is default in Ubuntu and some other distros


WIP: added basic summary actions with text-summary

I thought it'd be nice to have a summary of the text submitted to cacador. The text-summary library looked like a good candidate, but the results have been less than excellent.
From the Equation report:

"What is the Equation group?  What is the Equation group?  002.  002.  001.  002.  001.  002.  001.  002.  002.  002.  002.  002.  001.  001.  001.  001.  002.  001.  Win32.  Win32.  Win32.  Win32.
EquationDrug.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Wi
n32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  EquationDrug.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  Win32.  EquationDrug.  EquationDrug
.  Win32."

Doesn't seem terribly useful, but perhaps I'm using the library wrong or need a different library. We'll see.

Maybe try again with an online service?

http://autosummarizer.com/index.php

After a lot of consideration and playing with number of options I think I'm calling this one a nice to have but not doable at this time. Too many variables to be useful.


Bug: combat grid has heroes on wrong side

some of the dire heroes are with radiant and vice versa
https://www.opendota.com/matches/3465425218/combat

Huh, refreshed and went away. I had been browsing through the different tabs when this happened.
Maybe had to do with turning off heroes in the gold graph?

If you can find a reliable repro please share

this is reliable for me
Go here:
https://www.opendota.com/matches/3506394403/laning
sort by eff@10 and then click Combat
Browser:
Google Chrome
Version 61.0.3163.100 (Official Build) (64-bit)
Microsoft Windows 10

Ah OK, it seems the problem has to do with the sorting reordering the players so that 1-5 are no longer radiant and 6-10 are no longer dire.

Starting on this, trying my best :)


Restoring doesnt put messages into SMS anymore

I just got a new Samsung Note 3 and installed your software and signed in and did a restore ( I use it all the time on my note 2 worked great ) anyway I did a restore and it was restoring all my message (9034) or so of them and then when it finished I opened up Messages and nothing was there.. They went somewhere but not there.. What do I need to do .. Please Help
I am using versions:
Android Version - 4.3
SMS Backup+ Version - 1.5.5
Please let me know what I need to do to get them all back..
Thanks again
Patrick

Hello can I get this app on my new iPhone?
On Friday, November 21, 2014, Jan Berkel<EMAIL_ADDRESS>wrote:

Closed #379 https://github.com/jberkel/sms-backup-plus/issues/379.
—
Reply to this email directly or view it on GitHub
https://github.com/jberkel/sms-backup-plus/issues/379#event-196770638.


gumbel-softmax  in fairseq

I would like to test your code  with the transformer architecture in fairseq.
Have you ever tried?
Could you please suggest me the better way to do that?

It's not my code. I just fork it. I think you should ask the code writer.
At 2019-10-02 00:33:15, "Nicola Bertoldi"<EMAIL_ADDRESS>wrote:
I would like to test your code with the transformer architecture in fairseq.
Have you ever tried?
Could you please suggest me the better way to do that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@jianfeidahai
I did not find which repo you fork from?
Could you please point me to the original code writer?

https://github.com/ericjang/gumbel-softmax
At 2019-10-03 21:46:56, "Nicola Bertoldi"<EMAIL_ADDRESS>wrote:
@jianfeidahai
I did not find which repo you fork from?
Could you please point me to the original code writer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jianfeidahai
Actually I opened my issue (i.e. this one) on
https://github.com/ericjang/gumbel-softmax
Maybe @ericjang can help me.


Add Newsletter Subscription Option to Footer

Title and Issue number

Title :  Add Newsletter Subscription Option to Footer
Please review this changes and approve
Issue No. : https://github.com/apu52/METAVERSE/issues/1052
Code Stack :
Close #1052

Video (mandatory)
not able to attach video
Before

After

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

[x] I'm a GSSOC'24 contributor
[x] I'm a SSOC'24 contributor

Hello @apu52 ,
Please review the changes at your earliest convenience and consider merging them. Thank you!


Can't use my Existing Laravel Project

Can you solve this issue or install this repo in my existing laravel project

Can you provide me with further information?

Can you provide me with further information?

I have already laravel news project, I need to install this repo on my project, when I installed it then your all default template and database table replace my existing projects.
I need to use only generator, please help me on this script
Thank you

Sorry sir, but according to README.md, this package will overwrite several files by default.
Just using the generator would be a great alternative.
I apologize, but not soon, but I will add that feature.
kind regards.


docs(storybook): add theme playground

fix #35

:tada: This issue has been resolved in version 0.14.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


base64 and encryption

Add base64 encoding method and enhance parameters encryption

Now that’s what I’m talking about


Error while generating a project using WhiteSource Bolt template

Hi Team,
As a part of DevOps training & developer challenge, I was required to create a project in Azure DevOps using the Azure DevOps Demo Generator with WhiteSource Bolt (to be renamed to Mend Bolt) template. Unfortunately, the project creation failed with below error:
Error while creating build definition: The pipeline is not valid. A task is missing.
The pipeline references a task called '58dccf9e-3eaf-4533-a9b6-1e5a1845d036'.
This usually indicates the task isn't installed, and you may be able to install it from the Marketplace: https://marketplace.visualstudio.com. (Task version 21.*, job 'Phase_1', step ''.)

Please assist.
AB#3936

After installing the Mend Bolt plugin from marketplace, receiving below error:
Error while creating release definition: Tasks with versions 'ARM Outputs:6.*' are not valid for deploy job 'Agent job' in stage Stage 1.

for some reason, recreating the project worked just fine. 😃


Scroll to created org

Description
Scroll to created org
Fixes #2457
Type of change

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

How Has This Been Tested?

manually

Checklist:

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

@hetunandu found an issue, have updates the ids to use slug instead of orgName

@hetunandu found an issue, have updates the ids to use slug instead of orgName

@hetunandu have pushed the updates

@hetunandu have pushed the updates


Add repo contributors

@all-contributors please add @beardaway for review, maintenance

@all-contributors please add @damieng  for code, review and maintenance


GL vs GL ES GPU counter differences

Description
Using the GPU counters for GL ES on Android there are a few interesting results/findings:

We get GL_INVALID_ENUM error when glBeginQuery is called for GL_SAMPLES_PASSED and it results in a wrong value (-1) for the Samples Passed performance counter on Android.
Officially there is no GL_SAMPLES_PASSED in GLES but we could use GL_ANY_SAMPLES_PASSED instead.

Also, there is no GL_QUERY_BUFFER and GL_QUERY_BUFFER_BINDING in GLES, and it causes errors when glGetIntegerv and glBindBuffer are called with these targets.

When we fetch the table again and glGenQueries called, the error check will detect these previous errors for the invalid enums, and the query will be deleted. It will result in a wrong (negative or NaN) value to be displayed in the table for the GPU duration. We could clear GL errors after every fetching.

In GLES, GL_TIME_ELAPSED is provided by the EXT_disjoint_timer_query extension, so it would be good to check for safety whether it is supported or not.

An example of the wrong values on Android:

EID
GPU duration
Samples Passed

5
-1000000.00 µs
18446744073709551615

8
770.312 µs
18446744073709551615

9
50.469 µs
18446744073709551615

A possible fix for this issue is here: https://github.com/tabikati/renderdoc/commit/84d4ea99f6a0aeb55b48d0e2f8bd2879e1836685
I will create a pull request if you would like.
Environment

RenderDoc build: v1.x, 2019-07-02
Operating System: Android 7.0
API: OpenGL ES

That commit should fix this with the correct extension checks.

It has fixed the problem, thank you. Can we query GL_ANY_SAMPLES_PASSED for GLES?

I don't see any value in providing that counter since it provides virtually no useful information.


extend HTTPClientProvider with createNew on provided EventLoopGroup

Is your feature request related to a problem? Please describe.
In my (limited) experience with AWSSDKSwift/Soto I find that typically I want to share the event loop but dont
really need/care about the HTTP client implementation as such. (And would rather not need to manage its lifecycle.)
Describe the solution you'd like
It would be convenient to make AWSClient create new HTTP client on provided EventLoopGroup
and have it manage the HTTP client lifecycle.
AWSClient(httpClientProvider: .createNewOnSharedEventLoopGroup(eventLoopGroup))

(not sure about the naming)
Describe alternatives you've considered
Its possible to create a HTTP client and provide it to the AWS client.
This requires creating/importing HTTP client and managing its lifcycle.

Ok sounds fine. Maybe call it .createNewUsingEventLoopGroup.


what type of payload?

What type of payload can you add there?

Hi @soermejo, the pei tool inject raw binary code on the entry point of the PE executable. It's means you need to write the payload by hand in Assembly.
Just a PoC to you see it's running:
// poc.c
#include <stdio.h>

int main(void)
{
    register long int x asm("r15");

    printf("R15: %ld\n", x);
}

; poc.asm
bits 64

mov r15,<PHONE_NUMBER>

And compile using MinGW (I am using Linux):
x86_64-w64-mingw32-gcc poc.c -o poc.exe
nasm poc.asm -o poc.bin
pei -f poc.bin inject poc.exe

Output:

If you wanna see a full payload running, I ran msfvenom's payloads and that works.
Note: See op_inject function to learn how it's exactly inject the code.

Thanks


Cluster group suggestion

Is it possible to have cluster groups?
Imagine for example that we have the setup:
2 servers running X services
2 other servers running Y services
And we would like to keep the connection with the 4 servers, but without having to remove cluster windows and adding the others, because some commands exist in a server, but no in another.
Shortcuts like Ctrl + Alt + PgUp + 1 (repeat for N windows on group 1)
Shortcuts like Ctrl + Alt + PgUp + 2 (repeat for N windows on group 2)

Better late then never :yum:
Check out the latest release - I have added support for grouped clusters. You can find more infos in the project's README.


Small typo in the Makefile.

In the first line it says: "dynamic window manager", instead of "back ground setter".

@tfarina I guess if you delve further into the [dwm] (http://dwm.suckless.org/) project you'll find the answer.
I was looking for dead simple background setter for a long time, nitrogen is pretty much overkiller, so hats off to @Gottox for utilizing the `dwm' codebase as starting point.

awkward... But to make things clear: source is completely written by me, only the Makefile is from suckless.

I can't agree with you as your source code is 99% identical to the one in `dwm'.
If needed I can copy and paste every single line of your source code here, and do line by line comparison.
As I said, I am grateful for your work and the fact that you have utilized their codebase.

Well, I used to be an active dwm contributor. And why should I do things differently if they're good? :)

I'm not against reusing someone else's codebase or part of it.
I did contributed [statusbar] (http://dwm.suckless.org/dwmstatus/dwm-bar.c) program too.


BedRock macros widths and declarations are strongly coupled

If you try to use
`declare_bp_bedrock_mem_if(paddr_width_p, uce_mem_data_width_lp, lce_id_width_p, lce_assoc_p, uce);

without
`declare_bp_bedrock_mem_if_widths(paddr_width_p, uce_mem_data_width_lp, lce_id_width_p, lce_assoc_p, uce)

it will complain of a missing payload width declaration.  To fix, can either:

pass in the payload_width_lp as a parameter
recalculate payload width internally in declare_bp_bedrock_mem_if, using ____payload_width_lp = to obfuscate the name.

@dpetrisko can you take a look at this commit: https://github.com/black-parrot/black-parrot/commit/c48fe7dfeac7647c3ac217498f5ef2c6e2364c2a
I think it fixes the problem (the ME testbench compiled and ran without issue using vcs)

Perfect!


Brushed items sometimes don't get bigger

It seems that it only happens if the brush is set in one of the groups above an aggregated group.

Solved by removing fish-eye.


Features and Improvements statement: "The Azure AD Connect Health agent was updated to the latest version <IP_ADDRESS>"

Hello. I wonder if we should include in this statement the version release history of the agent here: https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health-version-history#june-2018  -That page includes the bugfixes of the health agent. Thank you.

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

ID: b5bc6d02-8ce9-e15d-4221-4aad75db260a
Version Independent ID: 8a375b59-d371-361a-b77f-3658059b4bee
Content: Azure AD Connect: Version release history
Content Source: articles/active-directory/connect/active-directory-aadconnect-version-history.md
Service: active-directory
GitHub Login: @billmath
Microsoft Alias: billmath

Good suggestion! I made a pull request to add a link to the release notes.


fix: treat multipart form as form

adds a more robust way to parse and check media types (case-insensitive, and aware of parameters, i.e. charset=utf-8)
updates parseFileUploadRequest to check if the media type is a multipart formdata rather than isFile=true

@abvthecity looks like an ete test is failing, otherwise this looks great


Dev/capture eye data

Add EyeGazeData ROS message which contains eye gaze origin and direction, as well as info about what object was being looked at (if any).
Add EyeGazeData capture & publish C# script.
Eye calibration must be performed on the HL2 if it hasn't been already.
https://docs.microsoft.com/en-us/windows/mixed-reality/mrtk-unity/features/input/eye-tracking/eye-tracking-basic-setup?view=mrtkunity-2021-05#eye-calibration

I think you will need to rebase on the updated master and resolve these conflicts such that the Unity scene is not in a bad state.

I think you will need to rebase on the updated master and resolve these conflicts such that the Unity scene is not in a bad state.

I think this should be good now. I built and tested on my end and things seem to be working.


feat: add hashicorp/copywrite

hashicorp/copywrite: Automate copyright headers and license files at scale
$ aqua g -i hashicorp/copywrite

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ copywrite --help
Copywrite provides utilities for managing copyright headers and license
files in HashiCorp repos.

You can use it to report on what licenses repos are using, add LICENSE files,
and add or validate the presence of copyright headers on source code files.

Usage:
  copywrite [command]

Common Commands:
  headers     Adds missing copyright headers to all source code files
  init        Generates a .copywrite.hcl config for a new project
  license     Validates that a LICENSE file is present and remediates any issues if found

Additional Commands:
  completion  Generate the autocompletion script for the specified shell
  debug       Prints env-specific debug information about copywrite
  dispatch    Dispatches audit jobs for a list of repos
  help        Help about any command
  report      Performs a variety of reporting tasks

Flags:
      --config string   config file (default ".copywrite.hcl")
  -h, --help            help for copywrite
  -v, --version         version for copywrite

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

Reference

README.md

https://github.com/hashicorp/copywrite/blob/main/README.md

Thank you!

v4.31.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.31.0


Remove unrequired vars file include

Move the cinder_service_port to maas defaults and remove the vars file
include for cinder default vars.
Fixes: #534

:+1: rebase

:+1: rebase please


Test effect of issue #11

I see you already moved it. OK, I will test and see if there are any issues.
Test that
self.client_node = rospy.init_node("qsr_lib_ros_client_example")  # needed for rospy.get_rostime() in the request method

that was moved from qsrlib_ros_client.py to example_ros_client doesn't  cause a problem with
req.header.stamp = rospy.get_rostime()

in qsrlib_ros_client.py/QSRlib_ROS_Client/make_ros_request_message

Can't change labels? Can't assign it to myself?

I made you an admin of this repo so now you should be able to do that.
As I said, tested it for qtc. Please test it for rcc. But it can't break anything. If it does we have to think of something else because it cannot stay the way it was.

I assume this didn't cause any problems as we all ran the lib and no one complained ;)


Support deep schemas: objects in objects, objects in arrays, arrays in objects, arrays in arrays etc.

@IonicaBizau, when in the definition of an object it is specified addField: true or editableFields: true should it be automatically allowed to add objects inside that object, edit the label and name of the objects inside that object and edit non-object fields to become subobjects, or there should be other properties such as allowSubobjects and allowSubarrays? :smiley: Please try to clarify these aspects. Thanks! :+1:

For now, just use the simplest way for you, and later we will improve this workflow–we will see what limitations we have and things like that. :wrench:

For reference, while working on this issue I reported this Chromium issue.

@IonicaBizau, in a table (which is the UI for a field of type "array"), in the cells under a column of type "object" (a column is a field inside the schema of that field of type "array"), all the objects in that column should have the same structure (or with other words, the same subfields)? Or, with other words, should each row of the table have a separate schema for the column of type "object"?

all the objects in that column should have the same structure

For now yes! Maybe in the future this is something we will improve when we will have limitations, but for now all should have the same schema/fields.


Mp/add scripts to deploy

This name is misleading, there are updates to mover policy migration and to the build scripts.

@marcparadise I'm having some trouble rebasing this against master to move it over to the chef-server repo.  Going to leave it for now and come back to it, but you might have more luck taking a stab at it.

I renamed this to a different branch that has already been merged, closing this one out.


Backport "HBASE-28485 Re-use ZstdDecompressCtx/ZstdCompressCtx for performance (#5797)" to branch-2.6

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 44s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.6 Compile Tests _

+1 :green_heart:
mvninstall
3m 23s
branch-2.6 passed

+1 :green_heart:
compile
0m 17s
branch-2.6 passed

+1 :green_heart:
checkstyle
0m  8s
branch-2.6 passed

-1 :x:
spotless
0m  9s
branch has 60 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
0m 22s
branch-2.6 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  6s
the patch passed

+1 :green_heart:
compile
0m 16s
the patch passed

+1 :green_heart:
javac
0m 16s
the patch passed

+1 :green_heart:
checkstyle
0m  7s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m 14s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

-1 :x:
spotless
0m  8s
patch has 60 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
0m 29s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

21m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5806

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 50ddbf572c3d 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / b8c797660f

Default Java
Eclipse Adoptium-11.0.17+8

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/artifact/yetus-general-check/output/branch-spotless.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-compression/hbase-compression-zstd U: hbase-compression/hbase-compression-zstd

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+1 :green_heart:
mvninstall
2m 35s
branch-2.6 passed

+1 :green_heart:
compile
0m 14s
branch-2.6 passed

+1 :green_heart:
shadedjars
4m 52s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 13s
branch-2.6 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 31s
the patch passed

+1 :green_heart:
compile
0m 13s
the patch passed

+1 :green_heart:
javac
0m 13s
the patch passed

+1 :green_heart:
shadedjars
5m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
3m  6s
hbase-compression-zstd in the patch passed.

22m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5806

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a5fdd55e5ccf 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / b8c797660f

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/testReport/

Max. process+thread count
696 (vs. ulimit of 30000)

modules
C: hbase-compression/hbase-compression-zstd U: hbase-compression/hbase-compression-zstd

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+1 :green_heart:
mvninstall
3m 21s
branch-2.6 passed

+1 :green_heart:
compile
0m 14s
branch-2.6 passed

+1 :green_heart:
shadedjars
6m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 12s
branch-2.6 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  2s
the patch passed

+1 :green_heart:
compile
0m 13s
the patch passed

+1 :green_heart:
javac
0m 13s
the patch passed

+1 :green_heart:
shadedjars
5m 57s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 10s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 34s
hbase-compression-zstd in the patch passed.

23m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5806

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3359c411b37a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / b8c797660f

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/testReport/

Max. process+thread count
725 (vs. ulimit of 30000)

modules
C: hbase-compression/hbase-compression-zstd U: hbase-compression/hbase-compression-zstd

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5806/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

Spotless errors predate this patch.


[client] Detect and report failed transactions

The client code has not been checking the VM status to determine if transactions executed successfully. This changes to check for a status of EXECUTED and reports an error otherwise. This exposed an issue where the external_transaction_signer test in smoke_test.rs has been failing because it ran out of gas, so this also adjusts the gas parameters for that test to make it pass.
https://github.com/libra/libra/issues/3663
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Ran existing tests and fixed the issues that were exposed

this will, incidentally will really affect faucet performance (because it uses CLI to mint)

I don't see how it will affect performance at all. I'm just adding a check of the VM status and reporting and error when a transaction fails to execute.

my bad I thought this changed how mint transaction work, but it didn't

@bors-libra r=thefallentree

:pushpin: Commit 722f8d5 has been approved by thefallentree

:hourglass: Testing commit 722f8d5b9adee76f4b52d37bbc48b213796b6f30 with merge a1b9370c6fc7422b58c2030671ddc7b48a87056e...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: thefallentree
Pushing a1b9370c6fc7422b58c2030671ddc7b48a87056e to master...


Domain resolution value changes output value...

In the showcase example of HVAC motor control,  the Domain for the motor is defined as follows:
motor   = Domain( "Speed", 0, 2000 )
When the example code is run, it results in an output of 1633.122481617619
when the domain has a resolution added as follows:
motor   = Domain( "Speed", 0, 2000, 0.1 )
the output when run is then<PHONE_NUMBER>4216137
It would appear that changing the resolution is altering the scale of the output -> resolution reduced by an order of magnitude results in an output reduction of an order of magnitude.    I do not believe that this is mentioned in the documentation.
Is this the intended result of additing resolution to the domains?   Does adding the resolution to the inputs (temperature and humidity in this example) have any scaling consequences?
Thank you very much

Well observed. There is some debate on this problem here https://github.com/Python-Fuzzylogic/fuzzylogic/discussions/47.

Well, here is the situation I am in.   I am interested in applying fuzzy logic to some engineering problems.  The first attempted application is in calculating the impedance of a microstrip transmission line.  The thinner the line, the higher the impedance, the thinner the line, the lower the impedance.   Currently, I have a routine which will iterate over different width of the transmission line to calculate an impedance, compare it to the target impedance and stop when the target impedance is close enough to calculated impedance.
It is my desire to use fuzzy logic and very the amount of change applied to the trace width as we calcuate new impedances.  The basic idea is that the larger the error between the target impedance and the desired impedance the more we change the width of the trace.   as we get closer to the desired impedance the smaller the change.
As I am new to fuzzy logic, and I really like the implementation of your code, I would like to understand how to implement a simple set of fuzzy logic calculations to determine the change in width to be applied to the trace based on the magnitude of the impedance error.
Below is my test code for attempting to implement the calculations for determining the change in width to be applied to the traces.    There are sections which are commented out for plotting the graphs of the veriables involved.    I have set up a loop which will run through different errors from large negative errors to large positive errors.   The expected outcome is for the width changes to start out large positive, approach 0, and then proceed to large negative numbers.
If the code below is run, the change in width which is output is practically constant.  I do not understand where things are going horribly wrong...
If there is any guidance you could suggest, I would greatly appreciate the suggestions...
'''
This code is to be used in another program which calculates the impedance of a
microstrip transmission line
The purpose of this routine is to determine the delta between the
desired impedance and the calculated impedance
The impedance error is the error between the desired impedance and the calculated
impedance
The trace_delta will be the amount that the trace width will be modified by
The idea being the bigger the impedance error, the larger the modification to the trace
before the impedance is calculated again.  The smaller the error, the smaller the
change in the trace width
'''
import matplotlib
from fuzzylogic.classes import Domain, Set, Rule
from fuzzylogic.hedges import very
from fuzzylogic.functions import R, S
from fuzzylogic.functions import (sigmoid, gauss, trapezoid, triangular,
triangular_sigmoid, rectangular)
import sys
#define the domains of our variables
trace_delta     = Domain( "Delta", -2, 2  )         #width delta in mm
impedance_error = Domain( "Error", -200, 200  )     #impedance error in ohms
#define the various deltas in width
trace_delta.neg_large   = S( -1, -0.25 )
trace_delta.neg_small   = trapezoid( -0.5, -0.25, -0.1, -0.05, c_m = 1 )
trace_delta.small       = trapezoid( -0.1, -0.05, 0.05, 0.1, c_m = 1 )
trace_delta.small       = gauss( 0, 100, c_m = 1 )
trace_delta.small       = triangular( -0.1, 0.1 )
trace_delta.pos_small   = trapezoid( 0.05, 0.1, 0.25, 0.5, c_m = 1  )
trace_delta.pos_large   = R( 0.25, 1 )
#define the error magnitude
impedance_error.neg_large   = S( -100, -50 )
impedance_error.neg_small   = trapezoid( -70, -30, -10, 0, c_m = 1 )
impedance_error.small       = trapezoid( -10, -5, 5, 10, c_m = 1 )
impedance_error.pos_small   = trapezoid( 0, 10, 30, 70, c_m = 1 )
impedance_error.pos_large   = R( 50, 100 )
#define the error magnitude
impedance_error.neg_large   = S( -100, -50 )
impedance_error.neg_small   = trapezoid( -80, -75, -20, 0, c_m = 1 )
impedance_error.small       = trapezoid( -30, -5, 5, 30, c_m = 1 )
impedance_error.small       = triangular( -30, 30, c_m = 1 )
impedance_error.pos_small   = trapezoid( 0, 20, 75, 80, c_m = 1 )
impedance_error.pos_large   = R( 50, 100 )
#define the plots
trace_delta.neg_large.plot( )
trace_delta.neg_small.plot( )
trace_delta.small.plot( )
trace_delta.pos_small.plot( )
trace_delta.pos_large.plot( )
#define the plots
impedance_error.neg_large.plot( )
impedance_error.neg_small.plot( )
impedance_error.small.plot( )
impedance_error.pos_small.plot( )
impedance_error.pos_large.plot( )
#show the plots
matplotlib.pyplot.show( )
sys.exit( )
#define the rules
R1 = Rule( { (impedance_error.neg_large, )  : trace_delta.neg_large    } )
R2 = Rule( { ( impedance_error.neg_small, ) : trace_delta.neg_small } )
R3 = Rule( { ( impedance_error.small, )     : trace_delta.small } )
R4 = Rule( { ( impedance_error.pos_small, ) : trace_delta.pos_small } )
R5 = Rule( { ( impedance_error.pos_large, ) : trace_delta.pos_large } )
rules = Rule( { ( impedance_error.neg_large, )  : trace_delta.neg_large,
( impedance_error.neg_small, )    : trace_delta.neg_small,
( impedance_error.small, )        : trace_delta.small,
( impedance_error.pos_small, )    : trace_delta.pos_small,
( impedance_error.pos_large, )    : trace_delta.pos_large,
} )
#implement the rules
rules = R1 | R2 | R3 | R4 | R5
rules = sum( [ R1, R2, R3, R4, R5 ] )
#for debug only
for test_value in range( -100, 101, 25 ):
# values = { impedance_error : 100, impedance: 150 }
values = { impedance_error : test_value }
print(   f'{"-"*80}' )
print(   f' impedance_error = {test_value}' )
print(   f'\t{R1( values )=}' )
print(   f'\t{R2( values )=}' )
print(   f'\t{R3( values )=}' )
print(   f'\t{R4( values )=}' )
print(   f'\t{R5( values )=}' )
print(   f'\t\t {rules( values ) = }' )

Tried to fix the formatting for the code segment..
FuzzyLogic-Test4.py.txt

You need to use backticks ``` to format a block as code

trace_delta.neg_large   = S( -1, -0.25 ) with a domain of trace_delta     = Domain( "Delta", -2, 2  )  looks weird. This assumes a resolution of 1, which is only the values of [-2, -1, 0, 1, 2], no? Is that what you intend?

trace_delta     = Domain( "Delta", -2, 2  )  looks weird. This assumes a resolution of 1, which is only the values of [-2, -1, 0, 1, 2], no? Is that what you intend?
This is where the resolution issue arose.    Originally, I had the resolution set to 0.01 as I felt this would be a good incremental value for changing the width.   When I was getting results which did not make sense to me, I started experimenting with other resolutions.    That piece of code is simply the point where I had eliminated the resolution to see if there would be a difference in the output characteristic.   There was not.
It was at this point where I thought I would seek the advise of a resonsible adult who could perhaps show me the error of my ways.

It was at this point where I thought I would seek the advise of a resonsible adult who could perhaps show me the error of my ways.

Reasonable? Me? Uhmmm... 😆
Well. "Eliminating" the resolution just means defaulting to 1 in this case. The problem with the resolution probably is with line 493 in classes.py, the final defuzzification step. You can try to experiment and see if you can figure out a better solution?
                return (target_domain._high - target_domain._low) / len(
                    target_domain.range
                ) * index + target_domain._low

Btw, thanks a lot for your actual usecase. Helps so much in understanding how my code is actually used and how it's supposed to work. Last person who contacted me wanted me to implement stuff without giving any clue on how it's supposed to work due to "intellectual property" BS.

Hmmm. Could the problem with the resolution be caused by the negative lower limit in the domain? I'm just trying to reproduce your problem and I having -3.2 in a domain that has -2 as lower bound really is an obvious bug.

Thank you for taking the time to look at the code.
I also noticed that there were cases where the output would be outside the domain.  If the inputs were outside their domain then I would not be surprised at something like that happening.  However, if all the values are within the approriate domains, I would not expect that output.
When I run the code, it appears that the output is stuck, or biased, toward the lower end of the domain.  I am not sure that I would expect the results to be rounded to the resolution if there is interpolation occuring, but if there is no interpolation, then yes, I would expect a result at some value in the domain that is a multple of the resolution...
In examing things this morning, I was checking to see if the impedance_error, for the various test values, was giving values that made sense.    It appears that reasonable values were being returned.   This only leaves the application of the various rules returning incorrect values.   I was waiting to hear what your thoughts were befroe trying to dive in any deeper as I only have a cursory understanding of the mathematics behind the transformations being applied.

I have a question concerning the center of gravity calculation (this is where I think things are going horribly wrong):
I modifed the code to print out values of various things:
                target_domain = list(self.conditions.values())[0].domain
                index = sum(v.center_of_gravity( ) * x for v, x in weights) / sum(x for v, x in weights)

                print( f'{target_domain = }' )
                print( f'{index = }' )

                temp_value = (target_domain._high - target_domain._low) / len(
                    target_domain.range
                ) * index + target_domain._low

                print( f'{temp_value = }' )

                return (target_domain._high - target_domain._low) / len(
                    target_domain.range
                ) * index + target_domain._low

temp_value is the same as the return value.   The index value contains a calculation of the center_of_gravity (cog),  I print out the cog value from center_of_gravity.  For the program that I run with the last value of imepedance_error = 100, I get the following output:
pos_large: weights = array([0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.        , 0.        , 0.        , 0.        ,
0.        , 0.01333333, 0.02666667, 0.04      , 0.05333333,
0.06666667, 0.08      , 0.09333333, 0.10666667, 0.12      ,
0.13333333, 0.14666667, 0.16      , 0.17333333, 0.18666667,
0.2       , 0.21333333, 0.22666667, 0.24      , 0.25333333,
0.26666667, 0.28      , 0.29333333, 0.30666667, 0.32      ,
0.33333333, 0.34666667, 0.36      , 0.37333333, 0.38666667,
0.4       , 0.41333333, 0.42666667, 0.44      , 0.45333333,
0.46666667, 0.48      , 0.49333333, 0.50666667, 0.52      ,
0.53333333, 0.54666667, 0.56      , 0.57333333, 0.58666667,
0.6       , 0.61333333, 0.62666667, 0.64      , 0.65333333,
0.66666667, 0.68      , 0.69333333, 0.70666667, 0.72      ,
0.73333333, 0.74666667, 0.76      , 0.77333333, 0.78666667,
0.8       , 0.81333333, 0.82666667, 0.84      , 0.85333333,
0.86666667, 0.88      , 0.89333333, 0.90666667, 0.92      ,
0.93333333, 0.94666667, 0.96      , 0.97333333, 0.98666667,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        , 1.        , 1.        , 1.        , 1.        ,
1.        ])
self.domain.range = array([-2.  , -1.99, -1.98, -1.97, -1.96, -1.95, -1.94, -1.93, -1.92,
-1.91, -1.9 , -1.89, -1.88, -1.87, -1.86, -1.85, -1.84, -1.83,
-1.82, -1.81, -1.8 , -1.79, -1.78, -1.77, -1.76, -1.75, -1.74,
-1.73, -1.72, -1.71, -1.7 , -1.69, -1.68, -1.67, -1.66, -1.65,
-1.64, -1.63, -1.62, -1.61, -1.6 , -1.59, -1.58, -1.57, -1.56,
-1.55, -1.54, -1.53, -1.52, -1.51, -1.5 , -1.49, -1.48, -1.47,
-1.46, -1.45, -1.44, -1.43, -1.42, -1.41, -1.4 , -1.39, -1.38,
-1.37, -1.36, -1.35, -1.34, -1.33, -1.32, -1.31, -1.3 , -1.29,
-1.28, -1.27, -1.26, -1.25, -1.24, -1.23, -1.22, -1.21, -1.2 ,
-1.19, -1.18, -1.17, -1.16, -1.15, -1.14, -1.13, -1.12, -1.11,
-1.1 , -1.09, -1.08, -1.07, -1.06, -1.05, -1.04, -1.03, -1.02,
-1.01, -1.  , -0.99, -0.98, -0.97, -0.96, -0.95, -0.94, -0.93,
-0.92, -0.91, -0.9 , -0.89, -0.88, -0.87, -0.86, -0.85, -0.84,
-0.83, -0.82, -0.81, -0.8 , -0.79, -0.78, -0.77, -0.76, -0.75,
-0.74, -0.73, -0.72, -0.71, -0.7 , -0.69, -0.68, -0.67, -0.66,
-0.65, -0.64, -0.63, -0.62, -0.61, -0.6 , -0.59, -0.58, -0.57,
-0.56, -0.55, -0.54, -0.53, -0.52, -0.51, -0.5 , -0.49, -0.48,
-0.47, -0.46, -0.45, -0.44, -0.43, -0.42, -0.41, -0.4 , -0.39,
-0.38, -0.37, -0.36, -0.35, -0.34, -0.33, -0.32, -0.31, -0.3 ,
-0.29, -0.28, -0.27, -0.26, -0.25, -0.24, -0.23, -0.22, -0.21,
-0.2 , -0.19, -0.18, -0.17, -0.16, -0.15, -0.14, -0.13, -0.12,
-0.11, -0.1 , -0.09, -0.08, -0.07, -0.06, -0.05, -0.04, -0.03,
-0.02, -0.01,  0.  ,  0.01,  0.02,  0.03,  0.04,  0.05,  0.06,
0.07,  0.08,  0.09,  0.1 ,  0.11,  0.12,  0.13,  0.14,  0.15,
0.16,  0.17,  0.18,  0.19,  0.2 ,  0.21,  0.22,  0.23,  0.24,
0.25,  0.26,  0.27,  0.28,  0.29,  0.3 ,  0.31,  0.32,  0.33,
0.34,  0.35,  0.36,  0.37,  0.38,  0.39,  0.4 ,  0.41,  0.42,
0.43,  0.44,  0.45,  0.46,  0.47,  0.48,  0.49,  0.5 ,  0.51,
0.52,  0.53,  0.54,  0.55,  0.56,  0.57,  0.58,  0.59,  0.6 ,
0.61,  0.62,  0.63,  0.64,  0.65,  0.66,  0.67,  0.68,  0.69,
0.7 ,  0.71,  0.72,  0.73,  0.74,  0.75,  0.76,  0.77,  0.78,
0.79,  0.8 ,  0.81,  0.82,  0.83,  0.84,  0.85,  0.86,  0.87,
0.88,  0.89,  0.9 ,  0.91,  0.92,  0.93,  0.94,  0.95,  0.96,
0.97,  0.98,  0.99,  1.  ,  1.01,  1.02,  1.03,  1.04,  1.05,
1.06,  1.07,  1.08,  1.09,  1.1 ,  1.11,  1.12,  1.13,  1.14,
1.15,  1.16,  1.17,  1.18,  1.19,  1.2 ,  1.21,  1.22,  1.23,
1.24,  1.25,  1.26,  1.27,  1.28,  1.29,  1.3 ,  1.31,  1.32,
1.33,  1.34,  1.35,  1.36,  1.37,  1.38,  1.39,  1.4 ,  1.41,
1.42,  1.43,  1.44,  1.45,  1.46,  1.47,  1.48,  1.49,  1.5 ,
1.51,  1.52,  1.53,  1.54,  1.55,  1.56,  1.57,  1.58,  1.59,
1.6 ,  1.61,  1.62,  1.63,  1.64,  1.65,  1.66,  1.67,  1.68,
1.69,  1.7 ,  1.71,  1.72,  1.73,  1.74,  1.75,  1.76,  1.77,
1.78,  1.79,  1.8 ,  1.81,  1.82,  1.83,  1.84,  1.85,  1.86,
1.87,  1.88,  1.89,  1.9 ,  1.91,  1.92,  1.93,  1.94,  1.95,
1.96,  1.97,  1.98,  1.99,  2.  ])
cog = 1.2980193236714976
target_domain = Domain('Delta', -2.0, 2.0, res=0.01, sets={'neg_large': Set(<function S..f at 0x00000193A4848A40>), 'neg_small': Set(<function trapezoid..f at 0x00000193CDD71A80>), 'small': Set(<function triangular..f at 0x00000193CF635580>), 'pos_small': Set(<function trapezoid..f at 0x00000193CF635760>), 'pos_large': Set(<function R..f at 0x00000193CF635800>)})
index = 1.2980193236714976
temp_value = -1.9870521763224789
rules( values ) = -1.9870521763224789
The array for pos_large I believe.   It looks reasonable.   Zeros for the beginng, a transition region, and the last values all 1.   So I would say that is correct.
The self.domain.range also looks goot (-2 to 2 with a res=0.1).   That is fine.
cog value of 1.298, assuming the np.average calculation is done correctly (and why wouldn't it), seems like a reasonable answer.
The index value is the same as cog.   This is not what I would expect.   I would expect the index to be an integer which is an index into the array which is closest to 1.298, as such, I would expect an integer and not a float.
using index as an index into the domain (-2 to 2 with res=0.1)  is going to return a value very close to -2, which is what appears to be happening looking at temp_value = -1.9870521763224789.
So, it seems to me that the index value is not correct.   I am not wise enough to work on fixing the code to get and actual index.   Perhaps this is something you could look at and see if what I am saying is correct or not.
Thank you very much

Seems like you've done a lot of digging, wow. Okay. Hmm. Let's see...

I'm running the code in debugger. The intermediate value of the index is -1.5

I would expect the index to be an integer which is an index into the array which is closest to 1.298, as such, I would expect an integer and not a float.
The return calculation (which should return the appropriate delta value to applied to the width) is attempting to return the value  which is closest to 1.298 (which is the cog value returned).   The calculation takes the span of the domain, divides it by the number of values in this range, (essentially getting res=0.01 value), multiplies by the index to get the number of res=0.01 steps which corresponds to the closest value of 1.298, and then adds the low value of the domain to obtain that value...
since this returns the closes value to the cog, why not just return the cog?   Or, take the cog value and divide by res=0.01 add 0.5 and take the integer value to get the index into the array, and return that value at that index...
seems like just returning the cog would be good enough to me...

Sorry, I deleted my comments after re-reading what you posted in detail.
As I understand it, the index is not an integer because at this point in the calculation it's basically an inversion of the axis and the index is abstract - you've calculated the y values, weighted them and then you've got an x value, which is not an actual array index, but rather stands for the relative position inside the continuous, but limited domain. This last step attempts to re-map the relative position inside the domain to the absolute number, taking into account the limits.

There is an alternative approach to using arrays, which could actually be intermixed. Simple functions like R, S, triangular, trapezoid could be mapped to actual geometric formulas, so the "index" would really be the x-value of your graph. I hope that clears it up.

well,  I changed the code to simply return the cog value and I appear to be actually getting usable results.
Like I said, I am no expert on this subject, but you statement above pretty much agrees with my observation.   In fact, your statement "the index is abstract - you've calculated the y values, weighted them and then you've got an x value, which is not an actual array index, but rather stands for the relative position inside the continuous, but limited domain.", which I agree with (and that is my point), index which is calculated is NOT an index into the array, but it is being treated as if it is...
I also believe your statement "As I understand it, the index is not an integer because at this point in the calculation it's basically an inversion of the axis" I also agree with, and I believe that the cog calculation is performing that inversion and giving you this inverted value which is being calculated as the cog...
As I am not an expert, and have no experience in any of this, this could very well be a coincidence and I am completely wrong...

What's the cog value you return now?

Sorry, I was busy for a couple of days and didn't have time to look at this discussion.
From the above output, the cog = 1.2980193236714976.  This is instead of the erroreous -1.9870521763224789.
From the looks of the self.domain.range, this looks like it is a reasonable answer.

HI there.   Sorry it has taken so long to respond.  I got busy with work and had to put this problem aside for a time.
Let me have a think about this and see if there is anything I can generate.


fix(hugo): latest release has no packages for reasons

This removes the latest constraint as they have tagged a source-only version. Now that we trim our cache it may be better to take the cautious approach and stop getting latest tags altogether.
Closes #1237

Tested and working locally:
cd /etc/deb-get/99-local.d
wget https://raw.githubusercontent.com/philclifford/deb-get/refs/heads/fix-hugo/01-main/packages/hugo
deb-get install hugo


Console errors when loading any Soundcloud track

Getting a load of these errors every time a Soundcloud track is loaded into the player, happens on the demo site as well for reference.
[Error] Not allowed to request resource
[Error] Cannot load http://ent/web-sourcemaps/widget-7-5e67950fc23c.js.map due to access control checks.

This isn’t happening for me. Is it still happening for you now @JClackett ?

Yeah in safari and chrome I get a load of these in the dev console on the demo site, using the example Soundcloud links. No extensions being used, no content blockers.

Happening to me as well. Reproducible on the demo site.


NIFI-3852 Add expression language support to Cassandra processors

NIFI-3852 Add expression language support to Cassandra contact points and keyspace properties

Thanks for this improvement!  As a suggestion (while you're in there), could you add EL support for some of the other properties such as Username, Password, and perhaps Character Set? Other properties for consideration are the particular properties (not shared) in the Cassandra processors themselves, such as Fetch Size for QueryCassandra.
Whichever properties you choose to enable EL support for, can you add unit test(s) for those properties? Please let me know if you'd like any guidance in the area, I'd be glad to help!

@mattyb149 Thanks for reviewing. Sounds reasonable to me, I have updated the PR.

+1 LGTM, built and ran unit tests and contrib-check, also ran with a NiFi instance using Variable Registry, everything looks great, thanks again for the contribution! Merging to master


Have native completion installation for bash, zsh and fish

At the moment, when I'm installing flux with homebrew, I don't have completion available right out of the box. Could you make sure it is enabled for each shell (bash, fish, zsh and powershell)?

Completions are enabled https://github.com/fluxcd/homebrew-tap/blob/master/Formula/flux.rb

They are not working for me on bash and zsh natively. Strangely they are
working in fish 🤔
Le ven. 21 juil. 2023, 17:27, Stefan Prodan @.***> a
écrit :

Completions are enabled
https://github.com/fluxcd/homebrew-tap/blob/master/Formula/flux.rb
—
Reply to this email directly, view it on GitHub
https://github.com/fluxcd/homebrew-tap/issues/7#issuecomment-1645761569,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJOITDAYLYF3OTYD42PB3XRKNULANCNFSM6AAAAAA2S53GVQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Responsive bootstrap 4 toggle button not working.

On a freshly installed Laravel 7, bootstrap 4 responsive toggle menu (hamburger) not working

Laravel Version: 7.0

Description: Bootstrap 4 responsive toggle menu button doesn't expand the menu instead throws an error
Cannot convert object to primitive value
Steps To Reproduce:
Install laravel (with auth)
npm install
npm run dev
visit localhost:8000
switch to responsive mode and click on menu button and see the error in console

I had the same problem in a rails 6 project I was developing. I am using bootstrap 4.4.1 and had the exact same problem with my collapsing navigation bar: The navbar collapses but the hamburger button which appears on collapse was not clickable.
The solution: Downgrade jquery from 3.5.0 to 3.4.1. I did not look into the actual reason of the error for now.

i had the same issue with a fresh laravel installation


[Feature] custom components can provide a ctor option for interfacing with vee-validate

Versions:

VueJs: Any
Vee-Validate: 2.0.0-rc.8

Description:
Currently only checkboxes have the exception of rejecting false as a valid value for the required rule. This can be a common use case for components that has a toggle state inputs like a switch or a toggle button.
This is original pointed out by @escapedcat in #613
This issue can also extend to having to provide data-vv-value-path for each component event tho they are the same component and the access method for them is the same, so that is very verbose for developers and makes their templates bloated more than needed.
Proposal:
Adding another data-vv-* attribute seems verbose and I would like to get rid of as many data attrs as possible for components.
A solution would be that each component can have a ctor option in their definition that defines numerous behaviors when being validated by vee-validate for example:
export default {
  $vee: {
      invalidatesFalse: Boolean, // this component does not consider false as a non-empty value.
      new: Boolean, // this component can inherit the parent's validator instance if injected.
      value: Function // returns the current component's value.
   }
};

I didn't follow the latest changes. Was this solved in a different way or isn't it an issue for the majority and will jsut be closed. I would be fine with both. Just checkin'.

It is a work-in-progress currently but not a priority.

Got it, thx for the update


[CI-PR Pipelines] Skip tests in Debug builds

Description
This PR updates the ci-test-steps yaml file to skip the test and coverage steps in the Debug builds.
Also, it fixes an issue found on the API Compat job matrix that caused that the Microsoft.Bot.Builder.Integration.ApplicationInsights.Core library wasn't getting compared.
Specific Changes

ci-test-steps yaml:

Removed the test steps for Debug 2.1 and Debug 3.1 jobs
Added a condition to execute the coverage steps only for Release builds.

botbuilder-dotnet-ci.yml:

Updated the PowerShell script to create the matrix for the API Compat job including all the libraries.
Updated the Powershell script to run all API Compat validation on Manual builds fixing an error.

Testing
The following image shows the test and coverage steps being skipped on the Debug build, releasing the agent that executes the Debug job about 4 minutes earlier.

Promoted # 4416


Test2: Creating a PR from a GH issue

Provide the actual tweet content between the commented colons
Hello! This tweet is created from a GH issue, which will be PRed automatically.

/kind tweet

@gkarthiks So I tried to test with the label here. but the action  to create a PR wasn't triggered https://github.com/kubernetes-sigs/contributor-tweets/actions/runs/1008990505. I think it might be because, the workflow expects the label as soon as the issue is created. But with the prow bot, we need to add it manually I guess. (Not sure if we can add it by default).
I guess we can add 'issue_comment'  with '\kind tweet' in it as a trigger for the whole workflow? wdyt?

You are a little faster in validating :) I am about to make the changes that I mentioned here https://github.com/kubernetes-sigs/contributor-tweets/issues/45#issuecomment-864457008.
Making that PR and this should work after that.

/validate

@rajula96reddy seems the issue is not created with the proper template in this. The action couldn't able to parse it.
The parsing symbol first found @ -1

https://github.com/kubernetes-sigs/contributor-tweets/runs/3018378320?check_suite_focus=true#step:5:14

Is it safe to close this?

yes. Thank you Chris.

/close


[cpprestsdk] Build error. Building cpprestsdk:x64-windows failed with: BUILD_FAILED

Operating System
Microsoft Windows Server 2022 10.0.203
from the windows-2022 GitHub Actions GitHub-hosted runner.
Compiler
Visual Studio Enterprise 2022 17.7.34202.233
from the windows-2022 GitHub Actions GitHub-hosted runner.
Steps to reproduce the behavior
vcpkg integrate install
vcpkg install cpprestsdk:x64-windows

Failure logs

Click here
Run vcpkg integrate install
  vcpkg integrate install
  vcpkg install cpprestsdk:x64-windows
  shell: C:\Program Files\Git\bin\bash.EXE -l {0}
  env:
    BUILD_TYPE: Release
    INPUT_RUN_POST: true

Applied user-wide integration for this vcpkg root.
CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake"

All MSBuild C++ projects can now #include any installed libraries. Linking will be handled automatically. Installing new libraries will make them instantly available.
Computing installation plan...
The following packages will be built and installed:
  * brotli:x64-windows -> 1.1.0#1
    cpprestsdk[brotli,compression,core]:x64-windows -> 2.10.18#4
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
  * zlib:x64-windows -> 1.3
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of 7zip was not found (required v23.1.0) Downloading portable 7zip 23.1.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2301-extra.7z->C:\vcpkg\downloads\7z2301-extra.7z
Downloading https://www.7-zip.org/a/7z2301-extra.7z
Extracting 7zip...
Restored 0 package(s) from C:\Users\runneradmin\AppData\Local\vcpkg\archives in 282 us. Use --debug to see more details.
Installing 1/5 vcpkg-cmake:x64-windows...
Building vcpkg-cmake:x64-windows...
-- Installing: C:/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 88.4 ms.
Elapsed time to handle vcpkg-cmake:x64-windows: 187 ms
Installing 2/5 vcpkg-cmake-config:x64-windows...
Building vcpkg-cmake-config:x64-windows...
-- Installing: C:/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg-port-config.cmake
-- Installing: C:/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 21.5 ms.
Elapsed time to handle vcpkg-cmake-config:x64-windows: 93.1 ms
Installing 3/5 brotli:x64-windows...
Building brotli:x64-windows...
-- Downloading https://github.com/google/brotli/archive/v1.1.0.tar.gz -> google-brotli-v1.1.0.tar.gz...
-- Extracting source C:/vcpkg/downloads/google-brotli-v1.1.0.tar.gz
-- Applying patch install.patch
-- Applying patch fix-arm-uwp.patch
-- Applying patch pkgconfig.patch
-- Applying patch emscripten.patch
-- Using source at C:/vcpkg/buildtrees/brotli/src/v1.1.0-958bece74c.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/lib/pkgconfig/libbrotlicommon.pc
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/lib/pkgconfig/libbrotlidec.pc
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/lib/pkgconfig/libbrotlienc.pc
-- Downloading https://mirror.msys2.org/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://repo.msys2.org/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst;https://mirror.selfnet.de/msys2/mingw/mingw32/mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst -> mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst...
-- Downloading https://mirror.msys2.org/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://repo.msys2.org/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst;https://mirror.selfnet.de/msys2/msys/x86_64/msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst -> msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst...
-- Using msys root at C:/vcpkg/downloads/tools/msys2/6f3fa1a12ef85a6f
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/debug/lib/pkgconfig/libbrotlicommon.pc
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/debug/lib/pkgconfig/libbrotlidec.pc
-- Fixing pkgconfig file: C:/vcpkg/packages/brotli_x64-windows/debug/lib/pkgconfig/libbrotlienc.pc
-- Installing: C:/vcpkg/packages/brotli_x64-windows/share/brotli/usage
-- Installing: C:/vcpkg/packages/brotli_x64-windows/share/brotli/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 1.2 s.
Elapsed time to handle brotli:x64-windows: 54 s
Installing 4/5 zlib:x64-windows...
Building zlib:x64-windows...
-- Downloading https://github.com/madler/zlib/archive/v1.3.tar.gz -> madler-zlib-v1.3.tar.gz...
-- Extracting source C:/vcpkg/downloads/madler-zlib-v1.3.tar.gz
-- Applying patch 0001-Prevent-invalid-inclusions-when-HAVE_-is-set-to-0.patch
-- Applying patch 0002-skip-building-examples.patch
-- Applying patch 0003-build-static-or-shared-not-both.patch
-- Applying patch 0004-android-and-mingw-fixes.patch
-- Using source at C:/vcpkg/buildtrees/zlib/src/v1.3-8825ee792f.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: C:/vcpkg/packages/zlib_x64-windows/share/zlib/vcpkg-cmake-wrapper.cmake
-- Fixing pkgconfig file: C:/vcpkg/packages/zlib_x64-windows/lib/pkgconfig/zlib.pc
-- Using cached mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using msys root at C:/vcpkg/downloads/tools/msys2/6f3fa1a12ef85a6f
-- Fixing pkgconfig file: C:/vcpkg/packages/zlib_x64-windows/debug/lib/pkgconfig/zlib.pc
-- Installing: C:/vcpkg/packages/zlib_x64-windows/share/zlib/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 135 ms.
Elapsed time to handle zlib:x64-windows: 28 s
Installing 5/5 cpprestsdk:x64-windows...
Building cpprestsdk[brotli,compression,core]:x64-windows...
-- Downloading https://github.com/Microsoft/cpprestsdk/archive/122d09549201da5383321d870bed45ecb9e168c5.tar.gz -> Microsoft-cpprestsdk-122d09549201da5383321d870bed45ecb9e168c5.tar.gz...
-- Extracting source C:/vcpkg/downloads/Microsoft-cpprestsdk-122d09549201da5383321d870bed45ecb9e168c5.tar.gz
-- Applying patch fix-find-openssl.patch
-- Applying patch fix_narrowing.patch
-- Applying patch fix-uwp.patch
-- Using source at C:/vcpkg/buildtrees/cpprestsdk/src/ecb9e168c5-295a1e905e.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
CMake Warning at installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:318 (message):
  The following variables are not used in CMakeLists.txt:

      WEBSOCKETPP_CONFIG
      WEBSOCKETPP_CONFIG_VERSION

  Please recheck them and remove the unnecessary options from the
  `vcpkg_cmake_configure` call.

  If these options should still be passed for whatever reason, please use the
  `MAYBE_UNUSED_VARIABLES` argument.
Call Stack (most recent call first):
  ports/cpprestsdk/portfile.cmake:33 (vcpkg_cmake_configure)
  scripts/ports.cmake:168 (include)

-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j3
    Working Directory: C:/vcpkg/buildtrees/cpprestsdk/x64-windows-dbg
    See logs for more information:
      C:\vcpkg\buildtrees\cpprestsdk\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/cpprestsdk/portfile.cmake:[48](https://github.com/redacted/redacted/actions/runs/redacted/job/redacted#step:10:49) (vcpkg_cmake_install)
  scripts/ports.cmake:168 (include)

error: building cpprestsdk:x[64](https://github.com/redacted/redacted/actions/runs/redacted/job/redacted#step:10:65)-windows failed with: BUILD_FAILED
Elapsed time to handle cpprestsdk:x64-windows: 31 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+cpprestsdk
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[cpprestsdk]+Build+error&body=Copy+issue+body+from+C%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
You can also submit an issue by running (GitHub CLI must be installed):
  gh issue create -R microsoft/vcpkg --title "[cpprestsdk] Build failure" --body-file C:/vcpkg/installed/vcpkg/issue_body.md
Error: Process completed with exit code 1.

Additional context
I tried restarting the GitHub Actions job three times. It fails consistently.

    See logs for more information:
      C:\vcpkg\buildtrees\cpprestsdk\install-x64-windows-dbg-out.log

Please provide detailed logs.

    See logs for more information:
      C:\vcpkg\buildtrees\cpprestsdk\install-x64-windows-dbg-out.log

Please provide detailed logs.

Here it is: https://gist.github.com/gsaponaro-af/b08f240b6d47d80efc9e329ee17406b9
Thank you

Do you fall into one of the following situations:

If you have a static library checked-in to your project which was built before Visual Studio 2022 version 17.2 Preview 2 and you build the rest of your project with a newer toolset you will see this error.
See: https://developercommunity.visualstudio.com/t/__imp___std_init_once_complete-unresolve/1684365#T-N10047968
The fix has been checked in for 17.3 Preview 3.
See: https://developercommunity.visualstudio.com/t/__imp___std_init_once_complete-unresolve/1684365#T-N10053839

You’re compiling some object files/static libraries with VS 2022, but performing the final link with VS 2019.
See:
https://developercommunity.visualstudio.com/t/__imp___std_init_once_complete-unresolve/1684365#T-N10079675
https://developercommunity.visualstudio.com/t/__imp___std_init_once_complete-unresolve/1684365#T-N10080626
If you have a different version of VS installed, the VS that vcpkg links to may not be the one you expect. You can specify this in VCPKG_PATH/triplets/install_triplet.cmake.
See: https://github.com/microsoft/vcpkg/issues/23308

Good news, this issue can be closed.
My GitHub runner job was structured like this:

Set up a Conda environment via the GitHub Action conda-incubator/setup-miniconda
Install C++ REST SDK using vcpkg install cpprestsdk:x64-windows
Set up Visual Studio shell via the GitHub Action egor-tensin/vs-shell

Now, I inverted the order of the first two steps, therefore placing the vcpkg step first, and the issue is gone!
I am convinced that the cause was "compiling some object files/static libraries with VS 2022, but performing the final link with VS 2019". I did not investigate further though. Thank you for the support.


suggestion for the centos on odroid c2 wiki

I found your wiki for using centos with the odroid c2, https://github.com/umiddelb/aarch64/wiki/Install-CentOS-7-on-the-ODROID-C2
Very nice writeup. I had one minor suggestion for it that simplifies the losetup step. I'm somewhat partial to using kpartx which handles identifying the partition offsets and makes the device available via loopback. There's an example of using it in the README at  http://mirror.centos.org/altarch/7/isos/aarch64/ReadMe.txt
Thanks again for the write-up!

Thank you very much! Indeed this is much easier and I wasn't aware of kpartx before.

Btw. I'm trying to adapt my automated setup procedure in order to create a CentOS install for my various ARM devices. The setup procedure would be much easier if you / CentOS consider to provide a rootfs only tar archive as well (like the Ubuntu people do with Ubuntu Core).
Another interesting addition would be a script which checks the presence of necessary kernel features (from the CentOS perspective), like check-config.sh does for Docker related requirements, because many ARM boards are still not able to run a mainline kernel.

I'll consider doing a rootfs build. I had initially NOT done one to try to help force the 'use UEFI' idea, but as much as I want to push UEFI, I want people using our distro as well.
As to the mainline kernel bit, yes. That's a bit of pain where I'm not overly happy about the current state of things, mostly because the vendor kernels almost never get security updates, or any sort of update for that matter.

I'll consider doing a rootfs build.

Cool, beside Ubuntu, Archlinux is providing this as well (ARMv8 only).

I had initially NOT done one to try to help force the 'use UEFI' idea, but as much as I want to push UEFI, I want people using our distro as well.

I'm not happy with u-boot's current status, too. I started to consolidate the u-boot implementations I was faced with in order to archive some common boot behaviour using u-boot macro language. And u-boot will remain reality for SBCs derived from Mobile/Tablet SoCs as long as UEFI is only indented for ARM server platforms. And chainloading UEFI on u-boot (like chainloading GRUB on u-boot) doesn't sound very reasonable.

That's a bit of pain where I'm not overly happy about the current state of things, mostly because the vendor kernels almost never get security updates, or any sort of update for that matter.

I totally agree. The consideration user base vs. rigour applies here as well. But having this check would vastly improve the adaption of CentOS for this kind of devices.

And sometimes the rhelsa kernel sources might be too old for recent ARM mainlining efforts.

In the meantime, I got CentOS 7 up and running on the PINE64+(ARMv8) and the ODROID-XU4(ARMv7) as well. It seems that the rootfs setup and package availability differ between ARMv7 and ARMv8 (e.g. ARMv7 doesn't include a Docker package and using the f23's Docker package turns the CentOS7 userland into something hybrid). There is no EPEL for ARM, isn't it?

No epel yet, though that will happen. Excellent news on the pine64! I'm traveling this week and part of next, but I'll try to get the rootfs built for you to test. Thanks again for your work.

Out of curiosity, do you have the pine64 image instructions available someplace? I'd like to see if we can promote it to get some more traction for aarch64. Also, I'd like to send you some CentOS swag for the work you've put in on this, if you wouldn't mind emailing me privately to work out the details.

No epel yet, though that will happen.

I've seen the announcement for EPEL on aarch64 and now subscribed to the arm-dev mailing list. So we may close this conversation here.


Whole minutes and seconds display ambiguously

Formatting a duration of whole minutes results in only the minutes as digits.
So a duration of say 600 seconds will be formatted as "10" and a duration is 10 seconds is also formatted at "10".
I would have expected the 600s to show as "10:00" or perhaps "10m" - and the 10s as "00:10" or "10s"

The moment maintainers had a few issues with my plan to save and access the input data on a moment object. I should have time to revisit this issue in the coming week, and I hope to have this addressed soon in a version 2.0.0 release of this plugin.

Sort of related:
moment.duration('0:15').format('hh:mm')
// 15

I would have expected "00:15".
What's your ETA on 2.0 release? Thanks.

Oh never mind, my last comment. The following settings fixes that:
moment.duration.fn.format.defaults.trim = false

@jacobg: ETA on 2.0 release... right! Should really get back around to that!

@jacobg , oh THANKS, mate!


feat(cart): add image and abridged_description to the cart item

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the new behavior?
We're going to need the cart item image for sure. We might need the abridged_description. The normal description field is way too long for a cart item.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

I'd veto the description. I don't see a purpose for it 99.9% of the time in the cart. that's not critical information most of time.


[JEI] Recipe for alchemical recombulator is sometimes wrong

If you press U on and Archaic Circuit to get to the recipe it shows the ashes go on Dawnstone and Lead which is wrong. However if you press R on the recombulator it shows the correct recipe of Copper+Lead Aspectuses (aspecti?)
https://i.imgur.com/K6fbSWL.png (U on circuit)
https://i.imgur.com/5XULzoJ.png (R on recombulator)
Soot version: 0.18hotfix
Embers version: 0.230
JEI version: <IP_ADDRESS>

update Soot to 1.x+ and Embers to Embers Rekindled


Facing Scaling issue on cpu (arm and x86).

Description
i was using an custom script and it was slow as per my expectation so inspection i observed that it is not scaling properly.
jax -> 0.4.35
jaxlib -> 0.4.35
ubuntu -> 20.04
performance

script

System info (python version, jaxlib version, accelerator, etc.)
script
"""
import jax
import jax.numpy as jnp
from jax import random
import time
def initialize_params(rng, input_size, hidden_size, output_size):
rng_hidden, rng_output = random.split(rng)
return {
"W_hidden": random.normal(rng_hidden, (input_size, hidden_size)) * jnp.sqrt(2 / input_size),
"b_hidden": jnp.zeros(hidden_size),
"W_output": random.normal(rng_output, (hidden_size, output_size)) * jnp.sqrt(2 / hidden_size),
"b_output": jnp.zeros(output_size),
}
def forward(params, x):
hidden = jnp.dot(x, params["W_hidden"]) + params["b_hidden"]
hidden = jax.nn.relu(hidden)
output = jnp.dot(hidden, params["W_output"]) + params["b_output"]
return output
batched_forward = jax.vmap(forward, in_axes=(None, 0))
if name == "main":
input_size = 512
hidden_size = 1024
output_size = 10
batch_size = 1000000
rng = random.PRNGKey(0)
params = initialize_params(rng, input_size, hidden_size, output_size)
inputs = random.normal(rng, (batch_size, input_size))
start_time = time.time()
outputs = batched_forward(params, inputs)
end_time = time.time()
print("Inference output shape:", outputs.shape)
print(f"Batched inference time for {batch_size} samples: {end_time - start_time:.4f} seconds")

"""

@mjwillson , @kashif, @dlwh, @d0k   can you please look into it!


Adding github actions automation to run tests

This will mean tests are run automatically on the main branch and pull requests

cc: @yakkomajuri @merrcury


build 构建项目时错误，缺少索引签名

使用arco初始创建，Arco Pro 项目，未做修改，build构建，缺少索引签名。
手动build，或使用github自动化构建，node14和node16环境均报错，详细如下：
Run yarn install
yarn install
yarn build
shell: /usr/bin/bash -e {0}
yarn install v1.22.18
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning gifsicle > bin-build > tempfile ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning stylelint ><EMAIL_ADDRESS>Use the original unforked package instead: postcss-markdown
warning stylelint-config-rational-order > stylelint > micromatch > snapdragon ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
warning stylelint-config-rational-order > stylelint > postcss-markdown > remark > unified > @types/vfile ><EMAIL_ADDRESS>This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
warning stylelint-config-rational-order > stylelint > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
warning stylelint-config-rational-order > stylelint > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
warning stylelint-config-rational-order > stylelint > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning vue-tsc ><EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/vue-language-service. Install using @volar/vue-language-service instead.
warning vue-tsc > vscode-vue-languageservice ><EMAIL_ADDRESS>WARNING: This project has been renamed to @johnsoncodehk/html2pug. Install using @johnsoncodehk/html2pug instead.
warning vue-tsc > vscode-vue-languageservice ><EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/pug-language-service. Install using @volar/pug-language-service instead.
warning vue-tsc > vscode-vue-languageservice ><EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/typescript-language-service. Install using @volar/typescript-language-service instead.
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^6.8.0 || ^7.2.0".
[5/5] Building fresh packages...
success Saved lockfile.
$ husky install
husky - Git hooks installed
Done in 48.07s.
yarn run v1.22.18
$ vue-tsc --noEmit && vite build --config ./config/vite.config.prod.ts
Error: src/views/user/setting/components/user-panel.vue(5,10): error TS2322: Type '(options: RequestOption) => Promise' is not assignable to type '(option: RequestOption) => UploadRequest'.
Type 'Promise' is not assignable to type 'UploadRequest'.
Index signature for type 'string' is missing in type 'Promise'.
Error: src/components/global-setting/form-wrapper.vue(6,6): error TS2322: Type 'string | number | boolean' is not assignable to type 'number | undefined'.
Type 'string' is not assignable to type 'number'.
Error: src/components/global-setting/form-wrapper.vue(11,6): error TS2322: Type 'string | number | boolean' is not assignable to type 'boolean | undefined'.
Type 'string' is not assignable to type 'boolean | undefined'.
Error: src/views/user/setting/components/enterprise-certification.vue(12,8): error TS2322: Type '({ label: string; value: number; } | { label: string; value: string; })[]' is not assignable to type 'DescData[]'.
Type '{ label: string; value: number; } | { label: string; value: string; }' is not assignable to type 'DescData'.
Type '{ label: string; value: number; }' is not assignable to type 'DescData'.
Types of property 'value' are incompatible.
Type 'number' is not assignable to type 'string | RenderFunction'.
Error: src/views/dashboard/workplace/components/quick-operation.vue(12,37): error TS2322: Type '{ text: string; icon: string; }' is not assignable to type 'string | number | symbol | undefined'.
Error: src/views/dashboard/monitor/components/data-statistic-list.vue(25,5): error TS2305: Module<EMAIL_ADDRESS>has no exported member 'TableColumn'.
Error: src/views/user/setting/components/user-panel.vue(22,10): error TS2322: Type '({ label: string; value: string | undefined; } | { label: string; value: number | undefined; })[]' is not assignable to type 'DescData[]'.
Type '{ label: string; value: string | undefined; } | { label: string; value: number | undefined; }' is not assignable to type 'DescData'.
Type '{ label: string; value: string | undefined; }' is not assignable to type 'DescData'.
Types of property 'value' are incompatible.
Type 'string | undefined' is not assignable to type 'string | RenderFunction'.
Type 'undefined' is not assignable to type 'string | RenderFunction'.
Error: src/views/dashboard/workplace/components/popular-content.vue(31,12): error TS2322: Type 'PopularRecord[] | undefined' is not assignable to type 'TableData[] | undefined'.
Type 'PopularRecord[]' is not assignable to type 'TableData[]'.
Type 'PopularRecord' is not assignable to type 'TableData'.
Types of property 'key' are incompatible.
Type 'number' is not assignable to type 'string'.
Error: src/views/list/card/components/quality-inspection.vue(50,14): error TS2322: Type '{ value: unknown; label: string; }[] | undefined' is not assignable to type 'DescData[] | undefined'.
Type '{ value: unknown; label: string; }[]' is not assignable to type 'DescData[]'.
Type '{ value: unknown; label: string; }' is not assignable to type 'DescData'.
Types of property 'value' are incompatible.
Type 'unknown' is not assignable to type 'string | RenderFunction'.
Error: src/views/list/search-table/index.vue(40,22): error TS2322: Type 'Options[]' is not assignable to type '(string | number | SelectOptionData | SelectOptionGroup)[]'.
Type 'Options' is not assignable to type 'string | number | SelectOptionData | SelectOptionGroup'.
Type 'Options' is missing the following properties from type 'SelectOptionGroup': isGroup, options
Error: src/views/list/search-table/index.vue(52,22): error TS2322: Type 'Options[]' is not assignable to type '(string | number | SelectOptionData | SelectOptionGroup)[]'.
Error: src/views/list/search-table/index.vue(75,22): error TS2322: Type 'Options[]' is not assignable to type '(string | number | SelectOptionData | SelectOptionGroup)[]'.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 2.

ts 错误问题，可以参考下 https://arco.design/vue/docs/pro/faq#构建相关