clean up ci and gpu scaling config files

Purpose

Currently we have config files under gpu_configs that are used for both ci and GPU scaling pipeline. I find it a bit confusing when trying to find the files and add new files. This PR moves GPU scaling pipeline config files to a new folder gpu_scaling_configs.
This is probably a breaking change as I think the coupler assumes some path of atmos configs. cc @juliasloan25
To-do

Content

[ ] I have read and checked the items on the review checklist.

Hmm, some configs are used in both ci and GPU scaling pipeline. That means we should probably clean it up - if it's already running in ci then we don't need to run it in weekly scaling again.

Yes, I guess it’s ok to run it twice for now. I mostly want to reorganize the files in this PR. We can clean up the jobs later.

@sriharshakandala are you ok with this folder change, or do you want to keep all of them in the same folder?

@sriharshakandala are you ok with this folder change, or do you want to keep all of them in the same folder?

One way is to keep the gpu_pipeline configs in gpu_configs (or rename that to gpu_pipeline_configs) and the CI GPU configs in model_configs! For the CI runs, we can use a smaller integration time, just to check if everything is running correctly. We may want to use a reasonably large integration time for the gpu_pipeline for accurate performance measurements.

@sriharshakandala are you ok with this folder change, or do you want to keep all of them in the same folder?

One way is to keep the gpu_pipeline configs in gpu_configs (or rename that to gpu_pipeline_configs) and the CI GPU configs in model_configs! For the CI runs, we can use a smaller integration time, just to check if everything is running correctly. We may want to use a reasonably large integration time for the gpu_pipeline for accurate performance measurements.

Ok, I can do that!

@sriharshakandala could you look at it again? @juliasloan25 I don't think it's a breaking change anymore if I change it this way (unless you use anything in model_configs in the coupler), do you still want it to be in the NEWS?

@juliasloan25 I don't think it's a breaking change anymore if I change it this way (unless you use anything in model_configs in the coupler), do you still want it to be in the NEWS?

We don't use Atmos's model_configs, so it's not a breaking change but it would still be nice to include in the NEWS :)


mvc: strict types in POST cause save error?

Working on the IPS rules and toggling a ruleset seems to cause empty values to be posted from a hidden dialog, which breaks boolean type:

Also, proxy seems to have issues I can't pin down:

Any ideas?

Hey Franco, @rails has a solution for that: You need to create a hidden input with the value when unchecked. After that, a normal checkbox exists, which has the same name. If it is checked, it will overwrite the previous value in the hidden field. A checkbox is usually not sent when it is not checked.
I hope that this info can help you.

Hi Fabian, well the type checking behaviour was added yesterday so I'm just recording this info here. Not sure which way to go, I think Ad will know best. :)

@fichtner thanks for testing, I will look at it asap.

@fichtner it seems like I can;t reproduce it easily, can you capture the response data from the web form?

Response is:
{"errorMessage":"[OPNsense.IDS.IDS.general.enabled] value should be a boolean (0,1)\n[OPNsense.IDS.IDS.general.ips] value should be a boolean (0,1)\n[OPNsense.IDS.IDS.general.promisc] value should be a boolean (0,1)\n[OPNsense.IDS.IDS.general.syslog] value should be a boolean (0,1)\n"}
Does this help?

maybe, does your config contain anything for OPNsense.IDS.IDS.general ?

No, it should have been OPNsense.IDS.general et al, these values are available. I tested against stable/17.1, it's not problematic there.

ok, that's strange. Even without a general section, I can't seem to reproduce this. my changes shouldn't impact this one, because it has no payload.
Can you dump the general section of your IDS config here? normally it shouldn't revalidate, because there are no changes there.... but maybe somethings off.

Triggering rule sets doesn't generate this error for you? (enable selected)
Section looks normal:
1945       <general>
1946         <enabled/>
1947         <ips/>
1948         <promisc/>
1949         <interfaces>wan</interfaces>
1950         <UpdateCron>ee9888a6-5a5f-4d71-b4d5-c9e206cc33cf</UpdateCron>
1951         <AlertLogrotate>W0D23</AlertLogrotate>
1952         <AlertSaveLogs>4</AlertSaveLogs>
1953         <MPMAlgo>hs</MPMAlgo>
1954         <syslog/>
1955       </general>
1956     </IDS>
1957   </OPNsense>

