PR: Update and complete the Array class

Resolves #36
Merge message:
Re-implemented the missing first, third and inter-quartile methods of the Array object, so that the main repository's tests succeed when using this library.

This work should be moved to #30


Feature request: Skip babel transpilation

Tell us how you think we can improve Sandpack
To give some context, I have additional library files in a public folder that is meant to be statically served. Currently, I am passing it to the Sandpack component via the files prop. However, these files have already been transpiled and passing them through the files prop seems to make the babel transpiler do it again. You would think that running it through would not have much impact but it turns out it just generates errors.
Packages affected

[ ] sandpack-client
[x] sandpack-react

What is this feature?
I am proposing that a flag be added to the SandpackFile type to skip babel transpilation.
How would your idea work?
<Sandpack
  files={{
    '/public/jquery.min.js': {
      code: '/public/jquery.min.js',
      transpile: false,  // Default: true
    }
  }}
/>

@danilowoz this is definitely doable. However this code would still be passed through our custom transformer that collects dependencies and rewrites import statements  which uses acorn and it super-fast.
Or maybe it should be more of a isolated module that can never have any dependencies?
Sounds very similar to https://github.com/codesandbox/sandpack/issues/119 which we already support in the bundler

Or should it be more of an isolated module that can never have any dependencies?

I think there's a chance that may be the case. Perhaps there should be another flag for skipping that as well?

Yeah probably, for your example you can probably use externalResources for now, but we've added this feature request to the backlog and will get to it once we've reworked the bundler to support this.

@danilowoz  Is this issue still open?

Yeah, this's a valid issue. However, it's not a priority now.
Please thumbs up the main comment for those who are interested in this feature.

+1 for skipping babel transpilation.


core: convert trigger.Type to byte when pushing on stack

trigger.Type is not present in makeStackItem.

Caused by #690, more specifically 7d46404e2db9aa0a836bf9f55a18cb29e9252b7c.


[BUG] last_reset move into set_state, too

Describe the bug
I missed to expand the set_state in sensor for set last_reset if set Total
SOrry for this

@unixorn i have to set the last_reset in set_state or ?
how will it send via mqtt ? maybe i missed more to add
https://developers.home-assistant.io/docs/core/entity/sensor/#state-class-sensorstateclasstotal

@unixorn  sorry bro I made a mistake, how can I test it in front of ?
 File "/usr/local/lib/python3.12/site-packages/ha_mqtt_discoverable/sensors.py", line 337, in set_state     self._state_helper(str(state), last_reset=last_reset)   File "/usr/local/lib/python3.12/site-packages/ha_mqtt_discoverable/__init__.py", line 749, in _state_helper     message_info = self.mqtt_client.publish(topic, state, retain=retain)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.12/site-packages/paho/mqtt/client.py", line 1247, in publish     raise TypeError( TypeError: payload must be a string, bytearray, int, float or None. Exception in thread Thread-62 (historical_data_task): Traceback (most recent call last):   File "/usr/local/lib/python3.12/threading.py", line 1073, in _bootstrap_inner     self.run()   File "/usr/local/lib/python3.12/threading.py", line 1010, in run     self._target(*self._args, **self._kwargs)   File "/build/GridboxConnector/__main__.py", line 59, in historical_data_task     ha_viessmann_historical_device.update_sensors(total, midnight_today.isoformat())   File "/build/GridboxConnector/ha_viessmann_gridbox_connector.py", line 106, in update_sensors     self.production_sensor.set_state(measurement.get("production", ""), last_reset=last_reset)   File "/usr/local/lib/python3.12/site-packages/ha_mqtt_discoverable/sensors.py", line 337, in set_state     self._state_helper(str(state), last_reset=last_reset)   File "/usr/local/lib/python3.12/site-packages/ha_mqtt_discoverable/__init__.py", line 749, in _state_helper     message_info = self.mqtt_client.publish(topic, state, retain=retain)

