Question: How similar or dissimilar is this compared to Hypergradient Descent?

Congratulations on the new optimizer, excited to try it out! In our fastai discussion group it was brought up that your optimizer seems similar to HGD. Would you be able to summarize the key differences between the two for me/us? :) Thank you in advance!
https://github.com/gbaydin/hypergradient-descent

The very general idea is similar for Adam, AdaBelief and HGD I guess, adapt stepsize for each element. The key difference is how to adapt: Adam scales by smoothed version of gradient^2, AdaBelief scales by smoother (change in gradient)^2, the reddit discussion points to "diffgrad" which scales by sigmoid( change-in-grad ); HGD is different, it hard-updates the lr, by the grad w.r.t lr (for each element).
I'm somehow concerned about HGD, because it's equivalent to setting extra N parameters, where N is the dimension of network parameters, and perform gradient descent on the 2N parameters. The training is on 2N params, though inference is on N parameters. Not sure if this is a big issue, but HGD is still a very interesting direction.

Awesome! Thank you very much! And yes fastai has an open discord :) We're talking about this in the #chitchat channel, I'll send you an email with the invite in a moment (as I saw you posted your email in the Discord)


Mamba v0.4 Marketing Banner

This issue covers the creation of the marketing banner for v0.4.
@ixje could you please provide a few bullets of key features?
FYI @J-G-W

Native smart contract support (NEP-5 and others)
Generic smart contract execution support

It's kind of hard to break it down into smaller pieces than this. It's a huge update, but it all falls under these 2 points. If it  works out as planned before the release I might be able to add

Blockchain helper class for supporting node like capabilities

The latter basically means that you can take the existing network syncing helper classes, combine them with the blockchain helper class to form a basic node that will collect all the blocks, process them and persist them in the select storage format.

@ixje @lllwvlvwlll  Let me know when the final copy has been decided and I'll amend and send the final artwork.


Saving runelite configuration presets

Is your feature request related to a problem? Please describe.
The particular settings I like to use vary by activity. It can take a while to go through multiple settings when switching between activities.
Describe the solution you'd like
The ability to save and give a name to various configuration presets.
Describe alternatives you've considered
N/A
Additional context
N/A

Duplicate of #2220


Container image is not published

Even though there is a pipeline, I cannot find the image on quay.io or dockerhub.

The image is available on our own Harbor: https://release.osism.tech/notes/5.0.0.html#openstack-image-manager.
harbor.services.osism.tech/osism/openstack-image-manager:latest


Adding fix for issue 5451 "putText fails with empty std::string"

:+1:

@sturkmen72 , so it seems, 2 seperate(but binary identical) fixes were merged for the same thing in master - wasted time, but no further harm done, no ?


Can we add custom field with logs

Currently we are storing the following field in table

id,
level,
message,
timestamp,
metadata

Though I want to add one more field which is userId along with the data so I can filter out the logs for particular user.
So do we have such feature or can you guide me if I want to add custom field in table?

You can add it to the logged object and it will be automatically added to the meta field as property, which can be used later for filtering (for example, using json/jsonb in postgress) this is a common way for Winston transports
I thought about how this could be expanded, but have not yet come to a satisfying way, can you suggest your own?


10.0/2.0 upgrades

Upgrades for psc 0.10 / 2.x core libs.

@garyb you interested in this one? spotted you're not watching

👍 LGTM, thanks!

Thanks!


Extract file-drop custom element to a package and include

We need to create small custom elements that we can just include in the project so that others can use our work and it's easier to maintain

This one's done


Correct types for const arrays

I wrote a similar function to retrieve a random element from an array, but I encountered a problem when I didn't consider const arrays. With certain TypeScript settings, it even throws an error. However, even if it doesn't, it's still better to specify a readonly array so that the return type is correctly parsed.
TypeScript can be tricky sometimes.

Examples

.

PS
Also, is there any particular reason why you don't use a shorthand arrow function like this?
const oneOf = <T>(arr: T[] | readonly T[], engine: Engine = defaultEngine): T =>
   arr[intRange(0, arr.length - 1, engine)];

I couldn't find any ESLint rules regarding this.

looks good, I wasn't aware of this specification.
as for your PS: i believe that the shorthand return is more difficult to read.  I use it sparingly, if ever with TypeScript, due to the nature of functions having longer declarations with TS


normal deployment is bad after Canary Rollout

Describe the bug

the problem is: the workflow is always running and the message is "local/default//testdeploy is not healthy(Wait)"
To Reproduce

use oamdev/hello-world to create an application and reproduce the problem with the following steps:

deploy the application with normal workflow
modify an environment parameter and deploy the application with canary-rollout workflow
modify the environment parameter and deploy the application with normal workflow
the problem is coming: the workflow is always running and the message is "local/default//testdeploy is not healthy(Wait)"

Expected behavior

the application can deploy normally.
Screenshots

KubeVela Version

v1.8.0
Cluster information

local cluster
Additional context

Can you provide the rollout's status currently?

Can you provide the rollout's status currently?

Please use kubectl get rollout  to display the verbose info of rollout.

verbose

Please get the related rollout detail into with -oyaml flag.

Please get the related rollout detail info with -oyaml flag.

kubectl get rollout -oyaml
apiVersion: v1
items:

apiVersion: rollouts.kruise.io/v1alpha1
kind: Rollout
metadata:
annotations:
app.oam.dev/appAlias: sectechops
app.oam.dev/appName: sectechops
app.oam.dev/deployVersion: "20230508081419955"
app.oam.dev/last-applied-configuration: '{"apiVersion":"rollouts.kruise.io/v1alpha1","kind":"Rollout","metadata":{"annotations":{"app.oam.dev/appAlias":"sectechops","app.oam.dev/appName":"sectechops","app.oam.dev/deployVersion":"20230508081419955","app.oam.dev/last-applied-time":"2023-04-19T11:54:48Z","app.oam.dev/publishVersion":"workflow-default-canary-20230508101535983","app.oam.dev/workflowName":"workflow-default-canary","controller.core.oam.dev/skip-resume":"true","oam.dev/kubevela-version":"v1.7.7","rollouts.kruise.io/rolling-style":"partition"},"labels":{"app.oam.dev/app-revision-hash":"98c1f08cc697ae3f","app.oam.dev/appName":"sectechops","app.oam.dev/appRevision":"sectechops-v27","app.oam.dev/cluster":"local","app.oam.dev/component":"sectechops","app.oam.dev/name":"sectechops","app.oam.dev/namespace":"default","app.oam.dev/resourceType":"TRAIT","app.oam.dev/revision":"","app.oam.dev/source-of-truth":"from-velaux","oam.dev/render-hash":"ba467f54a0fbbe28","trait.oam.dev/resource":"rollout","trait.oam.dev/type":"rolling-release"},"name":"sectechops","namespace":"default"},"spec":{"objectRef":{"workloadRef":{"apiVersion":"apps/v1","kind":"Deployment","name":"sectechops"}},"strategy":{"canary":{"steps":[{"pause":{},"weight":0}]}}}}'
app.oam.dev/last-applied-time: "2023-04-19T11:54:48Z"
app.oam.dev/publishVersion: workflow-default-canary-20230508101535983
app.oam.dev/workflowName: workflow-default-canary
controller.core.oam.dev/skip-resume: "true"
oam.dev/kubevela-version: v1.7.7
rollouts.kruise.io/hash: b84b4z46dd44v266v466x9b8wx454z44zczb4fv6x9d4w4bx5w6f4vdd47zd465v
rollouts.kruise.io/rolling-style: partition
creationTimestamp: "2023-05-08T08:14:20Z"
finalizers:

rollouts.kruise.io/rollout
generation: 4
labels:
app.oam.dev/app-revision-hash: 98c1f08cc697ae3f
app.oam.dev/appName: sectechops
app.oam.dev/appRevision: sectechops-v27
app.oam.dev/cluster: local
app.oam.dev/component: sectechops
app.oam.dev/name: sectechops
app.oam.dev/namespace: default
app.oam.dev/resourceType: TRAIT
app.oam.dev/revision: ""
app.oam.dev/source-of-truth: from-velaux
oam.dev/render-hash: ba467f54a0fbbe28
trait.oam.dev/resource: rollout
trait.oam.dev/type: rolling-release
name: sectechops
namespace: default
resourceVersion: "14375281"
uid: 1ccc44be-06b9-40a3-b98a-da8179702a08
spec:
objectRef:
workloadRef:
apiVersion: apps/v1
kind: Deployment
name: sectechops
strategy:
canary:
steps:

pause: {}
weight: 0
status:
canaryStatus:
canaryReadyReplicas: 0
canaryReplicas: 0
canaryRevision: 74997d688d
currentStepIndex: 1
currentStepState: StepUpgrade
lastUpdateTime: "2023-05-09T02:35:56Z"
message: BatchRelease is at state , rollout-id , step 1
observedWorkloadGeneration: 43
podTemplateHash: ""
rolloutHash: b84b4z46dd44v266v466x9b8wx454z44zczb4fv6x9d4w4bx5w6f4vdd47zd465v
stableRevision: 598fd679fd
conditions:

lastTransitionTime: "2023-05-08T10:10:35Z"
lastUpdateTime: "2023-05-08T10:10:35Z"
message: Rollout is in Progressing
reason: InRolling
status: "True"
type: Progressing
message: Rollout is in step(1/1), and upgrade workload to new version
observedGeneration: 4
phase: Progressing

apiVersion: rollouts.kruise.io/v1alpha1
kind: Rollout
metadata:
annotations:
app.oam.dev/appAlias: testdeploy
app.oam.dev/appName: testdeploy
app.oam.dev/deployVersion: "20230509021403210"
app.oam.dev/last-applied-configuration: '{"apiVersion":"rollouts.kruise.io/v1alpha1","kind":"Rollout","metadata":{"annotations":{"app.oam.dev/appAlias":"testdeploy","app.oam.dev/appName":"testdeploy","app.oam.dev/deployVersion":"20230509021403210","app.oam.dev/last-applied-time":"2023-05-09T02:12:51Z","app.oam.dev/publishVersion":"workflow-default-canary-20230509021403213","app.oam.dev/workflowName":"workflow-default-canary","controller.core.oam.dev/skip-resume":"true","oam.dev/kubevela-version":"v1.8.0","rollouts.kruise.io/rolling-style":"partition"},"labels":{"app.oam.dev/app-revision-hash":"fa3b19c47738d088","app.oam.dev/appName":"testdeploy","app.oam.dev/appRevision":"testdeploy-v3","app.oam.dev/cluster":"local","app.oam.dev/component":"testdeploy","app.oam.dev/name":"testdeploy","app.oam.dev/namespace":"default","app.oam.dev/resourceType":"TRAIT","app.oam.dev/revision":"","app.oam.dev/source-of-truth":"from-velaux","oam.dev/render-hash":"17e36f331f110176","trait.oam.dev/resource":"rollout","trait.oam.dev/type":"rolling-release"},"name":"testdeploy","namespace":"default"},"spec":{"objectRef":{"workloadRef":{"apiVersion":"apps/v1","kind":"Deployment","name":"testdeploy"}},"strategy":{"canary":{"steps":[{"pause":{"duration":0},"weight":100}]}}}}'
app.oam.dev/last-applied-time: "2023-05-09T02:12:51Z"
app.oam.dev/publishVersion: workflow-default-canary-20230509021403213
app.oam.dev/workflowName: workflow-default-canary
controller.core.oam.dev/skip-resume: "true"
oam.dev/kubevela-version: v1.8.0
rollouts.kruise.io/hash: f85xvv65zz678z4x4w8xbw2677bbbzwzb9z4v94f8bv7x7b46vb7cz422fb745z8
rollouts.kruise.io/rolling-style: partition
creationTimestamp: "2023-05-09T02:14:03Z"
finalizers:

rollouts.kruise.io/rollout
generation: 3
labels:
app.oam.dev/app-revision-hash: fa3b19c47738d088
app.oam.dev/appName: testdeploy
app.oam.dev/appRevision: testdeploy-v3
app.oam.dev/cluster: local
app.oam.dev/component: testdeploy
app.oam.dev/name: testdeploy
app.oam.dev/namespace: default
app.oam.dev/resourceType: TRAIT
app.oam.dev/revision: ""
app.oam.dev/source-of-truth: from-velaux
oam.dev/render-hash: 17e36f331f110176
trait.oam.dev/resource: rollout
trait.oam.dev/type: rolling-release
name: testdeploy
namespace: default
resourceVersion: "14365427"
uid: 5c216ae8-6c66-456b-a16b-e73f6dcb75c5
spec:
objectRef:
workloadRef:
apiVersion: apps/v1
kind: Deployment
name: testdeploy
strategy:
canary:
steps:

pause:
duration: 0
weight: 100
status:
canaryStatus:
canaryReadyReplicas: 0
canaryReplicas: 0
canaryRevision: 5f668887c9
currentStepIndex: 1
currentStepState: StepUpgrade
lastUpdateTime: "2023-05-09T02:14:39Z"
message: BatchRelease is at state , rollout-id , step 1
observedWorkloadGeneration: 14
podTemplateHash: ""
rolloutHash: f85xvv65zz678z4x4w8xbw2677bbbzwzb9z4v94f8bv7x7b46vb7cz422fb745z8
stableRevision: 5fb95d5dbd
conditions:

lastTransitionTime: "2023-05-09T02:14:36Z"
lastUpdateTime: "2023-05-09T02:14:36Z"
message: Rollout is in Progressing
reason: InRolling
status: "True"
type: Progressing
message: Rollout is in step(1/1), and upgrade workload to new version
observedGeneration: 3
phase: Progressing
kind: List
metadata:
resourceVersion: ""

This is a bug in rollout controller and will be fixed soon.


Attach missing MetricCollectingService decorator globally if ArmeriaS…

…ettings.enableMetrics is true

Shouldn't we fix the logic that calling setupMetricCollectingService? https://github.com/line/armeria/blob/armeria-0.99.8/spring/boot2-autoconfigure/src/main/java/com/linecorp/armeria/internal/spring/ArmeriaConfigurationUtil.java#L339

Shouldn't we fix the logic that calling setupMetricCollectingService? armeria-0.99.8/spring/boot2-autoconfigure/src/main/java/com/linecorp/armeria/internal/spring/ArmeriaConfigurationUtil.java#L339

I didn't touch setupMetricCollectingService related code.

If we remove the deprecated XXXRegistrationBean, then we don't need to remove setupMetricCollectingService.
If we are going to release the next Armeria version without removing XXXRegistrationBean, then I think setupMetricCollectingService and related code should be removed.

If we are going to release the next Armeria version without removing XXXRegistrationBean, then I think setupMetricCollectingService and related code should be removed.

Yes, let's get rid of all deprecated methods from the next release 😉

For clarity, we are not going to remove XXXRegistrationBean in 0.99.9 release.
@imasahiro Could you remove setupMetricCollectingService(...)?

Sorry, I missed this part. 😅
https://github.com/line/armeria/blob/fbe90f0f2a952578012a552c26b3f4f8bdb33c8c/spring/boot2-autoconfigure/src/main/java/com/linecorp/armeria/internal/spring/ArmeriaConfigurationUtil.java#L301-L304

ah, removed

@imasahiro Compilation errors :wink:


New version: WAV v1.0.4

Registering package: WAV
Repository: https://github.com/dancasimiro/WAV.jl
Created by: @dancasimiro
Version: v1.0.4
Commit: 9322315c5e526ec5d41179aef314fd3e0b8abac6
Reviewed by: @dancasimiro
Reference: https://github.com/dancasimiro/WAV.jl/commit/9322315c5e526ec5d41179aef314fd3e0b8abac6#commitcomment-42949900

I will fix the compat range, as recommended. Please close this pull request.

I believe that I fixed the compatibility ranges, as recommended. However, the automerge/decision is failing and I do not understand the reason.

@dancasimiro you compat specification for julia https://github.com/dancasimiro/WAV.jl/blob/9322315c5e526ec5d41179aef314fd3e0b8abac6/Project.toml#L14 means your package is compatible with Julia v0.7 and then any release in the v1.x series from v1.5 onwards, which is quite interesting because you're saying that it's isn't compatible with versions 1.0-1.4, while being compatible with v0.7 (which is almost identical to v1.0.0).  You can read more in https://julialang.github.io/Pkg.jl/v1/compatibility/#Version-specifier-format-1.  I assume you just made a mistake?
The error above points out that you can't restrict the supported julia versions with a patch version (v1.0.3 -> v1.0.4), you need to bump at least the minor version for that (v1.0.3 -> v1.1.0)

Please try PR dancasimiro/WAV.jl#93 to fix this.

Thanks @mgkuhn  and @giordano. This PR is replaced by #23974.


Difficulty using nested partials