Saving the general dialog is ok too...

@fichtner nope, it doesn't look normal...

0
0
0
wan

W0D23
4
ac
0

Funky, did this jut now...
Setting enabled: 1
Unsetting enabled:

Ok, found it.... it fails at saving the general section ;)

@fichtner can you try https://github.com/opnsense/core/commit/f54260277af5fdb9a31c8932db8b0107e7a0dd44 ?
(save general form again)

Looks better, thanks!
Will post web proxy debug info later, no more time at the moment.

(quick save in web proxy didn't solve this as with IPS)

As soon as you have some time, can you post the request/response for this one too? Maybe a parameter got damaged before and isn't rewritten.

{"result":"failed","validations":{"proxy.forward.acl.remoteACLs.blacklists.blacklist.909195a7-01a4-41d8-bd74-82e698b5daf8.sslNoVerify":"value should be a boolean (0,1)"}}

This is a bit of a pickle. Easily fixed by resaving the blacklist entry, but impossible to find for a normal user.

@fichtner sorry about that, this was already the case, my latest patch only saved the wrong value resulting in this ;(
Maybe we should add a "debug" option in the dialog to show the actual response message.... if the setting isn't on screen, it's indeed difficult to spot.

Like the API error, yes, that would already help.
I'd rather keep this new POST stuff on -devel for a while, maybe we can thing of a smoother migration strategy before it hits 17.1.x.
In any case, I do like this new strictness, just looking out for problematic user experience.

yes, your right, we should keep this for a couple of weeks on -devel. I will add a debug option in the dialog asap.

ok, this should help https://github.com/opnsense/core/commit/39628cd7f3cb25c3b7dad5e3108f513cee783877

LGTM, thank you very much :)


re-add Fullstack HQ to sites made with react-static

Description

Changes/Tasks

[ ] Changed code

Motivation and Context

Screenshots (if appropriate):

Types of changes

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[ ] My changes have tests around them

-- Please reply above this line --
Hi Nozzle/react-Static,
Thanks for the email!
We’re working on your request, and we’ll get back to you as soon
as possible (Monday-Friday 9am-9pm Philippine time).
Thanks again,
Team Fullstack HQ
P.S. We’ve got our best developers on it :)

Haha, @psdwizard your autoresponder is responding to github emails :) I fully expect another email after this!


Unable to test auth failure when test_mode is true

I've been playing around with the latest version of Omniauth and its various strategies, and I have come across a rather annoying issue. When I have test_mode set to true in my spec_helper and I am trying to test authentication failures, the authentication callback is always coming back as successful.
For example I have an acceptance test to check that if a user tries to log in using Identity but does not fill in the password field, they should see the authentication error. when I try this in my browser I get the expected outcome, however when I run my spec for this it is always logging in the user even without a password. I have verified this by changing the email address the test users to try and log in.
Yet if  I turn test_mode off, all the tests I have pass as expected.
Am I using Omniauths test_mode in the wrong manner or is there a way of acceptance testing with it set to true that means I can actually test what happens when someone tried logging in with invalid credentials.

I currently have the same problem in test mode.
OmniAuth.config.mock_auth[:twitter] = :invalid_credentials
is ignored and the failure endpoint is never used.
Switching test_mode to false does not help though.
Has anybody found a solution to this?

I will take a seat here.

I have just encountered this problem and I was able to trace it to the following lines:
https://github.com/omniauth/omniauth/blob/fce9e23dd4ed33c275485a43b9cc18c1412db9a9/lib/omniauth/strategy.rb#L299-L307
as you can see if you mock the "invalid credentials" scenario with
OmniAuth.config.mock_auth[:twitter] = :invalid_credentials

the code will call fail! with :invalid_credentials as a param. fail! is defined as:
https://github.com/omniauth/omniauth/blob/fce9e23dd4ed33c275485a43b9cc18c1412db9a9/lib/omniauth/strategy.rb#L480-L492
which accepts an optional exception which is never passed.
Also, the setup code above never calls OmniAuth.config.before_callback_phase so there's no way you can prepare env['omniauth.error'] or the other variables before hand (which would be overridden anyway).
BUT
if you look closely, the last thing fail! does is call OmniAuth.config.on_failure.call(env) so I thought to myself: "maybe there's an opportunity there".
I ended up with something like:
OmniAuth.config.mock_auth[:twitter] = :invalid_credentials

