Add a Gitter chat badge to README.md

apiaryio/api-blueprint now has a Chat Room on Gitter
@netmilk has just created a chat room. You can visit it here: https://gitter.im/apiaryio/api-blueprint.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Updated PR with fixed formatting: https://github.com/apiaryio/api-blueprint/pull/153


Update codeStyleSettings.xml so that licence boilerplate is included in new files

Also consider using a maven plugin or other appropriate tool to enforce all files having licences.

This library is now end-of-life and this issue won't be fixed.
This issue has been tagged EOL in case any forks want to import it.


Fix Email Validation Regex on Backend

The email regex on the backend should be modified to accept emails such as<EMAIL_ADDRESS>since currently sub domain names e.g. "cmail.carleton.ca" fail with the validation message "Not a valid email address".

from @zaidoon1:

so when it comes to regex expressions, there is always a trade off, whether it's slow, or missing cases. The best one that is currently available is:
(?:[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])*")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-]*[a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])+)\])
This works for 99.99% of email addresses which is more than enough for our use case. The link can be found below:
http://emailregex.com/

Another option could be to do some more casual form of validation, only checking to see if there is something at the start, something at the end, and an @ simple in the middle e.g<EMAIL_ADDRESS>

From @zaidoon1, another option which may be considered good enough:
^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,}$


Repository and package name mismatch

Github's repository is called markov, but it's published as kurwov at npm. I guess it's not intentional?

thanks, will fix that rn


the position of  experts

Thanks for your great code! According to your paper, the experts are located in layer3 and layer4 of resnet.  Do you conduct some ablation study of the position of the experts, such as experts only in layer4 or in layer2, layer3, and layer4?

Hi, thanks for your interest in our work and good question! Although deploying experts on layer2 or layer3 has similar parameters as those deployed on layer4, this will significantly increase the overall model flops. To make a fairer comparison with the previous baseline, we hope to ensure that RIDE's flops are basically comparable with the baseline. Because of this, we didn't try to deploy experts in earlier layers.
If you have any other questions, please let me know.


Which addons are required?

The docs say that this depends on react 12.0, with addons. I don't want to blindly install all addons - which addons does this library depend on from the list here?

I really like to know this too...my team aren't keen to add them all in.

Looks like the docs on that point are actually out of date - looking at that list I don't see anything that we're using. If memory serves me, the addon that we required was the children helper, but I guess that's built into react-core now.


Stop including EGL/eglmesaext.h

This was a mistake on Mesa's side. We'll need to revert https://github.com/swaywm/wlroots/commit/d113e48a2a32542fe6e12f1759f07888364609bf.
See https://gitlab.freedesktop.org/wayland/weston/merge_requests/289#note_283447

https://github.com/KhronosGroup/EGL-Registry/pull/95 was merged. We should be able to drop it the next mesa release if they pull in the new EGL headers.

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4953
https://gitlab.freedesktop.org/glvnd/libglvnd/-/merge_requests/225

Also need to revert https://github.com/swaywm/wlroots/pull/2171

Done in https://github.com/swaywm/wlroots/pull/2222.


Create a different lambda configuration for each mini-app type

This creates a specialized lambda configuration for each mini-app type that is tuned to the timeout and RAM needs for the mini-app.
Specifically, it sets the following:
Mini-app     | RAM    | Timeout
-------------------------------
Theater      | 1769MB | 90s
Playground   | 512MB  | 300s (can be increased to 900s)
Neighborhood | 512MB  | 60s
Console      | 512MB  | 60s

^ Note: Theater is currently set at 300s timeout since all mini-app types are currently using Theater and will continue to until after HOC week. Once the other app types have been transitioned, the Theater timeout will be decreased.
This PR is paired with a PR from the code-dot-org repo: https://github.com/code-dot-org/code-dot-org/pull/43871, but they can be merged in any order.
Details on how the mini-apps were tuned to these levels can be found here: https://docs.google.com/document/d/1cWpdw5vJkmgdcw4yLg1EO4vM5N3a8M4AtzroPK52j9E/edit#

MIght be worth dynamically provisioning the CloudWatch Alarms for Invocations and Severe Errors in this template, since we’ll have multiple Lambdas to monitor now. Here’s an ERB that renders a snippet of CloudFormation that provisions CloudWatch Alarms. We may want to conditionally create the Alarms only when the Javabuilder stack is production (perhaps by checking the subdomain and basedomain = javabuilderbeta.code.org?)


gptman: 0.8.3 -> 1.0.1

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

the latest version seems to be 1.0.1

there doesn't seem to be anything in the derivation, you might need to cli feature


Class generation

This is the final changes necessary to support class generation from yaml files.  It also reflects the new enum definition format and usage.

It doesn't look like I'm allowed to re-open this, we'll just have to remake it when pyon's PR #18 is ready (this must be pushed first)


Add HiGHS as an LP/QP solver

HiGHS is MIT and it's easy to compile and distribute.
This would be muuuuuch easier than trying to agree on a way that we can distribute Uno with BQPD.

I agree! It's on my to-do list.
We will see a difference in performance though, since HiGHS solves only convex QPs. Negative curvature seems to be important to make good progress.

I am not sure if it relevant in this context (I always get confused by the different requirements of different solvers) but proxsuite since 0.5.0 supports non-convex QPs, see https://github.com/Simple-Robotics/proxsuite/releases/tag/v0.5.0 .

It doesn't have to be HiGHS. But it's hard to distribute a version of Uno with the LP/QP subproblem features if we need the non-free BQPD.
Another option Is OSQP: https://github.com/osqp/osqp

since HiGHS solves only convex QPs. Negative curvature seems to be important to make good progress

I don't understand the details in Uno well enough to comment. At the very least, HiGHS is an excellent LP solver.

but perhaps they will extend their QP solver to nonconvex QPs some day?)

This seems hard.

I don't think this is the most important consideration. It doesn't have to be HiGHS. But it's hard (or impossible) to distribute a version of Uno with the LP/QP subproblem features if we need the non-free BQPD.

Another option Is OSQP: osqp/osqp

I was actually wanting to add an interface for OSQP after we get OSQP 1.0 finished.

Can we create a bqpd binary library and distribute that? As long as we don't send source code, we should be OK.
Sven
Sven Leyffer
Senior Computational Mathematician and Deputy Director
Mathematics and Computer Science Division
Argonne National Laboratory

