fix: Low version browsers do not have the at function

[shaohuzhang1]

fix: Low version browsers do not have the at function

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[shaohuzhang1]

The provided code is mostly clean, but there's one line that can be optimized. Here’s the relevant part:

const run_node = this.node_list.filter((item) => item.buffer.length > 0 || !item.is_end)[0];

This line uses filter with an array containing exactly one element, which can be written more directly using bracket notation:

const run_node = this.node_list[0] || null;

However, since you're checking both conditions (buffer.length > 0 and !item.is_end), you should maintain the original logic while simplifying it a bit by removing redundant steps:

const node_length_greater_than_zero = !!this.node_list.filter(x => x.buffer.length > 0).length;
const node_isnt_finished = !!this.node_list.find(x => !x.is_end);

if (node_length_greater_than_zero && node_isnt_finished) {
    // Your logic here
}

But if you want to keep everything concise and efficient without unnecessary nesting, you could just use:

const next_runnable = this.node_list.filter(item => item.buffer.length > 0 || !item.is_end)?.shift();

If none of these options meet your requirements, please let me know how I can assist further.