global_failure_handler = OmniAuth.config.on_failure

local_failure_handler = proc do |env|
  error = OmniAuth::Strategies::OAuth2::CallbackError.new(
    "Callback error", "Error reason", "https://example.com/error"
  )
  env["omniauth.error"] = error
  env
end
# here we compose the two handlers into a single function,
# the result will be global_failure_handler(local_failure_handler(env))
failure_handler = global_failure_handler << local_failure_handler

OmniAuth.config.on_failure = failure_handler

visit path
# check stuff

# set `OmniAuth.config.on_failure = global_failure_handler` when you're done

hope it helps someone!


Add new production src5 with lstchain v0.10

 20230829_src5_dec3476_v0.10_tuned
New Prod config
Self check-list:

[x] I have checked the lstchain config, in particular for:

[x] az_tel instead of sin_az_tel if data to be analyzed have been produced with lstchain <= v0.9.7
[x] "increase_nsb" and "increase_psf" are provided in "image_modifier" (if used)

[x] I have checked the environment in the lstmcpipe config and it is the one used to analyse DL>1 data
[x] I have provided the command (in README), or script (in additionnal .py file) used to produce the lstmcpipe config

Prod_ID
Short description of the config
Why this config is needed

Hi, I corrected the config file but it seems to be failing the PR as well.

Hi, I corrected the config file but it seems to be failing the PR as well.

this was a fluke, thanks for fixing the config, tests are now passing, I will launch the prod


Update README.md

replace --author by --authors to make doc consistent.

@lvthillo Thanks for your contribution! Sorry for the delay. I didn't read notifications actively.


Remove objects that are created by policies when the parent policies are deleted

Enhancement connected to https://github.com/stolostron/backlog/issues/22967

@willkutler could you please close this issue as complete?


Meta description typo

The meta description doesn't match the content of the page. When I paste the link into Slack for example, I see this typo: "Data sovereignty per microservice is one of the kay point of microservices."

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

ID: 81283b66-f8c6-4d93-73c8-551e1681f51e
Version Independent ID: c637cf8d-163a-4717-371f-2ff40d61f314
Content: Data sovereignty per microservice
Content Source: docs/architecture/microservices/architect-microservice-container-applications/data-sovereignty-per-microservice.md
Product: dotnet
Technology: dotnet-ebooks
GitHub Login: @nishanil
Microsoft Alias: nanil

Thank you for your feedback @DavidHogue. I've opened PR #13885 to fix this.


Debug visuals of Node3d descendants created in tool script don't work

Godot version
4.0.dev (60d031777b2a922cba03210181c9ba7ad3a6f3ab)
System information
Windows 11
Issue description
Nodes that have debug visuals that should be visible in 3d scene display them only if added via editor. If node is added to tree via code of tool script it won't show any debug visuals.

Steps to reproduce

Create scene with Area3D with collisionshape3d and sphereshape3D,
Create tool script extending Area3D with collisionshape3d and sphereshape3D added through core on _ready.
Place tool script node in the same scene beside original hierarchy.
Witness no debug visuals in 3d scene for tool script node

Minimal reproduction project
reproduce_no_debug_visuals_bug.zip

What happens if you set the owner of the newly added nodes to root?

I have forgot to add ownership to code collisionshape3d in demo project.

What happens if you set the owner of the newly added nodes to root?

It goes like this:

If CollisionShape3D owner is tool script no debug visuals
If CollisionShape3D owner is scene root debug visuals appear. But there are problems.

Problems:

Setting owner to external object is strange. My custom script is already in tree and serialized with scene.
CollisionShape3D appears as node in scene tree even if it is marked as Internal.
It exposes internal api and can be deleted by user from editor. This can break behavior. I wanted my type as script to expose only needed configuration.
Thus it is saved to serialized scene and on every project reload will duplicate. It must be handled manually by user.

Yeah, I wasn't saying it was a solution, I was just wondering whether it has an effect.