I'm having some trouble using partials nested in a folder; ex: {{> path/to/my/partial}}
Here's how I have things set up:
/server.js
/views/index.hbs
/views/cats/index.hbs
/views/cats/listing.hbs

Express configuration is like so...
var express = require('express');
var express_handlebars = require('express3-handlebars');
var router = express();

router.engine( 'hbs', express_handlebars({
    extname: '.hbs',
    partialsDir: __dirname +'/views'
}) );
router.set( 'view engine', 'hbs' );
router.set( 'views', __dirname +'/views' );

router.get( '/', function( req, res ){
    res.render('index');
});

Finally, imagine index.hbs is like so:

Index

{{> cats/index}}

I am getting same error, my config looks like this on express 4 and HB 4.0.5.
var hbs = exphbs.create({
    defaultLayout: 'main',
    helpers      : helpers,
    partialsDir: [
        'shared/templates/',
        'views/partials/'
    ]

and partial looks like
Example App: {{title}}
{{>icon_tag}}

please let me know the fix

Just in case someone still encounters this issue, for nested partials you need to add each individual partial path in the config.
Example:
/views/index.hbs
/views/cats/index2.hbs
/views/cats/listing.hbs

Then inside the view config be like:
partialsDir: [
    `${__dirname}/${viewPath}/views`,
    `${__dirname}/${viewPath}/cats`
  ]

From then we call each partial just like this:
{{> index}}
{{> index2}}
{{> listing}}


build(dev): update all nodejs packages

Lol @tylerbenson the more packages we have, the more people managing package lifecycle we need to deal with 😂


update backoff strategy to be exponential

The strategy backoff currently is linear with default values of 1second delay with 10 retries.
It should use an exponential backoff instead.
With default values of 10seconds defayl with 10 retries.
Because of OpenWhisk rate limit on trigger limits, it will return 429 statusCode.
OpenWhisk window for the rate limit is 1 minute.
I would make it on first 429 delay for 1 minute, if after 1 minute delay there is a another 429 then I would start exponential back off of 10 seconds (i.e. 10s, 40s, 90s, 160s. etc..)

resolved by PR #90


Debugging non-C# .NET projects (F#, VB.NET) fails due to missing .csproj file

What happened?
Expectation: When using --debugger-attach or VS Code to debug a non-C# .NET project, pulumi preview/up should build and attach to the target project.
What happens instead: it exits with the following message, indicating a failure to find a .csproj file:
[truncated]
    pulumi:pulumi:Stack MyStack  Build succeeded.
    pulumi:pulumi:Stack MyStack      0 Warning(s)
    pulumi:pulumi:Stack MyStack
    pulumi:pulumi:Stack MyStack  Time Elapsed 00:00:01.33
    pulumi:pulumi:Stack MyStack  'dotnet build -nologo MyProject.fsproj' completed successfully
    pulumi:pulumi:Stack MyStack  error: failed to find .csproj file, and could not start debugging
    pulumi:pulumi:Stack MyStack  1 error
Diagnostics:
  pulumi:pulumi:Stack (MyStack):
    error: failed to find .csproj file, and could not start debugging

When debugging an F# project (.fsproj) or VB.NET project (.vbproj), this file will never exist. This is because only .csproj files are searched for in pulumi-language-dotnet/main.go. This should be changed to also search for .fsproj and .vbproj files.
Additionally, the behaviour of searching for a project file is brittle. It does not respect the project file declared in Pulumi.yaml project settings:
name: MyPulumiFSharpProject
runtime: dotnet
main: MyProject.fsproj

Even with the above, the Go driver still uses the first .csproj found. If there are more than one .csproj (or a .csproj and .fsproj) in the same folder, the meaning of the arguments to dotnet build in main.go line 567 become ambiguous:
Diagnostics:
  pulumi:pulumi:Stack (MyStack):
    Found more than one project in `/workspace/MyProject`. Specify which one to use.

Solution: When debugging Pulumi .NET projects, the name property of the Pulumi.yaml project file should be respected, and its value should be added to the arguments passed to dotnet build. Per the docs:

For .NET projects, main can point to a .NET project file (e.g., example.csproj) and the file will be passed to dotnet run.

Example

Create an F# project with dotnet new classlib -lang "f#" -o MyPulumiProject and import NuGet dependencies for Pulumi.

Install the VS Code extension

Create a debugging profile. My launch.json:

    {
      "type": "pulumi",
      "request": "launch",
      "name": "pulumi preview",
      "command": "preview",
      "workDir": "${workspaceFolder}/"

    }

Launch and observe the debugging window.

The Go driver searches the child directories of the project folder in order to find a .csproj. This name is used to debug the corresponding .dll file. To confirm that main.go line 581 is the culprit, copy MyPulumiProject.fsproj to ./bin/MyPulumiProject.csproj and launch the debugger again. It works!

Output of pulumi about
CLI
Version      3.133.0
Go Version   go1.23.1
Go Compiler  gc

Plugins
KIND      NAME        VERSION
language  dotnet      unknown
resource  kubernetes  4.18.1
resource  random      4.16.5

Host
OS       darwin
Version  15.0
Arch     arm64

This project is written in dotnet: executable='/opt/homebrew/bin/dotnet' version='8.0.301'
[truncated]
Backend
Name           pulumi.com
[truncated]
Token type     personal

Dependencies:
NAME                                                   VERSION
Ben.Demystifier                                        0.4.1
FSharp.Core                                            8.0.400
Glob                                                   1.1.9
Google.Protobuf                                        3.28.2
Grpc.AspNetCore.Server                                 2.66.0
Grpc.AspNetCore.Server.Reflection                      2.66.0
Grpc.Core.Api                                          2.66.0
Grpc.Net.Client                                        2.66.0
Grpc.Net.Common                                        2.66.0
Grpc.Reflection                                        2.66.0
Microsoft.Extensions.DependencyInjection               8.0.0
Microsoft.Extensions.DependencyInjection.Abstractions  8.0.1
Microsoft.Extensions.Logging                           8.0.0
Microsoft.Extensions.Logging.Abstractions              8.0.1
Microsoft.Extensions.Options                           8.0.2
Microsoft.Extensions.Primitives                        8.0.0
Newtonsoft.Json                                        13.0.3
OneOf                                                  3.0.271
Pulumi                                                 3.67.1
Pulumi.FSharp                                          3.67.1
Pulumi.FSharp.Core                                     3.1.6
Pulumi.FSharp.Kubernetes                               4.16.0
Pulumi.FSharp.Random                                   4.16.3
Pulumi.Kubernetes                                      4.18.1
Pulumi.Protobuf                                        3.27.3
Pulumi.Random                                          4.16.5
Semver                                                 2.3.0
Serilog                                                4.0.1
Serilog.Extensions.Logging                             8.0.0
Serilog.Sinks.Console                                  6.0.0
System.Collections.Immutable                           8.0.0
System.Reflection.Metadata                             8.0.0
YamlConvert                                            2.1.1
YamlDotNet                                             15.1.2

Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for the detailed issue, @cagyirey!


[ja] Translate docs/tutorials/services/pods-and-endpoint-termination-flow/ into Japanese

This is a Feature Request

What would you like to be added

Translate https://kubernetes.io/docs/tutorials/services/pods-and-endpoint-termination-flow/ into Japanese
Why is this needed
Comments

/language ja
/assign

/language ja

/triage accepted

Fixed by #40199


Use AssertJ's Atomic*Assert support

AssertJ supports asserting on AtomicInteger and friends so there's no need to call .get() explicitly.

Incorporated into https://github.com/dropwizard/dropwizard/pull/4571


x-labels filter option

With a few options for this type of feature begin around at the moment i though i would add in my way of achieving it. It's basically a function that returns true if the label is to be filtered out (and not show) or false if it is to not be filtered out (shown). The reason i went for this method is it gives more control over the final output.
The function is given the value of the label, the index and the full label array so that all of these can be considered when deciding to filter the label.
a few examples
filter out by index every other label

http://jsfiddle.net/leighking2/9770Lwtc/

show first and last label

http://jsfiddle.net/leighking2/uz8ot1mq/

show first last and x number of labels to create a spread (crap explanation but when you see it you should understand what i mean)

http://jsfiddle.net/leighking2/7nn2s9kt/

show only labels that contain a 2 in them

http://jsfiddle.net/leighking2/mpkv1zbz/

I also did not touch the rotation of the labels because i found that when they are rotated it is clear which point the label is attached to, where as when you ignore the now missing labels and don't rotate, the label will span several points and it can be unclear which one it is attached to.

Just what i needed, thanks !

On the programatic side of things, I love this solution.  Great control, simple to understand.  On the responsive side of things, all we need now is a way to deal with dynamic width scales, etc.

@tannerlinsley do you think then it would also be useful to be told the total width of the x axis and the width of each label so a decision could be made based on that information. Or to have a separate option that could just be set to true to filter labels if they are going to overlap, this would allow fine control for people who wanted it or just a plain set and forget option for those who only care that the graph doesn't look stupid when displaying lots of data.

For dynamic scale, i did something like that in my js script
                var chartWidth=$("#char").parent().width();
                var minStepPx=50;

                var stepPx=chartWidth/(data.length);
                var step=Math.ceil(minStepPx/stepPx);

                [...]

                labelsFilter: function (value, index, labels) {
                        return (index  % step) != 0;
                },

In my #864 PR, I fiddled my way into a maxAxisHeight that would only let the labels rotate until 90 degrees or until they hit the max height. Then depending on how much rotation was done, labels would be removed until none were overlapping.  @etimberg is messing around with it a bit more, so it could end up being the other end of the solution.  We'll see if it's elegant or not.

Has there been any more conversation on what route Chart.js is going to take for this kind of feature? I see there is a Rewrite axis/scale code milestone but doesn't seem to be much happening of late between any of the options.

@leighquince: This is a major targeted feature for the June Chart.js 2.0 release. @etimberg has already done the bulk of rewriting the scale code to make it more customizable. @tannerlinsley rewrote the chart bootstrapping so that chart manipulation and updating can happen easily from the original config object. The core dev is done, and now the two of them are polishing it and extending the new functionality to all the core chart types.

In addition to what @derekperkins mentioned, check the v2.0 milestone for the things I've tentatively targeted for that release.

Cheers guys for the update awesome to know,  look forward to it.

We've recently announced a feature complete status for v1.x and will only be accepting bug fixes for v1.x. Be sure to take a look at v2.0-dev and it's new features that are either finished or currently under development.  If you see your feature is still not implemented, feel free to submit another PR to the v2.0-dev (or later) branch for your feature.

I really like this approach. Is anyone (@leighquince?) going to implement it for v2.x?
If not I can do it.

@olyckne you can do this with the callback that generates labels or with that hook. In the callback sturdiness null or undefined will hide the grid line. Return an empty string to simply hide the label.

@etimberg the callback didn't produce the result I wanted. I think the algorithm that automatically skips some labels interfere with the callback. I want to show every 10th label and sometimes it did, and sometimes it showed a lot less. Depending on the screen size.
Guess you could consider it a bug.

Yeah, could you file that as a separate issue?


Playback effect is laggy

Hello, I use your example to play an mp4 video, and the playback effect is stuck
https://github.com/user-attachments/assets/d84e44cf-8ee9-4696-89db-dbb80e0e9aa3

There will be no lag after packaging and compilation, but there will be lag during development


76 bug fixed seed leads to different results

fixes the same seed giving different results, by creating one random state variable for the Wildboottest class

Sorry, I am just getting back to this, I've decided to push a legacy R porject I had a little bit. wildrwolf is now submitted to CRAN and I am shifting focus to wildboottest again.
There are potentially a few problem with this PR, now that I have started to test it. For example, it is now necessary to provide a seed to wildboottest. This is probably not desirable (?).
E.g. this here fails:
from wildboottest.wildboottest import wildboottest
import pandas as pd
import numpy as np
import statsmodels.formula.api as sm

df = pd.read_csv("https://raw.github.com/vincentarelbundock/Rdatasets/master/csv/sandwich/PetersenCL.csv")
df['treat'] = np.random.choice([0, 1], df.shape[0], True)
model = sm.ols(formula='y ~ treat', data=df)

wildboottest(model, param = "treat", cluster = df.year, B= 999)
# AttributeError: 'WildboottestCL' object has no attribute 'rng'

Also, it looks like numba does not work with the 'new' random number generators. This does not affect the wild cluster bootstrap, but the heteroskedastic bootstrap. I see three options:

we create all weights matrices outside of the bootstrap loop. Potential problem: it's a N x B matrix, which potentially gets very large and time consuming to create
we drop numba support for the heteroskedastic bootstrap. Problem: it then is very slow.
we drop the random.default_rng.choice() for the heteroskedastic bootstrap in favor of the global random seed (which does not seem to be recommended).

What do you think @amichuda?

Yeah, I need to push a new change then. A random generator should be created if no seed is provided.
We can do that when defining self.rng so no need to have a setter method.

Also, I think we can do without generating a random seed, I think rng can take no seed?

For numba, I have to look at it, that's a pretty bad bug. I wouldn't want to drop numba because it makes things a lot faster.

One thing we can do is to refactor the weighting so that it calls a function that has the numba in it, not create an inner function in the method that's called.
@s3alfisc  can you point me to the line where the problem arises? I'm on my phone so can't look now.

Yeah, I need to push a new change then. A random generator should be created if no seed is provided.
We can do that when defining self.rng so no need to have a setter method.

I have already added a self.rng with dd9b58b in case no seed is provided. Basically it draws a random integer & should be reproducible if a global seed is set.

@s3alfisc can you point me to the line where the problem arises? I'm on my phone so can't look now.

The bug occurs here.
Note that this is only a problem for the HC bootstrap, where the weights matrix is produced within the numba-compiled for loop.
In the HC bootstrap, I don't use the weights class, as numba cannot handle the rng seed generator - that's why you'll see np.random.choice() and not np.random.default_rng().choice() being called.

One thing we can do is to refactor the weighting so that it calls a function that has the numba in it, not create an inner function in the method that's called.

I think I don't fully get this and if it would help. But one fix would definitely be to compute the weights prior to the bootstrap for loop, with the caveat that the produced weights matrix would be super large.

I have finally added CI support for tests so that we can get actual feedback on all commits. Currently only Python 3.9 (feel free to add other Python version if you think it is a good idea). Tests currently fail, I am investigating.

I have finally added CI support for tests so that we can get actual feedback on all commits. Currently only Python 3.9 (feel free to add other Python version if you think it is a good idea). Tests currently fail, I am investigating.

That's great! You're being very prolific right now! Sorry I haven't had a chance to look at this again yet. I'll find time during the week.

Quite a few errors in the unit tests 😅

Regarding the use of np.random.seed() within wildboottest, here is one workaround:
If users provide a seed as a function argument to wildboottest, use set.random.seed() within the function. But before doing so, store the state of the 'global rng' via np.random.get_state(). Then set the seed, then restore the state to the 'prior' state of the rng within the function via np.random.reset_state() Example:
np.random.seed(123)
x = np.random.get_state()
np.random.normal()
# -1.0856306033005612
np.random.set_state(x)
np.random.normal()

Do you think this is safe to use? I'd say yes?

Are you saying, don't use default_rng at all?
Also I don't think we need a set_seed function. We can just put it in init.

The idea would be to use default_rng() when possible, i.e. for the cluster bootstrap, but to use the 'deprecated' np.random.seed with the trick described above, when default_rng() is not supported by numba.

@amichuda I believe all unit tests are now fix. Please feel free to merge and publish a new version, in case you are happy with my changes =)

Hi Alex,
Thank you so much for doing this. I was really crammed with work, but you
pulled through. Thank you!
On Thu, Feb 16, 2023, 4:50 PM Alexander Fischer @.***>
wrote:

@amichuda https://github.com/amichuda I believe all unit tests are now
fix. Please feel free to merge and publish a new version, in case you are
happy with my changes =)
—
Reply to this email directly, view it on GitHub
https://github.com/s3alfisc/wildboottest/pull/78#issuecomment-1433758404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQVPBGA7DM5NQI3H3T5LFLWX2OK7ANCNFSM6AAAAAAT6OQ6VM
.
You are receiving this because you were mentioned.Message ID:
@.***>