I will push after Christmas an bug fix :( I am so sorry.

#294 @unixorn pushed fix with added unit test now it should working


Added basic X11 bar support

Can add a bar to Way Cooler now :tada:

Fixes #217
Confirms to work with lemonbar.

Added new config option config.bar.

To actually spawn the bar, as with all things in way cooler thus far, you need to add it to the init method.

Automatically tiles everything properly, making sure the bar is always on top and present in all workspaces.
Only supports "top" bars right now. We need to figure out the API to indicate that it is not on top

Could do something implicit, where we guess based on what geometry it wants to be at (flooring it to the nearest edge as appropriate)

Could break more complicated bar setups, such as with xfce4-panel (which probably does not work for other reasons though)

Could a "top", "bottom", etc. flag to the bar configuration setup.

Coverage decreased (-0.4%) to 57.35% when pulling 12d10f03c90e8cc6068accb4c89390104e5d07a8 on x11-bar-support into 2130d4677947c5bedfe2d021b6da364bc494630b on master.

Coverage decreased (-0.4%) to 57.121% when pulling 6dceec66765bc8da98118d97b85529cfa92e1a95 on x11-bar-support into f93d4e58d94597147d7ac6e0bc9504b0a13a8c8f on master.

Coverage decreased (-0.4%) to 57.032% when pulling 6822ca853825fac051002c312af58502a5555765 on x11-bar-support into a4dd3269ce2fadc4d2b5f0238e33953022190c01 on master.


support W4A8 Marlin kernel

Summary
We inroduce a mixed precision GEMM kernel for INT4-Weight and INT8-Activation. We implemented the W4A8 GEMM based on Marlin GEMM. The kernel is designed to support our W4A8 quantization method QQQ. For more details on the kernel implementation, you can refer to our paper. The kernel demonstrates excellent performance and has been merged into the official vLLM project (see https://github.com/vllm-project/vllm/pull/5218).
We hope the w4a8 GEMM can also provide a practical speedup for other W4A8 quantization methods in the community.
Additionally, since torchao is widely used in frameworks like SGLang, we can extend support for W4A8 once the kernel is integrated into torchao.
Performance
Here is the speedup over PyTorch FP16 GEMM (Calling CUTLASS) of all GEMMs under different numbers of input tokens. The weight matrix size is (N=8192, K=21760). You can reproduce the benchmark results using bench_w4a8.py in my repo.

can we do some comparisons between this and https://github.com/pytorch/ao/pull/880?

thanks, looks pretty good, can you add the benchmark code in https://github.com/pytorch/ao/tree/main/benchmarks as well

@drisspg @jerryzh168 I am working on the benckmark and I will give the comparisons with https://github.com/pytorch/ao/pull/880. The kernel is benchmarked on A100-80G GPU and it can work on SM > 8.0.

@jerryzh168 @drisspg @msaroufim
I have made the following modifications (code modifications refer to https://github.com/pytorch/ao/pull/621 and https://github.com/pytorch/ao/pull/880):

Added benchmark code for marlin_qqq_w4a8 GEMM inbenchmarks/benchmark_marlin_qqq.py
Summarized the main differences between marlin_qqq_w4a8 GEMM and marlin_w4a16 GEMM intorchao/quantization/marlin_qqq/README.md
Supported marlin_qqq in torchao/quantization/quant_api.py
Added some unit tests in test/quantization/test_marlin_qqq.py

w4a8-cutlass is a great work.  In comparison, we believe marlin_qqq_w4a8 can support weight per-group quantization in addition to weight per-channel quantization. However, marlin_qqq does have some limitations: it only supports symmetric quantization and the output dtype can only be torch.float16.
In addition, we also provide the performance of torchao/_models/llama/generate.py here. -g128 means  weight per-group quantization and the group size is 128.

-q parameter
Precison
Average tokens/sec
Average Bandwidth in GB/s
Peak Memory Usage in GB
Model Size in GB

--compile
fp16
112.45
1486.00
13.93
13.21

-q marlin_qqq --compile
w4a8
197.45
653.50
4.79
3.31

-q marlin_qqq --compile
w4a8-g128
187.62
640.32
4.82
3.41

@jerryzh168 @msaroufim @drisspg I have resolved the conficts. Look forward to see your new advice.

Hey @HandH1998  rekicking off the internal CI/CD here that failed
Overall this works looks very good, will do a more thorough review

It seems that you also applied formatting to a lot of files. This makes it pretty hard to review since all the changes get mixed together.
I opened https://github.com/pytorch/ao/pull/1226
Would you mind opening a separate PR for some of the other files you touched? And let's first add the formatting and then we can merge in your changes and make it easier to review.

@drisspg I have removed the extra formatting in this PR, which should now simplify the review process.

I've added a benchmarking script to #880, that makes it possible to compare the performance between the two W4A8 kernels.  As CUTLASS-based version doesn't support group quantization, at the moment it is only possible to make the comparison with group_size=-1 in the Marlin-based version.  Marlin-based version performs clearly better for input sizes less than 256, while CUTLASS-based version is faster for input sizes of 256 and higher.  Consequently, Marlin-based version performs better on Llama generator too, with tokens/sec about 25% higher than CUTLASS-based version (note that in both cases I ran the generator as follows python generate.py --compile --precision torch.float16 -q ...).  Please note that the comparison is not completely apples-to-apples, as besides group quantization support there are other small differences between kernels, but still it seems this is pretty much current state of affairs regarding the performance.
Let me return the compliment by stating that this Marlin-based kernel is a great work too.  In particular, for me it clearly shows where the CUTLASS-based kernel should be improved.

Overall looking really good, would you mind reporting lib size increase from this PR? I plan to take another once over of the cuda code tomorrow and then once CI is good this should be good to go :)

@drisspg @jerryzh168 Thanks for your reviews. I have fixed the most issues according to your advice. The increased lib size is about 5M. Let's go forward :)

Lib increases from 3.5M -> 5.0M for provenance, I think this is acceptable

@HandH1998  looks like there is 1 true failure on your PR would you mind fixing and then we can land?

@HandH1998 looks like there is 1 true failure on your PR would you mind fixing and then we can land?

I will try to fix it soon.

can you add a table similar to https://github.com/pytorch/ao/tree/main/torchao/quantization#sparse-marlin to README to show the performance? otherwise looks good to me

I have added it.

please fix lint: https://github.com/pytorch/ao/actions/runs/11812082822/job/32933511633?pr=1113

@HandH1998 It's so coooooool!


test-branch/execute-job/quoted-authorization/657b64de-e08e-4cfb-ad9e-763c9e3a3ddc

PR for testing b8b48e930b4a44b9c3107143ff8697cdf30326d8

/canonical/self-hosted-runners/run-workflows b8b48e930b4a44b9c3107143ff8697cdf30326d8


Changed the linux version of battery.rs

To read the stats from acpi command.
Instead of /sys/class/power_supply/BAT0
Fixes #21

Depending on awk slows down the program significantly.
I'll add a fallback path that Macchina will fetch battery information from, without having to use any commands.

commit https://github.com/grtcdr/macchina/commits/main solves this issue, so I'll close the PR, thanks for reporting it!


Changed island event

Fire an event whenever the current player changed island.
This is mostly useful for multiplayer games, where we want to keep each island linked to a room in a websockets server.

posix: https://github.com/decentraland/posix/pull/7
kernel: https://github.com/decentraland/kernel/pull/112
sdk: https://github.com/decentraland/js-sdk-toolchain/pull/50


Restructure: Only provide the dotnet-aspnet dependency

Background
This buildpack currently provides the dotnet-aspnetcore dependency, which

Provides a library of shared dll files needed for aspnet core apps

It always requires itself on launch, and the dotnet-runtime dependency on both build and launch. This is unnecessary because we might need these dll libraries during build if we want to build our app with dotnet publish, or only during launch if we want to run with app with dotnet run.
Proposal
In order to conform the the restructure rfc, this buildpack should provide the dotnet-aspnetcore dependency and require nothing. This will greatly simplify its interaction with other buildpacks in the language family.
The builldpack should Install a specified version of the dotnet-aspnetcore libraries into the correct location.
The buildpack should also be rewritten in a packit compliant way.

Some quick notes:

detect should always provide dotnet-aspnetcore and require it if there is an entry in buildpack.yml.
The current logic in build should be simplified to mimic that of our other provision buildpacks. We should priority sort, find a compatible version (if one exists), and install that version. Leave the failure to dotnet-publish or when the container is run.

Priority Order:

buildpack.yml
*.*sproj

Acceptance steps:
We need to see that

the dotnet-aspnet layer is added to the layer directory
/workspace/.dotnet_root links to the layers dir

When not requiring a version in buildpack.yml
Not specifying a version
$ cd acceptance
$ cat plan.toml

[[requires]]
  name = "dotnet-aspnetcore"

  [requires.metadata]
    launch = true

$ pack build my-app -b /tmp/aspenet.cnb -b gcr.io/paketo-community/build-plan

< ssh onto the container >

$ ls /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App
5.0.1

$ ls /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App/5.0.1
Microsoft.AspNetCore.Antiforgery.dll                  Microsoft.AspNetCore.Mvc.Core.dll                            Microsoft.Extensions.Configuration.Xml.dll
..................

$ ls -l /workspace/.dotnet_root/shared/

lrwxrwxrwx 1 cnb cnb 95 Jan  1  1980 Microsoft.AspNetCore.App -> /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App

When a version is specified
cd acceptance-yml
$ cat plan.toml

[[requires]]
  name = "dotnet-aspnetcore"

  [requires.metadata]
    launch = true

$ cat buildpack.yml

---
dotnet-framework:
  version: "3.1.9"

$ pack build my-app-yml -b /tmp/aspenet.cnb -b gcr.io/paketo-community/build-plan

< ssh onto the container >

$ ls /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App/
3.1.9

$ ls /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App/3.1.9
Microsoft.AspNetCore.Antiforgery.dll                  Microsoft.AspNetCore.Mvc.Core.dll                            Microsoft.Extensions.Configuration.Xml.dll
.........................................

$ /workspace/.dotnet_root/shared/Microsoft.AspNetCore.App
lrwxrwxrwx 1 cnb cnb 95 Jan  1  1980 Microsoft.AspNetCore.App -> /layers/paketo-buildpacks_dotnet-core-aspnet/dotnet-core-aspnet/shared/Microsoft.AspNetCore.App

When specifying the version with RUNTIME_VERSION
It should use the RUNTIME_VERSION at a higher priority than the version specified in the buildpack.yml
$ cd acceptance-yml

$ pack build my-app-env -b /tmp/aspenet.cnb -b gcr.io/paketo-community/build-plan --env 'RUNTIME_VERSION=3.1.10'
...
[builder] Paketo ASP.Net Core Buildpack 1.2.3
[builder]   Resolving Dotnet Core ASPNet version
[builder]     Candidate version sources (in priority order):
[builder]       RUNTIME_VERSION -> "3.1.10"
[builder]       buildpack.yml   -> "3.1.9"
[builder]       <unknown>       -> "*"
[builder]
[builder]     Selected dotnet-aspnetcore version (using RUNTIME_VERSION): 3.1.10
[builder]
[builder]   Executing build process
[builder]     Installing Dotnet Core ASPNet 3.1.10
[builder]       Completed in 1.274s
[builder]
[builder]   Configuring environment
[builder]     DOTNET_ROOT -> "/workspace/.dotnet_root"
[builder]
...
Successfully built image my-app-env

I am accepting this because in all cases we can see that the correct version of the dotnet-aspnet libraries are places in the correct place, and are correctly symlinked.


Spam find next and find previous in iFrame search leads to no selection

Testing #127173

Search a word
Spam find next / find previous
🐛 You will get to a point where both buttons are disabled and nothing is highlighted.

Duplicate of #127458.


Range Exception for AudioVolumeIndication

Describe the bug
I get an exception for RangeError in the AudioVolumeIndication callback inside the agora SDK in events.dart because the List only has 2 things according to the docs (aka range 0-1) but in the SDK they look for List Element[2] which is the 3rd element.
To Reproduce
Steps to reproduce the behavior:

Running an app with Audio Indication enabled

Expected behavior
No exceptions should happen
Screenshots

Desktop (please complete the following information):

Android and iOS

Smartphone (please complete the following information):

Android Emulator and iOS15 iPhone 11 pro

Additional context
It is commented out in one of the branches within the repo, I wonder if that's related. https://github.com/AgoraIO/Agora-Flutter-SDK/blob/dev/flutter2-iris/lib/src/events.dart#L1314

which version of SDK you used?

@LichKing-2234  I am facing same issue when running for android, for web it working fine.
I am using
agora_rtc_engine:
git:
url: https://github.com/AgoraIO/Agora-Flutter-SDK.git
ref: dev/flutter2
What can be the reason? Do I need to add anything else, I have added     await _engine.enableAudioVolumeIndication(200, 3, true);
Please help its urgent.

which version of SDK you used?

This was on version 4.0.6. And that was the odd thing, is that I don't think this version supports flutter web, but there is a platform check for Web

if you just want android or ios, you should use the latest version on pub.dev

@LichKing-2234  Actually I wanted for android/ios and web as well. Can you please let me know which version is suitable as I have checked a lot there are only alpha versions which supports web but not working properly for web.
Thanks

I think it's worth trying agora_rtc_engine: 6.0.0.


Improve dex operator credential management

At the moment, dex operator is configured via a secret in the config repository
although there is a script to create new credentials, creation and rotation of secrets is manual and reduces the benefit we get from the automation for oauth apps.
let's find an approach that is secure and reduces toil
from call with clippy: maybe workload identity can be interesting https://azure.github.io/azure-workload-identity/docs/

Team clippy is planning on making azure identity webhook an installable app: https://github.com/giantswarm/giantswarm/issues/25041

https://github.com/giantswarm/giantswarm/issues/24578
we may be able to use this app in the meantime


Material Gallery crash in HeroController

Steps to Reproduce
I was looking at the list of Components in the Material Gallery. I  thought that I accidentally dragged a finger on the screen and it crashed, but I can't reproduce it.
Flutter Doctor
[✓] Flutter (on Linux, channel master)
    • Flutter at /media/jimbe/mojossd/sysui/src/third_party/flutter
    • Framework revision 60755f6d9c (3 days ago), engine revision 28fbcc3a38

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.2)
    • Android SDK at /usr/local/google/home/jimbe/Android/Sdk
    • Platform android-23, build-tools 23.0.2
    • OpenJDK Runtime Environment (build 1.8.0-google-v7-119990345-117822431)

[✓] Atom - a lightweight development environment for Flutter
    • Atom installed; Flutter plugin version 0.2.2

Logs and Crash Reports
Please attach any relevent logs or crash reports.
I/flutter (13489): ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (13489): The following assertion was thrown during a scheduler callback:
I/flutter (13489): 'package:flutter/src/widgets/heroes.dart': Failed assertion: line 481: '_from != null' is not true.
I/flutter (13489): Either the assertion indicates an error in the framework itself, or we should provide substantially
I/flutter (13489): more information in this error message to help you determine and fix the underlying cause.
I/flutter (13489): In either case, please report this assertion by filing a bug on GitHub:
I/flutter (13489):   https://github.com/flutter/flutter/issues/new
I/flutter (13489): When the exception was thrown, this was the stack:
I/flutter (13489): #0      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:27)
I/flutter (13489): #1      HeroController._getMostValuableKeys (package:flutter/src/widgets/heroes.dart:481)
I/flutter (13489): #2      HeroController._updateQuest (package:flutter/src/widgets/heroes.dart:492)
I/flutter (13489): #3      BindingBase&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:393)
I/flutter (13489): #4      BindingBase&SchedulerBinding.handleBeginFrame (package:flutter/src/scheduler/binding.dart:362)
I/flutter (13489): #5      _beginFrame (file:///b/build/slave/Linux_Engine/build/src/out/android_Release/gen/sky/bindings/hooks.dart:48)
I/flutter (13489): ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This code path doesn't exist anymore, see https://github.com/flutter/flutter/pull/8112


Godot 4.3

This PR adds Godot 4.3 as an engine to be used by the Road to Vostok Demo.
There isn't enough documentation for me to figure out how to run the built package so I wasn't able to test the game.
I also don't know what's the process for adding a new version of the engine, so I can make changes if needed.
New Engine Package Submissions

[x] Have you followed the instructions in the build documentation?
[ ] Have you run the build locally and ensured the package allowed you to launch and play the Steam game?
[x] Have you updated the packages.json file?
[x] Have you ensured that there is not already a pull request or active engine package for the one you are adding?

The Cruelty Squad downloads the editor binary, which will reduce the performance and will run editor specific code. There's no official way to get a specific export template binary instead, they're all in a 1GB zip, so the binary would have to be uploaded somewhere and using the godot package will needlessly download the 3.4 version of the editor

The Cruelty Squad downloads the editor binary, which will reduce the performance and will run editor specific code. There's no official way to get a specific export template binary instead, they're all in a 1GB zip, so the binary would have to be uploaded somewhere and using the godot package will needlessly download the 3.4 version of the editor

AH I see now, I forgot that the godot engine actually builds godot.
So what you are doing makes sense then. You'l want to have a godot 4-3 asset script for running this particular game, since your script is excepting certain pcks.
For seeing if this builds, edit the engine godot file which will then trigger the build to complete and it'll upload an artifact. Then you can use that for your local testing.

Thanks for the great work so far here. I've done a minor change and then I'm going to merge this. Did a quick test and it loads the game well. Thanks for the idea.


gulp watch loop

After implementing gulp-htmlmin, gulp watch goes into an endless loop for me.
I'm on Laravel (elixir sits on top of gulp).
elixir.extend('compress', function() {
    new elixir.Task('compress', function() {
        return gulp.src('./storage/framework/views/*')
            .pipe(htmlmin({
                collapseWhitespace          : true,
                collapseInlineTagWhitespace : true,
                removeAttributeQuotes       : true,
                removeComments              : true,
                minifyJS                    : true,
                minifyCSS                   : true,
            }))
            .pipe(gulp.dest('./storage/framework/views/'));
    })
    .watch('./storage/framework/views/*');
});

Try some other HTML processor plugins inside watch task. If you can reproduce infinite loop even when you use other plugins, this is an issue with elixir.Task#watch.
If you cannot reproduce infinite loop with other plugins, pinpoint the HTML file that causes neverending process and open a new issue on https://github.com/kangax/html-minifier/issues with full content of the HTML file.

@rzb also it looks like your src and dest paths are the same. Since gulp-htmlmin changes the files, watch will trigger.


MAZE GAME

A classic maze game move from one side to another.
Fixes #271

@TusharAMD o/p video is provided u can check. i have not completed the solving but have demonstrated how the maze will be played, in a similar fashion


Add memset_s-like clearing mechanism and/or other secret data protection

See:

https://github.com/stouset/secrets/
https://github.com/seb-m/tars
https://github.com/briansmith/ring/issues/14
https://github.com/briansmith/ring/commit/b76f52c03a667c2ac6793ff566b55ad060421759 and the things it links to.

One of the major goals of ring is for it to be proven that it is immune from any kind of memory safety issue, including in particular memory safety issues that would leak key material like Heartbleed. However, We also want people to use ring-ffo to embed ring, in particular into not-so-safe languages and runtimes, and so ring-ffi should provide some protections similar to what OPENSSL_cleanse, TARS, and @stouset's secrets crate provide. It's unclear how to go about that as of yet. To be 100% effective, Rust language improvements may be necessary.

For additional ideas, see
https://github.com/stouset/secrets/blob/stack-secrets/src/buffer.rs

for my current approach to stack-based secrets. We can use a trick of Rust’s borrow checker to ensure a struct encapsulating keys is never moved (and thus, assuming the compiler is reasonable, never copied). On top of that, stack secrets are encrypted in-place while they are unused. Some of this is a bit overkill, but I’m playing with these ideas to get a feel for them.
Unfortunately with the non-movable type, one problem is that you eventually need to provide callers with a reference to the internal data. If that data implements Copy (as [u8; _] et al do), the containing struct being immovable doesn’t matter - rustc won’t see assignment as a move, so the borrow checker won’t complain, and the internal data will be copied. This can be fixed by newtype’ing secret key types, but I’m not thrilled with that solution.


New release

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/85912
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" d6bd4d7ec1f488e0f42e476855aa7a2109535724
git push origin v0.4.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/85912
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" 0736cb99265c2e530dc4153b54e5b5b67c28cf10
git push origin v0.4.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/90761
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.0 -m "<description of version>" 970e2b229ae094df09f33e7c25b333b55a958375
git push origin v0.5.0


Remove repo specific CoC file.

This removes the repository specific CODE_OF_CONDUCT.md file in favor of the newly added version maintained as the organization's default within the WordPress/.github repository.
While this file will not be included in git clones, it will be displayed on the repository's main page and anywhere else GitHub includes a Code of Conduct link.
This change enables more consistent messaging for the community code of conduct, which is adapted from the same Contributor Covenant currently used for the CoC file being removed. It also allows the file to be updated in one location for all repositories under the WordPress organization.
See https://github.com/WordPress/.github/pull/1.

@desrosj In principle agreed, but the file as per https://github.com/WordPress/.github/pull/1 is a very abbreviated version of the CoC, which I don't think conveys the right message.
Either that file should include the complete CoC as per https://make.wordpress.org/handbook/community-code-of-conduct/ or it should just be a simple paragraph pointing to the handbook page containing the CoC.
Anything in between will lead to confusion and can cause problems with enforcement.
I also wonder if the CoC should include some empowerment for repo managers/maintainers regarding behaviour in a specific repo ? At times swift action can be needed and while a diligent investigation via the IRT is always a good thing, harm can be experienced in the mean time when such a process is long and time-consuming.

Thanks @jrfnl!
The goal with https://github.com/WordPress/.github/pull/1 was to create a brief file and link out to the full CoC page in the handbook, which it does after the first paragraph.
I'm going to defer these questions to @angelasjin, though. While I worked with her on the abbreviated file and I'm helping her by creating these PRs to show the default file in all the organization's repositories, those are things that she'll need to weigh in on.

Hello! Thanks for sharing your thoughts, @jrfnl, and for tagging me in, @desrosj.
The CoC does include an Enforcement Responsibilities section, which states the following:
Community leaders (such as team reps, component maintainers, organizers, and project leads)  are responsible for clarifying and enforcing our standards of acceptable behavior; they will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, documentation edits, issues, videos, presentations, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Does this cover what you were hoping to see? If you would like to see edits, I recommend that we make them to the version in the Contributor Handbook as that is our primary source. To suggest edits, you can email<EMAIL_ADDRESS>

Hey @jrfnl! It sounds like I might have misunderstood your concern then. Let me double check my understanding before I try to give you another response?
It seemed like you were looking for repo managers/maintainers to be able to take some faster actions when you see inappropriate behaviors in repos, and hoped to see the CoC include language to that effect, is that correct? Are the additional concerns?

Hey @jrfnl! It sounds like I might have misunderstood your concern then. Let me double check my understanding before I try to give you another response?
It seemed like you were looking for repo managers/maintainers to be able to take some faster actions when you see inappropriate behaviors in repos, and hoped to see the CoC include language to that effect, is that correct? Are the additional concerns?

See: https://github.com/WordPress/WordPress-Coding-Standards/pull/2423#issuecomment-1947647225

Are you referring to the part about the CoC being abbreviated? As Jon noted, and I agree, the goal was to create a brief file and link to the full CoC page in the handbook, which it does twice. I personally feel like this works and sends the right message, but perhaps we disagree.

@GaryJones @dingo-d Shall we close this PR ? I don't think an abbreviated CoC with a reference to someone's personal site for the full version is a good idea.

Yes, let's close it for now.


Seastar Evaluation

Evaluation of Seastar framework.

Because sharing of information across cores requires costly locking, it't not a preferrable choice in our case:

Seastar utilizes the following concepts to achieve extreme performance:
Shared nothing design: Seastar runs one application thread per core, and depends on explicit message passing, not shared memory between threads. This design avoids slow, unscalable lock primitives and cache bounces. Any sharing of resources across cores must be handled explicitly. For example, when two requests are part of the same session, and two CPUs each get a request that depends on the same session state, one CPU must explicitly forward the request to the other. Either CPU may handle either response. Seastar provides facilities that limit the need for cross-core communication, but when communication is inevitable, it provides high performance non-blocking communication primitives to ensure performance is not degraded.

A simple Seastar program looks like this:
#include "core/app-template.hh"
#include "core/reactor.hh"
#include <iostream>

using namespace seastar;

int main(int argc, char** argv) {
    app_template app;
    app.run(argc, argv, [] {
            std::cout << "Hello world\n";
            return make_ready_future<>();
    });
}

This object starts the main event loop (the Seastar engine) on one or more CPUs, and then runs the given function - in this case an unnamed function, a lambda - once.
When the future returned by it resolves the app will shut down, stopping event loops on all cpus, and app.run() will return.
Seastar Threads:
Seastar-based programs run a single thread on each CPUa, and each of these threads runs its own event loop, known as the engine in Seastar. By default, the Seastar application will take over all the available cores, starting one thread per core. We can see this with the following program. The smp::count printed is the number of started threads:
#include "core/app-template.hh"
#include "core/reactor.hh"
#include <iostream>

int main(int argc, char** argv) {
    app_template app;
    app.run(argc, argv, [] {
            std::cout << smp::count << "\n";
            return make_ready_future<>();
    });
}

On a machine with 4 hardware threads (two cores, and hyperthreading enabled), Seastar will by default start 4 engine threads, meaning that smp::count will be 4.
Seastar memory:
Seastar applications shard their memory. Each thread is preallocated with a large piece of memory (on the same NUMA node it is running on), and uses only that memory for its allocations (such as malloc() or new).
By default, the machine's entire memory except a small reservation left for the OS (defaulting to 512 MB) is pre-allocated for the application in this manner. This default can be changed by either changing the amount reserved for the OS (not used by Seastar) with the --reserve-memory option, or by explicitly giving the amount of memory given to the Seastar application, with the -m option. This amount of memory can be in bytes, or using the units "k", "M", "G" or "T". These units use the power-of-two values: "M" is a mebibyte, 2^20 (=1,048,576) bytes, not a megabyte (10^6 or 1,000,000 bytes).
Futures and continuations in detail:
As mentioned before, a future is a result of a computation that may not be available yet, such as :

a data buffer that we are reading from the network
the expiration of a timer
the completion of a disk write
the result of a computation that requires the values from one or more other futures.

The type future<int> variable holds an int that will eventually be available - at this point might already be available, or might not be available yet. The method available() tests if a value is already available, and the method get() gets the value. The type future<> indicates something which will eventually complete, but not return any value.
A future is usually returned by a promise, also known as an asynchronous function, a function or object which returns a future and arranges for this future to be eventually resolved. One simple example is Seastar's function sleep():
future<> sleep(std::chrono::duration<Rep, Period> dur);
This function arranges a timer so that the returned future becomes available (without an associated value) when the given time duration elapses.

Links to similar building failures:
https://github.com/scylladb/seastar/issues/52
https://github.com/scylladb/seastar/issues/338
https://github.com/scylladb/seastar/issues/160
https://github.com/scylladb/seastar/issues/52
https://github.com/scylladb/seastar/issues/276
https://github.com/scylladb/seastar/issues/266
https://github.com/scylladb/seastar/issues/207
Note that these are the links to the problems that are similar to ours. There are issues pointing to other error messages that I've encountered and solved, and the ones that i haven't yet met.
Also, there are other sorts of building failures on other platforms such as docker, CentOS.
Such as :
https://github.com/scylladb/seastar/issues/436
https://github.com/scylladb/seastar/issues/252

I'm sorry to hear of the difficulties you've experienced with Seastar.
It is precisely because of these issues with the current build system and Seastar's approach to dependencies that we are close to switching to CMake and ensuring that a consumer of Seastar can compile it independent of how external dependencies are supplied. Patches for this are on the mailing list, and I encourage you to try them and report issues to expedite this process.

Thanks for the information and we really appreciate it :)


