Bazel version issue with Mediapipe.

/home/user/Med/mediapipe-master/WORKSPACE:13:1: Traceback (most recent call last):
File "/home/user/Med/mediapipe-master/WORKSPACE", line 13
versions.check(minimum_bazel_version = "0.24.1", ...")
File "/home/user/.cache/bazel/_bazel_user/0777cb37d575e5092fe0b62d55a00d51/external/bazel_skylib/lib/versions.bzl", line 116, in versions.check
fail("Current Bazel version is {}; ex...))
Current Bazel version is 1.0.0; expected at most 0.29.1
link for WORKSPACE file
https://github.com/google/mediapipe/blob/master/WORKSPACE

This is unrelated to the IntelliJ plugin -- it's either an issue with bazel itself, or whatever else is doing that version check (bazel_skylib?)
Could you file a bug with bazelbuild/bazel instead?


Show Central Link frequency

When the Central Link schedule is not published (weekdays) we should show the Links current frequency.

I don't think this is actionable at the client app level. Closing.


New package: GPnet v0.0.1

Registering package: GPnet
Repository: https://github.com/TuringLang/GPnet.jl
Created by: @yebai
Version: v0.0.1
Commit: 2272f5a5811216b64a15dbb56b5ceecf7c689917
Reviewed by: @yebai
Reference: https://github.com/TuringLang/GPnet.jl/issues/4#issuecomment-583871584

[noblock]
You need to rename src/GPJ.jl to src/GPnet.jl. Then re-trigger Registrator.


Optimize draining logic

Currently, the SRIOV network config daemon will drain a node, when

a node reboot is required;
the numVF is changed from non-zero value to another;
the 'mtu' is changed;
the configuration of the device plugin is changed.

Among all the conditions, draining is only mandatory for the node reboot case. For the other cases, it would be sufficient to just evict the pods with VF attached. With this enhancement, we can shorten the overall reconciliation time when applying new node policies.

should be fixed via https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/555


Support for multiple Office 365 tenants

Is there any configuration where one Company Communicator instance and authoring app can send messages to multiple of the same user bot in different tenants?
Example: Contoso has Company Comm deployment. Fabrikam is a subsidiary of Contoso, but they are in a different Office 365 tenant. Can Fabrikam install the same User Bot manifest as Contoso, and then receive messages?
Is that what the field "AllowedTenants"  is for in the App Service? Does this field accept a list of Office 365 tenants GUID's?

HI @GrantOliasani ,
Sending messages to multiple tenant at a time is not be possible due to restrictions from Azure side. However you can install another instance of company communicator to different tenant.

Hi @GrantOliasani,
Could you please confirm if the issue logged is fixed and we are good to close the request. If you have any further issue request you to please log another issue.

Hi @GrantOliasani ,
We tested the suggested approach to support multi-tenant. The messages were getting delivered as expected. However, we won't be able to confirm on go-ahead with a production deployment as while sending >100K messages we are not sure about how the behavior will be. Our recommendation will be to deploy another instance of CC for a different tenant.
However, if you are not willing for another instance, then the same instance can be used with the work around steps shared over Teams but it won't be our recommended approach.
Let us know if anything required and we are good to close the request.

Hi @GrantOliasani ,
We are closing the issue due to no confirmation from the author.

Hi,
Even if not recommended, what are the configurations needed to use only one instance of company communicator for multiple Office 365 tenants?
Is just adding the tenant Id to the "AllowedTenants" enough?
Thank you


static directory will result in 404 without slash

Question
Good day, I don't really know if it's a bug or a feature, but when enabling static files with enableStaticFiles("static") or enableStaticFiles("static", Location.EXTERNAL), I've noticed something unexpected.
When opening a directory path in browser for example http://localhost/page/, it serves the page/index.html automatically, but when removing the slash (http://localhost/page) it results in 404.
This was really confusing because my friend wrote all link addresses in HTML as /page rather than /page/.
Reproduce
You can reproduce this by simple
import io.javalin.Javalin
fun main(args: Array<String>) {
	Javalin.create()
			.enableStaticFiles("static")
			.start()
}

and placing html inside static folder.
Also I should mention that it doesnt occur when using custom mapping through get("/api") {...} ( see https://shardbytes.com/fruit and https://shardbytes.com/fruit/)
(and I've seen some solved issues about this, but nothing about static files).
I've looked in Javalin source but got lost :D, not sure if I can PR a fix.
Workaround
I've fixed it by placing my own static mapping after REST mapping (but it would be better just to use static files method ) :
< ... REST mapping and stuff ... >

get("/*") {
    val splat = it.splat(0) ?: "" // get route
    val reqfile = File("static/$splat") // grab file matching route

    if (reqfile.exists()) { // check if exists

        // different processing for directory and files
        if (reqfile.isDirectory()) {
            // if directory, render thymeleaf and serve index.html
            val index = File("static/$splat/index.html")
            if (index.exists()) {
                println("-> serving thymeleaf index.html of /$splat")
                it.renderThymeleaf(index.path, mapOf()) // render empty thymeleaf
                // ( this wont be executed if something else was routed here before ofc )
            } else {
                it.status(404)
            }
        } else {
            // if file, patch header MIME type and serve file through stream
            val type = MimeTypes.getDefaultMimeByExtension(reqfile.path)
            println("serve file -> ${reqfile.path} [$type]")
            it.contentType(type) // ULTRA IMPORTANT, http header needs the serve mime type matching !!!!
            it.result(FileInputStream(reqfile))
        }

    } else {
        it.status(404)
    }

}

As I said I don't know if this should be like this, but it was very confusing for me.
Also maybe dontIgnoreTrailingSlashes() doesnt affect static files ?
Thank you for looking at this.
Seb

I've done some googling and it seems like people have different opinions about this :
[https://www.quora.com/Should-my-URL-structure-contain-a-trailing-slash] (https://www.quora.com/Should-my-URL-structure-contain-a-trailing-slash)
[https://github.com/pyeve/eve/issues/118] (https://github.com/pyeve/eve/issues/118)
[https://www.cloudways.com/blog/trailing-slashes-urls/] (https://www.cloudways.com/blog/trailing-slashes-urls/)
I can't really decide which one to adapt to. I haven't worked that much with custom servers yet (only used like some NodeJS express or some free webhosting ), but having page and page/ has always had same result for me = geting the index.html in that directory (if it is a directory).
Also I don't know how difficult it would be to fix this so 🤔
What do you think  ? @tipsy

Right now the enableStaticFiles just enables Jettys own ResourceHandler (https://github.com/tipsy/javalin/blob/master/src/main/java/io/javalin/staticfiles/JettyResourceHandler.kt). Might be some configuration which enables it?

Yes @pkkummermo, I'm already working on a fix, there is already a dont dontIgnoreTrailingSlashes() in Javalin class but it works only for mapping, I'll add another method = dontIgnoreStaticFileTrailingSlashes() so it works for static files too. ( should i leave it to ignore slashes by default or no ? ). should be done in 15 min, will PR.

pull request created, now we just wait for David
https://github.com/tipsy/javalin/pull/295


Add more features

Add more features such steam,wallet,Minecraft,epic,battle net, and more to grabber check powershell token grabber of kdot you can see lot of features it's pretty cool if you gonna add it to rose inject

Blud powershell grabber is in a different lang lmao
but noted

i'm on holidays so i can't do it but it might be released soon

Add more features such steam,wallet,Minecraft,epic,battle net, and more to grabber check powershell token grabber of kdot you can see lot of features it's pretty cool if you gonna add it to rose inject

okay, thanks we gonn do that soon


rust-analyzer: 2020-06-01 -> 2020-06-15 and fix version display

Motivation for this change
Bump version.
Fix output when it is called with --version. (Used to be ??????)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

With https://github.com/NixOS/nixpkgs/pull/90211 merged, can this be rebased onto it?
Also, cc @lovesegfault on the version display. Isn't there a better way to pass this in?

@flokli I think this approach is fine, although perhaps it could benefit from being upstreamed with an explanation of why this helps us in Nix land.

Humm… I thought about using the git-version crate (but didn't check if it allows overriding the version via an env variable), instead of implementing (and extending the logic on our own)

Maybe we could wait for the next release to fix it.


Close the tsfile once the memtable is flushed into

We change this default config just to adapt for aligned timeseries.

Coverage increased (+0.02%) to 68.057% when pulling 7ae1ed00cf2b534ca48090b139fd7a17eedca7df on CloseOnce into cca356e43ea744a27cb8b5534a8e4168b1b65b5b on master.


Failed loading builtin log types from disk

Description
While performing the v4.10.0-alpha2 Installation Assistant test I found that error in the Wazuh Indexer logs:
[2024-10-22T13:03:15,665][ERROR][o.o.s.l.BuiltinLogTypeLoader] [node-1] Failed loading builtin log types from disk!

It has been seen in Amazon Linux 2023, Ubuntu 22.04 and RHEL 9 OSs.
You can see the full Wazuh Indexer log here.
To Reproduce
Steps to reproduce the behavior:

Perform an AIO installation with the Installation Assistant with the 4.10.0 version.
Check the /var/log/wazuh-indexer/wazuh-cluster.log log file.

Additional context
As you can see in the referred test, the deployment finished successfully, so it is not a bug that breaks the Wazuh installation process for now.

Caused by OpenSearch's security-analytics plugin:

https://github.com/opensearch-project/security-analytics/issues/1312

There is no fix available yet.


[discovery server] bump golang to 1.23

What this PR does / why we need it:
[discovery server] bump golang to 1.23
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
cc @dimityrmirchev

/lgtm

/kind enhancement

/cc @oliver-goetz


LG CNS in Seoul and Neutrona Networks

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

@karthikananth : Thanks for your contribution to the Azure documentation! The author, @cherylmc, has been notified to review your proposed change.

#sign-off


fixed issue #174 removed runtime checking on Projectile and moved git…

… operations to GitHubService

[x] Have you created an issue and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

created new PR #177


Add devcontainer configuration and update for IDEs integration

Summary

This PR fixes/implements the following bugs/features:

[ ] Bug 1
[ ] Bug 2
[ ] Feature 1
[ ] Feature 2
[ ] Breaking changes

What existing problem does the pull request solve?**

Test plan

Closing issues

Fixes #

devcontainer configuration and update for IDEs integration


Feature to show playlist

An option to show the list of all songs and let users choose a song to play.

Right, this feature is currently under dev. in #25 by @Monal5031 , though selection of tracks from the displayed list is one great thing we can incorporate !

Current plan is to have a slider button on top-left, which will slide in the tracks list onto the screen.
Any suggestions/thoughts on this @aviaryan ?

No, that is exactly what I had in mind.

Solution for this was fixed in https://github.com/Monal5031/Js-css-Experimentations/issues/7

This is ongoing in #183

Done in #187


Change the parsing of the data for the View this item links on event pages (from 2028)

Problem Description:
The frontend is not parsing the links for View this item on the <unit name> website on event pages. In some cases the unit name does not match the destination of the link.
Expected Behavior/Solution:
The frontend should read the data provided in subject_of > digitally_carried_by > identified_by > content to render the text for the link and the link will be retrieved from subject_of > digitally_carried_by > access_point > id.
"How Do I See It?" section will be removed and Web Pages will be added to the About section. (See wireframes below)
Requirements:

[x] update the getLinktoUnitSite function in the EventParser
[x] the How do I see it? section will be removed from events pages
[x] the web pages in the event data will appear alongside the About data

Example data to be parsed:

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Wireframe/Mockup
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - N/A
[x] Frontend requirements- Kameryn
[x] Questions
Should this issue also include a discussion regarding the naming of the "How do I see it?" section on the events pages as mentioned in the attached Bugherd? ANSWER: The How do I see it section will be moved out of events pages and the web pages will instead be placed with the about data for the event in the same fashion as People about sections. The label containing bolded text saying "Web Pages" and the web pages listed below it.

UAT/LUX Examples:

https://lux-front-tst.collections.yale.edu/view/activity/a36bcf00-699b-4ebc-bdc4-091568ce9858

Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:

https://www.bugherd.com/projects/284041/tasks/1961

Wireframe/Mockup:

What it looks like now:

What it should look like (Person Web Pages example):

Approved per UAT

deployed


feat/keep namespace filter

Save namespace filter to the kubectl.json file
also more elegant approach to saving a state to a file. we can reuse in the future.
Edit:
well.. sometimes it works, and sometimes it doesn't,
when it works it flashes between namespaced -> all -> namespaced
when it doesn't, it flashes  namespaced -> all
which could cause epilepsy:

Fixed! NS filter is working :)

Did a small refactor if you wanted to look at what I ment!


DBZ-6238 Use application level join rather than DB.

Use application level join since the issue with same code has been there previously in https://github.com/debezium/debezium-connector-spanner/pull/18.
https://issues.redhat.com/browse/DBZ-6238

@jpechane rebased to main

@nancyxu123 please check this issue

Hi @shantanu-sharechat this change looks good to me. @jpechane can you approve?

@jpechane I have tested this, but cannot apply label here.

@shantanu-sharechat It is task for @nancyxu123

@shantanu-sharechat It is task for @nancyxu123

Applied, thanks for waiting!

And merged, thanks a lot!


Arm64 support war

A new bug was discovered when run JAX container on ARM64 system: CUDA base container is missing support for ARM64 system when run on pyxis+enroot. The CUDA team is working on fixing this bug now, so a temporary WAR is introduced in this PR.

Could the logic be
if NVIDIA_REQUIRE_CUDA not set in arm64 container:
  fetch NVIDIA_REQUIRE_CUDA value from x86_64 container
  set that value in the arm64 container

instead? That way it will seamlessly keep working when they fix the base containers.

Could the logic be
if NVIDIA_REQUIRE_CUDA not set in arm64 container:
  fetch NVIDIA_REQUIRE_CUDA value from x86_64 container
  set that value in the arm64 container

Unfortunately, not, because in arm64 build NVIDIA_REQUIRE_CUDA is set to CUDA>=12.3, but it's not enough to pass compatibility test.
For comparison, here is what we have in amd64 build:
NVIDIA_REQUIRE_CUDA=cuda>=12.3 brand=tesla,driver>=470,driver<471 brand=unknown,driver>=470,driver<471 brand=nvidia,driver>=470,driver<471 brand=nvidiartx,driver>=470,driver<471 brand=geforce,driver>=470,driver<471 brand=geforcertx,driver>=470,driver<471 brand=quadro,driver>=470,driver<471 brand=quadrortx,driver>=470,driver<471 brand=titan,driver>=470,driver<471 brand=titanrtx,driver>=470,driver<471 brand=tesla,driver>=525,driver<526 brand=unknown,driver>=525,driver<526 brand=nvidia,driver>=525,driver<526 brand=nvidiartx,driver>=525,driver<526 brand=geforce,driver>=525,driver<526 brand=geforcertx,driver>=525,driver<526 brand=quadro,driver>=525,driver<526 brand=quadrortx,driver>=525,driver<526 brand=titan,driver>=525,driver<526 brand=titanrtx,driver>=525,driver<526 brand=tesla,driver>=535,driver<536 brand=unknown,driver>=535,driver<536 brand=nvidia,driver>=535,driver<536 brand=nvidiartx,driver>=535,driver<536 brand=geforce,driver>=535,driver<536 brand=geforcertx,driver>=535,driver<536 brand=quadro,driver>=535,driver<536 brand=quadrortx,driver>=535,driver<536 brand=titan,driver>=535,driver<536 brand=titanrtx,driver>=535,driver<536

A new bug was discovered when run JAX container on ARM64 system: CUDA base container is missing support for ARM64 system when run on pyxis+enroot.

This does not sound like the right diagnosis. Is the issue only pertinent to pyxis/enroot?
Agree, looks like this is a general docker image problem.


Demote some Docker e2e tests to flaky as per #7840

Replaces #10904
@yujuhong @ixdy @wojtek-t

The Jenkins failure seems unrelated to this change - LGTM
cc @davidopp for "ok-to-merge" label

LGTM

@quinton-hoole - how is it related to #10880 - didn't it fix the problem?

@wojtek-t Yes, you're right.  It has not flaked since #10880, as far as I can tell (barring what look like unrelated DNS errors).   Closing and will re-open if necessary.


Deno Postgress link in README.md does not work

I get a Server not found error when i go to https://deno-postgres.com/

Fixed!


suggestion: consider adding a report button next to the heart one

Once the report button is pressed the video gets pulled down from the DB. At least in my imagination

It's one solution but I think some people would abuse it and start reporting stories for no reason other than pure harassment. If it's implemented, the content shall not be instantly pulled down from the database before some sort of content 'revision', made either by a human or an AI built for that purpose.
I hope you guys can figure out how to deal with those troublemakers and get them out of the platform.

Once the report button is pressed the video gets pulled down from the DB. At least in my imagination

Excellent suggestion. Maybe we can work on this together if Ben gives the go-ahead.


Home page reorg (dev)

Re #518

@etorem FYI - I opened a pull request to get the changes on this working branch feature-home-page-reorg onto development, and approved it.
As a result, Github will automatically assemble the source code into the build site code, and commit that code to a branch called gh-pages. The contents of that branch get served up here, to our development site. This makes it easy for us to share previews of work-in-progress with people outside our team.


WIP: EO Band references proposal

This PR contains examples for a proposal to rework how EO Bands are defined and referenced from Assets, and to act as a facilitator for discussion.
There are three common use cases for Bands:

I have a static Catalog, and define the Bands in the Catalog and reference this single definition from Assets.
I have an API returning an Item with Assets that share no or few bands, and I want to put the band definition directly in the Asset to avoid indirection.
I have a static Catalog or API with Items with Assets that share more than a few bands, and want to define them once in the Item and reference each Band from multiple Assets.

The design constraints around bands are thus:

Bands may defined in an Item or its parent Collection
Assets that share bands should be able to each reference a single Band definition
Many Items will contain Assets that share no bands (e.g, Landsat 8 PDS), so defining Bands separately from the Asset they use them an unnecessary level of indirection.
Referencing Bands by array index is prone to implementation errors, and fragile in the the face of reordering Band definitions.
Semantics for when Bands are defined in the Item and in the Collection are not clearly defined (I would assume Item definition would take precedence, but this is not stated explicitly anywhere)

Overall, I fell that this proposed specification is a good balance between static catalogs that will typically define bands in the Catalog and API result Items that will need to be self-contained and can therefore have the band definitions within the Asset.

An issue worth reading on the history of bands in STAC:
https://github.com/radiantearth/stac-spec/issues/142


chore(tests): update S3 compat tests

What problem are we solving?
While present, the S3 compatibility tests were broken (at the very least when running on Linux) due to a few issues:

ubuntu:latest moving ahead of Python 3.6
Docker networking not working as expected (host.docker.internal)

This commit fixes the s3 compatibility tests, ensuring they run properly on linux, and updates the repository to contain some results.
How are we solving the problem?
Updating the machinery around running the tests
How is the PR tested?
Pull the repository and attempt to run the tests. The previous instructions should work almost unchanged, on MacOS.
Checks

[x] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

Ah, I just realized that the s3 tests have actually moved to be completely dockerized w/ compose. I can't tell which test is
That script doesn't work for me (./bootstrap is missing from more recent versions of ceph/s3-tests), but that code looks more recent than the code that was in test/s3/compatibility... Should I hollow out this directory and point at the make target @ docker/Makefile?
I can try to fix that test run as well (at least, pin it to a version of ceph/s3-tests that works).


release(v1.2.2): updating version to v1.2.2-beta-1

Updates versions and image tags in chart.yaml and values.yaml

[x] I have ensured that required images are available in MCR:

osm-controller, osm-injector, osm-bootstrap, osm-crds and init images of the corresponding chart version
envoy image of version listed in osm-arc/oss values.yaml
grafana, grafana-image-renderer, prometheus, jaegertracing/all-in-one image of version listed in osm-arc/oss values.yaml

[x] I have ensured that all the images mentioned in the previous step (aside from grafana-image-renderer) are available for both amd64 and arm64 architectures

[x] I have updated the Helm chart:

Updated the chart version, app version and dependency version in charts/osm-arc/Chart.yaml
Made applicable updates to the osm-arc values.yaml if any were made in the upstream OSM chart

[x] I have received 3 approvals from maintainers.

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

@microsoft-github-policy-service agree Microsoft

@microsoft-github-policy-service agree company="Microsoft"

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc

/azp run pr-e2e-arc

/azp run pr-e2e-arc

/azp run upgrade-e2e-arc


[#44] Simplify editing the CSR

Issue #44
🚸 Editing a CSR
Updated the UX to edit a CSR.  Removed the should renew check box. This could be done because a CSR is function of the subject information and the private key. Therefore we only stored the private key when creating the instance and regenerate the CSR on every save (it will stay the same if the subject did not change). Once the CSR is signed (upload a valid certifcate), we display a message to the user to let him know and make the field readonly so the CSR can't be edited.

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

Project coverage is 90.42%. Comparing base (2026162) to head (636ac6f).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
+ Coverage   90.14%   90.42%   +0.27%
==========================================
  Files          14       14
  Lines         467      470       +3
  Branches       71       72       +1
==========================================
+ Hits          421      425       +4
  Misses         41       41
+ Partials        5        4       -1

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

@sam-bertin if you use closing keywords in the PR description, then the PR will be linked to the issue, e.g.:

Closes #44


refactor: embed federation data inside the binary instead of reading it from disk

This makes the binary self-contained (no need to include the sources when deploying)
This also fixes the issue of LoadCsvFile opening files without closing them (breaks on my computer due to ulimits)

Thanks @LouisBrunner
I really appreciate it.


REF: OTel-Proto codec into otel-proto-common plugin

Description
This PR

Refactors OTelProtoCodec that lives in otel-trace-source into common plugins
Enriches and splits the codec into encoder and decoder class for the purpose of peer-forwarding
Uses the refactored codec in otel-trace-source

Issues Resolved
Contributes to #546
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (maint/546-migrate-trace-analytics-to-event-model@c614860). Click here to learn what that means.
The diff coverage is n/a.

@@                                 Coverage Diff                                 @@
##             maint/546-migrate-trace-analytics-to-event-model     #921   +/-   ##
===================================================================================
  Coverage                                                    ?   91.58%
  Complexity                                                  ?      642
===================================================================================
  Files                                                       ?       75
  Lines                                                       ?     1914
  Branches                                                    ?      163
===================================================================================
  Hits                                                        ?     1753
  Misses                                                      ?      121
  Partials                                                    ?       40

Continue to review full report at Codecov.

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

The common library is common to all plugins. I think creating a new library specifically for OTel is more appropriate.

@dlvenable Moved the codec to a separate module called otel-proto-common. Let me know whether it fits into the project structure

Would it be possible to achieve the same test effectiveness with less manual paring and helper functions?

@sbayer55 Would you mind point out examples inline?


Not listed yet: www.insights.com

The website at this url is unlisted: https://www.insights.com/us/resources/a-case-for-leadership-diversity/

This site is now listed in the latest version of Global Consent Manager. Thank you for the notification and let us know if you have any more issues.

Also, note that the Mozilla Add-On release will only be updated when I've finished all of the current listing issues. Today or tomorrow.


We need a way to search for text in snippets in Lepiter pages

There is currently no easy way to search within a long Lepiter page for a piece of text.
As a workaround, we could add a gtSearch extension in the Inpector view of a page.

Added LePage>>#gtSpotterForSnippetsFor:

Yes this is an important feature


MainLoop.ps1: Possible high CPU Usage due to constant event log check?

Background
We use a self service portal for spinning up local dev/test containers that are hosted on dedicated docker host machines (windows server 2019).
Problem
When the Containers run for a long (or not so long) time the event log (application) will be populated with many entries (i had an example with aprox. 7000 entries).
Due to these entries we saw very high cpu usage on thes docker host that was not entirly clear where they came from. It turned out they came from svchost which in turn was hosting several services which included also the eventlog service (and others: lmhosts, eventlog, dhcp).
After i had found hints about clearing out the event log here could solve the high cpu usage:
https://social.technet.microsoft.com/Forums/azure/en-US/eee36815-7be8-438b-bd60-8cc809f940ba/svchostexe-lmhosts-eventlog-dhcp-high-cpu-usage?forum=winservergen
I tested it on the host which was at that time running 11 Containers and hat an avg. cpu usage of 80-100% before the log cleanup.
when i look at MainLoop.ps1 i see that it constantly looks for event logs in the application log (every 2 seconds).
=> I think this causes the high cpu usage.

I have not tested with a custom MainLoop.ps1 if the problem disappears

Workaround
Then i cleared the logs on every running container with:
docker exec <container> powershell "Clear-EventLog System,Security,Application"

After that the cpu usage dropped to around 10%!
We could notice the drop to 0% on almost every container when using docker stats
Solution
I know the MainLoop is used to show errors in the docker logs but it is causing very bad performance.
Possible Solutions:

Remove the Get-EventLog
=>We will not do this obviously
Make an Environment Variable to control if the Get-EventLog will be executed
Make an Environment Variable to control the max. Log Length for the EventLog
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/limit-eventlog?view=powershell-5.1
And set the default to something low like 20kb instead of the default 20mb

For me Option 2 would be sufficient.

Thanks for the very detailed problem description.
The mainloop was made this way to allow docker run to show event logs in the display and in docker logs.
I described how to override scripts in this blog post: https://freddysblog.com/2018/03/20/navcontainerhelper-overriding-scripts-in-nav-containers
and the very last section is about mainloop.
If you use the following construct on your new-navcontainer:
-myscripts @(@{"mainloop.ps1" = "start-sleep -seconds<PHONE_NUMBER>"})
then you will in fact override mainloop.ps1 and wait for sleep for 100 years.
Considering the performance impact (and that we have other and better ways to check event log today with navcontainerhelper) I might turn the behavior around on new-navcontainer and add a parameter called -doCheckEventLog to enable the old behavior.

Thanks for the very detailed problem description.
The mainloop was made this way to allow docker run to show event logs in the display and in docker logs.
I described how to override scripts in this blog post: https://freddysblog.com/2018/03/20/navcontainerhelper-overriding-scripts-in-nav-containers
and the very last section is about mainloop.
(you shouldn't sleep for 100 years though - then you cannot create a pssession in the container)
If you use the following construct on your new-navcontainer:
-myscripts @(@{"mainloop.ps1" = 'while ($true) { start-sleep -seconds 1 }'})
then you will in fact override mainloop.ps1 and sleep for 100 years.
Considering the performance impact (and that we have other and better ways to check event log today with navcontainerhelper) I might turn the behavior around on new-navcontainer and add a parameter called -doCheckEventLog to enable the old behavior.

I can confirm the idea as we overrode also the default behavior because we noticed high CPU usage related to the mainloop.ps1 behavior.
And the benefits are really significant, especially very welcomed in environments where running containers with high density is a really important factor.

Next NavContainerHelper will introduce a parameter called dumpEventLog, which is required to get the eventlog in the output.

Also next NavContainerHelper will have a parameter called doNotCheckHealth, which will cause the container to always report healthy. This will cause the CPU usage from a container to be at its absolute minimum when not used.

Thats great news.
We already disable healthcheck currently because of the performance impact

https://freddysblog.com/2019/07/06/cpu-usage-in-business-central-containers/

I have some hints about your blogpost
To disable healthcheck --no-healthcheck on docker run does the trick.
Unfortunatly healthcheck only realy works with docker swarm as of my knowledge:
https://stackoverflow.com/questions/47088261/restarting-an-unhealthy-docker-container-based-on-healthcheck
So restarting of unhealthy containers is not supported out of the box...

Thanks for the info - I will change the implementation to use --no-healthcheck

Done


Implement Data Backfill Command

Objective
Create a command-line tool to efficiently backfill historical blockchain data into the indexer database, with support for resuming interrupted operations and parallel processing.
Scope of Work

Command Structure

Create CLI interface using clap
Add configuration options for block range
Implement progress reporting
Add resumption capabilities

Data Processing

Implement parallel block processing
Add batch size configuration
Implement error recovery

Performance Optimization

Add concurrent database writes
Implement memory usage optimization
Create progress monitoring

Requirements

Efficient parallel processing
Robust error handling and recovery
Clear progress indication
Documentation for all command options

I’d love to work on this issue as I have strong experience in building and managing APIs, handling server-side operations, and ensuring robust back-end performance.
Please assign this to me, and I’ll deliver a secure and high-quality PR within 12-24 hours.

Can I take this from here?

Hi, please can I be assigned this please? I would love to be the given the opportunity to solve this issue please. I have experience in html, css, JavaScript, TypeScript, cairo & rust.
Kindly assign me, I'm up for the task

Could I try solving this?

I'd love to work on this!

I’d like to resolve this.

i would to tackle this issue

I’d like to help with this.


Update README.md

Purpose
Describe the problem or feature in addition to a link to the issue(s).
'CapgeminiPackageTemplate' base class has been renamed with 'PackageTemplateBase' class. The PackageTemplateBase class is not updated in the readme file.
Approach
Updating the readme file to reflect the correct package template base class.
TODOs

[x] Documentation updated (if required)

also do stick to the conventional commits spec for the squash merge message e.g. docs: updated README to refer to new class name

also do stick to the conventional commits spec for the squash merge message e.g. docs: updated README to refer to new class name


Fix IndexPage reference in web-pages

ui-components path changed to web-pages
users.rs 'users' function migrated to IndexPage function
IndexPageProps struct added

Thanks for the pull requests I really appreciate it.


Create falco-0-30-0.md

Add falco-0-30-0.md Chinese document, easy to read.
Signed-off-by<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: gogolovefish
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval by writing /assign @leogr in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

hi @mstemm @vjjmiras :
I have submitted a Chinese translation of falco-0-29-0.md, please review it, thank you!

hi @mstemm @vjjmiras :
I have submitted a Chinese translation of falco-0-30-0.md, please review it, thank you!

/kind translation

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.