So is this no numba support at all or no numba for heteroscedastic bootstrap?
Sorry I've been slammed. I should be less busy this week and I'm going to look at the outstanding issues with this PR

Hi - I dropped numba support for the heteroskedastic bootstrap (for now), as I simply couldn't get random number generation within a numba compiled function to work. Not sure what I am doing wrong.
For the cluster bootstrap, the for loop is still jit compiled - there are no problems as the weights matrix is computed outside of the compiled bootstrap loop.
Also, don't worry - this is supposed to be fun for both of us (at least most of the time, I hope) =)

Finally all tests pass!


Cannot upgrade to LGTV Companion x64 v3.1.9: "The error code is 2503"

While the upgrade went flawlessly in my Windows 11 Pro partition the same didn't happen in my other Windows 10 Pro partition...
During the installation this error window came up and I couldn't end the setup.

Hi @Cr4z33 google shows me this is likely an issue with writing to the temp directory while installing. Why, I've no idea.
I came across this fix that you may want ro look into:
1 Navigate to the Windows Temp folder located at c:\windows\temp.
2 Make sure you uncheck the read only button.
3 Switch to the Security Tab and choose Administrators and make sure it is highlighted. Make sure that there is a check box next to Full Control for the Administrators and Users group
Let me know if this helps

Thank you @JPersson77 for the suggestion, but unfortunately the error window keeps popping up.
As this is not a LGTV Companion issue I will keep investigating further by Google searching.