fix(build): builds are now es5 compliant

As documented in #175, hapijs/isemail is not ES5 compliant.
I forked isemail to jaebradley/isemail and published an ES5 compliant package at isemail-es5.
I then updated email-prop-type to 1.1.4 which uses isemail-es5 instead of isemail.
static/index.js and themable/index.js now seem to be ES5 compliant.

This blocks #177.

Coverage remained the same at 99.579% when pulling c2f615bbe9b2a32a1733bbcadf5e573490ab4621 on upgrade-email-prop-type into 3f31fa844fa28d936f6091400828f2a5bc2cf97c on master.

Coverage remained the same at 99.579% when pulling c2f615bbe9b2a32a1733bbcadf5e573490ab4621 on upgrade-email-prop-type into 3f31fa844fa28d936f6091400828f2a5bc2cf97c on master.


Add documentation for a use case: "How To Pass a Physical NIC Into a Kata Container"

As discussed in issue #1876.
And in this comment by @amshinde
Note: The document is incomplete

@Yuval-Ai  thanks for the PR, we appreciate it and don't worry if you can't complete the document (https://github.com/kata-containers/runtime/issues/1876#issuecomment-603105747) we can work on it later

Hi @Yuval-Ai - just checking, presume you will get back to this sometime?

Hi! Yes :)
Hopefully soon.