Sorry, I didn't mean to sound harsh:( I have merely described consequences.
After shuffling some code around after testing your proposal somehow everything started working even after setting owner to self. I think the issue should be closed.


Update chrono dependency

You're using Duration::try_minutes in for example t31x_result.rs but try_minutes wasn't introduced before version 0.4.34 of chrono

Idk maybe i messed up with conflict resolution

I've updated this as part of a bundle that updated multiple packages.
Thanks for raising it!


Support for other FaaS (Google, IBM, etc.)

Hey, what about other vendors that offering FaaS (Google, IBM, etc.). I've already read the topic: #99 but it does not follow clearly whether the support of other vendors will be abandoned.

Hi, yes AWS is the only provider supported by Bref and it is the only one planned to be supported at the moment.
The reasons for this come from one of the principle behind bref (see https://bref.sh/docs/):

simplify problems by removing choices instead of trying to address every need

Providing compatibility with multiple providers would be a lot of work for maintainers, and would be more work as well for users. Indeed that would raise the question of which one to use? On top of that the experience is different from provider to provider, for example there can be important performance differences. It could be deceiving for users (that could expect the same experience between providers).
Now why AWS and not another one?

The choice of AWS as serverless provider is deliberate: at the moment AWS is the leading hosting provider, it is ahead in the serverless space in terms of features, performances and reliability.

Now this decision is made based on the current situation. If the situation changes (and it will very probably change over time) we should definitely revisit this.
But TL/DR Bref's choices could be summed up like this: it is more important to provide one good solution than many poor solutions.

Thanks for the comprehensive explanation :+1:

I'd love to be able to use Bref with Google Cloud Functions. But, to be fair, it's currently miles behind AWS Lambda... I really hope that changes soon rather than later.

How is google cloud functions miles behind AWS Lambda?

It has better performance, has the 3G of RAM option, can be set to run for up to 15 minutes, you have API gateway to "easily" setup a domain, the ecosystem is richer in terms of other AWS services that integrate with Lambda and there's also much more stuff built/written by the community. These are the ones that come to my mind right now, and will depend on the use case.
That said, I'm using Cloud Functions because of free credits and I'm happy with it. But I'm 99% sure I'd choose Lambda.
Nice post, thanks for sharing it. Cloud Run is indeed a really good option in some cases.

If Fargate could scale to zero, it might be equivalent.

Fargate can scale to 0 for asynchronous workloads.


Enabling Hyper-V windows feature crashes WSL

Environment
Windows build number: 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Your Distribution version: Ubuntu 18.04 LTS
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Steps to reproduce
Enable WSL in windows features
Enable Hyper-V in windows features
Expected behavior
WSL2 related services to work normally.
Actual behavior
WSL failes with
Error: 0x80041002

[process exited with code<PHONE_NUMBER>]

I struggled with #5760 for a month. Yesterday a new windows update came. Then I dissables WSL and Hyper-V from windows features. Then enabled WSL and installed Ubuntu on WSL2 (It works fine). Then I went on with turning Hyper-V (Needed for docker) and did a restart. Now WSL does not works. Throws above error.
How can I fix this?

/dupe #5760

@therealkenc  I opened #5760 and this issue is not a duplicate of it.

That you were the OP on #5760 was noted. For what it is worth, #5760 survived a dupe to #5329 at the time it was posted. The submission does not provide any information that is actionable in addition to Error: 0x80041002. Your post from two days ago asked "any update on this". If you think there is even a snowballs chance that the underlying cause of the new 0x80041002 is different than the old 0x80041002, please do collect new logs and post the backlink.

@therealkenc I have no idea about the internals but last time I could not get WSL2 working anyhow. This whatever the bug, affected me almost for a month. I did upload logs for 5760 in feedback hub. But what happened today is a new scenario following the update I recieved yesterday. WSL2 works but when enabled Hyper-V it crashed with the noted error.
However as I had enough of this, I reinstalled windows. The ISO I got had OS Build 19041.450 and surprisingly again WSL2 started to crash even though it's a fresh install of windows. Then I did an update to the latest (OS Build 19041.508). Now, WSL2 and Hyper-V working perfectly. So I'm closing this issue and 5760.


improve prediction accuracy

Hello, thansk for the nice job done!
I just followed the training and finetuning(I used the same preproessed data used in training) commands. But the prediction accuracy is low, for example:
src_test.txt:
The reaction mixture is allowed to warm to room temperature and stirred overnight.
The combined organic layers were washed with brine, dried over sodium sulfate, filtered, and concentrated to yield 2.98 g of N-{2-[4-amino-7-[(6-aminohexyl)oxy]-2-(ethoxymethyl)-1H-imidazo[4,5-c]quinolin-1-yl]-1,1-dimethylethyl}-N-isopropylurea as a dark orange solid.
3-Amino-2,4-dichloro-benzamide (2.00 g, 9.8 mmol) in THF (45 mL) was added dropwise to LiAlH4 (1 M in THF, 24.4 mL) in THF (45 mL).
A further drop of methanesulfonyl chloride was added and the mixture continued to stir at RT for 30 min.
pred.txt:
STIR for overnight at room temperature; QUENCH with saturated aqueous NH4Cl solution.
PURIFY; COLLECTLAYER organic; PH with K2CO3 (0.5 g) to pH basic; EXTRACT with DCM (50 ml) 2 x; DRYSOLUTION over unknown; CONCENTRATE; YIELD yellow solid (101 mg, 31%).
ADD 3-Bromo-2-fluoroaniline (10 g, 52.63 mmol); ADD DCM (100 mL) under nitrogen.
STIR for hr at room temperature; ADD methanolic HCl.
Could you give some tips to improve prediction? Is it maily beacuse training data is insufficient, or the traning paramenters are not well set?
Thanks!

Hi!
Did you train on the data files in this repository? If so, the reason is insufficient data. The files in this repository are provided as examples; the models presented in the paper were trained on more than 2M sentences.

Closing after one year inactivity. Feel free to reopen if needed.


Make tool scripts print on the editor Output panel

This makes the GDScript module include an editor header, and I'm not sure if that's okay, but I couldn't think of another way to do this.
Fix #8748.

Changed it to use a print handler for the editor. This also creates a print_error function, akin to print_line so the printerr function in GDScript (and VisualScript) can also be handled in the editor.

Will need a rebase after #12969.

Rebased.


Update dependencies and security margin

This updates the dependencies to secure versions since crypto_box 0.6 has a vulnerability.
This also updates from using Chacha12 to Chacha20 which has higher security margins and performance difference is negligible.

@laysakura ping

@laysakura ping


Keeps asking for username and password

I got the same problem

Just try to stop the script and it will work for you

Just try to stop the script and it will work for you.

How tell brother

Sigue ocurriendo lo mismo

same, when installing keeps asking for github name and pass and cannot finish installation

please help boss_  fatal: Authentication failed for 'https://github.com/Cyb0r9/SocialBox.git/
when installing keeps asking for github name and pass and cannot finish installation

Just press enter without typing  username or password then it should work

BEWARE IT'S FAKE!


处理增加完kubeconfig后集群空白问题

What this PR does / why we need it?
Summary of your change
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

处理增加完kubeconfig后集群空白问题


Unify swift-bootstrap with swift-build and swift-test

Motivation:
Existing code in swift-bootstrap mostly follows swift-build/swift-test in an ad-hoc manner, but somewhat deviates from that swift-test such that environmental builds are not possible with the current setup. Let's unify this code to avoid the divergence and make maintenance easier.
This is a prerequisite for enabling incremental builds when running ./Utillities/bootstrap build --release and ./Utilities/bootstrap test --release in sequence.
Modifications:

Moved required APIs like AsyncSwiftCommand extensions from Commands to CoreCommands.
Added a dependency on CoreCommands to swift-bootstrap.
Converted swift-bootstrap from top-level code to @main.
Renamed SwiftBoostrapBuildTool to SwiftBootstrapCommand for consistency with other commands.
Added AsyncSwiftCommand conformance to SwiftBootstrapCommand.
Added a trivial but sufficient func run(_: SwiftCommandState) implementation to SwiftBootstrapCommand.
Removed old code that became unused.

Result:
Made swift-bootstrap behavior more consistent and predictable, ~450 LoC removed.

@swift-ci test

@swift-ci test

@swift-ci test linux

@swift-ci test

@swift-ci test

Mind you, I find the title funny. swift-build and swift-test aren't necessary consistent with each other. But that's a separate issue :).