From: Ian McInerney @.>
Sent: Friday, November 1, 2024 8:42 AM
To: cvanaret/Uno @.>
Cc: Subscribed @.***>
Subject: Re: [cvanaret/Uno] Add HiGHS as an LP/QP solver (Issue #33)
I don't think this is the most important consideration. It doesn't have to be HiGHS. But it's hard (or impossible) to distribute a version of Uno with the LP/QP subproblem features if we need the non-free BQPD. Another option Is OSQP: osqp/osqp
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
I don't think this is the most important consideration. It doesn't have to be HiGHS. But it's hard (or impossible) to distribute a version of Uno with the LP/QP subproblem features if we need the non-free BQPD.
Another option Is OSQP: osqp/osqphttps://urldefense.us/v3/__https://github.com/osqp/osqp__;!!G_uCfscf7eWS!bEkLiXsTtQ4GL7DWV2p6a6-Tzh1-r_15Y5FU1WtrckQ3qyQDCX50f7-JG53FAqntG9nMKylsMdRMJ-DlKzHIpFFzI9I$
I was actually wanting to add an interface for OSQP after we get OSQP 1.0 finished.
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/cvanaret/Uno/issues/33*issuecomment-2451893897__;Iw!!G_uCfscf7eWS!bEkLiXsTtQ4GL7DWV2p6a6-Tzh1-r_15Y5FU1WtrckQ3qyQDCX50f7-JG53FAqntG9nMKylsMdRMJ-DlKzHINkgdce8$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AB52TLOO4GTDGCAMGYAA6XDZ6OAMXAVCNFSM6AAAAABQEZCRY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRHA4TGOBZG4__;!!G_uCfscf7eWS!bEkLiXsTtQ4GL7DWV2p6a6-Tzh1-r_15Y5FU1WtrckQ3qyQDCX50f7-JG53FAqntG9nMKylsMdRMJ-DlKzHIIQY3raI$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Providing a closed source binary library could be sufficient for people who compile Uno themselves. But I'm a bit cautious including it in Uno_jll for us to distribute.

What license would you provide the binary under?
Who would compile and host the binaries?
What platforms would be supported?

Currently we build Uno for a whole host of platforms: https://github.com/JuliaBinaryWrappers/Uno_jll.jl/tree/main?tab=readme-ov-file#platforms

macOS: aarch64 and x86_64
Linux: x86_64, i686, aarchh64, armv6 and v7, and PowerPC
Widows: x86_64 and i686
FreeBSD: x86_64

We also have both glibc and musl, and for differing C++ ABIs.
Perhaps we could have just BQPD binaries for Windows x86_64, Linux x86_64, macOS x86_64, and macOS aarch64, and then compile without BQPD on the more niche platforms?

Perhaps Sven @leyffer meant that we could build binaries of BQPD using BinaryBuilder.jl (without disclosing the source) in a BQPD_jll.jl package?

That would work. As long as the binary package is not openly available.
Sven
Get Outlook for iOShttps://aka.ms/o0ukef

From: Charlie Vanaret @.>
Sent: Saturday, November 2, 2024 3:09:51 AM
To: cvanaret/Uno @.>
Cc: Leyffer, Sven @.>; Mention @.>
Subject: Re: [cvanaret/Uno] Add HiGHS as an LP/QP solver (Issue #33)
Perhaps Sven @leyffer meant that we could build binaries of BQPD using BinaryBuilder. jl (without disclosing the source) in a BQPD_jll. jl package? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Perhaps Sven @leyfferhttps://urldefense.us/v3/__https://github.com/leyffer__;!!G_uCfscf7eWS!eoBqJ3a5CveU7T7sNB4PB_PKMydnCXs-_eHeE2R2FpYzbq9F0Cr20n5YJXo6sEOaySMBi9adrThMuNa7Xc0JL4LVWLY$ meant that we could build binaries of BQPD using BinaryBuilder.jl (without disclosing the source) in a BQPD_jll.jl package?
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/cvanaret/Uno/issues/33*issuecomment-2452942949__;Iw!!G_uCfscf7eWS!eoBqJ3a5CveU7T7sNB4PB_PKMydnCXs-_eHeE2R2FpYzbq9F0Cr20n5YJXo6sEOaySMBi9adrThMuNa7Xc0J6sVWEUU$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AB52TLLMYG75YMH7EUBHJ5LZ6SQG7AVCNFSM6AAAAABQEZCRY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHE2DEOJUHE__;!!G_uCfscf7eWS!eoBqJ3a5CveU7T7sNB4PB_PKMydnCXs-_eHeE2R2FpYzbq9F0Cr20n5YJXo6sEOaySMBi9adrThMuNa7Xc0J2-ptQR8$.
You are receiving this because you were mentioned.Message ID: @.***>

To clarify, I am not comfortable including BQPD in Uno_jll unless:

You make the source code is publicly available under an open-source license. We then compile, host, and distribute BQPD_jll for every platform on Yggdrasil.

or

You compile and host the BQPD binaries (but not source code) under an open-source license on the public internet. We pull in the binary during Uno_jll's build.

The first approach is my preferred option. The second could work, but we will probably run into various compatibility issues and need to restrict what platforms we include BQPD on.
However, it doesn't seem like either of these are viable options.
So, if you want to use the Julia infrastructure to compile and distribute Uno, there are three options:

Keep the status quo. BQPD is not available.
Do what Ipopt does and allow linking at run-time

Users would need to email you, compile the binary themselves, and then set some option in Uno

Do what HSL does

You compile and host a BQPD_jll package locally (not on the public internet). Users need to email you for access.
We compile a public facsimile of BQPD_jll with the correct symbols but no actual code. This lets the compilation of Uno_jll succeed because it thinks everything is there.
Then at runtime, users swap out our fake BQPD_jll with the real one from Sven

So, if you want to use the Julia infrastructure to compile and distribute Uno, there are three options:
1. Keep the status quo. BQPD is not available.

2. Do what Ipopt does and allow linking at run-time

   * Users would need to email you, compile the binary themselves, and then set some option in Uno

3. Do what HSL does

   * You compile and host a BQPD_jll package locally (not on the public internet). Users need to email you for access.
   * We compile a public facsimile of BQPD_jll with the correct symbols but no actual code. This lets the compilation of Uno_jll succeed because it thinks everything is there.
   * Then at runtime, users swap out our fake BQPD_jll with the real one from Sven

Longer term, it would be nice if we could somehow get BQPD support working in the UNO_jll, and creating a somewhat standardized workflow for doing this linking against proprietary libraries would be good, so I would say the method that HSL uses would be a good starting point. However, we also need to be careful that the software can properly handle the library not actually being the full library, so it should be able to identify that it doesn't have the library and fail gracefully to the user. (I don't know how the HSL facsimile handles that, actually).
Perhaps @amontoison can comment on how well the HSL fascimile system is working and if it is recommended to try that?

@imciner2 For HSL_jll.jl, I added a C routine LIBHSL_isfunctional that returns a boolean, allowing us to determine at runtime whether we have the dummy or official version of libHSL.
Uno relies on it to use MA57 or MUMPS at runtime.
I can answer a few questions:

Linking at runtime is a pain on Windows; they don't use standard symbols for that, as usual... I don’t want to go down that path.

Doing it like HSL_jll.jl would require distributing a BQPD_jll.jl from a portal or website, along with a dummy BQPD that includes all the symbols needed by Uno, plus a way to detect at runtime whether we have the official BQPD. It’s like using a hammer on an egg.

The best solution is Oscar's second proposal: we cross-compile BQPD locally on all platforms using BinaryBuilder.jl.
We host all precompiled tarballs publicly somewhere (e.g., Sven’s webpage).
We create a BQPD_jll.jl on Yggdrasil with all the precompiled tarballs.
This is what we already do for some packages that are distributed only in precompiled form (e.g., CUDA_SDK_jll, MKL_jll, etc.).
This approach avoids any compatibility issues and enables us to link Uno_jll.jl with BQPD_jll.jl. It also allows Charlie to generate precompiled Uno releases with BQPD.

The two questions we need to answer are:

Where should we upload all precompiled tarballs?
I think Sven's webpage is suitable since some users could also request the precompiled form of BQPD directly from him.
Finalize the license we want to include in the precompiled tarballs.

Thanks Alexis,
I think we can make your suggestion work. The license will have to be similar to the source code license. I have been distributing pre-compiled versions of BQPD, and also source code for research purposes, so I am OK with this approach.
Kind regard,
Sven
Sven Leyffer
Senior Computational Mathematician and Deputy Director
Mathematics and Computer Science Division
Argonne National Laboratory

From: Alexis Montoison @.>
Sent: Monday, November 4, 2024 8:37 AM
To: cvanaret/Uno @.>
Cc: Leyffer, Sven @.>; Mention @.>
Subject: Re: [cvanaret/Uno] Add HiGHS as an LP/QP solver (Issue #33)
@ imciner2 For HSL_jll. jl, I added a C routine LIBHSL_isfunctional that returns a boolean, allowing us to determine at runtime whether we have the dummy or official version of libHSL. Uno relies on it to use MA57 or MUMPS at runtime. I can answer
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
@imciner2https://urldefense.us/v3/__https://github.com/imciner2__;!!G_uCfscf7eWS!beexAwMTI6CMR94S-tupACXemXfwq3gNJA5FqMZBOhG-KMTb07RnJQqNBtmoN1JJadl2YTfuGfkpRP-vt3XjMD-fsk0$ For HSL_jll.jl, I added a C routine LIBHSL_isfunctional that returns a boolean, allowing us to determine at runtime whether we have the dummy or official version of libHSL.
Uno relies on it to use MA57 or MUMPS at runtime.
I can answer a few questions:

Linking at runtime is a pain on Windows; they don't use standard symbols for that, as usual... I don’t want to go down that path.

Doing it like HSL_jll.jl would require distributing a BQPD_jll.jl from a portal or website, along with a dummy BQPD that includes all the symbols needed by Uno, plus a way to detect at runtime whether we have the official BQPD. It’s like using a hammer on an egg.

The best solution is Oscar's second proposal: we cross-compile BQPD locally on all platforms using BinaryBuilder.jl.
We host all precompiled tarballs publicly somewhere (e.g., Sven’s webpage).
We create a BQPD_jll.jl on Yggdrasil with all the precompiled tarballs.
This is what we already do for some packages that are distributed only in precompiled form (e.g., CUDA_SDK_jll, MKL_jll, etc.).
This approach avoids any compatibility issues and enables us to link Uno_jll.jl with BQPD_jll.jl. It also allows Charlie to generate precompiled Uno releases with BQPD.

The two questions we need to answer are:

Where should we upload all precompiled tarballs?
I think Sven's webpage is suitable since some users could also request the precompiled form of BQPD directly from him.
Finalize the license we want to include in the precompiled tarballs.

—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/cvanaret/Uno/issues/33*issuecomment-2454883495__;Iw!!G_uCfscf7eWS!beexAwMTI6CMR94S-tupACXemXfwq3gNJA5FqMZBOhG-KMTb07RnJQqNBtmoN1JJadl2YTfuGfkpRP-vt3XjyHVLcDc$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AB52TLKTXY6ECRLZWKRLYWDZ652AZAVCNFSM6AAAAABQEZCRY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUHA4DGNBZGU__;!!G_uCfscf7eWS!beexAwMTI6CMR94S-tupACXemXfwq3gNJA5FqMZBOhG-KMTb07RnJQqNBtmoN1JJadl2YTfuGfkpRP-vt3XjdfdKLIo$.
You are receiving this because you were mentioned.Message ID: @.***>

The best solution is Oscar's second proposal: we cross-compile BQPD locally on all platforms using BinaryBuilder.jl.
I can take care of that.
We host all precompiled tarballs publicly somewhere (e.g., Sven’s webpage).
We create a BQPD_jll.jl on Yggdrasil with all the precompiled tarballs.
This is what we already do for some packages that are distributed only in precompiled form (e.g., CUDA_SDK_jll, MKL_jll, etc.).
This approach avoids any compatibility issues and enables us to link Uno_jll.jl with BQPD_jll.jl. It also allows Charlie to generate precompiled Uno releases with BQPD here.

I'm confused with what you are suggesting here. The precompiled packages like CUDA_SDK_jll and MKL_jll actually repackage the files and binaries compiled by the vendors into a tarball that we host on GitHub as an attachment to the releases, we don't link to any external tarballs in the JLL packages. That is then available to any Julia user to install.
Earlier in this thread, @leyffer said

As long as the binary package is not openly available.

was one of the conditions of use, so I think putting those precompiled tarballs with BQPD into the BQPD_jll repo would violate that because the binaries would be openly available for anyone to install. To do this so they aren't available to everyone, Sven still needs to control the distribution of them (somehow).

Hi all,
What I meant was that the source code is not public. It looks like the option that you describe would be OK.
Kind regards,
Sven
Sven Leyffer
Senior Computational Mathematician and Deputy Director
Mathematics and Computer Science Division
Argonne National Laboratory

From: Ian McInerney @.>
Sent: Monday, November 4, 2024 10:27 AM
To: cvanaret/Uno @.>
Cc: Leyffer, Sven @.>; Mention @.>
Subject: Re: [cvanaret/Uno] Add HiGHS as an LP/QP solver (Issue #33)
The best solution is Oscar's second proposal: we cross-compile BQPD locally on all platforms using BinaryBuilder. jl. I can take care of that. We host all precompiled tarballs publicly somewhere (e. g. , Sven’s webpage). We create a BQPD_jll. jl
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

The best solution is Oscar's second proposal: we cross-compile BQPD locally on all platforms using BinaryBuilder.jl.
I can take care of that.
We host all precompiled tarballs publicly somewhere (e.g., Sven’s webpage).
We create a BQPD_jll.jl on Yggdrasil with all the precompiled tarballs.
This is what we already do for some packages that are distributed only in precompiled form (e.g., CUDA_SDK_jll, MKL_jll, etc.).
This approach avoids any compatibility issues and enables us to link Uno_jll.jl with BQPD_jll.jl. It also allows Charlie to generate precompiled Uno releases with BQPD here.

I'm confused with what you are suggesting here. The precompiled packages like CUDA_SDK_jll and MKL_jll actually repackage the files and binaries compiled by the vendors into a tarball that we host on GitHub as an attachment to the releases, we don't link to any external tarballs in the JLL packages. That is then available to any Julia user to install.
Earlier in this thread, @leyfferhttps://urldefense.us/v3/__https://github.com/leyffer__;!!G_uCfscf7eWS!b60y3sFdlN1eQitJrsnwoaZXoowfxxP3PTYn8ks8Kqo65OGXu7_X5Rt89endcf18j6B9F8INSZm2Tkh9LzryTNI2DzA$ said
As long as the binary package is not openly available.
was one of the conditions of use, so I think putting those precompiled tarballs with BQPD into the BQPD_jll repo would violate that because the binaries would be openly available for anyone to install. To do this so they aren't available to everyone, Sven still needs to control the distribution of them (somehow).
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/cvanaret/Uno/issues/33*issuecomment-2455160351__;Iw!!G_uCfscf7eWS!b60y3sFdlN1eQitJrsnwoaZXoowfxxP3PTYn8ks8Kqo65OGXu7_X5Rt89endcf18j6B9F8INSZm2Tkh9LzryEmP5xHg$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AB52TLLZH5PPONQVG6UATRLZ66N73AVCNFSM6AAAAABQEZCRY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGE3DAMZVGE__;!!G_uCfscf7eWS!b60y3sFdlN1eQitJrsnwoaZXoowfxxP3PTYn8ks8Kqo65OGXu7_X5Rt89endcf18j6B9F8INSZm2Tkh9Lzrycrv-VWc$.
You are receiving this because you were mentioned.Message ID: @.***>

What I meant was that the source code is not public. It looks like the option that you describe would be OK.

Great, in that case we just will need some sort of statement (as the copyright holder) giving us the permissions to distribute the binaries, and include the appropriate license statement in the built tarballs. @odow I think you've done something similar for other packages, so maybe you can work with Sven to get that sorted out?

I checked a little bit to see what could be relevant, and I think a EULA seems good.
I started a draft:
END USER LICENSE AGREEMENT (EULA)

### 1. License Grant
The licensor grants you a license to use the software solely in its precompiled (binary) form, for a use within the Julia ecosystem as BQPD_jll.jl or inside precompiled binaries for the software Uno (https://github.com/cvanaret/Uno).

### 2. Permitted Use
You may:
   - Use the software in its binary form within the Julia ecosystem.
   - Integrate the software as a precompiled binary with Uno.

### 3. Restrictions
You may not:
   - Modify, reverse engineer, decompile, or disassemble the software.
   - Redistribute, sublicense, sell, lease, rent, or transfer the software in any form other than as provided by the licensor. Redistribution is only permitted in its original precompiled (binary) form without modification, except for the purpose of repackaging the software as part of another precompiled application, provided that the dynamic library remains unchanged.
   - Use the software to create derivative works.
   - Access or attempt to access the software’s source code.

### 4. Ownership
The software is licensed, not sold. All rights, title, and interest in and to the software, including all intellectual property rights, remain with the licensor. This Agreement does not grant you any ownership rights.

### 5. Redistribution in Precompiled Form
If you intend to redistribute the software as part of another precompiled application (e.g., Uno), you must:
   - Include this Agreement with your distribution, or reference it within the accompanying documentation.
   - Not modify the software in any way, and distribute it only in its original precompiled form provided by the licensor.

### 6. Updates and Support
The licensor may, at its discretion, provide updates, upgrades, or support for the software. Any updates or upgrades provided will be subject to the terms of this Agreement unless other terms are specified.

### 7. Disclaimer of Warranties
The software is provided "as is," without warranty of any kind, either express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement. The licensor does not guarantee that the software will be error-free or uninterrupted.

### 8. Limitation of Liability
To the fullest extent permitted by law, the licensor shall not be liable for any damages arising out of the use or inability to use the software, including but not limited to direct, indirect, incidental, or consequential damages, even if advised of the possibility of such damages.

### 9. License Duration
This Agreement is effective upon acceptance and shall remain in effect indefinitely unless a new agreement is established. The licensor cannot terminate this Agreement once it is accepted, regardless of any alleged violations. You may continue to use the software in accordance with the terms of this Agreement without the risk of termination.

### 10. Governing Law
The terms of this Agreement are intended to be enforceable under the applicable laws of the licensor's jurisdiction.

### 11. Entire Agreement
This Agreement constitutes the entire agreement between you and the licensor regarding the software and supersedes any prior agreements or understandings.

@amontoison can you please delete your comment? I don't want us to provide any legal advice or template.
Let's take this discussion offline. I'll send an email.

@odow Good idea.
I deleted the message.


External Dialog Title and Button follows Internal Padding

After some tests I found out that the external Dialogs, called with both ShowModalDialogExternally() and ShowDialogExternally(), kind of follows the last Internal Dialog shown size and their title appears lower than they should, and buttons higher. And even more if the dialog has not been shown internally.
First: Open an External one... Title is almost at the middle, and so does the button.

Then, open an Internal. Title is as up as it gets, and button down low.

Later, opening an external shows the title with a little less top distance and button with less down distance.

When opening an Internal on a Maximized window, title is still up and button down, as I would like it...

And the same occurs with it on the External.

@thalelinh is still present with the latest alpha?


add requests in setup.py

After reading document.  I know request is abstracted. however, the simple example in README.md will fail because the lack of request package.   how about add requests in your setup.py so the basic sample in README.MD can execute without error.

Sorry for spending time to figure this out.
I would like to make this library neutral to network-io library, for developers testing their own flask server, 'requests' is useless to them.
I will update the 'installation' section of readme for each deps of different usage, and add some warning banner on tutorial/samples. What do you think of this refinement?

I think it is good. people can know your intension better.


Support running tests in out-of-tree build

The test targets were broken for out-of-tree builds.
make test and
make test_basic_tls

Out in 1.5.20


The full path is not supported on current disk - local adapter supported only

Runtime Error,
When I am uploading video s3 bucket

Please check this - https://github.com/pionl/laravel-chunk-upload/wiki/Saving-to-Cloud
Saving chunks to s3 is impossible to use.


Beeping when engagement with enemy ends.

After the last ACT update, I keep getting incessant beeping whenever combat with an enemy ends. After a few seconds, I'll hear a four sequence beep, then after a few more seconds, I hear it again. I'm not sure what caused it to become active, or how to disable it. I even considered finding and deleting the sound file, but I have no idea where Cacbot stores it's sounds.

After a lot of effort, I figured it out. For anyone else with the same problem a new feature was added in the last update. Under Cacbot settings > Jobs > "Play a sound notification if a proc box for dots/etc. expires while in combat" > Switch to disabled.


<EMAIL_ADDRESS>hash check failed

App:         extras/grafana
URL:         https://dl.grafana.com/oss/release/grafana-6.2.2.windows-amd64.zip
First bytes: 50 4B 03 04 0A 00 00 00
Expected:    bee895c4635c54419c77a1e7694cad96e33a4e9d5657ffee0ae6be53ef30fa57
Actual:      c44ae0019834a73860ba9804965b79235be9284017d716823c316ac6b24abc4f
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/lukesampson/scoop-extras/issues/new?title=grafana%406.2.2%3A+hash+check+failed

Autoupdate was pulling the installer hash; now correctly pulls the standalone hash.


Use the current joken release

The current Joken release (0.13.0) requires some API changes. At the same time it reduces the dependency to Timexand to JSX, so we can the Poison as JSON encoder.

Looks great. Thanks!

What about a new hex package version?

done.


runtime/metrics: time.Sleep contributes to "user" rather than "idle" cpu class

What version of Go are you using (go version)?

$ go version
go version go1.20.4 darwin/arm64
go version devel go1.21-f777726ff0 Wed May 17 21:12:04 2023 +0000 darwin/arm64

Does this issue reproduce with the latest release?
Yes. New in Go 1.20 (with the introduction of /cpu/classes/user:cpu-seconds), still present in tip.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/rhys/Library/Caches/go-build"
GOENV="/Users/rhys/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/rhys/go/pkg/mod"
GONOPROXY="*"
GONOSUMDB="*"
GOOS="darwin"
GOPATH="/Users/rhys/go"
GOPRIVATE="*"
GOPROXY="direct"
GOROOT="/Users/rhys/go/version/go1.20"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/rhys/go/version/go1.20/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.4"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/lf/n4ry0qv5639_3z0nhyhy3z7c0000gs/T/go-build1529865541=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
I inspected /cpu/classes/user:cpu-seconds and /cpu/classes/idle:cpu-seconds from the runtime/metrics package before and after calling time.Sleep.
Note that CPU time accounting isn't available on the playground, so the problem doesn't reproduce there.
package main

import (
	"runtime"
	"runtime/metrics"
	"testing"
	"time"
)

func TestSleepAccounting(t *testing.T) {
	names := []string{
		"/cpu/classes/gc/mark/assist:cpu-seconds",
		"/cpu/classes/gc/mark/dedicated:cpu-seconds",
		"/cpu/classes/gc/mark/idle:cpu-seconds",
		"/cpu/classes/gc/pause:cpu-seconds",
		"/cpu/classes/gc/total:cpu-seconds",
		"/cpu/classes/idle:cpu-seconds",
		"/cpu/classes/scavenge/assist:cpu-seconds",
		"/cpu/classes/scavenge/background:cpu-seconds",
		"/cpu/classes/scavenge/total:cpu-seconds",
		"/cpu/classes/total:cpu-seconds",
		"/cpu/classes/user:cpu-seconds",
	}
	prep := func() []metrics.Sample {
		mm := make([]metrics.Sample, len(names))
		for i := range names {
			mm[i].Name = names[i]
		}
		return mm
	}
	m1, m2 := prep(), prep()

	dur := time.Second

	runtime.GC() // update /cpu/classes metrics
	metrics.Read(m1)
	time.Sleep(dur)
	runtime.GC() // update /cpu/classes metrics
	metrics.Read(m2)

	for i := range names {
		if m1[i].Value.Kind() == metrics.KindBad {
			continue
		}
		t.Logf("%s %0.3f\n", names[i], m2[i].Value.Float64()-m1[i].Value.Float64())
	}

	for i := range names {
		if names[i] == "/cpu/classes/user:cpu-seconds" {
			if dt := m2[i].Value.Float64() - m1[i].Value.Float64(); dt > (dur / 2).Seconds() {
				t.Errorf(`BUG: time.Sleep has contributed to "user" rather than "idle" CPU class`)
			}
		}
	}
}

What did you expect to see?
I expected time during which all user goroutines are asleep to count as "idle" time.
What did you see instead?
The full duration of the time.Sleep call is counted towards /cpu/classes/user:cpu-seconds. Maybe the P that is responsible for tracking the timer isn't considered to be "fully asleep"?
I see there's a chance of some overestimation:
/cpu/classes/user:cpu-seconds
	Estimated total CPU time spent running user Go code. This may
	also include some small amount of time spent in the Go runtime.
	This metric is an overestimate, and not directly comparable
	to system CPU time measurements. Compare only with other
	/cpu/classes metrics.

But there's also a chance of overestimation in the "idle" class. And during the sleep, no user or runtime code should be "executing".
/cpu/classes/idle:cpu-seconds
	Estimated total available CPU time not spent executing
	any Go or Go runtime code. In other words, the part of
	/cpu/classes/total:cpu-seconds that was unused. This metric is
	an overestimate, and not directly comparable to system CPU time
	measurements. Compare only with other /cpu/classes metrics.

$ go1.20 test /tmp/sleep_test.go -cpu=1,8
--- FAIL: TestSleepAccounting (1.00s)
    sleep_test.go:45: /cpu/classes/gc/mark/assist:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/mark/dedicated:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/mark/idle:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/pause:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/total:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/idle:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/scavenge/assist:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/scavenge/background:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/scavenge/total:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/total:cpu-seconds 1.001
    sleep_test.go:45: /cpu/classes/user:cpu-seconds 1.001
    sleep_test.go:51: BUG: time.Sleep has contributed to "user" rather than "idle" CPU class
--- FAIL: TestSleepAccounting (1.00s)
    sleep_test.go:45: /cpu/classes/gc/mark/assist:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/mark/dedicated:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/mark/idle:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/gc/pause:cpu-seconds 0.001
    sleep_test.go:45: /cpu/classes/gc/total:cpu-seconds 0.002
    sleep_test.go:45: /cpu/classes/idle:cpu-seconds 7.010
    sleep_test.go:45: /cpu/classes/scavenge/assist:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/scavenge/background:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/scavenge/total:cpu-seconds 0.000
    sleep_test.go:45: /cpu/classes/total:cpu-seconds 8.013
    sleep_test.go:45: /cpu/classes/user:cpu-seconds 1.002
    sleep_test.go:51: BUG: time.Sleep has contributed to "user" rather than "idle" CPU class
FAIL
FAIL	command-line-arguments	2.121s
FAIL

CC @golang/runtime @mknyszek

That's very odd. I would expect the M to be blocked in the netpoller, after releasing its P. Once the P is idle, all the CPU time should be going to idle time. Specifically, down here: https://cs.opensource.google/go/go/+/master:src/runtime/proc.go;l=3105?q=findRunnable&ss=go%2Fgo. pidleput is what actually switches the runtime to tracking idle time, and that specifically happens before blocking in the poller.
I suspect whatever the problem is, it'll be easy to fix.

Found the issue; we're using a stale "now" value for Ms that block in netpoll.
$ git diff
diff --git a/src/runtime/proc.go b/src/runtime/proc.go
index 35aeb2d1ac..987c1cd2c7 100644
--- a/src/runtime/proc.go
+++ b/src/runtime/proc.go
@@ -3112,7 +3112,7 @@ top:
                        goto top
                }
                lock(&sched.lock)
-               pp, _ := pidleget(now)
+               pp, _ := pidleget(0)
                unlock(&sched.lock)
                if pp == nil {
                        injectglist(&list)

Ugh, this probably has implications for the GC CPU limiter.

We may want to backport this? The fix is very small and we have a test.


Production flag

Only crash on serious bugs. Try to ignore minor assertions
Wait for hardware devices on start because they might take a while to initialise on start

fixed in dev-70


Archive gridpathratoolkit data from GCS

Overview
Closes https://github.com/catalyst-cooperative/pudl/issues/3895
What problem does this address?
Archives gridpathratoolkit data by uploading the original files given to us by Moment Energy Insights to a private sources.catalyst.coop bucket, and then directing the archiver to grab the data from there. This way, we can update the data in the GCS bucket and the archiver will automatically grab the new files and update the datapackage.json file.
What did you change in this PR?
Mimic the archiver in #438, but for the GridPath data.
Testing
How did you make sure this worked? How can a reviewer verify this?
Run pudl_archiver --datasets gridpathratoolkit
To-do list
- [x] Verify sandbox archive looks as expected and production archive can be updated
- [x] Review the PR yourself and call out any questions or issues you have

Now that we have this private bucket that we can use as the original source, I think it would be better to archive the entire collection of GridPath RA Toolkit data with all the original filenames, and rename the files that we're archiving on Zenodo programmatically? There's a lot of additional data in there, and I created the zipfiles and named them by hand to fit our expected partition names and now looking back it's not 100% clear what the mapping was for a couple of the files...
Solar

gridpath-ra-toolkit/TemporalData/HourlySolar_byProject.zip --> original_solar_capacity.zip
gridpath-ra-toolkit/MonteCarlo_Inputs.zip/temporal_data/solar/ --> aggregated_solar_capacity.zip
gridpath-ra-toolkit/MonteCarlo_Inputs.zip/temporal_data/solar_syn/ --> aggregated_extended_solar_capacity.zip
??? --> solar_capacity_aggregations.csv

Wind

gridpath-ra-toolkit/TemporalData/HourlyWind_byProject.zip --> original_wind_capacity.zip
gridpath-ra-toolkit/MonteCarlo_Inputs.zip/temporal_data/wind/ --> aggregated_wind_capacity.zip
gridpath-ra-toolkit/MonteCarlo_Inputs.zip/temporal_data/wind_syn/ --> aggregated_extended_wind_capacity.zip
??? --> wind_capacity_aggregations.csv

Weather

gridpath-ra-toolkit/TemporalData/DailyWeatherData_cleaned.csv --> daily_weather.csv

I was nervous to archive all of the original files on Zenodo since some of them were based on the WECC ADS which doesn't have clear licensing terms.

I was nervous to archive all of the original files on Zenodo since some of them were based on the WECC ADS which doesn't have clear licensing terms.

Just to clarify - you're proposing archiving them all on GCS but only uploading the ones that are already published, with the rename happening during the archiving?

Just to clarify - you're proposing archiving them all on GCS but only uploading the ones that are already published, with the rename happening during the upload to Zenodo?

Yes, exactly -- put the whole collection of data that's associated with the GridPath RA Toolkit in our private GCS bucket, and then use that as the original source (since it is), with any file renaming or zipping/unzipping that's required done in the source-to-Zenodo archiving process, like we do with our other sources.  I only renamed the files by hand because the entire archiving process was manual before and I wanted them to have a simple naming / partitioning convention.

That makes sense to me - do you want to go ahead and add the raw files to the correct source folder in GCS, and I can update this archiver?

I've uploaded the contents as published in GridLab's Google Drive to gs://sources.catalyst.coop/gridpathratoolkit/ (plus the PDF of the GridPath RA Toolkit report)
I've temporarily moved the old manually archived files to gs://sources.catalyst.coop/gridpathratoolkit-manual/ (we can remove after the new archive is working)

I spent a little time trying to identify which of the original files correspond to the {wind,solar}_capacity_aggregation.csv files in the manual archive and wasn't successful, so you'll probably be as fast to do it as I am with some finding and grepping.


Unhandled error during execution of scheduler flush.

Version
3.0.4
Reproduction link
https://jsfiddle.net/frikeldon/dqrpan9m/1/
Steps to reproduce
Press button with label "Toggle"
What is expected?
Must to appear an element with the "Hello world!" text
What is actually happening?
An exception appear in console

I'm trying to make a wrapper component for make child components work together

same as #2715 and closed by #2717
It's not release yet.


adapted pretrained model to training

Does this allows to use pretrained model
models--hpcai-tech--OpenSora-STDiT-v2-stage3/snapshots/3074d7cc95aca24ae12b685e07fab7d3e2570667/model.safetensors for finetuning?

We have updated the config to support huggingface's from_pretrained, you can specify from pretrained like this https://github.com/hpcaitech/Open-Sora/blob/main/configs/opensora-v1-1/inference/sample.py#L10.


MCS-188: IntPhys Scene Generator: Collision

use acceleration to check for possible collision between objects

Looks fine. Are there any corresponding unit test(s)?

No, but that's a good idea. I'll write one


tests: drivers: spi: dt_spec/drivers.spi.dt_spec and spi_loopback/drivers.spi.loopback BUS FAULT

Describe the bug
The tests/drivers/spi/spi_loopback/drivers.spi.loopback and tests/drivers/spi/dt_spec/drivers.spi.dt_spec
Observed for

nrf54h20dk/nrf54h20/cpuapp

To Reproduce
Steps to reproduce the behavior:

have nrf54h20dk/nrf54h20/cpuapp connected
go to your zephyr dir
call ./scripts/twister -T tests/drivers/spi -p nrf54h20dk/nrf54h20/cpuapp--device-testing --device-serial /dev/ttyACM0 -v --inline-logs
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
E: ***** BUS FAULT *****
E:   Precise data bus error
E:   BFAR Address: 0x5f09502c
E: r0/a1:  0x00000008  r1/a2:  0x00000000  r2/a3:  0x5f095000
E: r3/a4:  0x0000002c r12/ip:  0x0e0acea1 r14/lr:  0x0e0a8d11
E:  xpsr:  0x69000000
E: Faulting instruction address (r15/pc): 0x0e0aceae
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x2f0112c8 (main)
E: Halting system

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.16.5
Commit SHA or Version used: v3.6.0-3753-gbe682e22e166

@e-rk There seems to be hypothesis that after #71989 this test fails (ie. adding in this test /delete-node/ &exmif; helps)

This is because of lack of this commit: https://github.com/nrfconnect/sdk-zephyr/commit/7ea6937f02affb74cae2327aeca955ae5e5c3106
The commit is not suitable for upstream in this form and larger changes to the spi_dw.c will be needed.

The same for tests/drivers/spi/spi_slave/drivers.spi_slave.api for nrf54h20dk/nrf54h20/cpuapp


Black screen, the sound is there, there is no image.

[+] I have verified there are no duplicate active or recent bugs, questions, or requests
[+] I have verified that I am using the latest version of Easy Video Player.
[+] I have read over the documentation (before asking questions on how to do something).

Include the following:

Easy Video Player version: 0.3.0
Device OS version: 7.1.1
Device Manufacturer: LG
Device Name: Nexus 5

Also, please wrap Java with correct syntax highlighting.
Hello. Please tell me how to fix the problem with a black screen, the sound is there, there is no image. Other players (MX, VLC) reproduce without problems.

in Menifest file
android:hardwareAccelerated="true" may help you


Reopen HDDS-2034 Async RATIS pipeline creation and destroy through heartbeat commands

https://issues.apache.org/jira/browse/HDDS-2034

BTW, thank you very much @ChenSammi the re-creation of the patch. The build results look nice, full green.

"I think we should consider AllocatedPipelines during pipelineCount."
The allocated one means it is not reported from DN yet, which we don't know if it is in a health state.

"I think we should consider AllocatedPipelines during pipelineCount."
The allocated one means it is not reported from DN yet, which we don't know if it is in a health state.

If we don't consider them, then it will be always like a fresh installed cluster, as none will be in open state. As this count is got, during startup.(Where all pipelines in DB are set to initial state)
I think when data node is decommissioned, then we should remove those pipelines from SCM.

And also one more thing I have seen is in DeadnodeHandler, we fire the event to send close command to DN, and immediately removing pipeline from DB and calling trigger pipeline creation.
Now Datanode becomes stale means it might not be running. So, in this case below flow looks incorrect.
SCM PipelineManager.java:
private void destroyPipeline(Pipeline pipeline) throws IOException {
pipelineFactory.close(pipeline.getType(), pipeline);
// remove the pipeline from the pipeline manager
removePipeline(pipeline.getId());
triggerPipelineCreation();
}
DeadNodeHandler.java
pipelineManager.finalizeAndDestroyPipeline -> destoryPipeline.

So, in this case below flow looks incorrect or is this is fine?, as we are removing from DB, without removal.
I think we should be fine. Here is an example: one stale datanode releases two other datanodes of the destroyed pipeline. A new pipeline can be created if there are one of two extra datanodes available, they can be used to create a new pipeline.

If we don't consider them, then it will be always like a fresh installed cluster, as none will be in open state. As this count is got, during startup.(Where all pipelines in DB are set to initial state)

Good point. I somehow remember the DB always has the matching state update with the in-memory statemanager, which is not the case here. As a result, we will need to consider both ALLOCATED and OPEN pipeline here. Given that the in memory pipeline map always been initialized to ALLOCATED state at the time of the safemode rule is initialized, we could just check ALLOCATED state as well.

So, in this case below flow looks incorrect or is this is fine?, as we are removing from DB, without removal.

I think we should be fine. Here is an example: one stale datanode releases two other datanodes of the destroyed pipeline. A new pipeline can be created if there are one of two extra datanodes available, they can be used to create a new pipeline.

Yes, I agree. But without ratis group remove call, we are considering them to form a new pipeline.

So, in this case below flow looks incorrect or is this is fine?, as we are removing from DB, without removal.

I think we should be fine. Here is an example: one stale datanode releases two other datanodes of the destroyed pipeline. A new pipeline can be created if there are one of two extra datanodes available, they can be used to create a new pipeline.

Yes, I agree. But without ratis group remove call, we are considering them to form a new pipeline. Will this not be a problem?

So, in this case below flow looks incorrect or is this is fine?, as we are removing from DB, without removal.

I think we should be fine. Here is an example: one stale datanode releases two other datanodes of the destroyed pipeline. A new pipeline can be created if there are one of two extra datanodes available, they can be used to create a new pipeline.

Yes, I agree. But without ratis group remove call, we are considering them to form a new pipeline. Will this not be a problem?

Do you mean form a new pipeline with the datanodes which might should close the previous pipeline and remove the ratis group first, will it to be a problem?  Correct me if you don't mean this.
The answer to above question is No. It will not become a problem since the underneath Ratis library supports multi-raft.

So, in this case below flow looks incorrect or is this is fine?, as we are removing from DB, without removal.

I think we should be fine. Here is an example: one stale datanode releases two other datanodes of the destroyed pipeline. A new pipeline can be created if there are one of two extra datanodes available, they can be used to create a new pipeline.

Yes, I agree. But without ratis group remove call, we are considering them to form a new pipeline. Will this not be a problem?

Do you mean form a new pipeline with the datanodes which might should close the previous pipeline and remove the ratis group first, will it to be a problem? Correct me if you don't mean this.
The answer to above question is No. It will not become a problem since the underneath Ratis library supports multi-raft.

Do you mean form a new pipeline with the datanodes which might should close the previous pipeline and remove the ratis group first, will it to be a problem? Correct me if you don't mean this.

Yes this was my question. Thanks for the reply, then I think it should be okay here.

Hi @elek , the acceptance is cancelled.  Should I re-trigger the CI and make sure it succeeds?

/retest

@ChenSammi /retest doesn't work for Github Actions.  Checks can be re-run from the Checks page (for committers).
https://help.github.com/assets/images/help/repository/rerun-checks-drop-down.png

I will implement a /retest later, until that please push a new commit to have new results:
git commit --allow-empty -m "retrigger build" && git push

"Cancelled" means time out after 6 hours. On the master the acceptance tests can be executed until 1 hours, the timeout caused by the patch.
And actually this was the root cause of the revert. Without the patch it can work well.
It may be a problem with the new safe mode check?

It may be a problem with the new safe mode check?

Safe mode check looks good to me based on the code, and the last secure cluster passed the check:
2019-11-22T04:43:04.8986872Z SCM is out of safe mode.
2019-11-22T04:43:04.8987697Z Safe mode is off

But something is wrong with the execution of the secure test:
https://pipelines.actions.githubusercontent.com/O2JnqO9VD7g40zn5cnS8ZQ3t6IkBNUXf9dtdL8xzpLtWhEsOm2/_apis/pipelines/1/runs/279/signedlogcontent/44?urlExpires=2019-11-25T13%3A35%3A19.9767125Z&urlSigningMethod=HMACV1&urlSignature=Kzda9PFputac%2BHePoESDsVBJz8zyio8TIHOBvcMscIQ%3D

I tried to define a test timeout. Hopefully it makes possible to download real test log to identify the problem.

@elek ozonesecure acceptance test being stuck at Ozonefs test (and timing out after 6 hours) is happening intermittently in other PRs and post-commit builds, too.
https://github.com/apache/hadoop-ozone/pull/263/checks?check_run_id=316855596
https://github.com/apache/hadoop-ozone/runs/316658066

happening intermittently in other PRs and post-commit builds, too.

Thanks the info. But it seems to be reproducible with this patch. (it fails all the time). Can be connected with the async pipeline creation.
Will try to debug tomorrow with pushing more commits + adjust timeouts + save the log files even in case of timeouts...

This acceptance test failed.
1 datanode is up and healthy (until now)
3 datanodes are up and registered to the scm
SCM is out of safe mode.
Safe mode is off
ozone-basic :: Smoketest ozone cluster startup
Check webui static resources                                          | PASS |
Start freon testing                                                   | FAIL |
255 != 0
ozone-basic :: Smoketest ozone cluster startup                        | FAIL |
2 critical tests, 1 passed, 1 failed
2 tests total, 1 passed, 1 failed
Output:  /tmp/smoketest/ozone/result/robot-ozone-ozone-basic-scm.xml

Hi @elek,  can this be merged now?

Hi @elek, can this be merged now?

Definitely. I am 100% +1. Just waited one day for any potential feedback from us timezone.
(As I understood @bharatviswa504 an @xiaoyuyao were happy with the patch earlier, so I will commit this patch. The us holidays might help to find any instability on the mater).
Thank you very much the patient and the continues improvement. And sorry for this complicated merge. I owe you some quick code reviews for next patches ;-)
I am doing the last local compilation and will push it.

Thanks @elek @xiaoyuyao @bharatviswa504 for the code review, especially @elek for help narrow down the test failure issues.


headerTransparent: false in embedded stack adds white area at bottom of screen

Before submitting a new issue

[X] I tested using the latest version of the library, as the bug might be already fixed.
[X] I tested using a supported version of react native.
[X] I checked for possible duplicate issues, with possible answers.

Bug summary
When using headerTransparent: false and headerLargeTitle: false in an embedded native stack navigator a white area occurs at bottom of screen on iPad with iOS >= 18. The bug can be replicated in the example app when changing this line to false https://github.com/okwasniewski/react-native-bottom-tabs/blob/af0c62af8ab408a6b5e78622dca32b01b774aecc/apps/example/src/Examples/NativeBottomTabsEmbeddedStacks.tsx#L10
Printscreen of the bug:

Unsure if the issue is with this library or react-native-screens but posting it here since the bug does not occur with @react-navigation/bottom-tabs
Library version
0.6.0
Environment info
From the example app:

System:
  OS: macOS 14.7.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 297.39 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.17.0
    path: ~/.nvm/versions/node/v20.17.0/bin/node
  Yarn:
    version: 3.6.1
    path: ~/.nvm/versions/node/v20.17.0/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v20.17.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/johan.kasperi/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK:
    API Levels:
      - "28"
      - "30"
      - "34"
      - "35"
    Build Tools:
      - 28.0.3
      - 29.0.2
      - 29.0.3
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 34.0.0
      - 35.0.0
    System Images:
      - android-22 | Google APIs ARM 64 v8a
      - android-23 | Google APIs ARM 64 v8a
      - android-25 | Google APIs ARM 64 v8a
      - android-28 | Google ARM64-V8a Play ARM 64 v8a
      - android-35 | Google APIs ARM 64 v8a
      - android-VanillaIceCream | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12483815
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.5
    path: /Users/johan.kasperi/.sdkman/candidates/java/current/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/johan.kasperi/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false

Steps to reproduce

Change this line to false in the example app:  https://github.com/okwasniewski/react-native-bottom-tabs/blob/af0c62af8ab408a6b5e78622dca32b01b774aecc/apps/example/src/Examples/NativeBottomTabsEmbeddedStacks.tsx#L10
Run example app

Reproducible sample code
I think running the example app with the "steps to reproduce" is sufficient? Please let me know if I need to setup a runnable repro.

Hey, thanks for opening the issue!
Can you try setting ignoresTopSafeArea={false} on the navigator? It looks like it fixes the issue for me when running on iPad with this config of React Native Screens.

Same issue here.
By setting ignoresTopSafeArea={false} the white area is kinda gone. But The iOS navigation bar still has the white background and is not translucent.

Same issue here. By setting ignoresTopSafeArea={false} the white area is kinda gone. But The iOS navigation bar still has the white background and is not translucent.  And on screens without a stack / header the statusbar becomes blank (no longer translucent).

Same thing happening for me

Thanks for confirming! Looks like it makes it a bit better 👍🏻 I will check why it's still not under the bar

Should be fixed in 0.7.2 without SafeAreaView


Preconditioning in Multilevel Optimization

Users from the HYBRID project have requested the ability to precondition lower subspaces when steps are taken in higher subspaces, during multilevel optimization runs.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed? Improvement made
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)  Test for improvement in regression system
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?  Not defect, but an email could be useful, but not required.
[x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? Not defect
[x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided? Will be closed with merge request

Close reviewed by @joshua-cogliati-inl


Change name of service

https://github.com/kjaymiller/cookiecutter-relecloud/blob/51bf9d3569a162b5549f5e2192f0c2afe9b674d7/cookiecutter.json#L7

I'm not entirely sure if postgres-service is descriptive enough.
Possible options:
postgres-aca-addon
postgres-aca-extension
postgres-addon

Maybe add-on is okay since they used it in this blog post:
https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-container-apps-service-management-just-got-easier-preview/ba-p/3827305
addon does seem to be used in conjunction with AKS as well, but now I'm thinking perhaps it's used in the same way:
https://github.com/kjaymiller/cookiecutter-relecloud/blob/e3fe4450f155cbcbecb18964cdf94319f6fda76b/{{cookiecutter.__src_folder_name}}/infra/core/host/aks.bicep#L20
I agree that "service" isn't descriptive enough, I realized that after I made the change. :)

fixed in #127


Using a NSMapTable to hold references to associated objects

Protect against other third party libraries with duplicate keys as associated object.  The 'state' key could be quite common. This is slightly better than namespaces which is an alternative solution.

Using an enum AssociatedObjectKey with a rawValue to avoid duplicate strings and make it easier to add new properties if needed.

How about just adding some prefix on associated keys? For example: state becomes ReactorKit_state. What is the benefit of using NSMapTable?

Hmm. I couldn't find any benefits of using NSMapTable over associated objects. Isn't it same with using a global dictionary? And it doesn't work properly. RxTodo tests are failing with this code. 🤔🤔🤔

Fair enough. The test case shows that the values are written and removed as usual but maybe they need deeper tests.


Add a legend in the visualization frame

Legend should show,

what does the colors mean
What does the different arrows mean
Which is the root Qnode(maybe use a different color)

I think all of these are addressed at this point, closing.


import: documentation

I suggest to add the following information to:
http://elastalert.readthedocs.io/en/latest/ruletypes.html#import

Only one file can be imported in each rule file.
Filename can be absolute path or a relative path, path is relative to the rules directory.

https://github.com/Yelp/elastalert/pull/1250


fastboot: Fix hardcoded endpoint number

Some devices use a different endpoint number (5 and 6 in my device) under fastboot. This fix will use the endpoint number found during connect to perform transferIn and transferOut operations.

Thanks for the fix. The hard-coded endpoint numbers are a relic from the initial prototype that I never got around to addressing because all of my devices use endpoint 0x1 for both in and out, so it's nice to get that fixed.


proposal: design Wasm ABI for tracing providers

Title: design Wasm ABI for tracers
Context:

after Envoy moved to libc++, dynamic_ot-based tracers got broken because they were relying on C++ ABI
following that, a potential new tracing provider expressed its interest in C ABI instead
so, it seems that tracing providers could benefit from having their own Wasm ABI

Proposal:

Let's try to design Wasm ABI for tracers
Along the way, let's expand on ideas that came out of reviews for Wasm upstreaming PRs, namely:

ABI should be modular and complementary to proxy-wasm/spec
ABI should use versioning scheme similar to regular Envoy extensions, e.g. envoy.tracers.v1alpha0
ABI should support usage model consistent with regular Envoy extensions, e.g. it should be possible to have N instances of the same extension type each with a different configuration
ABI should be optimized for data passing from Envoy to the Wasm extension in just 1 function call

@yskopets do you have any thoughts on how existing trace libraries will work under Wasm? Is it reasonable to suspect that most of them will "just work" when built for a Wasm target and wrapped with an Envoy Wasm tracing ABI shim?

Is it reasonable to suspect that most of them will "just work" when built for a Wasm target and wrapped with an Envoy Wasm tracing ABI shim?

This would be optimal though I'm skeptical it's going to be easy to make this work. At a high level I think it's a great idea to start working on other extension types and see how we can make that work, especially as we navigate the envoy specific vs. non-envoy specific ABI.
My suggestion would be to start as @yskopets suggests and let's do a design proposal for an Envoy WASM tracing plugin ABI, and let's figure out where the process/design holes are. cc @jplevyak @PiotrSikora

@htuch
Right now, Envoy has roughly 3 categories of tracers:

Envoy-agnostic (dynamic_ot)
Almost Envoy-agnostic (opencensus)
Envoy-native (datadog, lightstep, xray, zipkin)

So,

Envoy-agnostic tracers should "just work".
Almost Envoy-agnostic - opencensus - hard to say. OpenCensus is very unique.
Envoy-native tracers will definitely require some changes:

TLS logic should be completely removed from the tracer
it would be necessary for Envoy to expose to a Wasm extension parts of API like ClusterManager, Runtime::Loader, etc. So, it might be more reasonable to slightly redesign the tracer instead.


Nuxt build failed on Cloudflare Pages. Cannot resolve "@img/sharp-wasm32/versions".

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[X] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[X] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
Cloudflare system properties can be found here, I'm using V2
https://developers.cloudflare.com/pages/configuration/language-support-and-tools/#supported-languages-and-tools
What are the steps to reproduce?

Create a nuxt app  with npx nuxi@latest init <project-name> 2. Add the sharp package with npm install sharp (also tried npm install --cpu=x64 --os=linux --libc=glibc sharp)
npm run dev works
npm run build works
Deploy to Cloudflare Pages

What is the expected behaviour?
Project deployed to cloudflare pages correctly.
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
Cloudflare build logs:

2024-05-22T23:15:10.918209Z	[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)
2024-05-22T23:15:15.338888Z	[error] [nitro] Error: Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
2024-05-22T23:15:15.339289Z
2024-05-22T23:15:15.33952Z
2024-05-22T23:15:15.33976Z	undefined
2024-05-22T23:15:15.341917Z	[error] Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
2024-05-22T23:15:15.34213Z	  at Object.resolveId (node_modules/nitropack/dist/nitro.mjs:1966:17)
2024-05-22T23:15:15.342262Z	  at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:19674:28)
2024-05-22T23:15:15.342382Z	  at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18355:26)
2024-05-22T23:15:15.3425Z	  at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18758:15)
2024-05-22T23:15:15.342608Z	  at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:785:16
2024-05-22T23:15:15.342721Z	  at async Promise.all (index 5)
2024-05-22T23:15:15.342837Z	  at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:777:32
2024-05-22T23:15:15.34298Z	  at async rewriteRequireExpressionsAndGetImportBlock (node_modules/@rollup/plugin-commonjs/dist/es/index.js:1354:28)
2024-05-22T23:15:15.343127Z	  at async transformCommonjs (node_modules/@rollup/plugin-commonjs/dist/es/index.js:1933:23)
2024-05-22T23:15:15.343243Z	  at async transform (node_modules/rollup/dist/es/shared/node-entry.js:18676:16)
2024-05-22T23:15:15.343346Z	  at async ModuleLoader.addModuleSource (node_modules/rollup/dist/es/shared/node-entry.js:18892:36)
2024-05-22T23:15:15.343449Z
2024-05-22T23:15:15.343571Z	[error] Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
2024-05-22T23:15:15.422188Z	Failed: Error while executing user command. Exited with error code: 1
2024-05-22T23:15:15.434278Z	Failed: build command exited with code: 1
2024-05-22T23:15:16.653163Z	Failed: error occurred while running build command

As the log says, it cant resolve @img/sharp-wasm32/versions, I have tried to add the @img/sharp-wasm32 package on the optionalDependencies, but it also fails.
The log also is salying that externals are not allowed, but as it says on the docs, I have tried to add the following code on the nuxt.config.ts:
vite:{
    build: {
      rollupOptions: {
        external: ['sharp']
      }
    }
  },

I also tried diferent versions of the package. The last working version is the 0.32.6
I'm doing something wrong? Im completely lost right now.

You are correct, if I change the Nitro preset to anything except the cloudflare one the build is done normally. Thanks for your reply.

Probablemente te hayas encontrado con unjs/nitro#1821

2024-05-22T23:15:10.918209Z [info] [nitro] Creación de servidor Nuxt Nitro (ajuste predeterminado: cloudflare-pages)

Según tengo entendido, el entorno de creación de páginas de Cloudflare se ejecuta en Node.js, por lo que es posible que puedas usar el ajuste predeterminado de Nuxt en lugar de hacerlo cloudflare-pagesy, por lo tanto, evitar la lógica de parcheo de Nitro require.

Thanks my friend
use
nuxt.config.ts
and

Success: Your site was deployed!
--

  nitro: {
    preset: 'node-server',
  },

I was able to deploy onto cloudflare pages with the following packages installed:
    "@img/sharp-libvips-dev": "^1.0.6",
    "@img/sharp-wasm32": "^0.33.5",
    "sharp": "^0.33.5",

I also have nodejs_compat flag set into my cloudflare pages project (for a different dependency) but not sure if it will impact it or not.


LiteLLM Improvements

Hi @akshata29,
Thanks for using LiteLLM.
I'm one of the co-maintainers. How can we make it better for you?

@krrishdholakia  - We will revert back once we start implementing further in the repo


plan_fragment_executor should call DataSink::try_close before close

fix
VTabletWriter::close called  VTabletWriter::try_close before refactor
now VTabletWriter::close is called by be/src/runtime/plan_fragment_executor.cpp
some formatting

Refactor of VTabletWriter should be the next target ...


Python GAPIC: Language v1

This pull request was generated by artman. Please review it thoroughly before merging.

@lukesneeringer docs build is still broken
Warning, treated as error:
/var/code/gcp/docs/language/gapic/v1beta2/api.rst:4: (WARNING/2) autodoc: failed to import module 'google.cloud.language_v1beta2'; the following exception was raised:
Traceback (most recent call last):
  File "/var/code/gcp/.nox/docs/lib/python3.6/site-packages/sphinx/ext/autodoc.py", line 657, in import_object
    __import__(self.modname)
  File "/var/code/gcp/.nox/docs/lib/python3.6/site-packages/google/cloud/language_v1beta2/__init__.py", line 17, in <module>
    from google.cloud.gapic.language.v1beta2 import language_service_client as lsc
ModuleNotFoundError: No module named 'google.cloud.gapic.language.v1beta2'

That is not a docs problem. That is an artman problem. I will need to massage this manually.


its cleared on blur if using properties "typeable" and "langague" together

When I using "typeable" and "language" properties together, picker cleared on blur.

Having same problem, any solutions?

if i use a date formatted like YYYY-MM-DD. Its not cleared on blur.
            required             :language="de"             format="dd.MM.yyyy"             :disabled-dates="datepickerState.disabled"             :value="dates.to"             v-model="date.to"             typeable

Having the same issue, it seems it only happens with certain dates. In my case any January, April, August or December date gets cleared on blur while the rest works as intended.
All the broken months besides January  are multiples of 4 so maybe it has something to do with an internal calculation?

Same problem here.
I read the code for the blur event. It uses Date.parse() to determine if the inputted value is valid.
This works well for dates formatted like MM/DD/YYYY of YYYY-MM-DD, but not for DD/MM/YYYY.
I don't see a workaround, my only option is to set :typeable="false".

pr https://github.com/charliekassel/vuejs-datepicker/pull/653 could solve this! It delegates the parsing of dates, so you can pass a parser function, the same way you can pass a formatter function

Having the same exact problem.

Having the exact same problem when using :language="nl" and :typeable="true" and format="D dd MMM yyyy" together. When removing typeable or language, it's working. I also managed to 'fix' this by changing my format to: format="MM/dd/yyyy".
Not working:
 <datepicker :language="nl"                                                 :typeable="true"                                                 format="D dd MMM yyyy"                                                 id="until"                                                 v-model="filter.until"/>
Working:
 <datepicker :language="nl"                                                 :typeable="true"                                                 format="MM/dd/yyyy"                                                 id="until"                                                 v-model="filter.until"/>                                 </div>


correct spelling mistake

Coverage remained the same at 48.563% when pulling addb095b3984bb5118a752d3b2e38c962b5dd9ef on EdwardBetts:spelling into a1cc3af1a3329b554513677cefe1e38bbc82919d on arteria:master.

@EdwardBetts Thanks


[ascon] add VARIANT field to support Ascon-128 and Ascon-128a

I've corrected the spelling and also added the corresponding typedefs

Thx @cdgori  for your review. I've changed the spelling. Regarding XOF: I haven't got any response, yet. As XOF is not supported atm, I think this is the best I can do for the moment. Imho the only other option is to combine variant and operation to something like: "Enc128a, Enc128, Dec128a, Dec128a, XOF" I'm happy to change this later, but for prototyping any decision is better than no decision.

CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_pkg.sv
CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_reg_pkg.sv
CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_reg_top.sv
These files are not relevant for the Earlgrey-PROD TO. It's fine to change them.

CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_pkg.sv
CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_reg_pkg.sv
CHANGE AUTHORIZED: hw/ip/ascon/rtl/ascon_reg_top.sv
Now that quiet period has ended, this can be merged


Add javadoc to Bullet wrapper

Thanks for a great wrapper. However, I often find myself having to look up documentation for most of the functions directly in Bullet. This often leads me to this site which has generated this from the comments, for instance from this file
Would it be possible to add these kind of comments as Javadoc to the generated Java-files for the wrapper?

For instance, this code
public class btGeneric6DofSpringConstraint extends btGeneric6DofConstraint {

could end up looking like
/**
 * Generic 6 DOF constraint that allows to set spring motors to any translational and rotational DOF
 *
 * DOF index used in enableSpring() and setStiffness() means:
 * etc...
*/
public class btGeneric6DofSpringConstraint extends btGeneric6DofConstraint {

which would make it much easier to work with.

No, swig doesn't support javadocs (yet).

Ahh, that's too bad. Keep this in mind when/if it is included. :)
The Bullet source code is not commented in a consistent manner, so not sure how easy it would be to extract all this information anyway.


Sometimes after device unlock the widget is stuck at "ToDo Agenda Loading..." view

Hi, since last update (v3.0), even recreating the widget from scratch, keeps crashing after a few hours...
Xiaomi Mi Mix 3, Android 9, Rootless Launcher

@StarCruiser75 I don't see any crash reports in Google Play yet... Could you capture crash errors / stack traces somehow, otherwise I don't know, what to fix...
See https://www.google.com/search?q=how+to+capture+android+logs&oq=How+to+capture+Android+logs on logs capture.
You need to search for errors in lines that contain "todoagenda"

Hi Yuri, thank you for your reply. To tell you the truth, I'm guessing that it is crashing, because the only thing I know is that after a few hours that I create a new cal widget, suddenly I unlock the phone and it is in the state that you can see in the pucture I uploaded. Between the creation and the "ghost mode", I have unlocked the phone many times and the widget was displayed perfectly, so I am sure that it was working, and before the v3.0 I never had a problem like this.
I can try to connect the phone in debug mode, but I do not know how to replicate the issue or when it will happen, so I doubt I'll be succesfull in this. If you have a "debug" version that writes a log on the phone, I can install it and then send you the log as soon as the problem occurs, hoping that something usefull is logged.

@StarCruiser75 Thanks for investigating. Please don't give up!
Aha, so it is not crashing but rather "doesn't load": the screenshot clearly (as I thought :-) ) tells that currently the widget "is loading" or maybe is waiting for Android system (Launcher app) to start its update.
Before v.3 release the widget didn't have the "Loading" view: it simply showed "No events" and thus confused users. But probably the cause is similar.
So we need to find out, why the widget is not loaded (or fails to load) sometimes. This means that logs may help... BTW AFAIK logs can be downloaded even if you connect to the phone AFTER seeing this problem, please try.
Honestly, I encountered this problem once also. It is cured by forcing loading by opening "ToDo Agenda" app (not a widget) using a Launcher, selecting the widget in the list (if you have more than one) and simply exiting. Please try!

Collecting links to solutions of similar problem with other Android AppWidget apps:
https://digibites.zendesk.com/hc/en-us/articles/208094229-Widget-not-loading

Just crashed on my screen. What can we search for in LogCat to look for errors?

I can reproduce this problem by simply changing font size in settings.
On the "CONFIGURATION_CHANGED" the widget is reset by Launcher, but receives no events/notifications for reloading and redrawing. Hence it stays in initial state.
I already figured out, how to catch that "android.intent.action.CONFIGURATION_CHANGED"  event, fighting now with Launcher to redraw the widget...

I hope that I fixed this problem in v.3.0.2 Beta, please check https://play.google.com/apps/testing/org.andstatus.todoagenda

Hi @yvolk, first of all, thank you for your work and for your time on this!
As soon as you posted about the new beta, I checked many times the Play Store for the update, but as of now the latest is still v3.0.1. Do you know if it is normal that it takes so long for a beta to be available?

UPDATE: v3.0.2 finally showed up in the Play Store. So far the widget seems to work, I'll let you know in the next hours as in my case it was not "crashing" immediately but after a few hours and a few unlocks.

@yvolk my widget a empty, updated, it refreshed with dates. Well done!!

@eturk1 Please try these steps:

Uninstall the "ToDo Agenda"app.
Reboot your device
Install the app again.
?!

I have exactly the same issue.
Will try the uninstall, reboot, install now and report back.

I did the following like 5 hours ago:

Force stop
Clear data/cache
Uninstalled
Rebooted phone
Installed/Configured again

And it still is working.
Lets hope it still keeps working the rest of the day.

Another attempt to improve / fix this is done in v.3.0.4, see #322

Well, v3.0.4 kind worked oke i think but v3.0.5 is making it worse again.
I Also disabled all battery optimizations for the app it self, the calendar app, the launcher etc...
No action seems to be able to fix it.
The v2.x versions worked without any issues on the same phone before.

@BlackDex Please try reinstallation steps that you mentioned before: https://github.com/plusonelabs/calendar-widget/issues/318#issuecomment-530391976

I test v.3.0.5 on three devices and an Emulator:
Android 4.3, 7, 8 and Emulator with Android 9:
No problems loading the widget found.
Emulator works slowly on my notebook, so right after boot I saw, for about a minute, the same not initialized widget that @BlackDex demonstrated on the screenshot. But after this, without my intervention, the widget was automatically initialized and showed a list of events correctly.
I also tested Android 9 behaviour after upgrade from ToDo Agenda v.2 to v.3 - it doesn't work properly after upgrade: old widgets are empty, a new widget created stays not initialized.
It took me two reboots (!) to have the new widget working properly (old widgets disappeared after the first reboot though...)

Well, i still have the issue.
I even did more this time by clearing the app/dalvik cache after uninstall. Did two reboots after that. Installed and configured again.
And it happened twice today. As right now also.
Never had these issues with v2.
So I'm wondering what has changed so significantly. No phone updates, or other apps installed, only updates.
Is there something we can do? Can you create a special debug/logcat version which logs somewhere to a file which we can send you after we noticed this?

@BlackDex First of all, thank you for taking time investigating the problem and willing to help developers. With your help we will definitely find a solution for your case, otherwise I don't know, how to reproduce the problem.
To all: please post your observations / thoughts on a way to reproduce the problem.
Q1. Two times in a day means that about once in 10 times, when you unlock your device, you see the widget not initialized ?!
Q2. What is your Device model and Android version?
Q3. What launcher do you use? If you use not a factory one, please try it.
Q4. Try to go to Android Settings -> Display -> Font size; Change the font size and press Home button on your device.
Does the ToDo Agenda widget still work?

@BlackDex 1. I could reproduce the problem by installing Nova Launcher and switching between it and default device Launcher.
2. I fixed the problem, now widget is initialized successfully in both Launchers, even after switching between them (when ToDo Agenda widgets exist in each Launcher).
Please try v.3.0.6, see #320

@yvolk, testing it now. I'm using nova indeed.
Ill keep you posted, thanks for the work.

Oke, this works quite nice.
There is just one quirk i spotted. Now only the headers shows the icon, but the calendar list is showing.

@BlackDex Do I understand correctly that you see the initial header with ToDo Agenda's icon instead of normal header with current date and buttons?!
I almost sure that this can be cured by uninstall/reboot/ install...
?!

Indeed, you understand correctly.
It only happened two times today.
But i will try the clean, uninstall, reboot, install again with this version :).

@BlackDex Anyway, I made another fix, please install v.3.0.7, see #320

Hi, I had the same problem as @BlackDex, occurring on my case each time screen was rotating, but with v.3.0.7 si fixed!
However I have a new thing I'd like to report, probably we cannot consider it an issue or problem, but more a strange behavior: with events where icons are shown, if the title is on two lines, the icon resizes to fit the two lines high, but in my opinion it is inconsistent with the other events with one line events, where icons are smaller. Probably the correct behaviors should be to have all the same size that is the one line.

@StarCruiser75 I couldn't reproduce such enlarged icons on my devices. Could you test previous version of ToDo Agenda with the same data on the same device (v.2.1, that is available e.g. on F-Droid and can be installed in parallel with this one)
I need to understand if this is a new problem, or it existed before.

I tried the comparison and the behavior is the same, maybe previously I was using a bigger font and the different hight was less evident (now I'l using the smallest).
In my opinion, anyway, icons should always remain of the same size regardless if the title is on one or two lines. This occurs in one case, that you can see in the image I attached in my previous comment in the third calendar event from the bottom, the one that has start and end time as second row.
But you are the creator, so you decide what's best. ;-)

@yvolk It is working fine since yesterday, No issues at all.
Great work.

I have not seen this issue any more today.
Seems it is fixed.
Thx.
Was this a nova compatibility issue? Or something more general?

I think this problem is caused by a failure of Android team to describe properly how a Launcher application should or should not interact with an application that provides its widgets (with Todo Agenda in this case).
This is why widgets are so fragile and work differently in different Launchers, this is why re-installs and restarts are needed...

@StarCruiser75 I hope that I fixed the problem with enlarged icons also, please try v.3.0.8 here #320

Hi @yvolk, now icons are all of the same size, big, but of the same size, at least for me that use "very small" font size. Thanks for the fix

@StarCruiser75 Could you create separate issue on this with screenshots, please.

Hello.
I'm adding my contribute after 2 years since I'm experiencing the same problem as described by the OP on my Xiaomi Redmi Note 7.
I'm using it without problems for several months, but since a couple of days it started "stucking" with the "loading" message.
I tried switching between different launchers (default launcher and Poco launcher) but the problem persists.
No updates on my side - none of which I'm aware - the problems simply started out of a blue.
Strange thing: I tested another widget (https://github.com/andstatus/todoagenda) and it has the same behaviour

@dagord ToDo Agenda widget is actually a continuation of this widget's (the "Calendar widget") work and source code.
In January 2019 the "Calendar Widget" was renamed to "Todo Agenda" and published to Google Play as the new application. More details: https://github.com/plusonelabs/calendar-widget/issues/291
I mean that maybe even today both old and new versions of the widget have something similar from Launcher's point of view, and this causes similar problems. It would be interesting to know if any other similar Open Source widget works normally on your device...

@yvolk
In the last days I tested the default calendar widget and "Calendar widget: month + agenda" (chosen at random and very similar to ToDo Agenda) and both work perfectly, at least with regard to this specific issue

@dagord Thank you for testing.
Unfortunately the "Calendar widget: month + agenda" is closed sourced.
Please try to find any Open Source "calendar widget" that works on your device. So I could compare their code with our.


Update jQuery cdn

Updated jQuery source url from code.jquery.com to cdnjs for better loading speed of websites.

@allouis @kevinansfield @peterzimon @JohnONolan @ErisDS :ping_pong:
Hope This ping represents 4-5 PRs that is pending from few days and will not ban my PR/comment regarding code of conduct.

I'm not sure what that means but we don't have any intention of changing jQuery source at the moment. We're very deliberately using the foundation's CDN.

cdnjs is better cdn then Foundation's cdn, you can use gtmetrix or pingdom to find out that.
cdnjs helps to reduce loading time of it by providing better cdn which is provided by cloudflare.


using the api to change Brightness does not work.

Describe The Bug:
using the api endpoint /api/accessories/{uniqueId} to change Brightness does not work for me. other characteristic types like On, TargetPosition or Hue and Saturation do work
To Reproduce:
PUT {"characteristicType": "Brightness", "value": "41" } does nothing
Expected behavior:
Brightness should change. like for the other working characteristic types.
how can i verify if the error is on my side or not? I'm sending data created exactly the same way to the same endpoint.

To Reproduce:
PUT {"characteristicType": "Brightness", "value": "41" } does nothing

The value should be an integer (unquoted).

i see. but why then is the behavior different


Couldn't download video

because of GFW，I can't download video by clicking the download button in this plugin.

Hi @cnBruceHong !
I know there are a few users in the same situation as you that had to manually download the videos from another non firewalled machine. We do have instructions of the files you need here : https://github.com/JohnCoates/Aerial/blob/master/Documentation/OfflineMode.md
I also have some instructions about automating the process here (you may need to change the destination cache if you are not using macOS 10.15) : https://github.com/JohnCoates/Aerial/issues/801#issuecomment-500205534
Side question, do you happen to know if Apple TV is sold in China directly by Apple ? There may be a mirror on the other side of the firewall if so, but not being there, I don't know.

Thanks!
Apple TV is not currently available in China. 😭

Thanks!
Apple TV is not currently available in China. 😭

Thanks for the confirmation. Good luck grabbing the videos!


Several 2.1.1 release specs hang on OSX

I have identified several specs that hang on MRI 2.2.3 running against the latest rubysl-socket release (71d2a458c9d1981d).
Environment:
OSX 10.10.5
MRI 2.2.3
Command:
% cd rubysl-socket
% mspec spec
These specs hang:

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/basicsocket/send_spec.rb#L112

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/socket/accept_spec.rb#L14

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/socket/accept_spec.rb#L20

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/socket/connect_spec.rb#L38

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/socket/sysaccept_spec.rb#L14

https://github.com/rubysl/rubysl-socket/blob/2.0/spec/socket/sysaccept_spec.rb#L20

Possibly related: https://github.com/rubysl/rubysl-socket/commit/ad14dbd
When introducing a sleep() or Thread.pass etc. resolves some issue, there is likely a race condition present. Just making the specs pass may give the impression of correctness (or "no obvious errors"), but that doesn't help in actual usage.

Papered over by commit ad14dbde28048bc58d22d9080b4952f7d64e4351 which introduces a short sleep. After all of the work to fix race conditions recently hard to know where to start to figure this one out. If this is a problem in practice, we can reliably reproduce this hang by removing the sleep 0.01 to find the race.


How to create a hostPath with specific uid:gid with local-volume-provisioner?

If it is not currently possible through configuration, can you please guide me in the local-volume code base such that I properly determine where I can change it to achieve chown -R uid:gid $host_path effect.

Hi can you clarify the issue you are seeing?  Is it that you're running the local-volume-provisioner as a non-root user and so it doesn't have permissions to read the discovery directories?

@msau42 no, the scenario is typical in the sense that local-volume-provisioner is actually running as root (which is typical). But as a result it create folders with root:root ownership attributes. Now, imagine you are trying to run Elasticsearch cluster that is not running as root, but as 1000:1000. It will simply be unable to right to the folder with root:root attributes.

The local volume provisioner does not create folders for use by local PVs.  It only discovers mount points that have been placed underneath the discovery directories.  So it shouldn't matter to the workload what permissions the discovery directory has, only the permissions of the mounts inside them will matter.

It actually does create folders. Tested.

Can you give an example your local PV spec and the config of your local provisioner?

PV is not created at the time when local-volume-provisioner is deployed. The point was to auto-create required directories before deploying app definitions, including PVs, etc.

Sounds interesting! That was a long path to figure this out :) Is it possible for you to give an example for hostPath volume that will create the folder if it does not exist? Last time I tested PV that points to non-existing path it complained.

Here's an example of a pod using hostpath volumes:
https://kubernetes.io/docs/concepts/storage/volumes/#example-pod-2

In addition to the required path property, user can optionally specify a type for a hostPath volume.
The supported values for field type are: DirectoryOrCreate, ...

Excellent! Thanks a lot! Will stop (mis-)using local-volume-provisioner for that.

But perhaps I was a bit too fast. Will hostPath allow to specify uid:gid for the path to be created?

No, hostpath volumes do not perform any permissions management.  You can use an init container to set the appropriate permissions as needed.

the files or directories created on the underlying hosts are only writable by root. You either need to run your process as root in a privileged Container or modify the file permissions on the host to be able to write to a hostPath volume

That is a much better option! Thanks for help, @msau42! Closing.


update troubleshooting for using PSP with User authentication

Issue #, if available:
#134
Description of changes:
EKS recently switched authentication from service account to User for VPC resource controller. This could be a breaking change. We need call this out in our doc. A PR was also created to update amazon-eks-user-guide
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Notification enum should not contain Connected

The Notification enum should not contain the variant Connected, since this can never happen once the stream created. It should not be mixed with the other MQTT stream logic, since It will only happen once, and only happen as the first thing when creating eventloop.
When creating the eventloop or stream this should be reported back in the form of a Result<Connected, ConnectionError>
Example:
let mut eventstream = eventloop(mqtt_options, rx).stream();

// this will always be the first event in a successfull connection
if let Some(Notification::Connected) = eventstream.next() {
  while let Some(notif) = evenstream.next() {
    match notif {
      Notification::Connected {
      // this can never happen again, and should thus not be part of this enum
      // and having it here kind of bloats the user logic
      },
      _ => { // all interesting events },
    }
  }
}

This is fixed but I might have to bring this back as high level client hides the eventloop


feat: correctly sort bazel module versions

Sort module versions in the official order.
See https://github.com/bazelbuild/bazel-central-registry/pull/1431#discussion_r1477936416.

The code looks good. However, I wanted to point out that a TypeScript library for bzlmod verions. Do you think it makes sense to leverage the library?

a TypeScript library for bzlmod verions

Nice, I had no idea this existing. I'll use that instead.

a TypeScript library for bzlmod verions

Nice, I had no idea this existed. I'll use that instead.

It looks like this hasn't actually been published to npm, yet. @hobofan Are there any plans to do so?