Hi @Yuval-Ai Thanks for the PR. Can you squash all your commits into a single commit. Will make it easier to review as well.

Hi @amshinde, squashed my commits. Can you please take a look and tell me if it's fine?
Thanks.

Hi @grahamwhaley, @amshinde.
Hope everybody’s fine these days.
I changed things as discussed, and squashed my commits. When you’ll have the time, please update me what to do next.
Wishing you the best of health,
Y

Hi @Yuval-Ai - thanks for updating! github is reporting that the README.md file is 'conflicted', which means it has changed since you made your changes - you will need to rebase your changes on top of the master again and re-push. That'll be the next step :-)

This seems like a worthwhile PR - I'm wondering if it'd be helpful if we applied a commit to the submitters branch in order to address any fixes that are needed, to help get this into merge-able shape.
@amshinde  WDYT?  Is it accurate at this point, and just needs editorial adjustments?

Folks, this PR has been stale and I'm closing it as we're walking towards the final 1.13.0 release of the kata-containers-1.x.
From now on, all the development will happen as part of https://github.com/kata-containers/kata-containers/ and fixes should be provided to that repo.
Thanks a lot for your contribution, we're sorry that for some reason it got stale, and we hope to see you around for new adventures in the kata-containers-2.x land.


How do I post a carousel?

This feature is currently not available, we will add it asap. Thanks

Would be nice to have this feature


How can multiple subscribers on a topic only consume once

Before asking, please check if your question has already been answered:

Check the documentation - https://micro.mu/docs/
Check the examples and plugins - https://github.com/micro/examples & https://github.com/micro/go-plugins
Search existing issues

Did you set SubscribeOptions's option "Queue"? If so, try unset it.
type SubscribeOptions struct {
	// AutoAck defaults to true. When a handler returns
	// with a nil error the message is acked.
	AutoAck bool
	// Subscribers with the same queue name
	// will create a shared subscription where each
	// receives a subset of messages.
	Queue string

	// Other options for implementations of the interface
	// can be stored in a context
	Context context.Context
}

http broker will set version as broadcastVersion if SubscribeOptions's Queue was set.
// check for queue group or broadcast queue
version := options.Queue
if len(version) == 0 {
    version = broadcastVersion
}

broker will broadcast message to all subscriber if version was set as broadcastVersion.
        switch service.Version {
	// broadcast version means broadcast to all nodes
	case broadcastVersion:
		var success bool

		// publish to all nodes
		for _, node := range nodes {
			// publish async
			if err := pub(node, topic, b); err == nil {
				success = true
			}
		}

		// save if it failed to publish at least once
		if !success {
			h.saveMessage(topic, b)
		}
	default:
		// select node to publish to
		node := nodes[rand.Int()%len(nodes)]

		// publish async to one node
		if err := pub(node, topic, b); err != nil {
			// if failed save it
			h.saveMessage(topic, b)
		}
	}

Did you set SubscribeOptions's option "Queue"? If so, try unset it.
type SubscribeOptions struct {
	// AutoAck defaults to true. When a handler returns
	// with a nil error the message is acked.
	AutoAck bool
	// Subscribers with the same queue name
	// will create a shared subscription where each
	// receives a subset of messages.
	Queue string

	// Other options for implementations of the interface
	// can be stored in a context
	Context context.Context
}

http broker will set version as broadcastVersion if SubscribeOptions's Queue was set.
// check for queue group or broadcast queue
version := options.Queue
if len(version) == 0 {
    version = broadcastVersion
}

broker will broadcast message to all subscriber if version was set as broadcastVersion.
        switch service.Version {
	// broadcast version means broadcast to all nodes
	case broadcastVersion:
		var success bool

		// publish to all nodes
		for _, node := range nodes {
			// publish async
			if err := pub(node, topic, b); err == nil {
				success = true
			}
		}

		// save if it failed to publish at least once
		if !success {
			h.saveMessage(topic, b)
		}
	default:
		// select node to publish to
		node := nodes[rand.Int()%len(nodes)]

		// publish async to one node
		if err := pub(node, topic, b); err != nil {
			// if failed save it
			h.saveMessage(topic, b)
		}
	}

ok，thanks

1

1


Removing 'optional' keyword as it is implied by proto3.

@sougou @enisoc
Will need to import this ASAP too.

LGTM


Refine post playlist

What's this PR do?
Update hover states on list for top songs. Add new feature for adding top songs of this year to your spotify profile. Clean up the UI for said feature.
Pre-Merge TODOs
still need to get testing going for top songs component :/
Learning
You need to stringify your POST body
https://googlechrome.github.io/samples/fetch-api/fetch-post.html
https://developer.spotify.com/web-api/create-playlist/
https://developer.spotify.com/web-api/add-tracks-to-playlist/
Where should the reviewer start?

Any background context you want to provide?
This is one of the features I wanted to build most! Only works for 1/3 top songs lists, may add it to the other or may take the night off who knows. ..... .... . .
What gif best describes this PR or how it makes you feel?

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&ved=0ahUKEwie3uHuibDXAhVGwGMKHewPDsgQjRwIBw&url=https%3A%2F%2Faminoapps.com%2Fpage%2Fanime%2F8978742%2Fgreatest-moments-in-each-saga-of-dragon-ball-z&psig=AOvVaw0NUV8FiVt1ZMx2N3eizLLi&ust=1510268260670875


added links, emphasis & minor tweaks

+1 Approve

Coverage remained the same when pulling 7fa6ffdde2bbc0bea7f2a50f8905f2c195c59ab3 on readme-minor-additions into d5c6290c52699606e67aa1dea7cc2f73f37d5814 on master.


Design review for translations

Feedback from Design team: Add a chevron down next to the dropdown text so it’s consistent with the homepage.

Language switcher dropdown proposed screenshot

Since we're using ripple colors and theme, buttons should follow this guideline here
https://www.figma.com/file/flntK6lS7xRAqMtxYOu2bY/Component-%2F-Button?type=design&node-id=0%3A1&t=xwq1eJrKlIEddhcY-1