feat: implement strimzi-ui build

Offers an implementation of the UI build detailed in #2
Adds extra documentation/scripts to allow easy running of the build
Adds a UI (which will be replaced) which makes use of this build. All elements of the build bar fonts are demonstrated in this simple 'Hello world' UI.

Closes: #1

@nictownsend / @seanforyou23 would you mind reviewing this?

Thank you all - please if all are happy, please feel free to merge at the earliest convenience


[qsr_lib] Switch from pickle to json

I personally never use pickle and don't like that you can just pickle anything and send it as it is highly ambiguous and not very reusable. If we want to have a C++ client for the lib for example, I expect to run into serious problems. Also: http://www.benfrederickson.com/dont-pickle-your-data/
I propose to switch to json as I already do here as well. I'm happy to give that ago if you don't want to @yianni
The only question is which milestone this would go into.
Of course I am open for a discussions.

Need to meditate on this. I will get back to you as it is not majorly urgent, is it?
From what I recall pickle is used for serialization during ROS service call and nowhere else. Have you seen it anywhere else? Anyway if we agree to do so (need to read and think about it before making an opinion), I would probably go for 0.3 or something as I doubt that this particular internal mechanism has been touched by anyone else other than me so far.

Or 0.2.x

It's not urgent, no. Just thought that this needs to be done at some point if we want to enable the use of the lib via C++ as well as afaik pickle only serialises python objects.

@cdondrup
I had a go on this. Unfortunately, it is not straightforward the slightest because json only supports serialisation of booleans, numerics and strings. This means that the whole qsrlib_io package will have to provide json encoders and decoders. And even then it is still not exposed to C, but merely might allow to use python code in C (for example see here), which might be better doing it in python in the first place. Proper exposure to C might require rewriting in C the qsrlib_io package, something that is quite time consuming.
I have no objection against doing it, but given the above reasons and since that there has not been even a single request for this, I am not going to do it.
Unless you want to give it a go, more than welcome to, I will mark it as wontfix and close the issue.


[Event Request] Table 5965 - Function "UpdateCust" -> Add publisher event "OnBeforeUpdateCust"

Dear Microsoft,
I would like to request an event at the beginning of the function "UpdateCust" in T5965 - "Service Contract Header":

Event Name -> OnBeforeUpdateCust
Rec -> (Var) Record - Service Contract Header (T5965)
ContactNo -> Code[20]
isHandled -> (Var) Boolean
The purpose is to be able to do some logic before updating the customer information.
Thank you.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Can you use imageAI to delete a camera based on what it detects?

For a project I am making it so a motion sensor only records when specifically a cat is there, Can I do that Live or at least have a program to delete videos without the cat? if so, how?

Hello,
Kindly follow the link below to a tutorial  I have published on Live
detection. You can modify the code to suit your needs.
https://heartbeat.fritz.ai/analyze-and-visualize-detected-video-objects-using-keras-and-imageai-d84c99b0ae8e
Regards.
Moses Olafenwa,
Creator of ImageAI,
Co-Founder and CEO at DeepQuest AI.
(A brand of AI Commons Global Limited)
Phone: +234<PHONE_NUMBER>,<PHONE_NUMBER>9.
Email<EMAIL_ADDRESS>Website: https://www.deepquestai.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, Jul 18, 2019 at 8:44 PM Stuffffffffff<EMAIL_ADDRESS>wrote:

For a project I am making it so a motion sensor only records when
specifically a cat is there, Can I do that Live or at least have a program
to delete videos without the cat? if so, how?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OlafenwaMoses/ImageAI/issues/248?email_source=notifications&email_token=ABNC33VXRG5RDA2XNGRPMLDQADB27A5CNFSM4IE7BJ72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAC6OWA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNC33WUW5MY2AJC7JL5VDDQADB27ANCNFSM4IE7BJ7Q
.


Is it possible to delete a queue ?

I have a topic with a single message scheduled for delivery each X minutes.
This message I send once the app bootstraps as a kind of scheduler:
send(
 'queue://',
  { data: {} },
  {
    schedule: {
      cron: `*/5 * * * *`,
    },
  }
);

I want to be able to delete the queue before creation. (recreate, before sending the first message).
Thanks a lot

Hello, how did you achieve it?

