Error with graph and mdreport after upgrading to 0.4.7

Updating to 0.4.7 solve my issue with solidity parser but I have now other issues.
As you can see in this commit it doesn't produce graph because I receive the following error Error: <stdin>: syntax error in line 1 near '{' and in mdreport it changed the file hash with [object Promise].
To reproduce run
npx surya graph dist/SampleContract.dist.sol | dot -Tpng > analysis/control-flow/SampleContract.png
npx surya mdreport analysis/description-table/SampleContract.md dist/SampleContract.dist.sol

I can't see a problem with the mdreport command, runs fine for me:

About the graph command, yes! Absolutely!  Pushing a fix right now.

Yes. If I force use v0.4.6 it works but not for v0.4.7 or v0.4.8.

hmmm, I really don't know what's happening 🤷

Will try to understand. I have this issue in all my repos with 0.4.8.


Freezes when trying to make a table with a large number of rows

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
I'm trying to make something like a Hex Viewer, apparently, this only works with a small number of lines, since the window just freezes. Is there any way to make a table?
Originally used the iced_aw widget grid so I asked them first. It was explained to me that this is some kind of problem inside iced, I tried the following code right in the tour example:
fn scrollable() -> Column<'a, StepMessage> {

        let test_addr_line   = vec!["adress column 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F ascii_ASCII_ascii".to_string(); 4500];
        let test_hex_line   = vec!["01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F".to_string(); 4500];
        let test_ascii_line   = vec!["ascii_ASCII_ascii".to_string(); 4500];

        let test_row = column![
            column(
                test_addr_line
                    .iter()
                    .cloned()
                    .map(|line| {
                      text(line).size(10)
                    })
                    .map(Element::from)
                    .collect()

            ),

        ]
        .padding(10)
        .spacing(10);

        Self::container("Scrollable")
            .push(
                "Iced supports scrollable content. Try it out! Find the \
                 button further below.",
            )
            .push(
                "Scroll test",
            )
            .push(test_row)
            .push(
                text("Tip: You can use the scrollbar to scroll down faster!")
                    .size(16),
            )
            .push(
                text("You are halfway there!")
                    .width(Length::Fill)
                    .size(30)
                    .horizontal_alignment(alignment::Horizontal::Center),
            )
            .push(ferris(300))
            .push(
                text("You made it!")
                    .width(Length::Fill)
                    .size(50)
                    .horizontal_alignment(alignment::Horizontal::Center),
            )
    }

What is the expected behavior?
The text table is a must have for any gui. Tables contain the logic of a very large number of applications.
I would like to know if this can be fixed and how
Version
master
Operative System
Windows
Do you have any log output?
No response