Card styling on page in light mode doesn't look right at the moment, should follow ripple documentation card style here https://www.figma.com/file/P9ILbAuUS5164ElkyE9G7s/Ripple-Documentation?type=design&node-id=1375%3A22325&t=GssKSocLCCtCCYT5-1

Ripple logo should not be inversed in dark mode, right now it's orange but it should be white


Buffer Full

Hello,
I use python code to connect :
process = subprocess.Popen(
['certstream', '--url', 'ws://<IP_ADDRESS>:8080'],
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
text=True
)
output_pattern = re.compile(r'[(.?)] (https://.?) - (.*?)$')
try:
    for line in process.stdout:
        match = output_pattern.match(line.strip())
        if match:
            time, log_url, domain = match.groups()
            json_entry = {
                "id": id_counter,
                "time": time,
                "log_url": log_url,
                "domaine": domain

My python code transforme output in real time into JSON --> database.
After a few minutes of use, I get this error message and the logs pause :
2024/06/04 00:06:31 broadcastmanager.go:99: Not providing client '10.10..:54222' with cert because our buffer is full. The client can't keep up.
Is this normal and how can it be corrected please?

I also have thus issue please help :
E0604 10:11:18.689366   19806 fetcher.go:292] https://ct.googleapis.com/logs/us1/argon2024: GetRawEntries() failed: Get "https://ct.googleapis.com/logs/us1/argon2024/ct/v1/get-entries?end=1683780465&start=1683780366": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
and
E0604 10:11:55.707438   19806 fetcher.go:292] https://ct.googleapis.com/logs/eu1/xenon2024: GetRawEntries() failed: Get "https://ct.googleapis.com/logs/eu1/xenon2024/ct/v1/get-entries?end=1848868040&start=1848867941": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Hi Rceros, I assume that your python code is just not fast enough to process all the certificates, since certstream handles ~250-300 certs per second. Please read my answer to a similar question: https://github.com/d-Rickyy-b/certstream-server-go/issues/28#issuecomment-1852523034

In my case I had to run 5 parallel node processes to handle the stream.

@d-Rickyy-b  many thanks,
I've noticed other things too, do you know what they're linked to?
https://yeti2025.ct.digicert.com/log: GetRawEntries() failed: Get "https://yeti2025.ct.digicert.com/log/ct/v1/get-entries?end=107046060&start=107045961": unexpected EOF

In my case I had to run 5 parallel node workers to handle the stream.

How do you do it? Do you have any code examples?
Do you use python to do it or Go?
please help

I've noticed other things too, do you know what they're linked to?

The error comes from the certificate-transparency-go module that's used by certstream-server-go (click).
These logs happen when either the log returns a 429 error, indicating that we're requesting too many certificates (although this is not the case here) or that the upstream API (the certificate transparency server of digicert in your case) returned an error or sent invalid/malformed data. "unexpected EOF" usually means that the server did not respond in an expected way or closed the connection before fully transferring the requested data.
Based on the test file client_test.go test file it can be understood that the unexpected EOF is thrown when the json client tries to parse a json string that's not valid.
From my past experience, digicert logs are causing regular issues. See also:

https://groups.google.com/a/chromium.org/g/ct-policy/c/AJ7msx2aWac
https://groups.google.com/g/certificate-transparency/c/NVByWgLE6XM
https://groups.google.com/a/chromium.org/g/ct-policy/c/PCkKU357M2Q

Hope this helps.

How do you do it? Do you have any code examples?

I created a python tool for this purpose (certleak). I am currently not actively using it so I can't tell you if it's still up for the task, but it worked fine in the past.
Feel free to try it out and send your feedback my way.

If you are still experiencing issues or have more questions, please open a new issue.


Updated documentation from React State to React Hooks

Updated documentation from React State to React Hooks

Todo: Check whether these examples are correctly.


How to change the Unit Decimal?? cause all setting set in 2 decimal point 0.00

How can i change the decimal. i have try set in yobiapps.sh and multichain.sh to 0.000001 but not working .

The current version of Yobichain allows you to issue and transact with assets that are divisible up to 8 decimal places.


FramerX help

On Spectrum it now says "Material-UI has a new home. This community is no longer on Spectrum"
Are you now on Discord and can I get an invite? I'm on FramerX Discord but some question is more Material-UI.framerfx related. Like right now I'm trying to extend the Typography component by wrapping it and it's clashing with the Framer/MatUI package.
As I use Material UI daily, I think the only way forward is to get a little closer to the project and maybe help on git eventually.
I did try StackOverflow, but it wasn't fruitful.

The community is now on StackOverflow

Unfortunately, not as I've been blocked due to spelling, or not articulating as a serious developer would. It all seems very formal and I have dyslexia (Like most designers) so makes it harder.
As Material UI is now in Framer X, maybe it could be more friendly and supportive for designers that are trying their best to navigate a very technical landscape.

Is there a way to create the equivalent of a slack channel on StackOverflow? Then I can pop all my FramerX questions in there
so as not to annoy hardcore devs.

@LincMitch Interesting point. The reason we close the Gitter channel, closed Spectrum, and never tried Discord, Slack is that from our experience, the incentive for the community to get there is to find help. This use case is better served on StackOverflow for a couple of reasons: 1. concentration of effort on a single place 2. has been doing that for a decade, 4. with proper incentive systems, 5. SEO, etc.
Getting his question accepted on StackOverflow requires to spend quite some time, I think that it's mostly designed to make sure the question will not only benefit the person that ask it but the broader community.
I think that if your request is code related, and even wearing the designer's casquet, StackOverflow is bested suited for this. StackOverflow is used in order fields through their https://stackexchange.com/ expansion.

Then I can pop all my FramerX questions in there

I'm sorry, it's not going to happen.

Understood. Was worth a shot.

Also, the Framer kit isn't comprehensive. If we do dedicate time into a fully fledged version, it would probably be paid to make it sustainable, in which case, the support you are looking for would come with it. But it's not on our agenda, yet?

There is a "?" at the end. Would you be asking if I would pay for it or be paid to help build it?  Would love to get involved in making this a reality. It would be an amazing and important contribution to the Framer X community and help bridge the gap between design and development.

Would you be asking if I would pay for it or be paid to help build it?

Actually, the answers to both of these questions are interesting. I think that we are still 6 months too early to consider it (too small of an audience yet) but there is potential.
@mbrookes One thing that could be great is to list the missing components, to get an idea of how far off we are, what we can improve.

Would be great to help put that list together. Does anyone on the team use Framer X, if not, I'm happy to point out what's missing from a designers point of view.

If you could point out what's missing, it would be awesome. No, we don't use FramerX. For now, it seems x5-10 less popular than Sketch and Figma, but that might change with the current trend :).


Adapt to access param change in nsdl struct.

Hide string setters from M2MBase class.

@TeroJaasko

+1


xrpc: Wrong error type returned when repo is not found

Testing on getLatestCommit at least - when called with a DID of a repo that doesn't exist (was deleted?), it returns:
https://atproto.brid.gy/xrpc/com.atproto.sync.getLatestCommit?did=did:plc:qwerty
{
    "error": "InvalidRequest",
    "message": "Repo None not found"
}

On Bluesky servers, it returns:
https://amanita.us-east.host.bsky.network/xrpc/com.atproto.sync.getLatestCommit?did=did:plc:qwerty
{
    "error": "RepoNotFound",
    "message": "Could not find root for DID: did:plc:qwerty"
}

The error type seems to be specified in the lexicon:
https://github.com/bluesky-social/atproto/blob/main/lexicons/com/atproto/sync/getLatestCommit.json#L30
"errors": [{ "name": "RepoNotFound" }]

Good point, thanks!

Done!


GUARD-450 basic plumbing and authentication

I had to merge since I now have more changes (GUARD-451). Feel free to review still.

@maxim-skuvault Looks good.


chore(deps): :arrow_up: update dependency @types/node to ^20.11.19

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@types/node (source)
^20.11.18 -> ^20.11.19

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   optional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/jest-preset-angular
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx/angular
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nrwl/angular
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/angular
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nrwl/angular
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-18T16_54_58_531Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-18T16_54_58_531Z-debug-0.log


Black Border to Mini Cursor

I really like the Blue Archive Mini Cursor, but i keep losing it in my screen. Could you make a version with a black border in it? Like the Milllenium

The Blue Archive cursor set labeled as "Regular Edition" in the README.md is made following the same design philosophy used in the cursors for the official Chinese website for the game (linked in the "Credits" section).
From there, a set of issues arose with these cursors, including poor visibility on certain display settings or over certain backgrounds, due to the cursor's color palette. (e.g. #13 )
As a way to combat such issues, I created the "Millennium Edition" cursor set, which takes several liberties with the design to improve on the user experience.
Hence, I stand by what I said in the Issue 13. The "Regular Edition" was made as closely as possible to the official cursors, as such it is working as intended. If you such problems are occurring frequently on your end and are disturbing to your experience, I strongly advise you to please try the "Millennium Edition" cursors. While it is larger than the "Mini" set for the "Regular Edition", I believe it should be smaller than the general ones, and "Millennium Edition" also has much more customization options for you to choose from.


goroutine fairness is not guaranteed causing the hang with GCCGO (x86 GCCGO CI)

Signed-off-by: Srini Brahmaroutu<EMAIL_ADDRESS>

Moving it up makes sense since now the "continue" when n == 0 won't skip it.

LGTM

@LK4D4 can you please review this?

The call to callSchedulerIfNecessary doesn't feel right to me. What deadlock scenario is being prevented? If the code depends on the order in which goroutines are scheduled, I strongly feel that the code should be fixed to be more robust. Having a gccgo-only call to invoke the scheduler doesn't seem like the right fix.
At the very least, there should be a detailed comment explaining why we need this hack. But again, there must be a better way.