Certainly more consistent with each other WRT incremental builds than either of them is with swift-bootstrap.

Note that the point of swift-bootstrap was to only require a minimal set of modules and dependencies for bootstrapping. It will transitively depend on Workspace (i.e. "everything") with this change, so I'd recommend just going to to use swift-build for bootstrapping at that point.

Note that the point of swift-bootstrap was to only require a minimal set of modules and dependencies for bootstrapping. It will transitively depend on Workspace (i.e. "everything") with this change, so I'd recommend to just use swift-build for bootstrapping at that point.

Yeah, I guess I've haven't quite figured out what the bootstrap was supposed to be for. If it's doing a build, wouldn't you need the Workspace, and then yeah, why not just use swift-build?

If it's doing a build, wouldn't you need the Workspace

You don't, a build system can be created without a Workspace.

and then yeah, why not just use swift-build?

swift build pulls in too much stuff, like package registries code and swift-crypto, which causes the current build issues on CI. Those are apparently due to wrong BoringSSL or swift-crypto libraries, maybe coming from the host instead of freshly built ones, IDK.
I'm going to refactor the PR to allow using SwiftCommandState (or a subset of it) without needing a Workspace, but still preserve the rest of swift-build logic and SwiftCommandState logic of build parameters preparation, which is apparently what breaks incremental builds in the first place.


