refactor some string operations with StringUtils

What is the purpose of the change
refactor some string operations with StringUtils
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #5112 into master will decrease coverage by 0.01%.
The diff coverage is 38.88%.

@@             Coverage Diff              @@
##             master    #5112      +/-   ##
============================================
- Coverage      64.1%   64.08%   -0.02%
  Complexity      453      453
============================================
  Files           769      769
  Lines         33263    33248      -15
  Branches       5250     5238      -12
============================================
- Hits          21324    21308      -16
- Misses         9504     9518      +14
+ Partials       2435     2422      -13

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/org/apache/dubbo/common/URLBuilder.java
59.86% <100%> (+0.65%)
0 <0> (ø)
:arrow_down:

...src/main/java/org/apache/dubbo/common/Version.java
62.62% <33.33%> (ø)
0 <0> (ø)
:arrow_down:

...mon/src/main/java/org/apache/dubbo/common/URL.java
51.5% <35.71%> (+1.28%)
0 <0> (ø)
:arrow_down:

.../apache/dubbo/qos/protocol/QosProtocolWrapper.java
65.85% <0%> (-17.08%)
0% <0%> (ø)

...g/apache/dubbo/rpc/protocol/rest/RestProtocol.java
68.21% <0%> (-3.11%)
0% <0%> (ø)

...pache/dubbo/registry/support/AbstractRegistry.java
78.54% <0%> (-3.07%)
0% <0%> (ø)

.../rpc/protocol/dubbo/LazyConnectExchangeClient.java
56.47% <0%> (-2.36%)
0% <0%> (ø)

...a/org/apache/dubbo/monitor/dubbo/DubboMonitor.java
89.71% <0%> (-0.94%)
16% <0%> (-1%)

...g/apache/dubbo/registry/consul/ConsulRegistry.java
61.87% <0%> (-0.63%)
29% <0%> (ø)

...rg/apache/dubbo/common/timer/HashedWheelTimer.java
62.75% <0%> (+0.34%)
0% <0%> (ø)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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

LGTM

well done


Add a basic state repr

Codecov Report

Merging #35 into master will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
+ Coverage   97.17%   97.25%   +0.07%
==========================================
  Files           4        4
  Lines         283      291       +8
  Branches       43       45       +2
==========================================
+ Hits          275      283       +8
  Misses          4        4
  Partials        4        4

Impacted Files
Coverage Δ

src/awsstepfuncs/state.py
97.47% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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


Accepting Hacktobefest Contributions

Is your feature request related to a problem? Please describe.
No, not a problem but for enhancing and adding more git commands to the repository.
Describe the solution you'd like
This is to inform that this repository is eligible for hacktoberfest and you can add more git commands or any new features to this repository.
Additional context

@MrKrishnaAgarwal would you assign this to me?

@MrKrishnaAgarwal would you assign this to me?

Definitely! Looking forward to your contribution.

@MrKrishnaAgarwal would you review my pull request

@loftydroid please fix the grammatical errors and make a new PR.

It will be done by today.

It will be done by today.

Sure, waiting.


Selection on TabFolder is wrong when setting programmatically

Problem description
Creating a TabFolder with paging enabled and setting the selection to another tab programmatically shows the new tab as expected. In the fired selectionChanged event the new tab is given as the event value. However when getting the current selection from the TabFolder in the selectionChanged event it still returns the previous tab.
Expected behavior
Inside the selectionChanged event the TabFolder.selection should be up to date to reflect the new selected tab.
When disabling paging the selection is updated as expected.
Environment

Tabris.js version: nightly
Device: iPhone SE
OS: iOS 10.3.2

Code snippet
const {Tab, TabFolder, TextView, ui} = require('tabris');

let tabFolder = new TabFolder({
  left: 0, top: 0, right: 0, bottom: 0,
  paging: true
}).on('selectionChanged', ({value: tab}) => {
  console.log(`selectionChanged tab: ${tab.title}`);
  console.log(`tabFolder tab: ${tabFolder.selection.title}`);
}).appendTo(ui.contentView);