All it does is allow the runtime to switch to a different thread instead of getting stuck on this one. Our gcc-go folks are looking into a fix for gcc-go but in the meantime just moving this call up in the loop fixes a hang in our unit testcases - iotuils TestBufReaderCloseWithReaderCloser().
With simpleReaderCloser.Read() returning so fast the for-loop in bufReader.drain() becomes a thread hog.  There's actually a bug in that unit tests which I'll submit a PR for in a few minutes, but in the meantime since this call to callSchedulerIfNecessary() is already there, we might as well move it to a better spot.  :-)

@aaronlehmann This is gccgo only call, to avoid the hang. It will not affect the regular Golang execution flow.
If you have a better suggestion I am happy to try it out.
Issue is that go-routines does not relinquish their execution run. Please see the following conversation https://groups.google.com/forum/#!msg/golang-nuts/uxnfIytdO7Y/Vmp7nHfk7oEJ
sync.Mutex is a low-level synchronization primitive and does not guarantee fairness.

This makes more sense to me after reading the golang-nuts thread. Here's my understanding of what happens: drain is designed to read as fast as it can into a buffer, and if it can't keep up with the data source, it may read continuously, without yielding the goroutine and giving other goroutines a chance to consume the data.
I think the real problem is that we buffer incoming data without any size limit or throttling. The scheduler call works around one effect of this design problem, but there are other problems that can result, like running out of memory. I think a saner design would cap the buffer size, or pass data between goroutines with a buffered channel.
That said, I'm okay with this as a short-term fix. It's not really reasonable to ask you to redesign this piece of code in order to make Docker work with a particular compiler :). But I'd really appreciate it if you could add a comment explaining why the scheduler call is necessary. It was quite mysterious to me when I first encountered it last week.
I also wonder if we should make the scheduler call happen with the standard Go compiler, as well. If the code works as is with the standard Go compiler, that may just be a matter of luck. I don't know of any guarantee that a call to Lock will yield. Explicitly yielding seems safer than depending on sync.Mutex to do it.

I think your last push included an errant change in the commit from your standardized errors work (not to mention it will break when committed in the right PR because of golint comment doesn't match name error).  Repush when you get a chance.

@estesp thanks, removed extra file.

LGTM


.exe or .msi installer file?

What's the Problem?
a .exe or .msi installer wanted
Solution/Idea
Add a exe or msi installer
Alternatives
None.
Files Version
v1.5
Windows Version
Windows 7 SP1
Additional comment
No response

@Whirlpool-Programmer Files is a packaged app which doesn't work with exe/msi installers. MSIX packages are available with releases of Files on GitHub.

While it maybe closed it is a valid request an msi or exe installer that way UWP is not used. Windows 10 and 11 people will use non UWP apps as much as possible.


#3412 set result and status properly; refactored lighthouse service

Closes #3412
Integration test run: https://github.com/keptn/keptn/actions/runs/697669743
Signed-off-by: Florian Bacher<EMAIL_ADDRESS>

@bacherfl can I ask you a favor of update the Readme.md of the lighthouse-service since it still uses old event types.


BUG? Pydiso not a requirement

Not sure if this is a bug or by design, but pydiso is not a requirement in the setup and therefore needs a separate install of pydiso to use the Paradiso solver.  It would be nice to install pymatsolver and get the Paradiso solver with it.

It is by design, not all platforms have access to the Pardiso solvers.


GoogleService-Info.plist alredy exist

good morning
I have the following problem, when I compile a project in ios, I miss the error that I left in the image, someone knows what may be happening.
regards

I'm having the same issue when I tried to run
ionic cordova platform add ios
or
ionic cordova plugin add cordova-plugin-firebase
Any idea how to solve this issue ?


Docker build and push to Docker Hub

This PR configures Github Actions to build and push Docker images do Docker Hub once main branch is modified.
In order to these changes to work correctly it is necessary:

[ ] Configure Docker Hub username as variables in this repository
[ ] Crete Docker Hub access token with read/write/delete permission (needed to update Docker Hub description using README.md from this repository)
[ ] Configure Docker Hub access token as secrety in this repository

I tested these changes on a test repository (only available while reviewing this PR).

@italovalcy I applied in the last commit all your suggestion but the last one. I justified it on the proper conversation above.

Nice, @italovalcy :)
Just did your suggestions.


Require.js / can not load ar.js

Hello,
Is it posible  to load ar.js using require.js?
When loading the modules the application stops working and by consulting the Firefox console I can see the following error:
Error: Script error for: WebAR
http://requirejs.org/docs/errors.html#scripterror
Looks like I forget to add WebAR but in the project that I created to test ar.js, it works without problems and does not request any WebAR file. The scripts of this project are loaded using the

This PR has been closed due to inactivity for over one year. Please open a new, updated issue if the problem or the question is still relevant.


how does the Sign and attach a certificate and certificate chain work

Question
I am confused on how the Sign and attach a certificate and certificate chain part works
We have a custom CA which generates our certs. I generated a cert and tried using it for the signing process thinking that the cert would provide some extra features like validity check etc
but what i noticed is irrespective of if i provide the cert or not during signing, the verify cmd does not care and it just checks if the key is provided or not
what is exactly happening here?
below is 1 of the output
`
$ cosign sign --key cosign.key IMAGE_NAME_AND_TAG@digest --tlog-upload=false
Pushing signature to: IMAGE_NAME_AND_TAG
$ cosign public-key --key cosign.key > cosign.pub
$ cosign verify --key cosign.pub --cert cert.crt --cert-chain chain.crt --insecure-ignore-tlog ${IMAGE_NAME_AND_TAG}
WARNING: Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.
Verification for IMAGE_NAME_AND_TAG --
The following checks were performed on each of these signatures:

The cosign claims were validated
The signatures were verified against the specified public key
[{"critical":{"identity":{"docker-reference":"IMAGE_NAME"},"image":{"docker-manifest-digest":"sha256:12ac9989d832da2e35052d8d8ef5f27f1eb7e85a260326d484a949c300a6fa"},"type":"cosign container image signature"},"optional":null}]
`

something similar when we sign and attach a cert but dont verify with that cert
`
$ cosign sign --key cosign.key --cert cert.crt --cert-chain chain.crt IMAGE_NAME_AND_TAG@digest --tlog-upload=false
Pushing signature to: IMAGE_NAME_AND_TAG
$ cosign public-key --key cosign.key > cosign.pub
$ cosign verify --key cosign.pub --insecure-ignore-tlog IMAGE_NAME_AND_TAG
WARNING: Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.
Verification for IMAGE_NAME_AND_TAG --
The following checks were performed on each of these signatures:

The cosign claims were validated
The signatures were verified against the specified public key
[{"critical":{"identity":{"docker-reference":"IMAGE_NAME_AND_TAG"},"image":{"docker-manifest-digest":"sha256:02ae9710e2a6c32ff714f27e5f3ade6412ff513f1d4556f37c96c3f2140bc8"},"type":"cosign container image signature"},"optional":{"Subject":""}}]
`

i want to know what is the use of attaching the cert and why in this case the cert is not verified or checked

Hi Team, any info on this will be appreciated


Survey Form

Developer Checklist

[x] Followed guidelines mentioned in the readme file.
[ ] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[x] Starred ⭐ the Repo (Optional)

Summary
A survey form which includes html , css, javascript
Screenshot
attach screenshots/gifs here
Live Project Link
add a working project link here

Follow PR check list and please add screenshots/live link etc.


Heartbeat should have consistent date format

When setting heartbeat, I see it's formatted using UTC. Whereas when comparing it, a local timezone is used. Which in my case (CST), causes all sessions being deleted.

@polyrabbit Could you also fix the delfile.Expire ? Which has the same problem.

After testing with sqlite3, I see it indeed has the same problem. But I'm wondering - do other DBs also have the same problem?
sqlite3 is special because it doesn't understand datetime type, so xorm handles it differently:
if dialect.URI().DBType == schemas.SQLITE {
	engine.DatabaseTZ = time.UTC
} else {
	engine.DatabaseTZ = time.Local
}

So my question is - it's easy to add a .UTC() suffix to every where condition, but will it break other DBs? I don't have mysql on handle for the testing.
In the long term, I suppose it's better to store all datetime types using timestamp to avoid all the problems caused by time zone. What do you think? @davies

@polyrabbit Yes, the timezone issue could be tough, we'd better to use timestamp instead.


Add Password validation

Closes:

Title: Add Password validation
Name: Prakruti Pathak
Idenitfy yourself: GSSOC

Describe the add-ons or changes you've made 📃
I have implemented password validation to ensure that the password meets the following requirements:

Minimum 8 characters
Contains at least 1 digit
Contains at least 1 special character
The valid_password function was added to check these criteria using regular expressions. Additionally, the password validation logic was integrated into the signup process, ensuring that users are informed if their password does not meet the strength requirements.

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Please provide a detailed video of the working with the errors like if not matched the criteria then what will it do.

Never commit your pr in main branch


[tiktok] Failed to fetch video or user detail

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
all
Provide a description that is worded well enough to be understood
failed to fetch video detail nor user detail. video is downloadable using other online downloader.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--', 'https://vt.tiktok.com/ZSjekG1vo/']
[debug] Encodings: locale cp950, fs utf-8, pref cp950, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [87408ccfd] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2022-02-10-git-b6bb6b9f22-essentials_build-www.gyan.dev (setts), ffprobe 2022-02-10-git-b6bb6b9f22-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.35.5, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1839 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[vm.tiktok] Extracting URL: https://vt.tiktok.com/ZSjekG1vo/
[vm.tiktok] ZSjekG1vo: Downloading webpage
[TikTok] Extracting URL: https://www.tiktok.com/@tribedaloca/video/7428151463727074561?_t=8qj15m0aC52&_r=1
[TikTok]<PHONE_NUMBER>727074561: Downloading webpage
ERROR: [TikTok]<PHONE_NUMBER>727074561: Unable to extract webpage video data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template.  If you are able to get the channel_id from a video posted by this user, try using "tiktokuser:channel_id" as the input URL (replacing `channel_id` with its actual value)
  File "yt_dlp\extractor\common.py", line 741, in extract
  File "yt_dlp\extractor\tiktok.py", line 1033, in _real_extract