Update Test Guidelines with a localization section

Fixes #81

This change is

@PlagueHO when you have time, if you could review this one too. 😃

When you have time, can you proof read this for me? 🙂


Websocket support

Figured I'd join the club and post my draft PR for websocket support for comparison. It's pretty similar in implementation to https://github.com/konveyor/forklift-ui/pull/768/ - I've exhausted a few more options with the http-proxy-middleware and ws packages, but while I can send events between the UI and node app, I can't seem to receive events from the inventory on the node app (although I was able to get same type confirmation logs for "Upgrading to websocket" as observed in https://github.com/konveyor/forklift-ui/pull/774.
I think next step is to try swapping usage of either of those two npm packages (just for the ws endpoint) and see if we can get message events going from the inventory to the node app - once we are there we're home free as communication from the react app and the websocket server is already working great.
The new WebSocket constructor in the browser seems to require ws:// schema to be specified, which prevents us from being able to use the dev server proxy config, so in the mean time I'm just hitting the express server directly for now. I did get a tip from a fellow UXD member to check into the webpack webSocketServer config, so I'm thinking that will help move things along on that front. I'll give it a spin as soon as I get back to this work.

Closing for now, we can revive this work later.


Define the context for metadata functions

Hello @andrerpena, what is this task about?? :stuck_out_tongue:

So, I changed the title so it's more comprehensible.
Here's the thing: Every metadata in RAF can be define both as a literal and a function. This function receives 2 parameters. The first one is the model. The second one is the context. The context is our opportunity to expose everything we think the developer will need.
Possible examples of helpers in the context (to be discussed):

Number and date localizers.. So it's possible to convert the string representation of a float into an actual number (Redux Forms stores the string, not the number, so you cannot make math operations).
Possible a way for the user to request services.. Like a "fetch" service so he can make URL calls. Or access the Redux state, or something like this.

This needs to be discussed further.

In the repo of v1, metadata is provided via Context-API, and each component access things via a Component with render-prop.


Cannot read property 'meta' of undefined

As soon as I include this cool little plugin I'm getting the following error for rendering my pie chart:
chartjs-plugin.js:84 Uncaught TypeError: Cannot read property 'meta' of undefined
    at Label.renderToDataset (chartjs-plugin.js:84)
    at Array.forEach (<anonymous>)
    at Label.render (chartjs-plugin.js:77)
    at chartjs-plugin.js:486
    at Array.forEach (<anonymous>)
    at Object.afterDatasetsDraw (chartjs-plugin.js:485)
    at Object.notify (Chart.min.js:13)
    at t.Controller.draw (Chart.min.js:11)
    at a.o.render (Chart.min.js:11)
    at Object.startDigest (Chart.min.js:11)

The pie chart works fine without the plugin. I did not make any changes to my options yet for the pie chart only included the minified js file.
Any suggestions?

