Fedora Silverblue support?

Silverblue doesn't have a "normal" package manager. All installations are the same. One can "overlay" RPMs (and their dependencies), but most of the time, all the work happens in Flatpaks and podman containers (especially toolbox containers, which are a special type of long-term podman contaner that simulates a standard Fedora installation, with dnf/yum and so on).
What's probably needed is to have podman support (#15) and ensure that nothing else is needed from the host system.

If you cannot run a docker client in Fedora Silverblue then I think this will be blocked by #15...

I currently have Docker as an overlay on Silverblue, and this is enough to get the (now deprecated) cockpit-docker add-on up and running, but it might not be working well enough for k3d. (I guess it isn't.)
There's the whole cgroups v1 vs. v2 issue, which may be problematic with Docker (Moby) still.

@garrett Could you try to install k3d and see if it works from command line? If that works then there must be a problem with k3x...

$ k3d cluster create mycluster
ERRO[0000] Failed to list containers
ERRO[0000] Failed to get nodes for cluster 'mycluster'
ERRO[0000] Failed to list docker networks
ERRO[0000] Failed to create cluster network
ERRO[0000] Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/networks?filters=%7B%22name%22%3A%7B%22k3d-mycluster%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
ERRO[0000] Failed to create cluster >>> Rolling Back
INFO[0000] Deleting cluster 'mycluster'
ERRO[0000] Failed to delete container ''
WARN[0000] Failed to delete node '': Try to delete it manually
INFO[0000] Deleting cluster network 'k3d-mycluster'
WARN[0000] Failed to delete cluster network 'k3d-mycluster': 'Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Delete "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/networks/k3d-mycluster": dial unix /var/run/docker.sock: connect: permission denied'
ERRO[0000] Failed to delete 1 nodes: Try to delete them manually
FATA[0000] Cluster creation FAILED, also FAILED to rollback changes!

With sudo:
$ sudo k3d cluster create mycluster
INFO[0000] Created network 'k3d-mycluster'
INFO[0000] Created volume 'k3d-mycluster-images'
INFO[0001] Creating node 'k3d-mycluster-server-0'
INFO[0002] Pulling image 'docker.io/rancher/k3s:v1.18.6-k3s1'
ERRO[0014] Failed to start container
ERRO[0014] Failed to create node 'k3d-mycluster-server-0'
ERRO[0014] Failed to create node
ERRO[0014] Error response from daemon: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown
ERRO[0014] Failed to create cluster >>> Rolling Back
INFO[0014] Deleting cluster 'mycluster'
INFO[0014] Deleted k3d-mycluster-server-0
INFO[0014] Deleting cluster network '59275b244928c7f7aea159077836aeb0a607f666567dff29800eafc6b8f6de5e'
FATA[0014] Cluster creation FAILED, all changes have been rolled back!

And here's a basic docker command:
sudo docker run -it fedora
Unable to find image 'fedora:latest' locally
latest: Pulling from library/fedora
c7def56d621e: Pull complete
Digest: sha256:d6a6d60fda1b22b6d5fe3c3b2abe2554b60432b7b215adc11a2b5fae16f50188
Status: Downloaded newer image for fedora:latest
docker: Error response from daemon: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown.
ERRO[0019] error waiting for container: context canceled

Docker does look like it's having issues on cgroups v2 and that is what's fouling up k3d. And k3d needs root access, which k3x in Flatpak doesn't have, right?
Anyway, I guess we just need to wait for k3d to get podman support and then hopefully everything will "magically" work, even on cgroups v2, possibly even rootless. :grin:

Not sure how things work in Silverblue, but you would need to be part of the right group for accessing /var/run/docker.sock. Once you fix that, you should be able to run k3d without sudo.
But besides that, this OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown message is really concerning. But it is strange because there must be some way to run Docker in Silverblue...

But it is strange because there must be some way to run Docker in Silverblue...

Running Docker in Silverblue is basically called podman, as it's docker-compatible clone of Docker, but with additional features (such as being able to run it as a user without root privs). Docker (Moby) hasn't been ported to cgroups v2 yet, so it only works for basic commands and not running containers (which is the important part of course :wink:).

Running Docker in Silverblue is basically called podman, as it's docker-compatible clone of Docker, but with additional features (such as being able to run it as a user without root privs). Docker (Moby) hasn't been ported to cgroups v2 yet, so it only works for basic commands and not running containers (which is the important part of course wink).

Yeah, but the important thing here would be to have a Docker-like API that the go docker client library could use. AFAIK, podman does not provide this, so it think it will not be possible to add support for podman in the near future. The solution I was proposing was to run the real-thing in Silverblue, but I don't know if that is possible or not...

Podman does actually provide a Docker-like API in Podman 2.0. https://podman.io/blogs/2020/07/01/rest-versioning.html
I think the API docs have the docker-compatible API under "compat" @ https://docs.podman.io/en/latest/_static/api.html (podman also has its own API to do additional things like handle pods)
I saw in a comment elswhere on GitHub that getting a podman service up an running is as running:
podman system service --time=0 &
export DOCKER_HOST=unix:/$XDG_RUNTIME_DIR/podman/podman.sock

That's for running podman without requiring root (in a user session), as it references $XDG_RUNTIME_DIR.
For system containers, it's:
sudo podman system service --time=0 &
export DOCKER_HOST=unix:/run/podman/podman.sock

To start up the service and specify a special URI, such as the Docker URI:
sudo podman system service --time=0 unix:/var/run/docker.sock

There are docs for podman system service.

Thanks for the clarification @garrett. Maybe it would be worth adding all this information in the k3d issue, as this is something that does not really need to be supported by k3x but by k3d...

@inercia: Thanks! Right, it should be talked about there. I copy/pasted/edited the comment to move it there.
Additionally, while podman support might just get Silverblue support working, there might be some additional issues due to the immutable filesystem and perhaps not having system packages. In other words, solving podman support will probably solve Silverblue support (but not ncessarily). That's why I opened up multiple issues. We could close this one and just assume podman support will make it on Silverblue or keep both open until we see what happens with podman.
Thanks again for your effort for on k3x and these issues! (I'm looking forward to being able to try it out someday.)

I got this same traceback on Fedora Kinoite (Silverblue KDE) 35 running under moby-engine.  It is most certainly not due to podman or a cgroups problem as shown below:
$ flatpak run com.github.inercia.k3x
GI search path:
[PRE-MAIN]  [search-path] - /usr/lib/x86_64-linux-gnu/girepository-1.0
[PRE-MAIN]  [search-path] - /app/lib/girepository-1.0
[PRE-MAIN]  [search-path] - /app/lib/girepository-1.0
[PRE-MAIN] Current LD_LIBRARY_PATH: /app/lib:/app/lib/x86_64-linux-gnu:/lib64:/lib:/usr/lib64:/usr/lib:/usr/local/lib
2022-04-13 22:00:09,131 [MainThread  ] [DEBUG]  [MAIN] Creating settings manager...
2022-04-13 22:00:09,139 [MainThread  ] [DEBUG]  Creating settings in delayed mode...
2022-04-13 22:00:09,140 [MainThread  ] [INFO ]  Changing loglevel to 20
2022-04-13 22:00:09,140 [MainThread  ] [INFO ]  [MAIN] Using icon /home/tidux/.var/app/com.github.inercia.k3x/cache/icons/app.svg
2022-04-13 22:00:09,140 [MainThread  ] [INFO ]  [MAIN] Starting appindicator.Indicator
2022-04-13 22:00:09,158 [MainThread  ] [INFO ]  Creating/recreating docker client with DOCKER_HOST=unix:///var/run/docker.sock

(k3x:2): Gtk-CRITICAL **: 22:00:09.259: gtk_entry_set_text: assertion 'text != NULL' failed
Traceback (most recent call last):
  File "/app/bin/k3x", line 62, in <module>
    sys.exit(main.main(VERSION))
  File "/app/share/k3x/k3x/main.py", line 139, in main
    _indicator = Indicator(version=version)  # NOTE: assign for keeping the object alive
  File "/app/share/k3x/k3x/main.py", line 113, in __init__
    self._keybinder = Keybindings(self._settings, self._shortcuts)
  File "/app/share/k3x/k3x/keybindings.py", line 85, in __init__
    self._keybinder = SystemHotkey(check_queue_interval=0.01)
  File "/app/lib/python3.7/site-packages/system_hotkey/system_hotkey.py", line 614, in __init__
    self.conn = xcffib.connect()
  File "/app/lib/python3.7/site-packages/xcffib/__init__.py", line 527, in __init__
    self.invalid()
  File "/app/lib/python3.7/site-packages/xcffib/__init__.py", line 559, in invalid
    raise ConnectionException(err)
xcffib.ConnectionException: Connection closed, error during parsing display string.
$ ls -l /var/run/docker.sock
srw-rw----. 1 root docker 0 Apr 13 21:55 /var/run/docker.sock
$ groups
tidux wheel docker
$ docker run -it alpine cat /etc/os-release
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
df9b9388f04a: Pull complete
Digest: sha256:4edbd2beb5f78b1014028f4fbb99f3237d9561100b6881aabbf5acce2c4f9454
Status: Downloaded newer image for alpine:latest
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.15.4
PRETTY_NAME="Alpine Linux v3.15"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"
$


Local run

Do we get it down to one simple command like npm test?

@emmenko and @yanns WDYT?

@daliwali thx for the hint - yes, it works without the path.

:+1:


feature request: class-based views support.

for some things, such as integration with DjangoRESTFramework, it would be nice if, in addition to the @inertia('ClientSidePage') decorator, support for class based views could be added.
My recommendation is to provide a mix-in (as shown here), which might be used like this:
from django.views import View
from inertia import InertiaMixin

class AsdfView(InertiaMixin, View):
    component = "Asdf"

    def get(self, request):
        return { "message": "asdf" }

If you're careful, then the mixin could function by internally decorating each method function with @inertia("Asdf") - though bear in mind these method functions take the View instance as the first arg, so chaperoning the mixin is necessary.

@method_decorator(inertia("User"), name='dispatch')

This works instead. :/ my bad guys lol

also when that doesn't work (due to the dispatcher expecting response objects returned in some contexts), you can still decorate the methods directly
from django.views import View
from inertia import inertia

class AsdfView(View):
    @method_decorator(inertia("Asdf"))
    def get(self, request):
        return { "message": "asdf" }

Considering that the latter be inconvenient, perhaps a mixin to make this easier would still be a good idea.

I think a mixin for class based views makes sense, but I don't have enough DRF experience to know offhand what it would look like. I definitely take a look when I have some time, but if you already have an idea about how it would structured that would be great to discuss here.

The generic way to do this would be to add middware to Django's dispatch function, though that doesn't seem to work in all cases, as the dict type Inertia allows returned from views isn't technically a Response object, which some Django libraries expect. We'd have to convert it into an inertia response before they see it (which is why without mixins manually decorating functions works but decorating the class doesn't)
I wrote some experimental code a bit ago to add specific support for DRF to django-inertia, but considering that it must import things from DRF, I'm not sure if that code should go in this package, or in a different package.
Full DRF support would mean that inertia views using DRF for (de)serialization and validation would have to catch DRF errors (they all inherit from one abstract class) and provide an API so they can be in shared, and likely boxed, component props. My code didn't even provide a way to use DRF's ViewSet feature, or their extension to Django's permission system. Then comes the special case of replying with inertia for HTML mimetype requests and inertia requests, but falling back to DRF otherwise (for public APIs)
TLDR: while DRF should be kept in mind, specific support for DRF would be very complicated.

Also, when digging around in DRF and Django source, I remember seeing a class property that is an enumeration of the available http method methods on the implementation. If that's part of Django itself, iterating over that list and internally using the decorator I demoed a few comments ago would work in all cases.


Component hooks will trigger family hooks before first configuration is finished for a given entity

Not sure if this is the intended behaviour, but it seems strange to me. For example, lets take this case, a simple component:
data class HealthComponent(
    var initialHealth: Int = 10,
    var health: Int = initialHealth
) : Component<HealthComponent> {
    override fun type() = HealthComponent

    companion object : ComponentType<HealthComponent>() {
        private val LOG = logger<HealthComponent>()
    }

    override fun World.onAdd(entity: Entity) {
        if (entity hasNo HealthBarComponent) {
            LOG.info { "adding health bar for entity with hitpoints because it was not present" }
            // configure is called
            entity.configure {
                entity += HealthBarComponent()
            }
        }
    }
}

When I create my entity....
val enemyEntity = world.entity {
            it += EnemyComponent()
            it += HealthComponent(enemyStats.getStartingHitpoints()) // configure is called again, inside
        }

and I have such a hook:
// inside configureWorld
val enemyFamily = family { all(EnemyComponent) }
onAdd(enemyFamily) {
    LOG.info { "spawned enemy" } // will always run twice in a row, once for world.entity and once after entity.configure
}

The hook will trigger twice, because when configure runs inside the health component, the entity already has an enemy component. I know why this is the case and I can obviously circumvent it knowing this, but I'm not sure if this is very intuitive to the user and maybe a bit error prone (I didn't run into this issue for Fleks 1.6)? It seems more intuitive if the family hooks trigger only when an entity has been added to the world with "world.entity" and not whenever a configuration is run.

Imo family hooks also need to run after configure because obviously the component configuration can change after configure is called and therefore the entity will be removed or added from/to families.
However, if I understand you correctly you call configure within a world.entity block and here I'd agree that it should only run once at the end.
Why do you think it should not get called after configure?

One more remark: I personally would not add a component inside a component hook. That feels like a design flaw imo. I personally would create an extension function for the EntityCreateContext e.g. that configures Health and HealthBar together. That way you don't forget to add both components and it is also easier to  follow the code because it happens together within a single method and you avoid the multiple hook notifications.
Just an idea 😉

no activity for couple of days ... reopen if you have feedback again ;)

@marcphilippebeaujean-abertay: I will merge a PR soon that should optimize the notifications. Please try it out via the SNAPSHOT version and let me know if that solves your issue.

Hi Quill, sorry I did not reply earlier because I went away for a bit.
| Why do you think it should not get called after configure?
I thought the main purpose of families was to be notified when an entity with a specific set of components was removed or created in the world, not whenever the configuration of those entities changed (this is what component hooks were for, at least from my understanding). If that is not the design philosophy, I feel like such a feature would be good to have because I think there is definitely a purpose for listening to specific create/remove events on the entity level, rather than just components.
I agree that avoiding nested configure calls is a good idea, but like you mentioned often it is not done on purpose. The configuration context is interesting, I am not sure if something like this is mentioned in the wiki actually it's great to be made aware of this!
Thanks for your awesome work, the library is great - will check out the PR.

I thought the main purpose of families was to be notified when an entity with a specific set of components was removed or created in the world, not whenever the configuration of those entities changed (this is what component hooks were for, at least from my understanding). If that is not the design philosophy, I feel like such a feature would be good to have because I think there is definitely a purpose for listening to specific create/remove events on the entity level, rather than just components.

This is not entirely correct. The purpose of a family is to store entities of a specific component configuration internally in order for us to iterate over those entities e.g. inside an IteratingSystem.
Since entity.configure is manipulating the components of an entity, it also must notify families about it because after the configuration is done, the entity can be part of new families and also can be removed from families where it currently is inside.
So we definitely need both notifications for families. One notification when an entity gets created and another notification whenever the components of an entity get changed.
Anyway, the new SNAPSHOT version should reduce the amount of notifications always to one which should help in your case. But as mentioned above, I'd vote for the extension method that I showed above which makes it easier to follow your  code and also removes the duplicated notifications.


Unable to install manually

I tried to install it manually in v49, but it seems that the dungeon never spawn on titans and there's no cfg file under the config folder, I wonder wether you will update the mods or not

The mod has been updated for v49, make sure you have all the dependencies and that the mod doesn't have any errors in the console on launch


URLEncoding went missing - fixed

This part went missing somehow.

Coverage decreased (-1.1%) to 66.463% when pulling 449455b9273e4cf0559da62983acd89ca36e50b9 on urlencoding into 259950410d3e8f0ea33761ed366413b03fd659ef on master.


Defer vesting timeout action in separate trx

This makes it independent from fails of neighbour actions

PR #701


500 is returned when CentralDogma server is closed

We have received reports that 500 is returned when CentralDogma is closing.
While we can't do much about requests that ignore health checks, we can try to reduce the count of such requests.
One hypothesis I have is that watch requests return a 500 before returning.

When ProjectManager#close is called, watch requests are shut down with a ShuttingDownException at the following location:
https://github.com/line/centraldogma/blob/54205bfcee1167f84bc1ab1a69e08fa0c3e3f2f3/server/src/main/java/com/linecorp/centraldogma/server/internal/storage/repository/git/GitRepository.java#L374
https://github.com/line/centraldogma/blob/54205bfcee1167f84bc1ab1a69e08fa0c3e3f2f3/server/src/main/java/com/linecorp/centraldogma/server/CentralDogma.java#L935
It might be worth shutting down the server first before ProjectManager#close is called so that HTTP2 connections are shut down with a GOAWAY, and close the ProjectManager afterwards
https://github.com/line/centraldogma/blob/54205bfcee1167f84bc1ab1a69e08fa0c3e3f2f3/server/src/main/java/com/linecorp/centraldogma/server/CentralDogma.java#L990

On second thought, returning ShuttingDownException probably propagates the server status to clients so it might be better to keep the current shutdown order.
Instead, we could return a 304 NOT_MODIFIED instead of a 500 when translating ShuttingDownException.
Additionally, we may optionally also want to let users configure a graceful shutdown period after setting the health check to false.
https://github.com/line/centraldogma/blob/54205bfcee1167f84bc1ab1a69e08fa0c3e3f2f3/server/src/main/java/com/linecorp/centraldogma/server/CentralDogma.java#L328


Google Analytics Input step

Hello,
Here are 3 changes I am using since a while and are simplificating my life.
I hope they are done the right way.
Thanks

This pull request is no longer valid


Feature request : Filter for (response size - payload size)

Hello there,
Thanks for the amazing work,
My request would be to implement a filter (and a result property, named for example "relative size") to sort out behavior when payloads are simply reflected in the HTTP response from payloads that cause an unexpected behavior from the server and thus an strange response with a size different from "generic" relative size (response size minus payload size,
Of course this feature would be a bit niche (but very useful for fuzzing code injection vulns with a payload directly reflected on the page when not working).

Are you referring to calculating the size of the fuzzed keyword and then normalizing the response size?
Normal response size (example): 200 bytes
Normalized Response Size = Response Size - Keywords Size
Example:

For keyword 'ABC' (3 bytes): 200 bytes - 3 bytes = 197 bytes
For keyword 'ABC123' (6 bytes): 200 bytes - 6 bytes = 194 bytes

If a keyword appears multiple times, subtract its size for each occurrence.
This approach makes sense; however, a significant issue arises when fuzzing common keywords that are always present, such as 'img', 'a', and 'title'.
There are also concerns with other keywords or additional terms that were not introduced by the keyword you are fuzzing but were already present in the response.
Performing a pre-flight request and storing the response might address this issue, but it could significantly impact the fuzzing speed as well as CPU and memory usage since you need to calculate sizes and pre-stored keywords.
Is this what you meant?

Yes that's exactly what I mean,
I'm aware of the

Thank you for the answer,
Yes that's exactly what I mean,
I don't understand issues you are mentioning though,
I my mind you would only do "response size (R) - keyword size (W) = normalized response size (N) "(W could be computed when loading the keyword from the wordlist) and return N inside the result table as a new column,
Users could then also use filters on N to find outlier values which could indicate a server weird behavior/malfunction/vuln,
Like this you don't need to parse the words inside the response and compare them to a preflight response,
This "static" approach has its drawbacks because it assumes the server will only reflect the keyword once in the majority of responses but it would need a lot less resources and would be quite easier to implement,
For an "upgrade" of this feature you would have multiple options for a more dynamic behavior:

Use preflight queries for every request (very resource intensive)
Use preflight queries only on a sample of requests to calibrate a function that would determine the relation between K and R (better but that doesn't seems trivial)
Let the user specify the relation between K and R when launching the FFUF command line (ie with a flag "--response-normalized 2W" (=response length - keyword length * 2) or even better with a static part "--response-normalized 2W-10" (=response length - keyword length * 2 - 10) or "--response-normalized 2W+10" (=response length - keyword length * 2 + 10)

For me the last one is the best option but I think I am getting ahead of myself and implementing the "static" behavior with an additional result column and filters would already be very cool !

A well defined request, but I’m going to throw in a curve ball; did you
know you can use the keyword in regex filter? To accomplish same result you
could have a regex filter with something like "FUZZ”
On Sun 28. Apr 2024 at 11.44, Aetiuss @.***> wrote:

Thank you for the answer,
Yes that's exactly what I mean,
I don't understand issues you are mentioning though,
I my mind you would only do "response size (R) - keyword size (W) =
normalized response size (N) "(W could be computed when loading the keyword
from the wordlist) and return N inside the result table as a new column,
Users could then also use filters on N to find outlier values which could
indicate a server weird behavior/malfunction/vuln,
Like this you don't need to parse the words inside the response and
compare them to a preflight response,
This "static" approach has its drawbacks because it assumes the server
will only reflect the keyword once in the majority of responses but it
would need a lot less resources and would be quite easier to implement,
For an "upgrade" of this feature you would have multiple options for a
more dynamic behavior:

Use preflight queries for every request (very resource intensive)
Use preflight queries only on a sample of requests to calibrate a
function that would determine the relation between K and R (better but that
doesn't seems trivial)
Let the user specify the relation between K and R when launching the
FFUF command line (ie with a flag "--response-normalized 2W" (=response
length - keyword length * 2) or even better with a static part
"--response-normalized 2W-10" (=response length - keyword length * 2 - 10)
or "--response-normalized 2W+10" (=response length - keyword length * 2 +

For me the last one is the best option but I think I am getting ahead of
myself and implementing the "static" behavior with an additional result
column and filters would already be very cool !
—
Reply to this email directly, view it on GitHub
https://github.com/ffuf/ffuf/issues/779#issuecomment-2081394813, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH6DJPFYBE2HMZQS5PMICDY7SZF7AVCNFSM6AAAAABG3PJKVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGM4TIOBRGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It's no curveball but the contrary if the feature I want already exists haha,
Though I am sorry if I don't understand but here I don't ask for the occurrence of the keyword inside the response,
What I am trying to do is find inconsistencies in the server behavior by looking at the repartitions of the responses lengths compared to the keyword length,
For 3 responses with the keyword inside 2 could only reflect it and the third could reflect it with additional characters showing the server may have interpreted an OS command for example,
That is why looking at the lengths of those elements is interesting,
Maybe I am missing your point and there is a way to do regex with the individual sizes of responses and keywords ?

Thanks for clearing that up. I do see the value, and it might get added in the future.

Jumping in here - response reflection and relative sizing would be a handy indicator especially in cases where the output is encoded in the result.
For example, if you're fuzzing looking for an XSS vulnerability but the output is using output scrubbing as a defence mechanism which you're trying to get around - you could graph the  "response size (R) - payload size (W) = normalized response size (N)" metric to see any outliers where the encoding behaviour may be misbehaving leading to a vulnerable condition.
This kind of statistical analysis is part of the reason for pull #771 Once the bulk run data is available, we can start to figure out what other metrics are useful in the vulnerability hunting space and start to roll those into FFUF directly.


pass --enable-source-maps flag to task script node command usage

Per Gregor's recommendation

@qwadratic will add this tweak in his next PR

lets reopen and merge )))


[WIP] Share this store on Twitter

Twitter Share Button on Home tab

@hoffmabc Since this is been kind of dormant for a while, can we close this PR and potentially re-vive it after we go through the aforementioned design phase?

I think you misspelled never. Sure that’s fine.


Aur complains about PGP

==> ERROR: One or more PGP signatures could not be verified!

Are you trying to install the AUR package? If yes, try running gpg --recv-keys 701DE74D84F87EE1BC91CD216E656AC5B97B5133.

Yes and thanks

Nope still complaining.
I use the AUR package for a while without trouble. The signature must have changed with the last release.

I've merged a pull request recently and I see that that commit has no signature... Will fix!

Could you please try again?

Perfect. Works fine again. Thanks for the fast fix


Clean up usage of name and key in source code

Make the source code cleanly differentiate between names (the raw name for a tensor, dataset, script, or model) and keys (the potentially prefixed version of the name that is used to reference it in the database).

Codecov Report

Merging #213 (a30d1f8) into develop (cc18c2a) will not change coverage.
The diff coverage is 98.27%.

@@           Coverage Diff            @@
##           develop     #213   +/-   ##
========================================
  Coverage    82.45%   82.45%
========================================
  Files           50       50
  Lines         2838     2838
========================================
  Hits          2340     2340
  Misses         498      498

Impacted Files
Coverage Δ

src/cpp/client.cpp
87.28% <98.27%> (ø)

include/client.h
100.00% <0.00%> (ø)

include/srexception.h
24.13% <0.00%> (ø)


dealing with profiles in script tags.

I am looking at the JSON-LD docs and specifically at
https://www.w3.org/TR/json-ld/#iana-considerations
I use your package as part of my tool that pulls JSON-LD documents from pages.   We look for the tags like
<script type="application/ld+json>....</script>

However, if we had people start to use profiles like in
<script type="application/ld+json;profile=http://www.w3.org/ns/json-ld#frame">

Would an implementation like
doc.Find("script[type='application/ld+json']").Each(func(i int, s *goquery.Selection) {...})

still find / match on the second example above?   I guess the question is, is the stuff beyond the ; ignored with respect to Find?

Hello Douglas,
The string you pass to doc.Find is a CSS selector, which is a web standard. What you want in this case, I think, is to find a script that has the type attribute that starts with the application/ld+json string. You can achieve this using script[type^=application/ld+json] selector (more info about the various supported attribute selectors here: https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors#syntax.
Here's an example program that shows this in context:
const data = `
<body>
	<script type="application/ld+json;profile=http://www.w3.org/ns/json-ld#frame">"js";</script>
</body>
`

func main() {
	doc, err := goquery.NewDocumentFromReader(strings.NewReader(data))
	if err != nil {
		log.Fatal(err)
	}

	fmt.Println(doc.Find("script[type^='application/ld+json']").Text())
}

Hope this helps!
Martin

@mna Thanks!   I'll work up a test and try it but this does sound like what I need.
Appreciate the help!

Sounds good, feel free to reopen if you have follow-up comments/questions (or of course open a new issue if needed).


Slow terminal

Issue Type: Performance Issue
Terminal takes 62s to start, while windows cmd only takes 12s.
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18999

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz (4 x 2095)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
5.95GB (1.98GB free)

Process Argv

Screen Reader
no

VM
0%

Issue Type: Performance Issue
I have a system where I need to start an .exe file, it takes 61 seconds to boot into the terminal, whereas in windows cmd it only takes 12 seconds.
 Changing terminal.integrated.rendererType might help, but the additional slowness may be attributed to additional overhead of going via node or https://github.com/microsoft/vscode/issues/74620

@Tyriar Excuse me, it really is milliseconds. But it's still a perfomace problem, I'll take a look at what you mentioned.


issue #2201: another strategy to gather descriptors to delete

Can you explain what this change does and why? If it's about performance, please post before and after numbers.

Can you explain what this change does and why? If it's about performance, please post before and after numbers.

Hello. I've added benchmark poll_2k_ping_pongs that exactly describes issue. I run it via old and new versions within both release (-O3 -DNDEBUG) and 'release-with-debuginfo' configurations (-O2 -g -DNDEBUG)
and obtained next numbers :
26300-29600 roundtrips for version 'before'
27000-33000 roundtrips for version 'after'.
Besides if you run callgrind for a given benchmark in 'old' version , you will see crucial part of code with 98% of 'instruction reads'.
Furthermore, it is possible to continue investigation by changing UV_LINUX_MAX_EVENTS_TO_LISTEN and UV_LINUX_EVENT_REPEAT_POLL_COUNT but i hasn't done it yet.
All changes are applied currently for linux only, have no way to check how it will work on other systems.

related commit:
https://github.com/libuv/libuv/commit/bbccafbe704090e294481d95f73862bc83f33026
why do someone want to reopen other fd from callback at all?

I think the scenario is you might close a tcp handle in a prepare handle and create it again in some other handle's read callback for example. Not an explicit action, but an accidental one.

I think the scenario is you might close a tcp handle in a prepare handle and create it again in some other handle's read callback for example. Not an explicit action, but an accidental one.

Seems given usecase is not relevant anymore.  We just remove manually 'bad' events from epoll's obtained ones, while more robust way is just deregister file descriptor from event poll that was added later in
https://github.com/libuv/libuv/commit/780d8ad8e58c675dc60f5b73ea22a203760da2f2. I mean, when 'prepare' is called the list removed_events (in my commit) or 'enevts' in older commits is garanteed to be empty. The only case when it is nonempty is when handle is closed from another 'poll' callback since this list is always reinitialized inside uv__io_poll. And latter one is a really weird use case. Why do someone wants to close fd from poll that belong to another fd? Now i vote instead of adding optimization is to just remove that 'events' array. And do not support such use cases anymore.


Bump Carbon Kernel Version

This PR bumps the carbon-kernel version from 4.10.18 to 4.10.19

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/10367663398

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/10367663398
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/10367764385

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/10367764385
Status: failure


CMD+B doesn't work on table names nor column names in REFERENCES clause.

It should!

Verified fixed in 1746d8130f940ecc7ffd5bec139f1b1dea44dde3

Is #616 then also solved?

we dont generate that constant any more so that issue can be closed as well 👍


Step 39 missing IOM provider transformer child flow name

Step 39. Missing child flow connector name to mention "IOM Provider Transformer"
39. Select Add an action within the Apply to each loop, add Run a child flow from the Flow connector, and rename it "Transform Message with Power Query Online".

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

ID: 37cf6c99-4619-09f6-ad94-6d59dc574d33
Version Independent ID: 12d529fe-2bfa-2999-daa1-fb637435ce9e
Content: Create intake provider
Content Source: topics/lab-create-intake-provider.md
Service: dynamics-365-intelligent-order-management
GitHub Login: @josaw1
Microsoft Alias: josaw

I ran into the same issue.  What I did was I navigated back to Flows and looked up the flow for "IOM Provider Transformer" and noticed that it was turned OFF so once I turned it ON I then was able to see and select the "IOM Provider Transformer" flow from the Child Flow drop down list. I would assume you would need to turn on any other flows required for this lab exercise.

Once I turned on the flow it was then visible for selection.

Thanks for the comments. @raybennett-msft can you please review this and determine whether updates to the article are needed?

Submitted PR with fix, please review and then @josaw1 you can close.


Disabling pull-to-refresh on FlatList causes all items to be re-created

🐛 Bug Report
When disabling pull-to-refresh in a FlatList by setting onRefresh to undefined every item in the list gets unmounted and recreated.
I looked into why this would be happening and it appears to be because of this code in ScrollView: https://github.com/facebook/react-native/blob/f741d338406d518c4f81fada723991b2938b8cc5/Libraries/Components/ScrollView/ScrollView.js#L1082-L1120
To Reproduce

Add a FlatList with some data and onRefresh and refreshing set to valid values
Change onRefresh and refreshing to undefined

Expected Behavior
The item components already rendered should be reused
Code Example
https://snack.expo.io/@maxschmeling/disrespectful-toffee
Environment
  React Native Environment Info:
    System:
      OS: macOS 10.14.3
      CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
      Memory: 8.02 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 11.3.0 - ~/.nvm/versions/node/v11.3.0/bin/node
      Yarn: 1.13.0 - /usr/local/bin/yarn
      npm: 6.9.0 - ~/.nvm/versions/node/v11.3.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    IDEs:
      Android Studio: 3.1 AI-173.4907809
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: ^16.8.3 => 16.8.4
      react-native: ^0.59.0 => 0.59.0
    npmGlobalPackages:
      react-native-git-upgrade: 0.2.7

Hey, we've confirmed this is an issue. I think I have an idea on how to fix it for iOS (we need to move the platform check to the inside of ScrollViewClass so we don't re-mount it), but it may get trickier on Android (need to investigate).
I'm gonna work on this later today, but if anyone wants to take a stab at it, please do so :)

@thymikee Please correct me if I'm wrong, but with the current implementation of <ScrollView /> changing any of its props will trigger re-render of the children.

While fixing this on iOS seems like a straight-forward job, avoiding unmounting on Android might not be doable without the support of re-parenting in React https://github.com/facebook/react/issues/3965.
SwipeRefreshLayout requires us to wrap the ScrollView with it, and from the React perspective, it will always invalidate the tree.
Perhaps we could always wrap ScrollView with SwipeRefreshLayout, and conditionally disable it, but it doesn't seem like a good idea.


minimal updates regarding plugin_info to pyproject

Minimal changes to correct informations on the existing documentation parts involving plugin_info.toml to remplace it with pyproject.toml

thx Loic


Error handling in Purchase()

The Purchase function in order.go has instances of silently ignored errors. For example,
n.Wallet.AddWatchedScript(script)

and
n.Datastore.Purchases().Put(orderId, *contract, pb.OrderState_CONFIRMED, true)

and
refundAddr := n.Wallet.CurrentAddress(spvwallet.EXTERNAL)

In the last example, the function CurrentAddress intentionally discards the error, which seems strange given the important of the refund address:
 addr, _ := w.rpcClient.GetAccountAddress(account)

For the line n.SendOrder(contract.VendorListings[0].VendorID.Guid, contract), the only error check is err != nill to determine "Vendor offline". This is a bit blunt.

I'll look into them

@cpacia is this issue still open?

It turns out openbazaar-go has many errors that are ignored throughout the repository. There are various tools to help you find such instances, e.g. https://github.com/kisielk/errcheck. Actually, I would run the whole repo under https://github.com/alecthomas/gometalinter to find low-hanging bugs.

Have you done that?

All errors should always be handled. If you find some that are not please feel free to patch it or start a discussion on how to best handle the failure if it's not straightforward.


Catch BadImageFormatException

Description
The ConvertFormat.To<> method fails if there are .dll or .exe files with invalid assemblies in the same folder where Yarhl.dll is located.
Capturing BadImageFormatException when loading the assemblies, we can skip those files.

The CI script is broken and it doesn't trigger on fork PR. I tested locally too.


Is database file contents deterministic?

If you create two different redb databases and perform the same sequence of inserts and deletions, will the two files be byte-for-byte the same?
If not, it might be nice to try to guarantee that they will be the same. We recently did a bunch of optimization work on ord, and it looked like the same operations could produce index.redb that contained the same keys and values, but which were not byte-for-byte identical. If they were identical, we could have done a byte-wise comparison of the before- and after-optimization databases, to ensure that the same databases were produced.

yes, I think it should be. There's no sources of randomness used. At least at the moment though, there are some additional things you would need to do for it to be exactly identical:

group them into the same transactions
order any read transactions the same way (reads allocate a transaction id at the moment)
ensure that they go through the same crash recovery, or always shut down redb cleanly: ensure drop is called on the Database.

Gotcha. In that case we wouldn't have gotten the exact same contents, because we changed the way writes are batched, but good to know for the future.

Ah, ya that's never going to produce bitwise identical files then. Page garbage collection happens when you commit a transaction, so changing that will change the pages that data gets allocated into


bounding boxes

Hi and thanks for releasing the code!
From the visualizations that I generated during training an inference, I realised that the box that is used to cropped the image to obtain a person which is given as input to the model at train and test time is not tight around that person and sometimes include other people in the image as well. Could you please let me know the reason?
Thanks!

During our GT preparation, we did bbox expansion by a factor of 1.2 (you could check relevant code here). So that for inference, the bboxes should be slightly larger than the original GT bbox. Sometimes you may see a larger bbox that include other people.
This scaling process is adopted from GraphCMR (CVPR 2019) implementation.
Further, during the training, we perform training data augmentation which will randomly scale the bbox a bit larger/smaller. Thus, the bbox may not be tight around the person.

Please re-open this thread if you encounter relevant issues or bugs. Thank you.


ISPN-11580 Change Stopping cache manager log message to info

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

@diegolovison It seems like you have changed the "starting" log message :slightly_smiling_face:

Thanks!

Merged, thanks @diegolovison !


Delay in opening datetimepicker popup on clicking the calender widget.

Hi Team,
I am using the datetimepicker bootstrap for displaying date and time. But when the number of datetimepicker is increased its opening very slow.
Below is the snapshot -

As i am increasing the number of datetimepicker  its getting delayed in opening. So can you please provide me solution for this issue.
Thanks in advance
Regards
Atul kumar

please try v4. It's been greatly improved over v3

where i can dl the v4?

https://github.com/Eonasdan/bootstrap-datetimepicker/tree/v4beta


deployment issues

Hello,
After adding some more photos lately I have noticed that the deploy is no longer functioning as expected. I also did an upgrade recently of the theme. Any idea what the issue could be? If anything I am happy to redeploy from a fresh version.
Thanks.
2:51:13 PM: Error: Error building site: failed to render pages: render of "home" failed: "/opt/build/repo/layouts/index.html:19:17": execute of template failed: template: index.html:19:17: executing "index.html" at <partial "gallerydeluxe/init.html" (dict "sourcePath" "images")>: error calling partial: "/opt/build/cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/bep/gallerydeluxe@v0.9.3/layouts/partials/gallerydeluxe/init.html:8:18": execute of template failed: template: partials/gallerydeluxe/init.html:8:18: executing "partials/gallerydeluxe/init.html" at <partial "gallerydeluxe/create-thumbs.html" .>: error calling partial: "/opt/build/cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/bep/gallerydeluxe@v0.9.3/layouts/partials/gallerydeluxe/create-thumbs.html:3:9": execute of template failed: template: partials/gallerydeluxe/create-thumbs.html:3:9: executing "partials/gallerydeluxe/create-thumbs.html" at <.Resize>: error calling Resize: this method is only available for image resources

Thanks! It turned out to be an Apple HEIC extension that it didn't like. I had only 1 photo that was added on there.
Awesome support my friend.
Thanks,
recycleleash


ReverseBinaryEncoder should not preserve the ordering of fields within IonStructs

ReverseBinaryEncoder that reverse-encodes the DOM should not preserve the ordering of fields within IonStructs, unless the field name SIDs are already sorted in ascending order (which would set the "ordered-bit-flag").
Currently this is not possible because it will fail a large amount of test cases that does strict checks on the ordering of fields within structs.
Imported from ION-358,IONJAVA-20

No guarantee of ordering.


no error when folder has no compressed files

Closes #320.

Removes the error (and web hook/command hook) for folders with no compressed files in them.

This is now in unstable for anyone that wants to test.


nixos/gdm: use systemd tmpfiles instead of preStart

Motivation for this change
Thet was a mess before. This should be more reliable.
Things done

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

[ ] NixOS
[ ] macOS
[ ] 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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

For ref the syntax https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html.

@GrahamcOfBorg test gnome3


Add FU to /om command

It's just the OMotM...

It's just the OMotM...

I've already seen questions about it, with a /om entry it's easier to find this, but feel free to just close it

I've already seen questions about it, with a /om entry it's easier to find this, but feel free to just close it


fix(browser)!: default to Chromium channel for new headless mode

BREAKING CHANGE: Updated chrome_channel to chromium to fix compatibility with the new Chromium headless implementation. This resolves the error playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found, caused by the removal of the old headless mode in Chromium.
With this change, channels like "chrome" now default to the new headless mode, aligning with upstream updates in Playwright v1.49.0 The new headless mode uses the real Chrome browser, offering more authenticity, reliability, and feature parity with the full browser.
Additionally, simplified fallback logic by directly assigning chrome_channel based on browser_type or defaulting to chromium.
Refer to:

https://playwright.dev/python/docs/browsers#chromium
https://github.com/microsoft/playwright/issues/33566

close #352, close #377

Environment Details
Python Version
python --version
Python 3.12.7

Installed Packages and Host System Information and Playwright Installation Output

Installed Packages
pip list
Package                   Version
------------------------- ----------
aiofiles                  24.1.0
aiohappyeyeballs          2.4.4
aiohttp                   3.11.11
aiosignal                 1.3.2
aiosqlite                 0.20.0
annotated-types           0.7.0
anyio                     4.7.0
attrs                     24.3.0
beautifulsoup4            4.12.3
certifi                   2024.12.14
charset-normalizer        3.4.1
click                     8.1.8
colorama                  0.4.6
distro                    1.9.0
fake-http-header          0.3.5
filelock                  3.16.1
frozenlist                1.5.0
fsspec                    2024.12.0
greenlet                  3.1.1
h11                       0.14.0
httpcore                  1.0.7
httpx                     0.27.2
huggingface-hub           0.27.0
idna                      3.10
importlib_metadata        8.5.0
iniconfig                 2.0.0
Jinja2                    3.1.5
jiter                     0.8.2
jsonschema                4.23.0
jsonschema-specifications 2024.10.1
litellm                   1.56.4
lxml                      5.3.0
MarkupSafe                3.0.2
mockito                   1.5.3
multidict                 6.1.0
numpy                     2.2.1
openai                    1.58.1
packaging                 24.2
pillow                    10.4.0
pip                       24.3.1
playwright                1.49.1
pluggy                    1.5.0
propcache                 0.2.1
pydantic                  2.10.4
pydantic_core             2.27.2
pyee                      12.0.0
pytest                    8.3.4
pytest-mockito            0.0.4
python-dotenv             1.0.1
PyYAML                    6.0.2
rank-bm25                 0.2.2
referencing               0.35.1
regex                     2024.11.6
requests                  2.32.3
rpds-py                   0.22.3
sniffio                   1.3.1
snowballstemmer           2.2.0
soupsieve                 2.6
tf-playwright-stealth     1.1.0
tiktoken                  0.8.0
tokenizers                0.21.0
tqdm                      4.67.1
typing_extensions         4.12.2
urllib3                   2.3.0
xxhash                    3.5.0
yarl                      1.18.3
zipp                      3.21.0

Host System Information
hostnamectl
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.0-25-arm64
    Architecture: arm64

Playwright Installation Output
playwright install
Downloading Chromium 131.0.6778.33 (playwright build v1148) from https://playwright.azureedge.net/builds/chromium/1148/chromium-linux-arm64.zip
165.1 MiB [====================] 100% 0.0s
Chromium 131.0.6778.33 (playwright build v1148) downloaded to /home/test/.cache/ms-playwright/chromium-1148
Downloading Chromium Headless Shell 131.0.6778.33 (playwright build v1148) from https://playwright.azureedge.net/builds/chromium/1148/chromium-headless-shell-linux-arm64.zip
103 MiB [====================] 100% 0.0s
Chromium Headless Shell 131.0.6778.33 (playwright build v1148) downloaded to /home/test/.cache/ms-playwright/chromium_headless_shell-1148
Downloading Firefox 132.0 (playwright build v1466) from https://playwright.azureedge.net/builds/firefox/1466/firefox-debian-12-arm64.zip
82.8 MiB [====================] 100% 0.0s
Firefox 132.0 (playwright build v1466) downloaded to /home/test/.cache/ms-playwright/firefox-1466
Downloading Webkit 18.2 (playwright build v2104) from https://playwright.azureedge.net/builds/webkit/2104/webkit-debian-12-arm64.zip
87.9 MiB [====================] 100% 0.0s
Webkit 18.2 (playwright build v2104) downloaded to /home/test/.cache/ms-playwright/webkit-2104
Downloading FFMPEG playwright build v1010 from https://playwright.azureedge.net/builds/ffmpeg/1010/ffmpeg-linux-arm64.zip
1.6 MiB [====================] 100% 0.0s
FFMPEG playwright build v1010 downloaded to /home/test/.cache/ms-playwright/ffmpeg-1010

Run Tests
pytest tests/async/test_basic_crawling.py

Test Execution before changes
========================================= short test summary info =========================================
FAILED tests/async/test_basic_crawling.py::test_successful_crawl - playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found at /op...
FAILED tests/async/test_basic_crawling.py::test_invalid_url - playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found at /op...
FAILED tests/async/test_basic_crawling.py::test_multiple_urls - playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found at /op...
FAILED tests/async/test_basic_crawling.py::test_javascript_execution - playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found at /op...
FAILED tests/async/test_basic_crawling.py::test_concurrent_crawling_performance - playwright._impl._errors.Error: BrowserType.launch: Chromium distribution 'chrome' is not found at /op...
===================================== 5 failed, 11 warnings in 3.14s ======================================

Test Execution after changes
=========================================== short test summary info ===========================================
FAILED tests/async/test_basic_crawling.py::test_concurrent_crawling_performance - assert False
================================== 1 failed, 4 passed, 43 warnings in 19.60s ==================================

Conclusions

Opt-In to the New Headless Mode

Moving to the new headless mode is essential for maintaining compatibility and benefiting from the improved testing reliability it offers.

Screenshot Differences

This PR does not address changes in screenshot expectations but is a first step towards adapting to the new headless mode.
After completing necessary testing, it would be prudent to release a new version.
It is recommended to incorporate CI testing (e.g., via GitHub Actions) to ensure a smooth user experience before merging PRs.

Optimize Playwright Installation

Given our default scenario of browser_type="chromium" and headless=True, i could recommend using:

playwright install --no-shell to reduce download size for most cases.
playwright install --only-shell when the old headless mode is required.

Additionally, including --with-deps (e.g., playwright install --with-deps) during installation might help reduce user issues by ensuring that all necessary system dependencies for browsers are installed. For example, in some environments (like mine), running this command was essential for proper browser operation.

Recommendations for Further Steps

Test the changes thoroughly, especially in scenarios involving screenshots and GPU/WebGL usage.
Consider updating documentation to reflect the new installation options and configurations for the new headless mode.
Provide a migration guide for users to adapt to the changes effectively.


middleware/auto improve zone handling

Currently one has 2 options:
Option 1:
Have only one auto section such as:
    .:5053 {
      auto {
        directory /etc/source/files/zones/ (.*) {1} 30
        transfer to *
        transfer $provider_1
        transfer $provider_2
      }
    }

Option 2:
Add all zones served manually such as:
    .:5053 {
      auto production.example.com {
        directory /etc/source/files/zones/prod/ (.*) {1} 30
        transfer to *
        transfer $provider_1
      }
      auto development.example.com {
        directory /etc/source/files/zones/non-prod (.*) {1} 30
        transfer to *
        transfer $provider_2
      }
    }

Option 1 notifies both providers of updates and in general seems like the wrong solution.
Option 2 isn't really worth having the auto directive as one has to add all zones manually anyway.
Various solutions:

bundle directory and transfer so only notifies to the right provider are done
load zones from files instead of manually having to declare them
let auto be chained basically it would run throught the first auto section for provider_1, if nothing is found it would use the section for provider_2 and if nothing is found it would SERVFAIL.

Shouldn't we just look at the NS records in the zones to infer upstreams?
On 17 Feb 2017 1:33 pm, "Michael Grosser"<EMAIL_ADDRESS>wrote:

Currently one has 2 options:
Option 1:
Have only one auto section such as:
.:5053 {
  auto {
    directory /etc/source/files/zones/ (.*) {1} 30
    transfer to *
    transfer $provider_1
    transfer $provider_2
  }
}

Option 2:
Add all zones served manually such as:
.:5053 {
  auto production.example.com {
    directory /etc/source/files/zones/prod/ (.*) {1} 30
    transfer to *
    transfer $provider_1
  }
  auto development.example.com {
    directory /etc/source/files/zones/non-prod (.*) {1} 30
    transfer to *
    transfer $provider_2
  }
}

Option 1 notifies both providers of updates and in general seems like the
wrong solution.
Option 2 isn't really worth having the auto directive as one has to add
all zones manually anyway.
Various solutions:

bundle directory and transfer so only notifies to the right provider
are done
load zones from files instead of manually having to declare them
let auto be chained basically it would run throught the first auto
section for provider_1, if nothing is found it would use the section for
provider_2 and if nothing is found it would SERVFAIL.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/miekg/coredns/issues/532, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVkW_x1Apgax-wu4D6LKaYYvJh1mYKJks5rdaGbgaJpZM4MERW0
.

Instead of providing transfer to $provider_ip you want to use the NS record?
That would mostly not work as the notify receiving and AXFR/IXFR servers of most providers are completely separated from their record serving servers, which would be the IPs you get back from using the NS record.

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/coredns] middleware/auto..." ]

Instead of providing transfer to $provider_ip you want to use the NS record?
That would mostly not work as the notify receiving and AXFR/IXFR servers of most providers are completely separated from their record serving servers, which would be the IPs you get back from using the NS record.

Hmmm, good point.

We're contemplating the syntax for a language to allows filtering in #469. What you need IMHO is a specifier that takes the zone into account and then sets the upstream for notifies etc. Or maybe ticked off on where the zonefile lives, i.e. take the directory name into account.
transfer ${f:/non-prod/) to <something>

or something like that.

This would enable:

catch-all zone
paritioned notifies + transfers

Sounds like a better solution than fall through for this use-case.

transfer <file/path-regex> to
most consistent would be the use of basepath instead of a regex, but that might limit usage.
basepath:
transfer /non-prod/ to <IP_ADDRESS>

regex style:
transfer *dev* to <IP_ADDRESS>


codes

When will the code of your article be released?

@LYL1946734397 Hi, I have updated.

@LYL1946734397 Thank you for your attention to my work. I apologize for the late update due to some things that happened some time ago.


Get material propertise by material name

I am working on a plug-in for Grasshopper to generate Idea StatiCa RCS models.
I would like user to generate concrete or rebar materials just by referring to its name, instead of providing all strength characteristic.
I have found that while specifying material I can use LoadFromLibrary variable; however, it does not seem to work.
In my example, I am trying to get Eurocode Concrete Class C12/15; however, in IOM xml I get Material with this name and all characteristics set to zero.
Firstly, I set settings for european (even though, they are default):

Secondly, I am trying to set the material by name and LoadFromLibrary to true:

Finally, I am assigning this material to cross-section:

As a result I got this in the xml file with IOM:

I understand that this issue is similar to idea-statica/iom-examples#57
I am using Idea StatiCa version 22.1.
I would be grateful if you could tell me what shall I do to make it work

This error is now resolved in v23.1. A new RCS API has also been developed. https://developer.ideastatica.com/docs/api/rcs/rcs_api_getting_started.html?tabs=dotnet


There Seems To Be No Way of Creating a Multipage Table Starting On Existing Page

According to your integration test, the way to draw a multipage table is:
/* builder details here */
.draw(() -> document, () -> new PDPage(PDRectangle.A4), 50f);

But this seems to call a new page for every section of the table. On the other hand, if I list an existing page, the table will just overwrite the same page. Would it be too hard to provide a function or class that takes two PDPage objects? The first would be the initial page the table starts in. The second would be a constructor for any table overflow (preferably, the new pages would be inserted in between existing pages if, for example, you wanted a table to be inserted in a document on page 2, with the document already containing 3 pages).  For example:
/* builder details here */
.draw(() -> document, () -> existingPage, () -> new PDPage(PDRectangle.A4), 50f);

Of course, in the meantime, I would've just overridden the RepeatedHeaderTableDrawer class myself while waiting for official patch, but as was mentioned in a prior issue ( #29 ), there's a lot of data hiding that stifles this.

Hi @snorhax, thanks for sharing your thoughts. You are right that there is a shortcoming here. It is also connected with https://github.com/vandeseer/easytable/issues/44, because if the issue you mentioned was resolved already that could be as well (at least partially).
The thing is: I do not have enough time right now to come up with a proper fix. Chances are rather low that I will implement this in the next two or three weeks. But I am always willing to accept pull requests ;) So please feel free to come up with a solution that fits your needs (for instance implementing the method with three parameters as proposed) and I will be happy to merge it.
If you have a bit more patience I will most likely implement a solution by my own. But that will take a bit (maybe in a month or so).

Of course, in the meantime, I would've just overridden the RepeatedHeaderTableDrawer class myself while waiting for official patch, but as was mentioned in a prior issue ( #29 ), there's a lot of data hiding that stifles this.

If Possible can you please share your fix? Many thanks.

Added a Pull Request that fixes the issue for me
https://github.com/vandeseer/easytable/pull/46/files

Thanks a lot for your pull request @styssi :+1:
I will release a new version shortly containing this change.

Fix is included in v0.5.1


Adds a constructor to provide a custom socketFactory.

Adds new constructor methods to provide a custom SocketFactory, if we don't want to use the cacerts truststore or the one pointed to by property  javax.net.ssl.trustStore.

This was merged awhile back.


TestCases for 3.2.1 Scenario

Purpose
Added testCase - <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>

Closing as there are conflicts. Please fix conflicts and resend the PR.


Fix list-prs-for-file (hopefully)

Try pasting this in the console:
JSON.parse(document.querySelector('[data-target="react-app.embeddedData"]').innerText.trim()).payload.path;

Test URL: https://github.com/Significant-Gravitas/Auto-GPT/blob/master/Dockerfile
My fix is based on this.
Not sure how to test, as Local Overrides don't work for extensions.
Closes #6299

Please include test URLs in your first post

Sorry, editing from my browser as it seemed such a simple fix..

I actually specifically downloaded the extension for this feature. It would be really useful in sorting out the PR tsunami in https://github.com/Significant-Gravitas/Auto-GPT :')

I believe you're referring to Xcode/Safari, which is a pain to test.

I was trying to test in Chrome using a Local Override to edit refined-github.js, but that didn't work.

What's a Local Override?

A way to edit source files of a website and preserve the edits through page reloads.

Oh you're talking about the chrome dev tools feature
https://www.debugbear.com/blog/devtools-local-overrides
Yeah you'd need to build the extension locally instead

FYI I don't have the time to fix this feature in the extension right now, so I'm going to fix this for myself by writing a simple shell script that uses the GraphQL API.

No worries, thanks for trying

Result:
#!/bin/bash
if [ -z "$1" ]; then
  echo "Usage: list-prs-for-path PATH [branch]";
  echo "Lists all PRs touching files starting with PATH";
  exit 1;
fi

branch=${2:-$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')}

echo "Querying PRs to branch $branch touching paths starting with '$1'";

response=$(gh api graphql -f query="query {
  repository($(gh repo view --json 'name,owner' --template 'owner: "{{.owner.login}}", name: "{{.name}}"')) {
    pullRequests(
      first: 100,
      states: OPEN,
      baseRefName: \"$branch\",
      orderBy: {
        field: UPDATED_AT,
        direction: DESC
      }
    ) {
      nodes {
        number author {
          login
        }
        title updatedAt url
        files(first: 100) {
          nodes {
            path
          }
        }
  } } }
}")

errors=$(jq -r '.errors' <<< "$response")

if [ ! "$errors" = "null" ]; then
  echo "GitHub API Query returned errors: $errors" >&2;
  exit 1;
fi

# # uncomment for debugging:
# jq -r '.' <<<"$response"

jq -r --arg path "$1" '.data.repository.pullRequests.nodes[] | select(.files.nodes | map(select(.path | startswith($path))) | length > 0) | {
  number: .number, title: .title, author: .author.login,
  updatedAt: .updatedAt,
  url: .url,
  filesChanged: .files.nodes | map(.path)
}' <<< "$response"

Fixed in https://github.com/refined-github/refined-github/pull/6578

It required a near-total rewrite because GitHub is making large changes to the UI


Find the best parameters for bp_osd under different situations

A guide on how to choose the different options for bp and osd (e.g. "bp_method", "osd_order", ...) could be useful for when we have a given experiment (i.e. noise type, noise level, number of QEC cycles, ...).
Use the insight from Roffe's presentation in Benasque 2024.

Create a benchmarking directory (or something like this) that stores these studies. This will help users in the future. I could even have some defaults for different codes that can be imported with this repo.


When Prometheus can be used vue.js ？

Thanks for your report. It looks as if this is actually a question about usage and not development.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

Thanks!


Closing running Tensorboard

As a user, I want to be able to stop an already running Tensorboard

For running multiple tensorboard, this implementation at jupyter_tensorboard/tensorboard_manager.py might be a good practice.
Maintaining multiple tensorboard by processes is not very efficient and hard to manage.

Hi, thanks for your proposal. Have you experienced any troubles with the current implementation? (Yes, it is not perfect, but I am trying to figure out if it makes sense to change it now)

Thank you for your reply.
In fact, the frontend is okay for using even if it is implemented in process-style.
I am just worried about running too much tensorboard in the background, which might overload my computer. And I cannot know how many tensorboard threads have been running there.


Performance issue with content hash

Large file can cause program to briefly freezes

Switching the hash to xxhash would fix this: https://github.com/jungomi/xxhash-wasm


What will be our Mantra (slogan of our company)?

Ex:
Requirement: No more than 9 words and it needs to make consumers remember us

Nike: "Just do it"
Peter: "If it works, don't touch it"
Senior Well Comp: ?

It has to be something short like 2-3 words as the video steve played said.
Here is a list of them:
"Empowering Care, Enriching Lives."
"Together in Care, Always There."
"Supporting the Journey of Aging with Grace."
"Compassionate Connections, Lasting Comfort."
"Care with Dignity, Life with Love."
"Guiding You to Better Days, Every Step of the Way."
"Nurturing Well-being, One Day at a Time."
"Where Care Meets Compassion."
"Dedicated to Every Moment of Comfort."
"Caring for the Heart, Body, and Mind."
Just some options to choose from.

This is a good one
"Empowering Care, Enriching Lives."


RemoteAgent uses async

Currently we separate out act over two methods in the RemoteAgent: send_obs() and recv_act(). We can simplify this if we use async.
class RemoteAgent():
    async def act(obs):
        # ...
        return act

Also add a new helper to AgentSpec: build_remote_agent() that will create an instance of RemoteAgent.

Used concurrent.futures to combine synchronous send_observation() and recv_action() methods into one asynchronous task act() which returns a concurrent.futures.Future object.
This issue is addressed by pull reqeust #138 .


remove deployment sidecar disconnect Easier to understand

I think it's easier to understand
This code is not necessary
			deps := []appsv1.Deployment{}
			deps = append(deps, *dep)
			return unInjectSideCarFromDeployment(client, deps, args[0], ns, writer)

It is easier to understand by changing it to the following way
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[x] Developer Infrastructure

Hi @ClareChu. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

@googlebot I signed it!

/ok-to-test

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

integ-galley-k8s-tests_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test integ-galley-k8s-tests_istio

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. I understand the commands that are listed here.

/test release-notes_istio
/test integ-galley-k8s-tests_istio

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test integ-galley-k8s-tests_istio

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

/test release-notes_istio

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

/test release-notes_istio

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

/test release-notes_istio

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

/test release-notes_istio

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

/test release-notes_istio

@ClareChu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

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. I understand the commands that are listed here.

@ClareChu: PR needs rebase.

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.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-ipv6-k8s-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test analyze-tests_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
12f2f321b364fb9183cc49b1cb7c1e31060b83e6
link
/test release-notes_istio

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test analyze-tests_istio

gencheck_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test gencheck_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test analyze-tests_istio

gencheck_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test gencheck_istio

release-notes_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-notes_istio

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. I understand the commands that are listed here.

@ClareChu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-multicluster-k8s-tests_istio

integ-security-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-security-k8s-tests_istio

integ-operator-controller-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-operator-controller-tests_istio

integ-distroless-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-telemetry-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test analyze-tests_istio

gencheck_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test gencheck_istio

release-notes_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test release-notes_istio

lint_istio
b819ed11cf5413533bc8cc0f361036939b2e787a
link
/test lint_istio

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. I understand the commands that are listed here.

/hold