I can't reproduce the issue; everything is working on my end. Have you been downloading heavily from TT recently? It's possible you've been rate-limited or are receiving a captcha challenge page

What happens when you open one of these pages in browser in a private/incognito tab? Do you get any sort of challenge page?

actually tiktok discontinued service in my area long time ago (kind of geoblock),
tiktok video/user page is not available in browser.

If the content is unavailable in your browser, then it's expected that yt-dlp will fail as well.
You could try passing --xff US (this seems to be effective for livestreams at least), or extracting via API by passing the app_info extractor-arg (but the extractor-arg would have no effect for the user extractor, only the video extractor).
If you have no success with those workarounds, you'll need to use a VPN

actually tiktok discontinued service in my area long time ago (kind of geoblock),
tiktok video/user page is not available in browser.

If the content is unavailable in your browser, then it's expected that yt-dlp will fail as well.
You could try passing --xff US (this seems to be somewhat effective for livestreams at least), or extracting via API by passing the app_info extractor-arg (but the extractor-arg may only be effective with the video extractor, not the user extractor).
If you have no success with those workarounds, you'll need to use a VPN

adding --xff US has no effect , but adding extractor-arg gives a slightly different output,
I guess the API JSON is also geoblocked regardless of xff ?
[debug] Command-line config: ['-v', '--xff', 'US', '--extractor-arg', 'tiktok:app_info=735572885697939226', '--', 'https://vt.tiktok.com/ZSjekG1vo/']
[debug] Encodings: locale cp950, fs utf-8, pref cp950, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [87408ccfd] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2022-02-10-git-b6bb6b9f22-essentials_build-www.gyan.dev (setts), ffprobe 2022-02-10-git-b6bb6b9f22-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.35.5, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1839 extractors
[debug] Using fake IP <IP_ADDRESS> (US) as X-Forwarded-For
[vm.tiktok] Extracting URL: https://vt.tiktok.com/ZSjekG1vo/
[vm.tiktok] ZSjekG1vo: Downloading webpage
[debug] Using fake IP <IP_ADDRESS> (US) as X-Forwarded-For
[TikTok] Extracting URL: https://www.tiktok.com/@tribedaloca/video/7428151463727074561?_t=8qj15m0aC52&_r=1
[debug] [TikTok] {'app_name': 'musical_ly', 'app_version': '35.1.3', 'manifest_app_version': '2023501030', 'aid': '0', 'iid': '735572885697939226'}
[TikTok]<PHONE_NUMBER>727074561: Downloading API JSON
WARNING: [TikTok]<PHONE_NUMBER>727074561: Failed to parse JSON (caused by JSONDecodeError("Expecting value in '': line 1 column 1 (char 0)")); trying with webpage
[TikTok]<PHONE_NUMBER>727074561: Downloading webpage
ERROR: [TikTok]<PHONE_NUMBER>727074561: Unable to extract webpage video data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 741, in extract
  File "yt_dlp\extractor\tiktok.py", line 889, in _real_extract
  File "yt_dlp\extractor\tiktok.py", line 250, in _extract_web_data_and_status

I guess the API JSON is also geoblocked regardless of xff

Looks like it. I think VPN or proxy is your only solution

Actually, the iid you used in the app_info arg has been banned / no longer works. Maybe try a different one


Creat Kyma Doc Indexer CronJob

Description
Create a CronJob doc_indexer project that indexes Kyma documentations.
Reasons
We need a K8s CronJob that indexes Kyma documentation with a schedule.
Acceptance Criteria

[ ]  All the necessary GH Action jobs for CI pipeline
[ ] A K8s CronJob that runs the indexer with a schedule

Versioning of the documentation needs to be discussed. ATM, we are pulling the docs from main branch of all kyma modules.
For BTP documentation, we can use BTP vector db as suggested by @muralov.

I've created the versioning issue for indexing.
It makes sense to separate the versioning as it is not trivial task.


Should verify state of Resources before trying to Change

What can be improved
Instead of applying the manipulator chain one piece at a time, we should verify if all manipulators are ok with the current state of the request.
Why
This would avoid us changing the state halfway before noticing something is missing/wrong.

Similar #856


Invalid value in searchCursor

Hello,
After i get the results of contacts search request, i try to use the searchScroll to fetch the next page, but instead i get Invalid value in searchCursor error.
  const page1 = await FC.contacts.contacts.search(auth.access_token, query);
  console.log('1st page : ', page1.contacts.length);

  if (res.hasOwnProperty('cursor')) {
    const page2 = await FC.contacts.contacts.search(auth.access_token, {
      ...query,
      searchCursor: res.cursor
    });

    console.log('2nd Page : ', page2.contacts.length);
  }

This is the searchCursor format when i log it :  -1982292599,-1817101551,2691, the doc show another format.
How can i fix this ??
Thanks

@sidati Sorry you're having trouble with the searchCursor. I believe it should be a SHA1 hash. We'll look into why it's coming back like that and get back to you.

@sidati this issue should be resolved. Any of the searchCursors you have that look like the format above will not work, but new responses should contain a hash for the cursor and those should work just fine. Let us know if you have any other questions or issues.


chart clear serie  cause memory leak

Important: issues that don't use this template will be ignored/closed.

Describe the bug
chart clear serie  cause memory leak
To Reproduce
lv_chart_series_t * ser1;
int i = 0;
for(;i<100;i++)
{
ser1 = lv_chart_add_series(chart, LV_COLOR_RED);
lv_chart_set_next(chart, ser1, y);
lv_chart_clear_serie(chart, ser1);
}
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

lv_chart_clear_serie only clears point visually and don't remove the created serie. We don't have function to remove a serie right now.  If you are interested you can add lv_chart_del_serie(chart, serie)


Fixed minor typo in second cat object

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

No problem, I’m trying to get used to contributing. Even if its just a little typo (for now)….lol. Just so I know in the future, did I go through the process correctly?

On Nov 4, 2016, at 5:03 PM, Jonathan<EMAIL_ADDRESS>wrote:
@atjonathan approved this pull request.
LGTM 👍
Thanks for catching this lol!
You might enjoy atjonathan.github.io/catphotoapp 😂 🐈
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/FreeCodeCamp/FreeCodeCamp/pull/11526#pullrequestreview-7291985, or mute the thread https://github.com/notifications/unsubscribe-auth/AIs4vtR7lRoYAQi2qRvCUjn5xcfIzucPks5q66uwgaJpZM4KqAL4.

@adevenuto you might want to create an issue for anything bigger than a typo :smile: check out our Contributing docs :wink:


Drop use_cache=False if training_args.gradient_checkpointing

If I understand properly, these lines:
https://github.com/huggingface/trl/blob/b6af2edc93b275afcee22a3eb71f9a5702ff9fd8/examples/scripts/dpo.py#L111
are because, previously, using cache with gradient checkpointing was broken, see https://github.com/huggingface/trl/issues/145#issuecomment-1459735966
Since https://github.com/huggingface/transformers/issues/21737 has been resolved, I think we can replace these lines by
    use_cache=model_args.use_cache,

wdyt?

Oh that will be really great! Could you test it out with some larger models to see if it indeed works? E.g., mistral 7B or gemma 2 24B.

Actually, there are still these warnings everywhere:
https://github.com/huggingface/transformers/blob/1082361a1978d30db5c3932d1ee08914d74d9697/src/transformers/models/blip_2/modeling_blip_2.py#L970
I'll investigate further


Update to fs2 3.9.4

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ee459c8) 85.45% compared to head (21b3ede) 85.45%.

Additional details and impacted files
@@              Coverage Diff              @@
##           series/0.6.x    #1033   +/-   ##
=============================================
  Coverage         85.45%   85.45%
=============================================
  Files               132      132
  Lines              2008     2008
  Branches            239      239
=============================================
  Hits               1716     1716
  Misses              292      292

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Implement actuator status command.

ACTUATOR_STATUS = 0x02

This now returns the status for each actuator on a node, or "no actuators found for node [nodId]"


Update vasp_input.py

Added functions to make vasp_std and vasp_ncl input files

Example notebook
3_Chemical_Potentials_Inputs - Jupyter Notebook.pdf

Super stuff @sabrine-28. Thanks for this!!


fix(qwik-city): strip internal parameters for compare

Followup for #6410 and #6687
Fixes #6660
Fixes #6677

seems like a duplicate of #6687 no?
btw did you see this?
https://github.com/QwikDev/qwik/pull/6687#issuecomment-2229606481

Very nice, hope this can be released soon. Have been waiting for a specific fix for awhile in anticipation. Great work team!


New City Request- Concord, NH (Partially adopted from Manchester, NH)

To<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Defund Concord Police Department
Message:
Dear Concord Government Officials,
My name is [YOUR NAME] and I am a resident of [YOUR DISTRICT]. I am writing to demand that the City Council adopt a People’s Budget that prioritizes community wellbeing and redirects funding away from the police and towards social services that actually keep our community safe.
We are in the midst of a pandemic that has had severe consequences on our city. As of April 2020, the unemployment rate in Merrimack County has skyrocketed to 15.8% of the labor force. According to Concord Coalition to End Homelessness we are “bracing for a new wave of homelessness.” The responsibility of solving this rising crisis cannot fall on outside organizations and private donors.
Supporting communities in need is necessary now, more than ever. Yet the FY 2021 Budget would increase the Concord Police's budget by nearly a million dollars. Research shows that a living wage, access to holistic health services and treatment, educational opportunity, and stable housing are far more successful at reducing crime than police or prisons. As such, I demand more aggressive financial support be directed to those areas, particularly in response to the economic impact of COVID-19. I insist as a taxpayer of the city of Concord that funds be reallocated from the Concord Police to Human Services to ensure that the basic needs of all Concord citizens are met.
As our poor communities and communities of color are disproportionate targets of police violence and disproportionately affected by the COVID-19 pandemic, the current proposed budget for 2021 that would increase the budget of the Concord Police is unacceptable. We must join the calls of those across the country to Defund The Police and demand a budget that adequately and ethically meets the needs of at-risk Concord residents during this trying and uncertain time, when livelihoods are on the line. I insist on a budget that supports community wellbeing, rather than empowers the police forces that tear them apart.
Thank you for your time,
[YOUR NAME]
[YOUR ADDRESS]
[YOUR EMAIL]
[YOUR PHONE NUMBER]