You can draw Widget inside Scrollable, drawing only rows inside a viewport. In my case freezes are gone(i've tested 10k elements).

Working example:
pub struct TableContents<Message> {
    item_height:f32,
    contents:Vec<Vec<String>>,
    on_double_clicked: Box<dyn Fn() -> Message>,
}

impl <Message>TableContents<Message> {
    pub fn new(item_height:f32,
        contents:Vec<Vec<String>>,
                on_double_clicked:impl Fn() -> Message + 'static
    ) -> Self {
        Self {item_height,contents,on_double_clicked:Box::new(on_double_clicked)}
    }
}

pub fn table_contents< Message>(item_height:f32,
    contents:Vec<Vec<String>>,
                              on_double_clicked:impl Fn() -> Message + 'static) -> TableContents<Message> {
    TableContents::new(item_height,contents,on_double_clicked)
}

impl<Message:std::clone::Clone> Widget<Message, iced::Renderer> for TableContents<Message>
{
    fn width(&self) -> Length {
        Length::Fill
    }

    fn height(&self) -> Length {
        Length::Fill
    }
    fn on_event(
        &mut self,
        _state: &mut Tree,
        event: iced::Event,
        layout: Layout<'_>,
        cursor_position: Point,
        _renderer: &iced::Renderer,
        _clipboard: &mut dyn Clipboard,
        _shell: &mut Shell<'_, Message>) -> Status {
        Status::Ignored
    }

    fn draw(
        & self,
        _state: &widget::Tree,
        renderer: &mut iced::Renderer,
        _theme: &iced::Theme,
        _style: &renderer::Style,
        layout: Layout<'_>,
        _cursor_position: Point,
        viewport: &Rectangle,
    ) {
        use iced_native::text::Renderer as text_renderer;
        let mut viewport_layout_y=(viewport.y-layout.bounds().y);
        let mut end_y=viewport.y+viewport.height;
        let mut number_of_element=(viewport_layout_y/self.item_height) as i32;
        let mut element_bounds=Rectangle{x:layout.bounds().x, y:(self.item_height*number_of_element as f32)+layout.bounds().y, width:layout.bounds().width, height:self.item_height};
        let mut contents=self.contents.clone();

        while element_bounds.y<end_y{
            let mut rectangle_bounds=element_bounds;
            if element_bounds.y+element_bounds.height>end_y {
                rectangle_bounds.height=end_y-element_bounds.y;
            }

            renderer.fill_quad(
                renderer::Quad {
                    bounds: rectangle_bounds,
                    border_radius: Default::default(),
                    border_width: 0.0,
                    border_color: Color::WHITE,
                }, Background::Color(if number_of_element % 2 == 0 { COLOR_LIGHTER } else { COLOR_DARKER })
            );

            let mut text_bounds=element_bounds;
            text_bounds.y=element_bounds.center_y();
            if let Some(itemvec)=contents.get(number_of_element as usize) {

                if itemvec.len()==1{
                    text_bounds.x=element_bounds.center_x();
                    renderer.fill_text(
                        iced_native::text::Text {
                            content: itemvec[0].as_str(),
                            bounds: text_bounds,
                            size: 20.0,
                            color: Color::WHITE,
                            font: Font::Default,
                            horizontal_alignment: Horizontal::Center,
                            vertical_alignment: Vertical::Center,
                        }
                    );
                }else{
                    text_bounds.width/=itemvec.len() as f32;
                    for item in itemvec.iter(){;
                        renderer.fill_text(
                            iced_native::text::Text {
                                content: format!("  {}",item.as_str()).as_str(),
                                bounds: text_bounds,
                                size: 20.0,
                                color: Color::WHITE,
                                font: Font::Default,
                                horizontal_alignment: Horizontal::Left,
                                vertical_alignment: Vertical::Center,
                            }
                        );
                        text_bounds.x+=text_bounds.width;
                    }
                }

            }
            element_bounds.y+=element_bounds.height;
            number_of_element+=1;
        }
    }

    fn layout(&self, renderer: &iced::Renderer, limits: &Limits) -> Node {
        layout::Node::new(Size{
            width: limits.max().width,
            height:  self.item_height*((self.contents.len()) as f32)
        })
    }

}

impl<'a, Message> From<TableContents<Message>> for Element< 'a,Message, iced::Renderer>
    where Message:'a,
          Message:std::clone::Clone
{
    fn from(table_contents: TableContents<Message>) -> Self {
        Self::new(table_contents)
    }
}

Sry if this code is bad, im new in rust. But it works without any freezes. One question to maintainers: how can i calculate item_height inside this widget, if i wanna draw only 7 rows in one view? Only way that i see requires viewport data inside layout method.

https://user-images.githubusercontent.com/60794504/220211354-d3590ac2-be07-4e38-8fda-536c89e9d165.mov
10k elements table

My Cargo.toml:
iced={version="0.8.0",features=["default_system_font","image","debug"]}
iced_lazy= "0.5.0"
iced_native="0.9.1"
iced_graphics = "0.7.0"
iced_futures = "0.6.0"

Works! I had an old version of iced, 0.7.
Thanks, I struggled with this for a long time, great, zbs.

Hey, I had the same issue in my app, so I created this small library to fix it! Although this component isn't finished, it's still usable.
iced-flatlist

Hey, I had the same issue in my app, so I created this small library to fix it! Although this component isn't finished, it's still usable. iced-flatlist

This is great! Will have to try. I did something too https://github.com/Kuraga13/usbdm_mc56f_rs/blob/master/src/gui/hexbuffer_widget.rs

I'll try to bump the version of my component, it uses an older version of iced. When I click your link it goes nowhere, maybe it is set to be private?

Ok I will wait. Link corrected

Alright, bumped iced version to 0.8.0


chore: release main

:robot: I have created a release beep boop
dev-dependencies-client: 4.1.11
4.1.11 (2024-02-04)
Bug Fixes

bump to latest common deps (6a28d3a)

dev-dependencies-server: 3.0.11
3.0.11 (2024-02-04)
Bug Fixes

bump to latest common deps (6a28d3a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aversini/dev-dependencies/releases/tag/dev-dependencies-client-v4.1.11 :sunflower:

:robot: Release is at https://github.com/aversini/dev-dependencies/releases/tag/dev-dependencies-server-v3.0.11 :sunflower:


Link in announcement pop-up not working

On my Android phone I have activated the 'Push Notifications' and I received the 'subscribed' message.
I have just published an announcement (Contributor Day Details) and received the pop-up. When clicking on that pop-up it tries to open https://app.wp-europe.org/contributor-day-details/ and that does not seem to work.
(Has to see with redirection or something else ??? Just guessing)

Duplicate of https://github.com/frontity/wordcamp-theme/issues/61.
It's already solved, but not on production yet. Probably tomorrow.


[Offline sync] Add ability to purge SQLite store operations

https://github.com/Azure/azure-mobile-apps-js-client/commit/66630d50ca915f9b0387def10fc0fe3017c896a1 closes https://github.com/Azure/azure-mobile-apps-js-client/issues/38


Mobile navbar disappears on mobile while scrolling

While scrolling on the mobile version of the site, the navbar disappears and then reappears. This only occurs on the homepage due to Bootstrap's "affix" functionality

Excellent work, @allejo !

wait wait this one hasn't been fixed yet! I do have a fix in mind for it though if you want the PR


add ability to write secrets for amplify app

what
Amplify can access secrets during build and runtime
This PR allows the
why
It may be useful depending on a user's secrets management pattern to write secrets here when creating the amplify app.
references
https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#environment-secrets
fixes #31

/terratest

/terratest

@kevcube, why can't a secret be written externally based on the module's outputs after the Amplify app is created?

@kevcube, why can't a secret be written externally based on the module's outputs after the Amplify app is created?

It can be written externally, if someone wants to use remote-state or something to grab the amplify ID that's an option, but because amplify has the ability to access secrets stored at these predefined paths I thought it made sense to package in this  module because they can be considered a part of the amplify application stack

/terratest


missing file "Vcl.Clipboard.Files"

hi,
where can i find the missing file: Vcl.Clipboard.Files.pas?

Hello, the missing file Vcl.Clipboard.Files.pas has been added.
https://github.com/ps147258/ImagesPackegViewer/blob/main/Vcl.Clipboard.Files.pas
or
https://github.com/ps147258/ImagesPackegViewer


Star Crossed Futures: Split FutureWithSession into 2.11 and 2.12 versions.

This adds proper support for transform(Try) and transformWith to 2.12,
while leaving 2.11 without unsupported operation exceptions. Also split
the specs so that we can test the two new 2.12 methods.

@pdyraga care to have a look since these are your baby?

All perfect 👌

:100: going to merge this next opportunity if I don't hear anything then!


make error compatible with hardhat-chai-machers

so it's more compatible with hardhat out of box, otherwise we will need to manually import '@nomiclabs/hardhat-waffle' and install extra pkgs;

it needs to be similar to Ethereum

Yeah I think our error format is already same as eth
{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -32000,
        "message": "some error msg"
    }
}

but hardhat matchers looks for error.data instead, not sure how it works for eth, need more digging
https://github.com/NomicFoundation/hardhat/blob/e92b6b7b90032e380d43919b11a0d7a61f093ff6/packages/hardhat-chai-matchers/src/internal/reverted/utils.ts#L29

oh actually eth do have a error.data field

closed by #756


Atomic bomb add uranium

About the PR
The "nuclear bomb" cocktail now adds uranium to the body rather than radium.
Why / Balance

Because uranium is used to create the cocktail
It makes sense for the antagonists to hack into the alcohol distributor in order to get uranium.

[ ] This PR does not require an ingame showcase

Changelog

tweak: A nuclear bomb adds uranium to the body, not radium

Please try updating to master to see if it fixes the failed test.

All tests completed successfully ＼(^ω^＼)

Changelog should probably better reflect that the drink is what's being modified.

I was changed it

Looks good, thanks.


Improve the message title

Hi, when I use the OSSChat to receive messages, the message looks like:

Actually, the PR number (#***) and the PR title is more meaningful than the repo name "apache/incubator-iotdb".
So, it is better to put the latter info ahead of the title.
How do you think?

Please feel free to submit a Pull Request to change the template at here:
https://github.com/kaiyuanshe/osschat/blob/a0a83cff30b8a7aafc646e6365b85769fb1928e2/src/issue-handlers.ts#L35-L39

I believe this feature should be online now after we merged the two PR from @jixuan1989

This feature has been implemented.


Create CI Pipeline

Hello, based on https://github.com/nitin-787/mynotes/issues/68, this adds a workflow for testing the project at every push to main branch, as the issue doesnt go in depth of what this project needs about workflows, we have a success condition based at project's own written tests.

Hello, based on https://github.com/nitin-787/mynotes/issues/68, this adds a workflow for testing the project at every push to main branch, as the issue doesnt go in depth of what this project needs about workflows, we have a success condition based at project's own written tests.

Yes I know but the person who the made the pull request at least he should make sure the initial c/cd pipeline works, he just copied the code from some and made pull request

Hello, based on https://github.com/nitin-787/mynotes/issues/68, this adds a workflow for testing the project at every push to main branch, as the issue doesnt go in depth of what this project needs about workflows, we have a success condition based at project's own written tests.

Yes I know but the person who the made the pull request at least he should make sure the initial c/cd pipeline works, he just copied the code from some and made pull request along with that he said he don't have knowledge of flutter and ci/cd pipeline but still I helped him

@nitin-787 Sure, i'm not aiming at anything, just trying to explain what the pipelines achieves :) Take a look and we can work further if needed.

@nitin-787 Sure, i'm not aiming at anything, just trying to explain what the pipelines achieves :) Take a look and we can work further if needed.

Thanks, but I know lil but about ci/cd pipeline


Options to control swift-format

There should be some options to control swift-format that is bundled with the toolchains.
I'm not sure how this'll play with the fact that the formatter is called by sourcekit-lsp, not directly by the vscode extension. Perhaps @ahoppen can enlighten me.
Some possible options:

Option to completely disable swift-format.
Custom swift-format executable path.
Custom arguments to be passed to swift-format.
Custom paths to search for .swift-format.
Option to disable formatting on projects with certain conditions.

For example is there is no Package.swift or if there is no .swift-format file.

Synced to Apple’s issue tracker as rdar://139514618

Option to completely disable swift-format.

What would be the benefit of that? If you don’t want it, you can choose to not invoke formatting. Or am I missing something?

Custom swift-format executable path.

What would be the use case? I would prefer to not add configuration options unless we know that they solve real-world problems.

Custom arguments to be passed to swift-format.

Which arguments would you pass here?

Custom paths to search for .swift-format.

What would be the reason to not have .swift-format in your project root?

Option to disable formatting on projects with certain conditions.

For example is there is no Package.swift or if there is no .swift-format file.

Similar here, when would this be useful?

I would prefer to not add configuration options unless we know that they solve real-world problems.

@ahoppen right. I didn't make these up, I just looked at what options the vknabel formatter extension gives and assumed there are reasons for existence of those options.

What would be the benefit of that? If you don’t want it, you can choose to not invoke formatting. Or am I missing something?

I'm not 100% sure how it plays in VSCode but someone might want to use one of the vknabel extensions and format their Swift files, just not use the swift-extension's formatter. But then you can choose another formatter in VSCode UI so i can get behind not having this option for now.

Custom swift-format executable path.

swift-format is bundled with the toolchains which means it's not updated too frequently. Maybe someone wants to use an updated version of swift-format.

Custom arguments to be passed to swift-format.

Not sure what I'd pass here ... I guess in swift-format's case there may not be too many options to modify (yet?). But I can see this being useful in the future. Maybe there is an experimental flag or something added?
Again, I just grabbed these from the other extension.

Custom paths to search for .swift-format.

I personally don't mind it but the root directory can get pretty crowded with 20 different config files sitting there in the bigger projects. VSCode does show the ./hidden files too in the navigator, unlike Xcode.

Option to disable formatting on projects with certain conditions.

This should be helpful to avoid swift-format running with its default configuration just because no config exists.
Not sure if that's already the behavior and if sourcekit-lsp already requires a config file to exist.
It's been a while i personally haven't used any projects missing a Package.swift, so not sure about that ... I can get behind not having the option for Package.swift, if noone else has a usecase.

For me personally it would be important to be able to disable/enable swift-format's "Format Document" behavior when no .swift-format exists, but still keep Format Selection and on-type formatting.
Because if a project has .swift-format then we're all good, but if it doesn't, I still want to use swift-format, just not to format the whole file, or to accidentally trigger format-on-save, mostly to make sure I don't format whole-files of repos i don't maintain which don't support swift-format.
It could be valuable to have options to disable each of on-type, selection or whole-document formattings only by themselves, when there is no .swift-format.

Thanks for your detailed reply. I don’t think there are any concrete needs for the options you mentioned in the original post and I’d prefer to not add options just for the sake of having more options. If there are use cases that are enabled by the options, I’m happy to add them.

For me personally it would be important to be able to disable/enable swift-format's "Format Document" behavior when no .swift-format exists, but still keep Format Selection and on-type formatting.

I think this option makes sense to add.

If we want to do minimal options for now unless a need appears, then I want to mention that i think Custom swift-format executable path. is also a relatively important one.
It won't be hard to have an outdated swift-format.
We currently use mint to make sure we use the same SwiftFormat version. We'd want to do the same for swift-format as well. Otherwise there can be formatting mismatches and the CI could fail while the local (outdated) formatter has done its best.
This has already happened to us with different SwiftFormat versions. Not hard to happen, specially as swift-format gains more and more options that can subtly conflict in weird scenarios.

It would be great if custom format tool flags could be provided, similar to the options offered by the Go extension. However, I'm not sure whether this option configuration should be provided by sourcekit-lsp or by VSCode-Swift. Personally, I'm not very accustomed to the apple/swift-format tied to sourcekit-lsp; I usually prefer using nicklockwood/SwiftFormat.

@MartinLau7 what flags would you want to provide that you can't now?

As for flags, I hope apple/swift-format could provide a default flag to ignore line breaks,

Ah that's an issue for https://github.com/swiftlang/swift-format if it doesn't already exist.

sourcekit-lsp to provide options to switch between different formatting tools

I'd like that as well to be honest.
@ahoppen do you see a path forward with that?
The only proper way i can think of is swift-format having the actual code to properly call each formatter tool? I'm not sure how we'll be able to make it pluggable, properly.
Maybe if the tools were expected to follow a certain format? Then anyone would be able to just use their tool of liking.
I can see this happening even now. SwiftFormat could add a subcommand which is compatible with how swift-format works, but it can get tricky with no docs or guarantees.

Yes, I think if we want to support arbitrary formatting tools, I think SourceKit-LSP should specify a command line option format that these formatting tools would need to follow – I haven’t checked but I wouldn’t be surprised if such a de-facto standard already exists. The tricky part is passing down options like indentation width (what we currently do here).


Can I use sbus in dronekit?

Previously, I gave a pwm signal to the servo motor to control the Viewpro gimbal camera.
However, I want to convert it to the sbus but I'm not sure how to use it.
Is sbus also controlled with Mavlink messages like servo motors?

Thank you for answer.
Is there a way to transfer to a port such as uart, telem, or i2c?

YOu send MAVLink commands via some radio or IP serial link to do "stuff". Those commands get turned internally into some operation on the flight stack.
MAVLink provides an interface to set arbitrary actuators (or servos) on the main outputs of a flight stack - i.e. that means UAVCAN or PWM.  There is no way to send an arbitrary command to other ports via MAVLink.
To use a gimbal, MAVLink provides the gimbal API. It would be up to a flight stack to decide how the hardware works when it gets one of those commands. Currently flight stacks attach to PWM outputs or a "pure mavlink" for gimbals. So while in theory you might control a gimbal on those other busses you would have to write a driver and gimbal backend to do the work.
So it is kind of "not a dronekit or mavlink question".


Add support for Data Explorer functionality (list, add, cp)

Add a new command:
tw data-explorer

that interacts with the new Data Explorer feature in the Seqera Platform. Some suggested functionality (need to add all the auth syntactic sugar):
tw data-explorer list                                           # lists all data links including custom name, provider, path, type
tw data-explorer list --provider                                # subset to just the specific cloud provider
tw data-explorer list --type [cloud|custom]                     # subset to just the automatic cloud or custom data links
tw data-explorer add                                            # add a custom data link
tw data-explorer cp <data-link> --include <pattern>             # copy/download all objects from the data link that match the defined pattern, similar to the AWS CLI S3 cp command
tw data-explorer cp <data-link>:/path/to/object.txt object.txt  # copy/download a single object from the data link to your localhost
tw data-explorer cp /path/to/samplesheet.csv <data-link>        # upload a file from your localhost to the data link
tw data-explorer cp /path/to/folder <data-link> --recursive     # upload all files in a folder from your localhost to the data link

Presumably tw data-explorer cp downloads to the current working directory? Could be nice to support alternative destinations too.. 🤔  Potentially as a separate tw data-explorer sync command, or a flag, or just a second positional argument..

For me it's a -1. Why bloating the CLI with this?

You could argue that it's not worth having a CLI at all, there's a perfectly good API!
Having it in the CLI makes it faster and easier to work with datasets from the terminal. It improves developer / user experience.

Also the technical reason for having it in the CLI for downloading files:
Presigned URLs expire after a short-ish window (@swampie thought it was 1 hour). If downloading a large dataset, the download could easily run for many hours. A generated bash script would therefore fail, however the CLI could request the presigned URLs one at a time in series, meaning that they're always fresh and continue to work.

Adding a usecase to download/list a dataset, with a flag to download/list the files inside the dataset csv/tsv/table. For example:
tw dataset cp <dataset_id> --files

This downloads the dataset table (csv/tsv) plus the files. In this way the user only has to be concerned with passing around the dataset object, and they can download/list the files at any time.
Note: Today, the auth to access/download/list files in a dataset is not guaranteed as users can create whatever s3:// paths they want in a csv. This issue also exists when launching a pipeline.

Fair enough

for upload and download why using the seqera cli when you can use the standard cloud tooling?

No need to maintain cloud credentials locally
Support multiple compute env types (clouds) with a consistent command and single CLI tool
Download via consistent Seqera identifiers, less risk of sample or file mixup
user experience if we add nice things as suggested by Evan: eg. downloading all data paths within the CSV

Considering the ongoing work to extend the Data Explorer availability to personal workspaces, these new CLI capability should be implemented for those as well.

I agree with Paolo that the complexity is not justified for the time being: open to discuss

Adding a very key point being lost here.
Our end users shouldn't need cloud console or cloud provider CLI access. They likely don't have cloud credentials. This is the point of having different roles with WS admins adding credentials and CEs.
End users want to upload data, run pipelines, and download results.

I agree 💯 that CLI should have first-class support. However, my understanding is that the feature highlighted here does not come for free, it may require some specific endpoints.

Updated original request to match the Data Explorer data-links API endpoint name

I feel a bit weird about naming this subcommand data-links. I've checked the data explorer's UI, and there, you can upload files without any mention of the "data link" concept. And you can create new "data links" also without any mention of that concept. Why should we use this name in the CLI?
The sub-title where you can list your "data links" says, "Browse remote data repositories and data for use in Seqera Cloud," with no reference to this "data link" concept. Overall, this "data link" concept is misleading.
I'd call it "data source", and then the command line can be tw data-source... with tw ds... alias. Also, the tw data-source add ... subcommand would be more meaningful.
But because naming is difficult and what sounds good to me may sound terrible to others, I suggest reviewing this naming before hardcoding it into the command line interface. Or at least,  if "data link" is chosen as the best way of naming it, the web UI should be consistent and call that section "data links" instead of "data explorer" with explicit references to the "data link" concept when you add a new one.

@jordeu Thanks for the feedback! The Data Explorer API endpoint is called data-links and we were being consistent with that. I think it would be more confusing to have the API endpoint named differently to the CLI interface (when both are publicly accessible). I agree that the term "data-link" is widely used internally but not directly surfaced externally. I would be in favor of explicitly referencing that term in our docs, but open to feedback.

@robnewman we are missing here the method to list content

@weronikasosnowskaseqera Please add. I wasn't necessarily comprehensive - just that the functionality needs to exist and reflect the API functionality.

This is now done except for the tw data-link cp command.

tw data-link cp (download/upload) will be handled with another task: https://seqera.atlassian.net/browse/PLAT-289


Automated Package Upgrade

:tada: This PR is included in version 25.3.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Upgrade Neo4j Driver Dependencies to Latest Version

Users of the latest version of the Neo4j driver (4.3.1 at this time) are unable to utilize this product.  Therefore, I recommend upgrading the Neo4j and EnsureThat dependencies to the latest version.

You can use the 4.3.1 version with these extensions.

Hey Charlotte!
Thanks for getting back with me!  I realized that I had not referenced the signed version of the Neo4j driver (Neo4j.Driver.Signed versus Neo4j.Driver).  Very cool extension btw!!!
Cya!
@.D773E4.B949FAD0]Andy Stutz
SW Engineer III
NCR Corporation
Phone: +16785169719
<EMAIL_ADDRESS>|  ncr.comhttp://www.ncr.com/
@.***D773E5.4ABA0910]https://www.facebook.com/ncrcorp  @.***D773E5.4ABA0910] https://twitter.com/NCRCorporation @.***D773E5.4ABA0910] https://www.linkedin.com/company/ncr-corporation @.***D773E4.B949FAD0] https://www.instagram.com/ncrcorporation/?hl=en
From: Charlotte Skardon @.>
Sent: Thursday, July 8, 2021 10:30 AM
To: DotNet4Neo4j/Neo4j.Driver.Extensions @.>
Cc: Stutz, Andy @.>; Author @.>
Subject: Re: [DotNet4Neo4j/Neo4j.Driver.Extensions] Upgrade Neo4j Driver Dependencies to Latest Version (#1)
External Message - Use caution before opening links or attachments
You can use the 4.3.1 version with these extensions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/DotNet4Neo4j/Neo4j.Driver.Extensions/issues/1*issuecomment-876488616__;Iw!!In4Qlw!4koC5NT3CEw-MBRrWNSRynjL-X9i4yM6IgjDyy75wa422dqVPsx1LqrKir3a-xzhGg$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AP5G5MGQTNFQZS7QE4FUHHDTWWY7NANCNFSM5AA2OHYA__;!!In4Qlw!4koC5NT3CEw-MBRrWNSRynjL-X9i4yM6IgjDyy75wa422dqVPsx1LqrKir2RKW2aoQ$.

Make sure to reference the signed version of the Neo4j driver (Neo4j.Driver.Signed versus Neo4j.Driver) in Nuget.


fix links - ci

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Line length guidelines

Wonil-Suh1 created the following on Jan 28:
User story
As a a designer I need guidelines around line lengths and text element size so that I can design consistent experiences.
Deliverables

[ ] finalize line length guidelines (explorations have been done) in Sketch

Original issue: https://github.ibm.com/webstandards/digital-design/issues/495

On Jan 29, Wonil-Suh1 commented:
The line length exploration from Duo is here.

On Apr 12, chsanche commented:
@Wonil-Suh1 We should get Collen or Jill involved in this task.

On Feb 17, chsanche commented:
@Wonil-Suh1 This is awesome. While it's not directly linked, I'd like you to also be aware of the #473. In a high-level, I created the issue bc I noticed many of the CTA labels are long and misleading across the IBM.com and even on our website.

On Jul 22, chsanche commented:
@Wonil-Suh1  Which version of the website is this task for? Thank you.

On Jul 22, Wonil-Suh1 commented:
@chsanche No new contents except comms related will be added to the current site. So this would be for the wedding cake.

On Oct 17, chsanche commented:
Note: @Jeff-Chew we need to migrate this issue to our new repo for prioritization.

The guidelines work has been deferred until resources are available.  The design kit and components will continue.


:sparkles: Feat: Add client status property

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1270  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


guide: cleanup some md links

I noticed the link checker doesn't recognize the ref style links too.

Closing per https://github.com/iterative/dvc.org/pull/2534#discussion_r648853426 as there's no indication that the link checker will support this style of links soon.

Reopening per https://github.com/iterative/link-check/pull/6


Exporter "used memory "not caculate blockcache && rediscache

Is this a regression?
Yes
Description

在打开index_cache_and_filter_cache参数的时候，因为没有计算blockcache会导致算出来的值不准确
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response

@sizhuo


FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/predictions_on_USPTO50K-aug-typed_test-prediction.txt'

After trained the RGN model and averaged the checkpoints, I tried to run bash translate.sh, but got the following error,
(nips) hugy@robotics180:~/RetroXpert/OpenNMT-py/script/USPTO50K-aug-typed$ bash translate.sh
Traceback (most recent call last):
  File "../../onmt/bin/translate.py", line 52, in <module>
    main()
  File "../../onmt/bin/translate.py", line 48, in main
    translate(opt)
  File "../../onmt/bin/translate.py", line 18, in translate
    translator = build_translator(opt, report_score=True)
  File "/home/hugy/miniconda3/envs/nips/lib/python3.6/site-packages/onmt/translate/translator.py", line 24, in build_translator
    out_file = codecs.open(opt.output, 'w+', 'utf-8')
  File "/home/hugy/miniconda3/envs/nips/lib/python3.6/codecs.py", line 895, in open
    file = builtins.open(filename, mode, buffering)
FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/predictions_on_USPTO50K-aug-typed_test-prediction.txt'

Where can we get the file predictions_on_USPTO50K-aug-typed_test-prediction.txt?

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the script python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the script python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the command python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Not sure what's the problem in your case. You are right that prepare_test_prediction.py outputs the src-test-prediction.txt; basically the script takes the bond disconnection predictions from EGAT & generates synthons & smi tokenizes them.
I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the command python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Not sure what's the problem in your case. You are right that prepare_test_prediction.py outputs the src-test-prediction.txt; basically the script takes the bond disconnection predictions from EGAT & generates synthons & smi tokenizes them.
I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the command python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Not sure what's the problem in your case. You are right that prepare_test_prediction.py outputs the src-test-prediction.txt; basically the script takes the bond disconnection predictions from EGAT & generates synthons & smi tokenizes them. This file will be in OpenNMT-py/data/USPTO50K-aug-typed/ folder
I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

You are right. That file is generated by translate.sh.

Please follow the instructions in README carefully.
# Generate synthons for test data according to the bond disconnection prediction in step-1, to do 2-step direct prediction:
python prepare_test_prediction.py  --typed

I have already run the command python prepare_test_prediction.py --typed and also checked the code in the python file, it seems like it only generates the file src-test-prediction.txt instead of predictions_on_USPTO50K-aug-typed_test-prediction.txt.

Not sure what's the problem in your case. You are right that prepare_test_prediction.py outputs the src-test-prediction.txt; basically the script takes the bond disconnection predictions from EGAT & generates synthons & smi tokenizes them. This file will be in OpenNMT-py/data/USPTO50K-aug-typed/ folder
I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

You are right. That file is generated by translate.sh.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

Your error info indicates "FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/", I guess you do not have the directory "experiments/results/". You may create a "experiments/results/" filefolder.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

Your error info indicates "FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/", I guess you do not have the directory "experiments/results/". You may create a "experiments/results/" filefolder.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

Your error info indicates "FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/", I guess you do not have the directory "experiments/results/". You may create a "experiments/results/" filefolder.

It works, thanks for your time.

I ran translate.sh & also inspected the code in detail. I am sure it outputs the predictions_on_USPTO50K-aug-typed_test-prediction.txt file. It will be in OpenNMT-py/experiments/results/ folder.

Did you mean the script translate.sh or translate.py outputs the file predictions_on_USPTO50K-aug-typed_test-prediction.txt? I encountered the FileNotFoundError when I ran the script translate.sh, not after that.

Your error info indicates "FileNotFoundError: [Errno 2] No such file or directory: '../../experiments/results/", I guess you do not have the directory "experiments/results/". You may create a "experiments/results/" filefolder.

It works, thanks for your time.


Use int64 for field.Numeric

In most of the iso8583 specs, amount fields are 12 digits. Currently, field.Numerc is storing value as int, which is max<PHONE_NUMBER> (and it's 10 digits). We should use int64 instead of int.
There are some options for fixing this:

change type for field.Numeric from int to int64 - a breaking change
add new field.BigNumeric 😂 which will accept int64 - looks like an extra complexity

I believe that option 3 is the right one as currently using int for amount fields is a bug and should be fixed.  While it's not a backward-compatible change, it fixes the issue and requires a simple upgrade.
P.S. this change should also support int64 (and *int64) in Marshal/Unmarshal in the field.String and field.Numeric.

Hi @alovak kindly assign this one to me, much appreciated!

What is "Option 3" @alovak? Do you mean option 1?
Thanks for the help @GalihFajar!

@GalihFajar, please join Moov's community Slack here: https://slack.moov.io/ and we can discuss any questions you have in #iso8583 channel as well.

closed by @GalihFajar in #294


Auto padding for sliding boxes and changing cookie setting box size

Is this enhancement or feature is related to a problem?
Since sliding box padding is constant, for a balanced view, especially on mobile devices, it is better to change padding automatically. Doing so also fixes the problem for mobile devices, where the close button may not be visible. (width: 320px)
Describe the solution you'd like
Auto padding referenced to --main-container-margin
Describe alternatives you've considered
none
Additional context
none

done with PR #141


force rerun of all/specific task

forced rerun of specific task implemented with close of #25
force rerun of all deferred to CLI implementation


Update modern-config.js

fix #1338

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

maybe someone could help with the prettier... I don't know whats the error, but also could not run it localy


Use UV_RUN_NOWAIT

This probably solves some things but I don't think this is right. It seems like it would turn the child process into a hardloop that pummels the CPU :/.

What an "interesting" PR.


Use type="number" for postcode and type="tel" for mobile

Bug report

[x] I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I’ve read and agree to the Code of Conduct.
[x] I’ve searched for any related issues and avoided creating a duplicate issue.

Go to examples of text inputs different widths and notice the postcode and mobile fields have type="text" when they should be type="number" and type="tel" respectively.

The for attribute on the label for the postcode on the light theme is does match the id attribute for the corresponding field.

We should probably add rationale around using different text input types for different scenarios, and the benefits that can be achieved by doing this. I.e. the type="number" triggers the number input on mobile devices.

closed by #499


Use SHA256 instead of MD5 when calcualting buildpack mount points

Needs similiar changes on the buildpacklifecycle side
Addresses: https://github.com/cloudfoundry/cloud_controller_ng/issues/3561

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

It was my understanding that the lifecycle_bundles get co-located with the cloud-controller so we just need to make sure both cloud-controller and the diego-release will be bumped at the same time, into cf-deployment (or TAS).

like @philippthun I am leaning more toward keeping things working in existing foundations.  Mostly cause I'm skeptical of keeping things co located. Though I can be convinced if we think most users are using cf-deployment and we want to put the effort on cf deployment getting a release with both this fix and lifecycle bundle fix at the same time

@jochenehret do you think it would be feasible to coordinate the bump of Cloud Controller and Diego so that both would switch to sha256 sums simultaneously?
cc @ameowlia

I'm not into the details, but I would doubt that a simultaneous update to sha256 will work without downtimes. For a seamless update, in a first step the receiver of the message should be able to accept the old md5 plus the new sha256 messages. In the next step, the sender could be switched from md5 to sha256. We could release both steps as major cf-deployment versions so that users are required to install both.

caller and receiver are colocated on the same instance, so they would be updated at the same time if the releases are bumped at the same time (cross-working group coordination effort, between CAPI, Diego & CF-deployment).

Which jobs on which instance_groups are involved here, precisely? Jobs are updated sequentially, so there could still be a small downtime during an update. @philippthun has started to think about solutions and could provide more details.

at this point its just unclear where the lifecycle binary is executed, is it being invoked by the cloud controller directly or is it executed in the diego container during staging and if so where does diego get it from. Are these lifecycle bits uploaded to a blobstore at cloud controller startup and referenced later? or are the bits taken from disk once a staging request comes in.

To be honest, I did not fully understand the workflow yet...
My understanding is that CC creates a message that includes these paths with MD5 or SHA256 checksums and sends this to Diego. Diego spins up a staging container and loads the buildpack_app_lifecycle.tgz from the file-server which seems to run on the api instance-group. So during an update there could be all possible combinations, i.e. new message + old lifecycle, old message + new lifecycle...

When is buildpack_app_lifecycle.tgz uploaded to the file-server? Is this done during cloud_controller start? or is this done every time an app gets staged? Also, are these bundles versioned somehow?

This does not look that hopeful:
==> file_server.stdout.log <==
{"timestamp":"2023-12-19T09:10:55.592678374Z","level":"info","source":"file-server","message":"file-server.ready","data":{}}
{"timestamp":"2023-12-19T09:31:13.834461087Z","level":"info","source":"file-server","message":"file-server.static-file.response","data":{"method":"GET","session":"1","size":58026358,"status":200,"uri":"/v1/static/buildpack_app_lifecycle/buildpack_app_lifecycle.tgz"}}
{"timestamp":"2023-12-19T09:32:18.436372800Z","level":"info","source":"file-server","message":"file-server.static-file.response","data":{"method":"GET","session":"2","size":0,"status":304,"uri":"/v1/static/buildpack_app_lifecycle/buildpack_app_lifecycle.tgz"}}
{"timestamp":"2023-12-19T10:09:46.756621977Z","level":"info","source":"file-server","message":"file-server.static-file.response","data":{"method":"GET","session":"3","size":0,"status":304,"uri":"/v1/static/buildpack_app_lifecycle/buildpack_app_lifecycle.tgz"}}

/var/vcap/sys/log/file_server# jq -r .static_directory /var/vcap/jobs/file_server/config/file_server.json
/var/vcap/jobs/file_server/packages/

The buildpack_app_lifecycle.tgz is "uploaded" during the BOSH deployment, the buildpack_app_lifecycle package is a dependency of the file_server job.
The file server adds an Etag header. Thus the HTTP status code 304 in your log, @rkoster.

Yeah, it seems like it's just serving the whole packages directory. So depending on if the file_server instance has been updated or not by the bosh director it will server to old or the new version of buildpack_app_lifecycle.tgz.

So we need to do this in three steps:

Update buildpack_app_lifecycle to support both (MD5 and SHA256) path variants (see comment).
Switch CC from using MD5 to SHA256 paths.
Update buildpack_app_lifecycle to only support SHA256 paths.

Each step should be done in a major cf-deployment release.
Open question: Do we really want to use a cryptographic hashing algorithm although this is not required?

If step 1 would be implemented with a fallback (only calculate md5 if sha256 based path does not exist). We could get away with 2 deploys.
We might be able to do it with 1 deploy if the file-server URL used by the cloud-controller would point to the instance which has created the staging request. The only downside here is that these request would fail if the instance would get updated.

With regards cryptographic hashing, I'm open to using something like xxhash. Inline with https://github.com/cloudfoundry/cloud_controller_ng/pull/3557

Ideally the use_xxhash_for_buildpack_staging_paths code path could be enable via a cloud controller feature flag.
This way it could option be switched on via a post deploy lifecycle script. Which means all changes could be rolled out in a single deploy.

Ideally the use_xxhash_for_buildpack_staging_paths code path could be enable via a cloud controller feature flag.

Yes, that would be a good shortcut. But we should have this flag only temporarily and remove it together with the obsolete MD5 coding in a subsequent (major cf-deployment) release.

After giving it some more thought, controlling the hashing algorithm via a bosh property cc.staging_buildpack_path_algorithm which would default to xxh64 but would also support md5 for the time being. From the VMware side, we probably would want to keep this option around for at least a year since we can only change the default in our major releases which we do twice a year.

Before bumping this into capi release, the legacy_md5_buildpack_paths_enabled property should be exposed via the release.
@jochenehret When bumping capi release the legacy_md5_buildpack_paths_enabled property should be set to true, until the next major release.

Can we use a more standard algorithm like SHA256 instead? I don't know if speed is of an issue here, but I think using a more known algorithm like SHA256 would be a better pattern.

@rkoster My understanding is that we are doing this because MD5 is failing on FIPS compliant stemcells, not necessarily because MD5/SHA256 is safe or not. I think using some algorithm that is more known would be safer option here. I don't know who maintains xxh64 whereas SHA256 implementation is maintained by the Go team.

Had a call with @winkingturtle-vmw to do a bit more research on xxhash to address the well-known algorithm concern.
It turns out xxhash is being used in the linux kernel, as well as promethus.


Remove default use of repo.anaconda.com

Switch to miniforge instead of the conda executable from anaconda
to avoid any possible licensing issues given the new TOS.

I guess we need to specify MacOS for Darwin @oavdeev ?

The following test fails: 2021-12-22T08:22:13.1086300Z [pid 2956] ### test 'ResumeForeachInnerTest' graph 'nested-foreach' in context python3-all-local ###. Not sure why. I'll try re-triggering to see if it was a fluke.


New Example for Lovelace

This PR adds the following:

A new example for the lovelace dashboard that uses stack-in-card and lovelace-card-mod.
I also added the yaml-tags to the code snippets to have correct highlighting in web-browsers.

Screenshot of my Example

Comparison with and without yaml-tag
Before (without)
type: picture-entity
entity: light.bedroom
camera_image: camera.bedroom_hd
camera_view: live

After (with)
type: picture-entity
entity: light.bedroom
camera_image: camera.bedroom_hd
camera_view: live

This is great, thank you!


Bugfix/83 passwords exposed for ORA connections

Fix for #83.
This only covers ORA connections, the fix for EXA needs to be discussed (see #94).
This fix introduces a small change in behavior:

before this fix: To connect to Oracle the user/password from the provided JDBC connection was used. The user/password in the Oracle connection were ignored.
with this fix: The user/password from the Oracle connection is used. If this connection does not have user/password you have to specify the properties USERNAMEand PASSWORD.

Thanks for the review @redcatbear ! I implemented all changes, but one (created #96 for it).
Please approve, so I can merge.


IE9 - SCRIPT5: Access is denied

Hi,
I'm getting the following error when using IE9... (Yeah.. I know IE9 ...)
SCRIPT5: Access is denied.

userinfo.js, line 42 character 13

Thanks.

After investigating a little bit, it seems to be a crossorigin issue... I'm working on a fix.

Hey @sebz !
Thanks for raising the issue.
Let me know if you find something.

Fixed in pull request #6


How to have adaptive bitrate for mpeg dash (mpd) from rtmp for live streaming.

How can i stream a mpeg dash adaptive bitrate video from a rtmp live stream i am using this code.
With this i am having a single bitrate video stream, i want it to be adaptive.
rtmp {
    server {
        listen 1935;

   application dash {
        live on;
        allow publish all;
        allow play all;

        dash on;
        dash_path /Users/ahmedhassan/Documents/videos/dash/;
        dash_fragment 2s;
        dash_nested on;

    }
}

}

hi ,I am also very interested in this issue. If you know how to config it, please let me know.


Can't enter games where the losing score is 0

This is due to the state being a number initially defined as 0, and when you enter 0 as the losing score, the GG button is still disabled.

I'll address this with #5.

Actually, #4 is proving to be a little more complicated than I thought, so I'll make a separate hotfix for this.


[Question] Is Worldguard needed to protect the "wilderness" from harm to fire etc

Title says it basically
Can i use GD only  to have it protect the global world while allowing a player next to full control over their own piece of land as otherwise wg may override their attempt too
if so, which flag sections should be altered because its very confusing

GDs wilderness is a fully fledged claim where you can enable and disable whatever you want. there is no need for WG if you have GD installed, unless you want poly regions.
not sure what you mean by "can I use GD only to have it protect global" how would peopel claim their own land then?

well you basically answered that, i'd still use wg for spawn etc, but i dont need to tell it to stop fire spread etc thanks


feat(Gravsearch): Enable ORDER BY external link (DEV-2704)

Pull Request Checklist
Task Description/Number

Issue Number: DEV-2704
PR Type

[ ] fix: represents bug fixes
[ ] refactor: represents production code refactoring
[x] feat: represents a new feature
[ ] docs: documentation changes (no production code change)
[ ] chore: maintenance tasks (no production code change)
[ ] test: all about tests: adding, refactoring tests (no production code change)
[ ] other... Please describe:

Basic Requirements for bug fixes and features

[x] Tests for the changes have been added
[ ] Docs have been added / updated

Does this PR introduce a breaking change?

[ ] Yes

Does this PR change client-test-data?

[ ] Yes

I'm uncertain about how to interpret this PR. The underlying issue is related to an error in a specific query. You've added tests for two similar queries, but it appears that no changes were made to the production code. This raises some questions for me:

Does the error still exists in our stage environment where @mdelez has reported the problem? If it does, how does this PR address that issue? If not, do you know what resolved the original problem?
Your tests currently only assert the HTTP status code. Are we confident that the ORDER BY clause is functioning correctly? Would it be a good idea to include assertions to ensure that the returned results are ordered as expected? I would even suggest having a test that checks if ORDER BY DESC(?prop0) returns the reverse order.

I'm uncertain about how to interpret this PR. The underlying issue is related to an error in a specific query. You've added tests for two similar queries, but it appears that no changes were made to the production code. This raises some questions for me:

Does the error still exists in our stage environment where @mdelez has reported the problem? If it does, how does this PR address that issue? If not, do you know what resolved the original problem?
Your tests currently only assert the HTTP status code. Are we confident that the ORDER BY clause is functioning correctly? Would it be a good idea to include assertions to ensure that the returned results are ordered as expected? I would even suggest having a test that checks if ORDER BY DESC(?prop0) returns the reverse order.

Edit: I initially misunderstood the change to the AbstractPreQueryGenerator as a simple property ordering adjustment. However, upon closer inspection, I see that you've added two mappings: Xsd.Uri and KnoraApiV2Complex.UriValue. This addresses my initial question nr. 1.
Upon further reflection, and this may be a question for the issue creator, @mdelez: If I understand correctly, the 'uri' property being used for sorting contains the value of the actual URI. Is this really suitable for creating a meaningful order?

This small PR just enables something in already working sorting feature. I find the idea of checking the order in this case simply as the over-testing.

@seakayone Whether or not the ordering of a URI value is meaningful or not, I don't see a reason why we wouldn't allow a user to do it. It may be meaningful for the user in some way if they have very specific URIs that they know can be sorted alphabetically to help them find their data faster.

I found the searchextended route order being already checked in one of the SearchResponderV2Spec tests.


Make tooltips work with SVG elements

This will use getBoundingClientRect instead of offsetWidth/offsetHeight because it works with SVG elements instead.
getBoundingClientRect is supported in all major browsers.

This is stupid.  jQuery tooltips work just fine with SVG elements, yet bootstrap overrides it with tipsy, which has never worked with SVG and has the exact same outstanding issue.

@bjcullinan This issue is over three years old. I'm unsure if we've fixed it since then, but if you have a bug report to share with either v3.3.5 or v4.0.0-alpha, please open a new issue with a JS Bin examp.e


integration tests using tf-job is hanging

this blocking post commit tests to timeout

The job is getting launched and log streaming is getting stuck.

the issue seems to be change in label format in tf-controller https://github.com/kubeflow/tf-operator/commit/6f748507e0cafe787cb358b802176a53b6b11040


Flaky error reporting

==> Switching to working directory: /bitrise/src/rn/Teacher
yarn flow v0.27.5
$ flow check --show-all-errors | flow-result-checker
Found 1 error
error Command failed with exit code 1.

Randomly flow will claim to have found 1 error and print no errors. Running again will result in success and zero errors found.

This is likely fixed a long time ago.


[HOLD for payment 2023-04-07] [$1000] Added padding on edited quote message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open staging.new.expensify.com
Send a quote-only message, for example > Original Quote
Edit the message and edit the content inside the quote, for example > Edited Quote
Save the edited message and examine the padding difference between those two

Expected Result:
Edited quote and original quote should have the same padding
Actual Result:
Edited quote have some additional padding between the message and the element above it
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.90-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/228028174-34f8cdd9-3d29-47eb-bba1-dc08790298a1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @kerupuksambel
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679881185809169
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01835689e07f63bb21
Upwork Job ID:<PHONE_NUMBER>838272000
Last Price Increase: 2023-03-27

Job added to Upwork: https://www.upwork.com/jobs/~01835689e07f63bb21

Current assignee @sakluger is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

Triggered auto assignment to @dangrous (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

PROPOSAL
This padding is coming since we have a line break
 in the HTML received. This is why when we are trying to render it in ReportActionItemFragment.js we are seeing extra padding for edited comments.
if (!differByLineBreaksOnly) {
                const editedTag = props.fragment.isEdited ? '<edited></edited>' : '';
                const htmlContent = html + editedTag;
                return (
                    <RenderHTML
                        html={props.source === 'email'
                            ? `<email-comment>${htmlContent}</email-comment>`
                            : `<comment>${htmlContent}</comment>`}
                    />
                );
            }

Solution:
We can replace the
 tag with blank space to resolve it.
if (!differByLineBreaksOnly) {
                const editedTag = props.fragment.isEdited ? '<edited></edited>' : '';
                const htmlContent = html + editedTag;
                return (
                    <RenderHTML
                        html={props.source === 'email'
                            ? `<email-comment>${htmlContent}</email-comment>`
                            : `<comment>${htmlContent}</comment>`.replace('
', '')}
                    />
                );
            }

📣 @ajaynagwani777! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

📣 @ajaynagwani777! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork. Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01a34e4c438af482d0

@s77rt I've replicated the issue and fixed it too. Can you please review it again?
Before:

After:

@ajaynagwani777 Thanks for the update. However it's not about how we fix the bug here. It's more about understanding the root cause and I don't think your RCA is correct, for instance you didn't explain why we have a new line in the first place.

@s77rt I've updated my proposal with a detailed RCA. Can you please have a look?

@ajaynagwani777 Thanks for the quick update. Still not the correct RCA. I will help you on this one. The issue seems occurring in the process of converting markdown to html for edited messages where a text like > hi gets incorrectly converted to

hi
. I think the bug is on handleUserDeletedLinks.

@s77rt Yeah. Then this is where it starts and then the HTML created is wrongly parsed. I've updated my proposal.

@ajaynagwani777 Thanks for the update. Your RCA is not accurate.

Please re-state the problem that we are trying to solve in this issue.
Editing a quote message add an extra leading
 to the quote message, which is rendered as a line break
What is the root cause of that problem?
When translating html blockquote tag to markdown, we simply wrap it with a leading and a trailing line break. For example, html

hi

will be translated into markdown string
\n> hi\n

If we change the markdown text to
\n> hi test\n

and save it, then markdown text
\n> hi test\n

will be translated to html

hi test

by applying markdown-to-html rules
https://github.com/Expensify/expensify-common/blob/9cf047b9741d3c02820d515dccb9e0a45b6595f5/lib/ExpensiMark.js#L156-L169
and
https://github.com/Expensify/expensify-common/blob/9cf047b9741d3c02820d515dccb9e0a45b6595f5/lib/ExpensiMark.js#L175-L179
The leading line break will be translated to the extra
 tag.
To have a closer look at the root cause, let's try another example.
Send a quote message
> quote message

In the editing mode, change the markdown string
\n> quote message\n

to (remove the leading and trailing line break)
> quote message test

Save it and the leading line break is still there.
This is because when we save a changed message, we don't simply call ExpensiMark#replace() once to get the html to save in backend. Instead, we do markdown-to-html, html-to-markdown and markdown-to-html conversion to get the final html to save. So the markdown input of the last markdown-to-html conversion is
\n> quote message test\n

instead of
> quote message test

See handleUserDeletedLinks
https://github.com/Expensify/App/blob/0763be562293a1b9e3782eaeee0843a7f805e38d/src/libs/actions/Report.js#L830-L840
So the root cause is the invalid regex rule to translate html
 to markdown.
What changes do you think we should make in order to solve the problem?
To fix this issue, we should improve the regex rule to translate blockquote tag to markdown. Instead of simply wrapping it with a leading and trailing line break, we should only add line break if there's non-empty text before or after the
. We can improve the replacement formatting from
https://github.com/Expensify/expensify-common/blob/9cf047b9741d3c02820d515dccb9e0a45b6595f5/lib/ExpensiMark.js#L263
to the following
return `[block]${resultString}[block]`;

Then we can reuse this function ExpensiMark#replaceBlockWithNewLine to handle line break properly. See
https://github.com/Expensify/expensify-common/blob/9cf047b9741d3c02820d515dccb9e0a45b6595f5/lib/ExpensiMark.js#L458-L468
What alternative solutions did you explore? (Optional)
Call trim method for markdown text

@hoangzinh Thanks for the proposal. Your RCA is so-so, it's indeed related to htmlToMarkdown but I don't think you are referencing the most relevant code here.

@hoangzinh I'm sorry but I don't think your proposal does that. You are proposing the change here which won't work. Where the required changes are here. Am I missing something?

@s77rt Thanks for reviewing my proposal!
I added more details to the alternative solution part, please see my updated proposal

@eh2077 Thanks for the update. I have already approved your proposal, we will discuss the details on the PR. Waiting for  @dangrous review.

Yep I think this makes sense! Assigning you now @eh2077!

📣 @eh2077 You have been assigned to this job by @dangrous!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

📣 @eh2077 You have been assigned to this job by @dangrous!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Applied the job and PR is under review!

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.92-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/16678

If no regressions arise, payment will be issued on 2023-04-07. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@s77rt / @dangrous] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@s77rt / @dangrous] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@s77rt / @dangrous] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@sakluger] Determine if we should create a regression test for this bug.
[ ] [@s77rt] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Regression test looks good @s77rt! Verifying in Slack whether or not we want to add to the checklist, in that discussion you started.

Hi @s77rt @eh2077 @kerupuksambel - I just send you all offers on the Upwork job (https://www.upwork.com/jobs/~01835689e07f63bb21). Sorry I didn't invite you sooner! Once you accept the offer, I can pay out for this issue.

I think we should add regression steps for this one, thanks for writing those up! Created a GH issue to add testrail steps here: https://github.com/Expensify/Expensify/issues/274604

@sakluger The offer seems no longer available.

Sorry about that @s77rt, I'm not sure what happened. I sent you a new contract (the related job may be wrong, but the contract title is correct).

@sakluger No problem, I have just accepted the offer.

All paid out, thanks for your patience on this one!


Clean up the CA API in istio/istio

Please provide a description for what this PR is for.
This PR is part of to the API definition move: istio/api#1520.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ X ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test release-notes_istio

unit-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test unit-tests_istio

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
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.

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

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

integ-operator-controller-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

integ-ipv6-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

integ-distroless-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

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

integ-pilot-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

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

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

integ-telemetry-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

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

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

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

integ-multicluster-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
1a7533b55cd9c79d8151f5dd9ba29e298e3ed140
link
/test integ-security-k8s-tests_istio

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

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

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

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

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

integ-mixer-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test unit-tests_istio

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

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

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

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

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

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

integ-mixer-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
link
/test integ-mixer-k8s-tests_istio

integ-security-k8s-tests_istio
b20904c5da0f67e8a99ae121c1fe901f61c44a27
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.

Closing this for a dup of https://github.com/istio/istio/pull/25677