createTab('One');
let tab2 = createTab('Two');

function createTab(title) {
  let tab = new Tab({
    title: title,
  }).appendTo(tabFolder);
  new TextView({
    centerX: 0, centerY: 0,
    text: 'Content of Tab ' + title
  }).appendTo(tab);
  return tab;
}

setTimeout(() => tabFolder.selection = tab2, 1000);

Fixed in https://github.com/eclipsesource/tabris-ios/commit/c66e2d0d8425df76ed0ffde5c4d9d4ff4179c5b5


Release on Microsoft Store: Process for v7.x.x

Summary of the new feature/enhancement
It is more convenient that PowerShell could update itself, with a prompt or automatically through a setting so that while it informs that there is a new update available, the user can update it on the fly and not by manually downloading a package or installer and go through a repetitive process.
Proposed technical implementation details (optional)
This is more of a release process. I suggest that like Windows Terminal that has moved on to Microsoft store, the PowerShell does too, so updates get handled by an already familiar and growing platform for devs on windows (since many features like WSL distros did too).
As for other release targets, I suggest releasing the package for their package managers and to their repositories, like official apt or rpm repositories for Debian or RedHat respectively.

This is a duplicate of #7730


Crashes if the Verdana font is missing

Hi,
I wanted to give this awesome tool a try but it made my JUCE app crash at startup. I debugged it and traced it down to this assertion because the melatonin_inspector was asking for the "Verdana" font which my Linux machine didn't have. I worked out how to install Verdana and now it works great!
It would be great to either mention in the documentation that you need to have Verdana, or have some kind of fall-back mechanism for font selection (no idea how - I'm very new to JUCE) or use one of the default fonts (juce::font::getDefaultSansSerifFontName()).
Thanks for the great tool!

Thank you for this, we don't have anyone testing on linux, though there are tests on linux. I'll have to make sure those are properly opening the app, I think I recently removed the "run and screenshot" there (or maybe verdana is default on the github runners).
Falling back to juce::font::getDefaultSansSerifFontName() sounds great. Will happily merge a PR for that if you are in the mood! Otherwise I'll take a look next time I'm working on the tool.
Thanks again for the report — hope the tool is worth it so far!

I'm quite unfamiliar with GitHub workflows. Let me know if the code (and process) looks good.


test framework: support hostname loadbalancer in ingress

In environments such as AWS, LoadBalancer may be supported, but never set LoadBalancer[0].IP – instead it sets Hostname.
Our framework should be robust to handle testing in such environments.
We will also want to handle this for multicluster, this PR isn't concerned with that for now.

Adding a hold so I can try testing this out in the affected env.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test release-notes_istio

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test lint_istio

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

analyze-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
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.

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

Test name
Commit
Details
Rerun command

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

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
d25434edd7c2926b5f06812984593100b39bd6ff
link
/test integ-security-multicluster-tests_istio

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-multicluster-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.

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

Test name
Commit
Details
Rerun command

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

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
8ebf3a1a07d566d4e8a3890ce71cab7070d79146
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
b2ef8a3c671d0a76b076dffc7f5b369b5634ff88
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
b6e90a6e8955657feec08a056fd0e039cef69648
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.

/retest

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
b6e90a6e8955657feec08a056fd0e039cef69648
link
/test integ-security-multicluster-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.

/retest

In response to a cherrypick label: new pull request created: #32408


internal compile rerror

The error is: vendor\github.com\seancfoley\bintree\tree\trienode.go:542:25: internal compiler error: method GetBitCount on *uint8 not found
when i run golang project

This looks very similar to https://github.com/seancfoley/ipaddress-go/issues/4 which I could not reproduce.
It looks a lot like https://github.com/golang/go/issues/54225

What version of go are you using?

No response from the bug opener, so closing.
This looks like https://github.com/golang/go/issues/54225, a regression with earlier versions of go version 1.19 that has since been fixed in later versions.


Porting Modbus Library: Need some guidance

Good day! I am just starting to be active on this project and after my last botched PR, I need some advice and direction.
I am attempting to port this ModBus Library to Zephyr and although I am still learning on the steps, I can't seem to successfully compile it or link it. This is the link to the original library:
https://github.com/Jacajack/liblightmodbus
I first built the library by itself and after verification I proceeded to look for a template code.
I have found and build the /samples/application_development/external_lib and flashed it to my Nucleo board to verify it. Afterwards I used this as my base and cloned the Modbus Library.
First problem is that the external_lib template uses make but the Modbus Library uses cmake first before make.
Second problem is after I disabled the "ExternalProject_Add" and proceeded in linking the prebuilt library. I suddenly got "liblightmodbus/build/liblightmodbus.a: error adding symbols: File format not recognized".
I'm still in the process of learning but right now I need any help on where I can identify where my mistake is. Any advice is appreciated.
Here is my most recent log when I just attempted to link the prebuilt library.
 Forgot that I can attach a log file. I have posted the log flies from the original library and ported one.

Here is the updated log after I ported the library into Zephyr. Please advise me where I have made the mistake.
stdout.log
CMakeLists.txt

Second scenario is I force the cmake to generate Unix Makefiles but it gives ma an error.  It looks like mixing -GNInja and -GUnix Makefiles is not good. Maybe this is also the reason I am seeing my first issue above?
Any ideas are welcome.
stdout2.log
CMakeLists2.txt

@Josh0027 Did you get anywhere with this, and where is the repository you've been working in?

@firmwareguru @Josh0027 Although we have modbus RTU on it's way for in-tree Zephyr (https://github.com/zephyrproject-rtos/zephyr/pull/26516), I did tried to use liblightmodbus for my personal use case. Adding my attempts just for the completion of this thread.
Am able to successfully compile and use the sample in zephyr.
Changes in liblightmodbus is here: https://github.com/linumiz/liblightmodbus
Changes with example in zephyr is here: https://github.com/linumiz/zephyr/tree/liblightmodbus


Can I create a good navbar with better UI design

Describe the feature
Making the navbar flow good with the use of great colour combination.
Add ScreenShots
.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

Could you share the ss to which you are changing into?

Not able to differentiate between navbar height and main page. I think you understand.
Want to enhance the user interface.
Also want to create a good navbar with better UI.


Delphi versions support

Currently I support 10.3 and 10.4.  Please comment on this issue if you need older versions supported and which version(s) you are using so i can prioritize.

Support is now extended to 10.0, 10.1. 10.2 as well as 11


Frequent calls to docker-credential-desktop and osascript when doing a copy

What steps did you take:
I was attempting to copy the image from these instructions: https://docs.vmware.com/en/VMware-Tanzu-Application-Platform/1.4/tap/install-aws.html
The copy was from a password-protected repository at registry.tanzu.vmware.com to a non-password-protected docker container registry.
What happened:
This is 214 images and approx 7GB of data.  I noticed that it took a long time (more than 2 minutes) to collect all the information for the clone, and while that was happening, the terminal title was flashing between osascript, sw_version and a few other commands.  A ps revealed the following:
28423 ttys011    0:01.87 imgpkg copy --concurrency=1 -b registry.tanzu.vmware.com/tanzu-application-platform/tap-packages:1.4.0 --to-repo registr
31366 ttys011    0:00.02 docker-credential-desktop get
31370 ttys011    0:00.09 osascript -e user locale of (get system info)

As an approximate guess, this looks like approx (31370 - 28423) / 4 > 700 invocations of docker-credential-desktop get, which seems excessive.  This seems to continue; after 5 minutes, there seem to have 1200 invocations (or approx 2/second).  Nothing else seems to be spawning processes on my machine (idle except for typing this bug report into Chrome).  Overall, it took 8 minutes to collect the information for these 214 images, and then approx 1 minute to verify that all the images had been copied to the destination registry (I'd prevously copied most images, so this should have been a metadata-only comparison).
What did you expect:
One invocation of docker-credential-desktop get per registry, or perhaps one per minute.
Anything else you would like to add:
This is running 0.35.0; looking through previous bugs, #334 looks related but clearly doesn't seem to have helped in this case.
Running with --debug doesn't show a lot of requests to the /v2 endpoint for authentication as described in #290
Environment:

imgpkg version (use imgpkg --version):

imgpkg version v0.35.0

Docker registry used (e.g. Docker HUB):
Self-install of Docker registry image from https://github.com/evankanderson/k8s-private-local-registry

OS (e.g. from /etc/os-release):

Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

(This is also adding 4+ minutes after the copy completes.  I'm doing a repo-to-repo copy)

This seems to be invoked about once per call to https://github.com/carvel-dev/imgpkg/blob/develop/pkg/imgpkg/registry/auth/custom_keychain.go#L62, still digging as to why.

It appears that we're constructing a new RoundTripper every time, here:
https://github.com/carvel-dev/imgpkg/blob/develop/pkg/imgpkg/registry/registry.go#L265
I'm guessing it's because the ref.Context object is different each time, and we should be using a string version of the Registry value.

Nevermind, we are finding the correct RoundTripper, but it's not caching the credentials at all.

I'm currently looking at https://github.com/carvel-dev/imgpkg/blob/develop/pkg/imgpkg/registry/registry.go#L244, and wondering whether we should be caching the set of []regremote.Option

(have to put this down for the evening, though)

Looking in go-containerregistry, it looks like supplying a keychain (as we do) calls o.keychain.Resolve(target) to get an authn.Authenticator each time.  I'm going to see if we can cache this.
Ref:
https://github.com/google/go-containerregistry/tree/main/pkg/v1/remote/options.go#L140

It looks like augmenting SimpleRegistry.transport to cache authenticators solves this, will be trying to put together PR shortly.


Support 'classpath:' and 'file:' URLs for URIConnectors in YAML

Change URIConnectorFactoryFactory.connectors to ResourceFactory to represent resource as URL with "classpath:", 'file:", etc. protocols and resource as absolute or relative file path.

#5


Send messages on events where the marathon appId matches given regex

In a large data-center the operations team would like to be notified of marathon events matching some Regular Expression pattern. This pull request allows users to specify a Marathon env var APP_ID_REGEXS which is a comma separated list of strings to filter events by.

Thanks for the PR! Could you please add an example of the usage to the Readme as well?

Do you also need an update of the DC/OS Universe package @eodgooch?

I'll go ahead and update the DC/OS package once you approve updates. What version tag? 0.3.2?
I am also considering adding an env var to log events. Not sure if this is something you want in the project. My goal is to log events to get picked up by our shipper and sent to ES. Let me know.

I implemented the desired changes in https://github.com/tobilg/marathon-slack/commit/af88c18c77ed0563b90b660750df986c03b310fa The Docker image is currently building in version 0.4.0.


phantomjs 2.0 cannot attach file with js: true

I originally opened this with capybara - https://github.com/jnicklas/capybara/issues/1494

On Mac, I upgraded to phantomjs 2.0 using homebrew and immediately couldn't attach a file in test cases that required :js. It's working without js: true.
Downgrading to "phantomjs192" resolved the issue.

It's known issue see phantomjs issues

@route can you reference the phantomjs issue? I mean upgrading to poltergeist 2.0 makes no sense if you cannot attach a file in specs :/

Upstream issue: https://github.com/ariya/phantomjs/issues/12506


sap.m.Select not recognized as readonly when editable is set to false

OpenUI5 version:
latest and older
Browser/version (+device/version):
any
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
https://sapui5.hana.ondemand.com/#/entity/sap.m.Select/sample/sap.m.sample.Select
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

set the property "editable" to false
use keyboard navigation to set focus on the select control

Same is with sap.m.MultiComboBox (and maybe other controls, maybe Screen-Reader compatibility with "editable"-property set to false should be checked in general...)
What is the expected result?
Screen-Reader should recognize the control as "read-only"
What happens instead?
Screen-Reader does not recognize the control as "read-only" and announces that value of the control can be changed. When the control gets focus, it appears to be editable, which is not true.
Any other information? (attach screenshot if possible)

Hi @wurst0815,
I've created an internal incident for you: DINC0305078.
We will get back to you as soon as possible.


Update readme with installation instructions

Hi Steffaan,
Thanks for taking on this plugin.
Can you update the readme with installation instructions?  Since your fork is not handled by npm, what are the manual steps to swap to this fork?
Also, the changelog is reporting 0.8.5 as the version.  I would be good to update to 0.9.1 for consistency.
Thanks again...

Updated the Changelog and Readme.
I also included a new section in the Readme which explains the new channels for Android.


[WIP] Added _.create test, improved _.clone test for lodash

Firstly, the _.clone test was not failing consistently, for two reasons: $ExpectError appears to cover the following block, not just the following line. If you have 2 lines that throw flow errors, and put // $ExpectError before the first line but not the second, both lines are allowed to pass the test. Secondly, the object passed to _.clone() was not typed strongly enough.
The main reason I have opened this PR is that _.create is not typed correctly. However, I can't find a way to do it correctly, so I'm opening this in the hope someone can help out.
var createdObj = _.create(createProto, {b: 2});
createdObj.b == 2;

This should pass, but flow errors out because the return type of create<T>(prototype: T, properties?: Object) is currently $Supertype<T>, making no mention of properties in the returned object.
Two points I can make with my limited understanding of OOP: Shouldn't the returned object be a subtype of T, not a supertype? And how can we, in flow syntax, express the relationship of the returned object both to the prototype T and the properties P?

This hasn't been updated for quite a while and I can't add commits to the PR.
If this is still relevant please submit a new PR.


Errors invoking VSCode from external application when debugging

Hi,
I'm working on the integration of VSCode with Unreal Engine, specifically our source code navigation systems. I've found a problem where I have build and run the editor through VSCode, but then subsequent attempts to open a class from the editor, or navigate to a particular file/line will fail with an error message in VSCode like this:
module.js:472
    throw err;
    ^

Error: Cannot find module '/Users/graemethornton/Epic Games/UE4'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:431:7)
    at startup (bootstrap_node.js:155:9)
    at bootstrap_node.js:551:3

Note that in this case, the arguments to VSCode that I passed on the command line were these:
"/Users/graemethornton/Epic Games/UE4/" "/Users/graemethornton/Epic Games/UE4/EngineTest/Source/EngineTest/EngineTestUtilityLibrary.h" "/Users/graemethornton/Epic Games/UE4/EngineTest/Source/EngineTest/EngineTestUtilityLibrary.cpp"

This only happens when I'm running the editor as a debug session from within VSCode. If I just launch the editor from the OS and then do exactly the same thing, it all works correctly.
Any ideas?

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T12:32:39.870Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

cpptools
ms-
0.14.0

csharp
ms-
1.13.0

mono-debug
ms-
0.15.8

perforce
sle
2.2.2

vscode-lldb
vad
0.7.1

How does your launch config for the editor look like?

{
	"name": "EngineTestEditor (Development)",
	"request": "launch",
	"preLaunchTask": "EngineTestEditor Mac Development Build",
	"program": "/Users/graemethornton/Epic Games/UE4/Engine/Binaries/Mac/UE4Editor.app/Contents/MacOS/UE4Editor",
	"args": [
		"EngineTest"
	],
	"cwd": "/Users/graemethornton/Epic Games/UE4",
	"type": "lldb"
}

Please report this issue against the "lldb" debugger extension (which is not part of VS Code).


Fix ABAP Language Version Handling for Repository Setting "Any" for AFF Object Types

Fixes #6791

@mbtools Thanks for the review.
I have tested it with a repository containing object types CHKO, CHKC and CHKV. For these it worked fine, now.


Update import paths in gh-pages

See #518

Ballin! Was just about to do this! You're on top of it!


Tutorial: choice of KDE kernel width

The tutorial contains the following comment : " In order to get good information out of a histogram, you have to choose a suitable bin size. This is a fiddly manual task. In contrast, a KDE is likely to be informative immediately, with no configuration required." (source : http://www.serpentine.com/criterion/tutorial.html#understanding-charts )
This is incorrect, since any kernel estimate depends on the (arbitrary) choice of kernel width.
Does criterion infer the kernel size from the data?

Yes.

And where in the sourcecode is this estimation made?


Compiler misreads try-catch.

The following event handler:
  add(e) {
    try {

    } catch(e) {
      console.log(e);
    }
  }

compiles into this:
  this.add = function(e) {
    try {

  this.catch = function(e) {
      console.log(e);
    }
  }

Which it shouldn't

maybe related to https://github.com/muut/riotjs/issues/141

Thanks. WIll fix.


Remove imgui support in favor of egui

Most Rust project use the native egui instead, including us so we don't want to maintain imgui support that we don't use.
Significantly reduces the dependency tree for development as we were pulling in old winit and almost deprecated glium renderers for it (egui uses wgpu).
cargo-vet stats (the exempted number is the most important):

Before: Vetting Succeeded (168 fully audited, 10 partially audited, 173 exempted)
After: Vetting Succeeded (151 fully audited, 10 partially audited, 133 exempted)

Resolves: #139
Resolves: #134

Shall we open an issue on imgui-rs to see if they want ownership?

nah don't think so, they do not own any applications built on imgui, just the imgui bindings themselves

Probably! Should we bother creating new repo with last code and archive it?

I think publishing a last release of the crate before this is merged, and changing the maintenance status in Cargo.toml to unsupported (think the as-is badge status listed here https://doc.rust-lang.org/cargo/reference/manifest.html#the-badges-section). then we have a release tag or commit hash for that which can be referenced for anyone wanting to get the last version. so no need to create a separate repo


Add Bitcoin.com Store to 'Services' section

The Bitcoin.com Store has been relaunched and is fully behind Bitcoin Cash (it's the only currency we support)!
Logo attached below:

Can you actually submit a PR for this?


Python3, video_gstplayer.py, line 88: self.player.set_volume(self.volume)  AttributeError: 'NoneType' object has no attribute 'set_volume'

Traceback (most recent call last):
File "/home/johndoe/kivy-examples/demo/kivycatalog/main.py", line 166, in
KivyCatalogApp().run()
File "/usr/lib/python3/dist-packages/kivy/app.py", line 825, in run
runTouchApp()
File "/usr/lib/python3/dist-packages/kivy/base.py", line 484, in runTouchApp
EventLoop.window.mainloop()
File "/usr/lib/python3/dist-packages/kivy/core/window/window_pygame.py", line 381, in mainloop
self._mainloop()
File "/usr/lib/python3/dist-packages/kivy/core/window/window_pygame.py", line 285, in _mainloop
EventLoop.idle()
File "/usr/lib/python3/dist-packages/kivy/base.py", line 324, in idle
Clock.tick()
File "/usr/lib/python3/dist-packages/kivy/clock.py", line 483, in tick
self._process_events()
File "/usr/lib/python3/dist-packages/kivy/clock.py", line 615, in _process_events
event.tick(self._last_tick, remove)
File "/usr/lib/python3/dist-packages/kivy/clock.py", line 374, in tick
ret = callback(self._dt)
File "/usr/lib/python3/dist-packages/kivy/uix/video.py", line 177, in _do_video_load
self._video.play()
File "/usr/lib/python3/dist-packages/kivy/core/video/video_gstplayer.py
", line 88, in play
self.player.set_volume(self.volume)
AttributeError: 'NoneType' object has no attribute 'set_volume'

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7162410-python3-video_gstplayer-py-line-88-self-player-set_volume-self-volume-attributeerror-nonetype-object-has-no-attribute-set_volume?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

@macropas is correct, the package is missing softboy.mpg.
As a workaround, try this:
# Manually copy the file into place, since the package is missing it.
sudo bash
cd /usr/share/kivy-examples/widgets/
wget https://github.com/kivy/kivy/raw/master/examples/widgets/softboy.mpg
exit

# Now launch the demo
python /usr/share/kivy-examples/demo/kivycatalog/main.py

This puts an uncontrolled file softboy.mpg into /usr/share/kivy-examples/demo/, which is bad sysadmin practice. It will eventually conflict with the package when they fix it. You can just delete the file when you're done playing, or else make a copy of the demo's main.py and edit it to use a copy of softboy.mpg under your $HOME directory.


JFFI leaves stale jffi*.dll files in temp folder

This is a duplicate of https://github.com/jruby/jruby/issues/3657
But I put it here because I also observed this issue on windows with JFFI directly (without using JRuby).
Do you know if there is a workaround?
Additional information:
OS: Windows 10
jnr-ffi 2.2.1

@david-bouyssie This is unfortunately still a known issue without a resolution (thanks for filing this so it is clear that jruby/jruby#3657 is a jffi issue).
As described in the JRuby issue, this is a limitation on Windows, preventing files from being deleted if they are still open in some process. We have looked at various ways to fix it internally but it is not an easy thing to solve.
The workarounds described in that issue are still valid and the best workaround for now: set up JVM properties to point at an already-unpacked version of the DLL, and we will not unpack another one.
I also describe there a possibility of using NIO.2 features to make the file deletable, but all opens of that file would have to use the same flags... including the open done by the JDK's own System.loadLibrary. Because of that, we still do not have a reliable solution to this problem (other than using JVM properties to point at a known location for the DLL.

Ok so the workarounds are not perfect and we may need yet another.

The JVM property jffi.extract.dir will put the files in a directory you control.
jffi.boot.library.path can be set to point at a directory with an already-extracted DLL, but it must match the naming in the native jar.

However neither of these address your issue directly. It may be worth us adding a third property that is a full path from which we should load (and if it does not exist, to which we should extract) the native stub. That would allow you to be sure all executions use the same DLL.

Thank you that's helpful.
What do you mean when you say "but it must match the naming in the native jar"?
Do you have an example?

I tried different settings, and yes I confirm, having a full path would be the best solution.
Actually this is what I'm also using for the library I want to load.
In my case I specify it through a static method call (I defined a MyLibraryEnv static class that I use for configuration/extraction from resources).

Back in the office today and I will be looking into this today. I think the best option at this point would be to provide a property you can set that will unpack the dll in a given location always and use the file that is there as long as it matches the one in the jar. That would not delete the file when finished, but it will not keep creating new ones.
Would that be sufficient for your case?

Yes would be perfect!
This is the solution I have currently implemented myself (by extracting my own copy of the libraries + setting jffi.boot.library.path ), but would be great if it was builtin.

@david-bouyssie I have pushed a prototype of this behavior in #99, perhaps you could give it a try and see if it does what you need?

This is not really fixed but it may not really be fixable. The improvements in #99 should help mitigate this problem for folks on Windows.

jffi-1.3.2 has been released!

Awesome 😃

@headius - silly question here, but since jffi is part of the JRuby release, would this then be a part of the next release of JRuby?

Would be also great to release the artifact "jnr-ffi" based on jffi 1.3.2.


Disabled Buttons in Ribbon should not hover and change to clicked style on click

It would be a better visualisation of the disabled state.

I will fix it in 4.3.8

I did like this:
.ribbon-button[disabled] {
    background: transparent;
    border: none;
    opacity: 0.5;
}

.ribbon-icon-button[disabled] {
    background: transparent;
    border: none;
    opacity: 0.5;
}

fixed in 4.3.8. Use attribute disabled or class disabled