Here are the email recipients<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I am unsure of where to put them within the template.

To<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Defund Concord Police Department
Message:
Dear Concord Government Officials,
My name is [YOUR NAME] and I am a resident of [YOUR DISTRICT]. I am writing to demand that the City Council adopt a People’s Budget that prioritizes community wellbeing and redirects funding away from the police and towards social services that actually keep our community safe.
We are in the midst of a pandemic that has had severe consequences on our city. As of April 2020, the unemployment rate in Merrimack County has skyrocketed to 15.8% of the labor force. According to Concord Coalition to End Homelessness we are “bracing for a new wave of homelessness.” The responsibility of solving this rising crisis cannot fall on outside organizations and private donors.
Supporting communities in need is necessary now, more than ever. Yet the FY 2021 Budget would increase the Concord Police's budget by nearly a million dollars. Research shows that a living wage, access to holistic health services and treatment, educational opportunity, and stable housing are far more successful promoting community safety than police or prisons. As such, I demand more aggressive financial support be directed to those areas, particularly in response to the economic impact of COVID-19. I insist as a taxpayer of the city of Concord that funds be reallocated from the Concord Police to Human Services to ensure that the basic needs of all Concord citizens are met.
As our poor communities and communities of color are disproportionate targets of police violence and disproportionately affected by the COVID-19 pandemic, the current proposed budget for 2021 that would increase the budget of the Concord Police is unacceptable. We must join the calls of those across the country to Defund The Police and demand a budget that adequately and ethically meets the needs of at-risk Concord residents during this trying and uncertain time, when livelihoods are on the line. I insist on a budget that supports community wellbeing, rather than empowers the police forces that tear them apart.
Thank you for your time,
[YOUR NAME]
[YOUR ADDRESS]
[YOUR EMAIL]
[YOUR PHONE NUMBER]

on it now


Fix DLP filter

Missing env and permission after we migrate to gke cluster. Tested-by: zlq
Tested:
Sandbox

/lgtm


Testing local changes can be viewed via PR

:rocket: deployed to http://connecting-to-services-pr-254.dev.c2s.nhschoices.net and using the latest release of nearby-services-api (0.2.0-beta)

Coverage remained the same at 98.897% when pulling 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master into 2c86218af69eb0203e6441aa250742c0afd3bd9e on test/docker_change_mh.

Pull request direction was wrong - master -> branch, recreating correct way around


bug: 1.1 configuration not working under docker version: apisix:1.2-centos

Issue description
After upgrade to docker image to 1.2-centos, it doesn't work with old (1.1) config
docker logs:
nginx: [emerg] invalid parameter: valid= in /usr/local/apisix/conf/nginx.conf:53
Environment

apisix version (cmd: apisix version): apisix:1.2-centos
OS: Centos 7.6

Minimal test code / Steps to reproduce the issue

using attached file conf.zip  to launch docker instance
Can see the docker instance keeps restarting
using docker logs to print the message,  can see
nginx: [emerg] invalid parameter: valid= in /usr/local/apisix/conf/nginx.conf:53

What's the actual result? (including assertion message & call stack if applicable)
What's the expected result?

dns_resolver_valid added in config.yaml from 1.2 release, so I think you should update config.yaml first.

After I add the below line in config.yaml under dns_resolver section
dns_resolver_valid: 30          # valid time for dns result 30 seconds
Docker still not able to start correctly, the error message becomes
nginx: [emerg] invalid number of arguments in "resolver_timeout" directive in /usr/local/apisix/conf/nginx.conf:54

@wangyjx You should add resolver_timeout option.
    dns_resolver_valid: 30          # valid time for dns result 30 seconds
    resolver_timeout: 5             # resolver timeout

look here

There is no answer from the author for a long time, please close it first.


Use a timeout in process.communicate when appropriate

Closes issue #121

Merge. Tag master branch as v1.0.1. Ask for the mosrs-setup/1.0.1 module to be created, and test using this module.


Nutanix Prisim Data Filter

Feature request:
We are interested in a new data ingestion scheme for Nutanix Prism. The sourcetype would be Nutanix.
I have attached a pcap report from our Nutanix server. The logs are in syslog format.
Nutanix Prism version: 5.20.3
nutanix.zip

Any updates on this ticket?

we are working on it, it should be released in few days after testing.

ok thank you

:tada: This issue has been resolved in version 2.31.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Gradle] Android build.gradle - project.configurations.compile is deprecated

The task project.configurations.compile is deprecated and likely to be removed by the end of 2018. implementation is what is supposed to be used now. There may be more that needs to be changed, but this seems to conform with new Gradle guidelines.

Hi, any progress on this?

When I change the lines in my project (1.9.9) then IntelliJ says "Resolving configuration 'implementation' directly is not allowed"?

changing compile to implementation in build.gradle of android module
project.configurations.compile ->  project.configurations.implementation
giving me an Error

Resolving configuration 'implementation' directly is not allowed

Below version specified in my project :
LibGDX - 1.9.9
Gradle - 4.10.1
Gradle Android Plugin - 3.3.0

Closing this, the lines in questions are long gone.


ISPN-14160 Upgrade Kafka client to version 3.2.3

https://issues.redhat.com/browse/ISPN-14160

Merged, thanks


Enum#inspect should be more specific

Enum#inspect prints the name of the enum member, or the numerical value if it's unnamed. It is the same as Enum#to_s.
This is ambiguous when multiple enums share the same member names.
enum Foo
  One
end

enum Bar
  One
end

Foo::One # => One
Bar::One # => One

I think this is okay for #to_s but #inspect should be unambiguous as possible. Using the full class name should help to fix that.
Foo::One # => Foo::One
Bar::One # => Bar::One

Of course this is less succinct, but I think that's acceptable. #to_s would be the shorter, but less precise alternative.
For flag enum values, the fully qualified name does not need to be repeated for every member. Following the syntax of Enum.flags method works great for that:
FlagsEnum.flags(One | Two | Three) # => FlagsEnum.flags(One | Two | Three)

A more succinct format with square brackets: FlagsEnum[One | Two | Three]
I think that's better because it conveys the same information with less space.
The result won't be valid code to recreate that enum value,[^1] but that's acceptable.
This should also work great as a representation format for unnamed members (cf. #12883) which wouldn't be valid syntax for .flags as well.[^2]
FlagsEnum::None                                         # => FlagsEnum::None
FlagsEnum::One                                          # => FlagsEnum::One
FlagsEnum.new(128)                                      # => FlagsEnum[128]
FlagsEnum::All                                          # => FlagsEnum[One | Two | Three]
(FlagsEnum::One | FlagsEnum::Two)                       # => FlagsEnum[One | Two]
(FlagsEnum::One | FlagsEnum.new(128))                   # => FlagsEnum[One | 128]
(FlagsEnum::One | FlagsEnum.new(8) | FlagsEnum.new(16)) # => FlagsEnum[One | 24]
(FlagsEnum::One | FlagsEnum::Two | FlagsEnum.new(16))   # => FlagsEnum[One | Two | 16]

[^1]: We could consider adding Enum.[] exactly like this, basically as a replacement for Enum.flags because there the same benefit applies: it's more concise.
[^2]: Supporting numerical values could be a potential enhancement for .flags/.[] as well.

I think separating elements with a comma instead of a pipe will allow implementing it as a method instead of a macro.

@asterite Yes, we could use symbols for autocasting. I considered that as well. But that would potentially be ambiguous. The mapping between member name and symbol is not exactly 1:1. Symbol autocasting is case-insensitive, which would lead to problems when an enum contains members with the same letters but different casing.
/ref #11660
enum Foo
  Bar
  BAR
end
Foo.new(:BAR) # => Bar

An unambiguous literal representation of the member name is necessary for #inspect.
I suppose we could use the literal casing for #inspect. That should be unambiguous. The problem appears when parsing back the output as Crystal code. But producing valid code with potentially invalid semantics doesn't sound like a good idea.

Idea: disallow two enum members if their snake case lead to the same value.

Idea: disallow two enum members if their snake case lead to the same value.

@asterite Sounds good for a regular code, but what about lib bindings where you cannot control the member naming?

How can you not control that?

Yeah, I think this should be controllable, though it means deviating from the original spelling of constants. Not sure if that would be a huge problem, but it causes some friction.
However, this uniqueness validation would definitely be a breaking change, so we couldn't enforce it short term.
So I'd leave that beside for now and just implement a format for #inspect that is unambiguous and can work with what we currently have: https://github.com/crystal-lang/crystal/issues/12884#issuecomment-1368421624

Oh, well I guess you can reassign values, forgot about that 🤦♂

In any case, it seems that to implement this it will require a macro, and separating values by commas will be easier to implement.

Right, using a comma for simplicity makes sense.

An edge case is a flag enum with a composite member:
@[Flags]
enum FlagsEnum
  One
  Two
  OneTwo = One | Two
end

FlagsEnum::OneTwo

#to_s currently returns "One | Two | OneTwo". But that's unnecessary. "OneTwo" should be enough. Similarly, for #inspect, it's "FlagsEnum::OneTwo.