Worth noting, that if on a queue there is no activity (no active consumers or no pending messages), the broker itself will delete that queue (I think after 10 minutes by default, but don't quote me on that).


ChatGPT text is not copying after plus upgrade

I have upgraded to ChatGPT Plus member. The "Copy to clipboard" option is not visible for the responses of chatGPT4. The attached image is a reference.

Thank you for reporting this issue! This seems like it is the same issue associated with #2 so I'll close this and continue this on the other thread!


[WFLY-13730] Work around problem by hiding requirement relationship f…

…rom Galleon
https://issues.redhat.com/browse/WFLY-13730

If you create a follow up issue I can remove the dependency on the JACC service entirely meaning the resource will no longer need a capability reference.

@chengfang @tadamski FYI in case this is causing you any problems with your layers work.

@darranl I filed https://issues.redhat.com/browse/WFLY-13733.

@jmesnil can you see about combining this with the core upgrade, I then need to follow up and delete the capability dependency entirely.

This was included in #13467 13467


Modify Chinese prompt: workflow definition error

Modify the status class in the dolphinscheduler-api module, Chinese prompt error.

Codecov Report

Merging #4352 (d2f9902) into dev (d446e33) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                dev    #4352      +/-   ##
============================================
- Coverage     43.22%   43.20%   -0.02%
+ Complexity     3184     3180       -4
============================================
  Files           471      471
  Lines         21732    21728       -4
  Branches       2626     2626
============================================
- Hits           9393     9387       -6
  Misses        11442    11442
- Partials        897      899       +2

Impacted Files
Coverage Δ
Complexity Δ

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <100.00%> (ø)
5.00 <0.00> (ø)

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

...che/dolphinscheduler/common/utils/HadoopUtils.java
34.29% <0.00%> (+1.12%)
21.00% <0.00%> (ø%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d446e33...d2f9902. Read the comment docs.

我这个pr是解决这个issue
https://github.com/apache/incubator-dolphinscheduler/issues/4178

thanks for your contribution, looking forward to your deep participation

@ApiException(CHECK_PROCESS_DEFINITION_ERROR)
public Result startCheckProcessDefinition(@ApiIgnore @RequestAttribute(value = Constants.SESSION_USER) User loginUser,
                                          @RequestParam(value = "processDefinitionId") int processDefinitionId) {
    logger.info("login user {}, check process definition {}", loginUser.getUserName(), processDefinitionId);
    Map<String, Object> result = execService.startCheckByProcessDefinedId(processDefinitionId);
    return returnDataList(result);
}

When API execute to failed, throw an unhandled exception, return status of CHECK_PROCESS_DEFINITION_ERROR.
So, set to "检查工作流定义失败" more appropriate


Crawl failing with syntax error

I seem to have run into a error which I can't pinpoint the source of. I'm thinking that its some dependency issue.
My setup:
Using create-react-app (react-scripts 0.9.5)
Which uses jsdom 9.12.0, react and react-dom 15.4.2
Having this very basic example:
import React from 'react';
import {render} from 'react-snapshot';

const TestComponent = () => (

Test

);

render(<TestComponent/>, document.querySelector('main'));

Which throws following error when running react-scripts build && react-snapshot:
(paths shortened to start at project root)

Starting crawling http://localhost:2999
Error: Uncaught [SyntaxError: Unexpected token <]
at reportException (...\node_modules\jsdom\lib\jsdom\living\helpers\runtime-script-errors.js:58:24)
at processJavaScript (...\node_modules\jsdom\lib\jsdom\living\nodes\HTMLScriptElement-impl.js:130:7)
at HTMLScriptElementImpl._eval (...\node_modules\jsdom\lib\jsdom\living\nodes\HTMLScriptElement-impl.js:65:7)
at e (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:31:22)
at Object.check (...\node_modules\jsdom\lib\jsdom\living\nodes\Document-impl.js:89:11)
at ...\node_modules\jsdom\lib\jsdom\living\nodes\Document-impl.js:108:12
at wrappedEnqueued (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:255:16)
at Request.request [as _callback] (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:203:9)
at Request.self.callback (...\node_modules\request\request.js:188:22)
at emitTwo (events.js:106:13) SyntaxError: Unexpected token <
at Object.exports.runInContext (vm.js:66:16)
at processJavaScript (...\node_modules\jsdom\lib\jsdom\living\nodes\HTMLScriptElement-impl.js:128:10)
at HTMLScriptElementImpl._eval (...\node_modules\jsdom\lib\jsdom\living\nodes\HTMLScriptElement-impl.js:65:7)
at e (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:31:22)
at Object.check (...\node_modules\jsdom\lib\jsdom\living\nodes\Document-impl.js:89:11)
at ...\node_modules\jsdom\lib\jsdom\living\nodes\Document-impl.js:108:12
at wrappedEnqueued (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:255:16)
at Request.request [as _callback] (...\node_modules\jsdom\lib\jsdom\browser\resource-loader.js:203:9)
at Request.self.callback (...\node_modules\request\request.js:188:22)
at emitTwo (events.js:106:13)
✏   Saving / as /index.html
�   Finished crawling.

I figured out that this problem has to do with the "homepage" field in the package.json file. If the field is not present, it renders as normal, but with homepage field present, it fails with above error.
As I need the homepage field for my builds (react page hosted under sub-folder of domain), it would be nice if this could be fixed

I have written a quick proof of concept that works for me (using the public-path): https://gist.github.com/kantenkugel/aee4d827d51e43ff9f1feb3709c0830b

I have also run into this limitation. If you (@kantenkugel) have a solution can you not create a PR?

that above PR from kevin looks much better than my ugly code and I also did a lot of other stuff for my personal use so i didn't want to make a PR out of that directly. Wanted to see what the opinion on it is first.

Closing issue as this is now implemented in 1.0.5-0. Would be nice to publish to npm tho as the npm registry still has 1.0.4 as its current version


NOISSUE - Add missing EID examples

This PR adds missing EID example for index, sovrn, openx and pubmatic.

Opened a PR in Prebid: https://github.com/prebid/Prebid.js/pull/10844


ML 0.3 : Real life application of Data Mining (D) #7315

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #issue_number_here

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[#] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[#] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[#] I follow Contributing Guidelines & Code of conduct of this project.
[#] I have performed a self-review of my own code or work.
[#] I have commented my code, particularly in hard-to-understand areas.
[#] My changes generates no new warnings.
[#] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

you need to edit the .md file above. seems to have some formatting issues.

sorry can you elaborate?
On Sat, Nov 6, 2021 at 7:43 PM Akshay Raina @.***>
wrote:

you need to edit the .md file above. seems to have some formatting issues.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/pull/7389#issuecomment-962457780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUEIB56UGDCAEXFYFIGKJ2DUKVA2LANCNFSM5HPSA5PA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

what to write inside module?
On Sat, Nov 6, 2021 at 10:03 PM isha @.***> wrote:

@.**** requested changes on this pull request.
Follow this :
https://github.com/girlscript/winter-of-contributing/blob/Machine_Learning/Machine_Learning/Demo/ML_%23_%23_Documentation Template_(D).md
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/pull/7389#pullrequestreview-799458369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUEIB56EEIAFC4G4OPHQASDUKVKENANCNFSM5HPSA5PA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

changes updated @Isha307  please have a look

Approved from my side @Ruchika-20 , let @Isha307 do the needful.

Okay....if psbl tell her to have a look before 11 am so that I can take up
new issues
On Sun, Nov 7, 2021, 10:09 AM Abhishek Sharma @.***>
wrote:

Approved from my side @Ruchika-20 https://github.com/Ruchika-20 , let
@Isha307 https://github.com/Isha307 do the needful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/pull/7389#issuecomment-962550928,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUEIB564VEC3JZ64XPP7PG3UKX7GTANCNFSM5HPSA5PA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Problem with integer normalization?

Hi all, I'm doing optimization on a problem with a lot of integer variables and I've observed much better performance when using spearmint instead of skopt. Since I really prefer skopt interface I would like to replicate spearmint's performance. After some testing I think I may have some problems with the normalization of integer values.
I've run some tests on the branin function varying the domains:

original branin function with domain [(-5.0, 10.0), (0.0, 15.0)]
branin scaled with domain [(-5.0, 10.0), (0.0, 15000.0)]
where by branin scaled I mean:

def branin_scaled(xs):
    xs = [xs[0], xs[1]/1000]
    return branin(xs)

branin scaled with domain [(-5.0, 10.0), (0, 15000)]

What I would expect is:
1-2 should be pretty similar: the actual domain is the same but skopt should see different scales, leading to different kernel behavior.
2-3 should also be pretty similar: it's true that skopt only sees integer numbers, but by dividing it I go back to a number with 3 decimal digits, which I think should be enough to optimize the function.
Instead, I've observed a much worse convergence on 3.
Specifically, I've run the tests for 100 epochs and repeated them for 50 runs, here's the graph of the average value obtained at each epoch:

(I've also included a test with a much bigger domain and the original branin function, obtaining a reasonably bad result. However, this is still better than scenario 3)
Is this behavior expected or is there some problem with integer normalization?

I've made another test where the variable is divided in a wrong way. I use as domain [(-5.0, 10.0), (0.0, 15000.0)] and the second variable is divided by 1000.0, but then explicitly casted to int.
In this way x2 cannot assume values like 5.123
The resulting behavior is totally similar to the one obtained in the case above (light blue and red):

I think that this could arise from the fact that I'm using python2 and therefore this could be solved by adding from future import division in transformers.py
I'm now running a test with this modification.

Yes, adding that fix solved the issue:

The import fixed the issue:

Can somebody make the proposed modification?

Hi,
Thanks for your investigation. This is very interesting!
In summary, what do you propose to change? Note that we do have a normalization mechanism in skopt, but I think it is turned off by default. See https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/space/space.py#L169
Gilles

If I remember the code correctly, the normalization is turned on when using gp_minimize().
The problem is that in transformers.py the value is normalized as (value - min) / (max-min) where by max and min I mean the variable's domain. When the domain is integer, the denominator is integer and python2 cast to integer the division result, leading to bad results.
This can be fixed by adding a from __future__ import division in the first line of transformers.py so that the division in python2 behaves like in python3 and returns a floating value.

Oh okay, I see, this is because you are using Python 2. That's an easy fix and we should do that!
 :)

Yes unfortunately I cannot decide which python to use on the machine I'm using.
Shall I clone the repo and make a pull request to make the fix?

Yes.

Make a clone
Create a branch
Make the fix in that branch
Submit a PR from that branch to our repo.

Fixed by #504


DOCTYPE is disallowed

Using version 1.1.0.
I have a valid SOAP message:
1- built in my code creating new SOAPMessageBuilder().build() {}
2- successfully validated and tested here http://wsdlbrowser.com/
3- calling client.send I have the exception
[Fatal Error] :1:10: DOCTYPE is disallowed when the feature "http://apache.org/xml/features/disallow-doctype-decl" set to true.
Reading changelog I was wondering it may have something to do, but didn't changed.
May this have something to do with http://stackoverflow.com/questions/10837706/solve-security-issue-parsing-xml-using-sax-parser

We were having this issue, but after some investigation we've detected it was due a bad soap response, I mean wslite wasn't receiving a proper SOAP Message.


Flammable curtains

Working with the curtains item and implementing how to set them on fire using the lighter

This feature is part of #3


Add TinyMCE Wysiwyg Field

Separate to #616, I want to add a WYSIWYG html field for the Admin UI.
It'll be useful while the content field is under development, and longer term helpful for transitioning from Keystone 4 or any other CMS that stores content in HTML.
The initial version should be a basic implementation of TinyMCE 5 and we should skin it a bit to fit in with the Admin UI style like we did in Keystone 4.

I hope you remember not to bundle the TinyMCE files like in Keystone v4 :) (which I got rid of recently)

How about a provider/adapter system with this field type? I am sure people would want to use something like Trumbowyg.
if there is adapter/provider system, dev can add their own editor without creating whole new FieldType

I left a comment on #929 re: supporting other editors.
tl;dr:
Really all this package is doing is integrating and configuring TinyMCE. Field types already work like what you're describing, and I think adding other editors as separate field packages is already the right abstraction for this.

I hope you remember not to bundle the TinyMCE files like in Keystone v4 :) (which I got rid of recently)

💯 I think you'll like what I've done!


[WIP] Include development dependencies in FileParsers::Php::Composer

Previously we were ignoring development dependencies for PHP. Including them needs a change to the parser and to the file updater.

@petehamilton - here's the dev-dependencies branch I mentioned.

@greysteil think this should work now, specs pass at least - thoughts?

Nice - 👍


Suggestion: the lack of doc

Nice wrok, but it is not quite friendly to user, due to the lack of wiki.
Is there a help doc or wiki ?

Hi, did you visit Github Pages ?

I have visited the page and the two videos, but how to configure the plugin settings is confusing.
There are neither docs nor wiki about this, eg. right click on the folder icon to add files seems a Easter egg, because of no hover tips 👈

"right click on the folder icon" described here. What plugin settings you want to configure?

http://ceh9.github.io/PackageTemplates/en is what I want. The language option button goes to  tutorials, which is really hard to get. Could we add a Doc/tutorial link to the project README or the home page?
I am frustrated I ignored the language option button, and spent a few minutes on gussing:joy: the usage.
Thanks a lot, nice work!

Added explanation
Also added wiki home page.


[BUG] Undefined behavior in thread pool's task queue

Describe the bug
Program crashes ("Access violation executing location...") as instruction pointer jumps to no man's land.
To Reproduce
Steps to reproduce the behavior:
OIIO::thread_pool thread_pool;

This single line will crash under VS 2015 (19.00.24234.1) with whole-program optimizations and/or other aggressive optimizations enabled.
No crash was observed with other VS versions (e.g. 2017) or without aggressive optimizations.
Expected behavior
No crash 😂🍺
Evidence
In src/libutil/thread.cpp on lines 55-64:
// deletes the retrieved element, do not use for non integral types
bool pop(T& v)
{
    std::unique_lock<Mutex> lock(this->mutex);
    if (this->q.empty())
        return false;
    v = this->q.front();
    this->q.pop();
    return true;
}

Even though the comment acknowledges the risk, this code is suspicious, and clearly it is undefined behavior to use the value v returned by pop().
That being said, I'm not sure this is the cause of the crash. All I can say for sure at this point is that it crashes with the following callstack:
-> thread_pool::Impl::set_thread()
   thread_pool::Impl::resize()
   thread_pool::Impl::Impl()

It appears to crash in the newly spawned thread but I don't have more details yet.

I wrote this bug report after many hours of tracing through optimized assembly; with the fresh mind of a new day, I realize that there is no UB in pop() as the front value from the queue is simply copied into v, and as long as T is an integral type then the cost of the copy is pretty much irrelevant.
There is still a crash in thread_pool::Impl::set_thread(). I can confirm that the crash occurs when spawning the new thread, i.e. the following line added at the beginning of thread_pool::Impl::Impl() is enough:
new std::thread([]{});

I wonder if there is something funny about MS's implementation of std::function that is causing a problem with the fact that it's being copied.
What happens when you change
v = this->q.front();

to this alternative:
v = std::move(this->q.front());

T is just a pointer so it should be fine.
I've been able to narrow the problem down further: https://developercommunity.visualstudio.com/content/problem/701555/stdthread-with-lambda-crashes-when-compiled-withou.html
TL;DR: we compile OIIO without Whole Program Optimization (/GL) but appleseed is compiled with (in Ship configuration), and that seems to cause
new std::thread([]{});

to crash.

Sounds like a MSVS compiler bug? Or are we specifically doing something that results in UB?

It's an MSVC bug I think. That, or /UB + not/UB isn't supported.

MS has confirmed that this may be an MSVC bug. Using a /GL (with Whole Program Optimization) build of OIIO for our /GL builds of appleseed solved the problem. Good enough for us for now.


Spook: Repair: Available entities are announced as unavailable.

What version of Spook are you using?
2.2.2 (latest)
What version of Home Assistant are you using?
2024.2.2
The problem
Hi @frenck
Since the last Update of spook I've a similar issue:
I got this repair announcement about an unknown entity:

but in developper tools this entity is known:

and in "Overview" it is also available:

I've received this message after restart from update from 2024.2.1 to 2024.2.2.
In former times, and also before last spook-update, I've received this message, too, but it was gone some seconds after restart of HA. On restart of HA, an automation will also restart the samba-addon, so for few seconds it might be possible, that spook recognize this entity as unavailable. But after the restart of the add-on it's available (as you can see in screen shots above).
I think it's a bug in the last spook-update.
Anything in the logs? Paste it here!
About this issue, there aren't any logs.

I'm having the same issue, spook doesn't seem to clean-up issues after a sensor becomes available again.
I don't think posting a screenshot will help, are there some hints in the log you could use?

are there some hints in the log you could use?

See above, there are no hints in the log's. ;-)

same here,
an entity got a new name, changed this in the automation but the message keeps showing the old sensor which isn't used anymore.
the messages for dashboard however got cleaned up.

same here, a sensor, which was used in several automatiions, was for couple of seconds unavailable due to reboot. Now it's avsilable and updating since four hours. Repairs are still there...

oddly enough this morning I had a hard reboot due to another issue that popped up and the entities are now working again.  not sure what was different this time.

same issue..repairs are not removed when fixed

I really like spook, it helped me resolve several issues.
I do however have the same issue (as reported in the initial message) with the sensor.samba_backup, can I provide additional information on this?

Which integration provides sensor.samba_backup?
../Frenck

Which integration provides sensor.samba_backup?
../Frenck

https://github.com/thomasmauerer/hassio-addons/tree/master/samba-backup

That is an add-on, which integration is it using for entities?

Aaah it isn't using an integration...
https://github.com/thomasmauerer/hassio-addons/blob/master/samba-backup/rootfs/scripts/sensor.sh
That is an upstream issue, as this is not the proper way to integrate with Home Assistant.
Closing on this end.


GET /wd/hub/screenshot request includes request body

Hello,
I work for a company called Sauce Labs that provides an Appium hosting services for our customers. We have an Appium proxy that does some parsing of requests, e.g. intercepting screenshot requests to extract images.
One thing we noticed recently with some customers was screenshot requests including a request body (a JSON encoded session ID). As far as I can tell reading the JSONWire spec this should not be the case: https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol#sessionsessionidscreenshot
The customer was using Robot framework 3.0.3.
Thank you.

Do I get it right that these screenshot requests are invalid? Are they causing a problem for you or is the problem that users don't get the information they expect? Either way, it's certain that Robot Framework itself isn't sending these requests because it in general doesn't directly interact with any tested system.
The culprit must be one of the test libraries used with it or possibly a tool such a library uses internally. The most used library for web testing with Robot Framework is SeleniumLibrary, but if this problem is related to Appium then the problem is likely elsewhere. The problem is that there are various libraries that use Appium and I don't personally have much experience with them. Do you got any more information about this issue that we could use to track down the library/tool that's causing the problem?

Thanks, I've looked into this further and discovered the customer is using this library: https://pythonhosted.org/robotframework-sofrecomappiumlibrary/
I'll file the bug there instead.

OK! There are also other Appium libraries out there, though.


Does not work with helm 3

Does not work with helm 3

[root@k8-coh-master coherence-operator]# helm version
version.BuildInfo{Version:"v3.2.3", GitCommit:"8f832046e258e2cb800894579b1b3b50c2d83492", GitTreeState:"clean", GoVersion:"go1.13.12"}
[root@k8-coh-master coherence-operator]# helm repo add coherence https://oracle.github.io/coherence-operator/charts
"coherence" has been added to your repositories
[root@k8-coh-master coherence-operator]# helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "coherence" chart repository
Update Complete. ⎈ Happy Helming!⎈
[root@k8-coh-master coherence-operator]# helm install coherence-operator coherence/coherence-operator \

--set prometheusoperator.enabled=true
--set prometheusoperator.prometheusOperator.createCustomResource=true
--set installEFK=true
--namespace coherence-example
--set imagePullSecrets[0].name=coherence-example-secret
load.go:112: Warning: Dependencies are handled in Chart.yaml since apiVersion "v2". We recommend migrating dependencies to Chart.yaml.
load.go:112: Warning: Dependencies are handled in Chart.yaml since apiVersion "v2". We recommend migrating dependencies to Chart.yaml.
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

Closing this because the latest Operator 3.0.0 version does work with Helm v3 and we have no intention of going back and changing v2.


Recalculate discounts even when tax app returns empty data.

When taxes are calculated with tax app, we update prices with data received from tax app. In case of tax data is empty (ie. lack of address) we currently skip all the calculation. This PR ensure we calculate at least net (or gross) values.
Issue: https://linear.app/saleor/issue/SHOPX-1594

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations

Docs

[ ] Link to documentation:

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases
[ ] All new fields/inputs/mutations have proper labels added (ADDED_IN_X, PREVIEW_FEATURE, etc.)
[ ] All migrations have proper dependencies
[ ] All indexes are added concurrently in migrations
[ ] All RunSql and RunPython migrations have revert option defined

Changelog skipped, because this is a fix for changes introduced in the same version (#16696)


#1100 - Fix startup script for windows

Signed-off-by: Aurélien Pupier<EMAIL_ADDRESS>

[merge]

Thanks @apupier!

[merge]

@hrishin any idea why CI is failing? It should be unrelated to this PR.

@hrishin any ideas?

retest this please

[merge]


Separate the dev and production outputs

Feature Request
Whether if I execute wxt or wxt --build, the output will be chrome-mv3
This poses an issue:
If I wish to simultaneously test on Chrome desktop and a Chromium browser on Android (such as Kiwi), it makes the development cycle quite cumbersome, especially since web-ext does not support yet setting up a dev server for chrome-android
Is your feature request related to a bug?
N/A
What are the alternatives?
Every time I make a modification I need to run wxt to test on Chrome desktop, and every time I need to run it on Android I need to run wxt --build, zip, and push [ext-name]-[version].zip to the device
If I could have separate chrome-dev-mv3 and chrome-prod-mv3, I could zip the latter directory and push it to the device flawlessly
Additional context
A potential solution is to let the developer specify a custom tag, e.g. wxt --build --tag prod → chrome-prod-mv3

@avi12 WXT already provide the way with reusable-module, but there is another problem and it is a blocker for use cases. See https://github.com/wxt-dev/wxt/issues/939 .

Regardless of this separation, I see it as a necessity to let the developer build the extension with a custom tag, e.g. for A/B testing

@aklinker1 Sorry for pinging, do you have a projection of when this feature will be available? I believe the implementation could involve adding to the wxt.config.ts a field outputDirTemplate

I work on WXT in my free time, so no, I will never have estimates for when I can work on things.

Closing this in favor of https://github.com/wxt-dev/wxt/issues/1069

Released outDirTemplate in v0.19.12

In v0.20, the default for outDirTemplate is changing to support this use-case by default. See https://github.com/wxt-dev/wxt/pull/1086 for details.


Dropdown On Hover Makes Text Input Inside Disappear

Hi there!
I'm having a bit of an issue with a text input inside of an a tag. When hovering over the element, the inputted text in the field disappears, however it's still there as the corresponding ajax request will fire on the "Go!" button click. I've tried adjusting the z-index of the input field, but that didn't work. Any help would be greatly appreciated, thank you in advance!!
Attached are example images showing what I'm speaking of:

Fixed issue, was being silly.


feat: enable dependabot dep updates

Issue #, if available:
Description of changes:
Add dependabot weekly updates to dependencies.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Should rebase and merge this after #32


Ability to Skip Homepage and Directly Access Feature Page

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
I'm seeking guidance on how to implement this feature. Specifically, I would like to know:
Which files or configurations control the homepage functionality?
What modifications should be made to enable users to skip the homepage and directly access the feature page?
Any potential implications or considerations to be aware of while implementing this change?
Expected Outcome:
By providing the option to skip the homepage, users can quickly access the core features of the project, thereby enhancing usability and user satisfaction.
Has this been requested on Canny?
No response
Motivation
Currently, upon deploying the open-source project, users are directed to a homepage containing introductory information before accessing the main functionality. I would like to propose an enhancement that allows users to skip the homepage and directly access the feature page upon initial visit.
Note: This issue is submitted with the intention of seeking guidance and implementation details rather than proposing a change directly to the project.
API design
No response
Have you tried building it?
No response
Self-service

[ ] I'd be willing to contribute this feature to Docusaurus myself.

It's not clear what you mean by "access the features". We don't have a "feature page", we have docs, blog and pages.
If you mean how to directly access the docs page (which may describe your project features 🤷♂ ), it's already documented here as "docs-only mode":
https://docusaurus.io/docs/docs-introduction#docs-only-mode
Closing because this is not a feature design / RFC. If you have questions or want support, please ask the community on discord.


[Macros] In-process plugin server

Separate swift-syntax libs for the compiler and for the library plugins. Compiler communicates with library plugins using serialized messages just like executable plugins.

lib/swift/host/compiler/lib_Compiler*.dylib(source lib/CompilerSwiftSyntax): swift-syntax libraries for compiler. Library evolution is disabled.

Compiler (ASTGen and swiftIDEUtilsBridging) only depends on lib/swift/host/compiler libraries.

lib/swift/host/libSwiftInProcPluginServer.dylib (source tools/swift-plugin-server/Sources/SwiftInProcPluginServer): In-process plugin server shared library. This has one swift_inproc_plugins_handle_message entry point that receives a message and return the response.

In the compiler:

Add -in-process-plugin-server-path front-end option, which specifies the SwiftInProcPluginServer shared library path.
Remove LoadedLibraryPlugin, because all library plugins are managed by SwiftInProcPluginServer
Introduce abstract CompilerPlugin class that has 2 subclasses:

LoadedExecutablePlugin existing class that represents an executable plugin
InProcessPlugins wraps dlopened SwiftInProcPluginServer and communicate with it via the swift_inproc_plugins_handle_message

Unified the code path in TypeCheckMacros.cpp and ASTGen, the difference between executable plugins and library plugins are now abstracted by CompilerPlugin

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

@swift-ci Please test Windows

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test Windows

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test Windows

:wave: does this PR remove support for the loadPluginLibrary approach entirely? Worth noting that we're relying on this mechanism in https://github.com/apple/swift/pull/73031 in order to enable support for WebAssembly-based plugins. We could move these in-process but I think it would be preferable to keep third-party Wasm plugins out-of-process for defence-in-depth/isolation reasons (especially if we eventually want to execute them with JIT), so IMO it's worth keeping the library plugin mechanism for that. Also, IIUC one of the ways we could improve macro performance is to reuse a single plugin library/executable across swiftc invocations. Would this PR preclude that change for library-based plugins?

does this PR remove support for the loadPluginLibrary approach entirely?

I'm not 100% sure what loadPluginLibrary approach you mean, but either it's about  -load-plugin-library compiler option or loadPluginLibrary plugin message, this PR doesn't remove them.
Since we need to keep supporting "in-process" plugins (i.e. -load-plugin-library and -plugin-path compiler options) for various reasons, we've been suffered by some limitations from that. The main intent of this PR is that separating swift-syntax libraries for the compiler and swift-syntax libraries for those "in-process" plugins. By that

We can unify the code path between in-process and out-of-process plugins
We can use different swift-syntax between the compiler and the in-process plugins. That let us compiling swift-syntax for the compiler without library-evolution, for the compiler performance

This PR doesn't have any intent of removing or deprecating out-of-process plugin mechanism.

IIUC one of the ways we could improve macro performance is to reuse a single plugin library/executable across swiftc invocations. Would this PR preclude that change for library-based plugins?

Yes, reusing plugins across multiple swift-frontend invocations is probably what we need to tackle on next. This PR does not preclude that approach.
I'm not sure I entirely understand your concerns. Let me know if you still have any questions!

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

Ah I was under the impression that this removed support for external plugin servers, but looks like I was confused. Thanks for the clarification!

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test Linux

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test Linux

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
@swift-ci Please Test Source Compatibility

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

@swift-ci please build toolchain Windows platform

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please build toolchain Windows

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please Build Toolchain macOS

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please smoke test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-syntax/pull/2659
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please Build Toolchain macOS

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please test

https://github.com/apple/llvm-project/pull/8855
https://github.com/apple/swift-driver/pull/1616
https://github.com/apple/swift-installer-scripts/pull/304
@swift-ci Please Build Toolchain Windows