I used a different plugin. But also found out I was using an old chartjs version. Might be worth checking if you're using the latest version.

You are right. Minified chart js is causing this issue. Uncompressed version made it work fine. Thanks for your prompt response 👍

I am also facing same problem for clicking on radar graph labels, Please any help would be appreciate...


Port the Mod to Forge

I have used your FastQuit mod on Fabric for a while, and it's absolutely fantastic!
The only thing that I wish to have is a Forge version of this mod. In my opinion, this mod will be very helpful for the Forge users out there. Especially those who play with demanding modpacks (like me).
For demonstration of how helpful it might be, I play Minecraft Forge with a modpack named Vault Hunters, and it takes the game
half a minute or more to get back to the title screen, after quitting a world.
If there's more demand for such port, will you consider it?

First of all, thank you very much! :)
Personally i've never used nor worked with Forge but i assume there's a first for everything so I wouldn't rule out the possibility that i want to try it in the future.
If demand for a port increases i could see myself making one, it isnt really a priority for me tho, the main version will always be on fabric.
If another modder reads this and doesn't want to wait for me to get around to it you're also more than welcome to make a port yourself and maybe make a pullrequest or smth idk
Yea so tl;dr i might do it in the future, not a priority tho :)

I can totally understand you! Making mods is not easy!
I am an early programmer, I learn C# for console apps, and Java for Android apps in high school.
So I have some knowledge as for what it's like to be a programmer like you ;)
And prioritizing things is incredibley important.

Huh, why was this issue closed?

I felt like there wasn't much more to discuss about it. I will reopen it if you wish.

No worries, i'm gonna reopen the issue so people who are also interested in a Forge version can comment on the issue rather than making a new one. :)

U can probably contact the guy who ported Fastload, to port FastQuit.

I could contact him (the developer who ports Fastload to Forge), but I'm not sure if I should.
My problem is that I already contacted him once on Discord and asked if he could create a newer Forge port of Fastload, which he did.
I'm sorry, but I think that if I contact him again, I will be asking too much for.

i asked in forges discord the other day and am actually planning to do it myself now since it shouldnt be too complicated
since i dont use fabric api except for translations and instead mostly rely on mixins
it would probably just be a matter of setting up architectury and finding an alternative to modmenu for forge

About the Modmenu alternative for Forge, there's a rather decent option named Catalogue (which is made for Fabric too).
It functions similarily to the Modmenu mod, although it's not perfect.
I found out while playing on Forge with a modpack (which has the Create mod, Create features its own variation of the Modmenu), that you can't access the config of all mods from both options (the Create mod browsing menu and Catalogue).
Sometimes the Create mod shows the option to configure a certain mod, while Catalogue doesn't show it for the same mod, and vice versa.

alright i will look into catalogue, thanks!
does create also have an api to link my config?

I do not know.

By the way, I am an early developer (I'm a high school student too), I learn C# (currently with console applications) and Java (for Android apps). So I understand a thing or two about programming.
Although, I have never made a mod for Minecraft, so I can't really help you about your question that much.

Hi, was the port canceled? and if it isn't, you should port it to NeoForge instead, as most forge mods are switching to that.

Neoforge ports should be made for 1.20.4+ instead, as many mods which only work on forge uses 1.20.1, and neoforge is more relevant on newer versions.


Java Library for Fourier Analysis

We need to find a Java Library which is capable of analyzing how often certain frequencies appear in a sample.
Example Data Structure:
Frequency | Occurences
20 Hz          | 312
20 Hz          | 312
20 Hz          | 312


HV-937 Changing how references are rendered in documentation

https://hibernate.atlassian.net/browse/HV-937

I guess that next release of hibernate-asciidoctor-extensions would be 1.0.3 :). This change depends on https://github.com/hibernate/hibernate-asciidoctor-extensions/pull/3

Now it looks better:

Merged, thanks Marko!
I also updated the pdf plugin so that it also includes the reference.

Great! Forgot about the pdf, thanks!


SSL Certificates issue: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException

I am looking for guidance around SSL certificates for talking to Splunk for an app (data input) implemented using your Java SDK. We have an app currently available in splunkbase: https://classic.splunkbase.splunk.com/app/4310/ implemented using the splunk-sdk-java.
When users of our app tries to validateInput or streamEvents, they see the error PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Looks like this happens because the certificate presented by their local splunk instance cannot be validated by the splunk-sdk-java code as it in not present in their local trust store.
The present workaround we suggest to our customers, is to manually export this cert and import it into their local java cacerts store. This is not always practical, as the location of truststore can vary for each customer and also in case of splunk cloud, customer would need to contact splunk support to make this change as they don't have access to the actual machines.
I see there are multiple open similar issues: https://github.com/splunk/splunk-sdk-java/issues/209, https://github.com/splunk/splunk-sdk-java/issues/204, https://github.com/splunk/splunk-sdk-java/issues/185
Also, we do not want the setValidateCertificates set to false -> https://docs.splunk.com/DocumentationStatic/JavaSDK/1.9.4/com/splunk/HttpService.html#validateCertificates
For PROD environment, TRUE is strongly recommended, whereas working in localhost OR development environment, FALSE is used.
Do you have any workarounds or possible solution for this issue? Any help would be appreciated.

Hi @jrobins04 sorry for the delay in the response. We are working on a feature to enable passing and validation of SSL certificate. Once we have the feature fully developed and merged, will publish a new SDK release with the feature. Will keep you updated for the same.

@jrobins04 Check this: https://github.com/splunk/splunk-sdk-java/issues/209#issuecomment-2048570594


[BEAM-14274] Fix staticcheck warnings in pipelinex

Cleans up staticcheck warnings in the pipelinex package, largely simplifying existing code. Also removes an unused test helper function.

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

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

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM

R: @lostluck


The Haddock databse is not detected

I created the haddock database as described in the README. Even though, I didn't get docs on hover and HIE complained about the missing hoogle database.
Only when I created the database using stack exec -- hoogle generate did the docs on hover started appearing.

What you report is the required process, as defined in the readme.
Is there something else that should happen?

That was a long time ago, I don't remember what exactly was in the readme, but I have a feeling that I expected stack haddock; hoogle generate to do the trick and not require a separate hoogle call in the stack environment


test: add test for carousel component

Closes #297
Description

Add a brief description

Current behavior (updates)

none

New behavior

none

Is this a breaking change (Yes/No):

no

Additional Information

@quangnmwork
Hey! Thanks for the asking. And I merged the PR before replying to the comment, sorry.
Yes! I know.
I just wrote some code. Is this what you wanted?
import { act, fireEvent } from "@testing-library/react"

test("Is the onDrop return files correctly", async () => {
  const file = new File(["test"], "test.png", { type: "image/png" })
  const onDrop = jest.fn()
  const { container } = render(<Dropzone onDrop={onDrop} />)

  const dropzone = container.querySelector(".ui-dropzone")

  await act(async () => {
    fireEvent.drop(dropzone!, {
      dataTransfer: { files: [file], types: ["Files"] },
    })
  })

  expect(onDrop).toHaveBeenCalledWith([file], [], expect.anything())
})

@hirotomoyamada  Sorrry,  I don't mean that.In the carousel component, I am recreating the user's swipe behavior but I am not able to do it. If you know, please tell me

@quangnmwork
Sorry, I misunderstood.
I haven't tested swipe behavior, but I know it can be done using puppeteer.


Helmetize the addons for a complete Helm-native experience with Istio

The helm charts are off to a great start thanks to the work of @sbezverk and @luisyonaldo and many reviewers in the community as well as a few other folks.  Could one or both of you work on adding the addons to the existing Helm charts?  There are no special ordering requirements on the addons that I am aware of.  I have launched them hundreds of times without ordering constraints using a bash script with no synchronization.

add-ons merged.


Fixed external broken links identified by CATS

@jmgsworld,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

patterns-practices/guide/12-patterns-in-the-prism-library-5.0-for-wpf.md
:white_check_mark:Succeeded

patterns-practices/guide/3-managing-dependencies-between-components-using-the-prism-library-5.0-for-wpf.md
:white_check_mark:Succeeded

patterns-practices/guide/bibliography-for-the-developers-guide-to-prism-library-5.0-for-wpf.md
:white_check_mark:Succeeded

patterns-practices/guide/sharing-code-between-silverlight-and-wpf.md
:white_check_mark:Succeeded

patterns-practices/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.